KR102439632B1 - Apparatus and method for providing transfer service related to shared mobility - Google Patents

Abstract

An apparatus and method for providing a transfer service linked to shared mobility are disclosed. The method for providing a transfer service linked to shared mobility according to an embodiment of the present application may include the steps of: receiving and processing a rental request including user identification information and identification information of shared mobility that a user intends to board; receiving and processing a return request including the user identification information and a public transportation usage history of the user; determining whether to apply transfer between the shared mobility and the public transportation based on the public transportation usage history; and generating reward information based on whether to apply the transfer.

Description

Apparatus and method for providing transfer service related to shared mobility

The present application relates to an apparatus and method for providing a transfer service associated with shared mobility.

Since the concept of the sharing economy emerged, sharing issues have been actively discussed throughout society, including accommodation, space, and finance.

Shared transportation includes not only various types of sharing services such as car-sharing, which shares vehicles, and ride-sharing, which is a concept of ride-sharing that shares vehicles and drivers, but also individual means of transportation (bicycles). , electric kickboard, etc.) sharing services for various means of transportation are being operated.

By means of transportation, if divided into the automobile sector and the non-vehicle sector, car sharing services are representative in the automobile sector. Bicycles can be divided into public bicycles, local shared services, and P2P services depending on the type of service. is operating. On the other hand, electric kickboards and electric scooters are mostly operated in a non-standing type, and in particular, the use of non-detachable electric scooters is active in Korea.

On the other hand, as described above, various problems occur with the diversification and increase in use of shared transportation services, and integrated operation of car sharing or public transportation use and personal transportation sharing service with different operational and usage characteristics and problems. The development of a platform that can do this is required.

The technology that is the background of the present application is disclosed in Korean Patent Application Laid-Open No. 10-2020-0111932.

The present application is to solve the problems of the prior art described above, and when providing a shared mobility service (Mobility as a Service, MaaS), it is determined whether the transfer between the shared transportation means and public transportation is applied according to the user's use of public transportation. An object of the present invention is to provide an apparatus and method for providing a transfer service linked to shared mobility that pays a user a reward.

However, the technical problems to be achieved by the embodiments of the present application are not limited to the technical problems as described above, and other technical problems may exist.

As a technical means for achieving the above technical problem, the method of providing a transfer service associated with shared mobility according to the first embodiment of the present application includes a rental including user identification information and identification information of a shared mobility that the user intends to board Receiving and processing a request, receiving and processing a return request including the user identification information and the user's public transportation usage history, based on the public transportation usage history, whether the shared mobility and public transportation transfer are applied and generating reward information based on whether the transfer is applied or not.

In addition, the method of providing a transfer service associated with shared mobility according to the first embodiment of the present application includes the steps of transmitting a payment request to a settlement operator server based on fare information corresponding to the return request and from the settlement operator server It may include receiving a processing result corresponding to the payment request.

In addition, the step of receiving and processing the return request may include receiving the public transport usage history collected through interworking between a public transport-related application pre-installed on the user terminal of the user and a shared mobility-related application.

In addition, the step of receiving and processing the return request may include receiving the payment details of the USIM-based transportation card mounted on the user terminal of the user as the public transportation usage details.

In addition, the step of receiving and processing the return request may include receiving the public transportation usage details of the user corresponding to the user identification information from the settlement service provider server.

In addition, the method of providing a transfer service associated with shared mobility according to the first embodiment of the present application includes transmitting an unlock control signal to a mobility terminal in response to the rental request and to the mobility terminal in response to the return request and transmitting a lock control signal.

In addition, in the method of providing a transfer service associated with shared mobility according to the first embodiment of the present application, if the user uses public transportation after the return request is received, public transportation updated after the user gets off the public transportation Obtaining a usage history, determining whether to apply the transfer of the shared mobility and public transportation based on the updated public transportation usage history, and updating the reward information based on whether the transfer is applied can

On the other hand, the method of providing a transfer service in connection with shared mobility according to the second embodiment of the present application includes the steps of obtaining a user's public transportation usage history, the public transportation usage history and the previously secured shared mobility usage history of the user Determining whether or not to apply the transfer of the shared mobility and public transportation based on , and generating reward information based on whether the transfer is applied.

On the other hand, the method of providing a transfer service associated with shared mobility according to the third embodiment of the present application includes the steps of collecting the user's shared mobility usage history, the user's public transportation usage history for a preset period from the settlement service provider server It may include receiving transfer information according to the and generating reward information based on the shared mobility usage history and the transfer information.

In addition, the method of providing a transfer service associated with shared mobility according to a fourth embodiment of the present application includes the steps of receiving and processing a rental request including user identification information and identification information of the shared mobility that the user intends to board, the user Receiving and processing a return request including identification information, transmitting a payment request to a settlement operator server based on fee information corresponding to the return request, and receiving a processing result corresponding to the payment request, the settlement The method may include receiving transfer information according to the user's public transportation usage history for a preset period from the operator server and generating reward information based on the transfer information.

On the other hand, the apparatus for providing a transfer service associated with shared mobility according to the first embodiment of the present application includes a rental processing unit that receives and processes a rental request including user identification information and identification information of the shared mobility that the user intends to board, the A return processing unit that receives and processes a return request including user identification information and user's public transportation usage history and determines whether to apply the transfer between the shared mobility and public transportation based on the public transportation usage history, and whether the transfer is applied It may include a reward generator for generating reward information based on the.

In addition, the apparatus for providing a transfer service associated with shared mobility according to the first embodiment of the present application transmits a payment request to a settlement service provider server based on fare information corresponding to the return request, and the payment from the settlement service provider server It may include a settlement unit for receiving a processing result corresponding to the request.

In addition, in the apparatus for providing a transfer service associated with shared mobility according to the first embodiment of the present application, if the user uses public transportation after the return request is received, public transportation updated after the user gets off the public transportation It may include a collection unit for obtaining the usage history.

In addition, the reward generating unit may determine whether to apply the transfer between the shared mobility and public transportation based on the updated public transportation usage history, and update the reward information based on whether the transfer is applied.

On the other hand, the apparatus for providing a transfer service in connection with shared mobility according to the second embodiment of the present application includes a collection unit for obtaining a user's public transportation usage history, the public transportation usage history, and the previously secured shared mobility use of the user It may include a reward generator that determines whether to apply the transfer of the shared mobility and public transportation based on the details, and generates reward information based on whether the transfer is applied.

On the other hand, the apparatus for providing a transfer service associated with shared mobility according to the third embodiment of the present application includes a first collection unit that collects user's shared mobility usage history, and the public of the user for a preset period from the settlement operator server. It may include a second collection unit for receiving transfer information according to the traffic usage history, and a reward generator for generating reward information based on the shared mobility use history and the transfer information.

In addition, the apparatus for providing a transfer service associated with shared mobility according to the fourth embodiment of the present application includes a rental processing unit that receives and processes a rental request including user identification information and identification information of the shared mobility that the user intends to board, the above A return processing unit that receives and processes a return request including user identification information, a settlement unit that transmits a payment request to a settlement operator server based on fee information corresponding to the return request, and receives a processing result corresponding to the payment request and a reward generator configured to receive transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server, and generate reward information based on the transfer information.

The above-described problem solving means are merely exemplary, and should not be construed as limiting the present application. In addition to the exemplary embodiments described above, additional embodiments may exist in the drawings and detailed description.

According to the above-described problem solving means of the present application, when providing a shared transportation service (MaaS), a shared type that pays a reward to a user by determining whether to apply a transfer between a shared transportation means and public transportation depending on whether the user uses public transportation An apparatus and method for providing a transfer service related to mobility may be provided.

According to the above-described problem solving means of the present application, it is possible to induce the use of shared transportation service (MaaS) and public transportation by reducing the user's fee burden.

According to the above-described problem solving means of the present application, it can contribute to solving the blind spots of public transportation by providing a shared transportation service in connection with public transportation even in an area where a public transportation network is relatively not equipped.

However, the effects obtainable herein are not limited to the above-described effects, and other effects may exist.

1 is a schematic configuration diagram of a transfer system including an apparatus for providing a transfer service associated with shared mobility according to an embodiment of the present application.
2 is a schematic configuration diagram of an apparatus for providing a transfer service associated with shared mobility according to an embodiment of the present application.
3A and 3B are operational flowcharts for a method of providing a transfer service associated with shared mobility according to an embodiment of the present application.
4A and 4B are operational flowcharts for a method of providing a transfer service associated with shared mobility according to another embodiment of the present application.

Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings so that those of ordinary skill in the art to which the present application pertains can easily implement them. However, the present application may be implemented in several different forms and is not limited to the embodiments described herein. And in order to clearly explain the present application in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout this specification, when a part is said to be “connected” to another part, it is not only “directly connected” but also “electrically connected” or “indirectly connected” with another element interposed therebetween. "Including cases where

Throughout this specification, when it is said that a member is positioned "on", "on", "on", "under", "under", or "under" another member, this means that a member is located on the other member. It includes not only the case where they are in contact, but also the case where another member exists between two members.

Throughout this specification, when a part "includes" a component, it means that other components may be further included, rather than excluding other components, unless otherwise stated.

The present application relates to an apparatus and method for providing a transfer service associated with shared mobility.

1 is a schematic configuration diagram of a transfer system including an apparatus for providing a transfer service associated with shared mobility according to an embodiment of the present application.

Referring to FIG. 1 , a transfer system 10 according to an embodiment of the present application is a transfer service providing apparatus 100 (hereinafter, 'service providing apparatus 100') associated with shared mobility according to an embodiment of the present application. ), a mobility terminal 200 , a settlement service provider server 300 , a user terminal 30 , and a public transportation payment terminal 500 . Meanwhile, in the description of the embodiment of the present application, the service providing apparatus 100 may be referred to as a service providing server or the like.

Also, referring to FIG. 1 , the user terminal 30 is a device possessed by a user using target mobility, and various mobile applications 400 may be installed in the user terminal 30 in the description of the embodiment of the present application. For example, the mobile application 400 may be a concept encompassing public transportation-related applications, shared mobility-related applications, and the like.

On the other hand, the shared mobility-related mobile application 400 disclosed herein may be operated by the same business entity as the service providing device 100 and interoperate, but is not limited thereto.

In addition, according to an embodiment of the present application, the user terminal 30 has a USIM-based transportation card 31 that can be used to pay the user's public transportation usage fee and further collect the user's public transportation usage history. can be mounted.

The service providing device 100 , the mobility terminal 200 , the settlement service provider server 300 , the user terminal 30 , and the public transportation payment terminal 500 may communicate with each other through the network 20 . The network 20 means a connection structure capable of exchanging information between each node, such as terminals and servers, and an example of such a network 20 includes a 3rd Generation Partnership Project (3GPP) network, a long-term LTE (LTE) network. Term Evolution) network, 5G network, WIMAX (World Interoperability for Microwave Access) network, Internet, LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area) Network), wifi network, Bluetooth (Bluetooth) network, satellite broadcasting network, analog broadcasting network, DMB (Digital Multimedia Broadcasting) network, RFID method, NFC method, etc. are included, but are not limited thereto.

The user terminal 30 is, for example, a smartphone (Smartphone), a smart pad (SmartPad), a tablet PC and the like and PCS (Personal Communication System), GSM (Global System for Mobile communication), PDC (Personal Digital Cellular), PHS ( Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), Wibro (Wireless Broadband Internet) terminals The same may be any type of wireless communication device.

In the description of the embodiment of the present application, the mobility terminal 200 is a device mounted on shared mobility such as target mobility for driving shared mobility, and a user terminal ( 30), when the tagging process through the reading means (eg, QR code, etc.) and the user terminal 30 is normally completed, unlock the driving of the mobility so that the user can operate the corresponding mobility Alternatively, a lock control means for applying or maintaining a lock on the driving of the mobility to prevent a user's manipulation of the corresponding mobility when the use of the mobility is terminated or the tagging process is not normally completed may be provided.

On the other hand, below, the embodiment of the present application will be described on the assumption that the shared mobility is a shared type electric kickboard, but the type of transportation means of the shared mobility is not limited thereto, and a bicycle, an electric bicycle, an electric scooter, a Segway, etc. Of course, it can be applied in various types.

In addition, in the description of the embodiment of the present application, the mobility terminal 200 provides mobility identification information, user identification information of a user using the corresponding mobility, and unlock command through communication based on the service providing device 100 and the network 20 . , and various data such as lock commands can be exchanged.

In addition, in the description of the embodiment of the present application, the settlement operator server 300 may be a server operated by a business operator that performs payment for a usage fee according to a user's use of public transportation. Illustratively, the settlement operator server 300 may be a transportation card operator server. In this regard, the service providing device 100 disclosed herein provides the settlement service provider server 300 and various information related to mobility use so that the user's target mobility usage fee can be integrated with the public transport usage fee and paid. can be exchanged

In addition, according to the embodiment of the present application, the settlement service provider server 300 may be extended to a subject that performs a function of processing payment for a user's shared mobility use (rental) fee as well as public transportation usage fee.

Hereinafter, a specific embodiment of the present application in connection with a transfer service associated with shared mobility provided by the service providing apparatus 100 will be described in detail.

According to the first embodiment of the present application, the service providing apparatus 100 may receive and process a rental request including user identification information and identification information of a shared mobility that the user intends to board.

In this regard, the user who wants to use (rent) the target mobility tags the user terminal 30 possessed by the mobility terminal 200 of the target mobility, and accordingly, the mobility identification information of the target mobility is transmitted to the user terminal 30. can

In this regard, the service providing apparatus 100 provides user identification information (eg, a mobile communication number of the user terminal 30, shared mobility) from at least one of the user terminal 30 and the mobility terminal 200 of the target mobility. Receiving a rental request including the related mobile application 400 account information, etc.) and mobility identification information of the target mobility that the user intends to board (drive) (eg, serial number, code, etc. assigned to the target mobility) can

Also, the service providing apparatus 100 may verify the validity of the user identification information and the mobility identification information in response to the received rental request, and may transmit a mobility unlock command to the mobility terminal 200 of the target mobility. Here, the mobility unlock command is a state that has not been previously occupied by the user, and the user who sent the rental request can operate the target mobility that has been placed in a locked state where user manipulation (eg, acceleration manipulation, etc.) is not possible. It may mean a command for transitioning to a state.

Also, the service providing apparatus 100 may receive the unlock result corresponding to the unlock command from the mobility terminal 200 of the target mobility, and store the mobility usage history of the corresponding user.

In addition, according to the first embodiment of the present application, the service providing apparatus 100 may receive and process a return request including user identification information and the user's public transportation usage history. In addition, according to the embodiment of the present application, the return request may further include mobility identification information of the target mobility rented by the user.

In this regard, when the user terminal 30 is tagged as the mobility terminal 200 of the target mobility so that the user who has finished driving through the target mobility ends the rental of the target mobility, the user terminal 30 from the corresponding mobility terminal 200 ), the mobility identification information may be transmitted through the mobile application 400 .

In addition, the shared mobility-related mobile application 400 installed in the user terminal 30 may collect the user's public transportation usage history and transmit a return request including the public transportation usage history to the service providing device 100 . More specifically, the user's public transportation usage history included in the return request may mean the user's public transportation boarding and alighting history prior to renting the corresponding target mobility.

In this regard, according to an embodiment of the present application, the service providing apparatus 100 collects data collected through interworking between a public transportation-related application (not shown) previously installed in the user terminal 30 and the shared mobility-related application 400 . The user's public transportation usage history may be received from the user terminal 30 .

In addition, according to another embodiment of the present application, the service providing apparatus 100 is to receive the payment details of the USIM-based transportation card 31 mounted on the user terminal 30 from the user terminal 30 as public transportation usage details. can

As another example, the service providing device 100 is the user's public transportation corresponding to the user identification information of the user from the settlement operator server 300 that performs the payment relay process of the user's public transportation usage amount according to the embodiment of the present application It may be to receive usage history.

In addition, the service providing apparatus 100 may transmit a payment request to the settlement service provider server 300 based on the fee information corresponding to the return request. In addition, the service providing apparatus 100 may receive a processing result corresponding to the payment request from the settlement operator server 300 .

In other words, when the user terminates the use of the target mobility and transmits a return request, the service providing apparatus 100 may process payment for fee information according to the user's use of the target mobility with the settlement service provider server 300 . . Here, the fee information according to the use of the target mobility is the fee for the exclusive use of the target mobility separately from the application of a reward depending on whether the user uses public transportation, which will be described later (for example, the fee determined according to the rental time of the target mobility, the target It may mean a fee determined according to the moving distance of mobility, etc.).

In addition, according to the first embodiment of the present application, the service providing apparatus 100 may determine whether to apply the transfer of shared mobility and public transportation based on the public transportation usage details included in the return request (shared after getting off the public transportation) Transfer judgment based on type mobility boarding).

Illustratively, the service providing device 100 includes a departure time of public transportation (eg, subway, bus, tram, taxi, etc.) included in the public transportation usage history collected for the user and the rental time of the target mobility ( For example, the time between when a rental request is received from the user terminal 30 , when tagging of the mobility terminal 200 is made through the shared-type mobility-related application 400 of the user terminal 30 , etc.) If the interval is within a preset transfer application period, the service providing apparatus 100 may determine that the transfer between the target mobility and the public transportation used by the user before the target mobility is driven has been made.

Also, according to the first embodiment of the present application, the service providing apparatus 100 may generate reward information to be paid to the user based on the determined transfer application. In this regard, 'reward information' disclosed herein is information related to the content of benefits paid to the user when it is determined that the transfer between the public transportation used by the user and the target mobility is applied, and the public transportation fee according to the embodiment of the present application Or it may be a concept that broadly includes discounts on shared mobility usage fees, usage fee refunds, accumulated points, mileage, and the like.

For reference, according to the first embodiment of the present application, the service providing apparatus 100 is configured when there is no public transportation usage history to which the shared mobility and transfer used by the user are applied based on the return request (eg, the user is last In the case of tagging the mobility terminal 200 for rental for shared mobility after the preset transfer application period has elapsed from the time of performing the alighting process through the public transportation payment terminal 500, etc.), reward information can be uncreated.

For example, when it is determined that the transfer between public transportation-shared mobility is applied, the service providing apparatus 100 determines the amount of points to be paid to the user, and uses the determined amount of points as reward information to the user terminal 30 as reward information. can be transmitted

Here, the service providing apparatus 100 specifically determines the number of points to be included in the reward information in consideration of the number of transfer applications between the user's public transportation-shared mobility, the total distance traveled, the public transportation fee, the driving pattern of the target mobility, etc. can

On the other hand, according to an embodiment of the present application, the service providing apparatus 100 selectively selects whether or not to pay a reward according to transfer application or a payment level (amount) according to whether the return place of the target mobility corresponds to a preset designated return place. By making a decision, users who want to receive benefits from the application of the shared mobility-public transportation transfer are encouraged to return the target mobility at a preset designated return location, thereby preventing the shared mobility from being indiscriminately neglected on the road or sidewalk. have.

In addition, according to an embodiment of the present application, the service providing device 100 applies a transfer if there is a history of non-compliance with traffic laws (eg, whether crossing signals are complied with, whether complied with speed limits, etc.) in the course of the target mobility driving process. It is possible to induce the user to drive the target mobility while complying with traffic laws or safety requirements by not paying a reward according to the

Illustratively, assuming that the reward is in the form of points accumulated according to the application of public transportation-sharing mobility transfer of use, the service providing apparatus 100 is credited in response to a point use request received from the user terminal 30 . Point-based payment for shared mobility usage fee while deducting the accumulated points, extending the transfer application period, which is the temporal range for determining the transfer application of shared mobility and public transportation, shared mobility-related products (e.g. helmets, protective gear) etc.) may provide benefits such as exchange.

In addition, according to the first embodiment of the present application, if the user uses public transportation after the return request is received, the service providing apparatus 100 may obtain an updated public transportation usage history after the user gets off the public transportation. .

For example, as described above, the acquisition process of the updated public transportation usage history is a collection method through interworking between public transportation-related applications and shared mobility-related applications, a method of receiving payment details of the USIM-based transportation card 31, a settlement operator A method of receiving a user's public transportation usage history corresponding to user identification information from the server 300 may be commonly applied.

In addition, according to the first embodiment of the present application, the service providing apparatus 100 may determine whether to apply the transfer between the shared mobility and public transportation based on the updated public transportation usage history (getting off the shared mobility and then boarding the public transportation) transfer judgment).

In addition, according to the first embodiment of the present application, the service providing apparatus 100 may update the reward information based on the determined transfer application. Illustratively, the update of reward information is applied multiple times of transfer application (for example, after the user uses the first public transportation, rents the shared mobility within the transfer application period, and after returning the shared mobility, the second public transportation is similarly used It may refer to a process of determining a discount on usage fees, additional points accumulation, etc. according to the case of getting on and off within the transfer application period, etc.).

In summary, the service providing device 100 obtains the user's public transportation usage history, and whether the transfer of shared mobility and public transportation is applied based on the acquired public transportation usage history and the previously secured user's shared mobility usage history may be determined to generate and provide reward information for the corresponding user. Meanwhile, in the case of shared mobility usage history, it may be information accumulated and stored (recorded) for each user in a database (not shown) interworking with the service providing apparatus 100 .

Hereinafter, a second embodiment of the present application will be described.

According to the second embodiment of the present application, the service providing apparatus 100 independently performs (relay) a payment process for a usage fee according to shared mobility use and a payment process for a usage fee according to the user's use of public transportation, respectively (relay) After doing so, it is possible to provide a reward in a post-settlement method through ex post transfer judgment on public transportation usage history and shared mobility usage history.

Specifically, according to the second embodiment of the present application, the service providing apparatus 100 may receive and process a rental request including user identification information and identification information of a shared mobility that the user intends to board. Also, the service providing apparatus 100 may receive and process a return request including user identification information, as in the first embodiment of the present application described in detail above.

In addition, the service providing device 100 transmits a payment request to the settlement operator server 300 based on the fee information corresponding to the return request, and may receive the processing result of the settlement operator server 300 corresponding to the payment request. have.

In addition, according to the second embodiment of the present application, the service providing apparatus 100 may receive transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server 300 . Illustratively, the period at which the service providing device 100 receives the user's transfer information (in other words, the user's public transportation usage history accumulated for a predetermined period) from the settlement service provider server 300 is 1 day, 1 week, etc. can be determined in units of

In this regard, according to an embodiment of the present application, the service providing apparatus 100 includes statistical information on public transportation usage history collected for a specific user, statistical information on mobility usage history, GPS module of the user terminal 30, etc. It may be to vary the length of the preset period, which is the temporal range for receiving (collecting) transfer information for the user, based on daily/weekly statistical information on the moving distance (moving line) collected through have.

In addition, according to the second embodiment of the present application, the service providing apparatus 100 determines whether or not to apply a transfer to the user's public transportation usage history and shared mobility usage history based on the received transfer information to generate reward information. can

More specifically, the service providing device 100 includes the user's shared mobility rental time and return time included in the previously secured shared mobility usage history and the public of the user included in the transfer information received from the settlement operator server 300 . Considering the time interval between boarding time and getting off time, if there is a history of transfer between shared mobility and public transportation within the preset transfer application period, it is determined that the transfer is applicable during the user's journey and responds accordingly reward information (eg, points, mileage, etc.) may be generated.

In summary, the service providing apparatus 100 according to the second embodiment of the present application collects the user's shared mobility usage history, and according to the user's public transportation usage history for a preset period from the settlement operator server 300 By receiving transfer information, it is possible to post-determin whether transfer is applied based on the shared mobility usage history and transfer information, and to generate and provide reward information.

2 is a schematic configuration diagram of an apparatus for providing a transfer service associated with shared mobility according to an embodiment of the present application.

Referring to FIG. 2 , the service providing apparatus 100 may include a rental processing unit 110 , a return processing unit 120 , a reward generation unit 130 , a settlement unit 140 , and a collection unit 150 . Also, the collecting unit 150 may include a first collecting unit 151 and a second collecting unit 152 .

The rental processing unit 110 may receive and process a rental request including user identification information and identification information of a shared mobility that the user intends to board.

The return processing unit 120 may receive and process a return request including user identification information and the user's public transportation usage history.

The collection unit 150 may collect at least one of the user's public transportation usage history and shared mobility usage history.

Specifically, the first collection unit 151 may collect the user's shared mobility usage history. For example, the first collection unit 151 may store (record) the shared mobility usage history for each user in a database (not shown) provided for the service providing apparatus 100 .

In addition, the second collection unit 152 may collect the user's public transportation usage history.

For example, if the user uses public transportation after a return request for shared mobility is received, the second collection unit 152 may obtain an updated public transportation usage history after the user gets off the public transportation.

As another example, the second collection unit 152 may collect public transportation usage history in a manner that receives transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server 300 .

The reward generating unit 130 may determine whether to apply the transfer of shared mobility and public transportation based on the user's public transportation usage history.

Also, the reward generating unit 130 may generate reward information for the user based on the determined transfer application.

As another example, the reward generating unit 130 may generate reward information based on the shared mobility usage history and transfer information received from the settlement service provider server 300 .

The settlement unit 140 may transmit a payment request to the settlement service provider server 300 based on the fee information corresponding to the received return request.

Also, the settlement unit 140 may receive a processing result corresponding to the payment request from the settlement service provider server 300 .

Hereinafter, based on the details described above, the operation flow of the present application will be briefly reviewed.

3A and 3B are operational flowcharts for a method of providing a transfer service associated with shared mobility according to an embodiment of the present application.

The method of providing a transfer service associated with shared mobility illustrated in FIGS. 3A and 3B may be performed by the service providing apparatus 100 described above. Accordingly, even if omitted below, the description of the service providing apparatus 100 may be equally applied to the description of the method of providing a transfer service associated with shared mobility.

Referring to FIG. 3A , in step S101, through the shared mobility-related mobile application 400 installed in the user terminal 30, tagging for the start of rental of the mobility terminal 200 provided in the shared mobility that the user wants to rent is performed. can

Next, the shared mobility-related mobile application 400 installed in the user terminal 30 in step S102 may obtain mobility identification information of the shared mobility from the mobility terminal 200 .

Next, in step S103, the rental processing unit 110 may receive from the user terminal 30 a rental request including user identification information and identification information of the shared mobility that the user intends to board.

Next, in step S104, the rental processing unit 110 may transmit a lock release control signal to the mobility terminal 200 in response to the rental request.

Next, in step S105 , the rental processing unit 110 may receive unlock result information corresponding to the unlock control signal from the mobility terminal 200 .

Next, in step S106, the service providing apparatus 100 may store the user's mobility use history. Specifically, in step S106, the service providing apparatus 100 may generate a usage history including mobility identification information, rental request reception time, user identification information, and the like in a database (not shown).

Next, in step S107 , the rental processing unit 110 may provide a processing result corresponding to the rental request through the shared mobility-related mobile application 400 of the user terminal 30 .

Next, in step S108, through the shared mobility-related mobile application 400 installed in the user terminal 30, tagging for termination of rental of the mobility terminal 200 provided in the shared mobility that the user wants to return after use can be made. have.

Next, in step S109 , the shared mobility-related mobile application 400 installed in the user terminal 30 may obtain mobility identification information of the shared mobility from the mobility terminal 200 .

Next, the shared mobility-related mobile application 400 installed in the user terminal 30 in step S110 may collect the public transportation usage history of the user.

For example, in step S110, the mobile application 400 may collect public transportation usage history through interworking with a public transportation-related application pre-installed in the user terminal 30 .

As another example, in step S110, the mobile application 400 may receive the payment details of the USIM-based transportation card 31 mounted on the user terminal 30 as the user's public transportation usage details.

As another example, in step S110, the mobile application 400 may receive the user's public transportation usage history corresponding to the user identification information from the settlement service provider server 300.

Next, in step S111, the return processing unit 120 may receive a return request including user identification information and the user's public transportation usage history.

Next, in step S112, the reward generating unit 130 may determine whether to apply the transfer between the shared mobility and public transportation based on the public transportation usage history.

Next, in step S113, the settlement unit 140 may transmit a payment request to the settlement service provider server 300 based on the fee information corresponding to the return request.

Next, in step S114, the settlement unit 140 may receive a processing result corresponding to the payment request (payment success or not) from the settlement operator server 300 .

Next, in step S115, the reward generating unit 130 may transmit the reward information generated based on whether the transfer is applied or not, determined in step S112, to the user terminal 30 through the mobile application 400 or the like.

Also, in step S115 , the service providing apparatus 100 may transmit the payment processing result received from the settlement service provider server 300 to the user terminal 30 .

Next, in step S116 , the return processing unit 120 may transmit a lock control signal to the mobility terminal 200 in response to the return request.

Next, in step S117 , the return processing unit 120 may receive lock result information corresponding to the lock control signal from the mobility terminal 200 .

Referring to FIG. 3B , in step S118 , the public transportation payment terminal 500 may receive boarding tagging information through the public transportation-related mobile application 400 when the user boards public transportation.

Next, in step S119, the public transportation payment terminal 500 may perform the user's ride processing (eg, ride information generation, fare reduction, etc.) based on the ride tagging information.

Next, in step S120, the public transportation payment terminal 500 may receive the getting off tagging information through the public transportation-related mobile application 400 when the user gets off the public transportation.

Next, in step S121, the public transportation payment terminal 500 may perform a user's alighting process (eg, generating alighting information, deducting an additional fee according to alighting, etc.) based on the alighting tagging information.

Next, the mobile application 400 installed in the user terminal 30 in step S122 may receive the user's getting on and off processing result from the public transportation payment terminal 500 .

Next, in step S123, the mobile application 400 may acquire the public transportation usage history updated after the user gets off the public transportation.

Next, in step S124 , the reward generator 130 may receive the user's updated public transportation usage history from the user terminal 30 through the mobile application 400 .

Next, in step S125, the service providing apparatus 100 may store (record) the user's public transportation usage history.

Next, in step S126, the reward generation unit 130 may determine whether to apply the transfer of shared mobility and public transportation based on the updated user's public transportation usage history.

Also, in step S126, the reward generating unit 130 may update the reward information based on whether the transfer determined in step S126 is applied.

Next, in step S127, the service providing apparatus 100 may transmit (provide) the updated reward information to the user terminal 30 through the mobile application 400 or the like.

In the above description, steps S101 to S127 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present application. In addition, some steps may be omitted if necessary, and the order between steps may be changed.

4A and 4B are operational flowcharts for a method of providing a transfer service associated with shared mobility according to another embodiment of the present application.

The method of providing a transfer service associated with shared mobility illustrated in FIGS. 4A and 4B may be performed by the service providing apparatus 100 described above. Accordingly, even if omitted below, the description of the service providing apparatus 100 may be equally applied to the description of the method of providing a transfer service associated with shared mobility.

Referring to FIG. 4A , steps S201 to S205 may be performed to correspond to steps S101 to S105 described above with reference to FIG. 3A . In addition, steps S206 to S208 may be performed to correspond to steps S107 to S109 described above with reference to FIG. 3A .

Next, in step S209, the service providing apparatus 100 may verify the mobility identification information of the shared mobility used by the user.

Next, in step S210, the return processing unit 120 may receive a return request including user identification information and the user's public transportation usage history.

Next, in step S211, the settlement unit 140 may calculate fee information including a usage fee according to the user's shared mobility use.

In addition, in step S211 , the service providing apparatus 100 may store the user's usage history for shared mobility.

Next, in step S212, the settlement unit 140 may transmit a payment request to the settlement service provider server 300 based on the fee information corresponding to the return request.

Next, in step S213 , the settlement unit 140 may receive a processing result corresponding to the payment request from the settlement operator server 300 .

Next, in step S214 , the service providing apparatus 100 may transmit the payment processing result received through the settlement operator server 300 to the user terminal 30 .

Next, in step S215 , the return processing unit 120 may transmit a lock control signal to the mobility terminal 200 in response to the return request.

Next, in step S216 , the return processing unit 120 may receive lock result information corresponding to the lock control signal from the mobility terminal 200 .

Referring to FIG. 4B , in step S217, the reward generating unit 130 may receive transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server.

Next, in step S218, the reward generator 130 may generate reward information based on the transfer information received in step S217.

Next, in step S219, the service providing apparatus 100 may transmit (provide) the generated reward information to the user terminal 30 through the mobile application 400 or the like.

Next, in step S220 , the mobile application 400 may provide (display) the reward information paid to the user in response to a user input for confirming the reward received by the user terminal 30 .

In the above description, steps S201 to S220 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present application. In addition, some steps may be omitted if necessary, and the order between steps may be changed.

The method of providing a transfer service associated with shared mobility according to an embodiment of the present application may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic such as floppy disks. - includes magneto-optical media, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to carry out the operations of the present invention, and vice versa.

In addition, the above-described method for providing a transfer service associated with shared mobility may be implemented in the form of a computer program or application executed by a computer stored in a recording medium.

The foregoing description of the present application is for illustration, and those of ordinary skill in the art to which the present application pertains will understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present application. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and likewise components described as distributed may also be implemented in a combined form.

The scope of the present application is indicated by the following claims rather than the above detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present application.

10: Transfer system
100: Device for providing transfer service linked to shared mobility
110: rental processing unit
120: return processing unit
130: reward generating unit
140: settlement department
150: collection unit
200: mobility terminal
300: settlement operator server
400: mobile application
500: public transportation payment terminal
20: network
30: user terminal

Claims (16)

In the method of providing a transfer service related to shared mobility,
receiving and processing a rental request including user identification information and identification information of a shared mobility that the user intends to board;
receiving and processing a return request including the user identification information and the user's public transportation usage history;
determining whether to apply the transfer between the shared mobility and public transportation based on the public transportation usage history; and
generating reward information based on whether the transfer is applied;
including,
The step of generating the reward information includes:
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of not meeting at least one of whether or not to comply with a crossing signal and whether or not to comply with a speed limit during driving of the shared mobility,
The public transport usage details are accumulated and collected for a preset period, and the preset period is variably applied based on statistical information on the user's movement line collected through a user terminal,
HOW TO PROVIDE SERVICES. According to claim 1,
transmitting a payment request to a settlement service provider server based on the fee information corresponding to the return request; and
receiving a processing result corresponding to the payment request from the settlement service provider server;
Further comprising a, service providing method. According to claim 1,
The step of receiving and processing the return request includes:
The service providing method of receiving the public transportation usage history collected through interworking between a public transportation-related application and a shared mobility-related application previously installed in the user terminal of the user. According to claim 1,
The step of receiving and processing the return request includes:
The service providing method of receiving the payment details of the USIM-based transportation card mounted on the user terminal of the user as the public transportation usage details. 3. The method of claim 2,
The step of receiving and processing the return request includes:
The service providing method of receiving the public transportation usage details of the user corresponding to the user identification information from the settlement service provider server. According to claim 1,
transmitting an unlock control signal to the mobility terminal in response to the rental request; and
transmitting a lock control signal to the mobility terminal in response to the return request;
Further comprising a, service providing method. According to claim 1,
If the user uses public transportation after the return request is received, obtaining an updated public transportation usage history after the user gets off the public transportation;
determining whether to apply the transfer between the shared mobility and public transportation based on the updated public transportation usage history; and
updating the reward information based on whether the transfer is applied;
Further comprising a, service providing method. In the method of providing a transfer service related to shared mobility,
obtaining the user's public transportation usage history;
determining whether to apply the transfer between the shared mobility and public transportation based on the public transportation usage history and the previously secured shared mobility usage history of the user; and
generating reward information based on whether the transfer is applied;
including,
The step of generating the reward information includes:
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of not meeting at least one of whether or not to comply with a crossing signal and whether or not to comply with a speed limit during driving of the shared mobility,
The public transport usage details are accumulated and collected for a preset period, and the preset period is variably applied based on statistical information on the user's movement line collected through a user terminal,
HOW TO PROVIDE SERVICES. In the method of providing a transfer service related to shared mobility,
collecting a user's shared mobility usage history;
Receiving transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server; and
generating reward information based on the shared mobility usage history and the transfer information;
including,
The step of generating the reward information includes:
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of not meeting at least one of whether or not to comply with a crossing signal and whether or not to comply with a speed limit during driving of the shared mobility,
The preset period is to be variably applied based on the statistical information on the movement of the user collected through the user terminal,
HOW TO PROVIDE SERVICES. In the method of providing a transfer service related to shared mobility,
receiving and processing a rental request including user identification information and identification information of a shared mobility that the user intends to board;
receiving and processing a return request including the user identification information;
transmitting a payment request to a settlement service provider server based on the fee information corresponding to the return request, and receiving a processing result corresponding to the payment request;
receiving transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server; and
generating reward information based on the transfer information;
including,
The step of generating the reward information includes:
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of not meeting at least one of whether or not to comply with a crossing signal and whether or not to comply with a speed limit during driving of the shared mobility,
The preset period is to be variably applied based on the statistical information on the movement of the user collected through the user terminal,
HOW TO PROVIDE SERVICES. In the transfer service providing device linked to shared mobility,
a rental processing unit for receiving and processing a rental request including user identification information and identification information of a shared mobility that the user intends to board;
a return processing unit for receiving and processing a return request including the user identification information and the user's public transportation usage history; and
A reward generation unit that determines whether to apply the transfer of the shared mobility and public transportation based on the public transportation usage history, and generates reward information based on whether the transfer is applied;
including,
The reward generating unit,
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of non-compliance with at least one of whether or not to comply with a crossing signal and whether or not to comply with the speed limit when driving the shared mobility,
The public transport usage details are accumulated and collected for a preset period, and the preset period is variably applied based on statistical information on the user's movement line collected through a user terminal,
Service providing device. 12. The method of claim 11,
Settlement unit for transmitting a payment request to a settlement service provider server based on the fee information corresponding to the return request, and receiving a processing result corresponding to the payment request from the settlement service provider server;
Which will further include, the service providing device. 12. The method of claim 11,
If the user uses public transportation after the return request is received, a collection unit for obtaining updated public transportation usage details after the user gets off the public transportation;
further comprising,
The reward generating unit,
Determining whether or not to apply the transfer of the shared mobility and public transportation based on the updated public transportation usage history, and to update the reward information based on whether the transfer is applied, the service providing apparatus. In the transfer service providing device linked to shared mobility,
a collection unit for obtaining the user's public transportation usage history; and
A reward generating unit that determines whether to apply the transfer of the shared mobility and public transportation based on the public transportation usage history and the previously secured shared mobility usage history of the user, and generates reward information based on whether the transfer is applied ,
including,
The reward generating unit,
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of non-compliance with at least one of whether or not to comply with a crossing signal and whether or not to comply with the speed limit when driving the shared mobility,
The public transport usage details are accumulated and collected for a preset period, and the preset period is variably applied based on statistical information on the user's movement line collected through a user terminal,
Service providing device. In the transfer service providing device linked to shared mobility,
a first collection unit for collecting user's shared mobility usage history;
a second collection unit for receiving transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server; and
a reward generating unit for generating reward information based on the shared mobility usage history and the transfer information;
including,
The reward generating unit,
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of non-compliance with at least one of whether or not to comply with a crossing signal and whether or not to comply with the speed limit when driving the shared mobility,
The preset period is to be variably applied based on the statistical information on the movement of the user collected through the user terminal,
Service providing device. In the transfer service providing device linked to shared mobility,
a rental processing unit for receiving and processing a rental request including user identification information and identification information of a shared mobility that the user intends to board;
a return processing unit for receiving and processing a return request including the user identification information;
a settlement unit for transmitting a payment request to a settlement service provider server based on the fee information corresponding to the return request and receiving a processing result corresponding to the payment request; and
A reward generating unit for receiving transfer information according to the user's public transportation usage history for a preset period from the settlement service provider server, and generating reward information based on the transfer information;
including,
The reward generating unit,
The reward information is selectively generated or included in the reward information based on whether the return place of the shared mobility corresponds to a preset designated return place and whether there is a history of non-compliance with traffic laws when driving the shared mobility Determining the level of reward payment, but not generating the reward information if there is a history of non-compliance with at least one of whether or not to comply with a crossing signal and whether or not to comply with the speed limit when driving the shared mobility,
The preset period is variably applied based on statistical information on the user's movement line collected through the user terminal,
Service providing device.

Images