Network-Indicated Software Version Switching for Communication Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The synchronization of network and communication devices running compliant software versions of a given protocol stack is challenging, limiting the flexibility and compatibility of UE programmability in 3GPP systems, especially when moving between different network areas or operators.
Innovation Solution
A method for managing software versions in communication devices, allowing them to obtain and perform actions on network-indicated software versions, including adding, deleting, modifying, activating, or deactivating these versions, and enabling the communication device to select and transmit acknowledge messages to ensure compatibility and flexibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network and communication devices use fixed software versions specified in 3GPP standards, then compliance and stability are ensured, but flexibility and adaptability to new features are limited
Solution Approach 1:
The patent implements dynamic software version management where the network node can indicate different software versions to different communication devices based on their capabilities and network requirements. This allows the system to adapt software configurations dynamically rather than using fixed versions, resolving the contradiction between maintaining compliance and enabling flexibility for new features.
Solution Approach 2:
The invention changes the software version parameter from a static standard-defined value to a dynamic parameter that can be indicated by the network node. This allows the software version to be adjusted based on device capabilities, network conditions, and feature requirements, thereby achieving both compliance through version control and flexibility through parameter variation.
2Adaptability or versatility
If multiple software versions are stored in communication devices for different networks, then compatibility across networks is improved, but device complexity increases
Solution Approach 1:
The patent implements a self-service mechanism where the network node automatically indicates the appropriate software version to each communication device based on its capabilities and the network's requirements. This eliminates the need for complex manual software version management in devices, as the network dynamically provides the correct version information, thereby maintaining compatibility without significantly increasing device complexity.
Solution Approach 2:
The invention uses feedback mechanisms where communication devices report their capabilities to the network node, which then determines and indicates the appropriate software version. This feedback loop enables automatic adaptation to different networks without requiring devices to pre-store multiple software versions, reducing complexity while maintaining compatibility.
3Reliability
If software versions are updated through standardization processes, then compliance is ensured, but latency occurs when devices move between networks with different protocol stacks
Solution Approach 1:
The patent implements preliminary action by having communication devices obtain software version indications from network nodes before actual network operations begin. This allows devices to pre-configure the appropriate software version based on the target network's characteristics, ensuring compliance without requiring time-consuming updates when moving between networks, thereby reducing switching latency.
Solution Approach 2:
The invention uses the network node as an intermediary that provides software version information to communication devices. This intermediary mechanism enables devices to quickly adapt to different networks by receiving version indications from the network itself, rather than relying on pre-configured versions or time-consuming standardization updates, thus maintaining compliance while reducing latency.
Data Source
Figure 1~2
Figure 3~4
Figure 3A~3C
AI summary
A communication device (600), a network node (700) and methods for managing a software version at the communication device (600). A method (300) performed by the communication device for managing a software version at the communication device comprises obtaining (320) an indication of at least one network indicated SW version from the network node, performing (340) at least one action on at least one of the at least one network indicated SW versions, and wherein at least two software versions are stored in the communication device in relation to a same subscriber identity module. Computer programs and a computer program product are also disclosed.