WO2022173464A1

WO2022173464A1 - Inviting users to cloud platforms

Info

Publication number: WO2022173464A1
Application number: PCT/US2021/046441
Authority: WO
Inventors: JinKyu Kook; Min NAMGOONG; ByeongJu HWANG; Seonae Park; Junghun Kim
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2021-02-09
Filing date: 2021-08-18
Publication date: 2022-08-18
Also published as: KR20220114990A

Abstract

According to an example, a cloud platform server includes a processor and a memory to store instructions. When executed, the instructions cause the processor to register apparatus information to be used in a first cloud platform, request user information associated with an apparatus from a second cloud platform on the basis of the apparatus information, receive the user information from the second cloud platform, and transmit a request to sign up for the first cloud platform to a user on the basis of the user information.

Description

INVITING USERS TO CLOUD PLATFORMS

BACKGROUND

[0001] There exist many different types of image forming apparatuses, including printers, scanners, photocopiers, facsimile machines, etc., and also multi-function printers (MFPs) that act as all-in-one devices to provide a combination of, e.g., printing, copying, scanning, and faxing functions.

[0002] An image forming apparatus may provide various kinds of services through a cloud platform. A user may register an image forming apparatus in a cloud platform and may use a service such as a consumable delivery service, a camera scanning service, a voice printing service, a mobile faxing service, etc. of the cloud platform

[0003] In order to provide a service to an image forming apparatus, a cloud platform may check user information of a user allowed to use the image forming apparatus, apparatus information of the image forming apparatus, and service contract information on a service available through the image forming apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 is a schematic diagram of a system including an image forming apparatus and a cloud platform according to an example;

[0005] FIG. 2 is a schematic diagram of an environment in which an image forming apparatus is used in a new cloud platform according to an example; [0006] FIG. 3 is a schematic diagram of an environment in which an image forming apparatus may be used in a cloud platform according to an example; [0007] FIG. 4 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example;

[0008] FIG. 5 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example;

[0009] FIG. 6 is a sequence diagram illustrating an operation of creating a new user account in a cloud platform according to an example; [0010] FIG. 7 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example;

[0011] FIG. 8 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example;

[0012] FIG. 9 i illustrates a cloud platform sign-up request provided to a user according to an example;

[0013] FIG. 10 is a block diagram conceptually showing a cloud platform server according to an example; and

[0014] FIG. 11 illustrates a computer-readable recording medium including instructions to perform a method according to an example.

DETAILED DESCRIPTION

[0015] A user may receive various services related to an image forming apparatus through a cloud platform (which is also referred to as a legacy platform) of the related art. However, depending on the situation, a cloud platform other than the cloud platform of the related art may be introduced. In this case, in order to provide a service to a user through a new cloud platform, the user should be invited to the new cloud platform for a process of registering information that may be used to provide the service (e.g., apparatus information, user information, contract information, etc.) because of the change of the cloud platform. Therefore, a separate sign-up procedure may be executed for the user to use the new cloud platform. Transferring user information or the like used in a cloud platform of the related art to a new cloud platform without user consent may not be allowed according to various regulations.

[0016] Accordingly, an example is to provide a continuous service regardless of whether a cloud platform is changed.

[0017] An example method invites a user to a new cloud platform. According to an example, after apparatus information to be used in a new cloud platform is registered, user information mapped to the corresponding apparatus information stored in the cloud platform of the related art is acquired based on the apparatus information, and a request to sign up for the new cloud platform is transmitted to the corresponding user on the basis of the acquired user information. Therefore, an apparatus may be newly connected to the new cloud platform and the sign-up request may be transmitted to a user who has authority to use the apparatus. The user may receive a service of the new platform without a separate sign-up procedure by responding to the sign-up request.

[0018] Various terms used in the following examples are chosen from a terminology of commonly used terms in consideration of their function herein, which may be appreciated differently depending on an implementation, a precedent case, or an emerging new technology. In certain instances, some terms are to be construed as set forth in the detailed description. Accordingly, the terms used herein are to be defined consistently with their meanings in the context of the present disclosure, rather than simply by their plain and ordinary meaning. [0019] The terms “comprising,” “including,” “having,” “containing,” etc. are used herein to describe the presence of the elements listed thereafter. Unless otherwise indicated, these terms and variations thereof are not meant to exclude the presence or addition of other elements.

[0020] As used herein, ordinal terms such as “first,” “second,” and so forth are meant to identify several similar elements. Unless otherwise described, such terms are not intended to impose limitations, e.g., a particular order of these elements or of their use, but rather are used merely for referring to multiple elements separately. For instance, an element may be referred to in an example with the term “first” while the same element may be referred to in another example with a different ordinal number such as “second,” “third,” etc. In such examples, such ordinal terms are not to limit the scope of the present disclosure. Also, the use of the term “and/or” in a list of multiple elements is inclusive of all possible combinations of the listed items, including any one or plurality of the items.

[0021] The term “image forming job” as used herein may encompass any of a variety of image-related jobs, such as a print job, a scan job, a photocopy job, a facsimile job, and the like, that involve an operation of forming an image and/or other processing operation, e.g., creation, generation, and/or transfer of an image file. Furthermore, an image forming job performed by an image forming apparatus may comprise various jobs related to printing, photocopying, scanning, faxing, storing, transmitting, coating, etc.

[0022] The term “image forming apparatus” as used herein may encompass any of a variety of apparatuses, such as printers, scanners, photocopiers, facsimile machines, multi-function printers (MFPs), display devices, and so on, that carry out an image forming job. Moreover, an image forming apparatus may be a two-dimensional (2D) or three-dimensional (3D) image forming apparatus. Such an image forming apparatus can provide basic functions such as photocopying, printing, scanning, etc., as well as various additional functions.

[0023] The term “user” as used herein may refer to a person who manipulates an image forming apparatus to perform an image forming job. Further, the term “administrator” as used herein may refer to a person who has access to the entire functionality of an image forming apparatus. In some examples, one person may have both the roles of an administrator and a user. [0024] The term “electronic device,” “electronic apparatus,” “user device,” and the like as used herein may refer to an information processing device that can be used by a user, such as a computer, a lap top, a tablet PC, a mobile phone, etc.

[0025] Certain examples will now be described with reference to the accompanying drawings. The present disclosure should not be construed as limited to the examples set forth herein. Rather, these examples are given in order to provide a better understanding of the scope of the present disclosure.

[0026] hereinafter, examples will be described with reference to the accompanying drawings.

[0027] FIG. 1 is a schematic diagram of a system including an image forming apparatus and a cloud platform according to an example. The example system of FIG. 1 includes an image forming apparatus 100, a legacy cloud platform 200, and a new cloud platform 300. A user may use the image forming apparatus 100 directly or through connection to a desktop, a laptop, a mobile apparatus, etc. The image forming apparatus 100 may be connected to a cloud platform to receive a service through the cloud platform. For example, the service that may be provided through the cloud platform may include mobile fax, printing, camera scan, consumable delivery service, etc., but the examples are not limited thereto. In order to provide a service to the image forming apparatus 100 through such a cloud platform, the cloud platform may manage user information (e.g., a user identifier, user contact information, etc.), apparatus information (e.g., an apparatus identifier of the image forming apparatus registered by the user, etc.), sign-up service information (e.g., service list information on a list of services that may be received by the user through the apparatus), etc.

[0028] In order to receive a service from the cloud platform, the image forming apparatus 100 may be connected to an existing cloud platform, for example, the legacy cloud platform 200. Also, the new cloud platform 300 may be introduced in addition to the legacy cloud platform 200. This new cloud platform 300 may be introduced, for example, to provide a new service that was not provided in the legacy cloud platform 200 or to upgrade the performance of a cloud platform.

[0029] In order to use a new service, a user may directly access the new cloud platform 300 through the image forming apparatus 100. For example, the user may access the new cloud platform 300 through a portal for accessing the new cloud platform 300 (e.g., a website, an application, or the like that a user can access to use a service, etc.) and may perform a procedure such as user sign up, service sign-up, and apparatus registration to register and use the apparatus in the new cloud platform 300.

[0030] Alternatively, the user may access the new cloud platform 300 through the legacy cloud platform 200. For example, the user may receive a service by accessing a portal that provides a cloud service for the image forming apparatus 100 without knowing which cloud platform he or she is accessing. In this case, the user checks and receives the provided service, and is not aware of which cloud platform his or her image forming apparatus 100 is accessing, for example, whether the image forming apparatus 100 is accessing the legacy cloud platform 200 or the new cloud platform 300.

[0031] In the latter scenario, in order to provide a service to a user through the new cloud platform 300, the new cloud platform 300 may require a sign-up procedure for the new cloud platform 300 and may receive user information to be used for the sign-up procedure from the legacy cloud platform 200. However, transferring the user's sign-up information to the new cloud platform 300 without the user's consent may be undesirable in consideration of various regulations such as the Personal Information Protection Act. Therefore, in order to smoothly provide a new service through the new cloud platform 300, information may be received from the legacy cloud platform 200 while minimizing a cumbersome sign-up procedure for a user. This can be achieved by example techniques described below herein.

[0032] FIG. 2 is a schematic diagram of an environment in which an image forming apparatus is used in a new cloud platform according to an example. According to an example, a user may use an image forming apparatus in an office, and the image forming apparatus may be connected to the legacy cloud platform 200 to provide a service. Thus, as the user uses the image forming apparatus registered in the legacy cloud platform 200, he or she may receive the service, for example, a service for replacing a consumable such as a toner, a shared printing service, or the like through the legacy cloud platform 200. In this case, apparatus information of the image forming apparatus and user information of the user authorized to use the image forming apparatus are registered in the legacy cloud platform 200.

[0033] In an example, the user may bring the image forming apparatus that had been used in the office to his or her home and use the apparatus to work from home. The image forming apparatus moved to the home and used to work from home may be connected to the new cloud platform 300 to receive a service through the cloud platform while working from home. As the image forming apparatus is connected to the new cloud platform 300, the user may wish to receive a service through the cloud platform such as, for example, the consumable replacement service, the shared printing service, or the like, as in the office. To this end, a sign-up procedure such as user sign-up and apparatus registration in the new cloud platform 300 should be completed so that the image forming apparatus moved to the environment of the new cloud platform 300 may be connected to the new cloud platform 300 to receive a service that can be provided to the image forming apparatus (e.g., a service that can be provided according to a contract between a company to which the user belongs and a cloud platform provider). Based on the image forming apparatus being newly connected to the new cloud platform 300 by an example method, the new cloud platform 300 can cooperate with the legacy cloud platform 200 so that the user can receive a service through the new cloud platform 300 without a cumbersome sign-up procedure.

[0034] FIG. 3 is a schematic diagram of an environment in which an image forming apparatus may be used in a cloud platform according to an example. In an example, a user may access a portal that provides a service so as to use a cloud platform service for an image forming apparatus. In an example, it is sufficient for a user to access the portal and use the service, and there is no need for the user to select a cloud platform to be connected to for providing the service. Therefore, the user may be provided with a service, through the portal, by the legacy cloud platform 200 or the new cloud platform 300. The environment shown in FIG. 3 is an example, and various modifications are possible in which a user can receive a service through a cloud platform.

[0035] FIG. 4 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example.

[0036] In operation S400, the legacy cloud platform 200 receives a contract-based request for registration for use from a contractor. The use registration request may be submitted via a portal (not shown) to access the cloud platforms 200 and/or 300. As described above, a user or a contractor of an image forming apparatus who receives a service through the cloud platform, for example, may enter a website address and use a service through the portal even if he or she is not aware of which cloud platform he or she is accessing. Based on the new cloud platform 300 being used to process the request received from the user through the portal, the user may be invited to the new cloud platform 300 without a separate sign-up procedure through an example technique described herein. [0037] Flere, a contractor refers to an entity that makes a contract with a cloud platform provider in order to receive a service through a cloud platform for an image forming apparatus. For example, the contractor may be an organization that makes a contract with the cloud platform provider so as to rent an image forming apparatus and receive a predetermined service (e.g., a consumable replacement service, but the examples are not limited thereto) through the rented image forming apparatus. For example, the organization may be a company, and the contract may be made for the use of a predetermined number of image forming apparatuses by employees belonging to the company, but the examples are not limited thereto. For example, the contractor may be an individual user who uses an image forming apparatus.

[0038] The contract-based request for registration for use may include contract information for use of the new cloud platform 300. For example, the contract information may include information that is used to provide a service through the cloud platform, which includes information such as information on a list of image forming apparatuses that have been signed up for the new cloud platform 300 and information on authority for a service to be provided to each image forming apparatus. As a non-limiting example, contract information may be information related to the contract for providing a service through a cloud platform based on an image forming apparatus that was previously used in a company being moved to a home for working from home and used there. Flowever, contract information may not include information on a user authorized to use an image forming apparatus. This may include a situation in which a user who will use an image forming apparatus is not determined in advance or a situation in which a user's personal identification information cannot be provided without the user’s consent, but the examples are not limited thereto.

[0039] In operation S410, based on the legacy cloud platform 200 receiving the request for registration for use based on the contract information from the contractor, the legacy cloud platform 200 extracts apparatus information of an apparatus that has sent the registration for a cloud platform service from the request for registration for use and sends the apparatus information to the new cloud platform 300. The apparatus information may include an apparatus identifier (e.g., a serial number (S/N), a universally unique identifier (UUID), etc.) for identifying each image forming apparatus.

[0040] In operation S420, the new cloud platform 300 receives the apparatus information and requests user information associated with the apparatus corresponding to the apparatus information from the legacy cloud platform 200 on the basis of the received apparatus information. For example, the new cloud platform 300 transmits the apparatus identifier of the apparatus information to the legacy cloud platform 200 and requests user information of a user who is allowed to use the apparatus corresponding to the apparatus identifier in the legacy cloud platform 200. If the corresponding apparatus is an apparatus registered and used in the legacy cloud platform 200, the user information of the user allowed to use the corresponding apparatus has been registered in the legacy cloud platform 200. The user information may include the user’s contact information (e.g., an e-mail address, a mobile phone number, etc.) or information used to acquire the user’s contact information (e.g., the user’s unique identifier). [0041] In operation S430, the new cloud platform 300 receives the requested user information.

[0042] In operation S440, the new cloud platform 300 acquires the user’s contact information on the basis of the received user information. For example, the user’s contact information may be included in the user information received by the new cloud platform 300. Alternatively, for example, information that can be used to acquire the user’s contact information (e.g., the user’s unique identifier) may be included in the user information received by the new cloud platform 300. In this case, the new cloud platform 300 may perform a separate operation for acquiring the user’s contact information on the basis of the received information, an example of which will be described below with reference to, e.g., FIG. 6. [0043] In operation S450, the new cloud platform 300 transmits a sign-up request for use of the new cloud platform 300 to the user.

[0044] After the new cloud platform 300 receives an acceptance of the sign-up request from the user in operation S460, the new cloud platform 300 performs a sign-up process so that the user can receive a service based on the new cloud platform 300 through the image forming apparatus in operation S470. For example, an identifier of the image forming apparatus that can be used by the user, service-related contract information applied to the user, and the like may be stored in association with a user account managed by the new cloud platform 300. [0045] According to the above example, based on apparatus information to be used in the new cloud platform 300 being registered, user information mapped to the corresponding apparatus information in the legacy cloud platform 200 may be acquired based on the apparatus information, and a request to sign up for the new cloud platform 300 may be transmitted to the corresponding user on the basis of the acquired user information. Therefore, based on an apparatus being newly connected to the new cloud platform 300, the sign-up request may be transmitted to a user who has authority to use the apparatus. The user may use a service of the new cloud platform 300 without a separate sign-up procedure simply by responding to the sign-up request. That is, a procedure of signing up for the new cloud platform 300 is performed in a manner of transmitting a sign-up request to a user who is allowed to use the image forming apparatus on the basis of the apparatus information of the image forming apparatus to be used in the new cloud platform 300. Thus, the sign-up procedure may be completed by the user responding to the sign-up request without a separate sign-up procedure. [0046] FIG. 5 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example. The above description with regard to FIG. 4 will be also applied to operations S400, S410, and S420 shown in FIG. 5, and additional descriptions thereof will be omitted.

[0047] In operation S421 , the legacy cloud platform 200 that has received a request for user information associated with the apparatus from the new cloud platform 300 determines that apparatus information included in the user information request (e.g., an apparatus identifier) is not yet registered in the legacy cloud platform 200 and notifies the new cloud platform 300 of the determination. For example, it is possible to consider a case in which a contractor has requested the initiation of a new service for an image forming apparatus according to new contract information but a user who is allowed to use the image forming apparatus has not yet registered the use of the image forming apparatus even in the legacy cloud platform 200, but the examples are not limited thereto. In that case, the legacy cloud platform 200 waits for the apparatus information to be transmitted from the user.

[0048] In operation S422, the user transmits a request to register the image forming apparatus in the legacy cloud platform 200 with the apparatus information. For example, the user who is allowed to use the image forming apparatus by the contractor may transmit a request to register and use the apparatus in the cloud platform.

[0049] In operation S423, the legacy cloud platform 200 notifies the new cloud platform 300 of an event notification indicating that the apparatus information received from the user is registered with the existing user information that has been managed by the legacy cloud platform 200. The new cloud platform 300 receives the event notification and requests user information corresponding to the apparatus information (e.g., the apparatus identifier) from the legacy cloud platform 200 on the basis of the event notification in operation S424.

[0050] Subsequently, the legacy cloud platform 200 proceeds to operation S430. The above description with regard to FIG. 4 will be applied to operations S430, S440, S450, S460, and S470, and an additional description thereof will be omitted below.

[0051] FIG. 6 is a sequence diagram illustrating an operation of creating a new user account in a cloud platform according to an example. In order for the new cloud platform 300 to acquire a user’s contact information from the legacy cloud platform 200, the user’s consent to the legacy cloud platform 200 providing the user’s contact information to the new cloud platform may be obtained. An example of a process of obtaining, from the user, consent to the transfer of his or her user information from the legacy cloud platform 200 to the new cloud platform 300 to use a new service through the new cloud platform 300 is shown in FIG. 6. [0052] In operation S500, a user may access the legacy cloud platform 200 to receive services provided based on the cloud platform through a portal (not shown).

[0053] In operation S510, the legacy cloud platform 200 may inform the user that the new cloud platform 300 has services that can be newly provided and may require an end-user license agreement (EULA) from the user to use the services.

[0054] Based on the user transmitting the agreement in operation S520, the legacy cloud platform 200 may request the new cloud platform 300 to create a new user account for the corresponding user in operation S530. This request may include existing user information of the corresponding user stored in the legacy cloud platform 200. The existing user information may include user identifier and contact information of the user.

[0055] In operation S540, the new cloud platform 300 may create the user account in the new cloud platform 300 using the existing user information. The user account may include the user identifier and contact information of the user. [0056] The user account created in the new cloud platform 300 may be used to acquire the user contact information in operation S440, which has been described with reference to FIGS. 4 and 5. That is, based on the user account being created in the new cloud platform 300 and a request for registration for use of the image forming apparatus is submitted to the new cloud platform 300 (e.g., operation S410), the new cloud platform 300 may request user information of a user who can use the corresponding apparatus from the legacy cloud platform 200 on the basis of apparatus information included in the request for registration for use (e.g., operation S420), receive the user information in response to the request (e.g., operation S430), and retrieve the user’s contact information from the created user account by using information such as a user identifier included in the user information.

[0057] FIG. 7 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example.

[0058] In operation S700, a user may access the legacy cloud platform 200 to receive a service provided based on the cloud platform through a portal (not shown).

[0059] In operation S701, the legacy cloud platform 200 may inform the user that the new cloud platform 300 has a service that can be newly provided and may require an end-user license agreement (EULA) from the user to use the service.

[0060] Based on the user transmitting the agreement in operation S702, the legacy cloud platform 200 may request the new cloud platform 300 to create a new user account for the corresponding user in operation S703. This request may include existing user information of the corresponding user stored in the legacy cloud platform 200. The existing user information may include user identifier and contact information of the user.

[0061] In operation S704, the new cloud platform 300 may create the user account in the new cloud platform using the existing user information. The user account may include user identifier and contact information of the user.

[0062] In operation S710, the legacy cloud platform 200 receives a contract-based request for registration for use from a contractor. The request for registration for use may be submitted through a portal (not shown) to access the cloud platforms 200 and 300.

[0063] The contract-based request for registration for use may include contract information for use of the new cloud platform 300. For example, the contract information may include information to provide a service through the platform, which includes information such as information on a list of image forming apparatuses that have been signed up for the new cloud platform 300 and information on authority for service to be provided to each image forming apparatus. As a non-limiting example, contract information may be information related to the contract for providing a service through a cloud platform based on an image forming apparatus previously used in a company being moved to a home for working from home and used there. However, contract information may not include information on a user authorized to use an image forming apparatus. This may include a situation in which a user who will use each image forming apparatus is not determined in advance or a situation in which a user's personal identification information cannot be provided without the user’s consent, but the examples are not limited thereto.

[0064] In operation S720, based on the legacy cloud platform 200 receiving the request for registration for use based on the contract information from the contractor, the legacy cloud platform 200 extracts apparatus information of an apparatus that has sent the registration for a cloud platform service from the request for registration for use and sends the apparatus information to the new cloud platform 300. The apparatus information may include an apparatus identifier (e.g., S/N, UUID, etc.) for identifying each image forming apparatus. [0065] In operation S730, the new cloud platform 300 receives the apparatus information and requests a user identifier associated with an apparatus corresponding to the apparatus information from the legacy cloud platform 200 on the basis of the apparatus identifier included in the received apparatus information. A user identifier may include information that can uniquely identify each user. For example, the new cloud platform 300 transmits an apparatus identifier to the legacy cloud platform 200 and requests a user identifier of a user who is allowed to use an apparatus corresponding to the apparatus identifier in the legacy cloud platform 200. If the corresponding apparatus is an apparatus registered and used in the legacy cloud platform 200, the user information including the user identifier of the user allowed to use the corresponding apparatus has been registered in the legacy cloud platform 200.

[0066] In operation S740, the new cloud platform 300 receives the requested user identifier.

[0067] In operation S750, the new cloud platform 300 acquires the user’s contact information on the basis of the received user information and the user account created in S704. As described above, the user account created by the new cloud platform 300, which is created based on the existing user information received from the legacy cloud platform 200, may include the user identifier and contact information. Therefore, based on an apparatus being newly registered in the new cloud platform 300, the new cloud platform 300 requests and receives a user identifier of a user allowed to use the corresponding apparatus from the legacy cloud platform 200 and acquires the user’s contact information (e.g., an e- mail, a mobile phone number, etc.) from the user account registered in the new cloud platform 300 on the basis of the received user identifier.

[0068] In operation S760, the new cloud platform 300 transmits a sign-up request for use of the new cloud platform 300 to the user using the user’s contact information.

[0069] After the new cloud platform 300 receives an acceptance of the sign-up request from the user in operation S770, the new cloud platform 300 performs a sign-up process so that the user can receive a service based on the new cloud platform 300 through the image forming apparatus in S780. For example, an identifier of the image forming apparatus that can be used by the user, service-related contract information applied to the user, and the like may be stored in association with the user account managed by the new cloud platform. [0070] FIG. 8 is a sequence diagram illustrating an operation of inviting a new user to a cloud platform according to an example. The above description with regard to FIG. 7 will be applied to operations S700, S701 , S702, S703, S704, S710, S720, and S730 shown in FIG. 8, and an additional description thereof will be omitted.

[0071] In operation S731 , the legacy cloud platform 200 that has received a request for a user identifier associated with an apparatus from the new cloud platform 300 determines that apparatus information included in the request for a user identifier (e.g., an apparatus identifier) is not yet registered in the legacy cloud platform 200 and notifies the new cloud platform 300 of the determination. For example, a contractor may have requested the initiation of a new service for an image forming apparatus according to new contract information but a user who is allowed to use the image forming apparatus has not yet registered the use of the image forming apparatus even in the legacy cloud platform 200, but the examples are not limited thereto. The legacy cloud platform 200 waits for the apparatus information to be transmitted from the user.

[0072] In operation S732, the user transmits a request to register the image forming apparatus in the legacy cloud platform 200 with the apparatus information. For example, the user who is allowed to use the image forming apparatus by the contractor may transmit a request to register and use the apparatus in the cloud platform.

[0073] In operation S733, the legacy cloud platform 200 notifies the new cloud platform 300 of an event notification indicating that the apparatus information received from the user is registered with the existing user information that has been managed by the legacy cloud platform 200.

[0074] In operation S734, the new cloud platform 300 receives the event notification and requests a user identifier corresponding to the apparatus information (e.g., the apparatus identifier) from the legacy cloud platform 200 on the basis of the event notification.

[0075] Subsequently, the legacy cloud platform 200 proceeds to operation S740. The above description with regard to FIG. 7 will be applied to operations S740, S750, S760, S770, and S780, and an additional description thereof will be omitted below.

[0076] According to the examples that have been described with reference to FIGS. 7 and 8, based on apparatus information to be used in the new cloud platform 300 being registered, user information mapped to the corresponding apparatus information in the legacy cloud platform 200 may be acquired based on the apparatus information, and a request to sign up for the new cloud platform 300 may be transmitted to the corresponding user on the basis of the acquired user information. Therefore, based on an apparatus being newly connected to the new cloud platform 300, the sign-up request may be transmitted to a user who has authority to use the apparatus. The user may receive a service of the new cloud platform 300 without a separate sign-up procedure by responding to the transmitted sign-up request. That is, a procedure of signing up for the new cloud platform 300 is performed in a manner of transmitting the sign-up request to a user who is allowed to use the apparatus on the basis of the apparatus information of the image forming apparatus to be used in the new cloud platform 300. Thus, the sign-up procedure may be completed by the user responding to the sign-up request without a separate sign-up procedure.

[0077] FIG. 9 illustrates a cloud platform sign-up request provided to a user according to an example.

[0078] Referring to FIG. 9, a user may receive a request to sign up for the new cloud platform 300 via e-mail. Flowever, it will be appreciated that other example methods for receiving the sign-up request may be used. According to the example method described above, based on an image forming apparatus to be used in the new cloud platform, a user may receive the sign-up request for using a service provided by the new cloud platform through his or her contact information (e.g., e-mail) that has been registered in the cloud platform of the related art (i.e. , the legacy cloud platform) even if the user does not proceed with a separate sign-up procedure. Based on the user accepting the sign-up request received via e-mail, a process of the user signing up for the new cloud platform may be completed. Flere, based on the user accepting the sign-up request, the user may verify that he or she is currently a rightful user of the image forming apparatus. For example, the user may enter a serial number of the image forming apparatus for the purpose of user verification to receive final approval of the sign up request or may scan a quick response (QR) code displayed on the image forming apparatus instead of entering a serial number. However, the examples are not limited thereto, and various methods may be applied for verifying that the user currently legitimately owns the image forming apparatus.

[0079] FIG. 10 is a block diagram conceptually showing a cloud platform server according to an example.

[0080] Referring to FIG. 10, a cloud platform server for configuring the new cloud platform 300 may include a processor 310, a memory 320, and a communication unit 330. However, the cloud platform server is not to be limitedly interpreted as shown in FIG. 10. For example, the cloud platform server may further include elements not shown in FIG. 10, e.g., a power supply for supplying power to each element, or other elements, or may exclude at least one of the elements shown in FIG. 10. Also, it may be understood that the cloud platform server may be one apparatus or may include a plurality of apparatuses connected to each other.

[0081] The processor 310 may include a central processing unit (CPU), a graphic processing unit (GPU), and the like as an element that controls and performs overall functions that can be provided by the cloud platform server. For example, the processor 310 may execute an instruction stored in the memory 320. Also, the processor 310 may read information stored in the memory 320. In addition, the processor 310 may store new information in the memory 320 and may update pre-stored information. For example, the processor 310 may perform an operation of acquiring information to control the cloud platform server from the memory 320 or storing the information in the memory 320.

[0082] The memory 320 may be implemented by various storage media, such as a random-access memory (RAM), a read-only memory (ROM), etc., which may store data. Various kinds of information may be stored in the memory 320. For example, an instruction executable by the processor 310 may be stored in the memory 320.

[0083] The communication unit 330 may be provided for the cloud platform server to communicate with other apparatuses. The communication unit 330 may include various communication modules. For example, the communication unit 330 may include a wireless communication module or a wired communication module. The wireless communication module may be a module that supports, for example, Wi-Fi, Wi-Fi Direct, Bluetooth, Ultra Wide Band (UWB), Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), 5G, Near Field Communication (NFC), etc., and the wired communication module may be a module that supports Local Area Network (LAN), Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), etc., but the examples are not limited thereto.

[0084] The cloud platform server may include the processor 310 and the memory 320 that stores an instruction, and based on the instruction being executed by the processor, the processor causes the cloud platform server to operate in a predetermined manner.

[0085] According to an example, the cloud platform server receives and registers apparatus information of an apparatus to be used in the cloud platform server and requests user information associated with the corresponding apparatus from the cloud platform of the related art (e.g., the legacy cloud platform 200) on the basis of the apparatus information. Subsequently, the cloud platform server receives the requested user information and transmits a sign-up request for use of the cloud platform server on the basis of the received user information.

[0086] In an example, the operations performed through the legacy cloud platform and the new cloud platform, which have been described with reference to FIGS. 4 to 8, may be performed by the cloud platform server of FIG. 10. Therefore, the above description related to examples of the configuration or operation of the cloud platform server may be applied to various parts that may be omitted from the description.

[0087] FIG. 11 illustrates a computer-readable recording medium including instructions to perform a method according to an example.

[0088] Each example operation included in the above-described method may be implemented through a computer program including instructions to perform the corresponding operation, and such a computer program may be stored on a computer-readable recording medium and executed by a processor. Example instructions of a computer program included on a computer-readable recording medium are shown in FIG. 11.

[0089] Referring to FIG. 11 , a computer-readable recording medium 1100 may include instructions to register apparatus information in a first cloud platform (e.g., the new cloud platform 300) S1100.

[0090] The computer-readable recording medium 1100 may include instructions to request user information associated with an apparatus from a second cloud platform (e.g., the legacy cloud platform 200) on the basis of the apparatus information S1200.

[0091] The computer-readable recording medium 1100 may include instructions to receive the user information from the second cloud platform S1300. [0092] The computer-readable recording medium 1100 may include instructions to transmit a request to sign up for the first cloud platform to a user on the basis of the user informationS1400.

[0093] In various examples, the operations described above with reference to FIGS. 4 to 8, including the instructions S1100, S1200, S1300, and S1400 of FIG. 11 , may be performed by a computer including a processor according to the execution of the computer program stored in the computer-readable recording medium 1100. Therefore, the above description related to examples of the configuration or operation of the cloud platform server may be applied to various parts that may be omitted here.

[0094] The computer-readable recording medium 1100 may be a non- transitory readable medium. The term “non-transitory readable medium” as used herein refers to a medium that is capable of semi-permanently storing data and is readable by an apparatus, rather than a medium, e.g., a register, a cache, a volatile memory device, etc., that temporarily stores data. For example, the foregoing program instructions may be stored and provided in a CD, a DVD, a hard disk, a Blu-ray disc, a USB, a memory card, a ROM device, or any of other type of non-transitory readable media.

[0095] In an example, the methodology disclosed herein may be incorporated into a computer program product. The computer program product may be available as a product for trading between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium, e.g., compact disc read-only memory (CD-ROM), or distributed online through an application store, e.g., PlayStore™. For online distribution, at least a portion of the computer program product may be temporarily stored, or temporarily created, in a storage medium such as a server of the manufacturer, a server of the application store, or a storage medium such as a memory of a relay server.

[0096] The foregoing description has been presented to illustrate and describe some examples. It should be appreciated that many modifications and variations are possible in light of the above description. In various examples, suitable results may be achieved if the above-described techniques are performed in a different order, and/or if some of the components of the above- described systems, architectures, devices, circuits, and the like are coupled or combined in a different manner, or substituted for or replaced by other components or equivalents thereof.

[0097] Although examples have been described in the context of an image forming apparatus and a cloud platform, it will be understood that the examples are not limited to an image forming apparatus. Also, it will be understood that the spirit of the various examples may be applied to an environment in which a user device or an electronic device is provided with a service through a cloud platform. [0098] Therefore, the scope of the disclosure is not to be limited to the precise form disclosed, but rather defined by the following claims and equivalents thereof.

Claims

WHAT IS CLAIMED IS:

1. A cloud platform server comprising: a processor; and a memory to store instructions which, when executed, cause the processor to: register apparatus information to be used in a first cloud platform; request user information associated with an apparatus from a second cloud platform on the basis of the apparatus information; receive the user information from the second cloud platform; and transmit a request to sign-up for the first cloud platform to a user on the basis of the user information.

2. The cloud platform server of claim 1 , wherein the apparatus information comprises an apparatus identifier of an apparatus registered to be used in the first cloud platform, and wherein, if the apparatus identifier is registered with existing user information that has been stored in the second cloud platform, the requesting of the user information comprises requesting the existing user information.

3. The cloud platform server of claim 1 , wherein the apparatus information comprises an apparatus identifier of an apparatus registered to be used in the first cloud platform, and wherein the requesting of the user information comprises receiving, from the second cloud platform, an event notification indicating that the apparatus identifier is registered with existing user information stored in the second cloud platform and requesting the existing user information corresponding to the apparatus identifier on the basis of the event notification.

4. The cloud platform server of claim 1 , wherein when executed, the instructions further cause the processor to: allow the first cloud platform to acquire, from the second cloud platform, existing user information stored in the second cloud platform, the existing user information including information of a user who accesses the second cloud platform; and create a user account in the first cloud platform using the acquired existing user information.

5. The cloud platform server of claim 4, wherein the existing user information comprises user identifier and contact information of the user, wherein information on the user account created in the first cloud platform comprises the user identifier and the contact information, and wherein when executed, the instructions further cause the processor to retrieve the user’s contact information from the user account created in the first cloud platform on the basis of the user identifier based on the user identifier being received in response to the requesting of the user information.

6. The cloud platform server of claim 1 , wherein when executed, the instructions further cause the processor to receive contract information for use of the first cloud platform, and wherein the contract information comprises the apparatus information and information on service authority allowed for the apparatus by the first cloud platform, and the apparatus information comprises an apparatus identifier of an apparatus registered to be used in the first cloud platform.

7. The cloud platform server of claim 1, wherein when executed, the instructions further cause the processor to allow the user to use the apparatus on the first cloud platform on the basis of a response to the sign-up request from the user.

8. A user inviting method performed by a cloud platform, the user inviting method comprising: causing a first cloud platform to acquire, from a second cloud platform, existing user information stored in the second cloud platform, the existing user information including information of a user who accesses the second cloud platform; creating a user account in the first cloud platform using the acquired existing user information; registering apparatus information in the first cloud platform; requesting a user identifier associated with an apparatus from the second cloud platform on the basis of the apparatus information; receiving the user identifier from the second cloud platform; and transmitting a request to sign-up for the first cloud platform to a user on the basis of the user account and the received user identifier.

9. The user inviting method of claim 8, further comprising: receiving contract information for use of the first cloud platform, wherein the contract information comprises the apparatus information and information on service authority allowed for the apparatus by the first cloud platform, and the apparatus information comprises an apparatus identifier of an apparatus registered to be used in the first cloud platform.

10. The user inviting method of claim 8, further comprising: allowing the user to use the apparatus on the first cloud platform on the basis of a response to the sign-up request from the user.

11. The user inviting method of claim 8, wherein, based on the apparatus identifier being registered with the existing user information of the second cloud platform, the requesting of the apparatus information comprises requesting the user identifier corresponding to the existing user information.

12. The user inviting method of claim 8, wherein the requesting of the apparatus information comprises receiving, from the second cloud platform, an event notification indicating that the apparatus identifier is registered and requesting the user identifier from the existing user information corresponding to the apparatus identifier on the basis of the event notification.

13. The user inviting method of claim 8, wherein the apparatus information comprises an apparatus identifier of an apparatus registered to be used in the first cloud platform, and the existing user information comprises user identifier and contact information of the user, and wherein the method further comprises, after the receiving of the user identifier, retrieving the contact information corresponding to the user identifier from the user account of the first cloud platform on the basis of the user identifier.

14. A non-transitory computer-readable recording medium having instructions for a user inviting method performed by a cloud platform stored thereon, the non-transitory computer-readable recording medium comprising: instructions to register apparatus information in a first cloud platform; instructions to request user information associated with an apparatus from a second cloud platform on the basis of the apparatus information; instructions to receive the user information from the second cloud platform; and instructions to transmit a request to sign up for the first cloud platform to a user on the basis of the user information.

15. The computer-readable recording medium of claim 14, further comprising: instructions to allow the first cloud platform to acquire, from the second cloud platform, existing user information stored in the second cloud platform, the existing user information including information of a user who accesses the second cloud platform; and instructions to create a user account in the first cloud platform using the acquired existing user information.