UWB-based mass transit payment system and method

Abstract

We provide a UWB-based mass transit payment system and method. [Solution] This embodiment provides a UWB-based public transport payment system and method that recognizes whether a terminal device is boarding public transport using a UWB-based system, automatically opens and closes the gate for boarding public transport, and simultaneously automatically settles the public transport fare using the authenticated information without the need for further tagging.

Description

Technical Field

[0001] One embodiment of the present invention relates to a UWB-based mass transit payment system and method.

Background Art

[0002] The following description merely provides background information related to this embodiment and does not constitute prior art.

[0003] Generally, mass transit comprehensively refers to all transportation facilities and means that provide transportation services available to the general public. In a broad sense, it exists in any of air, sea, road, railway, and intra-region, inter-region, and international transportation systems. In an urban transportation system, urban railways, city buses, village buses, or feeder buses and related facilities are representatives.

[0004] To use mass transit means, a predetermined transportation fare must be settled. As settlement means, transportation cards, credit cards, applications using smartphones, cash, etc. are used. Recently, a transfer system has been introduced, and a settlement system has been introduced in which transportation fares are settled in proportion to the user's travel distance.

[0005] When a user uses transportation means such as buses or subways, when boarding and alighting from the transportation means, the user terminal equipped with a transportation card or application must be brought close to the transportation card reader, and the fare is settled in this way.

[0006] During a specific time period, for example, rush hour, the number of users using transportation means increases, and it takes time to board and alight from the transportation means. Therefore, there is a problem that the boarding and alighting time increases and the bus operation time is delayed.

Summary of the Invention

Problems to be Solved by the Invention

[0007] The purpose of this embodiment is to provide a UWB-based public transport payment system and method that recognizes whether a terminal device is boarding public transport, automatically opens and closes the gate for boarding public transport, and simultaneously automatically settles public transport fares using authenticated information without the need for further tagging. [Means for solving the problem]

[0008] According to one aspect of this embodiment, a UWB-based public transport payment method is provided, which includes: a process of matching a gate ID with a payment decision area code at a positioning server; a process of transmitting zone information including the payment decision area code matched with the gate ID to a user terminal at a tagless terminal at a UWB-based terminal; a process of calculating the UWB-based user terminal position coordinates at the user terminal based on UWB signals received from an anchor installed within the zone information; a process of generating area movement information at the user terminal based on the UWB-based user terminal position coordinates; a process of transmitting an entry / exit message to a gate module corresponding to the area movement information at the positioning server; and a process of terminating the connection with the positioning server at the user terminal when the entry / exit message is transmitted to the gate module, thereby settling the public transport fare corresponding to the payment decision area code. [Effects of the Invention]

[0009] As described above, this embodiment has the effect of recognizing whether or not a terminal is boarding public transport based on UWB, automatically opening and closing the gate for boarding public transport, and simultaneously automatically settling the public transport fare using the authenticated information without the need for further tagging. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows a UWB-based mass transit payment system according to this embodiment. [Figure 2] This figure shows the area divisions for UWB-based mass transit payment according to this embodiment. [Figure 3] This figure shows the two-point positioning algorithm according to this embodiment. [Figure 4] This diagram shows the process of positioning using two tagless terminals according to this embodiment. [Figure 5] This figure shows the operation process of a pair of tagless terminals according to this embodiment. [Figure 6] This is a diagram illustrating the UWB-based mass transportation payment method according to this embodiment. [Modes for carrying out the invention]

[0011] The following embodiment will be described in detail with reference to the attached drawings.

[0012] Figure 1 shows a UWB-based mass transit payment system according to this embodiment.

[0013] The UWB-based mass transit payment system according to this embodiment includes a gate module 110, tagless terminals 122, 124, a positioning server 130, an anchor 140, an LTE modem 150, and a user terminal 160. The components included in the UWB-based mass transit payment system are not necessarily limited to these.

[0014] The gate module 110 refers to a module included in a public transport ticket gate (gate) that communicates with the positioning server 130. Each gate module 110 is installed in a public transport ticket gate (gate) and includes a unique identification ID.

[0015] The tagless terminals 122 and 124 include a BLE beacon module for transmitting the unique number of the public transport station and the unique number of the public transport gate, and a UWB module for user terminal positioning. The tagless terminals 122 and 124 are installed at public transport ticket gates (ticket gates).

[0016] When a UWB-equipped terminal or transit card enters the payment determination area, the tagless terminals 122 and 124 transmit the payer information to the payment system. The tagless terminals 122 and 124 use the UWB to verify whether the user terminal 160 is passing through a specific public transport gate.

[0017] The tagless terminals 122 and 124 confirm that the user terminal 160 has passed through a specific public transport gate when it enters the payment judgment area using the TDoA (Time Difference of Arrival) method. The tagless terminals 122 and 124 are installed facing each other on the entrance and exit sides of two adjacent public transport gates among a group of public transport gates, and are installed at the same height on the two adjacent public transport gates to reduce errors.

[0018] The tagless terminals 122 and 124 transmit zone information, including a payment decision area code matched with a gate ID corresponding to the gate module 110, to the user terminal 160 using a UWB (Ultraviolet Web Block) basis.

[0019] A pair of tagless terminals 122 and 124 use a UWB (Ultra-Wide Base) system to verify whether the user terminal 160 has passed through a specific public transport gate. The pair of tagless terminals 122 and 124 use a TDoA (Time Difference of Arrival) method to verify that the user terminal 160 has passed through a specific public transport gate when it enters the payment judgment area. The pair of tagless terminals 122 and 124 are installed facing each other on the entrance and exit sides of two adjacent public transport gates among a group of public transport gates, and are installed at the same height on the two adjacent public transport gates to reduce errors.

[0020] The positioning server 130 determines BLE positioning and mobile zone entry information. The positioning server 130 transmits mobile payment information to the gate module 110. The positioning server 130 receives the payment result from the gate module 110. The positioning server 130 determines the location within the public transport ticket gate (ticket gate).

[0021] When the positioning server 130 confirms that the user terminal 160 is about to pass through a specific mass transit gate, it causes the user terminal 160 to settle the mass transit fare corresponding to the specific mass transit gate, and opens or closes the mass transit gate according to whether the mass transit fare is approved.

[0022] When the mass transit fare is approved, the positioning server 130 opens the specific mass transit gate, and when the mass transit fare is not approved, the positioning server 130 keeps the specific mass transit gate blocked.

[0023] The positioning server 130 matches the settlement judgment area code with the gate ID. The positioning server 130 transmits an entry / exit message to the gate module 110 corresponding to the area movement information generated by the user terminal 160.

[0024] The positioning server 130 registers account information from the user terminal 160, generates a tag ID for the user terminal 160, assigns it to the user terminal 160, and transmits the settlement judgment area information to the user terminal 160.

[0025] The anchor 140 is preferably installed around the mass transit station building. The anchor 140 includes a BLE module and a UWB module. The anchor 140 performs BLE-based positioning using the BLE module. The anchor 140 performs UWB-based positioning (DL TDoA) using the UWB module.

[0026] When it is confirmed that the user terminal 160 has entered a preset area based on UWB (Ultra WideBand), multiple anchors 140 track the movement direction of the user terminal 160 and select a specific mass transit gate from among multiple mass transit gates.

[0027] Multiple anchors 140 use their built-in low-power Bluetooth® (BLE) modules to send advertising signals to already configured areas. When they receive a trigger signal from a user terminal 160 located in an already configured area, the user terminal 160 wakes up from UWB sleep mode and activates the UWB tag.

[0028] Multiple anchors 140 are installed on the ceiling in four directions, based on the multiple public transport gates, and overlooking the multiple public transport gates.

[0029] Multiple anchors 140 track the positioning results of the user terminal 160 using a triangulation method. After confirming whether the user terminal 160 enters a specific entry judgment area from among multiple entry judgment areas set within an already defined area, the anchors 140 make a final selection that the user terminal 160 will head towards a specific public traffic gate corresponding to the specific entry judgment area.

[0030] The LTE modem 150 transmits and receives mobile information in conjunction with the user terminal 160. The LTE modem 150 transmits and receives information in conjunction with the positioning server 130 and the gate module 110.

[0031] User terminal 160 supports BLE, UWB, and LTE. User terminal 160 communicates with anchor 140 or tagless terminals 122 and 124 using BLE. User terminal 160 communicates with positioning server 130 using LTE. User terminal 160 is connected to the station building-gate management server and receives information from the station building-gate management server.

[0032] The user terminal 160 receives zone entry information via BLE. The user terminal 160 receives zone entry information via UWB. The user terminal 160 executes the payment process.

[0033] The user terminal 160 includes a public transport application 310 and a public transport library 320. The user terminal 160 calculates UWB-based user terminal position coordinates based on UWB signals received from anchors 140 installed within the zone information. The user terminal 160 generates area movement information based on the UWB-based user terminal position coordinates.

[0034] When an entry / exit message is transmitted to the gate module 110, the user terminal 160 settles the public transport fare corresponding to the payment judgment area code and terminates its connection with the positioning server 130. When BLE signals are scanned from tagless terminals 122 and 124, the user terminal 160 extracts the public transport station unique number and public transport gate unique number contained in the BLE signal.

[0035] When user terminal 160 receives zone information from tagless terminals 122 and 124, it requests a WebSocket authentication token from positioning server 130, and then receives a WebSocket authentication token from positioning server 130.

[0036] The user terminal 160 connects to the web socket of the positioning server 130 based on the web socket authentication token, and then sends the web socket authentication token and account information to the web socket of the positioning server 130.

[0037] The user terminal 160 receives the tag ID and payment decision area information from the positioning server 130. The user terminal 160 generates a coordinate event including the UWB-based user terminal location coordinates. The user terminal 160 generates an area event based on the UWB-based user terminal location coordinates. The user terminal 160 generates area movement information by analyzing whether or not there has been area movement based on zone information including the coordinate event, area event, and payment decision area code matched with the gate ID.

[0038] When area movement information is generated, the user terminal 160 starts its business logic and then generates destination gate setting information, which indicates that the destination gate has been set. When an entry / exit message is transmitted to the gate module 110, the user terminal 160 terminates its business logic and then generates destination gate release information, which indicates that the destination gate has been released. If the user terminal 160 does not scan for BLE signals from the tagless terminals 122 and 124, it recognizes that the user has left the zone.

[0039] User terminal 160 draws a virtual center line between the pair of tagless terminals 122 and 124, then draws a first virtual arc with the first tagless terminal 122 as the central axis, and designates the point where the first virtual arc and the virtual center line intersect as P1. User terminal 160 then draws a second virtual arc with the second tagless terminal 124 as the central axis, and designates the point where the second virtual arc and the virtual center line intersect as P2. User terminal 160 selects either P1 or P2. User terminal 160 recognizes this point as the UWB-based user terminal location.

[0040] The user terminal 160 selects either one of P1 or P2 based on whether the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 is less than 0 at P1, or whether the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 is less than 0 at P2.

[0041] The user terminal 160 calculates the value obtained by subtracting the distance from P1 to the second tagless terminal L2 (P1~L2) from the distance from P1 to the first tagless terminal L1 (P1~L1) as the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 at P1. The user terminal 160 calculates the value obtained by subtracting the distance from P2 to the second tagless terminal L2 (P2~L2) from the distance from P2 to the first tagless terminal L1 (P2~L1) as the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2.

[0042] When the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2 is less than 0 (dd2 < 0), the user terminal 160 selects P2, which is one of P1 and P2 existing on the virtual center line, as the position of the user terminal 160. When the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2 is greater than 0 (dd2 > 0), the user terminal 160 selects P1, which is one of P1 and P2 existing on the virtual center line, as the position of the user terminal 160.

[0043] The user terminal 160 checks the distance D1 between the first tagless terminal L1 and P1, and checks the distance D2 between the first tagless terminal L1 and P2. When the distance D1 between the first tagless terminal L1 and P1 is less than the distance D2 between the first tagless terminal L1 and P2 (D1 < D2), the user terminal 160 determines that P1 is closer to the first tagless terminal L1 and arranges them in the order of {P1, P2}. When the distance D1 between the first tagless terminal L1 and P1 is greater than the distance D2 between the first tagless terminal L1 and P2 (D1 > D2), the user terminal 160 determines that P2 is closer to the first tagless terminal L1 and arranges them in the order of {P2, P1}.

[0044] The user terminal 160 calculates the distance difference (dd) by multiplying the value obtained by subtracting the time difference between the second tagless terminal L2 and T (td2) from the time difference between the first tagless terminal L1 and T (td1) by the velocity. If the distance difference (dd) is less than 0 (distance difference (dd) < 0), the user terminal 160 first selects the first coordinate. If the distance difference (dd) is greater than 0 (distance difference (dd) > 0), the user terminal 160 first selects the second coordinate.

[0045] The station building-gate management server manages station building-gate information. The station building-gate management server manages zones for each gate. The station building-gate management server manages RSSI (Received Signal Strength Indicator) values ​​to determine zones.

[0046] Figure 2 shows the area divisions for UWB-based mass transit payment according to this embodiment.

[0047] Area names are defined by combining multiple elements. Station code 210 uses the ID of an existing system and has a 4-digit number (0001 to 9999). Zone code 220 refers to information for dividing zones within the same station code. Zone code 220 is assigned sequentially from 01 within the station code and has a 2-digit number (01 to 99).

[0048] Exit zone code 230 sets the exit area to FREE and the boarding area to PAID. Exit zone code 230 includes the station code and zone code.

[0049] The settlement decision area code 240 refers to information used to demarcate settlement decision areas within zone code 220. The settlement decision area code 240 is defined as a two-digit number. Settlement decision area codes 240 are assigned sequentially from 01 within the same zone.

[0050] The additional code 250 within the settlement judgment area is a detailed subdivision of the settlement judgment area, and is assigned sequentially starting from 1, beginning with the exit side. The additional code 250 within the settlement judgment area is assigned a single-digit number.

[0051] Figure 3 shows the two-point positioning algorithm according to this embodiment.

[0052] The user terminal 160 uses only the pair of tagless terminals 122 and 124 to recognize the location of the terminal or card equipped with the UWB module (tag) using the TDoA method.

[0053] The user terminal 160 draws a virtual centerline between the pair of tagless terminals 122 and 124. The user terminal 160 recognizes the position of the terminal or card equipped with the UWB module (tag) using the arrival time difference, so the time difference between P1 and P2, where the terminal or card equipped with the UWB module (tag) is located on the virtual centerline, is the same.

[0054] The user terminal 160 draws a first virtual arc with the first tagless terminal 122 as its central axis, and then designates the point where the first virtual arc and the virtual center line meet as P1. The user terminal 160 then draws a second virtual arc with the second tagless terminal 124 as its central axis, and then designates the point where the second virtual arc and the virtual center line meet as P2.

[0055] The user terminal 160 selects one of two points, P1 or P2, located on a virtual centerline, and recognizes that point as the location of a terminal or card equipped with a UWB module (tag). The user terminal 160 can convert the time difference into a distance difference.

[0056] The user terminal 160 calculates the distance difference (dd) using [Equation 1], where td1 is the time difference between tagless terminals L1 and T, and td2 is the time difference between L2 and T.

[0057]

number

[0058] The user terminal 160 calculates dd1, dd2, and res in order to select one of P1 and P2, which are located on the virtual centerline.

[0059] The user terminal 160 uses [Equation 2] to calculate the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 at P1.

[0060]

number

[0061] Here, one of the distances from P1 to the first tagless terminal L1 (P1~L1) and the distance from P1 to the second tagless terminal L2 (P1~L2) is always less than 0.

[0062] The user terminal 160 uses [Equation 3] to calculate the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2.

[0063]

number

[0064]

number

[0065] Here, res has a value of 0 or less than 0.

[0066] The user terminal 160 recognizes that a terminal or card equipped with a UWB module (tag) is located midway between the positions of P1 and P2 if the distance difference between the first tagless terminal L1 and the second tagless terminal L2 (dd1) or the distance difference between the first tagless terminal L1 and the second tagless terminal L2 (dd2) at P1 is 0. In other words, the user terminal 160 can select either P1 or P2 if res is 0.

[0067] If the user terminal 160 finds that the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 at P1 is less than 0 (dd1 < 0), it selects P1 from P1 and P2, which lie on a virtual centerline, as the location of the terminal or card equipped with the UWB module (tag).

[0068] If the user terminal 160 finds that the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 at P1 is greater than 0 (dd1>0), it selects P2, which lies on the virtual centerline, as the location of the terminal or card equipped with the UWB module (tag).

[0069] If the user terminal 160 finds that the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2 is less than 0 (dd2<0), it selects P2, which lies on the virtual centerline, as the location of the terminal or card equipped with the UWB module (tag).

[0070] If the user terminal 160 finds that the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2 is greater than 0 (dd2>0), it selects P1 as the location of the terminal or card equipped with the UWB module (tag) from among P1 and P2 which lie on the virtual centerline.

[0071] Figure 4 shows the process of positioning using two tagless terminals according to this embodiment.

[0072] When the user terminal 160, which is a tagless terminal, sets the time difference between L1 and T as td1 and the time difference between L2 and T as td2, it calculates the distance difference (dd) using [Equation 1]. The user terminal 160 checks D1 and D2 to select one of P1 and P2 that exist on the virtual center line.

[0073] The user terminal 160 checks the distance D1 between the first tagless terminal L1 and P1. The user terminal 160 checks the distance D2 between the first tagless terminal L1 and P2. The user terminal 160 arranges the two points P1 and P2 in ascending order of proximity to the first tagless terminal L1.

[0074] When the distance D1 between the first tagless terminal L1 and P1 is smaller than the distance D2 between the first tagless terminal L1 and P2 (D1 < D2 pts[2]), the user terminal 160 determines that P1 is closer to the first tagless terminal L1 and arranges them in the order of {P1, P2}.

[0075] [[ID=​​​​​​​​​​​Figure 5 shows the operation process of a pair of tagless terminals according to this embodiment.

[0079] The public transport payment system automatically authenticates public transport gates based on distance and angle using UWB. The public transport payment system opens and closes the gates automatically using the authenticated information. The public transport payment system performs automatic payment (such as using transport cards) using authentication. The public transport payment system can be integrated with UWB radar technology to enhance entry and exit security (anti-tailgating). The public transport payment system automatically authenticates public transport gates using a mobile phone (mobile ID) or UWB tag equipped with UWB.

[0080] A pair of tagless terminals 122 and 124 are installed facing each other on the entrance and exit sides of two subway ticket gates. To reduce errors, the pair of tagless terminals 122 and 124 are installed at the same height at both subway ticket gates.

[0081] The first tagless terminal 122 is installed on the entrance side of the subway ticket gate (Gate A), and the remaining second tagless terminal 124, which communicates in conjunction with the first tagless terminal 122, is installed facing the first tagless terminal 122 on the exit side of the subway ticket gate (Gate B), which is adjacent to the first tagless terminal 122.

[0082] The user terminal 160 draws a virtual center line between the pair of tagless terminals 122 and 124, then draws a first virtual arc with the first tagless terminal 122 as the central axis, and designates the point where the first virtual arc and the virtual center line meet as P1. The user terminal 160 then draws a second virtual arc with the second tagless terminal 124 as the central axis, and designates the point where the second virtual arc and the virtual center line meet as P2. The user terminal 160 selects either P1 or P2, and then recognizes that point as the UWB-based user terminal location.

[0083] The user terminal 160 selects either P1 or P2 based on whether the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 is less than 0 at P1. The user terminal 160 also selects either P1 or P2 based on whether the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 is less than 0 at P2.

[0084] The user terminal 160 calculates the distance difference (dd1) between the first tagless terminal L1 and the second tagless terminal L2 at P1 by subtracting the distance from P1 to the second tagless terminal L2 (P1 to L2) from the distance from P1 to the first tagless terminal L1 (P1 to L1).

[0085] The user terminal 160 calculates the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2 by subtracting the distance from P2 to the second tagless terminal L2 (P2~L2) from the distance from P2 to the first tagless terminal L1 (P2~L1).

[0086] If the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 at P2 is less than 0 (dd2 < 0), the user terminal 160 selects P2 as the location of the user terminal 160, out of P1 and P2 which lie on the virtual centerline.

[0087] If the user terminal 160 is at P2 and the distance difference (dd2) between the first tagless terminal L1 and the second tagless terminal L2 is greater than 0 (dd2>0), then P1, which lies on the virtual centerline, is selected as the location of the user terminal 160.

[0088] The user terminal 160 checks the distance D1 between the first tagless terminal L1 and P1. The user terminal 160 checks the distance D2 between the first tagless terminal L1 and P2. When the distance D1 between the first tagless terminal L1 and P1 is smaller than the distance D2 between the first tagless terminal L1 and P2 (D1 < D2), the user terminal 160 determines that P1 is closer to the first tagless terminal L1 and arranges them in the order of {P1, P2}. When the distance D1 between the first tagless terminal L1 and P1 is larger than the distance D2 between the first tagless terminal L1 and P2 (D1 > D2), the user terminal 160 determines that P2 is closer to the first tagless terminal L1 and arranges them in the order of {P2, P1}.

[0089] The user terminal 160 calculates a distance difference (dd) obtained by multiplying the value obtained by subtracting the time difference (td2) from the second tagless terminal L2 to T from the time difference (td1) from the first tagless terminal L1 to T by the speed.

[0090] When the distance difference (dd) is smaller than 0 (distance difference (dd) < 0), the user terminal 160 first selects the first coordinate. When the distance difference (dd) is larger than 0 (distance difference (dd) > 0), the user terminal 160 first selects the second coordinate.

[0091] FIG. 6 is a diagram for explaining the UWB-based mass transit settlement method according to the present embodiment.

[0092] The positioning server 130 scans a serial port (S601). When the serial port is scanned, the positioning server 130 transmits an ID request signal to the gate module 110 (S602).

[0093] The gate module 110 receives the ID request signal from the positioning server 130, extracts the gate ID, generates an ID response signal including the gate ID, and transmits it at the positioning server 130 (S603).

[0094] The positioning server 130 extracts the gate ID contained in the ID response signal received from the gate module 110. The positioning server 130 matches the gate ID with the payment decision area code (S604). In step S604, the positioning server 130 transmits the payment decision area code matched with the gate ID to the tagless terminals 122 and 124. Subsequently, the tagless terminals 122 and 124 transmit zone information including the payment decision area code matched with the gate ID to the user terminal 160 on a UWB basis.

[0095] The public transport application 310 on the user terminal 160 starts after the account information is entered into the public transport library 320 (S611).

[0096] When the public transport library 320 of the user terminal 160 receives account information from the public transport application 310, it starts scanning for BLE signals for tagless terminals 122 and 124 (S612). In step S612, the public transport library 320 of the user terminal 160 transmits the BLE signals scanned from the tagless terminals 122 and 124 to the public transport application 310.

[0097] The tagless terminals 122 and 124 transmit zone information, including a payment decision area code matched with the gate ID, to the user terminal 160 using a UWB (S613). The public transport library 320 of the user terminal 160 receives the zone information, including a payment decision area code matched with the gate ID, from the tagless terminals 122 and 124 using a UWB.

[0098] When the public transport library 320 of the user terminal 160 receives zone information including a payment decision area code that matches the gate ID from tagless terminals 122 and 124 via UWB, it requests a WebSocket authentication token from the positioning server 130 and then receives a WebSocket authentication token from the positioning server 130 (S614).

[0099] The public transport library 320 of the user terminal 160 connects to the web socket of the positioning server 130 based on the web socket authentication token (S615). In step S615, the public transport library 320 of the user terminal 160 sends the authentication token and account information to the web socket of the positioning server 130.

[0100] The positioning server 130 registers account information, generates a tag ID for the user terminal 160 and assigns it to the user terminal 160, and transmits payment decision area information to the user terminal 160 (S622). The public transport library 320 of the user terminal 160 receives the tag ID and payment decision area information from the positioning server 130 (S624).

[0101] Anchor 140 generates a UWB signal at the location where it is installed (S631). The public transport library 320 of the user terminal 160 calculates the UWB-based user terminal position coordinates based on the UWB signal received from anchor 140 installed in the public transport station (S632).

[0102] The public transport library 320 of the user terminal 160 transmits zone information, including a payment decision area code matched with the gate IDs received from the tagless terminals 122 and 124 in step S613, to the public transport application 310 (S641).

[0103] The public transport library 320 of the user terminal 160 transmits coordinate events, including the UWB-based user terminal location coordinates, to the public transport application 310 (S652). The public transport library 320 of the user terminal 160 transmits area events to the public transport application 310 based on the UWB-based user terminal location coordinates (S654).

[0104] The public transport application 310 of the user terminal 160 generates area movement information by analyzing whether or not there has been area movement based on zone information including coordinate events, area events, and a payment judgment area code matched with gate IDs received from the public transport library 320 (S655).

[0105] When area movement information is generated, the public transport application 310 on the user terminal 160 starts its business logic (S656).

[0106] When the public transport library 320 of the user terminal 160 receives business logic start information from the public transport application 310, it generates destination gate setting information in which the destination gate has been set (S657). In step S657, the public transport library 320 of the user terminal 160 transmits the destination gate setting information to the public transport application 310.

[0107] The public transport application 310 of the user terminal 160 transmits gate data, including area movement information and destination gate information, to the public transport library 320 (S661). The public transport library 320 of the user terminal 160 transmits the gate data to the positioning server 130 (S662). The positioning server 130 transmits the gate data to the gate module 110 corresponding to the gate data received from the public transport library 320 (S663).

[0108] After receiving gate data from the positioning server 130, the gate module 110 transmits an inbound / outbound message to the positioning server 130 for the user terminal 160 corresponding to the gate data.

[0109] The positioning server 130 receives an entry / exit message from the gate module 110 to the user terminal 160, and then transmits the entry / exit message to the user terminal 160 (S665). The public transport library 320 of the user terminal 160 receives the entry / exit message from the positioning server 130, and then transmits it to the public transport application 310 (S666). The public transport application 310 of the user terminal 160 receives the entry / exit message from the public transport library 320 (S667).

[0110] When the public transport application 310 of the user terminal 160 receives an entry / exit message from the public transport library 320, it terminates its business logic (S668).

[0111] When the public transport library 320 of the user terminal 160 receives business logic completion information from the public transport application 310, it generates destination gate release information indicating that the destination gate has been released (S669). In step S669, the public transport library 320 of the user terminal 160 transmits the destination gate release information to the public transport application 310.

[0112] The public transport library 320 of user terminal 160 confirms zone departure based on BLE signals scanned from tagless terminals 122 and 124 (S670).

[0113] When the public transport library 320 of the user terminal 160 detects that the user has left the zone, it requests the public transport application 310 to terminate the connection with the positioning server 130 and stop the BLE signal scan (S680).

[0114] Figure 6 shows that steps S601 to S680 are executed sequentially, but this is not necessarily the only way to proceed. In other words, it is possible to modify the steps shown in Figure 6 or to apply the process to execute one or more steps in parallel. Therefore, Figure 6 is not limited to a chronological order.

[0115] As described above, the UWB-based mass transit payment method according to this embodiment shown in Figure 6 may be implemented as a program and recorded on a computer-readable recording medium. The recording medium on which the program for implementing the UWB-based mass transit payment method according to this embodiment is recorded and which is computer-readable may include any type of recording device on which data readable by a computer system is stored.

[0116] The above description is merely illustrative of the technical concept of this embodiment, and any person with ordinary skill in the art to which this embodiment belongs could make various modifications and alterations without departing from the essential characteristics of this embodiment. Therefore, this embodiment is for illustrative purposes only, not to limit the technical concept of this embodiment, and the scope of the technical concept of this embodiment is not limited by such embodiment. The scope of protection of this embodiment should be interpreted in accordance with the attached claims, and all technical concepts within an equivalent scope should be interpreted as being included in the scope of rights of this embodiment. [Explanation of symbols]

[0117] 110: Gate Module 122,124: Tagless terminals 130: Location positioning server 140: Anchor 150: LTE modem 160: User terminal

Claims

1. The process involves matching the payment decision area code with the gate ID on the positioning server, The process involves a tagless terminal transmitting zone information, including the payment judgment area code matched with the gate ID, to a user terminal using a UWB (Universal Web Gateway) basis, The process of calculating the UWB-based user terminal position coordinates based on the UWB signal received from an anchor installed within the zone information at the user terminal, The process of generating area movement information based on the UWB-based user terminal position coordinates in the user terminal, The process involves the positioning server transmitting an entry / exit message to the gate module corresponding to the area movement information, When the user terminal transmits the entry / exit message to the gate module, the public transport fare corresponding to the payment judgment area code is settled, and the connection with the positioning server is terminated. A UWB-based mass transportation payment method characterized by including the following.

2. The UWB-based public transport payment method according to claim 1, characterized in that when a BLE signal is scanned from a tagless terminal by the user terminal, the user terminal extracts the unique public transport station number and the unique public transport gate number contained in the BLE signal.

3. When the user terminal receives the zone information from the tagless terminal, it requests a WebSocket authentication token from the positioning server, and then receives the WebSocket authentication token from the positioning server. The process involves the user terminal connecting to the web socket of the location positioning server based on the web socket authentication token, and then transmitting the web socket authentication token and account information to the web socket of the location positioning server. The UWB-based mass transportation payment method according to claim 1, further comprising:

4. The process includes registering the account information at the location positioning server, generating a tag ID for the user terminal and assigning it to the user terminal, and transmitting payment decision area information to the user terminal, The process of the user terminal receiving the tag ID and payment decision area information from the location positioning server, The UWB-based mass transportation payment method according to claim 2, further comprising:

5. The process of generating a coordinate event including the UWB-based user terminal position coordinates on the user terminal, The process of generating a region event on the user terminal based on the UWB-based user terminal position coordinates, The process of generating area movement information by analyzing whether or not there has been area movement, based on the zone information including the coordinate event, the area event, and the payment judgment area code obtained by matching the gate ID, on the user terminal, The UWB-based mass transportation payment method according to claim 1, further comprising:

6. The UWB-based mass transportation payment method according to claim 5, characterized in that when the area movement information is generated on the user terminal, the business logic is started and then destination gate setting information is generated in which the destination gate is set.

7. The UWB-based mass transit payment method according to claim 1, characterized in that when the user terminal transmits the entry / exit message to the gate module, after terminating the business logic, destination gate release information is generated indicating that the destination gate has been released.

8. The UWB-based mass transit payment method according to claim 1, characterized in that the user terminal recognizes that the user has left the zone if the BLE signal is not scanned from the tagless terminal.

Images