Virtual card updating method, device, system, equipment, medium and program product

Abstract

This application discloses a method, apparatus, system, device, medium, and program product for updating a virtual card. The method includes: if update conditions for the virtual card are met, acquiring target personalized data corresponding to the update conditions; the virtual card is used to implement multiple functions across scenarios; generating an update trigger notification to trigger a user terminal to initiate a first data acquisition request for the target personalized data; sending the update trigger notification to a trusted service management platform to send the update trigger notification to the user terminal; receiving the first data acquisition request sent by the trusted service management platform; responding to the first data acquisition request, sending the target personalized data to the trusted service management platform so that the user terminal can acquire the target personalized data; and updating the virtual card based on the target personalized data. According to the embodiments of this application, the flexibility and scalability of virtual cards in cross-scenario applications can be enhanced, and the reliability of multifunctional virtual cards can be improved.

Description

Technical Field

[0001] This application belongs to the field of virtual card technology, and in particular relates to a method, apparatus, system, device, medium and program product for updating a virtual card. Background Technology

[0002] With the development of Integrated Circuit Card (IC card) technology and its integration with user terminals, it is now possible to bind different physical IC cards, such as bank cards, campus cards, and access control cards, to mobile payment applications such as MobilePay to obtain virtual cards corresponding to the physical IC cards. Furthermore, based on different virtual cards, functions such as contactless payment and contactless identity authentication can be implemented in different scenarios.

[0003] In different scenarios, business verification typically requires reading specific personalized fields (such as student status, access control permissions, etc.) to execute the corresponding logic and implement the Near Field Communication (NFC) function. However, the traditional IC card data architecture, due to its fixed fields, struggles to dynamically adapt to the permission judgment logic of different scenarios. Once personalized and bound to the user terminal, its data fields are difficult to change, resulting in the bound virtual card being unable to flexibly adapt to the dynamic business rules of various scenarios. Furthermore, traditional physical IC cards (such as bank cards) typically have a validity period of around ten years, while the validity period of virtual cards depends on the validity period of the physical IC card. After the card expires, the virtual card becomes invalid along with the physical IC card. Even if the physical chip is intact, the payment function will still fail, creating an awkward situation of "having a card but not being able to use it," leading to payment interruptions and impacting the user experience of the virtual card.

[0004] To address the aforementioned dual pain points, there is an urgent need for a virtual card processing method that can overcome the validity period limitations of physical cards and support cross-scenario applications, thereby improving the reliability and flexible scalability of virtual cards. Summary of the Invention

[0005] This application provides a method, apparatus, system, electronic device, computer-readable storage medium, and computer program product for updating virtual cards, which can enhance the flexibility and scalability of virtual cards in cross-scenario applications and improve the reliability of multifunctional virtual cards.

[0006] In a first aspect, embodiments of this application provide a method for updating a virtual card, applied to a virtual card issuer, the method comprising: Under the condition that the virtual card is updated, the target personalized data corresponding to the update condition is obtained, and the virtual card is used to realize multiple functions across scenarios; Based on the target personalized data, an update trigger notification is generated, which is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data; Send the update trigger notification to the trusted service management platform, so that the trusted service management platform sends the update trigger notification to the user terminal via the device management service platform of the user terminal; Receive the first data acquisition request sent by the trusted service management platform; In response to the first data acquisition request, the target personalized data is sent to the trusted service management platform so that the user terminal can acquire the target personalized data and update the virtual card based on the target personalized data.

[0007] Secondly, embodiments of this application provide a method for updating a virtual card, applied to a user terminal, the method comprising: The system receives an update trigger notification sent by the trusted service management platform via the device management service platform of the user terminal. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios. In response to the update trigger notification, a first data acquisition request is generated; The device management service platform sends the first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; Receive the target personalized data sent by the trusted service management platform via the device management service platform; The virtual card is updated based on the target personalized data.

[0008] Thirdly, embodiments of this application provide a method for updating a virtual card, applied to a trusted service management platform, the method comprising: The system receives an update trigger notification from the virtual card issuer. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios. The update trigger notification is sent to the user terminal via the device management service platform of the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request; Receive the first data acquisition request sent by the user terminal via the device management service platform; Send the first data acquisition request to the virtual card issuer; Receive the target personalized data returned by the virtual card issuer in response to the first data acquisition request; The target personalized data is sent to the user terminal via the device management service platform, so that the user terminal updates the virtual card based on the target personalized data.

[0009] Fourthly, embodiments of this application provide a method for updating a virtual card, applied to a device management service platform, the method comprising: The system receives an update trigger notification sent by the Trusted Service Management Platform. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the Trusted Service Management Platform when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios. Send the update trigger notification to the user terminal so that the user terminal responds to the update trigger notification and generates a first data acquisition request; Receive the first data acquisition request sent by the user terminal; Send the first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; Receive the target personalized data sent by the trusted service management platform; The target personalized data is sent to the user terminal so that the user terminal updates the virtual card based on the target personalized data.

[0010] Fifthly, embodiments of this application provide a virtual card update apparatus, applied to a virtual card issuer, the apparatus comprising: The acquisition module is used to acquire target personalized data corresponding to the update conditions when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The first generation module is used to generate an update trigger notification based on the target personalized data. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The first sending module is used to send the update trigger notification to the trusted service management platform, so that the trusted service management platform sends the update trigger notification to the user terminal via the device management service platform of the user terminal. The first receiving module is used to receive the first data acquisition request sent by the trusted service management platform; The first sending module is further configured to, in response to the first data acquisition request, send the target personalized data to the trusted service management platform, so that the user terminal can acquire the target personalized data and update the virtual card based on the target personalized data.

[0011] Sixthly, embodiments of this application provide a virtual card update apparatus, applied to a user terminal, the apparatus comprising: The second receiving module is used to receive an update trigger notification sent by the trusted service management platform through the device management service platform of the user terminal. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The second generation module is used to generate a first data acquisition request in response to the update trigger notification; The second sending module is used to send the first data acquisition request to the trusted service management platform via the device management service platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data. The second receiving module is further configured to receive the target personalized data sent by the trusted service management platform via the device management service platform; An update module is used to update the virtual card based on the target personalized data.

[0012] Seventhly, embodiments of this application provide a virtual card update apparatus applied to a trusted service management platform, the apparatus comprising: The third receiving module is used to receive an update trigger notification sent by the virtual card issuer. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The target personalized data is generated when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The third sending module is used to send the update trigger notification to the user terminal via the device management service platform of the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request; The third receiving module is further configured to receive the first data acquisition request sent by the user terminal via the device management service platform; The third sending module is also used to send the first data acquisition request to the virtual card issuer; The third receiving module is also used to receive the target personalized data returned by the virtual card issuer in response to the first data acquisition request; The third sending module is further configured to send the target personalized data to the user terminal via the device management service platform, so that the user terminal updates the virtual card based on the target personalized data.

[0013] Eighthly, embodiments of this application provide a virtual card update device applied to a device management service platform, the device comprising: The fourth receiving module is used to receive an update trigger notification sent by the trusted service management platform. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The fourth sending module is used to send the update trigger notification to the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request; The fourth receiving module is further configured to receive the first data acquisition request sent by the user terminal; The fourth sending module is further configured to send the first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; The fourth receiving module is also used to receive the target personalized data sent by the trusted service management platform; The fourth sending module is further configured to send the target personalized data to the user terminal, so that the user terminal updates the virtual card based on the target personalized data.

[0014] Ninthly, embodiments of this application provide a virtual card update system, including: The virtual card update device applied to a virtual card issuer as described in the fifth aspect; The virtual card update device applied to a user terminal as described in the sixth aspect; The virtual card update device applied to the trusted service management platform as described in the seventh aspect; The virtual card update device applied to the device management service platform as described in aspect eight.

[0015] In a tenth aspect, embodiments of this application provide an electronic device, which includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements any one of the possible implementations of the first, second, third, or fourth aspect described above.

[0016] Eleventhly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the method in any one of the possible implementations of the first, second, third, or fourth aspects described above.

[0017] In a twelfth aspect, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform a method as described in any of the possible implementations of the first, second, third, or fourth aspects above.

[0018] In this embodiment, when the update conditions of the virtual card are met, by acquiring the target personalized data corresponding to the update conditions, a first data acquisition request is generated to trigger the user terminal to initiate an update trigger notification for the target personalized data. The user terminal is then sent an update trigger notification via the Trusted Service Management Platform and the Device Management Service Platform, enabling it to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the Device Management Service Platform and the Trusted Service Management Platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the Trusted Service Management Platform, the user terminal can acquire the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continued availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multifunctional virtual cards. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating a method for updating a virtual card applied to a virtual card issuer, provided in one embodiment of this application. Figure 2 This is a flowchart illustrating a method for updating a virtual card applied to a user terminal, according to an embodiment of this application. Figure 3 This is a flowchart illustrating a method for updating a virtual card applied to a trusted service management platform, according to an embodiment of this application. Figure 4 This is a flowchart illustrating a method for updating a virtual card applied to a device management service platform, according to an embodiment of this application. Figure 5 This is a schematic diagram of the structure of a virtual card update device applied to a virtual card issuer according to an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a virtual card update device applied to a user terminal according to an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a virtual card update device applied to a trusted service management platform according to an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a virtual card update device applied to a device management service platform according to an embodiment of this application; Figure 9 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0021] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0022] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0023] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0024] Furthermore, the acquisition, storage, use, and processing of data in this application's technical solution all comply with relevant national laws and regulations.

[0025] With the development of Integrated Circuit Card (IC card) technology and its integration with user terminals, it is now possible to bind different physical IC cards, such as bank cards, campus cards, and access control cards, to mobile payment applications such as MobilePay to obtain virtual cards corresponding to the physical IC cards. Furthermore, based on different virtual cards, functions such as contactless payment and contactless identity authentication can be implemented in different scenarios.

[0026] In different scenarios, business verification typically requires reading specific personalized fields (such as student status, access control permissions, etc.) to execute the corresponding logic and implement the Near Field Communication (NFC) function for that scenario. However, the traditional IC card data architecture, due to its fixed fields, makes it difficult to dynamically adapt to the permission judgment logic of different industries and scenarios. Once personalized and bound to the user terminal, its data fields are difficult to change, resulting in the bound virtual card being unable to flexibly adapt to the dynamic business rules of various scenarios.

[0027] Furthermore, traditional physical IC cards (such as bank cards) typically have a validity period of around ten years, while the validity period of virtual cards depends on the validity period of the physical IC card. When the card expires, the virtual card becomes invalid along with the physical IC card. Even if the physical chip is intact, the payment function will still fail, creating an awkward situation of "having a card but not being able to use it," leading to payment interruptions and impacting the user experience of using the virtual card.

[0028] To address the aforementioned dual pain points, there is an urgent need for a virtual card processing method that can overcome the validity period limitations of physical cards and support cross-scenario applications, thereby improving the reliability and flexible scalability of virtual cards.

[0029] To address the related technical issues, embodiments of this application provide a method, apparatus, system, electronic device, computer-readable storage medium, and computer program product for updating virtual cards. The virtual card updating method can be applied to scenarios involving updating multi-functional virtual cards across various scenarios. These multiple functions can be implemented using NFC technology.

[0030] The virtual card update method can be executed by a virtual card update system. This system may include a virtual card issuer, a Trusted Service Manager (TSM) platform, a device management service platform, and a user terminal. The virtual card issuer can provide personalized data for the virtual card. This personalized data is the core data package used to configure a blank general-purpose security chip into a virtual card with specific identity, permissions, and functions. The Trusted Service Manager can securely and reliably transmit the personalized data provided by the virtual card issuer to the device management service platform. The device management service platform may include a backend server for the user terminal, used to transmit the personalized data to the user terminal at appropriate times. The user terminal can then write the personalized data into the security chip, thus updating the virtual card.

[0031] The following describes the method for updating virtual cards applied to virtual card issuers, as provided in the embodiments of this application.

[0032] Figure 1 This illustration shows a flowchart of a virtual card update method for a virtual card issuer, according to an embodiment of this application. This virtual card update method can be executed by the virtual card issuer. Figure 1 As shown, the virtual card update method provided in this application embodiment includes steps S110-S150.

[0033] S110: If the update conditions of the virtual card are met, generate target personalized data corresponding to the update conditions. The virtual card is used to realize multiple functions across scenarios.

[0034] A virtual card can be obtained by binding at least one physical card to a user's mobile payment application. That is, one virtual card can correspond to one or more physical cards, meaning the virtual card can be a multi-functional virtual card spanning multiple scenarios. The multiple physical cards are all physical IC cards. These physical cards can include bank cards, campus cards, access control cards, transportation cards, etc. Multiple scenarios can include financial payment scenarios, campus management and consumption scenarios, access control scenarios, public transportation scenarios, etc. Multi-functionality can include payment functions, identity authentication functions, etc. The relationship between scenarios and functions can be many-to-many. For example, a campus management and consumption scenario can simultaneously correspond to payment functions and identity authentication functions, and the payment function can correspond to multiple scenarios such as financial payment scenarios, campus management and consumption scenarios, and public transportation scenarios.

[0035] If a virtual card corresponds to multiple physical cards, any one of these physical cards can be selected as the base card, and the issuer of that base card can be designated as the virtual card issuer. If the multiple physical cards include bank cards, the base card is typically a bank card. If the base card is a bank card, the virtual card issuer can be the issuing bank.

[0036] Additionally, the user terminal may include a secure chip for storing personalized data. This secure chip may include a baseline configuration data area and multiple scenario-extended data areas.

[0037] Based on this, in order to obtain a multi-functional virtual card that can be used across different scenarios, meet the diverse needs of users for multiple uses of a single card, and improve the user experience of the virtual card, in some embodiments, before S110, the method may further include: Upon receiving a virtual card activation request for the base card sent by the user terminal via the device management service platform and the trusted service management platform, the first physical card associated with the base card is identified. Obtain the first humanized data corresponding to the baseline card and the second humanized data corresponding to the first physical card respectively; The first and second personalized data are sent to the user terminal through the trusted service management platform and the device management service platform, so that the user terminal writes the first personalized data into the baseline configuration data area and the second personalized data into the scene extension data area to obtain a virtual card.

[0038] Here, before binding the base card to the user terminal, the base card can first be associated with at least one first physical card. This association can be done by either the virtual card issuer or the first physical card issuer; there is no limitation on this. Assuming the first physical card is a campus card, the issuer of the campus card can be the school. Thus, the association between the bank card and the first physical card can be done centrally by the school or independently by the student within the integrated student service system.

[0039] If the association operation is completed by the virtual card issuer, the virtual card issuer can store the association relationship between the base card and at least one physical card after the association. If the association operation is completed by the issuer of the first physical card, the issuer of the first physical card can send the association relationship to the virtual card issuer after the association, and the virtual card issuer stores the association relationship. In this way, when the virtual card issuer receives a virtual card activation request for the base card sent by the user terminal through the device management service platform and the trusted service management platform, it can determine one or more first physical cards associated with the base card based on the association relationship.

[0040] Additionally, the first personalized data can be personalized data generated by the virtual card issuer based on the base card. The second personalized data can be personalized data obtained by the virtual card issuer from the issuer of the first physical card, and generated by the issuer of the first physical card based on the first physical card.

[0041] As an example, a virtual card issuer could send a request to the issuer of the first physical card to obtain the second personalized data of the first physical card after identifying the first physical card.

[0042] As another example, if the association operation is completed by the virtual card issuer, the virtual card issuer can send a request to the issuer of the first physical card to obtain the second personalized data after associating the base card with the first physical card. This request allows the virtual card issuer to retrieve and store the second personalized data of the first physical card, and, if the first physical card is identified, retrieve the second personalized data of the first physical card from its own storage. Alternatively, if the association operation is completed by the issuer of the first physical card, the issuer of the first physical card can simultaneously send the second personalized data when sending the association relationship to the virtual card issuer. This allows the virtual card issuer to store the second personalized data and, if the first physical card is identified, retrieve the second personalized data of the first physical card from its own storage.

[0043] After receiving the first personalized data and at least one second personalized data sent by the virtual card issuer through the trusted service management platform and the device management service platform, the user terminal can write the first personalized data into the base configuration data area and write at least one second personalized data into at least one scenario extension data area, thereby obtaining a virtual card that corresponds to the base card and at least one first physical card.

[0044] Based on this, assuming the base card is a bank card, at least one primary physical card can include a campus card, access control card, transportation card, etc. Assuming the primary physical card is an access control card, the aforementioned virtual card can simultaneously possess payment functionality in financial scenarios and identity authentication functionality in access control scenarios.

[0045] Furthermore, if there are multiple scenarios in the extended data area and multiple second-personalized data points, then for each second-personalized data point, when the user terminal writes the second-personalized data into the extended data area, it can also simultaneously mark the scenario identifier corresponding to the second-personalized data (i.e., the scenario identifier corresponding to the first physical card) as the scenario identifier for that extended data area. The scenario identifier can be a unique identifier for scenarios such as campus management and consumption, access control, and public transportation.

[0046] This application embodiment, upon receiving a virtual card activation request for a base card from a user terminal, determines the first physical card associated with the base card, acquires the first personalized data corresponding to the base card and the second personalized data corresponding to the first physical card, and provides the first and second personalized data to the user terminal. This enables the user terminal to write the first personalized data into the base configuration data area of ​​the security chip and the second personalized data into the scenario extension data area of ​​the security chip, thereby obtaining a multi-functional virtual card that can be used across scenarios, meeting the diverse needs of users for multiple uses of a single card, and improving the user experience of the virtual card.

[0047] In addition, meeting the update conditions for a virtual card may include at least one of the following: The virtual card's validity period has been detected and it has reached the renewal requirements. Received a scene attribute data change request from the issuer of the first physical card; The system receives a request from the issuer of the second physical card to add personalized data. The second physical card is a physical card associated with the base card after the base card is bound to the user terminal and a virtual card is obtained.

[0048] Here, the personalized data corresponding to the base card typically has an expiration date. After a virtual card is generated, its initial expiration date can be the expiration date of the corresponding base card (such as a 10-year validity period for a bank card). Subsequent updates to the virtual card's expiration date can be set by the virtual card issuer or a trusted service management platform, representing an expiration date that is unbound from the physical base card. That is, even if the base card expires, the virtual card can still be used by updating its expiration date. Furthermore, the virtual card issuer can simultaneously update the expiration date of the base card when updating the virtual card's expiration date.

[0049] As an example, if the virtual card issuer detects that the virtual card's validity period is about to expire (e.g., one day remaining), or if the trusted service management platform detects that the virtual card's validity period is about to expire and notifies the virtual card issuer, the virtual card issuer can determine that the virtual card's validity period meets the renewal conditions and thus obtain the target personalized data after the validity period update. The target personalized data can be complete personalized data or partial personalized data related to the validity period (i.e., the personalized data corresponding to the base card); this is not limited here.

[0050] Additionally, scenario attribute data can be attribute data related to the application scenario from the personalized data. For example, for a campus card, the personalized data corresponding to the campus card may include information such as student status and dormitory building. If a student changes their dormitory building from Building 1 to Building 2 during the transition from freshman to sophomore year, then the attribute data related to the dormitory building in the campus management and consumption scenario (i.e., scenario attribute data) needs to be changed from Building 1 to Building 2.

[0051] As an example, if the issuer of the first physical card is a school, then at the start of the school year, the school can send a scenario attribute data change request to the virtual card issuer to request the virtual card issuer to update the scenario attribute data corresponding to the first physical card, thereby obtaining the target personalized data. The scenario attribute data change request should include which scenario attribute data to change and how to change it. Furthermore, the target personalized data can be the updated complete personalized data or only partially updated personalized data, such as the updated personalized data corresponding to the first physical card; this is not limited here.

[0052] In addition, the personalized data addition request may include personalized data corresponding to the second physical card. Taking a bank card as the base card as an example, after the bank card has been bound to the user's terminal and the corresponding virtual card has been obtained, if the issuing bank or the issuer of the second physical card has associated the second physical card with the base card, and the issuing bank has received a personalized data addition request sent by the issuer of the second physical card, then the issuing bank may determine the personalized data corresponding to the second physical card as the target personalized data, or may determine the personalized data corresponding to the second physical card and the personalized data corresponding to the virtual card together as the target personalized data, without limitation here.

[0053] Furthermore, it should be noted that this application embodiment, by establishing an industry-standard interface, can integrate multiple scenarios such as payment, access control, campus, and transportation, and ensures that the personalized data corresponding to the base card and the personalized data corresponding to the multiple physical cards associated with the base card do not interfere with each other in the complete personalized data. Therefore, in order to improve data transmission efficiency and subsequent virtual card update efficiency, the target personalized data in this application embodiment can be only updated part of the corresponding personalized data, such as the updated third personalized data corresponding to the base card, the updated fourth personalized data corresponding to the first physical card, and the fifth personalized data corresponding to the newly added second physical card.

[0054] S120: Based on the target personalized data, an update trigger notification is generated. This notification triggers the user terminal to initiate a first data acquisition request for the target personalized data. This first data acquisition request can also be referred to as a re-personalization request.

[0055] Once the virtual card issuer obtains the target personalized data, it can generate an update trigger notification based on that data.

[0056] S130, send an update trigger notification to the trusted service management platform, so that the trusted service management platform sends the update trigger notification to the user terminal through the device management service platform of the user terminal.

[0057] The virtual card issuer can send the update trigger notification to the user terminal via the trusted service management platform and the device management service platform. Upon receiving the update trigger notification, the user terminal can respond by generating a first data acquisition request to obtain the target personalized data, and sending the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform.

[0058] S140, Receive the first data acquisition request sent by the Trusted Service Management Platform.

[0059] The virtual card issuer can receive the first data acquisition request sent by the user terminal through the device management service platform and the trusted service management platform.

[0060] S150, in response to the first data acquisition request, sends the target personalized data to the trusted service management platform so that the user terminal can acquire the target personalized data and update the virtual card based on the target personalized data.

[0061] Upon receiving the first data acquisition request, the virtual card issuer can respond to the request by returning the target personalized data to the user terminal through the trusted service management platform and the device management service platform.

[0062] After receiving the target personalized data, the user terminal can first parse the data to obtain at least one of the following: updated third personalized data corresponding to the base card, updated fourth personalized data corresponding to the first physical card, and fifth personalized data corresponding to the newly added second physical card. The parsed personalized data is then written into its corresponding target data area, thereby updating the virtual card. The target data area can be at least one of a base configuration data area and a scenario extension data area. Furthermore, there can be multiple scenario extension data areas, including a first scenario extension data area that already stores personalized data and an idle second scenario extension data area.

[0063] As a first example, if the update condition for the virtual card is that its validity period has reached the renewal condition, then the target personalized data can be the aforementioned third personalized data. Therefore, the user terminal can obtain the third personalized data by parsing the target personalized data, and replace the personalized data already stored in the baseline configuration data area with the third personalized data, thereby updating the validity period of the virtual card.

[0064] As a second example, if the update condition for the virtual card is receiving a scene attribute data change request from the issuer of the first physical card, then the target personalized data can be the aforementioned fourth personalized data. Therefore, the user terminal can obtain the fourth personalized data by parsing the target personalized data, and replace the personalized data already stored in the first scene extended data area with the fourth personalized data, thereby updating the functionality of the virtual card in the scene corresponding to the first physical card.

[0065] As a more specific example, there can be multiple first scene extended data areas, each corresponding to a scene identifier. Based on this, after parsing the target personalized data to obtain the fourth personalized data, the target scene extended data area corresponding to the fourth personalized data can be determined from among the multiple first scene extended data areas based on the scene identifier corresponding to the fourth personalized data, and the personalized data already stored in the target scene extended data area can be replaced with the fourth personalized data.

[0066] As a third example, if the update condition for the virtual card is that the virtual card receives a personalized data addition request from the issuer of the second physical card, then the target personalized data can be the aforementioned fifth personalized data. Therefore, the user terminal can obtain the fifth personalized data by parsing the target personalized data and write it into the second scenario extended data area, thereby updating the virtual card's function in the scenario corresponding to the second physical card. If there are multiple second scenario extended data areas, the fifth personalized data can be written into any one of them. Furthermore, to facilitate subsequent data updates, when writing the fifth personalized data into the second scenario extended data area, the scenario identifier corresponding to the fifth personalized data (i.e., the scenario identifier corresponding to the second physical card) is marked as the scenario identifier of that second scenario extended data area.

[0067] In this embodiment, when the update conditions of the virtual card are met, by acquiring the target personalized data corresponding to the update conditions, a first data acquisition request is generated to trigger the user terminal to initiate an update trigger notification for the target personalized data. The user terminal is then sent an update trigger notification via the Trusted Service Management Platform and the Device Management Service Platform, enabling it to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the Device Management Service Platform and the Trusted Service Management Platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the Trusted Service Management Platform, the user terminal can acquire the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continued availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multifunctional virtual cards.

[0068] The following describes the method for updating a virtual card applied to a user terminal, as provided in the embodiments of this application.

[0069] Figure 2 This illustration shows a flowchart of a virtual card update method applied to a user terminal according to an embodiment of this application. This virtual card update method can be executed by the user terminal. Figure 2 As shown, the virtual card update method provided in this application embodiment includes steps S210-S250.

[0070] S210, receive an update trigger notification sent by the trusted service management platform through the device management service platform of the user terminal. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios.

[0071] S220, in response to the update trigger notification, generates the first data retrieval request.

[0072] S230, the device management service platform sends a first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data.

[0073] S240 receives target personalized data sent by the trusted service management platform via the device management service platform.

[0074] S250 updates the virtual card based on the target's personalized data.

[0075] The steps of the method in this embodiment can be found above. Figure 1 The relevant descriptions of the embodiments shown will not be repeated here.

[0076] In this embodiment, when the virtual card update conditions are met, the virtual card issuer obtains the target personalized data corresponding to the update conditions, generates a first data acquisition request to trigger the user terminal to initiate an update trigger notification for the target personalized data, and sends an update trigger notification to the user terminal via the trusted service management platform and the device management service platform. This enables the user terminal to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the trusted service management platform, the user terminal can obtain the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continuous availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multi-functional virtual cards.

[0077] Based on this, in order to obtain a multi-functional virtual card that can be used across different scenarios, meet the diverse needs of users for multiple uses of a single card, and improve the user experience of the virtual card, in some embodiments, before S210, the method may further include: Receive the first input from the user for the virtual card used to activate the base card; In response to the first input, a virtual card activation request for the base card is generated; The virtual card activation request is sent to the virtual card issuer through the device management service platform and the trusted service management platform, so that the virtual card issuer can identify the first physical card associated with the base card, obtain the first humanized data corresponding to the base card and the second humanized data corresponding to the first physical card, and send the first humanized data and the second humanized data to the user terminal. Receive the first and second personalized data sent by the virtual card issuer through the trusted service management platform and the device management service platform; Write the first humanized data into the baseline configuration data area and the second humanized data into the scene extension data area to obtain the virtual card.

[0078] Here, a virtual card can correspond to multiple physical cards. The issuer of the virtual card is the issuer of the base card, and the base card is any one of the multiple physical cards. Additionally, the user terminal may include a security chip and a mobile payment application. The mobile payment application could be, for example, a mobile payment app like MobilePay. The security chip may include a base configuration data area and a scenario extension data area.

[0079] As an example, a user can open a mobile payment application and follow the prompts to activate a virtual card for the base card on their terminal (i.e., the first input). In response to the user's first input, the terminal can generate a virtual card activation request for the base card and send it to the virtual card issuer via the device management service platform and the trusted service management platform. Upon receiving the activation request, the virtual card issuer can first determine the first physical card associated with the base card based on the relationship between the base card and the physical card, then generate the first personalized data corresponding to the base card, and obtain the second personalized data corresponding to the first physical card. This second personalized data can be personalized data provided by the issuer of the first physical card. Finally, the virtual card issuer sends the first and second personalized data to the terminal via the trusted service management platform and the device management service platform.

[0080] After receiving the first humanized data and at least one second humanized data, the user terminal can write the first humanized data into the baseline configuration data area and write at least one second humanized data into at least one scenario extension data area, thereby obtaining a virtual card that corresponds to both the baseline card and at least one first physical card.

[0081] Based on this, assuming the base card is a bank card, at least one primary physical card can include a campus card, access control card, transportation card, etc. Assuming the primary physical card is an access control card, the aforementioned virtual card can simultaneously possess payment functionality in financial scenarios and identity authentication functionality in access control scenarios.

[0082] Furthermore, if there are multiple scenarios in the extended data area and multiple second-personalized data points, then for each second-personalized data point, when the user terminal writes the second-personalized data into the extended data area, it can also simultaneously mark the scenario identifier corresponding to the second-personalized data (i.e., the scenario identifier corresponding to the first physical card) as the scenario identifier for that extended data area. The scenario identifier can be a unique identifier for scenarios such as campus management and consumption, access control, and public transportation.

[0083] This application embodiment generates a virtual card activation request for the base card upon receiving a user's first input for activating a virtual card for the base card. Using this request, it obtains the first personalized data corresponding to the base card and the second personalized data corresponding to the first physical card from the virtual card issuer. It then writes the first personalized data into the base configuration data area of ​​the security chip and the second personalized data into the scenario extension data area of ​​the security chip. This enables a multi-functional virtual card that can be used across various scenarios, meeting the diverse needs of users for multiple uses with a single card and improving the user experience of the virtual card.

[0084] Based on this, if there are multiple scenario extension data areas, including a first scenario extension data area that already stores personalized data and a second scenario extension data area that is idle, then in order to support the flexible iteration and expansion of scenario functions on demand while ensuring the continuous availability of the core functions of the virtual card, in some embodiments, the above-mentioned S250 may specifically include: Parse the target personalized data to obtain at least one of the following: the updated third personalized data corresponding to the base card, the updated fourth personalized data corresponding to the first physical card, and the newly added fifth personalized data corresponding to the second physical card. The third personalized data includes the validity period, the fourth personalized data includes scene attribute data, and the second physical card is the physical card associated with the base card after binding the base card to the user terminal to obtain the virtual card. Perform at least one of the following operations: Replace the personal data already stored in the baseline configuration data area with the third personal data to update the validity period of the virtual card; Replace the personal data already stored in the first scenario extended data area with the fourth personal data to update the functionality of the virtual card in the corresponding scenario; The fifth personalized data is written into the second scene extended data area to increase the functionality of the virtual card in the corresponding scene.

[0085] Here, after receiving the target personalized data, the user terminal can first parse the target personalized data to obtain at least one of the following: the updated third personalized data corresponding to the base card, the updated fourth personalized data corresponding to the first physical card, and the fifth personalized data corresponding to the newly added second physical card. The parsed personalized data is then written into its corresponding target data area, thereby updating the virtual card. The target data area can be at least one of the base configuration data area and the scene extension data area.

[0086] As a first example, if the update condition for the virtual card is that its validity period has reached the renewal condition, then the target personalized data can be the aforementioned third personalized data. Therefore, the user terminal can obtain the third personalized data by parsing the target personalized data, and replace the personalized data already stored in the baseline configuration data area with the third personalized data, thereby updating the validity period of the virtual card.

[0087] As a second example, if the update condition for the virtual card is receiving a scene attribute data change request from the issuer of the first physical card, then the target personalized data can be the aforementioned fourth personalized data. Therefore, the user terminal can obtain the fourth personalized data by parsing the target personalized data, and replace the personalized data already stored in the first scene extended data area with the fourth personalized data, thereby updating the functionality of the virtual card in the scene corresponding to the first physical card.

[0088] As a more specific example, there can be multiple first scenario extended data areas, each corresponding to a scenario identifier. Based on this, to quickly and accurately update the virtual card, the aforementioned replacement of the stored personalized data in the scenario extended data area with fourth personalized data can specifically include: Based on the scene identifier corresponding to the fourth personalized data, the target scene extended data area corresponding to the fourth personalized data is determined among multiple scene extended data areas; Replace the already stored personalized data in the target scene extended data area with the fourth personalized data.

[0089] This application embodiment achieves accurate identification and independent updating of personalized data for multiple scenarios by setting a scenario identifier for each first scenario extended data area. When it is necessary to update the function of a specific scenario, the corresponding target scenario extended data area can be quickly and accurately located based on the scenario identifier carried by the fourth personalized data, and only the data in that area can be replaced, thereby quickly and accurately updating the virtual card.

[0090] This design ensures that functional data in different scenarios are isolated from each other, avoiding data corruption or mutual interference during the update process. As a result, while supporting the multi-functional expansion of virtual cards, it significantly improves the maintainability, accuracy and operational efficiency of scenario-based function management.

[0091] As a third example, if the update condition for the virtual card is that the virtual card receives a personalized data addition request from the issuer of the second physical card, then the target personalized data can be the aforementioned fifth personalized data. Therefore, the user terminal can obtain the fifth personalized data by parsing the target personalized data and write it into the second scenario extended data area, thereby updating the virtual card's function in the scenario corresponding to the second physical card. If there are multiple second scenario extended data areas, the fifth personalized data can be written into any one of them. Furthermore, to facilitate subsequent data updates, when writing the fifth personalized data into the second scenario extended data area, the scenario identifier corresponding to the fifth personalized data (i.e., the scenario identifier corresponding to the second physical card) is marked as the scenario identifier of that second scenario extended data area.

[0092] This application's embodiments map personalized data to a base configuration data area and different scenario extension data areas according to type. This allows for independent updates to the virtual card's validity period, optimization of specific scenario functions, and expansion of scenario functions brought about by adding physical cards, all through data replacement or writing, without requiring the entire card to be re-personalized. The aforementioned modular data processing enables unified dynamic management of the base card and multiple physical cards corresponding to the same virtual card. While maintaining the basic functions of the virtual card, it allows for flexible updates to the validity period, scenario attributes, or expansion of new scenario functions. This achieves on-demand flexible iteration and expansion of scenario functions while ensuring the continued availability of the core virtual card functions.

[0093] The following describes the method for updating virtual cards applied to a trusted service management platform, as provided in the embodiments of this application.

[0094] Figure 3 This illustration shows a flowchart of a virtual card update method applied to a trusted service management platform according to an embodiment of this application. This virtual card update method can be executed by the trusted service management platform. Figure 3 As shown, the virtual card update method provided in this application embodiment includes steps S310-S360.

[0095] S310 receives an update trigger notification sent by the virtual card issuer. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The target personalized data is generated when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios.

[0096] S320 sends an update trigger notification to the user terminal via the device management service platform of the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request.

[0097] S330 receives the first data acquisition request sent by the user terminal through the device management service platform.

[0098] S340 sends a first data acquisition request to the virtual card issuer.

[0099] S350 receives the target personalized data returned by the virtual card issuer in response to the first data acquisition request.

[0100] S360 sends target personalized data to the user terminal via the device management service platform, so that the user terminal can update the virtual card based on the target personalized data.

[0101] Therefore, in order to improve the security of data transmission and thus the security of the virtual card update process, in some embodiments, the above-mentioned S360 may specifically include: Generate data acquisition credentials corresponding to the target personalized data; The device management service platform sends a data acquisition credential to the user terminal, so that the user terminal can generate a second data acquisition request based on the data acquisition credential. Receive a second data acquisition request sent by the user equipment via the device management service platform; In response to the second data acquisition request, the target personalized data is sent to the user terminal via the device management service platform.

[0102] Here, the trusted service management platform does not directly transmit the target personalized data to the user terminal. Instead, it first caches the target personalized data and generates a data acquisition credential corresponding to the target personalized data. Then, the user terminal carries the data acquisition credential to obtain the target personalized data.

[0103] This application embodiment, through the generation and transmission of data acquisition credentials as an intermediary, and under the coordination of the device management service platform, achieves indirect, secure, and controllable transmission of target personalized data from the trusted service platform to the user terminal. This reduces the risk of critical data exposure in the intermediate link, improves the security of data transmission, and thus enhances the security of the virtual card update process.

[0104] Other steps of the method in this application embodiment can be found above. Figure 1 The relevant descriptions of the embodiments shown will not be repeated here.

[0105] In this embodiment, when the virtual card update conditions are met, the virtual card issuer obtains the target personalized data corresponding to the update conditions, generates a first data acquisition request to trigger the user terminal to initiate an update trigger notification for the target personalized data, and sends an update trigger notification to the user terminal via the trusted service management platform and the device management service platform. This enables the user terminal to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the trusted service management platform, the user terminal can obtain the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continuous availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multi-functional virtual cards.

[0106] The following describes the method for updating virtual cards applied to a device management service platform, as provided in the embodiments of this application.

[0107] Figure 4 This illustration shows a flowchart of a virtual card update method applied to a device management service platform according to an embodiment of this application. This virtual card update method can be executed by the device management service platform. Figure 4 As shown, the virtual card update method provided in this application embodiment includes steps S410-S460.

[0108] S410, receive an update trigger notification sent by the trusted service management platform. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios.

[0109] S420, the update trigger notification is sent to the user terminal so that the user terminal responds to the update trigger notification and generates a first data acquisition request.

[0110] Therefore, in order to improve the reliability of virtual card updates, in some embodiments, the above-mentioned S420 may specifically include: Obtain the network connection status of the user terminal; When the network status indicates that the user terminal's network is normal, an update trigger notification is sent to the user terminal. When the network status indicates a network anomaly on the user terminal, a cache update is triggered to trigger a notification until the network returns to normal.

[0111] Here, the device management service platform can actively poll or listen for network status change events through system interfaces (such as the network connection manager) to obtain and determine the current network status of the user terminal. If the network is determined to be normal, an update trigger notification is immediately sent to the user terminal to trigger its subsequent update process. If the network is determined to be abnormal (such as no network connection, weak signal, or server unreachable), the notification is not sent immediately, but is temporarily stored in a local or server-side cache queue, and the network status is continuously or periodically monitored. Once the user terminal's network is subsequently detected to have returned to normal, the previously stored notification is automatically retrieved from the cache and sent.

[0112] This application embodiment intelligently couples the sending of update trigger notifications with the real-time network status of the user terminal, effectively solving the problem that update instructions may be lost or fail in environments with no network or weak network, and improving the reliability of virtual card updates.

[0113] S430, receive the first data acquisition request sent by the user terminal.

[0114] S440, the first data acquisition request is sent to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data.

[0115] S450, receive the target personalized data sent by the trusted service management platform.

[0116] S460, the target personalized data is sent to the user terminal so that the user terminal updates the virtual card based on the target personalized data.

[0117] Therefore, in order to improve the security of data transmission and thus the security of the virtual card update process, in some embodiments, the above-mentioned S450 and S460 may specifically include: Receive data acquisition credentials sent by the trusted service management platform; Send a data acquisition credential to the user terminal so that the user terminal can generate a second data acquisition request based on the data acquisition credential; Receive a second data acquisition request sent by the user terminal; Send a second data acquisition request to the Trusted Service Management Platform so that the Trusted Service Management Platform responds to the second data acquisition request and returns the target personalized data.

[0118] Here, the trusted service management platform does not directly transmit the target personalized data to the user terminal. Instead, it first caches the target personalized data and generates a data acquisition credential corresponding to the target personalized data. Then, the user terminal carries the data acquisition credential to obtain the target personalized data.

[0119] Furthermore, after receiving the data acquisition credential, the device management service platform can first obtain the user terminal's network status before sending it to the user terminal. If the network status indicates that the user terminal's network is normal, the data acquisition credential is sent to the user terminal. If the network status indicates that the user terminal's network is abnormal, the data acquisition credential is cached until the network is normal before sending it to the user terminal. By intelligently coupling the sending of the data acquisition credential with the user terminal's real-time network status, the problem of potential loss or invalidation of the data acquisition credential in environments with no network or weak network is effectively solved, improving the reliability of virtual card updates.

[0120] This application embodiment, through the generation and transmission of data acquisition credentials as an intermediary, and under the coordination of the device management service platform, achieves indirect, secure, and controllable transmission of target personalized data from the trusted service platform to the user terminal. This reduces the risk of critical data exposure in the intermediate link, improves the security of data transmission, and thus enhances the security of the virtual card update process.

[0121] Other steps of the method in this application embodiment can be found above. Figure 1 The relevant descriptions of the embodiments shown will not be repeated here.

[0122] In this embodiment, when the virtual card update conditions are met, the virtual card issuer obtains the target personalized data corresponding to the update conditions, generates a first data acquisition request to trigger the user terminal to initiate an update trigger notification for the target personalized data, and sends an update trigger notification to the user terminal via the trusted service management platform and the device management service platform. This enables the user terminal to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the trusted service management platform, the user terminal can obtain the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continuous availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multi-functional virtual cards.

[0123] In summary, this application addresses the dual pain points of a virtual card's inability to flexibly adapt to dynamic business rules across various scenarios, and the virtual card's expiration upon the physical IC card's expiration. By reserving expandable field space in the IC card's data area, it supports the on-demand writing of scenario-specific parameters, such as student status identification in campus card consumption scenarios and access control system permission level codes, thus achieving dynamic data reconstruction across scenarios. Furthermore, when the base card is a bank card, as the card approaches its expiration date, the virtual card issuer triggers a cloud-based re-personalization process. Without replacing the physical card, the key validity period and data fields are updated via a secure channel, transforming the 10-year lifespan into a renewable mode. This achieves seamless continuation of payment functionality and completely eliminates transaction interruptions caused by card expiration.

[0124] Specifically, by mapping personalized data to the baseline configuration data area and different scenario-extended data areas according to type, updates to the validity period of virtual cards, optimization of specific scenario functions, and expansion of scenario functions brought about by the addition of physical cards can be performed independently through data replacement or writing, without re-personalizing the entire card. This modular data processing enables unified dynamic management of the baseline card and multiple physical cards corresponding to the same virtual card. While maintaining the basic functions of the virtual card, it can flexibly update the validity period, scenario attributes, or expand new scenario functions separately, thus supporting flexible iteration and expansion of scenario functions on demand while ensuring the continuous availability of the core functions of the virtual card. Furthermore, the introduction of the modular data architecture completely changes the upgrade mode of traditional smart card systems. By decoupling data fields and permission rules from the physical card body, dynamic configuration at the software level is achieved, so that field expansion and permission adjustments are no longer limited by the replacement cycle of the physical card body.

[0125] Secondly, the dynamic key management mechanism reconstructs the card lifecycle management system through a software-defined security paradigm. By migrating validity period control from the hardware chip to the virtual card issuer or trusted service management platform, the card gains the flexibility of lifetime usability. The system can dynamically adjust the key validity period according to security policies, achieving remote and flexible management of card status while maintaining financial-grade security standards.

[0126] Finally, the establishment of standardized interfaces has built a multi-scenario collaborative ecosystem. By defining clear industry application interface specifications, diverse application scenarios such as campus and access control are seamlessly integrated while ensuring the secure isolation of core payment data.

[0127] Therefore, this application constructs a future-oriented smart card infrastructure, enabling the system to achieve industry-leading levels in terms of security, flexibility, and scalability, and providing reliable technical support for complex scenarios such as smart cities and digital campuses.

[0128] Based on the virtual card update method for virtual card issuers provided in the above embodiments, this application also provides specific implementations of a virtual card update apparatus for virtual card issuers. Please refer to the following embodiments.

[0129] like Figure 5 As shown, a virtual card update apparatus 500 provided in one embodiment of this application includes the following modules: The acquisition module 510 is used to acquire target personalized data corresponding to the update conditions when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The first generation module 520 is used to generate an update trigger notification based on the target personalized data. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The first sending module 530 is used to send an update trigger notification to the trusted service management platform, so that the trusted service management platform sends the update trigger notification to the user terminal via the device management service platform of the user terminal. The first receiving module 540 is used to receive the first data acquisition request sent by the trusted service management platform; The first sending module 530 is also configured to respond to the first data acquisition request by sending target personalized data to the trusted service management platform so that the user terminal can acquire the target personalized data and update the virtual card based on the target personalized data.

[0130] The virtual card update device 500 described above will be explained in detail below: In some embodiments, the virtual card corresponds to multiple physical cards, the issuer of the virtual card is the issuer of the base card, and the base card is any one of the multiple physical cards; the user terminal includes a security chip, and the security chip includes a base configuration data area and a scene extension data area.

[0131] Based on this, the aforementioned virtual card update device 500 may further include: The determination module is used to determine the first physical card associated with the base card before generating the target personalized data corresponding to the update conditions when the update conditions of the virtual card are met. This is done when the user terminal receives a virtual card activation request for the base card sent through the device management service platform and the trusted service management platform. The acquisition module 510 is also used to acquire the first humanized data corresponding to the base card and the second humanized data corresponding to the first physical card, respectively; The first sending module 530 is also used to send the first personalized data and the second personalized data to the user terminal via the trusted service management platform and the device management service platform, so that the user terminal writes the first personalized data into the baseline configuration data area and writes the second personalized data into the scenario extension data area to obtain a virtual card.

[0132] In some embodiments, the conditions for updating the virtual card include at least one of the following: The virtual card's validity period has been detected and it has reached the renewal requirements. Received a scene attribute data change request from the issuer of the first physical card; The system receives a request from the issuer of the second physical card to add personalized data. The second physical card is a physical card associated with the base card after the base card is bound to the user terminal and a virtual card is obtained.

[0133] In this embodiment, when the update conditions of the virtual card are met, by acquiring the target personalized data corresponding to the update conditions, a first data acquisition request is generated to trigger the user terminal to initiate an update trigger notification for the target personalized data. The user terminal is then sent an update trigger notification via the Trusted Service Management Platform and the Device Management Service Platform, enabling it to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the Device Management Service Platform and the Trusted Service Management Platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the Trusted Service Management Platform, the user terminal can acquire the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continued availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multifunctional virtual cards.

[0134] Based on the virtual card update method for user terminals provided in the above embodiments, this application also provides specific implementations of a virtual card update apparatus for user terminals. Please refer to the following embodiments.

[0135] like Figure 6 As shown, a virtual card update apparatus 600 provided in one embodiment of this application includes the following modules: The second receiving module 610 is used to receive an update trigger notification sent by the trusted service management platform through the device management service platform of the user terminal. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The second generation module 620 is used to generate a first data acquisition request in response to an update trigger notification; The second sending module 630 is used to send a first data acquisition request to the trusted service management platform via the device management service platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data. The second receiving module 610 is also used to receive target personalized data sent by the trusted service management platform via the device management service platform; Update module 640 is used to update the virtual card based on the target personalized data.

[0136] The virtual card update device 600 described above will be explained in detail below: In some embodiments, the virtual card corresponds to multiple physical cards, the issuer of the virtual card is the issuer of the base card, and the base card is any one of the multiple physical cards; the user terminal includes a security chip, and the security chip includes a base configuration data area and a scene extension data area.

[0137] Based on this, the virtual card update device 600 may further include: The second receiving module 610 is also used to receive the first input of the virtual card used by the user to activate the base card before receiving the update trigger notification sent by the trusted service management platform via the device management service platform of the user terminal; The second generation module 620 is also used to generate a virtual card activation request for the base card in response to the first input; The second sending module 630 is also used to send a virtual card activation request to the virtual card issuer via the device management service platform and the trusted service management platform, so that the virtual card issuer can determine the first physical card associated with the base card, obtain the first humanized data corresponding to the base card and the second humanized data corresponding to the first physical card, and send the first humanized data and the second humanized data to the user terminal. The second receiving module 610 is also used to receive the first personalized data and the second personalized data sent by the virtual card issuer through the trusted service management platform and the device management service platform; The writing module is used to write the first humanized data to the baseline configuration data area and the second humanized data to the scene extension data area to obtain the virtual card.

[0138] In some embodiments, there are multiple scene extended data areas, including a first scene extended data area that already stores personalized data and a second scene extended data area that is idle. Based on this, the update module 640 may specifically include: The parsing submodule is used to parse the target personalized data to obtain at least one of the updated third personalized data corresponding to the base card, the updated fourth personalized data corresponding to the first physical card, and the newly added fifth personalized data corresponding to the second physical card. The third personalized data includes the validity period, the fourth personalized data includes scene attribute data, and the second physical card is the physical card associated with the base card after binding the base card to the user terminal to obtain the virtual card. Execution submodule, used to perform at least one of the following operations: Replace the personal data already stored in the baseline configuration data area with the third personal data to update the validity period of the virtual card; Replace the personal data already stored in the first scenario extended data area with the fourth personal data to update the functionality of the virtual card in the corresponding scenario; The fifth personalized data is written into the second scene extended data area to increase the functionality of the virtual card in the corresponding scene.

[0139] In some embodiments, there are multiple first scene extended data areas, each corresponding to a scene identifier. Based on this, the execution submodule can be specifically used for: Based on the scene identifier corresponding to the fourth personalized data, the target scene extended data area corresponding to the fourth personalized data is determined among multiple scene extended data areas; Replace the already stored personalized data in the target scene extended data area with the fourth personalized data.

[0140] In this embodiment, when the virtual card update conditions are met, the virtual card issuer obtains the target personalized data corresponding to the update conditions, generates a first data acquisition request to trigger the user terminal to initiate an update trigger notification for the target personalized data, and sends an update trigger notification to the user terminal via the trusted service management platform and the device management service platform. This enables the user terminal to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the trusted service management platform, the user terminal can obtain the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continuous availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multi-functional virtual cards.

[0141] Based on the virtual card update method for a trusted service management platform provided in the above embodiments, this application also provides a specific implementation of a virtual card update apparatus for a trusted service management platform. Please refer to the following embodiments.

[0142] like Figure 7 As shown, a virtual card update apparatus 700 provided in one embodiment of this application includes the following modules: The third receiving module 710 is used to receive an update trigger notification sent by the virtual card issuer. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The target personalized data is generated when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The third sending module 720 is used to send an update trigger notification to the user terminal via the device service management platform of the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request. The third receiving module 710 is also used to receive a first data acquisition request sent by the user terminal through the device service management platform; The third sending module 720 is also used to send a first data acquisition request to the virtual card issuer; The third receiving module 710 is also used to receive the target personalized data returned by the virtual card issuer in response to the first data acquisition request; The third sending module 720 is also used to send target personalized data to the user terminal via the device service management platform, so that the user terminal can update the virtual card based on the target personalized data.

[0143] The virtual card update device 700 described above will be explained in detail below: In some embodiments, the third transmitting module 720 may specifically include: The generation submodule is used to generate data acquisition credentials corresponding to the target personalized data; The third sending submodule is used to send a data acquisition certificate to the user terminal via the device service management platform, so that the user terminal can generate a second data acquisition request based on the data acquisition certificate. The third receiving submodule is used to receive the second data acquisition request sent by the user equipment through the device service management platform; The third sending submodule is also used to respond to the second data acquisition request and send the target personalized data to the user terminal via the device service management platform.

[0144] In this embodiment, when the virtual card update conditions are met, the virtual card issuer obtains the target personalized data corresponding to the update conditions, generates a first data acquisition request to trigger the user terminal to initiate an update trigger notification for the target personalized data, and sends an update trigger notification to the user terminal via the trusted service management platform and the device management service platform. This enables the user terminal to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the trusted service management platform, the user terminal can obtain the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continuous availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multi-functional virtual cards.

[0145] Based on the virtual card update method for a device management service platform provided in the above embodiments, this application also provides a specific implementation of a virtual card update device for a device management service platform. Please refer to the following embodiments.

[0146] like Figure 8 As shown, an embodiment of this application provides a virtual card update device 800 including the following modules: The fourth receiving module 810 is used to receive the update trigger notification sent by the trusted service management platform. The update trigger notification is used to trigger the user terminal to initiate the first data acquisition request for the target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The fourth sending module 820 is used to send an update trigger notification to the user terminal so that the user terminal responds to the update trigger notification and generates a first data acquisition request; The fourth receiving module 810 is also used to receive a first data acquisition request sent by the user terminal; The fourth sending module 820 is also used to send a first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; The fourth receiving module 810 is also used to receive target personalized data sent by the trusted service management platform; The fourth sending module 820 is also used to send target personalized data to the user terminal so that the user terminal can update the virtual card based on the target personalized data.

[0147] The virtual card update device 800 described above will be explained in detail below: In some embodiments, the fourth transmitting module 820 may specifically include: The acquisition submodule is used to obtain the network status of the user terminal; The fourth sending submodule is used to send an update trigger notification to the user terminal when the network status indicates that the user terminal's network is normal. The caching submodule is used to trigger a cache update notification when the network status indicates a network anomaly on the user terminal, until the network returns to normal.

[0148] In some embodiments, the fourth receiving module 810 may specifically include: The fourth receiving submodule is used to receive data acquisition credentials sent by the trusted service management platform; The fourth sending submodule is also used to send a data acquisition credential to the user terminal so that the user terminal can generate a second data acquisition request based on the data acquisition credential. The fourth receiving submodule is also used to receive a second data acquisition request sent by the user terminal; The fourth sending submodule is also used to send a second data acquisition request to the trusted service management platform, so that the trusted service management platform responds to the second data acquisition request and returns the target personalized data.

[0149] In this embodiment, when the virtual card update conditions are met, the virtual card issuer obtains the target personalized data corresponding to the update conditions, generates a first data acquisition request to trigger the user terminal to initiate an update trigger notification for the target personalized data, and sends an update trigger notification to the user terminal via the trusted service management platform and the device management service platform. This enables the user terminal to respond to the update trigger notification, generate the first data acquisition request, and send the first data acquisition request to the virtual card issuer via the device management service platform and the trusted service management platform. Thus, by having the virtual card issuer respond to the first data acquisition request and send the target personalized data to the trusted service management platform, the user terminal can obtain the target personalized data and update the virtual card based on it, thereby achieving automatic updates of the virtual card and ensuring its continuous availability. Furthermore, based on the multiple functions of the virtual card across scenarios, multiple uses of a single card can be achieved. Therefore, this embodiment enhances the flexibility and scalability of the virtual card in cross-scenario applications and improves the reliability of multi-functional virtual cards.

[0150] Based on the virtual card update method provided in the above embodiments, this application also provides specific implementation methods for electronic devices. Figure 9 A schematic diagram of the structure of an electronic device provided in one embodiment of this application is shown.

[0151] like Figure 9 As shown, the electronic device 900 may include a processor 910 and a memory 920 storing computer program instructions.

[0152] Specifically, the processor 910 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0153] Memory 920 may include mass storage for data or instructions. For example, and not limitingly, memory 920 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where suitable, memory 920 may include removable or non-removable (or fixed) media. Where suitable, memory 920 may be internal or external to electronic device 900. In a particular embodiment, memory 920 is a non-volatile solid-state memory.

[0154] In a specific embodiment, the memory 920 may be implemented as a read-only memory (ROM), random access memory (RAM), static storage device, dynamic storage device, etc. The memory 920 may store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 920 and executed by the processor 910. The processor 910 implements any of the virtual card update methods in the above embodiments by reading and executing the computer program instructions stored in the memory 920.

[0155] The processor 910 implements any of the virtual card update methods in the above embodiments by reading and executing computer program instructions stored in the memory 920.

[0156] In one example, electronic device 900 may further include communication interface 930 and bus 940. Wherein, as... Figure 9 As shown, the processor 910, memory 920, and communication interface 930 are connected via bus 940 and communicate with each other.

[0157] The communication interface 930 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0158] Bus 940 includes hardware, software, or both, that couples components of an electronic device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 940 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0159] For example, the electronic device 900 can be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0160] The electronic device can execute the virtual card update method in the embodiments of this application, thereby achieving the combination Figures 1 to 4 The method for updating the virtual card described herein, and the beneficial effects of the corresponding method embodiments, will not be elaborated further here.

[0161] Furthermore, in conjunction with the virtual card update method in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the virtual card update methods in the above embodiments. Examples of the computer-readable storage medium include non-transitory computer-readable storage media, such as read-only memory (ROM).

[0162] The computer program instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the virtual card update method as shown in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0163] Based on the virtual card update methods in the above embodiments, this application can provide a computer program product to implement them. When the instructions in this computer program product are executed by the processor of an electronic device, they implement any of the virtual card update methods in the above embodiments.

[0164] The computer program products of the above embodiments are used to implement the virtual card update method as shown in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0165] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0166] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0167] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0168] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0169] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for updating a virtual card, characterized in that, Applied to virtual card issuers, the method includes: Under the condition that the virtual card is updated, the target personalized data corresponding to the update condition is obtained, and the virtual card is used to realize multiple functions across scenarios; Based on the target personalized data, an update trigger notification is generated, which is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data; Send the update trigger notification to the trusted service management platform, so that the trusted service management platform sends the update trigger notification to the user terminal via the device management service platform of the user terminal; Receive the first data acquisition request sent by the trusted service management platform; In response to the first data acquisition request, the target personalized data is sent to the trusted service management platform so that the user terminal can acquire the target personalized data and update the virtual card based on the target personalized data.

2. The method according to claim 1, characterized in that, The virtual card corresponds to multiple physical cards, the issuer of the virtual card is the issuer of the base card, and the base card is any one of the multiple physical cards; the user terminal includes a security chip, and the security chip includes a base configuration data area and a scene extension data area; Before generating the target personalized data corresponding to the update conditions when the virtual card update conditions are met, the method further includes: Upon receiving a virtual card activation request for the base card sent by the user terminal via the device management service platform and the trusted service management platform, the first physical card associated with the base card is determined; The first humanized data corresponding to the base card and the second humanized data corresponding to the first physical card are obtained respectively; The first personalized data and the second personalized data are sent to the user terminal via the trusted service management platform and the device management service platform, so that the user terminal writes the first personalized data into the baseline configuration data area and writes the second personalized data into the scene extension data area to obtain the virtual card.

3. The method according to claim 2, characterized in that, The conditions for satisfying the virtual card update include at least one of the following: The validity period of the virtual card has been detected to have met the renewal conditions. Received a scene attribute data change request sent by the issuer of the first physical card; The system receives a request from the issuer of a second physical card to add personalized data. The second physical card is a physical card associated with the base card after the virtual card is obtained by binding the base card to the user terminal.

4. A method for updating a virtual card, characterized in that, Applied to a user terminal, the method includes: The system receives an update trigger notification sent by the trusted service management platform via the device management service platform of the user terminal. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios. In response to the update trigger notification, a first data acquisition request is generated; The device management service platform sends the first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; Receive the target personalized data sent by the trusted service management platform via the device management service platform; The virtual card is updated based on the target personalized data.

5. The method according to claim 4, characterized in that, The virtual card corresponds to multiple physical cards, the issuer of the virtual card is the issuer of the base card, and the base card is any one of the multiple physical cards; the user terminal includes a security chip, and the security chip includes a base configuration data area and a scene extension data area; Before receiving the update trigger notification sent by the trusted service management platform via the device management service platform of the user terminal, the method further includes: Receive the user's first input for activating the virtual card of the base card; In response to the first input, a virtual card activation request is generated for the base card; The virtual card activation request is sent to the virtual card issuer via the device management service platform and the trusted service management platform, so that the virtual card issuer can determine the first physical card associated with the base card, obtain the first personalized data corresponding to the base card and the second personalized data corresponding to the first physical card, and send the first personalized data and the second personalized data to the user terminal. Receive the first personalized data and the second personalized data sent by the virtual card issuer through the trusted service management platform and the device management service platform; The first personalized data is written into the baseline configuration data area, and the second personalized data is written into the scene extension data area to obtain the virtual card.

6. The method according to claim 5, characterized in that, The scenario extended data area is multiple, including a first scenario extended data area that already stores personalized data and a second scenario extended data area that is idle. Updating the virtual card based on the target personalized data includes: The target personalized data is parsed to obtain at least one of the following: the updated third personalized data corresponding to the base card, the updated fourth personalized data corresponding to the first physical card, and the newly added fifth personalized data corresponding to the second physical card. The third personalized data includes the validity period, the fourth personalized data includes scene attribute data, and the second physical card is the physical card associated with the base card after the base card is bound to the user terminal to obtain the virtual card. Perform at least one of the following operations: Replace the stored personalized data in the baseline configuration data area with the third personalized data to update the validity period of the virtual card; The fourth personalized data is used to replace the personalized data already stored in the first scenario extended data area to update the function of the virtual card in the corresponding scenario; The fifth personalized data is written into the second scene extended data area to increase the functionality of the virtual card in the corresponding scene.

7. The method according to claim 6, characterized in that, The first scene extended data area is multiple, and each first scene extended data area corresponds to a scene identifier. The step of replacing the stored personalized data in the scene extended data area with the fourth personalized data includes: Based on the scene identifier corresponding to the fourth personalized data, a target scene extended data area corresponding to the fourth personalized data is determined among multiple scene extended data areas; Replace the personalized data already stored in the target scene extended data area with the fourth personalized data.

8. A method for updating a virtual card, characterized in that, The method, applied to a trusted service management platform, includes: The system receives an update trigger notification from the virtual card issuer. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios. The update trigger notification is sent to the user terminal via the device management service platform of the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request; Receive the first data acquisition request sent by the user terminal via the device management service platform; Send the first data acquisition request to the virtual card issuer; Receive the target personalized data returned by the virtual card issuer in response to the first data acquisition request; The target personalized data is sent to the user terminal via the device management service platform, so that the user terminal updates the virtual card based on the target personalized data.

9. The method according to claim 8, characterized in that, Sending the target personalized data to the user terminal via the device management service platform includes: Generate a data acquisition credential corresponding to the target personalized data; The data acquisition credential is sent to the user terminal via the device management service platform, so that the user terminal generates a second data acquisition request based on the data acquisition credential. Receive the second data acquisition request sent by the user equipment via the device management service platform; In response to the second data acquisition request, the target personalized data is sent to the user terminal via the device management service platform.

10. A method for updating a virtual card, characterized in that, Applied to an equipment management service platform, the method includes: The system receives an update trigger notification sent by the Trusted Service Management Platform. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the Trusted Service Management Platform when the update conditions of the virtual card are met. The virtual card is used to implement multiple functions across scenarios. Send the update trigger notification to the user terminal so that the user terminal responds to the update trigger notification and generates a first data acquisition request; Receive the first data acquisition request sent by the user terminal; Send the first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; Receive the target personalized data sent by the trusted service management platform; The target personalized data is sent to the user terminal so that the user terminal updates the virtual card based on the target personalized data.

11. The method according to claim 10, characterized in that, Sending the update trigger notification to the user terminal includes: Obtain the network connection status of the user terminal; When the network status indicates that the user terminal's network is normal, the update trigger notification is sent to the user terminal; If the network status indicates a network anomaly for the user terminal, the update trigger notification is cached until the network returns to normal.

12. The method according to claim 10, characterized in that, The step of receiving the target personalized data sent by the trusted service management platform and sending the target personalized data to the user terminal includes: Receive the data acquisition credential sent by the trusted service management platform; Send the data acquisition credential to the user terminal so that the user terminal generates a second data acquisition request based on the data acquisition credential; Receive the second data acquisition request sent by the user terminal; Send the second data acquisition request to the trusted service management platform, so that the trusted service management platform responds to the second data acquisition request and returns the target personalized data.

13. A virtual card update device, characterized in that, The device, used by virtual card issuers, includes: The acquisition module is used to acquire target personalized data corresponding to the update conditions when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The first generation module is used to generate an update trigger notification based on the target personalized data. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The first sending module is used to send the update trigger notification to the trusted service management platform, so that the trusted service management platform sends the update trigger notification to the user terminal via the device management service platform of the user terminal. The first receiving module is used to receive the first data acquisition request sent by the trusted service management platform; The first sending module is further configured to, in response to the first data acquisition request, send the target personalized data to the trusted service management platform, so that the user terminal can acquire the target personalized data and update the virtual card based on the target personalized data.

14. A virtual card update device, characterized in that, The device, applied to a user terminal, includes: The second receiving module is used to receive an update trigger notification sent by the trusted service management platform through the device management service platform of the user terminal. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The second generation module is used to generate a first data acquisition request in response to the update trigger notification; The second sending module is used to send the first data acquisition request to the trusted service management platform via the device management service platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data. The second receiving module is further configured to receive the target personalized data sent by the trusted service management platform via the device management service platform; An update module is used to update the virtual card based on the target personalized data.

15. A virtual card update device, characterized in that, The device, used in a trusted service management platform, includes: The third receiving module is used to receive an update trigger notification sent by the virtual card issuer. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for the target personalized data. The target personalized data is generated when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The third sending module is used to send the update trigger notification to the user terminal via the device management service platform of the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request; The third receiving module is further configured to receive the first data acquisition request sent by the user terminal via the device management service platform; The third sending module is also used to send the first data acquisition request to the virtual card issuer; The third receiving module is also used to receive the target personalized data returned by the virtual card issuer in response to the first data acquisition request; The third sending module is further configured to send the target personalized data to the user terminal via the device management service platform, so that the user terminal updates the virtual card based on the target personalized data.

16. A virtual card update device, characterized in that, The device, used in an equipment management service platform, includes: The fourth receiving module is used to receive an update trigger notification sent by the trusted service management platform. The update trigger notification is used to trigger the user terminal to initiate a first data acquisition request for target personalized data. The target personalized data is generated by the virtual card issuer and sent to the trusted service management platform when the update conditions of the virtual card are met. The virtual card is used to realize multiple functions across scenarios. The fourth sending module is used to send the update trigger notification to the user terminal, so that the user terminal responds to the update trigger notification and generates a first data acquisition request; The fourth receiving module is further configured to receive the first data acquisition request sent by the user terminal; The fourth sending module is further configured to send the first data acquisition request to the trusted service management platform, so that the trusted service management platform sends the first data acquisition request to the virtual card issuer, so that the virtual card issuer responds to the first data acquisition request and returns the target personalized data; The fourth receiving module is also used to receive the target personalized data sent by the trusted service management platform; The fourth sending module is further configured to send the target personalized data to the user terminal, so that the user terminal updates the virtual card based on the target personalized data.

17. A virtual card update system, characterized in that, include: The virtual card update device applied to a virtual card issuer as described in claim 13; The virtual card update device applied to a user terminal as described in claim 14; The virtual card update device applied to a trusted service management platform as described in claim 15; The virtual card update device applied to the device management service platform as described in claim 16.

18. An electronic device, characterized in that, The electronic device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the virtual card update method as described in any one of claims 1-3, 4-7, 8-9, or 10-12.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the virtual card update method as described in any one of claims 1-3, 4-7, 8-9, or 10-12.

20. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the virtual card update method as described in any one of claims 1-3, 4-7, 8-9, or 10-12.

Images