1、 ETSI TS 129 522 V15.0.0 (2018-07) 5G; 5G System; Network Exposure Function Northbound APIs; Stage 3 (3GPP TS 29.522 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 129 522 V15.0.0 (2018-07)13GPP TS 29.522 version 15.0.0 Release 15Reference DTS/TSGC-0329522vf00 Keywords 5G ETSI 650 R
2、oute 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: http:/www.et
3、si.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 differenc
4、e 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 or change
5、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/CommiteeSupportStaff
6、.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 authorization of
7、 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 benefit of
8、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 522 V15.0.0 (2018-07)23GPP TS 29.522 version 15.0.0 Release 15Intellectual Property Rights Es
9、sential 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 (IP
10、Rs); 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 been
11、 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 tradenames
12、 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 constitute
13、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 3GPP ident
14、ities, 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 documen
15、t “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 except whe
16、n used in direct citation. ETSI ETSI TS 129 522 V15.0.0 (2018-07)33GPP TS 29.522 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 Abbreviatio
17、ns . 6g34 NEF Northbound Interface . 7g34.1 Overview 7g34.2 Reference model . 7g34.3 Functional elements 8g34.3.1 NEF . 8g34.3.2 AF . 8g34.4 Procedures over NEF Northbound Interface 9g34.4.1 Introduction. 9g34.4.2 Procedures for Monitoring 9g34.4.3 Procedures for Device Triggering . 9g34.4.4 Procedu
18、res for resource management of Background Data Transfer 9g34.4.5 Procedures for CP Parameters Provisioning . 9g34.4.6 Procedures for PFD Management . 10g34.4.7 Procedures for Traffic Influence . 10g34.4.7.1 General 10g34.4.7.2 AF request for an individual UE . 10g34.4.7.3 AF request for multiple UEs
19、 . 11g35 NEF Northbound APIs . 11g35.1 Introduction 11g35.2 Information applicable to several APIs 11g35.3 Reused APIs . 11g35.4 TrafficInfluence API 12g35.4.1 Resources 12g35.4.1.1 Overview. 12g35.4.1.2 Resource: Traffic Influence Subscription 12g35.4.1.2.1 Introduction . 12g35.4.1.2.2 Resource Def
20、inition . 12g35.4.1.2.3 Resource Methods . 13g35.4.1.2.3.1 General . 13g35.4.1.2.3.2 GET 13g35.4.1.2.3.3 POST 13g35.4.1.3 Resource: Individual Traffic Influence Subscription 14g35.4.1.3.1 Introduction . 14g35.4.1.3.2 Resource Definition . 14g35.4.1.3.3 Resource Methods . 14g35.4.1.3.3.1 General . 14
21、g35.4.1.3.3.2 GET 14g35.4.1.3.3.3 PUT 14g35.4.1.3.3.4 PATCH 15g35.4.1.3.3.5 DELETE 15g35.4.2 Notifications . 16g35.4.2.1 Introduction . 16g35.4.2.2 Event Notification . 16g35.4.2.3 Operation Definition . 16g35.4.2.3.1 Notification via HTTP POST 16g3ETSI ETSI TS 129 522 V15.0.0 (2018-07)43GPP TS 29.5
22、22 version 15.0.0 Release 155.4.2.3.2 Notification via Websocket . 16g35.4.3 Data Model . 16g35.4.3.1 General 16g35.4.3.2 Reused data types 16g35.4.3.3 Structured data types . 17g35.4.3.3.1 Introduction . 17g35.4.3.3.2 Type: TrafficInfluSub 17g35.4.3.3.3 Type: TrafficInfluSubPatch . 20g35.4.3.3.4 Ty
23、pe: TrafficRoute 21g35.4.3.3.5 Type: TrafficRouteInfo 21g35.4.3.3.6 Type: EventNotification 21g35.4.3.4 Simple data types and enumerations . 22g35.4.3.4.1 Introduction . 22g35.4.3.4.2 Simple data types . 22g35.4.3.4.3 Enumeration: SubscribedEvent . 22g35.4.3.4.4 Enumeration: NotifyType 22g35.4.4 Use
24、d Features 22g36 Security. 22g37 Using Common API Framework 23g3Annex A (normative): OpenAPI representation for NEF Northbound APIs . 24g3A.1 General . 24g3A.2 TrafficInfluence API 24g3Annex B (informative): Change history . 30g3History 31g3ETSI ETSI TS 129 522 V15.0.0 (2018-07)53GPP TS 29.522 versi
25、on 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 formal TSG approval. Should the TSG modify the contents of the pres
26、ent 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 cha
27、nge 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 522 V15.0.0 (2018-07)63GPP TS 29.522 version 15.0
28、.0 Release 151 Scope The present specification describes the protocol for the NEF Northbound interface between the NEF and the AF. The NEF Northbound interface and the related stage 2 functional requirements are defined in 3GPP TS 23.502 2. 2 References The following documents contain provisions whi
29、ch, through reference 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
30、, the latest version 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.
31、502: “Procedures for the 5G system“. 3 3GPP TS 23.501: “System Architecture for the 5G“. 4 3GPP TS 29.122: “T8 reference point for northbound Application Programming Interfaces (APIs)“. 5 Open API Initiative, “OpenAPI 3.0.0 Specification“, https:/ 6 3GPP TS 33.501: “Security architecture and procedu
32、res for 5G System“. 7 3GPP TS 29.514: “5G System; Policy Authorization Service; Stage 3“. 8 3GPP TS 29.571: “5G System; Common Data Types for Service Based Interfaces; Stage 3“. 9 3GPP TS 29.521: “5G System; Binding Support Management Service; Stage 3“. 10 3GPP TS 29.505: “5G System; Usage of the Un
33、ified Data Repository services for Subscription Data; Stage 3“. 11 3GPP TS 23.222: “Common API Framework for 3GPP Northbound APIs; Stage 2“. 12 3GPP TS 29.222: “Common API Framework for 3GPP Northbound APIs; Stage 3“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present do
34、cument, 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 TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP
35、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 3GPP TR 21.905 1. AF Application Function BDT Background Data Transfer ETSI ETSI TS 129 522 V15.0.0 (2018-07)73GPP TS 29.522 version 15.0.0 R
36、elease 15CAPIF Common API Framework CP Communication PatternDN Data Network DNAI DN Access Identifier DNN Data Network Name GPSI Generic Public Subscription Identifier NEF Network Exposure Function PCF Policy Control Function PCRF Policy and Charging Rule Function PFD Packet Flow Description PFDF Pa
37、cket Flow Description Function REST Representational State Transfer SCEF Service Capability Exposure Function S-NSSAI Single Network Slice Selection Assistance Information UDR Unified Data Repository UP User Plane 4 NEF Northbound Interface 4.1 Overview The NEF Northbound interface is between the NE
38、F and the AF. It specifies RESTful APIs that allow the AF to access the services and capabilities provided by 3GPP network entities and securely exposed by the NEF. This document also specifies the procedures triggered at the NEF by API requests from the AF and by event notifications received from 3
39、GPP network entities. The stage 2 level requirements and signalling flows for the NEF Northbound interface are defined in 3GPP TS 23.502 2. The NEF Northbound interface supports the following procedures: - Procedures for Monitoring - Procedures for Device Triggering - Procedures for resource managem
40、ent of Background Data Transfer - Procedures for CP Parameters Provisioning - Procedures for PFD Management - Procedures for Traffic Influence Which correspond to the following services respectively, supported by the NEF as defined in 3GPP TS 23.502 2: - Nnef_EventExposure service - Nnef_Trigger ser
41、vice - Nnef_BDTPNegotiation service - Nnef_ParameterProvision service - Nnef_PFDmanagement service - Nnef_TrafficInfluence service 4.2 Reference model The NEF Northbound interface resides between the NEF and the AF as depicted in figure 4.2.1. The overall NEF architecture is depicted in 3GPP TS 23.5
42、02 2. An AF can get services from multiple NEFs, and an NEF can provide service to multiple AFs. ETSI ETSI TS 129 522 V15.0.0 (2018-07)83GPP TS 29.522 version 15.0.0 Release 15NOTE: The AF can be provided by the third party. g3g69g28g38g3g4g38g3g69g374g286g296g3Figure 4.2-1: Reference Architecture f
43、or the Nnef Service; SBI representation g3g69g1007g1007g3g69g28g38g3 g4g38g3Figure 4.2-2: Reference Architecture for the Nnef Service; reference point representation 4.3 Functional elements 4.3.1 NEF The Network Exposure Function (NEF) is a functional element that supports the following functionalit
44、ies: - The NEF shall securely expose network capabilities and events provided by 3GPP NFs to AF. - The NEF shall provide a means for the AF to securely provide information to 3GPP network and may authenticate, authorize and assist in throttling the AF. - The NEF shall be able to translate the inform
45、ation received from the AF to the one sent to internal 3GPP NFs, and vice versa. - The NEF shall support to expose information (collected from other 3GPP NFs) to the AF. - The NEF may support a PFD Function which allows the AF to provision PFD(s) and may store and retrieve PFD(s) in the UDR. The NEF
46、 further provisions PFD(s) to the SMF. A specific NEF instance may support one or more of the functionalities described above and consequently an individual NEF may support a subset of the APIs specified for capability exposure. NOTE: The NEF can access the UDR located in the same PLMN as the NEF. 4
47、.3.2 AF The Application Function (AF) may interact with the 3GPP Core Network via the NEF in order to access network capabilities. ETSI ETSI TS 129 522 V15.0.0 (2018-07)93GPP TS 29.522 version 15.0.0 Release 154.4 Procedures over NEF Northbound Interface 4.4.1 Introduction All procedures that operat
48、e across the NEF Northbound interface, as specified in 3GPP TS 23.502 2, are specified in the following subclauses. 4.4.2 Procedures for Monitoring The procedures for monitoring as described in subclause 4.4.3 of 3GPP TS 29.122 4 shall be applicable in 5GS with the following differences: - descripti
49、on of the SCS/AS applies to the AF; - description of the SCEF applies to the NEF; - description of the HSS applies to the UDM, and the NEF shall interact with the UDM by using Nudm_EventExposure service; - description of the MME/SGSN applies to the AMF, and the NEF shall interact with the AMF by using Namf_EventExposure service; - description about the PCRF is not applicable. 4.4.3 Procedures for Device Triggering The procedures for device triggering as described in
