Parameter-Driven Value Conversion Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current client/server architectures lack client-side control over data value representations, especially in mobile business scenarios where clients are used 'out of the box' and consumers have no control over client implementation, necessitating a shift in control over data values during service calls.
Innovation Solution
A parameter-driven value conversion framework is introduced, where conversion IDs and field names are passed as tuples from the client to the server, allowing the conversion handler to look up and execute conversion routines from the conversion registry, enabling data field conversions between internal server-side and external client-side representations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If data values are exposed in a fixed internal representation on the server side, then the server implementation is simplified and consistent, but the clients cannot be configured differently for client side value representation and must implement their own conversion logic
Solution Approach 1:
The patent introduces a conversion service as an intermediary component between the server and clients. This service receives conversion requests containing source and target format specifications, performs the appropriate conversions using registered converters, and returns the converted values. This mediator approach allows the server to maintain a fixed internal representation while providing adaptable client-side representations through the conversion service.
Solution Approach 2:
The patent implements a parameter-driven conversion system where conversion requests include parameters specifying the source format, target format, and the data value to be converted. The conversion service uses these parameters to dynamically select and execute the appropriate conversion routine. This parameter-based approach enables flexible client-side value representations without changing the server's fixed internal structure.
2Adaptability or versatility
If conversion logic is implemented in the client to adjust data representation, then client side control over data values is achieved, but the clients cannot be used 'out of the box' and require custom implementation control
Solution Approach 1:
The conversion service acts as a centralized intermediary that handles all data format conversions. Clients can use the service by simply calling its conversion methods with their desired format parameters, eliminating the need for custom client implementation. The service registry and converter infrastructure provide the adaptability, while the unified interface provides ease of use.
Solution Approach 2:
The conversion service is designed as a universal component that can handle multiple conversion scenarios through a single interface. It supports different data types, formats, and conversion strategies through a unified mechanism. This multi-functionality allows any client to use the service for any conversion need without requiring client-specific implementation.
3Adaptability or versatility
If a conversion framework with registry and lookup mechanisms is implemented, then client side control and flexibility are enabled, but the system complexity increases with conversion handlers, registries, and protocol handlers
Solution Approach 1:
The conversion framework implements self-service mechanisms where the conversion service automatically manages the converter registry, performs lookups based on format specifications, and selects appropriate conversion routines without manual intervention. The system self-configures and self-manages the complexity internally, presenting a simple interface to clients.
Solution Approach 2:
The conversion framework is segmented into distinct functional components: the protocol handler that receives requests, the conversion handler that processes conversions, the registry that stores converters, and the actual converter implementations. This segmentation organizes the complexity into manageable, loosely-coupled modules that can be developed and maintained independently.
Data Source
AI summary
A system and method for parameter-driven value conversion in a client/server architecture is presented. A request is received from a client computer for an application service. The request includes a parameter defining a data field for a conversion and a conversion ID that specifies the conversion. A lookup is performed of a converter in a conversion registry based on the conversion ID, and the converter is then called to perform the conversion of the data field defined by the parameter in the request, to generate a converted data field. Finally, the converted data field is returned to the protocol handler.