KR20110062031A - System for providing the restful bus-related information service - Google Patents

Abstract

PURPOSE: A REST based bus related information providing system is provided to obtain bus related information through an HTTP(Hypertext Transfer Protocol) client application based on REST. CONSTITUTION: An HTTP request receiver(111) receives HTTP based bus related information request from a client(100). A resource provider(112) searches for requested information based on REST. The resource provider provides searched information to a client. The bus related information includes bus information, bus station information, and bus arrival information.

Description

System for providing the RESTful bus-related information service

The present invention relates to a service providing technology for providing an application service to a terminal with internet access, and more particularly, to a technology for providing bus-related information requested by a terminal user.

The present invention is derived from a study conducted as part of the Ministry of Knowledge Economy. [Task Management No .: 2009-F-048-01, Title: Development of a network-based consumer-oriented convergence service common platform technology]

Recently, Intelligent Transport Systems (ITS) are being built around local governments. The intelligent transportation system is constructed as a comprehensive traffic information management system combined with wired / wireless communication technology to promote safety and convenience to road users such as traffic management, electronic toll payment, public transportation activation, and safe driving assistance, centering on the local government. have. Such an intelligent transportation system also provides a service of notifying the estimated time of arrival of the bus, in order to provide convenience to the passengers, especially during public transportation. When the bus user accesses the intelligent transportation system through the Internet and inquires when a specific bus will arrive at a specific stop, the intelligent transportation system informs the bus user of the estimated time of arrival of a specific stop by SMS. However, this type of service has problems such as transmission time delay and inaccurate bus related information due to bulk SMS transmission. In addition, since the transmission request is set to be fixed only at a fixed time, it does not provide appropriate bus arrival information according to a user's variable situation, which causes a problem of waste of resources and inefficiency of service use.

On the other hand, Hypertext Transfer Protocol (HTTP) technology based on Representational State Transfer (REST) proposes a basic principle in exchange of information based on the Internet. That is, in order not only to exchange information between a person and a machine (web server) but also to exchange information between machines and machines, a resource identifiable by a URL is configured, and a resource (resource) link (link) is formed. It presents the principle of mutual information exchange with resources based on HTTP-based information generation (POST), query (GET), deletion (DELETE), update (PUT), and operation (Operation). In recent years, REST technology has provided an open API (Application Programming Interface, Open API) for web portals and service providers. Based on WSDL (Simple Object Access Protocol) and WSDL (Simple Object Access Protocol) It is widely used as an alternative to the Web Services approach.

An object of the present invention is to provide a REST-based bus-related information providing device, method, and system that can provide a user with convenient and efficient bus-related information.

The REST-based bus-related information providing apparatus for achieving the above-described technical problem includes information requested from the bus-related information consisting of an HTTP request receiving unit, a REST-based resource and a link, which receives an HTTP-based bus-related information request from a client. It includes a resource providing unit for searching and providing to the client.

Meanwhile, a method for providing REST-based bus-related information for achieving the above-described technical problem includes receiving an HTTP-based bus-related information request from a client, requesting information from bus-related information consisting of resources and links represented by REST-based information. Retrieving, and responding the retrieved information to the client.

On the other hand, the REST-based bus-related information providing system for achieving the above-described technical problem manages bus-related information consisting of a client requesting and receiving bus-related information based on HTTP, and resources and links represented by REST, It includes a REST-based bus-related information providing device for retrieving the information in response to the HTTP-based bus-related information request from the client to respond to the client.

The present invention configures bus-related information resources and links based on REST, and enables the user to easily obtain bus-related information at a desired time through an HTTP client application that can be installed on the client. In addition, the present invention is to set the information on the bus and the station mainly used by the user in the client application, the user can search the bus arrival schedule information anytime, anywhere in real time. In addition, the present invention also provides a list of scheduled bus arrival times, to help the user determine when to move to the stop. That is, the present invention can help the user to easily access the bus arrival information, thereby activating the recent increase in the use of public transportation.

The foregoing and further aspects of the present invention will become more apparent through the preferred embodiments described with reference to the accompanying drawings. Hereinafter, the present invention will be described in detail to enable those skilled in the art to easily understand and reproduce the present invention.

1 is a block diagram of a REST-based bus-related information providing system according to an embodiment of the present invention.

The REST based bus related information providing system includes a client 100 and a REST based bus related information providing apparatus 110. The client 100 may be an example of a mobile terminal. The client 100 is equipped with HTTP-based application software 101 for using a bus-related service. The application software 101 has a basic function of processing a request and response of HTTP through a wired Internet or a wireless Internet (2G, 3G, WLAN, Wibro, etc.) according to a connection situation of a mobile terminal. In addition, the application software 101 receives an input in the form of a form from a user, requests an HTTP transmission, and parses the received content in response. That is, the application software 101 has a role of parsing an XML schema mutually defined with the REST based bus related information providing apparatus 110. Since the application software 101 operates on the HTTP function, there is no dependency on the terminal of a specific product. Like an open marketplace such as an App Store, a user may download and install the application software 101 to the client 100 by paying a certain amount, or may download and install the REST-based bus-related information providing apparatus 110.

The REST-based bus-related information providing apparatus 110 is a system for expressing bus-related information as a REST-based resource and responding the related information to the HTTP request therefor. Therefore, the overall operation flow is that the application software 101 receives the user's input and transmits the HTTP request to the REST-based bus-related information providing device 110, and receives the response and expresses the response to the user. The REST based bus related information providing apparatus 110 includes an HTTP request receiving unit 111 and a resource providing unit 112. The HTTP request receiver 111 receives a bus-related information request using HTTP from the application software 101 and transmits the request to the resource provider 112. The resource provider 112 searches for the corresponding information among the bus related information in response to the bus related information request, and transmits the found resource to the application software 101. According to one aspect of the present invention, bus-related information is composed of resources and links expressed on a REST basis. Bus-related information includes bus information, bus stop information, and bus arrival information.

2 is a block diagram of REST-based resources and links according to an embodiment of the present invention.

The REST-based bus information providing apparatus 110 manages bus-related information through the configuration of the representation and link of the REST-based resources. Bus related information is largely composed of bus information, bus stop information, and bus arrival information. The client 100 may obtain each information through the parameterized HTTP request as follows.

① Example of request and response for bus information

When the user requests the bus information through the application software 101, the user may request the bus information by inputting the name of the city or by inputting the main institution or the building name. In addition, the bus information may be requested by inputting trunk lines or branch lines, or by inputting a bus vertical and horizontal direction.

-Dong name: GET http://daejeon.bus.com/buses?q = Dunsan-dong

-Major Institutions or Buildings: GET http://daejeon.bus.com/buses?q = Korea Electronics and Telecommunications Research Institute

-Main Line or Branch Line: GET http://daejeon.bus.com/buses?q = Main Line

-Bus Crossing Direction: GET http://daejeon.bus.com/buses/South/North

<Response>: The REST-based bus-related information providing device 110 responds to the application software 101 a list value composed of a bus identifier corresponding to the above query.

200 OK
Content-Type: application / xml

<? xml version = "1.0" encoding = "utf-8"?>
<buses>
<bus href = "/ buses / 111A"/>
<bus href = "/ buses / 111B"/>
<bus href = "/ buses / 333A"/>
<bus href = "/ buses / 333B"/>
</ buses>

② Example of request and response for specific bus information

The user may request specific bus information by inputting a desired bus identifier among the response bus identifiers through the application software 101.

-GET http://daejeon.bus.com/buses/ { bus _ id }

<Response>: The REST-based bus related information device 110 responds to the application software 101 with information about the specific bus requested. In one embodiment, the response information includes information on the bus identifier (bus_id), the name of the bus (going up 111), the dispatch interval (30 minutes), the route map image, and the like.

200 OK
Content-Type: application / xml

<? xml version = "1.0" encoding = "utf-8"?>
<bus_info id = "111A">
<bus_id> 111A </ bus_id>
<bus_name> Uphill 111 </ bus_name>
<interval type = "minute"> 30 </ interval>
<route type = "image"> http://daejon.bus.com/buses/111A/route.jpg </ route>
</ buses>

③ Example of request and response for bus stop information

When requesting bus stop information through the user application software 101, the name may be inputted, or the bus stop information may be requested by inputting a major institution or building name.

-Dong name: GET http://daejeon.bus.com/stops?q = Dunsan-dong

-Major Institution or Building: GET http://daejeon.bus.com/stops?q = Korea Electronics and Telecommunications Research Institute

<Response>: The REST-based bus-related information providing device 110 responds to the application software 101 a list value composed of a bus stop identifier corresponding to the above query.

200 OK
Content-Type: application / xml

<? xml version = "1.0" encoding = "utf-8"?>
<stops>
<stops href = "/ stops / 1234A"/>
<stops href = "/ stops / 1234B"/>
<stops href = "/ stops / 5678A"/>
<stops href = "/ stops / 5678B"/>
<stops href = "/ stops / 3456A"/>
<stops href = "/ stops / 3456B"/>
</ stops>

④ Example of request and response for specific bus stop information

The user may request specific bus stop information by inputting a desired bus stop identifier among the response bus stop identifiers through the application software 101.

-GET http://daejeon.bus.com/stops/ { stop _ id }

<Response>: The REST-based bus-related information providing device 110 responds to the application software 101 with information on the requested specific bus stop. In one embodiment, the response information includes information such as a stop identifier (stop_id), the name of the stop (in front of the Korea Electronics and Telecommunications Research Institute), a link to a stop location image, a bus list that stops at the stop, and the like.

200 OK
Content-Type: application / xml

<? xml version = "1.0" encoding = "utf-8"?>
<stop_info id = "1234A">
<stop_id> 1234A </ stop_id>
<stop_name> In front of Korea Electronics and Telecommunications Research Institute </ stop_name>
<location type = "image"> http://daejeon.bus.com/stops/1234A/stopimage.jpg
</ location>
<buses>
<bus href = "/ buses / 111A"/>
<bus href = "/ buses / 333A"/>
</ buses>
</ stop_info>

⑤ Request and response example for bus arrival information

When the user requests the bus arrival schedule information through the application software 101, the user may request the bus arrival schedule information by inputting the bus identifier and the stop identifier.

-GET http://daejeon.bus.com/arrival?bus_id="111A"&stop_id="1234A "

<Response>: The REST-based bus related information providing apparatus 110 responds to the application software 101 with the requested bus arrival schedule information. In one embodiment, the response bus arrival schedule information includes information on the scheduled time for the bus (bus_id) to arrive at the bus stop (stop_id) as the main content. In addition, the estimated arrival time may include only the scheduled arrival time of the bus closest to the current bus stop, and the scheduled arrival time for the buses scheduled to arrive thereafter may also be included if the information is valid. In addition, for display to the client 100, the bus name (above 111) and the stop name (in front of the Korea Institute of Electronics and Telecommunications) are included in the response bus arrival schedule information.

200 OK
Content-Type: application / xml

<? xml version = "1.0" encoding = "utf-8"?>
<arrival_info xmlns = http: //daejeon.businfo.com/ns/bus_arrival>
<base-url> http://daejeon.businfo.com </ base-url>
<bus href = "/ buses / 111A" name = "go up 111"/>
<stop href = "/ stops / 1234A" name = "In front of Korea Electronics and Telecommunications Research Institute"/>
<next_arrival>
<timeleft type = 'minute'> 10 </ timeleft>
<timeleft type = 'minute'> 30 </ timeleft>
</ next_arrival>
</ arrival info>

3 is a flowchart illustrating a bus information request and response process according to an embodiment of the present invention.

The client 100 obtains bus information through a total of three request and response processes. That is, in the initial request and response process 3-1, the client 100 obtains link information on available resources belonging to the bus information from the REST-based bus related information providing apparatus 110, and the second request and response. In the process (3-2), the bus information related to “Dunsan-dong” is requested to receive the relevant bus list. In the third request and response process (3-3), the bus information for the specific bus identifier is designated by specifying the specific bus identifier. I get a response. The second request and response process (3-2) and the third request and response process (3-3) of this process correspond to the request and response process of ① and ② in the above examples. Through such a procedure, the application software 101 may obtain desired bus information from the REST-based bus related information providing apparatus 110.

4 is a flowchart illustrating a bus stop information request and response process according to an embodiment of the present invention.

The client 100 obtains bus stop information through a total of three request and response processes. That is, in the initial request and response process 4-1, the client 100 obtains link information on available resources belonging to bus stop information from the REST-based bus-related information providing apparatus 110, and obtains a second request and In the response process (4-2), the bus station information related to the “Korea Electronics and Telecommunications Research Institute” is requested to receive a list of relevant bus stops.In the third request and response process (4-3), a specific bus station identifier is designated and specified. Receive bus stop information on the bus stop identifier. The second request and response process (4-2) and the third request and response process (4-3) of this process correspond to the request and response process of ③ and ④ of the above example. Through such a procedure, the application software 101 may obtain desired bus stop information from the REST-based bus related information providing apparatus 110.

5 is a flowchart illustrating a bus arrival schedule information request and response process according to an embodiment of the present invention.

In the initial request and response process 5-1, the client 100 obtains link information on available resources belonging to bus information and bus stop information from the REST-based bus related information providing apparatus 110. Next, the client 100 obtains bus information through process 5-2 of FIG. 3, and acquires bus stop information through process 5-3 of FIG. 4. Then, in the request and response process (5-4), the client 100 requests the bus arrival information related to “111A (bus_id)” and “1234A (stop_id)” to the REST-based bus-related information providing device 110 and responds. Receive. In addition, the client 100 may further learn detailed bus information through a link provided in bus related information as in the request and response process 5-5. In addition, the client 100 may further learn detailed stop information through a link provided in bus-related information as in the request and response process (5-6).

The above procedure is performed when the user searches for and finds "bus information" or "bus stop information" through the client 100, and then makes a parameterized query using the bus identifier (bus_id) and the bus stop identifier (stop_id). It is a procedure that takes place. The above procedure is used when the user first searches for bus arrival schedule information through the client 100 or when the client 100 does not have a bus identifier or a bus stop identifier preset by the user. If the user sets a frequently used bus identifier or stop identifier, the client 100 may immediately perform the request and response process 4 of FIG. 5. Therefore, the user can obtain bus arrival information more quickly when desired.

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope will be construed as being included in the present invention.

1 is a block diagram of a REST-based bus-related information providing system according to an embodiment of the present invention.

2 is a block diagram of a REST-based resource and link according to an embodiment of the present invention.

3 is a flowchart illustrating a bus information request and response process according to an embodiment of the present invention.

4 is a procedure showing a bus stop information request and response process according to an embodiment of the present invention.

5 is a flowchart illustrating a bus arrival schedule information request and response process according to an embodiment of the present invention.

Claims (17)

An HTTP request receiver configured to receive a Hypertext Transfer Protocol (HTTP) based bus related information request from a client; A resource providing unit searching for the requested information from bus-related information including resources and links represented on a REST (Representational State Transfer) basis and providing the requested information to the client; REST-based bus-related information providing device comprising a. The method of claim 1, The bus-related information includes a REST-based bus-related information providing device, characterized in that at least one of bus information, bus stop information, bus arrival information. The method of claim 2, The bus information provided to the client by the resource provider includes at least one of a bus identifier, a bus name, a dispatch interval, and a route map. The method of claim 2, The bus stop information provided by the resource provider to the client includes at least one of a bus stop identifier, a bus stop name, bus stop location information, and a bus list stopping at the bus stop. The method of claim 2, The bus arrival schedule information provided by the resource provider to the client includes a bus identifier, a bus stop identifier, a bus name, and a bus stop name to inform a predetermined time at which a specific bus arrives at a specific bus stop. Related Information Device. Receiving a Hypertext Transfer Protocol (HTTP) based bus related information request from a client; Retrieving the requested information from bus-related information consisting of resources and links represented on a Representational State Transfer (REST) basis; And Responding the retrieved information to the client; REST-based bus-related information providing method comprising a. The method of claim 6, The bus-related information includes at least one of bus information, bus stop information, bus arrival information, the REST-based bus-related information providing method. The method of claim 7, wherein The bus information retrieved from the bus-related information includes at least one of a bus identifier, a bus name, a dispatch interval, and a route map. The method of claim 7, wherein The bus stop information searched among the bus-related information includes at least one of a bus stop identifier, a bus stop name, bus stop location information, and a bus list stopping at the bus stop. The method of claim 7, wherein The bus arrival information retrieved from the bus-related information includes a bus identifier, a bus stop identifier, a bus name, and a bus stop name to inform a predetermined time at which a specific bus arrives at a specific bus stop. Way. Client for requesting and responding to bus-related information based on Hypertext Transfer Protocol (HTTP); And REST-based bus-related information that manages bus-related information consisting of resources and links expressed on the basis of REST (Representational State Transfer), and retrieves the corresponding information in response to an HTTP-based bus-related information request from the client and responds to the client. Providing device; REST-based bus-related information providing system comprising a. The method of claim 11, The bus-related information includes a REST-based bus-related information providing system, characterized in that at least one of bus information, bus stop information, bus arrival information. The method of claim 12, The bus information retrieved among the bus-related information includes at least one of a bus identifier, a bus name, a dispatch interval, and a route map. The method of claim 12, The bus stop information retrieved from the bus-related information includes at least one of a bus stop identifier, a bus stop name, bus stop location information, and a bus list stopping at the bus stop. The method of claim 12, The bus arrival information retrieved from the bus-related information includes a bus identifier, a bus stop identifier, a bus name, and a bus stop name to inform a predetermined time at which a specific bus arrives at a specific bus stop. system. The method of claim 12, And the client transmits predetermined bus information and bus stop information to the REST-based bus-related information providing apparatus based on HTTP to request bus arrival schedule information. The method of claim 16, The bus information transmitted by the client for requesting bus arrival schedule information is a bus identifier, and bus stop information is a bus-based bus related information providing system, characterized in that the bus stop identifier.

Images