1、 ETSI TS 129 500 V15.0.0 (2018-07) 5G; 5G System; Technical Realization of Service Based Architecture; Stage 3 (3GPP TS 29.500 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 129 500 V15.0.0 (2018-07)13GPP TS 29.500 version 15.0.0 Release 15Reference RTS/TSGC-0429500vf00 Keywords 5G
2、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 document can be downloaded from: ht
3、tp:/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 case of any existing or perceived
4、 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 document may be subject to revision
5、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:/portal.etsi.org/People/CommiteeSu
6、pportStaff.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 without the written author
7、ization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the b
8、enefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 129 500 V15.0.0 (2018-07)23GPP TS 29.500 version 15.0.0 Release 15Intellectual Property
9、 Rights Essential patents IPRs essential or potentially essential to normative deliverables 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
10、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 searches
11、 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. Trademarks The present document may include trademarks and/or
12、tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not c
13、onstitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their
14、3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the prese
15、nt 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 Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables
16、except when used in direct citation. ETSI ETSI TS 129 500 V15.0.0 (2018-07)33GPP TS 29.500 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 A
17、bbreviations . 7g34 Service Based Architecture Overview 7g34.1 NF Services 7g34.2 Service Based Interfaces 7g34.3 NF Service Framework 7g34.3.1 General 7g34.3.2 NF Service Advertisement URI 8g35 Protocols Over Service Based Interfaces . 8g35.1 Protocol Stack Overview 8g35.2 HTTP/2 Protocol 9g35.2.1
18、General 9g35.2.2 HTTP standard headers . 9g35.2.2.1 General 9g35.2.2.2 Mandatory HTTP standard headers . 9g35.2.3 HTTP custom headers . 10g35.2.3.1 General 10g35.2.3.2 Mandatory to support custom headers. 10g35.2.3.2.1 General 10g35.2.3.2.2 3gpp-Sbi-Message-Priority . 10g35.2.4 HTTP error handling .
19、 11g35.2.5 HTTP/2 server push 11g35.2.6 HTTP/2 connection management . 11g35.2.7 HTTP status codes 11g35.2.7.1 General 11g35.2.7.2 NF as HTTP Server . 12g35.2.7.3 NF as HTTP Client . 14g35.2.8 HTTP/2 request retries 15g35.3 Transport Protocol 15g35.4 Serialization Protocol . 15g35.5 Interface Defini
20、tion Language 15g36 General Functionalities in Service Based Architecture 16g36.1 Routing Mechanisms 16g36.1.1 General 16g36.1.2 Identifying a target resource . 16g36.1.3 Connecting inbound 16g36.1.4 Pseudo-header setting . 16g36.1.4.1 General 16g36.1.4.2 Routing within a PLMN 17g36.1.4.3 Routing ac
21、ross PLMN . 17g36.1.5 Host header . 17g36.1.6 Message forwarding 17g36.2 Server-Initiated Communication 17g36.3 Load Control 18g36.4 Overload Control 18g36.4.1 General 18g3ETSI ETSI TS 129 500 V15.0.0 (2018-07)43GPP TS 29.500 version 15.0.0 Release 156.4.2 HTTP Status Code “503 Service Unavailable“
22、 18g36.4.3 HTTP Status Code “429 Too Many Requests“ . 19g36.4.4 HTTP Status Code “307 Temporary Redirect“ . 19g36.5 Support of Stateless NFs 19g36.5.1 General 19g36.5.2 Stateless AMFs . 19g36.5.2.1 General 19g36.5.2.2 AMF as service consumer . 19g36.5.2.3 AMF as service producer 20g36.6 Extensibili
23、ty Mechanisms 21g36.6.1 General 21g36.6.2 Feature negotiation . 21g36.6.3 Vendor-specific extensions . 22g36.7 Security Mechanisms . 22g36.7.1 General 22g36.7.2 Transport layer security protection of messages . 22g36.7.3 Authorization of NF service access 22g36.7.4 Application layer security across
24、PLMN 23g36.8 SBI Message Priority Mechanism 23g36.8.1 General 23g36.8.2 Message level priority . 23g36.8.3 Stream priority 23g36.8.4 Recommendations when defining SBI Message Priorities . 24g36.8.5 HTTP/2 client behaviour 24g36.8.6 HTTP/2 server behaviour 25g36.8.7 HTTP/2 proxy behaviour 25g36.8.8 D
25、SCP marking of messages 25g3Annex A (informative): Client-side Adaptive Throttling for Overload Control 26g3Annex B (informative): Change history . 27g3History 28g3ETSI ETSI TS 129 500 V15.0.0 (2018-07)53GPP TS 29.500 version 15.0.0 Release 15Foreword This Technical Specification has been produced b
26、y the 3rd Generation 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 the TSG with an identifying change o
27、f 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 incremented for all changes of substance,
28、 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 500 V15.0.0 (2018-07)63GPP TS 29.500 version 15.0.0 Release 151 Scope The present document specifies the technical realizatio
29、n of the 5GC Service Based Architecture, protocols supported over the Service Based Interfaces, and the functionalities supported in the Service Based Architecture. The service requirements for the 5G system are defined in 3GPP TS 22.261 2. The system architecture requirements are defined in 3GPP TS
30、 23.501 3 and the procedures and flows in 3GPP TS 23.502 4. The design principles and documentation guidelines for 5GC SBI APIs are specified in 3GPP TS 29.501 5. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present docum
31、ent. - 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 to a 3GPP document (i
32、ncluding 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 22.261: “Service requirements for the 5G system; Stage 1“. 3 3GPP TS 23.501: “Sys
33、tem Architecture for the 5G System; Stage 2“. 4 3GPP TS 23.502: “Procedures for the 5G System; Stage 2“. 5 3GPP TS 29.501: “5G System; Principles and Guidelines for Services Definition; Stage 3“. 6 IETF RFC 793: “Transmission Control Protocol“. 7 IETF RFC 7540: “Hypertext Transfer Protocol Version 2
34、 (HTTP/2)“. 8 3GPP TS 29.510: “5G System; Network Function Repository Services; Stage 3“. 9 OpenAPI: “OpenAPI 3.0.0 Specification“, https:/ 10 IETF RFC 8259: “The JavaScript Object Notation (JSON) Data Interchange Format“. 11 IETF RFC 7231: “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Cont
35、ent“. 12 IETF RFC 7230: “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing“. 13 3GPP TS 29.571: “5G System; Common Data Types for Service Based Interfaces Stage 3“. 14 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. 15 3GPP TS 23.003: “Numbering, addressing and i
36、dentification“. 16 IETF RFC 5681: “TCP Congestion Control“. 17 3GPP TS 33.501: “Security Architecture and Procedures for 5G System”. 18 IANA: “SMI Network Management Private Enterprise Codes“, http:/www.iana.org/assignments/enterprise-numbers. 19 IETF RFC 7944: “Diameter Routing Message Priority“. 2
37、0 IETF RFC 7234: “Hypertext Transfer Protocol (HTTP/1.1): Caching“. ETSI ETSI TS 129 500 V15.0.0 (2018-07)73GPP TS 29.500 version 15.0.0 Release 1521 IETF RFC 7235: “ Hypertext Transfer Protocol (HTTP/1.1): Authentication“. 22 IETF RFC 6749: “The OAuth 2.0 Authorization Framework“. 23 IETF RFC 6750:
38、 “The OAuth 2.0 Authorization Framework: Bearer Token Usage“. 24 IETF RFC 7232: “Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the follow
39、ing apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the presen
40、t document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. HTTP Hypertext Transfer Protocol TCP Transmission Control ProtocolSMP SBI Message Priority 4 Service Based Architecture Overview 4.1 NF Services 3GPP TS 23.501 3 defines the 5G System Architecture
41、as a Service Based Architecture, i.e. a system architecture in which the system functionality is achieved by a set of NFs providing services to other authorized NFs to access their services. Control Plane (CP) Network Functions in the 5G System architecture shall be based on the service based archit
42、ecture. A NF service is one type of capability exposed by a NF (NF Service Producer) to other authorized NF (NF Service Consumer) through a service based interface. A NF service may support one or more NF service operation(s). See clause 7 of 3GPP TS 23.501 3. Network Functions may offer different f
43、unctionalities and thus different NF services. Each of the NF services offered by a Network Function shall be self-contained, acted upon and managed independently from other NF services offered by the same Network Function (e.g. for scaling, healing). 4.2 Service Based Interfaces A service based int
44、erface represents how the set of services is provided or exposed by a given NF. This is the interface where the NF service operations are invoked. The following Control Plane interfaces within the 5G Core Network specified in 3GPP TS 23.501 3 are defined as service based interfaces: - Namf, Nsmf, Nu
45、dm, Nnrf, Nnssf, Nausf, Nnef, Nsmsf, Nudr, Npcf, N5g-eir, Nlmf. 4.3 NF Service Framework 4.3.1 General The Service Based Architecture shall support the NF Service Framework that enable the use of NF services as specified in subclause 7.1 of 3GPP TS 23.501 3. ETSI ETSI TS 129 500 V15.0.0 (2018-07)83G
46、PP TS 29.500 version 15.0.0 Release 15The NF Service Framework includes the following mechanisms: - NF service registration and de-registration: to make the NRF aware of the available NF instances and supported services (see subclause 7.1.5 of 3GPP TS 23.501 3); - NF service discovery: to enable a N
47、F Service Consumer to discover NF Service Producer instance(s) which provide the expected NF service(s) (see subclause 7.1.3 of 3GPP TS 23.501 3); - NF service authorization: to ensure the NF Service Consumer is authorized to access the NF service provided by the NF Service Producer (see subclause 7
48、1.4 of 3GPP TS 23.501 3). The corresponding stage 3 procedures are defined in 3GPP TS 29.510 8. 4.3.2 NF Service Advertisement URI When invoking a service operation of a NF Service Producer that use HTTP methods with a message body (i.e PUT, POST and PATCH), the NF Service Consumer may provide NF S
49、ervice Advertisement URL(s) in the service operation request, based on operator policy, if it expects that the NF Service Producer may subsequently consume NF service(s) which the NF Service Consumer can provide (as a NF Service Producer). When receiving NF Service Advertisement URI(s) in a service operation request, the NF Service Producer may store and use the Service Advertisement URL(s) to discover NF services produced by the
