NFC online travel method, storage medium and program product

Abstract

The present application discloses an NFC online travel method, storage medium and program product, which relates to the field of mobile payment technology, and discloses an NFC online travel method, including: obtaining user registration and login information; receiving and caching the user account number returned by the application end background according to the user registration and login information; reading the cached user's last trip identifier according to the user account number; comparing the user's last trip identifier with the trip identifier in the information tag on the device end, and judging the consistency of the trip identifier; matching the user's trip according to the judgment result of the consistency of the trip identifier, and judging whether to perform an asynchronous deduction operation according to the matching result. The information tag configured on the device end is read by NFC, and the application end is called up to realize the interconnection between the application end and the device, and through the interaction with the application end background, an online travel mode of asynchronous payment in which the user rides first and pays later is realized.

Description

Technical Field

[0001] The present application relates to the field of mobile payment technology, and in particular to an NFC online travel method, a storage medium, and a program product. Background Art

[0002] In the field of modern transportation, the prepaid model is a common payment method that requires users to pay a certain amount in advance before riding. This model is implemented in the form of physical cards, mobile phone interoperability cards, etc. Users need to purchase physical cards or activate mobile phone interoperability cards and pre-charge them; the prepaid model provides a convenient riding experience, and users do not need to make cash transactions when riding, which reduces the waiting time in line.

[0003] With the development of mobile payment technology, the field of transportation has also begun to introduce mobile APP as a payment tool, such as boarding code and mobile phone interoperability card. Users generate boarding code through mobile APP or use NFC function to interact with rail transportation equipment to achieve fast boarding and fare deduction; mobile payment methods provide a more flexible and convenient payment experience. Users do not need to carry physical cards, but they need to ensure that the mobile phone has sufficient power and network connection.

[0004] However, most of the existing transportation modes are prepaid or simultaneous payment, which cannot meet the user's expectation of online travel where they can ride first and pay later. Summary of the invention

[0005] The main purpose of this application is to provide an NFC online travel method, storage medium and program product, aiming to solve the technical problem that most existing transportation modes are prepaid or synchronous payment, and cannot realize the user's expectation of online travel of riding first and paying later.

[0006] To achieve the above objectives, the present application proposes an NFC online travel method, which is applied to an application end, and the method includes:

[0007] Get user registration and login information;

[0008] Receive and cache the user account number returned by the application backend according to the user registration and login information;

[0009] Read the cached user's last trip identifier according to the user account number;

[0010] Compare the user's last trip identifier with the trip identifier in the information tag on the device to determine the consistency of the trip identifier;

[0011] The user itinerary is matched according to the judgment result of the consistency of the itinerary identifier, and it is determined whether to perform an asynchronous deduction operation according to the matching result.

[0012] In one embodiment, the step of reading the cached user's last trip identifier according to the user account number includes:

[0013] Check whether the user's last trip identifier corresponding to the user account number in the cache is empty;

[0014] If the user's last trip identifier is empty, a request is sent to the application backend to query the user's last trip identifier;

[0015] Receive the request query response returned by the application backend, and cache the user's last trip identifier queried by the application backend.

[0016] In one embodiment, the step of comparing the user's last trip identifier with the trip identifier in the information tag on the device to determine whether the trip identifiers are consistent includes:

[0017] Determine whether the user has registered and logged in;

[0018] If the user has not registered and logged in, he / she will register and log in. An account number will be generated in the background of the application according to the user's registration and login information, and cached on the user side;

[0019] If the user is logged in, the information tag on the device is read through NFC and cached in the backend of the application;

[0020] The device-side information tag is generated by assembling the application-side URL, site information, device information, and itinerary identifier.

[0021] In one embodiment, the step of comparing the user's last trip identifier with the trip identifier in the information tag on the device to determine the consistency of the trip identifier includes:

[0022] Read the user's last trip ID and the information tag on the device;

[0023] Comparing the consistency of the trip identifier according to the user's last trip identifier and the information tag on the device;

[0024] If the user's last trip ID is consistent with the trip ID in the information tag on the device, a trip ID discrepancy instruction is issued, and abnormal information is displayed or broadcast on the device, and the user's last trip ID in the cache is set to exit the station;

[0025] If the user's last trip ID is inconsistent with the trip ID in the information tag on the device, check whether the user is in arrears.

[0026] In one embodiment, the step of setting the user's last trip identifier in the cache as exiting the station includes:

[0027] Clear the cached user's last trip identifier, read the cached application-side account information through the BOM machine and assemble the site equipment information to which the BOM machine belongs, generate a trip push and set the cached user's last trip identifier in the trip push to exit.

[0028] In one embodiment, the querying whether the user is in arrears includes:

[0029] Call the application backend to query the user's arrears status;

[0030] If the user has outstanding payments, an outstanding payment error message will be issued, and abnormal information will be displayed or broadcasted on the device to prompt the user to complete the outstanding payment.

[0031] If the user has no outstanding payments, the user's trip ID in the device's information tag will be cached in the user's last trip ID field, and a gate opening instruction will be issued to obtain the current time, and the trip will be asynchronously pushed to the application backend.

[0032] In one embodiment, the step of matching the user's itinerary according to the judgment result of the consistency of the itinerary identifier and judging whether to perform the asynchronous deduction operation according to the matching result includes:

[0033] Receive itinerary push from the backend of the application and record the current itinerary;

[0034] Updating the user's trip identifier in the current trip to the user's last trip identifier and storing it in the database;

[0035] Check whether the itinerary ID in the current itinerary record is an outbound record or a BOM processing record through the application backend to determine whether to match the user's itinerary;

[0036] If the trip identifier is an outbound record or a BOM processing record, the application backend will perform user trip matching;

[0037] When the itinerary is successfully matched, the deduction record generated by the application background is received and the deduction operation is performed asynchronously.

[0038] In addition, to achieve the above purpose, the present application also proposes an NFC online travel method, which is applied to the background of the application end, and the method includes:

[0039] Send the user account number to the application according to the user registration and login information;

[0040] Return the user's last trip ID to the application based on the user account number;

[0041] Determine the consistency of the trip identifier based on the cached user's last trip identifier and the trip identifier in the information tag on the device side;

[0042] The user's itinerary is matched according to the cached itinerary identifier consistency result, and it is determined whether to perform the asynchronous deduction operation.

[0043] In addition, to achieve the above-mentioned purpose, the present application also provides an NFC online travel device, the NFC online travel device comprising:

[0044] Information acquisition module, used to obtain user registration and login information;

[0045] The receiving and caching module is used to receive and cache the user account number returned by the application backend according to the user registration and login information;

[0046] An information reading module is used to read the cached user's last trip identifier according to the user account number;

[0047] A consistency judgment module is used to compare the user's last trip identifier with the trip identifier in the information tag on the device to determine their consistency;

[0048] The itinerary matching module is used to match the user itinerary according to the itinerary identification consistency result, and determine whether to perform the asynchronous deduction operation according to the matching result.

[0049] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the NFC online travel method described above are implemented.

[0050] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, wherein the computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the NFC online travel method described above are implemented.

[0051] One or more technical solutions proposed in this application have at least the following technical effects:

[0052] By obtaining user registration and login information; receiving and caching the user account number returned by the application backend according to the user registration and login information; reading the cached user's last trip identifier according to the user account number; comparing the user's last trip identifier with the trip identifier in the information tag on the device side to determine the consistency of the trip identifier; matching the user's trip according to the judgment result of the consistency of the trip identifier, and determining whether to perform an asynchronous deduction operation according to the matching result; solving the problem that most existing transportation modes are prepaid or synchronous payment modes. Compared with the existing technology, there is no need to activate a ride code / mobile phone interconnection card or purchase a physical card, realizing the user's expectation of online travel of riding first and paying later, and improving the user's riding experience and satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0054] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0055] Figure 1 A flow chart of the first embodiment of the NFC online travel method of the present application;

[0056] Figure 2 A flow chart of the second embodiment of the NFC online travel method of the present application;

[0057] Figure 3 A flow chart of the third embodiment of the NFC online travel method of the present application;

[0058] Figure 4 A flow chart of the fourth embodiment of the NFC online travel method of the present application;

[0059] Figure 5 A flowchart of the fifth embodiment of the NFC online travel method of the present application is provided;

[0060] Figure 6 This is a schematic diagram of the module structure of the NFC online travel device according to an embodiment of the present application;

[0061] Figure 7 This is a schematic diagram of the device structure of the hardware operating environment involved in the NFC online travel method in the embodiment of the present application.

[0062] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0063] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0064] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0065] In this embodiment, for ease of description, the following description is made by taking the identification application end as the execution subject.

[0066] Since most of the existing transportation modes in the prior art are prepaid or synchronous payment, it is impossible to realize the user's expectation of online travel in which the user rides first and pays later.

[0067] The present application provides a solution, which includes obtaining user registration and login information; receiving and caching the user account number returned by the application end background according to the user registration and login information; reading the cached user's last trip identifier according to the user account number; comparing the user's last trip identifier with the trip identifier in the information tag on the device end to determine the consistency of the trip identifier; matching the user's trip according to the determination result of the consistency of the trip identifier, and determining whether to perform an asynchronous deduction operation according to the matching result; solving the problem that most existing transportation travel modes are prepaid modes or synchronous payment modes. Compared with the existing technology, there is no need to activate a ride code / mobile phone interconnection card or purchase a physical card, thereby realizing the user's expectation of online travel of riding first and paying later, thereby improving the user's riding experience and satisfaction.

[0068] Based on this, the present application embodiment provides an NFC online travel method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the NFC online travel method of the present application.

[0069] In this embodiment, the NFC online travel method includes steps S10 to S50:

[0070] Step S10, obtaining user registration and login information;

[0071] It should be noted that the user registration and login information is the necessary information entered by the user when registering and logging in to the application, such as mobile phone number, ID number, email address, password, etc.; the user registration and login information is sent to the application backend for verification.

[0072] Step S20, receiving and caching the user account number returned by the application backend according to the user registration and login information;

[0073] It should be noted that the registration and login information provided by the user is verified through the application background, including mobile phone number verification, email verification, etc. After the verification is passed, the application background generates a unique user account number based on the user's registration and login information for the purpose of identifying and tracking the user's information.

[0074] Specifically, the application backend returns the generated user account number to the application, and the application receives the user account number and caches it on the user's device, such as the local storage or cache of a mobile phone.

[0075] Step S30, reading the cached user's last trip identifier according to the user account number;

[0076] It should be noted that the user's last trip identifier refers to the identifier of the user's last trip recorded in the transportation system, which is used to track the user's historical trip information, including the starting station, end station, timestamp, etc. of the last trip.

[0077] Specifically, the application sends a read request to the application background, and the read request includes the user account number. After receiving the read request, the application background searches for the corresponding user's last trip identifier in the cache and reads it out. The application background returns the read user's last trip identifier to the application.

[0078] Step S40, comparing the user's last trip identifier with the trip identifier in the information tag on the device to determine the consistency of the trip identifier;

[0079] It should be noted that an information tag is an identifier used to classify and mark information; the information tag on the device side is assembled and generated by the URL, site information, device information, itinerary identifier, etc. on the application side.

[0080] Specifically, the user's last trip identifier is read from the cache on the application side. When the user passes through a transportation device, the device generates an information tag containing the identification information of the current trip. The user's last trip identifier is compared with the trip identifier in the device-side information tag. The comparison may include site information, timestamp, device information, etc. to ensure the consistency of the two identifiers. Whether the two trip identifiers are consistent is determined based on the comparison result. If they are consistent, it may mean that the user is trying to reuse the previous trip identifier and further processing is required. If they are inconsistent, it means that the user has made a new trip and the normal trip processing flow can continue.

[0081] Step S50, matching the user's itinerary is performed according to the judgment result of the consistency of the itinerary identifier, and judging whether to perform an asynchronous deduction operation according to the matching result.

[0082] It should be noted that the user itinerary matching refers to the process of comparing and verifying the user's actual itinerary information with the itinerary information recorded in the system, including comparing the user's entry and exit records to confirm whether the user uses the transportation service according to the normal itinerary route; the asynchronous deduction refers to the process of riding first and paying later without the user having to pay immediately after completing the transportation itinerary. This deduction method is different from the traditional instant payment method, which usually requires the user to perform payment operations when riding, such as swiping a card or scanning a code. It is also different from the payment method of activating a physical card in advance and prepaying the recharge amount.

[0083] This embodiment provides an NFC online travel method, which obtains user registration and login information; receives and caches the user account number returned by the application end background according to the user registration and login information; reads the cached user's last trip identifier according to the user account number; compares the user's last trip identifier with the trip identifier in the information tag on the device end to determine the consistency of the trip identifier; matches the user's trip according to the judgment result of the consistency of the trip identifier, and determines whether to perform an asynchronous deduction operation according to the matching result. This solves the problem that most existing transportation travel methods are prepaid or synchronous payment methods. Compared with the existing technology, there is no need to activate a ride code / mobile phone interconnection card or purchase a physical card, realizing the user's online travel expectation of riding first and paying later, and improving the user's riding experience and satisfaction.

[0084] Further, refer to Figure 2 The second embodiment of the NFC online travel method of the present application provides a flow chart based on the above Figure 2 The embodiment shown is a further refinement of the step S10 of "reading the cached user's last trip identifier according to the user account number" and includes steps A201 to A203:

[0085] Step A201, querying whether the user's last trip identifier corresponding to the user account number in the cache is empty;

[0086] Specifically, the application sends a request to the application backend, and the request includes the user's account number. After receiving the request, the application backend searches the cache for the corresponding user's last trip identifier.

[0087] Step A202: if the user's last trip identifier is empty, a request is sent to the application backend to query the user's last trip identifier;

[0088] It should be noted that if the user's last trip identifier is empty, it means that the user has not completed any trip, or the last trip information has not been updated to the cache.

[0089] Step A203, receiving the request query response returned by the application backend, and caching the user's last trip identifier queried by the application backend.

[0090] It should be noted that the location and method of caching depends on the implementation on the application side, such as local storage or application cache.

[0091] In this embodiment, the user account number is used to ensure that the application end can quickly and accurately obtain the status of the user's last trip identification, providing the user with a smooth riding experience.

[0092] Further, refer to Figure 3The third embodiment of the NFC online travel method of the present application provides a flow chart based on the above Figure 3 The embodiment shown in the figure further includes steps A301 to A303 before "comparing the user's last trip identifier with the trip identifier in the information tag on the device to determine the consistency of the trip identifier" in step S40:

[0093] Step A301, determine whether the user has registered and logged in;

[0094] It should be noted that users complete the registration and login process on the application and enter necessary information, such as mobile phone number, ID number, email address, etc.

[0095] Specifically, the user end checks whether the user has completed the registration and login process, usually by checking whether the user's mobile phone number, email address, user name and other information exists. If this information already exists in the system, the user is registered; it can also be determined by checking whether the user's login credentials, such as password, mobile phone verification code, biometric information, etc. are valid. If the login credentials are valid, the user is logged in; it can also be determined by analyzing the user's behavior patterns to determine whether the user is logged in, such as inferring that the user is logged in by the user viewing travel information, modifying settings and configurations, etc.

[0096] Step A302: If the user has not registered and logged in, register and log in, generate an account number in the application end background according to the user registration and login information, and cache it in the user end;

[0097] It should be noted that the application sends the user information to the application background for verification. After the verification is passed, an account number is generated for the user and cached on the user side.

[0098] Step A303, if the user has logged in, the information tag on the device side is read through NFC and cached to the background of the application side; the information tag on the device side is assembled and generated by the URL, site information, device information, and itinerary identifier of the application side.

[0099] It should be noted that the information tag on the device side is dynamically generated by the device side according to the user's itinerary operation; the user approaches the transportation equipment through the NFC function on the mobile phone, and the NFC reader on the device side reads the NFC signal of the user's mobile phone and generates an information tag containing the user's current itinerary.

[0100] Specifically, when user A passes through a transportation device during a trip, the application checks whether user A has completed registration and login. If it is found that user A has not logged in, it guides user A to register and log in. After user A completes the registration and login process on the application, the front end of the application caches user A's account number to the application. User A reads the information tag generated by the transportation device through the NFC function of the mobile phone, and caches the read information tag to the application.

[0101] This embodiment ensures the user's identity authentication and authorization on the application side by determining whether the user has registered and logged in, and obtains real-time travel information by reading the information tag generated by the device side through the mobile phone NFC. The information tag data is transmitted to the user's mobile phone in real time via NFC or other wireless communication methods, ensuring real-time updating and transmission of information and reducing the risk of information leakage.

[0102] Further, refer to Figure 4 The fourth embodiment of the NFC online travel method of the present application provides a flow chart based on the above Figure 4 The embodiment shown further refines the step S40 of "comparing the user's last trip identifier with the trip identifier in the information tag on the device to determine the consistency of the trip identifier", including steps A401 to A404:

[0103] Step A401, reading the user's last trip identifier and the information tag on the device;

[0104] It should be noted that the application reads the user's last trip identifier from the cache, which contains the necessary information of the user's last trip; at the same time, the application reads the information tag from the transportation equipment through NFC or other wireless communication methods, which contains the identification information of the current trip, such as entry or exit information.

[0105] Step A402, comparing the consistency of the trip identifier according to the user's last trip identifier and the information tag on the device;

[0106] It should be noted that the comparison content includes at least station information, timestamp, equipment, etc. to ensure the consistency of the two itinerary identifiers.

[0107] Step A403: If the user's last trip identifier is consistent with the trip identifier in the information tag on the device, a trip identifier inconsistency instruction is issued, and abnormal information is displayed or broadcasted on the device, and the user's last trip identifier in the cache is set to exit the station;

[0108] It should be noted that if the user's last trip identifier is consistent with the trip identifier in the information tag on the device side, it means that the user may have attempted to reuse the previous trip identifier, and a trip identifier mismatch instruction will be sent to the device side, and abnormal information will be displayed or broadcast on the device side, such as "The trip identifier does not match, please swipe the card again." When the user's last trip identifier in the cache is set to the exit status through the customer service center, it means that the user's last trip has been completed and a new trip identifier is required for the next trip.

[0109] Step A404: If the user's last trip identifier is inconsistent with the trip identifier in the information tag on the device, it is checked whether the user is in arrears.

[0110] It should be noted that if the user's last trip identifier is inconsistent with the trip identifier in the information tag on the device side, it means that the user has made a new trip. The application side queries whether the user is in arrears. If the user is in arrears, the user can be prompted to handle the arrears.

[0111] Specifically, when user B passes through transportation equipment, such as a rail transit gate or a bus gate, the application reads the last trip identifier of user B from the cache, and reads the information tag generated by the device through NFC, compares the last trip identifier of user B with the trip identifier in the information tag on the device, and finds that they are consistent. At this time, the application sends an instruction that the trip identifier does not match, and displays or broadcasts abnormal information on the device. After processing by the customer service center, the application sets the last trip identifier of user B in the cache to the exit status.

[0112] This embodiment ensures the consistency of the trip identifier by comparing the user's last trip identifier with the trip identifier in the device-side information tag, prevents the user from repeatedly using the previous trip identifier to commit fraud, ensures the accuracy of billing and the security of the system, and reminds the user to perform correct operations by displaying or broadcasting abnormal information on the device side, thereby improving the user experience.

[0113] Furthermore, in one embodiment, the “setting the user's last trip identifier in the cache as having exited the station” is further refined to include:

[0114] Clear the cached user's last trip identifier, read the cached application-side account information through the BOM machine and assemble the site equipment information to which the BOM machine belongs, generate a trip push and set the cached user's last trip identifier in the trip push to exit.

[0115] It should be noted that when the user's last trip identifier is consistent with the trip identifier in the information tag on the device side, the user can go to the customer service center and find the customer service staff to clear the cached user's last trip identifier. The clearing operation may be to delete or update the relevant data in the cache so that the user's last trip identifier is no longer used for subsequent trip processing; the BOM machine is a special device used to read user account information and trip information, including user account number, balance, last trip identifier, etc.; site equipment information may include the user's current site, the equipment number used, entry and exit times, etc.; trip push is a request containing the user's current trip information, which is used to notify the application backend to update the user's trip record; the exited status indicates that the user's last trip has been completed and a new trip identifier is required for the next trip.

[0116] This embodiment clears the erroneous user's last trip identifier through the BOM machine, thereby avoiding possible duplicate billing or erroneous deductions. By assembling site equipment information and generating itinerary push, it is helpful to obtain the latest itinerary information, which is helpful for itinerary management and deduction calculation in the background of the application end. By setting the user's last trip identifier cached in the itinerary push to exit the station, the end of the user's last trip is confirmed.

[0117] Furthermore, in one embodiment, the “querying whether the user is in arrears” is further refined to include:

[0118] If the user has outstanding payments, an outstanding payment error message will be issued, and abnormal information will be displayed or broadcasted on the device to prompt the user to complete the outstanding payment.

[0119] If the user has no outstanding payments, the user's trip ID in the device's information tag will be cached in the user's last trip ID field, and a gate opening instruction will be issued to obtain the current time, and the trip will be asynchronously pushed to the application backend.

[0120] Specifically, if the user has any outstanding payments, the application sends an outstanding payment error instruction to the device, and displays or broadcasts abnormal information on the device, such as "Your account has outstanding payments, please complete the repayment", prompting the user to complete the outstanding payment repayment, which may include providing repayment options or guiding the user to the corresponding interface; if the user has no outstanding payments, the user's trip identifier in the information tag on the device is cached to the user's last trip identifier field, and a gate opening instruction / pass instruction is sent to the device, allowing the user to obtain the current time through the device, which is used to record the timestamp of the trip and asynchronously push the trip to the backend server of the application; the device includes at least rail transit gates and bus card swiping gates, which are suitable for rail transit scenarios or bus segmentation scenarios.

[0121] Further, refer to Figure 5 The fifth embodiment of the NFC online travel method of the present application provides a flow chart based on the above Figure 5 The embodiment shown further refines the step S50 of "matching the user's itinerary according to the judgment result of the consistency of the itinerary identifier, and judging whether to perform the asynchronous deduction operation according to the matching result", including steps A501 to A505:

[0122] Step A501, receiving the itinerary push from the application backend and recording the current itinerary;

[0123] It should be noted that the itinerary push includes the user's current itinerary information, such as entry or exit information, site information, equipment information, etc.

[0124] Step A502, updating the user's trip identifier in the current trip to the user's last trip identifier, and storing it in a database;

[0125] Step A503, checking whether the trip identifier in the current trip record is an outbound record or a BOM processing record through the application end background, and determining whether to perform user trip matching;

[0126] It should be noted that the exit record or BOM processing record indicates that the user has completed a complete trip.

[0127] Step A504, if the trip identifier is an outbound record or a BOM processing record, the application backend performs user trip matching;

[0128] It should be noted that the itinerary matching process may include comparing the user's entry or exit records to ensure the continuity of the itinerary.

[0129] Step A505, when the itinerary is successfully matched, the deduction record generated by the application backend is received and the deduction operation is performed asynchronously.

[0130] It should be noted that the deduction record contains information such as the amount and deduction time; the asynchronous execution of the deduction operation refers to a method of riding first and paying later, which does not interfere with the user's current operation and does not require the user to make immediate payment after completing the transportation trip. This deduction method is different from the traditional instant payment method, which usually requires the user to make payment operations when riding, such as swiping a card or scanning a code. It is also different from the payment method of activating a physical card in advance and prepaying the recharge amount.

[0131] This embodiment ensures accurate recording of user travel information by receiving travel push and recording the current travel, updates the user travel identifier in the current travel to the user's last travel identifier, helps to maintain the continuity and consistency of the travel record, and stores the updated travel record in the database for subsequent query and processing; by checking whether the travel identifier in the travel record is an exit record or a BOM processing record, user travel matching is performed, and entry and exit records are compared, thereby improving the accuracy and efficiency of travel processing; when the travel matching is successful, a deduction record is generated, and the deduction operation is performed asynchronously, which solves the problem that most existing transportation travel modes are prepaid or synchronous payment modes, and there is no need to activate a ride code / mobile phone interconnection card or purchase a physical card, thereby realizing the user's online travel expectation of riding first and paying later, thereby improving the user's riding experience and satisfaction.

[0132] In one embodiment, the present application further proposes an NFC online travel method, which is applied to the backend of the application end, and the method includes:

[0133] Send the user account number to the application according to the user registration and login information;

[0134] Return the user's last trip ID to the application based on the user account number;

[0135] Determine the consistency of the trip identifier based on the cached user's last trip identifier and the trip identifier in the information tag on the device side;

[0136] The user's itinerary is matched according to the consistency result of the cached itinerary identifier, and it is determined whether to perform the asynchronous deduction operation.

[0137] In this embodiment, based on the registration and login information collected by the application end, the application end background sends the user account number to the application end, searches for the corresponding user's last trip identifier in the database, sends it back to the application end, receives the user's last trip identifier cached by the application end and the trip identifier in the information tag of the device end, automatically matches the user's trip information, and reduces manual intervention; if the cached user's last trip identifier is consistent with the trip identifier in the device end information tag, the user's trip is matched, a deduction record is generated in the application end background, and the deduction operation is performed asynchronously, which improves the user's travel efficiency and reduces the user's payment pressure when traveling.

[0138] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the NFC online travel method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0139] In addition, this application also provides an NFC connected travel device, please refer to Figure 6 , the NFC online travel device comprises:

[0140] 10: Information acquisition module, used to obtain user registration and login information;

[0141] 20: Receiving and caching module, used to receive and cache the user account number returned by the application backend according to the user registration and login information;

[0142] 30: an information reading module, used to read the cached user's last trip identifier according to the user account number;

[0143] 40: a consistency judgment module, used to compare the user's last trip identifier with the trip identifier in the information tag on the device side to judge their consistency;

[0144] 50: Itinerary matching module, used to match user itineraries according to itinerary identifier consistency results, and determine whether to perform asynchronous deduction operations according to the matching results.

[0145] The NFC online travel device provided by the present application adopts the NFC online travel method in the above embodiment, which can solve the technical problem that most existing transportation modes are prepaid or synchronous payment, and cannot realize the user's expectation of online travel of riding first and paying later. Compared with the prior art, the beneficial effects of the NFC online travel device provided by the present application are the same as the beneficial effects of the NFC online travel method provided by the above embodiment, and other technical features in the NFC online travel device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0146] In addition, the present application also provides an NFC online travel device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the NFC online travel method in the above-mentioned embodiment one.

[0147] Reference below Figure 7 , which shows a schematic diagram of the structure of an NFC online travel device suitable for implementing the embodiment of the present application. The NFC online travel device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7The NFC online travel device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0148] like Figure 7 As shown, the NFC connected travel device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 to the random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the xxx device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. The input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the NFC connected travel device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an NFC connected travel device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0149] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0150] The NFC online travel device provided by this application adopts the NFC online travel method in the above embodiment, which can solve the technical problem that most existing transportation modes are prepaid or synchronous payment, and cannot realize the user's expectation of online travel of riding first and paying later. Compared with the prior art, the beneficial effects of the NFC online travel device provided by this application are the same as the beneficial effects of the NFC online travel method provided by the above embodiment, and other technical features in the NFC online travel device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0151] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0152] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0153] In addition, the present application also provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the NFC online travel method in the above-mentioned embodiment.

[0154] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0155] The computer-readable storage medium may be included in the NFC connected travel device; or may exist independently without being assembled into the NFC connected travel device.

[0156] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the NFC online travel device, the NFC online travel device: obtains user registration and login information; receives and caches the user account number returned by the application backend according to the user registration and login information; reads the cached user's last trip identifier according to the user account number; compares the user's last trip identifier with the trip identifier in the information tag on the device side to determine the consistency of the trip identifier; matches the user trip according to the judgment result of the consistency of the trip identifier, and determines whether to perform an asynchronous deduction operation according to the matching result.

[0157] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0158] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0159] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0160] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned NFC online travel method, and can solve the technical problem that most existing transportation modes are prepaid or synchronous payment, and cannot realize the user's online travel expectations of riding first and paying later. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the NFC online travel method provided by the above-mentioned embodiment, and will not be repeated here.

[0161] In addition, the present application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps of the NFC online travel method as described above are implemented.

[0162] The computer program product provided by this application can solve the technical problem that most existing transportation modes are prepaid or synchronous payment, and cannot realize the user's expectation of online travel of riding first and paying later. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the NFC online travel method provided by the above embodiment, which will not be repeated here.

[0163] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. An NFC online travel method, characterized in that: Applied to the application side, the method includes: Get user registration and login information; The user registration and login information is the information entered by the user when registering and logging in on the application side, including at least mobile phone number, ID number, email address, and password. The user registration and login information is sent to the application side backend for verification; Receive and cache the user account number returned by the application backend according to the user registration and login information; Read the cached user's last trip identifier according to the user account number; Compare the user's last trip identifier with the trip identifier in the information tag on the device to determine the consistency of the trip identifier; The step of comparing the user's last trip identifier with the trip identifier in the information tag on the device side to determine the consistency of the trip identifier includes: reading the user's last trip identifier and the information tag on the device side; comparing the consistency of the trip identifier based on the user's last trip identifier and the information tag on the device side; if the user's last trip identifier is consistent with the trip identifier in the information tag on the device side, issuing a trip identifier inconsistency instruction, displaying or broadcasting abnormal information on the device side, and setting the user's last trip identifier in the cache as exited; if the user's last trip identifier is inconsistent with the trip identifier in the information tag on the device side, querying whether the user is in arrears; The querying whether the user is in arrears includes: calling the application end backend to query the user's arrears status; if the user is in arrears, issuing an arrears error instruction, and displaying or broadcasting abnormal information on the device end, prompting the user to complete the arrears repayment; if the user is not in arrears, caching the user's trip identifier in the information tag on the device end to the user's last trip identifier field, issuing a gate opening instruction, obtaining the current time, and asynchronously sending the trip push to the application end backend; The user itinerary is matched according to the judgment result of the consistency of the itinerary identifier, and whether to perform the asynchronous deduction operation is determined according to the matching result; the user itinerary matching is the process in which the application backend compares and verifies the user's actual itinerary information with the itinerary information recorded in the system.

2. The method according to claim 1, characterized in that The step of reading the cached user's last trip identifier according to the user account number includes: Check whether the user's last trip identifier corresponding to the user account number in the cache is empty; If the user's last trip identifier is empty, a request is sent to the application backend to query the user's last trip identifier; Receive the request query response returned by the application backend, and cache the user's last trip identifier queried by the application backend.

3. The method according to claim 2, characterized in that The step of comparing the user's last trip identifier with the trip identifier in the information tag on the device to determine whether the trip identifiers are consistent includes: Determine whether the user has registered and logged in; If the user has not registered and logged in, he / she will register and log in. An account number will be generated in the background of the application according to the user's registration and login information, and cached on the user side; If the user is logged in, the information tag on the device is read through NFC and cached in the backend of the application; The device-side information tag is generated by assembling the application-side URL, site information, device information, and itinerary identifier.

4. The method according to claim 1, characterized in that The step of setting the user's last trip identifier in the cache as exiting the station comprises: Clear the cached user's last trip identifier, read the cached application-side account information through the BOM machine and assemble the site equipment information to which the BOM machine belongs, generate a trip push and set the cached user's last trip identifier in the trip push to exit.

5. The method according to claim 1, characterized in that The step of matching the user itinerary according to the judgment result of the consistency of the itinerary identifier and judging whether to perform the asynchronous deduction operation according to the matching result comprises: Receive itinerary push from the backend of the application and record the current itinerary; Updating the user's trip identifier in the current trip to the user's last trip identifier and storing it in the database; Check whether the itinerary ID in the current itinerary record is an outbound record or a BOM processing record through the application backend to determine whether to match the user's itinerary; If the trip identifier is an outbound record or a BOM processing record, the application backend will perform user trip matching; When the itinerary is successfully matched, the deduction record generated by the application background is received and the deduction operation is performed asynchronously.

6. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the NFC online travel method according to any one of claims 1 to 5 are implemented.

7. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the NFC online travel method according to any one of claims 1 to 5 are implemented.

Images