ETSI TS 129 570 V19.2.0 (2026-03)

5G; 5G System; Service Communication Proxy Services; Stage 3 (3GPP TS 29.570 version 19.2.0 Release 19)

RTS/TSGC-0429570vj20

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System;
Service Communication Proxy Services;
Stage 3
(3GPP TS 29.570 version 19.2.0 Release 19)


3GPP TS 29.570 version 19.2.0 Release 19 1 ETSI TS 129 570 V19.2.0 (2026-03)

Reference
RTS/TSGC-0429570vj20
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
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 contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 2 ETSI TS 129 570 V19.2.0 (2026-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property 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 IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, 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 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 constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
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 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
3GPP TS 29.570 version 19.2.0 Release 19 3 ETSI TS 129 570 V19.2.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 7
2 References . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Overview . 8
4.1 Introduction . 8
5 Services offered by the SCP . 8
5.1 Introduction . 8
5.2 Nscp_EventExposure Service . 9
5.2.1 Service Description . 9
5.2.1.1 General . 9
5.2.1.2 Events supported by the service . 9
5.2.2 Service Operations . 10
5.2.2.1 Introduction . 10
5.2.2.2 Subscribe . 10
5.2.2.2.1 General . 10
5.2.2.2.2 Creation of a subscription . 10
5.2.2.2.3 Modification of a subscription . 11
5.2.2.3 Unsubscribe . 11
5.2.2.3.1 General . 11
5.2.2.4 Notify . 12
5.2.2.4.1 General . 12
6 API Definitions . 12
6.1 Nscp_EventExposure Service API . 12
6.1.1 Introduction. 12
6.1.2 Usage of HTTP . 13
6.1.2.1 General . 13
6.1.2.2 HTTP standard headers . 13
6.1.2.2.1 General . 13
6.1.2.2.2 Content type . 13
6.1.2.3 HTTP custom headers . 13
6.1.3 Resources . 13
6.1.3.1 Overview . 13
6.1.3.2 Resource: subscriptions (Collection). 14
6.1.3.2.1 Description . 14
6.1.3.2.2 Resource Definition . 14
6.1.3.2.3 Resource Standard Methods . 14
6.1.3.3 Resource: subscriptionId (Document) . 15
6.1.3.3.1 Description . 15
6.1.3.3.2 Resource Definition . 15
6.1.3.3.3 Resource Standard Methods . 16
6.1.4 Custom Operations without associated resources . 17
6.1.4.1 Overview . 17
6.1.5 Notifications . 17
6.1.5.1 General . 17
6.1.5.2 SCP Event Exposure Notification . 18
6.1.5.2.1 Description . 18
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 4 ETSI TS 129 570 V19.2.0 (2026-03)
6.1.5.2.2 Target URI . 18
6.1.5.2.3 Standard Methods . 18
6.1.6 Data Model . 19
6.1.6.1 General . 19
6.1.6.2 Structured data types . 20
6.1.6.2.1 Introduction . 20
6.1.6.2.2 Type: ScpEventExposureSubscription . 20
6.1.6.2.3 Type: ScpEventExposureNotification . 21
6.1.6.2.4 Type: ScpEventExposureSubsResp . 21
6.1.6.2.5 Type: ScpEventFilter . 21
6.1.6.2.6 Type: ScpEventReport . 22
6.1.6.2.7 Type: FailureCauseOccurrence . 22
6.1.6.2.8 Type: ScpSignallingInfo . 23
6.1.6.2.9 Type: ScpEventFilterConfig . 26
6.1.6.2.10 Type: ReselectionStat . 28
6.1.6.3 Simple data types and enumerations . 28
6.1.6.3.1 Introduction . 28
6.1.6.3.2 Simple data types . 28
6.1.6.3.3 Enumeration: FailureCause . 28
6.1.6.3.4 Enumeration: ScpEventType . 29
6.1.6.3.5 Enumeration: ReselectionReason . 29
6.1.6.3.6 Enumeration: ConnectionStatus . 29
6.1.7 Error Handling . 29
6.1.7.1 General . 29
6.1.7.2 Protocol Errors . 29
6.1.7.3 Application Errors . 29
6.1.8 Feature negotiation . 30
6.1.9 Security . 30
6.1.10 HTTP redirection . 30
Annex A (normative): OpenAPI specification . 31
A.1 General . 31
A.2 Nscp_EventExposure API . 31
Annex B (informative): Change history . 38
History . 39

ETSI
3GPP TS 29.570 version 19.2.0 Release 19 5 ETSI TS 129 570 V19.2.0 (2026-03)
Foreword
This Technical Specification has been produced by 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 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 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.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 6 ETSI TS 129 570 V19.2.0 (2026-03)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 7 ETSI TS 129 570 V19.2.0 (2026-03)
1 Scope
The present document specifies the stage 3 protocol and data model for the Nscp Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SCP.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2], TS 23.288 [14], and TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in TS 29.500 [4] and TS 29.501 [5].
2 References
The following documents contain provisions which, 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, 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.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[7] 3GPP TR 21.900: "Technical Specification Group working methods".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11] IETF RFC 9113: "HTTP/2".
[12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13] IETF RFC 9457: "Problem Details for HTTP APIs".
[14] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data
analytics services".
[15] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch".
[16] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[17] 3GPP TS 29.122: "T8 reference point for Northbound APIs".
[18] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 8 ETSI TS 129 570 V19.2.0 (2026-03)
3 Definitions, symbols 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 TR 21.905 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and 3GPP TS 23.501 [2] and
the following apply. An abbreviation defined in the present document or 3GPP TS 23.501 [2] takes precedence over the
definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. An abbreviation defined in the present document
takes precedence over the definition of the same abbreviation, if any, in 3GPP TS 23.501 [2].
SCP Service Communication Proxy

4 Overview
4.1 Introduction
Within the 5GC, the SCP offers services to the NWDAF and DCCF via the Nscp service based interface (see
3GPP TS 23.501 [2], 3GPP TS 23.502 [3], 3GPP TS 23.288 [14]).
Figure 4.1-1 provides the reference model (in service based interface representation and in reference point
representation), with focus on the SCP and the scope of the present specification.
NWDAF
Nscp SCP
DCCF
Figure 4.1-1: Reference model – SCP

5 Services offered by the SCP
5.1 Introduction
The table 5.1-1 shows the SCP services and SCP service operations:

ETSI
3GPP TS 29.570 version 19.2.0 Release 19 9 ETSI TS 129 570 V19.2.0 (2026-03)
Table 5.1-1 List of SCP Services
Service Name Service Operations Operation Example Consumer(s)
Semantics
Nscp_EventExposure Subscribe Subscribe/Notify NWDAF, DCCF
Unsubscribe Subscribe/Notify NWDAF, DCCF
Notify Subscribe/Notify NWDAF, DCCF

Table 5.1-2 summarizes the corresponding APIs defined for this specification.
Table 5.1-2: API Descriptions
Service Name Clause Description OpenAPI Specification File apiName Annex
SCP Event
Nscp_EventExposure 6.1 Exposure TS29570_Nscp_EventExposure.yaml nscp-ee A.2
Service
5.2 Nscp_EventExposure Service
5.2.1 Service Description
5.2.1.1 General
The Nscp_EventExposure service enables the SCP to expose real-time event data related to network signaling and
performance to other NFs (e.g. NWDAF and DCCF) for analytics and monitoring.
5.2.1.2 Events supported by the service
The following event type(s) are supported by the Nscp_EventExposure Service:
Event: SERVICE_SIGNALLING_CHARACTERISTICS:
An NF subscribes to this event type to receive the SCP reports of the observed rate (i.e. number per time
interval) of several types of signalling messages received and sent by NF instance(s) or NF service instance(s),
the percentage of failed transactions, NF or NF service overload control information, SCP reselection reasons,
NF service connection status, and various delay and performance metrics.
This event implements the "Service Signalling Characteristics Information" as described in clause 5.2.29 of
3GPP TS 23.502 [3] and Table 6.22.2-8 of 3GPP TS 23.288 [14].
Target: NF type, NF service instance, NF instance, NF set or NF service name.
Report Type: Periodic Report, One-Time Report.
Input in the subscription: target ID, optional filters, e.g. reporting threshold (in terms of absolute transaction or
deviation from average, or in terms of a minimum percentage failed transactions), time window.
Notification: Event type, time stamp, and optionally: one or more of the following types of information:
- Per NF instance, See Table 6.22.2-8 of 3GPP TS 23.288 [14].
- Number of successful responses related to SCP egress interface associated to their initial requests during a
time interval.
- Number of failed responses related to SCP egress interface associated to their initial requests during a
time interval.
- Distribution of reasons for failed responses related to SCP egress interface associated to their initial
requests, e.g. the number of failed responses due to time-outs, the number of failed responses due to
server errors, the number of failed responses due to consumer errors.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 10 ETSI TS 129 570 V19.2.0 (2026-03)
- Connection status: The connection status between SCP and NF service instance.
- SCP reselection statistics: Reselection reasons with their occurrence counts.
- Overload control information indicating the current overload of the NF and NF Service(s).
- Average response time: Average time taken to get response from NF service instance after SCP sent the
request.
5.2.2 Service Operations
5.2.2.1 Introduction
The Nscp_EventExposure service defines three service operations:
- Notify: The SCP sends notifications to subscribed consumers, providing event data and related information.
- Subscribe: A network function (NF) subscribes to receive notifications for specific events, with the option to
define filtering or subscription parameters.
- Unsubscribe: An NF unsubscribes from a previously established event notification subscription.
These operations allow consumers to manage the receipt of event data related to network signaling and performance.
5.2.2.2 Subscribe
5.2.2.2.1 General
See Table 5.1-1 for an overview of the service operations supported by the Nscp_EventExposure service.
5.2.2.2.2 Creation of a subscription
This procedure allows NF Service Consumer to subscribe by using HTTP POST method with the URI of subscriptions
collection.
NF Service
SCP
Consumer
1. POST …/subscriptions(ScpEventExposureSubscription)
2a. 201 Created
2b. 4xx/5xx (ProblemDetails) or 3xx

Figure 5.2.2.2.2-1: Subscription of NF service consumer to SCP Event Exposure
1. The NF Service Consumer shall send an HTTP POST request to the resource URI associated with the
subscription collection.
2a. On success, "201 Created" shall be returned. The response body shall include a HTTP Location header
including the subscription ID together with the status code 201 indicating the requested resource is created in
the response message.
2b. On failure or redirection, one of the HTTP status codes listed in Table 6.1.3.2.3.1-3 shall be returned. For a
4xx/5xx response, the message body should contain a ProblemDetails structure indicating appropriate additional
error information.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 11 ETSI TS 129 570 V19.2.0 (2026-03)
5.2.2.2.3 Modification of a subscription
This procedure allows NF Service Consumer to modify an existing subscription by using HTTP PATCH method with
the URI of the individual subscription resource.
NF Service
SCP
Consumer
1. PATCH …/subscriptions/{subscriptionId}(array(PatchItem))
2a. 204 No Content/200 OK
2b. 4xx/5xx (ProblemDetails) or 3xx

Figure 5.2.2.2.3-1: Modification of subscription for SCP Event Exposure
1. The NF Service Consumer shall send a PATCH request to modify a subscription resource in the SCP.
2a. On success,
"204 No Content" shall be returned, if there is no payload in the response. If the request included an expiry time
and "204 No Content" is returned, it indicates that the SCP has accepted the requested expiry time.
"200 OK" shall be returned and include a response body of type ScpEventExposureSubsResp if a payload needs
to be returned. When returning a "200 OK" response, if the request included an expiry time, then the response
based on operator policies and taking into account the expiry time included in the request, shall contain an expiry
time (i.e. a future timestamp), as determined by the SCP, after which the subscription becomes invalid. If an
expiry time was included in the request, then the expiry time returned in the response should be less than or
equal to that value.
NOTE: In this release of the specification, the payload contains only one item, i.e. expiry time. In this release, if
the expiry time included is in the request and the expiry time determined by SCP is equal to the value of
the expiry time in the request, a payload is not needed to be returned and "204 No Content" is returned.
2b. On failure or redirection, one of the HTTP status codes listed in Table 6.1.3.3.3.1-3 shall be returned. For a
4xx/5xx response, the message body contains a ProblemDetails structure indicating appropriate additional error
information.
5.2.2.3 Unsubscribe
5.2.2.3.1 General
This procedure allows NF Service Consumer to delete an existing subscription by using the HTTP DELETE method
with the URI of the individual subscription resource to be deleted.
NF Service
SCP
Consumer
1. DELETE …/subscriptions/{subscriptionId}
2a. 204 No Content
2b. 4xx/5xx (ProblemDetails) or 3xx

Figure 5.2.2.3.1-1: Unsubscribe Service Operation for SCP Event Exposure
1. The NF consumer shall send a DELETE request to the SCP to delete the subscription.
2a. On success, "204 No content" shall be returned by the NF Service Consumer.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 12 ETSI TS 129 570 V19.2.0 (2026-03)
2b. On failure or redirection, one of the appropriate HTTP status codes listed in Table 6.1.3.3.3.2-3 shall be returned.
For a 4xx/5xx response, the message body should contain a ProblemDetails structure indicating appropriate
additional error information.
5.2.2.4 Notify
5.2.2.4.1 General
The Notify service operation is used to allow the NF service consumer to get notifications from SCP.
NF Service
SCP
Consumer
1. POST {NotificationUrl}(ScpEventExposureNotification)
2a. 204 No Content
2b. 4xx/5xx (ProblemDetails) or 3xx

Figure 5.2.2.4.1-1: Notification for SCP Event Exposure
1. The SCP shall send a POST request to the NF Service Consumer with the information on Notification target
address. The request body shall include Event specific parameters and notification correlation ID, if received.
2a. On success, "204 No content" shall be returned by the NF Service Consumer.
2b. On failure or redirection, one of the appropriate HTTP status codes listed in Table 6.1.5.2.3.1-2 shall be returned.
For a 4xx/5xx response, the message body should contain a ProblemDetails structure indicating appropriate additional
error information.
6 API Definitions
6.1 Nscp_EventExposure Service API
6.1.1 Introduction
The Nscp_EventExposure shall use the Nscp_EventExposure API.
The API URI of the Nscp_EventExposure API shall be:
{apiRoot}//
The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the
Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}///
with the following components:
- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
- The shall be "nscp-ee".
- The shall be "v1".
- The shall be set as described in clause 6.1.3.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 13 ETSI TS 129 570 V19.2.0 (2026-03)
6.1.2 Usage of HTTP
6.1.2.1 General
HTTP/2, IETF RFC 9113 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
The OpenAPI [6] specification of HTTP messages and content bodies for the Nscp_ee API is contained in Annex A.
6.1.2.2 HTTP standard headers
6.1.2.2.1 General
See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
6.1.2.2.2 Content type
JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as
specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type
"application/json".
"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and
shall be signalled by the content type "application/problem+json", as defined in IETF RFC 9457 [13].
6.1.2.3 HTTP custom headers
The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and
the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported.
6.1.3 Resources
6.1.3.1 Overview
This clause describes the structure for the Resource URIs and the resources and methods used for the service.
Figure 6.1.3.1-1 depicts the resource URIs structure for the Nscp_EventExposure API.
{apiRoot}/nscp-ee/

Figure 6.1.3.1-1: Resource URI structure of the Nscp_EventExposure API
Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 14 ETSI TS 129 570 V19.2.0 (2026-03)
Table 6.1.3.1-1: Resources and methods overview
HTTP
method
Resource URI (relative path
Resource purpose/name or Description (service operation)
after API URI)
custom
operation
subscriptions /subscriptions POST Mapped to the service operation
(Collection) subscribe, when to create a
subscription
subscriptionId PATCH Modify the subscription identified by
(Document) {subscriptionId}
/subscriptions/{subscriptionId}
DELETE Delete the subscription identified by
{subscriptionId}
6.1.3.2 Resource: subscriptions (Collection)
6.1.3.2.1 Description
This resource represents a collection of subscriptions created by NF service consumers of Nscp_EventExposure service.
This resource is modelled as the Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [5]).
6.1.3.2.2 Resource Definition
Resource URI: {apiRoot}/nscp-ee//subscriptionsThis resource shall support the resource URI variables
defined in table 6.1.3.2.2-1.
Table 6.1.3.2.2-1: Resource URI variables for this resource
Name Data type Definition
apiRoot string See clause 6.1.1

6.1.3.2.3 Resource Standard Methods
6.1.3.2.3.1 POST
This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1.
Table 6.1.3.2.3.1-1: URI query parameters supported by the POST method on this resource
Name Data type P Cardinality Description Applicability
n/a
This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and
response codes specified in table 6.1.3.2.3.1-3.
Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type P Cardinality Description
ScpEventExposur M 1 SCP Event Exposure Subscription to be created
eSubscription
ETSI
3GPP TS 29.570 version 19.2.0 Release 19 15 ETSI TS 129 570 V19.2.0 (2026-03)
Table 6.1.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type P Cardinality Response Description
codes
ScpEventExposur M 1 201 Represents successful creation of an SCP Subscription
eSubsResp Created
RedirectRespons O 0.1 307 Temporary redirection.
e Temporary
Redirect
RedirectRespons O 0.1 308 Permanent redirection.
e Permanent
Redirect
NOTE: The manadatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of
3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see
clause 5.2.7 of 3GPP TS 29.500 [4]).

Table 6.1.3.2.3.1-4: Headers supported by the 201 response code on this resource
Name Data type P Cardinality Description
Location string M 1 Contains the URI of the newly created
resource, according to the structure:
{apiRoot}/nscp-ee//subscrip
tions/{subscriptionId}
Table 6.1.3.2.3.1-5: Headers supported by the 307 Response Code on this resource
Name Data type P Cardinality Description
Location string M 1 An alternative URI of the resource located on an alternative
service instance within the same SCP.

Table 6.3.3.2.3.1-6: Headers supported by the 308 Response Code on this resource
Name Data type P Cardinality Description
Location string M 1 An alternative URI of the resource located on an alternative
service instance within the same SCP.

6.1.3.3 Resource: subscriptionId (Document)
6.1.3.3.1 Description
This resource represents an individual of subscription created by NF service consumers of Nscp_EventExposure
service.
This resource is modelled as the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]).
6.1.3.3.2 Resource Definition
Resource URI: {apiRoot}/nscp-ee//subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 6.1.3.3.2-1.
Table 6.1.3.3.2-1: Resource URI variables for this resource
Name Data type Definition
apiRoot string See clause 6.1.1
subscriptionId string Represents the identity of a specific subscription

ETSI
3GPP TS 29.570 version 19.2.0 Release 19 16 ETSI TS 129 570 V19.2.0 (2026-03)
6.1.3.3.3 Resource Standard Methods
6.1.3.3.3.1 PATCH
This method shall support the URI query parameters specified in table 6.1.3.3.3.1-1.
Table 6.1.3.3.3.1-1: URI query parameters supported by the PATCH method on this resource
Name Data type P Cardinality Description
n/a
This method shall support the request data structures specified in table 6.1.3.3.3.1-2 and the response data structure and
response codes specified in table 6.1.3.3.3.1-3.
Table 6.1.3.3.3.1-2: Data structures supported by the PATCH Request Body on this resource
Data type P Cardinality Description
array(PatchItem) M 1.N It contains the list of changes to be made to the subscription,
according to the JSON PATCH format specified in
IETF RFC 6902 [15].
Table 6.1.3.3.3.1-3: Data structures supported by the PATCH Response Body on this resource
Data type P Cardinality Response Description
codes
n/a 204 No Represents a successful update on SCP Event
Content Exposure Subscription
ScpEventExposureSubs M 1 200 OK Represents successful modification of an SCP
Resp Subscription.
RedirectResponse O 0.1 307 Temporary redirection.
Temporary
Redirect
RedirectResponse O 0.1 308 Permanent redirection.
Permanent
Redirect
NOTE: The mandatory HTTP error status code for the PATCH method listed in Table 5.2.7.1-1 of
3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see
clause 5.2.7 of 3GPP TS 29.500 [4]).

Table 6.1.3.3.3.1-4: Headers supported by the 307 Response Code on this resource
Name Data type P Cardinality Description
Location string M 1 An alternative URI of the resource l
...