WO2020228771A1 - 一种生成计费信息的方法,以及终端、服务器和系统 - Google Patents

一种生成计费信息的方法,以及终端、服务器和系统 Download PDF

Info

Publication number
WO2020228771A1
WO2020228771A1 PCT/CN2020/090230 CN2020090230W WO2020228771A1 WO 2020228771 A1 WO2020228771 A1 WO 2020228771A1 CN 2020090230 W CN2020090230 W CN 2020090230W WO 2020228771 A1 WO2020228771 A1 WO 2020228771A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
information
charging
bus
server
Prior art date
Application number
PCT/CN2020/090230
Other languages
English (en)
French (fr)
Inventor
王义然
李维国
姚建丽
万海燕
Original Assignee
京东方科技集团股份有限公司
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 京东方科技集团股份有限公司 filed Critical 京东方科技集团股份有限公司
Priority to US17/298,091 priority Critical patent/US12086850B2/en
Publication of WO2020228771A1 publication Critical patent/WO2020228771A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q30/00Commerce
    • G06Q30/04Billing or invoicing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/023Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/029Location-based management or tracking services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/42Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for mass transport vehicles, e.g. buses, trains or aircraft
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Definitions

  • This application relates to but is not limited to the field of communication technology, and in particular refers to a method for generating charging information, as well as a terminal, a server, and a system.
  • NFC Near Field Communication
  • NFC technology is a short-distance and high-frequency wireless communication method that can realize identification and data interaction with compatible devices within a short distance.
  • Common applications include swiping cards for buses and company access cards.
  • the current public transportation billing method using NFC technology is to perform NFC card swiping operations when passengers get on and off the bus, and charge by swiping the number of stations or distance traveled to get on and off the bus.
  • passengers need to swipe their cards once at the beginning and end of the trip to determine the beginning and end of the trip.
  • the embodiments of the present disclosure provide a method for generating charging information, a terminal, a server, and a system.
  • the embodiment of the present disclosure provides a method for generating charging information, including:
  • the first terminal whose distance from the public transportation is greater than the distance threshold is performed to terminate the charging operation and generate charging information.
  • the charging termination operation is performed on the first terminal whose distance to the public transportation is greater than a distance threshold according to the location information of the terminal and the public transportation information, include:
  • the method further includes:
  • the performing the charging termination operation on the first terminal includes:
  • the charging result information including the ending charging information sent to the first terminal and the second terminal whose distance from the public transportation means is less than or equal to the distance threshold
  • the terminal's rejection ends the charging message.
  • the embodiment of the present disclosure also provides a method for generating charging information, including:
  • the terminal that got off the car and did not swipe the card is inquired, and the current travel of the terminal is ended and charging information is generated.
  • the embodiment of the present disclosure also provides a method for generating charging information, including:
  • the server Sending an end billing request to the server, where the end billing request includes location information of the terminal and public transportation information, where the public transportation information is information in the current itinerary of the terminal;
  • the charging result information returned by the server is received and the charging information is generated.
  • the charging result information includes the charging termination information or the charging termination rejection message, wherein the charging termination information is the server according to the terminal.
  • the location information and the public transportation information determine that the distance between the terminal and the public transportation is greater than the distance threshold, and the terminal performs a charging operation on the terminal, and then the terminal is sent to the terminal.
  • the method before the sending the end charging request to the server, the method further includes:
  • the real-time monitoring of whether the terminal gets off the vehicle without swiping the card includes:
  • the terminal gets off the vehicle without swiping the card.
  • a prompt message for instructing the terminal to get off the vehicle without swiping the card is displayed.
  • the embodiment of the present disclosure further provides a server, including: a memory and a processor;
  • the memory is configured to store executable instructions
  • the processor is configured to, when executing the executable instructions stored in the memory, implement any one of the methods for generating charging information executed by the server.
  • An embodiment of the present disclosure also provides a terminal, including: a memory and a processor;
  • the memory is configured to store executable instructions
  • the processor is configured to, when executing the executable instructions stored in the memory, implement any one of the above-mentioned methods for generating charging information executed by the terminal.
  • the embodiment of the present disclosure also provides a charging system, including: the server according to any one of the above, the terminal according to any one of the above, and a public transportation card machine;
  • the public transportation card machine is configured to write public transportation information to a terminal that performs a card swipe and boarding operation, and delete the stored public transportation information from a terminal that performs a swipe card and get off operation;
  • the public transportation card machine is also configured to upload information to the server that the terminal performs the operation of swiping in and getting off the car by swiping the card.
  • the embodiment of the present disclosure also provides a computer-readable storage medium, the computer-readable storage medium stores executable instructions, and when the executable instructions are executed by a processor, it can realize any generation of any item executed by the server.
  • the method for charging information, or, when the executable instruction is executed by the processor, the method for generating charging information can be implemented as any one of the above-mentioned terminal executions.
  • FIG. 1 is a flowchart of a method for generating charging information according to an embodiment of the disclosure
  • FIG. 2 is a flowchart of another method for generating charging information according to an embodiment of the disclosure
  • FIG. 3 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • FIG. 4 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • FIG. 5 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • FIG. 6 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • FIG. 7 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • FIG. 8 is an interaction flowchart of a method for generating charging information provided by an embodiment of the disclosure.
  • FIG. 9 is a schematic structural diagram of a server provided by an embodiment of the disclosure.
  • FIG. 10 is a schematic structural diagram of another server provided by an embodiment of the disclosure.
  • FIG. 11 is a schematic structural diagram of a terminal provided by an embodiment of the disclosure.
  • FIG. 12 is a schematic structural diagram of another terminal provided by an embodiment of the disclosure.
  • FIG. 13 is a schematic structural diagram of a system for generating charging information provided by an embodiment of the disclosure.
  • Fig. 1 is a flowchart of a method for generating charging information provided by an embodiment of the disclosure.
  • the present disclosure can be applied to a city bus system to generate charging information according to the distance and/or time the user actually rides, so as to obtain fee information consistent with the actual use of the user, that is, the current Disclosure can be used to bill users.
  • the system for generating charging information involved in other embodiments may be referred to as "charging system" for short.
  • the method for generating billing information provided in this embodiment is applicable to a situation where passengers take a bus and bill the passenger’s journey.
  • the method for generating billing information may be executed by a server for charging for a ride.
  • the charging information is generated through communication with the card swiping terminal used by the passengers.
  • the method for generating charging information provided by the embodiment of the present disclosure may include the following steps:
  • S110 Receive a charging end request sent by the terminal, where the charging end request includes location information of the terminal and bus information;
  • the method for generating billing information provided by the embodiment of the present disclosure is a processing manner in which the server for performing bus billing performs charging for the passenger based on the getting on and off of the bus.
  • the way that the server learns the passenger's getting on and off the bus may be based on the swiping on board operation and/or the swiping off operation performed by the bus swiping terminal used by the passenger.
  • the terminal used by the passenger has performed the swiping and boarding operation, but the swiping and disembarking operation has not been performed, it is considered that the passenger is currently riding on the bus on which the passenger has swiped the card; for another example, the terminal used by the passenger has performed the swiping and boarding operation, And the passenger is deemed to have completed the trip by swiping the card to get off the same bus; for another example, the terminal used by the passenger has a record of the swiping and getting on the bus during the previous trip, and the passenger has been in the previous trip If the itinerary does not perform the swipe card and get off operation, if the current ride itinerary is executed, it will be considered that the passenger's previous ride trip has forgotten to perform the swipe and get off operation.
  • the previous ride trip is usually recorded
  • the cost of the whole journey is to end the previous trip, so that it is convenient to record the current trip.
  • the server will perform the swiping and boarding operations next time the passengers use the terminal, that is, when starting a new ride, the The itinerary is fully billed, which causes relatively large economic losses to passengers.
  • the terminal used to perform bus swiping in the embodiment of the present disclosure is, for example, a mobile phone with NFC function, and an application that performs swiping interactive operations with the bus card machine and server can be installed in the mobile phone (Application , Abbreviated as: APP), to realize the swiping operation and the way of charging through the information interaction with the server, open the APP in the mobile phone and approach the bus card machine to perform the swipe and boarding operations, and perform the swipe and boarding operations
  • the program can also be a small program in an existing APP in a mobile phone, such as a ride code in WeChat or Alipay.
  • the terminal used to perform bus swiping in the embodiments of the present disclosure can also be used in conjunction with a NFC bus card and a mobile phone.
  • a NFC bus card In the way of binding the NFC bus card in the mobile phone APP, charging is realized by the information exchange between the mobile phone and the server.
  • the terminal used to perform the bus swiping can exchange information with the server, and the server can receive an end billing request actively sent by the terminal, and the end billing request can be when the passenger finds that he has got off the bus. And in the case of not swiping the card, through the operation performed on the terminal side to send the end billing request to the server, the operation performed by the passenger on the terminal side is, for example, clicking on the option of forcibly ending billing in the mobile phone APP.
  • the method of ending charging can be set as follows: after the server receives the request for ending charging, it can first determine whether the terminal that sent the request meets the conditions for ending the charging, for example, judge whether the terminal that sent the request meets the end based on the distance between the terminal and the bus Billing conditions.
  • the charging termination request sent by the terminal in the embodiment of the present disclosure may carry the current location information of the terminal to provide the server with basic information for judgment.
  • the bus card machine can write the bus information into the terminal through the NFC communication with the terminal, and the terminal billing request sent by the terminal can also carry the stored bus Bus information, the bus information includes, for example, the line name of the bus, the license plate number, and the number of the bus card machine.
  • the server can learn the current location information of the bus based on the bus information , Thereby judging whether the terminal meets the conditions for ending charging according to the location information of the bus and the terminal’s location information.
  • the distance between the terminal and the bus can be determined based on the location information of the terminal and the bus information.
  • the distance threshold can be set to not less than the length of the bus, and the passenger is considered to have got off the bus.
  • the distance threshold in the embodiment of the present disclosure may be the distance information set in the server to determine whether the passenger has got off the bus. Due to different bus models, different distance thresholds can be set for different buses. The distance threshold is also It can be reflected in the bus information in the charging end request sent by the terminal. For example, if the bus information has the model of the bus, the server can determine the appropriate distance threshold according to the model of the bus to determine the passengers Have you gotten off?
  • the terminal that the server determines that the charging termination condition is met is defined as the first terminal, and the first terminal is the terminal that sends a charging termination request to the server and whose distance from the bus is greater than the distance threshold.
  • the server receives the terminal's location information and bus information sent by the terminal to end the charging request, and according to the location information of the terminal and bus information in the request, the The first terminal whose distance of the bus is greater than the distance threshold executes an ending charging operation.
  • the above method for generating billing information provided by the embodiments of the present disclosure does not deduct the full fee for passengers who take a bus and forget to swipe their card when getting off the bus. Instead, the billing can be forced to end according to the location of the passenger (that is, the end of the terminal sending The location information of the terminal in the billing request) deducts the cost of the corresponding station or the mileage.
  • the embodiment of the present disclosure provides The method of generating billing information can greatly reduce the economic loss caused by passengers forgetting to swipe their card when getting off the bus, and has a great market prospect.
  • FIG. 2 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • the implementation of S120 may include the following steps:
  • S122 Determine whether the distance between the terminal and the bus is greater than the distance threshold according to the location information of the terminal and the location information of the bus; when the distance is greater than the distance threshold, execute S123;
  • S123 Perform an ending charging operation on the first terminal whose distance from the bus is greater than the distance threshold.
  • the end billing request received by the server includes bus information
  • the server can interact with the corresponding bus card machine according to the known bus information, that is, according to the above-mentioned bus information
  • the server can obtain the current location information of the bus in the journey for which the terminal requests to end charging.
  • the server combines the location information of the bus acquired in real time and the location information of the terminal in the request to calculate the current distance between the terminal that sent the request and the bus, and compare the calculated distance with a known distance threshold If the calculated current distance is greater than the distance threshold, it is considered that the passenger using the terminal (that is, the first terminal) has got off the vehicle, and the charging operation can be performed on the first terminal.
  • the server determines that the distance between the terminal and the bus is less than or equal to the distance threshold, it considers that the passenger using the terminal (that is, the second terminal) is not currently getting off the bus, and it will not execute the operation on the first terminal End the billing operation. At this time, the server may send a reminder message to the second terminal to remind the passenger using the second terminal that the distance between the current bus and the bus is too close, and the billing cannot be forcibly terminated temporarily. Please try again later.
  • the server can send it the end of charging information, thereby instructing the first terminal to clear the bus information written by the terminal when swiping the card to board the bus, and deduct the corresponding travel itinerary cost of.
  • S124 Send a charging rejection end message to a second terminal whose distance from the bus is less than or equal to a distance threshold;
  • S125 Send charging end information to the first terminal.
  • the charging result information sent by the server to the terminal includes information sent to two types of terminals in different situations.
  • the charging result information sent by the server to it is End billing information
  • the end billing information can be returned to the APP of the first terminal
  • the APP will access the end billing information into the NFC bus card or the NFC module of the machine, and deduct the corresponding travel expenses.
  • the server sends the charging result information as a rejection to end the charging message, which is also returned to the terminal
  • the APP reminds the passenger that the billing cannot be forcibly terminated for the time being, please try again later, that is, the passenger can send the billing termination request again through the second terminal later. Therefore, after S124 in the embodiment shown in FIG. 2, it is possible to return to perform S110.
  • the terminal that sends the charging end request to the server may include the second terminal that received the message of refusing to end the charging in S124.
  • FIG. 3 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • the method provided in this embodiment of the present invention may further include:
  • S111 Determine whether the terminal sending the end charging request has an unfinished journey; when it is determined that the terminal has an unfinished journey, the server performs subsequent judgments according to the end charging request, and performs corresponding operations based on the judgment structure.
  • Figure 3 shows an example based on the process shown in Figure 2 above.
  • the passengers of these terminals are considered to have the prerequisite for getting off the bus and forgetting to swipe their card, that is, these passengers The operation of swiping the card to get on the bus has been performed, but the operation of swiping the card to get off the bus has not been performed.
  • the server can continue to perform the operation of S120.
  • the server executes the judgment result of S111, when some terminals sending the request have unfinished itineraries, the server executes S120 on these terminals (that is, the first terminal and the second terminal in the above embodiment); when the server executes S111 In the judgment result, when some terminals sending the request do not have unfinished itineraries, the server executes S126 on these terminals (for example, the third terminal).
  • the method for generating billing information adopts the APP technology of the terminal, the NFC communication technology of the terminal (or bus card) and the bus card machine, and the billing system of the server.
  • the passenger can actively initiate a request to the server through the operation performed on the terminal side to request the server to end the billing of the current trip.
  • the server After the server receives the end billing request from the terminal, it can be
  • the actual situation obtained determines whether the terminal meets the conditions for ending charging, such as determining whether the terminal has a trip that needs to be charged, and whether the terminal has got off the vehicle and has not yet swiped the card, so that the first terminal that meets the conditions for ending the charging is executed for the ending calculation. Fee operation.
  • the foregoing method of generating billing information can be operated by the three entities of a terminal with NFC function, a bus card machine, and a server.
  • a terminal with NFC function For passengers who take the bus and forget to swipe their card when getting off the bus, it will not The full cost is deducted, but the cost of the corresponding station or mileage can be deducted according to the location where the passenger is forced to end the billing.
  • the full fee is deducted for the passenger who forgets to get off and swipe the card Compared with the method, it can greatly reduce the economic loss caused by passengers getting off the bus and forgetting to swipe their card. Therefore, this billing method has a greater market prospect.
  • FIG. 4 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • the method for generating billing information provided in this embodiment is applicable to a situation where passengers take a bus and bill the passenger’s journey.
  • the method for generating billing information can be executed by a server for charging for a ride.
  • the server performs ride charging through communication with the card swiping terminal used by passengers.
  • the method for generating charging information provided by the embodiment of the present disclosure may include the following steps:
  • S140 Receive travel end information sent by the bus card machine, where the travel end information includes terminal information that has performed the operation of swiping the card to board the bus.
  • the method of generating billing information provided in any of the above-mentioned embodiments shown in Figs. 1 to 3 of the present disclosure is that when a passenger who uses a terminal to perform a swipe to board the vehicle finds that he has got off the vehicle and has not performed the swipe to get off operation, take the initiative
  • the terminal sends an end billing request to the server to end the passenger's current journey through this method.
  • the passenger has got off the bus and has not performed the swipe card to get off the car, and has not found that the card has been forgotten to perform the swipe to get off the car, or the terminal has not been actively used. Request the server to end the billing for this trip.
  • the terminal information of the terminal used by the passenger is still stored on the bus card machine, and the terminal also always stores the information of this unfinished trip, such as bus information and Information to perform the operation of swiping on the car.
  • the terminal will detect that the terminal has an unfinished itinerary when the terminal is swiped to board the bus next time, and the full amount of the unfinished itinerary will be deducted, which not only causes a relatively large impact on passengers
  • the terminal, server and bus card machine have always stored relevant information about the terminal’s unfinished trip, which is not conducive to the management of the server, bus card machine and the internal storage information of the terminal.
  • the bus card will send the trip end information to the server. Since the terminal swipes and gets on and off the bus, the passengers who swipe the card are executed once. After getting off the bus and swiping the card, the bus card will clear the information of the terminal, that is, after the bus arrives, the information of the terminal that normally performs swiping on and off the bus has been deleted, and for the terminal that performs swiping on the bus and not performing the swipe to get off the bus , The information of the card-swiping and boarding operations it has performed is still recorded in the bus card machine. Therefore, the trip end information received by the server may include the terminal information that has performed the card-swiping and boarding operations.
  • S150 Find out the terminal that has not swiped the card to get off the car according to the travel end information, and end the current travel of the terminal.
  • the server receives the trip end information sent by the bus card machine, and knows that the current trip of the corresponding bus has ended, and all passengers of the current trip get off the bus. When it reads the content of the trip end information It can be queried that some passengers have got off the bus and did not use the terminal to perform the swipe card and get off operation. At this time, the server can actively end the current trip of these terminals for the terminals that have not been swiped by the server.
  • the method provided in the embodiment of the present disclosure may further include the following steps:
  • S160 Send end billing information to the terminal, so that the terminal clears the stored bus information according to the end billing information, and deducts the cost of the current trip.
  • the server after the server ends the current trip of the terminal that has not performed the swipe card to get off the bus, it can send the end billing information to these terminals, so that the terminal deducts the cost of the current trip at the local end and clears the stored bus information . Since the trip end information received by the server in the embodiment of the present disclosure records the information of the terminal's swiping and boarding operations, the charging standard for the terminal can be: from the station where the card is swiped and boarding to the corresponding station or boarding at the end of the trip The cost of mileage.
  • the server receives the trip end information sent by the bus card machine.
  • the trip end information includes the terminal information that performs the card swiping and boarding operation, and according to the above trip end information, the query finds out Swipe to get off the terminal and end the current journey of these terminals.
  • the fee will not be deducted when the passenger uses the terminal next time to swipe the card to board the bus, but a server based on the received
  • the trip end information actively determines which terminals are performing the swipe card and get off operation, and the server actively terminates the current trips of these terminals.
  • the cost of the corresponding station or mileage can be deducted according to the station where the passenger uses the terminal to swipe the card to get on the bus, not only to a certain extent It also reduces the economic loss of passengers, and does not need to wait until the next time the terminal swipes the card to board the bus.
  • the current trip can be ended, avoiding the recording of redundant information, which is beneficial to the information management and optimization of the bus billing system. market expectation.
  • Fig. 5 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • the method for generating billing information provided in this embodiment is applicable to a situation where passengers take a bus and actively initiate billing for the ride through a terminal.
  • the method for generating billing information can be executed by the terminal used by the passenger, and the terminal is connected with The NFC communication of the bus card machine and the communication with the server complete the charging for the current journey.
  • the method for generating charging information provided by the embodiment of the present disclosure may include the following steps:
  • S210 Send a billing termination request to the server, where the billing termination request includes location information of the terminal and bus information, and the bus information is information in the current itinerary of the terminal.
  • the method for generating billing information is a processing manner in which a terminal for swiping a card for a ride requests a server to charge a ride for its current trip.
  • a terminal for swiping a card for a ride requests a server to charge a ride for its current trip.
  • passengers board and get off the bus, they can use the bus swiping terminal to perform swiping on and off operations, and all the swiping and getting off operations performed by passengers can be reported to the server by the bus card machine. Therefore, the server Based on the swipe card boarding operation and/or the swiping card getting off operation performed by the bus swiping terminal used by the passenger, the passenger's getting on and off the bus can be known, so as to realize the ride billing.
  • the terminal used by the passenger has performed the swiping and boarding operation, but the swiping and disembarking operation has not been performed, it is considered that the passenger is currently riding on the bus on which the passenger has swiped the card; for another example, the terminal used by the passenger has performed the swiping and boarding operation, And the passenger is deemed to have completed the trip by swiping the card to get off the same bus; for another example, the terminal used by the passenger has a record of the swiping and getting on the bus during the previous trip, and the passenger has been in the previous trip If the itinerary does not perform the swipe card and get off operation, if the current ride itinerary is executed, it will be considered that the passenger's previous ride trip has forgotten to perform the swipe and get off operation.
  • the previous ride trip is usually recorded
  • the cost of the whole journey is to end the previous trip, so that it is convenient to record the current trip.
  • the server will perform the swiping and boarding operations next time the passengers use the terminal, that is, when starting a new ride, the The itinerary is fully billed, which causes relatively large economic losses to passengers.
  • the terminal used to perform bus swiping in the embodiments of the present disclosure can exchange information with the server.
  • passengers using the terminal find that they have got off the bus and have not swiped the card, they can perform operations on the terminal side ,
  • the terminal actively sends a billing termination request to the server, and the operation performed by the passenger on the terminal side is, for example, clicking on the option of forcibly ending billing in the APP of the mobile phone.
  • the charging end request can carry the current location information of the terminal and the bus information in the current unfinished journey of the terminal.
  • the bus information is the current journey opened by the terminal (execute the journey opened when the card was swiped last time) When the time, the bus card machine writes the information in the terminal.
  • the terminal used to perform bus swiping in the embodiment of the present disclosure is, for example, a mobile phone with NFC function, which can be implemented by installing an APP that performs swiping interactive operations with the bus card machine and the server in the mobile phone.
  • Swipe card operation and billing through information interaction with the server open the APP in the mobile phone and approach the bus card machine to perform the swipe card boarding and boarding operations, the program to execute the card swiping boarding and boarding can also be an existing APP in the phone
  • the terminal used to perform bus swiping in the embodiments of the present disclosure can also be used in conjunction with an NFC bus card and a mobile phone.
  • the NFC bus card can be used for boarding and swiping operations.
  • charging is realized by the information exchange between the mobile phone and the server.
  • S220 Receive the charging result information returned by the server, where the charging result information includes the ending charging information or the ending charging rejection message, where the ending charging information is that the server determines that the terminal is connected to the terminal according to the location information of the terminal and the bus information.
  • the bus is sent to the terminal after the distance of the bus is greater than the distance threshold and the charging operation is performed on the terminal.
  • the server performs billing termination in the same manner as the above embodiment, that is, after the server receives the billing termination request, it can first determine whether the terminal sending the billing termination request meets the conditions for termination of billing, for example, by the distance between the terminal and the bus Determine whether the terminal sending the request meets the conditions for ending charging.
  • the terminal that the server determines that the charging condition is qualified is defined as the first terminal, and the terminal that does not meet the charging condition is defined as the second terminal.
  • the terminal in the embodiment of the present disclosure may be It is the above-mentioned first terminal or second terminal.
  • the first case is to determine that the terminal meets the conditions for ending charging, and the terminal is the first terminal mentioned above.
  • the terminal receives
  • the billing result information includes end billing information.
  • the terminal's APP can clear the bus information written by the terminal when swiping the card to get on the bus, and deduct the cost of the corresponding trip; the second case is to determine If the terminal does not meet the conditions for ending charging, the terminal is the above-mentioned second terminal.
  • the charging result information received by the terminal includes a refusing to end charging message, which can be returned to the terminal’s APP through the terminal’s
  • the APP reminds the passenger that the billing cannot be forcibly terminated for the time being, please try again later, that is, the passenger can send the billing termination request again through the operation performed on the terminal, that is, if the terminal receives the server sent in S220 If the end of charging message is rejected, S210 and S220 can be repeated subsequently.
  • the charging termination request sent by the terminal in the embodiment of the present disclosure may carry the current location information of the terminal to provide the server with basic information for judgment.
  • the bus card machine can write the bus information into the terminal through the NFC communication with the terminal, and the terminal billing request sent by the terminal can also carry the stored bus Bus information
  • the bus information includes, for example, the bus line name, license plate number, and bus card machine number, so that the server can learn the current location information of the bus based on the bus information.
  • the location information and the location information of the terminal determine whether the terminal meets the conditions for ending billing.
  • the distance between the terminal and the bus can be determined based on the location information of the terminal and the bus information.
  • the distance threshold can be set to be no less than the length of the bus, and the passenger is considered to have got off the bus.
  • the distance threshold in the embodiment of the present disclosure may be the distance information set in the server to determine whether the passenger has got off the bus. Due to different bus models, different distance thresholds can be set for different buses. The distance threshold is also It can be reflected in the bus information in the charging end request sent by the terminal. For example, if the bus information has the model of the bus, the server can determine the appropriate distance threshold according to the model of the bus to determine the passengers Have you gotten off?
  • the terminal sends a request for ending charging including the location information of the terminal and bus information to the server, and receives the charging result information returned by the server.
  • the charging result information includes End billing information or refuse end billing message, where the end billing information is that the server judges that the distance between the terminal and the bus is greater than the distance threshold according to the location information of the terminal and the bus information in the above request, and the execution of the terminal ends Sent to the terminal after the charging operation.
  • the above method for generating billing information provided by the embodiments of the present disclosure does not deduct the full fee for passengers who take a bus and forget to swipe their card when getting off the bus.
  • the billing can be forced to end according to the location of the passenger (that is, the end of the terminal sending The location information of the terminal in the billing request) deducts the cost of the corresponding station or the mileage.
  • the embodiment of the present disclosure provides The method of generating billing information can greatly reduce the economic loss caused by passengers forgetting to swipe their card when getting off the bus, and has a great market prospect.
  • FIG. 6 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure. Based on the embodiment shown in FIG. 5, the method for generating charging information provided by the embodiment of the present disclosure may further include before S210:
  • the terminal will start the current ride only after the terminal uses its NFC function and the bus card machine to perform the operation of swiping and boarding the bus, that is, it has the prerequisite for compulsory termination of billing.
  • the bus card machine and the terminal execute During NFC communication, it can be known that the terminal is performing the operation of swiping the card to board the bus.
  • the bus card machine writes the corresponding bus information into the terminal's memory, and the bus information can be used by the server to subsequently board the terminal Charging can also be used by the server to determine whether the terminal meets the conditions for ending charging by combining the bus information when receiving the charging end information.
  • the terminal can start real-time monitoring of whether it gets off the car and does not swipe the card by triggering the operation of swiping the card to get on the car by itself.
  • This monitoring operation can be performed through a preset program.
  • the monitoring method is for example:
  • the car operation triggers the start of monitoring, which can be the thread that starts the monitoring program, and the program enters the sleep state after the program is started.
  • the sleep time can be set by the designer or can be set according to user requirements. After the sleep time is reached, it wakes up and monitors whether the terminal When you get off the car and do not swipe your card, the sleep time can be a set period of time, for example, the monitoring will be awakened every 1 minute (min) of sleep, and the sleep time will continue after the monitoring is completed.
  • the method for generating billing information provided by the embodiments of the present disclosure can be monitored in real time by the terminal on its own card swiping and disembarking operations, that is, passengers can actively learn through the terminal whether the swiping and disembarking operations have been performed. If the passenger has not got off the car, then You can ignore the monitored results of not performing swipe to get off the bus. If the passenger has got off the bus and finds that the terminal monitors to get the result of not performing the card to get off, you can actively initiate a billing termination request, that is, you can actively perform the above implementation based on the monitoring results S210 ⁇ S220 in the example.
  • the foregoing real-time monitoring of whether the terminal gets off the vehicle without swiping the card may include the following steps:
  • Step 1 Read the stored bus information in real time
  • Step 2 Obtain the location information of the terminal when the bus information is read, and obtain the location information of the bus from the server;
  • Step 3 When the distance between the terminal and the bus is greater than the distance threshold, it is determined that the terminal gets off the bus without swiping the card.
  • monitoring whether the terminal gets off the bus without swiping the card refers to monitoring that the passenger using the terminal has got off the bus and has not performed the swipe card to get off operation.
  • the terminal can actively prompt the passenger that the card is not swiped. Get off the bus, so that the passengers know the current riding situation, and actively initiate a request to end the billing to the server through the operation of the terminal.
  • the implementation of S210 may be: after the monitoring terminal gets off the vehicle and has not swiped the card, it sends a charging end request to the server;
  • the terminal may further include:
  • S202 Display a prompt message for instructing the terminal to get off the vehicle without swiping the card. Subsequently, S210 to S220 can be executed according to the prompt message.
  • FIG. 7 is a flowchart of another method for generating charging information provided by an embodiment of the disclosure.
  • the method for generating charging information provided by the embodiment shown in FIG. 7 may include the following steps:
  • the passenger uses the terminal to perform the operation of swiping the card to board the bus, and stores the bus information;
  • S303 Enter a sleep state of the monitoring mode, for example, sleep for 1 minute;
  • S305 Determine whether the bus information can be read; when the valid bus information is read, execute S306; when the bus information is not read, it means that the terminal has no unfinished itinerary, that is, it means the passengers using the terminal Swipe to get off the car, the process ends;
  • S306 Obtain location information of the terminal, and obtain location information of the bus from the server;
  • S307 Determine that the distance between the terminal and the bus is greater than the distance threshold; when the judgment result is that the distance between the two is greater than the distance threshold, execute S308; when the judgment result is that the distance between the two is less than or equal to the distance threshold, return to execute S303, that is, continue Carrying out the monitoring module;
  • S308 Display a prompt message on the terminal.
  • the prompt message is used to instruct the terminal to get off the bus without swiping the card, that is, to prompt the passenger that the terminal currently has an unfinished trip, and instruct the passenger to initiate an operation to end billing actively.
  • the passenger may use the terminal to perform the following steps S309 to S310, or may ignore the prompt message and cause excessive vehicle billing. That is, after S308, the passenger can also return to execute S303.
  • S309 Send a charging end request to the server, where the charging end request also includes the location information of the terminal and the bus information.
  • S310 Receive charging result information returned by the server, where the charging result information includes the charging end information or the charging end rejection message.
  • S311 Clear the bus information according to the ending billing information, and deduct the cost of the current trip.
  • the terminal may receive the message of denying the end of charging, that is, S309 may be continued after S310; in addition, before the terminal clears the bus information, the terminal may repeat S303 after performing S308 until the terminal clears the bus At this time, valid bus information cannot be read when S304 is executed, and the process ends after the judgment of S305.
  • FIG. 8 it is an interaction flowchart of a method for generating charging information provided by an embodiment of the present disclosure.
  • the method for generating charging information provided by the embodiment shown in FIG. 8 is executed by a terminal with NFC function, a bus card machine, and a server.
  • two terminals, terminal A and terminal B, are shown for generating charging information. It can include the following steps:
  • the passenger opens the APP of the terminal and executes the operation of swiping and boarding, that is, the above-mentioned swiping and boarding operation is performed through the NFC communication between the terminal and the bus card machine;
  • the terminal turns on the monitoring mode
  • S403 Enter the sleep state of the monitoring mode, for example, sleep for 1 minute;
  • S405 Determine whether the bus information can be read; when it is read, execute S406; when it is not read, it means that the passenger using the terminal has performed the operation of swiping the card to get off the bus, and the process ends;
  • S408 Determine that the distance between the terminal and the bus is greater than the distance threshold; when it is greater than the distance threshold, execute S409; when it is less than or equal to the distance threshold, return to execute S403, that is, continue the monitoring module;
  • the bus card machine communicates with the terminal through NFC, and after recording the terminal's swiping and boarding operations, the bus card machine performs the following steps:
  • S502 The bus card machine uploads the terminal information to the server.
  • the bus card machine performs the following steps:
  • S503 The bus card machine deletes the bus information in the terminal, and ends the process.
  • S401 and S503 are selectively executed. If the terminal does not actively perform the swipe card and get off operation, S401 and S503 are not executed, but the steps after S402 are executed.
  • S410 The passenger clicks on the APP of the terminal to forcibly end the billing operation, so that the terminal sends a billing end request to the server, and the billing end request includes the location information of the terminal and the bus information.
  • the server in the embodiment of the present disclosure After receiving the charging end request sent by the terminal, the server in the embodiment of the present disclosure performs the following steps:
  • S601 The server judges whether the terminal has an unfinished itinerary; when it judges that there is no unfinished itinerary, it means that the terminal has performed the swipe card and get off operation, then executes S602; when it judges that there is an unfinished itinerary, executes S603;
  • S602 The server returns a prompt message to the APP of the terminal for prompting the passenger that there is no unfinished itinerary currently;
  • S603 The server obtains current location information of the bus
  • S604 The server determines whether the distance between the terminal and the bus is greater than the distance threshold; when it is less than or equal to the distance threshold, execute S605; when it is greater than the distance threshold, execute S606;
  • S605 The server sends a message to the terminal to refuse to end the billing, which is used to remind the passenger that the terminal used by the passenger cannot end the billing temporarily and can try again later;
  • S606 The server ends the trip of the terminal
  • S607 The server sends end charging information to the terminal.
  • the terminal After the terminal receives the foregoing charging termination information, it performs the following operations:
  • S411 The terminal clears the bus information and deducts the cost of the trip.
  • the bus jam machine can also perform the following steps:
  • the bus card machine uploads the arrival information to the server
  • the operations performed by the server include:
  • S608 The server queries the information of the terminals that have not swiped the card while getting off the car, and ends the trip of these terminals;
  • S609 The server sends charging end information to the terminal that ended charging in S608;
  • the terminal that receives the foregoing charging termination information can also execute:
  • S412 The terminal clears the bus information and deducts the cost of the trip. In this case, the deducted fee is different from the fee for sending an end billing request actively in S411, such as deducting the full fee, or deducting the fee from the point where the card is swiped on the bus to the destination. It should be noted that S608 to S609 and S412 in the process shown in FIG. 8 are selectively executed, and the above steps are executed only when the bus arrives at the stop and the terminal does not always charge the current itinerary.
  • the terminal used by the passenger can actively initiate a billing termination request, and the terminal can monitor in real time whether the passenger has got off the bus and has not swiped the card according to the trigger of the card swiping and boarding operation, and In the case of monitoring that the passenger gets off the bus without swiping the card, the passenger is actively reminded that the passenger currently has the itinerary to be completed, so that the passenger who uses the terminal actively initiates an end billing request to end the current trip and deduct the corresponding fee, and Compared with the existing billing method of getting off the bus without swiping the card, it can greatly reduce the economic loss caused by passengers who forget to swipe the card when getting off the bus, and has a larger market prospect.
  • an embodiment of the present disclosure also provides a server for executing the method shown in Figs. 1 to 4 above.
  • the hardware structure of the method for generating charging information provided in any embodiment is also the server in the method for generating charging information shown in FIG. 8.
  • the server provided by the embodiment of the present disclosure may include a memory and a processor
  • the memory is configured to store executable instructions
  • the processor is configured to implement the method of generating charging information in any of the embodiments shown in FIGS. 1 to 3 and FIG. 8 when executing the executable instructions stored in the memory,
  • the processor is also configured to implement the method of generating charging information in any of the embodiments shown in FIG. 4 and FIG. 8 when executing the executable instructions stored in the memory.
  • FIG. 9 it is a schematic structural diagram of a server provided by an embodiment of the present disclosure.
  • the server 700 provided by the embodiment of the present disclosure is applicable to a situation in which passengers take a bus and charge for the passenger’s journey.
  • the server 700 performs the charge for the ride through communication with the card swiping terminal used by the passenger. It may include: a receiving module 710 and a processing module 720;
  • the receiving module 710 is configured to receive a charging end request sent by the terminal, and the charging end request includes location information of the terminal and bus information.
  • the server provided by the embodiment of the present disclosure is used to charge the passenger in the bus charging process according to the getting on and off the bus.
  • the way that the server learns the passenger's getting on and off the bus may be based on the swiping on board operation and/or the swiping off operation performed by the bus swiping terminal used by the passenger.
  • the billing method of the existing server For passengers who perform swiping and boarding operations without swiping and getting off the bus, the server will perform the next time the passengers use the terminal to perform the swiping and boarding, that is, when a new ride is started, the previous trip will be completed.
  • the itinerary is billed in full, which causes relatively large economic losses to passengers.
  • the terminal used to execute card swiping on a bus is, for example, a mobile phone with NFC function.
  • the terminal used to perform bus swiping in the embodiments of the present disclosure can also be used in conjunction with an NFC bus card and a mobile phone.
  • the NFC bus card can be used for boarding and swiping operations.
  • charging is realized by the information exchange between the mobile phone and the server.
  • the terminal used to perform bus swiping can exchange information with the server, and the receiving module 710 of the server 700 can receive the terminal charging request actively sent by the terminal, and the charging ending request may be a passenger.
  • the operation performed on the terminal side is used to send an end billing request to the server.
  • the operation performed by the passenger on the terminal side is, for example, clicking the option to force end billing in the mobile phone APP .
  • the processing module 720 is configured to perform an ending charging operation on the first terminal whose distance from the bus is greater than the distance threshold according to the location information of the terminal and the bus information.
  • the processing module 720 can first determine whether the terminal sending the request meets the conditions for ending the billing, for example, through the terminal and the bus. The distance determines whether the terminal sending the request meets the conditions for ending charging.
  • the charging termination request sent by the terminal in the embodiment of the present disclosure may carry the current location information of the terminal to provide the server with basic information for judgment .
  • the bus card machine can write the bus information into the terminal through the NFC communication with the terminal, and the terminal billing request sent by the terminal can also carry the stored bus Bus information, the bus information includes, for example, the line name of the bus, the license plate number, and the number of the bus card machine.
  • the processing module 720 determines whether the terminal meets the conditions for ending the billing according to the location information of the bus and the location information of the terminal. For example, the processing module 720 can determine the relationship between the terminal and the bus based on the location information of the terminal and the bus information. When the distance between the bus and the terminal is greater than a set distance threshold, the distance threshold can be set to not less than the length of the bus, and the passenger is considered to have got off the bus.
  • the distance threshold in the embodiment of the present disclosure may be the distance information set in the server to determine whether the passenger has got off the bus. Due to different bus models, different distance thresholds can be set for different buses. The distance threshold is also It can be reflected in the bus information in the end billing request sent by the terminal. For example, if the bus information has the model of the bus, the processing module 720 can determine the appropriate distance threshold according to the model of the bus for Determine whether the passenger has got off the bus.
  • the server 700 in the embodiment of the present disclosure there may be multiple terminals that send the end charging request to the server. Some of these terminals meet the conditions for ending the charging, and some do not meet the conditions for ending the charging.
  • the terminal that the server determines that the charging termination condition is met is defined as the first terminal, and the first terminal is the terminal that sends a charging termination request to the server and whose distance from the bus is greater than the distance threshold.
  • the receiving module 710 in the server 700 in the embodiment of the present disclosure is, for example, a receiver
  • the processing module 720 is, for example, a processor.
  • the server 700 provided in the disclosed embodiment is used to execute the method for generating charging information provided in the embodiment shown in FIG. 1 of the present disclosure, and has corresponding functional modules.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 10 is a schematic structural diagram of another server provided by an embodiment of the disclosure.
  • the processing module 720 may include:
  • the location obtaining unit 721 is configured to obtain location information of the bus according to bus information
  • the judging unit 722 is configured to judge whether the distance between the terminal and the bus is greater than the distance threshold according to the location information of the terminal and the location information of the bus;
  • the charging unit 723 is configured to perform an ending charging operation on the first terminal whose distance from the bus is greater than the distance threshold.
  • the server 700 provided in the embodiment of the present disclosure may further include:
  • the sending module 730 is configured to send charging result information to the terminal, where the charging result information includes the charging end information sent to the first terminal and the charging rejection end message sent to the second terminal.
  • the sending module 730 in the embodiment of the present disclosure may be a transmitter.
  • the server 700 provided in the disclosed embodiment is used to execute the method for generating charging information provided in the embodiment shown in FIG. 2 of the present disclosure, and has corresponding functional modules.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • the judgment unit 722 in the processing module 720 thereof is further configured to judge whether the terminal sending the end charging request has an unfinished trip;
  • the implementation manner for the charging unit 723 to perform an ending charging operation on the first terminal may include:
  • the billing unit 723 is configured to perform an end billing operation on the first terminal that is determined to have an unfinished trip and whose distance from the bus is greater than a distance threshold.
  • the sending module 730 in the embodiment of the present disclosure is also configured to send a prompt message without charging to a third terminal that does not have an unfinished trip.
  • the server 700 provided in the disclosed embodiment is used to execute the method for generating charging information provided in the embodiment shown in FIG. 3 of the present disclosure, and has corresponding functional modules.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • the billing method executed by the server in any of the embodiments shown in FIG. 9 to FIG. 10 of the present disclosure is that the passenger who uses the terminal to execute the swipe card to board the vehicle finds that he has got off the vehicle and has not performed the swipe card to get off operation.
  • the terminal actively sends an end billing request to the server to end the passenger's current journey through this method.
  • the passenger has got off the bus and has not performed the swipe card to get off the car, and has not found that the card has been forgotten to perform the swipe to get off the car, or the terminal has not been actively used. Request the server to end the billing for this trip.
  • the terminal information of the terminal used by the passenger is still stored on the bus card machine, and the terminal also always stores the information of this unfinished trip, such as bus information and Information to perform the operation of swiping on the car.
  • the terminal will detect that the terminal has an unfinished itinerary when the terminal is swiped to board the bus next time, and the full amount of the unfinished itinerary will be deducted, which not only causes a relatively large impact on passengers
  • the terminal, server and bus card machine have always stored relevant information about the terminal’s unfinished trip, which is not conducive to the management of the server, bus card machine and the internal storage information of the terminal.
  • each module in the server 700 is further configured with the following functions.
  • the receiving module 710 is also configured to receive travel end information sent by the bus card machine, where the travel end information includes terminal information that has performed the operation of swiping the card to board the bus;
  • the processing module 720 is also configured to query the terminal that has not executed the swipe card to get off the car according to the travel end information, and end the current travel of the terminal.
  • the sending module 730 is also configured to send end billing information to the terminal that has not executed the card to get off the bus, so that the terminal clears the stored bus information according to the end billing information and deducts the cost of the current trip.
  • the server 700 provided in the disclosed embodiment is used to execute the method for generating charging information provided in the embodiment shown in FIG. 4 of the present disclosure, and has corresponding functional modules.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • an embodiment of the present disclosure also provides a terminal for performing the above-mentioned Figs. 5 to 7
  • the hardware structure of the method for generating charging information provided in any embodiment is also the terminal in the method for generating charging information shown in FIG. 8.
  • the terminal may include a memory and a processor
  • the memory is configured to store executable instructions
  • the processor is configured to implement the method of generating charging information in any of the embodiments shown in FIGS. 5 to 7 and FIG. 8 when executing executable instructions stored in the memory.
  • FIG. 11 it is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure.
  • the terminal 800 provided by the embodiment of the present disclosure is suitable for passengers taking a bus and actively initiates charging through the terminal.
  • the terminal 800 completes the current journey through the NFC communication with the bus card machine and the communication with the server
  • the terminal 800 may include: a communication module 810, a sending module 820, and a receiving module 830.
  • the communication module 810 is configured to perform the operation of swiping on the bus or the operation of getting off the bus through the communication with the bus card machine;
  • the sending module 820 is configured to send a billing end request to the server.
  • the billing end request includes the location information of the terminal and bus information, and the bus information is information in the current itinerary of the terminal.
  • the terminal 800 provided by the embodiment of the present disclosure is used to request the server to charge the current trip by the bus during the bus charging process.
  • passengers board and get off the bus, they can use the bus swiping terminal to perform swiping on and off operations, and all the swiping and getting off operations performed by passengers can be reported to the server by the bus card machine. Therefore, the server Based on the swipe card boarding operation and/or the swiping card getting off operation performed by the bus swiping terminal used by the passenger, the passenger's getting on and off the bus can be known, so as to realize the ride billing.
  • the way that the server learns the passenger's getting on and off the bus may be based on the swiping on board operation and/or the swiping off operation performed by the bus swiping terminal used by the passenger.
  • the billing method of the existing server For passengers who perform swiping and boarding operations without swiping and getting off the bus, the server will perform the next time the passengers use the terminal to perform the swiping and boarding, that is, when a new ride is started, the previous trip will be completed.
  • the itinerary is billed in full, which causes relatively large economic losses to passengers.
  • the terminal 800 used to perform bus card swiping in the embodiment of the present disclosure can communicate with the bus card machine through the communication module 810 for NFC communication, and its sending module 820 and receiving module 830 can exchange information with the server.
  • the sending module 820 of the terminal 800 can actively send a billing termination request to the server through an operation performed on the terminal side.
  • the operation performed by the passenger on the terminal side is, for example, Click the option to force end billing in the mobile phone APP.
  • the billing termination request sent by the sending module 820 may carry the current location information of the terminal and the bus information of the terminal's current unfinished trip.
  • the bus information is the terminal to start the current trip (the last time the card was swiped to board the bus) When opening the trip), the bus card machine writes the information in the terminal.
  • the terminal used to execute card swiping on a bus is, for example, a mobile phone with NFC function.
  • the terminal used to perform bus swiping in the embodiments of the present disclosure can also be used in conjunction with an NFC bus card and a mobile phone.
  • the NFC bus card can be used for boarding and swiping operations.
  • charging is realized by the information exchange between the mobile phone and the server.
  • the communication module 810 in the terminal 800 is, for example, an NFC communication device.
  • the receiving module 830 is configured to receive the charging result information returned by the server, the charging result information includes ending charging information or refusing to end charging messages, where the ending charging information is the server according to the location information of the terminal and bus information It is sent to the terminal after it is determined that the distance between the terminal and the bus is greater than the distance threshold, and the charging operation is performed on the terminal.
  • the method of ending charging can be set as follows: after the server receives the request for ending charging, it can first determine whether the terminal that sent the request meets the conditions for ending the charging, for example, judge whether the terminal that sent the request meets the end based on the distance between the terminal and the bus Billing conditions.
  • the sending module 820 in 800 is, for example, a transmitter
  • the receiving module 830 is, for example, a receiver
  • the terminal that the server determines that the charging condition is qualified is defined as the first terminal, and the terminal that does not meet the charging condition is defined as the second terminal.
  • the terminal in the embodiment of the present disclosure may be It is the above-mentioned first terminal or second terminal.
  • the first case is to determine that the terminal meets the conditions for ending charging, and the terminal is the first terminal mentioned above.
  • the terminal receives
  • the billing result information includes end billing information.
  • the terminal's APP can clear the bus information written by the terminal when swiping the card to get on the bus, and deduct the cost of the corresponding trip; the second case is to determine If the terminal does not meet the conditions for ending charging, the terminal is the above-mentioned second terminal.
  • the charging result information received by the terminal includes a refusing to end charging message, which can be returned to the terminal’s APP through the terminal’s
  • the APP reminds the passenger that the billing cannot be forcibly terminated for the time being, please try again later, that is, the passenger can send a billing termination request by the sending module 820 again through an operation performed on the terminal 800 in the future.
  • the charging termination request sent by the sending module 820 of the terminal 800 in the embodiment of the present disclosure may carry the current location information of the terminal to provide the server with basic information for judgment.
  • the bus card machine can write the bus information into the terminal through the NFC communication with the communication module 810, and send the end charging request sent by the module 820 It can also carry stored bus information, so that the server can learn the current location information of the bus based on the bus information, so as to determine whether the terminal meets the end of charging according to the location information of the bus and the location information of the terminal.
  • the distance between the terminal and the bus can be determined based on the location information of the terminal and the bus information.
  • the distance threshold can be set to not less than The length of the bus is considered that the passengers have got off the bus.
  • the distance threshold in the embodiment of the present disclosure may be the distance information set in the server to determine whether the passenger has got off the bus. Due to different bus models, different distance thresholds can be set for different buses. The distance threshold is also It can be reflected in the bus information in the charging end request sent by the terminal. For example, if the bus information has the model of the bus, the server can determine the appropriate distance threshold according to the model of the bus to determine the passengers Have you gotten off?
  • the terminal 800 provided in the disclosed embodiment is configured to execute the method for generating charging information provided in the embodiment shown in FIG. 5 of the present disclosure, and has corresponding functional modules.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 12 is a schematic structural diagram of another terminal provided by an embodiment of the present disclosure. Based on the structure of the terminal 800 shown in FIG. 11, the terminal 800 provided by the embodiment of the present disclosure may further include: a storage module 840 and a processing module 850;
  • the storage module 840 is configured to store bus information when the communication module 810 performs a card swiping and boarding operation;
  • the processing module 850 is configured to be triggered by the operation of swiping the card to get on the car to monitor in real time whether the terminal gets off the car without swiping the card.
  • the storage module 840 in the embodiment of the present disclosure is, for example, a memory
  • the processing module 850 is, for example, a processor.
  • the processing module 850 may include:
  • the reading unit is configured to read the bus information stored in the storage module in real time
  • the location obtaining unit is configured to obtain the location information of the terminal when the bus information read by the unit is read, and obtain the location information of the bus from the server;
  • the monitoring unit is configured to monitor that the terminal gets off the bus without swiping the card when the distance between the terminal and the bus is greater than the distance threshold.
  • the terminal 800 provided in the embodiment of the present disclosure may further include:
  • the display module 860 is configured to display a prompt message for instructing the terminal to get off the vehicle without swiping the card.
  • the terminal 800 provided in the disclosed embodiment is used to execute the method for generating charging information provided in the embodiments shown in FIG. 6 and FIG. 7 of the present disclosure, and has corresponding functional modules.
  • the implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 13 it is a schematic structural diagram of a charging system provided by an embodiment of the present disclosure.
  • the charging system provided by the embodiment of the present disclosure may include: the server 700 in any embodiment shown in FIGS. 9 and 10, the terminal 800 in any embodiment shown in FIGS. 11 and 12, and a bus Car card machine 900.
  • the bus card machine 900 is configured to write bus information to the terminal 800 that performs the swiping and boarding operation, and to delete the stored bus information for the terminal 800 that performs the swiping and getting off operation;
  • the bus card machine 900 is also configured to upload to the server 700 information that the terminal performs a swipe card boarding operation and a swiping card getting off operation.
  • the bus card machines 900a and 900b of the two buses are shown, and the five terminals 800a ⁇ e are shown.
  • the current trips of the terminals 800a ⁇ c are the same as those of the bus
  • the card machine 900a executes swiping to board the bus
  • the terminal 800c gets off the bus without swiping the card
  • the current travel itinerary of the terminals 800d-e is to execute the card swiping board with the bus card machine 900b, and both get off the bus.
  • there are a large number of bus card machines 900 and terminals 800 and the getting on and off of the terminal 800 is also reflected by the NFC communication with the bus card machine 900 of the current trip.
  • each network element performs charging in the charging system provided by the embodiment of the present disclosure is the same as the manner in which the corresponding network element performs charging in the embodiment shown in FIG. 9 to FIG.
  • the method for generating charging information provided by any of the embodiments shown in 1 to FIG. 8 has a corresponding physical device, and its implementation principles and technical effects are similar, and will not be repeated here.
  • the embodiments of the present disclosure also provide a computer-readable storage medium, the computer-readable storage medium stores executable instructions, and when the executable instructions are executed by a processor, any one of the implementations shown in FIGS. 1 to 4 of the present disclosure can be implemented.
  • the method for generating charging information provided in the example, or, when the executable instruction is executed by a processor, the method for generating charging information provided by any one of the embodiments shown in FIG. 5 to FIG. 7 of the present disclosure can be implemented.
  • the implementation of the computer-readable storage medium provided by the embodiment of the present disclosure is basically the same as the fault detection method provided by the foregoing embodiment of the present disclosure, and will not be repeated here.
  • Such software may be distributed on a computer-readable medium
  • the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .
  • the method for generating charging information, as well as the terminal, the server and the charging system provided by the embodiments of the present disclosure the server receives the terminal's location information and bus information sent by the terminal to end the charging request, and according to the above request Location information and bus information, and perform an ending charging operation on the first terminal whose distance from the bus is greater than the distance threshold.
  • the above method for generating billing information provided by the embodiments of the present disclosure does not deduct the full fee for passengers who take a bus and forget to swipe their card when getting off the bus. Instead, the billing can be forced to end according to the location of the passenger (that is, the end of the terminal sending The location information of the terminal in the billing request) deducts the cost of the corresponding station or the mileage.
  • the embodiment of the present disclosure provides The method of generating billing information can greatly reduce the economic loss caused by passengers getting off the bus and forgetting to swipe their card, and has a great market prospect.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Electric Propulsion And Braking For Vehicles (AREA)

Abstract

本公开实施例公开了一种生成计费信息的方法,以及终端、服务器和计费系统。生成计费信息的方法方法包括:接收终端发送的结束计费请求,该结束计费请求中包括终端的位置信息和公交车信息;根据终端的位置信息和公交车信息,对与公交车的距离大于距离阈值的第一终端执行结束计费操作。

Description

一种生成计费信息的方法,以及终端、服务器和系统
相关申请的交叉引用
本申请要求于2019年5月14日递交的中国专利申请第201910399315.0号的优先权,在此全文引用上述中国专利申请公开的内容以作为本申请的一部分。
技术领域
本申请涉及但不限于通信技术领域,尤指一种生成计费信息的方法,以及终端、服务器和系统。
背景技术
随着通信技术的发展,近距离无线通信(Near Field Communication,简称为:NFC)以其使用的安全性、便捷性和低功耗特性,已被广泛应用到人们的日常生活中。
NFC技术是一种短距离高频的无线通信方式,可以实现在短距离内与兼容设备进行识别和数据交互,常见应用例如为公交车乘车刷卡、公司门禁卡等。目前采用NFC技术进行公共交通计费方式为:在乘客上车和下车时分别执行NFC刷卡操作,并通过刷卡上车和刷卡下车的站点数量或乘坐距离进行计费。根据现有技术,乘客需要在行程开始和结束时各刷卡一次以确定行程的开始和结束。需要说明的是,在上述背景技术部分公开的信息仅用于加强对本公开的背景的理解,因此可以包括不构成对本领域普通技术人员已知的现有技术的信息。
发明内容
本公开实施例提供了一种生成计费信息的方法,以及终端、服务器和系统。
本公开实施例提供一种生成计费信息的方法,包括:
接收终端发送的结束计费请求,所述结束计费请求中包括所述终端的位置信息和公共交通工具信息;
根据所述终端的位置信息和所述公共交通工具信息,对与公共交通工具的距离大于距离阈值的第一终端执行结束计费操作并生成计费信息。
可选地,如上所述的方法中,所述根据所述终端的位置信息和所述公共交通工具信息,对与公共交通工具的距离大于距离阈值的所述第一终端执行结束计费操作,包括:
根据所述公共交通工具信息获取所述公共交通工具的位置信息;
根据所述终端的位置信息和所述公共交通工具的位置信息,判断所述终端与所述公共交通工具的距离是否大于所述距离阈值;
对与所述公共交通工具的距离大于所述距离阈值的所述第一终端执行结束计费操作。
可选地,如上所述的方法中,所述接收终端发送的结束计费请求之后,所述方法还包括:
判断发送所述结束计费请求的终端是否具有未完成的行程;
所述对所述第一终端执行结束计费操作,包括:
对判断出具有未完成的行程、且与所述公共交通工具的距离大于所述距离阈值的第一终端执行结束计费操作。
可选地,如上所述的方法中,还包括:
向所述终端发送计费结果信息,所述计费结果信息包括发送给所述第一终端的结束计费信息和发送给与所述公共交通工具的距离小于或等于所述距离阈值的第二终端的拒绝结束计费消息。
本公开实施例还提供一种生成计费信息的方法,包括:
接收公共交通工具卡机发送的行程结束信息,所述行程结束信息中包括已执行刷卡上车操作的终端信息;
根据所述行程结束信息查询出下车且未刷卡的终端,并结束所述终端的当前行程并生成计费信息。
可选地,如上所述的方法中,还包括:
向所述终端发送结束计费信息,以使得所述终端根据所述结束计费信息清除已存储的公共交通工具信息,并扣除所述当前行程的费 用。
本公开实施例还提供一种生成计费信息的方法,包括:
向服务器发送结束计费请求,所述结束计费请求中包括终端的位置信息和公共交通工具信息,所述公共交通工具信息为所述终端的当前行程中的信息;
接收所述服务器返回的计费结果信息并生成计费信息,所述计费结果信息包括结束计费信息或拒绝结束计费消息,其中,所述结束计费信息为所述服务器根据所述终端的位置信息和所述公共交通工具信息判断出所述终端与公共交通工具的距离大于距离阈值、且对所述终端执行结束计费操作后,向所述终端发送的。
可选地,如上所述的方法中,所述向服务器发送结束计费请求之前,所述方法还包括:
执行刷卡上车操作,并存储所述公共交通工具信息;
通过所述刷卡上车操作的触发,实时监控所述终端是否下车且未刷卡。
可选地,如上所述的方法中,所述实时监控终端是否下车且未刷卡,包括:
实时读取已存储的所述公共交通工具信息;
在读取到的所述公共交通工具信息时,获取所述终端的位置信息,并从所述服务器中获取所述公共交通工具的位置信息;
在所述终端与所述公共交通工具的距离大于距离阈值时,确定出所述终端下车且未刷卡。
可选地,如上所述的方法中,还包括:
显示用于指示所述终端下车且未刷卡的提示消息。
本公开实施例还提供一种服务器,包括:存储器和处理器;
所述存储器,被配置为保存可执行指令;
所述处理器,被配置为在执行所述存储器保存的所述可执行指令时实现如上述服务器所执行的任一项的生成计费信息的方法。
本公开实施例还一种终端,包括:存储器和处理器;
所述存储器,被配置为保存可执行指令;
所述处理器,被配置为在执行所述存储器保存的所述可执行指令时实现如上述终端所执行的任一项的生成计费信息的方法。
本公开实施例还提供一种计费系统,包括:如上述任一项所述的服务器,如上述任一项所述的终端,以及公共交通工具卡机;
所述公共交通工具卡机,被配置为对执行刷卡上车操作的终端写入公共交通工具信息,对执行刷卡下车操作的终端删除已存储的公共交通工具信息;
所述公共交通工具卡机,还被配置为向所述服务器上传终端执行刷卡上车操作和刷卡下车操作的信息。
本公开实施例还提供一种计算机可读存储介质,所述计算机可读存储介质存储有可执行指令,所述可执行指令被处理器执行时可以实现如上述服务器所执行的任一项的生成计费信息的方法,或者,所述可执行指令被处理器执行时可以实现如上述终端所执行的任一项的生成计费信息的方法。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性和解释性的,并不能限制本公开。
本节提供本公开中描述的技术的各种实现或示例的概述,并不是所公开技术的全部范围或所有特征的全面公开。
附图说明
附图用来提供对本公开技术方案的进一步理解,并且构成说明书的一部分,与本申请的实施例一起用于解释本公开的技术方案,并不构成对本公开技术方案的限制。
图1为本公开实施例提供的一种生成计费信息的方法的流程图;
图2为本公开实施例提供的另一种生成计费信息的方法的流程图;
图3为本公开实施例提供的又一种生成计费信息的方法的流程图;
图4为本公开实施例提供的又一种生成计费信息的方法的流程图;
图5为本公开实施例提供的又一种生成计费信息的方法的流程图;
图6为本公开实施例提供的又一种生成计费信息的方法的流程图;
图7为本公开实施例提供的又一种生成计费信息的方法的流程图;
图8为本公开实施例提供的一种生成计费信息的方法的交互流程图;
图9为本公开实施例提供的一种服务器的结构示意图;
图10为本公开实施例提供的另一种服务器的结构示意图;
图11为本公开实施例提供的一种终端的结构示意图;
图12为本公开实施例提供的另一种终端的结构示意图;
图13为本公开实施例提供的一种生成计费信息的系统的结构示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚明白,下文中将结合附图对本公开的实施例进行详细说明。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且,虽然在流程图中示出了逻辑顺序,但是在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤。
本公开提供以下几个具体的实施例可以相互结合,对于相同或相似的概念或过程可能在某些实施例不再赘述。
在下文中,将以公交车为例具体解释本公开,然而本领域技术人员应当理解,本公开的应用并不仅限于通常意义上的城市公交车(city bus),而是可以应用于其它的通过上下车分别刷卡来计算行程的公共交通工具,例如有轨/无轨电车、城铁、观光车等等。
图1为本公开实施例提供的一种生成计费信息的方法的流程图。根据本公开的一个应用场景,本公开可以应用于城市公交车系统,以 根据用户实际乘坐的距离和/或时间来生成计费信息,从而得到与用户实际使用情况相符的费用信息,即,本公开可以用于向用户计费。相应地,其它实施例中涉及的例如生成计费信息的系统可以被简称为“计费系统”。本实施例提供的生成计费信息方法适用于乘客乘坐公交车并对乘客的乘坐行程进行计费的情况中,该生成计费信息方法可以由用于进行乘车计费的服务器执行,该服务器通过与乘客所使用刷卡终端之间的通信生成计费信息,如图1所示,本公开实施例提供的生成计费信息的方法可以包括如下步骤:
S110,接收终端发送的结束计费请求,该结束计费请求中包括终端的位置信息和公交车信息;
本公开实施例提供的生成计费信息的方法,为用于执行公交车计费的服务器根据乘客端的上下车情况对其进行乘车计费的处理方式。该服务器对乘客上下车情况的获知方式,可以基于该乘客使用的公交刷卡终端执行的刷卡上车操作和/或刷卡下车操作。例如,乘客使用的终端已执行刷卡上车操作,但未执行刷卡下车操作,则认为该乘客当前在乘坐其刷卡上车的公交车;再例如,乘客使用的终端已执行刷卡上车操作,且执行对同一公交车的刷卡下车操作,则认为该乘客完成了乘车行程;又例如,乘客使用的终端具有前一次乘车行程中执行刷卡上车操作的记录,且在前一次乘车行程未执行刷卡下车操作的情况下,执行当前乘车行程的刷卡上车操作,则认为该乘客的前一次乘车行程忘记执行刷卡下车操作,此时,通常对前一次乘车行程记录全程费用以结束前一乘车行程,从而次便于对当前乘车行程进行记录。上述各种应用场景中,对于乘客执行刷卡上车操作、且未执行刷卡下车的情况,服务器会在下一次乘客采用终端执行刷卡上车,即开启新的乘车行程时,对上一次完成的行程进行全额计费,从而对乘客造成比较大的经济损失。
需要说明的是,本公开实施例中用于执行公交车刷卡的终端例如为一个具有NFC功能的手机,可以通过在该手机中安装与公交车卡机和服务器执行刷卡交互操作的应用程序(Application,简称为:APP),来实现刷卡操作以及通过与服务器的信息交互实现计费的方 式,将该手机中的APP打开并接近公交车卡机即可执行刷卡上下车操作,执行刷卡上下车的程序也可以是手机中已有APP中的小程序,例如为微信或支付宝中的乘车码等。另外,本公开实施例中用于执行公交车刷卡的终端还可以为NFC公交卡与手机的配合使用,例如手机并不具备NFC功能,则可以使用NFC公交卡进行上下车刷卡操作,并通过在手机的APP中绑定NFC公交卡的方式,由手机与服务器之间的信息交互实现计费。
在本公开实施例中,用于执行公交车刷卡的终端可以与服务器之间进行信息交互,服务器可以接收到终端主动发送的结束计费请求,该结束计费请求可以是乘客在发现已下车且未刷卡的情况下,通过在终端侧执行的操作以向服务器发送的结束计费请求,乘客在终端侧执行的操作例如为在手机的APP中点击强制结束计费的选项。
S120,根据终端的位置信息和公交车信息,对与公交车的距离大于距离阈值的第一终端执行结束计费操作。
在本公开实施例中,考虑到乘客使用终端发送结束计费请求的误操作,例如有些乘客未下车就使用终端点击强制结束计费的选项。结束计费的方式可以设置为:服务器接收到结束计费请求后,可以先判断发送请求的终端是否符合结束计费的条件,例如,通过终端与公交车的距离判断发送请求的终端是否符合结束计费的条件。
基于服务器对终端是否符合结束计费条件的判断需求,本公开实施例中终端发送的结束计费请求中可以携带有该终端当前的位置信息,以向服务器提供判断的基础信息。另外,终端在执行刷卡上车操作时,公交车卡机可以通过与终端之间的NFC通信将公交车信息写入到终端中,终端发送的结束计费请求中还可以携带有已存储的公交车信息,该公交车信息例如包括公交车的线路名称、车牌号、以及公交车卡机的编号等信息,由于公交车是实时移动的,服务器可以根据公交车信息获知该公交车当前的位置信息,从而根据公交车的位置信息和终端的位置信息判断该终端是否符合结束计费的条件,例如,可以根据上述终端的位置信息和公交车信息确定出终端与公交车之间的距离,当公交车与终端的距离大于一设定的距离阈值时,该距离 阈值可以设置为不小于公交车的长度,则认为乘客已经下车。
本公开实施例中的距离阈值可以是在服务器中设置的用于判断乘客是否已下车的距离信息,由于公交车的型号不同,可以对不同的公交车设置不同的距离阈值,该距离阈值还可以通过终端发送的结束计费请求中公交车信息中体现出,例如,公交车信息中具有该公交车的型号,则服务器可以根据该公交车的型号确定出合适的距离阈值,用于判断乘客是否已经下车。
需要说明的是,本公开实施例中向服务器发送结束计费请求的终端可以有多个,这些终端中有的符合结束计费条件,有的不符合结束计费条件,本公开各实施例将服务器判断出符合结束计费条件的终端定义为第一终端,该第一终端即为向服务器发送结束计费请求、且其与公交车之间的距离大于距离阈值的终端。
本公开实施例提供的生成计费信息的方法,服务器通过接收终端发送的包括终端的位置信息和公交车信息的结束计费请求,并且根据上述请求中终端的位置信息和公交车信息,对与公交车的距离大于距离阈值的第一终端执行结束计费操作。本公开实施例提供的上述生成计费信息的方法,对于乘坐公交车且下车忘记刷卡的乘客,不会扣除全额费用,而是可以根据乘客强制结束计费的位置(即终端发送的结束计费请求中终端的位置信息)扣除相应站点或乘车里程的费用,与现有公交计费方式中对忘记下车刷卡的乘客扣除全额费用的计费方式相比,本公开实施例提供的生成计费信息的方法可以在很大程度上减少乘客因下车忘刷卡而造成的经济损失,具有较大的市场前景。
可选地,图2为本公开实施例提供的另一种生成计费信息的方法的流程图。在图1所示实施例的基础上,本公开实施例提供的生成计费信息的方法中,S120的实现方式,可以包括以下步骤:
S121,根据公交车信息获取公交车的位置信息;
S122,根据终端的位置信息和公交车的位置信息,判断终端与公交车的距离是否大于距离阈值;当距离大于距离阈值时,执行S123;
S123,对与公交车的距离大于距离阈值的第一终端执行结束计 费操作。
本公开上述实施例中已经说明服务器接收到的结束计费请求中包括公交车信息,并且服务器可以根据已知的公交车信息与相应公交车卡机之间进行信息交互,即根据上述公交车信息,服务器可以获取到终端请求结束计费的乘车行程中,公交车当前的位置信息。服务器结合实时获取到的公交车的位置信息,结合请求中终端的位置信息,可以计算出发送该请求的终端与公交车的当前距离,并且将该计算出的距离与已知的距离阈值进行比较,若计算出的当前距离大于该距离阈值,则认为使用该终端(即第一终端)的乘客已下车,可以对该第一终端执行结束计费操作。
在实际应用中,服务器判断出终端与公交车的距离小于或等于距离阈值的情况下,认为使用该终端(即第二终端)的乘客当前并未下车,则不会对该第一终端执行结束计费操作。此时,服务器可以对该第二终端发送一提示消息,用于提示使用该第二终端的乘客当前与公交车的距离太近,暂时无法强制结束计费,请稍后重试。另外,对于服务器已执行结束计费的第一终端,服务器可以向其发送结束计费信息,从而指示第一终端清除本端在刷卡上车时写入的公交车信息,并扣除相应乘车行程的费用。如图2所示,本公开实施例提供的生成计费信息的方法中,当S122的判断结果为终端与公交车的距离小于或等于距离阈值时,则执行S124;另外,图2所示实施例的S123之后,执行S125。
S124,向与公交车的距离小于或等于距离阈值的第二终端发送的拒绝结束计费消息;
S125,向第一终端发送结束计费信息。
在本公开实施例中,服务器向终端发送的计费结果信息,包括向两类不同情况的终端发送的信息,对于符合结束计费条件的第一终端,服务器向其发送的计费结果信息为结束计费信息,该结束计费信息可以返回到第一终端的APP中,APP将结束计费信息接入到NFC公交卡或者本机的NFC模块中,并扣除相应乘车行程的费用,此时,该第一终端完成了一次完整的乘车行程;对于不符合结束计费条件的 第一终端,服务器向其发送的计费结果信息为拒绝结束计费消息,该消息同样返回到终端的APP中,通过APP提示乘客暂时无法强制结束计费,请稍后重试,即乘客后续还可以再次通过第二终端发送结束计费请求。因此,图2所示实施例的S124之后,还可以返回执行S110,此时,向服务器发送结束计费请求的终端可以包括S124中接收到拒绝结束计费消息的第二终端。
可选地,图3为本公开实施例提供的又一种生成计费信息的方法的流程图。在上述各实施例的基础上,本发实施例提供的方法在S110之后,还可以包括:
S111,判断发送结束计费请求的终端是否具有未完成的行程;当判断出终端具有未完成的行程,服务器则根据结束计费请求执行后续的判断,并基于判断结构执行相应的操作。
图3以在上述图2所示流程的基础上为例予以示出,当判断出发送请求的终端具有未完成的行程时,认为这些终端的乘客具有下车忘记刷卡的前提条件,即这些乘客已执行刷卡上车的操作,但尚未执行刷卡下车的操作,对于这些具有未完成的行程的乘客,服务器可以继续执行S120的操作。当判断出发送请求的终端不具有未完成的行程时,认为这些终端的乘客已进行了一次完整的乘车行程,当前没有可以强制结束计费的行程。因此,当服务器执行S111的判断结果中,一些发送请求的终端具有未完成的行程时,服务器对这些终端(即上述实施例中的第一终端和第二终端)执行S120;当服务器执行S111的判断结果中,一些发送请求的终端不具有未完成的行程时,服务器对这些终端(例如为第三终端)执行S126。
S130,向不具有未完成行程的第三终端发送无需计费的提示消息。
本公开实施例提供的生成计费信息的方法,采用终端的APP技术,终端(或公交卡)和公交车卡机的NFC通信技术,以及服务器的计费系统,在乘客乘坐公交车、且下车后发现忘记刷卡下车的情况下,乘客可以通过在终端侧执行的操作主动向服务器发起请求,以请求服务器结束当前行程的计费,服务器接收到终端的结束计费请求 后,可以根据其获取的实际情况判断终端是否符合结束计费的条件,例如判断终端是否具有需要计费的行程,以及终端是否已下车且尚未刷卡,从而对符合结束计费条件的第一终端,执行结束计费操作。本公开实施例提供的上述生成计费信息的方法,可以由具有NFC功能的终端、公交车卡机和服务器这三个实体的协同操作,对于乘坐公交车且下车忘记刷卡的乘客,不会扣除全额费用,而是可以根据乘客强制结束计费的位置扣除相应站点或乘车里程的费用,与现有公交车扣费方式中,对忘记下车刷卡的乘客扣除全额费用的计费方式相比,可以在很大程度上减少乘客因下车忘刷卡而造成的经济损失,因此,该计费方式具有较大的市场前景。
图4为本公开实施例提供的又一种生成计费信息的方法的流程图。本实施例提供的生成计费信息的方法适用于乘客乘坐公交车并对乘客的乘坐行程进行计费的情况中,该生成计费信息的方法可以由用于进行乘车计费的服务器执行,该服务器通过与乘客所使用刷卡终端之间的通信进行乘车计费,如图4所示,本公开实施例提供的生成计费信息的方法可以包括如下步骤:
S140,接收公交车卡机发送的行程结束信息,该行程结束信息中包括已执行刷卡上车操作的终端信息。
本公开上述图1到图3所示任一实施例中提供的生成计费信息的方法,均为使用终端执行刷卡上车的乘客发现已下车且未执行刷卡下车操作的情况下,主动通过终端向服务器发送结束计费请求,以通过该方法结束乘客的当前行程。在采用终端进行乘车计费的应用中,还存在一种应用场景为:乘客已下车且未执行刷卡下车操作,并且一直未发现忘记执行刷卡下车操作,或者,一直未采用终端主动请求服务器结束本次行程的计费。
对于上述应用场景下,当公交车到站后,该乘客所使用终端的终端信息仍然存储在公交车卡机上,且该终端中也始终存储本次未完成行程的信息,例如包括公交车信息和执行刷卡上车操作的信息。现有技术的公交计费方式中,会在该终端下次执行刷卡上车时检测出该 终端存在尚未完成的行程,并对该未完成的行程扣除全额费用,这样不仅对乘客造成比较大的经济损失,在终端、服务器和公交车卡机上也一直存储有该终端未完成行程的相关信息,这样不利于服务器、公交车卡机和终端内部存储信息的管理。相比之下,本公开实施例提供的生成计费信息的方法,公交车到站后,公交车卡机会将行程结束信息发送给服务器,由于采用终端刷卡上下车的乘客,在执行一次刷卡上车和刷卡下车后,公交车卡机会清除该终端的信息,即公交车到站后,正常执行刷卡上下车的终端信息已被删除,而对于执行刷卡上车且未执行刷卡下车的终端,其已执行的刷卡上车操作的信息仍然记录在公交车卡机中,因此,服务器接收到的行程结束信息中可以包括已执行刷卡上车操作的终端信息。
S150,根据行程结束信息查询出未执行刷卡下车的终端,并结束终端的当前行程。
在本公开实施例中,服务器接收到公交车卡机发送的行程结束信息,可知相应公交车的当前行程已结束,该当前行程的乘客也都下车,在其读取行程结束信息的内容时可以查询出部分乘客已下车且未采用终端执行刷卡下车操作,此时,对于服务器查询出的未执行刷卡的终端,可以由服务器主动结束这些终端的当前行程。
可选地,本公开实施例提供的方法,还可以包括如下步骤:
S160,向终端发送结束计费信息,以使得终端根据结束计费信息清除已存储的公交车信息,并扣除当前行程的费用。
在本公开实施例中,服务器结束未执行刷卡下车的终端的当前行程后,可以向这些终端发送结束计费信息,使得终端在本端扣除当前行程的费用,并清除已存储的公交车信息。由于本公开实施例中服务器接收到的行程结束信息中记录有这些终端的刷卡上车操作的信息,对终端的计费标准可以为:从刷卡上车的站点到行程终点的相应站点或乘车里程的费用。这样,相比于全额计费,不仅可以在一定程度上降低乘客的经济损失,并且无需等到终端下一次刷卡上车时,就可以结束当前乘车行程,使得行程结束后服务器、公交车卡机和终端中都可以删除当前行程的相关信息,避免了冗余信息的记录,有利于 公交计费系统的信息管理与优化。
本公开实施例提供的生成计费信息的方法,服务器通过接收公交车卡机发送的行程结束信息,该行程结束信息包括执行刷卡上车操作的终端信息,并且根据上述行程结束信息查询出未执行刷卡下车的终端,并结束这些终端的当前行程。本公开实施例提供的上述生成计费信息的方法,对于乘坐公交车且下车忘记刷卡的乘客,不是在乘客使用的终端下次执行刷卡上车时扣费,而是有服务器根据接收到的行程结束信息主动判断哪些终端为执行刷卡下车操作,并由服务器主动结束这些终端的当前行程,可以根据乘客采用终端刷卡上车的站点扣除相应站点或乘车里程的费用,不仅可以在一定程度上降低乘客的经济损失,并且无需等到终端下一次刷卡上车时,就可以结束当前乘车行程,避免了冗余信息的记录,有利于公交计费系统的信息管理与优化,具有较大的市场前景。
图5为本公开实施例提供的又一种生成计费信息的方法的流程图。本实施例提供的生成计费信息的方法适用于乘客乘坐公交车并通过终端主动发起乘车计费的情况中,该生成计费信息的方法可以由乘客所使用的终端执行,该终端通过与公交车卡机的NFC通信,以及与服务器之间的通信完成当前行程的乘车计费,如图5所示,本公开实施例提供的生成计费信息的方法可以包括如下步骤:
S210,向服务器发送结束计费请求,该结束计费请求中包括终端的位置信息和公交车信息,该公交车信息为终端的当前行程中的信息。
本公开实施例提供的生成计费信息的方法,为用于进行乘车刷卡的终端请求服务器对其当前行程进行乘车计费的处理方式。通常地,乘客在上车和下车时,可以采用公交刷卡终端执行刷卡上车操作或刷卡下车操作,且乘客执行的刷卡上下车操作都可以由公交车卡机上报给服务器,因此,服务器可以基于该乘客使用的公交刷卡终端执行的刷卡上车操作和/或刷卡下车操作,获知该乘客上下车情况,从而实现乘车计费。例如,乘客使用的终端已执行刷卡上车操作,但未 执行刷卡下车操作,则认为该乘客当前在乘坐其刷卡上车的公交车;再例如,乘客使用的终端已执行刷卡上车操作,且执行对同一公交车的刷卡下车操作,则认为该乘客完成了乘车行程;又例如,乘客使用的终端具有前一次乘车行程中执行刷卡上车操作的记录,且在前一次乘车行程未执行刷卡下车操作的情况下,执行当前乘车行程的刷卡上车操作,则认为该乘客的前一次乘车行程忘记执行刷卡下车操作,此时,通常对前一次乘车行程记录全程费用以结束前一乘车行程,从而次便于对当前乘车行程进行记录。上述各种应用场景中,对于乘客执行刷卡上车操作、且未执行刷卡下车的情况,服务器会在下一次乘客采用终端执行刷卡上车,即开启新的乘车行程时,对上一次完成的行程进行全额计费,从而对乘客造成比较大的经济损失。
基于上述问题,本公开实施例中用于执行公交车刷卡的终端可以与服务器之间进行信息交互,使用该终端的乘客发现已下车且未刷卡的情况下,可以通过在终端侧执行的操作,由终端主动向服务器发送结束计费请求,乘客在终端侧执行的操作例如为在手机的APP中点击强制结束计费的选项。该结束计费请求中可以携带有终端当前的位置信息,以及该终端当前未完成的行程中的公交车信息,该公交车信息为终端开启当前行程(执行最近一次刷卡上车时开启的行程)时,公交车卡机写入终端中的信息。
需要说明的是,本公开实施例中用于执行公交车刷卡的终端例如为一个具有NFC功能的手机,可以通过在该手机中安装与公交车卡机和服务器执行刷卡交互操作的APP,来实现刷卡操作以及通过与服务器的信息交互实现计费的方式,将该手机中的APP打开并接近公交车卡机即可执行刷卡上下车操作,执行刷卡上下车的程序也可以是手机中已有APP中的小程序,例如为微信或支付宝中的乘车码等。另外,本公开实施例中用于执行公交车刷卡的终端还可以为NFC公交卡与手机的配合使用,例如手机并不具备NFC功能,则可以使用NFC公交卡进行上下车刷卡操作,并通过在手机的APP中绑定NFC公交卡的方式,由手机与服务器之间的信息交互实现计费。
S220,接收服务器返回的计费结果信息,该计费结果信息包括 结束计费信息或拒绝结束计费消息,其中,结束计费信息为服务器根据终端的位置信息和公交车信息判断出该终端与公交车的距离大于距离阈值、且对该终端执行结束计费操作后,向该终端发送的。
在本公开实施例中,考虑到乘客使用终端发送结束计费请求的误操作,例如有些乘客未下车就使用终端点击强制结束计费的选项。服务器执行结束计费的方式与上述实施例相同,即服务器接收到结束计费请求后,可以先判断发送结束计费请求的终端是否符合结束计费的条件,例如,通过终端与公交车的距离判断发送请求的终端是否符合结束计费的条件。
需要说明的是,本公开实施例中服务器判断终端是否符合结束计费条件的实现方式,在上述服务器侧的实施例中已经详细描述,故在终端侧的实施例中此不再赘述。
上述实施例中已经说明服务器判断出符合计费条件的终端定义为第一终端,判断出不符合计费条件的终端定义为第二终端,基于服务器的判断结果,本公开实施例中的终端可能为上述第一终端或第二终端。在本公开实施例中,服务器在执行上述判断后,存在以下两种情况,第一种情况是判断出该终端符合结束计费的条件,则终端为上述第一终端,该情况下终端接收到的计费结果信息中包括结束计费信息,此时,终端的APP可以清除本端在刷卡上车时写入的公交车信息,并扣除相应乘车行程的费用;第二种情况是判断出该终端不符合结束计费的条件,则终端为上述第二终端,该情况下终端接收到的计费结果信息中包括拒绝结束计费消息,该消息可以返回到终端的APP中,通过终端的APP提示乘客暂时无法强制结束计费,请稍后重试,即乘客后续还可以再次通过在终端上执行的操作发送结束计费请求,也就是说,若终端在S220中接收到的服务器发送的拒绝结束计费消息,后续还可以重复执行S210和S220。
基于服务器对终端是否符合结束计费条件的判断需求,本公开实施例中终端发送的结束计费请求中可以携带有该终端当前的位置信息,以向服务器提供判断的基础信息。另外,终端在执行刷卡上车操作时,公交车卡机可以通过与终端之间的NFC通信将公交车信息 写入到终端中,终端发送的结束计费请求中还可以携带有已存储的公交车信息,该公交车信息例如包括公交车的线路名称、车牌号、以及公交车卡机的编号等信息,以使得服务器可以根据公交车信息获知该公交车当前的位置信息,从而根据公交车的位置信息和终端的位置信息判断该终端是否符合结束计费的条件,例如,可以根据上述终端的位置信息和公交车信息确定出终端与公交车之间的距离,当公交车与终端的距离大于一设定的距离阈值时,该距离阈值可以设置为不小于公交车的长度,则认为乘客已经下车。
本公开实施例中的距离阈值可以是在服务器中设置的用于判断乘客是否已下车的距离信息,由于公交车的型号不同,可以对不同的公交车设置不同的距离阈值,该距离阈值还可以通过终端发送的结束计费请求中公交车信息中体现出,例如,公交车信息中具有该公交车的型号,则服务器可以根据该公交车的型号确定出合适的距离阈值,用于判断乘客是否已经下车。
本公开实施例提供的生成计费信息的方法,终端通过向服务器发送包括该终端的位置信息和公交车信息的结束计费请求,并且接收服务器返回的计费结果信息,该计费结果信息包括结束计费信息或拒绝结束计费消息,其中,结束计费信息为服务器根据上述请求中终端的位置信息和公交车信息判断出该终端与公交车的距离大于距离阈值、且对该终端执行结束计费操作后向该终端发送的。本公开实施例提供的上述生成计费信息的方法,对于乘坐公交车且下车忘记刷卡的乘客,不会扣除全额费用,而是可以根据乘客强制结束计费的位置(即终端发送的结束计费请求中终端的位置信息)扣除相应站点或乘车里程的费用,与现有公交计费方式中对忘记下车刷卡的乘客扣除全额费用的计费方式相比,本公开实施例提供的生成计费信息的方法可以在很大程度上减少乘客因下车忘刷卡而造成的经济损失,具有较大的市场前景。
可选地,图6为本公开实施例提供的又一种生成计费信息的方法的流程图。在图5所示实施例的基础上,本公开实施例提供的生成计费信息的方法,在S210之前还可以包括:
S200,执行刷卡上车操作,并存储公交车信息;
S201,通过刷卡上车操作的触发,实时监控终端是否下车且未刷卡。
在本公开实施例中,终端通过其NFC功能与公交车卡机执行刷卡上车操作后,才开启当前的乘车行程,即才具有强制结束计费的前提条件,公交车卡机与终端执行NFC通信时,可知终端本次执行的为刷卡上车操作,此时,公交车卡机将相应的公交车信息写入到终端的存储器中,该公交车信息可用于服务器后续对终端进行乘车计费,也可用于服务器在接收到计费结束信息时结合该公交车信息判断终端是否符合结束计费的条件。终端通过其自身执行刷卡上车操作的触发,可以开启实时监控其自身是否下车且未刷卡的监控操作,该监控操作可以通过预设的程序执行,监控方式例如为:通过终端执行的刷卡上车操作触发开启监控,可以是开启监控程序的线程,且程序开启后进入休眠状态,休眠的时间可以为设计人员设定的,也可以根据用户要求设定,休眠时间到达后唤醒并监控终端是否下车且未刷卡,上述休眠时间可以是设定的一段时间,例如每休眠1分钟(min)唤醒监控一次,完成本次监控后继续进入休眠时间。
本公开实施例提供的生成计费信息的方法,可以由终端对其自身的刷卡上下车操作进行实时监控,即乘客可以通过终端主动获知是否已执行刷卡下车操作,若乘客尚未下车,则可以忽略监控到的未执行刷卡下车的结果,若乘客已经下车、且发现终端监控得到未执行刷卡下车的结果,则可以主动发起结束计费请求,即可以根据监控结果主动执行上述实施例中的S210~S220。
可选地,在本公开实施例中,上述实时监控终端是否下车且未刷卡的实现方式,可以包括如下步骤:
步骤1,实时读取已存储的公交车信息;
步骤2,在读取到的公交车信息时,获取终端的位置信息,并从服务器中获取公交车的位置信息;
步骤3,在终端与公交车的距离大于距离阈值时,确定出终端下车且未刷卡。
需要说明的是,本公开实施例中监控终端是否下车且未刷卡是指监控出使用终端的乘客已下车且未执行刷卡下车操作,在该情况下,终端可以主动提示乘客未执行刷卡下车操作,从而使得乘客得知当前的乘车情况,并通过对终端的操作主动向服务器发起结束计费请求。也就是说,本公开实施例中,S210的实现方式可以为:监控终端下车且未刷卡后,向服务器发送结束计费请求;
本公开实施例在S201中确定出终端下车且未刷卡之后,还可以包括:
S202,显示用于指示终端下车且未刷卡的提示消息。随后,可以根据该提示消息执行S210~S220。
可选地,图7为本公开实施例提供的又一种生成计费信息的方法的流程图。在本公开上述各实施例中,图7所示实施例提供的生成计费信息的方法可以包括如下步骤:
S301,乘客使用终端执行刷卡上车操作,存储公交车信息;
S302,根据刷卡上车操作的触发,开启监控模式;
S303,进入监控模式的休眠状态,例如为休眠1min;
S304,从终端中读取公交车信息;
S305,判断是否可以读取到公交车信息;当读取到有效公交车信息时,执行S306;当未读取到公交车信息时,说明终端当前没有未完成的行程,即说明使用终端的乘客已经执行刷卡下车操作,则结束流程;
S306,获取终端的位置信息,并从服务器中获取公交车的位置信息;
S307,判断终端与公交车的距离大于距离阈值;当判断结果为两者的距离大于距离阈值时,执行S308;当判断结果为两者的距离小于或等于距离阈值时,返回执行S303,即继续进行监控模块;
S308,在终端上显示提示消息,该提示消息用于指示终端下车且未刷卡,即提示乘客该终端当前有未完成的行程,并指示乘客可以主动发起结束计费的操作。
本公开实施例在终端上显示提示消息后,乘客可能采用终端执 行以下步骤S309~S310,也可能忽略了提示消息从而造成乘车计费过多的情况,即S308之后同样可以返回执行S303。
S309,向服务器发送结束计费请求,该结束计费请求中同样包括终端的位置信息和公交车信息,
S310,接收服务器返回的计费结果信息,该计费结果信息包括结束计费信息或拒绝结束计费消息。
S311,根据结束计费信息清除公交车信息,并扣除当前行程的费用。
本公开实施例的S310中,终端可能接收到拒绝结束计费消息,即S310后可以继续执行S309;另外,在终端清除公交车信息之前,终端执行S308之后可以重复执行S303,直到终端清除公交车信息,此时,执行S304时无法读取到有效公交车信息,在S305的判断后结束流程。
以下通过终端、公交车卡机和服务器三侧的交互方式,说明本公开实施例提供的生成计费信息的方法的实际应用情况。如图8所示,为本公开实施例提供的一种生成计费信息的方法的交互流程图。图8所示实施例提供的生成计费信息的方法通过具有NFC功能的终端、公交车卡机和服务器执行,图8中示意出两个终端,终端A和终端B,生成计费信息的方法可以包括如下步骤:
S400,乘客打开终端的APP,执行刷卡上车操作,即通过终端与公交车卡机进行的NFC通信执行上述刷卡上车操作;
S402,终端开启监控模式;
S403,进入监控模式的休眠状态,例如休眠1min;
S404,从终端中读取公交车信息;
S405,判断是否可以读取到公交车信息;当读取到时,执行S406;当未读取到时,说明使用终端的乘客已经执行刷卡下车操作,则结束流程;
S406,从服务器中获取公交车的位置信息;
S407,获取终端当前的位置信息;
S408,判断终端与公交车的距离大于距离阈值;当大于距离阈值时,执行S409;当小于或等于距离阈值时,返回执行S403,即继续进行监控模块;
S409,在终端上显示下车且未刷卡的提示消息;随后返回执行S403,且在S405的判断中未读取到公交车信息后,结束流程。
在公交车卡机侧,公交车卡机与终端通过NFC通信,记录终端的刷卡上车操作后,公交车卡机执行如下步骤:
S501,公交车卡机向终端中写入公交车信息;
S502,公交车卡机将终端的信息上传给服务器。
可选地,若本公开实施例中的终端下车时主动通过NFC通信执行刷卡下车操作,即终端执行S401,执行刷卡下车操作,则公交车卡机执行如下步骤:
S503,公交车卡机将终端中的公交车信息删除,并结束流程。
需要说明的是,本公开实施例中S401和S503是选择性执行的,若终端没有主动执行刷卡下车操作,则不执行S401和S503,而是执行S402之后的步骤。
本公开实施例中,使用终端的乘客发现终端上显示的提示消息后,可以继续执行如下步骤:
S410,乘客通过在终端的APP上点击强制结束计费操作,使得终端向服务器发送结束计费请求,该结束计费请求中包括终端的位置信息和公交车信息。
本公开实施例的服务器接收到终端发送的结束计费请求后,执行如下步骤:
S601,服务器判断终端是否具有未完成的行程;当判断出没有未完成的行程时,说明终端已执行刷卡下车操作,则执行S602;当判断出具有未完成的行程时,执行S603;
S602,服务器返回提示消息到终端的APP,用于提示乘客当前没有未完成的行程;
S603,服务器获取公交车当前的位置信息;
S604,服务器判断终端与公交车的距离是否大于距离阈值;当 小于或等于距离阈值时,执行S605;当大于距离阈值时,执行S606;
S605,服务器向终端发送拒绝结束计费消息,用于提示乘客所使用的终端暂时不能结束计费,可以稍后重试;
S606,服务器结束终端的行程;
S607,服务器向终端发送结束计费信息。
终端接收到上述结束计费信息后,执行如下操作:
S411,终端清除公交车信息,并扣除本次行程的费用。
在本公开实施例中,公交车到站后,公交车卡机还可以执行如下步骤:
S504,公交车卡机向服务器上传到站信息;
相应地,服务器执行的操作包括:
S608,服务器查询下车未刷卡的终端信息,并结束这些终端的行程;
S609,服务器向S608中结束计费的终端发送结束计费信息;
相应地,接收到上述结束计费信息的终端,还可以执行:
S412,终端清除公交车信息,并扣除本次行程的费用。该情况下扣除的费用与S411中通过主动发送结束计费请求的费用不同,例如扣除全额费用,或扣除从刷卡上车站点到终点的费用。需要说明的是,图8所示流程中的S608~S609,以及S412为选择性执行的,只有在公交车到站时,终端始终未对当前行程计费,才执行上述步骤。
本公开实施例提供的生成计费信息的方法,可以由乘客使用的终端主动发起结束计费请求,且该终端可以根据刷卡上车操作的触发,实时监控乘客是否已下车且未刷卡,并且在监控到乘客下车未刷卡的情况下,主动提示乘客当前具有待完成的行程,从而使得使用该终端的乘客主动发起结束计费请求,以结束当前的乘车行程并扣除相应的费用,与现有乘车时下车未刷卡的计费方式相比,可以在很大程度上减少乘客因下车忘刷卡而造成的经济损失,具有较大的市场前景。
基于本公开上述图1到图4,以及图8所示任一实施例提供的生 成计费信息的方法,本公开实施例还提供一种服务器,该服务器为执行上述图1到图4所示任一实施例提供的生成计费信息的方法的硬件结构,同样为图8所示生成计费信息的方法中服务器。
本公开实施例提供的服务器可以包括存储器和处理器;
该存储器,被配置为保存可执行指令;
该处理器,被配置为在执行所述存储器保存的可执行指令时实现如图1到图3,以及图8所示任一实施例中的生成计费信息的方法,
该处理器,还被配置为在执行存储器保存的可执行指令时实现如权图4和图8所示任一实施例中的生成计费信息的方法。
如图9所示,为本公开实施例提供的一种服务器的结构示意图。本公开实施例提供的服务器700适用于乘客乘坐公交车并对乘客的乘坐行程进行计费的情况中,该服务器700通过与乘客所使用刷卡终端之间的通信进行乘车计费,该服务器700可以包括:接收模块710和处理模块720;
其中,接收模块710,被配置为接收终端发送的结束计费请求,该结束计费请求中包括终端的位置信息和公交车信息。
本公开实施例提供的服务器,用于在公交车计费过程中根据乘客端的上下车情况对其进行乘车计费。该服务器对乘客上下车情况的获知方式,可以基于该乘客使用的公交刷卡终端执行的刷卡上车操作和/或刷卡下车操作。现有服务器的计费方式,对于乘客执行刷卡上车操作、且未执行刷卡下车的情况,服务器会在下一次乘客采用终端执行刷卡上车,即开启新的乘车行程时,对上一次完成的行程进行全额计费,从而对乘客造成比较大的经济损失。
需要说明的是,本公开实施例中用于执行公交车刷卡的终端例如为一个具有NFC功能的手机。另外,本公开实施例中用于执行公交车刷卡的终端还可以为NFC公交卡与手机的配合使用,例如手机并不具备NFC功能,则可以使用NFC公交卡进行上下车刷卡操作,并通过在手机的APP中绑定NFC公交卡的方式,由手机与服务器之间的信息交互实现计费。
在本公开实施例中,用于执行公交车刷卡的终端可以与服务器 之间进行信息交互,服务器700的接收模块710可以接收到终端主动发送的结束计费请求,该结束计费请求可以是乘客在发现已下车且未刷卡的情况下,通过在终端侧执行的操作以向服务器发送的结束计费请求,乘客在终端侧执行的操作例如为在手机的APP中点击强制结束计费的选项。
处理模块720,被配置为根据终端的位置信息和公交车信息,对与公交车的距离大于距离阈值的第一终端执行结束计费操作。
在本公开实施例中,考虑到乘客使用终端发送结束计费请求的误操作,例如有些乘客未下车就使用终端点击强制结束计费的选项。结束计费的方式可以设置为:服务器700的接收模块710接收到结束计费请求后,可以由处理模块720先判断发送请求的终端是否符合结束计费的条件,例如,通过终端与公交车的距离判断发送请求的终端是否符合结束计费的条件。
基于服务器700的处理模块720对终端是否符合结束计费条件的判断需求,本公开实施例中终端发送的结束计费请求中可以携带有该终端当前的位置信息,以向服务器提供判断的基础信息。另外,终端在执行刷卡上车操作时,公交车卡机可以通过与终端之间的NFC通信将公交车信息写入到终端中,终端发送的结束计费请求中还可以携带有已存储的公交车信息,该公交车信息例如包括公交车的线路名称、车牌号、以及公交车卡机的编号等信息,由于公交车是实时移动的,服务器可以根据公交车信息获知该公交车当前的位置信息,从而处理模块720根据公交车的位置信息和终端的位置信息判断该终端是否符合结束计费的条件,例如,处理模块720可以根据上述终端的位置信息和公交车信息确定出终端与公交车之间的距离,当公交车与终端的距离大于一设定的距离阈值时,该距离阈值可以设置为不小于公交车的长度,则认为乘客已经下车。
本公开实施例中的距离阈值可以是在服务器中设置的用于判断乘客是否已下车的距离信息,由于公交车的型号不同,可以对不同的公交车设置不同的距离阈值,该距离阈值还可以通过终端发送的结束计费请求中公交车信息中体现出,例如,公交车信息中具有该公交车 的型号,则处理模块720可以根据该公交车的型号确定出合适的距离阈值,用于判断乘客是否已经下车。
需要说明的是,本公开实施例中向服务器发送结束计费请求的终端可以有多个,这些终端中有的符合结束计费条件,有的不符合结束计费条件,本公开各实施例将服务器判断出符合结束计费条件的终端定义为第一终端,该第一终端即为向服务器发送结束计费请求、且其与公交车之间的距离大于距离阈值的终端。另外,本公开实施例的服务器700中的接收模块710例如为一个接收器,处理模块720例如为处理器。
公开实施例提供的服务器700用于执行本公开图1所示实施例提供的生成计费信息的方法,具备相应的功能模块,其实现原理和技术效果类似,此处不再赘述。
可选地,图10为本公开实施例提供的另一种服务器的结构示意图。在图9所示服务器700的结构基础上,本公开实施例提供的服务器700中,处理模块720可以包括:
位置获取单元721,被配置为根据公交车信息获取所述公交车的位置信息;
判断单元722,被配置为根据终端的位置信息和公交车的位置信息,判断终端与公交车的距离是否大于距离阈值;
计费单元723,被配置为对与公交车的距离大于距离阈值的第一终端执行结束计费操作。
可选地,本公开实施例提供的服务器700,还可以包括:
发送模块730,被配置为向终端发送计费结果信息,该计费结果信息包括发送给第一终端的结束计费信息和发送给第二终端的拒绝结束计费消息。本公开实施例中的发送模块730可以为一发送器。
公开实施例提供的服务器700用于执行本公开图2所示实施例提供的生成计费信息的方法,具备相应的功能模块,其实现原理和技术效果类似,此处不再赘述。
可选地,本公开实施例提供的服务器700,其处理模块720中的判断单元722,还被配置为判断发送结束计费请求的终端是否具有未 完成的行程;
相应地,计费单元723对第一终端执行结束计费操作的实现方式,可以包括:
计费单元723,被配置为对判断出具有未完成的行程、且与公交车的距离大于距离阈值的第一终端执行结束计费操作。
本公开实施例中的发送模块730,还被配置为向不具有未完成行程的第三终端发送无需计费的提示消息。
公开实施例提供的服务器700用于执行本公开图3所示实施例提供的生成计费信息的方法,具备相应的功能模块,其实现原理和技术效果类似,此处不再赘述。
需要说明的是,本公开上述图9到图10所示任一实施例中服务器所执行的计费方式,均为使用终端执行刷卡上车的乘客发现已下车且未执行刷卡下车操作的情况下,主动通过终端向服务器发送结束计费请求,以通过该方法结束乘客的当前行程。在采用终端进行乘车计费的应用中,还存在一种应用场景为:乘客已下车且未执行刷卡下车操作,并且一直未发现忘记执行刷卡下车操作,或者,一直未采用终端主动请求服务器结束本次行程的计费。
对于上述应用场景下,当公交车到站后,该乘客所使用终端的终端信息仍然存储在公交车卡机上,且该终端中也始终存储本次未完成行程的信息,例如包括公交车信息和执行刷卡上车操作的信息。现有技术的公交计费方式中,会在该终端下次执行刷卡上车时检测出该终端存在尚未完成的行程,并对该未完成的行程扣除全额费用,这样不仅对乘客造成比较大的经济损失,在终端、服务器和公交车卡机上也一直存储有该终端未完成行程的相关信息,这样不利于服务器、公交车卡机和终端内部存储信息的管理。
在本公开实施例的一种实现方式中,服务器700中的各模块还配置有以下功能。
接收模块710,还被配置为接收公交车卡机发送的行程结束信息,该行程结束信息中包括已执行刷卡上车操作的终端信息;
处理模块720,还被配置为根据行程结束信息查询出未执行刷卡 下车的终端,并结束终端的当前行程。
可选地,本公开实施例提供的服务器700中,
发送模块730,还被配置为向上述未执行刷卡下车的终端发送结束计费信息,以使得终端根据结束计费信息清除已存储的公交车信息,并扣除当前行程的费用。
公开实施例提供的服务器700用于执行本公开图4所示实施例提供的生成计费信息的方法,具备相应的功能模块,其实现原理和技术效果类似,此处不再赘述。
基于本公开上述图5到图7,以及图8所示任一实施例提供的生成计费信息的方法,本公开实施例还提供一种终端,该终端为执行上述图5到图7所示任一实施例提供的生成计费信息的方法的硬件结构,同样为图8所示生成计费信息的方法中终端。
本公开实施例提供的终端可以包括存储器和处理器;
该存储器,被配置为保存可执行指令;
该处理器,被配置为在执行存储器保存的可执行指令时实现如图5到图7,以及图8所示任一实施例中的生成计费信息的方法。
如图11所示,为本公开实施例提供的一种终端的结构示意图。本公开实施例提供的终端800适用于乘客乘坐公交车并通过终端主动发起乘车计费的情况中,该终端800通过与公交车卡机的NFC通信,以及与服务器之间的通信完成当前行程的乘车计费,该终端800可以包括:通信模块810、发送模块820和接收模块830。
其中,通信模块810,被配置为通过与公交车卡机进行的通信,执行刷卡上车操作或刷卡下车操作;
发送模块820,被配置为向服务器发送结束计费请求,该结束计费请求中包括终端的位置信息和公交车信息,该公交车信息为终端的当前行程中的信息。
本公开实施例提供的终端800,用于在公交车计费过程中请求服务器对其当前行程进行乘车计费。通常地,乘客在上车和下车时,可以采用公交刷卡终端执行刷卡上车操作或刷卡下车操作,且乘客执行 的刷卡上下车操作都可以由公交车卡机上报给服务器,因此,服务器可以基于该乘客使用的公交刷卡终端执行的刷卡上车操作和/或刷卡下车操作,获知该乘客上下车情况,从而实现乘车计费。服务器对乘客上下车情况的获知方式,可以基于该乘客使用的公交刷卡终端执行的刷卡上车操作和/或刷卡下车操作。现有服务器的计费方式,对于乘客执行刷卡上车操作、且未执行刷卡下车的情况,服务器会在下一次乘客采用终端执行刷卡上车,即开启新的乘车行程时,对上一次完成的行程进行全额计费,从而对乘客造成比较大的经济损失。
基于上述问题,本公开实施例中用于执行公交车刷卡的终端800,可以通过通信模块810与公交车卡机进行NFC通信,其发送模块820和接收模块830可以与服务器之间进行信息交互,使用该终端的乘客发现已下车且未刷卡的情况下,可以通过在终端侧执行的操作,由终端800的发送模块820主动向服务器发送结束计费请求,乘客在终端侧执行的操作例如为在手机的APP中点击强制结束计费的选项。发送模块820发送的结束计费请求中可以携带有终端当前的位置信息,以及该终端当前未完成的行程中的公交车信息,该公交车信息为终端开启当前行程(执行最近一次刷卡上车时开启的行程)时,公交车卡机写入终端中的信息。
需要说明的是,本公开实施例中用于执行公交车刷卡的终端例如为一个具有NFC功能的手机。另外,本公开实施例中用于执行公交车刷卡的终端还可以为NFC公交卡与手机的配合使用,例如手机并不具备NFC功能,则可以使用NFC公交卡进行上下车刷卡操作,并通过在手机的APP中绑定NFC公交卡的方式,由手机与服务器之间的信息交互实现计费。该终端800中的通信模块810例如为NFC通信设备。
接收模块830,被配置为接收服务器返回的计费结果信息,该计费结果信息包括结束计费信息或拒绝结束计费消息,其中,结束计费信息为服务器根据终端的位置信息和公交车信息判断出该终端与公交车的距离大于距离阈值、且对该终端执行结束计费操作后,向该终端发送的。
在本公开实施例中,考虑到乘客使用终端800发送结束计费请求的误操作,例如有些乘客未下车就使用终端点击强制结束计费的选项。结束计费的方式可以设置为:服务器接收到结束计费请求后,可以先判断发送请求的终端是否符合结束计费的条件,例如,通过终端与公交车的距离判断发送请求的终端是否符合结束计费的条件。
需要说明的是,本公开实施例中服务器判断终端是否符合结束计费条件的实现方式,在上述服务器侧的实施例中已经详细描述,故在终端侧的实施例中此不再赘述。另外,本公开实施例的中800中的发送模块820例如为一发送器,接收模块830例如为一个接收器。
上述实施例中已经说明服务器判断出符合计费条件的终端定义为第一终端,判断出不符合计费条件的终端定义为第二终端,基于服务器的判断结果,本公开实施例中的终端可能为上述第一终端或第二终端。在本公开实施例中,服务器在执行上述判断后,存在以下两种情况,第一种情况是判断出该终端符合结束计费的条件,则终端为上述第一终端,该情况下终端接收到的计费结果信息中包括结束计费信息,此时,终端的APP可以清除本端在刷卡上车时写入的公交车信息,并扣除相应乘车行程的费用;第二种情况是判断出该终端不符合结束计费的条件,则终端为上述第二终端,该情况下终端接收到的计费结果信息中包括拒绝结束计费消息,该消息可以返回到终端的APP中,通过终端的APP提示乘客暂时无法强制结束计费,请稍后重试,即乘客后续还可以再次通过在终端800上执行的操作由发送模块820发送结束计费请求。
基于服务器对终端是否符合结束计费条件的判断需求,本公开实施例中终端800的发送模块820发送的结束计费请求中可以携带有该终端当前的位置信息,以向服务器提供判断的基础信息。另外,终端800的通信模块810在执行刷卡上车操作时,公交车卡机可以通过与通信模块810之间的NFC通信将公交车信息写入到终端中,发送模块820发送的结束计费请求中还可以携带有已存储的公交车信息,以使得服务器可以根据公交车信息获知该公交车当前的位置信息,从而根据公交车的位置信息和终端的位置信息判断该终端是否符合结 束计费的条件,例如,可以根据上述终端的位置信息和公交车信息确定出终端与公交车之间的距离,当公交车与终端的距离大于一设定的距离阈值时,该距离阈值可以设置为不小于公交车的长度,则认为乘客已经下车。
本公开实施例中的距离阈值可以是在服务器中设置的用于判断乘客是否已下车的距离信息,由于公交车的型号不同,可以对不同的公交车设置不同的距离阈值,该距离阈值还可以通过终端发送的结束计费请求中公交车信息中体现出,例如,公交车信息中具有该公交车的型号,则服务器可以根据该公交车的型号确定出合适的距离阈值,用于判断乘客是否已经下车。
公开实施例提供的终端800用于执行本公开图5所示实施例提供的生成计费信息的方法,具备相应的功能模块,其实现原理和技术效果类似,此处不再赘述。
可选地,图12为本公开实施例提供的另一种终端的结构示意图。在图11所示终端800的结构基础上,本公开实施例提供的终端800中还可以包括:存储模块840和处理模块850;
存储模块840,被配置为在通信模块810执行刷卡上车操作时,存储公交车信息;
处理模块850,被配置为通过刷卡上车操作的触发,实时监控终端是否下车且未刷卡。
本公开实施例中的存储模块840例如为一存储器,处理模块850例如为处理器。
可选地,本公开实施例提供的终端800中,处理模块850可以包括:
读取单元,被配置为实时读取存储模块中存储的公交车信息;
位置获取单元,被配置为在读取单元读取到的公交车信息时,获取终端的位置信息,并从服务器中获取公交车的位置信息;
监控单元,被配置为在终端与公交车的距离大于距离阈值时,监控到终端下车且未刷卡。
可选地,本公开实施例提供的终端800,还可以包括:
显示模块860,被配置为显示用于指示终端下车且未刷卡的提示消息。
公开实施例提供的终端800用于执行本公开图6和图7所示实施例提供的生成计费信息的方法,具备相应的功能模块,其实现原理和技术效果类似,此处不再赘述。
如图13所示,为本公开实施例提供的一种计费系统的结构示意图。本公开实施例提供的计费系统可以包括:如上述图9和图10所示任一实施例中的服务器700,如上述图11和图12所示任一实施例中的终端800,以及公交车卡机900。
其中,公交车卡机900,被配置为对执行刷卡上车操作的终端800写入公交车信息,对执行刷卡下车操作的终端800删除已存储的公交车信息;
公交车卡机900,还被配置为向服务器700上传终端执行刷卡上车操作和刷卡下车操作的信息。
图13所示计费系统中仅示意出2个公交车各自的公交车卡机900a和900b,并示意出5个终端800a~e,其中,终端800a~c的当前乘车行程为与公交车卡机900a执行刷卡上车,终端800c下车且未刷卡,终端800d~e的当前乘车行程为与公交车卡机900b执行刷卡上车,且均为下车。实际应用中,公交车卡机900和终端800的数量比较多,且终端800的上下车情况也是通过与当前行程的公交车卡机900的NFC通信体现的,当终端800自身监控出终端800与当前行程的公交车的距离大于距离阈值时,提示使用终端800的乘客主动发起结束计费。本公开实施例提供的计费系统中的各网元执行计费的处理方式,与上述图9到图12所示实施例中对应网元执行计费的方式相同,同样用于执行本公开图1到图8所示任一实施例提供的生成计费信息的方法,具备相应的实体装置,其实现原理和技术效果类似,此处不再赘述。
本公开实施例还提供一种计算机可读存储介质,该计算机可读 存储介质存储有可执行指令,该可执行指令被处理器执行时可以实现本公开上述图1到图4所示任一实施例提供的生成计费信息的方法,或者,该可执行指令被处理器执行时可以实现本公开上述图5到图7所示任一实施例提供的生成计费信息的方法。本公开实施例提供的计算机可读存储介质的实施方式与本公开上述实施例提供的故障检测方法基本相同,在此不做赘述。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中,在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分;例如,一个物理组件可以具有多个功能,或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器,如数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外,本领域普通技术人员公知的是,通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据,并且可包括任何信息递送介质。
本公开实施例提供的生成计费信息的方法,以及终端、服务器和计费系统,服务器通过接收终端发送的包括终端的位置信息和公交车信息的结束计费请求,并且根据上述请求中终端的位置信息和公交车信息,对与公交车的距离大于距离阈值的第一终端执行结束计费操作。本公开实施例提供的上述生成计费信息的方法,对于乘坐公交车 且下车忘记刷卡的乘客,不会扣除全额费用,而是可以根据乘客强制结束计费的位置(即终端发送的结束计费请求中终端的位置信息)扣除相应站点或乘车里程的费用,与现有公交计费方式中对忘记下车刷卡的乘客扣除全额费用的计费方式相比,本公开实施例提供的生成计费信息的方法可以在很大程度上减少乘客因下车忘刷卡而造成的经济损失,具有较大的市场前景。
虽然本公开所揭露的实施方式如上,但所述的内容仅为便于理解本公开而采用的实施方式,并非用以限定本公开。任何本公开所属领域内的技术人员,在不脱离本公开所揭露的精神和范围的前提下,可以在实施的形式及细节上进行任何的修改与变化,但本公开的专利保护范围,仍须以所附的权利要求书所界定的范围为准。

Claims (15)

  1. 一种生成计费信息的方法,包括:
    接收终端发送的结束计费请求,所述结束计费请求中包括所述终端的位置信息和公共交通工具信息;
    根据所述终端的位置信息和所述公共交通工具信息,对与公共交通工具的距离大于距离阈值的第一终端执行结束计费操作并生成计费信息。
  2. 根据权利要求1所述的方法,其中,所述根据所述终端的位置信息和所述公共交通工具信息,对与公共交通工具的距离大于距离阈值的所述第一终端执行结束计费操作并生成计费信息,包括:
    根据所述公共交通工具信息获取所述公共交通工具的位置信息;
    根据所述终端的位置信息和所述公共交通工具的位置信息,判断所述终端与所述公共交通工具的距离是否大于所述距离阈值;
    对与所述公共交通工具的距离大于所述距离阈值的所述第一终端执行结束计费操作并生成计费信息。
  3. 根据权利要求1所述的方法,其中,所述接收终端发送的结束计费请求之后,所述方法还包括:
    判断发送所述结束计费请求的终端是否具有未完成的行程;
    所述对所述第一终端执行结束计费操作并生成计费信息,包括:
    对判断出具有未完成的行程、且与所述公共交通工具的距离大于所述距离阈值的第一终端执行结束计费操作并生成计费信息。
  4. 根据权利要求1所述的方法,其中,还包括:
    向所述终端发送计费结果信息并根据所述计费结果信息生成计费信息,所述计费结果信息包括发送给所述第一终端的结束计费信息和发送给与所述公共交通工具的距离小于或等于所述距离阈值的第二终端的拒绝结束计费消息。
  5. 一种生成计费信息的方法,包括:
    接收公共交通工具卡机发送的行程结束信息,所述行程结束信息中包括已执行刷卡上车操作的终端信息;
    根据所述行程结束信息查询出下车且未刷卡的终端,结束所述终端的当前行程并生成计费信息。
  6. 根据权利要求5所述的方法,其中,还包括:
    向所述终端发送结束计费信息,以使得所述终端根据所述结束计费信息清除已存储的公共交通工具信息。
  7. 一种生成计费信息的方法,包括:
    向服务器发送结束计费请求,所述结束计费请求中包括终端的位置信息和公共交通工具信息,所述公共交通工具信息为所述终端的当前行程中的信息;
    接收所述服务器返回的计费结果信息并生成计费信息,所述计费结果信息包括结束计费信息或拒绝结束计费消息,其中,所述结束计费信息为所述服务器根据所述终端的位置信息和所述公共交通工具信息判断出所述终端与公共交通工具的距离大于距离阈值、且对所述终端执行结束计费操作后,向所述终端发送的。
  8. 根据权利要求7所述的方法,其中,所述向服务器发送结束计费请求之前,所述方法还包括:
    执行刷卡上车操作,并存储所述公共交通工具信息;
    通过所述刷卡上车操作的触发,实时监控所述终端是否下车且未刷卡。
  9. 根据权利要求8所述的方法,其中,所述实时监控终端是否下车且未刷卡,包括:
    实时读取已存储的所述公共交通工具信息;
    在读取到的所述公共交通工具信息时,获取所述终端的位置信息,并从所述服务器中获取所述公共交通工具的位置信息;
    在所述终端与所述公共交通工具的距离大于距离阈值时,确定出所述终端下车且未刷卡。
  10. 根据权利要求8所述的方法,其中,还包括:
    显示用于指示所述终端下车且未刷卡的提示消息。
  11. 一种服务器,包括:存储器和处理器;
    所述存储器,被配置为保存可执行指令;
    所述处理器,被配置为在执行所述存储器保存的所述可执行指令时实现如权利要求1所述的方法。
  12. 一种服务器,包括:存储器和处理器;
    所述存储器,被配置为保存可执行指令;
    所述处理器,被配置为在执行所述存储器保存的所述可执行指令时实现如权利要求5所述的方法。
  13. 一种终端,包括:存储器和处理器;
    所述存储器,被配置为保存可执行指令;
    所述处理器,被配置为在执行所述存储器保存的所述可执行指令时实现如权利要求7所述的方法。
  14. 一种生成计费信息的系统,包括:如权利要求11所述的服务器,以及公共交通工具卡机;
    所述公共交通工具卡机,被配置为对执行刷卡上车操作的终端写入公共交通工具信息,对执行刷卡下车操作的终端删除已存储的公共交通工具信息;
    所述公共交通工具卡机,还被配置为向所述服务器上传终端执行刷卡上车操作和刷卡下车操作的信息,
    其中,所述终端向服务器发送结束计费请求,所述结束计费请求中包括终端的位置信息和公共交通工具信息,所述公共交通工具信息为所述终端的当前行程中的信息;以及接收所述服务器返回的计费结果信息并根据所述计费结果信息生成计费信息,所述计费结果信息包括结束计费信息或拒绝结束计费消息,其中,所述结束计费信息为所述服务器根据所述终端的位置信息和所述公共交通工具信息判断出所述终端与公共交通工具的距离大于距离阈值、且对所述终端执行结束计费操作后,向所述终端发送的。
  15. 一种生成计费信息的系统,包括:如权利要求12所述的服务器,以及公共交通工具卡机;
    所述公共交通工具卡机,被配置为对执行刷卡上车操作的终端写入公共交通工具信息,对执行刷卡下车操作的终端删除已存储的公共交通工具信息;
    所述公共交通工具卡机,还被配置为向所述服务器上传终端执行刷卡上车操作和刷卡下车操作的信息,
    其中,所述终端向服务器发送结束计费请求,所述结束计费请求中包括终端的位置信息和公共交通工具信息,所述公共交通工具信息为所述终端的当前行程中的信息;以及接收所述服务器返回的计费结果信息并根据所述计费结果信息生成计费信息,所述计费结果信息包括结束计费信息或拒绝结束计费消息,其中,所述结束计费信息为所述服务器根据所述终端的位置信息和所述公共交通工具信息判断出所述终端与公共交通工具的距离大于距离阈值、且对所述终端执行结束计费操作后,向所述终端发送的。
PCT/CN2020/090230 2019-05-14 2020-05-14 一种生成计费信息的方法,以及终端、服务器和系统 WO2020228771A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/298,091 US12086850B2 (en) 2019-05-14 2020-05-14 Method for generating billing information, terminal, server, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910399315.0 2019-05-14
CN201910399315.0A CN110113710B (zh) 2019-05-14 2019-05-14 一种计费方法,以及终端、服务器和计费系统

Publications (1)

Publication Number Publication Date
WO2020228771A1 true WO2020228771A1 (zh) 2020-11-19

Family

ID=67489873

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/090230 WO2020228771A1 (zh) 2019-05-14 2020-05-14 一种生成计费信息的方法,以及终端、服务器和系统

Country Status (3)

Country Link
US (1) US12086850B2 (zh)
CN (1) CN110113710B (zh)
WO (1) WO2020228771A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110113710B (zh) 2019-05-14 2022-01-18 京东方科技集团股份有限公司 一种计费方法,以及终端、服务器和计费系统
CN112419529A (zh) * 2020-10-29 2021-02-26 中电信用服务有限公司 一种用户补打卡的系统及方法
CN113744446B (zh) * 2021-09-17 2023-02-03 中科美络科技股份有限公司 基于车联网与边缘计算的无感交互方法、装置及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089446A1 (en) * 2016-11-11 2018-05-17 Operr Technologies, Inc. System and method for geo-aware transportation billing verification
CN108551651A (zh) * 2018-04-08 2018-09-18 深圳卡通新技术有限公司 基于移动终端的公交车分段计费方法
CN108834048A (zh) * 2018-06-14 2018-11-16 武汉斑马快跑科技有限公司 一种乘客下车行为识别方法及装置
CN109168130A (zh) * 2018-08-16 2019-01-08 北京三快在线科技有限公司 营运车辆计费方法及装置、电子设备、存储介质
CN110113710A (zh) * 2019-05-14 2019-08-09 京东方科技集团股份有限公司 一种计费方法,以及终端、服务器和计费系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102890832A (zh) * 2012-09-18 2013-01-23 深圳创维数字技术股份有限公司 一种公交车分段计费方法及装置、系统
US10332162B1 (en) * 2013-09-30 2019-06-25 Square, Inc. Using wireless beacons for transit systems
CN105631945B (zh) * 2014-10-30 2018-11-23 国际商业机器公司 用于识别起点/终点配对的方法和装置
JP6602683B2 (ja) * 2016-02-05 2019-11-06 株式会社東芝 充電装置および位置ずれ検出方法
CN105894272A (zh) * 2016-04-05 2016-08-24 南昌大学 一种基于手机app的公交即时支付方法及支付、充值和查询系统
CN111340464B (zh) * 2016-09-20 2023-12-12 徐蔚 一种数字人的支付方法、装置与移动终端
CN106651337A (zh) * 2016-11-29 2017-05-10 湖州朗讯信息科技有限公司 一种公交车付费方法及系统
CN108492098B (zh) 2018-01-30 2022-04-22 青岛中兴智能交通有限公司 一种跨区域公交卡统一结算方法和装置
CN109685492A (zh) * 2018-12-25 2019-04-26 杭州琛华科技有限公司 一种公共交通付款方法和装置
CN109685577A (zh) * 2018-12-25 2019-04-26 杭州琛华科技有限公司 一种公共交通自助计费方法和装置
CN109658202A (zh) * 2018-12-27 2019-04-19 浙江言川科技有限公司 一种基于公共交通的自助乘车方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089446A1 (en) * 2016-11-11 2018-05-17 Operr Technologies, Inc. System and method for geo-aware transportation billing verification
CN108551651A (zh) * 2018-04-08 2018-09-18 深圳卡通新技术有限公司 基于移动终端的公交车分段计费方法
CN108834048A (zh) * 2018-06-14 2018-11-16 武汉斑马快跑科技有限公司 一种乘客下车行为识别方法及装置
CN109168130A (zh) * 2018-08-16 2019-01-08 北京三快在线科技有限公司 营运车辆计费方法及装置、电子设备、存储介质
CN110113710A (zh) * 2019-05-14 2019-08-09 京东方科技集团股份有限公司 一种计费方法,以及终端、服务器和计费系统

Also Published As

Publication number Publication date
US20220020068A1 (en) 2022-01-20
CN110113710B (zh) 2022-01-18
US12086850B2 (en) 2024-09-10
CN110113710A (zh) 2019-08-09

Similar Documents

Publication Publication Date Title
WO2020228771A1 (zh) 一种生成计费信息的方法,以及终端、服务器和系统
CA3084854C (en) Processing method and apparatus for fee calculation, and vehicle payment system
CN108346042B (zh) 车费缴纳方法、装置、终端及计算机可读存储介质
CN105429200A (zh) 一种基于移动智能终端的电动汽车智能充电方法
CN106114251A (zh) 一种基于移动终端的充电桩预约充电方法
EP3528193A1 (en) Method and device for in-vehicle payment
CN105956905A (zh) 一种无人值守的汽车分时租赁系统
CN109886732A (zh) 一种公共交通的计费方法、存储介质和车载计费设备
CN109816391A (zh) 公共交通工具的客票支付方法及系统、存储介质
CN110667431B (zh) 电动车辆的支援系统
CN108334965A (zh) 一种停车场车位预约的方法和装置
CN108422882A (zh) 充电方法及装置
WO2023060902A1 (zh) 公共交通工具的乘车方法及装置、设备、存储介质和计算机程序产品
CN112232797B (zh) 一种无人驾驶汽车的乘车付费方法、装置及电子设备
KR20200028277A (ko) 전기차 대여 서비스 제공 서버, 방법 및 프로그램
CN107610351A (zh) 一种实现汽车共享的设备、云平台及系统
CN108777002A (zh) 停车场收费方法、系统及计算机可读存储介质
US20190164355A1 (en) Fee setting server, fee setting method, and fee setting system for car sharing fee
CN110852851B (zh) 基于区块链的交通工具共享方法、装置及可读存储介质
CN109887326A (zh) 车位预约控制方法及车位预约控制装置
CN109903401A (zh) 车辆支付管理方法、车载终端及电子设备
CN110853157B (zh) 一种停车场出入场支付管理系统及方法
CN110414737B (zh) 多种公共交通工具的统一行程处理方法及装置
CN112669112B (zh) 一种停车月卡自动续费的方法及系统
CN111275836A (zh) 基于二维码的乘车收费方法、装置、系统以及终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20805284

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20805284

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20805284

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 25/07/2022)