Providing method of access card and apparatus for performing the method

Abstract

A method for providing an access card is disclosed. The method for providing an access card identifies a link or code of a card issuance page for an access card for entry into an online area or an offline area, accesses the card issuance page through the link or code of the card issuance page, requests the issuance of an access card on the card issuance page, and receives data regarding the access card. The access card is displayed through an application installed on a user terminal.

Description

Technology Field

[0001] The present invention relates to a method for providing an access card and an apparatus for performing said method. Background Technology

[0002] Users engage in various activities through online and offline domains. For example, a user may arrive at work at 9 a.m., tag their employee ID to enter the office, exercise at a fitness center by presenting their membership at 12 p.m., purchase a ticket on an online site at 6 p.m., chat with friends in a chat room at 7 p.m., and leave work at 9 p.m. to pass through the entrance of an apartment by tagging their access card.

[0003] In this situation, there may be a need to require users to possess specific credentials to gain access when logging in to the online realm or entering the offline realm. A method is required to collectively manage the access credentials necessary for various online or offline activities through user terminals. The problem to be solved

[0004] The present invention provides a method and apparatus that allows a user to more easily and conveniently obtain and manage access cards required for online or offline access through an application.

[0005] The present invention provides a method and apparatus for accessing a specific online or offline area related to a partner by managing an access card generated by a partner through an application installed on a user terminal, thereby enabling access through the necessary access card when accessing the partner. means of solving the problem

[0006] According to one embodiment, an access card provision method performed by a user terminal includes the steps of: identifying a link or code of a card issuance page for an access card for entry into an online area or an offline area; accessing a card issuance page through the link or code of the card issuance page; requesting the issuance of the access card on the card issuance page; and receiving data regarding the access card, wherein the access card is displayed through an application installed on the user terminal.

[0007] The above access card is a virtual card representing the qualification to enter the above online area or the above offline area set by the partner terminal, and can be issued and managed through the above application.

[0008] The above access card may be manufactured based on card information entered by the partner terminal.

[0009] The above user terminal can be issued different types of access cards produced by different partner terminals.

[0010] User information of a user terminal designated by a partner terminal is assigned to the access card, and the user information may include at least one of the phone number of the user terminal and a user account for the user terminal.

[0011] The above access card is assigned user information related to a user terminal that requested issuance within the number of access cards that can be issued as specified by the partner terminal, and the user information may include at least one of the phone number of the user terminal and a user account for the user terminal.

[0012] A validity condition is set on the access card, and the validity condition may include at least one of time information, type information, profile information, and authentication information associated with the access card.

[0013] An instant message related to the production of the access card may include (i) an instant message containing a notification that the production of the access card has been completed, or (ii) an instant message containing information about the access card, and may be provided to the partner terminal through a chat room identified by a business entity corresponding to the partner terminal or the access card production server.

[0014] The instant message related to the issuance of the access card includes an instant message containing a notification that the issuance of the access card has been completed, and may be provided to a partner terminal or a user terminal through a chat room identified by a business entity corresponding to a partner terminal or an access card issuance server.

[0015] If the partners corresponding to the partner terminal producing the access card can be expanded according to a hierarchical structure, the access card can be created based on the hierarchical structure.

[0016] According to one embodiment, an access card provision method performed by an access card management server comprises: generating a link or code for a card issuance page for an access card for entry into an online area or an offline area; receiving a request for issuance of the access card from a user terminal through the link or code; and providing data for the access card in response to the request for issuance of the access card, wherein the access card is displayed through an application installed on the user terminal.

[0017] The above access card may be manufactured based on card information received from a partner terminal.

[0018] The above access card may be a virtual card representing the qualification to enter the above online area or the above offline area set by the partner terminal.

[0019] The above user terminal can be issued different types of access cards produced by different partner terminals.

[0020] The access card is assigned user information of a user terminal designated by the partner terminal, and the user information may include at least one of the phone number of the user terminal and a user account for the user terminal.

[0021] The above access card is assigned user information related to a user terminal that has requested issuance within the number of access cards that can be issued as specified by the partner terminal, and the user information may include at least one of the phone number of the user terminal and a user account for the user terminal.

[0022] A validity condition is set on the access card, and the validity condition may include at least one of time information, type information, profile information, and proof information associated with the access card.

[0023] If the partners corresponding to the partner terminal producing the access card can be expanded according to a hierarchical structure, the access card can be created based on the hierarchical structure.

[0024] An instant message related to the production of the access card may include (i) an instant message containing a notification that the production of the access card has been completed or (ii) an instant message containing information about the access card, and may be provided to the partner terminal through a chat room identified as a business entity corresponding to the partner terminal or the access card production server.

[0025] The instant message related to the issuance of the access card includes an instant message containing a notification that the issuance of the access card has been completed, and may be provided to the partner terminal or the user terminal through a chat room identified by a business entity corresponding to the partner terminal or the access card issuance server. Effects of the invention

[0026] According to one embodiment of the present invention, access cards required for a user to access online or offline can be managed more easily and conveniently through an application.

[0027] According to one embodiment of the present invention, access cards issued by a plurality of partners are managed through an application, and access can be made through the necessary access card when accessing a specific online or offline area related to a partner. Brief explanation of the drawing

[0028] FIG. 1 is a diagram illustrating the operation of devices performing a method for providing an access card according to a first embodiment of the present invention. FIG. 2 is a diagram illustrating the process of providing an access card according to a first embodiment of the present invention. FIG. 3 is a flowchart illustrating the process of performing an access card provision method according to a first embodiment of the present invention. FIG. 4 is a diagram illustrating the operation of devices performing a method for providing an access card according to a second embodiment of the present invention. FIG. 5 is a diagram illustrating the process of providing an access card according to a second embodiment of the present invention. FIG. 6 is a flowchart illustrating the process of performing an access card provision method according to a second embodiment of the present invention. FIG. 7 is a diagram illustrating a partner management page accessed by a partner terminal according to an embodiment of the present invention. FIG. 8 is a drawing illustrating a card creation page accessed by a partner terminal according to an embodiment of the present invention. FIG. 9 is a drawing illustrating a card management page accessed by a partner terminal according to an embodiment of the present invention. FIG. 10 is a diagram illustrating an example of a user terminal accessing a card issuance page according to an embodiment of the present invention. FIG. 11 is a diagram illustrating an example in which a user terminal issues an access card through an application according to an embodiment of the present invention. FIG. 12 is a diagram illustrating an example in which a user terminal manages an access card through an application according to an embodiment of the present invention. FIG. 13 is a diagram illustrating an example of using an access card through a plurality of user terminals according to an embodiment of the present invention. FIG. 14 is a drawing illustrating an example of creating an access card corresponding to a partner package according to an embodiment of the present invention. Specific details for implementing the invention

[0029] Hereinafter, embodiments will be described in detail with reference to the attached drawings. However, the scope of the patent application is not limited or restricted by these embodiments. Identical reference numerals in each drawing indicate identical components.

[0030] Various modifications may be made to the embodiments described below. The embodiments described below are not intended to limit the forms of practice and should be understood to include all modifications, equivalents, and substitutions thereof.

[0031] Terms such as "first" or "second" may be used to describe various components, but these terms should be understood solely for the purpose of distinguishing one component from another. For example, a first component may be named a second component, and similarly, a second component may be named a first component.

[0032] The terms used in the embodiments are used merely to describe specific embodiments and are not intended to limit the embodiments. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as “comprising” or “having” are intended to indicate the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0033] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the embodiments pertain. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this application.

[0034] In addition, when describing with reference to the attached drawings, identical components are assigned the same reference numeral regardless of drawing symbols, and redundant descriptions thereof are omitted. When describing the embodiments, if it is determined that a detailed description of related prior art could unnecessarily obscure the essence of the embodiments, such detailed description is omitted.

[0035] Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

[0037] FIG. 1 is a diagram illustrating the operation of devices performing a method for providing an access card according to a first embodiment of the present invention.

[0038] Referring to FIG. 1, a partner terminal (101), an access card production server (102), an access card issuance server (103), a user terminal (104), and an application server (105) are illustrated. The partner terminal (101) can produce an access card through the access card production server (102) for access by a user who possesses the user terminal (104) online or offline. The production of the access card can be carried out through an access card production page provided by the access card production server (102).

[0039] Additionally, the access card may be provided to a user terminal (104) that accesses the access card issuance page provided by the access card issuance server (103). Alternatively, the access card may be provided through an application linked to the access card issuance server (103). In this case, the application is installed on the user terminal (104) and operates in conjunction with the application server (105), and may provide links or menus, etc., to enable the user terminal (104) to access the access card issuance page.

[0040] According to one embodiment of the present invention, a partner terminal (101) can provide a user terminal (104) with an access card, which is a virtual card corresponding to a valid identity, qualification, affiliated company, affiliated school, membership, access card, guarantee, business card, ticket, or admission ticket, without using offline means.

[0041] In FIG. 1, the access card production server (102), the access card issuance server (103), and the application server (105) may be operated by the same business entity or by different business entities.

[0042] An access card may refer to a virtual card containing information regarding qualifications for logging in to and entering a specific online area (e.g., a site, an application, etc.) related to a partner, or for entering a specific offline space (e.g., a building, etc.) related to a partner. An access card may refer to a virtual card for allowing access or entry of a user terminal (104) to an online or offline area related to a partner.

[0043] That is, the access card may be a virtual card that digitizes an identity, qualification, affiliated company, affiliated school, membership, access card, guarantee, business card, ticket, or admission ticket valid online or offline. The partner terminal (101) may produce an access card that is a virtual card that digitizes and displays an identity, right, qualification, ownership right, access authority, etc. verified online or offline in a cloud-type service.

[0044] Access cards can be classified into various types. For example, an access card may be a card used to prove identity or affiliation related to a partner, such as a student ID, employee ID, membership card, business card, or ID card. Alternatively, an access card may be an admission ticket for watching a performance, exhibition, or game related to the partner taking place at a specific time. An access card may be a membership or season ticket related to the partner valid for a specific area. Furthermore, an access card may refer to an access card for a building designated by the partner, or information used to authenticate the purchase or ownership of products or services related to the partner, such as a guarantee. The access cards described above refer to information that proves whether a user has the authority to access online or offline areas related to the partner, and are not limited to the examples described above.

[0045] For example, in order for a user to enter a chat room created by a partner, the user terminal (104) can obtain an access card, which is the authority to enter the chat room, through the card issuance page of the access card issuance server (103). As another example, in order for a user to visit a specific space (office) of a partner, the user terminal (104) can obtain an access card, which is the authority to enter and exit the office, through the card issuance page of the access card issuance server (103). The access card issued through the card issuance page of the access card issuance server (103) can be stored in at least one of the access card production server (102), the access card issuance server (103), the application server (105), or the user terminal (104).

[0046] The access card creation server (102) may provide an access card creation page, which is an interface that allows a partner terminal (101) that wishes to create an access card to create an access card after it has signed up and registered. The access card issuance server (103) may provide an access card issuance page, which is an interface that allows a user terminal (104) that wishes to issue an access card to issue an access card to connect. The user terminal (104) may access the access card issuance page through an application provided by the application server (105) and transmit a request for the issuance of an access card. Furthermore, after the issuance of the access card is completed, the user terminal (104) may manage the access card through the application. For example, the application may be a message application.

[0047] By having an access check device (not shown) connected to a partner terminal (101) check whether an access card exists for the user terminal (104), the user can enter a specific offline space associated with the partner. The user terminal (104) and the access check device may use a short-range wireless method (e.g., Bluetooth, NFC, etc.), or the access check device may read identification information (e.g., QR code) displayed on the user terminal (104), or the user terminal (104) may read identification information displayed on the access check device, thereby checking whether an access card exists in an application installed on the user terminal (104).

[0048] According to one embodiment of the present invention, access cards required for various online or offline activities of a user are managed through an application installed on a user terminal (104), thereby allowing convenient access to the user terminal (104).

[0050] FIG. 2 is a diagram illustrating the process of providing an access card according to a first embodiment of the present invention.

[0051] Referring to FIG. 2, the process of issuing an access card produced by the access card production server (102) to a user terminal (104) connected to the access card issuance server (103) is illustrated.

[0052] A partner terminal (101) associated with a partner can register the partner on a card creation page provided by an access card creation server (102) and create an access card associated with the partner. The card creation page can provide an interface that allows the partner terminal (101) to create an access card by registering information about the partner and inputting card information represented as an image or text.

[0053] The partner terminal (101) may use an application installed on the partner terminal (101) to access the card creation page. The partner terminal (101) may create an access card by inputting card information for creating an access card into the card creation page. The card information will be described in detail in FIG. 8.

[0054] When the access card is completed at the access card production server (102), an instant message containing a notification that the access card has been completed or information about the created access card based on card information may be provided to the partner terminal (101) through a message application. At this time, the message may be provided through a chat room identified as a business entity corresponding to the partner terminal (101) or a chat room identified as a business entity corresponding to the access card production server (102). The chat room identified as a business entity may be represented by the name or icon of the business entity.

[0055] An access card produced by an access card production server (102) can be provided to a user terminal (104) through a card issuance page provided by an access card issuance server (103). The card issuance page may be accessible via a link (URL) or a QR code. The link or QR code that allows access to the card issuance page may be provided directly to the user terminal (104) by a partner terminal (101) or provided to the user terminal (104) through the access card production server (102) or the access card issuance server (103).

[0056] The user terminal (104) accesses the card issuance page via a link or QR code that allows access to the card issuance page, and can receive the access card issued on the card issuance page through an application. A message indicating whether the access card has been issued can be provided to the partner terminal (101) through the application.

[0057] When the access card issuance is completed at the access card issuance server (103), an instant message including a notification that the access card has been issued may be provided to the partner terminal (101) or user terminal (104) through a message application. At this time, the message may be provided through a chat room identified as a business entity corresponding to the partner terminal (101) or a chat room identified as a business entity corresponding to the access card issuance server (103). The chat room identified as a business entity may be represented by the name or icon of the business entity.

[0058] An access card can be generated in correspondence with user information. User information is information for identifying a user and may include the phone number of the user terminal (104) or account information (ID) of an application installed on the user terminal (104).

[0059] The access card is stored in an application installed on the user terminal (104) or in an access card issuance server (103) other than the user terminal (104), and the user terminal (104) can check it through the application.

[0060] Access cards can be stored in various ways. For example, when an access card is generated by an access card production server (102), the access card may be stored in a secure storage area of ​​the access card production server (102) or the access card issuance server (103). In this case, consent from the user terminal (104) may be required for the access card to be stored in the secure storage area of ​​the access card production server (102) or the access card issuance server (103). In this case, the access card is not stored in the user terminal (104), and a list of access cards issued to the partner may be provided through an application installed on the user terminal (104). Subsequently, when accessing a specific area of ​​the partner online or offline through the user terminal (104), the user terminal (104) may download and store the access card from the secure storage area of ​​the access card production server (102) or the access card issuance server (103). Alternatively, when accessing a specific area of ​​a partner online or offline through a user terminal (104), the access card is not downloaded to the user terminal (104), and the existence of the access card stored in the secure storage area of ​​the access card production server (102) or access card issuance server (103) can be confirmed through user information corresponding to the access card.

[0061] As another example, when an access card is generated by an access card production server (102), the access card can be downloaded to a user terminal (104) and managed through an application. That is, the access card can be encrypted and stored in the storage area of ​​the user terminal (104). When accessing a specific area of ​​a partner online or offline through the user terminal (104), the existence of the access card can be verified by decrypting the encrypted access card through the certificate of the user terminal (104).

[0063] FIG. 3 is a flowchart illustrating the process of performing an access card provision method according to a first embodiment of the present invention.

[0064] In step (301), the partner terminal (101) can subscribe to the access card service through the partner management page provided by the access card production server (102). The information entered when subscribing to the access card service is specifically described in FIG. 7.

[0065] In step (302), the partner terminal (101) can provide card information to the card creation page provided by the access card creation server (102). The card information is described in detail in FIG. 8.

[0066] In step (303), the access card production server (102) can produce an access card based on card information entered by the partner terminal (101). The card information that the partner terminal (101) transmits to or registers to the access card production server (102) to create an access card is described in more detail in FIG. 8.

[0067] In step (304), the access card production server (102) can assign user information of the user terminal (104) to the access card. For example, if the access card is issued to a specific user terminal (104), user information can be assigned to the access card. Although not shown in FIG. 3, if the user terminal (104) to which the access card is issued is not specified, the number of access cards that can be issued on a first-come, first-served basis can be assigned to the access card.

[0068] In step (305), the access card creation server (102) can provide a link to a card issuance page for the access card to the partner terminal (101).

[0069] In step (306), the partner terminal (101) can provide a link to the card issuance page of the access card to the user terminal (104).

[0070] In step (307), the user terminal (104) can access the card issuance page of the access card and request the issuance of the access card from the access card issuance server (103).

[0071] In step (308), the access card issuing server (103) can request an access card from the access card production server (102).

[0072] In step (309), the access card production server (102) can provide data about the access card to the application server (105). The access card actually produced is stored in the access card production server (102), and data about the access card required to display the access card can be provided to the application server (105).

[0073] In step (310), the application server (105) can provide data about the access card to the user terminal (104).

[0074] In step (311), the user terminal (104) can display the access card through an application using data about the access card.

[0076] FIG. 4 is a diagram illustrating the operation of devices performing a method for providing an access card according to a second embodiment of the present invention.

[0077] FIG. 4 illustrates a case where the access card production server (102), access card issuance server (103), and application server (105) described in FIG. 1 are implemented through an access card management server (402), which is a single server. The access card management server (402) can perform the same operations as the access card production server (102), access card issuance server (103), and application server (105). The operation of the partner terminal (401) is the same as the operation of the partner terminal (101), and the operation of the user terminal (403) may be the same as the operation of the user terminal (104).

[0078] The partner terminal (101) can create an access card through the access card management server (402) for access by a user who possesses a user terminal (104) online or offline. The creation of the access card can be carried out through an access card creation page provided by the access card management server (402). Then, the access card can be provided through an application to a user terminal (403) who accesses the access card issuance page provided by the access card management server (402).

[0080] FIG. 5 is a diagram illustrating the process of providing an access card according to a second embodiment of the present invention.

[0081] Specifically, FIG. 5 illustrates the process in which an access card produced by the access card management server (402) of the partner terminal (401) is issued to a user terminal (403) connected to the access card management server (402).

[0082] A partner terminal (401) associated with a partner can register the partner on a card creation page provided by an access card management server (402) and create an access card associated with the partner. The card creation page can provide an interface that allows the partner terminal (401) to create an access card by registering information about the partner and inputting card information represented as an image or text. The card information that the partner terminal (401) transmits to or registers to the access card management server (402) to create an access card is described in more detail in FIG. 8.

[0083] The partner terminal (401) can use an application installed on the partner terminal (401) to access the card creation page. The partner terminal (401) can create an access card by inputting card information for creating an access card into the card creation page.

[0084] When the access card is completed at the access card management server (402), an instant message containing a notification that the access card has been completed or information about the created access card based on card information may be provided to the partner terminal (401) through a message application. At this time, the message may be provided through a chat room identified as a business entity corresponding to the partner terminal (401) or a chat room identified as a business entity corresponding to the access card management server (402). The chat room identified as a business entity may be represented by the name or icon of the business entity.

[0085] An access card produced by the access card management server (402) can be provided to a user terminal (403) through a card issuance page. The user terminal (403) can access the card issuance page through a link (URL) or a QR code. The link or QR code that allows access to the card issuance page can be provided directly to the user terminal (403) by the partner terminal (401) or provided to the user terminal (403) through the access card management server (402).

[0086] The user terminal (403) can access the card issuance page through a link or QR code that can access the card issuance page, and can receive the access card issued on the card issuance page through an application. A message indicating whether the access card has been issued can be provided to the partner terminal (401) through the application.

[0087] When the access card issuance is completed at the access card management server (402), an instant message including a notification that the access card has been issued may be provided to the partner terminal (401) or user terminal (403) through a message application. At this time, the message may be provided through a chat room identified as a business entity corresponding to the partner terminal (401) or a chat room identified as a business entity corresponding to the access card management server (402). The chat room identified as a business entity may be represented by the name or icon of the business entity.

[0088] When an access card is created, user information may be assigned to the access card. The user information is information for identifying the user and may include the phone number of the user terminal (403), account information (ID) of an application installed on the user terminal (403), or other user identification information (employee number / student number, etc.).

[0089] The access card is stored in an application installed on the user terminal (403) or in an access card management server (402) other than the user terminal (403), and the user terminal (403) can check it through the application.

[0091] FIG. 6 is a flowchart illustrating the process of performing an access card provision method according to a second embodiment of the present invention.

[0092] In step (601), the partner terminal (401) can subscribe to the access card service through the partner management page provided by the access card management server (402). The information entered when subscribing to the access card service is specifically described in FIG. 7.

[0093] In step (602), the partner terminal (101) can provide card information to the card creation page provided by the access card management server (402). The card information is described in detail in FIG. 8.

[0094] In step (603), the access card management server (402) can produce an access card based on the card information entered by the partner terminal (401).

[0095] In step (604), the access card management server (402) may assign user information of the user terminal (403) to the access card. For example, if the access card is issued to a specific user terminal (403), user information may be assigned to the access card. Although not shown in FIG. 6, if the user terminal (403) to which the access card is issued is not specified, the number of access cards that can be issued on a first-come, first-served basis may be assigned to the access card.

[0096] In step (605), the access card management server (402) can provide a link to a card issuance page for the access card to the user terminal (403).

[0097] In step (606), the user terminal (403) can access the card issuance page of the access card and request the issuance of the access card from the access card management server (402).

[0098] In step (607), the access card management server (402) can check the access card requested for issuance by the user terminal (403).

[0099] In step (608), the access card management server (402) may provide data about the access card to the user terminal (403). The access card actually manufactured may be stored in the access card management server (402), and data about the access card required to display the access card may be provided to the user terminal (403). Alternatively, the data about the access card may be stored in the user terminal (403).

[0100] In step (609), the user terminal (104) can display the access card through an application using data about the access card.

[0102] The partner management page and card creation page described in FIGS. 7 through 14 may be provided by an access card creation server (102) or an access card management server (402). Additionally, the card issuance page may be provided by an access card issuance server (103) or an access card management server (402). The description of FIGS. 7 through 14 is to describe the partner terminal (101) and the user terminal (104).

[0104] FIG. 7 is a diagram illustrating a partner management page accessed by a partner terminal according to an embodiment of the present invention.

[0105] The partner management page illustrated in FIG. 7 may refer to a page for managing an access card after the partner terminal (101) has signed up to produce an access card or has signed up.

[0106] The partner terminal (101) may register the partner's name and administrator information to produce an access card. In addition, according to an embodiment of the present invention, billing may be performed for the issuance of an access card. Account information for the partner may be set for billing purposes. Account information may include a charged amount, an access card issuance cost, the number of access cards issued, and a current balance. The charged amount refers to the amount charged by the partner to issue an access card. The access card issuance cost may refer to the amount consumed each time one access card is issued. The access card issuance cost may vary depending on the type of access card and the number of access cards issued. The current balance may refer to the amount obtained by subtracting the amount obtained by multiplying the access card issuance cost and the number of issuances from the charged amount.

[0107] The access card list refers to a list of access cards produced by the partner terminal (101). The access card list may provide a menu for viewing or editing the classification of the access cards, the validity period, the number of productions, the number of issuances, and the details of the access cards.

[0108] Each item shown in Fig. 7 is merely an example, and additional items related to the access card may be added.

[0110] FIG. 8 is a drawing illustrating a card creation page accessed by a partner terminal according to an embodiment of the present invention.

[0111] FIG. 8 illustrates a card creation page provided by an access card creation server (102) or an access card management server (402). The following description describes the operation between the partner terminal (101) and the access card creation server (101), but the following descriptions may also apply equally to the operation between the partner terminal (401) and the access card management server (402). The card creation page of FIG. 8 is a page that the partner terminal (101) can access, and can be configured for each access card that the partner terminal (101) intends to create. The interface for creating an access card is not limited to FIG. 8.

[0112] For example, card information that is input or registered by a partner terminal (101) to produce an access card may be produced based on at least one of the following information. The card information described below is an example and the present invention is not limited thereto.

[0113] (1) Information on the issuance target for the access card (e.g., phone number of the user terminal (104), application ID of the user terminal (104), personal identification information related to the user of the user terminal (104) (e.g., student ID or employee ID))

[0114] (2) Information on the number of issuances for the access card (the number of issuances can be set when there is no information on the issuance target for the user terminal (104))

[0115] (3) Application identification information of a business entity corresponding to a partner terminal (101) (e.g., identification information (ID) of an official account associated with the business entity of the partner terminal (101) in a message application),

[0116] (4) Information about the access terminal (101),

[0117] (5) Types of access cards (e.g., access card, student ID, membership card, etc.),

[0118] (6) Access card expiration date information

[0119] (7) Conditions regarding whether the access card is reclaimable, transferable, reassignable, transferable, or reassignable (e.g., at least one of the pre-processing requirements, time requirements, geographical requirements, and personal requirements for transfer or reassignment)

[0120] (8) Points where the access card can be used (e.g., in the case of a chain, only at specific chain stores) or the geographical area where it can be used

[0121] (7) Connection information to a third-party server connected to the access card (for example, when borrowing books using a student ID as an access card, it is linked to the library server to check the borrowing status of the user holding the student ID)

[0122] (8) Display information for the access card (e.g., at least one of the name, image or color, hologram, logo, and text data registered by the partner terminal (101) for the access card)

[0123] The access card creation page can provide an interface that allows editing the front and back of the access card, just as if it were a physical card. The information entered on the access card creation page may vary depending on the type of access card.

[0124] For example, the front of the access card may display information indicating the user of the user terminal (104) (name, photo, nickname, email address, affiliation, etc.) and the name of the access card. Additionally, detailed information that varies depending on the type of access card may be entered on the back of the access card. If the access card is an access pass, the back of the access card may include the location accessed via the access card, the recipient of the access card (the user of the user terminal (104)), and the validity period of the access card.

[0125] Additionally, detailed information regarding the access card may be entered. For example, settings such as how to use the access card, precautions when using the access card, a menu for requesting the reissuance of the access card, and a menu for requesting the return of the access card may be additionally entered by the partner terminal (101).

[0127] FIG. 9 is a drawing illustrating a card management page accessed by a partner terminal according to an embodiment of the present invention.

[0128] The card management page of Fig. 9 is a page that the partner terminal (101) can access, and can be configured for each access card produced by the partner terminal (101).

[0129] The card management page is a page for providing information regarding the issuance of an access card to a partner terminal (101) after the access card has been produced. The card management page may include the issuance period of the access card, an issuance link (URL, QR code, etc.), the issuance status of the access card, the number of access card issuance targets, and the issuance history of the access card.

[0130] If the issued link is in the form of a URL, the partner terminal (101) can copy the issued link and provide it to the user terminal (104) through an application. Also, if the issued link is a QR code, it can be provided to the partner terminal (101) so that the user terminal (104) can scan and recognize it.

[0131] In the case where the partner terminal (101) produces N access cards, user information (e.g., a user account of an application or a phone number of a user terminal (104)) may be assigned when the access card is issued. However, if the access card is not assigned to a specific user terminal but is issued on a first-come, first-served basis, the user information included in the issuance history may be assigned when the access card is actually issued to the user terminal (104) after the access card has been produced.

[0132] The issuance and retrieval status of access cards can be verified through the issuance history. The number of pending access card issuances may refer to the number of eligible candidates minus the number of issued cards.

[0134] FIG. 10 is a diagram illustrating an example of a user terminal accessing a card issuance page according to an embodiment of the present invention.

[0135] FIG. 10A illustrates a case where a link to an access card issuance page is transmitted through an application installed on a user terminal (104) to obtain an access card. For example, a link to obtain an access card may be provided to the user terminal (104) through a message application. In this case, the link may be provided through a chat room identified as a business entity corresponding to the partner terminal (101) or a chat room identified as a business entity corresponding to the access card production server (102). A chat room identified as a business entity may be represented by the name or icon of the business entity.

[0136] And, when a link to obtain an access card through a chat room is provided to a user terminal (104), the user terminal (104) providing the link through the chat room can be linked to the access card. For example, identification information of the application of the user terminal (104) (e.g., ID) and identification information of the user terminal (104) (e.g., phone number) can be mapped to the access card.

[0137] When a user terminal (104) selects a menu called "Get Issued," the user terminal (104) can access a card issuance page through a link to the card issuance page connected to the menu and transmit a request for the issuance of an access card.

[0138] Figure 10B illustrates a case where the user terminal (104) accesses a card issuance page by recognizing a QR code displayed on the partner terminal (101) or displayed online (e.g., webpage) or offline (e.g., kiosk, wall, etc.) through an application installed on the user terminal (104).

[0139] That is, with reference to FIG. 10, the user terminal (104) can request the issuance of an access card produced by the partner terminal (101) by accessing the card issuance page provided by the access card issuance server (103) by selecting a URL through an application or by recognizing a QR code.

[0141] FIG. 11 is a diagram illustrating an example in which a user terminal issues an access card through an application according to an embodiment of the present invention.

[0142] Referring to FIG. 11(A), when an access card is created by the partner terminal (101) through the access card creation server (102), the user terminal (104) can request the issuance of the access card through an application. And when the access card is issued, a notification message related to the card issuance can be provided through the application.

[0143] For example, if the application is a messenger application, a message containing the fact that an access card has been issued may be provided to the partner terminal (101) or the user terminal (104) in a chat room associated with the partner terminal (101) or the access card issuance server (103). In this case, the user terminal (104) can check the access card through the application. When data regarding the access card is provided to the user terminal (104) through the access card issuance server (104), the user terminal (104) can display the access card using the data regarding the access card through the application.

[0144] Referring to FIG. 11(B), an interface may be provided in a specific function (e.g., an access card wallet) of an application installed on the user terminal (104) to manage access cards corresponding to partners, such as viewing, deleting, and editing. The user terminal (104) may receive multiple access cards of different types produced by different partner terminals (101) through the application. Additionally, the user terminal (104) may manage multiple access cards of different types produced by different partner terminals (101) through the interface illustrated in FIG. 11(B). A list of access cards is provided through the application installed on the user terminal (104). Additional information may be assigned to each of the access cards.

[0145] For example, when an access card is created in correspondence with user information, additional information related to the conditions for the access card to operate or be valid may be additionally set. For example, the additional information may include time information, type information, profile information, authentication information, etc., related to the access card.

[0146] Time information may refer to the start and end times for the access card to be valid. Type information may refer to whether the access card is one-time use or semi-permanent through reissuance, whether it can be shared or transferred to others, and information regarding how the access card is used. Profile information may relate to the user's personal details, such as region, age, gender, and affiliation. Certification information may relate to qualifications essential for the user's online or offline activities, such as vaccination status, license possession, or membership status.

[0148] FIG. 12 is a diagram illustrating an example in which a user terminal manages an access card through an application according to an embodiment of the present invention.

[0149] Referring to FIGS. 12(A) and FIGS. 12(B), the result of displaying an access card through an application of a user terminal (104) is shown. FIGS. 12(A) shows the front side of the access card described in FIGS. 8, and FIGS. 12(B) may correspond to the back side of the access card described in FIGS. 8.

[0150] Referring to FIG. 12(A), partner information and user information related to the issuance of an access card may be provided in the application of the user terminal (104). Additionally, menus for returning and discarding the access card or extending its validity period may be provided through a display screen. User information may refer to information for identifying the user, such as the user's name, photo, affiliation, nickname, or email address of the user possessing the user terminal (104).

[0151] Referring to FIG. 12(B), information necessary for using the access card may be provided on the back of the access card. For example, as shown in the display screen in FIG. 12(B), the validity period of the access card (issue date and expiration date), a display menu of identification information corresponding to the access card (e.g., QR code), detailed information related to the partner who created the access card (e.g., issuer), and location information where the access card can be used (e.g., entry point) may be provided.

[0153] FIG. 13 is a diagram illustrating an example of using an access card through a plurality of user terminals according to an embodiment of the present invention.

[0154] Referring to FIG. 13, a method for providing access cards is provided when a user owns multiple user terminals. Here, the same application may be installed on the user terminals. And, a list of access cards may be provided through the application installed on each of the user terminals.

[0155] For example, each user terminal owned by the same user (e.g., user k) can have the same user information (e.g., user account) set up through an application. Then, the list of access cards displayed through the application installed on each user terminal can also be provided identically.

[0156] As another example, each user terminal owned by the same user (e.g., User k) may have the same user information (e.g., user account) set through an application. However, the list of access cards displayed through the application installed on each user terminal may be provided differently for each user terminal.

[0157] For example, the list of access cards may be provided differently based on the type of user terminals set by the partner who created the access card (e.g., whether it is a smartphone, tablet PC, wearable device, etc.), the frequency of use of the user terminals, the priority set for the user terminals, and the attributes of the user terminals (screen size, communication support method, etc.).

[0159] FIG. 14 is a drawing illustrating an example of creating an access card corresponding to a partner package according to an embodiment of the present invention.

[0160] A partner terminal (101) that manufactures an access card may be associated with partner X. In this case, if there are lower-level partners X-1 to XN in partner X, the partner terminal (101) may manufacture an access card for partner X in the form of a partner's package.

[0161] For example, if Partner X is a specific university and Partner X-1 to Partner XN correspond to colleges located within that specific university, when the Partner Terminal (101) produces an access card (e.g., access pass) for Partner X for the User Terminal (104), the access cards for Partner X-1 to Partner XN, which belong to the lower layer of Partner X, may also be produced together.

[0162] At this time, only information about the access card of Partner X, which is an upper layer, may be provided to the application installed on the user terminal (104), or information about the access card of Partner X and the access card of Partner X-1 to Partner XN, which are lower layers of Partner X, may also be provided together.

[0163] When partners are hierarchically organized, when an access card for a partner in the upper tier is created, an access card for a partner in the lower tier can be automatically created on a partner package basis. In this case, the hierarchical relationship for the partners can be entered at the partner terminal (101). Additionally, an access card corresponding to a partner in the lower tier can be created independently of the access card corresponding to a partner in the upper tier. For example, as illustrated in FIG. 8, the information entered when creating an access card corresponding to a partner in the upper tier on the card creation page and the information entered when creating an access card corresponding to a partner in the lower tier can be set differently.

[0165] Meanwhile, the method according to the present invention is written as a program executable on a computer and can also be implemented on various recording media such as magnetic storage media, optical reading media, and digital storage media.

[0166] Implementations of the various technologies described herein may be implemented as digital electronic circuits, or as computer hardware, firmware, software, or combinations thereof. Implementations may be implemented as computer program products, i.e., computer programs tangibly embodied in information carriers, such as machine-readable storage devices (computer-readable media) or radio signals, for processing by the operation of data processing devices, e.g., programmable processors, computers, or multiple computers, or for controlling such operation. Computer programs such as the computer program(s) described above may be written in any form of programming language, including compiled or interpreted languages, and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. Computer programs may be deployed to be processed on one computer or multiple computers at one site, or distributed across multiple sites and interconnected by a communication network.

[0167] Processors suitable for processing computer programs include, for example, both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Generally, the processor will receive instructions and data from read-only memory or random access memory, or both. The elements of the computer may include at least one processor that executes instructions and one or more memory devices that store instructions and data. Generally, the computer may include one or more mass storage devices that store data, for example, magnetic, magneto-optical disks, or optical disks, or may be combined to receive data from these, transmit data to these, or both. Information carriers suitable for embodying computer program instructions and data include, for example, semiconductor memory devices, magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs (Compact Disk Read Only Memory) and DVDs (Digital Video Disks); magneto-optical media such as floptical disks; ROMs (Read Only Memory); RAMs (Random Access Memory); flash memory; EPROMs (Erasable Programmable ROM); EEPROMs (Electrically Erasable Programmable ROM); etc. Processors and memory may be supplemented by or included in special-purpose logic circuit organizations.

[0168] Additionally, a computer-readable medium may be any available medium accessible by a computer and may include both computer storage media and transmission media.

[0169] Although this specification contains details of a number of specific embodiments, they should not be understood as limiting the scope of any invention or claimables, but rather as descriptions of features that may be characteristic of a specific embodiment of a specific invention. Specific features described in this specification in the context of individual embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any appropriate sub-combination. Furthermore, while features may operate in a specific combination and be described as initially claimed, one or more features from the claimed combination may be excluded from the combination in some cases, and the claimed combination may be changed to a sub-combination or a variation of the sub-combination.

[0170] Likewise, although operations are depicted in the drawings in a specific order, this should not be understood as requiring that such operations be performed in that specific or sequential order depicted to obtain a desirable result, or that all depicted operations must be performed. In certain cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various device components of the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and devices can generally be integrated together into a single software product or packaged into multiple software products.

[0171] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to aid understanding and are not intended to limit the scope of the present invention. It is obvious to those skilled in the art that other variations based on the technical concept of the present invention are possible in addition to the embodiments disclosed herein. Explanation of the symbols

[0172] 101: Partner Terminal 102: Access Card Production Server 103: Access Card Issuance Server 104: User terminal 105: Application Server

Claims

Claim 1 A method for providing an access card performed by a user terminal, comprising: identifying a link or code of a card issuance page for an access card for entry into an online area or an offline area; accessing a card issuance page through the link or code of the card issuance page; requesting the issuance of the access card on the card issuance page; and receiving data regarding the access card, wherein, through an application installed on the user terminal, i) a link to obtain the access card is transmitted, ii) the access card is displayed, and iii) an interface to manage the access card is provided, and through the interface, a plurality of access cards of different types manufactured by different partner terminals are managed. Claim 2 A method for providing an access card, wherein, in claim 1, the access card is a virtual card representing the qualification to enter the online area or the offline area set by the partner terminal. Claim 3 A method for providing an access card according to claim 1, wherein the access card is manufactured based on card information entered by a partner terminal. Claim 4 A method for providing access cards according to claim 1, wherein the user terminal can receive different types of access cards produced by different partner terminals. Claim 5 A method for providing an access card according to claim 1, wherein user information of a user terminal designated by a partner terminal is assigned to the access card, and the user information includes at least one of a phone number of the user terminal and a user account for the user terminal. Claim 6 A method for providing an access card according to claim 1, wherein the access card is assigned user information related to a user terminal that has requested issuance within the number of access cards that can be issued as specified by a partner terminal, and the user information includes at least one of a telephone number of the user terminal and a user account for the user terminal. Claim 7 A method for providing an access card according to claim 1, wherein a valid condition is set on the access card, and the valid condition includes at least one of time information, type information, profile information and proof information associated with the access card. Claim 8 A method for providing an access card according to claim 1, wherein the instant message related to the production of the access card comprises (i) an instant message including a notification that the production of the access card is complete, or (ii) an instant message including information about the access card, and is provided to the partner terminal through a chat room identified by a business entity corresponding to the partner terminal or the access card production server. Claim 9 A method for providing an access card according to claim 1, wherein the instant message related to the issuance of the access card includes an instant message including a notification that the issuance of the access card has been completed, and is provided to a partner terminal or a user terminal through a chat room identified by a business entity corresponding to a partner terminal or an access card issuance server. Claim 10 A method for providing an access card according to claim 1, wherein, if a partner corresponding to a partner terminal producing the access card can be expanded according to a hierarchical structure, the access card is created based on the hierarchical structure. Claim 11 A method for providing an access card performed by an access card management server, comprising: generating a link or code for a card issuance page for an access card for entry into an online area or an offline area; receiving a request for issuance of the access card from a user terminal through the link or code; and providing data for the access card in response to the request for issuance of the access card, wherein, through an application installed on the user terminal, i) a link to obtain the access card is transmitted, ii) the access card is displayed, and iii) an interface to manage the access card is provided, and through the interface, a plurality of access cards of different types manufactured by different partner terminals are managed. Claim 12 A method for providing an access card according to claim 11, wherein the access card is manufactured based on card information received from a partner terminal. Claim 13 A method for providing an access card according to claim 11, wherein the access card is a virtual card representing the qualification to enter the online area or the offline area set by the partner terminal. Claim 14 In claim 11, the method of providing access cards, wherein the user terminal can receive different types of access cards produced by different partner terminals. Claim 15 A method for providing an access card according to claim 11, wherein the access card is assigned user information of a user terminal designated by a partner terminal, and the user information includes at least one of a phone number of the user terminal and a user account for the user terminal. Claim 16 A method for providing an access card according to claim 11, wherein the access card is assigned user information related to a user terminal that has requested issuance within the number of access cards that can be issued specified by a partner terminal, and the user information includes at least one of the phone number of the user terminal and a user account for the user terminal. Claim 17 A method for providing an access card according to claim 11, wherein a valid condition is set on the access card, and the valid condition includes at least one of time information, type information, profile information, and proof information associated with the access card. Claim 18 In claim 11, if the partner corresponding to the partner terminal producing the access card can be expanded according to a hierarchical structure, the access card is an access card providing method created based on the hierarchical structure. Claim 19 A method for providing an access card according to claim 11, wherein an instant message related to the production of the access card comprises (i) an instant message including a notification that the production of the access card has been completed or (ii) an instant message including information about the access card, and is provided to the partner terminal through a chat room identified as a business entity corresponding to the partner terminal or the access card production server. Claim 20 A method for providing an access card according to claim 11, wherein the instant message related to the issuance of the access card includes an instant message including a notification that the issuance of the access card has been completed, and is provided to the partner terminal or the user terminal through a chat room identified by a business entity corresponding to the partner terminal or the access card issuance server.

Images