WO2024090984A1 - Server apparatus for managing resume and operation method thereof - Google Patents

Abstract

An operation method for a server apparatus is disclosed. The operation method for the server apparatus according to an embodiment of the present disclosure comprises the operations of: receiving a task contract (TC) of a first apparatus for a first task from the first apparatus; receiving a TC of a second apparatus for the first task from the second apparatus matching the first apparatus; generating first TC data on the basis of the TC of the first apparatus for the first task and the TC of the second apparatus for the first task; and configuring a first TC table including information regarding an apparatus and application having access authority over the first TC data, wherein the first TC table includes the first apparatus and the second apparatus, any one of the first apparatus and the second apparatus corresponds to a worker who performs the first task, and the other one may correspond to an employer who provides the first task to the worker.

Description

Server device for managing resumes and its operation method

Embodiments disclosed in this document relate to a server device for managing resumes 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 workers 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, data related to job evaluation can be recorded through blockchain to create data that cannot be manipulated, thereby accumulating reliable evaluation data on workers. Additionally, workers' identities can be easily verified, for example, minimizing concerns about hacking.

In order to provide gig labor services, the online platform manages the information about the task (task contract, TC) provided by the worker to the employer, and the worker, employer, or authorized third party records this information. You will need to provide this information upon request. As forms of labor diversify, information on TC is also diversifying, and this information can be used as important data for workers and employers.

Embodiments disclosed in this document provide a device and a method of operating the same to allow authorized persons (e.g., workers who performed the work, employers who provided the work) to view information about work performed by workers. do.

In addition, it provides a device and operating method for granting workers the authority to view and modify information about work performed.

A method of operating a server according to an embodiment of the present disclosure includes receiving a TC (task contract) of the first device for a first task from a first device, matching with the first device. An operation of receiving, from a second device, a TC of the second device for the first task, based on the TC of the first device for the first task and the TC of the second device for the first task An operation of generating first TC data and setting a first TC table containing information about a device and an application having access to the first TC data, wherein the first TC table contains the first TC data. One device and the second device are included, one of the first device and the second device is a device corresponding to a worker performing the first task, and the other is a device that performs the first task. It may be a corresponding device provided by the employer to the worker.

A server according to an embodiment of the present disclosure includes a memory, a communication unit, and at least one processor electrically connected to the memory and the communication unit, and the at least one processor performs a first task from a first device. Receive a TC (task contract) of the first device for the first device, receive a TC of the second device for the first task from a second device matching the first device, and receive the TC of the second device for the first task. Information about devices and applications that generate first TC data based on the TC of the first device for the task and the TC of the second device for the first task, and have access to the first TC data Set a first TC table including, the first TC table includes the first device and the second device, and one of the first device and the second device performs the first task. One device corresponds to a worker, and the other device may correspond to an employer providing the first task to the worker.

According to the server and its operating method according to various embodiments disclosed in this document, it is possible to efficiently manage information about work performed by workers.

In addition, the server and its operating method provide the effect of safely managing personal information by setting the authority to access information about the work performed by workers.

In addition, the server and its operating method provide the effect of providing information about work performed by workers to authorized third parties, allowing the information to be utilized as part of property.

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.

FIG. 1A shows the configuration of a transaction system including an electronic device, a server, and a blockchain network according to an embodiment.

Figure 1B shows the block configuration of a server according to one embodiment.

Figure 2 shows an example of generating a curriculum vitae (CV) of a server according to an embodiment.

Figure 3 shows an example of CV generation of a server according to an embodiment.

Figure 4 shows an example of generating a CV of a server according to an embodiment.

Figure 5 shows an example of setting access permissions for a server according to an embodiment.

Figure 6 shows the operation flow of a server according to one embodiment.

Figure 7 shows the operation flow of a server according to one embodiment.

Figure 8 shows the operation flow of a server 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, various embodiments of the present invention are described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include various modifications, equivalents, and/or alternatives to the embodiments of the present invention. In the following description, the same/similar reference numbers are used for substantially the same components, and overlapping descriptions may be omitted.

FIG. 1A shows the configuration of a transaction system including an electronic device, a server, and a blockchain network according to an embodiment.

Referring to FIG. 1A , the transaction system 100 may include an electronic device 110, a server 130, and a blockchain network 150.

In one embodiment, the electronic device 110 may include a communication circuit 112, a secure memory 114, a processor 116, and a display 118. In one embodiment, the communication circuit 112 may establish a communication channel between the electronic device 110 and an external electronic device (eg, server 130) and transmit and receive data. For example, the communication circuit 112 may transmit data from the electronic device 110 performing a transaction to the server 130.

In one embodiment, the electronic device 110 may generate a key pair using asymmetric key cryptography (eg, public-key cryptography). A key pair may include a private key and a public key. In one embodiment, secure memory 114 may store the generated private key. In one embodiment, the secure memory 114 may refer to a hardware type memory that provides a security environment. For example, the secure memory 114 may be built into the electronic device 110 or may be a device that can be separately inserted into the electronic device 110 (eg, a micro SD card). For example, the secure memory 114 may refer to a memory that is hardware-separated from general memory. In another embodiment, the secure memory 114 may refer to memory in the form of software that is encrypted to provide a secure environment. For example, secure memory 114 may be a form of software that encrypts and stores data so that it can only be accessed through some configuration (e.g., TEE). For example, the secure memory 114 may be implemented on the same memory as the general memory, but may be in the form of software stored in a secure memory area that is separated by software (eg, memory address).

In one embodiment, the display 118 may visually provide information to the outside of the electronic device 110 (eg, to a user). For example, the display 118 may externally provide at least one of transaction creation information, balance information, transaction transmission delay information, and transaction completion information of the electronic device 110.

In one embodiment, the server 130 may include a communication unit 132, a memory 134, and a processor 136. In one embodiment, the communication unit 132 may transmit and receive data by establishing a communication channel between the server 130 and an external device (e.g., electronic device 110, blockchain network 150). For example, the communication unit 132 may transmit data received from the electronic device 110 to the blockchain network 150. The transmitted data may be stored in the blockchain node 152.

In one embodiment, the processor 136 may receive data from the electronic device 110 through the communication unit 132. In one embodiment, the processor 136 may identify a classification flag included in data received from the electronic device 110. In one embodiment, the processor 136 may determine whether to transmit the received data to the blockchain network 150 based on a distinction flag included in the data. For example, when the received data includes a specific classification flag (or when the value of the included classification flag is the first classification value), the processor 136 may store the received data in the memory 134. . For another example, when the received data does not include a specific distinction flag (or, if the value of the included distinction flag is a second distinction value that is distinct from the first distinction value), the processor 136 Data can be transmitted to the blockchain network 150. In one embodiment, the distinction flag may mean a distinction value included in a data packet. For example, if some bits of the data packet received from the electronic device 110 include the first classification value “1”, the processor 136 may store the received data in the memory 134. For another example, if some bits of the received data packet include the second distinction value “0”, the processor 136 may transmit the received data to the blockchain network 150. Figure 1A shows only a transaction system in which data generated by the electronic device 110 is transmitted to the blockchain network 150 through the server 130, but in another embodiment, data generated by the electronic device 110 A portion of may be transmitted directly to the blockchain network 150. For example, the electronic device 110 may directly transmit data that does not include a specific classification flag to the blockchain network 150. For another example, the electronic device 110 may transmit data including a specific classification flag to the server 130. The server 130, which has received data including a specific classification flag, can monitor the blockchain network 150. When an abnormal transaction is detected in the blockchain network 150, the server 130 may transmit data including a specific classification flag to the blockchain network 150. As another example, the electronic device 110 may store data including a specific classification flag in a memory (eg, secure memory 114). When an abnormal transaction is detected in the blockchain network 150, the server 130 may request the electronic device 110 to transmit data including a specific classification flag to the blockchain network 150.

Figure 1B shows the block configuration of a server according to one embodiment.

The server 130 according to an embodiment may refer to a server device for managing and providing information about tasks (eg, task contract (TC)) of a plurality of client devices.

In one embodiment, the client device may refer to an electronic device used by employers and employees (hereinafter referred to as “service users”) who use the resume creation and management service to receive the service. For example, a client device may mean a service user's portable terminal (e.g., smartphone, personal digital assistant (PDA), tablet PC, wearable device, etc.), laptop, PC, etc.

Referring to FIG. 1, the server 130 according to one embodiment may include a processor 136, a memory 134, and a communication circuit 132. The configuration shown in FIG. 1 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 server functions may be added, and the illustrated configurations may be omitted.

The memory 134 according to one embodiment is a storage medium used by the server 130 and can store data such as at least one command 121 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 134 is a flash memory type, hard disk type, multimedia card micro type, card type 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 circuit 132 according to one embodiment includes the server 130 and an external electronic device (e.g., a client device (not shown), an IAM server (not shown), a billing server (not shown), a cloud server (not shown), Direct (e.g. wired) communication between IPFS (not shown) can be performed. For example, communications circuitry 132 may receive TC data transmitted from a client device. Additionally, for example, communication circuitry 132 may transmit TC data to a cloud server (not shown) and IPFS (not shown) (e.g., blockchain network 150).

In one embodiment, the communication circuit 132 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, IAM server 130, billing server 170, cloud server 140, and IPFS 150).

In one embodiment, the communication circuitry 132 may support 5G networks after 4G networks and next-generation communication technologies, such as new radio access technology (NR access technology). NR access technology provides high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and access to multiple terminals (massive machine type communications (mMTC)), or ultra-reliable and low-latency (URLLC). -latency communications)) can be supported. Communication circuitry 132 may support high frequency bands (e.g., mmWave bands), for example, to achieve high data rates. The communication circuit 132 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 and output. It may support technologies such as full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna.

In one embodiment, the communication circuit 132 includes a server 130, an external electronic device (e.g., a client device (not shown), an IAM server (not shown), a billing server (not shown), a cloud server (not shown), It can support various requirements specified in IPFS (not shown) or network systems.

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

In one embodiment, as at least part of data processing or computation, processor 136 stores instructions or data received from another component (e.g., communication circuit 132) in volatile memory, and stores the instructions or data stored in volatile memory. Data can be processed and the resulting data can be stored in non-volatile memory.

In one embodiment, the processor 136 may be 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, processor 136 may receive TC data from at least one client device that includes information about tasks performed by a user of the at least one client device.

The processor 136 according to one embodiment may perform the operation of the server 130 described through the drawings below.

Figure 2 shows an example of CV (Curriculum vitae) generation according to one embodiment. 3 shows an example of CV generation according to one embodiment. 4 shows an example of CV generation according to one embodiment. The server device described in FIGS. 2 to 4 may refer to the server 130 of FIG. 1 .

The server device according to one embodiment includes a client device (a first device used by the worker performing the task, a second device used by the employer providing the task to the worker) and a blockchain-based cloud server (not shown) or blockchain. Information regarding work performed by at least one node (not shown) on a network (not shown) and an employee may be transmitted and received. In the following description, an employer may mean a person who instructs employees to do work and provides compensation accordingly, and may be referred to as “company,” “employee,” or equivalent terms. An employee may refer to a person who performs work instructed by an employer and is compensated accordingly, and may be referred to as “worker,” “employee,” “gig,” or equivalent terms. Additionally, the employer and the employee who use the CV management service according to embodiments of the present disclosure may be referred to as “service users.” In the following description, the first device may represent a device used by an employee to receive a resume management service. The second device may refer to a device used by employers to provide resume management services.

2 to 4, the server device generates TCs (220, 320, 420) based on TC data (e.g., 210, 310, 410), and generates CVs (e.g., 230, 420) based on the generated TCs. 330, 430) can be generated.

In one embodiment, the server device collects information about tasks (task contract, TC) provided by the employee to the employer from the first device and the second device (e.g., information about the work performed by the user (worker) of the first device). Information and information about work provided by the user (employer) of the second device) can be received. Although not shown in the drawing, the server device, the first device, and the second device may communicate TC through a specific interface (eg, mobile application, etc.).

In one embodiment, the server device may generate curriculum vitae (CV) through a plurality of blockchain layers. CV may refer to data containing information about at least one task performed by a worker or information about at least one task provided by an employee.

In one embodiment, the server device may generate TC data based on TC received from the first device and the second device. In one embodiment, TC data may be generated for each task performed. TC data may each include unique identification information (TC ID).

In one embodiment, TC data may include task data (non-fungible token (NFT) task), asset data (NFT-asset), and time (NFT-time) data. . For example, TC data can be classified as shown in Table 1 below.

-	category	Sub Category	example
TC data	NFT Task (task data)	Task	Task information performed by the user Task information created by the employer
	NFT Assets (asset data)	for sale	digital content Physical goods membership
		Not for sale	certificate recipe formula (e.g. a method of making cosmetics)
	NFT Time (time data)	license	License to use recipes/formulas, etc.
		course ticket	Cooking course ticket

In one embodiment, task data may include information about tasks performed by employees and information about tasks created by employers. For example, TC data may include the type of work performed by the employee, date, time, location, work content, and evaluation information about the employee. Figure 2 shows an example of generating a task data CV by combining task data, Figure 3 shows an example of generating an asset data CV by combining asset data, and Figure 4 shows an example of combining time data to generate a time data CV. An example of creation is shown. Referring to FIG. 2, the server device according to one embodiment includes a plurality of TCs (e.g., TC (210-1), TC (210-2), TC (210-3), ...TC (210-l). Based on this, combined task data can be created. A plurality of TCs may represent task data. In one embodiment, task data includes an identification number (ID), employee key value, category of work, subcategory, date of work performance, time of work performance, location of work performance, and information about the work performed. It may include the employer's evaluation, income paid for work performed, and attachments.

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

Category	Data
Task ID	001
Employer	ABC Food
State	Matched
User Address	DFKDUYF08A90FD
Category	Restaurant
Sub Category	Serving
Date	2022-06-03
Time	3 hours
Location	Gangnam-gu, Seoul
Feedback	Excellent
Income	60,000

The content included in <Table 1> above is only an example, and TC data may include not only the content included in Table 1 above, but also other content related to the work performed by the employee, and the content included in Table 1 above. Some of them may be omitted. In one embodiment, task data may include identification information (e.g., Task ID) of the work performed by the worker. The identification information of the work performed by the worker may represent an identifier generated for each task for the worker. In one embodiment, the task data may include information about the object that receives the work performed by the worker (eg, Employer). For example, the object that receives the work performed by the worker could be the employer. For example, the object that receives work performed by a worker may be a third party other than the worker or employer.

In one embodiment, task data may include information regarding the state of the task data. For example, the state of the task data may include a first state indicating that the employer has created the task, but the worker who will perform the task has not yet been matched. For example, the state of the task data may include a second state indicating that the worker who will perform the task created by the employer has been determined, but has not yet performed the task. For example, the state of the task data may include a third state indicating a state in which the worker has started performing the task. For example, the state of the task data may include a fourth state indicating a state in which the worker has completed performing the task. For example, the state of the task data may include a fifth state indicating that the worker has completed the task and the employer has completed payment of compensation. Task data in the fifth state may also be referred to as TR (task receipt) data.

Referring to FIG. 2, the server device according to one embodiment may store a plurality of task data (e.g., TC (210-1), TC (210-2), TC (210-3), ... TC (TR-l) ) can be combined to generate combined task data 220 (TC aggregation). For example, in the combined task data, the categories of work performed by the user are “restaurant” and “cleaning,” and the subcategories are “serving,” “delivery,” and “home cleaning.” clean)” may be included. Additionally, for example, the combined task data may include information indicating that the user performed work in “Gangnam-Gu” or “Yangcheon-Gu.” Also, for example, the combined data may include information about task performance times (e.g., 140 hours for delivery and 200 hours for serving). Additionally, for example, the combined task data may include feedback information about the work performed by the user (e.g., “excellent” for delivery and “excellent” for serving). there is.

In one embodiment, each of the plurality of TCs 210 may include a category, subcategory, work performance location, work performance time, and feedback information.

In one embodiment, the CV 230 includes information 232 regarding the user's personal information, information 234 related to certification of the work performed, information 236 related to the user's educational background, and work experience performed. It may include information 238 about. Information 238 regarding work experience performed may include at least a portion of the combined task data.

Referring to FIG. 3, the server device according to an embodiment includes at least one TC (310) among a plurality of TCs (e.g., TC (310-1), TC (310-2), TC (310-3), Based on TC (310-m)), combined asset data (NFT Tasks aggregation) can be created. At least one TC 310 may include a TC corresponding to asset data among a plurality of TCs (task data).

In one embodiment, asset data (NFT asset) may refer to information about assets held by a worker or employer. In one embodiment, asset data may include for-sale assets that can be sold and non-sale assets that cannot be sold. For example, among asset data, assets for sale may include digital content (e.g., images, videos, etc.), goods, membership, etc. Additionally, for example, among asset data, non-sale assets may include certificates, recipes, formulas for making cosmetics, etc. For example, asset data may have the form shown in Table 3 below.

Category	Data(example)
Task ID	002
State	Authorized
User Address	DSLFJI988DSVJSDKF
Category	Digital Contents
Sub Category	Movie Clip
CID	QmbWqx… … qsKc92xm

In one embodiment, the asset data may include identification information (e.g., Task ID) of the task. In one embodiment, the asset data may include information regarding the state (e.g., state) of the asset data. For example, the status of asset data for sale may include a “creation status” indicating the state in which the asset data was created. Also, for example, the status of asset data for sale may include a “certification status” indicating that authentication has been completed as to whether the asset data is recognized as a valid asset. Also, for example, the status of asset data for sale may include a “matching status” indicating that authentication of the asset data has not been completed, but has not yet been sold and is awaiting matching. Also, for example, the status of asset data for sale may include a “sale complete status” indicating a state in which the sale of the asset data has been completed.

For example, the status of non-sale asset data may include a “creation status” indicating the state in which the asset data was created. Also, for example, the status of non-sale asset data may include a “certification status” indicating that authentication has been completed as to whether the asset data is recognized as valid asset data. Also, for example, the status of non-sale asset data may include a “registration complete” status, which indicates that authentication and registration for the asset data have been completed.

In one embodiment, the asset data may include identifying information (e.g., user address) of the worker or employer. In one embodiment, asset data may include information about the type of asset (e.g., Category: Digital contents, Sub-Category: Movie Clip).

In one embodiment, asset data may include information about the location where the asset is stored (e.g., content ID (CID)).

Referring to FIG. 3, a server device according to an embodiment may store a plurality of task data (e.g., TC (310-1), TC (310-2), TC (310-3), ... TC (TR-m) ) can be combined to create combined asset data 320 (NFT Assets aggregation). For example, in the combined task data, the category of the task performed by the user may be “Digital Contents,” and the subcategories may be “image” and “movie clip.” Additionally, for example, combined asset data may include the number of asset data (# of assets), asset data sales volume (# of sold assets), total assets, information on market estimated price (market estimated price), total It may include information about total income, average monthly income (income avg per month), etc.

Referring to FIG. 4, the server device according to one embodiment includes at least one TC 410 (e.g., TC 410-1, TC 410-2, TC 410-3, ... TC 410). Time data 420 can be generated based on -l)). At least one TC 410 may include a TC corresponding to a non-sale asset among the at least one TC 310.

In one embodiment, time data may mean data converted from non-saleable asset data into a form that can be sold in the form of a course ticket, usage right, etc. For example, time data may have the form shown in Table 4 below.

Category	Data (example)
Task ID	003
State	Completed
User Address	VCJBKJSO0890DFJL12
Category	Voucher
Sub Category	Recipe
Expired date (or duration)	2022-10-08

In one embodiment, time data may include identification information (eg, Task ID) of the time data. In one embodiment, temporal data may include information regarding the state of the temporal data. For example, the status of time data may include “creation status” indicating the state in which the time data was created. For example, the status of time data may include “authentication status” indicating a state in which authentication regarding whether the time data is valid has been completed. For example, the state of the time data may include a “matching state” indicating a state in which a buyer of the time data is waiting to be matched. For example, the status of the time data may include a “sold” status indicating that a buyer for the time data has been matched. For example, the status of the time data may include a “used status” indicating that the use of the time data has been completed (e.g., license usage complete) after completion of sale. For example, the status of time data may include a “time expiration status” indicating that the validity period of time data has expired after completion of sale. In one embodiment, time data with a “completed” or “time expired” status may be delivered back to the Owner (e.g., worker or employer). In one embodiment, time data may include worker or employer identifying information (e.g., user address). In one embodiment, asset data may include information about the type of asset (e.g., Category: Voucher, Sub-Category: Recipe).

In one embodiment, time data may include information about the validity period of the time data (eg, expiration date).

Referring to FIG. 4, a server device according to an embodiment may store a plurality of time data (e.g., TC (410-1), TC (410-2), TC (410-3), ...TC (410-n) ) can be combined to generate combination time data 420 (NFT Time Aggregation). For example, the category of combination time data may be “Voucher” and the subcategories may be “Recipe” and “Class”. Additionally, for example, combined time data may include information about the number of assets (# of assets), total income, average income per month (income avg per month), feedback information (e.g. Class feedback: Excellent”, etc.) may include.

The server device according to one embodiment may generate CVs 230, 330, 430 based on combined TC data (e.g., combined task data, combined asset data, combined time data) combined through the aggregator. In one embodiment, the server device may transmit the CV to the first device and the second device through an application programming interface (API).

In one embodiment, the server device may receive information about the worker's profile (e.g., information about personal information, information about qualifications, education information, etc.) from the first device. In one embodiment, the server device may receive information about the employer's profile (e.g., information about personal information, information about operational work, information about the company operated by the employer, etc.) from the second device.

In one embodiment, although not shown in the drawing, the server device may transmit a message requesting to store information about the profiles of workers and employers received from the first device and the second device to the cloud server. Accordingly, the cloud server can store information about the profiles of workers and employers.

Figure 5 shows an example of setting access rights for a server device according to an embodiment. Figure 6 shows the operation flow of a server device according to an embodiment. The operations of the server device performed in FIGS. 5 and 6 may be performed on the blockchain layer, and the results generated by performing at each layer (e.g., TC data, TC table, CV data, etc.) are stored only in the memory of the server device. Rather, it can be stored in nodes of the blockchain network.

According to one embodiment, in operation 610, the server device may receive the TC of the first device for the first task from the first device. For example, referring to FIG. 5, the server 130 may receive the TC of the first device 501-1 for the first task from the first device 501-1.

In one embodiment, the first device may represent a device used by an employee to receive a resume management service.

In one embodiment, the TC of the first device may mean information about work performed by the worker. For example, the TC of the first device may include task data, asset data, and time data described in FIGS. 2 to 4.

According to one embodiment, in operation 620, the server device may receive the TC of the second device for the first task from the second device that matches the first device. For example, the server 130 may receive the TC of the second device 502-1 for the first task from the second device 502-1.

In one embodiment, the second device may refer to a device used by an employer to provide a resume management service.

In one embodiment, the TC of the second device may refer to information about work provided by the employer to the worker. For example, the TC of the first device may include task data, asset data, and time data described in FIGS. 2 to 4.

In one embodiment, the first device and the second device may be matched when a worker is determined to perform a task created by the employer.

According to one embodiment, in operation 630, the server device may generate first TC data based on the TC of the first device for the first task and the TC of the second device for the first task. For example, the server 130 may generate first TC data 512 based on the TC of the first device 501-1 for the first task and the TC of the second device 502-1 for the first task. can be created.

According to one embodiment, in operation 640, the server device may create a first TC table 513 containing information about devices and applications having access to the first TC.

In one embodiment, the access rights may include access rights to the TC and access rights to the CV. In one embodiment, the access rights may include a first right to view only, a second right to view and modify, and a third right to view, modify, and grant permission. For example, access rights may have the form shown in Table 5 below.

Privilege level	scope of authority
Owner (third authority)	- Owner can edit/view - Acting and Viewer ratings can be specified
Acting (second authority)	- Owner agency, modification/viewing possible - Viewer rating can be specified
Viewer (primary authority)	- Available for viewing

In one embodiment, permission levels may include Owner, Acting, and Viewer. Owner may represent the owner of a Task Contract or NFT CV. If you have owner authority, you can edit or view the TC or CV. Additionally, a device with Owner privileges can specify Acting and Viewer privileges. In one embodiment, a device with an Acting level can mean a role that acts as an Owner. For example, when user A performs task B through an application called C, if C is given an Acting grade, after the performed task is created and date or time errors are discovered, TC correction is made to C. You can do it quickly. Additionally, a device with the Acting level can modify Viewer permissions. In one embodiment, a device with the Viewer level can view the TC or CV, but may not have the permission to modify it.

In one embodiment, there may be priorities among access rights, and the priorities may be in the following order: Owner, Acting, and Viewer.

In one embodiment, when a task contract is created, the server device can set the owner first. For example, the worker who performed the task and the employer who provided the task can have owner authority. Also, for example, in the case of an NFT Asset, the server device can set the owner of the Asset as Owner.

In one embodiment, when Owner authority for a TC or CV is determined, the Owner may designate a device with Acting authority. A device with Acting authority can take on the role by receiving authority from the Owner. Additionally, after the device with Acting privileges is determined, the device with Owner or Acting privileges can determine the device with Viewer privileges.

In one embodiment, a table representing access rights may also have the form shown in Table 6 or Table 7 below.

authority	item	expiration period
Owner	Worker02	Permanent
Acting	App02(client application)	Sign Up
Viewer	Platform company A	Permanent
	Platform company B	Permanent
	Platform company C	2022.12.31.
	Financial company A	Permanent
	Financial company B	2022.08.31.

In one embodiment, the permission table may include information about who is assigned to each permission and how long it is valid. For example, in the case of an Owner, there is no separate validity period and may have a permanent validity period. Also, for example, the validity period of the permission can be set to while subscribed to the app. Also, for example, Platform Company A and B can always have Viewer rights, and Platform Company C can have rights until the end of 22 years. For example, when a server device receives a permission request from a specific device (e.g. Financial Company B), it can be set to have permission for a predetermined period of time (e.g. a week).

authority	item	expiration period
Owner	Worker 02	Permanent
Acting	APP02(Client Application)	Sign up
Viewer	All platform companies	Permanent
	All financial companies	2022-12-31

In one embodiment, Viewer items may be designated one by one, such as Platform Company A, B, and C, but may be set according to a preset Preset. For example, the server device can enable all job platform companies to view my NFT CV, and financial-related companies can view it at a specific point in time (e.g., 2022). In one embodiment, the server device is an object that transmitted the combined TC to generate TC data (e.g., in the case of the first TC data 513, the first device 501-1 and the second device 502-1) Since each TC has been received from , it can be determined that the first device 501-1 and the second device 502-1) have third authority over the TC data. For example, the server 130 has the first device 501-1, the second device 502-1, the third device 502-3, and App01 as the first authority for the first TC data 512. With this, the first TC table 513 can be created so that the first device 501-1 and the second device 501-2 have the second authority and the third authority.

In one embodiment, the server device may receive TC data of a second device for a second task from a second device, and may receive TC of another first device for a second task from another first device. The server device may generate second TC data based on the TC of the second device for the second task and the TC of another first device for the second task. The server device may create a second TC table containing information about devices and applications that have access to the second TC data. For example, the server 130 receives the TC of the second device for the second task from the second device 502-1 and the TC of the first device for the second task from the first device 501-1. TC can be received. The server 130 may generate the second TC data 514 based on the TC of the second device 502-1 for the second task and the TC of the first device 501-2 for the second task. there is. The server 130 is a device having access to the second TC data 514 (e.g., first authority: second device 502-1, second device 502-2, third device 502- 3), a second TC table 515 containing information about the fourth device (502-4), second authority: application (App01)) can be created.

In one embodiment, the server device may generate the first CV by combining the first TC data and the second TC data. The server device may create a first CV table containing information about devices and applications that have access to the first CV. For example, the server 130 may generate the first CV 532 by combining the first TC data 512 and the second TC data 514 through the aggregator 522. The server 130 may create a first CV table 533 containing information about devices and applications that have access to the first CV 532.

In one embodiment, the server 130 may receive a TC of another first device for a third task from another first device and receive a TC of another second device for a third task from another second device. there is. The server device may generate third TC data based on the TC of another first device for the third task and the TC of the other second device for the third task. The server device may set up a third TC table containing information about devices and applications that have access to third TC data. For example, in one embodiment, the server 130 receives the TC of the first device 501-2 for the third task from the first device 501-2, and the second device 502-2 The TC of the second device 502-2 for the third task may be received from. The server 130 may generate third TC data 516 based on the TC of the first device 5021-2 for the third task and the TC of the second device 502-2 for the third task. there is. The server 130 provides information about devices and applications that have access to the third TC data 516 (e.g., the third authority includes the first device 501-2, the second device 502-2, and the third device 501-2). 1 authority is the second device (502-1), the second device (502-2), the third device (502-3), the fourth device (502-4), the second authority is the third device including APP01) The TC table 533 can be set.

In one embodiment, the server device may combine the second TC data and the third TC data to generate a second CV, the second CV including information about devices and applications that have access to the second CV. You can create a table. For example, the server 130 may generate the second CV 534 by combining the second TC data 514 and the third TC data 516 through the aggregator 524. The server 130 may create a second CV table 535 that includes information about devices and applications that have access to the second CV 534.

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

According to one embodiment, in operation 710, the server device may receive a CV access request from a third device. A CV access request may include a request to view or modify a CV.

According to one embodiment, in operation 720, the server device may determine whether the third device has CV access authority in response to receiving the CV access request. In one embodiment, the server device may determine whether the third device has CV access authority based on the CV table for the CV corresponding to the CV access request. For example, if a third device is included in the access authority table of the CV corresponding to the CV access request, it may be determined that the third device has CV access authority. If the third device is not included in the access authority table of the CV corresponding to the CV access request, the server device may determine that the third device does not have CV access authority.

According to one embodiment, in operation 730, when the server device determines that the third device has CV access authority, it may transmit data related to the CV corresponding to the CV access request to the third device.

According to one embodiment, in operation 740, when the server device determines that the third device does not have CV access authority, it transmits an access permission request to at least one device that has access authority to the CV corresponding to the CV access request. can do.

In one embodiment, when receiving an access authorization response from at least one device with access authority, the server device may transmit data related to the CV to the third device. In one embodiment, when an access authorization response is not received from at least one device with access authority, a rejection may be transmitted to a third device.

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

According to one embodiment, in operation 810, the server device may receive a TC modification request from the fourth device. If there is incorrect information in the TC or something needs to be added, it can be modified. However, an entity with the authority to modify the TC (e.g., the employer who created the TC, the worker who performed the task of the TC) needs to modify it. There is.

According to one embodiment, in operation 820, the server device may determine whether a second authority or a third authority for the TC exists in the fourth device.

In one embodiment, the server device may determine whether the fourth device has second authority or third authority for the TC based on whether the fourth device is included in the TC table.

According to one embodiment, when the server device determines that a second authority or a third authority exists in the fourth device, in operation 830, the server device may modify the TC corresponding to the TC modification request.

According to one embodiment, if the server device determines that the second authority or the third authority does not exist in the fourth device, in operation 840, the server device grants the third authority to the TC based on the TC's access authority table. A modification confirmation request can be sent to the device having the modification.

In one embodiment, when the server device receives a modification authorization response from a device with third authority, the server device may modify the TC table by reflecting the modification requested by the fourth device.

In one embodiment, if the server device does not receive a modification authorization response from the device with third authority, the server device may send a rejection to the fourth device.

In one embodiment, when the server device receives a CV access request from a specific application, all CVs given to the specific application with Acting permission can be sent to the specific application.

In one embodiment, in the description according to FIGS. 1 to 6, data received by the server device 130 from the electronic device 110 (e.g., TC), data generated by the server device 130 (e.g., TC data) , TC table, CV data) may be stored in the memory of the server device (e.g., memory 134), on an external server (e.g., cloud server), or on the node 152 of the blockchain network 150.

A method of operating a server device according to an embodiment of the present disclosure includes receiving a TC (task contract) of the first device for a first task from a first device, matching with the first device. ), an operation of receiving, from a second device, a TC of the second device for the first task, a TC of the first device for the first task, and a TC of the second device for the first task. An operation of generating first TC data based on the first TC data, setting a first TC table containing information about a device and an application having access to the first TC data, and the first TC table includes the A first device and a second device are included, one of the first device and the second device is a device corresponding to a worker performing the first task, and the other is a device that performs the first task. It may be a corresponding device provided by the employer to the worker.

In one embodiment, a method of operating a server device includes receiving a TC of the second device for a second task from the second device, receiving the TC for the second task from a first device different from the first device. An operation of receiving a TC of another first device, an operation of generating second TC data based on the TC of the second device for the second task and the TC of the other first device for the second task, An operation of setting a second TC table containing information about devices and applications having access rights to second TC data, wherein the second TC table may include the other first device and the second device. there is.

In one embodiment, a method of operating a server device includes generating a first CV by combining the first TC data and the second TC data, and information about devices and applications having access to the first CV. An operation of setting a first CV table including, and the first CV table may include the second device.

In one embodiment, a method of operating a server device includes receiving a TC of the other first device for a third task from the other first device, receiving a TC of the other first device for the third task from the other second device. An operation of receiving a TC of a device, an operation of generating third TC data based on the TC of the other first device for the third task and the TC of the other second device for the third task, the third An operation of setting a third TC table containing information about devices and applications having access to TC data, and the third TC table may include the other first device and the other second device. .

In one embodiment, a method of operating a server device includes generating a second CV by combining the second TC data and the third TC data, and information about devices and applications having access to the second CV. An operation of generating a second CV table including, wherein the second device, the other first device, and the other second device may be included in the second CV table.

In one embodiment, a method of operating a server device includes receiving a CV access request from a third device, and in response to receiving the CV access request, determining whether the third device has CV access authority; If the third device determines that the third device has CV access authority, transmitting data related to the CV corresponding to the CV access request to the third device. If the third device determines that the third device does not have CV access authority, the third device transmits data related to the CV corresponding to the CV access request. It may include transmitting an access permission request to at least one device that has access authority to the CV corresponding to the CV access request.

In one embodiment, the operating method of the server device includes, when the third device is included in the access authority table of the CV corresponding to the CV access request, determining that the third device has CV access authority, If the third device is not included in the access authority table of the CV corresponding to the CV access request, it may include determining that the third device does not have CV access authority.

In one embodiment, the method of operating the server device includes the following: a first authority that allows only viewing, a second authority that allows viewing and modification, and a third authority that allows viewing, modification, and granting of authority. May include permissions.

In one embodiment, an operating method of a server device includes receiving a TC modification request from a fourth device, and in response to receiving the TC modification request, determining whether the fourth device has the second authority or the third authority. An operation of determining whether the fourth device has the second authority or the third authority, an operation of modifying TC data corresponding to the TC modification request, if the fourth device determines that the second authority or the third authority is When it is determined that there is no third authority, the method may include transmitting a modification confirmation request to a device with the third authority for the TC based on the access authority table of the TC.

In one embodiment, the operating method of the server device includes receiving a modification permission response in response to the modification confirmation request sent to the device having the third authority for the TC, and responding to receiving the modification authorization response. This may include an operation of modifying the TC data.

A server device according to an embodiment of the present disclosure includes a memory, a communication unit, and at least one processor electrically connected to the memory and the communication unit, wherein the at least one processor receives a first task from a first device. ), receive a TC (task contract) of the first device for the first device, receive a TC of the second device for the first task from a second device matching the first device, and 1 Generating first TC data based on the TC of the first device for the task and the TC of the second device for the first task, and relating to a device and an application having access to the first TC data Set a first TC table containing information, the first TC table includes the first device and the second device, and one of the first device and the second device performs the first task. A device corresponds to a worker, and the other device may correspond to an employer who provides the first task to the worker.

The server device according to an embodiment receives the TC of the second device for the second task from the second device, and receives the TC of the second device for the second task from the first device and the other first device. Receive a TC of, generate second TC data based on the TC of the second device for the second task and the TC of the other first device for the second task, and generate second TC data for the second TC data. A second TC table containing information about devices and applications with access rights is set, and the second TC table may include the other first device and the second device.

The server device according to an embodiment generates a first CV by combining the first TC data and the second TC data, and includes information about a device and an application having access to the first CV. 1 CV table is set, and the first CV table may include the second device.

The server device according to an embodiment receives the TC of the other first device for the third task from the other first device, and receives the TC of the other second device for the third task from the other second device. Receive, generate third TC data based on the TC of the other first device for the third task and the TC of the other second device for the third task, and have access to the third TC data. A third TC table containing information about devices and applications is set, and the third TC table may include the other first device and the other second device.

In the server device according to an embodiment, the at least one processor generates a second CV by combining the second TC data and the third TC data, and the device and application have access to the second CV. A second CV table containing information about may be generated, and the second device, the other first device, and the other second device may be included in the second CV table.

The server device according to an embodiment receives a CV access request from a third device, and in response to receiving the CV access request, determines whether the third device has CV access authority, and determines whether the third device has CV access authority. If it is determined that there is CV access authority, data related to the CV corresponding to the CV access request is sent to the third device, and if the third device determines that there is no CV access authority, data related to the CV corresponding to the CV access request is sent to the third device. An access permission request may be sent to at least one device that has access authority to the CV.

The server device according to an embodiment determines that the third device has CV access authority when the third device is included in the access authority table of the CV corresponding to the CV access request, and responds to the CV access request. If the third device is not included in the access authority table of the corresponding CV, it may be determined that the third device does not have CV access authority.

In the server device according to one embodiment, the access rights to the TC or CV include a first right to view only, a second right to view and modify, and a third right to view, modify, and grant permission. can do.

The server device according to an embodiment receives a TC modification request from a fourth device, and in response to receiving the TC modification request, determines whether the fourth device has the second authority or the third authority, and , if the fourth device determines that it has the second authority or the third authority, modify the TC data corresponding to the TC modification request, and determine that the fourth device does not have the second authority or the third authority. If determined, a modification confirmation request may be transmitted to the device with the third authority for the TC based on the access authority table of the TC.

According to claim 1, the server device according to one embodiment may store the TC of the first device, the TC of the second device, first TC data, and a first TC table in the memory.

Server devices according to various embodiments disclosed in this document may be of various types. Server devices may include, for example, display devices, portable communication devices (eg, smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliance devices. The server device according to the embodiment of this document is not limited to the above-described devices.

Server devices according to various embodiments disclosed in this document may be of various types. Server devices may include, for example, display devices, portable communication devices (eg, smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliance devices. The server device according to the embodiment of this document is 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, but 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 this disclosure are only intended to designate the presence of features, components, parts, or combinations thereof described in this 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 those components 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 means “when” or “when” or “in response to determining” or “in response to detecting,” depending on the context. It can be interpreted. Similarly, “when it is determined” or “when it is detected” is taken to mean “when determining” or “in response to determining,” or “when detecting” or “in response to detecting,” depending on the context. It can be interpreted.

The program executed by the server device 200 described throughout this document may be implemented with 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 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 identically or similarly to 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 that communicates with an electronic device and a blockchain network,

   An operation of receiving, from a first device corresponding to a worker performing a first task, a task contract (TC) of the first device for the first task,

   receiving, from a second device corresponding to an employer providing the first task to the worker, a TC of the second device for the first task;

   Generating first TC data based on the TC of the first device for the first task and the TC of the second device for the first task,

   An operation of creating a first TC table including information about access rights to the first TC data and information about a validity period for each access right of the first TC data,

   An operation of receiving a permission setting request containing information about permission setting of a specific device different from the first device and the second device from at least one of the first device or the second device,

   In response to receiving the permission setting request, modifying the first TC table,

   Comprising the operation of storing the first TC table in the blockchain network,

   Information regarding the above access rights:

   Information about devices and applications with a first right to read, information about devices and applications with a second right to read and modify, and a third right to read, modify and grant permission. Contains information about devices and applications having,

   The method of claim 1, wherein the device having third authority over the first TC data includes the first device and the second device.
2. In claim 1,

   An operation of receiving a TC of the second device for a second task from the second device,

   An operation of receiving a TC of the other first device for the second task from a first device different from the first device,

   Generating second TC data based on the TC of the second device for the second task and the TC of the other first device for the second task,

   Comprising the operation of setting a second TC table containing information about access rights to the second TC data and information about the validity period for each access right of the second TC data,

   The method of claim 1, wherein the device having the third authority over the second TC data includes the other first device and the second device.
3. In claim 2,

   Generating a first CV by combining the first TC data and the second TC data,

   Comprising the operation of creating a first CV table including information about the access rights of the first CV and information about the validity period for each access right of the first CV,

   The method of claim 1, wherein the third authoritative device for the first CV includes the second device.
4. In claim 3,

   An operation of receiving a TC of the other first device for a third task from the other first device,

   An operation of receiving a TC of the second device for the third task from another second device,

   An operation of generating third TC data based on the TC of the other first device for the third task and the TC of the other second device for the third task,

   Comprising the operation of creating a third TC table containing information about access rights to the third TC data and information about the validity period for each access right of the third TC data,

   The method wherein the device having the third authority for the third TC data includes the other first device and the other second device.
5. In claim 4,

   Generating a second CV by combining the second TC data and the third TC data,

   Comprising the operation of creating a second CV table including information about the access rights of the second CV and information about the validity period for each access right of the second CV,

   The method of claim 1, wherein the device having the third authority over the second CV includes the second device, the other first device, and the other second device.
6. In claim 5,

   Receiving a CV access request from a third device,

   In response to receiving the CV access request, determining whether the third device has CV access authority;

   When the third device determines that the third device has CV access authority, transmitting data related to the CV corresponding to the CV access request to the third device;

   When the third device determines that it does not have CV access authority, transmitting an access permission request to at least one device that has access authority to the CV corresponding to the CV access request.
7. In claim 6,

   If the third device is included in the access authority table of the CV corresponding to the CV access request, determining that the third device has CV access authority;

   When the third device is not included in the access authority table of the CV corresponding to the CV access request, determining that the third device does not have CV access authority.
8. In claim 6,

   Receiving a TC modification request from a fourth device;

   In response to receiving the TC modification request, determining whether the fourth device has the second authority or the third authority;

   If the fourth device determines that there is the second authority or the third authority, modifying TC data corresponding to the TC modification request,

   When the fourth device determines that it does not have the second authority or the third authority, transmitting a modification confirmation request to the device with the third authority for the TC based on the access authority table of the TC. How to.
9. In claim 8,

   An operation of receiving a modification permission response in response to the modification confirmation request transmitted to the device having the third authority for the TC,

   Modifying the TC data in response to receiving the modification authorization response.
10. In electronic devices and server devices that communicate with blockchain networks,

    Memory;

    Ministry of Communications;

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

    The at least one processor:

    Receiving a task contract (TC) of the first device for the first task from a first device corresponding to a worker performing the first task,

    receive, from a second device corresponding to an employer providing the first task to the worker, a TC of the second device for the first task;

    Generate first TC data based on the TC of the first device for the first task and the TC of the second device for the first task,

    Creating a first TC table containing information about access rights to the first TC data and information about the validity period for each access right of the first TC data,

    Receiving a permission setting request containing information about permission setting of a specific device different from the first device and the second device from at least one of the first device or the second device,

    In response to receiving the permission setting request, modify the first TC table, and

    Configured to store the first TC table in the blockchain network,

    Information regarding the above access rights:

    Information about devices and applications that have a first right to read, information about devices and applications that have a second right to read and modify, and third parties that are allowed to set view, modify, and access rights. Contains information about authorized devices and applications,

    The device having the third authority for the first TC data includes the first device and the second device.
11. In claim 10,

    The at least one processor:

    Receiving the TC of the second device for the second task from the second device,

    Receiving a TC of the other first device for the second task from a first device different from the first device,

    Generate second TC data based on the TC of the second device for the second task and the TC of the other first device for the second task,

    Configured to create a second TC table containing information about access rights to the second TC data and information about the validity period for each access right of the second TC data,

    The second TC data includes the other first device and the second device.
12. In claim 11,

    The at least one processor:

    Combining the first TC data and the second TC data to generate a first CV,

    Configured to generate a first CV table containing information about the access rights of the first CV and information about the validity period for each access right of the first CV,

    The device having the third authority over the first CV includes the second device.
13. In claim 12,

    The at least one processor:

    Receiving a TC of the other first device for a third task from the other first device,

    Receiving a TC of the second device for the third task from another second device,

    Generating third TC data based on the TC of the other first device for the third task and the TC of the other second device for the third task,

    Configured to create a third TC table containing information about access rights to the third TC data and information about the validity period for each access right of the third TC data,

    The device having the third authority for the third TC data includes the other first device and the other second device.
14. In claim 13,

    The at least one processor:

    Combining the second TC data and the third TC data to generate a second CV,

    configured to create a second CV table containing information about devices and applications having access to the second CV;

    The device having the third authority for the second CV includes the second device, the other first device, and the other second device.
15. In claim 14,

    The at least one processor:

    3 Receive a CV access request from the device,

    In response to receiving the CV access request, determine whether the third device has CV access permission,

    If the third device determines that it has CV access rights, transmit data related to the CV corresponding to the CV access request to the third device,

    If the third device determines that it does not have CV access authority, send an access permission request to at least one device that has access authority to the CV corresponding to the CV access request.

Images