Service Identifier for Message Proxy in 5G Service-Based Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G service-based architecture communications networks, existing service discovery methods face challenges with message proxy involvement, where important information sent by the client during the service discovery process may be lost, and load balancing among service instances is complex, raising trust issues and requiring granular access control.
Innovation Solution
Assigning a unique service identifier to the service discovery request that links it to multiple service-related parameters, allowing these parameters to be conveyed and stored, enabling subsequent requests to determine capable processing entities based on these parameters, thereby ensuring accurate service instance selection and load balancing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a message proxy is introduced in the service-based architecture, then common functions such as service discovery, access control, and load balancing can be centralized, but important information sent by the client during service discovery may be lost
Solution Approach 1:
The service identifier acts as an intermediary mechanism that bridges the client's service discovery parameters and the message proxy's processing. The identifier preserves the link between original parameters and subsequent requests, ensuring information is not lost while enabling centralized processing.
Solution Approach 2:
The service identifier extracts and isolates the critical linking information from the complex service discovery parameter set. By separating this essential identifier from the full parameter set, the system can maintain the connection without requiring the message proxy to process all original parameters, thus preventing information loss.
2Reliability
If load balancing is implemented among multiple service instances, then service reliability improves, but the complexity of determining capable processing entities increases
Solution Approach 1:
The service identifier serves as a mediator that carries service-related parameters from the client through the message proxy to the service instances. This intermediary mechanism simplifies the load balancing decision process by providing a structured reference to capable processing entities without requiring complex real-time analysis.
Solution Approach 2:
The system performs preliminary service discovery and parameter collection before the actual service request. By determining capable processing entities in advance and storing service-related parameters associated with the service identifier, the system reduces the complexity of real-time load balancing decisions.
3Reliability
If access control is performed at the service registry level, then security is improved, but granular control over specific service parameters becomes difficult
Solution Approach 1:
The access control mechanism is segmented from the general service registry level to the specific service instance level. The service identifier enables fine-grained control by associating parameters with specific service instances, allowing granular access control while maintaining security through centralized registry operations.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Inclusion of a message proxy in a service based architecture A method for handling a service discovery request for a service provided by a service based architecture communications network, the method comprising at an entity (100, 200) handling the service discovery request, comprising the steps of: -receiving (S31, S51) the service discovery request from a client requesting a service in the service based architecture communications network in which the service is provided by a plurality of different processing entities (31, 32), the received service discovery request comprising a plurality of service related parameters, -assigning (S32, S52) a service identifier to the service discovery request, the identifier linking the received service discovery request to the plurality of service related parameters, - storing the plurality of service related parameters with the service identifier at the entity handling the service discovery request, -transmitting (S33, S56) a service discovery response to the client in response to the received service discovery request, the service discovery response comprising the service identifier, -receiving (S36, S57) a subsequent request related to the service, the subsequent request comprising the service identifier, -determining the plurality of service related parameters for the subsequent request based on the received service identifier present in the subsequent request and the stored plurality of service related parameters,and -determining (S37, S58) a list of processing entities (31, 32) capable of handling the subsequent request related to the service based on the determined plurality of service related parameters.