№ files_lp_4_process_1_35758
File format: docx Character count: 14069 File size: 131 KB
Aligns TS 33.501 with TS 29.510 to resolve mismatched PLMN ID claims in service access authorization during roaming.
Year: 2026
Region / City: Goa, India
Topic: Roaming Service Access Authorization
Document Type: Change Request
Organization: 3GPP
Author: Ericsson, Nokia, BSI (DE)
Target Audience: 3GPP technical groups, telecom industry professionals
Period of Validity: From Release-19 onward
Approval Date: 2026-02-12
Revision History: CR-Form-v12.1, Revision 1
Category: F (correction)
Release: Rel-19
Price: 8 / 10 USD
The file will be delivered to the email address provided at checkout within 12 hours.

Don’t have cryptocurrency yet?

You can still complete your purchase in a few minutes:
  1. Buy Crypto in a trusted app (Coinbase, Kraken, Cash App or any similar service).
  2. In the app, tap Send.
  3. Select network, paste our wallet address.
  4. Send the exact amount shown above.
After sending, paste your TXID (transaction ID) and your email to receive the download link. Need help? Contact support and we’ll guide you step by step.

The final amount may vary slightly depending on the payment method.
The file will be sent to the email address provided at checkout within 24 hours.
The product description is provided for reference. Actual content and formatting may differ slightly.
3GPP TS 33.501 Change Request 2214: Correction of Misalignment with TS 29.510 Regarding PLMN ID Access Token Claims in Roaming (Release 20)
Year: 2026
Date: 2026-02-02
Meeting: 3GPP TSG-SA3 Meeting #126
Location: Goa, India
Specification: 3GPP TS 33.501
Related specification: 3GPP TS 29.510
Change Request: CR 2214
Revision: -
Current version: 20.0.0
Release: Rel-20
Category: F (correction)
Work item code: TEI20
Source organizations: Ericsson; Nokia; BSI (DE)
Working Group: SA3
Technical domain: 5G security architecture and authorization
Affected clauses: 13.4.1.2.2; 14.3.2
Network components involved: Core Network; NF Service Consumer; NF Service Producer; NRF; SEPP
Protocol context: OAuth2.0 access token handling in roaming scenarios
Purpose of change: Alignment of PLMN ID handling in access token claims with TS 29.510
Potential impact if not approved: Interoperability issues between specifications
CASE OF KULYKOV AND OTHERS v. UKRAINE (Applications nos. 5114/09 and 17 others – see appended list)
Year: 2017
Region / City: Strasbourg
Subject: Human Rights
Document Type: Judgment
Institution: European Court of Human Rights
Author: Angelika Nußberger, Erik Møse, Ganna Yudkivska, André Potocki, Yonko Grozev, Carlo Ranzoni, Mārtiņš Mits, Milan Blaško
Target Audience: Legal professionals, human rights advocates, academics
Period of validity: Final
Approval Date: 19 January 2017
Amendment Date: 19 April 2017
THIRD SECTION DECISION Application no. 21891/12 Igor Ivanovich BOYKO against Russia and 8 other applications (see list appended)
Year: 2019
Region / City: Strasbourg
Theme: Human Rights
Document Type: Court Decision
Organization / Institution: European Court of Human Rights
Author: Alena Poláčková, Dmitry Dedov, Jolien Schukking
Target Audience: Legal professionals, human rights scholars
Period of Validity: 5 March 2019
Approval Date: 28 March 2019
Amendment Date: None
3GPP TS 33.501 Change Request 2214: Correction of Misalignment with TS 29.510 Regarding PLMN ID Access Token Claims in Roaming (Release 20)
Year: 2026
Date: 2026-02-02
Meeting: 3GPP TSG-SA3 Meeting #126
Location: Goa, India
Specification: 3GPP TS 33.501
Related specification: 3GPP TS 29.510
Change Request: CR 2214
Revision: -
Current version: 20.0.0
Release: Rel-20
Category: F (correction)
Work item code: TEI20
Source organizations: Ericsson; Nokia; BSI (DE)
Working Group: SA3
Technical domain: 5G security architecture and authorization
Affected clauses: 13.4.1.2.2; 14.3.2
Network components involved: Core Network; NF Service Consumer; NF Service Producer; NRF; SEPP
Protocol context: OAuth2.0 access token handling in roaming scenarios
Purpose of change: Alignment of PLMN ID handling in access token claims with TS 29.510
Potential impact if not approved: Interoperability issues between specifications
Topics: 29510 appended misalignment