Commit f8ad4d00 authored by Jan Reimes's avatar Jan Reimes
Browse files

feat(3gpp): enhance documentation for 3GPP skills and processes

- Added sections for MCC and PCG in 3gpp-basics
- Updated related skills in 3gpp-change-request
- Included common mistakes in 3gpp-meetings
- Corrected content type and request body in 3gpp-portal-authentication
- Added official release timeline in 3gpp-releases
- Introduced quick reference table in 3gpp-tdocs
- Updated working group identifiers in 3gpp-working-groups
- Improved cross-reference map in README
parent e3343eb6
Loading
Loading
Loading
Loading
+17 −0
Original line number Diff line number Diff line
@@ -32,6 +32,23 @@ Since 3GPP is not a legal entity, technical administration and infrastructure is
- Portal access for certain resources
- File servers and infrastructure

### MCC (Mobile Competence Centre)

The MCC is the technical support team for 3GPP operations:
- Maintains 3GPP specifications and FTP servers
- Publishes new/revised specs after each TSG round
- Manages the CR database and work item tracking
- Provides meeting document templates
- Target: specs available within 3-4 weeks after TSG plenary

### PCG (Project Coordination Group)

The PCG coordinates the 3GPP partnership:
- Coordinates work across the three TSGs
- Manages relationships with Organizational Partners
- Oversees 3GPP budget and resources
- Strategic planning for 3GPP direction

## Technical Specification Groups (TSGs)

3GPP has three main Technical Specification Groups (TSGs):
+1 −0
Original line number Diff line number Diff line
@@ -7,6 +7,7 @@ related:
  - 3gpp-working-groups
  - 3gpp-tdocs
  - 3gpp-portal-authentication
  - 3gpp-releases
---

# 3GPP Change Requests
+8 −1
Original line number Diff line number Diff line
@@ -139,10 +139,17 @@ The 3GPP Meeting Calendar is available on the 3GU Portal:

## Cross-References

**@3gpp-working-groups** - For understanding WG codes in meeting URLs
- **@3gpp-working-groups** - For understanding WG codes in meeting URLs
- **@3gpp-tdocs** - For accessing TDocs from meetings with files links
- **@3gpp-portal-authentication** - For accessing meeting details pages that require login

## Common Mistakes

1. **Using meeting name for database lookups** - Always use `meeting_id` integer
2. **Parsing date strings directly** - Normalize to ISO format first
3. **Skipping empty Files column** - Don't attempt crawl, skip meeting
4. **Year format changes** - Early years use different conventions

## Best Practices

### When Working with Meeting Data
+2 −2
Original line number Diff line number Diff line
@@ -250,8 +250,8 @@ response = session.get("https://www.3gpp.org/ftp/tsg_ran/WG1_RL1/RAN1_98/Docs/R1

- **URL**: `https://portal.3gpp.org/ngppapp/LoginEOL.ashx`
- **Method**: POST
- **Content-Type**: `application/json`
- **Request Body**: JSON with `username` and `password` fields
- **Content-Type**: `application/x-www-form-urlencoded`
- **Request Body**: Form-encoded with `username` and `password` fields
- **Response**: JSON with `success` boolean

### Session Management
+3 −1
Original line number Diff line number Diff line
@@ -13,6 +13,8 @@ related:

# 3GPP Releases

**Official Release Timeline:** https://www.3gpp.org/specifications-technologies/releases

## Overview

3GPP specifications are published four times a year following quarterly Technical Specification Group (TSG) plenary meetings. Each Release represents a set of frozen technical specifications.
@@ -130,7 +132,7 @@ TS numbers follow pattern: `<series>.<spec>`, where `<series>` is 21, 22, 23, et

## Cross-References

**@3gpp-working-groups** - For understanding which TSGs produce which specs
- **@3gpp-working-groups** - For understanding which TSGs produce which specs
- **@3gpp-specifications** - For spec file format and numbering
- **@3gpp-change-request** - For modifications to specs in releases

Loading