WO2017181808A1

WO2017181808A1 - Network element data playback method and apparatus

Info

Publication number: WO2017181808A1
Application number: PCT/CN2017/077838
Authority: WO
Inventors: 熊广
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-04-20
Filing date: 2017-03-23
Publication date: 2017-10-26
Also published as: CN107306199A; CN107306199B

Abstract

A network element data playback method. The method comprises: obtaining network element data to be played back, the network element data comprising multiple call detail record messages; decoding the network element data to obtain a history timestamp and a network element number of each call detail record message; preprocessing each call detail record message, the preprocessing comprising replacing the history timestamp of each call detail record message by a current timestamp and replacing the network element number of each call detail record message by a target network element number; encoding each preprocessed call detail record message; determining an actual rate of the network element data according to the history timestamp or the current timestamp of each call detail record message; and sending the multiple encoded call detail record message according to the determined actual rate.

Description

Method and device for playing back network data

Technical field

The present disclosure relates to the field of communication technologies, for example, to a method and apparatus for network element data playback.

Background technique

In the process of debugging and testing the communication system, the playback of network element data plays an important role. The data playback of the communication network element may be that the collected network element data is not modified to be sent to the designated server at a fixed rate to implement playback of the network element data. This will result in unrealistic data after playback, which imposes great limitations on flexibility, cannot guarantee the true sequence and delay of signaling, and cannot reflect the real business processes and usage habits of users within a certain period of time. There are methods to calculate the interval between each message when playing back a small amount of signaling data, and send the true rate at intervals. In this way, the signaling data for small data volume is still controllable. In the case of massive data (hundreds of thousands of messages per second, it is necessary to calculate the interval of sending hundreds of thousands of times), the transmission performance is completely unsatisfactory. .

Summary of the invention

The present disclosure provides a method and apparatus for playing back network data, which can implement accurate playback of network element data.

The embodiment provides a method for playing back network data. The method may include: acquiring network element data to be played back, where the network element data may include multiple message messages. Decoding the network element data, and obtaining a historical timestamp and a network element number of each CDR message. Pre-processing each of the CDR messages, the pre-processing may include replacing a historical timestamp of each CDR message with a current timestamp, and replacing the network element number of each CDR message The target network element number. Each pre-processed message is encoded. Determining an actual rate of the network element data according to the historical timestamp or the current timestamp of each of the CDR messages. The encoded plurality of CDR messages are sent according to the determined actual rate.

The embodiment further provides an apparatus for playing back network data, and the apparatus may include: acquiring a module a block, configured to acquire network element data to be played back, the network element data includes a plurality of CDR messages, and a codec module configured to decode the network element data, obtain a historical timestamp and a network element of each CDR message a pre-processing module, configured to pre-process each of the CDR messages, the pre-processing may include replacing a historical timestamp of each of the CDR messages with a current timestamp, and The network element number of the CDR message is replaced with the target network element number; the codec module may be further configured to encode the pre-processed CDR message; and the rate control module is set to be based on the historical time of each CDR message. The stamp or the current timestamp determines an actual rate of the network element data; and the sending module is configured to send the encoded bill message according to the determined actual rate.

The embodiment further provides a computer readable storage medium storing computer executable instructions for performing the above method for playing back network data.

The embodiment also provides a server including one or more processors, a memory, and one or more programs, the one or more programs being stored in the memory, when executed by one or more processors, The method for performing the above-mentioned network element data playback.

The embodiment further provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer a method of causing the computer to perform the above-described network element data playback.

The method and the device for playing back the network element data can solve the problem that the authenticity of the playback network element data is not high by replacing the historical time stamp of each CDR message in the decoded network element data with the current time stamp. By replacing the network element number of each CDR message with the target network element number, you can configure a suitable NE number for each CDR message according to different test environments. The actual rate of the network element data is determined according to the historical timestamp or the current timestamp of each CDR message, and the encoded CDR message is sent according to the determined actual rate, thereby realizing the real-time real-time message throughput in the live network environment. To ensure the true sequence and delay of signaling. The process of playing back the network element data may not be restricted by the complex network element hardware and software equipment, so that the problem that the playback data is not authentic and does not match the real data characteristics of the existing network can be solved.

DRAWINGS

FIG. 1 is a flow chart of a method for playing back network data in an embodiment.

2 is a flow chart of a method for pre-processing each CDR message in one embodiment.

3 is a flow chart of a method for decoding network element data in an embodiment.

FIG. 4 is a structural block diagram of an apparatus for playing back network data in an embodiment.

Figure 5 is a block diagram showing the structure of a preprocessing module in one embodiment.

FIG. 6 is a structural block diagram of an apparatus for playing back network data in another embodiment.

FIG. 7 is a schematic diagram of a general hardware structure of a server according to an embodiment.

detailed description

As shown in FIG. 1, in one embodiment, a method for playing back network data is proposed, and the method may include the following steps.

In step 102, the network element data to be played back is obtained, and the network element data may include multiple CDR messages.

Optionally, the network element data refers to data transmitted between network elements, and may include control plane data (signaling data), and may also include media plane user data. Network element data is often massive, and the storage form is a text file. The network element data can be saved in the form of a single bill, so the obtained network element data can include multiple bill messages. Optionally, the content of the network element data may be hexadecimal. Optionally, receiving the request for playing back the network element data, searching the path parameter corresponding to the network element data in the configuration file, and acquiring the network element data to be played back according to the path parameter. The network element data can be pre-stored in the database.

In step 104, the network element data is decoded, and the historical timestamp and the network element number of each CDR message are obtained.

Optionally, the network element data may be saved in the form of a single CDR, and decoding the obtained network element data is to decode each CDR message, and parse out the service time of each CDR message. Information such as the historical timestamp, NE type, and NE number of the service. The network element number may be an identity (ID) of the network element.

Optionally, the decoding rule follows the 3rd Generation Partnership Project (3GPP) standard protocol, and the decoded object may be each CDR message, and each CDR message may be composed of two parts: a message header and a message body. Then the decoded content corresponds to two blocks: decoding of the message header and decoding of the message body. The network element number and the network element type can be decoded from the message header, and all the information is decoded from the message body. A field related to the time when the service occurs, the time field may include: a report time field, a start time field, and an end time field. A time field can be arbitrarily selected as the above historical time stamp. Optionally, the historical timestamp of the CDR message may be a reporting time field.

In step 106, the pre-processing of each CDR message is performed. The pre-processing may include replacing the historical timestamp of each CDR message with the current timestamp, and replacing the network element number of each CDR message with the target network element. number.

Optionally, in order to improve the authenticity of the data playback of the network element, the historical timestamp of each CDR message is replaced with the current timestamp, and the network of each CDR message is used in order to adapt the network element number in the test environment. Replace the element number with the target NE number in the test environment.

Optionally, replacing the historical timestamp of each CDR message with the current timestamp may include: determining a time interval between a historical timestamp of the first CDR message and a current time, and adding a historical timestamp of each CDR message. This time interval is made such that the historical timestamp becomes the current timestamp.

Optionally, replacing the network element number of each CDR message with the target network element number in the test environment may include: finding a location of the network element number in the CDR message, and then according to the network element type of each CDR message The network element number is uniquely matched to the target network element number in the test environment, and the network element number is replaced by the target network element number.

In step 108, the pre-processed CDR message is encoded.

Optionally, after the CDR message is pre-processed, the processed CDR information needs to be re-encoded, and the coding rule can follow the 3GPP standard protocol, and adopts a common Type-Length-Value (TLV) The encoding format is encoded. The length of the encoded data is variable, and the data length and value can be determined by type. Optionally, the coding adopts the original coding mode of the CDR message, that is, the coding mode before decoding. The encoding may include a message header encoding the CDR message, a message body, and a packet of the message header and the message body. Optionally, after the dialog message is encoded, the decoded message is loaded into the sending queue for subsequent transmission.

In step 110, the actual rate of the network element data is determined according to the historical timestamp or current timestamp of each CDR message.

Optionally, each CDR message can have two timestamps: a historical timestamp and a current timestamp. Count The actual time rate can be selected as the historical timestamp or the current timestamp. It should be noted that the timestamps must be consistent, that is, all the CDR messages are selected with historical timestamps, or all CDR messages are selected with the current timestamp.

Optionally, determining the actual rate of the network element data may include: retrieving the preset time based on the historical timestamp or the current timestamp of the first bill message, and then calculating the number of the bill message in the preset time, The calculated CDR message value is used as the actual rate in the preset time.

Optionally, the timer is started, and the preset time is set to 1 second. The CDR message in the sending queue is scanned every second, and the historical timestamp or the current timestamp of the first CDR message in the sending queue is used as a reference, and the recursion is 1 second. The number of the CDRs in the sending queue is determined within one second, and the number of CDR messages per second is obtained in real time, and the actual rate of the network data is obtained as the number of CDRs per second.

Optionally, the network element data includes multiple CDR messages. During the playback of the network element data, the multiple CDR messages in the sending queue are divided into multiple intervals according to a preset time, and each interval may include different numbers. Order message. The actual rate of the corresponding network element data of each interval is successively recursively calculated. For example, in the first interval, calculating the number of the CDR message in the preset time, and determining that the actual rate of sending the network element data in the first interval is equal to the number of CDR messages divided by the preset time; similarly, determining the second interval The actual rate at which network element data is sent. The actual rate of sending network element data in all intervals is calculated by recursing in turn. And sending the CDR message in the first interval to the target server in batches at the actual rate of the first interval; and sending the CDR message in the second interval to the target server in batches at the actual rate of sending the network element data in the second interval, until All CDR messages in all intervals are sent to the target server.

In step 112, the encoded plurality of CDR messages are transmitted according to the determined actual rate.

Optionally, the encoded multiple CDR messages are sent to the designated server in an original manner according to the actual rate calculated in real time. The original mode here may refer to the original transmission protocol of the network element data, that is, the transmission protocol of the network element data in the current network, such as the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). Optionally, the encoded multiple CDR messages are loaded into the sending queue, and then multiple CDR messages in the sending queue are sent according to the actual rate determined in real time, and the sent CDR message is moved out of the sending queue. During the sending process, it is detected in real time whether the sending queue is empty. When it is detected that the sending queue is not empty, then Continue to send until all the CDR messages have been sent. When it is detected that the sending queue is empty, it indicates that all the CDR messages in the sending queue have been sent, and then the sending is stopped.

Optionally, the problem that the playback network element data is not authentic is solved by replacing the historical timestamp of each CDR message in the decoded network element data with the current timestamp. By replacing the network element number of each CDR message with the target network element number, you can flexibly configure the appropriate NE number for each CDR message according to different test environments. The actual rate of the network element data is determined according to the historical timestamp or the current timestamp of each CDR message, and the encoded CDR message is sent according to the determined actual rate, thereby realizing the real-time real-time message throughput in the live network environment. To ensure the true sequence and delay of signaling. The process of playing back the network element data may be free from the limitation of the hardware and software devices of the complex network element, and may solve the problem that the playback data is not authentic and does not match the real data characteristics of the existing network.

As shown in FIG. 2, the pre-processing of each CDR message is performed by replacing the historical timestamp of each CDR message with the current timestamp, and replacing the network element number of each CDR message with the target network element. The steps of the number may include steps 106a-106b.

In step 106a, the time interval between the historical timestamp of the first bill message and the current time is calculated, and the historical time stamp of each bill message plus the time interval is converted into the current time stamp.

Optionally, each CDR message may have a historical timestamp, and the historical timestamp may refer to the original time when the CDR message service occurs. To improve the authenticity of the network element data playback, the original historical time is required. Replace the stamp with the current timestamp. Optionally, the replacing process may include: finding a historical timestamp of the first CDR message, calculating a historical timestamp of the first CDR message and a current time interval, and adding a historical timestamp of all the CDR messages. The time interval, that is, the original historical time stamp can be converted to the current time stamp.

In step 106b, the network element type of each CDR message is obtained, and the network element number of each CDR message is replaced with the target network element number according to the network element type.

Optionally, each CDR message is decoded, and the network element type of the CDR message is parsed from the header portion of each CDR message, and each message is obtained according to the obtained network element type and the network element number. Replace the NE number of the single message with the target NE number in the test environment.

Optionally, the step of calculating the actual rate of the network element data according to the historical timestamp or the current timestamp of each CDR may include: recursing the preset based on the historical timestamp or the current timestamp of the first CDR message. Time, calculate the number of CDR messages in the preset time, so that the actual rate of the network element data is equal to the number of CDR messages divided by the preset time.

Optionally, in order to restore the real sequence and delay of the real-time message throughput guarantee signaling in the live network environment, the CDR message needs to be sent to the target server according to the actual rate of the network element data. The actual rate is calculated by recursing the preset time (for example, 1 second) based on the historical timestamp or the current timestamp of the first CDR, provided that the delay and order of the existing CDR messages are consistent. Then, the number of the CDRs in the preset time is calculated, and the actual rate of the network data in the preset time is calculated to be equal to the number of CDRs divided by the preset time. The number of CDR messages in the preset time may be sent to the corresponding target server in batches (one time).

Optionally, the step of decoding the network element data and obtaining the historical timestamp and the network element number of each CDR message may include: decoding each obtained CDR message, where the CDR message may include a message header and a message body. . The network element number of the CDR message can be parsed from the message header; the historical timestamp of the CDR message can be parsed from the message body.

Optionally, the CDR message may include a message header and a message body. The decoding network element data may be a message header and a message body of each CDR message, and the network element number of the CDR message is parsed from the message header. The historical timestamp of the CDR message is parsed from the message body. Optionally, the network element type of the CDR message may also be parsed from the message header.

Optionally, after the step of encoding the pre-processed CDR message, the network element data playback method of the embodiment may further include: adding the encoded multiple CDR messages to the sending queue.

Optionally, after the step of transmitting the encoded multiple CDR messages according to the determined actual rate, the method may further include: moving the sent CDR message out of the sending queue.

Optionally, after the pre-processed CDR message is encoded, the encoded multiple CDR messages are loaded into the sending queue, and then the CDR message in the sending queue is scanned, and the first CDR is used. The historical timestamp or current timestamp of the message is used as a reference, and the preset time (for example, 1 second) is recursed, and the number of all the CDRs in the preset time is obtained according to the timestamp of the CDR message, and the message is sent in the queue. Preset All the CDRs in the time are sent in batches. After the transmission is complete, the sent CDRs are sent out of the sending queue to detect whether the sending queue is empty. When it is detected that the sending queue is not empty, the CDR message continues to be sent. Until all the CDR messages are sent, when it is detected that the send queue is empty, the CDR message is stopped.

As shown in FIG. 3, the flow of the method for playing back the network element data may include steps 301-308.

In step 301, the network element data to be played back is obtained, and the network element data may include multiple message messages.

In step 302, the network element data is decoded, and the historical timestamp and the network element number of each CDR message are obtained.

In step 303, the pre-processing of each CDR message is performed. The pre-processing may include replacing the historical timestamp of each CDR message with the current timestamp, and replacing the network element number of each CDR message with the target network element. number.

In step 304, the pre-processed CDR message is encoded, and the encoded CDR message is added to the sending queue.

In step 305, the actual rate of the network element data is determined according to the historical timestamp or current timestamp of each CDR message.

In step 306, the encoded CDR message is transmitted according to the determined actual rate.

In step 307, the sent bill message is moved out of the send queue.

In step 308, it is determined whether the sending queue is empty. When it is determined that the sending queue is empty, the sending of the bill message is ended. When it is determined that the sending queue is not empty, then steps 306-308 are continued.

As shown in FIG. 4, the embodiment further provides an apparatus for playing back network data. The apparatus may include an obtaining module 402, a codec module 404, a preprocessing module 406, a rate control module 408, and a sending module 410.

The obtaining module 402 is configured to obtain network element data to be played back, and the network element data includes multiple bill messages.

The codec module 404 is configured to decode the network element data, and obtain a historical timestamp and a network element number of each CDR message.

The pre-processing module 406 is configured to pre-process each CDR message, and the pre-processing includes replacing the historical timestamp of each CDR message with the current timestamp, and replacing the network element number of each CDR message with the target. Network element number.

The codec module 404 can also be configured to encode each pre-processed message.

The rate control module 408 is configured to determine an actual rate of the network element data according to a historical timestamp or a current timestamp of each CDR message;

The sending module 410 is configured to send the encoded multiple CDR messages according to the determined actual rate.

As shown in FIG. 5, optionally, the pre-processing module 406 may include: a timestamp conversion sub-module 406a, configured to calculate a time interval between a historical timestamp of the first bill message and a current time, and each message of the bill is The historical timestamp plus the time interval is converted to the current timestamp of each CDR message.

The network element replacement sub-module 406b is configured to obtain the network element type of each CDR message, and replace the network element number of each CDR message with the target network element number according to the network element type.

Optionally, the rate control module 408 may be configured to recurs the preset time based on the historical timestamp or the current timestamp of the first CDR message, and calculate the number of CDRs in the preset time to obtain the preset time. The actual rate of network element data is equal to the number of CDR messages divided by the preset time.

Optionally, the codec module is further configured to: decode each CDR message in the obtained network element data, where the CDR message may include a message header and a message body; and the network that parses the CDR message from the message header. The meta number; the historical timestamp of the CDR message parsed from the message body.

As shown in FIG. 6, the apparatus for playing back the network element data may further include: an adding module 412, configured to add the encoded multiple CDR messages to the sending queue. The moveout module 414 is configured to move the sent CDR message out of the send queue.

A person skilled in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, such as the present invention. In an embodiment, the program can be stored in a storage medium of the computer system and executed by at least one processor in the computer system to implement a flow of an embodiment of a method including playback of any of the network element data as described above. The storage medium may be a non-transitory storage medium, including a magnetic disk, an optical disk, a read-only memory (ROM), or a random A memory (Random Access Memory, RAM) or the like may also be a transient storage medium.

A plurality of technical features of the above-described embodiments may be combined in any combination. For the sake of brevity of description, all possible combinations of the plurality of technical features in the above embodiments are not described, however, as long as the combination of these technical features does not exist. Contradictions should be considered as the scope of this manual.

The embodiment further provides a computer readable storage medium storing computer executable instructions for performing the method for playing back any of the above network element data.

As shown in FIG. 7, it is a schematic diagram of a hardware structure of a server provided in this embodiment. As shown in FIG. 7, the server includes:

A processor 510 and a memory 520; may further include a communication interface 530 and a bus 540.

The processor 510, the memory 520, and the communication interface 530 can complete communication with each other through the bus 540. Communication interface 530 can be used for information transfer. The processor 510 can call the logic instructions in the memory 820 to perform the method of any of the network element data playback in the above embodiments.

In addition, the logic instructions in the memory 520 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in this embodiment. The foregoing storage medium may be a non-transitory storage medium or a transitory storage medium.

Industrial applicability

The present disclosure provides a method and apparatus for playing back network data, which can limit the process of playing back network data by hardware and software devices of complex network elements, and can solve the problem that the playback data is not authentic and does not match the real data characteristics of the live network. problem.

Claims

A method for playing back network data data, which is applied to a server, including:

Obtaining network element data to be played back, where the network element data includes multiple bill messages;

Decoding the network element data, and obtaining a historical timestamp and a network element number of each CDR message;

Pre-processing each of the CDR messages, the pre-processing includes replacing a historical timestamp of each CDR message with a current timestamp, and replacing the network element number of each CDR message with Target network element number;

Encoding each pre-processed message;

Determining an actual rate of the network element data according to a historical timestamp or a current timestamp of each of the CDR messages;

The encoded plurality of CDR messages are sent according to the determined actual rate.
The method of claim 1, wherein the pre-processing each of the bill messages comprises:

Calculating a historical timestamp of the first CDR message and a current time interval, and converting the historical timestamp of each CDR message to the time interval to be converted into a current timestamp of each CDR message;

The network element type of each CDR message is obtained, and the network element number of each CDR message is replaced with the target network element number according to the network element type.
The method according to claim 1, wherein the step of calculating the actual rate of the network element data according to the historical timestamp or the current timestamp of each of the CDR messages comprises:

Based on the historical timestamp or the current timestamp of the first CDR message, the preset time is recursed, and the number of CDRs in the preset time is calculated, and the actual rate of the network element data in the preset time is equal to the number of CDR messages. Divide by the preset time.
The method of claim 1, wherein the step of decoding the network element data to obtain a historical timestamp and a network element number of each CDR message comprises:

Decoding each obtained CDR message, where each CDR message includes a message header and a message body;

Parsing the network element number of each CDR message from the message header;

The historical timestamp of each CDR message is parsed from the message body.
The method of claim 1, after the step of encoding each pre-processed message, further comprising:

Adding the encoded multiple CDR messages to the sending queue;

After the step of transmitting the encoded multiple CDR messages according to the determined actual rate, the method further includes: moving the sent CDR message out of the sending queue.
A device for playing back network data, comprising:

An acquiring module, configured to acquire network element data to be played back, where the network element data includes multiple bill messages;

a codec module, configured to decode the network element data, and obtain a historical timestamp and a network element number of each CDR message;

a pre-processing module, configured to pre-process each of the CDR messages, the pre-processing includes replacing a historical timestamp of each CDR message with a current timestamp, and sending each CDR message Replace the NE number with the target NE number;

The codec module is further configured to encode each pre-processed message;

a rate control module, configured to determine an actual rate of the network element data according to a historical timestamp or a current timestamp of each of the CDR messages;

The sending module is configured to send the encoded multiple CDR messages according to the determined actual rate.
The apparatus of claim 6 wherein said pre-processing module comprises:

a timestamp conversion sub-module, configured to calculate a historical timestamp of the first CDR message and a current time interval, and convert the historical timestamp of each CDR message to the time interval to be converted into each CDR The current timestamp of the message;

The network element replacement sub-module is configured to obtain the network element type of each CDR message, and replace the network element number of each CDR message with the target network element number according to the network element type.
The device according to claim 6, wherein the rate control module is further configured to recurs the preset time based on the historical timestamp or the current timestamp of the first bill message, and calculate the bill message in the preset time. Number, the actual rate of the network data obtained in the preset time is equal to the number of CDRs divided by the number Set the time.
The apparatus of claim 6, wherein the codec module is further configured to decode each of the acquired CDR messages, the CDR message including a message header and a message body; from the message header The network element number of each bill message is parsed; the historical time stamp of each bill message is parsed from the message body.
The apparatus of claim 6 further comprising:

Adding a module, and setting, after encoding each pre-processed CDR message, adding the encoded multiple CDR messages to the sending queue;

And removing the module, configured to: after sending the encoded multiple CDR messages according to the determined actual rate, move the sent CDR message out of the sending queue.
A computer readable storage medium storing computer executable instructions for performing a playback method of the network element data according to any one of claims 1-5.