Summary of 3GPP Technical Document S4-260116
Document Information
- CR Number: 0014
- Specification: TS 26.113 v19.1.0
- Work Item: iRTCW-TEI (Interactive Real-Time Communication Work - Technical Enhancement and Improvement)
- Category: F (Correction)
- Release: Rel-19
Main Technical Contribution
Problem Statement
The JSON schema for the SWAP (Service and Workflow Adaptation Protocol) protocol contains inconsistencies that make it invalid and misaligned with the specification text. These issues could hinder proper implementation and interoperability.
Technical Changes to Clause 13.2.4.6 (JSON Schema)
The CR proposes a complete restructuring of the SWAP message JSON schema with the following key modifications:
1. Schema Structure Simplification
- Removed: Complex nested
definitions section that defined matching_criteria_object as a reusable component
- Removed: Separate
payload property with complex oneOf structures
- Changed: Flattened schema structure by moving payload definitions directly under the root
oneOf
2. Matching Criteria Handling
- Before: Matching criteria was defined as a reusable object reference with
type and value properties, allowing both predefined enums and custom strings via anyOf
- After: Simplified to a direct string enum without the flexible
anyOf structure
- Impact: More restrictive but clearer definition - only allows predefined matching criteria types (ipv4, ipv6, fqdn, service, user, eas, app, location, qos, processing)
3. Message Payload Structure
- Before: Payloads were nested under a
payload property with detailed descriptions for each message type (register, response, connect, accept, reject, application)
- After: Payloads are defined directly at the root level using
oneOf, removing the intermediate payload wrapper
- Removed: Explicit descriptions for each payload variant
- Removed: Array structure for
matching_criteria in connect payload
4. Required Fields
- Changed:
"source" in required fields changed to "source_id" to match the actual property name defined in the schema
5. Data Type Corrections
- Reject/Error Payload: Changed
request field type from "integer" to "number" for more flexibility
6. Extensions Object
- Before: Defined with type
"object" and description
- After: Simplified to empty object
{}
Impact Assessment
Positive Impacts
- Corrects schema validation errors
- Aligns JSON schema with specification requirements
- Ensures proper interoperability between implementations
Potential Concerns
- The simplified matching criteria structure is less flexible (removed
anyOf allowing custom strings)
- Removal of array support for matching criteria in connect payload may limit functionality
- Loss of descriptive metadata for payload variants may reduce schema self-documentation
Affected Specifications
- Core Specification: TS 26.113 (SWAP protocol)
- Other Specifications: None directly affected
- Test Specifications: Not affected
- O&M Specifications: Not affected