XML based transaction detail records
View Patent ↗The present invention is directed to a method for managing transactions in a telecommunications network. The method includes creating an XML transaction detail file. At least one transaction detail record is stored in the XML transaction detail file in response to a telecommunications transaction. The at least one transaction detail record includes transaction data corresponding to the telecommunications transaction.
1. A method comprising:
creating, by a server device, an extensible markup language (XML) transaction detail file, where the XML transaction detail file is active for a predetermined period of time, where creating the XML transaction detail file includes:
detecting a telecommunications transaction,
analyzing the telecommunications transaction to determine that the telecommunications transaction is conducted between a telecommunications apparatus and a session initiation protocol server (SIP-server), and
generating the XML transaction detail file based on the telecommunications transaction; and
during the predetermined period of time, storing, via the server device, at least one transaction detail record in the XML transaction detail file in response to determining that the telecommunications transaction is conducted between the telecommunications apparatus and the SIP-server, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction,
where the telecommunications apparatus is a proxy server and the SIP-server is a redirect server,
where the XML transaction detail file is a first XML transaction detail file, and
where the redirect server forms a second XML transaction detail file that differs in format from the first XML transaction detail file.
2. The method of claim 1 , further comprising:
closing the XML transaction detail file when the predetermined period of time expires;
creating a third XML transaction detail file, the third XML transaction detail file being active for a second predetermined period of time; and
repeating the steps of closing and creating for a number of times, as directed by a network management system.
3. The method of claim 1 , where the XML transaction detail file comprises:
an XML declaration field, the XML declaration field defining the XML transaction detail file as an XML file;
a server identification field, the server identification field including an internet protocol (IP) address of the server device; and
a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the XML transaction detail file in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
4. The method of claim 1 , where the telecommunications transaction includes a SIP-INVITE message.
5. The method of claim 1 , where the telecommunications transaction includes a SIP-ACK message.
6. The method of claim 1 , where the telecommunications transaction includes a SIP-OPTIONS message.
7. The method of claim 1 , where the telecommunications transaction includes a SIP-BYE message.
8. The method of claim 1 , where the telecommunications transaction includes a SIP-CANCEL message.
9. The method of claim 1 , where the telecommunications transaction includes a SIP-REGISTER message.
10. The method of claim 1 , where the telecommunications transaction includes a billing transaction.
11. The method of claim 1 , where the telecommunications transaction includes a monitoring transaction.
12. The method of claim 1 , where the telecommunications transaction includes a performance measurement transaction.
13. A tangible computer-readable medium having stored thereon computer-executable instructions to cause a processor in a server to perform a method comprising:
creating an extensible markup language (XML) transaction detail file, the XML transaction detail file being active for a predetermined period of time, where creating the XML transaction detail file includes:
detecting a telecommunications transaction,
analyzing the telecommunications transaction to determine that the telecommunications transaction is conducted between a telecommunications apparatus and a session initiation protocol server (SIP-server), and
generating the XML transaction detail file based on to the telecommunications transaction; and
storing, during the predetermined period of time, at least one transaction detail record in the XML transaction detail file in response to determining that the telecommunications transaction is conducted between the telecommunications apparatus and the SIP-server, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction, where, after the predetermined period of time expires, no additional transaction detail record can be added to the XML transaction detail file,
where the telecommunications apparatus is a proxy server and the SIP-server is a redirect server,
where the XML transaction detail file is a first XML transaction detail file, and
where the redirect server forms a second XML transaction detail file that differs in format from the first XML transaction detail file.
14. The computer readable medium of claim 13 , further comprising:
closing the XML transaction detail file when the predetermined period of time expires;
creating a third XML transaction detail file, the third XML transaction detail file being active for a second predetermined period of time; and
repeating the steps of closing and creating for a number of times as directed by a network management system.
15. The computer readable medium of claim 13 , where the XML transaction detail file comprises:
an XML declaration field, the XML declaration field defining the XML transaction detail file as an XML file;
a server identification field, the server identification field including an internet protocol (IP) address of the server; and
a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the XML transaction detail file in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
16. The computer readable medium of claim 13 , where the telecommunications transaction includes a session initiation protocol server (SIP) INVITE message.
17. The computer readable medium of claim 13 , where the telecommunications transaction includes a SIP-ACK message.
18. The computer readable medium of claim 13 , where the telecommunications transaction includes a SIP-OPTIONS message.
19. The computer readable medium of claim 13 , where the telecommunications transaction includes a SIP-BYE message.
20. The computer readable medium of claim 13 , where the telecommunications transaction includes a SIP-CANCEL message.
21. The computer readable medium of claim 13 , where the telecommunications transaction includes a SIP-REGISTER message.
22. The computer readable medium of claim 13 , where the telecommunications transaction includes a billing transaction.
23. The computer readable medium of claim 13 , where the telecommunications transaction includes a monitoring transaction.
24. The computer readable medium of claim 13 , where the telecommunications transaction includes a performance measurement transaction.
25. A device comprising:
a processor to:
create an extensible markup language (XML) transaction detail file, where the XML transaction detail file is active for a predetermined period of time, where creating the XML transaction detail file includes:
detecting a telecommunications transaction,
analyzing the telecommunications transaction to determine that the telecommunications transaction is conducted between a telecommunications apparatus and a session initiation protocol server (SIP-server), and
generating the XML transaction detail file based on the telecommunications transaction; and
store, during the predetermined period of time, at least one transaction detail record in the XML transaction detail file in response to determining that the telecommunications transaction is conducted between the telecommunications apparatus and the SIP-server, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction,
where the telecommunications apparatus is a proxy server and the SIP-server is a redirect server,
where the XML transaction detail file is a first XML transaction detail file, and
where the redirect server forms a second XML transaction detail file that differs in format from the first XML transaction detail file.
26. The device of claim 25 , where the processor is further to:
close the XML transaction detail file when the predetermined period of time expires;
create a third XML transaction detail file, the third XML transaction detail file being active for a second predetermined period of time; and
repeat the closing and the creating for a number of times, as directed by a network management system.
27. The device of claim 25 , where the XML transaction detail file comprises:
an XML declaration field, the XML declaration field defining the XML transaction detail file as an XML file;
a server identification field, the server identification field including an internet protocol (IP) address of the server device; and
a transaction detail section including at least one transaction detail record, the at least one transaction detail record being stored in the XML transaction detail file in response to a telecommunications transaction, the at least one transaction detail record including transaction data corresponding to the telecommunications transaction.
28. The device of claim 25 , where the telecommunications transaction includes a SIP-INVITE message.
29. The device of claim 25 , where the telecommunications transaction includes a SIP-ACK message.
30. The device of claim 25 , where the telecommunications transaction includes a SIP-OPTIONS message.
31. The device of claim 25 , where the telecommunications transaction includes a SIP-BYE message.
32. The device of claim 25 , where the telecommunications transaction includes a SIP-CANCEL message.
33. The device of claim 25 , where the telecommunications transaction includes a SIP-REGISTER message.
34. The device of claim 25 , where the telecommunications transaction includes a billing transaction.
35. The device of claim 25 , where the telecommunications transaction includes a monitoring transaction.
36. The device of claim 25 , where the telecommunications transaction includes a performance measurement transaction.