A management method and system for information reported by travel users

Abstract

The embodiments of this specification provide a method and system for managing information reported by travel users, which evaluates the validity of user-reported information in combination with real road condition information and user credit information. The validity of user-reported information is in turn used to update user credit information, thereby forming an automated user-generated content value closed loop. In this disclosure, the collection, storage, use, processing, transmission, provision and presentation of relevant information are all in compliance with the provisions of relevant laws and regulations, do not infringe on the privacy of others, and do not violate public order and good customs.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a method and system for managing information reported by travel users. Background Art

[0002] Users of travel platforms can report some information to the platform for use by the platform. For example, online car-hailing drivers and passengers can report traffic incidents encountered on the road, such as traffic accidents, traffic control, road construction, etc. to the online car-hailing platform. The online car-hailing platform can share the user's reported information with other users. However, the validity of the reported information needs to be ensured before it can be used to avoid being misled by false or even false information. Summary of the invention

[0003] The embodiments of this specification provide a method and system for managing information reported by travel users, which evaluates the effectiveness of user-reported information in combination with real road condition information and user credit information. The effectiveness of user-reported information is in turn used to update user credit information, thereby forming an automated UGC (User Generated Content) value closed loop, which can save labor costs, improve the recognition accuracy of user-reported information, and solve the problem of difficulty in identifying user-reported information.

[0004] One of the embodiments of the present specification provides a method for managing information reported by travel users, including: obtaining the user's reported information and its corresponding target geographic location; obtaining real road condition information of the target geographic location; obtaining the user's current credit information; evaluating the validity of the reported information based on the reported information, the real road condition information and the credit information; and updating the user's current credit information based on the validity of the reported information.

[0005] One of the embodiments of the present specification provides a management system for reporting information of a travel user, including an acquisition module, an evaluation module and an update module. The acquisition module is used to: acquire the user's reported information and its corresponding target geographic location; acquire the real road condition information of the target geographic location; and acquire the user's current credit information; the evaluation module is used to evaluate the validity of the reported information based on the reported information, the real road condition information and the credit information; the update module is used to update the user's current credit information based on the validity of the reported information.

[0006] One of the embodiments of the present specification provides a management device for travel user reported information, including a processor and a storage device, wherein the storage device is used to store instructions. When the processor executes the instructions, a management method for travel user reported information as described in any embodiment of the present specification is implemented.

[0007] One of the embodiments of this specification provides a computer-readable storage medium, characterized in that computer instructions are stored in the storage medium. When a computer reads the computer instructions in the storage medium, it executes the method for managing travel user reporting information as described in any embodiment of this specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein:

[0009] Figure 1 is a schematic diagram of an application scenario of a travel system according to some embodiments of this specification;

[0010] Figure 2 is an exemplary module diagram of a management system for reporting information of travel users according to some embodiments of this specification;

[0011] Figure 3 is an exemplary flow chart of a method for managing information reported by travel users according to some embodiments of this specification;

[0012] Figure 4 is an exemplary flow chart of a method for managing information reported by travel users according to other embodiments of this specification;

[0013] Figure 5 This is an exemplary flowchart for evaluating the validity of user reported information according to some embodiments of this specification. DETAILED DESCRIPTION

[0014] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of this specification. For ordinary technicians in this field, this specification can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0015] It should be understood that the "system", "device", "unit" and / or "module" used herein are a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

[0016] As shown in this specification, unless the context clearly indicates an exception, the words "a", "an", "a kind" and / or "the" do not refer to the singular, but also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0017] Flowcharts are used in this specification to illustrate the operations performed by the system according to the embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed precisely in order. Instead, the steps may be processed in reverse order or simultaneously. At the same time, other operations may also be added to these processes, or one or more operations may be removed from these processes.

[0018] The technical solutions of the embodiments of this specification, if they involve the processing of personal information, will be processed on the premise of having a legal basis (for example, obtaining the consent of the subject of personal information, or being necessary for the performance of a contract, etc.), and will only be processed within the prescribed or agreed scope. The user's refusal to process personal information other than the necessary information required for basic functions will not affect the user's use of basic functions. The collection, storage, use, processing, transmission, provision and presentation of relevant information shall comply with the provisions of relevant laws and regulations, do not infringe on the privacy of others, and do not violate public order and good customs.

[0019] In this specification, the terms "user" and "user end" can be used interchangeably without causing confusion.

[0020] Figure 1 It is a schematic diagram of an application scenario of a travel system according to some embodiments of this specification.

[0021] like Figure 1 As shown, the travel system 100 may include a user end 110 , a service end 120 , a network 130 and a storage device 140 .

[0022] The user end 110 may obtain travel services from the service end 120. In some embodiments, the travel services may include taxi services, navigation services, map services, chauffeur services, and the like.

[0023] The client 110 may send data and / or information to the server 120 , and receive data and / or information from the server 120 .

[0024] In some embodiments, the user terminal 110 may send a service request to the server terminal 120 and receive a service response returned by the server terminal 120. For example, a passenger may initiate a taxi service request through the user terminal 110. After receiving the request, the server terminal 120 allocates a vehicle to the passenger and sends a service response including the vehicle license plate, driver information, price information, etc. to the passenger.

[0025] In some embodiments, the user terminal 110 may report information to the server terminal 120, or receive information reported by other user terminals from the server terminal 120. For example, a driver / passenger may report the road congestion conditions (such as smooth driving, slow driving, general congestion, extreme congestion) of the current road section and / or traffic events (such as traffic accidents, traffic control, construction ahead) occurring on the current road section through the user terminal 110, and may also obtain road congestion conditions and / or traffic events reported by other users through the user terminal 110.

[0026] In some embodiments, the user terminal 110 may include one or more of a vehicle computer (such as 110-1), a smart phone (such as 110-2), a wearable device, a tablet computer, etc. In some embodiments, the user terminal 110 may provide various user input methods, such as key input, touch input, voice recognition, gesture recognition, etc.

[0027] The service end 120 can provide travel services to the user end 110, and is sometimes also referred to as a "travel platform" or "platform".

[0028] The server 120 may send data and / or information to the client 110 , and receive data and / or information from the client 110 .

[0029] In some embodiments, the server 120 may receive a service request from the user terminal 110 and return a service response to the user terminal 110. For example, the server 120 may receive a taxi service request initiated by a passenger through the user terminal 110, allocate a vehicle to the passenger, and send a service response including a vehicle license plate, driver information, price information, etc. to the passenger.

[0030] In some embodiments, the server 120 may receive the user's report information. In some embodiments, the server 120 may share the user's valid report information with other users. In some embodiments, the server 120 may issue reminders to other users based on the user's valid report information. As an example only, if user A uploads a traffic accident that occurred on road section L and the traffic accident is evaluated as valid by the platform, the platform may push the traffic accident to other users who are about to enter road section L for their reference, or may remind other users that there is a traffic accident on road section L and they need to take a detour.

[0031] The server 120 may also process data and / or information generated in the travel system 100 .

[0032] In some embodiments, the server 120 may analyze the data collected by the vehicle-related devices (not shown) to obtain the real road condition information. The devices here may include auxiliary driving systems, sensors, radars, cameras, driving recorders, etc. In other embodiments, the server 120 may also directly call the real road condition information obtained by the external system (such as analyzed).

[0033] In some embodiments, the server 120 can evaluate the validity of the user's reported information based on the user's reported information and the real road condition information. In some embodiments, the server 120 can perform data mining based on the user's valid (real) reported information, and the data mining results can be fed back to the user. For example, the number of traffic accidents that occurred on a certain road section during a period of time can be counted based on the user's reported information within a period of time. If the number exceeds a set threshold, the road section can be marked as a road section with frequent accidents, and then the user who is about to enter the road section can be reminded (notified) that "the dangerous road section ahead, pay attention to driving safety."

[0034] In some embodiments, the server 120 may establish a user credit system, which includes the credit information of each user. The server may maintain the credit system (update the user's credit information) according to the validity of the user's reported information, so as to evaluate the validity of the user's reported information in combination with the user's credit information.

[0035] The network 130 can facilitate the exchange of information and / or data in the travel system 100. In some embodiments, one or more components of the travel system 100 (e.g., the user end 110, the service end 120, and the storage device 140) can transmit information and / or data to one or more other components of the travel system 100 via the network 130. For example, the user end 110 can send a service request to the service end 120 via the network 130, and the service end 120 can return a service response to the user end 110 via the network 130. For another example, the user end 110 can report information to the service end 120 via the network 130, and can obtain the reported information of other users via the network 130. For another example, the vehicle-related device can save the collected data to the storage device 140 or send it to the service end 120 via the network 130, and the service end 120 can receive data from the vehicle-related device via the network 130. For another example, the service end 120 can save the reported information marked with validity and / or the updated user credit information to the storage device 140 via the network 130.

[0036] The storage device 140 can store data and / or information from one or more components in the travel system 100. For example, the storage device 140 can store data from vehicle-related devices, reporting information of the validity of the tag from the service end 120, and updated user credit information, etc.

[0037] In some embodiments, the server 120 may be indirectly connected to the storage device 140 via the network 320 , or directly connected to the storage device 140 (indicated by the dotted line). In some embodiments, the storage device 140 may be integrated into the server 120 .

[0038] Figure 2 It is an exemplary module diagram of a management system for travel user reporting information as shown in some embodiments of this specification.

[0039] System 200 can be Figure 1 The server 120 is implemented as shown. Figure 2 As shown, the system 200 may include an acquisition module 210 and an evaluation module 220 .

[0040] The acquisition module 210 can be used to: acquire the user's reported information and its corresponding geographical location; and acquire the real traffic information at the same geographical location.

[0041] The evaluation module 220 may be configured to evaluate the validity of the reported information based at least on the reported information and the actual road condition information.

[0042] In some embodiments, the acquisition module 210 may also be used to acquire the credit information of the user. Accordingly, the evaluation module 220 may be used to evaluate the validity of the reported information based on the reported information, the real road condition information and the credit information. Further, the system 200 may also include an update module 230, which is used to update the current credit information of the user based on the validity of the reported information.

[0043] In some embodiments, the system 200 may further include a feedback module 240. In some embodiments, the feedback module 240 may be used to: in response to the evaluation module 220 evaluating the reported information as valid, share the reported information with other users. In some embodiments, the feedback module 240 may be used to: in response to the evaluation module 220 evaluating the reported information as valid, provide a notification (reminder) to other users according to the reported information.

[0044] More details about the system 200 and its modules can be found elsewhere in this specification and will not be repeated here.

[0045] It should be understood that Figure 2The system and its modules shown can be implemented in various ways. For example, in some embodiments, the system and its modules can be implemented by hardware, software or a combination of software and hardware. Among them, the hardware part can be implemented using dedicated logic; the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or a dedicated design hardware. Those skilled in the art will understand that the above methods and systems can be implemented using computer executable instructions and / or included in a processor control code, such as a carrier medium such as a disk, CD or DVD-ROM, a programmable memory such as a read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. Such code is provided on the system and its modules of this specification. Not only can the hardware circuits such as ultra-large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc. be implemented, it can also be implemented with software such as executed by various types of processors, and it can also be implemented by a combination of the above hardware circuits and software (for example, firmware).

[0046] It should be noted that the above description of the system and its modules is only for the convenience of description, and this specification cannot be limited to the scope of the embodiments. It is understandable that for those skilled in the art, after understanding the principle of the system, it is possible to arbitrarily combine the various modules, or form a subsystem to connect with other modules without deviating from this principle. For example, in some embodiments, the acquisition module 210 and the evaluation module 220 can be different modules in a system, or one module can implement the functions of these two modules. For example, in some embodiments, the acquisition module 210 can be a module, or it can be divided into multiple discrete modules, such as a reporting information acquisition module, a geographic location acquisition module, a real road condition information acquisition module, and a credit information acquisition module. Such variations are all within the scope of protection of this specification.

[0047] Figure 3 It is an exemplary flowchart of a method for managing travel user reporting information according to some embodiments of this specification.

[0048] In some embodiments, process 300 may be performed by Figure 2 The system 200 shown in FIG. 200 can be implemented in Figure 1 The process 300 can be implemented on the server 120 shown in FIG. Figure 1 The server 120 shown in FIG. Figure 3 As shown, process 300 may include the following steps.

[0049] Step 310 , obtaining the user's reported information and its corresponding target geographic location. In some embodiments, step 310 may be performed by the obtaining module 210 .

[0050] In some embodiments, the reported information may reflect road congestion. In some embodiments, the reported information may reflect events, such as traffic incidents, sudden dangers, weather events, etc. In some embodiments, traffic incidents may include one or more of traffic accidents, traffic control, road construction, etc. In some embodiments, sudden dangers may include one or more of mudslides, fires, landslides, damaged bridges, etc. In some embodiments, weather events may include one or more of severe convective weather, thunderstorms, heavy rain, heavy snow, hail, etc. It can be understood that the user's reported information may be information that is of reference value to other users and / or is beneficial to the service end 120 (such as an online car-hailing platform) to provide better services. For this reason, it is necessary to ensure the validity of the user's reported information to avoid misleading information. Taking a traffic accident as an example, when user A encounters a traffic accident on road section L, user A can report the traffic accident to the platform. After the platform verifies (ensures validity), it can issue a reminder to the user who is about to enter road section L, such as "There is a traffic accident on the road ahead, please detour".

[0051] In some embodiments, the user can report information to the server 120 through various input methods provided by the user terminal 110. For example, the driver can input the report information provided to the server 120 through the voice recognition function of the vehicle computer. For another example, the passenger / pedestrian can input the report information provided to the server 120 through the touch keyboard of the mobile device.

[0052] In some embodiments, the user terminal 110 may provide preset tags for reporting information for the user to select, and the preset tags may include road condition tags and / or event tags. For details, please refer to the above examples. In some embodiments, the user terminal 110 / server terminal 120 may identify the user's intention (such as the road condition and / or event that the user wants to report) from the user's original input content (such as voice, text) to obtain the reporting information to be evaluated. The recognition of user intention can be achieved through one or more of the following technologies: machine learning model prediction, semantic recognition, pattern recognition, etc.

[0053] The user's reported information corresponds to time and geographic location, which can be called target time and target geographic location for the convenience of description.

[0054] The target time is the time corresponding to the road condition or event reported by the user, such as a certain moment within the duration of the road condition or event. In practical applications, the time when the reported information is generated by the user terminal 110 or the time when the user terminal receives the original input content of the user can be used as the target time, or the time when the server terminal 120 receives the reported information can be used as the target time.

[0055] The target geographic location is the geographic location where the road condition or event reported by the user occurred. In some embodiments, the user can input the geographic location where the road condition or event to be reported occurred while inputting the original content to generate the reporting information. For example, the user can input the geographic location where he is located (such as "XX intersection") by voice. For another example, the user can select (such as click) the target geographic location in the map application. In some embodiments, the target geographic location can be determined based on the positioning information of the user terminal 110 or the vehicle, for example, the target road section is determined based on the latitude and longitude coordinates of the vehicle.

[0056] Step 320 , obtaining real traffic information of the target geographic location. In some embodiments, step 320 may be performed by the obtaining module 210 .

[0057] The same geographical location here refers to the geographical location corresponding to the information reported by the user in step 310, such as a road section, intersection, landmark, POI (Point of Interest), geographical coordinates, area, etc.

[0058] It is understandable that strictly speaking, it is necessary to obtain the real traffic information of the same time and space (same time and geographical location). However, in actual applications, without affecting the use of the reported information, a time error between the obtained reported information and the real traffic information can be allowed. For example, user A reported a traffic accident at time t1, the platform received the report information corresponding to time t1, and obtained the real traffic information at time t2. When the communication delay and processing delay are low (such as seconds) and the duration of the traffic accident is generally long, the time error t2-t1 can be ignored.

[0059] The real road condition information can reflect the road condition. It should be distinguished that the road condition reflected by the user's reported information is the road condition to be verified (see evaluation step 330), while the real road condition information reflects the real road condition. The road condition may include road congestion and events occurring on the road. Among them, the road congestion may be classified / graded according to actual needs. As an example only, the road condition may be graded into smooth driving, slow driving, general congestion, and extreme congestion.

[0060] In some embodiments, the real road condition can be determined based on information and / or data collected by a real device. The real device here can be a vehicle device, or a device installed at a fixed position in the real environment (such as a speed camera) or an autonomously moving device (such as a drone with a camera). In some embodiments, the real road condition information is generated based on data collected by one or more sensors of a vehicle located at the target geographic location. For example, the one or more sensors can collect the relative distance and relative speed of the vehicle and other surrounding objects (for example, nearby vehicles), so as to reflect the real road condition around the vehicle. For another example, when the trajectory data collected by the auxiliary driving system integrated with multiple sensors shows that the vehicle's driving speed is maintained at a low speed level, it can be determined that the road section where the vehicle is located is in a congested state, wherein the road section where the vehicle is located can be determined by the vehicle positioning information. For another example, it can be determined whether the road section where the vehicle is located is congested based on the speed information collected by the speed sensor over a period of time.

[0061] In some embodiments, one or more of machine learning model prediction, image recognition, pattern recognition, etc. can be used to obtain real road condition information. For example, in some embodiments, the real road condition information can be generated based on driving record images collected by one or more image acquisition devices (such as body cameras, in-vehicle driving recorders) of a vehicle located at the target geographic location.

[0062] It can be understood that the real road condition information can be generated based on data from different sources to improve the reliability of the obtained real road condition. As an example only, in some embodiments, the real road condition information can be generated based on the data collected by the one or more sensors and the driving record images collected by the one or more image acquisition devices, that is, the real road condition can be determined by combining the data collected by (different) sensors and (different) image acquisition devices. Relying on multiple data sources to determine the real road condition can avoid the drawbacks of missing, abnormal, and error data from a single data source and the information provided by a single data source is not enough to accurately analyze the real road condition, which helps to obtain more reliable real road condition information. In a specific implementation, the data collected by multiple data sources can be used as multiple inputs (for example, as multiple inputs of a model), and one output (for example, model output) is obtained after processing as the real road condition information. It is also possible to generate corresponding reference real road condition information based on the data collected by each data source, and then summarize (for example, average, weighted sum) the reference real road condition information corresponding to multiple data sources to obtain the real road condition information. It should be pointed out that this specification does not impose any restrictions on the definition of a single data source. A single sensor, an assisted driving system integrating multiple sensors, or a single image acquisition device can all be regarded as a single data source.

[0063] Step 330 , based on the reported information and the real road condition information, evaluate the validity of the reported information. In some embodiments, step 330 may be performed by the evaluation module 220 .

[0064] It can be understood that when the reported information and the real road condition information are consistent (sufficiently matched), the evaluation module 220 can evaluate the reported information as valid (true), otherwise, the reported information can be evaluated as invalid (such as false, incorrect). Specifically, the consistency (sufficiently matched) here can refer to the road conditions reflected by the reported information and the real road condition information being the same (such as both are extremely congested or both are traffic accidents) or close (such as general congestion and extreme congestion), or it can refer to the existence of a causal relationship between the event reported by the user and the real road congestion (such as traffic accidents causing congestion). In some embodiments, when the evaluation module 220 cannot determine the consistency or matching degree between the reported information and the real road condition information, the validity of the reported information can be evaluated based on other information (such as credit information, the number of identical events, see below for details), or the reported information can be directly evaluated as invalid or unknown in validity.

[0065] In some embodiments, validity evaluation (consistency / matching degree judgment) can be achieved through comparison, rule hitting, machine learning model prediction, etc. The following is an intuitive understanding through some examples. In the comparison mode, when the reported information and the real road condition information both reflect road congestion or events occurring on the road, the evaluation module 220 can calculate the vector distance between the semantic vector of the reported information and the semantic vector of the real road condition information (reflecting the degree of matching between the reported information and the real road condition information). If the vector distance is less than the set threshold, it means that the reported information and the real road condition information are sufficiently matched, and the evaluation module 220 evaluates the reported information as valid. For example, the user reported information is "car accident", and the real road condition information obtained by the platform is "traffic accident". The distance between the semantic vectors of "car accident" and "traffic accident" is less than the set value, and then the evaluation module 220 can evaluate the "car accident" reported by the user as valid. In the rule-hitting mode, several causal relationships can be set. When the reported information and the real road condition information meet any one of the causal relationships, it means that the reported information is consistent with the real road condition information. Accordingly, the evaluation module 220 can evaluate the reported information as valid. For example, the user reported information is "traffic control" and the real road condition information obtained by the platform is "congestion". The two meet the set causal relationship, and then the evaluation module 220 can evaluate the traffic control information reported by the user as valid. In the machine learning model prediction mode, a binary classification model can be trained to identify (predict) whether the input reported information and the real road condition information are consistent. If they are consistent, the evaluation module 220 can evaluate the reported information as valid. Alternatively, a scoring model (which can be regarded as part of the evaluation module 220) can be trained to score the matching degree between the input reported information and the real road condition information. If the score exceeds the set threshold, it means that the reported information and the real road condition information are sufficiently matched, and the evaluation module 220 evaluates the reported information as valid.

[0066] In some embodiments, when the reported information reflects an event reported by a user, the evaluation module 220 can also evaluate the validity of the reported information based on the number of users who report the same event. It should be understood that the same event here refers to an event that occurs in the same time and space. For example, events reported by different users that occur within the same time interval and at the same geographical location can be identified as the same event. In some embodiments, when the number of users who report the same event reaches a set threshold, the evaluation module 220 can evaluate the reported information as valid. It can be understood that the number of users who report the same event reaching a set threshold can serve as a sufficient condition for the reported information reflecting the event to be evaluated as valid, and can also serve as a necessary condition for the reported information reflecting the event to be evaluated as valid.

[0067] Figure 4 is an exemplary flow chart of a method for managing travel user reporting information according to other embodiments of this specification. Figure 3 The process 300 and process 400 shown in the figure introduce a user credit system. Generally speaking, the higher the user's credit, the more credible the information reported by the user is (and the more likely it is to be evaluated as valid).

[0068] In some embodiments, process 400 may be performed by system 200 / server 120. Figure 4 As shown, process 400 may include the following steps.

[0069] Step 410 , obtaining the user's reported information and its corresponding geographical location. In some embodiments, step 410 may be performed by the obtaining module 210 .

[0070] Regarding step 410, please refer to Figure 3 Step 310 and its associated description are shown.

[0071] Step 420 , obtaining real traffic information of the same geographical location. In some embodiments, step 420 may be performed by the obtaining module 210 .

[0072] Regarding step 420, please refer to Figure 3 Step 320 and its associated description are shown.

[0073] Step 430 , obtaining the current credit information of the user. In some embodiments, step 430 may be performed by the obtaining module 210 .

[0074] The user's credit information can reflect the level of the user's credit. In some embodiments, the user's credit information can be labeled. For example, the user's credit can be graded as poor / medium / good (or credible / uncredible), that is, the user's credit information can indicate the user's credit level. In some embodiments, the user's credit information can be numerical. For example, each user can be given an initial credit score, and the user's current credit score can be updated based on the validity of each user's historical reported information (see step 450). It should be understood that the numerical value of the credit information can be consistent with the credit level, or it can be opposite. That is, there are two user credit systems: (1) The higher the numerical value of the user's credit information (which can be regarded as a credit score), the more credible the user is; (2) The lower the numerical value of the user's credit information (which can be regarded as a risk coefficient / probability of default), the more credible the user is. In some embodiments, the numerical value of the user's credit information can have an upper limit and / or a lower limit, for example, the value interval of the credit score can be [0,100], and the value interval of the analysis coefficient can be [0,1]. In addition, each user's credit information can be updated starting from an initial state (such as an initial value or an initial label), the initial value can be between an upper limit and a lower limit (such as 50 in [0,100]), and the initial label can be medium or poor in poor / medium / good (or untrustworthy in trustworthy / untrustworthy).

[0075] Step 440 , based on the reported information, the real road condition information and the credit information, evaluate the validity of the reported information. In some embodiments, step 440 may be performed by the evaluation module 220 .

[0076] In some embodiments, the evaluation module 220 may determine the degree of match between the reported information and the real road condition information, and update the degree of match according to the credit information. Furthermore, the evaluation module 220 may evaluate the validity of the reported information based on the updated degree of match. As an example only, the evaluation module 220 may determine the matching score s between the reported information and the real road condition information, convert the value of the credit information into a weight k according to a certain conversion relationship, and weight (update) the matching score s with the weight k to obtain an updated matching score s′, that is, s′=k*s. Furthermore, the evaluation module 220 may determine whether the updated matching score s′ is greater than a set threshold. If so, the evaluation module 220 may evaluate the reported information as valid. Otherwise, the evaluation module 220 may evaluate the reported information as invalid.

[0077] In some embodiments, the evaluation module 220 may determine whether the user is trustworthy based on the credit information. In response to determining that the user is not trustworthy, the evaluation module 220 may evaluate the validity of the reported information based on the reported information and the real road condition information. Details on the information validity evaluation based on the reported information and the real road condition information can be found in the relevant description of step 330 and will not be repeated here.

[0078] For the numerical credit information, the evaluation module 220 can determine whether the user is untrustworthy by judging whether the credit information satisfies a first threshold condition. When the credit information satisfies the first threshold condition, it indicates that the user is untrustworthy. Specifically, the first threshold condition may include a credit score lower than a set threshold or a risk factor higher than a set threshold.

[0079] For labeled credit information, the evaluation module 220 can determine whether the user is untrustworthy by judging whether the credit information is a first label. When the credit information is a first label, it indicates that the user is untrustworthy. Specifically, the first label can be poor / medium (or untrustworthy) in the credit rating.

[0080] In some embodiments, the evaluation module 220 may determine whether the user is trustworthy based on the credit information. In response to determining that the user is trustworthy, the evaluation module 220 may directly evaluate the reported information as valid.

[0081] For the numerical credit information, the evaluation module 220 can determine whether the user is trustworthy by judging whether the credit information satisfies a second threshold condition. When the credit information satisfies the second threshold condition, it indicates that the user is trustworthy. Specifically, the second threshold condition may include a credit score higher than a set threshold or a risk factor lower than a set threshold.

[0082] For the labeled credit information, the evaluation module 220 can determine whether the user is trustworthy by judging whether the credit information is a second label. When the credit information is a second label, it indicates that the user is trustworthy. Specifically, the second label can be good (or trustworthy) in the credit rating.

[0083] Figure 5 This is an exemplary flowchart for evaluating the validity of user reported information according to some embodiments of this specification.

[0084] like Figure 5As shown, the evaluation module 220 can first determine whether the user is trustworthy. If so, the evaluation module 220 can directly evaluate the user's reported information as valid. Otherwise, the evaluation module 220 can continue to determine whether the user's reported information is consistent with the actual road condition information (for example, whether there is a causal relationship between the event reported by the user and the actual road condition). If so, the evaluation module 220 can evaluate the user's reported information as valid, otherwise, the evaluation module 220 can evaluate the user's reported information as invalid.

[0085] In some embodiments, a machine learning model (binary classification model or scoring model) can also be trained with reference to the method in process 300. The evaluation module 220 can process the reported information, the actual road condition information and the credit information through the trained model to evaluate the validity of the reported information.

[0086] Step 450 : Based on the validity of the reported information, the current credit information of the user is updated. In some embodiments, step 450 may be performed by the updating module 230 .

[0087] In process 400, user credit information is used to evaluate the validity of user-reported information, and the validity of user-reported information is in turn used to update user credit information. In this way, a UGC value closed loop is formed, which can solve the problem of difficulty in identifying user-reported information (difficulty in evaluating the validity of information).

[0088] Under the credit point system, in response to evaluating the reported information as valid, the update module 230 may increase the value (credit point) of the user's current credit information; in response to evaluating the reported information as invalid, the update module 230 may reduce the value (credit point) of the user's credit information. As an example only, each time a valid piece of information reported by the user is increased, the user's credit point may be increased by a preset value (such as 1 point); each time an invalid piece of information reported by the user is increased, the user's credit point may be reduced by the same or more value (such as 1 point or 2 points).

[0089] Under the risk coefficient system, in response to evaluating the reported information as valid, the update module 230 can reduce the value (risk coefficient) of the user's current credit information; in response to evaluating the reported information as invalid, the update module 230 can increase the value (risk coefficient) of the user's credit information. As an example only, whenever a valid piece of information reported by the user is increased, the user's risk coefficient can be increased by a preset value (such as minus 0.1); whenever an invalid piece of information reported by the user is increased, the user's risk coefficient can be increased by the same or more value (such as plus 0.1 or 0.2).

[0090] In some embodiments, the user's current credit information can also be updated regularly or irregularly based on the validity of the information reported by the user in the recent period, that is, the user's credit information is updated once every period of time (such as every month). For example, when the number of valid information reported by the user in the recent period reaches a first threshold and the number of invalid information reported is less than a second threshold, the value of the user's credit information can be increased (such as increasing a preset value) or the user's credit level can be increased (such as from medium to good), where the first threshold is greater than the second threshold; when the number of invalid information reported by the user in the recent period reaches a third threshold and the number of valid information reported is less than a fourth threshold, the value of the user's credit information can be reduced (such as reducing a preset value) or the user's credit level can be reduced (such as from good to medium). For another example, when the ratio M / N of the number of valid information items M reported by a user in a recent period to the number of invalid information items N is greater than a preset ratio (such as 9 / 1), the value of the user's credit information can be increased (such as increasing the preset value) or the user's credit level can be increased (such as from medium to good); when the ratio N / M of the number of invalid information items N reported by a user in a recent period to the number of valid information items M is greater than a preset ratio (such as 9 / 1), the value of the user's credit information can be reduced (such as reducing the preset value) or the user's credit level can be reduced (such as from good to medium). The preset ratio can be greater than 1.

[0091] It should be noted that the above description of the relevant process is only for example and explanation, and does not limit the scope of application of this specification. For those skilled in the art, various modifications and changes can be made to the process under the guidance of this specification. However, these modifications and changes are still within the scope of this specification.

[0092] The beneficial effects that may be brought about by the embodiments of this specification include but are not limited to: (1) Machine identification (evaluation) of the validity of user-reported information can save labor costs and improve the accuracy of identification; (2) By introducing a credit system, the UGC value closed loop is automatically constructed, which can solve the problem of difficulty in identifying user-reported information (difficulty in evaluating the validity of information). It should be noted that different embodiments may produce different beneficial effects. In different embodiments, the beneficial effects that may be produced may be any one or a combination of the above, or any other possible beneficial effects.

[0093] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only for example and does not constitute a limitation on the embodiments of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements and corrections to the embodiments of this specification. Such modifications, improvements and corrections are suggested in the embodiments of this specification, so such modifications, improvements and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0094] At the same time, this specification uses specific words to describe the embodiments of this specification. For example, "one embodiment", "an embodiment" and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different locations in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures or characteristics in one or more embodiments of this specification can be appropriately combined.

[0095] In addition, it will be appreciated by those skilled in the art that the various aspects of the embodiments of this specification may be illustrated and described by a number of patentable categories or situations, including any new and useful process, machine, product or combination of substances, or any new and useful improvements thereto. Accordingly, the various aspects of the embodiments of this specification may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may all be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". In addition, the various aspects of the embodiments of this specification may be represented as a computer product located in one or more computer-readable media, the product including computer-readable program code.

[0096] A computer storage medium may include a propagated data signal containing computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may be in a variety of forms, including electromagnetic, optical, etc., or a suitable combination. A computer storage medium may be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit the program for use. The program code on the computer storage medium may be transmitted via any suitable medium, including radio, cable, fiber optic cable, RF, or similar media, or any combination of the above media.

[0097] The computer program coding required for the operation of each part of the embodiment of this specification can be written in any one or more programming languages, including object-oriented programming languages ​​such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python, etc., conventional procedural programming languages ​​such as C language, VisualBasic, Fortran2003, Perl, COBOL2002, PHP, ABAP, dynamic programming languages ​​such as Python, Ruby and Groovy, or other programming languages, etc. The program coding can be run completely on the user's computer, or run on the user's computer as an independent software package, or partly run on the user's computer and partly run on the remote computer, or run completely on the remote computer or processing equipment. In the latter case, the remote computer can be connected to the user's computer by any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (e.g., by the Internet), or in a cloud computing environment, or used as a service such as software as a service (SaaS).

[0098] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences described in the embodiments of this specification, the use of alphanumeric characters, or the use of other names are not intended to limit the order of the processes and methods of the embodiments of this specification. Although the above disclosure discusses some invention embodiments that are currently considered useful through various examples, it should be understood that such details are only for illustrative purposes, and the attached claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing processing device or mobile device.

[0099] Similarly, it should be noted that in order to simplify the description of the embodiments disclosed in this specification, thereby helping to understand one or more embodiments of the invention, in the above description of the embodiments of this specification, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the objects of the embodiments of this specification are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0100] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, documents, etc., cited in this specification is hereby incorporated by reference in its entirety. Except for application history documents that are inconsistent with or conflicting with the contents of this specification, documents that limit the broadest scope of the claims of this application (currently or later attached to this application) are also excluded. It should be noted that if the descriptions, definitions, and / or use of terms in the materials attached to this specification are inconsistent or conflicting with the contents described in this specification, the descriptions, definitions, and / or use of terms in this specification shall prevail.

[0101] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of the embodiments of this specification. Therefore, as an example and not a limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly introduced and described in this specification.

Claims

1. A method for managing information reported by travel users, characterized in that: include: Obtain the user's reported information and its corresponding target geographic location; Acquire real traffic information of the target geographical location; Obtaining the current credit information of the user; Based on the reported information, the real road condition information and the credit information, evaluating the validity of the reported information specifically includes: Determining the matching degree between the reported information and the real road condition information; According to the credit information, updating the matching degree includes: Determine a matching score between the reported information and the actual road condition information; Determining a weight of the matching score based on the credit information; Based on the weight and the matching score, updating the matching degree; and evaluating the validity of the reported information according to the updated matching degree; Based on the validity of the reported information, the current credit information of the user is updated.

2. The method according to claim 1, characterized in that The reported information includes one or more of traffic accidents, traffic control, and road construction, and the real road condition information reflects the road congestion situation.

3. The method according to claim 1, characterized in that The real road condition information is generated based on data collected by one or more sensors of the vehicle located at the target geographic location and / or driving record images collected by an image acquisition device of the vehicle located at the target geographic location.

4. The method according to claim 1, characterized in that The reported information reflects events reported by users, and the method further includes evaluating the validity of the reported information based on the number of users reporting the same event.

5. The method according to claim 1, characterized in that The evaluating the validity of the reported information based on the reported information, the real road condition information and the credit information includes: Determining whether the credit information satisfies a first threshold condition; when the credit information satisfies the first threshold condition, indicating that the user is not trustworthy; In response to determining that the credit information satisfies the first threshold condition, the validity of the reported information is evaluated based on the reported information and the actual road condition information.

6. The method according to claim 1, characterized in that Also includes: Determining whether the credit information meets a second threshold condition; When the credit information meets the second threshold condition, indicating that the user is trustworthy; In response to determining that the credit information satisfies the second threshold condition, the reported information is evaluated as valid.

7. The method according to claim 1, characterized in that Also includes: In response to evaluating the reported information as being valid, sharing the reported information with other users.

8. The method according to claim 1, characterized in that The updating of the current credit information of the user based on the validity of the reported information includes: In response to evaluating the reported information as valid, increasing the value of the user's current credit information; in response to evaluating the reported information as invalid, decreasing the value of the user's current credit information; wherein a higher value of the credit information indicates that the user is more trustworthy; or In response to evaluating the reported information as valid, the value of the user's current credit information is reduced; in response to evaluating the reported information as invalid, the value of the user's current credit information is increased; wherein, the lower the value of the credit information, the more trustworthy the user is.

9. A management system for travel user reporting information, characterized in that: It includes acquisition module, evaluation module and update module; The acquisition module is used to: acquire the user's reported information and its corresponding target geographical location; acquire the real road condition information of the target geographical location; and, obtaining the current credit information of the user; The evaluation module is used to evaluate the validity of the reported information based on the reported information, the real road condition information and the credit information, specifically including: Determining the matching degree between the reported information and the real road condition information; According to the credit information, updating the matching degree includes: Determine a matching score between the reported information and the actual road condition information; Determining a weight of the matching score based on the credit information; Based on the weight and the matching score, updating the matching degree; and evaluating the validity of the reported information according to the updated matching degree; The updating module is used to update the current credit information of the user based on the validity of the reported information.

10. The system according to claim 9, characterized in that The reported information includes one or more of traffic accidents, traffic control, and road construction, and the real road condition information reflects the road congestion situation.

11. The system according to claim 9, characterized in that The real road condition information is generated based on data collected by one or more sensors of the vehicle located at the target geographic location and / or driving record images collected by an image acquisition device of the vehicle located at the target geographic location.

12. The system according to claim 9, characterized in that The reporting information reflects the event reported by the user, and the evaluation module is further used to evaluate the validity of the reporting information based on the number of users who report the same event.

13. The system of claim 9, wherein: The evaluating the validity of the reported information based on the reported information, the real road condition information and the credit information includes: Determining whether the credit information satisfies a first threshold condition; when the credit information satisfies the first threshold condition, indicating that the user is not trustworthy; In response to determining that the credit information satisfies the first threshold condition, the validity of the reported information is evaluated based on the reported information and the actual road condition information.

14. The system of claim 9, wherein: The evaluation module is also used to: Determining whether the credit information satisfies a second threshold condition; when the credit information satisfies the second threshold condition, indicating that the user is trustworthy; In response to determining that the credit information satisfies the second threshold condition, the reported information is evaluated as valid.

15. The system of claim 9, wherein: It also includes a feedback module for sharing effective reporting information with other users.

16. The system of claim 9, wherein: The updating of the current credit information of the user based on the validity of the reported information includes: In response to evaluating the reported information as valid, increasing the value of the user's current credit information; in response to evaluating the reported information as invalid, decreasing the value of the user's current credit information; wherein a higher value of the credit information indicates that the user is more trustworthy; or In response to evaluating the reported information as valid, the value of the user's current credit information is reduced; in response to evaluating the reported information as invalid, the value of the user's current credit information is increased; wherein, the lower the value of the credit information, the more trustworthy the user is.

17. A management device for information reported by travel users, characterized in that: The method comprises a processor and a storage device, wherein the storage device is used to store instructions. When the processor executes the instructions, the method according to any one of claims 1 to 8 is implemented.

18. A computer-readable storage medium, characterized in that: The storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the method according to any one of claims 1 to 8.

Images