5G RRC Inactive Resume Security for SDT and Non-SDT
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the RRC_INACTIVE state of 5G networks, conventional data transmission methods require transitioning to RRC_CONNECTED state for each data transmission, leading to unnecessary power consumption and signaling overhead, especially for small and infrequent data packets, and lack appropriate security configurations for non-SDT procedures.
Innovation Solution
A network device provides separate sets of security configurations for both SDT and non-SDT procedures, allowing terminal devices to perform these operations efficiently and flexibly without transitioning to RRC_IDLE state when SDT fails, using parameters like I-RNTIs and NCCs for secure data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If terminal devices transition to RRC_CONNECTED state for each data transmission in RRC_INACTIVE state, then data transmission can be performed, but power consumption increases and signaling overhead increases
Solution Approach 1:
The patent segments security configurations into two distinct sets: one set for SDT (Small Data Transmission) procedures and another set for non-SDT procedures. This segmentation allows the terminal device to use appropriate security parameters for each transmission type, enabling efficient small data transmissions in RRC_INACTIVE state without requiring full connection resumption, thereby reducing power consumption while maintaining transmission capability
Solution Approach 2:
The network device pre-configures multiple sets of security parameters (including I-RNTIs and NCCs) to the terminal device before the terminal enters RRC_INACTIVE state. This preliminary configuration enables the terminal to perform SDT procedures directly in inactive state without transitioning to connected state, thus avoiding the power consumption and signaling overhead associated with connection resumption
2Reliability
If terminal devices transition to RRC_CONNECTED state for each data transmission, then data transmission can be performed, but signaling overhead increases
Solution Approach 1:
The patent divides security configurations into separate sets for SDT and non-SDT procedures. By segmenting the security parameter sets, the system enables lightweight SDT procedures in RRC_INACTIVE state that require minimal signaling, while reserving full security configurations for non-SDT procedures that may require connection resumption. This reduces overall signaling overhead compared to requiring full connection resumption for all transmissions
Solution Approach 2:
The terminal device is equipped with multiple sets of security parameters that enable it to autonomously perform SDT procedures in RRC_INACTIVE state without needing to transition to RRC_CONNECTED state. This self-service capability allows the terminal to handle small data transmissions independently, reducing the signaling overhead that would otherwise be required for connection management
3Reliability
If separate security configurations are provided for SDT and non-SDT procedures, then secure operations are ensured for both procedures, but device complexity increases
Solution Approach 1:
The patent segments security configurations into distinct sets for SDT and non-SDT procedures, each containing necessary parameters (I-RNTIs, NCCs). While this creates multiple parameter sets, each set is self-contained and purpose-specific, making management straightforward through clear separation of concerns rather than requiring complex integrated security management
Data Source
AI summary
Example embodiments of the present disclosure relate to devices, methods, apparatuses and computer readable storage media of data transmission with security parameters. The method comprises: receiving, from a second device, a first plurality of parameters associated with a connection resume procedure between the first device and the second device; in accordance with a determination that the connection resume procedure is to be performed, transmitting, in the inactive state and to the second device, a request for connection resume, the request comprising one or more of the first plurality of parameters; and performing the connection resume procedure with the second device. In this way, the terminal device is capable of triggering non-SDT procedure when the SDT procedure is ongoing.