Cross-border payment method, terminal equipment, system and storage medium

Abstract

The present application belongs to the field of communication technology, and in particular, relates to a cross-border payment method, terminal device, system and storage medium. By acquiring device information of a user device, a cloud user identity card is allocated to the user device based on the device information, a target user account is allocated based on the cloud user identity card, and based on the user's payment operation, a corresponding consumption amount is deducted from the target user account. Cross-border payment is implemented based on a temporarily allocated cloud user identity card, which simplifies the operation process of cross-border mobile payment and makes the operation more convenient.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and in particular, relates to a cross-border payment method, terminal equipment, system and storage medium. Background Art

[0002] With the accelerated development of globalization, more and more tourists are seeking more convenient and modern consumption methods during cross-border travel. However, traditional payment methods, such as credit cards and cash consumption, are still common, but are gradually showing their limitations. Especially in today's digital age, mobile payment is becoming an important part of daily transactions due to its fast and contactless characteristics.

[0003] However, existing mobile payment methods are cumbersome to operate, and there is still room for further improvement in convenience when it comes to cross-border payments. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a cross-border payment method, terminal device, system and storage medium to solve the technical problems of the existing cross-border payment methods that are cumbersome to operate and have poor convenience.

[0005] A first aspect of an embodiment of the present application provides a cross-border payment method, which is applied to a service device, and the method includes:

[0006] Get device information of user device;

[0007] allocating a cloud user identity card to the user device based on the device information;

[0008] Allocating a target user account based on the cloud user identity card;

[0009] Based on the user's payment operation, the corresponding consumption amount is deducted from the target user account.

[0010] The second aspect of an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of a cross-border payment method provided in the first aspect of an embodiment of the present application are implemented.

[0011] A third aspect of an embodiment of the present application provides a cross-border payment system, including a service device and a user device, wherein the service device is used to execute the steps of a cross-border payment method provided in the first aspect of an embodiment of the present application.

[0012] The fourth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of the cross-border payment method provided in the first aspect of the embodiments of the present application.

[0013] The cross-border payment method provided in the first aspect of the embodiment of the present application is applied to a service device, which obtains device information of a user device, allocates a cloud user identity card to the user device based on the device information, allocates a target user account based on the cloud user identity card, and deducts the corresponding consumption amount through the target user account based on the user's payment operation. Cross-border payment is implemented based on a temporarily allocated cloud user identity card, which simplifies the operational process of cross-border mobile payment and makes the operation more convenient.

[0014] It can be understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 This is a flow chart of a cross-border payment method provided by an embodiment of the present application;

[0017] Figure 2 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0018] Figure 3 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0019] Figure 4 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0020] Figure 5 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0021] Figure 6 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0022] Figure 7 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0023] Figure 8 This is a flow chart of a cross-border payment method provided by another embodiment of the present application;

[0024] Fig. 9 This is a schematic diagram of the structure of a terminal device provided by an embodiment of the present application;

[0025] Fig.10 It is a structural diagram of a cross-border payment system provided in one embodiment of the present application. DETAILED DESCRIPTION

[0026] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0027] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0028] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0029] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0030] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0031] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0032] Embodiment 1

[0033] The cross-border payment method provided in the embodiment of the present application is applied to a service device, by obtaining device information of a user device, allocating a cloud user identity card to the user device based on the device information, allocating a target user account based on the cloud user identity card, and deducting a corresponding consumption amount through the target user account based on the user's payment operation. Cross-border payment is implemented based on a temporarily allocated cloud user identity card, which simplifies the operational process of cross-border mobile payment and makes the operation more convenient.

[0034] In the application, the device formed by the server and SIMbank (SIM card reading and writing device) is used as a service device to run the cross-border payment method of the embodiment of the present application. The operator of this method can be an operator or a virtual operator. The server can be a cloud server or a service group formed by a group of independent servers connected to each other. SIMbank is a device that centrally inserts physical SIM cards and can read and write these SIM cards.

[0035] In the application, the service device is configured to have functions such as cloud SIM card scheduling, user information and device management, global roaming traffic service, and operation management to implement the cross-border payment method of the embodiment of the present application. Cloud SIM card scheduling refers to the control of the cloud SIM card in the SIMbank, including the status management of the cloud SIM card (idle, busy, etc.), allocation to the user terminal according to certain algorithm rules, remote authentication of the physical cloud SIM card, and recovery of the cloud SIM card. The cloud SIM card can also be in other forms, such as soft SIM card, ESIM card, etc., and no matter what form it is, it is uniformly managed by the cloud SIM card scheduling program. User information and device management refers to the storage and management of the user's identity information, device information, and the binding information of the identity information and device information. The global roaming traffic service is used to provide paid international roaming traffic packages. Users can choose the appropriate package according to the destination and the expected amount of data used, and intelligently identify the country or region where the user is located, automatically connect to the local network operator, and achieve seamless roaming. Operation management is achieved through the operation management system (i.e., BOSS system, BOSS: business & operation support system). The operation management system includes the origin operation management system (origin BOSS system) and the destination operation management system (destination BOSS system). The BOSS system interacts with the account interface provided by the bank to realize the expense settlement of the enterprise bank account.

[0036] In the application, the user device can be any one of a mobile phone, a personal digital assistant (PDA), a self-service terminal, a wearable device, a tablet computer, a laptop computer, a personal computer (PC), a netbook, and a portable broadband wireless router (MiFi device). The embodiments of the present application do not impose any restrictions on the specific types of service devices and user devices.

[0037] like Figure 1 As shown, a cross-border payment method provided in an embodiment of the present application is applied to a service device, including the following steps S101-S104:

[0038] Step S101: Acquire device information of a user device.

[0039] In the application, users can obtain user devices through the OTA platform at the starting point (the starting point of the user in this article is the starting point, and the place where the user is going to go is the destination) or the system operator's offline counter leasing or purchasing. After obtaining the user device, the user can use his or her mobile phone or other user terminal to scan the QR code on the user device to install the system's user program "User APP"; in particular, in this system, the user device will pre-install an APP for payment, and one application example can be the UnionPay Cloud QuickPass client APP. Among them, the user APP can be an APP software program that integrates at least one of the functions of user registration, binding the user device ID (usually the IMEI number of the user device), purchase of traffic packages in countries and regions around the world, and payment. When it has only one or part of the functions, the corresponding software programs can be installed for different functions. When it has all the above functions, only one software program (that is, the above-mentioned user APP) needs to be installed. The user APP can be installed by the user after the user receives the device, and can also be pre-installed by the user device manufacturer in mobile phones, personal digital assistants (PDA), self-service terminals, wearable devices, tablet computers, laptops, personal computers (PC), netbooks, portable broadband wireless routers (MiFi devices) and other user devices. The embodiment of the present application does not limit the installation location of the user APP. The user can register the user through the user APP on the user device, and perform operations such as binding the user device ID number. The user's registered identity information and device ID information can be uploaded to the service device, so that the operation of the user APP is associated with the user's rented or purchased user device and the user's registered identity information.

[0040] The user pre-charges through the user APP at the starting point, and uses the pre-charged amount to purchase the data package of the destination the user is going to, and the balance can be used as consumption money at the destination. Among them, user transfers can be through the link entrance such as PAYPAL (unlimited) provided by the user APP. The user uses his own credit card, savings card, etc. to transfer to the starting point corporate payment account opened in advance by the operator of this system to the selected bank, that is, the pre-charged amount is transferred to the starting point corporate payment account of the selected bank. The value of the pre-charged amount is also stored in the starting point operation management system of the service device. The above user registration information (that is, the user's identity information), the ID information of the user device obtained by the user (that is, the device information), the pre-charged amount, and the purchased target data package are all stored in the service device in association.

[0041] Step S102: allocating a cloud user identity card to the user device based on the device information.

[0042] In the application, the cloud user identity card (cloud SIM card) is a fixed cloud user identity card allocated by the cloud service device to the user device based on the target data package purchased by the user. The user device can access the mobile network of the target location through the cloud user identity card.

[0043] Step S103: allocating a target user account based on the cloud user identity card.

[0044] In the application, the target user account can be a sub-account pre-created by the operator under the target enterprise payment account pre-opened by the selected bank. When the user arrives at the target, the system can register and authenticate the sub-account based on the cloud user identity card to facilitate the user to temporarily use the payment method of the target. After success, a sub-account will be assigned, which will be used as the target user account of the user. The bank can be any bank that supports international business and has branches in the target location or region or has a good international network.

[0045] Step S104: Based on the user's payment operation, the corresponding consumption amount is deducted from the target user account.

[0046] In the application, when users use devices to make payments across borders (such as online shopping, restaurant checkout, etc.), they can deduct the corresponding amount from the target user account bound to the cloud user identity card through mobile payment, etc. The whole process is fast and transparent, ensuring the security of user funds and smooth payment experience.

[0047] In one embodiment, Figure 2 As shown, step S101 includes the following steps S111 to S112:

[0048] Step S111, based on the user's registration operation, obtain the user's registered identity information.

[0049] In the application, user registration is achieved through the registration operation of the user APP. After successful registration, the user's identity information (including username and password) is stored by the service device. After successful registration, the user can enter the username and password to log in to the user APP to perform subsequent user device binding operations.

[0050] Step S112: based on the binding operation of the user on the user device, the device information is obtained, and the user's identity information is bound to the device information and stored.

[0051] In the application, the user can bind the identity information with the device information in the user APP to establish a binding relationship between the user identity and the user device. The device information can be the IMEI number of the user device. The user's identity information and the device information can be uploaded to the service device for storage.

[0052] In one embodiment, Figure 3 As shown, after step S112, the following steps S113 to S115 are included:

[0053] Step S113: Based on the user's pre-charge operation, the enterprise payment account at the origin is pre-charged to obtain the pre-charge amount.

[0054] In the application, the operator pre-creates a corporate payment account at the origin and a corporate payment account at the destination. Both the corporate payment account at the origin and the corporate payment account at the destination are corporate accounts of the operator. At the origin, users can use their own credit cards, savings cards, etc. to transfer money to the corporate payment account at the origin through PAYPAL and other link entrances provided by the user APP. That is, after the user performs the pre-recharge operation, the pre-recharge will be made to the corporate payment account at the origin. The amount in the corporate payment account at the origin is the pre-recharge amount, which can be used to purchase traffic packages at the destination and can also be used by users for consumption at the destination.

[0055] Step S114, based on the user's operation of purchasing traffic using the pre-charged amount, a target traffic package of the user device is obtained.

[0056] In the application, after the user pre-recharges, he can purchase the target traffic package in the user APP. When purchasing traffic, he can choose the corresponding duration as needed, such as three days, five days, seven days, etc. After the user purchases the target traffic package, after the user enters the target location and turns on the user device for the first time, network services of corresponding duration can be provided according to the duration of the traffic purchased by the user. The amount for purchasing the target traffic package is paid from the user's pre-recharge amount, so that the user balance in the starting place enterprise payment account is the remaining amount after deducting the purchase cost of the target traffic package from the pre-recharge amount. When the starting place enterprise payment account deducts the amount, the amount deduction information can also be obtained by the starting place operation management system of the service equipment, so that the starting place operation management system can obtain the user balance in the starting place enterprise payment account.

[0057] In the application, the user's starting pre-charge amount can also be analyzed, including but not limited to the total amount of recharge, the currency used (such as US dollars, euros, RMB, etc.), the recharge time, and the payment method used when recharging (such as credit cards, debit cards, third-party payment platforms, etc.). By verifying the accuracy and completeness of this information, the user's total pre-charge amount is finally determined. The service device can interact with the payment gateway and the bank system for confirmation to ensure the validity of the recharge transaction and the security of the funds.

[0058] Step S115, binding and storing the user's pre-charge amount, the target destination traffic package, the identity information and the device information.

[0059] In the application, the user's pre-charged amount, the target traffic package, the identity information and the device information can all be bound and stored in the service device, thereby realizing traffic billing and consumption amount billing.

[0060] In one embodiment, Figure 4 As shown, step S102 includes the following steps S1021 and S1022:

[0061] Step S1021: based on the first startup operation of the user device at the target location by the user, the cloud user identity card is allocated to the user device according to the traffic package of the target location.

[0062] Step S1022, during the use of the user device at the target location, the cloud user identity card is bound to the user device until the user successfully performs a bill settlement operation on the user device.

[0063] In the application, when the user enters the destination and starts the user device for the first time, the data of the traffic package purchased by the user is obtained. On the premise that the user has purchased the traffic package of the destination, a cloud user identity card is allocated to the user. The cloud user identity card is bound to the user device during the use period of the user device to realize the network access service of the user within the corresponding period of the traffic package. When the user successfully settles the bill for the user device, the cloud user identity card is unbound from the user device, so that it can be allocated to other users, realizing the recycling of cloud user identity cards.

[0064] In one embodiment, for a user who rents the user device, a cloud user identity card is allocated to the user based on the device information; for a user who purchases the user device, a cloud user identity card or a seed card is allocated to the user based on the device information.

[0065] In the application, when the user chooses to rent a user device, since the ownership of the user device does not belong to the user, a cloud user identity card is allocated. As a virtual card, the cloud user identity card can be recycled for reuse by different rental devices. Simbank devices contain operator SIM cards from countries and regions around the world, so that no matter where the user is, the user device can be allocated the most suitable cloud SIM card according to the traffic package purchased by the user, and enjoy convenient network services, thereby providing a basis for cross-border payment for users who will rent across borders. The seed card is a physical user identity card built into the user device. For users who purchase user devices, a cloud user identity card or a seed card can be used as an account for subsequent payment. When the cloud user identity card is insufficient, the seed card built into the user device can be used as an account for subsequent payment. The seed card can be assigned to a user device, and can also be assigned to different user devices at different times.

[0066] In one embodiment, Figure 5 As shown, step S103 includes the following steps S1031 and S1033:

[0067] Step S1031: Apply for registration of the target user account by using the cloud user identity card as the account number of the target user account.

[0068] Step S1032: Based on the registration application, a sub-account pre-created under the target enterprise payment account is allocated to the user and used as the target user account, wherein the target enterprise payment account is an enterprise-level account pre-created at the target location.

[0069] In the application, after the registration application is approved, a sub-account in the "free" state is selected from the pre-created multiple sub-accounts and allocated to the user. The sub-account is the target user account obtained by the user's registration application, and the account number of the target user account is the cloud user identity card in step S1031. The corresponding sub-account status mark is changed from "free" to "occupied", so that it cannot be allocated to other users before the target user account is recovered.

[0070] Step S1033, binding and storing the user's target user account with the pre-charged amount, the target traffic package, the identity information, the device information and the cloud user identity card.

[0071] In the application, after the target user account is bound and stored with the user's pre-charged amount, target traffic package, identity information, device information and cloud user identity card, the user's consumption in the target destination can be paid directly from the target user account, thereby realizing the user's cross-border payment.

[0072] In one embodiment, Figure 6 As shown, after step S1031, the following steps S131 and S132 are also included:

[0073] Step S131, based on the user balance of the enterprise payment account at the originating place, recharge the corresponding amount to the user account at the destination place through the enterprise payment account at the destination place.

[0074] In the application, after the target user account is allocated, the target user account is recharged by transferring money from the target enterprise payment account to the sub-account based on the user balance of the originating enterprise payment account.

[0075] Step S132, freezing the user balance of the enterprise payment account at the originating place;

[0076] Among them, the user balance in the enterprise payment account at the starting place is the remaining amount after using the pre-charge amount to purchase traffic (or purchase other goods or services provided by the system).

[0077] In the application, when the user's balance is recharged into the target user's account, the user's balance in the originating company's payment account is frozen. Usually, the originating operation management system sets the funds availability status in the associated stored user-related information to, for example, "funds unavailable". When the user's bill settlement operation is successful, if there is a balance in the target user's account, the remaining funds will be returned to the originating company's payment account. Usually, the originating operation management system resets the user's status to, for example, "funds available", and notifies the originating company's payment account to deduct the amount that has been consumed by the user in the target location, and the remaining funds are returned to the bank account used by the user for recharging.

[0078] In one embodiment, Figure 7 As shown, step S131 includes the following steps S1311 and S1312:

[0079] Step S1311, obtaining the user balance in the enterprise payment account at the originating place through the originating place operation and management system of the service device, and transmitting it to the destination place operation and management system of the service device.

[0080] In the application, since data cannot be directly exchanged between the enterprise payment account at the origin and the enterprise payment account at the destination, the enterprise payment account at the destination itself cannot obtain the user balance in the enterprise payment account at the origin. In the embodiment of the present application, through the interaction between the operation management system at the origin and the enterprise payment account at the origin, when the enterprise payment account at the origin deposits or deducts funds, the fund deposit or deduction information can also be obtained and stored by the operation management system at the origin of the service device, so that the operation management system at the origin can obtain the user balance in the enterprise payment account at the origin. The operation management system at the origin transmits the user balance information to the operation management system at the destination, and the recharge of the user account at the destination can be realized through the interaction between the operation management system at the destination and the enterprise payment account at the destination or the user account at the destination.

[0081] Step S1312: The target location operation management system recharges the target location user account with an amount corresponding to the user balance through the target location enterprise payment account.

[0082] In the application, the operator of this system pre-deposit a certain amount of funds in the target location corporate payment account based on the overall operation situation for all its users to consume at the target location. When the user arrives at the target location, the target location corporate payment account transfers the same amount of funds as the balance in the starting location corporate payment account to the target location user account applied for by the user.

[0083] In the application, when the target destination supports consumption in the currency pre-charged by the user, the amount in the user account of the target destination can be the user balance in the same currency. For example, if the user balance of the enterprise payment account in the originating destination is 1,000 US dollars, the amount in the user account of the target destination is still 1,000 US dollars. When the target destination does not support consumption in the currency pre-charged by the user, the user balance must be converted into the currency of the target destination, and the converted target amount must be used as the recharge amount in the user account of the target destination. Using the obtained exchange rate, the service device converts the user's pre-charged amount into the target currency. In addition, after the calculation is completed, the service device can also inform the user of the converted amount and exchange rate details through SMS, in-app notification or email, so that the user can clearly understand his actual available amount at the target destination.

[0084] In one embodiment, after step S104, the following steps are included:

[0085] Based on the user's settlement operation on the user device, a settlement process is executed.

[0086] In one embodiment, the billing process includes:

[0087] Cancel the target user account;

[0088] The balance of the target user account is returned to the user.

[0089] In the application, the balance of the user account at the destination is returned to the user after the user makes a settlement operation (usually the user returns to the starting place, returns the rental equipment, and settles the bill on the software system). The balance of the user account at the destination is obtained through the target operation management system of the service equipment, and the value is transmitted to the starting place operation management system; the starting place operation management system changes the "funds unavailable" status of the user to the "funds available" status, and notifies the starting place enterprise payment account to return the corresponding remaining amount in the target user account to the bank card originally used for the user to recharge. During this period, if currency conversion is required, the currency calculation is performed according to the legal effective exchange rate obtained in real time by the operation management system. It can also be performed in other ways specified by the user to ensure that the funds are safely returned to the user.

[0090] In one embodiment, canceling the target user account includes reclaiming the cloud user identity card used by the user device and reclaiming the target user account.

[0091] In the application, recycling the cloud SIM card of the user's device means that the user's terminal device deletes the corresponding cloud SIM card information to ensure that the user's device can no longer use the cloud SIM card to access the mobile network. At the same time, the cloud user identity card will be automatically recycled by the service device when the bill is settled, which means that the virtual card will no longer be associated with the user's user device. The cloud SIM card status is reset to "idle", which also means that the binding relationship between the cloud SIM card and the user's device is released, thereby ensuring the safe retirement of the card information and avoiding the subsequent potential risk of misuse or abuse. The system resources occupied by the cloud user identity card are released so that they can be reallocated to other users, improving the recycling rate of resources.

[0092] In one embodiment, returning the balance of the target user account to the user includes:

[0093] Obtaining the balance of the user account at the destination through the destination operation and management system of the service device, and transmitting the balance to the origin operation and management system of the service device;

[0094] The origin operation management system sends a refund instruction to the origin enterprise payment account, and the origin enterprise payment account is used to refund the balance to the user based on the refund instruction.

[0095] In the application, the target user account is recovered after the balance of the target user account is transmitted to the origin operation management system through the target operation management system, the balance of the enterprise sub-account occupied by the target user account is cleared, the binding relationship between the sub-account and the user device is released, the password of the sub-account is reset, and the target enterprise payment account recovers the sub-account as a reusable enterprise sub-account.

[0096] In one embodiment, Figure 8 As shown, a cross-border payment method further includes the following steps S201 to S203:

[0097] Step S201: Acquire device information, location information and requested service type of the user equipment.

[0098] Step S202, allocating the cloud user identity card to the user device based on the device information, location information and the service type, and the user device is used to access the local mobile network based on the allocated cloud user identity card and establish a communication connection with the service device.

[0099] In the application, the service device can store the user identity information of the service to be shared through the user identity information database, select the appropriate user identity information (i.e., cloud user identity card) from the user identity information database and assign it to the user according to the location of the user device and the type of service requested, and communicate with the corresponding operator service provider system through the cloud user identity card to obtain the service requested by the user. The service device selects the appropriate SIM card from the physical SIM card inserted in the SIM card reader (SIMbank) according to the location of the user terminal and the type of service requested, and can consider the user's network environment, user attributes, etc., and assign it to the user device in the form of a cloud SIM card, so that the user can enjoy cross-border, cross-network (operator service provider), cross-technology standard, and cross-business network access services, and realize the sharing of services owned by personal or group SIMs.

[0100] Step S203: Based on the billing operation of the user, a cloud user identity card recovery instruction is sent to the user device, and the user device is used to disconnect the local mobile network connection and delete the cloud user identity card information based on the cloud user identity card recovery instruction.

[0101] In the application, the service device can respond to the user's billing operation and send a cloud user identity card recovery instruction to the user device. After receiving the cloud user identity card recovery instruction, the user device disconnects from the local mobile network and deletes the cloud user identity card information. In this way, the user device can use the newly allocated cloud user identity card to access the local mobile network when it is rented by another user.

[0102] In one embodiment, the user device supports digital payments.

[0103] In applications, the digital payment system can adopt the UnionPay Cloud QuickPass system. In some applications, for example, the target enterprise payment account is UnionPay's Cloud QuickPass account A, and multiple sub-accounts can be opened under Cloud QuickPass account A, such as A.1, A.2, ..., AN (the value of N is determined according to the system operation needs and the bank's negotiation) as accounts for temporary use by users of this system at the target location. A sub-account is a virtual account, which is an empty account when it is not allocated to a user. Enterprises can deposit a certain amount of funds into the target enterprise payment account in advance, and allocate a certain amount of funds to the sub-account for use when the sub-account needs it. When the sub-account is recovered, the balance of the sub-account will be aggregated to the target enterprise payment account.

[0104] The UnionPay Cloud QuickPass client APP can be pre-installed on the user's device. When the user brings the user's device to the destination, the user's device is successfully assigned a cloud SIM card according to the purchased traffic package of the destination. After accessing the mobile network of the destination, for example, the system assigns the user's device a cloud SIM card of the destination with the card number: 138********. When the user opens the Cloud QuickPass client payment APP pre-installed on the "desktop" of the user's device for the first time, he must first complete the application for the user's UnionPay Cloud QuickPass account. The Cloud QuickPass client can automatically obtain the card number 138******** of the cloud SIM of the user's device (in actual application, the user can also manually enter the SIM card number), and use the cloud SIM card number as the user account to register and apply for the "free" sub-account under the target enterprise payment account of this system. According to certain sub-account allocation rules, the UnionPay backend selects the A.4 sub-account that is currently in the "free" state and allocates it to the user. After completing the SMS verification and password setting of the user account registration process of the UnionPay system, the status of the sub-account A.4 is updated to the "occupied" state, and the A.4 sub-account is the user account of the user's destination.

[0105] After the target user account application is successfully registered, the user device APP obtains a UnionPay Cloud QuickPass virtual card (or digital bank card). At the same time, after the target operation management system (i.e., the target BOSS system) obtains the balance of the user's recharge amount at the starting point, the amount is passed to the target corporate payment account at the UnionPay backend through the target BOSS system. The corporate payment account transfers the amount of funds (the currency of the funds can be calculated as the target currency according to the user's needs) to the target user account for the user to consume at the target.

[0106] When the user consumes at a merchant in the target location, he opens the UnionPay QuickPass APP on his device and shows his digital bank card to the merchant. The merchant scans the code with the corresponding UnionPay QuickPass payment terminal, and the user enters the password set when applying for the account registration, and the payment can be made conveniently and quickly. After the payment is completed, the funds in the target user account (that is, one of the sub-accounts A.4 it occupies) are the balance after this consumption. When the user's device is pre-installed with the QuickPass client APP, the client applet of the BOSS system of the target location of this system will also be installed. This BOSS system client applet connects the QuickPass client APP with the BOSS system on the service device, and sends the amount of the QuickPass client APP to the BOSS system on the service device synchronously, so that the BOSS system can synchronize the user's consumption bill information in real time.

[0107] When the user needs to settle a bill, such as performing a settlement operation on the user's APP after returning to the user's starting location, the BOSS system at the target location will obtain the balance in the user's account at the target location and transmit it to the BOSS system at the starting location. The BOSS system at the starting location will release the "frozen" status of the user's original account, notify the corporate payment account at the starting location to deduct the user's consumption amount, and return the balance to the user's bank account through the original path. In addition, the BOSS system at the target location needs to notify the corporate payment account at the target location to reclaim the A.4 subaccount used by the user, and the A.4 subaccount will be reset to the "idle" status and the password will be reset for future use. In addition, the user device deletes the cloud SIM card information, and the cloud SIM card scheduler on the service device reclaims the cloud SIM card used by the user device, and releases the association between the user and the user device, cloud SIM card, and subaccount.

[0108] In one embodiment, the user device is a portable broadband wireless device (MiFi device), so that the MiFi device can access the local mobile network based on the assigned cloud user identity card and establish a communication connection with the service device.

[0109] Embodiment 2

[0110] like Fig. 9 As shown, the embodiment of the present application further provides a terminal device 200, including: at least one processor 201 ( Fig. 9 Only one processor is shown in the figure), a memory 202, and a computer program 203 stored in the memory 202 and executable on at least one processor 201. When the processor 201 executes the computer program 203, the steps of the cross-border payment method in the first embodiment are implemented.

[0111] In the application, the terminal device may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that Fig. 9It is only an example of a terminal device and does not constitute a limitation on the terminal device. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0112] In applications, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0113] In the application, the memory may be an internal storage unit of the terminal device in some embodiments, such as a hard disk or memory of the terminal device. In other embodiments, the memory may also be an external storage device of the terminal device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device. Furthermore, the memory may include both an internal storage unit of the terminal device and an external storage device. The memory is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as program code of a computer program. The memory may also be used to temporarily store data that has been output or is to be output.

[0114] Embodiment 3

[0115] The embodiment of the present application also provides a cross-border payment system, including the above-mentioned service device 10 and user device 20, wherein the service device 10 is used to execute the steps of the cross-border payment method in embodiment one.

[0116] In the application, the service device 10 and the user device 20 are the same as those in the first embodiment and will not be described again here.

[0117] like Fig.10As shown, a user device of a cross-border payment system may be a mobile phone, a personal digital assistant (PDA), a self-service terminal, a wearable device, a tablet computer, a laptop computer, a personal computer (PC), a netbook, a portable broadband wireless router (MiFi device), etc. The embodiment of the present application takes the user APP installed on the MiFi device as an example (not limited to this).

[0118] In the application, the application software in the user device 20 includes three APP applications, including a user APP, a payment APP (such as the UnionPay Cloud QuickPass client APP), and a client BOSS applet of the target BOSS system, and the corresponding functions are described in the above steps. In some instances, these three APP applications can also be integrated into one APP as three software modules, which should not be limited here.

[0119] The detailed process of the cross-border payment method executed by the cross-border payment system of the embodiment of the present application is as follows:

[0120] S301, based on the user's registration operation, obtaining the user's registered identity information.

[0121] S302: Based on the binding operation of the user on the user device, the device information is obtained, and the user's identity information is bound to the device information and stored.

[0122] S303, based on the user's pre-charge operation, pre-charge the enterprise payment account at the originating location to obtain the pre-charge amount.

[0123] S304: Based on the user's operation of purchasing traffic using the pre-charged amount, a target traffic package of the user device is obtained.

[0124] S305: Bind and store the user's pre-charge amount, the target traffic package, the identity information, and the device information.

[0125] S306: Based on the first startup operation of the user device at the target location by the user, allocate the cloud user identity card to the user device according to the traffic package of the target location.

[0126] S307: Bind the cloud user identity card to the user device during use of the user device at the target location.

[0127] S308: Allocate a pre-created sub-account under the target enterprise payment account to the user based on the cloud user identity card and use it as the target user account.

[0128] S309, obtaining the user balance in the enterprise payment account at the originating place through the operation and management system at the originating place of the service device, and transmitting the balance to the operation and management system at the destination place of the service device.

[0129] S310, the target location operation management system recharges the target location user account with an amount corresponding to the user balance through the target location enterprise payment account.

[0130] S311, freezing the user balance of the enterprise payment account at the originating location.

[0131] S312: Based on the user's payment operation, deduct the corresponding consumption amount from the target user account.

[0132] S313: Execute a settlement process based on the settlement operation of the user device.

[0133] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0134] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0135] An embodiment of the present application also provides a network device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on at least one processor, and when the processor executes the computer program, the steps of the cross-border payment method in the above-mentioned embodiment 1 or embodiment 2 are implemented.

[0136] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the cross-border payment method in the above-mentioned embodiment 1 or embodiment 2 are implemented.

[0137] An embodiment of the present application provides a computer program product. When the computer program product runs on a terminal device, the terminal device implements the steps of the cross-border payment method in the above-mentioned embodiment 1 or embodiment 2 when executing the computer program product.

[0138] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0139] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0140] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0141] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0142] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0143] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A cross-border payment method, characterized in that: Applied to a service device, the method comprises: Get device information of user device; allocating a cloud user identity card to the user device based on the device information; Allocating a target user account based on the cloud user identity card; Based on the user's payment operation, the corresponding consumption amount is deducted from the target user account; The allocating a target user account based on the cloud user identity card includes: Using the cloud user identity card as the account number of the target user account to apply for registration of the target user account; Based on the registration application, a pre-created sub-account under the target enterprise payment account is allocated to the user and used as the target user account; The target enterprise payment account is an enterprise-level account pre-created at the target location.

2. The cross-border payment method according to claim 1, characterized in that: The obtaining of device information of the user device includes: Based on the user's registration operation, obtain the user's registered identity information; Based on the binding operation of the user on the user device, the device information is obtained, and the user's identity information is bound to the device information and stored.

3. The cross-border payment method according to claim 2, characterized in that: After the identity information of the user is bound to the device information and stored, the method includes: Based on the user's pre-charge operation, pre-charge the enterprise payment account at the origin to obtain the pre-charge amount; Based on the user's operation of purchasing traffic using the pre-charged amount, a target traffic package for the user's device is obtained; Binding and storing the user's pre-charged amount, the target destination traffic package, the identity information and the device information; The starting place enterprise payment account is an enterprise-level account pre-created at the starting place.

4. The cross-border payment method according to claim 3, characterized in that: The allocating a cloud user identity card to the user device based on the device information includes: Based on the first startup operation of the user device by the user at the target location, allocating the cloud user identity card to the user device according to the traffic package of the target location; During use of the user device at the target location, the cloud user identity card is bound to the user device.

5. The cross-border payment method according to claim 3, characterized in that: The allocating a target user account based on the cloud user identity card also includes: The target user account of the user is bound and stored with the pre-charged amount, the target traffic package, the identity information, the device information and the cloud user identity card.

6. The cross-border payment method according to claim 5, characterized in that: After allocating the target user account based on the cloud user identity card, the method further includes: Based on the user balance of the enterprise payment account at the originating location, a corresponding amount is recharged to the user account at the destination location through the enterprise payment account at the destination location.

7. The cross-border payment method according to claim 6, characterized in that: The recharging of the corresponding amount to the user account at the destination through the corporate payment account at the destination based on the user balance of the corporate payment account at the originating location includes: Obtaining the user balance in the enterprise payment account at the origin through the operation management system at the origin of the service device, and transmitting it to the operation management system at the destination of the service device; The target location operation management system recharges the target location user account with an amount corresponding to the user balance through the target location enterprise payment account.

8. The cross-border payment method according to claim 1, characterized in that: After the corresponding consumption amount is deducted from the target user account, the method includes: Based on the user's settlement operation on the user device, a settlement process is executed.

9. The cross-border payment method according to claim 8, characterized in that: The billing process includes: Cancel the target user account; The balance of the target user account is returned to the user.

10. The cross-border payment method according to claim 9, characterized in that: The canceling of the target user account includes: Reclaiming the cloud user identity card; The target user account is recovered.

11. The cross-border payment method according to claim 9, characterized in that: The returning the balance of the target user account to the user includes: Obtaining the balance of the user account at the destination through the destination operation and management system of the service device, and transmitting the balance to the origin operation and management system of the service device; The origin operation management system sends a refund instruction to the origin enterprise payment account, and the origin enterprise payment account is used to refund the balance to the user based on the refund instruction.

12. The cross-border payment method according to claim 1, characterized in that: The method further comprises: Obtaining device information, location information, and requested service type of the user device; Allocating the cloud user identity card to the user device based on the device information, location information and the service type, and the user device is used to access the local mobile network based on the allocated cloud user identity card and establish a communication connection with the service device; Based on the user's settlement operation, a cloud user identity card recovery instruction is sent to the user device, and the user device is used to disconnect the local mobile network connection and delete the cloud user identity card information based on the cloud user identity card recovery instruction.

13. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 12 are implemented.

14. A cross-border payment system, characterized by: The method comprises a service device and a user device, wherein the service device is used to execute the steps of the method according to any one of claims 1 to 12.

15. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

Images