B.3 Service Operation

29.5073GPP5G SystemAccess and Mobility Policy Control ServiceRelease 18Stage 3TS

B.3.1 Introduction

The descriptions in clause 4.2.1 are applied with the following differences:

– UE is replaced by the 5G-RG.

B.3.2 Npcf_AMPolicyControl_Create Service Operation

B.3.2.1 General

The procedure defined in clause 4.2.2.1 is applied with following differences:

– UE is replaced by the 5G-RG or FN-RG if applicable.

– Handling of RFSP information is not applicable if the 5G-RG or FN-RG connects the 5GC via wireline access.

– When the 5G-BRG or FN-BRG connects the 5GC via W-5BBAN, the "n3gaLocation" attribute shall be included in the "ueLoc" attribute and:

– Global Line ID including the line Id and either PLMN Id or operator Id shall be encoded within the "gli" attribute; and

– the "w5gbanLineType" attribute to indicate whether the W-5GBAN access is DSL or PON may be included.

– The HFC Node Identifier in the "hfcNodeId" attribute of the "n3gaLocation" attribute included in the "userLoc" attribute within the PolicyAssociationRequest data structure when the 5G-CRG or FN-CRG connects to the 5GC via W-5GCAN.

– Only the policy control request triggers defined in clause B.3.4.2 are provided by the PCF when the 5G-RG or FN-RG connects the 5GC via wireline access.

– The PolicyAssociationRequest data structure shall include, if available, and if the feature "WirelineWirelessConvergence" is supported, wireline access Service Area Restrictions (see clause B.3.2.2.2) derived from the wireline access Service Area Restrictions obtained from the UDM by mapping any service areas denoted by geographical information into Line IDs (for a 5G-BRG) or HFC Node IDs (for a 5G-CRG and FN-CRG) encoded as "wlServAreaRes" attribute.

– The PolicyAssociation data type returned as body of the HTTP "201 Created" response shall include if the feature "WirelineWirelessConvergence" is supported, and if the PCF received the "wlServAreaRes" in the request, wireline Service Area Restrictions encoded as "wlServAreaRes" attribute.

– If the feature "MultipleAccessTypes" is supported, the NF service consumer (e.g. AMF) shall include:

a) the RAT type entry corresponding to non-3GPP wireline access and/or the RAT type entry corresponding to the 3GPP access encoded in the "ratTypes" attribute, if available; and

b) the "accessTypes" attribute indicating registration in the 3GPP access, or registration in the non-3GPP access, or registration in both 3GPP and non-3GPP access, if available.

NOTE: When both, 3GPP access and non-3GPP accesses are available, the "accessType" attribute and the "ratType" attribute within the PolicyAssociationRequest type contain the access type and RAT type corresponding to the 3GPP access.

– If the feature "SliceSupport" or the feature "DNNReplacementControl" is supported in the AMF, the UE is registered in the non-3GPP access, and the feature "MultipleAccessTypes" is supported, the NF service consumer (e.g. AMF) shall include the Allowed NSSAI in the non-3GPP access encoded in the "n3gAllowedSnssais" attribute.

– If the feature "DNNReplacementControl" is supported, the UE is registered in the non-3GPP access, and the feature "MultipleAccessTypes" is supported, the NF service consumer (e.g. AMF) may include the mapping of each S-NSSAI of the Allowed NSSAI in the non-3GPP access to the corresponding S-NSSAI of the HPLMN encoded in the "mappingSnssais" attribute.

– The PEI that may be included within the "pei" attribute shall have one of the following representations:

a) If the 5G-BRG supports only wireline access, the PEI shall be the 5G-BRG MAC address.

b) If the 5G-CRG supports only wireline access, the PEI shall be the cable modem MAC address.

c) If the 5G-RG supports at least one 3GPP access technology, the PEI shall be the allocated IMEI or IMEISV.

d) For the FN-BRG and FN-CRG, the PEI shall be the FN-RG MAC address.

NOTE: When the PEI includes an indication that the MAC address cannot be used as Equipment identifier of the FN-RG, the PEI cannot be trusted for regulatory purposes and cannot be used for equipment based policy evaluation.

B.3.2.2 AMF Access and Mobility Policy

B.3.2.2.1 General

The functionality defined in clause 4.2.2.3 shall apply with the following modifications:

– UE-AMBR defined in clause 4.2.2.3.3 shall not apply for wireline access.

– RFSP Index defined in clause 4.2.2.3.2 shall not apply for wireline access.

– Service Area Restriction defined in clause 4.2.2.3.1 is only applicable for a 5G-RG connected via NG-RAN. The wireline access Service Area Restriction defined in clause B.3.2.2.2 shall apply for a FN-CRG and/or a 5G-RG (5G-BRG and 5G-CRG) connected via wireline access.

B.3.2.2.2 Wireline Service Area Restriction

If service area restrictions are enabled, and if the feature "WirelineWirelessConvergence" is supported, the Service Area Restriction information is encoded using the "WirelineServiceAreaRestriction" data type defined in 3GPP TS 29.571 [11] and consists of:

– either a limited allowed area represented as both of:

(i) a list of either Line IDs encoded as "globLineIds" (for a 5G-BRG) or HFC-Node IDs (for 5G-CRG and FN-CRG) encoded as "hfcNIds" attribute within the "areas" attribute; and

(ii) the "restrictionType" attribute set to "ALLOWED_AREAS";

– or a limited not allowed area represented as both of:

(i) a list of either Line IDs encoded as "globLineIds" (for a 5G-BRG) or HFC-Node IDs (for 5G-CRG and FN-CRG) encoded as "hfcNIds" attribute within the "areas" attribute; and

(ii) the "restrictionType" attribute set to "NOT_ALLOWED_AREAS";

When the authorized wireline service area restrictions result in an unlimited set of allowed HFC-Node IDs or Line IDs, the PCF shall include:

– an empty "wlServAreaRes" attribute; or

– the "restrictionType" attribute set to "NOT_ALLOWED_AREAS" and an empty "areas" attribute.

When the authorized wireline service area restrictions result in an unlimited set of not-allowed HFC-Node IDs or Line IDs, the PCF shall include the "restrictionType" attribute set to "ALLOWED_AREAS" and an empty "areas" attribute.

B.3.2.2.3 Void

B.3.3 Npcf_AMPolicyControl_UpdateNotify Service Operation

B.3.3.1 General

The functionality defined in clause 4.2.4.2 and 4.2.4.3 shall apply.

B.3.4 Npcf_AMPolicyControl_Update Service Operation

B.3.4.1 General

The general procedure specified in clause 4.2.3.2 to modify an existing AM policy association shall apply with the exception that for a FN-RG or a 5G-RG registering via wireline access only, the existing AM policy association shall not be updated due to location change (tracking area), change of UE presence in PRA, or RFSP index change.

If the feature "MultipleAccessTypes" is supported, the NF service consumer may include in the PolicyAssociationUpdateRequest data structure:

– if the Access Type and/or the RAT type changed and the access type change Policy Control Request Trigger was previously provisioned (see clause B.3.4.2), the list of Access Type and RAT Type combinations available encoded in the "accessTypes" attribute, "ratTypes" attribute.

When the feature "MultipleAccessTypes" is supported the PCF may include in the PolicyUpdate data type the access type change Policy Control Request Trigger (see clause B.3.4.2) encoded within the "triggers" attribute.

If the feature "SliceSupport" or the feature "DNNReplacementControl" is supported in the AMF, the UE is registered in the non-3GPP access, and the feature "MultipleAccessTypes" is supported, the NF service consumer (e.g. AMF) shall include the Allowed NSSAI in the non-3GPP access encoded in the "n3gAllowedSnssais" attribute together with the "ALLOWED_NSSAI_CH" policy control request trigger when a change of the Allowed NSSAI for the non-3GPP access occurred.

If the feature "DNNReplacementControl" is supported, the UE is registered in the non-3GPP access, and the feature "MultipleAccessTypes" is supported, the Allowed NSSAI changed and/or the mapping of a S-NSSAI of the Allowed NSSAI to the corresponding S-NSSAI of the HPLMN changed, and the Policy Control Request Trigger "Change of allowed NSSAI" was provided then NF service consumer (e.g. AMF) may include the mapping of each S-NSSAI of the Allowed NSSAI in the non-3GPP access to the corresponding S-NSSAI of the HPLMN encoded in the "mappingSnssais" attribute.

In addition, if the feature "WirelineWirelessConvergence" is supported:

– the PolicyAssociationUpdateRequest data structure shall include if a wireline access Service Area restriction change occurred, the wireline access Service Area Restrictions (see clause B.3.2.2.2) derived from the ones obtained from the UDM encoded as "wlServAreaRes" attribute;

– the PolicyUpdate data returned in the response, if the PCF received the " wlServAreaRes" attribute in the request, wireline access Service Area Restrictions encoded as "wlServAreaRes" attribute.

B.3.4.2 Policy Control Request Triggers

For a 5G-RG registering via NG-RAN, the Policy Control Request Triggers defined in clause 4.2.3.2 shall apply.

For a FN-RG or a 5G-RG registering via wireline access, only the following Policy Control Request Triggers defined in clause 4.2.3.2 shall apply:

– "SERV_AREA _CH", i.e. Service Area Restriction change: the UDM notifies the NF service consumer that the subscribed service area restriction information has changed;

– "ALLOWED_NSSAI_CH", i.e. change of allowed NSSAI of the served UE;

NOTE 1: The "ALLOWED_NSSAI_CH" trigger only applies if the feature "SliceSupport" or the feature "DNNReplacementControl" is supported.

NOTE 2: The "SERV_AREA_CH" trigger is also used to notify that the subscribed wireline access service area restriction information has changed.

– "ACCESS_TYPE_CH", i.e. the access type change: the NF service consumer notifies that the access type and the RAT type combinations available in the NF service consumer for a UE with simultaneous 3GPP and non-3GPP connectivity has changed; and

NOTE 3: The "ACCESS_TYPE_CH" trigger only applies if the "MultipleAccessTypes" feature is supported.

– "SMF_SELECT_CH", i.e. SMF selection information change.

NOTE 4: The "SMF_SELECT_CH" trigger only applies if the "DNNReplacementControl" feature is supported.

B.3.4.3 Encoding of updated policy

Updated policies shall be encoded within the PolicyUpdate as specified in clause 4.2.3.3 with the modifications listed in clauses B.3.4.1, B.3.4.2, and this clause.

– AMF Access and Mobility Policy (see clause B.3.2.2.2) Service Area Restriction for wireline access is encoded as "wlServAreaRes" attribute.

B.3.5 Npcf_AMPolicyControl_Delete Service Operation

B.3.5.1 General

The functionality defined in clause 4.2.5 shall apply.

Annex C (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Cat

Subject/Comment

New

2017-10

TS skeleton of Access and Mobility Policy Control Service specification

0.0.0

2017-10

CT3#92

C3-175324, C3-175338 and C3-17525

0.1.0

2017-12

CT3#93

C3-176355, C3-176354, C3-176237, C3-176238 and C3-176239

0.2.0

2018-01

CT3#94

C3-180033, C3-180195 C3-182307, C3-182308, C3-182309, C3-182442, C3-182311, C3-182312, C3-182313 and C3-182314.

0.3.0

2018-05

CT3#97

C3-183447, C3-183803, C3-183449, C3-183804, C3-183805, C3-183806, C3-183807, C3-183844, C3-183650 and C3-183650

0.5.0

2018-06

CT#80

CP-181025

TS sent to plenary for approval

1.0.0

2018-06

CT#80

CP-181025

TS approved by plenary

15.0.0

2018-09

CT#81

CP-182023

0002

1

B

Trace activation

15.1.0

2018-09

CT#81

CP-182015

0003

3

F

AM Policy Association management during the AMF relocation

15.1.0

2018-09

CT#81

CP-182015

0004

4

F

Completion of Error Codes in OpenAPI file

15.1.0

2018-09

CT#81

CP-182015

0005

1

F

Stateless AMF support updates

15.1.0

2018-09

CT#81

CP-182015

0006

7

F

Removal of editor´s note about additional parameters to further qualify event triggers

15.1.0

2018-09

CT#81

CP-182029

0007

3

F

Service Area Restrictions

15.1.0

2018-09

CT#81

CP-182015

0008

3

F

UE Policies

15.1.0

2018-09

CT#81

CP-182015

0009

1

F

V-PCF procedures

15.1.0

2018-09

CT#81

CP-182015

0010

F

Alignment of resource URIs to resource URI structure

15.1.0

2018-09

CT#81

CP-182015

0011

1

F

Including location information when a location change event is met

15.1.0

2018-09

CT#81

CP-182015

0012

1

F

Description of Structured data types

15.1.0

2018-09

CT#81

CP-182015

0014

1

F

Update of notification

15.1.0

2018-09

CT#81

CP-182015

0015

F

Update the consumer of Npcf_AMPolicyControl service

15.1.0

2018-09

CT#81

CP-182015

0016

1

F

Type of Rfsp attribute in PolicyAssociation data type

15.1.0

2018-09

CT#81

CP-182015

0017

3

F

Encoding to provide only updated parts of policies

15.1.0

2018-09

CT#81

CP-182015

0018

1

F

Termination Causes

15.1.0

2018-09

CT#81

CP-182015

0019

1

F

Update of resource figure

15.1.0

2018-09

CT#81

CP-182015

0020

F

Correction of cardinality of arrays

15.1.0

2018-12

CT#82

CP-183205

0021

1

F

Cleanup of UE policy

15.2.0

2018-12

CT#82

CP-183205

0022

2

F

AM Policy association handling during the AMF relocation

15.2.0

2018-12

CT#82

CP-183205

0023

1

F

Removal of unused abbreviations

15.2.0

2018-12

CT#82

CP-183205

0024

1

F

Correction of HTTP header field with URL of created resource

15.2.0

2018-12

CT#82

CP-183205

0025

F

Type of servAreaRes attribute within Type PolicyAssociation

15.2.0

2018-12

CT#82

CP-183205

0026

F

HTTP Error responses for Notifications

15.2.0

2018-12

CT#82

CP-183205

0028

2

F

Individual AM policy deletion at AMF relocation

15.2.0

2018-12

CT#82

CP-183205

0029

1

F

Correction of the update of Policy Control Request triggers

15.2.0

2018-12

CT#82

CP-183205

0030

F

Default value for apiRoot

15.2.0

2018-12

CT#82

CP-183205

0031

F

API version

15.2.0

2018-12

CT#82

CP-183205

0032

F

ExternalDocs OpenAPI field

15.2.0

2018-12

CT#82

CP-183205

0033

F

Location header field in OpenAPI

15.2.0

2018-12

CT#82

CP-183205

0034

1

F

Security

15.2.0

2018-12

CT#82

CP-183205

0035

F

supported content types

15.2.0

2018-12

CT#82

CP-183205

0036

2

F

HTTP Error responses

15.2.0

2018-12

CT#82

CP-183205

0037

1

F

Correction to the PolicyAssociation data type

15.2.0

2018-12

CT#82

CP-183205

0039

F

Re-use PresenceInfoRm data type

15.2.0

2018-12

CT#82

CP-183205

0040

F

Correction to the PresenceInfo data type

15.2.0

2018-12

CT#82

CP-183205

0041

1

F

Alternate IP address in Npcf_AMPolicyControl_Update

15.2.0

2018-12

CT#82

CP-183205

0042

2

F

Corrections on authorized service area restrictions and RFSP index

15.2.0

2018-12

CT#82

CP-183205

0043

2

F

Corrections on encoding of Service Area Restrictions

15.2.0

2018-12

CT#82

CP-183205

0044

1

F

AM Policy Control support for Emergency Registration

15.2.0

2018-12

CT#82

CP-183205

0045

1

F

Multiple Internal Group identifiers

15.2.0

2018-12

CT#82

CP-183205

0046

2

F

Corrections on Protocol and Application errors

15.2.0

2018-12

CT#82

CP-183205

0047

1

F

Correction of Resource name

15.2.0

2018-12

CT#82

CP-183205

0048

1

F

Removal of pras attribute

15.2.0

2018-12

CT#82

CP-183176

0049

F

Corrections of Cardinality in OpenAPI

15.2.0

2019-03

CT#83

CP-190114

0050

2

F

Correction on PCF-initiated AM Policy association termination

15.3.0

2019-06

CT#84

CP-191187

0053

1

F

Precedence of OpenAPI file

15.4.0

2019-06

CT#84

CP-191187

0057

1

F

Correction to Service Area Restriction and RFSP

15.4.0

2019-06

CT#84

CP-191187

0059

1

F

Copyright Note in YAML file

15.4.0

2019-06

CT#84

CP-191089

0051

3

F

Support of Allowed NSSAI

16.0.0

2019-06

CT#84

CP-191089

0054

1

F

Correction on Policy Association termination

16.0.0

2019-06

CT#84

CP-191101

0055

2

F

API version Update

16.0.0

2019-06

CT#84

CP-191096

0056

1

F

Adding tags to OpenAPI File

16.0.0

2019-06

CT#84

CP-191089

0058

1

F

Race Condition handling

16.0.0

2019-09

CT#85

CP-192178

0061

B

Adding NID as input for policy decisions

16.1.0

2019-09

CT#85

CP-192156

0062

B

Serving PLMN UE AMBR control

16.1.0

2019-09

CT#85

CP-192140

0065

1

A

Correcting the resource URI of AM Policy Associations

16.1.0

2019-09

CT#85

CP-192176

0066

1

B

Support of wireline and wireless access convergence, NFs

16.1.0

2019-09

CT#85

CP-192152

0067

2

B

Support of 5WWC, Policy Control Request Triggers

16.1.0

2019-09

CT#85

CP-192152

0068

B

Annex of wireless and wireline convergence access support

16.1.0

2019-09

CT#85

CP-192152

0070

B

Npcf_AMPolicyControl_Create Service Operation of annex

16.1.0

2019-09

CT#85

CP-192140

0074

2

A

GUAMI included in the Update operation

16.1.0

2019-09

CT#85

CP-192173

0076

F

OpenAPI version update for TS 29.507 Rel-16

16.1.0

2019-12

CT#86

CP-193197

0078

1

F

Data type of the "serviceName" attribute

16.2.0

2019-12

CT#86

CP-193182

0080

A

Correction to PolicyUpdate

16.2.0

2019-12

CT#86

CP-193197

0081

2

B

DNN replacement

16.2.0

2019-12

CT#86

CP-193237

0084

2

B

Line Identifier

16.2.0

2019-12

CT#86

CP-193197

0086

1

B

AM Policy association establishment rejection

16.2.0

2019-12

CT#86

CP-193182

0088

1

A

Correction to Service Area Restrictions description

16.2.0

2019-12

CT#86

CP-193182

0090

1

A

Correction on 307 error, 29.507

16.2.0

2019-12

CT#86

CP-193232

0091

1

B

Support of simultaneous registration in multiple accesses

16.2.0

2019-12

CT#86

CP-193232

0092

2

B

Support of S-NSSAI for non-3GPP access

16.2.0

2019-12

CT#86

CP-193191

0093

1

B

Support of 5WWC, Service Area Restrictions

16.2.0

2019-12

CT#86

CP-193191

0094

1

B

Clarification of PEI format, 29.507

16.2.0

2019-12

CT#86

CP-193226

0095

2

B

HFC node Id in Location information

16.2.0

2019-12

CT#86

CP-193212

0096

F

Update of API version and TS version in OpenAPI file

16.2.0

2020-03

CT#87e

CP-200203

0097

1

B

Policy Control Request Triggers for wireline access

16.3.0

2020-03

CT#87e

CP-200203

0098

1

B

The data type of GlobalLineId

16.3.0

2020-03

CT#87e

CP-200207

0099

F

Corrections related to DNN replacement

16.3.0

2020-03

CT#87e

CP-200207

0100

F

Remove the possibility of SNSSAI change for DNN replacement

16.3.0

2020-03

CT#87e

CP-200207

0101

B

Mapping Of Allowed NSSAI

16.3.0

2020-03

CT#87e

CP-200207

0102

B

Completion of DNN replacement functionality

16.3.0

2020-03

CT#87e

CP-200207

0103

1

B

Completing the description of triggers values applicability in PolicyAssociation and PolicyUpdate types.

16.3.0

2020-03

CT#87e

CP-200216

0105

1

B

Update of OpenAPI version and TS version in externalDocs field

16.3.0

2020-06

CT#88e

CP-201215

0107

1

A

Corrections on Service Area Restriction

16.4.0

2020-06

CT#88e

CP-201215

0109

1

A

Location Header of 307 status code

16.4.0

2020-06

CT#88e

CP-201215

0111

1

A

Notification URI

16.4.0

2020-06

CT#88e

CP-201233

0112

3

B

Correction to the DNN replacement

16.4.0

2020-06

CT#88e

CP-201233

0113

1

B

Enable removing the policy decision

16.4.0

2020-06

CT#88e

CP-201233

0114

1

B

FQDN of alternative AMF

16.4.0

2020-06

CT#88e

CP-201228

0115

F

Removal of MAC address

16.4.0

2020-06

CT#88e

CP-201233

0116

3

D

OpenAPI: Removal of values from description of "triggers" property

16.4.0

2020-06

CT#88e

CP-201228

0117

1

F

Corrections on Annex B

16.4.0

2020-06

CT#88e

CP-201228

0118

1

B

Untrusted FN-RG PEI

16.4.0

2020-06

CT#88e

CP-201244

0119

1

F

Storage of YAML files in ETSI Forge

16.4.0

2020-06

CT#88e

CP-201256

0121

1

F

URI of the Npcf_AMPolicyControl service

16.4.0

2020-06

CT#88e

CP-201261

0122

1

F

Removal of RG_TMBR trigger

16.4.0

2020-06

CT#88e

CP-201228

0123

F

Correction to wireline service area restriction

16.4.0

2020-06

CT#88e

CP-201244

0125

F

Optionality of ProblemDetails

16.4.0

2020-06

CT#88e

CP-201244

0126

1

F

Supported headers, Resource Data type, Operation Name

16.4.0

2020-06

CT#88e

CP-201255

0128

F

Update of OpenAPI version and TS version in externalDocs field

16.4.0

2020-09

CT#89e

CP-202059

0129

1

F

correction to ACCESS_TYPE_CH trigger

16.5.0

2020-09

CT#89e

CP-202079

0130

1

F

report initial presence status for PRA

17.0.0

2020-09

CT#89e

CP-202073

0131

1

B

Successful Response

17.0.0

2020-09

CT#89e

CP-202073

0132

B

Error status code

17.0.0

2020-09

CT#89e

CP-202085

0134

F

Update of OpenAPI version and TS version in externalDocs field

17.0.0

2020-12

CT#90e

CP-203074

0137

2

A

Essential corrections and alignments

17.1.0

2020-12

CT#90e

CP-203139

0139

1

A

Storage of YAML files in 3GPP Forge

17.1.0

2020-12

CT#90e

CP-203143

0141

1

A

Correction to PRA

17.1.0

2020-12

CT#90e

CP-203148

0142

1

F

Report current value in Update for location and accessType related triggers

17.1.0

2020-12

CT#90e

CP-203148

0143

1

B

Adding 200OK response for UpdateNotify

17.1.0

2020-12

CT#90e

CP-203147

0144

F

PolicyAssociationReleaseCause enumeration name

17.1.0

2020-12

CT#90e

CP-203148

0145

F

"400 Bad Request" response on notification

17.1.0

2020-12

CT#90e

CP-203153

0148

F

Update of OpenAPI version and TS version in externalDocs field

17.1.0

2021-03

CT#91e

CP-210191

0152

1

A

Support of stateless NFs

17.2.0

2021-03

CT#91e

CP-210218

0153

F

Adding "description" field for map data types

17.2.0

2021-03

CT#91e

CP-210218

0154

F

OpenAPI reference

17.2.0

2021-03

CT#91e

CP-210226

0155

F

Encoding of Snssai as key of a map

17.2.0

2021-03

CT#91e

CP-210219

0156

F

Clarification on optional HTTP custom headers

17.2.0

2021-03

CT#91e

CP-210227

0158

1

F

Clarification of update operation

17.2.0

2021-03

CT#91e

CP-210221

0159

1

F

Ambiguous concept of NF service consumer terminology

17.2.0

2021-03

CT#91e

CP-210221

0160

1

F

Adding some missing description fields to data type definitions in OpenAPI specification files

17.2.0

2021-03

CT#91e

CP-210191

0162

A

Correction to resource identifiers descriptions used in notifications

17.2.0

2021-03

CT#91e

CP-210227

0163

1

F

Correction to Service Area Restrictions

17.2.0

2021-03

CT#91e

CP-210240

0165

F

Update of OpenAPI version and TS version in externalDocs field

17.2.0

2021-06

CT#92e

CP-211257

0166

2

B

Enabling Dynamic Changes of AM Policies in AMPolicyControl

17.3.0

2021-06

CT#92e

CP-211245

0168

1

B

GLI report

17.3.0

2021-06

CT#92e

CP-211200

0170

1

A

Temporary and Permanent Redirection

17.3.0

2021-06

CT#92e

CP-211104

0171

2

B

Serving PLMN UE Slice-MBR control

17.3.0

2021-06

CT#92e

CP-211265

0173

F

Update of OpenAPI version and TS version in externalDocs field

17.3.0

2021-09

CT#93e

CP-212220

0174

F

Correction of URI structure

17.4.0

2021-09

CT#93e

CP-212225

0175

1

B

Add retrieval of and subscription to AM Influence requests for DCAMP

17.4.0

2021-09

CT#93e

CP-212223

0177

F

Update of OpenAPI version and TS version in externalDocs field

17.4.0

2021-12

CT#94e

CP-213194

0179

1

B

Request of notification of PDU session established/terminated

17.5.0

2021-12

CT#94e

CP-213229

0180

F

Direct access to SNPN

17.5.0

2021-12

CT#94e

CP-213228

0181

3

B

NWDAF instance provisioning to the PCF

17.5.0

2021-12

CT#94e

CP-213194

0182

F

Miscellaneous corrections

17.5.0

2021-12

CT#94e

CP-213243

0183

F

Correction to Update procedure

17.5.0

2021-12

CT#94e

CP-213230

0184

1

F

Some updates to UE-Slice-MBR

17.5.0

2021-12

CT#94e

CP-213230

0185

F

Corrections to UE-Slice-MBR

17.5.0

2021-12

CT#94e

CP-213230

0186

1

B

RFSP Index associated with the Target NSSAI

17.5.0

2021-12

CT#94e

CP-213244

0187

F

Correction of the applicability feature for data type Snssai

17.5.0

2021-12

CT#94e

CP-213244

0188

F

Correction on the condition for location change reporting

17.5.0

2021-12

CT#94e

CP-213244

0190

1

A

Correction to PCF-provisioned triggers

17.5.0

2021-12

CT#94e

CP-213244

0191

B

DNN Replacement implications when URSP rules are provided

17.5.0

2021-12

CT#94e

CP-213244

0192

1

F

Error handling when no AM Policy Association exists

17.5.0

2021-12

CT#94e

CP-213246

0193

F

Update of OpenAPI version and TS version in externalDocs field

17.5.0

2022-03

CT#95e

CP-220197

0194

1

B

Clarification of the dynamic AM policy decision

17.6.0

2022-03

CT#95e

CP-220183

0195

3

B

5G access stratum time distribution support

17.6.0

2022-03

CT#95e

CP-220176

0197

1

A

Alignment of "Application Errors" clause with SBI TS template

17.6.0

2022-03

CT#95e

CP-220196

0198

F

Clarification to Policy Update Notification

17.6.0

2022-03

CT#95e

CP-220195

0199

F

Reporting available allowed NSSAI when ImmediateReport applies

17.6.0

2022-03

CT#95e

CP-220167

0204

1

A

Handling of error responses

17.6.0

2022-03

CT#95e

CP-220197

0206

1

F

Removal of Editor’s Notes

17.6.0

2022-03

CT#95e

CP-220194

0207

F

Update of info and externalDocs fields

17.6.0

2022-06

CT#96

CP-221155

0210

3

F

Formatting of description fields

17.7.0

2022-06

CT#96

CP-221154

0211

F

Using the common data type for FQDN

17.7.0

2022-06

CT#96

CP-221144

0212

F

Determination of error budgets for a given UE

17.7.0

2022-06

CT#96

CP-221145

0213

4

F

Correction to access stratum time distribution

17.7.0

2022-06

CT#96

CP-221139

0214

1

F

remove EN related to Target NSSAI

17.7.0

2022-06

CT#96

CP-221139

0215

2

F

decouple UE-Slice-MBR from Allowed_NSSAI

17.7.0

2022-06

CT#96

CP-221139

0216

F

missing TARGET_NSSAI trigger from the triggers provisioned by PCF

17.7.0

2022-06

CT#96

CP-221129

0217

F

Correction to NWDAF_DATA_CH trigger

17.7.0

2022-06

CT#96

CP-221130

0219

1

F

Mapping between RAT type and frequency and the RFSP Index

17.7.0

2022-06

CT#96

CP-221144

0220

1

F

Correction to AS Time Distribution

17.7.0

2022-06

CT#96

CP-221154

0221

F

Removal of sibling element

17.7.0

2022-06

CT#96

CP-221159

0223

1

F

Correction to the notification of PCF for a PDU session

17.7.0

2022-06

CT#96

CP-221151

0224

F

Update of info and externalDocs fields

17.7.0

2022-09

CT#97e

CP-222123

0225

1

F

Alignment with the SBI template

17.8.0

2022-09

CT#97e

CP-222107

0227

1

F

Correction to UE-Slice-MBR handling for VPLMN S-NSSAI to HPLMN S-NSSAI mapping

17.8.0

2022-12

CT#98e

CP-223201

0229

2

B

Feature awareness during UE mobility with AMF change

18.0.0

2022-12

CT#98e

CP-223191

0230

F

Adding the mandatory error code 502 Bad Gateway

18.0.0

2022-12

CT#98e

CP-223198

0232

1

F

Correction on the handling of RFSP Index authorized by PCF

18.0.0

2022-12

CT#98e

CP-223198

0233

F

Correction to DNN encoding

18.0.0

2022-12

CT#98e

CP-223189

0234

F

Update of info and externalDocs fields

18.0.0