WO2024043613A1 - Server device for providing curriculum vitae generation and management service, and operating method thereof - Google Patents

Abstract

Disclosed is an operating method of a server device for generating and managing curriculum vitae (CV) of a plurality of client devices. The operating method of the server device may comprise the steps of: receiving, from at least one client device, task receipt (TR) data including information about a task performed by a user of the at least one client device; determining whether the TR data includes file data of a pre-determined size or greater; if it is determined that the TR data does not include the file data of the pre-determined size or greater, transmitting a first storage request including the TR data to a blockchain-based cloud server that stores TR data of the plurality of client devices; and if it is determined that the TR data includes the file data of the pre-determined size or greater, transmitting a second storage request including at least a portion of the TR data to an InterPlanetary File System (IPFS) connected to the server device.

Description

Server device and method of operating the same for providing resume creation and management services

Embodiments disclosed in this document relate to an apparatus for providing resume creation and management services and a method of operating the same.

Gig work refers to a form of labor in which companies recruit workers as short-term contract workers or temporary workers as needed and pay for them. Gig labor can be provided based on online platforms, and is expanding into a variety of work fields such as delivery, designated driving, and quick service, as well as restaurant assistance and serving, nursing and hospice, cleaning, and security services.

In this regard, blockchain technology can be used to fairly distribute work to gigs and provide objective evaluation and reasonable compensation for the work performed. For example, it is possible to minimize fees and pay appropriate compensation through cryptocurrency operated based on blockchain technology. Additionally, for example, by recording data related to job evaluation through blockchain, data that cannot be manipulated can be created and reliable evaluation data on gig workers can be accumulated. Also, for example, the identity of the gigs can be easily verified, minimizing the risk of hacking.

In order to provide gig labor services, the online platform collects, analyzes and manages the work performed by gig workers to create a CV (curriculum vitae) and provides the content needed by gig workers when they need it. It is necessary to provide The work performed by gig workers can be recorded in various forms, such as the gig workers' profiles and text data, as well as work-related image data and video data, and accordingly, TR data can have a large capacity.

Various embodiments disclosed in this document define a task receipt (TR) and provide a device and method of operating the same for generating a CV based on this.

Additionally, in order to create and provide a reliable CV, we provide a device and operating method for safely storing TR received from gig workers using blockchain technology.

In addition, TR data received from gig workers is stored in a decentralized space, various types of resumes are stored, and a device and method of operating the same are provided.

A method of operating a server device for creating and managing CVs (curriculum vitae) according to an embodiment of the present disclosure includes information about a task performed by a user of the at least one client device from at least one client device. An operation of receiving TR (task receipt) data including, an operation of determining whether the TR data includes file data of a predetermined size or more, and determining that the TR data does not contain file data of a predetermined size or more. In this case, an operation of transmitting a first storage request including the TR data to a blockchain-based cloud server that stores TR data of the plurality of client devices, when determining that the TR data includes file data of a predetermined size or more. , It may include an operation of transmitting a second storage request including at least part of the TR data to an InterPlanetary File System (IPFS) connected to the server device.

A server device for generating and managing CVs (curriculum vitae) of a plurality of client devices according to an embodiment of the present disclosure includes a communication unit, a memory, and at least one processor operably connected to the communication unit and the memory. It includes, wherein the at least one processor receives task receipt (TR) data containing information about a task performed by a user of the at least one client device from at least one client device through the communication unit. and determine whether the TR data includes file data larger than a predetermined size, and when determining that the TR data does not include file data larger than the predetermined size, the TR data of the plurality of client devices is transmitted through the communication unit. A first storage request containing the TR data is transmitted to a blockchain-based cloud server that stores data, and when it is determined that the TR data includes file data of a predetermined size or more, a connection is made with the server device through the communication unit. A second storage request containing at least part of the TR data may be transmitted to the InterPlanetary File System (IPFS).

According to various embodiments disclosed in this document, a server device and its operating method provide the effect of efficiently managing TR (task receipt) data received from a client device.

In addition, the server device and its operating method provide the effect of generating and managing client history information based on large-capacity TR data.

Additionally, the server device and its operating method provide the effect of filtering stored TR data based on a client's request.

The effects that can be obtained from the exemplary embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned are common knowledge in the technical field to which the exemplary embodiments of the present disclosure belong from the following description. It can be clearly derived and understood by those who have it. That is, unintended effects resulting from implementing the exemplary embodiments of the present disclosure may also be derived by those skilled in the art from the exemplary embodiments of the present disclosure.

1 shows an example of a resume creation and management system according to an embodiment.

Figure 2 shows the block configuration of a server device according to an embodiment.

Figure 3 shows the operation flow of a server device according to an embodiment.

Figure 4 shows a signaling flow for storing TR (task receipt) data according to an embodiment.

Figure 5 shows a signaling flow for generating curriculum vitae (CV) according to one embodiment.

Figure 6 shows an example of CV generation according to one embodiment.

Figure 7 shows a signaling flow for authentication of TR data according to an embodiment.

Figure 8 shows a signaling flow for billing according to one embodiment.

In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components.

Hereinafter, with reference to the drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components. Additionally, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

1 shows an example of a resume creation and management system according to an embodiment.

Referring to Figure 1, the resume creation and management system 100 according to one embodiment includes a client device 110, a management server 120, an identity and access management (IAM) server, and a blockchain-based cloud server 140 ( Hereinafter referred to as a cloud server), an authentication server 141, an interplanetary file system (IPFS), an external server 160, and a billing server 170 may be included.

The client device 110 according to one embodiment may refer to an electronic device of a gig worker (hereinafter referred to as a “user”) who uses a resume creation and management service. For example, the client device 110 may refer to a user's portable terminal (e.g., smartphone, personal digital assistant (PDA), tablet PC, wearable device, etc.), laptop, PC, etc.

In one embodiment, client device 110 may generate task receipt (TR) data. TR data may include data about information about tasks performed by the user. For example, TR data may include the type of work performed by the user, date, time, location, work content, and evaluation information about the user.

In one embodiment, TR data may be generated for each task performed by the user. TR data may include identification information (TR ID) generated for each TR data.

In one embodiment, the client device 110 may transmit the generated TR data to the management server 120.

In one embodiment, the client device 110 may request curriculum vitae (CV) data from the management server 120.

In one embodiment, client device 110 may receive CV data from management server 120.

The management server 120 according to an embodiment may refer to a server that performs operations related to storing and managing TR data and generating CV data.

In one embodiment, management server 120 may determine how to store TR data received from client device 110. For example, the management server 120 may decide to store TR data in the cloud server 140. Also, for example, the management server 120 may decide to store the information in the cloud server 140 and the interplanetary file system (IPFS) 150.

In one embodiment, the management server 120 may request the cloud server 140 and IPFS 150 to store TR data. Accordingly, the management server 120 may transmit TR data to the cloud server 140 or IPFS 150.

In one embodiment, the management server 120 may communicate with the identity and access management (IAM) server 130 to obtain the user's unique identifier. For example, management server 120 may send a client identifier request to IAM server 130. Also, for example, management server 120 may receive a client identifier from IAM server 130.

The IAM server 130 according to one embodiment may refer to a server for managing user identifiers.

In one embodiment, the IAM server 130 may discover and generate a unique user identifier based on TR data transmitted from the client device 110 to the management server 120.

In one embodiment, IAM server 130 may determine whether an identifier corresponding to the user ID of the TR data exists.

In one embodiment, the IAM server 130 may generate a unique user identifier based on the user ID included in TR data. The identifier generated by the IAM server 130 may be transmitted together when the corresponding TR data is stored in the blockchain-based cloud server 140 or IPFS 150.

The cloud server 140 according to an embodiment may mean a server that stores TR data received from the management server 120.

In one embodiment, the cloud server 140 may receive a request to store TR data and TR data from the management server 120. For example, when the management server 120 requests storage of TR data, a Transaction (including TR data and a request to store TR) occurs, the Smart Contract of the cloud server 140 is called, and the cloud TR data may be stored in the storage of the server 140. Transactions that have occurred can be stored in blocks that constitute a private network (a private network including the cloud server 140 and the authentication server 141). Accordingly, TR data generated from the client device 110 can be safely stored from external hacking.

In one embodiment, the cloud server 140 may transmit at least one stored TR data when the management server 120 requests TR data.

The authentication server 141 according to an embodiment may refer to a server for authenticating TR data.

In one embodiment, when receiving a request for authentication of TR data from the cloud server 140, the authentication server 141 may transmit the TR data to an external server related to the TR data and request authentication.

In one embodiment, when a user is requested to authenticate TR data generated by performing a government task, the authentication server 141 may communicate with the external server 160 to request authentication for the TR data.

In one embodiment, the authentication server 141 can receive public authentication of the credentials stored by the user for the CV.

In one embodiment, the content of receiving public certification may include an indicator (e.g., "") indicating that public certification has been received when creating a CV.

IPFS 150 according to one embodiment may mean distributed storage. In one embodiment, when the IPFS 150 receives a request to store TR data from the management server 120, the IPFS 150 may store the TR data or at least a portion of the TR data. For example, IPFS 150 may store image data included in TR data. Image data may include data about still images (images) and data about dynamic images (eg, videos).

The external server 160 according to an embodiment may refer to a server that performs authentication for TR data in response to an authentication request received from the authentication server 141.

The billing server 170 according to an embodiment may refer to a server that manages energy (gas) used to store TR data according to a billing request from the management server 120 and calculates the amount for billing based on this. .

In the description and drawings below, the management server 120 may be referred to as a “Task handler.” Additionally, the IAM server 130 may be referred to as an “IAM handler.” Additionally, the cloud server 140 may be referred to as “Task Smart Contract.” Additionally, the authentication server 150 may be referred to as “Oracles smart contract.” Additionally, the billing server 170 may be referred to as a “Billing Handler.”

Figure 2 shows the block configuration of a server device according to an embodiment. The server device 200 according to one embodiment may mean a server device corresponding to the management server 120 of FIG. 1.

Referring to FIG. 2, the server device 200 according to an embodiment may include a processor 210, a memory 220, and a communication unit 230. The configuration shown in FIG. 2 illustrates a configuration related to the description of an embodiment according to the present disclosure, and in addition to the illustrated configuration, other configurations for performing the function of the server device may be added, and the illustrated configurations may be omitted. .

The memory 220 according to an embodiment is a storage medium used by the server device 200 and can store data such as at least one command 221 or setting information corresponding to at least one program. The program may include an operating system (OS) program and various application programs.

In one embodiment, the memory 220 is a flash memory type, a hard disk type, a multimedia card micro type, or a card type of memory (e.g., SD or memory, etc.), random access memory (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), programmable ROM (PROM), magnetic memory, magnetic disk, It may include at least one type of storage medium, such as an optical disk.

The communication unit 230 according to one embodiment includes a server device 200 and an external electronic device (e.g., client device 110, IAM server 130, billing server 170, cloud server 140, IPFS 150). ) can perform direct (e.g. wired) communication between For example, the communication unit 230 may receive TR data transmitted from the client device 110. Also, for example, the communication unit 230 may transmit TR data to the cloud server 140 and IPFS 150.

In one embodiment, the communication unit 230 may include a wireless communication unit (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication unit. Among these communication units, the corresponding communication units communicate with external electronic devices (e.g., clients) through networks (e.g., legacy cellular networks, 5G networks, next-generation communication networks, the Internet, or telecommunication networks such as computer networks (e.g., LAN or WAN)). It can communicate with the device 110, IAM server 130, billing server 170, cloud server 140, and IPFS 150).

In one embodiment, the communication unit 230 may support a 5G network after the 4G network and next-generation communication technology, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. For example, the communication unit 230 may support a high frequency band (eg, mmWave band) to achieve a high data transmission rate. The communication unit 230 uses various technologies to secure performance in the high frequency band, for example, beamforming, massive MIMO (multiple-input and multiple-output), and full-dimensional multiple input/output ( It can support technologies such as FD-MIMO (full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna.

In one embodiment, the communication unit 230 includes a server device 200, an external electronic device (e.g., a client device 110, an IAM server 130, a billing server 170, a cloud server 140, and an IPFS 150). ) or can support various requirements specified in network systems.

The processor 210 according to one embodiment, for example, executes software (e.g., a program) to execute at least one other component (e.g., a hardware or software component) of the server device 200 connected to the processor 210. ) can be controlled and various data processing or operations can be performed.

In one embodiment, the processor 210 stores commands or data received from another component (e.g., communication unit 230) in volatile memory, as at least part of data processing or calculation, and stores the commands or data stored in the volatile memory. can be processed, and the resulting data can be stored in non-volatile memory.

In one embodiment, the processor 210 is a main processor (e.g., a central processing unit or an application processor) or an auxiliary processor that can operate independently or together (e.g., a graphics processing unit, a neural processing unit (NPU), or a communication processor).

In one embodiment, the processor 210 may receive TR data including information about a task performed by a user of the at least one client device from at least one client device.

In one embodiment, the processor 210 may determine whether TR data includes image data of a predetermined size or more.

In one embodiment, when the processor 210 determines that the TR data does not include image data larger than a predetermined size, the processor 210 sends a first storage request containing the TR data to a cloud server that stores the TR data of a plurality of client devices. Can be sent.

In one embodiment, when the processor 210 determines that the TR data includes image data of a predetermined size or more, the processor 210 may transmit a second storage request including at least a portion of the TR data to IPFS.

In one embodiment, the processor 210 may transmit the remaining portion, but not the at least part, of TR data to the cloud server in response to transmitting a second storage request to the at least one node.

In one embodiment, the processor 210 may generate a TR table including information about the storage location of the TR data in response to determining whether the TR data includes image data of a predetermined size or more.

In one embodiment, processor 210 may receive a CV transmission request from at least one client device requesting to transmit a CV of a user of the at least one client device.

In one embodiment, the processor 210 transmits a TR transmission request requesting one or more TR data of a user to at least one of the cloud server and IPFS, based on information about the location where TR data included in the TR table is stored. can do.

Figure 3 shows the operation flow of a server device according to an embodiment. The server device of FIG. 3 may refer to a device corresponding to the management server 120 of FIG. 1 and the electronic device 200 of FIG. 2. The operation of the server device shown in FIG. 3 may include all or part of the operation of the management server 120 of FIGS. 4 and 5.

According to one embodiment, in operation 310, the server device may receive task receipt (TR) data including information about a task performed by a user of the at least one client device from at least one client device.

In one embodiment, a client device may refer to a server device used by a user.

In one embodiment, the server device may receive respective TR data from a plurality of client devices.

In one embodiment, TR data may mean the result of a completed task that the user's server device, that is, the client device, creates through a specific application when the user completes the task.

In one embodiment, TR data may be generated for each task performed by the user.

In one embodiment, TR data may include information regarding tasks performed by the user of the client device.

In one embodiment, TR data includes identification number (ID), user key value, category of work, subcategory, date of work performed, time of work performed, location of work performed, and employer for work performed. It may include the evaluation, the amount paid for the work performed (income), and attachments.

In one embodiment, TR data may be created and managed in the form of a table. For example, TR data may be generated and managed in the form shown in Table 1 below.

Category	Data
TR ID	001
User Key	DFKDUYF08A90FD
Category	Restaurant
Sub Category	Serving
Date	2022-06-03
Time	3 Hours
Location	Seoul/Gangnam-gu
Feedback	Excellent
Income	60,000
Attachment(Hash)	Movie clips, photos, output

The content included in Table 1 above is only an example, and TR data may include not only the content included in Table 1 but also other content about the work performed by the user, and some of the content included in Table 1 above is It may be omitted. Referring to Table 1, TR ID may mean a unique ID of the performed task. Category and sub-category may refer to items that classify what kind of work the user has completed. User Key may refer to the user's unique identifier. Date and Time may refer to the date and time the user performed work. Location may refer to the place where the user performed work. Feedback may refer to the employer's evaluation of the work performed. Income may refer to the income earned by the user by performing tasks. Attachments are additional information about tasks performed by the user and may include image data such as videos or photos.

In one embodiment, TR data generated on a client device may be transmitted to a server device based on input from a user identified on the client device.

In one embodiment, although not shown in the drawing, the server device may receive information about the user's profile (eg, information about personal information, information about qualifications, educational background information, etc.) from the client device. The server device may transmit a message requesting to store information about the user's profile received from the client device to the cloud server. Accordingly, the cloud server may store information about the user's profile. Information regarding the user's profile may be included when creating the user's CV, as described later.

In one embodiment, the server device may request a user's unique identifier (e.g., key value) from the IAM server. Accordingly, the server device can receive the user's unique identifier from the IAM server. In one embodiment, although not shown in the drawing, if a user's unique key value does not exist, the IAM server may generate the user's key value. For example, although not shown in the drawing, the server device may transmit necessary information to the IAM server so that the IAM server can generate a unique key value for the user. The server device can receive information from the client device that the IAM server needs to generate the key value.

According to one embodiment, in operation 320, the server device may determine whether TR data includes image data of a predetermined size or more.

In one embodiment, when the server device receives TR data from a client device, it may analyze the TR data. TR data may mainly consist of text, but may additionally include data about images or videos to represent the tasks performed by the user in more detail. In this case, storing large amounts of data on a cloud server may incur large costs, so large amounts of data can be stored in IPFS to reduce costs.

In one embodiment, image data of a predetermined size or larger may include images included in TR data in addition to images related to the user's personal information (e.g., profile photo, etc.). For example, image data larger than a predetermined size is image data related to the work performed (e.g., photos showing the results of the work performed, photos showing the process of performing the work, video data showing the user performing the work) etc.) may be included.

In one embodiment, if the TR data includes images other than image data related to personal information, the server device may determine that the TR data includes image data of a predetermined size or more.

In one embodiment, when the size of the TR data exceeds a threshold, the server device may determine that the TR data includes image data of a predetermined size or more.

In one embodiment, the server device may check whether TR data includes a large file. For example, image files may include image files such as jpeg, png, and gif, file formats such as pdf and tiff, video files, and audio files. The file may be data containing information about work performed by the user. For example, if the work performed was a lecture on a specific topic, additional information related to the lecture can be added to the TR data. Also, for example, if prior training is required to perform a specific task, TR data regarding the task may further include completion information certifying that prior training has been completed.

In one embodiment, when TR data includes a file, the server device may check whether a file such as an image or PDF is the same as a previously stored file to avoid storing duplicate files.

In one embodiment, the server device may determine whether a file contains sensitive information if the file is not the same as a previously stored file. For example, sensitive information may include personal information (e.g. social security number). The server device can extract text information using technology such as OCR and check whether there is sensitive information. If sensitive information is identified, the server device can blur the relevant portion and store it.

In one embodiment, the server device may create a table such as Table 2 below.

TR ID	Task S.C.	IPFS (Hash)	Image	Movie	Audio	Doc
000	O	X
001	O	O		32489E..		DSFJSR..
002

As described above, when TR data has a large capacity because additional image files are attached, efficient TR data management is possible by storing it in IPFS rather than a cloud server. According to one embodiment, when the server device determines that the TR data does not include image data larger than a predetermined size, in operation 330, the server device includes the TR data to a cloud server that stores TR data of a plurality of client devices. A first storage request may be sent. In one embodiment, when the server device determines that the TR data does not contain image data larger than a predetermined size, the storage capacity is not large and storing it on the cloud server is sufficient, so storing the TR data on the cloud server is requested. Sending a request. In one embodiment, the first storage request may include TR data to be stored by the cloud server at the same time as requesting the cloud server to store TR data.

According to one embodiment, when the server device determines that the TR data includes image data of a predetermined size or more, in operation 340, the server device stores at least a portion of the TR data into an interplanetary file system (IPFS) connected to the server device. A second storage request may be transmitted including: If the server device determines that the TR data contains image data of a predetermined size or more, since the capacity of the TR data is relatively large, storing it through IPFS is more efficient than storing it on a cloud server, TR data is stored in the cloud. It can be stored separately on the server and IPFS.

In one embodiment, at least a portion of TR data transmitted by the server device to IPFS may include image data included in the TR data. By storing large amounts of data in IPFS, efficient TR data management can be possible.

In one embodiment, the server device may create a table regarding the location where TR data is stored. For example, if the server device stores TR data separately in the cloud server and IPFS, a table indicating that it is stored separately can be created as shown in Table 3 below.

TR ID	Chain	IPFS(Hash value)
000	O	X
001	O		DSKFLJOIFWJJV232RWEFDWSKLFJLW
002

In one embodiment, a server device may receive a CV request from a client device. CV (curriculum vitae) may refer to data containing information about the user's history. In one embodiment, when the server device receives a CV request from a client device, the server device may identify the location where the desired TR data is stored based on a TR data table that the server device creates and manages for each client device. For example, if TR data 001, 002, 003, 004 is needed to create a user's CV, identify the location where each TR data is stored and request that the TR data be transmitted to the cloud server and/or IPFS. By receiving this and aggregating the received TR data, a CV can be generated. In one embodiment, the server device sends at least one TR data to be included in the CV to the cloud server based on the user's key value. You can request it.

In one embodiment, the CV request sent by the client device to the server device and the TR data request sent by the server device to the cloud server extract only the TR data desired by the user from among a plurality of TR data stored in the cloud server or IPFS. Filtering information that allows the acquisition of filtering information (e.g., receiving only TR data on work performed in a specific period, receiving only TR data on work performed in a specific location, receiving TR data only on work performed in a specific category, receiving TR data only on work performed in a specific category, It may include receiving only TR data containing feedback above the standard, etc.).

In one embodiment, the TR data request is a CV request that transmits at least one TR data among TR data about tasks performed by the user stored in the cloud server and IPFS in order to generate a CV desired by the client device. It may mean a signal requesting something to be done. The specific operation for generating CV is explained in detail in FIG. 5 described later.

In one embodiment, although not shown in the drawing, the server device may request public authentication of TR data from the cloud server.

In one embodiment, although not shown in the drawing, the server device may transmit a charging request for TR data to the cloud server.

Figure 4 shows a signaling flow for storing TR (task receipt) data according to an embodiment. In the description of FIG. 4, parts that overlap with content described in FIGS. 1, 2, and 3 may be omitted. The operation shown in FIG. 4 shows a process in which one TR data is saved, and each TR data generated in the client device 1100 can be stored through the process shown in FIG. 4. The management server 120 in FIG. 4 The operation of ) may include the operation of the server device in Figure 3. Although only one client device 110 is shown in Figure 4, this is for convenience of explanation, and a plurality of clients communicating with the management server 120 Devices may exist.

According to one embodiment, in operation 401, the client device 110 may transmit a TR data storage request to the management server 120. TR data storage requests may include TR data regarding tasks performed by the user.

According to one embodiment, in operation 403, the management server 120 may request the user's key value from the IAM server 130.

According to one embodiment, in operation 405, the IAM server 130 may transmit the user's key value to the management server 120.

In one embodiment, the IAM server 130 may generate a unique key value for the user if the user's key value does not exist. Although not shown in the drawing, the IAM server 130 may obtain the information necessary to generate a user's unique key value by requesting the management server 120 and the client device 110.

According to one embodiment, in operation 407, the management server 120 may determine a storage location of the TR data received in operation 401.

In one embodiment, the management server 120 may decide to store the TR data in the cloud server 140, or may decide to store the TR data separately in the cloud server 140 and the IPFS 150.

In one embodiment, the management server 120 may decide to divide and store the TR data into the cloud server 140 and the IPFS 150 when the TR data includes image data of a predetermined size or more.

In one embodiment, the management server 120 may determine to store the TR data in the cloud server 140 when the TR data does not include image data larger than a predetermined size.

According to one embodiment, in operation 409, the management server 120 may transmit a signal requesting to store TR data to the cloud server 140.

In one embodiment, when the management server 120 determines to store the TR data only in the cloud server 140, the management server 120 sends a first storage request requesting to store the TR data in the cloud server 140 to the cloud server 140 It can be sent to . The first storage request may include TR data to be stored.

According to one embodiment, in operation 411, the management server 120 may transmit a signal requesting to store TR data to the IPFS 150.

In one embodiment, when the management server 120 determines to store TR data divided into the cloud server 140 and IPFS 150, at least some of the TR data (e.g., additionally attached data) is sent to the cloud server 140. A second storage request requesting to store image data, video data) may be transmitted to IPFS. In this case, the management server 120 may request that the remaining part of the TR data be stored in the cloud server 140.

In one embodiment, the cloud server 140 may store the TR data received in operation 409.

In one embodiment, IPFS 150 may store TR data received in operation 411.

According to one embodiment, in operation 413, the IPFS 150 may transmit a hash value for the stored TR data to the management server 120. When TR data is stored in IPFS, since it is stored separately, a hash value for the TR data can be generated and transmitted to the management server 120 to identify the stored node.

In one embodiment, the management server 120 may create a table related to the location where TR data is stored based on the received Hash value. For example, a table related to the location where TR data is stored can be created in the form shown in Table 2 described above.

According to one embodiment, in operation 415, the management server 120 may transmit TR data that does not include a hash value to the cloud server 140.

Operations 403 and 405 of FIG. 4 may be omitted. If the management server 120 decides to store TR data only in the cloud server 140, operations 411, 413, and 415 may be omitted. Additionally, if the management server 120 decides to store TR data separately in the cloud server 140 and IPFS, operation 409 may be omitted.

Figure 5 shows a signaling flow for generating curriculum vitae (CV) according to one embodiment. In the description of FIG. 5, parts that overlap with content described in FIGS. 1, 2, 3, and 4 may be omitted. The operation shown in FIG. 5 illustrates the signaling flow performed when a user requests a CV, and the TR data storage process according to FIG. 4 may precede the CV request. The operation of the management server 120 of FIG. 5 may include the operation of the server device of FIG. 3. Although only one client device 110 is shown in FIG. 5, this is for convenience of explanation, and a plurality of client devices communicating with the management server 120 may exist.

According to one embodiment, in operation 501, the client device 110 may request the user's curriculum vitae (CV) from the management server 120. CV may refer to the user's history information generated based on the user's TR data.

In one embodiment, the CV request transmitted from the client device 110 to the management server 120 extracts only the TR data desired by the user from among the plurality of TR data stored in the cloud server 140 or IPFS 150. Filtering information that allows the acquisition of filtering information (e.g., receiving only TR data on work performed in a specific period, receiving only TR data on work performed in a specific location, receiving TR data only on work performed in a specific category, receiving TR data only on work performed in a specific category, It may include receiving only TR data containing feedback above the standard, etc.).

According to one embodiment, in operation 503, the management server 120, in response to receiving a CV request from the client device 110, requests a key value of the client device 110 from the IAM server 130. A signal can be transmitted.

According to one embodiment, in operation 505, the management server 120 may receive the key value of the client device 110 from the IAM server 130.

According to one embodiment, in operation 507, the management server 120 may request TR data from the cloud server 140.

In one embodiment, the management server 120 may request at least one TR data to be included in the CV from the cloud server based on the user's key value.

In one embodiment, the TR data request is a CV request, in order to generate a CV desired by the client device 110, at least one TR among TR data about tasks performed by the user stored in the cloud server and IPFS. This may mean a signal requesting data to be transmitted.

In one embodiment, at least one TR data may be selected based on filtering information included in the CV request.

According to one embodiment, in operation 509, the management server 120 may receive at least one TR data requested from the cloud server 140.

According to one embodiment, in operation 511, the management server 120 may determine whether at least one TR data received from the cloud server 140 is stored in IPFS.

In one embodiment, the management server 120 may determine whether at least one TR data is stored in IPFS based on a table of TR data created and managed by the management server 120. For example, if a table related to TR data includes a Hash value in the TR data area, it may be determined that at least one TR data is stored in IPFS.

According to one embodiment, in operation 513, the management server 120 may request TR data from IPFS.

According to one embodiment, in operation 513, the management server 120 may receive TR data requested from IPFS.

In one embodiment, operations 513 and 515 are operations performed when there is data stored in the IPFS 150 among at least one TR data requested by the management server 120 from the cloud server 140, and if at least one If there is no data stored in the IPFS 150 among the TR data, operations 513 and 515 may be omitted.

According to one embodiment, in operation 517, the management server 120 may generate a CV based on at least one data received from the cloud server and TR data received from the IPFS 150.

In one embodiment, the management server 120 may generate a CV by combining TR data received from the cloud server 140 and the IPFS 150.

In one embodiment, the management server 120 may generate a CV by combining TR data received from the cloud server 140 and IPFS 150 and information about the user's profile received from the client device 110. there is. Operation 517 can be described in detail in FIG. 6 described below.

According to one embodiment, in operation 519, the management server 120 may transmit the generated CV to the client 110.

Figure 6 shows an example of CV generation according to one embodiment. The content shown in FIG. 6 is only an example, and some content may be added or omitted.

The management server 120 according to an embodiment may generate the CV 630 based on a plurality of TR data 610 received from the cloud server 140 and the IPFS 150.

In one embodiment, each of TR data (e.g., 610-1, 610-2, 610-3, 610-N) may include a category, subcategory, work performance location, work performance time, and feedback information. .

In one embodiment, the management server 120 stores a plurality of TR data (e.g., TR data 610-1, TR data 610-2, TR data 610-3, TR data 610-N). ) can be combined to generate combined TR data 620. For example, referring to FIG. 6, the combined TR data 620 shows that the categories of tasks performed by the user are “restaurant” and “cleaning,” and the subcategories are “serving” and “serving.” May include “delivery” and “home cleaning.” Additionally, for example, the combined TR data 620 may also include information indicating that the user performed work in “Gangnam-Gu” and “Yangcheon-Gu.” Also, for example, the combined data 620 may include information about task performance times (e.g., 140 hours for delivery and 200 hours for serving). Additionally, for example, the combined TR data 620 may provide feedback information about the work performed by the user (e.g., “excellent” for delivery, “excellent” for serving). may include.

In one embodiment, the CV 630 includes information 632 regarding the user's personal information, information 634 related to certification of the work performed, information 636 related to the user's educational background, and work experience performed. It may include information 638 about. Information 638 regarding work experience performed may include at least a portion of the combined TR data.

Figure 7 shows a signaling flow for authentication of TR data according to an embodiment. In the description of FIG. 7, parts that overlap with the content described in FIGS. 1 to 6 may be omitted. The operation shown in FIG. 7 illustrates the signaling flow performed when a user requests authentication of TR data, and the TR data storage process according to FIG. 4 may precede the CV request. The operation of the management server 120 of FIG. 7 may include the operation of the server device of FIG. 3. Although only one client device 110 is shown in FIG. 7, this is for convenience of explanation, and a plurality of client devices communicating with the management server 120 may exist.

According to one embodiment, in operation 701, the client device 110 may transmit a TR data authentication request to the management server 120.

According to one embodiment, in operation 703, the management server 120 may request the key value of the client device 110 from the IAM server 130.

According to one embodiment, in operation 705, the management server 120 may receive the key value of the client device 110 from the IAM server 130.

According to one embodiment, in operation 707, the management server 120 may transmit an authentication request for TR data to the cloud server 140.

According to one embodiment, in operation 709, the cloud server 140 may request the authentication server 141 to perform authentication of the corresponding TR data.

According to one embodiment, in operation 711, the authentication server 141 may request authentication of TR data from the external server 160. Although only one external server 160 is shown in FIG. 7 for convenience of explanation, a plurality of external servers that perform authentication of TR data may exist, and the authentication server 141 may communicate with a plurality of external servers.

In one embodiment, the authentication server 141 may identify the external server 160 based on TR data and the type of public authentication to be performed.

According to one embodiment, in operation 713, the authentication server 141 may receive authentication information about TR data from the external server 160.

According to one embodiment, in operation 715, the cloud server 140 may receive authentication information for TR data from the authentication server 141.

In one embodiment, the cloud server 140 may store authentication information for TR data received from the authentication server 141 together with the TR data.

According to one embodiment, in operation 717, the cloud server 140 may transmit authentication information for TR data to the management server 120.

According to one embodiment, in operation 719, the management server 120 may transmit authentication information for TR data received from the cloud server 140 to the client device 110.

Figure 8 shows a signaling flow for billing according to one embodiment.

According to one embodiment, in operation 801, the client device 110 may transmit TR data to the management server 120.

According to one embodiment, in operation 803, the management server 120 may request storage of TR data from the cloud server 140.

In one embodiment, operations 801 and 803 may correspond to the operations of FIG. 3 .

According to one embodiment, in operation 805, the management server 120 may request confirmation of Gas used by the cloud server 140.

According to one embodiment, in operation 807, the cloud server 140 may calculate Gas used to store the corresponding TR data.

According to one embodiment, in operation 809, the cloud server 140 may transmit information about how much gas has been used based on the calculation result to the management server 120.

According to one embodiment, in operation 811, the management server 120 may transmit information regarding the amount of Gas used to store the corresponding TR data to the billing server 170.

According to one embodiment, in operation 815, the charging server 170 may store information on how much gas is used to store the corresponding TR data and the price thereof.

According to one embodiment, in operation 813, the client device 110 may request billing from the management server 120.

According to one embodiment, in operation 817, the management server 120 may request price confirmation from the billing server 170.

According to one embodiment, in operation 819, the management server 120 may receive information about the price from the billing server 170.

According to one embodiment, in operation 821, the management server 120 may transmit information about the charged amount to the client device 110.

A method of operating a server device for creating and managing CVs (curriculum vitae) of a plurality of client devices according to an embodiment of the present disclosure is performed by a user of the at least one client device from at least one client device. An operation of receiving task receipt (TR) data containing information about a task, an operation of determining whether the TR data includes image data of a predetermined size or more, and an operation of determining whether the TR data includes image data of a predetermined size or more. If it is determined that it does not contain image data, transmitting a first storage request including the TR data to a cloud server that stores the TR data of the plurality of client devices, where the TR data is image data of a predetermined size or more If it is determined to include, it may include transmitting a second storage request including at least part of the TR data to an InterPlanetary File System (IPFS) connected to the server device.

In one embodiment, at least part of the TR data may include image data larger than or equal to the predetermined size.

In one embodiment, in response to transmitting the second storage request to the IPFS, the operation may include transmitting the remaining portion, but not at least part, of the TR data to the cloud server.

In one embodiment, in response to determining whether the TR data includes image data larger than the predetermined size, the method may include generating a TR table including information about a storage location of the TR data.

In one embodiment, in response to transmitting the second storage request, receiving a hash value of the TR data from the IPFS, wherein the TR table may include a hash value of the TR data. there is.

In one embodiment, in response to receiving the TR data from the at least one client device, requesting an identity and access management (IAM) server for an identifier of the at least one client device based on the TR data, It may include receiving the identifier of the at least one client device from an IAM server, and transmitting the identifier of the at least one client device and the TR data to the cloud server or the IPFS.

In one embodiment, the TR data may further include information about the personal information of the user of the at least one client device, information about a certificate owned by the user, and information about the user's educational background.

In one embodiment, the operation of receiving a CV transmission request requesting to transmit a CV of a user of the at least one client device from the at least one client device, and a location where the TR data included in the TR table is stored. Based on information about, transmitting a TR transmission request requesting one or more TR data of the user to at least one of the cloud server and the IPFS, wherein the CV transmission request filters the one or more TR data. May include filtering information for filtering.

In one embodiment, receiving at least one TR data of the user from at least one of the cloud server and the IPFS, generating a CV of the user based on the at least one TR data and the filtering information, and transmitting the generated CV of the user to the at least one client device.

In one embodiment, the operation of receiving a request for authentication of the TR data from the at least one client device, in response to receiving a request for public authentication of the TR data, performing public authentication of the TR data with the cloud server. It may include an operation of transmitting a request to perform public authentication, and an operation of receiving a public authentication response to the public authentication request from the cloud server.

In one embodiment, transmitting a billing information request requesting transmission of billing information for the TR data to the cloud server, receiving a billing information response including billing information for the TR data from the cloud server. Can include actions.

In one embodiment, if the server has transmitted image data identical to the image data of the predetermined size or more to the IPFS before receiving the TR data, the operation of updating the TR table may be included. there is.

A server device for generating and managing CVs (curriculum vitae) of a plurality of client devices according to an embodiment of the present disclosure includes a communication unit, a memory, and at least one processor operably connected to the communication unit and the memory. It includes, wherein the at least one processor receives task receipt (TR) data containing information about a task performed by a user of the at least one client device from at least one client device through the communication unit. and determine whether the TR data includes image data of a predetermined size or larger, and when determining that the TR data does not include image data of a predetermined size or larger, TR of the plurality of client devices through the communication unit. When transmitting a first storage request including the TR data to a cloud server that stores data, and determining that the TR data includes image data of a predetermined size or more, an IPFS (IPFS) connected to the server device through the communication unit A second storage request containing at least part of the TR data may be transmitted to the InterPlanetary File System.

In one embodiment, at least part of the TR data may include image data larger than or equal to the predetermined size.

In one embodiment, the at least one processor may transmit the remaining portion, but not the at least part, of the TR data to the cloud server in response to transmitting the second storage request to the IPFS.

In one embodiment, in response to determining whether the TR data includes image data larger than the predetermined size, a TR table containing information about a storage location of the TR data may be generated.

In one embodiment, in response to transmitting the second storage request, a hash value of the TR data is received from the IPFS, and the TR table may include a hash value of the TR data.

In one embodiment, the at least one processor, in response to receiving the TR data from the at least one client device, determines the identifier of the at least one client device based on the TR data through identity and access management (IAM). A request may be made to a server, an identifier of the at least one client device may be received from the IAM server, and the identifier of the at least one client device and the TR data may be transmitted to the cloud server or the IPFS.

In one embodiment, the TR data may further include information about the personal information of the user of the at least one client device, information about a certificate owned by the user, and information about the user's educational background.

In one embodiment, the at least one processor receives a CV transmission request from the at least one client device requesting to transmit a CV of a user of the at least one client device, and selects the TR included in the TR table. Based on information about the location where data is stored, transmit a TR transmission request requesting one or more TR data of the user to at least one of the cloud server and the IPFS, and the CV transmission request requests the one or more TR data It may contain filtering information for filtering.

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, display devices, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or replacements of the embodiments. For example, a component expressed in the singular should be understood as a concept that includes plural components unless the context clearly indicates only the singular. It should be understood that the term 'and/or' used in this document encompasses any and all possible combinations of one or more of the listed items. Terms such as 'include', 'have', 'consist', etc. used in the present disclosure are only intended to designate the presence of features, components, parts, or combinations thereof described in the present disclosure, and the use of such terms It is not intended to exclude the presence or addition of one or more other features, components, parts, or combinations thereof. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to that component in other respects (e.g., importance or order) is not limited.

The term “unit” or “module” used in various embodiments of this document may include a unit implemented with hardware, software, or firmware, for example, logic, logic block, component, or circuit. Can be used interchangeably with the same term. The “~part” or “~module” may be an integrated part or a minimum unit of the part or a part thereof that performs one or more functions. For example, according to one embodiment, “~unit” or “~module” may be implemented in the form of an application-specific integrated circuit (ASIC).

The term “if” used in various embodiments of this document is interpreted to mean “when” or “when” or “in response to determining” or “in response to detecting,” depending on the context. It can be. Similarly, “when it is determined that” or “when it is detected” means “upon determining” or “in response to determining,” or “upon detecting” or “in response to detecting,” depending on the context. It can be interpreted as

Programs executed by the electronic device 110 and the remote control device 120 described throughout this document may be implemented as hardware components, software components, and/or a combination of hardware components and software components. A program can be executed by any system that can execute computer-readable instructions.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. Software may be implemented as a computer program including instructions stored on computer-readable storage media. Computer-readable storage media include, for example, magnetic storage media (e.g., ROM (Read-Only Memory), RAM (Random-Access Memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). (CD-ROM), DVD (Digital Versatile Disc), etc. The computer-readable storage medium is distributed across networked computer systems, so that computer-readable code can be stored and executed in a distributed manner. Computer programs may be distributed (e.g., downloaded or uploaded) online, through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. there is. According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, or omitted. Alternatively, one or more other operations may be added.

Claims (15)

1. In a method of operating a server device for creating and managing CVs (curriculum vitae) of a plurality of client devices,

   An operation of receiving, from at least one client device, task receipt (TR) data containing information about a task performed by a user of the at least one client device;

   An operation of determining whether the TR data includes file data of a predetermined size or more,

   When determining that the TR data does not include file data larger than the predetermined size, transmitting a first storage request including the TR data to a blockchain-based cloud server that stores TR data of the plurality of client devices. ,

   When determining that the TR data includes file data greater than or equal to the predetermined size:

   identifying that the file data is not identical to other previously stored file data;

   An operation of transmitting a second storage request including the file data to an InterPlanetary File System (IPFS) connected to the server device,

   The file data includes data related to at least one of images, videos, and sounds.
2. In claim 1,

   In response to identifying that the file data is not identical to other previously stored file data, extracting text information from the file data;

   An operation of determining whether the file data includes personal identification information of a user based on the text information;

   When determining that the file data does not include the user's personal identification information, transmitting the second storage request including the file data to an InterPlanetary File System (IPFS) connected to the server device;

   When determining that the file data includes the user's personally identifiable information, a method comprising blurring a portion related to the personally identifiable information.
3. In claim 1,

   In response to transmitting the second storage request to the IPFS, the method comprising transmitting data other than the file data of the TR data to the cloud server.
4. In claim 3,

   In response to determining whether the TR data includes file data larger than or equal to the predetermined size, generating a TR table including information about a storage location of the TR data.
5. In claim 4,

   In response to transmitting the second storage request, receiving a hash value of the TR data from the IPFS,

   The TR table includes a hash value of the TR data.
6. In claim 1,

   In response to receiving the TR data from the at least one client device, requesting an identity and access management (IAM) server for an identifier of the at least one client device based on the TR data;

   Receiving an identifier of the at least one client device from the IAM server,

   A method comprising transmitting the identifier of the at least one client device and the TR data to the cloud server or the IPFS.
7. In claim 1,

   The TR data further includes information about the personal information of the user of the at least one client device, information about a certificate owned by the user, and educational background information of the user.
8. In claim 4,

   Receiving a CV transmission request from the at least one client device requesting to transmit a CV of a user of the at least one client device, and

   Based on information about the location where the TR data included in the TR table is stored, transmitting a TR transmission request requesting one or more TR data of the user to at least one of the cloud server and the IPFS; ,

   The CV transmission request includes filtering information for filtering the one or more TR data.
9. In claim 8,

   An operation of receiving at least one TR data of the user from at least one of the cloud server and the IPFS,

   An operation of generating the user's CV based on the at least one TR data and the filtering information, and

   Transmitting the generated CV of the user to the at least one client device.
10. In claim 1,

    An operation of receiving an authentication request for the TR data from the at least one client device,

    In response to receiving the authentication request for the TR data, transmitting an authentication request requesting to perform authentication of the TR data to the cloud server, and

    A method comprising receiving an authentication response to the authentication request from the cloud server.
11. In claim 1,

    An operation of transmitting a billing information request requesting transmission of billing information for the TR data to the cloud server,

    A method comprising receiving a billing information response including billing information regarding the TR data from the cloud server.
12. In claim 4,

    A method comprising updating the TR table when the server has transmitted file data identical to the file data of the predetermined size or more to the IPFS before receiving the TR data.
13. In a server device for creating and managing CVs (curriculum vitae) of a plurality of client devices,

    Ministry of Communications;

    Memory;

    Comprising at least one processor operably connected to the communication unit and the memory,

    The at least one processor:

    Receiving task receipt (TR) data containing information about a task performed by a user of the at least one client device from at least one client device through the communication unit,

    Determine whether the TR data includes file data of a predetermined size or more,

    When it is determined that the TR data does not include file data larger than the predetermined size, a first storage request containing the TR data is sent to a blockchain-based cloud server that stores TR data of the plurality of client devices through the communication unit. and send

    If it is determined that the TR data includes file data of a predetermined size or more:

    Identifying that said file data is not identical to other previously stored file data,

    Transmitting a second storage request including the file data to an InterPlanetary File System (IPFS) connected to the server device through the communication unit,

    The file data includes data related to at least one of images, videos, and sounds.
14. In claim 13,

    The at least one processor:

    In response to identifying that the file data is not identical to other previously stored file data, extract text information in the file data;

    determine whether the file data contains personal identification information of a user based on the text information;

    If it is determined that the file data does not contain the user's personal identification information, transmitting the second storage request containing the file data to an InterPlanetary File System (IPFS) connected to the server device;

    When determining that the file data contains personally identifiable information of the user, blur the portion relating to the personally identifiable information.
15. In claim 13,

    The at least one processor:

    In response to transmitting the second storage request to the IPFS, the device transmits remaining data excluding the file data of the TR data to the cloud server.

Images