KR20220097223A - Electronic apparatus for community based mobility service, system including the same, and vehicle sharing method therefor - Google Patents

Abstract

In accordance with one aspect of the present disclosure, an electronic device comprises: at least one memory storing at least one instruction; and at least one processor connected with the memory. The at least one processor is configured to execute the at least one instruction to: create a sharing group for vehicle sharing, set a group rule for the sharing group, wherein the group rule is associated with at least one of a vehicle use time per preset time unit and a vehicle use cost for each of a plurality of owners included in the sharing group, permit a vehicle use right to at least one sub owner, excluding a main owner who is already permitted for the vehicle use right, of the plurality of owners, and manage the vehicle use of the plurality of owners. The total vehicle use time allocated to the plurality of owners based on the group rule can be within a vehicle use time which is already allocated to the main owner. Therefore, the present invention is capable of enabling the main owner to flexibly use the time allocated to the main owner, and minimizing a waste of time.

Description

ELECTRONIC APPARATUS FOR COMMUNITY BASED MOBILITY SERVICE, SYSTEM INCLUDING THE SAME, AND VEHICLE SHARING METHOD THEREFOR

The present disclosure relates to an electronic device for a community-based mobility service, a system including the same, and a vehicle sharing method.

Currently, the culture of using vehicles from 'own' to 'consumption' is spreading as the weight of the economy and convenience of maintaining a vehicle is increasing. The main reason for changing people's concept of 'ownership' to 'consumption' is that it reduces the high economic cost that people have to pay for owning a vehicle, and at the same time provides high service availability, the inconvenience of not owning a vehicle. Because it removes the elements quite a bit. In addition, the recent market trend in which the types of vehicles used are diversifying from passenger cars to electric kickboards and bicycles are accelerating this change.

Existing long-term car rental provides periodic maintenance of the vehicle according to the mileage and reduction of expenses incurred to maintain the vehicle, such as registration tax and insurance cost. However, in long-term rental, you can rent a vehicle on condition of an initial charge (advance payment, deposit) and a long-term contract period, but the number of users who can use the vehicle is limited. In addition, although it is economical in terms of cost compared to directly purchasing and owning a vehicle, there is a problem in that idle time that is not used still occupies a greater proportion than time in which the vehicle is used.

In order to solve such a problem, subscription-type vehicle provision service products are being diversified recently, and a shared-type service in which several people use a privately owned vehicle is also being implemented. In addition, the usage patterns of users are changing to use and return various types of vehicles for the required time, and the demand to allow only members of the community to use the vehicle, not just people who do not know each other, is increasing.

Japanese Patent No. 3610025 Republic of Korea Patent No. 1543773

Various embodiments of the present disclosure provide an electronic device for a community-based mobility service in which the main owner can flexibly use the time allotted to him and minimize wasted time in a car sharing service that rents for a specific time in advance, This is to provide a system and a vehicle sharing method including the same. In the community-based mobility service, messages will be transmitted in various forms between members of the community or between the user and the mobility service system. Service users will be confused, and problems will occur even in service activation, and the present invention intends to solve these problems.

Technical problems to be achieved in various embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned are common knowledge in the art from various embodiments of the present disclosure to be described below. can be considered by those with

In one aspect of the present disclosure, at least one memory (memory) for storing at least one instruction (instruction); and at least one processor coupled to the memory, wherein the at least one processor executes the at least one instruction to: create a sharing group for vehicle sharing; a group rule for the sharing group, wherein the group rule is associated with at least one of vehicle usage time and vehicle usage amount per preset time unit of each of a plurality of owners included in the sharing group; to set; allowing the vehicle use right to at least one sub-owner other than the main owner to which the vehicle use right is previously permitted among the plurality of owners; and the electronic device configured to manage vehicle use of the plurality of owners, wherein a total sum of vehicle use time allocated to the plurality of owners based on the group rule is within a range of vehicle use time pre-allocated to the main owner. to be.

For example, the at least one processor may: receive a group rule setting message from the main owner; and to set the group rule based on the group rule setting message, wherein the group rule setting message may include at least one of the vehicle usage time and the vehicle usage amount.

For example, the at least one processor is: When the remaining vehicle use time occurs when the preset time unit elapses, transmits a notification message including the remaining vehicle use time to at least one owner among the plurality of owners do; receiving a processing message for the remaining vehicle use time from the at least one owner; when a settlement request is included in the processing message, transmitting a settlement message corresponding to the remaining vehicle use time to the settlement server; and when the transfer request is included in the processing message, the remaining vehicle use time may be carried forward after the preset time unit.

For example, the at least one processor may: receive an additional use request message including an additional use time from the at least one owner; sending a settlement request message corresponding to the additional use time to the settlement server; and when receiving a settlement completion message corresponding to the settlement request message from the settlement server, the at least one owner may be further configured to allow an additional vehicle use right corresponding to the additional use time.

For example, the at least one processor may be configured to: receive, from the main owner, an additional usage allocation message including additional usage time for the at least one sub-owner; and allowing an additional vehicle use right corresponding to the additional use time to the at least one sub-owner, wherein the additional use time is within a range excluding the total sum of the vehicle use time from the pre-allocated vehicle use time and may have priority over the group rule.

In another aspect of the present disclosure, there is provided a vehicle sharing method performed by an electronic device, the method comprising: creating a sharing group for vehicle sharing; a group rule for the sharing group, wherein the group rule is associated with at least one of vehicle usage time and vehicle usage amount per preset time unit of each of a plurality of owners included in the sharing group; to set; allowing the vehicle use right to at least one sub-owner other than the main owner to which the vehicle use right is previously permitted among the plurality of owners; and managing the vehicle use of the plurality of owners, wherein the total sum of vehicle use time allocated to the plurality of owners based on the group rule is within the range of vehicle use time pre-allocated to the main owner. How to share a car.

For example, when the remaining vehicle usage time occurs when the preset time unit has elapsed, transmitting a notification message including the remaining vehicle usage time to at least one owner among the plurality of owners; receiving a processing message for the remaining vehicle use time from the at least one owner; transmitting a settlement message corresponding to the remaining vehicle use time to a settlement server when the settlement request is included in the processing message; and when the transfer request is included in the processing message, carrying forward the remaining vehicle use time after the preset time unit.

For example, receiving an additional use request message including an additional use time from the at least one owner; transmitting a settlement request message corresponding to the additional use time to the settlement server; and allowing an additional vehicle use right corresponding to the additional use time to the at least one owner when a settlement completion message corresponding to the settlement request message is received from the settlement server.

For example, receiving an additional use allocation message including an additional use time for the at least one sub-owner from the main owner; and allowing an additional vehicle use right corresponding to the additional use time to the at least one sub-owner, wherein the additional use time is determined by subtracting the total sum of the vehicle use time from the pre-allocated vehicle use time within the range, and may have priority over the group rule.

The various embodiments of the present disclosure described above are only some of the preferred examples of the present disclosure, and various examples reflecting the technical characteristics of various embodiments of the present disclosure will be described below by those of ordinary skill in the art. It can be derived and understood based on the detailed description.

According to various embodiments of the present disclosure, the following effects are obtained.

According to various embodiments of the present disclosure, for a community-based mobility service in which the main owner can flexibly use the time allotted to him and minimize wasted time in a car-sharing service that rents for a specific time in advance. An electronic device, a system including the same, and a vehicle sharing method may be provided.

In addition, in the community-based mobility service, messages will be transmitted in various forms between members of the community or between the user and the mobility service system, and between these messages, a third party sends spam or phishing messages with impure intentions If this is done, service users will be confused, and there may be problems in activating the service, and these problems can be solved.

Effects obtainable from various embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned are clear to those of ordinary skill in the art based on the following detailed description can be derived and understood.

The accompanying drawings are provided to help understanding of various embodiments of the present disclosure, and provide various embodiments of the present disclosure together with a detailed description. However, technical features of various embodiments of the present disclosure are not limited to specific drawings, and features disclosed in each drawing may be combined with each other to constitute a new embodiment. Reference numerals in each drawing refer to structural elements.
1 illustrates a vehicle sharing system according to an example of the present disclosure.
2 is a block diagram of an electronic device according to an example of the present disclosure.
3 is for explaining an example of group rule setting.
4 to 8 illustrate a vehicle sharing system according to various examples of the present disclosure.
9 is a flowchart of a vehicle sharing method according to an example of the present disclosure.
10 is a flowchart of a group rule setting method according to an example of the present disclosure;
11 is a flowchart of a method for processing remaining vehicle usage time according to an example of the present disclosure.
12 is a flowchart of a method for allocating additional usage time according to an example of the present disclosure.
13 is a flowchart of a method for allocating additional usage time according to another example of the present disclosure.
14 is a flowchart of a method of providing a security service according to an example of the present disclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, implementations according to the present invention will be described in detail with reference to the accompanying drawings. DETAILED DESCRIPTION The detailed description set forth below in conjunction with the appended drawings is intended to describe exemplary implementations of the present invention, and is not intended to represent the only implementation forms in which the present invention may be practiced. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details.

In some cases, well-known structures and devices may be omitted or shown in block diagram form focusing on core functions of each structure and device in order to avoid obscuring the concepts of the present disclosure. In addition, the same reference numerals are used to describe the same components throughout the present disclosure.

Since various embodiments according to the concept of the present invention can have various changes and have various forms, various embodiments are illustrated in the drawings and described in detail in the present disclosure. However, this is not intended to limit the various embodiments according to the concept of the present invention to specific disclosed forms, and includes changes, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from other components, for example, without departing from the scope of rights according to the concept of the present invention, a first component may be named a second component, Similarly, the second component may also be referred to as the first component.

When an element is referred to as being “connected” or “connected” to another element, it is understood that it may be directly connected or connected to the other element, but other elements may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle. Expressions describing the relationship between elements, for example, “between” and “between” or “directly adjacent to”, etc. should be interpreted similarly.

In various embodiments of the present disclosure, “/” and “,” should be interpreted as indicating “and/or”. For example, “A/B” may mean “A and/or B”. Furthermore, “A, B” may mean “A and/or B”. Furthermore, “A/B/C” may mean “at least one of A, B, and/or C”. Furthermore, “A, B, and C” may mean “at least one of A, B and/or C”.

In various embodiments of the present disclosure, “or” should be construed as indicating “and/or”. For example, “A or B” may include “only A”, “only B”, and/or “both A and B”. In other words, “or” should be construed as indicating “additionally or alternatively”.

The terminology used in the present disclosure is used only to describe various specific embodiments, and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present disclosure, terms such as "comprise" or "have" are intended to designate that the described feature, number, step, operation, component, part, or combination thereof exists, and includes one or more other features or numbers, It should be understood that the possibility of the presence or addition of steps, operations, components, parts or combinations thereof is not precluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present disclosure. does not Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

A system for providing ride-sharing services

Hereinafter, various embodiments for providing a community-based vehicle sharing service will be described.

In a community-based vehicle sharing service provided according to various embodiments of the present disclosure, within a sharing group including a main owner and sub-owner, each owner can share and use the same vehicle in various ways. let it be

Here, the main owner is a user who has already rented the shared vehicle, and the sub-owner is an owner who shares the shared vehicle already rented by the main owner with the main owner. The main owner and the sub-owner may be referred to as a plurality of owners.

1 illustrates a vehicle sharing system according to an example of the present disclosure.

Referring to FIG. 1 , the vehicle sharing system 10 according to an example of the present disclosure includes a plurality of user terminals 111 and 112 , a sharing server 120 , and a settlement server 130 .

Each of the plurality of user terminals 111 and 112, the sharing server 120 and the settlement server 130 may include a transceiver, a memory and a processor.

Each of the plurality of user terminals 111 and 112, the sharing server 120 and the settlement server 130 may be connected through a wired/wireless communication network to communicate with each other. The wireless communication network may include a mobile communication network, a wireless LAN, a local area wireless communication network, and the like. For example, a wireless communication network includes LTE, LTE Advance (LTE-A), code division multiple access (CDMA), wideband CDMA (WCDMA), universal mobile telecommunications system (UMTS), Wireless Broadband (WiBro), and Global System (GSM). for Mobile Communications) may include cellular communication using at least one of. For example, the wireless communication network may include at least one of wireless fidelity (WiFi), Bluetooth, Bluetooth low energy (BLE), Zigbee, near field communication (NFC), and radio frequency (RF).

Here, the wired communication network may include at least one of a Universal Serial Bus (USB), a Universal Synchronous/Asynchronous Receiver Transmitter (USART), and an Ethernet.

The plurality of user terminals 111 and 112 may correspond to the user terminals possessed by the above-described main owner and sub-owner. For convenience, a user terminal owned by the main owner may be referred to as a main owner terminal, and a user terminal owned by the sub-owner may be referred to as a sub-owner terminal. Also, in the present disclosure, the main owner may be used as a term meaning not only a user but also a main owner terminal, and the sub-owner may be used as a term meaning not only a user but also a sub-owner terminal.

The sharing server 120 is a server for providing a vehicle sharing service according to the present disclosure. The sharing server 120 may include an electronic device 121 . The sharing server 120 is configured to exchange various data or signals with a plurality of user terminals 111 and 112 and the settlement server 130 through a communication network, and to provide a vehicle sharing service to a plurality of user terminals 111 and 112 through a communication network. do.

The settlement server 130 is a server for calculating a usage amount generated when a plurality of owners use the vehicle sharing service provided according to the present disclosure.

Hereinafter, the electronic device 121 included in the above-described sharing server 120 will be described.

2 is a block diagram of an electronic device according to an example of the present disclosure.

Referring to FIG. 2 , the electronic device 121 according to an example of the present disclosure includes at least one transceiver 122 , at least one memory 123 , and at least one processor 124 .

The transceiver 122 may be connected to the processor 124 and may transmit and/or receive wired/wireless signals. For example, the transceiver 122 may be connected to the above-described vehicle sharing system 10 through a wired/wireless communication network.

Each of the at least one transceiver 122 may correspond to the above-described wired/wireless communication network.

The transceiver 122 may include a transmitter and a receiver. The transceiver 122 may be used interchangeably with a radio frequency (RF) unit. The transceiver 122 may be connected to the vehicle sharing system 10 through the control of the processor 124 to transmit and receive various data or signals.

The memory 123 may be connected to the processor 124 and may store various information related to the operation of the processor 124 . For example, the memory 123 may include instructions for performing some or all of the processes controlled by the processor 124 , or for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts of the present disclosure. It may store software code including (instructions).

The processor 124 controls the transceiver 122 and/or the memory 123, and executes instructions stored in the memory 123 to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts of the present disclosure. can be configured. For example, the processor 124 may receive a signal through the transceiver 122 and store information included in the signal in the memory 123 . In addition, the processor 124 may provide a vehicle sharing service based on a command stored in the memory 123 . In addition, the processor 124 may generate a signal by processing information stored in the memory 123 , and then transmit the generated wireless signal through the transceiver 122 .

Hereinafter, various embodiments of the electronic device 121, the sharing server 120 including the same, and the vehicle sharing system 10 including the same will be described.

According to an embodiment, the electronic device 121 creates a sharing group for vehicle sharing. As described above, the sharing group includes a plurality of owners including a main owner and a sub-owner.

The electronic device 121 may receive a sharing group creation message from the main owner and create a sharing group based on a sub-owner list included in the sharing group creation message. For example, the sub-owner list may refer to a list including sub-owners permitted by the main owner among sub-owners who have sent a sharing group participation message to the main owner.

A plurality of sharing groups may be created for the same main owner. In this case, the plurality of sharing groups may correspond to each of the plurality of vehicles rented by the same main owner.

According to an embodiment, the electronic device 121 sets a group rule for the created sharing group. The group rule is a rule set so that a plurality of owners included in the sharing group share the same vehicle. For example, the group rule may be associated with at least one of a vehicle usage time and a vehicle usage amount per preset time unit of each of a plurality of owners included in the sharing group.

3 is for explaining an example of group rule setting.

Referring to FIG. 3 , the group rule may allocate a share of use with respect to the total vehicle use time for each owner. In this case, each owner is allocated as much as the usage time corresponding to the usage share assigned to him in the total vehicle usage time, and the vehicle usage amount is also allocated as much as the usage amount corresponding to the usage share assigned to him in the total vehicle usage amount. have.

Group rules can be set only by the main owner. For example, the electronic device 121 may receive a group rule setting message from the main owner through a communication network, and may set a group rule based on the received group rule setting message. The group rule setting message may include at least one of a vehicle usage time and a vehicle usage amount set for each of the plurality of owners.

The total sum of vehicle use time allocated to the plurality of owners based on the group rule may be within the range of vehicle use time pre-allocated to the main owner. That is, the electronic device 121 may set the group rule so that the total of the vehicle use time allocated to the plurality of owners is within the range of the vehicle use time previously allocated to the main owner.

According to the group rule, the total sum of vehicle use time allocated to a plurality of owners may or may not be the same as the previously allocated vehicle use time. The remaining group time, which is the usage time excluding the sum, may occur. The remaining group usage time may be additionally used when the vehicle usage time allocated to each owner is exhausted.

According to an embodiment, the electronic device 121 permits vehicle use rights to at least one sub-owner other than a main owner to which vehicle use rights are previously permitted among a plurality of owners. The sub-owner may control the shared vehicle when the vehicle use right is permitted. For example, the sub-owner may control the shared vehicle in various ways based on an application installed in the sub-owner terminal.

According to an embodiment, the electronic device 121 manages vehicle use by a plurality of owners.

For example, the electronic device 121 performs settlement based on the allocated vehicle use time when a preset payment date arrives, manages the allocated vehicle use time when an owner uses a shared vehicle, or sets a preset time unit When the remaining vehicle usage time has elapsed, the remaining vehicle usage time may be processed, or additional usage time may be allocated when the allotted vehicle usage time is exhausted.

According to an embodiment, when a preset payment date arrives, the electronic device 121 settles the usage amount corresponding to the vehicle usage time allocated to each owner through the settlement server 130 . In this case, the vehicle usage amount for each owner may be proportional to the proportion of the vehicle usage time allocated to each of the total vehicle usage time as described above.

According to an embodiment, when each owner uses the shared vehicle, the electronic device 121 may deduct the allocated vehicle usage time by the actual usage time in real time. Also, when all the allocated vehicle use time is exhausted, the electronic device 121 may transmit an exhaustion message to the owner.

According to an embodiment, when the remaining vehicle usage time occurs when a preset time unit has elapsed, the electronic device 121 may process the remaining vehicle usage time.

For example, when the remaining vehicle usage time occurs when a preset time unit has elapsed, the electronic device 121 transmits a notification message including the remaining vehicle usage time to the owner.

The owner may receive the notification message to recognize that there is a remaining vehicle usage time, determine a processing of the remaining vehicle usage time, and transmit a processing message including the determined processing method to the electronic device 121 . The processing method may include settlement processing and carryover processing.

For example, when a settlement request is included in the processing message received from the owner, the electronic device 121 transmits a settlement message corresponding to the remaining vehicle use time to the settlement server 130 . When the settlement message is received, the settlement server 130 may refund an amount corresponding to the remaining vehicle use time to the owner.

Alternatively, when a transfer request is included in the processing message received from the owner, the electronic device 121 may carry forward the remaining vehicle use time to a preset time unit. The carried over remaining vehicle usage time may be added to the vehicle usage time allocated based on a group rule newly set after a preset time unit.

According to an embodiment, the electronic device 121 may allocate additional usage time when all the allocated vehicle usage time is exhausted.

For example, when all the allocated vehicle use time is exhausted, the owner transmits an additional use request message including the additional use time (or may be referred to as a first additional use request message) to the electronic device 121 . can

When receiving the first additional use request message from the owner, the electronic device 121 transmits a settlement request message corresponding to the additional use time to the settlement server 130 . Thereafter, when receiving the settlement completion message corresponding to the settlement request message from the settlement server 130 , the electronic device 121 may allow the owner to use the additional vehicle permission corresponding to the additional use time.

The allocation of the additional usage time based on the settlement server 130 described above may be applied separately from the vehicle usage time previously allocated to the main owner. That is, each owner belonging to the sharing group can use the shared vehicle by separately calculating the additional usage amount, even if all of the vehicle usage time allocated to each owner is exhausted.

Alternatively, for example, the owner (or sub-owner) may transmit an additional use request message (or may be referred to as a second additional use request message) to the main owner when all the allocated vehicle use time is exhausted.

When the main owner receives the second additional use request message and intends to allocate additional use time to the owner who has transmitted the second additional use request message, it sends an additional use allocation message including the additional use time to the owner. may be transmitted to the device 121 .

When the electronic device 121 receives the additional use assignment message, the electronic device 121 may allow the owner to use an additional vehicle use right corresponding to the additional use time. In this case, the additional usage time is within the range of the remaining group usage time, and may be given priority over the group rule. That is, when additional usage time is allocated to the owner based on the additional usage allocation message, the allocated additional usage time can be applied regardless of the vehicle usage time allocated to each owner by the group rule as long as the allocated additional usage time is within the group remaining usage time range. .

A system for providing security services for ride-sharing services

Hereinafter, various embodiments of a security service that can be applied together to provide the above-described vehicle sharing service will be described. Various embodiments related to the security service described below may be applied separately or together with the embodiments related to the vehicle sharing service described above. Hereinafter, detailed descriptions of parts overlapping with the previously described parts will be omitted.

4 to 8 illustrate a vehicle sharing system according to various examples of the present disclosure.

Referring to FIG. 4 , the vehicle sharing system 20 according to another example of the present disclosure includes an authentication server 210 , a data transmission device 220 , and a data reception device 230 .

Each of the data transmission device 220 and the data reception device 230 may correspond to any one of the plurality of user terminals 111 and 112 , the sharing server 120 , and the settlement server 130 described above.

The authentication server 210 may include a transceiver, a memory, and a processor, and the data transmission device 220 and the data reception device 230 each have a plurality of user terminals 111 and 112, a sharing server 120 and a settlement server. Since it corresponds to any one of 130, each may include a transceiver, a memory, and a processor as described above. Hereinafter, various operational examples of the vehicle sharing system 20 are the authentication server 210, the data transmission device 220 and the transceiver included in each of the data receiving device 230, commands stored in the memory, and executing the commands It may be performed by a processor.

The authentication server 210 , the data transmission device 220 , and the data reception device 230 are connected through a communication network.

The authentication server 210 receives the credential transmitted by the data transmission device 220 and performs authentication, and generates a one-time authentication code (A_device) according to the result. In addition, the authentication server 210 stores the sender code (code_sender) transmitted from the data transmitting device 220, and when the data receiving device 230 transmits the receiver code (code_receiver), the received receiver code (code_receiver) and It verifies whether the data is valid by comparing the stored sender code (code_sender).

The data transmission device 220 generates a sender code (code_sender) for the data to be transmitted using the one-time authentication code and verification value generation algorithm received from the authentication server 210 .

The data transmission device 220 transmits the generated sender code (code_sender) to the authentication server 210 , while transmitting data and a one-time authentication code to the data receiving device 230 . The data may be an SMS message, mail, or the like.

The data receiving device 230 and the data transmitting device 220 have a verification value generating algorithm.

The data receiving device 230 generates a receiver code (code_receiver) for the received data by using the received one-time authentication code and a verification value generation algorithm.

The data receiving device 230 transmits the generated receiver code (code_receiver) to the authentication server 210 to request verification.

The authentication server 210 compares the sender code (code_sender) transmitted from the data transmission device 220 and the receiver code (code_receiver) transmitted from the data reception device 230 to verify whether the data is valid, and receives the result of the data to device 230 .

The authentication server 210 performs credentials in response to the credential request of the data transmission device 220 is performed as follows.

The authentication server 210 has a physical storage device (not shown) for storing the unique ID of the data transmission device 220, and the unique ID transmitted from the data transmission device 220 for credentials is stored in the physical storage device. Credentials are performed by checking for equality with the recorded unique ID. A hard disk, an optical disk, a magneto-optical disk, etc. are mentioned as an example of a physical storage device.

Here, the unique ID of the data transmission device 220 is systematically managed not to be duplicated.

The unique ID of the data transmission device 220 may be created by a combination of information previously used by manufacturers, such as manufacturer code + model code + product serial number.

In addition, if a specific constant value distributed by the authentication server 210 is added to the above value to generate a unique ID of each data transmission device 220 using a hash or encryption method, an attempt to predict and attack this is prevented. can disable it.

The unique ID of the data transmission device 220 is a value calculated through mathematical operations on the constant value distributed by the authentication server 210 and information on the physical parts constituting the data transmission device 220, and is calculated by another device. It is the only value that does not overlap with a value.

device_id = fid(k, d1, d2, d3,,,dn) - - - Equation (1)

here,

device_id: Unique ID of the sending device

fid: A hash function or encryption function as a unique ID generation function

k: a constant value distributed by the authentication server 210

d1,,,dn: A value calculated through mathematical operation of information on physical parts constituting the data transmission device 220, and a unique value that does not overlap with values calculated by other devices

ex) device_id = fid(k, device_args, nonce)

here,

device_args: device information (manufacturer code + model code + product serial number or Mac

Address, etc.)

nonce: random number

If the credential is correctly performed, the authentication server 210 generates a one-time authentication code (A_device) from the unique ID of the data transmission device 220 .

A_device = fauth(device_id) - - - Equation (2)

here,

A_device: one-time authentication code

fauth: one-time authentication code generation function

device_id: Unique ID of the data transfer device

The unique ID of the data transmission device 220 may be directly used as the one-time authentication code, or a value modified through mathematical operation may be used as the one-time authentication code.

Since the one-time authentication code (A_device) is a unique value for authenticating each data transmission device 220 , it is necessarily unique within the authentication route.

Here, the authentication root means a system comprising one or more authentication servers and having the same function as the authentication server according to the invention.

A method of implementing a one-time authentication code (A_device) and a unique ID (device_id) by using a mathematical operation to have a 1:1 relationship always exists mathematically.

For example, one-time authentication code (A_device) can be obtained simply by XORing a specific value on the unique ID (device_id). (device_id) can be obtained.

On the other hand, a one-time authentication code (A_device) can be obtained simply by combining a counter that increases by a predetermined value (for example, increases by 1) whenever the above-described unique ID (device_id) is generated. may be

Here, the one-time authentication code should be used only once and discarded.

The generation of the sender code (code_sender) by the data transmission device 220 is performed as follows.

code_sender = fsolve(fval(A_device, data)) - - - Equation (3)

here,

code_sender: sender code

fsolve: transform function

fval: Validation value generation function

A_device: one-time authentication code

data: data to send

If a hash algorithm such as '' is used as the verification value generating function (fval) in Equation (3), it is possible to generate the same sender code (code_sender) for the same '', as a result, the sender code (code_sender) within the authentication root ) is a unique value.

The data transmission device 220 converts the verification value using the conversion function fsolve and transmits it to the authentication server 210 as a sender code (code_sender).

The sender code (code_sender) is stored in the authentication server 210 , and is deleted from the authentication server 210 after the authentication server 210 processes the verification request from the data receiving device 230 .

Here, the reason for applying the conversion function (fsolve) is as follows.

When a third party acquires the sender code (code_sender) transmitted by the data transmission device 220 during communication, the data receiving device ( 230) is possible, as well as a man-in-the-middle attack that prevents the data receiving device 230 from proceeding with the verification procedure by transmitting a sender code (code_sender) to the authentication server 210 .

To prevent this, in the present invention, the sender code (code_sender) transmitted by the data transmission device 220 and the receiver code (code_receiver) transmitted by the data reception device 230 are not the same, but have a 1:1 function relationship. , to prepare them for a man-in-the-middle attack.

The data receiving device 230 generates a receiver code (code_receiver) is performed as follows.

code_receiver = fval(A_device, data) - - - Equation (4)

here,

code_receiver: receiver code

fval: Validation value generation function

A_device: one-time authentication code

data: received data

The receiver code (code_receiver) generated by the data receiving device 230 is transmitted to the authentication server 210 .

The authentication server 210 compares the stored sender code (code_sender) and the receiver code (code_receiver) to verify whether the data is valid.

In this case, the authentication server 210 stores a functional relationship (fsolve) between the sender code (code_sender) and the receiver code (code_receiver) therein.

The relationship between the sender code (code_sender) generated by the data transmission device 220 and the receiver code (code_receiver) generated by the data reception device 230 can be expressed by the following equation, and the sender code (code_sender) and the recipient code (code_sender) code_receiver) has a 1:1 correspondence. The conversion function fsolve is stored in the data transmission device 220 , the data reception device 230 , and the authentication server 210 , and is not disclosed to the outside.

The relationship between the sender code (code_sender) and the receiver code (code_receiver) can be expressed as follows.

code_sender = fsolve(code_receiver)

= HASH(code_receiver) - - Equation (5)

or vice versa

code_receiver = fsolve(code_sender)

= HASH(code_sender) - - Equation (6)

is also possible

That is, the conversion function fsolve applied to the verification value by the data receiving device 230 instead of the data transmitting device 220 may be transmitted to the authentication server 210 as a receiver code (code_receiver).

Since the reliable HASH function is determined, an attacker can find out the functional relationship between the sender code (code_sender) and the receiver code (code_receiver) by executing several HASH functions. Therefore, the actual technical implementation of the present invention is

code_sender = HASH(code_receiver), k) - - Equation (7)

Here, k is preferably an arbitrary constant value.

Referring to FIG. 5 , the data transmission device 220 may be the sharing server 120 , and the data reception device 230 may be user terminals 111 and 112 .

For example, the authentication server 210 receives the credential transmitted by the sharing server 120 and performs authentication, and generates a one-time authentication code (A_device) according to the result. In addition, the authentication server 210 stores the sender code (code_sender) transmitted from the sharing server 120, and when the user terminals 111 and 112 transmit the receiver code (code_receiver), the received receiver code (code_receiver) and It is verified by comparing the stored sender code (code_sender). The user terminals 111 and 112 determine whether the data is valid based on the verification result received from the authentication server 210 .

Referring to FIG. 6 , the data transmission device 220 may be the first user terminal 111 , and the data reception device 230 may be the second user terminal 112 .

For example, the authentication server 210 receives the credential transmitted from the first user terminal 111 and performs authentication, and generates a one-time authentication code (A_device) according to the result. In addition, the authentication server 210 stores the sender code (code_sender) transmitted from the first user terminal 111, and when the second user terminal 112 transmits the receiver code (code_receiver), the received receiver code (code_receiver) ) and the stored sender code (code_sender) are compared and verified. The second user terminal 112 determines whether the data is valid based on the verification result received from the authentication server 210 .

Referring to FIG. 7 , the data transmission device 220 may be the sharing server 120 , and the data reception device 230 may be vehicle hardware 240 .

For example, the authentication server 210 receives the credential transmitted by the sharing server 120 and performs authentication, and generates a one-time authentication code (A_device) according to the result. In addition, the authentication server 210 stores the sender code (code_sender) transmitted from the sharing server 120, and when the vehicle hardware 240 transmits the receiver code (code_receiver), the received receiver code (code_receiver) and the stored sender It is verified by comparing the code (code_sender). The vehicle hardware 240 determines whether the data is valid based on the verification result received from the authentication server 210 . Here, the data may be data related to commands and arguments for control and monitoring purposes (eg, unlocking a door, flashing an emergency light, sounding a horn, changing a vehicle status report cycle, etc.).

Referring to FIG. 8 , the data transmission device 220 may be vehicle hardware 240 , and the data reception device 230 may be the sharing server 120 .

For example, the authentication server 210 receives the credentials transmitted by the vehicle hardware 240 and performs authentication, and generates a one-time authentication code (A_device) according to the result. In addition, the authentication server 210 stores the sender code (code_sender) transmitted from the vehicle hardware 240, and when the sharing server 120 transmits the receiver code (code_receiver), the received receiver code (code_receiver) and the stored sender It is verified by comparing the code (code_sender). The sharing server 120 determines whether the data is valid based on the verification result received from the authentication server 210 . Here, the data may be related to monitoring data (eg, vehicle status, information collected while driving, accident information, etc.).

Methods for providing ride-sharing services and security services

9 is a flowchart of a vehicle sharing method according to an example of the present disclosure.

Referring to FIG. 9 , in S110 , the electronic device 121 creates a sharing group for vehicle sharing.

In S120 , the electronic device 121 sets a group rule for the sharing group. Here, the group rule may be associated with at least one of a vehicle usage time and a vehicle usage amount per preset time unit of each of the plurality of owners included in the sharing group. In this case, the total sum of vehicle use time allocated to the plurality of owners based on the group rule may be within the range of vehicle use time pre-allocated to the main owner.

In S130 , the electronic device 121 allows the vehicle use right to at least one sub-owner, except for the main owner, to which the vehicle use right is previously allowed among the plurality of owners.

In S140 , the electronic device 121 manages vehicle use by a plurality of owners.

In addition, the above-described vehicle sharing method may further include a device-to-device authentication step. The device-to-device authentication step may be performed by various embodiments related to the system for providing the above-described security service, and a detailed description thereof will be omitted.

10 is a flowchart of a group rule setting method according to an example of the present disclosure;

Referring to FIG. 10 , in S210 , the electronic device 121 receives a group rule setting message from the main owner through a communication network. In this case, the group rule setting message may include at least one of a vehicle usage time and a vehicle usage amount.

In S220, the electronic device 121 sets a group rule based on the group rule setting message.

11 is a flowchart of a method for processing remaining vehicle usage time according to an example of the present disclosure.

Referring to FIG. 11 , in S310 , when the remaining vehicle usage time occurs when a preset time unit has elapsed, the electronic device 121 sends a notification message including the remaining vehicle usage time to at least one of a plurality of owners through a communication network. sent to the owner of

In S320 , the electronic device 121 receives a processing message for the bonus vehicle use time from at least one owner through a communication network.

In S330 , when a settlement request is included in the received processing message, the electronic device 121 transmits a settlement message corresponding to the remaining vehicle use time to the settlement server 130 through a communication network.

In S340 , when the transfer request is included in the processing message, the electronic device 121 carries over the remaining vehicle use time to a preset time unit.

12 is a flowchart of a method for allocating additional usage time according to an example of the present disclosure.

Referring to FIG. 12 , in S410 , the electronic device 121 receives an additional use request message including an additional use time from at least one owner through a communication network.

In S420, the electronic device 121 transmits a settlement request message corresponding to the additional use time to the settlement server 130 through the communication network.

In S430 , when receiving the settlement completion message corresponding to the settlement request message from the settlement server 130 , the electronic device 121 grants at least one owner an additional vehicle use right corresponding to the additional use time.

13 is a flowchart of a method for allocating additional usage time according to another example of the present disclosure.

Referring to FIG. 13 , in S510 , the electronic device 121 receives an additional use allocation message including additional use time for at least one sub-owner from the main owner through a communication network.

In S520 , the electronic device 121 allows the additional vehicle use right corresponding to the additional use time to the at least one sub-owner. In this case, the permitted additional use time is within a range excluding the total sum of the vehicle use time from the pre-allocated vehicle use time, and may be given priority over the group rule.

14 is a flowchart of a method of providing a security service according to an example of the present disclosure.

Referring to FIG. 14 , the method of providing a security service according to the present disclosure includes a process in which the data transmission device 220 requests credentials from the authentication server 210 ( S602 );

The authentication server 210 receives and authenticates the credential request of the data transmission device 220, and transmits a one-time authentication code to the data transmission device 220 (S604, S606);

a process in which the data transmission device 220 generates a verification value for the one-time authentication code and the data using a verification value generation function (S608);

The data transmission device 220 converts the generated verification value using a conversion function (fsolve), and transmits the converted result as a sender code (code_sender) to the authentication server 210 (S610);

a process in which the authentication server 210 stores the sender code (code_sender) received from the data transmission device 220 (S612);

The data transmission device 220 transmits a one-time authentication code together with the data to be transmitted to the data reception device 230 (S614);

A process in which the data receiving device 230 generates a receiver code (code_receiver) for data using the same verification value generating function as in the data transmitting device 104, the received one-time authentication code, and the received data (S616) ;

a process in which the data receiving device 230 transmits a receiver code (code_receiver) to the authentication server 210 to request verification (S618); and

The authentication server 210 receives the sender code (code_sender) from the data transmission device 220, the receiver code (code_receiver) received from the data reception device 230, the sender code (code_sender) and the receiver code (code_receiver) ) comparing and verifying using a transformation function (fsolve) indicating a 1:1 correlation, and notifying the result to the data receiving device 230 (S618);

includes

Although the sender code (code_sender) generated by the data transmission device 220 and the receiver code (code_receiver) generated by the data reception device 230 are not the same, they have a 1:1 function relationship.

code_receiver = fsolve(code_sender)

= HASH(code_sender)

or vice versa

code_sender = fsolve(code_receiver)

= HASH(code_receiver)

is also possible

According to various embodiments of the present disclosure described above, a closed car-sharing service that can be used by users in a community may be provided. In the car sharing service according to various embodiments of the present disclosure, when the main owner who has already rented a shared vehicle does not have much time to use in the pre-allocated vehicle use time, the remaining use time is calculated based on group rule settings. It can be assigned to sub-owners. Accordingly, in the car sharing service that rents a specific time in advance, the main owner can flexibly use the time allotted to him and also minimize wasted time.

Since examples of the proposed method in the above description may also be included as one of the implementation methods of the present disclosure, it is clear that they may be regarded as a kind of proposed method. In addition, the above-described proposed methods may be implemented independently, but may also be implemented in the form of a combination (or merge) of some of the proposed methods.

The examples of the present disclosure disclosed as described above are provided to enable those skilled in the art to implement and practice the present disclosure. Although the above has been described with reference to examples of the present disclosure, those skilled in the art may variously modify and change the examples of the present disclosure. Accordingly, this disclosure is not intended to be limited to the examples set forth herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

10: car sharing system
111, 112: a plurality of user terminals 120: a sharing server
130: settlement server

Claims (9)

at least one memory (memory) for storing at least one instruction (instruction); and
At least one processor coupled to the memory,
The at least one processor executes the at least one instruction to:
create a sharing group for vehicle sharing;
a group rule for the sharing group, wherein the group rule is associated with at least one of vehicle usage time and vehicle usage amount per preset time unit of each of a plurality of owners included in the sharing group; to set;
allowing the vehicle use right to at least one sub-owner other than the main owner to which the vehicle use right is previously permitted among the plurality of owners; and
configured to manage vehicle use of the plurality of owners;
The total sum of vehicle use time allocated to the plurality of owners based on the group rule is within a range of vehicle use time pre-allocated to the main owner.
electronic device.
According to claim 1,
The at least one processor comprises:
receive a group rule setting message from the main owner; and
further configured to set the group rule based on the group rule setting message,
The group rule setting message includes at least one of the vehicle use time and the vehicle use amount,
electronic device.
According to claim 1,
The at least one processor comprises:
transmitting a notification message including the remaining vehicle use time to at least one owner among the plurality of owners when the remaining vehicle usage time occurs when the preset time unit has elapsed;
receiving a processing message for the remaining vehicle use time from the at least one owner;
when a settlement request is included in the processing message, transmitting a settlement message corresponding to the remaining vehicle use time to the settlement server; and
Further configured to carry over the remaining vehicle use time after the preset time unit when the transfer request is included in the processing message,
electronic device.
4. The method of claim 3,
The at least one processor comprises:
receiving an additional use request message including additional use time from the at least one owner;
sending a settlement request message corresponding to the additional use time to the settlement server; and
When receiving a settlement completion message corresponding to the settlement request message from the settlement server, the at least one owner is further configured to allow an additional vehicle use right corresponding to the additional use time,
electronic device.
4. The method of claim 3,
The at least one processor comprises:
receiving an additional usage allocation message including additional usage time for the at least one sub-owner from the main owner; and
It is further configured to allow an additional vehicle use right corresponding to the additional use time to the at least one sub-owner,
The additional use time is within a range excluding the total sum of the vehicle use time from the previously allocated vehicle use time, and is prioritized over the group rule,
electronic device.
A vehicle sharing method performed by an electronic device, comprising:
creating a sharing group for vehicle sharing;
a group rule for the sharing group, wherein the group rule is associated with at least one of vehicle usage time and vehicle usage amount per preset time unit of each of a plurality of owners included in the sharing group; to set;
allowing the vehicle use right to at least one sub-owner other than the main owner to which the vehicle use right is previously permitted among the plurality of owners; and
and managing the vehicle use of the plurality of owners;
The total sum of vehicle use time allocated to the plurality of owners based on the group rule is within the range of vehicle use time pre-allocated to the main owner.
How to share a car.
7. The method of claim 6,
transmitting a notification message including the remaining vehicle usage time to at least one owner among the plurality of owners when the remaining vehicle usage time occurs when the preset time unit has elapsed;
receiving a processing message for the remaining vehicle use time from the at least one owner;
transmitting a settlement message corresponding to the remaining vehicle use time to a settlement server when the settlement request is included in the processing message; and
When the transfer request is included in the processing message, the method further comprising the step of carrying forward the remaining vehicle use time after the preset time unit,
How to share a car.
8. The method of claim 7,
receiving an additional use request message including additional use time from the at least one owner;
transmitting a settlement request message corresponding to the additional use time to the settlement server; and
When receiving a settlement completion message corresponding to the settlement request message from the settlement server, the method further comprising: allowing an additional vehicle use right corresponding to the additional use time to the at least one owner;
How to share a car.
8. The method of claim 7,
receiving an additional use allocation message including additional use time for the at least one sub-owner from the main owner; and
Further comprising the step of allowing the additional vehicle use rights corresponding to the additional use time to the at least one sub-owner,
The additional use time is within a range excluding the total sum of the vehicle use time from the previously allocated vehicle use time, and is prioritized over the group rule,
How to share a car.

Images