SDAP Entity Maintenance via Destination Identifiers in 5G V2X

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The 5G communication system's New Radio (NR) vehicle-to-everything (V2X) lacks a specific method for maintaining Service Data Adaptation Protocol (SDAP) entities, which compromises the reliability of communication services.

Innovation Solution

A method for maintaining SDAP entities based on destination identifiers, including sidelink communication IDs, combinations of IDs, and cast types, involving establishment, release, and reconfiguration processes on both transmitting and receiving terminals, ensuring accurate SDAP entity management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If SDAP entity maintenance methods are not established in NR V2X, then the system structure remains simple, but communication service reliability cannot be guaranteed

Engineering Contradiction:
Improvecommunication service reliabilityVSAvoidSDAP entity maintenance complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by using different destination identifier configurations (single destination ID, combination of source and destination IDs, addition of cast type) to adapt SDAP entity maintenance to various V2X communication scenarios. This allows the system to maintain reliability across different communication modes (unicast, groupcast, broadcast) without requiring fundamentally different maintenance mechanisms for each scenario.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent implements universality by designing a unified SDAP entity maintenance method that works across multiple V2X communication scenarios and modes. The same basic maintenance framework (establishment, release, reconfiguration) is applied universally, with flexibility in destination identifier configuration to accommodate different communication types, thereby ensuring reliability without multiplying complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple destination identifier configurations are used for SDAP entity maintenance, then adaptability to different communication scenarios is improved, but the complexity of entity management increases

Engineering Contradiction:
Improveadaptability to communication scenariosVSAvoidentity management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by breaking down the destination identifier into configurable components (source ID, destination ID, cast type) that can be selectively combined based on communication scenario requirements. This modular approach allows the system to adapt to different scenarios by including or excluding specific identifier elements, rather than requiring entirely separate identification mechanisms for each scenario.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamics by making the destination identifier configuration flexible and adaptable to different communication modes. The system can dynamically select appropriate identifier configurations based on whether the communication is unicast, groupcast, or broadcast, allowing high adaptability while maintaining a unified management framework that prevents complexity from escalating.

Inventive Principle:
Principle #15Dynamics

3Reliability

If SDAP entities are maintained without specific maintenance methods, then the implementation process is simpler, but service reliability and communication quality cannot be ensured

Engineering Contradiction:
Improveservice reliabilityVSAvoidimplementation simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies self-service by enabling the SDAP entity maintenance process to automatically manage establishment, release, and reconfiguration based on destination identifier matching. The system self-regulates entity creation and teardown without requiring manual intervention, ensuring service reliability through consistent automated maintenance while keeping the implementation simple through standardized procedures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements feedback mechanisms where the system monitors communication scenarios and automatically adjusts SDAP entity maintenance accordingly. When communication conditions change (e.g., switching between unicast and groupcast modes), the system receives feedback about the new scenario and automatically configures appropriate destination identifiers and maintains corresponding SDAP entities, ensuring reliability without complicating operation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12082040B2Service data adaptation protocol entity maintenance method, transmitting terminal and receiving terminal
Publication Date: 2024.09.03 DATANG MOBILE COMM EQUIP CO LTD
  • US12082040B2 patent drawing
  • US12082040B2 patent drawing
  • US12082040B2 patent drawing

AI summary

The present disclosure provides an SDAP entity maintenance method, a transmitting terminal and a receiving terminal. The SDAP entity maintenance method includes: maintaining the SDAP entity based on a destination identifier; wherein, the destination identifier includes: a sidelink communication destination ID; or the destination identifier includes: a combination of a sidelink communication source ID and the sidelink communication destination ID; or the destination identifier includes: a combination of the sidelink communication destination ID and a cast type; or the destination identifier includes: a combination of the sidelink communication source ID, the sidelink communication destination ID, and the cast type; or the destination identifier includes: a user ID of the transmitting terminal.