Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.534  Word version:  18.3.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 8

The present document specifies the stage 3 protocol and data model for the Access and Mobility Policy Authorization service (Npcf_AMPolicyAuthorization) of the 5G System.
The 5G System stage 2 architecture of the Access and Mobility Policy Authorization service are contained in TS 23.502 and TS 23.503. The 5G System Architecture is defined in TS 23.501.
Stage 3 call flows for policy and charging control use cases are provided in TS 29.513.
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 and TS 29.501.
The Access and Mobility Policy Authorization service is provided by the Policy Control Function (PCF). This service creates access and mobility policies (e.g. service area restrictions, or access stratum time distribution information) as requested by an authorized NF service consumer (e.g. AF, NEF, or TSCTSF) for the Access and Mobility Policy Context to which the related NF service consumer's context (e.g. AF, NEF, or TSCTSF) is bound. This service also enables subscription/notifications on UE 5G ProSe Policy event(s) related to the UE context to which the NF service consumer's context (e.g. 5G DDNMF) is bound.
Up

2  Referencesp. 8

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5]
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]
TR 21.900: "Technical Specification Group working methods".
[8]
TS 33.501: "Security architecture and procedures for 5G system".
[9]
RFC 6749:  "The OAuth 2.0 Authorization Framework".
[10]
TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11]
RFC 9113:  "HTTP/2".
[12]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[13]
RFC 9457:  "Problem Details for HTTP APIs".
[14]
TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[15]
TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3".
[16]
TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
[17]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[18]
RFC 7396:  "JSON Merge Patch".
[19]
RFC 3986:  "Uniform Resource Identifier (URI): Generic Syntax".
[20]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[21]
TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
[22]
TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[23]
TS 24.555: "Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3".
[24]
TS 29.555: "5G System; 5G Direct Discovery Name Management Services; Stage 3".
[25]
TS 29.565: "5G System; Time Sensitive Communication and Time Synchronization Function Services; Stage 3".
Up

3  Definitions, symbols and abbreviationsp. 9

3.1  Definitionsp. 9

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Application Function (AF):
Element acting on behalf of applications(s) that require the control of the Access and Mobility context of a UE, which can in turn lead to e.g. Service Area Restrictions and/or RFSP changes.
AF application AM context:
Information about the capabilities that an AF application requires from the access network for a registered UE. It is established by the AF before or during the use of the service that requires it.
NF service consumer AM context:
Information about the capabilities that a NF service consumer requires from the access network for a registered UE.
Up

3.2  Symbolsp. 9

None.

3.3  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5G DDNMF
5G Direct Discovery Name Management Function
AF
Application Function
AMF
Access and Mobility Management Function
JSON
JavaScript Object Notation
NEF
Network Exposure Function
NF
Network Function
PCF
Policy Control Function
PDUID
ProSe Discovery UE ID
ProSe
Proximity Services
RFSP
RAT Frequency Selection Priority
SMF
Session Management Function
TSCTSF
Time Sensitive Communication and Time Synchronization Function
Up

Up   Top   ToC