CN108243015B - Call bill information extraction method, call bill server and network management server - Google Patents
Call bill information extraction method, call bill server and network management server Download PDFInfo
- Publication number
- CN108243015B CN108243015B CN201611228416.4A CN201611228416A CN108243015B CN 108243015 B CN108243015 B CN 108243015B CN 201611228416 A CN201611228416 A CN 201611228416A CN 108243015 B CN108243015 B CN 108243015B
- Authority
- CN
- China
- Prior art keywords
- ticket
- byte
- call
- server
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1428—Invoice generation, e.g. customization, lay-out, database processing, algorithms for calculating the bill or formatting invoices as WWW pages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
Abstract
The embodiment of the invention provides a call ticket information extraction method, a call ticket server and a network management server, wherein the method comprises the following steps: receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information; according to the user identification and the ticket query time period, acquiring a target ticket corresponding to the user identification in a preset time period from a ticket server, wherein the preset time period comprises the ticket query time period; and extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server. The ticket server and the network management server execute the method. The ticket information extraction method, the ticket server and the network management server provided by the embodiment of the invention optimize the utilization of manpower, bandwidth and computing resources and improve the efficiency of ticket information query.
Description
Technical Field
The embodiment of the invention relates to the technical field of mobile communication, in particular to a call ticket information extraction method, a call ticket server and a network management server.
Background
With the development of mobile communication technology, more and more people use mobile phones to perform services such as conversation and internet surfing, and therefore, original call ticket data containing a large amount of information can be generated, and therefore, users need to perform operations such as query and download on the original call ticket data.
Fig. 1 is a flow chart of a method for extracting call ticket information in the prior art, as shown in fig. 1, the existing scheme for inquiring original call ticket data of a user is that an engineer judges a general time range through information fed back by a call charge question of the user, downloads all original call ticket files conforming to the time range, adds some field descriptions to the decoded files while decoding by a decoder provided by a device manufacturer, and finally extracts the user information contained in all the files by searching whether each decoded file contains the user information, generates a result, and if the required information is not retrieved, enlarges or modifies the time range and repeats the previous steps. In the process of implementing the embodiment of the present invention, the inventor finds that the above prior art has the following defects: (1) downloading a plurality of ticket files without related information: in the existing scheme, all original call tickets judged within a time range are downloaded and decoded, and files contain information of all users in the time period, so that bandwidth and computing resources are greatly wasted. (2) In decoding, the existing scheme for all the additional redundant information can analyze the information including the user only after decoding by a decoder provided by a manufacturer, and judge whether the file is a required file, and the decoder provided by the manufacturer can add additional description information to all call tickets, each generated text file is as much as 20 MB, so that the efficiency is very low, and the resource waste is increased for subsequent analysis. (3) The current solution is to manually open each file for searching or match the file with a regular expression through a script, the manual searching needs a great deal of labor waste, and the regular expression necessarily requires a query staff to understand the relevant technology, so that the application range is limited. The final analysis result has no uniform structure and is different along with different query conditions set by each query staff. And each query needs to be re-filled. In summary, each query requires a lot of manual intervention, and is inefficient, wasting a lot of resources such as manpower, bandwidth, and computation.
Therefore, how to optimize the utilization of manpower, bandwidth and computing resources and improve the efficiency of ticket information query becomes an urgent problem to be solved.
Disclosure of Invention
Aiming at the problems in the prior art, the embodiment of the invention provides a call ticket information extraction method, a call ticket server and a network management server.
In one aspect, an embodiment of the present invention provides a method for extracting ticket information, including:
receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information;
according to the user identification and the ticket query time period, acquiring a target ticket corresponding to the user identification in a preset time period from a ticket server, wherein the preset time period comprises the ticket query time period;
and extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server.
The embodiment of the invention also provides a ticket information extraction method, which comprises the following steps:
after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server so that the ticket server obtains ticket content information according to the user query information;
receiving the call ticket content information sent by the call ticket server;
and converting the ticket content information into a JSON file, and sending the converted file to a client server.
On the other hand, an embodiment of the present invention provides a ticket server for extracting ticket information, including:
the receiving module is used for receiving user query information sent by the network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information;
the acquisition module is used for acquiring a target call ticket corresponding to the user identifier in a preset time period from a call ticket server according to the user identifier and the call ticket query time period, wherein the preset time period comprises the call ticket query time period;
and the extraction module is used for extracting the call ticket content information in the target call ticket and sending the extracted call ticket content information to the network management server.
The embodiment of the invention provides a network management server for extracting call ticket information, which comprises:
the system comprises a sending module, a receiving module and a processing module, wherein the sending module is used for sending user query information to a call ticket server by a network management server after receiving the user query information sent by a client server so as to enable the call ticket server to obtain call ticket content information according to the user query information;
the call ticket receiving module is used for receiving call ticket content information sent by the call ticket server;
and the conversion module is used for converting the ticket content information into a JSON file and sending the converted file to the client server.
The ticket information extraction method, the ticket server and the network management server provided by the embodiment of the invention optimize the utilization of manpower, bandwidth and computing resources and improve the efficiency of ticket information query.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is a flow chart of a call ticket information extraction method in the prior art;
FIG. 2 is a connection diagram of a call ticket information extraction apparatus according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of a call ticket information extraction method according to an embodiment of the present invention;
FIG. 4 is a data format diagram of ticket information extraction according to the embodiment of the present invention;
FIG. 5 is a ticket file diagram according to an embodiment of the present invention;
FIG. 6 is a schematic flow chart of a ticket information extraction method according to another embodiment of the present invention;
FIG. 7 is a diagram of a ticket file and a decoded file according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a call ticket server structure for extracting call ticket information according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a network management server for extracting call ticket information according to the embodiment of the present invention;
fig. 10 is a schematic structural diagram of a ticket server entity provided in the embodiment of the present invention;
fig. 11 is a schematic structural diagram of a network management server entity according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 2 is a connection diagram of the ticket information extraction device according to the embodiment of the present invention, and as shown in fig. 2, the client server is a front-end HTML server and is responsible for providing a query entry, submitting query information to the network management server, parsing a JSON file returned by the network management server into a form for output, and providing output content customization, such as displaying which fields, sorting, and the like. Excel and HTML files can be optionally exported for downloading by a user.
The network management server is responsible for generating a command according to the submitted query information, issuing the command to the ticket server, retrieving the result, decoding the result, converting the decoded result into JSON (Java Server object notation) and returning the JSON to the client server.
The call ticket server (CG) is responsible for receiving and executing the command of the network management server, the command content mainly comprises the first step of filtering the file according to the query time, the second step of filtering is used for extracting the content information in the original call ticket, and the content information is combined into a single file or a single data stream and fed back to the network management server.
Fig. 3 is a schematic flow diagram of a call ticket information extraction method according to an embodiment of the present invention, and as shown in fig. 3, the call ticket information extraction method according to the embodiment includes the following steps:
s1: receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information.
Specifically, the ticket server receives user query information sent by the network management server, where the user query information includes a user identifier and a ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original ticket information. It should be noted that: the user query information may include a user identifier and a ticket query time, but is not specifically limited, where the user identifier may be a phone Number of a query user or an International Mobile Subscriber identity Number (International Mobile Subscriber identity Number, hereinafter referred to as "IMSI"), the ticket information in the embodiment of the present invention is hexadecimal data, and the network management server converts the user query information into a format identical to that of the ticket information and then sends the format to the ticket server, where the format of the user identifier is identical to that of the ticket information, and may be understood as: the user identifier is also required to be hexadecimal data, and the mobile phone number of the user, such as 13800471507, is decimal and can be converted into hexadecimal, and the specific conversion method is not described any more. The address of the file where the ticket information is located, namely the address of the corresponding binary file, can be obtained by a perl and python method carried by a tool or a system. The query time may be a time period of a specific service, such as a time for querying internet traffic, a time for recording a call, and a time for sending and receiving a short message, which is selected by a user, for example: the user with IMSI number 64002274249544F6 wants to query short message transmission and reception between 10/1/2016 and 11/2016 and 30/2016, and may input the query time as: if the service type is short message from 2016, 1, to 11, 30, then the client server will process the input query message as described in fig. 2, which has been described in the above embodiments and will not be described again.
S2: and acquiring a target call ticket corresponding to the user identifier in a preset time period from a call ticket server according to the user identifier and the call ticket query time period, wherein the preset time period comprises the call ticket query time period.
Specifically, the ticket server obtains a target ticket corresponding to the user identifier within a preset time period from the ticket server according to the user identifier and the ticket query time period, wherein the preset time period comprises the ticket query time period. It should be noted that: the preset time period can be set independently according to actual conditions.
S3: and extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server.
Specifically, the ticket server extracts the ticket content information in the target ticket and sends the extracted ticket content information to the network management server. Fig. 4 is a data format diagram of the extraction of the ticket information according to the embodiment of the present invention, as shown in fig. 4, the data format of the ticket information is a triple (ticket type + ticket length + ticket content), and the whole structure is as shown in fig. 4, where the first byte represents the ticket type, the first 2 bits represent a classification ID, which can be used to identify the classification type of the ticket, and the 3 rd bit represents whether a sub-item is included, which can be defined as: if the value of the 3 rd bit is 1, the child item is included, which can be understood as a nested triple (indicating that the content includes a structure of type + length + content); if the value of the 3 rd bit is 0, no child item is included, which can be understood as a triplet including no nesting. Fig. 5 is a call ticket file diagram according to an embodiment of the present invention, as shown in fig. 5, which illustrates the following: the user identifier IMSI is 64002274249544F6, and the extracted target ticket includes 64002274249544F6, as shown in the fifth row, column 12 to sixth row, column 3 in fig. 5.
The method for extracting the call ticket information optimizes the utilization of manpower, bandwidth and computing resources and improves the efficiency of inquiring the call ticket information.
On the basis of the above embodiment, the extracting of the ticket content information of the target ticket includes:
and taking the first byte from the initial address of the target ticket as the ticket type, converting the first byte into a binary number value, and judging whether the third digit value from the left in the binary number value is 1.
Specifically, the ticket server takes a first byte from the starting address of the target ticket as a ticket type, converts the first byte into a binary number value, and judges whether a third digit value from the left in the binary number value is 1. It should be noted that: according to the source file coding format, the format is analyzed from the starting position of the target call ticket, because the first bytes of each call ticket represent the length of the call ticket, the cut-off address of the target call ticket can be analyzed according to the rule. The cutoff address can be understood as: and extracting the ending byte address of the action execution of the call ticket content information in the target call ticket.
If yes, judging whether the value of a second byte adjacent to the first byte is larger than a preset value.
Specifically, if the call ticket server judges that the number of the second byte adjacent to the first byte is greater than the preset number, the call ticket server judges whether the number of the second byte adjacent to the first byte is greater than the preset number.
If yes, converting the third byte into a decimal value, and acquiring the ending address of the target call ticket according to the decimal value and the position information of the third byte.
Specifically, if the result is judged to be yes, the call ticket server converts the third byte into a decimal value, and obtains the cut-off address of the target call ticket according to the decimal value and the position information of the third byte. As shown in fig. 5, the following is illustrated: the first byte in the target ticket is a0, which can be converted into binary 10100000, the third bit is 1, the next byte 81 is identified as the ticket length with nested sub items, the preset value can be set to 0x80, since the byte 81 is greater than the preset value 0x80, and the digit of the byte 81 is 1, the decimal value corresponding to the next byte D8 of the byte 81 is 216, the value corresponding to the position information of D8 is 3, that is, the total byte number between the start address a0 is 3 (including the start address and the byte address itself), the byte where the ending address of the target ticket is 216+3 ═ 219, that is, the last F6 of the target ticket, when the extraction process is performed to the ending address F6, it is indicated that the target ticket has been extracted. It should be noted that: if the byte bit value greater than the preset value 0x80 is M, the following is given as an example where M is 2: (this is not shown in fig. 5) assuming that the last two bytes of the byte 81 are 07 and a1 in sequence, the binary system corresponding to 07 is 00000111, the binary system corresponding to a1 is 10100001, the combined value is 0000011110100001, the value is converted into a decimal system, and the ending address of the target ticket is determined according to the sum of the decimal value and the value corresponding to the position information of a 1.
Otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte and then according to the sequence as the first content information.
Specifically, if not, the ticket server extracts the byte number which is the same as the decimal value from the second byte according to the sequence as the first content information according to the decimal value. (this is not addressed in fig. 5) is additionally illustrated as follows: if the second byte adjacent to the first byte is 03, the value is smaller than the preset call ticket length value of 0x80, the second byte is 03, the decimal is 3, and 3 bytes are extracted from the third byte behind the second byte according to the sequence to be used as the first content information.
And repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
Specifically, the ticket server repeats the above steps as the ticket type for the first byte after the extracted byte number, and sequentially extracts the nth content information, where N is a natural number greater than 1. As shown in fig. 5, the bytes marked with no straight underline and no curved underline are the 1 st to nth content information, the bytes marked with straight underline are the call ticket type, and the bytes marked with curved underline are the call ticket length.
The method for extracting the ticket information provided by the embodiment of the invention ensures the improvement of the ticket information query efficiency by extracting the ticket content information in the ticket server.
On the basis of the above embodiment, after the step of converting the first byte into a binary value and determining whether the third digit value from the left in the binary value is 1, the method further includes:
if the third digit is 0, the second byte is converted into a decimal value, and according to the decimal value, the byte number which is the same as the decimal value is extracted from the back of the second byte according to the sequence to be used as the first content information.
Specifically, if the call ticket server judges that the third digit is 0, the second byte is converted into a decimal value, and according to the decimal value, the byte number which is the same as the decimal value is extracted from the back of the second byte according to the sequence and is used as the first content information. Referring to the byte 86 in the seventh column of the first row of fig. 5, the byte is converted into 10000110 in decimal, the third bit is 0 and contains no sub-entries, and the byte in the eighth column of the first row is 03 and represents the first content information of the target call ticket, i.e. 10, 04, 12, which is extracted 3 bytes from the byte according to the ordering.
The method for extracting the ticket information provided by the embodiment of the invention improves the ticket information query efficiency by extracting the ticket content information from the ticket server.
On the basis of the above embodiment, after the step of converting the first byte into a binary value, the method further includes:
and judging whether the last five digits of the binary numerical value are all 1.
Specifically, the ticket server determines whether the last five digits of the binary number are all 1.
If not, executing the step of judging whether the third digit value from the left in the binary number value is 1.
Specifically, the call ticket server determines whether the binary number is 1, and executes the step of determining whether the third digit from the left in the binary number is 1.
If so, converting a third byte after the first byte into a decimal value, extracting the byte number which is the same as the decimal value from the rear of the third byte according to the sequence as the first content information according to the decimal value, and separating the first byte and the third byte by one byte.
Specifically, the call ticket server judges that the third byte after the first byte is converted into a decimal value, extracts the byte number which is the same as the decimal value from the back of the third byte according to the sequence according to the decimal value and uses the byte number as the first content information, and the interval between the first byte and the third byte is one byte. As shown in fig. 5, the eleventh column 9F of the seventh row is converted into 10011111, the adjacent two bytes are 37 and 02 in turn, and the same number of bytes as the decimal value is extracted from the byte 02 in the order as the first content information. Reference may be made to the above embodiments, which are not described in detail.
The method for extracting the ticket information provided by the embodiment of the invention further ensures the improvement of the ticket information query efficiency by extracting the ticket content information from the ticket server.
On the basis of the above embodiment, the step of obtaining, in the ticket server, the target ticket corresponding to the user identifier within a preset time period according to the user identifier and the ticket query time period includes:
the call ticket server screens all call tickets of the user identification according to the user identification; and
according to the call ticket query time period, screening target call tickets which accord with a preset time period from all the screened call tickets;
specifically, the ticket server screens out all tickets of the user identifier according to the user identifier, which can refer to the above embodiment and is not described again, and
according to the call ticket query time period, screening target call tickets meeting a preset time period from all the screened call tickets, wherein the following steps are required: the command in the ticket server for executing the filtering of the ticket by date may be ls, but is not limited specifically.
Alternatively, the first and second electrodes may be,
the call ticket server screens all call tickets of the user identification according to the user identification; and
the call ticket server sends a call ticket screening request to a network management server, wherein the call ticket screening request comprises: a preset time period to be screened and all call tickets are screened;
and the ticket server receives a target ticket screened by the network management server, wherein the target ticket is a ticket screened from all tickets by the network management server according to the ticket screening request.
Specifically, the ticket server screens out all tickets of the user identifier according to the user identifier, which can refer to the above embodiment and is not described again and described in detail
The call ticket server sends a call ticket screening request to a network management server, wherein the call ticket screening request comprises: a preset time period to be screened and all call tickets are screened;
and the ticket server receives a target ticket screened by the network management server, wherein the target ticket is a ticket screened from all tickets by the network management server according to the ticket screening request. It should be noted that: and if the lss command is not found by the self-check of the ticket server, sending a ticket screening request to the network management server, and the network management server can screen all tickets within the preset time period in a form of a file list returned by program analysis, so as to obtain the screened target tickets and send the target tickets to the ticket server.
The method for extracting the ticket information further ensures the smooth operation of ticket information extraction through the target ticket screened from the ticket server or the network management server.
On the basis of the above embodiment, after extracting the content information of the target ticket, the method further includes:
and combining the content information extracted from the target call tickets into a target total call ticket, and sending the target total call ticket to the network management server.
Specifically, the ticket server combines the content information extracted from the plurality of target tickets into a target total ticket, and sends the target total ticket to the network management server. It should be noted that: the extracted call ticket content information in the multiple target call tickets can be combined and sent to the network management server in the form of a single file or a single data stream, and the network management server decodes the target total call ticket and then corresponds the data to the codes in the target call ticket.
The method for extracting the call ticket information provided by the embodiment of the invention combines the extracted content information into a target total call ticket, realizes the optimized utilization of manpower, bandwidth and computing resources, and improves the efficiency of call ticket information query.
Fig. 6 is a schematic flow diagram of a method for extracting ticket information according to another embodiment of the present invention, and as shown in fig. 6, the embodiment of the present invention further provides a method for extracting ticket information, which is characterized in that the method includes the following steps:
s10: after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server, so that the ticket server obtains ticket content information according to the user query information.
Specifically, after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server, so that the ticket server obtains ticket content information according to the user query information. The ticket server obtains the ticket content information according to the user query information, which can refer to the description in the above embodiment and is not described here again.
S20: and receiving the call ticket content information sent by the call ticket server.
Specifically, the network management server receives the call ticket content information sent by the call ticket server. It should be noted that the ticket content information here is the processed ticket content information after the method steps of the above embodiment have been executed.
S30: and converting the ticket content information into a JSON file, and sending the converted file to a client server.
Specifically, fig. 7 is a ticket file and a decoded file diagram according to the embodiment of the present invention, and as shown in fig. 7, the network management server converts the ticket content information into a JSON file and sends the converted file to the client server. The client server can analyze the JSON file returned by the network management server into table output, and simultaneously provide output content customization, and optionally export Excel and HTML files for users to download.
The ticket method for extracting the ticket information provided by the embodiment of the invention realizes the optimized utilization of manpower, bandwidth and computing resources and improves the efficiency of ticket information query.
Fig. 8 is a schematic diagram of a ticket server structure for ticket information extraction according to an embodiment of the present invention, and as shown in fig. 8, this embodiment provides a ticket server for ticket information extraction, including a receiving module 1, an obtaining module 2, and an extracting module 3, where:
the receiving module 1 is used for receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a ticket query time period corresponding to the user identifier, the format of the user identifier is the same as that of the original ticket information, the obtaining module 2 is used for obtaining a target ticket corresponding to the user identifier in a preset time period from the ticket server according to the user identifier and the ticket query time period, the preset time period comprises the ticket query time period, and the extracting module 3 is used for extracting ticket content information in the target ticket and sending the extracted ticket content information to the network management server.
Specifically, the receiving module 1 is configured to receive user query information sent by a network management server, where the user query information includes a user identifier and a ticket query time period corresponding to the user identifier, a format of the user identifier is the same as a format of the original ticket information, the receiving module 1 sends the user query information to the obtaining module 2, the obtaining module 2 is configured to obtain a target ticket corresponding to the user identifier in a preset time period in a ticket server according to the user identifier and the ticket query time period, the preset time period includes the ticket query time period, the obtaining module 2 sends the target ticket to the extracting module 3, and the extracting module 3 is configured to extract ticket content information in the target ticket and send the extracted ticket content information to the network management server.
The ticket server for extracting the ticket information optimizes the utilization of manpower, bandwidth and computing resources and improves the efficiency of ticket information query.
On the basis of the foregoing embodiment, the extraction module 3 is specifically configured to:
taking a first byte counted from the starting address of the target ticket as a ticket type, converting the first byte into a binary numerical value, and judging whether a third numerical value from the left in the binary numerical value is 1 or not; if yes, judging whether the numerical value of a second byte adjacent to the first byte is larger than a preset numerical value or not; if so, converting the third byte into a decimal numerical value, and acquiring a cut-off address of the target call ticket according to the decimal numerical value and the position information of the third byte; otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte according to the sequence to be used as first content information; and repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
Specifically, the extraction module 3 is specifically configured to: taking a first byte counted from the starting address of the target ticket as a ticket type, converting the first byte into a binary numerical value, and judging whether a third numerical value from the left in the binary numerical value is 1 or not; if yes, judging whether the numerical value of a second byte adjacent to the first byte is larger than a preset numerical value or not; if so, converting the third byte into a decimal numerical value, and acquiring a cut-off address of the target call ticket according to the decimal numerical value and the position information of the third byte; otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte according to the sequence to be used as first content information; and repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
The ticket information extracting ticket server provided by the embodiment of the invention ensures the improvement of the ticket information query efficiency by extracting the ticket content information in the ticket server.
The ticket server for extracting ticket information provided in this embodiment may be specifically configured to execute the processing flows of the foregoing method embodiments, and its functions are not described herein again, and reference may be made to the detailed description of the foregoing method embodiments.
Fig. 9 is a schematic structural diagram of a network management server for extracting ticket information according to an embodiment of the present invention, and as shown in fig. 9, the embodiment provides a network management server for extracting ticket information, which includes a sending module 4, a ticket receiving module 5, and a converting module 6, where:
the system comprises a sending module 4, a ticket receiving module 5 and a converting module 6, wherein the sending module is used for sending the user query information to a ticket server after the network management server receives the user query information sent by a client server, so that the ticket server obtains ticket content information according to the user query information, the ticket receiving module 5 is used for receiving the ticket content information sent by the ticket server, and the converting module 6 is used for converting the ticket content information into a JSON file and sending the converted file to the client server.
Specifically, the sending module 4 is configured to send, by the network management server, the user query information to the ticket server after receiving the user query information sent by the client server, so that the ticket server obtains ticket content information according to the user query information, the sending module 4 sends the user query information to the ticket receiving module 5, the ticket receiving module 5 is configured to receive the ticket content information sent by the ticket server, the ticket receiving module 5 sends the ticket content information to the converting module 6, and the converting module 6 is configured to convert the ticket content information into a JSON file and send the converted file to the client server.
The network management server for extracting the ticket information optimizes the utilization of manpower, bandwidth and computing resources and improves the efficiency of ticket information query.
The network management server for extracting the ticket information provided in this embodiment may be specifically configured to execute the processing flows of the foregoing method embodiments, and the functions of the network management server are not described herein again, and refer to the detailed description of the foregoing method embodiments.
Fig. 10 is a schematic structural diagram of a ticket server entity provided in the embodiment of the present invention, and as shown in fig. 10, the ticket server includes: a processor (processor)1001, a memory (memory)1002, and a bus 1003;
the processor 1001 and the memory 1002 complete communication with each other through a bus 1003;
the processor 1001 is configured to call the program instructions in the memory 1002 to execute the methods provided by the above-mentioned method embodiments, for example, including: receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information; according to the user identification and the ticket query time period, acquiring a target ticket corresponding to the user identification in a preset time period from a ticket server, wherein the preset time period comprises the ticket query time period; and extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server.
The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, comprising: receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information; according to the user identification and the ticket query time period, acquiring a target ticket corresponding to the user identification in a preset time period from a ticket server, wherein the preset time period comprises the ticket query time period; and extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server.
The present embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the methods provided by the above method embodiments, for example, including: receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of the original call ticket information; according to the user identification and the ticket query time period, acquiring a target ticket corresponding to the user identification in a preset time period from a ticket server, wherein the preset time period comprises the ticket query time period; and extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server.
Fig. 11 is a schematic structural diagram of a network management server entity provided in an embodiment of the present invention, and as shown in fig. 11, the ticket server includes: a processor (processor)1101, a memory (memory)1102, and a bus 1103;
the processor 1101 and the memory 1102 complete communication with each other through a bus 1103;
the processor 1101 is configured to call the program instructions in the memory 1102 to perform the methods provided by the above-mentioned method embodiments, for example, including: after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server so that the ticket server obtains ticket content information according to the user query information; receiving the call ticket content information sent by the call ticket server; and converting the ticket content information into a JSON file, and sending the converted file to a client server.
The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, comprising: after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server so that the ticket server obtains ticket content information according to the user query information; receiving the call ticket content information sent by the call ticket server; and converting the ticket content information into a JSON file, and sending the converted file to a client server.
The present embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the methods provided by the above method embodiments, for example, including: after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server so that the ticket server obtains ticket content information according to the user query information; receiving the call ticket content information sent by the call ticket server; and converting the ticket content information into a JSON file, and sending the converted file to a client server.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
The above-described embodiments of the ticket server and the network management server are merely illustrative, where the units described as the separate components may or may not be physically separated, and the components displayed as the units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the embodiments of the present invention, and are not limited thereto; although embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (8)
1. A method for extracting call ticket information is characterized by comprising the following steps:
receiving user query information sent by a network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of original call ticket information;
according to the user identification and the ticket query time period, acquiring a target ticket corresponding to the user identification in a preset time period from a ticket server, wherein the preset time period comprises the ticket query time period;
extracting the call ticket content information in the target call ticket, and sending the extracted call ticket content information to the network management server;
the extracting of the call ticket content information of the target call ticket comprises the following steps:
taking a first byte counted from the starting address of the target ticket as a ticket type, converting the first byte into a binary numerical value, and judging whether a third numerical value from the left in the binary numerical value is 1 or not;
if yes, judging whether the numerical value of a second byte adjacent to the first byte is larger than a preset numerical value or not;
if so, converting the third byte into a decimal numerical value, and acquiring a cut-off address of the target call ticket according to the decimal numerical value and the position information of the third byte;
otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte according to the sequence to be used as first content information;
and repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
2. The method of claim 1, wherein after the step of converting the first byte into a binary value and determining whether a value of a third bit from the left of the binary value is 1, the method further comprises:
if the third digit is 0, the second byte is converted into a decimal value, and according to the decimal value, the byte number which is the same as the decimal value is extracted from the back of the second byte according to the sequence to be used as the first content information.
3. The method of claim 1, wherein after the step of converting the first byte to a binary value, the method further comprises:
judging whether the last five digits of the binary numerical value are all 1;
if not, executing the step of judging whether the third digit value from the left in the binary number value is 1,
if so, converting a third byte after the first byte into a decimal value, extracting the byte number which is the same as the decimal value from the rear of the third byte according to the sequence as the first content information according to the decimal value, and separating the first byte and the third byte by one byte.
4. The method according to any one of claims 1 to 3, wherein the step of obtaining a target call ticket corresponding to the user identifier within a preset time period in a call ticket server according to the user identifier and the call ticket query time period comprises:
the call ticket server screens all call tickets of the user identification according to the user identification; and
according to the call ticket query time period, screening target call tickets which accord with a preset time period from all the screened call tickets;
alternatively, the first and second electrodes may be,
the call ticket server screens all call tickets of the user identification according to the user identification; and
the call ticket server sends a call ticket screening request to a network management server, wherein the call ticket screening request comprises: a preset time period to be screened and all call tickets are screened;
and the ticket server receives a target ticket screened by the network management server, wherein the target ticket is a ticket screened from all tickets by the network management server according to the ticket screening request.
5. The method of claim 1, wherein after extracting the content information of the target ticket, the method further comprises:
and combining the content information extracted from the target call tickets into a target total call ticket, and sending the target total call ticket to the network management server.
6. A method for extracting call ticket information is characterized in that the method comprises the following steps:
after receiving user query information sent by a client server, a network management server sends the user query information to a ticket server so that the ticket server obtains ticket content information according to the user query information;
receiving the call ticket content information sent by the call ticket server;
converting the ticket content information into a JSON file, and sending the converted file to a client server;
the ticket content information is extracted by the ticket server based on the following steps, and comprises the following steps:
taking a first byte counted from the starting address of the target ticket as a ticket type, converting the first byte into a binary number value, and judging whether a third digit value from the left in the binary number value is 1;
if yes, judging whether the numerical value of a second byte adjacent to the first byte is larger than a preset numerical value or not;
if so, converting the third byte into a decimal numerical value, and acquiring a cut-off address of the target call ticket according to the decimal numerical value and the position information of the third byte;
otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte according to the sequence to be used as first content information;
and repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
7. A call ticket information extraction call ticket server is characterized by comprising:
the receiving module is used for receiving user query information sent by the network management server, wherein the user query information comprises a user identifier and a call ticket query time period corresponding to the user identifier, and the format of the user identifier is the same as that of original call ticket information;
the acquisition module is used for acquiring a target call ticket corresponding to the user identifier in a preset time period from a call ticket server according to the user identifier and the call ticket query time period, wherein the preset time period comprises the call ticket query time period;
the extraction module is used for extracting the call ticket content information in the target call ticket and sending the extracted call ticket content information to the network management server;
the extraction module is specifically configured to:
taking a first byte counted from the starting address of the target ticket as a ticket type, converting the first byte into a binary numerical value, and judging whether a third numerical value from the left in the binary numerical value is 1 or not;
if yes, judging whether the numerical value of a second byte adjacent to the first byte is larger than a preset numerical value or not;
if so, converting the third byte into a decimal numerical value, and acquiring a cut-off address of the target call ticket according to the decimal numerical value and the position information of the third byte;
otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte according to the sequence to be used as first content information;
and repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
8. A call ticket information extraction network management server is characterized by comprising:
the system comprises a sending module, a call ticket server and a processing module, wherein the sending module is used for sending user query information to the call ticket server after the network management server receives the user query information sent by a client server so as to enable the call ticket server to obtain call ticket content information according to the user query information;
the call ticket receiving module is used for receiving call ticket content information sent by the call ticket server;
the conversion module is used for converting the ticket content information into a JSON file and sending the converted file to a client server;
the ticket content information is extracted by the ticket server based on the following steps, and is specifically used for:
taking a first byte counted from the starting address of the target ticket as a ticket type, converting the first byte into a binary number value, and judging whether a third digit value from the left in the binary number value is 1;
if yes, judging whether the numerical value of a second byte adjacent to the first byte is larger than a preset numerical value or not;
if so, converting the third byte into a decimal numerical value, and acquiring a cut-off address of the target call ticket according to the decimal numerical value and the position information of the third byte;
otherwise, according to the decimal value, extracting the byte number which is the same as the decimal value from the second byte according to the sequence to be used as first content information;
and repeating the steps as the ticket type for the first byte after the extracted byte number, and sequentially extracting the Nth content information, wherein N is a natural number greater than 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611228416.4A CN108243015B (en) | 2016-12-27 | 2016-12-27 | Call bill information extraction method, call bill server and network management server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611228416.4A CN108243015B (en) | 2016-12-27 | 2016-12-27 | Call bill information extraction method, call bill server and network management server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108243015A CN108243015A (en) | 2018-07-03 |
| CN108243015B true CN108243015B (en) | 2021-07-02 |
Family
ID=62702741
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611228416.4A Active CN108243015B (en) | 2016-12-27 | 2016-12-27 | Call bill information extraction method, call bill server and network management server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108243015B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328760B (en) * | 2020-11-03 | 2024-01-30 | 中国联合网络通信集团有限公司 | Service providing method, device and system |
| CN116346923A (en) * | 2021-12-22 | 2023-06-27 | 中兴通讯股份有限公司 | Service processing method, system and computer readable storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2693349A1 (en) * | 2012-08-03 | 2014-02-05 | Tata Consultancy Services Limited | A system and method for massive call data storage and retrieval |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101009728A (en) * | 2007-01-09 | 2007-08-01 | 华为技术有限公司 | CDR server, match server, CDR inquiry system and CDR inquiry method |
| CN104780519A (en) * | 2014-01-10 | 2015-07-15 | 中国移动通信集团四川有限公司 | Phone bill query method and system |
-
2016
- 2016-12-27 CN CN201611228416.4A patent/CN108243015B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2693349A1 (en) * | 2012-08-03 | 2014-02-05 | Tata Consultancy Services Limited | A system and method for massive call data storage and retrieval |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108243015A (en) | 2018-07-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108345692B (en) | Automatic question answering method and system | |
| CN111431926B (en) | Data association analysis method, system, equipment and readable storage medium | |
| US10218775B2 (en) | Methods for servicing web service requests using parallel agile web services and devices thereof | |
| CN109582289B (en) | Method, system, storage medium and processor for processing rule flow in rule engine | |
| CN111629081A (en) | Internet protocol IP address data processing method and device and electronic equipment | |
| CN109254854A (en) | Asynchronous invoking method, computer installation and storage medium | |
| CN108243015B (en) | Call bill information extraction method, call bill server and network management server | |
| CN105630767A (en) | Text similarity comparison method and device | |
| CN111679886A (en) | Heterogeneous computing resource scheduling method, system, electronic device and storage medium | |
| CN105991722B (en) | Downloader recommendation method, application server, terminal and system | |
| CN109753424B (en) | AB test method and device | |
| CN115456781A (en) | Market data processing method and device, electronic equipment and storage medium | |
| CN106997394B (en) | A kind of data random ordering arrival processing method and system | |
| CN105786941B (en) | Information mining method and device | |
| CN113535749A (en) | Query statement generation method and device | |
| CN110554877A (en) | JSON data analysis method, device, equipment and storage medium | |
| CN110855555A (en) | Mail sending method, device, equipment and computer readable storage medium | |
| CN110505289B (en) | File downloading method and device, computer readable medium and wireless communication equipment | |
| CN111914548A (en) | Intelligent document filling method and system and related equipment | |
| CN111046145A (en) | Interactive intention path mining method and device | |
| CN110784553A (en) | Message encapsulation method, device and domain name resolution system | |
| CN115495658A (en) | Data processing method and device | |
| CN107508705B (en) | Resource tree construction method of HTTP element and computing equipment | |
| CN109657184B (en) | Rich text processing method, rich text processing device, server and computer readable medium | |
| CN115048277A (en) | Log analysis method, device, equipment and storage medium for data audit |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |