CN114138680A

CN114138680A - Data construction method, data query method, data test method, electronic device, and storage medium

Info

Publication number: CN114138680A
Application number: CN202210056426.3A
Authority: CN
Inventors: 李响
Original assignee: Alibaba Singapore Holdings Pte Ltd
Current assignee: Alibaba Innovation Co
Priority date: 2022-01-18
Filing date: 2022-01-18
Publication date: 2022-03-04

Abstract

The embodiment of the application provides a data construction method, a data query method, a data test method, electronic equipment and a storage medium. The data construction method comprises the following steps: acquiring service configuration data of traffic broadcasting service and broadcasting content data generated by each upstream production link as scene data of a service link test demand scene; matching the scene data with the label matching rules of each scene label; determining scene tags meeting tag matching rules with the scene data as target scene tags; and storing the scene data and the target scene label in an associated manner. The embodiment of the invention improves the efficiency of constructing the link test data, thereby being beneficial to improving the link test efficiency.

Description

Data construction method, data query method, data test method, electronic device, and storage medium

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a data construction method, a data query method, a data test method, electronic equipment and a storage medium.

Background

The traffic broadcast is generally used in services such as electronic maps, and traffic information required by a user is broadcasted in real time based on the current position of the user, so that great convenience is brought to the user for traveling.

In order to provide reliable traffic broadcasting service, real-time performance and accuracy of offline data need to be guaranteed. On one hand, the real-time performance of the data has high requirements on the computing capacity of a background server of the traffic broadcast service, on the other hand, the real-time data is a large amount of offline data, the offline data are distributed in a dispersed manner, the background server of the traffic broadcast service is required to have a reliable service link, and the acquired offline data can be reliably coupled into the traffic broadcast service.

Generally speaking, in order to implement the service quality of the traffic broadcast service, the background server has a unique network architecture design to implement the acquisition of various required real-time data and each data processing link with a higher dependency degree, so that the complex business logic, the longer service link, the interdependence or mutual coupling of various data, and the like are presented. For example, the service link of the background server includes a processing node for receiving reported data such as traffic reported data and client feedback, a processing node for processing a data format of the reported data, a data screening node for screening matching reported data, a preprocessing node for preprocessing the reported data, and the like.

The processing amount of each processing node is relatively large, different processing nodes are usually maintained independently, and generally, when testing data of a link, reliable link testing data can be constructed only by considering the service configuration of each processing node, which results in low efficiency of constructing the link testing data.

Disclosure of Invention

In view of this, embodiments of the present application provide a data construction method, a data query method, a data test method, an electronic device, and a storage medium, which can improve efficiency of constructing link test data when a server has a complex service link, and thus are beneficial to improving link test efficiency.

According to a first aspect of embodiments of the present application, there is provided a data storage method, including: acquiring service configuration data of traffic broadcasting service and broadcasting content data generated by each upstream production link as scene data of a service link test demand scene; matching the scene data with the label matching rules of each scene label; determining scene tags meeting tag matching rules with the scene data as target scene tags; and storing the scene data and the target scene label in an associated manner.

In another implementation manner of the present invention, the acquiring service configuration data of a traffic broadcast service and broadcast content data generated by each upstream production link as scene data of a service link test demand scene includes: acquiring an online broadcast request of a traffic broadcast service and online dynamic broadcast content data generated by each upstream production link, wherein the online broadcast request comprises service configuration data; changing the online configuration parameters of the online broadcast request and the online dynamic broadcast content data into test configuration parameters conforming to a link test environment; determining playback data of the on-line dynamic broadcast content data after changing the parameters in the link test environment and an on-line broadcast request after changing the parameters as scene data of the service link test requirement scene.

In another implementation manner of the present invention, the matching the scene data with the tag matching rule of each scene tag includes: triggering the playback of the service configuration data, processing the broadcast content data to obtain a playback response, wherein the playback response comprises a service attribute field indicating the broadcast content data; and matching the service attribute field of the playback response with the field matching expression of each scene label.

In another implementation manner of the present invention, the determining, as the target scene tag, the scene tag that satisfies the tag matching rule with the scene data includes: and judging whether the service attribute field of the playback response hits a field matching item in a field matching expression of a scene label, and if so, determining the scene label as a target scene label.

In another implementation manner of the present invention, the service attribute field includes a plurality of hierarchies, and a plurality of field matching items in the field matching expression respectively correspond to the plurality of hierarchies.

In another implementation of the present invention, the plurality of field matches includes at least two of a test requirement match, a type match for a test event, and an occurrence segment match for a test event.

In another implementation of the invention, the method further comprises: obtaining user-defined test data, wherein the user-defined test data comprises a service attribute field; matching the service attribute field of the user-defined test data with the field matching expression of each scene label; and associating and storing the scene label meeting the label matching rule with the custom data and the target scene label.

According to a second aspect of embodiments of the present application, there is provided a data query method, including: acquiring a test data query request of a downstream link test of a traffic broadcasting service, wherein the test data query request comprises a target scene label; according to the target scene label, inquiring scene data stored in a correlated manner and a scene label of a link test demand scene, wherein the scene data comprises service configuration data of the traffic broadcasting service and broadcasting content data generated by each upstream production link; and returning the scene data matched with the target scene label as the test data of the downstream link test.

According to a third aspect of embodiments of the present application, there is provided a test method, including: generating a test data query request of a downstream link test of the traffic broadcasting service, wherein the test data query request comprises a target scene label so as to query by using the data query method according to the second aspect; acquiring inquired scene data matched with the target scene label as test data of the downstream link test; and performing link test based on the test data of the downstream link test.

According to a fourth aspect of embodiments of the present application, there is provided a data structuring apparatus comprising: the acquisition module acquires service configuration data of the traffic broadcasting service and broadcasting content data generated by each upstream production link as scene data of a service link test demand scene; the matching module is used for matching the scene data with the label matching rules of all the scene labels; the determining module is used for determining the scene label meeting the label matching rule with the scene data as a target scene label; and the storage module is used for storing the scene data and the target scene label in a correlation manner.

According to a fifth aspect of embodiments of the present application, there is provided a data query apparatus including: the acquisition module is used for acquiring a test data query request of a downstream link test of the traffic broadcasting service, wherein the test data query request comprises a target scene label; the query module is used for querying scene data stored in a correlated manner and the scene tags of the link test demand scenes according to the target scene tags, wherein the scene data comprises service configuration data of the traffic broadcast service and broadcast content data generated by each upstream production link; and the return module returns the scene data matched with the target scene label as the test data of the downstream link test.

According to a sixth aspect of embodiments of the present application, there is provided an electronic apparatus, including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus; the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the corresponding operation of the method according to any one of the first aspect to the third aspect.

According to a seventh aspect of embodiments of the present application, there is provided a computer storage medium having a computer program stored thereon, which when executed by a processor, implements the method according to any one of the first to third aspects.

According to the scheme of the embodiment of the application, in the downstream link test of the traffic broadcasting service, the service configuration data and the broadcast content data generated by each upstream production link are used as the scene data of the test demand scene, and a reliable test case can be generated.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present application, and other drawings can be obtained by those skilled in the art according to the drawings.

Fig. 1 is a schematic network architecture diagram of an on-line service of a typical example traffic broadcast service.

FIG. 2 is a schematic flow diagram of a data construction method according to one embodiment of the present application.

FIG. 3 is a schematic flow chart diagram of a data query method according to another embodiment of the present application

Fig. 4 shows an exemplary software architecture to which the embodiments of fig. 2 and 3 are applicable.

Fig. 5 is a schematic flow chart diagram of a testing method according to another embodiment of the present application.

Fig. 6 is a schematic structural diagram of an electronic device according to another embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application shall fall within the scope of the protection of the embodiments in the present application.

The following further describes specific implementations of embodiments of the present application with reference to the drawings of the embodiments of the present application.

Fig. 1 is a schematic network architecture diagram of an on-line service of a typical example traffic broadcast service. The network architecture of the online service of fig. 1 includes a real-time data collection 10 network node, an online service link 20, an electronic map service 30 network node, and a client 40. The network nodes described above may be implemented using one or more virtual computing devices or computing entities, and the number of network nodes, the number of devices or apparatuses in each network, and the number and types of modules or components in each device or apparatus are shown only schematically, in other examples, other networking modes, network topologies or apparatus arrangements, inter-module communication modes, connection modes or calling modes in each apparatus or device may be modified variously, and combinations or modifications of the embodiments or examples of the present invention given herein are within the scope of the embodiments of the present invention. In particular, the real-time data collection 10 network node may include one or more means, for example, collection of scene or environmental information using sensors 11.

The traffic report 12 can be used for real-time entry or periodic entry by traffic management personnel through a road condition entry interface. The traffic report 12 can be entered by traffic management personnel through any client with a data reporting function, a special client, and a monitoring platform or monitoring equipment.

The network 13 utilized for network acquisition may be of any type, fixed network such as ethernet, wireless network such as WIFI, mobile network, etc. In the networks described above, the protocols by which message-related data may be transmitted and received may be any, such as Internet protocol ("IP") datagrams and other higher layer protocols that use IP datagrams, such as user Datagram protocol ("UDP"), real-time streaming protocol ("RTSP"), real-time transport protocol ("RTP"), Microsoft (R) media Server ("MMS"), Transmission control protocol ("TCP"), Hypertext transfer protocol ("HTTP"), simple mail transfer protocol ("SMTP"), and the like.

The user feedback 14 may be made using a client 40 of the electronic map, for example, the client having installed a portal component for the user feedback. For example, the component may include the user evaluating the authenticity of the road condition event in order for the service to re-evaluate the confidence level of the road condition data or update the algorithm. Additionally, the user feedback 14 may also be in a similar manner to the traffic advisory 12, such as, for example, a random advisory, a timed advisory, an unscheduled advisory, etc., by a vehicle driver or pedestrian through a client having traffic service capability.

In this example, the online service link 20 may be used to enable a connection between collecting data to events provided for the user. In other words, the online service link 20 obtains event information or scenario information that the user intends to access through a series of data processing procedures. The in-line service link 20 may include one or more data processing nodes. The data processing nodes may be implemented as virtual nodes or as physical nodes, for example, each node may be implemented by using a separate server or a server cluster. The functions performed by the data processing nodes include, but are not limited to, data cleaning, data mining, data simulation, and the like. Algorithms employed by the data processing nodes include, but are not limited to, neural network calculations such as classification or clustering, filtering calculations, distributed calculations, etc. at the software level, and scalar calculations, vector calculations, tensor calculations, etc. at the hardware level. In this example, the online service link 20 includes an interface processing node 21, a data format processing node 22, a data screening node 23, a data pre-processing node 24, a big data computing node 25, and an event generating node 26.

In this example, the electronic map server 30 includes a network module 31, a vector data calculation module 32, and a database 33. The client 40 of the electronic map includes a network module and a map rendering module. It should be understood that the electronic map service 30 and the client 40 also include other components not shown, related or unrelated to the present example service. Specifically, the electronic map service 30 acquires event data ultimately provided by the event generating node from an upstream online service link, and generates a data structure or data type that facilitates presentation or processing at the front end based on the event data. For an electronic map service, event data may be acquired in real time from an online service link, and map data such as vector data is generated to be transmitted to a client through the network module 31. The client 40 may receive the vector data through the network module 41, and perform rendering by using the local map rendering module 42, so as to implement visualization of the event data. It should be understood that the map data described above may be transmitted to the user 50 through an access operation in response to the user 50. Or may be pushed to the user 50 as a real-time map service. The present example does not limit the various possible interaction modes of the front end.

It should be understood that the data service link described above performs data processing, and the software architecture, hardware architecture, development mode, algorithm framework, etc. are generally tightly connected as a whole for the specific service provided for the user. For the plurality of processing flows executed by the service side, when performing, for example, algorithm optimization or computation framework upgrade, ensuring independence of optimization targets is an important optimization target, in other words, when upgrading a specific aspect of the system, an upgrade target which has no influence or little influence on other aspects of the system is important. In optimizing a particular aspect of a service, it is an important optimization goal to have no or less impact on other aspects of the service.

Therefore, the traffic broadcasting service line has many problems in the link test process due to the service characteristics of complex service, long links during service realization, much data dependence, mutual coupling and incapability of blackening internal logic. For example, the complex data construction results in higher test cost at each node on the link, the missing data source in the link test environment results in the test data being unstructured and thus untested, and so on.

FIG. 2 is a schematic flow diagram of a data construction method according to one embodiment of the present application. The scheme of the embodiment can be executed by a server such as a test server, a cloud server, a tag library server, and the like.

The data construction method of the embodiment comprises the following steps:

s210: and acquiring service configuration data of the traffic broadcasting service and broadcasting content data generated by each upstream production link as scene data of a service link test requirement scene.

It should be understood that the scene data herein may indicate the test environment configuration, broadcast the test content data, the service configuration, and the like, and not only indicate to broadcast the test content data.

It should also be understood that the service link test demand scenario includes, but is not limited to, a numerous experience test, a congestion test, an accident test, and the like.

It should also be understood that, in the case of being applied to the network architecture of fig. 1, in the traffic condition monitoring system, a plurality of sensors 11 may be arranged at intersections, buildings, specific traffic network monitoring nodes, and the like. Additionally, the sensor monitoring of the present example also includes remote monitoring mechanisms such as satellite telemetry. For example, in other monitoring scenarios, placement of sensor locations or data reporting opportunities may be deployed in conjunction with specific data services to provide data of high data mining or processing value. The one or more sensors 11 may also be used to monitor physical information such as temperature, humidity, air visibility, etc. at a particular time or location, as well as statistical information such as people stream density, noise intensity, etc. In this case, the sensor 11 may collect various data, input into the upstream of the data processing service link 20, and obtain corresponding broadcast content data at the downstream of the data processing service link 20.

As another example, the traffic report 12 may be used for real-time entry or periodic entry by traffic managers through a road condition entry interface. The entered traffic information includes, but is not limited to, time, location, road segment, vehicle type, number of vehicles, traffic type, confidence of traffic condition, population, etc. of the traffic. In this case, the traffic advisor 12 may collect various data, input into the data processing service link 20 upstream, and obtain corresponding advisory content data downstream of the data processing service link 20.

In addition, the sensor 11 and the traffic report 12 are only examples of the data acquisition node 10, and may also acquire data in other manners and generate corresponding broadcast content data.

S220: and matching the scene data with the label matching rules of the scene labels.

It should be understood that a context tag may also be understood herein as a context data store. The scene data warehouse stores the incidence relation between the scene data and the scene label. Scene data can be obtained by inquiring the scene tags based on the incidence relation, so that the test requirement scene indicated by the scene data can be quickly restored. The scene data warehouse realizes the circular circulation of data, and the test data construction is carried out based on the requirements (test points) of the test cases such as the downstream link test case, so that the efficiency of constructing the test data required by the test case is improved.

It is also understood that individual scene tags may be constructed into a scene tag set and may be pre-stored, for example, in a tag library server. And a new scene label can be constructed, and the current scene label library can be updated. Each scene tag may have its own tag matching rules.

It should also be understood that a rule match indicating a tag match rule includes multiple levels, each level having a higher match priority than the next level, e.g., multiple levels may include parent rules, child rules, and link rules. Accordingly, the matching priority of the parent rule is higher than that of the child rule, and the matching priority of the child rule is higher than that of the link rule. More specifically, the service field information of the scene data may be matched with the parent rule, and if the first service field information is matched with the parent rule, it is determined whether other service fields are matched with the child rule; and if the second service field is matched with the sub-rule, judging whether the third service field is matched with the link rule or not.

It should also be understood that for scene data that matches a parent rule but does not match a child rule and its subordinate rules, the rule matching entry may include only the matching entry corresponding to the parent rule. For the scene data that matches each hierarchy, the rule matching item may include a plurality of matching items corresponding to each hierarchy. In addition, for different scene data, a parent rule of one scene data may correspond to a child rule of another scene data.

S230: and determining the scene label meeting the label matching rule with the scene data as a target scene label.

It should be understood that the tag matching rules may be set for scene tags and pre-associated. The label matching rule can be keyword matching and can also be subject matching. The tag matching rule of each scene tag may be matched with the scene data, and the scene tag corresponding to the successfully matched tag rule is associated with the scene data.

Further, based on the example in step S220, in the case where the first traffic field indicates a navigation type, the second traffic field indicates a traffic event type, and the third traffic field indicates an occurrence section of a traffic event, for scene data that matches the parent rule but does not match the child rule and its lower rule, the parent rule may be associated with the navigation type. For scene data matching each hierarchy, a parent rule, a child rule, and a link rule may be associated with a navigation type, a traffic event type, and an occurrence section, respectively.

S240: and storing the scene data and the target scene label in an associated manner.

It should be appreciated that the index of the scene data and the target scene tag may be established in a scene tag database. For example, the scene data, the target scene tag, and the association relationship may be stored independently, e.g., in different databases or in different mapping tables in the same database. When querying data, a scene data tag may be obtained first, and then a corresponding association relationship is obtained according to the scene data tag, so as to determine a scene identifier accordingly. The scene data identifier can be searched in a mapping table from the scene data identifier to the scene data, and accordingly the scene data can be obtained.

In other words, the scene data can realize the rapid reduction of the test demand scene, weaken the complex data preparation process, and even realize low-cost multiplexing, thereby solving the test cost of the upstream and downstream nodes of the test link of the traffic reporting service.

In other examples, for obtaining scene data of a service link test requirement scenario, an online broadcast request of a traffic broadcast service and online dynamic broadcast content data generated by each upstream production link may be obtained, where the online broadcast request includes service configuration data, then online configuration parameters of the online broadcast request and the online dynamic broadcast content data are changed to test configuration parameters conforming to a link test environment, and then playback data of the online dynamic broadcast content data in the link test environment after changing the parameters and the online broadcast request after changing the parameters are determined to serve as the scene data of the service link test requirement scenario. Based on the processing, the online broadcast request of the traffic broadcast service and the online dynamic broadcast content data generated by each upstream production link are easy to obtain, and scene data of a service link test demand scene which is difficult to construct is obtained by changing the configuration parameters of the data, so that the data processing efficiency is improved.

Alternatively, for obtaining the scene data of the service link test requirement scene, custom test data may be obtained, where the custom test data includes a service attribute field, then the service attribute field of the custom test data is matched with the field matching expression of each scene tag, and then the scene tag meeting the tag matching rule with the custom data is stored in association with the target scene tag. Based on the processing, the associated storage of the custom test data and the scene label is realized, the storage and use of the data are realized, the data constructing mode is further improved, and the quantity of the test data is increased.

In other examples, matching the scene data to the tag matching rules for the respective scene tags includes: triggering the playback of the service configuration data, processing the broadcast content data to obtain a playback response, wherein the playback response comprises a service attribute field indicating the broadcast content data; and matching the service attribute field of the playback response with the field matching expression of each scene label. Therefore, the service attribute field for indicating the broadcast content data can be quickly obtained by triggering the playback response obtained by the playback of the service configuration data, and in addition, the service attribute field of the playback response is matched with the field matching expression of each scene label, so that the matching accuracy can be improved.

In other examples, determining a scene tag that satisfies a tag matching rule with the scene data as a target scene tag includes: and judging whether the service attribute field of the playback response hits a field matching item in a field matching expression of a scene label, and if so, determining the scene label as a target scene label. Therefore, by judging whether the service attribute field of the playback response hits the field matching expression of the scene label, the field matching efficiency is improved.

Specifically, the field matching expression indicates a scene matching rule. The scene matching rule may include at least one matching item. In one example, the plurality of matching items in the scenario matching rule include a parent rule matching item, a child rule matching item, and a link rule matching item as scenario tags, for example, the parent rule matching item may be a test requirement matching item, the child rule matching item may be a type matching item of a test event, and the link rule matching item may be an occurrence section matching item of the test event.

Further, the field matching expression may include at least one field. The field match expression includes a field indicating a parent rule, a field indicating a child rule, and a field indicating a link rule. The service attribute field of the scene data may include at least one hierarchy level. In particular, the number of levels of the service attribute field may correspond to matching items in the scene matching rule, for example, having a one-to-one correspondence.

The correspondence between the respective levels of the service attribute field and the respective matching items in the scene matching rule will be exemplarily described in the form of table 1 below.

Table 1

Scene matching rules	Matching item 1	Matching item 2	Matching item 3
					Parent rule matching item	Sub-rule matching items	Link rule matching entry
Service attribute field type	Field 1	Field 2	Field 3
				Type 1	Test requirements	Test event type	Testing event occurrence road section
Type 2	Test event type	Testing event occurrence road section
				Type 3	Testing event occurrence road section

Specifically, different service attribute field types may include different numbers of fields, and information indicated by fields at the same position in different service attribute field types may be the same or different. For example, type 1 includes 3 fields, type 2 includes 2 fields, type 1 field 2 is the same as type 2 field 1, and type 1 field 3 is the same as type 2 field 3. Further, 1 field is included in type 3, and the field of type 3 is the same as field 3 of type 1 and the same as field 2 of type 2.

An example of the service attribute field corresponding to each test scenario will be exemplarily described in the form of table 2.

Table 2

Specifically, taking the example that the service attribute field is composed of a test requirement, a test event type and a test event occurrence section, different test scenarios may include information corresponding to at least some of the fields.

According to the example in step S220, for different scene data, the parent rule of one scene data may correspond to the child rule of another scene data, and the field levels corresponding to the respective fields are marked in the table.

Accordingly, the scene data 1 and the scene data 3 include information corresponding to the above three fields. Scenario data 2 does not include information of the test requirements, e.g., identification of the test requirements. The scene data 4 does not include information of the test time transmission section.

When matching is performed based on the scene matching rule, data corresponding to each matching item in the scene data may be determined based on the scene matching expression. And under the condition that each matching item corresponds to each service attribute field, the corresponding data in the scene data comprises the field value corresponding to each service attribute field.

In addition, the service elements are reliably reflected by the test requirement matching item, the type matching item of the test event and the occurrence road section matching item of the test event, and the accuracy of matching processing is favorably improved.

Fig. 3 is a schematic flow chart diagram of a data query method according to another embodiment of the present application. The scheme of the embodiment can be executed by a server such as a test server, a cloud server, a tag library server, and the like. The data query method of fig. 3 includes:

s310: and acquiring a test data query request of a downstream link test of the traffic broadcasting service, wherein the test data query request comprises a target scene label.

S320: and inquiring scene data and scene labels of the link test requirement scenes in a correlated manner according to the target scene labels, wherein the scene data comprises service configuration data of the traffic broadcast service and broadcast content data generated by each upstream production link.

S330: and returning the scene data matched with the target scene label as the test data of the downstream link test.

According to the scheme of the embodiment of the application, the scene data of the service link test requirement scene comprises the service configuration data and the broadcast content data generated by each upstream production link, so that the method can be used for the test case of the downstream link test of the traffic broadcast service, and the efficiency of acquiring the test data is improved by inquiring the scene tags of the scene data stored in association with the scene label of the link test requirement scene.

In an example, taking tables 1 and 2 as an example, corresponding to the above-mentioned matching based on the scenario matching rule, the test data query request includes a target scenario tag, and the target scenario tag may indicate at least one of field 1, field 2, and field 3. When the target scene tag corresponds to 3 fields, accordingly, since the scene data 2 and 4 do not include information of 3 fields, the scene data 1 and the scene data 3 (including 3 fields) are determined as candidates. Then, according to the respective corresponding field types of the field 1, the field 2 and the field 3 of the target scene (for example, the type of the field 1 is determined first, and after the type of the field 1 is matched, it is determined that the scene data 1 and the scene data 3 both meet the test requirements of the target scene.

Alternatively, the target scene tag corresponds to 2 fields, and since the scene data 1 and the scene data 3 respectively include 3 fields, the scene data 2 and the scene data 4 are determined to be candidates. Then, the field 1 corresponding to the target scene tag indicates a test requirement, and since the field 1 of the scene data 2 indicates that a traffic vehicle arrives, the scene data 4 is determined to be the scene data matched with the target scene tag.

It can be seen that, without loss of generality, candidate scene data may be selected from the associated scene data according to the number of fields corresponding to the target scene tag, where the number of service fields in the candidate scene data matches the number of fields corresponding to the target scene tag.

Then, the service field information of the candidate scene data is sequentially matched with each hierarchy. Matching the service field information of the candidate scene data with the father rule, and if the first service field information is matched with the father rule, judging whether other service fields are matched with the son rule or not; and if the second service field is matched with the sub-rule, judging whether the third service field is matched with the link rule or not.

FIG. 4 shows an exemplary software architecture of a data construction method and a query method according to another embodiment of the present application. As shown, the tag library software architecture to which the data construction method and the query method are applied may include an application layer, a service layer, and a data layer. The application layer can be used for interacting with the outside, the service layer can be used for core logic processing, and the data layer can perform data interaction processing.

Specifically, the application layer provides storage and reading (query) functions externally, including an open call interface for data entry and a front-end page for data reading. In some examples, custom test data in the text may be input, and when the call interface receives the custom test data, the tag matching calculation is triggered to obtain an association relationship corresponding to the custom test data. In other examples, playback of the online data may be performed by a timed task. As in the above embodiments, acquiring the online traffic of the traffic broadcast service and the online source data at the same time are merged into the link test environment (for example, by changing configuration parameters). The online service request may then be played back, resulting in a playback response. And matching the service data field in the playback response with the matching rule to obtain the association relation to be stored.

It should be understood that the scene data in the tag database server may be short-term data and long-term data, respectively. The long-term data may include weather data, traffic light data, and trend data, industry data, etc., that lack a data source without generating, that do not change frequently in the link test environment. The on-line data acquisition, fusion and tag library updating can be triggered by timing every day and the like, so that the timeliness of the scene data tag is guaranteed. The short-term data may include data that is subject to frequent changes, such as events, road conditions, etc., and may be obtained by online data playback, such as in hours or minutes, for example.

In addition, the service layer plays an important role in the software architecture of the tag library. The service layer may include a plurality of modules. For example, the corresponding storage processing modules may include an update timing task module, an intelligent parameter generation module, a data processing module, a scene matching rule module, a tag matching calculation module, a link testing environment broadcast service module, and the like. In the storage processing, the response of the input data in the link test environment can be processed through the self-defined scene rule. In addition, the module corresponding to the query processing may include a data acquisition module, a data filtering module, and the like. In the query processing, a data acquisition module may be used to acquire a query request such as test data, and determine matching scene data through a data screening module, and then return the scene data to a front-end page.

In addition, the data layer may include a local database, an object storage service database, a scene tag database in which a user stores scene tags, and the like. One type of data stored in the data layer comprises online source data acquired from a history release interface and the like through a timing synchronization task and a traffic broadcast service request. Another type of data of the data store includes scene data, scene tags, and the like. The electronic device may include: a processor (processor)602, a communication Interface 604, a memory 606, and a communication bus 608.

Wherein: the processor 602, communication interface 604, and memory 606 communicate with one another via a communication bus 608. A communication interface 604 for communicating with other electronic devices or servers.

The processor 602 is configured to execute the program 610, and may specifically perform relevant steps in the foregoing method embodiments.

In particular, program 610 may include program code comprising computer operating instructions.

The processor 602 may be a processor CPU, or an application Specific Integrated circuit (asic), or one or more Integrated circuits configured to implement embodiments of the present application. The intelligent device comprises one or more processors which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.

And a memory 606 for storing a program 610. Memory 606 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The program 610 may specifically be configured to cause the processor 602 to perform the following operations: acquiring service configuration data of traffic broadcasting service and broadcasting content data generated by each upstream production link as scene data of a service link test demand scene; matching the scene data with the label matching rules of each scene label; determining scene tags meeting tag matching rules with the scene data as target scene tags; and storing the scene data and the target scene label in an associated manner.

Alternatively, the program 610 may specifically be configured to cause the processor 602 to perform the following operations: acquiring a test data query request of a downstream link test of a traffic broadcasting service, wherein the test data query request comprises a target scene label; according to the target scene label, inquiring scene data stored in a correlated manner and a scene label of a link test demand scene, wherein the scene data comprises service configuration data of the traffic broadcasting service and broadcasting content data generated by each upstream production link; and returning the scene data matched with the target scene label as the test data of the downstream link test.

Alternatively, the program 610 may specifically be configured to cause the processor 602 to perform the following operations: generating a test data query request of a downstream link test of the traffic broadcasting service, wherein the test data query request comprises a target scene label so as to query by using a data query method; acquiring inquired scene data matched with the target scene label as test data of the downstream link test; and performing link test based on the test data of the downstream link test.

In addition, for specific implementation of each step in the program 610, reference may be made to corresponding steps and corresponding descriptions in units in the foregoing method embodiments, which are not described herein again. It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described devices and modules may refer to the corresponding process descriptions in the foregoing method embodiments, and are not described herein again.

It should be noted that, according to the implementation requirement, each component/step described in the embodiment of the present application may be divided into more components/steps, and two or more components/steps or partial operations of the components/steps may also be combined into a new component/step to achieve the purpose of the embodiment of the present application.

The above-described methods according to embodiments of the present application may be implemented in hardware, firmware, or as software or computer code storable in a recording medium such as a CD ROM, a RAM, a floppy disk, a hard disk, or a magneto-optical disk, or as computer code originally stored in a remote recording medium or a non-transitory machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the methods described herein may be stored in such software processes on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware such as an ASIC or FPGA. It will be appreciated that a computer, processor, microprocessor controller, or programmable hardware includes memory components (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code that, when accessed and executed by a computer, processor, or hardware, implements the methods described herein. Further, when a general-purpose computer accesses code for implementing the methods illustrated herein, execution of the code transforms the general-purpose computer into a special-purpose computer for performing the methods illustrated herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

The above embodiments are only used for illustrating the embodiments of the present application, and not for limiting the embodiments of the present application, and those skilled in the relevant art can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application, so that all equivalent technical solutions also belong to the scope of the embodiments of the present application, and the scope of patent protection of the embodiments of the present application should be defined by the claims.

Claims

1. A method of data construction, comprising:

acquiring service configuration data of traffic broadcasting service and broadcasting content data generated by each upstream production link as scene data of a service link test demand scene;

matching the scene data with the label matching rules of each scene label;

determining scene tags meeting tag matching rules with the scene data as target scene tags;

and storing the scene data and the target scene label in an associated manner.

2. The method according to claim 1, wherein the acquiring of the traffic broadcast service configuration data and the broadcast content data generated by each upstream production link as the scene data of the service link test demand scene comprises:

acquiring an online broadcast request of a traffic broadcast service and online dynamic broadcast content data generated by each upstream production link, wherein the online broadcast request comprises service configuration data;

changing the online configuration parameters of the online broadcast request and the online dynamic broadcast content data into test configuration parameters conforming to a link test environment;

determining playback data of the on-line dynamic broadcast content data after changing the parameters in the link test environment and an on-line broadcast request after changing the parameters as scene data of the service link test requirement scene.

3. The method of claim 1, wherein the matching the scene data to the tag matching rules for each scene tag comprises:

triggering the playback of the service configuration data, processing the broadcast content data to obtain a playback response, wherein the playback response comprises a service attribute field indicating the broadcast content data;

and matching the service attribute field of the playback response with the field matching expression of each scene label.

4. The method of claim 3, wherein the determining a scene tag satisfying a tag matching rule with the scene data as a target scene tag comprises:

and judging whether the service attribute field of the playback response hits a field matching item in a field matching expression of a scene label, and if so, determining the scene label as a target scene label.

5. The method of claim 4, wherein the service attribute field comprises a plurality of tiers, and a plurality of field matches in the field match expression correspond to the plurality of tiers, respectively.

6. The method of claim 5, wherein the plurality of field matches includes at least two of a test requirement match, a type match for a test event, and an occurrence segment match for a test event.

7. The method of claim 1, wherein the method further comprises:

obtaining user-defined test data, wherein the user-defined test data comprises a service attribute field;

matching the service attribute field of the user-defined test data with the field matching expression of each scene label;

and associating and storing the scene label meeting the label matching rule with the custom data and the target scene label.

8. A method of data query, comprising:

acquiring a test data query request of a downstream link test of a traffic broadcasting service, wherein the test data query request comprises a target scene label;

according to the target scene label, inquiring scene data stored in a correlated manner and a scene label of a link test demand scene, wherein the scene data comprises service configuration data of the traffic broadcasting service and broadcasting content data generated by each upstream production link;

and returning the scene data matched with the target scene label as the test data of the downstream link test.

9. A method of testing, comprising:

generating a test data query request of a downstream link test of a traffic broadcasting service, wherein the test data query request comprises a target scene label so as to query by using the data query method according to claim 8;

acquiring inquired scene data matched with the target scene label as test data of the downstream link test;

and performing link test based on the test data of the downstream link test.

10. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus; the memory is configured to store at least one executable instruction that causes the processor to perform the method of any of claims 1-9.

11. A computer storage medium having stored thereon a computer program which, when executed by a processor, carries out the method of any one of claims 1 to 9.