メニュー
TS and TR numbering, spec file formats, FTP directory structure, and accessing 3GPP specifications. Use when working with 3GPP specification numbering, finding spec files, or understanding spec directory organization.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Comprehensive Python development skill covering coding standards, CLI development, linting, testing, debugging, refactoring, code review, auditing, documentation, project planning, and bulk operations. Use when writing, reviewing, refactoring, debugging, or documenting Python code; configuring linters; setting up CLI tools; planning features; performing code audits; checking Python antipatterns, forbidden methods, or bad style; or handling bulk operations (10+ files) that benefit from batch workflows instead of per-file iteration.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
ITU-T-specific contribution document drafting: template structure, header table fields, style-name mapping, equation conventions, and batch workflows. Use when preparing or editing ITU-T contribution .docx files (C-series or TD-series). Delegates formatting rules to sdo-docx-formatting and officecli operations to sdo-docx-operations.
Cross-platform operational guardrails and deterministic helper scripts for officecli OOXML edits on .docx files. Use when editing .docx with officecli raw-set, fixing tab run issues, inserting bookmarks or field codes (SEQ/REF), validating XPath targeting, or preventing destructive raw-set mistakes. Applies across all SDOs -- concrete style names provided by the per-SDO drafting skill.
General 3GPP organization overview, partnerships, scope, and fundamental concepts. Use when working with 3GPP data structures, understanding 3GPP hierarchy, or needing context about 3GPP as an organization.
Change Request procedure, workflow, status tracking, CR database, and step-by-step instructions. Use when working with 3GPP Change Requests to modify specifications, understanding CR lifecycle, or querying CR status.
| name | 3gpp-specifications |
| description | TS and TR numbering, spec file formats, FTP directory structure, and accessing 3GPP specifications. Use when working with 3GPP specification numbering, finding spec files, or understanding spec directory organization. |
3GPP specifications are the primary deliverables of the 3GPP partnership. They include:
21.456 (Series + Spec number)TR 21.900 (TR + number)Two-digit series number + Three-digit spec number:
<series>.<spec>
Examples:
Each two-digit series corresponds to a specific technical domain:
| Series | Domain | Responsible TSG |
|---|---|---|
| 21 | Requirements | SA |
| 22 | Service aspects ("stage 1") | SA1 |
| 23 | Technical realization ("stage 2") | SA2 |
| 24 | Signalling protocols ("stage 3") - UE to network | CT1 |
| 25 | Radio aspects (UTRA/UTRAN) | RAN |
| 26 | CODECs | SA4 |
| 27 | Data services | CT1 |
| 28 | Signalling protocols ("stage 3") - RSS-CN | CT4 |
| 29 | Signalling protocols ("stage 3") - Intra-CN | CT3/CT4 |
| 31 | UE terminal conformance (USIM) | CT6 |
| 32 | OAM&P and Charging | SA5 |
| 33 | Security | SA3 |
| 34 | UE and USIM test specifications | CT6/RAN5 |
| 35 | Security algorithms | SA3 |
| 36 | LTE (Evolved UTRA/E-UTRAN) | RAN |
| 37 | Multiple radio access technology aspects | RAN |
| 38 | 5G NR (New Radio) | RAN |
Key patterns:
.doc.ziphttps://www.3gpp.org/ftp/Specs/<YYYY>-<MM>/
TSG Round Examples:
https://www.3gpp.org/ftp/Specs/2025-12/https://www.3gpp.org/ftp/Specs/2025-12/https://www.3gpp.org/ftp/Specs/2025-12/SpecslistexTSG/TSG110.htmEach TSG round directory contains:
When a new spec is created:
Example:
Series 21: 21.001, 21.002, 21.003, ..., 21.456
Series 22: 22.001, 22.002, 22.003, ..., 22.101
Spec files follow 3GPP naming conventions:
Example:
21.456.doc - TS 21.456 Word™ document21.456.zip - Zip™ archive containing Word™ files21.456_003.doc - Version 003 revisionEach Working Group is responsible for specifications in their domain:
Specs are assigned to Working Groups based on their scope:
The MCC aims to make all specs available following TSG round as soon as possible.
Example Revision Numbering:
Spec version numbers follow the format: <series>.<version>
Examples:
21.456.0 - Initial version of spec 21.45621.456.1 - First revision of spec 21.45622.101.3 - Third revision of spec 22.101Change Requests are tracked in a database accessible via:
3GPP Work Items define features to be developed. New specs and CRs are linked to Work Items.
3gpp-releases - For release structure and freeze concepts3gpp-working-groups - For understanding which WG owns which specs3gpp-change-request - For modification process via CRs3gpp-meetings - For understanding when specs are approved (at TSG plenaries)import requests
from bs4 import BeautifulSoup
# FTP directory for Release 18
base_url = "https://www.3gpp.org/ftp/Specs/2018-12/"
response = requests.get(base_url)
soup = BeautifulSoup(response.text, "html.parser")
# Parse all spec files
for link in soup.find_all("a", href=True):
href = link.get("href")
if href.endswith(".doc") or href.endswith(".zip"):
print(f"Found spec: {href}")
import re
def parse_spec_number(filename: str) -> tuple:
"""Parse spec number from filename."""
# Extract series number and spec number
match = re.match(r"(\d{2})(\d{3})(\.doc|\.zip)", filename)
if not match:
return (None, None)
return (match.group(1), match.group(2))
For parallel releases (e.g., Rel-4/5/6), 3GPP creates delta directories containing only changed specs.
Purpose: Reduce duplicate storage and make it easy to identify what's new in each release.