Service Logic Execution Recording Parameter in Telecommunication Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telecommunication network architectures face difficulties in activating logging and transmission control protocol (TCP) dumps at nodes involved in call establishment between calling and called User Equipment (UE), especially in cloud computing environments, leading to extensive manual file processing and unnecessary data generation due to the uncertainty of application logic execution locations.
Innovation Solution
A method is introduced where a node in the telecommunication network inserts a service logic execution recording parameter into call establishment messages, triggering each node in the chain to perform recording, allowing for efficient service logic execution recording only for the specific call, thereby reducing unnecessary log and trace file creation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If logging and TCP dump are activated on each node in the telecommunication network, then complete service logic execution recording can be achieved, but massive amounts of surplus data are generated and extensive manual file processing is required
Solution Approach 1:
The patent applies local quality by making logging selective rather than universal. Each node determines whether to perform service logic execution recording based on local evaluation of the call type and node's involvement, rather than all nodes logging all traffic. This selective approach reduces data volume while maintaining recording completeness for relevant calls.
Solution Approach 2:
The patent implements preliminary action by evaluating and determining logging requirements before the call is established. The node assesses whether service logic execution recording is needed for the incoming call and makes this determination in advance, preventing unnecessary logging from the outset rather than filtering data after generation.
2Reliability
If logging is activated on all nodes regardless of call type, then no recording gaps occur, but extensive manual file processing is required and data overhead increases
Solution Approach 1:
The patent enables each node to independently determine its logging status based on local criteria such as call type and service requirements. This decentralized decision-making eliminates recording gaps by ensuring relevant nodes log relevant traffic, while reducing manual processing effort through automated selective logging rather than universal logging requiring manual filtering.
Solution Approach 2:
The system implements self-service by enabling nodes to automatically determine and execute their own logging decisions based on predefined criteria. Each node autonomously evaluates whether to perform service logic execution recording without requiring centralized coordination or manual configuration, reducing operational complexity while maintaining recording reliability.
3Loss of information
If service logic execution recording is performed at every node for every call, then complete traceability is achieved, but data overhead and processing complexity increase significantly
Solution Approach 1:
The patent applies local quality by enabling each node to independently assess its relevance to the call and make localized logging decisions. This ensures that traceability is maintained for all relevant nodes while avoiding unnecessary logging at nodes not involved in service logic execution, thereby reducing processing complexity without sacrificing traceability where needed.
Solution Approach 2:
The patent implements preliminary action by having nodes evaluate and determine their logging participation before processing the call. This advance determination allows the system to establish a streamlined logging plan that ensures complete traceability for involved nodes while avoiding the processing overhead of universal logging across the entire network.
Data Source
AI summary
A method for triggering service logic execution recording of a call between a calling User Equipment, UE, and a called UE in a telecommunication network, wherein said service logic execution recording is to be triggered by nodes in a chain of nodes involved in establishing a call between said calling UE and said called UE, wherein said method comprises the step of inserting in a call establishment message, a service logic execution recording parameter, wherein said parameter indicates that nodes involved in said establishing of said call between said calling UE and said called UE should perform service logic execution recording, wherein said service logic execution recording is any of recording of log files and recording of trace files reflecting signalling between said nodes in said chain.