PTOISB/14 (11-08)
`Approved for use through 01/31/2014. 0MB 0651-0032
`US. Patent and Trademark Office; US. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Attorney Docket Number P4302USOO
`Application Data Sheet 37 CFR 1.76
`Application Number
`
`
`
`
`
`SYSTEM AND METHOD FOR MANAGING MOBILE WALLET AND ITS RELATED CREDENTIALS
`Title of Invention
`
`
`
`
`
`
`The application data sheet is part of the provisional or nonprovisional application for which it is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`document may be printed and included in a paper filed application.
`
`
`
`
`
`
`Secrecy Order 37 CFR 5.2
`
`Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to
`
`
`
`37 CFR 5.2 (Paper filers only. Applications that fall under Secrecy Order may not be filed electronically.)
`
`Applicant Information:
`
`Applicant1
`
`IOParty of Interest under 35 U.S.C. 118
`Applicant Authority @Inventor OLegal Representative under 35 U.S.C. 117
`
`Prefix Given Name
`Middle Name
`Family Name
`Suffix
`
`
`
`
`Yongsung
`
`KWON
`
`Residence Information (Select One) 0 US Residency @ Non US Residency 0 Active US Militan/ Service
`
`
`Citizenship under 37 CFR 1.41(b) i
`KR
`
`Mailing Address of Applicant:
`
`Address 1
`401-1302 Lotte APT. Ggaichi Maeul, Gumi dong
`
`Address 2
`Bundang Gu, Gyeonggi—do
`
`
`
`I Seongnam-si
`City
`Postal Code
`
`
`StatelProvince
`Countryi
`KR
`
`A licant 2
`
`Applicant Authority @Inventor OLegal Representative under 35 U.S.C. 117
`OParty of Interest under 35 U.S.C. 118
`Prefix Given Name
`Middle Name
`Family Name
`Suffix
`
`
`
`
`Hyungjoon
`HONG
`
`Residence Information (Select One) 0 US Residency
`6) Non US Residency 0 Active US Military Service
`
`City I Seoul I KR Country Of Residencei
`
`
`Citizenship under 37 CFR 1.41(b) i
`KR
`
`
`Mailing Address of Applicant:
`
`Address 1
`202—9 302, Jamsil bon dong, Songpa Gu
`Address 2
`
`
`State/Province
`
`I Seoul
`City
`Countryi
`KR
`Postal Code
`
`Applicant 3
`
`(Party of Interest under 35 U.S.C. 118
`Applicant Authority @Inventor OLegal Representative under 35 U.S.C. 117
`
`Given Name
`Middle Name
`Family Name
`Suffix
`
`Jiwon
`KANG
`
`Residence Information (Select One) 0 US Residency
`6) Non US Residency 0 Active US Military Service
`
`City
`Seoul
`Country Of Residencei
`KR
`EFS Web 2.2.2
`
`Apple Ex. 1002, p. 1
`Apple Ex. 1002, p. 1
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`PTOISB/14 (11-08)
`Approved for use through 01/31/2014. 0MB 0651-0032
`US. Patent and Trademark Office; US. DEPARTMENT OF COMMERCE
`
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`Application Number
`
`
`Attorney Docket Number
`P4302USOO
`
`
`
`SYSTEM AND METHOD FOR MANAGING MOBILE WALLET AND ITS RELATED CREDENTIALS
`Title of Invention
`
`
`
`KR
`Citizenship under 37 CFR 1.41(b) i
`
`Mailing Address of Applicant:
`Address 1
`512 Hyundai Parisian 907—10, Mokdong Yangcheon—gu
`Address 2
`
`
`
`
`City
`I Seoul
`
`StatelProvince
`
`
`Countryi
`Postal Code
`KR
`
`Applicant 4
`
`Applicant Authority @Inventor OLegal Representative under 35 U.S_C_ 117
`‘OParty of Interest under 35 U.S_C_ 118
`Prefix Given Name
`Middle Name
`Family Name
`Suffix
`
`
`
`
`Hyunjin
`
`KIM
`
`Residence Information (Select One) 0 US Residency
`
`(9 Non US Residency 0 Active US Military Service
`
`I
`
`Citizenship under 37 CFR 1.41(b) i
`
`KR
`
`Mailing Address of Applicant:
`
`Address 1
`706-2003, Sangrok APT. Pungduckcheon dong, Suji-gu
`
`
`
`Address 2
`
`Gyeonggi—do
`
`Yongin—si
`City
`Postal Code
`
`I StatelProvince
`
`
`
`
`
`
`All
`Inventors Must Be Listed - Additional
`Inventor Information blocks may be
`Add
`
`generated within this form by selecting the Add button.
`
`
`Correspondence Information:
`
`Enter either Customer Number or complete the Correspondence Information section below.
`
`For further information see 37 CFR 1.33(a).
`
`
`
`:I An Address is being provided for the correspondence Information of this application.
`Customer Number
`58027
`
`Email Address
`
`
`
`Application Information:
`
`Title of the Invention
`SYSTEM AND METHOD FOR MANAGING MOBILE WALLET AND ITS RELATED CREDENTIALS
`
`
`Attorney Docket Number P4302USOO
`Small Entity Status Claimed
`|:|
`
`Application Type
`Nonprovisional
`
`Utility
`Subject Matter
`
`Suggested Class (if any)
`Sub Class (if any)
`
`
`
`Suggested Technology Center (if any)
`
`Total Number of Drawing Sheets (if any) I Suggested Figure for Publication (if any) I 5
`
`
`
`EFS Web 2.2.2
`
`Apple Ex. 1002, p. 2
`Apple Ex. 1002, p. 2
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`PTOISB/14 (11-08)
`Approved for use through 01/31/2014. 0MB 0651-0032
`US. Patent and Trademark Office; US. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Attorney Docket Number
`P4302USOO
`
`
`Application Data Sheet 37 CFR 1.76
`Application Number
`
`
`
`SYSTEM AND METHOD FOR MANAGING MOBILE WALLET AND ITS RELATED CREDENTIALS
`Title of Invention
`
`
`Publication Information:
`
`:| Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`
`
`Request Not to Publish. I hereby request that the attached application not be published under 35 US.
`:l C. 122(b) and certify that the invention disclosed in the attached application has not and will not be the subject of
`an application filed in another country, or under a multilateral international agreement, that requires publication at
`eighteen months after filing.
`
`
`
`
`
`
`
`
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32).
`Enter
`either Customer Number
`or
`complete
`the
`Representative Name
`section
`below.
`If
`both
`are completed the Customer Number will be used for the Representative Information during processing.
`
`
`Please Select One:
`(9 Customer Number
` I 0 US Patent Practitioner 0 Limited Recognition (37 CFR 11.9)
`
`Customer Number
`58027
`
`sections
`
`Domestic BenefithationaI Stage Information:
`
`This section allows for the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(0) or indicate National Stage
`entry from a PCT application. Providing this information in the app ication data sheet constitutes the specific reference required by
`35 U.S.C. 119(e) or 120, and 37 CFR 1.78(a)(2) or CFR 1.78(a)(4), and need not otherwise be made part of the specification.
`
`Prior Application Status
`Pending
`
`Application Number
`Continuity Type
`Prior Application Number
`Filing Date (YYYY-MM-DD)
`
`non provisional of
`61428846
`2010—12—30
`
`
`
`Additional Domestic Benefit/National Stage Data may be generated within this form
`by selecting the Add button.
`
`Add
`
`Foreign Priority Information:
`
`This section allows for the applicant to claim benefit of foreign priority and to identify any prior foreign application for which priority is
`not claimed. Providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b)
`and 37 CFR 1.55(a).
`
`
`Application Number
`Country i
`Parent Filing Date (YYYY-MM-DD)
`Priority Claimed
`
`
`
`
`
`
`
`
`
`0 Yes O No
`
`Add
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`
`
`Assignee Information:
`Providing this information in the application data sheet does not substitute for compliance with any requirement of part 3 of Title 37
`of the CFR to have an assignment recorded in the Office.
`
`Assignee 1
`
`EFS Web 2.2.2
`
`Apple Ex. 1002, p. 3
`Apple Ex. 1002, p. 3
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`PTOISB/14 (11-08)
`Approved for use through 01/31/2014. 0MB 0651-0032
`US. Patent and Trademark Office; US. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`
`
`Attorney Docket Number
`P4302USOO
`
`Application Data Sheet 37 CFR 1.76
`Application Number
`
`
`
`SYSTEM AND METHOD FOR MANAGING MOBILE WALLET AND ITS RELATED CREDENTIALS
`Title of Invention
`
`
`
`
`
`
`
`EIf the Assignee is an Organization check here.
`Organization Name
`SK (3&0
`
`Mailing Address Information:
`
`
`
` Address 1 SK u-Tower, 25-1 Jeongja-dong, Bundang-gu
`
`
`
`
`
`
`
`
`
`
`
`
` Address 2 Gyeonggi-do
`
`
`
`
`City
`Seongnam
`State/Province
`
`Country I KR 463—844 Postal Code
`
`
`Phone Number
`Fax Number
`
`Email Address
`
`Additional Assignee Data may be generated within this form by selecting the Add
`button.
`
`Add
`
`
`Signature:
`A signature of the applicant or representative is required in accordance with 37 CFR 1.33 and 10.18. Please see 37
`
`CFR 1.4(d) for the form of the signature.
`
`Signature
`
`lhae—chan park/
`Date (YYYY- MM-DD)
`
`
`2011—12—02
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to
`complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and
`Trademark Office, US. Department of Commerce, PO. Box 1450, Alexandria, VA 22313—1450. DO NOT SEND FEES OR
`COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 2.2.2
`
`Apple Ex. 1002, p. 4
`Apple Ex. 1002, p. 4
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Privacy Act Statement
`
`
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to
`a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that:
`(1) the general authority for the collection
`of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is
`used by the US. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent.
`If you do not
`furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`The information on this form will be treated confidentially to the extent allowed underthe Freedom of Information Act (5 U.S.C. 552)
`and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine
`whether the Freedom of Information Act requires disclosure of these records.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or
`administrative tribunal, including disclosures to opposing counsel in the course of settlement negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a request involving an
`individual, to whom the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of
`the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in
`order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as
`amended, pursuant to 5 U.S.C. 552a(m).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed,
`as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security
`review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee,
`during an inspection of records conducted by GSA as part of that agency's responsibility to recommend improvements in records
`management practices and programs, under authority of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the
`GSA regulations governing inspection of records for this purpose, and any other relevant (i.e., GSA or Commerce) directive. Such
`disclosure shall not be used to make determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant
`to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37
`CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were
`terminated and which application is referenced by either a published application, an application open to public inspections or an issued
`patent.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law enforcement agency, if the
`USPTO becomes aware of a violation or potential violation of law or regulation.
`
`
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`9.
`
`
`
`
`EFS Web 2.2.2
`
`Apple Ex. 1002, p. 5
`Apple Ex. 1002, p. 5
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`SYSTEM AND METHOD FOR MANAGING MOBILE WALLET AND ITS RELATED
`
`CREDENTIALS
`
`10
`
`15
`
`CROSS REFERENCE TO RELATED APPLICATION
`
`[0001] This application claims priority from and the benefit under 35 US. C. §ll9(a) of
`
`US. Provisional Patent Application No. 61/428,846, filed on December 30, 2010, which is
`
`incorporated by reference for all purposes as if fully set forth herein. Also, the present
`
`application is related to co—pending US. Provisional Patent Application N o. 61/428,851 filed on
`
`December 30, 2010; US. Provisional Patent Application No. 61/428,852, filed on December 30;
`
`and US. Provisional Patent Application No. 61/428,853, filed on December 30. Applicant
`
`hereby incorporates by reference the above-mentioned co-pendin g provisional applications,
`
`which are not admitted to be prior art with respect to the present invention by their mention here
`
`or in the background section that follows.
`
`BACKGROUND OF THE INVENTION
`
`[0002] l. FIELD
`
`[0003] The following description relates to management of virtual cards stored on mobile
`
`devices.
`
`[0004] 2. DISCUSSION OF THE BACKGROUND
`
`[0005] With the advent of advancing mobile technology, more features have been
`
`integrated into mobile devices. From GPS applications to mobile office products, mobile
`
`devices, such as mobile communicative terminals, have practically become a necessity for
`
`everyday needs. In order to further utilize mobile technology to better cater to a user’s daily
`
`Apple Ex. 1002, p. 6
`Apple Ex. 1002, p. 6
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`requirements, attempts have been made to provide for a mobile financial management system to
`
`replace conventional physical wallets. Specifically, this mobile wallet functionality was sought
`
`to be realized through provisioning of card issuer’s account inf01mation directly into a secure
`
`element (SE) of the mobile device equipped with Near Field Communication (NFC) chipset.
`
`The SE may be a smart card chip capable of storing multiple applications, including of account
`
`specific information that may not be easily accessed by external parties. The model mobile
`
`wallet application may have the same composition as a conventional wallet, which may contain
`
`payment cards, member cards, transportation cards, and loyalty cards.
`
`[0006] Further, to make the wallet function more convenient to the owners of the mobile
`
`10
`
`15
`
`device, a method of providing contactless payment (NFC-based applications) through
`
`provisioning account specific information within the secure domain of the mobile device’s SE
`
`has been provided. More specifically, user financial credentials, such as credit card numbers,
`
`may be provisioned onto mobile devices equipped with Near Field Communication chipset (NFC
`
`enabled) to make payments. Once the user financial credentials have been provisioned onto the
`
`NFC enabled mobile device, the provisioned NFC enabled device may transfer information or
`
`make payments to another NFC compatible device by coming near within a few centimeters of
`
`one another without physically contacting each other. This type of technology is conventionally
`
`referred to as “contactless” technology and a payment made with this technology is referred to as
`
`“contactless” payment.
`
`[0007] However, regardless of benefits that may be obtained through integrating wallet
`
`functionality into mobile device, prevailing technology still lacks an effective means to manage
`
`various payment applets residing within the mobile device.
`
`[0008] With the advent of NFC—based contactless payment applications, users were
`
`Apple Ex. 1002, p. 7
`Apple Ex. 1002, p. 7
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`provided a way to select a contactless payment applet (i.e., contactless payment virtual card)
`
`from various contactless payment applets stored in the mobile device for payment at
`
`corresponding point—of—sale (POS) devices. However, while these contactless payment applets
`
`may be selected to make a purchase, the management of payment applets may be limited. For
`
`example, a user may be limited to view the contactless payment applets stored in the user’s
`
`mobile device when interacting with a POS device. Further, even if the user is able to view the
`
`various contactless payment applets stored in the mobile device with or without the POS device,
`
`the user may be unable to view the details related to the contactless payment applets (e. g.,
`
`account number, expiration date, security code, balance and the like). Accordingly, users may be
`
`unable to effectively manage or keep track of various contactless payment applets stored in their
`
`respective mobile devices.
`
`[0009] Typically, the contactless card applets may be stored within a specific
`
`compartment, or a secured domain, of the SE to be accessed during an interaction with the POS
`
`device. Moreover, even when such payment applications are accessed, since these applications
`
`are managed through industry standard Payment Procedure Secure Elements (PPSE) that only
`
`provide for application identification (ID) and label, a limited generic description may be
`
`provided to the user. Accordingly, the user may be unable to view any account specific
`
`information stored within the SE or manage such applications with or without the use of POS
`
`10
`
`15
`
`equipment.
`
`[0010] Another limitation of current mobile wallet applications is the lack of support
`
`providing for such technology. With such focus on mobile commerce, many competing service
`
`providers seek delivering their services to the users. However, such services may be offered to
`
`the users without regard to the mobile device capabilities or mobile service providers utilized by
`
`Apple Ex. 1002, p. 8
`Apple Ex. 1002, p. 8
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`the user. Due to technical or business compatibility, there may be numerous applications that
`
`may be inapplicable to the user’s individual attributes (e. g., bank membership, mobile service
`
`provider, manufacturer of a mobile device owned by the user, type of secure element installed in
`
`the mobile device, operating system of the mobile device, and the like). Accordingly, users may
`
`often be bombarded with various applications that may be inapplicable to the user, making the
`
`process more difficult than necessary.
`
`[0011] Another issue with the current mobile wallet application is its ability to update its
`
`information. As various service providers operate independently from one another, when an
`
`update is required by a palticular service provider, each individual application is typically
`
`updated separately. Such inefficiency may dissuade users from obtaining crucial updates that
`
`may be necessary to a particular application.
`
`SUMMARY
`
`[0012] Exemplary embodiments of the present invention provide a mobile device to store
`
`a mobile wallet application and a wallet management system (WMS) to store corresponding
`
`wallet application information. Exemplary embodiments of the present invention provide a
`
`method for provisioning a wallet application, a contactless card applet, a wallet management
`
`applet (WMA), and a widget. Exemplary embodiments of the present invention provide a
`
`method for synchronizing a mobile wallet application with the WMS.
`
`[0013] Additional features of the invention will be set forth in the description which
`
`follows, and in part will be apparent from the description, or may be learned by practice of the
`
`invention.
`
`[0014] Exemplary embodiments of the present invention provide a method for installing
`
`10
`
`15
`
`Apple Ex. 1002, p. 9
`Apple Ex. 1002, p. 9
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`a wallet application in a mobile device including requesting, by the mobile device, a mobile
`
`wallet application comprising a corresponding Over—the—Air (OTA) proxy; receiving mobile
`
`wallet application installation information; installing the mobile wallet application in the mobile
`
`device; capturing mobile device information by using the OTA proxy, the mobile device
`
`information comprising secure element (SE) information; and transmitting the mobile device
`
`information for registering the installed mobile wallet application.
`
`[0015] Exemplary embodiments of the present invention provide a method for managing
`
`mobile wallet accounts installed on a mobile devices including receiving a request for a mobile
`
`wallet application from a mobile device; transmitting the mobile wallet application to the mobile
`
`device; receiving mobile device information, the mobile device information comprising SE
`
`information; and registering the mobile device and the corresponding mobile wallet application
`
`in a trusted service manager (TSM).
`
`[0016] Exemplary embodiments of the present invention provide method for provisioning
`
`a contactless card applet in a mobile device comprising a mobile wallet application including
`
`activating the mobile wallet application; connecting to a TSM system; synchronizing the mobile
`
`wallet application with the TSM system; displaying a contactless card applet based on attributes
`
`of the mobile device; receiving a selection of a contactless card applet; retrieving a widget and a
`
`WMA corresponding to the contactless card applet; and provisioning the selected contactless
`
`card applet, widget, and the WMA.
`
`[0017] Exemplary embodiments of the present invention provide a WMS in a non-
`
`transitory storage medium to store and manage mobile wallet account information including a
`
`wallet client management component to store and to manage a mobile wallet application; a
`
`widget management component to store and to manage widgets; a device profile management
`
`10
`
`15
`
`Apple Ex. 1002, p. 10
`Apple Ex. 1002, p. 10
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`component to store mobile device information; and a rule engine to filter a widget based on the
`
`mobile device information.
`
`[0018] Exemplary embodiments of the present invention provide a mobile device
`
`including a SE; a mobile wallet application to store a widget corresponding to a contactless card
`
`applet, wherein the contactless card applet is stored in the SE; a WMA corresponding to the
`
`contactless card applet, wherein WMA is stored in the SE; and an OTA proxy to provision the
`
`contactless card applet, a widget corresponding to the contactless card applet, and the WMA.
`
`[0019] It is to be understood that both foregoing general descriptions and the following
`
`detailed description are exemplary and explanatory and are intended to provide further
`
`explanation of the invention as claimed. Other features and aspects will be apparent from the
`
`following detailed description, the drawings, and the claims.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0020] The accompanying drawings, which are included to provide a further
`
`understanding of the invention and are incorporated in and constitute a part of this specification,
`
`illustrate embodiments of the invention, and together with the description serve to explain the
`
`principles of the invention.
`
`[0021] FIG. I is a system diagram of a mobile wallet application and associated
`
`integration in accordance with an exemplary embodiment of the present invention.
`
`[0022] FIG. 2 is a system diagram illustrating a system and method for provisioning
`
`mobile card wallet management application along with supporting applications. mobile card
`
`widgets, contactless card applets, and related credentials in accordance with an exemplary
`
`embodiment of the present invention.
`
`10
`
`15
`
`Apple Ex. 1002, p. 11
`Apple Ex. 1002, p. 11
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`[0023] FIG. 3 is a system diagram illustrating a system and method for provisioning
`
`service provider specific mobile card widgets, contactless card applets, and wallet management
`
`application account information in accordance with an exemplary embodiment of the present
`
`invention.
`
`[0024] FIG. 4 is a system diagram illustrating a system and method for dynamically
`
`filtering applicable mobile wallet service provider specific widgets based upon user account
`
`attributes in accordance with an exemplary embodiment of the present invention.
`
`[0025] FIG. 5 is a system diagram illustrating a system and method for synchronizing
`
`mobile wallet application with the master mobile wallet configuration server to provide a most
`
`current version of the mobile wallet application in accordance with an exemplary embodiment of
`
`the present invention.
`
`DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS
`
`[0026] The invention is described more fully hereinafter with references to the
`
`accompanying drawings, in which exemplary embodiments of the invention are shown. This
`
`invention may, however, be embodied in many different forms and should not be construed as
`
`limited to the embodiments set forth herein. Rather, these exemplary embodiments are provided
`
`so that this disclosure is thorough, and will fully convey the scope of the invention to those
`
`skilled in the art. It will be understood that for the purposes of this disclosure, “at least one of
`
`each” will be interpreted to mean any combination the enumerated elements following the
`
`respective language. including combination of multiples of the enumerated elements. For
`
`example, “at least one of X, Y, and Z” will be construed to mean X only, Y only, 2 only, or any
`
`combination of two or more items X, Y, and Z (e. g. XYZ, X2, Y2). Throughout the drawings
`
`10
`
`15
`
`Apple Ex. 1002, p. 12
`Apple Ex. 1002, p. 12
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`and the detailed description, unless otherwise described, the same drawing reference numerals
`
`are understood to refer to the same elements, features, and structures. The relative size and
`
`depiction of these elements may be exaggerated for clarity, illustration, and convenience.
`
`[0027] FIG. 1
`
`is a system diagram of a mobile wallet system and associated integration,
`
`according to an exemplary embodiment of the present invention.
`
`[0028] As shown in FIG. 1, an example system utilizing mobile wallet technology may
`
`include a mobile device 100, mobile wallet management system (WMS) 110, supporting Trusted
`
`Service Manager (TSM) system 120, Mobile Network Operator (MN 0) 130, and Service
`
`Provider (SP) 140.
`
`[0029] WMS 110 includes a wallet client management component 111, widget
`
`management component 112, device profile management component 113, user profile
`
`management component 114, data management component 115, and rule engine 116.
`
`[0030] In particular, wallet client management component 111 is responsible for the
`
`wallet application itself (referred as the container), which may house the individual Widgets (e. g.,
`
`applications stored at the application level related to a financial institution, transportation
`
`account, and the like). The wallet client management component 111 may store container
`
`specific information, including the type of wallet application and manufacturer. For example,
`
`wallet client management component 111 may recognize a user John has a mobile wallet
`
`application manufactured by Google® and has specified set of known functionalities. By
`
`managing the type of wallet application the user has on the mobile device, it may be possible to
`
`provide the same wallet application when necessary.
`
`[0031] Widget management component 112 on the other hand is responsible for the
`
`individual widgets stored within the wallet container. Widgets may be an application configured
`
`10
`
`IS
`
`Apple Ex. 1002, p. 13
`Apple Ex. 1002, p. 13
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`to interface with a user of the mobile device. In an example, widgets may refer to individual
`
`payment applications, transportation applications, and other related applications. Device Profile
`
`management component 113 houses a memory to store one or more programs, such as
`
`applications, and other related information. Device Profile management component 1 13 may
`
`store device specific information, such as information related to the mobile device itself
`
`including type of mobile device, supporting operating system (OS), mobile service provider, and
`
`other relevant information. User Profile management component 114 captures user identifying
`
`information such as name, address, birthday, phone number, and the like. Data Management
`
`component 115 allows further expansion of data management services offered by a mobile WMS
`
`(e. g., transaction history, user preferences, loyalty programs, digital receipts, digital coupons and
`
`the like). Rule engine 116 may filter widgets based on information related to the mobile device.
`
`Although various components were illustrated to be included in the WMS 110, the configuration
`
`of WMS 110 is not limited thereto. The illustrated components may be included within the
`
`WMS 110 or external to the WMS 110.
`
`[0032] The disclosed WMS l 10 may reside within TSM system 120 or independent of
`
`the TSM system 120. For the purposes of this disclosure, it will be assumed that the WMS 110
`
`is housed within the TSM system 120. Like the TSM system 120, WMS 110 may interact with
`
`MNO 130 to transmit and receive billing related information. Further, WMS 110 may interact
`
`with SP 140 to receive and transmit SP payment card information.
`
`[0033] The TSM system 120 may refer to a third party entity positioned to consolidate
`
`various information from various service providers including, financial institutions, MNOs,
`
`handset manufacturers, and card manufacturers. As TSM system 120 may hold various
`
`information from various parties, the mobile device may interact with the TSM system
`
`10
`
`IS
`
`Apple Ex. 1002, p. 14
`Apple Ex. 1002, p. 14
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`individually rather than various discrete entities. Accordingly, the described TSM system 120
`
`may act as an integration point for all of the external parties the mobile device may deal with,
`
`providing for a seamless and more efficient operation of mobile services.
`
`[0034] A method for installing a mobile wal