ETSI TS 129 675 V17.5.0 (2022-05)

LTE; 5G; User Equipment (UE) radio capability provisioning service; Stage 3 (3GPP TS 29.675 version 17.5.0 Release 17)

RTS/TSGC-0329675vh50

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 3 - Interworking with external networks (formely CN3)
• Current Stage: 12 - Completion
• Completion Date: 12-May-2022

Standards Content (Sample)

ETSI TS 129 675 V17.5.0 (2022-05)






TECHNICAL SPECIFICATION
LTE;
5G;
User Equipment (UE) radio capability provisioning service;
Stage 3
(3GPP TS 29.675 version 17.5.0 Release 17)



---------------------- Page: 1 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 1 ETSI TS 129 675 V17.5.0 (2022-05)

Reference
RTS/TSGC-0329675vh50
Keywords
5G,LTE
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:
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 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 at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision 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/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
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
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
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 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 2 ETSI TS 129 675 V17.5.0 (2022-05)
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 Web server (https://ipr.etsi.org/).
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™ and LTE™ 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 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 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

---------------------- Page: 3 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 3 ETSI TS 129 675 V17.5.0 (2022-05)
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 Symbols . 8
3.3 Abbreviations . 8
4 UE Radio Capability Provisioning Service . 8
4.1 Service Description . 8
4.1.1 Overview . 8
4.1.2 Service Architecture . 8
4.1.3 Network Functions . 9
4.1.3.1 UCMF . 9
4.1.3.2 NF Service Consumers . 9
4.2 Service Operations . 9
4.2.1 Introduction. 9
4.2.2 Nucmf_Provisioning_Create service operation . 10
4.2.2.1 General . 10
4.2.2.2 Creating UE radio capability provisioning resource . 10
4.2.3 Nucmf_Provisioning_Update service operation . 11
4.2.3.1 General . 11
4.2.3.2 Modifying a UE radio capability provisioning resource . 11
4.2.4 Nucmf_Provisioning_Delete service operation . 12
4.2.4.1 General . 12
4.2.4.2 Removing a UE radio capability provisioning resource . 12
5 Nucmf_Provisioning Service API . 12
5.1 Introduction . 12
5.2 Usage of HTTP . 13
5.2.1 General . 13
5.2.2 HTTP standard headers . 13
5.2.2.1 General . 13
5.2.2.2 Content type . 13
5.2.3 HTTP custom headers . 13
5.3 Resources . 14
5.3.1 Overview . 14
5.3.2 Resource: UE radio capability provisionings (Collection) . 14
5.3.2.1 Description . 14
5.3.2.2 Resource Definition . 14
5.3.2.3 Resource Standard Methods . 14
5.3.2.3.1 POST . 14
5.3.2.4 Resource Custom Operations . 15
5.3.3 Resource: Individual UE radio capability provisioning (Document) . 15
5.3.3.1 Description . 15
5.3.3.2 Resource Definition . 15
5.3.3.3 Resource Standard Methods . 16
5.3.3.3.1 GET . 16
5.3.3.3.2 PUT . 16
5.3.3.3.3 PATCH . 17
5.3.3.3.4 DELETE . 17
5.4 Custom Operations without associated resources. 18
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 4 ETSI TS 129 675 V17.5.0 (2022-05)
5.5 Notifications . 18
5.6 Data Model . 18
5.6.1 General . 18
5.6.2 Structured data types . 18
5.6.2.1 Introduction . 18
5.6.2.2 Type: RacsData . 19
5.6.2.3 Type: RacsDataPatch . 19
5.6.3 Simple data types and enumerations . 19
5.6.3.1 Introduction . 19
5.6.3.2 Simple data types . 19
5.7 Error Handling . 20
5.7.1 General . 20
5.7.2 Protocol Errors . 20
5.7.3 Application Errors . 20
5.8 Feature negotiation . 20
5.9 Security . 20
Annex A (normative): OpenAPI specification . 21
A.1 General . 21
A.2 Nucmf_Provisioning API . 21
Annex B (informative): Change history . 26
History . 27

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 5 ETSI TS 129 675 V17.5.0 (2022-05)
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, certain modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not
appear in Technical Reports.
NOTE 2: 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
NOTE 3: 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
NOTE 4: The constructions "can" and "cannot" shall not to be used as 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

---------------------- Page: 6 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 6 ETSI TS 129 675 V17.5.0 (2022-05)
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
NOTE 5: The constructions "is" and "is not" do not indicate requirements.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 7 ETSI TS 129 675 V17.5.0 (2022-05)
1 Scope
The present document specifies the stage 3 protocol and data model for the Nucmf Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UCMF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP 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 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13] IETF RFC 7807: "Problem Details for HTTP APIs".
[14] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
[15] 3GPP TS 29.122: "T8 reference point for northbound Application Programming Interfaces
(APIs)".
[16] IETF RFC 7396: "JSON Merge Patch".
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 8 ETSI TS 129 675 V17.5.0 (2022-05)
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 Symbols
No symbol is defined in the present document.
3.3 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 definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
AF Application Function
IMEI-TAC Type Allocation Code part of an IMEI
NEF Network Exposure Function
NF Network Function
RACS Radio Capabilities Signalling optimisation
UCMF UE radio Capability Management Function
4 UE Radio Capability Provisioning Service
4.1 Service Description
4.1.1 Overview
The UE radio capability provisioning service, as defined in 3GPP TS 23.502 [3], is provided by the UE radio Capability
Management Function (UCMF).
This service:
- allows NF service consumers to create, update and delete UCMF dictionary entries for Manufacturer-assigned
UE Radio Capability IDs.
4.1.2 Service Architecture
The Service Architecture is defined in 3GPP TS 23.501 [2].
The UE radio capability provisioning service (Nucmf_Provisioning) is part of the Nucmf service-based interface
exhibited by the UCMF.
The known NF service consumers of the Nucmf_Provisioning service are:
- Network Exposure Function (NEF); and
- Application Function (AF).
The Nucmf_Provisioning service is provided by the UCMF and consumed by the NEF and the AF, as shown in
figure 4.1.2-1 for the SBI representation model and in figure 4.1.2-2 for reference point representation model.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 9 ETSI TS 129 675 V17.5.0 (2022-05)
UCMF
Nucmf
Nucmf_Provisioning
NEF
AF

Figure 4.1.2-1: Nucmf_Provisioning service Architecture, SBI representation
UCMF
N57 N56
AF NEF

Figure 4.1.2-2: Nucmf_Provisioning service Architecture, reference point representation
4.1.3 Network Functions
4.1.3.1 UCMF
The UCMF is a functional element that provides service to the NF service consumer.
It allows NF consumers to provision (create, update and delete) UCMF dictionary entries for Manufacturer-assigned UE
Radio Capability IDs.
4.1.3.2 NF Service Consumers
The Network Exposure Function (NEF):
- Provision (create, update and delete) UCMF dictionary entries for Manufacturer-assigned UE Radio Capability
IDs to the UCMF, if it receives the UE Radio Capability information from the untrusted AF.
The Application Function (AF):
- As the trusted AF, provision (create, update and delete) UCMF dictionary entries for Manufacturer-assigned UE
Radio Capability IDs to the UCMF.
4.2 Service Operations
4.2.1 Introduction
Service operations defined for the Nucmf_Provisioning Service are shown in table 4.2.1-1.
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 29.675 version 17.5.0 Release 17 10 ETSI TS 129 675 V17.5.0 (2022-05)
Table 4.2.1-1: Nucmf_Provisioning Service Operations
Service Operation Name Description Initiated by
Nucmf_Provisioning_Create This service operation is used by an NF service consumer NF service
to create UE radio capability provisioning resource for consumer (e.g.
Manufacturer-assigned UE Radio Capability IDs. AF, NEF)
Nucmf_Provisioning_Update This service operation is used by an NF service consumer NF service
to modify UE radio capability provisioning resource for consumer (e.g.
Manufacturer-assigned UE Radio Capability IDs. AF, NEF)
Nucmf_Provisioning_Delete This service operation is used by an NF service consumer NF service
to remove a UE radio capability provisioning resource. consumer (e.g.
AF, NEF)

4.2.2 Nucmf_Provisioning_Create service operation
4.2.2.1 General
This service operation is used by an NF service consumer to create UE radio capability provisioning resource for
Manufacturer-assigned UE Radio Capability IDs.
The following procedure using the Nucmf_Provisioning_Create service operation is supported:
- creating a UE radio capability provisioning resource.
4.2.2.2 Creating UE radio capability provisioning resource
This procedure is used by the NF service consumer (e.g. NEF) to create a UE radio capability provisioning resource
containing UCMF dictionary entries for Manufacturer-assigned UE Radio Capability IDs, as defined in
3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
NF service
UCMF
consumer
1. POST …/provisionings
2. "201 Created"

Figure 4.2.2.2-1: Creating new UE radio capability provisioning resource
To create a UE radio capability provisioning resource, the NF service consumer shall send an HTTP POST request to
the UCMF with: "{apiRoot}/nucmf-provisioning//provisionings" as request URI as shown in step 1 of
figure 4.2.2.2-1, and the "RacsData" data structure as request body. The "RacsData" data type shall contain one or more
RACS configurations in the "racsConfigs" attribute which include:
- a RACS ID in the "racsId" attribute;
- UE radio capability information in the "racsParamEps" and/or "racsParam5Gs" attributes; and
- the related UE model(s) IMEI-TAC value(s) in the "imeiTacs" attribute.
Upon re
...