CN113065863B - Bus fee payment method and device - Google Patents

Bus fee payment method and device Download PDF

Info

Publication number
CN113065863B
CN113065863B CN202110332383.2A CN202110332383A CN113065863B CN 113065863 B CN113065863 B CN 113065863B CN 202110332383 A CN202110332383 A CN 202110332383A CN 113065863 B CN113065863 B CN 113065863B
Authority
CN
China
Prior art keywords
user
riding
information
bus
commuting
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110332383.2A
Other languages
Chinese (zh)
Other versions
CN113065863A (en
Inventor
陆凯华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AlipayCom Co ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202210655468.9A priority Critical patent/CN115063136A/en
Priority to CN202110332383.2A priority patent/CN113065863B/en
Publication of CN113065863A publication Critical patent/CN113065863A/en
Application granted granted Critical
Publication of CN113065863B publication Critical patent/CN113065863B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Tourism & Hospitality (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Traffic Control Systems (AREA)

Abstract

The embodiment of the specification provides a bus fare payment method and a bus fare payment device, wherein the bus fare payment method comprises the following steps: acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus; detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs; and if so, calling the institution account of the target institution to pay the riding fee.

Description

Bus fee payment method and device
Technical Field
The document relates to the technical field of data processing, in particular to a bus fare payment method and device.
Background
The public transportation system is an indispensable part in urban infrastructure, the current development situation of a city can be reflected from the development degree of the public transportation, therefore, the public transportation system plays an important role in the aspect of travel, particularly, on the premise of advocating green travel and enjoying low-carbon life, the public transportation travel is a better travel mode which reduces cost and relieves traffic jam, the customized public transportation is a better travel mode which sets lines in a mode of sharing vehicles by multiple persons according to the personalized requirements of passengers by gathering the common points of the requirements, and a customized passenger transportation service mode is provided for people with similar travel starting and ending points, travel time and service level requirements.
Disclosure of Invention
One or more embodiments of the present specification provide a method for payment of a bus fare. The bus fare payment method comprises the following steps: acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; and the user riding information is determined based on the riding code of the user collected by the code scanning component configured by the signed bus. Detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs; and if so, calling the institution account of the target institution to pay the riding fee.
One or more embodiments of the present specification provide a bus fare payment device, including: the acquisition module is configured to acquire user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; and the user riding information is determined based on the riding code of the user collected by the code scanning component configured by the signed bus. The detection module is configured to detect whether the user riding information and the vehicle information are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs; and if so, operating a payment module, wherein the payment module is configured to call the institution account of the target institution to pay the riding fee.
One or more embodiments of the present specification provide a bus fare payment device, including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; and the user riding information is determined based on the riding code of the user collected by the code scanning component configured by the signed bus. Detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs; and if so, calling the institution account of the target institution to pay the riding fee.
One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following: acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; and the user riding information is determined based on the riding code of the user collected by the code scanning component configured by the signed bus. Detecting whether the user riding information and the vehicle information are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs; and if so, calling the institution account of the target institution to pay the riding fee.
Drawings
In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings used in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the description below are only some embodiments described in the present specification, and that other drawings may be obtained by those skilled in the art without inventive labor.
Fig. 1 is a process flow diagram of a bus fare payment method provided in one or more embodiments of the present disclosure;
fig. 2 is a process flow diagram of a bus fare payment method applied to a user riding scenario according to one or more embodiments of the present disclosure;
fig. 3 is a schematic view of a bus fare payment device according to one or more embodiments of the present disclosure;
fig. 4 is a schematic structural diagram of a bus fare payment device provided in one or more embodiments of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
The embodiment of the bus fare payment method provided by the specification comprises the following steps:
referring to fig. 1, which shows a processing flow chart of a bus fare payment method provided by the embodiment, and referring to fig. 2, which shows a processing flow chart of a bus fare payment method applied to a user riding scene provided by the embodiment.
Referring to fig. 1, the method for paying the bus fare provided by the embodiment specifically includes the following steps S102 to S108.
And step S102, obtaining user riding information and vehicle information of signed buses which are synchronous with the public transport system and sign with the mechanism on a line.
The bus fare payment method provided by this embodiment enables, by providing a line contract service for a bus to a mechanism, an employee of the mechanism to pay the fare of the employee through an organization account of the mechanism at the moment when the employee signs a contract with the mechanism, specifically, after the mechanism signs a contract with a bus system, according to acquired user riding information, it is determined whether the user riding information of the user when the user takes the bus conforms to the contract information signed with the bus system, and if so, the organization account of the mechanism is used to pay the fare generated by the user, so as to improve the efficiency and convenience of the user for riding and checking.
The public transport vehicles comprise public transport vehicles suitable for vehicle scheduling, such as buses, subways, trams and the like; the signed public transport vehicle is a public transport vehicle with a mechanism signing a line with a public transport system; the user riding information comprises user identification, riding time, riding cost and/or riding station identification; it should be noted that the user riding information is determined based on the riding code of the user collected by the code scanning component configured for the contracted public transport vehicle; the vehicle information comprises vehicle identification and/or vehicle line number.
In practical application, from the perspective of a public transportation system, a contracted bus line of a mechanism is fixed, passenger flow is stable, the contracted bus line is a service direction for long-term operation, income of the public transportation system can be increased to a certain extent, the public transportation system and the mechanism contract a commuting line number and a commuting stop of the mechanism, and the public transportation vehicle in an idle state is contracted into the contracted bus vehicle of the mechanism within a commuting time range contracted with the mechanism, in an optional implementation mode provided by the embodiment, the contracted bus line is mainly realized through the following steps:
signing at least one public transport vehicle belonging to the public transport line number as a signed public transport vehicle of the mechanism;
and signing a specific station of a bus line corresponding to the bus line number into the commuting station of the signed bus of the organization, and carrying out the configuration of the commuting station of the signed bus according to the station submitted by the organization, and/or updating the line number of the signed bus into the commuting line number of the organization.
Specifically, the line signing is completed by the cooperation of the mechanism and the public transportation system, and when the mechanism and the public transportation system carry out the line signing, the commuting line number and the commuting time of the mechanism are agreed together, such as 'A mechanism 1 way', and the commuting station where the signed public transportation vehicles stop is agreed, and when the public transportation system detects the commuting time of the mechanism, the free public transportation vehicles are signed as the signed public transportation vehicles of the mechanism.
For example, the organization a signs a route with the public transportation system, and makes an agreement that the commuting route number for the organization a is "a 01 route", the commuting time is 7 hours to 9 hours, 12 hours to 14 hours, and 17 hours to 20 hours per day, and when the public transportation system detects that a bus with the number "286 route" is in an idle state, the route number of the bus is changed to "a 01 route", and the bus operates according to the commuting time.
For another example, the organization B signs a line contract with the public transportation system, and makes an agreement to sign xx1, xx2 and xx3 stations in the public transportation line of the public transportation vehicle with the public transportation line number of "233 lines" as the commuting stations of the organization B, so that the organization B pays the riding fee when the staff of the organization B takes a car at any station of the three stations.
For another example, the organization C signs a line contract with the public transportation system, appoints that the commuting line numbers of the organization C are 'C01 way' and 'C02 way', does not appoint the transit time, and appoints the commuting station, wherein the commuting station aiming at the 'C01 way' includes the east station of the organization C, the west station of the organization C and the lightnings cell station, and the commuting station aiming at the 'C02 way' includes the east station of the organization C and the shopping center station; the public transport company determines that the signed public transport vehicle with the line number of C01 passes through three stations of a C organization east station, a B organization west station and a Guangming cell station according to the commuting station provided by the C organization, and determines that the signed public transport vehicle with the line number of C02 passes through two stations of the C organization east station and a shopping center station.
It should be noted that the line signing form of the organization and the bus may include three items, that is, a commuting station of the signed bus corresponding to the bus line number is signed as the commuting station of the signed bus of the organization, the configuration of the commuting station of the signed bus is performed according to the station submitted by the organization, and the line number of the signed bus is updated to the commuting line number of the organization, or any one or two of the three items, or other forms agreed by the organization and the bus system in an actual scene, which is not limited in this embodiment; the content of line signing between the organization and the bus can include a commuting user identifier, a commuting time range, a commuting station identifier and a commuting line number, and also can include other contents agreed by the organization and the bus system in an actual scene.
In addition, in order to improve the perception degree of the staff of the organization, the commuting time and/or the commuting line number in the subscription information table may be displayed to the staff of the organization, and specifically, the manner of reaching the staff of the organization is not specifically limited in this embodiment.
In a specific implementation, after an organization signs with a public transportation system, in order to identify users who take a bus, avoid the resource loss of the organization due to the fact that the bus cost of all users who take the signed public transportation is paid by the organization, and further standardize the management of the users who take the signed public transportation, in an optional implementation manner provided by this embodiment, before obtaining the bus information of the users and the vehicle information, a synchronous signing information table after the organization and the public transportation system sign a line for the signed public transportation needs to be obtained; and recording the commuting user identification, the commuting time range and/or the commuting line number of the mechanism in the subscription information table.
Specifically, after the organization signs a contract with the public transportation system, a signing information table is established according to the employee list, the appointed commuting line number, the commuting station mark and the commuting time of the organization, and the signing information table is synchronized with a server, wherein the server is a third-party server capable of carrying out deduction and payment, such as a server corresponding to third-party payment application.
For example, a subscription information table of a mechanism a synchronized after signing with the public transportation system and a subscription information table of a mechanism B synchronized after signing with the public transportation system are obtained, and a user identifier of a mechanism employee, a commuting time and a commuting line number are recorded in the subscription information table of the mechanism a, wherein the commuting line number is "a 01" when the commuting time is 7 hours to 9 hours, 12 hours to 14 hours and 17 hours to 20 hours of each day; the contract information table of organization B records the user identification and the commuting station identification of employees of organization B, wherein the commuting station identification is xx1 station, xx2 station and xx3 station.
In the process that a user takes a public transport vehicle, the user needs to show a bus taking code to a code scanning assembly of the public transport vehicle to pay the bus taking fee, in specific implementation, when the user takes the signed public transport vehicle, the code scanning assembly of the signed public transport vehicle scans and identifies the bus taking code shown by the user through a third party application, and an identification result and component information of the code scanning assembly are uploaded to the public transport system; the public transportation system determines and synchronizes the user riding information and the vehicle information based on the identification result and the component information; specifically, in order to save resource loss caused by data selection and save cost, the riding information and vehicle information of all the users of the public transport vehicles synchronized by the public transport system can be acquired.
In this embodiment, the bus taking code is displayed by the user through a third-party application (for example, a payment application), and based on this, the bus taking fee payment method provided in this embodiment is applied to a server executed in cooperation with the third-party application.
In specific implementation, after the user riding information and the vehicle information are acquired, matching detection is performed on the user riding information and the vehicle information and a riding verification and cancellation protocol of a target mechanism. The target mechanism is a mechanism corresponding to a mechanism identifier bound with a user identifier contained in the user riding information; the riding verification and cancellation protocol refers to a protocol of a user and a server for riding, which is determined according to the contract information table synchronized by the target mechanism, and specifically, under the condition that the riding information and the vehicle information of the user meet the riding verification and cancellation protocol, the server calls a mechanism account of the target mechanism bound by the riding verification and cancellation protocol to pay riding cost; in other words, the riding verification and cancellation protocol is a riding verification and cancellation condition, and when the user riding information and the vehicle information satisfy the riding verification and cancellation condition, the riding fee is paid by the institution account corresponding to the institution identity bound with the user identity included in the user riding information. In order to improve the accuracy of the matching result and improve the efficiency of the matching detection, in an optional implementation manner provided in this embodiment, after obtaining the user riding information and the vehicle information, the following operations are further performed:
inquiring whether an organization identifier bound with the user identifier contained in the user riding information exists or not;
if yes, inquiring a signing information table of the target mechanism according to the mechanism identification, executing a step S104, and detecting whether the user riding information and the vehicle information are matched with a riding verification and cancellation protocol of the target mechanism to which the user belongs;
and if not, the user account corresponding to the user identification is utilized to pay the riding expense.
For example, obtaining the user riding information and the vehicle information synchronized with the public transportation system, querying that the user u1 is an employee of the organization a according to the user identification of the user u1 and the user identification of the user u1, querying a subscription information table corresponding to the organization a according to the organization identification of the organization a, and performing further matching detection on the user riding information and the vehicle information of the user u1 according to the subscription information table.
And step S104, detecting whether the user riding information and the vehicle information are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs.
The taking car verification and cancellation protocol in this embodiment includes that a user identifier included in the taking car information of the user has a matching relationship with any commuting user identifier in the subscription information table, a taking time included in the taking car information of the user has a matching relationship with a commuting time range recorded in the subscription information table, and/or a vehicle line number included in the vehicle information has a matching relationship with any commuting line number in the subscription information table. Specifically, the riding verification and cancellation protocol corresponding to each mechanism is determined according to the synchronous contract information table of each mechanism.
In the specific implementation, in the process of detecting whether the riding information and the vehicle information of the user are matched with the riding verification and cancellation protocol of the target mechanism to which the user belongs, firstly, whether a user identifier contained in the riding information of the user has a matching relationship with any commuting user identifier in a subscription information table of any mechanism is judged, that is, the following steps are performed: judging whether the user identification is a commuting user identification in any subscription information table, if so, performing further matching detection on the riding information and the vehicle information of the user according to the subscription information table where the user identification is located; and if not, the user account corresponding to the user identification is utilized to pay the riding expense. In an optional implementation manner provided by this embodiment, after querying the subscription information table of the target mechanism, whether the user riding information matches the riding verification and cancellation protocol is detected by performing the following steps:
judging whether the riding time contained in the riding information of the user is within the commuting time range recorded in the subscription information table;
if not, determining that the matching result is matching failure;
if so, judging whether the vehicle line number contained in the vehicle information is any commuting line number recorded in the subscription information table;
if so, determining that the matching result is successful;
if not, determining that the matching result is matching failure;
and recording the commuting time range and the commuting line number in the subscription information table.
For example, it is determined whether the riding time included in the user riding information of the user u1 is the commuting time agreed by the organization a, if so, it is determined whether the vehicle route number included in the vehicle information is any one of the commuting route numbers agreed by the organization a, if so, it is determined that the user riding information and the vehicle information of the user u1 are successfully matched with the riding verification agreement of the organization a, it is determined that the user u1 satisfies the condition that the organization a reports reimbursement due to public payment, and otherwise, the matching is failed.
In addition, the institution and the public transportation system may also agree with other contents, and when the institution and the public transportation system agree with a commuting station, in an optional implementation manner provided in this embodiment, the detection of whether the user riding information matches the riding verification and cancellation protocol is performed in the following manner:
judging whether a riding station identifier contained in the user riding information is any commuting station identifier recorded in the subscription information table;
if so, determining that the matching result is successful;
if not, determining that the matching result is matching failure;
and recording the commuting station identification in the subscription information table.
For example, it is inquired that the user identifier of the user u2 is bound with the mechanism identifier of the mechanism B and a subscription information table of the mechanism B is inquired, a commuting station identifier and a commuting line number agreed by the mechanism B and a public traffic system are recorded in the subscription information table of the mechanism B, whether a riding station of the user u2 is any commuting station recorded in the subscription information table is judged, if yes, whether a vehicle line number of the user u2 is any commuting line number recorded in the subscription information table is judged, if yes, it is determined that the riding information and the vehicle information of the user u2 are successfully matched with a riding verification and cancellation protocol of the mechanism B, and if not, it is determined that the riding information and the vehicle information of the user u2 are unsuccessfully matched with the riding verification and cancellation protocol of the mechanism B.
In specific implementation, if the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of a target institution to which the user belongs, step S106 is executed to call an institution account of the target institution to pay the riding fee, in an optional implementation manner provided in this embodiment, the institution account of the target institution is determined in the following manner:
and inquiring an institution account corresponding to the institution identification bound with the riding user identification according to the user identification contained in the riding information of the user.
In an optional implementation manner provided in this embodiment, if it is detected that the detection result of whether the user riding information and the vehicle information are matched with the riding verification and cancellation protocol of the target organization to which the user belongs is negative, it is determined that the user does not satisfy the condition of reimbursement due to public payment, a user account corresponding to a user identifier included in the user riding information is called to perform payment processing on the riding fee, and a user payment result is generated according to the payment processing result and sent to the user. Specifically, in the process of payment processing, resources in the user account are transferred to a bus account corresponding to the bus system according to the bus cost.
For example, if the user riding information and the vehicle information of the user u1 are successfully matched with the riding verification and sale protocol of the organization A, the organization account of the organization A is called to pay the riding fee of the user u1, and an organization payment result is sent to the user u 1; and when the failure of matching of the user riding information and the vehicle information of the user u2 with the riding verification and marketing protocol of the organization B is detected, calling a user account of the user u2 to pay the riding fee of the user u2, and sending a user payment result to the user u 2.
And step S106, calling the institution account of the target institution to pay the riding fee.
In an optional implementation manner provided by this embodiment, after an institution account is determined, according to the riding cost, resources in the institution account are transferred to a bus account corresponding to the bus system, and an institution payment result is sent to the user. For example, if the riding cost of the user u1 is m yuan, the corresponding fund in the institution account of institution a is transferred to the public transport account corresponding to the public transport system, and the result of resource transfer by institution a is sent to the user u 1.
The following describes the bus fare payment method provided in this embodiment with reference to fig. 2 by taking an application of the bus fare payment method provided in this embodiment in a user riding scene as an example. Referring to fig. 2, the bus fare payment method applied to the user riding scene specifically includes steps S202 to S216.
Step S202, user riding information and vehicle information of the commuting public transport vehicles which are synchronous with the public transport system and signed with the commuting line of the organization are obtained.
The riding information of the user is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus.
Step S204, judging whether an organization identifier of a target organization having a binding relation with the user identifier contained in the user riding information exists;
if yes, go to step S206;
if not, calling the user account corresponding to the user identification to pay the riding expense.
And step S206, inquiring a subscription information table corresponding to the target mechanism according to the mechanism identification.
Step S208, judging whether the riding time contained in the riding information of the user is within the commuting time range recorded in the contract information table;
if yes, go to step S210;
if not, calling the user account corresponding to the user identification to pay the riding expense.
Step S210, judging whether the vehicle route number contained in the vehicle information is the commuting route number recorded in the contract information table;
if yes, go to step S212;
if not, calling the user account corresponding to the user identification to pay the riding expense.
In step S212, the institution account corresponding to the institution identification of the target institution is queried.
In step S214, the fare payment process is performed on the riding fee included in the riding information of the user using the organization account.
Step S216, generating and sending payment processing results to the user.
In summary, according to the bus fare payment method provided in this embodiment, first, user riding information and vehicle information of a contracted bus signed with a mechanism and synchronized with a public transportation system are obtained, then it is detected whether the user riding information and the vehicle information match a riding verification and cancellation protocol of a target mechanism to which the user belongs, and if it is detected that the user riding information and the vehicle information match the riding verification and cancellation protocol, a mechanism account of the target mechanism is called to pay riding fare, so as to improve convenience of taking commuter vehicles by mechanism staff.
The embodiment of the bus fare payment device provided by the specification is as follows:
in the above embodiment, a method for paying the bus fee is provided, and correspondingly, a device for paying the bus fee is also provided, which is described below with reference to the accompanying drawings.
Referring to fig. 3, a schematic diagram of a bus fare payment device provided by the embodiment is shown.
Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions only need to refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.
The embodiment provides a bus fare payment device, including:
an obtaining module 302, configured to obtain user riding information and vehicle information of signed public transport vehicles which are synchronized with a public transport system and have a line contract with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus;
a detection module 304 configured to detect whether the user riding information and the vehicle information match a riding verification and cancellation protocol of a target organization to which the user belongs;
if so, a payment module 306 is run, which is configured to invoke the institution account of the target institution to pay the ride fee.
Optionally, the line subscription is performed by operating the following sub-modules:
the vehicle signing sub-module is configured to sign at least one public transport vehicle belonging to the public transport line number as a signed public transport vehicle of the organization;
and the line signing submodule is configured to sign a specific stop of a bus line corresponding to the bus line number as the commuting stop of the signed bus of the organization, and the line number of the signed bus is updated to the commuting line number of the organization according to the configuration of the commuting stop of the signed bus submitted by the organization.
Optionally, the bus fare payment device further includes:
the information table acquisition module is configured to acquire a signed information table synchronized after the mechanism and the public transportation system sign a sign for the signed public transportation vehicle; and recording the commuting user identification, the commuting time range and/or the commuting line number of the mechanism in the subscription information table.
Optionally, the riding verification and cancellation protocol is specifically configured to enable a user identifier included in the riding information of the user to have a matching relationship with any commuting user identifier in the subscription information table, enable riding time included in the riding information of the user to have a matching relationship with a commuting time range recorded in the subscription information table, and/or enable a vehicle line number included in the vehicle information to have a matching relationship with any commuting line number in the subscription information table.
Optionally, the bus fare payment device further includes:
the mechanism inquiry module is configured to inquire whether a mechanism identifier bound with the user identifier contained in the user riding information exists or not;
and if so, operating a matching detection module, wherein the matching detection module is configured to query a signing information table of the target mechanism according to the mechanism identification, and execute the step of detecting whether the riding information and the vehicle information of the user are matched with a riding verification and marketing protocol of the target mechanism to which the user belongs.
Optionally, whether the user riding information and the vehicle information are matched with the riding verification and cancellation protocol is detected by operating the following sub-modules:
the time judgment submodule is configured to judge whether the riding time contained in the riding information of the user is within the commuting time range recorded in the subscription information table;
if yes, operating a number judgment submodule, wherein the number judgment submodule is configured to judge whether a vehicle line number contained in the vehicle information is any commuting line number recorded in the subscription information table;
if yes, operating a result determination submodule, wherein the result determination submodule is configured to determine that the matching result is successful;
and recording the commuting time range and the commuting line number in the subscription information table.
Optionally, whether the user riding information and the vehicle information are matched with the riding verification and cancellation protocol is detected by operating the following sub-modules:
the station judgment submodule is configured to judge whether a riding station identifier contained in the user riding information is any commuting station identifier recorded in the subscription information table; if so, determining that the matching result is successful; and recording the commuting station mark in the signing information table.
Optionally, the institution account of the target institution is determined by operating the following sub-modules:
the mechanism account inquiry submodule is configured to inquire a mechanism account corresponding to a mechanism identifier bound with the riding user identifier according to a user identifier contained in the riding information of the user;
accordingly, the payment module 306 includes:
and the resource transfer sub-module is configured to transfer the resources in the institution account to a bus account corresponding to the bus system according to the bus cost.
Optionally, if the operation result after the operation of the detection module 304 is negative, the following modules are operated:
the user account calling module is configured to call a user account corresponding to the user identifier contained in the user riding information to pay the riding fee;
and the payment processing module is configured to generate a user payment result according to the payment processing result and send the user payment result to the user.
Optionally, the code scanning component scans and identifies the riding code displayed by the user through a third-party application, and uploads an identification result and component information of the code scanning component to the public transportation system; and the public transportation system determines and synchronizes the user riding information and the vehicle information based on the identification result and the component information.
The embodiment of the bus fare payment device provided by the specification is as follows:
on the basis of the same technical concept, one or more embodiments of the present specification further provide a bus fare payment device for executing the bus fare payment method, and fig. 4 is a schematic structural diagram of the bus fare payment device provided in one or more embodiments of the present specification.
As shown in fig. 4, the bus fare payment device may have a relatively large difference due to different configurations or performances, and may include one or more processors 401 and a memory 402, where one or more stored applications or data may be stored in the memory 402. Wherein memory 402 may be transient or persistent. The application stored in memory 402 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a bus fare payment device. Still further, the processor 401 may be configured to communicate with the memory 402 to execute a series of computer-executable instructions in the memory 402 on a bus fare payment device. The bus fare payment device may also include one or more power sources 403, one or more wired or wireless network interfaces 404, one or more input/output interfaces 405, one or more keyboards 406, etc.
In one particular embodiment, a bus fare payment device includes a memory, and one or more programs, where 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 configured to be executed by one or more processors include computer-executable instructions for:
acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus;
detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs;
and if so, calling the institution account of the target institution to pay the riding fee.
Optionally, the line subscription includes:
signing at least one bus belonging to the bus route number as a signed bus of the mechanism;
and signing a specific station of a bus line corresponding to the bus line number into the commuting station of the signed bus of the organization, and carrying out the configuration of the commuting station of the signed bus according to the station submitted by the organization, and/or updating the line number of the signed bus into the commuting line number of the organization.
Optionally, the computer executable instructions, when executed, further comprise:
inquiring whether an organization identifier bound with the user identifier contained in the user riding information exists or not;
if so, inquiring a signing information table of the target mechanism according to the mechanism identification, and executing the step of detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of the target mechanism to which the user belongs.
Optionally, whether the user riding information and the vehicle information are matched with the riding verification and cancellation protocol is detected in the following manner:
judging whether the riding time contained in the riding information of the user is within the commuting time range recorded in the subscription information table;
if so, judging whether the vehicle line number contained in the vehicle information is any commuting line number recorded in the subscription information table;
if so, determining that the matching result is successful;
and recording the commuting time range and the commuting line number in the subscription information table.
Optionally, whether the user riding information and the vehicle information are matched with the riding verification and cancellation protocol is detected in the following manner:
judging whether a riding station identifier contained in the user riding information is any commuting station identifier recorded in the subscription information table;
if so, determining that the matching result is successful;
and recording the commuting station identification in the subscription information table.
An embodiment of a storage medium provided in this specification is as follows:
on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the bus fare payment method described above.
The storage medium provided in this embodiment is used to store computer-executable instructions, and when executed, the computer-executable instructions implement the following processes:
acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus;
detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of a target mechanism to which the user belongs;
and if so, calling the institution account of the target institution to pay the riding fee.
Optionally, the line subscription includes:
signing at least one public transport vehicle belonging to the public transport line number as a signed public transport vehicle of the mechanism;
and signing a specific station of a bus line corresponding to the bus line number into the commuting station of the signed bus of the organization, and carrying out the configuration of the commuting station of the signed bus according to the station submitted by the organization, and/or updating the line number of the signed bus into the commuting line number of the organization.
Optionally, when executed, the computer-executable instructions further implement the following process:
inquiring whether an organization identifier bound with the user identifier contained in the user riding information exists or not;
if yes, inquiring a signing information table of the target mechanism according to the mechanism identification, and executing a step of detecting whether the riding information and the vehicle information of the user are matched with a riding verification and cancellation protocol of the target mechanism to which the user belongs.
Optionally, whether the user riding information and the vehicle information are matched with the riding verification and cancellation protocol is detected in the following manner:
judging whether the riding time contained in the riding information of the user is within the commuting time range recorded in the subscription information table;
if so, judging whether the vehicle line number contained in the vehicle information is any commuting line number recorded in the subscription information table;
if so, determining that the matching result is successful;
and recording the commuting time range and the commuting line number in the subscription information table.
It should be noted that the embodiment of the storage medium in this specification and the embodiment of the method for paying the bus fare in the bus in this specification are based on the same inventive concept, so that specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described again.
Characteristic embodiments of the present specification have been described above. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. Additionally, the processes depicted in the accompanying figures do not necessarily require the order in which features are shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is an integrated circuit whose Logic functions are determined by a user programming the Device. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a characteristic Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbylangue (Hardware Description Language), vhjhdul, and vhigh-Language, which are currently used in most general. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, 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, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, 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.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.
One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
One or more embodiments of the specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims (10)

1. A bus fare payment method comprises the following steps:
acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus; the user riding information comprises a user identifier and a riding station identifier;
inquiring whether an organization identifier bound with the user identifier exists; if yes, inquiring a signing information table of a target mechanism according to the mechanism identification, and judging whether the riding station identification is any commuting station identification recorded in the signing information table;
and if so, calling the institution account of the target institution to pay the riding fee.
2. The bus fare payment method of claim 1, the line contract, comprising:
signing at least one public transport vehicle belonging to the public transport line number as a signed public transport vehicle of the mechanism;
and signing a specific station of a bus line corresponding to the bus line number into the commuting station of the signed bus of the organization, and carrying out the configuration of the commuting station of the signed bus according to the station submitted by the organization, and/or updating the line number of the signed bus into the commuting line number of the organization.
3. The method for paying bus riding fee according to claim 1, wherein before the step of obtaining the user riding information and the vehicle information of the signed bus which is synchronous with the public transportation system and has line contract with the organization is executed, the method further comprises the following steps:
acquiring a signing information table synchronized after the mechanism and the public transport system sign a line for the signed public transport vehicle;
and recording the commuting user identification, the commuting time range and/or the commuting line number of the mechanism in the subscription information table.
4. A method of payment of a ride fee for a bus as in claim 1, further comprising:
judging whether the riding time contained in the riding information of the user is within the commuting time range recorded in the subscription information table;
if yes, judging whether the vehicle line number contained in the vehicle information is any commuting line number recorded in the contract information table;
if yes, executing the step of calling the institution account of the target institution to pay the riding fee;
and recording the commuting time range and the commuting line number in the subscription information table.
5. A method as claimed in claim 1 wherein the institution account of the target institution is determined by:
inquiring an institution account corresponding to the institution identification bound with the user identification according to the user identification;
correspondingly, the invoking of the institution account of the target institution for payment of the riding fee comprises:
and transferring the resources in the institution account to a public transport account corresponding to the public transport system according to the riding cost.
6. The bus fare payment method according to claim 1, if the query indicates that the execution result after the execution of the agency identifier operation bound to the user identifier is negative, executing the following operation:
calling a user account corresponding to the user identification to pay the riding expense;
and generating a user payment result according to the payment processing result and sending the user payment result to the user.
7. The bus fare payment method according to claim 1, the code scanning component scans and identifies a riding code displayed by the user through a third party application, and uploads an identification result and component information of the code scanning component to the bus system; the public transportation system determines and synchronizes the user riding information and the vehicle information based on the recognition result and the component information.
8. A bus fare payment device comprising:
the acquisition module is configured to acquire user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus; the user riding information comprises a user identifier and a riding station identifier;
the mechanism inquiry module is configured to inquire whether a mechanism identifier bound with the user identifier exists; if yes, inquiring a signing information table of a target mechanism according to the mechanism identification; judging whether the bus station mark is any commuting station mark recorded in the signing information table;
and if so, operating a payment module, wherein the payment module is configured to call the institution account of the target institution to pay the riding fee.
9. A bus fare payment device comprising:
a processor; and (c) a second step of,
a memory configured to store computer-executable instructions that, when executed, cause the processor to:
acquiring user riding information and vehicle information of signed public transport vehicles which are synchronous with a public transport system and carry out line contract with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning assembly configured by the contracted public transport vehicle; the user riding information comprises a user identifier and a riding station identifier;
inquiring whether an organization identifier bound with the user identifier exists; if so, inquiring a signing information table of a target mechanism according to the mechanism identifier, and judging whether the riding station identifier is any commuting station identifier recorded in the signing information table;
and if so, calling the institution account of the target institution to pay the riding fee.
10. A storage medium storing computer-executable instructions that when executed implement the following:
acquiring user riding information and vehicle information of a signed public transport vehicle which is synchronous with a public transport system and performs line signing with a mechanism; the user riding information is determined based on riding codes of the user, which are acquired by a code scanning component configured by the signed bus; the user riding information comprises a user identifier and a riding station identifier;
inquiring whether an organization identifier bound with the user identifier exists; if so, inquiring a signing information table of a target mechanism according to the mechanism identifier, and judging whether the riding station identifier is any commuting station identifier recorded in the signing information table;
and if so, calling the institution account of the target institution to pay the riding fee.
CN202110332383.2A 2021-03-29 2021-03-29 Bus fee payment method and device Active CN113065863B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202210655468.9A CN115063136A (en) 2021-03-29 2021-03-29 Bus fare payment method and device
CN202110332383.2A CN113065863B (en) 2021-03-29 2021-03-29 Bus fee payment method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110332383.2A CN113065863B (en) 2021-03-29 2021-03-29 Bus fee payment method and device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202210655468.9A Division CN115063136A (en) 2021-03-29 2021-03-29 Bus fare payment method and device

Publications (2)

Publication Number Publication Date
CN113065863A CN113065863A (en) 2021-07-02
CN113065863B true CN113065863B (en) 2022-07-08

Family

ID=76564314

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202210655468.9A Pending CN115063136A (en) 2021-03-29 2021-03-29 Bus fare payment method and device
CN202110332383.2A Active CN113065863B (en) 2021-03-29 2021-03-29 Bus fee payment method and device

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202210655468.9A Pending CN115063136A (en) 2021-03-29 2021-03-29 Bus fare payment method and device

Country Status (1)

Country Link
CN (2) CN115063136A (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110136281A (en) * 2019-05-30 2019-08-16 陕西交通电子工程科技有限公司 Highway self-service charging method, apparatus, computer equipment and storage medium

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105719475B (en) * 2016-03-21 2018-01-05 广州地理研究所 A kind of elastic public bus network is set and running scheduling method
CN106600268A (en) * 2016-12-21 2017-04-26 华录智达科技有限公司 Intelligent vehicle terminal based on mobile payment and payment method
CN108376321A (en) * 2018-03-22 2018-08-07 西安艾润物联网技术服务有限责任公司 Unit vehicle method of payment, device and computer readable storage medium
CN110874770B (en) * 2018-09-03 2023-07-04 阿里巴巴集团控股有限公司 Invoice processing method and device, invoice processing service processing method and device, server and electronic equipment
CN110827014A (en) * 2018-09-28 2020-02-21 武汉小码联城科技有限公司 Riding payment method and system based on enterprise account, enterprise terminal and user terminal
CN112258174A (en) * 2019-07-22 2021-01-22 北京车和家信息技术有限公司 Payment method and related equipment
CN111242603B (en) * 2020-01-03 2024-06-11 腾讯科技（深圳）有限公司 Riding settlement method and device based on blockchain

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110136281A (en) * 2019-05-30 2019-08-16 陕西交通电子工程科技有限公司 Highway self-service charging method, apparatus, computer equipment and storage medium

Also Published As

Publication number Publication date
CN115063136A (en) 2022-09-16
CN113065863A (en) 2021-07-02

Similar Documents

Publication Publication Date Title
CN110134668B (en) Data migration method, device and equipment applied to blockchain
CN112232795A (en) Transaction processing method, device, equipment and system
CN113128508A (en) License plate number-based payment processing method and device
CN113222679A (en) Bill generation method and device
CN113435862A (en) Bill processing method and device based on mailbox
CN115293533A (en) Order dispatching processing method and device
CN112288502B (en) Electronic riding invoice processing method and device
CN112148737B (en) Attendance checking processing method and device
CN114006924A (en) Vehicle service processing method and device
CN113065863B (en) Bus fee payment method and device
CN108282471B (en) Electronic certificate transmission method, device and equipment
CN112990940B (en) Enterprise authentication method and device
CN111414436B (en) Data pushing method, device, equipment and system
CN111738473B (en) Processing method, device, equipment and system for ticket booking service
CN113643030B (en) Transaction processing method, device and equipment
CN112396707A (en) Bus cost calculation method and device
CN116017395A (en) Resource transfer processing method and device
CN113672784B (en) Vehicle information processing method, device and system based on block chain
CN115330372A (en) Payment processing method and device based on prepaid voucher
CN112693496B (en) Train taking reminding processing method and device for railway train
CN111324778B (en) Data and service processing method and device and electronic equipment
CN114529180A (en) Data processing method and device
CN106548331B (en) Method and device for determining release sequence
CN110321752B (en) Method and device for checking offline graphic codes
CN112561483A (en) Stroke processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20230113

Address after: 200120 Floor 15, No. 447, Nanquan North Road, China (Shanghai) Pilot Free Trade Zone, Pudong New Area, Shanghai

Patentee after: Alipay.com Co.,Ltd.

Address before: 310000 801-11 section B, 8th floor, 556 Xixi Road, Xihu District, Hangzhou City, Zhejiang Province

Patentee before: Alipay (Hangzhou) Information Technology Co.,Ltd.