Public bus fare payment method and device

Abstract

The embodiments of this specification provide a method and device for paying bus fares, wherein a method for paying bus fares includes: obtaining user riding information and vehicle information of a contracted bus that has a route contract with an institution, which is synchronized with the bus system; the user riding information is determined based on the user's riding code collected by a code scanning component configured on the contracted bus; detecting whether the user riding information and vehicle information match the ride verification agreement of the target institution to which the user belongs; and if so, calling the institutional account of the target institution to pay the fare.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of March 29, 2021, application number CN202110332383.2, and name “Method and Device for Payment of Public Bus Fares”. Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a method and device for paying bus fares. Background Art

[0003] The public transportation system is an indispensable part of urban infrastructure. The development level of public transportation can also reflect the development status of a city. It can be seen that the public transportation system plays an important role in travel. Especially under the premise of advocating green travel and enjoying a low-carbon life, public transportation is the best way to reduce costs and alleviate traffic congestion. Customized public transportation is based on the personalized needs of passengers. By gathering the common points of these needs, routes are set in the form of multi-person shared vehicles, providing customized passenger transportation services for people with similar travel starting and ending points, travel time, and service level requirements. Summary of the Invention

[0004] One or more embodiments of this specification provide a method for paying for public transit fares. The method includes: obtaining user and vehicle information synchronized with the public transit system for buses contracted with an organization for routes; determining the user's boarding information based on a user's boarding code collected by a code scanning component configured on the contracted bus; and detecting whether the user and vehicle information match the bus reimbursement agreement of the target organization to which the user belongs; if so, using the target organization's institutional account to pay the fare.

[0005] One or more embodiments of this specification provide a bus fare payment device, comprising: an acquisition module configured to acquire user boarding information and vehicle information synchronized with a public transportation system for buses contracted with an organization for routes; the user boarding information is determined based on a user boarding code collected by a code scanning component configured on the contracted bus; a detection module configured to detect whether the user boarding information and vehicle information match the bus fare verification agreement of the target organization to which the user belongs; if so, to execute a payment module configured to call the target organization's institutional account to pay the fare.

[0006] One or more embodiments of this specification provide a bus fare payment device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein when executed, the computer-executable instructions cause the processor to: obtain user boarding information and vehicle information synchronized with a public transportation system for a contracted bus that has a route contract with an institution; determine the user boarding information based on a user boarding code collected by a code scanning component configured on the contracted bus; detect whether the user boarding information and vehicle information match a bus reimbursement agreement of a target institution to which the user belongs; and if so, invoke the target institution's institutional account to pay the fare.

[0007] One or more embodiments of this specification provide a storage medium for storing computer-executable instructions that, when executed, implement the following process: obtaining user boarding information and vehicle information synchronized with a public transportation system for a contracted public transportation vehicle with a route contracted by an organization; determining the user boarding information based on a user boarding code collected by a code scanning component configured on the contracted public transportation vehicle; detecting whether the user boarding information and vehicle information match a bus reimbursement agreement of a target organization to which the user belongs; and, if so, using the target organization's institutional account to pay the bus fare. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0009] Figure 1 A flowchart of a method for paying a bus fare provided in one or more embodiments of this specification;

[0010] Figure 2 A flowchart of a method for paying a bus fare applied to a user's bus riding scenario provided in one or more embodiments of this specification;

[0011] Figure 3 A schematic diagram of a bus fare payment device provided in one or more embodiments of this specification;

[0012] Figure 4 A schematic diagram of the structure of a bus fare payment device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0013] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0014] This specification provides an embodiment of a method for paying bus fares:

[0015] Reference Figure 1 , which shows a process flow chart of a bus fare payment method provided by this embodiment, referring to Figure 2 , which shows a processing flow chart of a method for paying bus fares applied to a user's riding scenario provided by this embodiment.

[0016] Reference Figure 1 The bus fare payment method provided in this embodiment specifically includes the following steps S102 to S108.

[0017] Step S102: Acquire the user riding information and vehicle information of the contracted buses that have signed the route contract with the organization in synchronization with the public transportation system.

[0018] The bus fare payment method provided in this embodiment provides a bus route contract service to an organization, so that the organization's employees can pay the employee's fare through the organization's institutional account when riding the contracted bus signed by the organization. Specifically, after the organization and the public transportation system sign a bus contract, the method determines whether the user's fare information when riding the bus is consistent with the contracted information signed between the organization and the public transportation system based on the obtained user fare information. If it is consistent, the organization's institutional account is used to pay the user's fare, thereby improving the efficiency and convenience of user fare verification.

[0019] The public transportation vehicles described in this embodiment include public transportation suitable for vehicle scheduling, such as buses, subways, and trams; the contracted public transportation vehicles refer to public transportation vehicles for which the agency has signed a route contract with the public transportation system; the user's boarding information includes user identification, boarding time, boarding fare and / or boarding station identification; it should be noted that the user's boarding information is determined based on the user's boarding code collected by the code scanning component configured for the contracted public transportation vehicle; the vehicle information includes vehicle identification and / or vehicle route number.

[0020] In actual applications, from the perspective of the public transportation system, the agency's contracted buses have fixed routes and stable passenger flow, which is a long-term business direction and can increase the public transportation system's revenue to a certain extent. During the route contracting process between the public transportation system and the agency, the bus company and the agency agree on the agency's commuting route number and commuting stops, and within the commuting time range agreed with the agency, the bus company contracts idle buses as the agency's contracted buses. In an optional implementation provided in this embodiment, route contracting is mainly achieved through the following steps:

[0021] Contracting at least one bus belonging to the bus route number as a contracted bus of the said organization;

[0022] The specific station of the bus line corresponding to the bus line number is signed as a commuting station of the contracted bus of the organization, the commuting station of the contracted bus is configured according to the station submitted by the organization, and / or the line number of the contracted bus is updated to the commuting line number of the organization.

[0023] Specifically, the route contract is completed by the agency and the public transportation system. When the agency and the public transportation system sign the route contract, they jointly agree on the commuting route number and commuting time for the agency, such as "A Agency Route 1", and agree on the commuting stops where the contracted bus stops. When the public transportation system detects that it is the commuting time for the agency, it will sign the idle bus as the agency's contracted bus.

[0024] For example, institution A signs a route contract with the bus system, agreeing that the commuting route for institution A is numbered "Route A01" and the commuting hours are from 7:00 to 9:00, 12:00 to 14:00, and 17:00 to 20:00 every day. If the bus system detects that a bus numbered "Route 286" is idle, the route number of the bus will be changed to "Route A01" and it will operate according to the commuting hours.

[0025] For another example, institution B signs a route contract with the bus system, agreeing to sign stations xx1, xx2, and xx3 on the bus route numbered "Route 233" as commuter stops for institution B, so that institution B will pay for the fare when its employees take the bus at any of these three stops.

[0026] For another example, institution C signed a route contract with the bus system, agreeing that the commuting routes for institution C are numbered "Route C01" and "Route C02". The travel time was not agreed upon, but the commuting stops were agreed upon. Among them, the commuting stops for "Route C01" include the East Gate Station of Institution C, the West Gate Station of Institution C, and the Guangming Community Station, and the commuting stops for "Route C02" include the East Gate Station of Institution C and the Shopping Center Station; based on the commuting stops provided by Institution C, the bus company determined that the contracted buses with route number "Route C01" pass through three stops: the East Gate Station of Institution C, the West Gate Station of Institution B, and the Guangming Community Station, and that the contracted buses with route number "Route C02" pass through two stops: the East Gate Station of Institution C and the Shopping Center Station.

[0027] It should be noted that the form of route contract between the agency and the public bus may include signing a specific station of the bus line corresponding to the bus line number as a commuting station of the agency's contracted public bus, configuring the commuting station of the contracted public bus according to the station submitted by the agency, and updating the route number of the contracted public bus to the commuting route number of the agency. It can also be any one or two of the above three items, and may also include other forms agreed upon by the agency and the public transportation system in actual scenarios, which are not limited in this embodiment; the content of the route contract between the agency and the public bus may include commuting user identification, commuting time range, commuting station identification and commuting route number, and may also include other content agreed upon by the agency and the public transportation system in actual scenarios, which are not limited in this embodiment. Specifically, the number of commuting route numbers agreed upon by each agency is not limited here.

[0028] In addition, in order to enhance the awareness of the organization's employees, the commuting time and / or commuting line number in the contract information table may be displayed to the organization's employees. Specifically, the method of reaching the organization's employees is not specifically limited in this embodiment.

[0029] In specific implementation, after the agency signs a contract with the public transportation system, in order to identify the users who ride the bus, avoid the agency having to pay the fare of all users riding the contracted bus, which would cause loss of the agency's resources, and further standardize the management of users riding the contracted bus, this embodiment provides an optional implementation method. Before obtaining the user's riding information and the vehicle information, it is necessary to obtain a contract information table synchronized after the agency and the public transportation system sign a route contract for the contracted bus; wherein, the contract information table records the agency's commuting user identification, commuting time range and / or commuting route number.

[0030] Specifically, after the organization signs a contract with the public transportation system, it constructs a contract information table based on the organization's employee list, agreed commuting route number, commuting station identification and commuting time, and synchronizes it to the server. The server refers to a third-party server that can perform deductions and payments, such as the server corresponding to the third-party payment application.

[0031] For example, the contract information table of Institution A, which was synchronized after Institution A signed the contract with the public transportation system, and the contract information table of Institution B, which was synchronized after Institution B signed the contract with the public transportation system, were obtained. The contract information table of Institution A records the user ID, commuting time, and commuting route number of Institution A’s employees, where the commuting time is from 7:00 to 9:00, 12:00 to 14:00, and 17:00 to 20:00 every day, and the commuting route number is "Route A01"; the contract information table of Institution B records the user ID and commuting station ID of Institution B’s employees, where the commuting station IDs are Station xx1, Station xx2, and Station xx3.

[0032] When a user takes a public bus, he or she needs to show his or her boarding code to the bus's code scanning component to pay the fare. In specific implementation, when a user takes the contracted public bus, the contracted public bus's code scanning component scans and recognizes the boarding code displayed by the user through a third-party application, and uploads the recognition result and the component information of the code scanning component to the public transportation system; the public transportation system determines and synchronizes the user's boarding information and the vehicle information based on the recognition result and the component information; specifically, in order to save resource loss caused by data selection and save costs, the user's boarding information and vehicle information of all buses synchronized by the public transportation system can also be obtained.

[0033] In this embodiment, the boarding code is displayed by the user through a third-party application (for example, a payment application). Based on this, the bus fare payment method provided in this embodiment is applied to a server that cooperates with the third-party application.

[0034] During specific implementation, after obtaining the user's boarding information and vehicle information, the user's boarding information and vehicle information must be matched with the target agency's boarding verification agreement for detection. The target agency refers to the agency corresponding to the agency identifier bound to the user identifier contained in the user's boarding information; the boarding verification agreement refers to the agreement between the boarding user and the server determined based on the contract information table synchronized with the target agency. Specifically, when the user's boarding information and vehicle information meet the boarding verification agreement, the server calls the agency account of the target agency bound to the boarding verification agreement to pay the boarding fee; in other words, the boarding verification agreement is also the boarding verification condition. When the user's boarding information and vehicle information meet the boarding verification condition, the boarding fee is paid by the agency account corresponding to the agency identifier bound to the user identifier contained in the user's boarding information. In order to improve the accuracy of the matching results and improve the efficiency of matching detection, in an optional implementation provided by this embodiment, after obtaining the user's boarding information and the vehicle information, the following operations must be performed:

[0035] Checking whether there is an institution identifier bound to the user identifier included in the user's ride information;

[0036] If so, query the contract information table of the target organization according to the organization identifier, and execute step S104 to check whether the user's ride information and vehicle information match the ride verification agreement of the target organization to which the user belongs;

[0037] If not, the user account corresponding to the user identifier is used to pay the fare.

[0038] For example, the user riding information and vehicle information synchronized with the public transportation system are obtained. According to the user ID of user u1 contained in the user riding information, it is found that user u1 is an employee of institution A. According to the institution ID of institution A, the contract information table corresponding to institution A is queried, and further matching detection is performed on the user riding information and vehicle information of user u1 based on the contract information table.

[0039] Step S104: Check whether the user's ride information and vehicle information match the ride verification agreement of the target organization to which the user belongs.

[0040] The ride verification agreement described in this embodiment includes a matching relationship between the user ID included in the user's ride information and any commuting user ID in the contract information table, a matching relationship between the ride time included in the user's ride information and the commuting time range recorded in the contract information table, and / or a matching relationship between the vehicle route number included in the vehicle information and any commuting route number in the contract information table. Specifically, the ride verification agreement corresponding to each institution is determined based on the contract information table synchronized by each institution.

[0041] During specific implementation, when detecting whether the user's riding information and vehicle information match the ride verification agreement of the target institution to which the user belongs, first determine whether the user identifier contained in the user's riding information has a matching relationship with any commuting user identifier in the contract information table of any institution, that is: determine whether the user identifier is a commuting user identifier in any contract information table. If so, perform further matching detection on the user's riding information and vehicle information based on the contract information table where the user identifier is located; if not, use the user account corresponding to the user identifier to pay the ride fare. In an optional implementation provided by this embodiment, after querying the contract information table of the target institution, perform the following steps to detect whether the user's riding information matches the ride verification agreement:

[0042] Determining whether the boarding time included in the user's boarding information is within the commuting time range recorded in the contract information table;

[0043] If not, the matching result is determined to be a matching failure;

[0044] If so, determining whether the vehicle route number included in the vehicle information is any commuting route number recorded in the contract information table;

[0045] If so, determine that the matching result is a successful match;

[0046] If not, the matching result is determined to be a matching failure;

[0047] The contract information table records the commuting time range and commuting route number.

[0048] For example, determine whether the travel time included in the user travel information of user u1 is the commuting time agreed upon by institution A. If so, determine whether the vehicle route number included in the vehicle information is any of the commuting route numbers agreed upon by institution A. If so, determine that the user travel information and vehicle information of user u1 are successfully matched with the travel verification agreement of institution A, and determine that user u1 meets the conditions for reimbursement of official payments by institution A. Otherwise, the match fails.

[0049] In addition, the organization and the public transportation system may also agree on other contents. When the organization and the public transportation system agree on commuting stops, in an optional implementation provided by this embodiment, whether the user's riding information matches the riding verification agreement is detected in the following manner:

[0050] Determining whether the boarding station identifier included in the user boarding information is any commuting station identifier recorded in the contract information table;

[0051] If so, the matching result is determined to be a successful match;

[0052] If not, the matching result is determined to be a matching failure;

[0053] The contract information table records the commuting station identifier.

[0054] For example, it is found that the user ID of user u2 is bound to the organization ID of institution B and the contract information table of institution B is found. The contract information table of institution B records the commuting station ID and commuting line number agreed upon by institution B and the public transportation system. It is determined whether the boarding station of user u2 is any commuting station recorded in the contract information table. If so, it is determined whether the vehicle line number of user u2 is any commuting line number recorded in the contract information table. If so, it is determined that the user boarding information and vehicle information of user u2 are successfully matched with the boarding verification agreement of institution B. If not, it is determined that the user boarding information and vehicle information of user u2 are unmatched with the boarding verification agreement of institution B.

[0055] In specific implementation, if the user's ride information and vehicle information match the ride verification agreement of the target organization to which the user belongs, step S106 is executed to call the target organization's institutional account to pay the ride fare. In an optional implementation provided in this embodiment, the target organization's institutional account is determined in the following manner:

[0056] According to the user identification included in the user boarding information, the institution account corresponding to the institution identification bound to the boarding user identification is queried.

[0057] In an optional implementation provided by this embodiment, if the result of checking whether the user's travel information and vehicle information match the travel reimbursement agreement of the target institution to which the user belongs is negative, the user is determined to not meet the requirements for business-related payment reimbursement. The user account corresponding to the user identifier included in the user's travel information is used to pay the travel fare. A user payment result is generated based on the payment processing result and sent to the user. Specifically, during the payment processing process, the resources in the user account are transferred to the corresponding public transportation account of the public transportation system based on the travel fare.

[0058] For example, if it is detected that the user travel information and vehicle information of user u1 successfully match the travel reimbursement agreement of institution A, the institutional account of institution A will be called to pay the travel fee of user u1 and the institutional payment result will be sent to user u1; if it is detected that the user travel information and vehicle information of user u2 fail to match the travel reimbursement agreement of institution B, the user account of user u2 will be called to pay the travel fee of user u2 and the user payment result will be sent to user u2.

[0059] Step S106: calling the target organization's institutional account to pay the fare.

[0060] In an optional implementation provided by this embodiment, after the institutional account is determined, the resources in the institutional account are transferred to the public transportation account corresponding to the public transportation system based on the fare, and the institutional payment result is sent to the user. For example, if user u1's fare is m yuan, the corresponding funds in the institutional account of institution A are transferred to the public transportation account corresponding to the public transportation system, and the result of the resource transfer by institution A is sent to user u1.

[0061] The following combined Figure 2 , taking the application of the bus fare payment method provided by this embodiment in the user's riding scenario as an example, the bus fare payment method provided by this embodiment is further explained. Figure 2 The bus fare payment method applied to the user riding scenario specifically includes steps S202 to S216.

[0062] Step S202: Acquire user riding information and vehicle information of commuter buses that have signed commuter route contracts with the organization, which are synchronized with the public transportation system.

[0063] Among them, the user's boarding information is determined based on the user's boarding code collected by the scanning component configured on the contracted public bus.

[0064] Step S204, determining whether there is an institution identifier of a target institution that has a binding relationship with the user identifier included in the user's ride information;

[0065] If yes, go to step S206;

[0066] If not, the user account corresponding to the user ID is called to pay the fare.

[0067] Step S206: query the contract information table corresponding to the target organization according to the organization identifier.

[0068] Step S208: determining whether the ride time included in the user's ride information is within the commuting time range recorded in the contract information table;

[0069] If yes, go to step S210;

[0070] If not, the user account corresponding to the user ID is called to pay the fare.

[0071] Step S210, determining whether the vehicle route number included in the vehicle information is the commuting route number recorded in the contract information table;

[0072] If yes, go to step S212;

[0073] If not, the user account corresponding to the user ID is called to pay the fare.

[0074] Step S212: query the institution account corresponding to the institution identifier of the target institution.

[0075] Step S214: Use the institutional account to pay the fare included in the user's travel information.

[0076] Step S216: Generate a payment processing result and send it to the user.

[0077] To sum up, the bus fare payment method provided in this embodiment first obtains the user riding information and vehicle information of the contracted bus that has signed a route contract with the organization, which is synchronized with the bus system, and then detects whether the user riding information and vehicle information match the ride verification agreement of the target organization to which the user belongs. If it is detected that the user riding information and vehicle information match the ride verification agreement, the institutional account of the target organization is called to pay the fare, thereby improving the convenience of the organization's employees in taking commuting vehicles.

[0078] An embodiment of a bus fare payment device provided in this specification is as follows:

[0079] In the above embodiment, a method for paying a bus fare is provided, and correspondingly, a device for paying a bus fare is also provided, which will be described below with reference to the accompanying drawings.

[0080] Reference Figure 3 , which shows a schematic diagram of a bus fare payment device provided by this embodiment.

[0081] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0082] This embodiment provides a bus fare payment device, comprising:

[0083] The acquisition module 302 is configured to acquire user boarding information and vehicle information of a contracted public bus that has a route contract with an organization, which is synchronized with the public transportation system; the user boarding information is determined based on the user's boarding code collected by a code scanning component configured on the contracted public bus;

[0084] A detection module 304 is configured to detect whether the user's ride information and vehicle information match the ride verification agreement of the target organization to which the user belongs;

[0085] If yes, the payment module 306 is executed, and the payment module is configured to call the institution account of the target institution to pay the ride fare.

[0086] Optionally, the line contract is performed by running the following submodules:

[0087] A vehicle contracting submodule is configured to contract at least one bus belonging to a bus route number as a contracted bus of the organization;

[0088] The route contracting submodule is configured to contract a specific station of the bus route corresponding to the bus route number as a commuting station of the contracted bus of the organization, configure the commuting station of the contracted bus according to the station submitted by the organization, and / or update the route number of the contracted bus to the commuting route number of the organization.

[0089] Optionally, the bus fare payment device further includes:

[0090] The information table acquisition module is configured to obtain a contract information table synchronized after the agency and the public transportation system sign a route contract for the contracted public transportation vehicle; wherein the contract information table records the agency's commuting user identification, commuting time range and / or commuting route number.

[0091] Optionally, the ride verification agreement is specifically configured so that the user identifier contained in the user's ride information has a matching relationship with any commuting user identifier in the contract information table, the ride time contained in the user's ride information has a matching relationship with the commuting time range recorded in the contract information table, and / or the vehicle route number contained in the vehicle information has a matching relationship with any commuting route number in the contract information table.

[0092] Optionally, the bus fare payment device further includes:

[0093] an institution query module configured to query whether there is an institution identifier bound to the user identifier included in the user's ride information;

[0094] If so, run the matching detection module, which is configured to query the contract information table of the target institution based on the institution identifier, and execute the step of detecting whether the user's ride information and vehicle information match the ride verification agreement of the target institution to which the user belongs.

[0095] Optionally, whether the user's ride information and the vehicle information match the ride verification agreement is detected by running the following submodules:

[0096] a time determination submodule configured to determine whether the ride time included in the user's ride information is within the commuting time range recorded in the contract information table;

[0097] If so, running a number determination submodule, the number determination submodule is configured to determine whether the vehicle route number included in the vehicle information is any commuting route number recorded in the contract information table;

[0098] If yes, run the result determination submodule, wherein the result determination submodule is configured to determine that the matching result is a successful match;

[0099] The contract information table records the commuting time range and commuting route number.

[0100] Optionally, whether the user's ride information and the vehicle information match the ride verification agreement is detected by running the following submodules:

[0101] The station judgment submodule is configured to judge whether the boarding station identifier contained in the user's boarding information is any commuting station identifier recorded in the contract information table; if so, determine that the matching result is a successful match; wherein the commuting station identifier is recorded in the contract information table.

[0102] Optionally, the target institution's institutional account is determined by running the following submodules:

[0103] An institution account query submodule is configured to query an institution account corresponding to the institution identifier bound to the riding user identifier based on the user identifier included in the riding user information;

[0104] Accordingly, the payment module 306 includes:

[0105] The resource transfer submodule is configured to transfer the resources in the institution account to the public transportation account corresponding to the public transportation system according to the fare.

[0106] Optionally, if the result of the detection module 304 is negative, the following modules are executed:

[0107] A user account calling module is configured to call the user account corresponding to the user identifier included in the user's ride information to pay the ride fee;

[0108] The payment processing module is configured to generate a user payment result based on the payment processing result and send it to the user.

[0109] Optionally, the code scanning component scans and identifies the boarding code displayed by the user through a third-party application, and uploads the identification result and component information of the code scanning component to the public transportation system; the public transportation system determines and synchronizes the user's boarding information and the vehicle information based on the identification result and the component information.

[0110] This specification provides an embodiment of a bus fare payment device as follows:

[0111] Corresponding to the above-described method for paying a bus fare, based on the same technical concept, one or more embodiments of this specification further provide a bus fare payment device, which is used to execute the above-described method for paying a bus fare. Figure 4 A schematic diagram of the structure of a bus fare payment device provided in one or more embodiments of this specification.

[0112] like Figure 4 As shown, the bus fare payment device can vary significantly due to different configurations or performance. It may include one or more processors 401 and memory 402. Memory 402 may store one or more applications or data. Memory 402 may be either ephemeral or persistent. The applications stored in memory 402 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for the bus fare payment device. Furthermore, processor 401 may be configured to communicate with memory 402 to execute the series of computer-executable instructions in memory 402 on the bus fare payment device. The bus fare payment device may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input / output interfaces 405, one or more keyboards 406, and the like.

[0113] In a specific embodiment, a bus fare payment device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the bus fare payment device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following:

[0114] Acquire user boarding information and vehicle information of contracted buses that have signed a route contract with the organization, which are synchronized with the public transportation system; the user boarding information is determined based on the user's boarding code collected by the code scanning component configured on the contracted bus;

[0115] Checking whether the user's ride information and vehicle information match the ride verification agreement of the target organization to which the user belongs;

[0116] If so, the target organization's institutional account is used to pay the fare.

[0117] Optionally, the line contract signing includes:

[0118] Contracting at least one bus belonging to the bus route number as a contracted bus of the said organization;

[0119] The specific station of the bus line corresponding to the bus line number is signed as a commuting station of the contracted bus of the organization, the commuting station of the contracted bus is configured according to the station submitted by the organization, and / or the line number of the contracted bus is updated to the commuting line number of the organization.

[0120] Optionally, when the computer executable instructions are executed, they further include:

[0121] Checking whether there is an institution identifier bound to the user identifier included in the user's ride information;

[0122] If so, query the contract information table of the target institution according to the institution identifier, and execute the step of detecting whether the user's riding information and vehicle information match the riding verification agreement of the target institution to which the user belongs.

[0123] Optionally, whether the user's ride information and the vehicle information match the ride verification agreement is detected in the following manner:

[0124] Determining whether the boarding time included in the user's boarding information is within the commuting time range recorded in the contract information table;

[0125] If so, determining whether the vehicle route number included in the vehicle information is any commuting route number recorded in the contract information table;

[0126] If so, the matching result is determined to be a successful match;

[0127] The contract information table records the commuting time range and commuting route number.

[0128] Optionally, whether the user's ride information and the vehicle information match the ride verification agreement is detected in the following manner:

[0129] Determining whether the boarding station identifier included in the user boarding information is any commuting station identifier recorded in the contract information table;

[0130] If so, the matching result is determined to be a successful match;

[0131] The contract information table records the commuting station identifier.

[0132] An embodiment of a storage medium provided in this specification is as follows:

[0133] Corresponding to the above-described method for paying bus fares, based on the same technical concept, one or more embodiments of this specification further provide a storage medium.

[0134] The storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented:

[0135] Acquire user boarding information and vehicle information of contracted buses that have signed a route contract with the organization, which are synchronized with the public transportation system; the user boarding information is determined based on the user's boarding code collected by the code scanning component configured on the contracted bus;

[0136] Checking whether the user's ride information and vehicle information match the ride verification agreement of the target organization to which the user belongs;

[0137] If so, the target organization's institutional account is used to pay the fare.

[0138] Optionally, the line contract signing includes:

[0139] Contracting at least one bus belonging to the bus route number as a contracted bus of the said organization;

[0140] The specific station of the bus line corresponding to the bus line number is signed as a commuting station of the contracted bus of the organization, the commuting station of the contracted bus is configured according to the station submitted by the organization, and / or the line number of the contracted bus is updated to the commuting line number of the organization.

[0141] Optionally, when the computer executable instructions are executed, they further implement the following process:

[0142] Checking whether there is an institution identifier bound to the user identifier included in the user's ride information;

[0143] If so, query the contract information table of the target institution according to the institution identifier, and execute the step of detecting whether the user's riding information and vehicle information match the riding verification agreement of the target institution to which the user belongs.

[0144] Optionally, whether the user's ride information and the vehicle information match the ride verification agreement is detected in the following manner:

[0145] Determining whether the boarding time included in the user's boarding information is within the commuting time range recorded in the contract information table;

[0146] If so, determining whether the vehicle route number included in the vehicle information is any commuting route number recorded in the contract information table;

[0147] If so, the matching result is determined to be a successful match;

[0148] The contract information table records the commuting time range and commuting route number.

[0149] It should be noted that the embodiment of the storage medium in this specification and the embodiment of the method for paying bus fares in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0150] The foregoing description describes characteristic embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the characteristic order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0151] In the 1930s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this type of programming is mostly performed using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0152] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

[0153] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0154] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0155] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0156] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0157] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a characteristic manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, the instruction device being implemented in the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0158] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0159] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0160] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0161] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0162] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0163] One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform characteristic tasks or implement characteristic abstract data types. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In distributed computing environments, program modules may be located in local and remote computer storage media, including storage devices.

[0164] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0165] The foregoing description is merely an example of the present invention and is not intended to limit the present invention. Persons skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be included within the scope of the claims herein.

Claims

1. A method for paying a bus fare, comprising: Obtain user boarding information and vehicle route numbers of contracted buses synchronized with the bus system and signed with the agency; The user's boarding information is determined based on the user's boarding code collected by the code scanning component configured for the contracted public bus; Determining whether the vehicle route number is any commuting route number recorded in the contract information table of the target organization to which the user belongs; If so, the target organization's institutional account is used to pay the fare.

2. The bus fare payment method according to claim 1, wherein the route contract signing comprises: Contracting at least one bus belonging to the bus route number as a contracted bus of the said organization; The specific station of the bus line corresponding to the bus line number is signed as a commuting station of the contracted bus of the organization, the commuting station of the contracted bus is configured according to the station submitted by the organization, and / or the line number of the contracted bus is updated to the commuting line number of the organization.

3. The method for paying for bus fares according to claim 1, before the step of obtaining user boarding information and vehicle route numbers of buses that have signed route contracts with the organization and are synchronized with the bus system, further comprising: Obtaining a contract information table synchronized between the agency and the public transportation system after the contracted public transportation vehicle has signed a route contract; The contract information table records the commuting user identification, commuting time range and / or commuting route number of the organization.

4. The method for paying for a bus fare according to claim 1, further comprising: after the step of obtaining user boarding information and vehicle route numbers of buses that have contracted routes with organizations and synchronized with the public transportation system, and before the step of determining whether the vehicle route number is any commuting route number recorded in the contract information table of the target organization to which the user belongs, the method further comprises: Determining whether the boarding time included in the user's boarding information is within the commuting time range recorded in the contract information table; If so, executing the step of determining whether the vehicle route number is any commuting route number recorded in the contract information table of the target organization to which the user belongs; The contract information table records the commuting time range and the commuting route number.

5. The method for paying for bus fares according to claim 1, wherein the target institution's institutional account is determined in the following manner: According to the user identifier included in the user's ride information, query the institution account corresponding to the institution identifier bound to the user identifier; Accordingly, calling the target organization's account to pay the ride fare includes: According to the fare, the resources in the institution account are transferred to the public transportation account corresponding to the public transportation system.

6. The bus fare payment method according to claim 1, wherein if the step of determining whether the bus route number is any commuter route number recorded in the contract information table of the target organization to which the user belongs is executed, the following operations are performed: Calling the user account corresponding to the user identifier included in the user's ride information to pay the ride fee; Generate a user payment result based on the payment processing result and send it to the user.

7. According to the bus fare payment method according to claim 1, the code scanning component scans and recognizes the boarding code displayed by the user through a third-party application, and uploads the recognition result and the component information of the code scanning component to the bus system; the bus system determines and synchronizes the user's boarding information and the vehicle route number based on the recognition result and the component information.

8. A bus fare payment device, comprising: An acquisition module is configured to acquire user riding information and vehicle route numbers of contracted buses that have signed route contracts with the agency and are synchronized with the public transportation system; The user's boarding information is determined based on the user's boarding code collected by the code scanning component configured for the contracted public bus; an institution query module configured to determine whether the vehicle route number is any commuting route number recorded in the contract information table of the target institution to which the user belongs; If yes, run the payment module, which is configured to call the target organization's account to pay the ride fare.

9. A bus fare payment device, comprising: processor; as well as, a memory configured to store computer-executable instructions that, when executed, cause the processor to: Obtaining user boarding information and vehicle route numbers of contracted buses synchronized with the bus system and signed with the agency; the user boarding information is determined based on the user's boarding code collected by the code scanning component configured on the contracted bus; Determining whether the vehicle route number is any commuting route number recorded in the contract information table of the target organization to which the user belongs; If so, the target organization's institutional account is used to pay the fare.

10. A storage medium for storing computer-executable instructions, wherein the computer-executable instructions, when executed, implement the following process: Obtaining user boarding information and vehicle route numbers of contracted buses synchronized with the bus system and signed with the agency; the user boarding information is determined based on the user's boarding code collected by the code scanning component configured on the contracted bus; Determining whether the vehicle route number is any commuting route number recorded in the contract information table of the target organization to which the user belongs; If so, the target organization's institutional account is used to pay the fare.

Images