CN111612562B

CN111612562B - Data marking method and device and electronic equipment

Info

Publication number: CN111612562B
Application number: CN201910143797.3A
Authority: CN
Inventors: 唐旭; 刘章勋; 韩冰
Original assignee: Beijing Didi Infinity Technology and Development Co Ltd
Current assignee: Beijing Didi Infinity Technology and Development Co Ltd
Priority date: 2019-02-25
Filing date: 2019-02-25
Publication date: 2023-10-24
Anticipated expiration: 2039-02-25
Also published as: CN111612562A

Abstract

The application provides a data marking method, a device and electronic equipment, wherein the data marking method comprises the following steps: acquiring completed target order data from an order server, wherein the target order data carries an initial tag; acquiring order related operation data submitted by a service requester terminal and/or a service provider terminal; assigning values to the parameters matched with the target order data according to the order related operation data to obtain attribute parameters; judging whether the attribute parameters are matched with the attributes of the initial tags of the target order data; if yes, setting the target label which is the same as the initial label for the target order data.

Description

Data marking method and device and electronic equipment

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data marking method, a data marking device, and an electronic device.

Background

The data used for training needs to be labeled before the model of the neural network is trained. The current marking modes mainly comprise: manual marking, which is relatively slow, is also a waste of human resources.

Disclosure of Invention

In view of the above, an object of the embodiments of the present application is to provide a data marking method, apparatus and electronic device, which can identify whether a current tag of data is matched with updated information by matching updated or acquired parameters of the tagged data, so as to solve the problem in the prior art that the data tag is inaccurate or the tag marking is slow, and achieve the effect of fast and accurate data marking.

According to one aspect of the application, an electronic device is provided that may include one or more storage media and one or more processors in communication with the storage media. One or more storage media store machine-readable instructions executable by a processor. When the electronic device is in operation, the processor and the storage medium communicate over the bus, and the processor executes the machine-readable instructions to perform one or more of the following:

acquiring completed target order data from an order server, wherein the target order data carries an initial tag;

acquiring order related operation data submitted by a service requester terminal and/or a service provider terminal;

assigning values to the parameters matched with the target order data according to the order related operation data to obtain attribute parameters;

Judging whether the attribute parameters are matched with the attributes of the initial tags of the target order data;

if yes, setting the target label which is the same as the initial label for the target order data.

The verification operation of the label of the data can be further realized through the received order related operation data submitted by the service requester terminal and/or the service provider, so that the label attached to the data can be more accurate. In addition, the matching parameters are assigned through the order related operation data, the matching degree of the attribute parameters and the attribute of the initial label can be intuitively judged according to the values of the attribute parameters in the judging process, and quick marking data can be realized.

In some embodiments, the step of obtaining order related operation data submitted by the service requester terminal and/or the service provider terminal includes:

acquiring first cancellation operation data of cancellation orders sent by a service requester terminal;

the step of assigning the parameters matched with the target order data according to the order related operation data to obtain attribute parameters comprises the following steps:

judging whether the service requester terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the first cancel operation data;

If yes, a first class value is given to the abnormal operation parameters of the service request party of the target order data.

if not, acquiring service requester feedback information carried in the first cancellation operation data;

and assigning a value to the parameter matched with the feedback information of the service requester.

In some embodiments, the step of assigning a value to a parameter that matches the service requester feedback information includes:

if the service requester feedback information comprises self responsibility data, assigning a first class value for the responsibility parameters of the service requester; or alternatively, the first and second heat exchangers may be,

and if the feedback information comprises complaint data, assigning a first class value to the responsibility parameters of the service provider.

acquiring second cancellation operation data of cancellation orders sent by a service provider terminal;

judging whether the service provider terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the second cancel operation data;

if yes, a first class value is given to the abnormal operation parameters of the service provider of the target order data.

If not, acquiring service provider feedback information carried in the second canceling operation data;

and assigning a value to the parameter matched with the feedback information of the service provider.

if not, judging whether the service provider terminal has a communication record with the service requester terminal before the second cancel operation data;

if not, a first class of values is assigned to the responsibility parameters of the service provider.

if not, judging whether the service provider terminal has a communication record of the terminal bound with the background server side before the second cancel operation data;

In some embodiments, the parameters include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider; the step of judging whether the attribute parameter matches the attribute of the initial tag of the target order data includes:

if the initial label is a service provider responsibility, judging whether a responsibility parameter of the service provider or an abnormal operation parameter of the service provider is a first class value, and if the responsibility parameter of the service requester and the abnormal operation parameter of the service requester are non-first class values, judging that an attribute parameter is matched with the attribute of the initial label of the target order data; or alternatively, the process may be performed,

If the initial label is responsible for a service requester, judging whether the responsibility parameter of the service provider or the abnormal operation parameter of the service provider is a non-first type value, and if the responsibility parameter of the service requester and the abnormal operation parameter of the service provider are first type values, judging that the attribute parameter is matched with the attribute of the initial label of the target order data.

In another aspect, an embodiment of the present application further provides a data marking apparatus, including:

the first acquisition module is used for acquiring completed target order data from the order server, wherein the target order data carries an initial tag;

the second acquisition module is used for acquiring order related operation data submitted by the service requester terminal and/or the service provider terminal;

the assignment module is used for assigning values to the parameters matched with the target order data according to the order related operation data to obtain attribute parameters;

the judging module is used for judging whether the attribute parameters are matched with the attributes of the initial tags of the target order data;

and the setting module is used for setting the target label which is the same as the initial label for the target order data if the attribute parameter is matched with the attribute of the initial label of the target order data.

In some embodiments, the second acquisition module is further configured to: acquiring first cancellation operation data of cancellation orders sent by a service requester terminal;

the assignment module is further configured to:

In some embodiments, the second acquisition module is further to:

the assignment module is further configured to:

In some embodiments, the assignment module is further configured to:

In some embodiments, the second acquisition module is further configured to:

the assignment module is further configured to:

In some embodiments, the second acquisition module is further configured to:

the assignment module is further configured to:

In some embodiments, the second acquisition module is further configured to:

the assignment module is further configured to:

In some embodiments, the second acquisition module is further configured to:

the assignment module is further configured to:

In some embodiments, the parameters include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider; the judging module is further configured to:

In another aspect, embodiments of the present application also provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the data marking method in any of the possible embodiments described above.

In another aspect, an embodiment of the present application further provides an electronic device, including: the system comprises a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, the processor and the memory are communicated through the bus when the electronic device runs, and the machine-readable instructions are executed by the processor to execute the steps of the data marking method.

In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a data marking system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

FIG. 3 is a flow chart of a method for marking data according to an embodiment of the present application;

fig. 4 shows a schematic structural diagram of a data marking device according to an embodiment of the present application.

Icon: 100-a data tagging system; 110-a server; 120-network; 130-service requester terminal; 140-service provider terminal; 150-a database; 200-an electronic device; 210-network ports; 220-a processor; 230-a communication bus; 240-storage medium; 250-interface; 401-a first acquisition module; 402-a second acquisition module; 403-assignment module; 404-a judging module; 405-set up module.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.

In order to enable those skilled in the art to use the present disclosure, the following embodiments are presented in connection with a specific application scenario "net car". It will be apparent to those having ordinary skill in the art that the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the application. While the application is primarily described in the context of a net cart, it should be understood that this is but one exemplary embodiment. The application can be applied to any other traffic type. For example, the present application may be applied to different transportation system environments, including land, sea, or air, or the like, or any combination thereof. The transportation means of the transportation system may include taxis, private cars, windmills, buses, trains, bullet trains, high speed railways, subways, ships, airplanes, spacecraft, hot air balloons, or unmanned vehicles, etc., or any combination thereof. The application may also include any service system for order service, e.g. a system for sending and/or receiving express, a service system for trading between buyers and sellers. Applications of the system or method of the present application may include web pages, plug-ins to a browser, client terminals, customization systems, internal analysis systems, or artificial intelligence robots, etc., or any combination thereof.

It should be noted that the term "comprising" will be used in embodiments of the application to indicate the presence of the features stated hereafter, but not to exclude the addition of other features.

The terms "passenger," "requestor," "attendant," "service requestor," and "customer" are used interchangeably herein to refer to a person, entity, or tool that may request or subscribe to a service. The terms "driver," "provider," "service provider," and "provider" are used interchangeably herein to refer to a person, entity, or tool that can provide a service. The term "user" in the present application may refer to a person, entity or tool requesting, subscribing to, providing or facilitating the provision of a service. For example, the user may be a passenger, driver, operator, etc., or any combination thereof. In the present application, "passenger" and "passenger terminal" may be used interchangeably, and "driver" and "driver terminal" may be used interchangeably.

The terms "service request" and "order" are used interchangeably herein to refer to a request initiated by a passenger, service requester, driver, service provider, or vendor, etc., or any combination thereof. Accepting the "service request" or "order" may be a passenger, a service requester, a driver, a service provider, a vendor, or the like, or any combination thereof. The service request may be either fee-based or free.

One aspect of the application relates to a data marking system. The system can identify whether the current label of the data is matched with updated information or not by matching the data already labeled with the updated or acquired parameters, so that the inaccuracy of the data label in the prior art is solved.

Example 1

FIG. 1 is a block diagram of a data tagging system 100 according to some embodiments of the application. For example, the data tagging system 100 may be an online transportation service platform for a transportation service such as a taxi, a ride service, a express, a carpool, a bus service, a driver rental, or a class service, or any combination thereof. The data tagging system 100 may include one or more of a server 110, a network 120, a service requester terminal 130, a service provider terminal 140, and a database 150, and a processor executing instruction operations may be included in the server 110.

In some embodiments, the server 110 may be a single server or a group of servers. The server farm may be centralized or distributed (e.g., server 110 may be a distributed system). In some embodiments, the server 110 may be local or remote to the terminal. For example, the server 110 may access information and/or data stored in the service requester terminal 130, the service provider terminal 140, or the database 150, or any combination thereof, via the network 120. As another example, the server 110 may be directly connected to at least one of the service requester terminal 130, the service provider terminal 140, and the database 150 to access stored information and/or data. In some embodiments, server 110 may be implemented on a cloud platform; for example only, the cloud platform may include a private cloud, public cloud, hybrid cloud, community cloud (community cloud), distributed cloud, inter-cloud (inter-cloud), multi-cloud (multi-cloud), and the like, or any combination thereof. In some embodiments, server 110 may be implemented on an electronic device 200 having one or more of the components shown in FIG. 2 of the present application.

In some embodiments, server 110 may include a processor. The processor may process information and/or data related to the service request to perform one or more of the functions described in the present application. For example, the processor may determine the target vehicle based on a service request obtained from the service requester terminal 130. In some embodiments, a processor may include one or more processing cores (e.g., a single core processor (S) or a multi-core processor (S)). By way of example only, the Processor may include a central processing unit (Central Processing Unit, CPU), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), special instruction set Processor (Application Specific Instruction-set Processor, ASIP), graphics processing unit (Graphics Processing Unit, GPU), physical processing unit (Physics Processing Unit, PPU), digital signal Processor (Digital Signal Processor, DSP), field programmable gate array (Field Programmable Gate Array, FPGA), programmable logic device (Programmable Logic Device, PLD), controller, microcontroller unit, reduced instruction set computer (Reduced Instruction Set Computing, RISC), microprocessor, or the like, or any combination thereof.

Network 120 may be used for the exchange of information and/or data. In some embodiments, one or more components in the data tagging system 100 (e.g., the server 110, the service requester terminal 130, the service provider terminal 140, and the database 150) may send information and/or data to other components. For example, the server 110 may obtain a service request from the service requester terminal 130 via the network 120. In some embodiments, network 120 may be any type of wired or wireless network, or a combination thereof. By way of example only, the network 120 may include a wired network, a wireless network, a fiber optic network, a telecommunications network, an intranet, the internet, a local area network (Local Area Network, LAN), a wide area network (Wide Area Network, WAN), a wireless local area network (Wireless Local Area Networks, WLAN), a metropolitan area network (Metropolitan Area Network, MAN), a wide area network (Wide Area Network, WAN), a public switched telephone network (Public Switched Telephone Network, PSTN), a bluetooth network, a ZigBee network, a near field communication (Near Field Communication, NFC) network, or the like, or any combination thereof. In some embodiments, network 120 may include one or more network access points. For example, network 120 may include wired or wireless network access points, such as base stations and/or network switching nodes, through which one or more components of data tagging system 100 may connect to network 120 to exchange data and/or information.

In some embodiments, the user of the service requester terminal 130 may be a person other than the actual consumer of the service. For example, user a of service requester terminal 130 may use service requester terminal 130 to initiate a service request for service actual requester B (e.g., user a may call his own friend B), or receive service information or instructions from server 110, etc. In some embodiments, the user of the service provider terminal 140 may be the actual service provider or may be a person other than the actual service provider. For example, user C of service provider terminal 140 may use service provider terminal 140 to receive a service request for providing a service by service actual provider D (e.g., user C may pick up for driver D employed by himself), and/or information or instructions from server 110. In some embodiments, "service requester" and "service requester terminal" may be used interchangeably and "service provider" and "service provider terminal" may be used interchangeably.

In some embodiments, the service requester terminal 130 may include a mobile device, a tablet computer, a laptop computer, or a built-in device in a motor vehicle, or the like, or any combination thereof. In some embodiments, the mobile device may include a smart home device, a wearable device, a smart mobile device, a virtual reality device, or an augmented reality device, or the like, or any combination thereof. In some embodiments, the smart home device may include a smart lighting device, a control device for a smart appliance device, a smart monitoring device, a smart television, a smart video camera, or an intercom, or the like, or any combination thereof. In some embodiments, the wearable device may include a smart bracelet, a smart lace, a smart glass, a smart helmet, a smart watch, a smart garment, a smart backpack, a smart accessory, etc., or any combination thereof. In some embodiments, the smart mobile device may include a smart phone, a personal digital assistant (Personal Digital Assistant, PDA), a gaming device, a navigation device, or a point of sale (POS) device, or the like, or any combination thereof. In some embodiments, the virtual reality device and/or the augmented reality device may include a virtual reality helmet, a virtual reality glass, a virtual reality patch, an augmented reality helmet, an augmented reality glass, an augmented reality patch, or the like, or any combination thereof. For example, the virtual reality device and/or the augmented reality device may include various virtual reality products, and the like. In some embodiments, the built-in devices in the motor vehicle may include an on-board computer, an on-board television, and the like. In some embodiments, the service requester terminal 130 may be a device having location technology for locating the location of the service requester and/or service requester terminal.

In some embodiments, the service provider terminal 140 may be a similar or identical device to the service requester terminal 130. In some embodiments, the service provider terminal 140 may be a device with positioning technology for locating the location of the service provider and/or service provider terminal. In some embodiments, the service requester terminal 130 and/or the service provider terminal 140 may communicate with other positioning devices to determine the location of the service requester, the service requester terminal 130, the service provider, or the service provider terminal 140, or any combination thereof. In some embodiments, the service requester terminal 130 and/or the service provider terminal 140 may send the positioning information to the server 110.

Database 150 may store data and/or instructions. In some embodiments, database 150 may store data obtained from service requester terminal 130 and/or service provider terminal 140. In some embodiments, database 150 may store data and/or instructions for the exemplary methods described in the present disclosure. In some embodiments, database 150 may include mass storage, removable storage, volatile Read-write Memory, or Read-Only Memory (ROM), or the like, or any combination thereof. By way of example, mass storage may include magnetic disks, optical disks, solid state drives, and the like; removable memory may include flash drives, floppy disks, optical disks, memory cards, zip disks, magnetic tape, and the like; the volatile read-write memory may include random access memory (Random Access Memory, RAM); the RAM may include dynamic RAM (Dynamic Random Access Memory, DRAM), double data Rate Synchronous dynamic RAM (DDR SDRAM); static Random-Access Memory (SRAM), thyristor RAM (T-RAM) and Zero-capacitor RAM (Zero-RAM), etc. By way of example, ROM may include Mask Read-Only Memory (MROM), programmable ROM (Programmable Read-Only Memory, PROM), erasable programmable ROM (Programmable Erasable Read-Only Memory, PEROM), electrically erasable programmable ROM (Electrically Erasable Programmable Read Only Memory, EEPROM), compact disk ROM (CD-ROM), digital versatile disk ROM, and the like. In some embodiments, database 150 may be implemented on a cloud platform. For example only, the cloud platform may include a private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, cross-cloud, multi-cloud, or other similar, or the like, or any combination thereof.

In some embodiments, database 150 may be connected to network 120 to communicate with one or more components in data tagging system 100 (e.g., server 110, service requester terminal 130, service provider terminal 140, etc.). One or more components in the data tagging system 100 may access data or instructions stored in the database 150 via the network 120. In some embodiments, database 150 may be directly connected to one or more components in data tagging system 100 (e.g., server 110, service requester terminal 130, service provider terminal 140, etc.); alternatively, in some embodiments, database 150 may also be part of server 110.

In some embodiments, one or more components in the data tagging system 100 (e.g., the server 110, the service requester terminal 130, the service provider terminal 140, etc.) may have access to the database 150. In some embodiments, one or more components in the data tagging system 100 may read and/or modify information related to a service requester, a service provider, or the public, or any combination thereof, when certain conditions are met. For example, server 110 may read and/or modify information of one or more users after receiving a service request. As another example, the service provider terminal 140 may access information related to the service requester upon receiving a service request from the service requester terminal 130, but the service provider terminal 140 may not modify the related information of the service requester.

In some embodiments, the exchange of information of one or more components in the data tagging system 100 may be accomplished through a request service. The object of the service request may be any product. In some embodiments, the product may be a tangible product or a non-physical product. The tangible product may include a food, a pharmaceutical, a merchandise, a chemical product, an appliance, a garment, an automobile, a house, a luxury item, or the like, or any combination thereof. The non-substance product may include a service product, a financial product, a knowledge product, an internet product, or the like, or any combination thereof. The internet product may include a host product alone, a web product, a mobile internet product, a commercial host product, an embedded product, or the like, or any combination thereof. The internet product may be used in software, a program, a system, etc. of the mobile terminal, or any combination thereof. The mobile terminal may include a tablet computer, a notebook computer, a mobile phone, a personal digital assistant (Personal Digital Assistant, PDA), a smart watch, a Point of sale (POS) device, a car computer, a car television, or a wearable device, or the like, or any combination thereof. For example, the internet product may be any software and/or application used in a computer or mobile phone. The software and/or applications may involve social, shopping, shipping, entertainment time, learning, or investment, or the like, or any combination thereof. In some embodiments, the transportation related software and/or applications may include travel software and/or applications, vehicle scheduling software and/or applications, drawing software and/or applications, and the like. In the vehicle scheduling software and/or applications, the vehicle may include horses, dollies, rickshaw (e.g., wheelbarrows, bicycles, tricycles, etc.), automobiles (e.g., taxis, buses, private cars, etc.), trains, subways, watercraft, aircraft (e.g., aircraft, helicopters, space shuttles, rockets, hot air balloons, etc.), and the like, or any combination thereof.

Fig. 2 shows a schematic diagram of exemplary hardware and software components of an electronic device 200 of a server 110, a service requester terminal 130, a service provider terminal 140, which may implement the inventive concepts according to some embodiments of the application. For example, a processor may be used on electronic device 200 and to perform functions in the present application.

The electronic device 200 may be a general purpose computer or a special purpose computer, both of which may be used to implement the data tagging method of the present application. Although only one computer is shown, the functionality described herein may be implemented in a distributed fashion across multiple similar platforms for convenience to balance processing loads.

For example, the electronic device 200 may include a network port 210 connected to a network, one or more processors 220 for executing program instructions, a communication bus 230, and various forms of storage media 240, such as magnetic disk, ROM, or RAM, or any combination thereof. By way of example, the computer platform may also include program instructions stored in ROM, RAM, or other types of non-transitory storage media, or any combination thereof. The method of the present application may be implemented in accordance with these program instructions. The electronic device 200 also includes an Input/Output (I/O) interface 250 between the computer and other Input/Output devices (e.g., keyboard, display screen).

For ease of illustration, only one processor is depicted in the electronic device 200. It should be noted, however, that the electronic device 200 of the present application may also include multiple processors, and thus, steps performed by one processor described in the present application may also be performed jointly by multiple processors or separately. For example, if the processor of the electronic device 200 performs steps a and B, it should be understood that steps a and B may also be performed by two different processors together or performed separately in one processor. For example, the first processor performs step a, the second processor performs step B, or the first processor and the second processor together perform steps a and B.

Example two

The embodiment provides a data marking method. The method of this embodiment may be performed by the server 110 shown in fig. 1, or may be performed by a device communicatively coupled to the database 150. FIG. 3 shows a flow chart of a data tagging method in one embodiment of the application. The flow of the data marking method shown in fig. 3 is described in detail below.

In step S301, the completed target order data is obtained from the order server.

The target order data carries an initial label.

The order data may be any type of order that requires a party to provide service, a party to receive service, such as a network-bound vehicle order, a takeout order, a taxi order, a network purchase order, etc.

The target order data may include: order end time, order start time, order service parameters, etc. The order end time may be the time when the order is cancelled or the order service completion time.

The tags include liability tags, rewards tags, attribute tags, and the like. Wherein, the responsibility label includes: service provider responsibility and service requester responsibility. The bonus tag includes: a bonus service provider and a bonus service requester. The attribute tags may include: categorizing the service provider and categorizing the service requestor. The following description will be mainly made by taking responsibility tags as examples.

Step S302, order related operation data submitted by the service requester terminal and/or the service provider terminal is obtained.

The order related operation data may be operation data submitted by a service provider or operation data submitted by a service requester.

In an implementation manner, the order data in step S301 may carry order related operation data, and when the order data needs to be used, the order related operation data may be obtained by analyzing the order data.

In another implementation, the order related operations may also be stored in a database server, and when needed, the order related operations are obtained in the database server by using the order identification in the order data as a query standard.

In yet another implementation, the order related operations may also be data submitted in real time by the service requester terminal and/or the service provider terminal.

The order related operations may include operations prior to order cancellation, operations at the completion of the order, and operations for a period of time after the completion of the order.

In one embodiment, step S302 may include: first cancellation operation data of cancellation orders sent by a service requester terminal are obtained.

The first cancel operation data represents data submitted at the time of the cancel operation of the service requester terminal.

The first cancellation operation may be a cancellation operation performed by the service provider for a period of time before the service provider provides the service after the service provider receives the order of the service requester.

Further, the service requester may also select a corresponding cancellation reason before submitting the cancellation operation. Reasons include, but are not limited to, 1) self-cause; 2) Service provider reasons, etc.

Further, prior to submitting the cancellation operation, the service requestor may further include selecting whether to complain about the service provider.

The first cancel operation data may include: cancel reasons, complaint service provider data, etc.

In another embodiment, step S302 may include: second cancel operation data of the cancel order sent by the service provider terminal is acquired.

The second cancel operation data described above may represent data submitted at the time of the cancel operation of the service provider terminal.

The second cancel operation may be a cancel operation of the service provider terminal after receiving the order submitted by the service requester.

The second cancel operation data may include: cancel cause, complaint service requester data, etc.

In other embodiments, the order related operations described above may include: and after the order is ended, the service requester terminal or the service provider terminal submits complaint data.

Step S303, assigning values to the parameters matched with the target order data according to the order related operation data to obtain attribute parameters.

The order related operational data may include data submitted by the service requester terminal or may include data submitted by the service provider terminal.

In an embodiment, step S303 may include: judging whether the service requester terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the first cancel operation data; if yes, a first class value is given to the abnormal operation parameters of the service request party of the target order data.

In one example, the first cancel operation data is data submitted by the service provider terminal on 1 st 2018 at 10:00:00 am; the time period corresponding to the first cancel operation data may be expressed as ten minutes before 2018, 1 month and 1 day, and 10:00:00 am.

The first type of values described above may be represented as true values and the second type of values may be represented as false values. In one example, the first class value may be 1 and the second class value may be 0.

The above-mentioned set number of times may be five times, seven times, or the like. The setting times can be selected according to the time period, for example, if the matching time period is longer, the setting times of the matching are correspondingly more; the matching time period is shorter, and the matching setting times are correspondingly smaller.

If the service requester terminal submits an order a plurality of times within a period of time and cancels the order which is not started a plurality of times, the abnormal operation possibly exists in the current order. For example, if a service requester terminal submitted five orders within ten minutes and all of the five orders were cancelled, the cancellation operation of all of the five orders cancelled within the ten minutes may be regarded as an abnormal operation.

Whether the corresponding cancel operation is abnormal operation or not is judged by the frequency of canceling the order, and if not, feedback information carried by the first cancel operation data can be further identified.

In another embodiment, step S303 may include: judging whether the service requester terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the first cancel operation data; if not, acquiring service requester feedback information carried in the first cancellation operation data; and assigning a value to the parameter matched with the feedback information of the service requester.

The feedback information may include cancellation reasons, complaint information, and the like.

In some embodiments, the step of assigning a value to a parameter that matches the service requester feedback information includes: if the service requester feedback information comprises self responsibility data, assigning a first class value for the responsibility parameters of the service requester; or if the feedback information comprises complaint data, assigning a first class value to the responsibility parameter of the service provider.

In the network vehicle-contract field, the self-responsibility data may include: the cancellation of the selection is due to: the platform is sent too far away, the journey has change, and time is more urgent to transfer other vehicles, etc., corresponding cancellation operation data. The complaint data may include: the cancellation of the selection is due to: the driver has various reasons of not receiving me, refusing to receive the call, and corresponding cancellation operation data when the driver is late. The complaint data also includes complaint operation data submitted by the service requester terminal, and the like.

In one example, a parameter may be matched for each cancellation order cause, each feedback submitted by the service requester terminal or the service provider terminal, respectively, and after the corresponding cancellation order cause is selected, a first class value may be assigned to the corresponding parameter. For example, the parameters may include: the method comprises the following steps of enabling various reasons of a driver not to receive I parameters, enabling the driver to refuse to receive calls, enabling the driver to delay to get to the platform, enabling the platform to send the car too far, enabling the platform to have a path to change parameters, enabling the time to be compared with the time to be in urgent transfer with other vehicle parameters, and enabling corresponding parameters to be given a first type value when any one of the reasons is selected. For example, if the cancellation submitted by the service requester terminal is that there is a change in the journey, the journey change parameter is given to the first type value.

In another example, the parameters may include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider. The following parameters may include: the responsibility parameters of the service provider, the responsibility parameters of the service requester, the abnormal operation parameters of the service requester, and the abnormal operation parameters of the service provider are described as examples.

In one example, if the feedback information is the cause of the service requester itself, the responsibility parameter of the service requester is correspondingly given a true value. For example, the responsibility parameters of the service requester are denoted with Passenger responsibility, passenger responsibility =1 may be used.

In another example, if the feedback information is the cause of the service provider, the responsibility parameter correspondence of the service provider is given a true value. For example, if the responsibility parameter of the service provider uses Driver's response reliability, driver's response reliability=1 may be used.

In another example, if the feedback information is complaining about the service provider, the responsibility parameter correspondence of the service provider is given a true value. For example, if the responsibility parameter of the service provider uses Driver's response reliability, driver's response reliability=1 may be used.

In another embodiment, step S303 may include: judging whether the service provider terminal submits cancel operation data exceeding the set times in a time period corresponding to the second cancel operation data submitted by the service provider; if yes, a first class value is given to the abnormal operation parameters of the service provider of the target order data.

If the service provider terminal submits an order multiple times within a period of time and cancels an order which does not start multiple times, the abnormal operation possibly exists in the current order. For example, if a service provider terminal submitted five orders within ten minutes and all of the five orders were cancelled, the cancellation operation of all of the five orders cancelled within the ten minutes may be regarded as an abnormal operation.

Whether the corresponding cancel operation is abnormal operation or not is judged through the frequency of canceling the order, and if not, feedback information carried by the second cancel operation data can be further identified.

In another embodiment, step S303 may include: judging whether the service provider terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the second cancel operation data; if not, acquiring service provider feedback information carried in the second canceling operation data; and assigning a value to the parameter matched with the feedback information of the service provider.

In another embodiment, step S303 may include: judging whether the service provider terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the second cancel operation data; if not, judging whether the service provider terminal has a communication record of the terminal bound with the background server side before the second cancel operation data; if not, a first class of values is assigned to the responsibility parameters of the service provider.

The terminal bound by the server side can be a telephone of a background customer service person.

If the service provider calls a background customer service personnel before the order is cancelled, and the reason for the need of cancelling the order is stated, a second class value can be given to the responsibility parameters of the service provider; if the service provider does not call the background customer service personnel before the order is cancelled, a first class value is given to the responsibility parameters of the service provider.

In another embodiment, step S303 may include: judging whether the service provider terminal submits cancel operation data exceeding a set number of times in a time period corresponding to the second cancel operation data; if not, judging whether the service provider terminal has a communication record with the service requester terminal before the second cancel operation data; if not, a first class of values is assigned to the responsibility parameters of the service provider.

If the service provider terminal directly cancels the order under the condition that the service provider terminal does not communicate with the service requester terminal, and the service requester can not know the cancellation of the order in advance, a first class value is given to the responsibility parameters of the service provider; if the service provider terminal cancels the order under the condition that the service provider terminal tries to communicate with the service requester terminal but is not successfully connected, the second class value is given to the responsibility parameters of the service provider.

Step S304, judging whether the attribute parameters are matched with the attributes of the initial labels of the target order data.

If yes, step S305 is performed. If not, deleting the corresponding order data, and not taking the corresponding order data as a sample of the subsequent training data.

In some embodiments, the parameters include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider; step S304 may include:

In an alternative embodiment, each parameter may correspond to a type, where the type may include: service provider responsibility class, service requester responsibility class.

For example, the parameters described above include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider.

The responsibility parameters of the service provider and the abnormal operation parameters of the service provider may belong to the responsibility class of the service provider; the responsibility parameters of the service requester and the abnormal operation parameters of the service requester belong to the responsibility class of the service requester.

In one example, if the tag carried by the target order data is the responsibility of the service provider; and if any parameter in the responsibility class of the service provider is a first class value, the attribute parameter is matched with the attribute of the initial label of the target order data.

In one example, if the tag carried by the target order data is the responsibility of the service provider; and if the attribute parameter is the second class value of all the parameters in the responsibility class of the service provider or/and if the attribute parameter is the first class value of any one of the parameters in the responsibility class of the service requester, the attribute parameter is not matched with the attribute of the initial label of the target order data.

In one example, if the tag carried by the target order data is the responsibility of the service requester; and if any parameter in the responsibility class of the service requester is a first class value, the attribute parameter is matched with the attribute of the initial label of the target order data.

In one example, if the tag carried by the target order data is the responsibility of the service requester; and if the attribute parameter is the second class value of all the parameters in the responsibility class of the service requester, or/and if the attribute parameter is the first class value of any one of the parameters in the responsibility class of the service requester, the attribute parameter is not matched with the attribute of the initial label of the target order data.

Step S305, setting a target label identical to the initial label for the target order data.

Order data with attribute parameters matching the attributes of the initial tag of the target order data may be used as training data for subsequent training of the model.

The label of the obtained order data can be more accurate through the initial label and the subsequent confirmation label, and the model obtained through subsequent training can also more meet the training requirement.

The following provides a pseudo code schematic of an algorithm flow corresponding to the data mark by taking a network bus as an example:

/>

Example III

Based on the same application conception, the embodiment of the application also provides a data marking device corresponding to the data marking method, and because the principle of solving the problem by the device in the embodiment of the application is similar to that of the data marking method in the embodiment of the application, the implementation of the device can refer to the implementation of the method, and the repetition is omitted.

Fig. 4 is a block diagram illustrating a data marking apparatus implementing functions corresponding to the steps performed by the above-described method according to some embodiments of the present application. The device may be understood as the above server, or the processor of the server, or may be understood as a component, independent of the above server or processor, that implements the functions of the present application under the control of the server, and as shown in the figure, the data marking device may include: a first acquisition module 401, a second acquisition module 402, an assignment module 403, a judgment module 404, and a setting module 405, wherein,

a first obtaining module 401, configured to obtain completed target order data from an order server, where the target order data carries an initial tag;

a second obtaining module 402, configured to obtain order related operation data submitted by the service requester terminal and/or the service provider terminal;

the assignment module 403 is configured to assign a value to the parameter matched with the target order data according to the order related operation data, so as to obtain an attribute parameter;

a determining module 404, configured to determine whether the attribute parameter matches an attribute of the initial tag of the target order data;

and the setting module 405 is configured to set, for the target order data, a target label identical to the initial label if the attribute parameter matches the attribute of the initial label of the target order data.

In some embodiments, the second obtaining module 402 is further configured to: acquiring first cancellation operation data of cancellation orders sent by a service requester terminal;

the assignment module 403 is further configured to:

In some embodiments, the second acquisition module 402 is further configured to:

the assignment module 403 is further configured to:

In some embodiments, the assignment module 403 is further configured to:

In some embodiments, the second obtaining module 402 is further configured to:

the assignment module 403 is further configured to:

In some embodiments, the second obtaining module 402 is further configured to:

the assignment module 403 is further configured to:

In some embodiments, the second obtaining module 402 is further configured to:

the assignment module 403 is further configured to:

In some embodiments, the second obtaining module 402 is further configured to:

the assignment module 403 is further configured to:

In some embodiments, the parameters include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider; the judging module 404 is further configured to:

The modules may be connected or communicate with each other via wired or wireless connections. The wired connection may include a metal cable, optical cable, hybrid cable, or the like, or any combination thereof. The wireless connection may include a connection through a LAN, WAN, bluetooth, zigBee, or NFC, or any combination thereof. Two or more modules may be combined into a single module, and any one module may be divided into two or more units.

The process flow of each module in the apparatus and the interaction flow between the modules may be described with reference to the related descriptions in the above method embodiments, which are not described in detail herein.

Furthermore, the embodiment of the present application also provides a computer readable storage medium, on which a computer program is stored, which when being executed by a processor, performs the steps of the data marking method described in the above method embodiment.

The computer program product of the data marking method provided by the embodiment of the present application includes a computer readable storage medium storing a program code, where the program code includes instructions for executing the steps of the data marking method described in the above method embodiment, and specifically, reference may be made to the above method embodiment, and details thereof are not repeated herein.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the method embodiments, and are not repeated in the present disclosure. In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, and the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, and for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, indirect coupling or communication connection of devices or modules, electrical, mechanical, or other form.

The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims

1. A method of marking data, comprising:

2. The method of claim 1, wherein the step of obtaining order related operational data submitted by the service requester terminal and/or the service provider terminal comprises:

3. The method of claim 1, wherein the step of obtaining order related operational data submitted by the service requester terminal and/or the service provider terminal comprises:

4. The method of claim 3, wherein the step of assigning a value to a parameter that matches the service requester feedback information comprises:

5. The method of claim 1, wherein the step of obtaining order related operational data submitted by the service requester terminal and/or the service provider terminal comprises:

6. The method of claim 1, wherein the step of obtaining order related operational data submitted by the service requester terminal and/or the service provider terminal comprises:

7. The method of claim 1, wherein the step of obtaining order related operational data submitted by the service requester terminal and/or the service provider terminal comprises:

8. The method of claim 1, wherein the step of obtaining order related operational data submitted by the service requester terminal and/or the service provider terminal comprises:

9. The method of any of claims 1-8, wherein the tag comprises: service provider responsibility and service requester responsibility; the parameters include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider; the step of judging whether the attribute parameter matches the attribute of the initial tag of the target order data includes:

10. A data marking apparatus, comprising:

11. The apparatus of claim 10, wherein the second acquisition module is further to: acquiring first cancellation operation data of cancellation orders sent by a service requester terminal;

the assignment module is further configured to:

12. The apparatus of claim 10, wherein the second acquisition module is further to:

the assignment module is further configured to:

13. The apparatus of claim 12, wherein the assignment module is further to:

14. The apparatus of claim 10, wherein the second acquisition module is further to:

The assignment module is further configured to:

15. The apparatus of claim 10, wherein the second acquisition module is further to:

the assignment module is further configured to:

16. The apparatus of claim 10, wherein the second acquisition module is further to:

the assignment module is further configured to:

17. The apparatus of claim 10, wherein the second acquisition module is further to:

the assignment module is further configured to:

18. The apparatus of any of claims 10-17, wherein the parameters include: responsibility parameters of the service provider, responsibility parameters of the service requester, abnormal operation parameters of the service requester, and abnormal operation parameters of the service provider; the judging module is further configured to:

19. An electronic device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory in communication over the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the steps of the method of any of claims 1 to 9.

20. A computer-readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, performs the steps of the method according to any of claims 1 to 9.