1、 ETSI TS 129 521 V15.0.0 (2018-07) 5G; 5G System; Binding Support Management Service; Stage 3 (3GPP TS 29.521 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 129 521 V15.0.0 (2018-07)13GPP TS 29.521 version 15.0.0 Release 15Reference DTS/TSGC-0329521vf00 Keywords 5G ETSI 650 Route de
2、s 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: http:/www.etsi.org/
3、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 difference in co
4、ntents 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 or change of stat
5、us. 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/CommiteeSupportStaff.aspx C
6、opyright 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 authorization of ETSI.
7、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 benefit of its Mem
8、bers 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 521 V15.0.0 (2018-07)23GPP TS 29.521 version 15.0.0 Release 15Intellectual Property Rights Essential
9、 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 Rights (IPRs); Es
10、sential, 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 been carrie
11、d 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 tradenames which
12、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 constitute an endo
13、rsement 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 3GPP identities,
14、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 present document “shal
15、l“, “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 except when used
16、in direct citation. ETSI ETSI TS 129 521 V15.0.0 (2018-07)33GPP TS 29.521 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g
17、34 Binding Support Management Service . 7g34.1 Service Description 7g34.1.1 Overview 7g34.1.2 Service Architecture . 7g34.1.3 Network Functions 8g34.1.3.1 Binding Support Function (BSF) 8g34.1.3.2 NF Service Consumers 8g34.2 Service Operations . 8g34.2.1 Introduction. 8g34.2.2 Nbsf_Management_Regist
18、er Service Operation . 9g34.2.2.1 General 9g34.2.2.2 Register a new PCF Session binding information . 9g34.2.3 Nbsf_Management_Deregister Service Operation . 9g34.2.3.1 General 9g34.2.3.2 Deregister an individual PCF Session binding information 10g34.2.4 Nbsf_Management_Discovery Service Operation 1
19、0g34.2.4.1 General 10g34.2.4.2 Retrieve the PCF Session binding information for a given tuple 10g35 Nbsf_Management Service API . 11g35.1 Introduction 11g35.2 Usage of HTTP . 11g35.2.1 General 11g35.2.2 HTTP standard headers . 11g35.2.2.1 General 11g35.2.2.2 Content type 11g35.2.3 HTTP custom header
20、s . 11g35.2.3.1 General 11g35.3 Resources . 12g35.3.1 Resource Structure 12g35.3.2 Resource: PCF Session Bindings 12g35.3.2.1 Description 12g35.3.2.2 Resource definition . 12g35.3.2.3 Resource Standard Methods 13g35.3.2.3.1 POST . 13g35.3.2.3.2 GET . 13g35.3.3 Resource: Individual PCF Session Bindin
21、g 14g35.4 Custom Operations without associated resources. 15g35.5 Notifications . 15g35.6 Data Model . 15g35.6.1 General 15g35.6.2 Structured data types . 15g35.6.2.1 Introduction . 15g35.6.2.2 Type PcfBinding . 16g35.6.3 Simple data types and enumerations . 16g35.6.3.1 Introduction . 16g3ETSI ETSI
22、TS 129 521 V15.0.0 (2018-07)43GPP TS 29.521 version 15.0.0 Release 155.6.3.2 Simple data types 16g35.7 Error handling 16g35.8 Feature negotiation . 17g3Annex A (normative): OpenAPI specification . 18g3A.1 General . 18g3A.2 Nbsf_Management API 18g3Annex B (informative): Change history . 19g3History 2
23、0g3ETSI ETSI TS 129 521 V15.0.0 (2018-07)53GPP TS 29.521 version 15.0.0 Release 15Foreword 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 forma
24、l TSG approval. Should the TSG modify the contents of the present 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 ap
25、proval; 3 or greater indicates TSG approved document under change 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
26、 ETSI TS 129 521 V15.0.0 (2018-07)63GPP TS 29.521 version 15.0.0 Release 151 Scope The present specification provides the stage 3 definition of the Binding Support Management Service of the 5G System. The 5G System Architecture is defined in 3GPP TS 23.501 2. The stage 2 definition and related proce
27、dures for Binding Support Management Service is specified in 3GPP TS 23.502 3 and 3GPP TS 23.503 4. The 5G System stage 3 call flows are provided in 3GPP TS 29.513 5. The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified i
28、n 3GPP TS 29.500 6 and 3GPP TS 29.501 7. The Binding Support Management Service is provided by the Binding Support Function (BSF). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either spe
29、cific (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 (including a GSM document), a non-
30、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.501: “System Architecture for the 5G System; Stage 2“. 3 3GPP TS 23.502: “Procedures for the 5G System; Stage
31、2“. 4 3GPP TS 23.503: “Policy and Charging Control Framework for the 5G System; Stage 2“. 5 3GPP TS 29.513: “5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3“. 6 3GPP TS 29.500: “5G System; Technical Realization of Service Based Architecture; Stage 3“. 7 3GP
32、P TS 29.501: “5G System; Principles and Guidelines for Services Definition; Stage 3“. 8 IETF RFC 7540: “Hypertext Transfer Protocol Version 2 (HTTP/2)“. 9 IETF RFC 7159: “The JavaScript Object Notation (JSON) Data Interchange Format“. 10 3GPP TS 29.571: “5G System; Common Data Types for Service Base
33、d Interfaces Stage 3“. 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 following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
34、TR 21.905 1. ETSI ETSI TS 129 521 V15.0.0 (2018-07)73GPP TS 29.521 version 15.0.0 Release 153.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 present document takes precedence over the defin
35、ition of the same abbreviation, if any, in 3GPP TR 21.905 1. API Application Programming Interface BSF Binding Support Function HTTP Hypertext Transfer Protocol NF Network Function 4 Binding Support Management Service 4.1 Service Description 4.1.1 Overview The Binding Support Management Service as d
36、efined in 3GPP TS 23.502 3 and 3GPP TS 23.503 4, is provided by the Binding Support Function (BSF). The Nbsf service is used for the BSF to provide a PDU session binding functionality, which ensures that an AF request for a certain PDU Session reaches the relevant PCF holding the PDU Session informa
37、tion. This service: - Allows NF consumers to register, update and remove the binding information; and - allows NF consumers to retrieve the binding information. 4.1.2 Service Architecture The 5G System Architecture is defined in 3GPP TS 23.501 2. The Policy and Charging related 5G architecture is al
38、so described in 3GPP TS 23.503 4 and 3GPP TS 29.513 5. The Binding Support Management Service (Nbsf_Management) is exhibited by the Binding Support Function (BSF). Known consumers of the Nbsf_management service are: - Policy Control Function (PCF) - Network Exposure Function (NEF) - Application Func
39、tion (AF) As described in 3GPP TS 23.503 4, the BSF is a function that can be deployed standalone or can be the functionality provided by other network functions, such as PCF, UDR, NRF, SMF. NOTE: The PCF accesses the Nbsf_management service at the BSF via an internal interface when it is collocated
40、 with BSF. ETSI ETSI TS 129 521 V15.0.0 (2018-07)83GPP TS 29.521 version 15.0.0 Release 15Figure 4.1.2-1: Reference Architecture for the Nbsf_management service; SBI representation 4.1.3 Network Functions 4.1.3.1 Binding Support Function (BSF) The BSF provides: - stores the binding information for a
41、 certain PDU Session; and - discovers the selected PCF according to the binding information. The BSF allows PCFs to register, update and remove the binding information from it, and allows NF consumers to discover the selected PCF. The BSF can be deployed standalone or can be collocated with other ne
42、twork functions, such as PCF, UDR, NRF andSMF. 4.1.3.2 NF Service Consumers The Policy Control Function (PCF): - registers and deregisters the binding information in BSF for a UE when an IP address is allocated , updated or released for a PDU Session. The Network Exposure Function (NEF): - provides
43、a means for the Application Functions to securely interact with the Policy framework for policy control to 3GPP network. During the procedure, it needs to discover the selected PCF by using the Nbsf management service discovery service operation. The Application Function (AF): - discover the selecte
44、d PCF by using the Nbsf management service discovery service operation when it is allowed to interact directly with the policy framework for policy control. 4.2 Service Operations 4.2.1 Introduction Table 4.2.1-1: Operations of the Nbsf_management Service Service operation name Description Initiated
45、 by Nbsf_Management_Register This service operation is used to register the binding information for a UE when an IP address is allocated for a PDU Session. NF consumer (PCF) Nbsf_Management_Deregister This service operation is used to deregister the binding information for a UE when the PDU Session
46、is released. NF consumer (PCF) Nbsf_Management_Discovery This service operation is used by an NEF or AF to discover a selected PCF . NF consumer (NEF, AF) BSFNbsfPCF NEF AFuni004Euni0062uni0073uni0066uni005Funi006Duni0061uni006Euni0061uni0067uni0065uni006Duni0065uni006Euni0074uni0020uni0073uni0065un
47、i0072uni0076uni0069uni0063uni0065ETSI ETSI TS 129 521 V15.0.0 (2018-07)93GPP TS 29.521 version 15.0.0 Release 154.2.2 Nbsf_Management_Register Service Operation 4.2.2.1 General This service operation allows the service consumer to register the session binding information for a UE in the BSF by provi
48、ding the user identity, the DNN, the UE IP address(es) and the selected PCF address for a certain PDU Session to the BSF, and BSF stores the information. 4.2.2.2 Register a new PCF Session binding information Figure 4.2.2.2-1: NF service consumer register a new PCF Session binding information The NF
49、 service consumer shall invoke the Nbsf_Management_Register service operation to register the session binding information for a UE in the BSF. The NF service consumer shall send an HTTP POST request with “apiRoot/nbsf-management/v1/pcfBindings“ as Resource URI representing the “PCF Session Bindings“, as shown in figure 4.2.2.2-1, step 1, to create a binding information for an “Individual PCF Session Binding“ arording to the information (e.g. UE address(es), SUPI; GPSI, DNN, S-NNSAI,.NSI) in message body. The PcfBinding data
