5G; 5G System; Access and Mobility Policy Control Service; Stage 3 (3GPP TS 29.507 version 17.11.0 Release 17)

RTS/TSGC-0329507vhb0

General Information

Status
Not Published
Current Stage
12 - Citation in the OJ (auto-insert)
Completion Date
25-Mar-2025
Ref Project
Standard
ETSI TS 129 507 V17.11.0 (2025-03) - 5G; 5G System; Access and Mobility Policy Control Service; Stage 3 (3GPP TS 29.507 version 17.11.0 Release 17)
English language
78 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


TECHNICAL SPECIFICATION
5G;
5G System;
Access and Mobility Policy Control Service;
Stage 3
(3GPP TS 29.507 version 17.11.0 Release 17)


3GPP TS 29.507 version 17.11.0 Release 17 1 ETSI TS 129 507 V17.11.0 (2025-03)

Reference
RTS/TSGC-0329507vhb0
Keywords
5G
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 - 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 2025.
All rights reserved.
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 2 ETSI TS 129 507 V17.11.0 (2025-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.507 version 17.11.0 Release 17 3 ETSI TS 129 507 V17.11.0 (2025-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Access and Mobility Policy Control Service. 9
4.1 Service Description . 9
4.1.1 Overview . 9
4.1.2 Service Architecture . 9
4.1.3 Network Functions . 11
4.1.3.1 Policy Control Function (PCF) . 11
4.1.3.2 NF Service Consumers . 11
4.2 Service Operations . 11
4.2.1 Introduction. 11
4.2.2 Npcf_AMPolicyControl_Create Service Operation . 11
4.2.2.1 General . 11
4.2.2.2 Void. 15
4.2.2.2.0 Void . 15
4.2.2.2.1 Void . 15
4.2.2.2.2 Void . 15
4.2.2.3 AMF Access and Mobility Policy . 15
4.2.2.3.1 Service Area Restriction . 15
4.2.2.3.2 RFSP Index . 16
4.2.2.3.3 UE-AMBR . 16
4.2.2.3.4 SMF Selection Management . 17
4.2.2.3.5 UE-Slice-MBR . 17
4.2.2.3.6 5G access stratum time distribution . 17
4.2.3 Npcf_AMPolicyControl_Update Service Operation . 18
4.2.3.1 General . 18
4.2.3.2 Policy Control Request Triggers . 21
4.2.3.3 Encoding of updated policy. 22
4.2.4 Npcf_AMPolicyControl_UpdateNotify Service Operation . 23
4.2.4.1 General . 23
4.2.4.2 Policy update notification . 23
4.2.4.3 Request for termination of the policy association . 25
4.2.5 Npcf_AMPolicyControl_Delete Service Operation . 26
5 Npcf_AMPolicyControl API . 27
5.1 Introduction . 27
5.2 Usage of HTTP . 27
5.2.1 General . 27
5.2.2 HTTP standard headers . 27
5.2.2.1 General . 27
5.2.2.2 Content type . 28
5.2.3 HTTP custom headers . 28
5.3 Resources . 28
5.3.1 Resource Structure . 28
5.3.2 Resource: AM Policy Associations . 29
5.3.2.1 Description . 29
5.3.2.2 Resource definition . 29
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 4 ETSI TS 129 507 V17.11.0 (2025-03)
5.3.2.3 Resource Standard Methods . 29
5.3.2.3.1 POST . 29
5.3.3 Resource: Individual AM Policy Association . 30
5.3.3.1 Description . 30
5.3.3.2 Resource definition . 30
5.3.3.3 Resource Standard Methods . 30
5.3.3.3.1 GET . 30
5.3.3.3.2 DELETE . 31
5.3.3.4 Resource Custom Operations . 32
5.3.3.4.1 Overview . 32
5.3.3.4.2 Operation: Update . 32
5.3.3.4.2.1 Description . 32
5.3.3.4.2.2 Operation Definition . 32
5.4 Custom Operations without associated resources. 33
5.5 Notifications . 33
5.5.1 General . 33
5.5.2 Policy Update Notification . 33
5.5.2.1 Description . 33
5.5.2.2 Operation Definition . 33
5.5.3 Request for termination of the policy association . 34
5.5.3.1 Description . 34
5.5.3.2 Operation Definition . 34
5.6 Data Model . 35
5.6.1 General . 35
5.6.2 Structured data types . 38
5.6.2.1 Introduction . 38
5.6.2.2 Type PolicyAssociation . 39
5.6.2.3 Type PolicyAssociationRequest . 42
5.6.2.4 Type PolicyAssociationUpdateRequest . 45
5.6.2.5 Type PolicyUpdate . 48
5.6.2.6 Type TerminationNotification. 50
5.6.2.7 Type SmfSelectionData . 51
5.6.2.8 Type CandidateForReplacement . 51
5.6.2.9 Type AmRequestedValueRep . 52
5.6.2.10 Type: AsTimeDistributionParam . 52
5.6.2.11 Type UeSliceMbr . 52
5.6.3 Simple data types and enumerations . 53
5.6.3.1 Introduction . 53
5.6.3.2 Simple data types . 53
5.6.3.3 Enumeration: RequestTrigger . 53
5.6.3.4 Enumeration: PolicyAssociationReleaseCause . 54
5.7 Error handling . 54
5.7.1 General . 54
5.7.2 Protocol Errors . 54
5.7.3 Application Errors . 54
5.8 Feature negotiation . 55
5.9 Security . 55
Annex A (normative): OpenAPI specification . 57
A.1 General . 57
A.2 Npcf_AMPolicyControl API . 57
Annex B (normative): Wireless and wireline convergence access support . 68
B.1 Scope . 68
B.2 Npcf_AMPolicyControl Service . 68
B.2.1 Service Description . 68
B.2.1.1 Overview . 68
B.2.1.2 Service Architecture . 68
B.2.1.3 Network Functions . 68
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 5 ETSI TS 129 507 V17.11.0 (2025-03)
B.2.1.3.1 Policy Control Function (PCF) . 68
B.2.1.3.2 NF Service Consumers . 68
B.3 Service Operation . 68
B.3.1 Introduction . 68
B.3.2 Npcf_AMPolicyControl_Create Service Operation . 69
B.3.2.1 General . 69
B.3.2.2 AMF Access and Mobility Policy . 70
B.3.2.2.1 General . 70
B.3.2.2.2 Wireline Service Area Restriction . 70
B.3.2.2.3 Void. 70
B.3.3 Npcf_AMPolicyControl_UpdateNotify Service Operation . 70
B.3.3.1 General . 70
B.3.4 Npcf_AMPolicyControl_Update Service Operation . 71
B.3.4.1 General . 71
B.3.4.2 Policy Control Request Triggers . 71
B.3.4.3 Encoding of updated policy . 72
B.3.5 Npcf_AMPolicyControl_Delete Service Operation . 72
B.3.5.1 General . 72
Annex C (informative): Change history . 73
History . 77

ETSI
3GPP TS 29.507 version 17.11.0 Release 17 6 ETSI TS 129 507 V17.11.0 (2025-03)
Foreword
rd
This Technical Specification has been produced by the 3 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.
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 7 ETSI TS 129 507 V17.11.0 (2025-03)
1 Scope
The present specification provides the stage 3 definition of the Access and Mobility Policy Control Service
(Npcf_AMPolicyControl) of the 5G System.
The stage 2 definition and procedures of the Access and Mobility Policy Control Service are contained in
3GPP TS 23.502 [3] and 3GPP TS 23.503 [4]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows are provided in 3GPP TS 29.513 [7].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
of the 5G System are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The Access and Mobility Policy Control Service is provided by the Policy Control Function (PCF). This service
provides Access and Mobility Policies.
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 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[5] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[7] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter
mapping; Stage 3".
[8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[9] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[10] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[12] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[13] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[14] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[15] void.
[16] void.
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 8 ETSI TS 129 507 V17.11.0 (2025-03)
[17] 3GPP TS 29.519: "5G System; Usage of the Unified Data Repository service for Policy Data,
Application Data and Structured Data for Exposure; Stage 3".
[18] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace
control and configuration management".
[19] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[20] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[21] IETF RFC 7807: "Problem Details for HTTP APIs".
[22] 3GPP TR 21.900: "Technical Specification Group working methods".
[23] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[24] 3GPP TS 29.531: "5G System; Network Slice Selection Services; Stage 3".
[25] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[26] 3GPP TS 29.534: "5G System; Access and Mobility Policy Authorization Service; Stage 3".
[27] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[28] 3GPP TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
[29] 3GPP TS 29.525: "UE Policy Control Service; Stage 3".
[30] 3GPP TS 29.521: "5G System; Binding Support Management Service; Stage 3".
[31] 3GPP TS 29.502: "5G System; Session Management Services; 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 TR 21.905 [1].
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [2], clause 3.1
apply:
Allowed NSSAI
Target NSSAI
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 present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
5G-BRG 5G Broadband Residential Gateway
5G-RG 5G Residential Gateway
5GC 5G Core Network
5G-CRG 5G Cable Residential Gateway
5GS 5G System
AMBR Aggregated Maximum Bit Rate
AMF Access and Mobility Management Function
BBF Broadband Forum
DNN Data Network Name
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 9 ETSI TS 129 507 V17.11.0 (2025-03)
EPS Evolved Packet System
FN-BRG Fixed Network Broadband Residential Gateway
FN-CRG Fixed Network Cable Residential Gateway
FN-RG Fixed Network Residential Gateway
FQDN Fully Qualified Domain Name
GBR Guaranteed Bit Rate
GPSI Generic Public Subscription Identifier
GUAMI Globally Unique AMF Identifier
HFC Hybrid Fiber-Coaxial
JSON JavaScript Object Notation
LBO Local Break Out (roaming)
MBR Maximum Bit Rate
NID Network Identifier
NRF Network Repository Function
NSSAI Network Slice Selection Assistance Information
NWDAF Network Data Analytics Function
PCF Policy Control Function
PEI Permanent Equipment Identifier
PRA Presence Reporting Area
QoS Quality of Service
RFSP RAT Frequency Selection Priority
SMF Session Management Function
S-NSSAI Single Network Slice Selection Assistance Information
SNPN Stand-alone Non-Public Network
SUPI Subscription Permanent Identifier
UDM Unified Data Management
URSP UE Route Selection Policy
V-PCF Visited Policy Control Function
W-5GAN Wireline 5G Access Network
W-5GBAN Wireline BBF Access Network
W-5GCAN Wireline 5G Cable Access Network
W-AGF Wireline Access Gateway Function
4 Access and Mobility Policy Control Service
4.1 Service Description
4.1.1 Overview
The Access and Mobility Policy Control Service, as defined in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4], is
provided by the Policy Control Function (PCF).
This service provides access control and mobility management related policies to the NF service consumer and offers
the following functionalities:
- policy creation based on a request from the NF service consumer during UE registration;
- notification of the NF service consumer of the updated policies which are subscribed; and
- deletion of the policy context for a UE.
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 also
described in 3GPP TS 29.513 [7].
The Access and Mobility Policy Control Service (Npcf_AMPolicyControl) is part of the Npcf service-based interface
exhibited by the Policy Control Function (PCF).
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 10 ETSI TS 129 507 V17.11.0 (2025-03)
The known NF service consumer of the Npcf_AMPolicyControl service is the Access and Mobility Management
Function (AMF).
The AMF accesses the Access and Mobility Policy Control Service at the PCF via the N15 Reference point. In the
roaming scenario, the N15 reference point is located between the V-PCF in the visited network and the AMF.
(V-)PCF
Npcf
Npcf_AMPolicyControl
AMF
Figure 4.1.2-1: Reference Architecture for the Npcf_AMPolicyControl Service; SBI representation

Figure 4.1.2-2: Non-roaming Reference Architecture for the Npcf_AMPolicyControl Service; reference
point representation
V-PCF
N15
AMF
Figure 4.1.3-2: Roaming reference Architecture for the Npcf_AMPolicyControl Service; reference
point representation
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 11 ETSI TS 129 507 V17.11.0 (2025-03)
4.1.3 Network Functions
4.1.3.1 Policy Control Function (PCF)
The Policy Control Function (PCF):
- Supports unified policy framework to govern network behaviour; and
- Provides Access and Mobility Management related policies to the NF service consumer that enforces them.
In the roaming scenario, the Visited Policy Control Function (V-PCF) provides the functions described in this
clause towards the visited network.
4.1.3.2 NF Service Consumers
The Access and Mobility Management function (AMF) provides:
- Registration management;
- Connection management;
- Reachability management; and
- Mobility Management.
4.2 Service Operations
4.2.1 Introduction
Table 4.2.1-1: Operations of the Npcf_AMPolicyControl Service
Service operation name Description Initiated by
Npcf_AMPolicyControl_Create Creates an AM Policy Association and provides NF service consumer
corresponding policies to the NF service consumer. (e.g. AMF)
Npcf_AMPolicyControl_Update Updates an AM Policy Association and provides NF service consumer
corresponding policies to the NF service consumer (e.g. AMF)
when a policy control request trigger is met or the
AMF is relocated due to UE mobility and the old PCF
is selected.
Npcf_AMPolicyControl_UpdateNotify Provides updated policies to the NF service PCF (V-PCF in
consumer. roaming case)
Npcf_AMPolicyControl_Delete Provides means for the NF service consumer to NF service consumer
delete the AM Policy Association. (e.g. AMF)

4.2.2 Npcf_AMPolicyControl_Create Service Operation
4.2.2.1 General
The procedure in the present clause is applicable when the NF service consumer (e.g. AMF) creates an AM policy
association when the UE registers to the network, and when the AMF is relocated (between the different AMF sets) and
the new AMF selects a new PCF. The procedure for the case where the AMF is relocated and the new AMF selects the
old PCF is defined in clause 4.2.3.1.
The creation of an AM policy association only applies for normally registered UEs, i.e., it does not apply for
Emergency Registered UEs.
Figure 4.2.2.1-1 illustrates the creation of a policy association.
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 12 ETSI TS 129 507 V17.11.0 (2025-03)

Figure 4.2.2.1-1: Creation of a policy association
When a UE registers and a UE context is being established, the AMF can obtain Service Area Restrictions, RFSP index,
subscribed UE-AMBR, subscribed UE-Slice-MBR(s) and GPSI(s) from the UDM during the Access and Mobility
Subscription Data retrieval procedure, the list of NWDAF instance IDs used for the UE and their associated Analytic
ID(s) consumed by the AMF and the allowed NSSAI and the Target NSSAI from local configuration or from the NSSF
during the slice selection procedure and shall decide based on local policies whether to request policies from the PCF.
To request policies from the PCF, the NF service consumer (e.g. AMF) shall send an HTTP POST request with:
"{apiRoot}/npcf-am-policy-control/v1/policies" as Resource URI and the PolicyAssociationRequest data structure as
request body that shall include:
- Notification URI encoded as "notificationUri" attribute;
- SUPI encoded as "supi" attribute; and
- if the feature "SliceSupport" or the feature "DNNReplacementControl" is supported in the NF service consumer
and the UE is registered via a 3GPP access, the allowed NSSAI in the 3GPP access encoded in the
"allowedSnssais" attribute;
and that shall include when available:
- GPSI encoded as "gpsi" attribute;
- if the feature "MultipleAccessTypes" is not supported, the access type encoded as "accessType" attribute;
NOTE 1: In this Release, for SNPN-enabled UE registered in the SNPN, direct access to the SNPN is specified for
3GPP access only.
- Permanent Equipment Identifier (PEI) encoded as "pei" attribute;
- User Location Information encoded as "userLoc" attribute;
- UE Time Zone encoded as "timeZone" attribute;
- the identifier of the serving network (the PLMN Identifier or the SNPN Identifier)encoded as "servingPlmn"
attribute;
NOTE 2: The SNPN Identifier consists of the PLMN Identifier and the NID.
- if the feature "MultipleAccessTypes" is not supported, the RAT type encoded as "ratType" attribute;
- Service Area Restrictions (see clause 4.2.2.3.1) derived from the Service Area Restrictions obtained from the
UDM by mapping any service areas denoted by geographical information into Tracking Area Identities (TAIs)
and encoded as "servAreaRes" attribute;
- RFSP index (see clause 4.2.2.3.2) as obtained from the UDM encoded as "rfsp" attribute;
- a list of Internal Group Identifiers encoded as "groupIds" attribute;
- if the NF service consumer is an AMF, the GUAMI encoded as "guami" attribute;
ETSI
3GPP TS 29.507 version 17.11.0 Release 17 13 ETSI TS 129 507 V17.11.0 (2025-03)
- if the NF service consumer is an AMF, the name of a service produced by the AMF that expects to receive
information within Npcf_AMPolicyControl_UpdateNotify service operation encoded as "serviceName"
attribute;
- Alternate or backup IPv4 Address(es) where to send Notifications encoded as "altNotifIpv4Addrs" attribute;
- Alternate or backup IPv6 Address(es) where to send Notifications encoded as "altNotifIpv6Addrs" attribute;
- Alternate or backup FQDN(s) where to send Notifications encoded as "altNotifFqdns" attribute;
- trace control and configuration parameters information encoded as "traceReq" attribute;
- if the feature "UE-AMBR_Authorization" is supported in the NF service consumer, the subscribed UE-AMBR
(see clause 4.2.2.3.3) in the "ueAmbr" attribute;
- if the feature "DNNReplacementControl" is supported, the mapping of each S-NSSAI of the Allowed NSSAI to
the corresponding S-NSSAI of the HPLMN encoded in the "mappingSnssais" attribute;
- if the feature "UE-Slice-MBR_Authorization" is supported in the NF service consumer, the subscribed UE-Slice-
MBR for each subscribed S-NSSAI of the home PLMN mapping to a S-NSSAI of the serving PLMN if available
(see clause 4.2.2.3.5) encoded in the "ueSliceMbrs" attribute; and.
- when the "EneNA" feature is supported, the list of NWDAF instance IDs used for the UE and their associated
Analytic IDs consumed by the NF service consumer within the "nwdafDatas" attribute; and
- if the feature "TargetNSSAI" is supported in the NF service consumer, the Target NSSAI generated by the NF
service consumer or received from the NSSF encoded in the "targetSnssais" attribute.
Upon the reception of this HTTP POST request, the PCF shall:
- assign a policy association ID;
- determine the applicable policy (taking into consideration and optionally modifying the possibly received UE-
AMBR, UE-Slice-MBR(s) for the allowed NSSAI, Service Area Restrictions and/or RFSP index);
- for the successful case, send a HTTP "201 Created" response with the URI for the created resource in the
"Location" header field
NOTE 3: The assigned policy association ID is part of the URI for the created resource and is thus associated with
the SUPI.
and the PolicyAssociation data type as response body including:
- conditionally AMF Access and Mobility Policy (see clause 4.2.2.3), i.e.:
a) if the PCF received the "servAreaRes" attribute in the request, Service Area Restrictions encoded as
"servAreaRes" attribute; and/or
b) if the PCF received the "rfsp" attribute in the request, RAT Frequency Selection Priority (RFSP) Index
encoded as "rfsp" attribute; and/or
c) if the feature "UE-AMBR_Authorization" is supported and the PCF received the "ueAmbr" attribute in
the request, the authorized UE-AMBR encoded as "ueAmbr" attribute;
d) if the feature "UE-Slice-MBR_Authorization" is supported and the PCF received the "ueSliceMbrs"
attribute in the request, the corresponding authorized UE-Slice-MBR(s) encoded as "ueSliceMbrs"
attribute; and/or
e) if the feature "AMInfluence" is supported, the PCF for the UE determines that the access and mobility
policies may be influenced by the traffic of PDU session(s) and local operator policies indicate that the
PCF for the UE shall subscribe with the PCF for the PDU session for established/terminat
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...