CN107306199B - Network element data playback method and device - Google Patents
Network element data playback method and device Download PDFInfo
- Publication number
- CN107306199B CN107306199B CN201610251575.XA CN201610251575A CN107306199B CN 107306199 B CN107306199 B CN 107306199B CN 201610251575 A CN201610251575 A CN 201610251575A CN 107306199 B CN107306199 B CN 107306199B
- Authority
- CN
- China
- Prior art keywords
- network element
- message
- ticket
- ticket message
- timestamp
- 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
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
- H04L43/0894—Packet rate
Abstract
The invention relates to a method for replaying network element data, which comprises the steps of obtaining network element data to be replayed, wherein the network element data comprises a plurality of ticket messages; decoding the network element data, and acquiring the historical timestamp and the network element number of each ticket message; preprocessing each ticket message, wherein the preprocessing comprises replacing a historical timestamp of each ticket message with a current timestamp and replacing a network element number of each ticket message with a target network element number; coding the preprocessed call ticket message; determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message; and sending the coded call ticket message according to the determined actual rate. The process of replaying the network element data is not limited by complex network element software and hardware equipment any more, and the problems that the replay data is not high in authenticity and is not matched with the real data characteristics of the existing network are solved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for network element data playback.
Background
The network element data playback plays an important role in the debugging and testing processes of the communication system. Currently, most of data playback of communication network elements sends collected network element data to a designated server at a fixed rate without modification. Therefore, the played back data is not real, great limitation is brought to flexibility, the real sequence and time delay of signaling cannot be guaranteed, and the real service flow and use habit of a user in a certain time period cannot be reflected. There is a method proposed to calculate the interval between each message when a small amount of signaling data is played back, and to send back the true rate at intervals. The method is still controllable aiming at the signaling data with small data volume, and is not worried under the condition of the current massive data (hundreds of thousands of message volumes per second, hundreds of thousands of time intervals need to be calculated and sent), and the sending performance can not meet the requirement completely.
Disclosure of Invention
In view of the foregoing, there is a need to provide a method and apparatus for relatively precise network element data playback.
A method of network element data playback, the method comprising:
acquiring network element data to be played back, wherein the network element data comprises a plurality of ticket messages;
decoding the network element data, and acquiring the historical timestamp and the network element number of each ticket message;
preprocessing each ticket message, wherein the preprocessing comprises replacing a historical timestamp of each ticket message with a current timestamp and replacing a network element number of each ticket message with a target network element number;
coding the preprocessed call ticket message;
determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message;
and sending the coded call ticket message according to the determined actual rate.
An apparatus for network element data playback, the apparatus comprising:
the system comprises an acquisition module, a playback module and a playback module, wherein the acquisition module is used for acquiring network element data to be played back, and the network element data comprises a plurality of ticket messages;
the coding and decoding module is used for decoding the network element data and acquiring the historical timestamp and the network element number of each ticket message;
the preprocessing module is used for preprocessing each ticket message, and the preprocessing comprises replacing the historical timestamp of each ticket message with the current timestamp and replacing the network element number of each ticket message with the target network element number;
the coding and decoding module is also used for coding the preprocessed call ticket message;
the rate control module is used for determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message;
and the sending module is used for sending the coded call ticket message according to the determined actual rate.
According to the method and the device for replaying the network element data, the historical timestamp of each ticket message in the decoded network element data is replaced by the current timestamp, so that the problem that the replay network element data is low in authenticity is solved; by replacing the network element number of each ticket message with the target network element number, the method realizes that the appropriate network element number can be flexibly configured for each ticket 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 ticket message, and then the coded ticket messages are sent according to the determined actual rate, so that the actual sequence and the time delay of the signaling are ensured by restoring the actual real-time message throughput in the current network environment. The process of replaying the network element data is not limited by complex network element software and hardware equipment any more, and the problems that the replay data is not high in authenticity and is not matched with the real data characteristics of the existing network are solved.
Drawings
FIG. 1 is a flowchart of a method for network element data playback according to an embodiment;
FIG. 2 is a flow chart of a method for preprocessing each call ticket message in one embodiment;
FIG. 3 is a flow diagram of a method for decoding network element data in one embodiment;
FIG. 4 is a block diagram of an apparatus for network element data playback according to an embodiment;
FIG. 5 is a block diagram of the structure of a pre-processing module in one embodiment;
fig. 6 is a block diagram of an apparatus for playing back network element data in another embodiment.
Detailed Description
As shown in fig. 1, in one embodiment, a method for network element data playback is provided, which includes the following steps:
In this embodiment, the network element data refers to data transmitted between network elements, and includes both control plane data (signaling data) and media plane user data. The network element data is often massive and is stored in the form of text files. The network element data is stored in a form of a single ticket, so that the acquired network element data comprises a plurality of ticket messages. In one embodiment, the content of the network element data is hexadecimal. Specifically, a request for replaying the network element data is received, a path parameter corresponding to the network element data is searched in a configuration file, and the network element data to be replayed is obtained according to the path parameter. The network element data is pre-stored in a database.
And step 104, decoding the network element data, and acquiring the historical timestamp and the network element number of each ticket message.
In this embodiment, the network element data is stored in a form of a single ticket, and the obtained network element data is decoded, that is, a dialog ticket message is decoded, and the service time of each ticket message, that is, information such as a history timestamp of service occurrence, a network element type, and a network element number is analyzed. In one embodiment, the decoding rules follow the 3GPP standard protocol, the decoded objects are call ticket messages, and each call ticket message is composed of two parts, namely a message header and a message body. The decoded content then consists of two blocks: a message header and a message body. Wherein, the network element number and the network element type are decoded from the message header, and all fields related to the service occurrence time are decoded from the message body, and the method comprises the following steps: reporting time field, starting time field and ending time field. One of the time fields may be selected as the historical timestamp. Preferably, the history timestamp of the ticket message is a reporting time field.
And 106, preprocessing each ticket message, wherein the preprocessing comprises replacing the historical timestamp of each ticket message with the current timestamp and replacing the network element number of each ticket message with the target network element number.
In this embodiment, the parsed call ticket messages are preprocessed, in order to improve the authenticity of network element data playback, the historical timestamp of each call ticket message is replaced by the current timestamp, and in order to adapt to the network element number in the test environment, the network element number of each call ticket message is replaced by the target network element number in the test environment. Specifically, the historical timestamp of each ticket message is added with the interval between the historical timestamp of the first ticket message and the current time, so that the historical timestamp is changed into the current timestamp. Firstly, finding the position of the network element number in the call ticket message, then, according to the network element type and the network element number of each call ticket message, uniquely matching a target network element number for the network element number in a test environment, and replacing the previous network element number with the target network element number.
And step 108, coding the preprocessed call ticket message.
Specifically, after the ticket message is preprocessed, the processed ticket message needs to be encoded again, and the encoding rule follows a 3GPP standard protocol and adopts a general TLV encoding format for encoding. Wherein TLV means Type, Length, Value. The length of the coded data is variable, and the specific meaning of the data length and the value can be determined by the type. In one embodiment, the encoding adopts the original encoding mode of the ticket message, namely the encoding mode before decoding. The encoding specifically comprises encoding a message header and a message body of the call ticket message, and packaging the message header and the message body. In another embodiment, the dialog list message is encoded and loaded into the transmit queue for subsequent transmission.
And step 110, determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message.
In this embodiment, each ticket message has two timestamps, a historical timestamp and a current timestamp. The historical timestamp or the current timestamp can be selected for calculating the actual rate, and it needs to be stated that the timestamps must be selected consistently, that is, the historical timestamps are selected for all the call ticket messages, or the current timestamps are selected for all the call ticket messages. Specifically, a preset time is recurred by taking the historical time stamp or the current time stamp of the first ticket message as a reference, then the number of ticket messages in the preset time is calculated, and the calculated value of the ticket messages is used as the actual rate in the preset time. In one embodiment, a timer is started, the preset time is set to be 1 second, the call ticket messages in the sending queue are scanned every second, the time stamp of the first call ticket message in the sending queue is taken as a reference, 1 second is recurred, the number of the call ticket messages in the 1 second is found, and therefore the number of the call ticket messages in each second is obtained in real time, and the actual rate of the network element data is the number of the call ticket messages/each second.
And step 112, sending the coded call ticket message according to the determined actual rate.
In this embodiment, the encoded call ticket message is sent to the designated server according to the actual rate obtained by real-time calculation. The original mode here refers to the original transmission protocol of the network element data, i.e. the transmission protocol of the network element data in the current network, such as TCP, UDP. In one embodiment, the coded call ticket message is loaded into a sending queue, then the call ticket message in the sending queue is sent according to the real-time determined actual rate, the sent call ticket message is removed from the sending queue, whether the sending queue is empty or not is detected, if not, the sending is continued until all the call ticket messages are sent, and if yes, the sending is stopped.
In the embodiment, the problem of low authenticity of playback network element data is solved by replacing the historical timestamp of each ticket message in the decoded network element data with the current timestamp; by replacing the network element number of each ticket message with the target network element number, the method realizes that the appropriate network element number can be flexibly configured for each ticket 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 ticket message, and then the coded ticket messages are sent according to the determined actual rate, so that the actual sequence and the time delay of the signaling are ensured by restoring the actual real-time message throughput in the current network environment. The process of replaying the network element data is not limited by complex network element software and hardware equipment any more, and the problems that the replay data is not high in authenticity and is not matched with the real data characteristics of the existing network are solved.
As shown in fig. 2, in an embodiment, the step of preprocessing each ticket message, where the preprocessing includes replacing a historical timestamp of each ticket message with a current timestamp, and replacing a network element number of each ticket message with a target network element number, includes:
and 106a, calculating the time interval between the historical time stamp of the first ticket message and the current time, and adding the time interval to the historical time stamp of each ticket message to convert the historical time stamp of each ticket message into the current time stamp.
In this embodiment, each ticket message has a historical timestamp, where the historical timestamp refers to an original time of occurrence of a service of the ticket message, and in order to improve the authenticity of network element data playback, the original historical timestamp needs to be replaced with a current timestamp. Specifically, the historical timestamp of the first ticket message is found out, the time interval between the historical timestamp of the first ticket message and the current time is calculated, and then the historical timestamps of all the ticket messages are added to the time interval, namely the original historical timestamp is converted into the current timestamp.
And step 106b, acquiring the network element type of each call ticket message, and replacing the network element number of each call ticket message with the target network element number according to the network element type.
In this embodiment, each ticket message is decoded, the network element type of the ticket message can be analyzed from the message header part of each ticket message, and then the network element number of each ticket message is replaced by the target network element number in the test environment according to the obtained network element type and network element number.
In one embodiment, the step of calculating the actual rate of the network element data according to the historical time stamp or the current time stamp of each call ticket comprises: and recursion of preset time is carried out by taking the historical timestamp or the current timestamp of the first ticket message as a reference, the number of ticket messages in the preset time is calculated, and the calculated ticket message value is taken as the actual rate of the preset time.
Specifically, in order to restore the real-time message throughput in the current network environment and ensure the real sequence and time delay of the signaling, the ticket 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 recursion of a preset time (for example, 1 second) by taking the historical timestamp or the current timestamp of the first ticket as a reference on the premise of ensuring the time delay and the sequence among the existing ticket messages to be consistent, then calculating the number of the ticket messages within the preset time, wherein the calculated value of the ticket messages is the actual rate within the preset time, namely the number of the ticket messages/the preset time, and then transmitting the number of the ticket messages within the preset time to a corresponding target server in batches (once).
In one embodiment, the step of decoding the network element data and obtaining the historical timestamp and the network element number of each ticket message includes: and decoding the acquired call ticket message, wherein the call ticket message comprises a message header and a message body. Analyzing the network element number of the ticket message from the message header; and analyzing the historical timestamp of the ticket message from the message body.
In this embodiment, the ticket message includes a message header and a message body, and the decoding network element data is to decode the message header and the message body of each ticket message, analyze the network element number of the ticket message from the message header, and analyze the historical timestamp of the ticket message from the message body. In another embodiment, the network element type of the ticket message can be analyzed from the message header.
In one embodiment, after the step of encoding the preprocessed ticket message, the method further includes: and adding the coded call ticket message into a sending queue. After the step of sending the coded call ticket message according to the determined actual rate, the method further comprises the following steps: and removing the transmitted call ticket message from the transmission queue.
Specifically, after the preprocessed ticket messages are coded, the coded ticket messages are loaded into a sending queue, then the ticket messages in the sending queue are scanned, a preset time (such as 1 second) is recurred by taking a timestamp of the first ticket message as a reference, all the ticket messages in the preset time are obtained according to the timestamp of the ticket messages, all the ticket messages in the preset time in the sending queue are sent in batches, after the sending is completed, the sent ticket messages are removed from the sending queue, whether the sending queue is empty is detected, if not, the sending queue continues to be sent until all the ticket messages are sent, and if yes, the sending is stopped.
As shown in fig. 3, in one embodiment, the network element data playback flow is as follows:
And step 304, coding the preprocessed ticket message, and adding the coded ticket message into a sending queue.
And 305, determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message.
And step 306, sending the coded call ticket message according to the determined actual rate.
As shown in fig. 4, in an embodiment, an apparatus for network element data playback is provided, the apparatus including:
an obtaining module 402, configured to obtain network element data to be played back, where the network element data includes multiple ticket messages.
And the encoding and decoding module 404 is configured to decode the network element data, and obtain a historical timestamp and a network element number of each ticket message.
And the preprocessing module 406 is configured to preprocess each ticket message, where the preprocessing includes replacing a historical timestamp of each ticket message with a current timestamp, and replacing a network element number of each ticket message with a target network element number.
The coding and decoding module 404 is further configured to code the preprocessed ticket message.
A rate control module 408, configured to determine an actual rate of the network element data according to a historical timestamp or a current timestamp of each ticket message;
and a sending module 410, configured to send the encoded ticket message according to the determined actual rate.
As shown in FIG. 5, in one embodiment, the pre-processing module 406 includes:
the timestamp conversion module 406a is configured to calculate a time interval between a historical timestamp of a first ticket message and current time, and add the time interval to the historical timestamp of each ticket message to convert the historical timestamp of each ticket message into a current timestamp;
and the network element number replacing module 406b is configured to acquire the network element type of each ticket message, and replace the network element number of each ticket message with the target network element number according to the network element type.
In an embodiment, the rate control module 408 is further configured to recur the preset time by using a historical timestamp or a current timestamp of the first ticket message as a reference, calculate the number of ticket messages within the preset time, and use the calculated value of the ticket messages as an actual rate of the preset time.
In one embodiment, the encoding and decoding module is further configured to decode a ticket message in the obtained network element data, where the ticket message includes a message header and a message body; analyzing the network element number of the ticket message from the message header; and analyzing the historical timestamp of the ticket message from the message body.
As shown in fig. 6, in an embodiment, the apparatus for network element data playback further includes:
and an adding module 412, configured to add the encoded ticket message to a sending queue.
And a removing module 414, configured to remove the sent ticket message from the sending queue.
It will be understood by those skilled in the art that all or part of the processes in the methods of the embodiments described above may be implemented by hardware related to instructions of a computer program, which may be stored in a computer readable storage medium, for example, in the storage medium of a computer system, and executed by at least one processor in the computer system, so as to implement the processes of the embodiments including the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method of network element data playback, the method comprising:
acquiring network element data to be played back, wherein the network element data comprises a plurality of ticket messages;
decoding the network element data, and acquiring the historical timestamp and the network element number of each ticket message;
preprocessing each ticket message, wherein the preprocessing comprises replacing a historical timestamp of each ticket message with a current timestamp and replacing a network element number of each ticket message with a target network element number;
coding the preprocessed call ticket message;
determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message;
and sending the coded call ticket message according to the determined actual rate.
2. The method of claim 1, wherein the step of preprocessing each ticket message, the preprocessing comprising replacing a historical timestamp of each ticket message with a current timestamp and replacing a network element number of each ticket message with a target network element number, comprises:
calculating the time interval between the historical time stamp of the first ticket message and the current time, and converting the historical time stamp of each ticket message and the time interval into the current time stamp;
and acquiring the network element type of each ticket message, and replacing the network element number of each ticket message with the target network element number according to the network element type.
3. The method of claim 1, wherein the step of determining the actual rate of the network element data according to the historical timestamp or the current timestamp of each ticket message comprises:
and recursion of preset time is carried out by taking the historical time stamp or the current time stamp of the first ticket message as a reference, the number of ticket messages in the preset time is calculated, and the calculated ticket message value is taken as the actual rate of the preset time.
4. The method of claim 1, wherein the step of decoding the network element data to obtain the historical timestamp and the network element number of each ticket message comprises:
decoding an acquired call ticket message, wherein the call ticket message comprises a message header and a message body;
analyzing the network element number of the ticket message from the message header;
and analyzing the historical timestamp of the ticket message from the message body.
5. The method of claim 1, wherein the step of encoding the preprocessed ticket message further comprises:
adding the coded call ticket information into a sending queue;
after the step of sending the encoded call ticket message according to the determined actual rate, the method further comprises the following steps:
and removing the transmitted call ticket message from the transmission queue.
6. An apparatus for network element data playback, the apparatus comprising:
the system comprises an acquisition module, a playback module and a playback module, wherein the acquisition module is used for acquiring network element data to be played back, and the network element data comprises a plurality of ticket messages;
the coding and decoding module is used for decoding the network element data and acquiring the historical timestamp and the network element number of each ticket message;
the preprocessing module is used for preprocessing each ticket message, and the preprocessing comprises replacing the historical timestamp of each ticket message with the current timestamp and replacing the network element number of each ticket message with the target network element number;
the coding and decoding module is also used for coding the preprocessed call ticket message;
the rate control module is used for determining the actual rate of the network element data according to the historical time stamp or the current time stamp of each ticket message;
and the sending module is used for sending the coded call ticket message according to the determined actual rate.
7. The apparatus of claim 6, wherein the pre-processing module comprises:
the timestamp conversion module is used for calculating the time interval between the historical timestamp of the first ticket message and the current time, and converting the historical timestamp of each ticket message and the time interval into the current timestamp;
and the network element number replacing module is used for acquiring the network element type of each ticket message and replacing the network element number of each ticket message with the target network element number according to the network element type.
8. The device of claim 6, wherein the rate control module is further configured to recur a preset time based on a historical timestamp or a current timestamp of a first ticket message, calculate the number of ticket messages within the preset time, and use the calculated ticket message value as an actual rate of the preset time.
9. The device of claim 6, wherein the codec module is further configured to decode an acquired ticket message, where the ticket message includes a message header and a message body; analyzing the network element number of the ticket message from the message header; and analyzing the historical timestamp of the ticket message from the message body.
10. The apparatus of claim 6, further comprising:
the adding module is used for adding the coded call ticket information into a sending queue;
and the removing module is used for removing the sent call ticket message from the sending queue.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610251575.XA CN107306199B (en) | 2016-04-20 | 2016-04-20 | Network element data playback method and device |
| PCT/CN2017/077838 WO2017181808A1 (en) | 2016-04-20 | 2017-03-23 | Network element data playback method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610251575.XA CN107306199B (en) | 2016-04-20 | 2016-04-20 | Network element data playback method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107306199A CN107306199A (en) | 2017-10-31 |
| CN107306199B true CN107306199B (en) | 2020-03-27 |
Family
ID=60115621
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610251575.XA Active CN107306199B (en) | 2016-04-20 | 2016-04-20 | Network element data playback method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107306199B (en) |
| WO (1) | WO2017181808A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114445184A (en) * | 2022-01-27 | 2022-05-06 | 聚好看科技股份有限公司 | Order flow playback method and device |
| CN116684837B (en) * | 2023-07-19 | 2023-10-03 | 贵阳朗玛通信科技有限公司 | Billing preprocessing method and device for ticket |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571687A (en) * | 2010-12-10 | 2012-07-11 | 联芯科技有限公司 | Method for building synchronous status information among real-time media streams, device adopting same and SCC AS |
| CN104410807A (en) * | 2014-11-24 | 2015-03-11 | 深圳市华宝电子科技有限公司 | Method and device for synchronously replaying multi-channel video |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9570124B2 (en) * | 2012-01-11 | 2017-02-14 | Viavi Solutions Inc. | High speed logging system |
-
2016
- 2016-04-20 CN CN201610251575.XA patent/CN107306199B/en active Active
-
2017
- 2017-03-23 WO PCT/CN2017/077838 patent/WO2017181808A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571687A (en) * | 2010-12-10 | 2012-07-11 | 联芯科技有限公司 | Method for building synchronous status information among real-time media streams, device adopting same and SCC AS |
| CN104410807A (en) * | 2014-11-24 | 2015-03-11 | 深圳市华宝电子科技有限公司 | Method and device for synchronously replaying multi-channel video |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107306199A (en) | 2017-10-31 |
| WO2017181808A1 (en) | 2017-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110225417B (en) | Data processing method and server, and method and server for detecting stuck state | |
| US9781474B2 (en) | Content playback information estimation apparatus and method and program | |
| CN110781433A (en) | Data type determination method and device, storage medium and electronic device | |
| CN103795762A (en) | Reverse agent test system and method | |
| CN111107423A (en) | Video service playing card pause identification method and device | |
| CN107306200B (en) | Network fault early warning method and gateway for network fault early warning | |
| CN112738538B (en) | Live broadcasting room on-hook behavior detection method and device, electronic equipment and computer readable storage medium | |
| CN107306199B (en) | Network element data playback method and device | |
| CN104811959B (en) | Mobile network user perception analysis system and method based on big data | |
| CN104468248B (en) | Service performance monitoring method, reverse proxy server, statistical analysis server and system | |
| CN117130870B (en) | Transparent request tracking and sampling method and device for Java architecture micro-service system | |
| CN113612516A (en) | Compression test method, system and equipment for satellite communication data packet | |
| KR101465891B1 (en) | Traffic redundancy elimination method and apparatus in wireless network | |
| CN111064976B (en) | Method for sending live broadcast information and server | |
| CN106304122B (en) | Business data analysis method and system | |
| US9130827B2 (en) | Sampling from distributed streams of data | |
| CN114470749A (en) | Improved cloud game user card pause data quantization method | |
| CN109348413B (en) | Position information sharing method, device, equipment and storage medium | |
| CN113411544A (en) | Video fragment file sending method and device, storage medium and electronic device | |
| CN112261065A (en) | Method and device for compression transmission and calculation decompression of satellite communication | |
| CN111131249A (en) | Data processing method and device | |
| JP4460548B2 (en) | User experience quality estimation apparatus, method, and program | |
| CN114726891A (en) | Video transmission reporting method based on Internet of things | |
| CN117294687A (en) | Short video APP use perception evaluation method, device, equipment and storage medium | |
| CN115695463A (en) | Cloud edge cooperative self-adaptive data transmission management method and system based on fence mechanism |
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 |