KR102740146B1 - Method And Apparatus for mobility sharing in fleet system - Google Patents

Abstract

The present invention can provide a mobile sharing service in a fleet system. At this time, a method for providing a mobile sharing service can include a step of registering a first device and a mobile with a fleet system, a step of performing authentication for the first device to receive the mobile sharing service through the mobile, and a step of controlling the mobile based on the first device when the authentication is completed. At this time, the first device includes setting information about a user of the first device, and the mobile can change the mobile status information based on the setting information.

Description

Method and Apparatus for Mobility Sharing in Fleet System {Method And Apparatus for Mobility Sharing in Fleet System}

The present invention relates to a method and device for providing a mobile sharing service through a fleet system.

As technology advances, the concept of vehicle ownership is weakening, and the use of shared vehicles is increasing. Specifically, the need to share vehicles, such as car sharing or carpooling, is increasing, but existing shared vehicles do not reflect the diverse tendencies of individual users, so a user-specific interaction system may be needed for this.

In addition, the need for sharing vehicles for the convenience of living in a specific area or residence and receiving services using them is increasing. However, in the case of vehicle sharing, the satisfaction level for services is still not high compared to privately owned vehicles, and vehicle security and service provision are difficult because the vehicle sharing system is not properly established. In the following, considering the above-mentioned points, a vehicle fleet system is to be provided.

In addition, unlike before, vehicles are evolving into various forms of transportation as moving objects, and the description below is based on moving objects.

The present invention can provide a method and device for providing a mobile sharing service through a fleet system.

The present invention can provide a method and device for providing a shared service for a personal mobile device through a fleet system.

The present invention can provide an operating method and device for a system that provides a shared service for a personal mobile device through a fleet system.

The present invention can provide a method and device for controlling a personal mobility sharing service through a fleet system.

According to one embodiment of the present invention, a method for providing a mobile sharing service in a fleet system can be provided. At this time, the method for providing a mobile sharing service can include a step of performing authentication for a first device to receive a mobile sharing service provided through the fleet system as a mobile, and a step of controlling the mobile based on the first device when the authentication is completed. At this time, the first device includes setting information about a user of the first device, and the mobile changes mobile status information based on the setting information, wherein the mobile is a mobile registered in the fleet system based on a second device, and the fleet system can provide the mobile sharing service for the mobile based on a sharing condition set through the second device.

In addition, according to one embodiment of the present invention, a mobile device providing a mobile sharing service in a fleet system can be provided. At this time, the mobile device can include a transceiver for transmitting and receiving a signal, and a processor for controlling the transceiver. At this time, the processor transmits authentication information for providing a mobile sharing service to a first device based on the fleet system, and when authentication between the mobile device and the first device is completed based on the authentication information, the mobile device is controlled based on the first device, wherein the first device includes setting information about a user of the first device, and the mobile device changes mobile device status information based on the setting information, wherein the mobile device is a mobile device registered in the fleet system based on a second device, and the fleet system can provide a mobile sharing service for the mobile device based on a sharing condition set via the second device.

In addition, according to one embodiment of the present invention, a fleet system providing a mobile sharing service can be provided. At this time, the fleet system can include a plurality of devices registered to the fleet system and a plurality of mobiles registered to the fleet system. At this time, a first device among the plurality of devices performs authentication to receive a mobile sharing service as a first mobile among the plurality of mobiles provided through the fleet system, and when the authentication is completed, the first mobile is controlled based on the first device, wherein the first device includes setting information about a user of the first device, and the first mobile changes mobile status information based on the setting information, wherein the first mobile is a mobile registered to the fleet system based on a second device, and the fleet system can provide a mobile sharing service for the mobile based on a sharing condition set through the second device.

Additionally, the following may be commonly applied to methods, devices and systems for providing a mobile sharing service based on a fleet system.

According to one embodiment of the present invention, the sharing condition may be set based on at least one of the usage time information of the mobile device, the movable area information, the departure point information, and the destination information.

In addition, according to one embodiment of the present invention, when the first device uses a mobile sharing service through a fleet system, the first device can transmit departure information, destination information, and mobile usage time information for mobile usage to the fleet system.

Additionally, according to one embodiment of the present invention, the fleet system may provide a mobile device to the first device for a mobile device sharing service if information transmitted by the first device satisfies a sharing condition.

In addition, according to one embodiment of the present invention, the mobile status information may include at least one of a driver's seat position, a driver's seat height, an interior lighting color, an interior lighting brightness, a rearview mirror position, a rearview mirror angle, a side mirror position, a side mirror angle, an interior temperature, a steering wheel angle, a tire pressure, an autonomous driving function setting variable, a transmission setting mode, an instrument panel mode, a navigation setting, a content setting, and a wireless communication connection mode.

Additionally, according to one embodiment of the present invention, when a mobile body is controlled by a first device, operation information about the mobile body can be provided to the first device.

Additionally, according to one embodiment of the present invention, the first device can update setting information for the user based on the driving information.

Additionally, according to one embodiment of the present invention, the driving information may be updated based on machine learning or a learning method and reflected in the setting information for the user.

Additionally, according to one embodiment of the present invention, after authentication is completed, if the first device detects that the mobile is located within a preset distance from the mobile and identification of the mobile is completed, the mobile can change the mobile status information based on the setting information provided by the first device.

In addition, according to one embodiment of the present invention, when the mobile body is a first type mobile body, the mobile body may change the mobile body status information based on the setting information provided by the first device, and when the mobile body is a second type mobile body, the mobile body may only provide the usage permission to the first device and may not change the mobile body status information based on the setting information.

According to the present invention, a mobile sharing service can be provided through a fleet system.

According to the present invention, an interactive vehicle sharing service reflecting the vehicle usage tendencies of individual users can be provided through a fleet system.

According to the present invention, a mobile sharing service can be operated through a fleet system.

According to the present invention, sharing of a mobile device can be controlled through a fleet system.

Figure 1 is a diagram illustrating how a mobile device communicates with another device over a network.
Figure 2 is a diagram illustrating a method for sharing a mobile device based on a fleet system.
Figure 3 is a diagram showing a method for authenticating a mobile device in a fleet system.
Figure 4 is a drawing showing a method for reflecting a user's usage tendencies in a mobile device based on a fleet system.
Figure 5 is a diagram illustrating how personally provided vehicles are shared based on a fleet system.
Figure 6 is a drawing showing a method for providing a mobile sharing service by considering the mobile type.
Figure 7 is a diagram illustrating a method for collecting and learning driving tendency information in a fleet system.
Figure 8 is a diagram showing how a device is coupled to a mobile device in a fleet system.
Figure 9 is a diagram showing the configuration of a device operating in a fleet system.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

In describing embodiments of the present disclosure, if it is determined that a specific description of a known configuration or function may obscure the gist of the present disclosure, a detailed description thereof will be omitted. In addition, parts in the drawings that are not related to the description of the present disclosure have been omitted, and similar parts have been given similar drawing reference numerals.

In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection relationship, but also an indirect connection relationship in which another component exists in between. In addition, when a component is said to "include" or "have" another component, this does not exclude the other component unless specifically stated otherwise, but means that the other component may be included.

In this disclosure, the terms first, second, etc. are used only for the purpose of distinguishing one component from another component, and do not limit the order or importance between the components unless specifically stated. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

In the present disclosure, the components that are distinguished from each other are intended to clearly explain the characteristics of each, and do not necessarily mean that the components are separated. That is, a plurality of components may be integrated to form a single hardware or software unit, or a single component may be distributed to form a plurality of hardware or software units. Accordingly, even if not mentioned separately, such integrated or distributed embodiments are also included in the scope of the present disclosure.

In the present disclosure, the components described in various embodiments do not necessarily mean essential components, and some may be optional components. Accordingly, an embodiment that consists of a subset of the components described in one embodiment is also included in the scope of the present disclosure. In addition, an embodiment that includes other components in addition to the components described in various embodiments is also included in the scope of the present disclosure.

The advantages and features of the present invention, and the method for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments presented below, but may be implemented in various different forms, and these embodiments are provided only to make the disclosure of the present invention complete and to fully inform a person having ordinary skill in the art to which the present invention belongs of the scope of the invention.

FIG. 1 is a diagram illustrating a method for a mobile device to communicate with another mobile device or device through a network. Referring to FIG. 1, a mobile device can communicate with another mobile device or device. At this time, as an example, the mobile device can communicate with another mobile device or device based on cellular communication, WAVE communication, DSRC (Dedicated Short Range Communication), or other communication methods. That is, a communication network such as LTE or 5G, a WiFi communication network, or a WAVE communication network can be used as a cellular communication network. In addition, a short-range communication network used in a mobile device, such as DSRC, can be used, and is not limited to the above-described embodiment. The mobile device can be equipped with a device capable of performing communication, and can communicate with another device based on the device.

In addition, as an example, in relation to communication of a mobile device, a module that can perform communication only with devices located inside the mobile device for the purpose of securing the mobile device and a module that can perform communication with devices outside the mobile device may exist separately. For example, inside a vehicle, communication based on security can be performed only with devices within a certain range inside the mobile device, such as Wi-Fi communication. As an example, a mobile device and a personal device of a driver of the mobile device may include a communication module for performing communication only between each other. In other words, the mobile device and the personal device of the driver of the mobile device may use a communication network that is blocked from an external communication network, and may also use an In Vehicle Network. In addition, as an example, the mobile device may include a communication module that performs communication with an external device. Through this, the mobile device may receive necessary information from the outside and operate based on the fleet system based on the information.

In addition, FIG. 2 may be a method for providing a mobile sharing service based on a fleet system. For example, a fleet system may be applied to provide a mobile sharing service. At this time, the fleet system may be a system including a plurality of devices and a plurality of mobiles. At this time, each of the plurality of mobiles may have a specific owner. That is, there may be a separate owner for each of the plurality of mobiles, and other users may use them based on the fleet system. For example, a separate owner device may correspond to each of the plurality of mobiles. That is, there may be a device corresponding to the owner for each mobile. In addition, for example, there may be a device for each user using each mobile. In this case, the users may use the mobile based on each device. In the following, for convenience of explanation, the device for the owner is referred to as the owner device, and the device for the user is referred to as the tenant device. However, this is only an example for convenience of explanation, and is not limited to the above-described embodiment. In addition, for example, the owner device and the tenant device may be smart devices. In addition, the owner device and the lessee device may be devices worn by a person. For example, they may be smart watches or other decorations. As another example, the owner device and the lessee device may be SIM cards. For example, the SIM card may be a portable device. As another example, the owner device and the lessee device may be separate devices for the fleet system. That is, the owner device and the lessee device may be devices for mobile device recognition, and are not limited to the above-described embodiments.

Also, as an example, the mobile body may be a vehicle. Also, as an example, the mobile body may be an object that moves in an area equipped with rails, etc. As another example, the mobile body may be a flying object, such as a drone, etc. In other words, the mobile body may refer to a movable object, and may mean a mobile body shared based on a fleet system. However, for the convenience of explanation, it is described as a vehicle below, but this may be equally applied to other mobile bodies.

In addition, as an example, referring to FIG. 2, the above-described mobiles and devices may always be connected through a network based on the fleet system. More specifically, a specific mobile in the fleet system may always be connected to a device of the mobile owner. For example, a service may be provided through the fleet system only when the mobile is connected to the device of the mobile owner, and is not limited to the above-described embodiment. In addition, as an example, a plurality of mobiles in the fleet system and the devices of tenants who may use the mobiles may always be connected through a network. That is, tenants may check information about the mobiles provided based on the fleet system in real time through their devices, and may perform operations for services using the mobiles based on this. Meanwhile, as another example, the mobiles and devices that are mutually connected based on the fleet system may be limited to the mobiles and devices included in a specific group. For example, a large number of mobiles and devices may be registered in the fleet system. At this time, unnecessary overhead may occur only when the mobiles and devices registered in the fleet system are mutually connected, and service provision may not be smooth. In consideration of the above, the fleet system can provide connections for the mobiles and devices included in a specific group. That is, management of service provision can be performed based on groups that can be interconnected in the fleet system. Meanwhile, the devices for the mobiles and the mobile owners can be connected to the devices of the tenants within the group in which they are included. In addition, the tenant devices are always connected to the mobiles within the group in which they are included, so that the status of the mobiles can be checked in real time and whether or not to use them. That is, as described above, a plurality of devices and a plurality of mobiles can be connected to each other, and the following describes a method of recognizing a mobile that a tenant wants to use based on the above-described situation and using the mobiles based on this.

As another example, RSU may be a device capable of communication as a roadside device. Also, as an example, RSU may refer to a structure installed to transmit and receive signals to a building or other area, and is not limited to the above-described embodiment. However, for the convenience of explanation, it is collectively referred to as RSU below, and this may refer to various structures or devices, and is not limited to the above-described embodiment.

In addition, as an example, an RSU may be a communication-capable device that is placed at a certain distance or periodically on a road. In addition, as an example, an RSU may be a device that is placed at a certain point on a road and that can communicate with a mobile object. In another example, an RSU may refer to a terminal that can communicate as a traffic infrastructure. In another example, an RSU may refer to a V2X terminal, a surrounding mobile object, or another device that can communicate with a mobile object. In other words, an RSU refers to a device that can perform communication with a mobile object in the vicinity of a mobile object, and is referred to as an RSU below for convenience of explanation.

As another example, the fleet system may provide a mixed fleet of shared vehicles provided by the system as well as private vehicles with owners as described above. As an example, the fleet system may set identification information to distinguish shared vehicles provided by the system from privately owned vehicles. At this time, a privately owned vehicle indication field may exist, and if the privately owned vehicle indication field has a value of 0, the shared vehicle may be indicated as a vehicle provided by the system provider without private ownership. On the other hand, if the privately owned vehicle indication field has a value of 1, it may indicate that private ownership exists in the vehicle and that such vehicle is provided to the fleet system as a shared vehicle, as shown in Table 1 below. That is, based on the above, a case where privately owned vehicles and shared vehicles provided by the system are mixed may also be considered. At this time, as an example, a service provided by the fleet system may differ based on the vehicle type indication field. For example, in the case of a fleet system-provided vehicle, there may be no usage restrictions for a user using the vehicle. On the other hand, in the case of a privately shared vehicle, usage restrictions may exist. As another example, in the case of fleet system vehicles and personal shared vehicles, services may be provided based on different charging systems, and are not limited to the above-described embodiments.

[Table 1]

As another example, with respect to specific operations of the fleet system, services may be provided based on devices registered with the fleet system.

More specifically, a device registered in the fleet system can obtain information about a shared mobile device after the system and authentication and security procedures. That is, information about a shared mobile device can be provided from the device's perspective. At this time, the device can contact the mobile device it wants to use based on the information about the shared mobile device.

For example, there may be a vehicle registered in the fleet system and a registered device (or user). At this time, the vehicle registered in the fleet system may be a privately owned vehicle as described above. For example, if a privately owned vehicle is registered in the fleet system, the fleet system may provide information on incentives by considering a situation in which the privately owned vehicle is leased to another person. For example, the fleet system may determine incentive information based on the type, condition, model year, rental time, and at least one of the provided private vehicles. That is, the fleet system may calculate incentive information for the private vehicles provided to the lessee and provide the same to the owner of the private vehicles. For example, the owner of the private vehicles may receive a certain reward from the fleet system based on the incentive information. In addition, as an example, it may be utilized as information for using the fleet system, and is not limited to the above-described embodiment.

In addition, as an example, only certain mobiles and devices can be registered in the fleet system based on authentication and authorization. At this time, the fleet system can be operated based on the status information of the registered mobiles and registered devices. For example, the fleet system can check information on the currently used mobiles and location information on each mobile in real time. At this time, as an example, each mobile can periodically transmit its information to the fleet system. In addition, as an example, each mobile can transmit its information to the fleet system based on an event trigger. For example, when an event is triggered that changes the location of the mobile or changes the use, the mobile can transmit its information to the fleet system (or server). In addition, the fleet system (or server) can check information on the registered devices in real time. At this time, as an example, the registered devices may not always use the services of the fleet system. Therefore, activation information indicating whether the registered devices use the services of the fleet system may be required. At this time, as an example, the fleet system may include list information on the registered devices. Among the registered devices included in the list of the fleet system, devices currently using a mobile device or devices that have activated the system to use a mobile device can be provided with list information. As another example, registered devices that do not use the fleet system (deactivated devices), registered devices that are using a mobile device of the fleet system (activated devices), and registered devices that intend to use a mobile device (temporary devices) can be displayed separately. In other words, information can be provided on whether the device is actually being used, has no intention of using it, or has intention to use it but has not yet been used. In addition, as an example, usage status information can be further indicated for a device that is using a mobile device of the fleet system. As an example, the usage status information can further include expected usage time information or usage location information.

More specifically, the fleet system may include list information for a plurality of registered mobiles and a plurality of devices. At this time, the list information may include at least one of usage status information, device location information, and mobile location information. At this time, the fleet system may provide a mobile sharing service based on the device location information and the mobile location information. In addition, the usage status information described above may include at least one of the mobile information in use, the expected time information for the mobile information in use, the device-mobile matching information, the deactivated device information, the activated device information, the deactivated mobile information, and the activated mobile information. At this time, as an example, the usage status information may further include the mobile information in use currently being used by another device and the expected time information for the mobile information in use. In addition, the usage status information may further include the device-mobile matching information based on the information in the form of a list. In addition, the usage status information may include the activated device information and the deactivated device information. As an example, the activated device information may be a device that is currently using a mobile or is preparing to use a mobile among the devices registered in the fleet system as described above. For example, an active device may refer to a device that runs a program or application for a fleet system. On the other hand, an inactive device may refer to a device that is registered with a fleet system but does not use mobile sharing. For example, an inactive device may refer to a device that does not run a program or application for a fleet system or that has been inactivated.

In addition, the fleet system may include information on activated vehicles and information on inactive vehicles. In this case, as an example, the fleet system may include status information on a plurality of vehicles. In this case, the status information on the vehicles may be information on the vehicles, such as information on whether the vehicles are abnormal, information on the remaining driving distance, or information on the time of refueling. In other words, the status information on the vehicles may be information for determining whether the vehicles can be provided for vehicle sharing, and is not limited to the above-described embodiment. In this case, the fleet system may determine whether the vehicles are activated based on the above-described status information. For example, the fleet system may provide information on a vehicle that is not abnormal in its vehicle status and has sufficient fuel as an activated vehicle. On the other hand, the fleet system may classify a vehicle that is abnormal in its vehicle status as an inactive vehicle. In this case, the fleet system may provide information on the inactive vehicles to a linked system or server. For example, the linked system or server may perform repair or management on the inactive vehicles, and is not limited to the above-described embodiment.

Also, as an example, the fleet system can classify a vehicle with a fuel level below a certain level as an inactive vehicle as described above. As another example, if a vehicle with a fuel level below a certain level is shared through a device, the fleet system can provide information about the fuel level to the device user through a notification. Also, as an example, the fleet system can provide information about a designated system linked to the user (e.g., a gas station of a specific brand) and provide information that refueling is required. In this case, the fleet system can exchange billing or other necessary information with the designated system linked regardless of the user and provide a service based on this.

In other words, users of the vehicle sharing system can refuel at designated locations without paying, and the costs can be processed through the fleet system and linked systems.

Meanwhile, as an example, a device (temporary device) that wants to use a mobile device as described above may check the fleet system and use the mobile device.

For example, referring to FIG. 3, the device (310) can be allocated a mobile object (320) to be used through the fleet system (or server, 330). At this time, for example, the fleet system (or server, 330) can allocate the mobile object (320) to the device (310) using at least one of information about the mobile object (320) being used, location information of the mobile object, and location information of the device. Meanwhile, for example, if the fleet system (330) cannot allocate the mobile object (320), it can provide information about the failure to the device (310). In addition, for example, the fleet system (330) can perform allocation only for a mobile object (320) within a certain distance from the location of the device (310), and is not limited to the above-described embodiment. Next, the device (310) can approach the mobile object (320) within a certain distance. At this time, the device (310) can transmit an authentication signal to the mobile (320). In addition, as an example, the device (310) can use the shared mobile (320) through a tag for the shared mobile based on a list of available shared mobiles. As an example, the device (310) can tag the mobile based on NFC, Bluetooth, or a magnetic such as a transportation card. At this time, the shared mobile (320) can perform an authentication procedure from the fleet system (330) when the device (310) is tagged so that the device (310) can provide the mobile (320). As an example, when authentication is completed based on the device tag, the door of the mobile (320) can be opened.

With regard to a more specific operation for authentication, referring to FIG. 3, when a device (310) approaches a mobile body (320) within a certain distance, an authentication signal may be transmitted to the mobile body (320). At this time, the communication that can be used by the mobile body (320) and the device (310) may be Bluetooth, NFC, or a tag as described above. That is, a procedure for authentication may be performed under certain conditions, and is not limited to the above-described embodiment. When the device (310) approaches (or tags) the mobile, the mobile and the device exchange signals to determine whether the device (310) can use the mobile, and can be authenticated. At this time, the device (310) can transmit an authentication signal including its own identification information and identification information of a group to which it is included to the mobile. At this time, the mobile (320) can check whether the device (310) is a device registered in the fleet system (330) based on the identification information of the device (310) included in the received authentication signal. In addition, the mobile (320) can check whether the device (310) is a device (310) included in a group to which it can provide a service based on the identification information of the group included in the authentication signal. That is, the mobile (320) can determine whether the device (310) can use the mobile (320) based on the device identification information and the group identification information. For example, if the device (310) cannot use the mobile (320), The mobile device (320) can transmit information about unavailability to the device (310). For example, the device (310) can obtain information about unavailability from an application or other service providing program.

Meanwhile, if the device can use the mobile body (320), the mobile body (320) can transmit a signal for requesting execution of an authentication procedure to the device (310). That is, if the device (310) is legally registered in the fleet system (330) described above, and the mobile body (320) can also legally operate based on the fleet system (330), the mobile body (320) can transmit a signal for requesting execution of an authentication procedure to the device (310). At this time, the mobile body (320) can transmit its own identification information and encryption key information to the device (310) in the signal for requesting execution of the authentication procedure. For example, both the identification information of the mobile body and the device information may be information registered in the fleet system. At this time, the mobile body (320) can transmit a signal including the identification information of the mobile body, the identification information of the device, and the encryption key information to the fleet system (330).

Additionally, the device may also transmit a signal including identification information of the mobile device, encryption key information, and its own identification information included in the authentication procedure execution request signal to the fleet system.

Thereafter, the fleet system (330) can compare the information included in the signal received from the mobile (320) and the signal received from the device (330). At this time, if the identification information of the mobile, the identification information of the device, and the encryption key information all match, the fleet system (330) can recognize that the device (310) can use the mobile. Thereafter, the fleet system (330) can transmit authentication confirmation information to the mobile (320) and the device (330). At this time, the fleet system (330) can register information that the device (310) uses the mobile (320) in the database. In addition, as an example, the time at which the device (310) uses the mobile (320) and additional information can also be continuously transmitted.

Additionally, the mobile device (320) can register the device based on the authentication verification information and open the mobile device door. Additionally, the lock device for using the mobile device can be released and the device (310) can control the mobile device.

At this time, for example, when the above-described authentication is completed, the mobile body (320) and the device (310) can periodically exchange signals. That is, while the device (310) uses the mobile body (320), the mobile body (320) can perform continuous confirmation of use through periodic signal exchange with the device (310).

At this time, as an example, referring to FIG. 4, the device may provide information on personal tendencies or user information to the vehicle. As an example, the device may include information on autonomous driving level information, vehicle seat, instrument panel mode settings, usage channels, navigation settings, personal device settings, mirror settings, etc. as personal tendencies information. However, this is only one example and is not limited to the above-described embodiment. That is, the vehicle provided by the fleet system may be in the form of communicating with a personal device in which the driving tendencies (style) of the individual are stored in a learned manner. Through this, even when a personally owned vehicle is provided to a lessee, a service tailored to the lessee can be provided. That is, the driving performance and driving environment of the vehicle can be converted and provided in a customized manner to the user. As shown in FIG. 4 described above, information set to the user can be converted and provided in a customized manner to the user. For more specific examples, various driving environments such as the position and height of the driver's seat, the color and brightness of interior lights, the position and angle of the rearview mirror and side mirror, the range of temperature adjustment (air conditioning and heater) in the car, the angle of the steering wheel, the tire pressure, the transmission setting mode (normal, eco, power mode, etc.), the wireless communication connection mode (WAVE, cellular, etc.), and the range of autonomous driving function setting variables (speed and inter-vehicle gap, lane change lateral speed, acceleration and deceleration, etc.) can be changed and provided according to the driving tendencies set in the user's personal device. At this time, as an example, in order to operate based on the above, setting information about the tenant can be stored in the tenant device. At this time, when the tenant uses a mobile device, the tenant device can be linked with the mobile device. For example, as described above, when the tenant device is linked to the mobile device, setting information about the tenant is provided to the mobile device, and can operate as described above. As another example, if the lessee device is linked to a mobile device and the lessee uses the mobile device, driving information about the lessee can be updated in the device. That is, the device can perform an update based on information obtained from the rented mobile device as the driving information about the lessee. Thereafter, the device updates the setting information of the lessee and can further utilize the updated information when renting another mobile device in the future. That is, the history information about the lessee is managed by the lessee device and the related information can be utilized when the lessee uses a personally owned mobile device. Meanwhile, as an example, if the lessee device and the mobile device are linked, information about the use of the mobile device can be transmitted to the owner device. As an example, if the owner device is linked to the lessee device and the mobile device is used by the lessee, the owner device can continuously check information about whether the mobile device is rented. Through this, the owner device can continuously check information about the owned mobile device.

At this time, for example, each user may have different settings for operating a vehicle, and if each user uses a vehicle that does not match his or her settings, accidents may increase due to reasons such as lack of skill in operation. Therefore, the risk of accidents may increase when shared vehicles are used. Considering the above, if the fleet system provides a sharing service through shared vehicles, the vehicle settings may be set differently based on the user's personal preferences through the information described above.

Another example may be a case where a tenant reuses a previously used vehicle based on a fleet system. For example, in a case where a private vehicle is shared based on a fleet system, there may be many cases where the same tenant uses the same vehicle based on similar lifestyle patterns. Considering the above, the tenant device may store history information about the vehicle used once. In addition, as an example, the vehicle may also store history information about the tenant device used once. In this case, as an example, if the vehicle and the tenant device perform initial settings and perform recognition for the first time, multiple procedures for authentication and identification may be performed. However, as described above, if the tenant device or the vehicle includes history information about the usage history, additional procedures may be omitted with only basic authentication for the use of the vehicle. For example, if the tenant device performs only basic authentication for the vehicle, the settings for the vehicle may be automatically changed based on the previous usage history. In addition, as an example, the history information may include usage history information, driving pattern information, personal tendency information, and driving tendency information based on the tenant device, and is not limited to the above-described embodiment. In this case, as an example, the mobile device may further perform additional settings for the tenant device based on the above-described history information, and is not limited to the above-described embodiment.

In addition, in a specific example of a device using a shared mobile, the device can check a list of shared mobiles provided and select a shared mobile. At this time, when the device is adjacent to or comes into contact with a shared mobile, the shared mobile can be used centered on the device. At this time, settings for the shared mobile or other related settings can be changed centered on the device so that the device user can use the shared mobile. At this time, the setting information for the mobile can be changed not only for security and authentication-related settings but also for content, etc., reflecting even the tastes or tendencies of the device user. For example, the form displayed on the shared mobile can be changed based on the interface set on the device, and operation can be performed based on this. That is, as described above, when the device approaches the shared mobile, the shared mobile can be changed centered on the device and used.

As a more specific example, referring to FIG. 5, a privately owned vehicle (510) may be provided to a lessee by a fleet system. At this time, as an example, the privately owned vehicle (510) may be set with vehicle owner information before being provided to the lessee. As an example, the information described above in FIG. 4 may be set based on the vehicle owner information. Thereafter, the privately owned vehicle (510) may be provided to the lessee by the fleet system. At this time, conditions may be set for sharing the privately owned vehicle (510). As an example, the conditions for sharing may be set based on at least one of vehicle usage time, movement restriction area, departure point, destination, and vehicle status. As an example, an owner device (530) corresponding to the privately owned vehicle (510) may set conditions for sharing the privately owned vehicle (510). As an example, an application for the fleet system may exist in the owner device (530). At this time, information on sharing conditions can be input by the owner through the application. Thereafter, the owner device (530) can transmit the input information to the fleet system and provide a mobile sharing service based on this. Meanwhile, as an example, the fleet system can set a grade for the above-described sharing conditions and provide high incentive information when the grade is high. On the other hand, the fleet system can provide low incentive information when the grade is low. That is, when many conditions are set as sharing conditions and there are many restrictions for providing sharing services, low incentive information can be provided. On the other hand, when not many conditions are set as sharing conditions and the sharing service can be provided relatively easily, high incentive information can be provided. As an example, the owner device (530) can receive additional services from the system based on the incentive information. For example, when the owner device (530) uses another mobile as a shared mobile, the service can be provided based on the above-described incentive information. That is, the incentive information can be a type of compensation, and the fleet system can be operated based on this.

Meanwhile, the lessee can obtain information about available vehicles from the fleet system based on the sharing conditions described above. For example, the lessee device (520) may also have an application for the fleet system. At this time, the lessee device (520) may set information about the starting point, destination, and usage time, and search for a shareable vehicle based on this. At this time, the shareable vehicle may be one in which the starting point, destination, and usage time are within an allowable range based on the sharing conditions described above. Thereafter, the lessee may select a specific vehicle and perform identification and authentication based on the fleet system. At this time, if the identification and authentication are completed based on the fleet system, the lessee device (520) may use the corresponding vehicle (510). At this time, if the lessee device (520) is adjacent to the corresponding vehicle (510) or performs vehicle recognition in a certain manner, the lessee device (520) may use the corresponding vehicle (510). At this time, for example, the lessee device (520) can store the lessee setting information as in the above-described FIG. 4. At this time, when the lessee device (520) can use the corresponding mobile device (510), the lessee device (520) can provide the lessee setting information to the corresponding mobile device (510). At this time, the corresponding mobile device (510) can change the setting of the mobile device based on the information received from the lessee device (520). For example, as described above, the dashboard information or the autonomous driving level can be set based on the lessee device (520). Through this, the lessee can use the mobile device in a familiar environment even when using a different mobile device. Thereafter, the case where the lessee device (520) ends the use of the corresponding mobile device (510) can be considered. At this time, as an example, referring to FIG. 5A, the mobile device (510) can additionally provide a shared service to another tenant device, and can maintain the settings. At this time, the other tenant device performs identification and authentication based on the fleet system, and when the mobile device (510) is used, the mobile device settings can be changed based on the setting information of the other tenant device. On the other hand, when the tenant use is terminated and the mobile owner device (530) completes identification and authentication for its own mobile device (510), the setting information for the mobile device (510) can be changed again based on the mobile owner information stored in the owner device (530). That is, when mobile sharing is terminated, the previous state can be restored based on the setting information for the mobile owner, and based on this, the mobile owner can also use the mobile device in the same way as before.

In addition, as an example, referring to FIG. 5b, when the lessee device (520) ends use of the mobile device (510), the setting information for the mobile device (510) may be changed to the setting information for the owner device (530). That is, when the use of the lessee device (520) is ended, the existing setting of the owner device (530) may be immediately restored, so that the owner device (530) may use the mobile device (510) in the state before sharing, thereby providing convenience. That is, even if the mobile device owner shares his or her mobile device with the lessee, he or she may directly use his or her setting information without changing the setting information, thereby reducing inconvenience caused by the provision of a sharing service. At this time, as an example, when the mobile device (510) is used again by another lessee device, the mobile device may be changed to the setting information for another lessee device after the other lessee device completes identification and authentication, and is not limited to the above-described embodiment.

In addition, as an example, when the lessee device (520) drives via the corresponding mobile device (510), the lessee setting information of the lessee device (520) may be updated. As an example, the lessee setting information may include information related to driving, and the lessee device (520) may update the relevant information based on information acquired while using the mobile device (510). As another example, the setting information may be changed by the lessee device (520). As an example, the lessee may change the setting information through an application in the lessee device (520). However, in the case of the mobile device setting, the setting information may be applied more accurately to the user when the setting information is changed while sitting in the mobile device or while using the mobile device. Considering the above, when the lessee device (520) is using the corresponding mobile device (510), the lessee may change the setting for the corresponding mobile device (510). At this time, information about the change in settings for the mobile device can be transmitted to the tenant device (520), and the tenant device (520) can reflect this and store related information in the tenant device (520). That is, the setting information for the tenant can be stored and updated in the tenant device (520). At this time, the tenant can utilize the above-described update information when using another mobile device.

As another example, referring to FIG. 6, legacy mobility and fleet applied mobility can be considered. More specifically, if a shared mobility is provided by a fleet system, the shared mobility may not have a problem supporting operations or functions provided by the fleet system. However, if a personal mobility is provided as a shared mobility by the fleet system, the personal mobility may not support all operations or functions provided by the fleet system. In this case, as an example, the fleet system may provide a shared mobility service only to a fleet system mobility that supports fleet system operations.

As another example, shared vehicle services may be provided for vehicles that do not support all operations or functions of the fleet system, taking into account compatibility with existing or legacy systems. For example, a vehicle that does not support all operations or functions of the fleet system may be a first-type vehicle. On the other hand, a vehicle that supports all operations or functions of the fleet system may be a second-type vehicle. In other words, the fleet system may provide different vehicle sharing services considering the type of the vehicle.

As a specific example, referring to FIG. 6(a), a tenant device (610) can use a legacy mobile (620) through a fleet system. At this time, the legacy mobile (620) may be a mobile that cannot change its mobile status based on the tenant setting information stored in the tenant device (610). In other words, even if the tenant setting information is transmitted to the corresponding mobile (620), the mobile setting information may not be changed in the corresponding mobile (620). At this time, when the tenant device (610) completes identification and authentication for the legacy mobile (620), the fleet system can only provide the mobile door opening and usage authority for the corresponding mobile (620). In other words, the tenant device (610) can only be granted the authority to use a specific mobile (620) through the fleet system, and can use the corresponding mobile (620) based on this.

On the other hand, the vehicle to which the fleet system is applied can operate as described above. For example, referring to FIG. 6(b), based on the fleet system, the tenant device (610) can complete identification and authentication for the vehicle (630) to which the fleet system can be applied. At this time, as described above, the tenant setting information stored in the tenant device (610) is provided to the corresponding vehicle (630), and the corresponding vehicle (630) can change the vehicle setting information as described above based on the tenant setting information. That is, the fleet system can provide sharing services for existing vehicles and sharing services for vehicles to which the fleet system is applied, and can perform compatible operations with the existing system based on this.

As another example, referring to FIG. 7, the information described above may be information that is continuously learned based on machine learning. More specifically, based on FIG. 4, personal tendencies or driver information may be information set by the user. However, there are many cases where the driver may not know the information accurately. In other words, the driver may not be able to clearly confirm the exact values and settings for the information. At this time, as an example, the user's personal device (710) may collect information on driving tendencies based on information on shared vehicle use. For example, the driver may adjust some settings according to convenience from the default settings based on the driving tendencies information while using the shared vehicle (720). In addition, the driver may change the settings described above in consideration of a specific situation or driving condition while driving. At this time, the user may be aware of the change described above, but may not be able to recognize it as an exact value or value. Considering the above, the personal device (710) may collect information on vehicle driving or information on driving tendencies. Thereafter, the personal device (710) can continuously update the setting information suitable for the user through machine learning or learning. At this time, if the number of times the user uses the shared vehicle increases, the related information can increase. At this time, the personal device (710) can analyze the driver's tendencies and other information based on the above-described information and learn this. Thereafter, the personal device (710) can apply the above-described change information when using the next shared vehicle. That is, since the user cannot input all of the driving tendencies or other information in numerical form, the information about this can be automatically acquired through machine learning and learning, and a service can be provided based on this. Through this, the lessee can use the shared vehicle based on the same settings even if he or she uses a different vehicle, and the convenience of the user can be increased.

As another example, referring to FIG. 8, the device (810) may be used in a state of being coupled with a mobile (820). For example, in the case of sharing a mobile, there may be a security issue. In addition, if a control authority is changed by another device while a specific device is using the mobile, a risk of an accident may occur. Considering the above, a method of increasing the security and authentication level of the mobile may be required. At this time, as an example, the mobile (820) may periodically transmit information about being “in use” to the fleet system while the device (810) is coupled or while periodically exchanging signals with the device (810). At this time, the fleet system may exclude the above-mentioned mobile from the shared mobile list provided to other devices based on the information received from the mobile. In addition, as an example, the mobile (820) may periodically report information about the case where the device (810) is using the mobile (810) to the fleet system. For example, information on mileage, information on the amount of fuel used, information on the travel route, and information on other services provided may be periodically provided to the fleet system. At this time, for example, the fleet system may transmit charging information to the device (810) based on the information received from the vehicle. In addition, for example, the fleet system may provide usage information to the device (810) based on the information received from the vehicle (820), and may perform cost calculation based on the charging system at a later time, and is not limited to the above-described embodiment.

At this time, as an example, the device (810) may be coupled with the mobile body (820) in a state in which it is attached or coupled to the mobile body as in FIG. 8a. In addition, as an example, the device (810) may be positioned at the upper part inside the mobile body (820) as in FIG. 8b. At this time, a cradle or pad to which the device (810) may be coupled may exist inside the mobile body (820). At this time, the cradle or pad may couple the device (810) to the mobile body based on magnetic or magnetic properties. As an example, after the device (810) performs authentication with the mobile body (820) based on the above, the mobile body (820) may be controlled only when the device (810) is attached to the above-described cradle or pad. That is, the mobile body status information of the mobile body (820) may be changed through authentication of the device (810). At this time, the security level for using the mobile body (820) is increased, and the mobile body (820) can be controlled while the device (810) is coupled to the cradle or pad in consideration of linkage with the device (810), and is not limited to the above-described embodiment.

In addition, for example, charging may be performed when the device (810) is coupled to the cradle or pad described above. More specifically, the device (810) may be attached to the mobile body (820) to be charged, and may exchange information with the mobile body (820) while attached. In addition, for example, as in FIG. 8c, the device (810) may be attached inside the mobile body (820) to face the driving direction of the mobile body (820). At this time, for example, the device (810) may additionally display information on the use of the mobile body (820) or may further display information (e.g. navigation) on the driving of the mobile body (820), and is not limited to the above-described embodiment. That is, the device (810) may be attached or coupled to the mobile body (820) to perform identification and authentication, and the above-described fleet service may be provided.

In addition, as an example, as described above, the device (810) may be maintained in a coupled state to provide driving tendency information to the device (810) through machine learning or a learning method. That is, the device (810) may provide personal driving tendency information or setting information as described above only when the device is coupled to a moving object. Through this, the device (810) may obtain personal driving tendency information or setting information as described above only when actually driving or actually being used, and may provide a personalized service by machine learning or learning actual information.

Meanwhile, as an example, a shared mobile used in a fleet system may include a module for operating based on the fleet system. As an example, the module may be an interface module for allowing the mobile and the device to recognize each other based on the fleet system. As another example, a jack or gender for recognizing the device may be further included in the mobile to clearly recognize each other between the mobile and the device. In other words, the fleet system may operate based on a separate module for using the shared mobile.

As another example, if a device registered in the fleet system is able to use a mobile through authentication as described above, the mobile needs to be linked with the device. For example, the mobile can detect that the device is within a certain distance of the mobile. At this time, if the device is within a certain distance of the mobile, the mobile can provide the device with information on whether to use it through a notification. In addition, the mobile can communicate with the fleet system when the device is located within a certain distance, and can automatically open the door by confirming this. As another example, existing mobiles could be managed and secured through a mobile key. On the other hand, in the case of a shared mobile, since the mobile user may change each time, it cannot be operated based on a certain key. In other words, only when the device and the mobile are linked and can perform authentication from the fleet system, the device can be linked with the mobile to control the mobile. Each of the device and the mobile can include an application based on the fleet system. For example, the mobile can include a device that can internally implement an application. As another example, the mobile may be provided as a device for the fleet system through a detachable external device, and is not limited to the above-described embodiment. In this case, as an example, the device and the mobile may each include encryption key information. In this case, the fleet system may exchange the encryption key information included in the device and the mobile so that the mobile control is possible only when authentication is permitted. Meanwhile, when the device uses the mobile, it is necessary to prevent access to other devices. This can prevent accidents that occur when the devices collide. In this case, as an example, when authentication is performed for the mobile and the device, the device may be used in a form attached to the mobile. For example, when the devices are adjacent based on the fleet system, the mobile door may be opened. However, in order to secure stability in the fleet system, the device may be set to have control authority over the mobile only when mutual interoperation is performed while the device is attached to the shared mobile. That is, opening the door of a mobile device may have a relatively low security level, but considering that the device controls a shared mobile device, there is a need to set the security level high.

As another example, the fleet system can provide a service for sharing a mobile device through communication with the RSU as a surrounding infrastructure. As an example, parking for a mobile device registered as a shared mobile device in the fleet system can be limited to a certain point. As an example, the fleet system can create a group based on a certain area and register multiple mobile devices in the group to provide a shared mobile device service. At this time, as an example, the shared mobile device can be parked only at a certain point in an area corresponding to the group. That is, the fleet system can perform parking management for the shared mobile device and perform management for location tracking. At this time, the fleet system can manage all mobile devices by checking only the mobile devices parked at a certain point and the mobile devices being used by the device. That is, the fleet system can efficiently perform mobile distribution by checking the certain point and the used mobile devices. Meanwhile, as an example, if the fleet system cannot efficiently perform mobile distribution based on the above-described management method, the fleet system can provide a command to forcibly perform mobile movement through the manager, and the system can operate smoothly based on this.

As another example, the fleet system can perform management of vehicles using autonomous driving and existing vehicles, and provide vehicle sharing services based on this. In other words, the fleet system can provide vehicle sharing services based on the functions provided to each vehicle as a legacy vehicle and a current vehicle.

More specifically, vehicles shared through a fleet system can provide the same functions based on the same model and the same type of aircraft. As another example, vehicles shared through a fleet system can provide different functions as different models.

First, the vehicles shared through the fleet system can provide the same function based on the same model and the same type of aircraft. For example, the function can be an autonomous driving level. At this time, the autonomous driving level is autonomous driving information, and the autonomous driving function provided for each level may be different, and is not limited to the above-described embodiment. In the above-described situation, the fleet system can grant all functions provided by the vehicle to the device using the vehicle. In addition, as an example, the fleet system can grant only some functions provided by the vehicle to the device using the vehicle. At this time, the user corresponding to each device may have different proficiency in handling the vehicle, and the fleet system can provide functions for the vehicle based on the user information corresponding to the device in consideration of accident prevention and safety. That is, if it is determined that all vehicle functions are available based on the user information, the fleet system can grant all functions to the device. On the other hand, if the fleet system determines that all vehicle functions are not available based on the user information (e.g. driving experience, autonomous driving function use experience, etc.), the fleet system can grant only some functions to the device to prevent accidents.

Meanwhile, for example, if the fleet system provides shared vehicles with different functions, the fleet system can provide additional information on the function of the vehicle for the vehicle used by the device. More specifically, in order to prevent accidents that may occur due to the user corresponding to the device not being properly familiar with the function of the vehicle, the fleet system can provide information about the vehicle to the device in advance. Through this, the fleet system can prevent accidents related to the shared vehicle.

FIG. 9 is a diagram showing the configuration of a first device (1100) and a second device (1200). Referring to FIG. 9, the first device (1100) and the second device (1200) may each be a device performing communication. For example, the first device (1100) and the second device (1200) may include at least one of the above-described devices, mobile devices, fleet systems (or servers), and RSUs.

That is, the first device (1100) and the second device (1200) may be devices that perform communication with each other. At this time, as an example, the first device (1100) and the second device (1200) may include a processor (1110, 1120) and a transceiver (1210, 1220) for the above-described operation. That is, the first device (1100) and the second device (1200) may include a processor for controlling the communication operation and the related operation. In addition, the first device (1100) and the second device (1200) may include a transceiver in consideration of the operation as described above, and may perform the above-described operations.

Although the exemplary methods of the present disclosure described above are expressed as a series of operations for clarity of explanation, this is not intended to limit the order in which the steps are performed, and each step may be performed simultaneously or in a different order, if necessary. In order to implement the method according to the present disclosure, additional steps may be included in the exemplary steps, or some of the steps may be excluded and the remaining steps may be included, or some of the steps may be excluded and additional other steps may be included.

The various embodiments of the present disclosure are not intended to list all possible combinations but rather to illustrate representative aspects of the present disclosure, and the matters described in the various embodiments may be applied independently or in combinations of two or more.

Additionally, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. In the case of hardware implementation, the embodiments may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), general processors, controllers, microcontrollers, microprocessors, etc.

The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and being executable on the device or the computer.

First device: 1100 Processor: 1110
Transmitter and receiver: 1120 Second device: 1200
Processor: 1210 Transmitter/Receiver: 1220

Claims (35)

A method for providing a mobile sharing service in a fleet system,
A step for performing authentication for a first device to receive the mobile sharing service provided through the fleet system, wherein the first device is a tenant device; and
Including a step in which the mobile body is controlled based on the first device when the above authentication is completed;
The first device includes tenant setting information for the user of the first device,
The above mobile device is a mobile device registered in the fleet system based on a second device, wherein the second device is an owner device;
The above mobile device changes the mobile device status information set by the owner information prior to providing the shared service to the above tenant setting information based on the above tenant setting information.
The above fleet system provides the mobile sharing service for the mobile based on the sharing conditions set through the second device,
If the mobile is a first type mobile, the mobile changes the mobile status information based on the tenant setting information provided by the first device, but if the first device completes use of the mobile, the mobile status information is automatically returned to the owner information.
A method for providing a mobile sharing service, wherein, if the mobile is a second type mobile that does not support a change in the mobile status that is allowable by the setting information, the mobile only provides usage rights to the first device and does not support a change in the mobile status information based on the tenant setting information.
In paragraph 1,
A method for providing a mobile sharing service, wherein the above sharing conditions are set based on at least one of the usage time information of the mobile device, the movable area information, the departure point information, and the destination information.
In the second paragraph,
A method for providing a mobile sharing service, wherein when the first device uses the mobile sharing service through the fleet system, the first device transmits departure information, destination information, and mobile usage time information for mobile usage to the fleet system.
In the third paragraph,
A method for providing a mobile sharing service, wherein the fleet system provides the mobile device to the first device for the mobile sharing service if the information transmitted by the first device satisfies the sharing condition.
In paragraph 1,
A method for providing a vehicle sharing service, wherein the above-mentioned vehicle status information includes at least one of a driver's seat position, a driver's seat height, an interior lighting color, an interior lighting brightness, a rearview mirror position, a rearview mirror angle, a side mirror position, a side mirror angle, an interior temperature, a steering wheel angle, a tire pressure, an autonomous driving function setting variable, a transmission setting mode, an instrument panel mode, a navigation setting, a content setting, and a wireless communication connection mode.
In paragraph 1,
A method for providing a mobile sharing service, wherein when the mobile is controlled by the first device, operation information about the mobile is provided to the first device.
In paragraph 6,
A method for providing a mobile sharing service, wherein the first device updates the setting information for the user based on the operation information.
In paragraph 7,
A method for providing a mobile sharing service, wherein the above operation information is reflected and updated in the above setting information for the user based on machine learning or a learning method.
In paragraph 1,
A method for providing a mobile sharing service, wherein after the above authentication is completed, the first device detects that the mobile is located within a preset distance from the mobile, and when the identification of the mobile is completed, the mobile changes the mobile status information based on the setting information provided by the first device.
delete delete In paragraph 1,
A method for providing a mobile sharing service, wherein history information on the use of the mobile is stored when the mobile is controlled by the first device.
In Article 12,
A method for providing a mobility sharing service, wherein the above history information includes at least one of usage history information, driving pattern information, personal tendency information, and driving tendency information.
In Article 13,
A method for providing a mobile sharing service, wherein when the first device reuses the mobile device, the mobile device is controlled based on the stored history information.
In paragraph 1,
A method for providing a mobile sharing service, wherein the mobile status information of the mobile is changed at the point in time when the first device completes authentication for the mobile.
In Article 15,
A method for providing a mobile sharing service, wherein when the first device completes use of the mobile, the first device provides information about the completion of use to the mobile, and authentication is terminated based on the information about the completion of use.
In Article 16,
A method for providing a mobile sharing service, wherein the mobile status information of the mobile device is changed based on the setting information set in the second device at the time the authentication is terminated.
In Article 16,
A method for providing a mobile sharing service, wherein when the above authentication is terminated and the second device completes authentication with the mobile, the mobile status information of the mobile is changed based on the setting information set in the second device.
In paragraph 1,
A method for providing a mobile sharing service, wherein the mobile is controlled by the first device when the first device is attached to the mobile after completing authentication with the mobile.
In Article 19,
A method for providing a mobile sharing service, wherein the mobile includes a cradle to which a device is coupled, and the first device is mounted based on the cradle.
For a mobile device that provides a mobile sharing service in a fleet system,
A transceiver that transmits and receives signals;
Including a processor that controls the above transceiver,
The above processor,
Transmitting authentication information for providing the mobile sharing service to the first device based on the above fleet system, wherein the first device is a tenant device;
If authentication between the mobile device and the first device is completed based on the above authentication information, the mobile device is controlled based on the first device.
The first device includes tenant setting information for the user of the first device,
The above mobile device is a mobile device registered in the fleet system based on a second device, wherein the second device is an owner device;
The above mobile device changes the mobile device status information set by the owner information prior to providing the shared service to the above tenant setting information based on the above tenant setting information.
The above fleet system provides the mobile sharing service for the mobile based on the sharing conditions set through the second device,
If the mobile is a first type mobile, the mobile changes the mobile status information based on the tenant setting information provided by the first device, but if the first device completes use of the mobile, the mobile status information is automatically returned to the owner information.
A mobile device that provides only usage rights to the first device and does not support changes in the mobile device status information based on the tenant setting information, if the mobile device is a second type mobile device that does not support changes in the mobile device status information based on the tenant setting information.
In Article 21,
A mobile device in which the above sharing conditions are set based on at least one of the usage time information, movable area information, departure information, and destination information of the mobile device.
In paragraph 22,
A mobile device that, when the first device uses the mobile sharing service through the fleet system, transmits departure information, destination information, and mobile device use time information for mobile device use to the fleet system.
In paragraph 23,
A mobile device, wherein the fleet system provides the mobile device to the first device for the mobile device sharing service if the information transmitted by the first device satisfies the sharing condition.
In Article 21,
The above moving object status information includes at least one of a driver's seat position, a driver's seat height, an interior lighting color, an interior lighting brightness, a rearview mirror position, a rearview mirror angle, a side mirror position, a side mirror angle, an interior temperature, a steering wheel angle, a tire pressure, an autonomous driving function setting variable, a transmission setting mode, an instrument panel mode, a navigation setting, a content setting, and a wireless communication connection mode.
In Article 21,
A mobile body, wherein when the mobile body is controlled by the first device, operation information about the mobile body is provided to the first device.
In Article 26,
A mobile device, wherein the first device updates the setting information for the user based on the operation information.
In Article 27,
A mobile device in which the above operation information is reflected and updated in the above setting information for the user based on machine learning or a learning method.
delete delete In a fleet system that provides a mobile sharing service,
A plurality of devices registered in the above fleet system; and
A plurality of mobile units registered in the above fleet system; including:
A first device among the plurality of devices performs authentication to receive the mobile sharing service as a first device among the plurality of mobile devices provided through the fleet system, wherein the first device is a tenant device.
When the above authentication is completed, the first mobile body is controlled based on the first device,
The first device includes tenant setting information for the user of the first device,
The first mobile device is a mobile device registered in the fleet system based on the second device, wherein the second device is an owner device;
The above first mobile device changes the mobile device status information set by the owner information prior to providing the shared service to the tenant setting information based on the tenant setting information.
The above fleet system provides a mobile sharing service, which provides the mobile sharing service to the first mobile device based on the sharing conditions set through the second device,
If the first mobile is a first type mobile, the first mobile changes the mobile status information based on the tenant setting information provided by the first device, and if the first device completes use of the first mobile, automatically returns the mobile status information to the owner information.
A fleet system in which the first mobile device is a second type mobile device that does not support a change in the mobile device status that is allowable by the setting information, and the first mobile device only provides usage rights to the first device and does not support a change in the mobile device status information based on the tenant setting information.
In paragraph 31,
A fleet system that provides a mobile sharing service, in which the plurality of devices and the plurality of mobiles registered in the fleet system maintain a state of mutual connection based on a network.
In paragraph 32,
A fleet system that provides a mobile sharing service, which maintains a mutual connection state based on the network for the devices and mobiles included in the same group among the plurality of devices and the plurality of mobiles registered in the fleet system.
For a mobile device that provides a mobile sharing service in a fleet system,
A transceiver that transmits and receives signals;
Including a processor that controls the above transceiver,
The above processor,
Transmitting authentication information for providing the mobile sharing service to a device based on the above fleet system, wherein the device is a tenant device storing tenant setting information;
If authentication between the mobile body and the device is completed based on the above authentication information, the mobile body is controlled based on the device.
The above mobile device is a mobile device registered in the fleet system, and the mobile device changes the mobile device status information set by the owner information prior to providing the shared service to the tenant setting information based on the tenant setting information provided by the device.
The above fleet system provides the mobile sharing service for the mobile based on the above authentication result,
The above mobile device changes the mobile device status information based on the user setting information included in the device,
If the mobile is a first type mobile, the mobile changes the mobile status information based on the setting information provided by the device, but if the device completes use of the mobile, the mobile status information is automatically returned to the owner information.
A mobile device that provides only usage rights to the device and does not support changes in the mobile device status information based on the tenant setting information, if the mobile device is a second type mobile device that does not support changes in the mobile device status information that are allowable by the setting information.
In a fleet system that provides a mobile sharing service,
A plurality of devices registered in the above fleet system; and
A plurality of mobile units registered in the above fleet system; including:
A first device among the plurality of devices performs authentication to receive the mobile sharing service as a first device among the plurality of mobile devices provided through the fleet system, wherein the first device is a tenant device storing tenant setting information.
When the above authentication is completed, the first mobile body is controlled based on the first device,
The first mobile device is a mobile device registered in the fleet system based on the second device, wherein the second device is an owner device;
The above fleet system provides a mobile sharing service, which provides the mobile sharing service to the mobile based on the sharing conditions set through the second device,
The first mobile device changes the mobile device status information set by the owner information prior to providing the shared service to the tenant setting information based on the tenant setting information for the user included in the first device.
If the first mobile is a first type mobile, the first mobile changes the mobile status information based on the tenant setting information provided by the first device, and if the first device completes use of the first mobile, automatically returns the mobile status information to the owner information.
A fleet system in which the first mobile device is a second type mobile device that does not support a change in the mobile device status that is allowable by the setting information, and the first mobile device only provides usage rights to the first device and does not support a change in the mobile device status information based on the tenant setting information.

Images