KR20210061061A - Platfrom for providing sharing economy service based on sal(secure access lock) module and block chain - Google Patents

Abstract

Provided is a sharing economy platform combining an SAL module and a blockchain. According to an embodiment, the sharing economy platform combining an SAL module and a blockchain comprises: a communication unit for performing communication with a user terminal; a shared space register unit for registering shared space information for a plurality of shared spaces; a shared space recommendation unit for recommending a shared space among the plurality of shared spaces, when a rental request for the shared space is transmitted from the user terminal; and a sharing space permission control unit for providing whether the user terminal has a sharing space permission for the selected specific shared space, when the sharing space permission is selected among the recommended shared spaces.

Description

Sharing economy platform combined with SAL module and blockchain {PLATFROM FOR PROVIDING SHARING ECONOMY SERVICE BASED ON SAL(SECURE ACCESS LOCK) MODULE AND BLOCK CHAIN}

The present invention relates to a sharing economy platform in which a SAL module and a block chain are combined, and in detail, the security of the sharing economy service is improved by using a block chain-based smart contract and a SAL (Secure Access Lock) module together. It is about a sharing economy platform that combines SAL modules and blockchains that can be used.

Recently, a number of sharing economy methods based on cooperative consumption in which a product produced once is shared and used by a plurality of users are emerging. In particular, a number of Sharing Economy services that connect to others to temporarily use resources such as offices, accommodation facilities, and furniture owned by a specific person have recently emerged and are showing high utilization rates. However, in the conventional sharing economy service, as users diversify, new risks such as trust, safety, loss, and security among users appear, and there is a problem that security is weak due to problems such as personal information leakage and hacking.

Republic of Korea Patent Publication No. 10-2018-0105044 (published on September 27, 2018)

The present invention was conceived to solve the above problems, and an aspect of the present invention is to provide a sharing economy platform in which an SAL module capable of providing various shared transaction services and a blockchain are combined.

The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems that are not mentioned will be clearly understood by those skilled in the art from the following description.

The sharing economy platform combined with the SAL module and the blockchain according to an embodiment of the present invention includes a communication unit that performs communication with a user terminal, a shared space registration unit that registers shared space information for a plurality of shared spaces, and a shared space from the user terminal. When a rental request is transmitted, a shared space recommendation unit that recommends a shared space among a plurality of shared spaces, and when a specific shared space is selected from among the recommended shared spaces, it provides the user terminal's shared space permission for the selected specific shared space. It includes a shared space authority control unit.

In addition, the shared space permission control unit may include a shared space password providing unit that generates a one-time password for the user terminal and provides it to the user terminal when the shared space permission of the user terminal is granted.

The sharing economy platform in which the SAL module and the blockchain are combined according to an embodiment of the present invention can provide a variety of sharing transaction services.

In addition, the sharing economy platform combined with the SAL module and the blockchain according to the embodiment of the present invention improves the security of the sharing economy service by using a blockchain-based smart contract and a SAL (Secure Access Lock) module together. I can make it.

1 is a diagram showing a sharing economy platform in which an SAL module and a block chain are combined according to an embodiment of the present invention.
FIG. 2 is a block diagram showing the configuration of a sharing economy platform in which the SAL module of FIG. 1 and a block chain are combined.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various forms different from each other, and only these embodiments make the disclosure of the present invention complete, and common knowledge in the technical field to which the present invention pertains. It is provided to completely inform the scope of the invention to the possessor, and the invention is only defined by the scope of the claims. The same reference numerals refer to the same elements throughout the specification.

Although the first, second, etc. are used to describe various elements, components and/or sections, of course, these elements, components and/or sections are not limited by these terms. These terms are only used to distinguish one element, component or section from another element, component or section. Therefore, it goes without saying that the first element, the first element, or the first section mentioned below may be a second element, a second element, or a second section within the technical idea of the present invention.

The terms used in the present specification are for describing exemplary embodiments and are not intended to limit the present invention. In this specification, the singular form also includes the plural form unless specifically stated in the phrase. As used in the specification, "comprises" and/or "made of" a referenced component, step, operation and/or element is one or more of the other elements, steps, operations and/or elements. It does not exclude presence or addition.

Unless otherwise defined, all terms (including technical and scientific terms) used in the present specification may be used with meanings that can be commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in a commonly used dictionary are not interpreted ideally or excessively unless explicitly defined specifically.

In this case, the same reference numerals refer to the same elements throughout the specification, and it will be understood that each configuration of the flowchart diagrams and combinations of the flowchart diagrams may be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart configuration(s). It creates a means to perform functions.

In addition, it should be noted that in some alternative embodiments, functions mentioned in the configurations may occur out of order. For example, two configurations shown in succession may in fact be performed substantially simultaneously, or the configurations may sometimes be performed in the reverse order depending on the corresponding function.

[Sharing Economy Blockchain Platform Architecture Design]

ㅇ Construction items

EOSIO keosd Item Detail Remark EOSIO wallet <wallet>
-A wallet in EOSIO (EOSIO platform) refers to a series of storages that store public-private key-pairs (these key-pairs are required to perform signatures on the blockchain)
-The wallet is managed through keosd and can be accessed through cleos.
-The wallet file is saved under the name 00.wallet, and default.wallet is created as an initial value.
-When creating each wallet, a password is created. At this time, the password is required to be saved and used to unlock the wallet in the future.
-The wallet can be used only when it is open, and it is exposed to the wallet inquiry list only in the open state.
-When keosd is restarted, all wallets are executed in a closed state.
-The wallet in the close state has the 00.wallet file, but it is inactive and must be activated through the open command to be used.
-Wallets in unlock status are marked with'*' in the wallet list When creating a wallet, it is possible to specify the wallet name. keosd
Process execution <keosd: abbreviation for key + eos>
-keosd path: eos/build/programs/keosd
-Plays the role of managing EOSIO's key and wallet
-Used by the cleos program to store the private key that will be used to sign the transaction to be sent to the blockchain. keosd only works on the local computer and the private key is also stored locally. keosd settings -Auto lock
-By default, the wallet is set to lock after 15 minutes of inactivity.

EOSIO BP settings Item Detail EOSIO BP definition -In EOS, which adopts the DPos method, a representative node elected by voting generates a block, and the rest of the nodes do not generate a block.
-Representative nodes elected by voting are called block producers (BP), and other nodes are called non-BP or full nodes.
-The 21 elected BPs are delegated the authority to operate the EOS blockchain, collecting transactions in the network, verifying transactions, and adding them to blocks.
-Since there is no need to pay attention to the rest of the nodes except for the representative node, blocks can be stably generated, resulting in improved block generation speed. EOSIO BP settings
(eosio.bios) <eosio.bios>
-After starting nodeos for the first time, it is distributed to the Genesis (eosio) account, and it is a system contract that has the function of allocating resources and designating BP.
<Settings>
-Register an eosio.bios contract with an eosio account.
-Enter the BP account name you want to designate when executing the action.
-A maximum of 21 people can be designated as a JSON array. EOSIO BP settings
(eosio.system) <eosio.system>
-Provides a contract for token-based operation. It is a contract that has functions to stake and unstake tokens, purchase resources, register BP candidates, vote, and set producer compensation.
<Settings>
-Register an account as a BP candidate in a multi-node environment without the enable satle production option.
-Vote for accounts registered as candidates for token stake accounts. At this time, more than 15% of the total token issuance must be staked and voted.
-Set the producer-name option to an account.
-Defines a tuple in the signature-provider by setting the private public key with the authority for the account.
-Define the p2p-peer-address list.
-Required plugin loading is as follows.
Chain_plugin: A core plugin required to process node set chain data
·Producer_plugin: required function for nodes to produce blocks

EOSIO nodeos Item Detail EOSIO node server <node server (nodeos)>
-The node server literally means the node that runs the actual blockchain, and the client accesses the node server and the wallet server, issues commands, and receives the result.
-Used for block production, dedicated API endpoint, and local development. nodeos
Process execution -nodeos: abbreviation for node + eos
-Producing Node: Connects to the Peer to Peer network and actively creates new blocks.
-Non-producing Node: Connects to the Peer to Peer network, but does not create a new block. Simply checks the block and maintains a local copy of the blockchain. It can be used to monitor the blockchain. Monitoring status
(Monitoring the status of transactions in the blockchain) 3 modes of nodeos
-Speculative (default mode): You can see the transaction and state changes up to the current head block and the pending block changes, and the state changes of the pending blocks are also included in the chain state file.
-Head: You can see the transaction and state change up to the current head block. Creates a pending block but is not included in the chain state file.
-Read: You can see the transaction and state change up to the current head block. Do not create pending blocks. eosio plugin <chain_plugin>
-Core plugin required to process EOSIO node set chain data
<http_plugin>
-Core plug-in required to use the RPC API on the EOSIO node.
<net_plugin>
-Provides p2p protocol to continuously synchronize nodes.
<net_api_plugin>
-Provides RPC API interface function managed from net_plugin to http_plugin.
<producer_plugin>
-This is a necessary function for a node to create a block.
<producer_api_plugin>
-Provides RPC API interface function managed by http_plugin in producer_plugin.
<state_history_plugin>
-It is useful for obtaining historical data by caching blockchain data as a file.

EOSIO_CDT eosio.bios Build: Smart Contract SET Item Detail EOSIO CDT -EOSIO Contract Development Toolkit
-Used as an EOSIO smart contract development tool, used to compile smart contracts and create ABI files Smart contract source code -Generate cpp/hpp files and implement smart contract source code using C++ language Smart contract compilation -Compile smart contract source code to create wasm file / abi file

[Web service architecture design] Item Detail Smart contract
Push Action Controller -Smart contract execution: Java SSHExecutor library used -Visitor management: Create a session object according to the visitor -EOSIO mainnet connection: Create SSHExecutor connection using Java Thread class inheritance HTTP Restful API -Method: HTTP METHOD / Data type: JSON -Sharing economy service monitoring I/O Request role -Smart contract action requested by the sharing economy service dApp
-Plays the role of CRUD -Exception handling: Using RuntimeException class inheritance RDBMS connection -Use Java JDBC library

[System Interface List] No Interface name System (From) System (To) Contents One Password request DApp Main-Net One-time password 2 Signing a contract DApp Main-Net Contract signing/modification/cancellation/inquiry 3 SAL module connection SAL Smart Device Main-Net (un)Lock 4 User authentication SAL Smart Device, DApp Main-Net User check available 5 Resource information management DApp Main-Net Registration/modification/deletion/inquiry

[Detailed system interface definition]

(1) Password request

ㅇ Interface information

Functional requirements

-Ability to create a one-time password

-DApp requests a one-time password from the mainnet and responds to the result

-The server must respond within 30 seconds after receiving the request message. The client transmits the request message and waits to receive the response message for 30 seconds, and when the time expires, the session is terminated.

System From-To

-DApp -> Mainnet

Connection method

-HTTP RESTful API

Linkage cycle

- real time

Linked processor

-DApp -> WAS(Connection Plugin) -> Core Smart Contract -> BlockChain Data Storage -> WAS -> DApp

ㅇ Linked data item

request Field name Data type Length Remark Control Number String 8 Resource serial number
(2 digit core separator + 6 digit serial number) ID String 40 User information Request date and time String 14 Service request time Service name String 10 One-time password

answer Field name Data type Length Remark Control Number String 8 Resource serial number key String 64 One-time password Response code String 2 00: Information exchange at the transport protocol level
01: Client request was successfully executed
02: Mandatory parameter is missing
03: Bad request from client
04: Server side error Request date and time String 14 Service request time Response date and time String 14 Service response time

(2) Signing a contract

ㅇ Interface information

Functional requirements

-The DApp requests a service for signing a contract from the mainnet and responds to the processing result.

-The server must respond within 30 seconds after receiving the request message. The client transmits the request message and waits to receive the response message for 30 seconds, and when the time expires, the session is terminated.

System From-To

-DApp -> Mainnet

Connection method

-HTTP RESTful API

Linkage cycle

- real time

Linked processor

-DApp -> WAS(Connection Plugin) -> Core Smart Contract -> BlockChain Data Storage -> WAS -> DApp

ㅇ Linked data item

request Field name Data type Length Remark Control Number String 8 Resource serial number
(2 digit core separator + 6 digit serial number) ID String 40 User information Request date and time String 14 Service request time Service name String 10 Contract information execution/inquiry/deletion/modification Service contents String text Contents

answer Field name Data type Length Remark Control Number String 8 Resource serial number Service name String 10 Contract information execution/inquiry/deletion/modification Request result String text Processing result Response code String 2 00: Information exchange at the transport protocol level
01: Client request was successfully executed
02: Mandatory parameter is missing
03: Bad request from client
04: Server side error Request date and time String 14 Service request time Response date and time String 14 Service response time

(3) SAL module connection

ㅇ Interface information

Functional requirements

-Lock/unlock function through personal smart device tagging

-Final access by using the active/inactive setting and SAL module in the manager app

-Active/inactive setting in user app and final access using SAL module

-The DApp transmits smart data other than member authentication to the SAL module, requests the mainnet server to perform the service, and responds to the processing result.

-The server must respond within 30 seconds after receiving the request message. The client transmits the request message and waits to receive the response message for 30 seconds, and when the time expires, the session is terminated.

System From-To

-SAL Smart Device -> Mainnet

Connection method

-Bluetooth, NFC

Linkage cycle

- real time

Linked processor

-SAL Smart Device -> WAS(Connection Plugin) -> Core Smart Contract -> BlockChain Data Storage -> WAS -> SAL Smart Device

ㅇ Linked data item

request Field name Data type Length Remark key String 64 One-time password ID String 40 User information Request date and time String 14 Service request time Service name String 10 Door lock lock/unlock Control Number String 8 Resource serial number

answer Field name Data type Length Remark Control Number String 8 Resource serial number Service name String 10 Door lock lock/unlock Response code String 2 00: Information exchange at the transport protocol level
01: Client request was successfully executed
02: Mandatory parameter is missing
03: Bad request from client
04: Server side error Request date and time String 14 Service request time Response date and time String 14 Service response time

(4) User authentication

ㅇ Interface information

Functional requirements

-Check if the user through REST API is valid.

-The smart device or personal smart device with the SAL module is the client, and the mainnet that checks member information from the management server to the mainnet becomes the server.

-The server must respond within 30 seconds after receiving the request message. The client transmits the request message and waits to receive the response message for 30 seconds, and when the time expires, the session is terminated.

System From-To

-SAL Smart Device, DApp -> Mainnet

Connection method

-HTTP Restful API

Linkage cycle

- real time

Linked processor

-DApp, SAL Smart Device -> WAS (Identification Plugin) -> Core Smart Contract -> BlockChain Data Storage -> WAS -> DApp, SAL Smart Device

ㅇ Linked data item

request Field name Data type Length Remark ID String 40 User information Pause String 14 Service request time
(yyyymmddHHMMSS) Control Number String 8 Resource serial number
(2 digit core separator + 6 digit serial number)

answer Field name Data type Length Remark ID String 40 User information Authentication code String 2 00: service user
01: Invalid user
02: Server side error Response code String 2 00: Information exchange at the transport protocol level
01: Client request was successfully executed
02: Mandatory parameter is missing
03: Bad request from client
04: Server side error Request date and time String 14 Service request time Response date and time String 14 Service response time

(5) Resource information management

ㅇ Interface information

Functional requirements

-The DApp requests the resource information management service from the mainnet and then responds to the processing result.

-The server must respond within 30 seconds after receiving the request message. The client transmits the request message and waits to receive the response message for 30 seconds, and when the time expires, the session is terminated.

System From-To

-DApp -> Mainnet

Connection method

-HTTP RESTful API

Linkage cycle-real time

Linked processor

-DApp -> WAS(Connection Plugin) -> Core Smart Contract -> BlockChain Data Storage -> WAS -> DApp

ㅇ Linked data item

request Field name Data type Length Remark Control Number String 8 Resource serial number
(2 digit core separator + 6 digit serial number) ID String 40 User information Request date and time String 14 Service request time Service name String 10 Resource information registration/inquiry/deletion/modification Service contents String text Contents

answer Field name Data type Length Remark Control Number String 8 Resource serial number Service name String 10 Resource information registration/inquiry/deletion/modification Request result String text Processing result Response code String 2 00: Information exchange at the transport protocol level
01: Client request was successfully executed
02: Mandatory parameter is missing
03: Bad request from client
04: Server side error Request date and time String 14 Service request time Response date and time String 14 Service response time

[Sharing Economy Blockchain Platform Functional Design]

ㅇ Summary of detailed functions of the sharing economy blockchain platform

Decentralized infrastructure Function 01 Function 02 main function Decentralization
infra p2p network -A number of distributed computers form a blockchain network -Main node genesis block creation
-Participation in block generation from registered BP
-Performing the role of backup node in candidate BP -Generates a certain amount of time or number of blocks in the order of registered BP-Responds to updating the EOSIO platform version
-Smart contract modification and distribution Decentralized database -Stores necessary information in the blockchain, not in a centralized database
-Decentralization by storing data in a decentralized blockchain -Save smart contract data in the created block
-Performs the CRUD role in the same way as the centralized database Development platform -Provide API used for development -Sharing economy smart contract development and distribution -EOSIO version update real-time response monitoring -Visitor, transaction monitoring support -Number of visitors / authentication processing speed / transaction processing speed monitoring security -Data encryption
-Prevention of forgery and alteration
-User verification

Membership / Transaction Function 01 Function 02 main function Sign Up Sign Up -User membership registration
-Administrator membership registration
-Member identification Member management -Member information inquiry
-Member information modification
- Withdrawal deal Sharing economy transaction service provision - Sharing economy resource transaction Cryptocurrency - Cryptocurrency creation, issuance, and transaction

[Detailed Functional Specification of the Sharing Economy Blockchain Platform]

(1) Register as an administrator

ㅇ Description

Administer membership registration.

After entering the administrator member information, the data is stored in BlockChain Data Storage.

ㅇ Event

Administrator member information duplicate check

Save manager member information

Create manager smart contract when creating account

ㅇ Related table

Administrator member information table

(2) Modify administrator member information

ㅇ Description

Modify the saved administrator member information.

ㅇ Event

Administrator member ID validity check

Save after modifying administrator member information

ㅇ Related table

Administrator member information table

(3) Manager member information inquiry

ㅇ Description

Inquire the saved administrator member information.

ㅇ Event

Administrator member ID validity check

Administrator member information inquiry-The result is displayed on the screen.

ㅇ Related table

Administrator member information table

(4) Deletion of administrator member information

ㅇ Description

Delete the data of the saved administrator member information.

ㅇ Event

Administrator member ID validity check

Delete administrator member information

ㅇ Related table

Administrator member information table

(5) User registration

ㅇ Description

Process membership registration.

After entering member information, the data is stored in BlockChain Data Storage.

ㅇ Event

User member information duplicate check

User member information storage

User smart contract creation when creating an account

ㅇ Related table

User member information table

(6) User member information modification

ㅇ Description

Modify the data of saved user member information.

ㅇ Event

User member ID validity check

Save after modifying user member information

ㅇ Related table

User member information table

(7) User member information inquiry

ㅇ Description

Inquiry stored user member information.

ㅇ Event

User member ID validity check

User member information inquiry-The result is displayed on the screen.

ㅇ Related table

User member information table

(8) User member information deletion

ㅇ Description

Delete the saved user member information data.

ㅇ Event

User member ID validity check

Delete user member information

ㅇ Related table

User member information table

(9) Shared resource registration

ㅇ Description

The administrator registers the shared resource information.

Location (address, floor), area information, possible occupancy date, contract amount (deposit option), rental period, auxiliary facilities (parking, air conditioning/heating, elevator, office equipment, internet, etc.), landlord information (rental business number), etc. Register.

ㅇ Event

Check for duplicate shared resource information

Saving shared resource information

ㅇ Related table

Resource information table

(10) Modification of shared resources

ㅇ Description

The administrator modifies the registered shared resource information.

ㅇ Event

Shared resource information validation

Save after modifying shared resource information

ㅇ Related table

Resource information table

(11) Delete shared resources

ㅇ Description

The administrator deletes the registered shared resource information.

ㅇ Event

Shared resource information validation

Delete shared resource information

ㅇ Related table

Resource information table

(12) Shared resource inquiry

ㅇ Description

Inquiry registered shared resource information.

ㅇ Event

Shared resource information validation

Shared resource information inquiry-The result is displayed on the screen.

ㅇ Related table

Resource information table

(13) Device registration

ㅇ Description

The administrator registers the device information.

ㅇ Event

Device information duplicate check

Save device information

ㅇ Related table

Device information table

(14) Device information modification

ㅇ Description

The administrator modifies the registered device information.

ㅇ Event

Device information validation

Save after modifying device information

ㅇ Related table

Device information table

(15) Delete device

ㅇ Description

The administrator deletes the registered device information.

Device information in use cannot be deleted.

ㅇ Event

Device information validation

Device authorization check

Delete device information

ㅇ Related table

Device information table

(16) Device inquiry

ㅇ Description

Inquire registered device information.

ㅇ Event

Device information validation

Device information inquiry-display the result on the screen

ㅇ Related table

Device information table

(17) Device test

ㅇ Description

Test whether the registered device is working properly.

The device in use cannot be tested.

ㅇ Event

Device information validation

Device authorization check

Device operation test

ㅇ Related table

Device information table

(18) Signing a contract

ㅇ Description

Confirm and conclude the contract with the user.

ㅇ Event

Check for duplicate contract information

Saving contract information

ㅇ Related table

Contract information table

(19) Contract rejection

ㅇ Description

Confirm and reject the contract with the user.

ㅇ Event

Cancellation (deletion) after returning contract information

ㅇ Related table

Contract information table

(20) Contract modification

ㅇ Description

Modify the contents of the contract.

User's consent is required (refer to the contract modification agreement function).

ㅇ Event

Contract information validation

Check agreement to modify contract information

Save after modifying contract information

ㅇ Related table

Contract information table

(21) Agreement to amend the contract

ㅇ Description

I agree to amend the terms of the contract.

When the administrator revises the contract, the user's consent is required.

ㅇ Event

Contract information validation

Contract information inquiry

Check agreement to modify contract information

ㅇ Related table

Contract information table

(22) Contract extension

ㅇ Description

Apply for extension of the period of use of the shared resources currently being used.

If the administrator disables the extension function, it cannot be used.

ㅇ Event

Contract information validation

Check for inactive extension of contract period

Save contract information extension request

ㅇ Related table

Contract information table

(23) allow/disallow extension of contract

ㅇ Description

Processes permission to extend the use period of the shared resource requested by the user.

ㅇ Event

Contract information validation

Saving contract information after allowing extension of contract information

Saving the result of processing after disallowing extension of contract information

ㅇ Related table

Contract information table

(24) Delete contract

ㅇ Description

Delete the contents of the contract.

Contract information that has been concluded and is being executed cannot be deleted.

ㅇ Event

Contract information validation

Check the permission to delete contract information

Delete contract information

ㅇ Related table

Contract information table

(25) Contract inquiry

ㅇ Description

Inquiry about contract information.

ㅇ Event

Contract information validation

Contract information inquiry-results are displayed on the screen

ㅇ Related table

Contract information table

(26) Contract completion

ㅇ Description

Contract completion processing for contracts whose period has expired.

ㅇ Event

Contract information validation

Check the validity period of contract information

Contract information completion processing

ㅇ Related table

Contract information table

(27) Registration of affiliated facilities

ㅇ Description

The manager registers the information of the subsidiary facilities of the shared resource.

ㅇ Event

Check for duplicate information on affiliated facilities

Storage of affiliated facilities

ㅇ Related table

Auxiliary Facility Table

(28) Inquiry of affiliated facilities

ㅇ Description

Inquire information of registered affiliated facilities.

This is possible only for administrators or users using shared resources.

ㅇ Event

Validation of information on subsidiary facilities

Information inquiry authority check

Inquiry about the information of affiliated facilities-Display the results on the screen

ㅇ Related table

Auxiliary Facility Table

(29) Correction of information on affiliated facilities

ㅇ Description

Correct the information of registered subsidiary facilities.

ㅇ Event

Validation of information on subsidiary facilities

Save after modifying the information of subsidiary facilities

ㅇ Related table

Auxiliary Facility Table

(30) Application for use of subsidiary facilities

ㅇ Description

Apply for the use of registered subsidiary facilities.

ㅇ Event

Validation of information on subsidiary facilities

Checking the usage time of affiliated facilities

Reservation for use of subsidiary facilities

ㅇ Related table

Auxiliary Facility Table

(31) Cancellation of application for use of affiliated facilities

ㅇ Description

Cancel the use of reserved facilities.

ㅇ Event

Validation of information on subsidiary facilities

Cancellation of reservation for use of affiliated facilities

ㅇ Related table

Auxiliary Facility Table

(32) Extension of use of subsidiary facilities

ㅇ Description

Extend the use of subsidiary facilities in use.

This is only possible if there is no application for use during the extended time.

ㅇ Event

Validity check of attached facility information

Checking the reservation information of affiliated facilities

Correction of use time of subsidiary facilities

ㅇ Related table

Auxiliary Facility Table

(33) User registration for additional shared resources

ㅇ Description

Register additional users of shared resources in use.

It is possible only for users who have signed a contract.

ㅇ Event

Contract information validation

Member information validation

Register additional users

ㅇ Related table

Member information table

Contract information table

Shared resource table

(34) Add shared resource delete user

ㅇ Description

Delete additional users of registered shared resources.

It is possible only for users who have signed a contract.

ㅇ Event

Contract information validation

Delete user

ㅇ Related table

Contract information validation

Delete additional users

(35) Device control

ㅇ Description

Controls the open/lock of the device.

ㅇ Event

User authentication check

Device validation

Contract information validation

Device control transmission

ㅇ Related table

User table

Contract information table

Device table

(36) Issuing a one-time device password

ㅇ Description

Issue a one-time device password.

ㅇ Event

Send after generating password

ㅇ Related table

Device table

[DApp function definition-dApp requirement analysis for users]

(1) User role definition

ㅇ The role of the shared space tenant is defined as follows.

The tenant who wants to lease the shared space office is defined as a user.

Users use dApps of the sharing economy platform to lease a shared office.

Users search for shared offices that are suitable for their intended purpose and are currently available for rent.

The user requests a smart contract for the shared office that he wants to lease.

When the manager's smart contract is completed, he or she freely enters and exits the leased shared office during the period of use.

Using the user dApp, unlock the door lock of the rental office where you can access.

When the rental period expires, the smart contract contract is automatically completed and the door lock can no longer be opened.

(2) User requirements definition Requirement ID Requirements name Requirements details Constraint dApp-user-01 -Join the sharing economy platform -You must be able to create an account through the sharing economy platform homepage or user dApp. dApp-user-02 -Search for a shared office that fits the purpose you want to use -You must be able to search for rentable shared offices by entering search conditions. dApp-user-03 -Entering into a lease contract with the owner of the shared office you want to use -Signing a use contract through the user dApp
-When the landlord agrees to the contract, the rent and deposit must be transferred.
-The deposit must be staking and can be returned after the contract is completed. dApp-user-04 -Use of the shared office for which the contract has been concluded -In order to actually use the contracted shared office, the door lock to which SAL has been applied must be able to unlock through the user dApp.-The door lock receives a one-time password that has been authenticated through the sharing economy blockchain platform through short-range communication such as Bluetooth and the door lock. Should be able to unlock. dApp-user-05 -Register additional joint users other than the contracting party to use the office -You must be able to add members who can use the shared office you are currently using. dApp-user-06 -If there is a space such as a public conference room, reserve the use of the space in advance -You must be able to search for available time slots and register usage reservations through the user dApp.-When changing the schedule, use the reservation cancellation function to allow other tenants to use it. dApp-user-07 -Extend the period of use of the shared office currently being used -You must be able to register a postponement request through the dApp's smart contract extension option-If there are the following users or the administrator does not allow it, you must be able to reject the postponement request. dApp-user-08 -Terminating the office contract that has expired -When the user's period expires or when the conditions of the smart contract set in advance are fulfilled, the usage rights must be able to be released. dApp-user-09 -Write a review of the shared office you used -Must be able to input reviews through dApp-Must be able to help other users in their selection by writing reviews.

[Analysis of dApp requirements for administrators]

(1) Administrator role definition

ㅇ The role of the shared space lessor is defined as follows.

The lessor who wants to lease the shared space office is defined as the manager.

We are trying to reduce the fee burden through direct transactions that do not use a real estate broker, and we want to manage the shared office contract directly.

The concept of sharing a smart office applies only to short-term rentals of 1 to 2 months, and depending on the landlord, you may or may not receive a deposit.

Pursuing a model different from other shared space business models by minimizing the distance between the lessor and the lessee by using the token business.

The role of the blockchain platform is limited to linking contracts, and functions as a medium through which users directly transact.

After signing up for membership, the administrator individually registers the information of the shared office to be rented.

Office location (address, number of floors), area (rental area/exclusive area), available date, contract amount (depending on the number of contract days), rental period (1-30 days), additional facilities rental status (parking, cooling/heating, Elevator, office equipment, internet, etc.), landlord information (rental business number)

Information for each shared office is registered, and accordingly, the door lock to which SAL is applied is registered as a shared resource using dApp on the blockchain platform.

(2) Administrator requirements definition Requirement ID Requirements name Requirements details Constraint dApp-manager-01 -Join the sharing economy platform -The lessor (manager) account must be created through the sharing economy platform homepage or through the manager dApp. dApp-manager-02 -Registration and management of leasable shared space -The dApp must be able to register shared office information for each SAL door lock-Access permission information must be registered according to the shared resource information registration.
-Location (address, floor), area information, date of occupancy, contract amount (deposit option), rental period, auxiliary facilities (parking, cooling/heating, elevator, office equipment, internet, etc.), landlord information (rental business number), etc. Should be able to register. dApp-manager-03 -Registration and management of installed door locks -You must be able to register a new device installed using the administrator dApp-You must be able to test whether the registered device works normally through the administrator dApp. dApp-manager-04 -Signing a contract for the contract in which the rental request was received -According to the contract made through the dApp, even the manager cannot access the leased object during the contract period, and if the tenant permits it to open, the door lock must be able to open.-Review the rental request and then open the manager dApp. You must be able to conclude or reject a lease contract through. dApp-manager-05 -Contract completion processing for contracts that have expired -If the rental period has expired, it must be possible to confirm that there is no abnormality in the shared office and to process the lease contract-If there is a deposit, the staked deposit must be returned to the tenant. dApp-manager-06 -Termination of contract at the request of user or manager -If a certain reason arises and the contract needs to be terminated midway, the contract should be able to expire midway with the consent of the lessee and landlord. Rent is settled on a daily prorated basis. dApp-manager-07 -Current status information management on lease -It must be possible to inquire and manage current contract status and expiration status of the shared office operated by the lessor, and status information on shared resource information. dApp-manager-08 -Edit and manage shared space information -You must be able to manage access rights and information on shared offices.

[DApp architecture for users of space sharing service]

Account information management: User account ID/passwith creation and management module

Login/out control: dApp login and logout management module

Account additional attribute information management: Additional information management module such as contact information required for shared transactions

Public Key/Private Key: Public key/private key management module required for smart contract and token economy

Nodeos Controller: A controller that distributes smart contracts and loads information on the blockchain mainnet.

Setsmartcontract.cpp: Smart contract creation file and management module

Recardian contract: A digital document that defines the conditions and content for two or more parties to act with each other.

Shared space information inquiry/management: currently available shared space information inquiry module, search history management

Shared space member management: A module that manages additional users of the shared space currently in use

Door lock permission control: A module that checks whether the user has the permission to release the device to which the SAL module is applied, through the blockchain.

One-time password: Controls the function that the user receives and opens the door lock number through the one-time password.

SAL Communicatiom: Communication module with SAL device

Lock unlock management: Lock unlock history and lock management for the shared space

[DApp Architecture for Space Sharing Service Manager]

Account information management: User account ID/passwith creation and management module

Login/out control: dApp login and logout management module

Account additional attribute information management: Additional information management module such as contact information required for shared transactions

Public Key/Private Key: Public key/private key management module required for smart contract and token economy

Nodeos Controller: A controller that distributes smart contracts and loads information on the blockchain mainnet.

Setsmartcontract.cpp: Smart contract creation file and management module

Recardian contract: A digital document that defines the conditions and content for two or more parties to act with each other.

Door lock permission control: A module that checks whether the user has the permission to release the device to which the SAL module is applied, through the blockchain.

One-time password: Controls the function that the user receives and opens the door lock number through the one-time password.

SAL Communicatiom: Communication module with SAL device

Lock unlock management: Lock unlock history and lock management for the shared space

SAL device registration/management: a management module that registers a new SAL door lock device or deletes a previously registered device

Remote control/monitoring: SAL door lock current status monitoring and remote control module

Shared space information registration/management: A module that registers, modifies/deletes shared space information available for rent

Subsidiary facility registration/management: A module that registers or modifies/deletes facilities that can be used incidentally in the space to be rented

Shared resource access right management: A module in which the administrator for each space where the SAL device is installed sets the access right for each user (contracted user/all users/specific user-specific authority)

Usage history management: Shared space usage history management

Design of dApp operation scenarios for users

(1) User scenario design

ㅇ User refers to the person who rents the office space, and the operation scenario is shown in the following table.

Motivation for use Needs Service function scenario First use of shared office through the sharing economy platform Join the sharing economy platform User status information management function-Membership registration (account creation) Create a lessor (manager) account through the sharing economy platform homepage or through the manager dApp. Browse available shared offices Search for a shared office that fits the purpose you want to use Shared resource information management function-Search for rental space Enter search criteria to search for rentable shared offices. Shared Office Use Agreement Entering into a lease agreement with the owner of the shared office you want to use User dApp-lease management A contract for use is concluded through the user dApp, and the rent and deposit are transferred at the same time as the tenant agrees to the contract. Use of a shared office Actual use of the shared office for which the contract has been concluded User dApp-SAL Door Lock Open In order to actually use the contracted shared office, the door lock to which SAL is applied is unlocked through the user dApp.
The door lock is unlocked by receiving a one-time password authenticated through the sharing economy blockchain platform through short-range communication such as NFC. Add members for shared office use Register additional joint users other than the contracting party to use the office User dApp-Add User Add members who can jointly use the shared office you are currently using. Use of subsidiary spaces such as conference rooms If there is a space such as a public conference room, reserve the use of the space in advance. User dApp-Application for use of subsidiary space Search the available time slot through the user dApp and register a reservation for use.
When changing the schedule, use the reservation cancellation function to make it available to other tenants. Extended period of use of shared office Extend the period of use of the currently used shared office. User dApp-lease management Register a postponement request through the dApp's smart contract extension option.
If the next user exists or the administrator does not allow it, the request for postponement will be rejected. Office use termination (contract expiration) Terminate the office contract for which the period of use has expired. User dApp
-Lease contract management When the user's period expires or when the conditions of the smart contract set in advance are fulfilled, the usage rights are released. Write a review Write a review of the shared office you used. User dApp-Write a review Enter the review through dApp.
It helps other users to make their choices by writing a review.

[Design of dApp operation scenarios for administrators]

(One) Manager scenario design

ㅇ The manager means the person who rents the office space, and the operating scenario is shown in the following table.

Motivation for use Needs Service function scenario Started rental business using the sharing economy platform Join the sharing economy platform User status information management function-Membership registration (account creation) Create a lessor (manager) account through the sharing economy platform homepage or through the manager dApp. Register the shared space you want to lease Registration and management of leasable shared space Shared resource information management function-Registration/modification/deletion/inquiry of rental space In dApp, the shared office information is registered for each SAL door lock, and the access right information is registered according to the shared resource information registration.
-Location (address, floor), area information, date of occupancy, contract amount (deposit option), rental period, auxiliary facilities (parking, cooling/heating, elevator, office equipment, internet, etc.), landlord information (rental business number), etc. Register. Door lock installation with SAL applied to the leased shared space Registration and management of installed door locks Shared resource information management function-New registration of SAL device
-Registered SAL device management (modify/delete/view) Purchase and install door locks with SAL applied to each office space to be rented.
Register a new device installed using the manager dApp.
Test whether the registered device works normally through the manager dApp. Shared office lease contract signed Signing a contract for the contract in which the rental request was received Manager dApp-lease management According to the contract made through the dApp, even A cannot access the leased property during the contract period, and if the tenant permits it to open, the door lock can be opened. Signed or rejected. Shared office rental expiration Contract expiration processing for contracts that have expired Manager dApp-lease management If the rental period has expired, it is confirmed that there is no problem with the shared office and the rental contract is expired.
If there is a deposit, the staked deposit will be returned to the tenant. Termination of shared office contract Termination of contract at the request of user or manager Manager dApp-lease management If a certain reason arises and it is necessary to terminate the contract midway, the contract is terminated midway with the consent of the tenant and the landlord. Rent is settled on a daily prorated basis. Shared office contract status management Management of current status information on lease Shared resource information management function*Lease contract management-Shared resource information management View and manage current contract status and expiration status of the shared office operated by the lessor, and status information on shared resource information. Shared office shared space management Shared space information modification and management Shared resource access right management function Shared resource information management function
View Reviews
-Shared resource information management Manage access rights and information on shared offices.

[Analysis of requirements for matching heterogeneous services]

(1) Defining the function of matching heterogeneous services

ㅇ Refers to a function that can interchange/share various heterogeneous services provided by the shared transaction service

When using the space sharing service, it is recommended to rent the subsidiary space and related services that users frequently use in the service.

(2) Definition of requirements for heterogeneous service matching function

Requirement ID Requirements name Requirements details Constraint matching-01 Registration of heterogeneous services It should be possible to register various shared transaction services. In this project, space and object transaction services are developed, so the test is limited to using two services. matching-02 Heterogeneous service inquiry Must be able to search registered heterogeneous services matching-03 Heterogeneous service recommendation It should be possible to recommend related heterogeneous services based on the shared transaction service and location used by the user. matching-04 Heterogeneous service management It should be possible to modify or delete registered heterogeneous services.

[Design of heterogeneous service automatic matching platform architecture]

(1) Heterogeneous service matching platform architecture definition

ㅇ Create Recommendation: A module that recommends heterogeneous services based on the service information currently used by the user

ㅇ Service Docker: A module that registers and manages heterogeneous services

ㅇ Service Classification: A module that classifies and manages registered heterogeneous services by category

ㅇ Knowledge Management: A module that stores preferences and usage status of heterogeneous services selected by the user and uses it when recommending the next model

Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.

1 is a diagram showing a sharing economy platform in which an SAL module and a block chain are combined according to an embodiment of the present invention. In addition, FIG. 2 is a block diagram showing the configuration of a sharing economy platform in which the SAL module of FIG. 1 and a block chain are combined.

Referring to FIG. 1, the sharing economy platform 10 in which the SAL module and the block chain are combined is a user terminal 100, and the sharing economy platform 200 in which the SAL module and the block chain are combined (hereinafter referred to as a sharing economy platform). And a manager terminal 300.

The sharing economy platform 10 in which the SAL module and the blockchain are combined according to an embodiment of the present invention may be connected to the user terminal 100, the sharing economy platform 200, and the manager terminal 300 through a wired or wireless network.

The user terminal 100 may correspond to an individual, that is, one of the mobile communication terminals owned by the tenant of the shared space. Specifically, the user terminal 100 is a general mobile communication terminal such as a cellular phone, PCS phone (Personal Communications Services phone), synchronous/asynchronous International Mobile Telecommunication-2000 (IMT-2000), 2G /3G/4G, WiBro wireless network service terminal, Palm Personal Computer, Personal Digital Assistant (PDA), Smart phone, WAP phone: Wireless application protocol phone, etc. It may mean all wired/wireless home appliances/communication devices having a user interface for accessing a network, and may be a device equipped with an interface for wireless LAN access, such as an IEEE 802.11 wireless LAN network card. In addition, the user terminal 100 may be an information communication device such as a computer or a laptop computer, or a device including the same, in addition to a mobile communication terminal.

Referring to FIG. 2, the sharing economy platform 200 in which the SAL module and the blockchain are combined includes a communication unit 210, a shared space registration unit 220, a shared space recommendation unit 230, and a shared space permission control unit 240. can do.

The communication unit 210 may communicate with the user terminal 100. In addition, the communication unit 210 may perform communication with the manager terminal 300.

The shared space registration unit 220 may register shared space information for a plurality of shared spaces. The user may search for a shared space registered in the sharing economy platform 200 in which the SAL module and the blockchain are combined in order to lease the shared space using the user terminal 100. In addition, the user may input information on a desired shared space through the user terminal 100, and based on this, a shared space may be recommended from the sharing economy platform 200 in which the SAL module and the blockchain are combined.

The shared space recommendation unit 230 may recommend a shared space suitable for a user from among the shared spaces of the double-stay registered in the shared space registration unit 220. In detail, the shared space recommendation unit 230 may recommend a shared space among a plurality of shared spaces when a rental request for a shared space is transmitted from the user terminal 100.

The shared space permission control unit 240 may control the user terminal 100 to provide whether or not the shared space permission is granted. In detail, when a specific shared space is selected from among the recommended shared spaces, the shared space permission control unit 240 may provide whether or not the user terminal has the shared space permission for the selected specific shared space.

The shared space permission control unit 240 may include a shared space password providing unit 242. In addition, when the shared space authority of the user terminal 100 is granted, the shared space password providing unit 242 may generate a one-time password for the user terminal 100 and provide it to the user terminal 100. The user is provided with a one-time password generated by the sharing economy platform 200, and can freely access the shared space by using the one-time password.

The manager terminal 300 may correspond to an individual, that is, one of the mobile communication terminals owned by the renter of the shared space. In addition, since the manager terminal 300 is the same as the user terminal 100 described above, a detailed description thereof will be omitted.

Here, the shared space permission control unit 240 according to the present embodiment may check whether the user has the unlock permission for the lock device to which the Secure Access Lock (SAL) module is applied, through the block chain.

Therefore, the sharing economy platform 200 in which the SAL module and the blockchain are combined according to the present embodiment uses the SAL (Secure Access Lock) module and the blockchain together to determine whether the user has normal or abnormal access to the shared space. In normal access, the user can allow access to the shared space.

Consequently, according to the present embodiment, it is possible to provide a sharing economy service with improved security.

Although the embodiments of the present invention have been described with reference to the accompanying drawings, those of ordinary skill in the art to which the present invention pertains can be implemented in other specific forms without changing the technical spirit or essential features. You will be able to understand. Therefore, it should be understood that the embodiments described above are illustrative and non-limiting in all respects.

100: user terminal
200: Sharing economy platform combined with SAL module and blockchain
210: communication unit 220: shared space registration unit
230: Shared space recommendation unit
240: shared space authority control unit 242: shared space password providing unit
300: manager terminal

Claims (2)

A communication unit for performing communication with a user terminal;
A shared space registration unit for registering shared space information for a plurality of shared spaces;
A shared space recommendation unit for recommending a shared space among the plurality of shared spaces when a rental request for the shared space is transmitted from the user terminal; And
When a specific shared space among the recommended shared spaces is selected, a shared space authority control unit that provides whether or not the user terminal has a shared space authority for the selected specific shared space; a SAL module and a blockchain-based sharing economy platform including . The method of claim 1,
The shared space permission control unit,
When the user terminal's shared space permission is granted,
A sharing economy platform in which a SAL module and a block chain including; a shared space password providing unit that generates a one-time password for the user terminal and provides it to the user terminal.

Images