JP5341663B2 - Content providing server system and method thereof - Google Patents

Description

  The present invention relates to a content providing server system that selects a specific back-end server from a plurality of back-end servers that acquire content data in response to a request request from a client terminal, and a method thereof.

  In recent years, countless contents exist on the Internet, and when a request request specified by a URL (Uniform Resource Locator) is made, the target contents are provided to the client terminal.

  By the way, depending on the user agent (for example, browser type or communication carrier type) in the client terminal, the content may not be correctly displayed even if the URL is specified and the management server is accessed. That is, if the user agent of the client terminal does not support the content data creation environment, the content is not displayed accurately.

  In such a case, a technique for providing a guide page for notifying that a user agent of a client terminal cannot display content is disclosed (for example, see Patent Document 1). In this patent document 1, when the user agent supports XML (Extensible Markup Language), a cast site list corresponding to the request request is provided. When the user agent does not support XML, a guide page is provided.

JP 2008-27104 A

  By the way, in patent document 1, the management server (front-end server) accessed by URL had to distribute whether to provide a cast site list or a guidance page. Therefore, in Patent Document 1, the environment of the front-end server has to be changed in order to newly add a distribution condition.

  However, changing the environment of the front-end server may cause various unexpected problems, and depending on the content provider, the environment of the front-end server cannot be changed (for example, in the case of a rental server). is there.

  On the other hand, content can be distributed and provided by newly providing a front-end server different from the current front-end server without changing the environment of the front-end server itself.

  FIG. 7 is a diagram conceptually showing that contents are distributed and provided by newly providing a front-end server. For example, there is a case where it is desired to provide new content by improving the currently operated content. In such a case, the beta version content may be provided as a sample for the user to try before the improved content is officially provided (FIG. 7 (1)).

  At this time, it is necessary to distribute the currently operated version content and the β version content according to the request request. In FIG. 7B, in addition to the currently operated version front-end server 11A. In addition, content distribution is performed by newly providing a front end server 11B for the beta version. As a result, contents can be distributed without changing the environment of the front-end server, but a new front-end server must be added, resulting in a large cost for capital investment.

  Further, from the viewpoint of the user who provides the content, the URL (front-end server address) is different between the case of obtaining the currently operated version of the content and the case of obtaining the beta version of the content. Will be annoying.

  Accordingly, an object of the present invention is to provide a content providing server system and a method for providing a plurality of contents according to one URL without changing the environment of the front-end server.

  (1) A front-end server that accesses a request for content from a mobile terminal with a single URL, and a plurality of back-end servers that respectively execute processing of multiple versions of content corresponding to the request to the front-end server A content table that stores content data; and a back-end proxy server that selects one back-end server from the plurality of back-end servers corresponding to request requests, and the back-end proxy server includes the front-end server. A request receiving unit that receives a request request received from the front-end server, a terminal information acquisition unit that acquires terminal information indicating a type of mobile terminal from the received request request, and a back-end corresponding to the terminal information. A distribution information DB that stores distribution information that defines a server, and a backend selection that refers to the distribution information stored in the distribution information DB and selects a backend server corresponding to the acquired terminal information Means, and a request transmission means for transmitting the request request to the selected back-end server, wherein the back-end server receives content data from the content table in response to the request request received from the back-end proxy server. Content data acquisition means for acquiring the data, and data transmission means for transmitting the acquired content data to the front-end server, wherein the front-end server transmits the received content data to the mobile terminal. Providing content characterized by Server system.

  According to the invention according to (1), when a request request is accessed from a mobile terminal with a URL of 1, the back-end proxy server performs a plurality of back requests corresponding to the request request based on terminal information indicating the type of mobile terminal. Select a specific backend server from the endservers. Then, content data corresponding to the request is acquired by this specific back-end server and provided to the mobile terminal. At this time, the selection of the specific back-end server is performed by a back-end proxy server installed between the front-end server and the back-end server, not the front-end server that directly receives a request request from the mobile terminal. As a result, a plurality of contents can be provided according to one URL without changing the environment of the front-end server. In addition, it can be used regardless of the operating environment such as the production environment and development environment. For example, even if the back-end server has different owners and multiple back-end servers cannot be built with one back-end server, the front-end server environment can be Without changing, a specific back-end server can be selected from a plurality of back-end servers according to one URL, and contents can be provided based on a development environment constructed by the specific back-end server.

  (2) The content providing server system according to (1), further comprising distribution change means for changing distribution information stored in the distribution information DB.

  According to the invention according to (2), the content provider can change the content distribution condition later without changing the environment of the front-end server.

  (3) a front-end server that is accessed with a single URL for a request for content from a mobile terminal, and a plurality of back-end servers that respectively execute processing of a plurality of versions of content corresponding to the request to the front-end server A content providing server system comprising: a content table for storing content data; and a back-end proxy server that selects one back-end server from the plurality of back-end servers corresponding to the request request. The content data is provided in response to a request request received by the front-end server from the front-end server by the back-end proxy server; Acquiring the terminal information indicating the type of mobile terminal from the request, storing the distribution information defining the back-end server corresponding to the terminal information, and referring to the stored distribution information Selecting a back-end server corresponding to the terminal information; and transmitting the request request to the selected back-end server, to the request request received from the back-end proxy server by the back-end server. Accordingly, acquiring content data and transmitting the acquired content data to the front-end server, and transmitting the received content data by the front-end server to the mobile terminal. One characterized by inclusion Law.

  (4) The method according to (3), including a step of changing the stored distribution information.

  According to the invention according to (3), the same effect as the invention according to (1) can be expected, and according to the invention according to (4), the same effect as the invention according to (2) can be expected.

  According to the present invention, it is possible to provide a plurality of contents according to one URL without changing the environment of the front-end server.

It is a figure which shows the outline of the content provision server system which concerns on this invention. It is a block diagram which shows the structure of the back end proxy server which concerns on this invention. It is a figure which shows the outline of the request request | requirement from a mobile terminal. It is a figure which shows an example of distribution information DB which concerns on this invention. It is a flow which shows an example of operation | movement of the content provision server system which concerns on this invention. It is a figure which shows the content of the content provided according to the request request | requirement from a mobile terminal. It is a figure which shows the outline of the conventional content distribution method.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[Outline of content providing server system]
FIG. 1 is a diagram showing an outline of a content providing server system 1 according to the present embodiment. The content providing server system 1 includes a front-end server 11, a back-end proxy server 12, back-end servers 13A, 13B (hereinafter referred to as “back-end server 13” if not distinguished), and a content table 14A. , 14B (hereinafter referred to as “content table 14” if not distinguished).

  The front-end server 11 is a server accessed by a URL. Upon receiving a request request from the mobile terminal 20, the front-end server 11 acquires terminal information of the mobile terminal 20 included in the request request and is associated with the acquired terminal information. The related information is acquired from the front-end server 11 or a DB server (not shown) connectable to the front-end server 11, and the related information associated with the terminal information is added to the request request. Further, the front end server 11 performs an optimization process on the content data corresponding to the request request based on the related information associated with the terminal information, and then returns the content data to the mobile terminal 20. The front-end server 11 is a server whose administrator cannot arbitrarily change its environment.

  Here, the “request request” is information for specifying content desired by the mobile terminal 20 (user), and is specified by the URL.

  The back-end proxy server 12 is provided between the front-end server 11 and the back-end server 13 and receives a request request from the front-end server 11. The back-end proxy server 12 selects a specific back-end server 13 from the plurality of back-end servers 13 according to the received request request. The back-end proxy server 12 transmits a request request to the selected specific back-end server 13, receives content data acquired in response to the request request from the back-end server 13, and transmits it to the front-end server 11.

  The back end server 13 acquires content data corresponding to the request request from the content table 14 and transmits it to the front end server 11 via the back end proxy server 12. Here, in this embodiment, the back-end server 13 is provided with one or a plurality of, for example, one back-end server 13A and one back-end server 13B for one URL. Note that the content data acquired by the back-end server 13A and the back-end server 13B is different. That is, in the present embodiment, even when the mobile terminal 20 accesses the front-end server 11 with one URL, different content may be provided to the mobile terminal 20.

  The content table 14 stores a plurality of content data provided by the content provider.

In the content providing server system 1 according to the present embodiment, a plurality of back-end servers 13 for acquiring content data are provided for the front-end server 11, and a specific back-end server 13 is selected from the plurality of back-end servers 13. Then, different content data is acquired by the selected specific back-end server 13. Here, the specific back-end server 13 is selected not by the front-end server 11 but by the back-end proxy server 12. Therefore, a plurality of content data can be provided by one request request specified by the URL, and it is not necessary to change the environment of the front-end server 11 when distributing the content data.
Hereinafter, the back-end proxy server 12 of the content providing server system 1 according to the present embodiment will be described.

[Configuration of back-end proxy server]
FIG. 2 is a block diagram showing the configuration of the backend proxy server 12.

  The back-end proxy server 12 includes a request reception unit 121, a terminal information acquisition unit 122, a back-end selection unit 123, a distribution information DB 124, a distribution change unit 125, a request transmission unit 126, and a content data reception unit 127. And content data transmission means 128.

  The request receiving unit 121 receives a request request from the mobile terminal 20 from the front end server 11. The request request includes a header information part 151 and a content part 152 as shown in FIG.

  The terminal information acquisition unit 122 acquires terminal information indicating the type of the mobile terminal 20 and related information associated with the terminal information from the received request request. Specifically, terminal information is acquired from the header information part 151 of the request request. “Terminal information” refers to the user agent, subscriber ID, user ID, etc. of the mobile terminal. The “related information associated with the terminal information” is, for example, information indicating that the beta version content before formal provision is desired, and refers to information registered in association with the user ID. The “information associated with the user ID” is stored in the front end server 11 or a DB server connectable to the front end server 11.

  The back-end selection unit 123 refers to the distribution information stored in the distribution information DB 124 and selects the back-end server 13 corresponding to the acquired terminal information.

  The distribution information DB 124 stores distribution information that defines the back-end server 13 corresponding to the terminal information for each request request. FIG. 4 is a diagram illustrating an example of the distribution information DB 124.

  FIG. 4A shows distribution information provided for a request request (www..co.jp /), and defines the type of back-end server 13 corresponding to the user agent. For example, when the communication carrier of the mobile terminal 20 is “X”, the back-end server 13A is selected as the back-end server 13 to which the mobile terminal 20 is allocated. On the other hand, when the communication carrier of the mobile terminal 20 is “Y”, the back-end server 13B is selected as the back-end server 13 that is the distribution destination. Note that different content data is acquired between the back-end server 13A and the back-end server 13B. That is, content data corresponding to the communication carrier “X” is acquired by the back-end server 13A, and content data corresponding to the communication carrier “Y” is acquired by the back-end server 13B. As described above, even when one request request (www.?..co.jp/) is made, different contents are provided to the mobile terminal 20 by the terminal information (user agent) of the mobile terminal 20. Is done.

  FIG. 4 (2) shows distribution information provided for the request request (www. ***. Co.jp/), which defines the type of backend server 13 corresponding to an arbitrary character string. ing. For example, when it is registered in advance that the mobile terminal 20 (user) desires the β-version content, the back-end server 13D is selected as the back-end server 13 that is the distribution destination. On the other hand, if the mobile terminal 20 (user) does not register in advance that the β-version content is desired, the back-end server 13E is selected as the back-end server 13 to which the content is distributed. Then, according to the back-end server 13D, trial version beta content data is acquired, and according to the back-end server 13E, current content data is acquired. In this way, even when one request request (www. ***. Co.jp/) is made, different contents are obtained for the mobile terminal 20 depending on the terminal information (arbitrary character string) of the mobile terminal 20. Is provided.

  With reference to FIG. 2, the distribution changing unit 125 changes the distribution information stored in the distribution information DB 124. For example, when the content provider continuously improves the content and the content is improved, when the β version content is newly provided for trial production, the distribution changing unit 125 stores the distribution information in the distribution information DB 124. Add new distribution information. By providing the distribution changing unit 125 as described above, it is possible to newly add distribution information in a situation where content is continuously provided.

The request transmission unit 126 transmits a request request to the backend server 13 selected by the backend selection unit 123.
The content data receiving unit 127 receives content data acquired by the back-end server 13 in response to the request from the back-end server 13.
The content data transmission unit 128 transmits the received content data to the front end server 11.

[Configuration of Front End Server 11 and Back End Server 13]
Although not shown in the figure, the front-end server 11 is a means for receiving a request request from the mobile terminal 20, a means for transmitting the received request request to the back-end proxy server 12, and the content data corresponding to the request request as a back-end. Means for receiving from the back-end server 13 via the proxy server 12 and means for transmitting the received content data to the mobile terminal 20 are provided.

  Further, the back-end server 13 is a means for receiving a request request from the back-end proxy server 12, a means for acquiring content data from the content table 14 in response to the request request, and the acquired content data via the back-end proxy server 12. Means for transmitting to the front-end server 11.

  Note that all or part of each of the above means can be configured by hardware, software, or both hardware and software. As the hardware, for example, in addition to the CPU, as a storage device, a memory (RAM, ROM), a hard disk (HDD), a magneto-optical disk (CD, DVD, etc.), a communication device, various wired, wireless interface devices, a display device As a general computer, a display (liquid crystal display, plasma display, etc.) and a keyboard, pointing device (mouse, etc.) as appropriate as input devices may be used. The software includes a computer program and data that causes a computer to function as each of the above-described means. The computer program (including data) can be distributed via a communication line, or can be recorded and distributed on a computer-readable medium such as a CD-ROM.

[Processing flow in content providing server system]
Next, the flow of processing performed by the content providing server system 1 will be described with reference to FIG.

  S1 to S4: The mobile terminal 20 transmits a request for content desired by the user. The front-end server 11 acquires related information related to the terminal information from the terminal information (user ID) included in the request request, adds the information to the request request, and transmits the request request to the back-end proxy server 12. To do.

  S5, S6: The terminal information acquisition unit 122 of the backend proxy server 12 analyzes the header information part 151 of the request request, and acquires terminal information and related information.

  S7: The backend selection unit 123 of the backend proxy server 12 refers to the distribution information DB 124 and selects the backend server 13 corresponding to the request request and the terminal information.

  S8: The request transmission unit 126 of the backend proxy server 12 transmits a request request to the selected backend server 13.

  S9 to S11: The back-end server 13 analyzes the request request, refers to the content part 152 of the request request, and acquires the corresponding content data from the content table 14.

  S12 to S13: The back-end server 13 transmits the acquired content data to the front-end server 11 via the back-end proxy server 12.

  S14 to S17: The front-end server 11 optimizes the received content data based on the terminal information and the user-related information, transmits the optimized content data to the mobile terminal 20, and the mobile terminal 20 receives the received content. Display content based on data.

[Operation example]
As described above, a method for selecting a specific back-end server from the content providing server system 1, the back-end proxy server 12, and the plurality of back-end servers that acquire content data in response to a request request from the mobile terminal according to the present embodiment Explained. Hereinafter, an example of these operations will be described with reference to FIG.

  FIG. 6 shows an example of operation when the content provider does not want the beta version in the case where the beta version is created by improving the content currently provided and the user wishes to try this beta version before official operation. (FIG. 6 (1)), an example of an operation when desired (FIG. 6 (2)) is shown. Whether or not the β version is desired is selected in advance by the user, and the information is registered in the front-end server 11 or a DB server connectable to the front-end server 11 in association with the user ID.

  The mobile terminal 20 makes a request request for specifying a URL to the front-end server 11. This request request includes information indicating whether or not the β version is desired. Subsequently, the front-end server 11 transmits a request request to the back-end proxy server 12. The back-end proxy server 12 analyzes the request request header information and determines whether the user of the mobile terminal 20 desires the β version.

  At this time, if the user of the mobile terminal 20 does not desire the β version (FIG. 6 (1)), the back-end proxy server 12 selects the back-end server 13D from the back-end server group, and this back-end server 13D. Send request request to. The back-end server 13D acquires content data corresponding to the request request and transmits the content data to the front-end server 11 via the back-end proxy server 12. Then, the front end server 11 transmits the content data to the mobile terminal 20.

  On the other hand, when the user of the mobile terminal 20 desires the beta version (FIG. 6 (2)), the back-end proxy server 12 selects the back-end server 13E from the back-end server group, and sends it to the back-end server 13E. Send a request request. The back-end server 13E acquires content data corresponding to the request request and transmits the content data to the front-end server 11 via the back-end proxy server 12. Then, the front end server 11 transmits the content data to the mobile terminal 20.

  As a result, when the user of the mobile terminal 20 does not desire the β version, the content 171 is displayed on the display unit of the mobile terminal 20, and when the user of the mobile terminal 20 desires the β version, the content 171 is different. Content 172 is displayed.

  As described above, in the present embodiment, a plurality of different contents can be provided for one request request without changing the environment of the front-end server 11.

  As mentioned above, although embodiment of this invention was described, this invention is not restricted to embodiment mentioned above. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

DESCRIPTION OF SYMBOLS 1 Content provision server system 11 Front-end server 12 Back-end proxy server 13 Back-end server 14 Content table 121 Request reception means 122 Terminal information acquisition means 123 Back-end selection means 124 Distribution information DB
125 Distribution change means 126 Request transmission means 127 Content data reception means 128 Content data transmission means

Claims (4)

A front-end server to which a request for content from a mobile terminal is accessed with a single URL, a plurality of back-end servers that respectively execute processing of a plurality of versions of content corresponding to the request to the front-end server, and content data And a back-end proxy server that selects one back-end server from the plurality of back-end servers corresponding to request requests,
The backend proxy server is
Request receiving means for receiving a request request received by the front-end server from the front-end server;
Terminal information acquisition means for acquiring terminal information indicating the type of mobile terminal and related information from the received request request;
And sorting information DB that stores distribution information which defines the back-end server that corresponds to an arbitrary character string included in the user agent and the related information included in the terminal information,
Referring to the distribution information stored in the distribution information DB, the user agent is included in the acquired terminal information, the user in the case does not contain the arbitrary character string to the related information When a back-end server corresponding to an agent is selected , and the user agent is included in the terminal information and the arbitrary character string is included in the related information, a back end corresponding to the arbitrary character string Backend selection means for selecting a server ;
Request transmitting means for transmitting the request request to the selected back-end server;
With
The backend server is
Content data acquisition means for acquiring content data of a type corresponding to the user agent or content data of a display format corresponding to the arbitrary character string from the content table in response to a request request received from the back-end proxy server; ,
Data transmitting means for transmitting the acquired content data to the front-end server;
With
The content providing server system, wherein the front-end server includes transmission means for transmitting the received content data to the mobile terminal.   The content providing server system according to claim 1, further comprising distribution changing means for changing distribution information stored in the distribution information DB. A front-end server to which a request for content from a mobile terminal is accessed with a single URL, a plurality of back-end servers that respectively execute processing of a plurality of versions of content corresponding to the request to the front-end server, and content data A content providing server system comprising: a content table that stores information; and a back-end proxy server that selects one back-end server from the plurality of back-end servers corresponding to the request request, in response to a request request from a mobile terminal Providing content data,
By the backend proxy server,
Receiving a request request accepted by the front-end server from the front-end server;
Obtaining terminal information indicating the type of mobile terminal and related information from the received request request;
And storing the sorting information defining the back-end server that corresponds to an arbitrary character string included in the user agent and the related information included in the terminal information,
Referring to the stored the allocation information, the back-end server the user agent is included in the acquired terminal information, wherein, when does not contain the arbitrary character string to the related information corresponding to the user agent Selecting the back-end server corresponding to the arbitrary character string when the user agent is included in the terminal information and the arbitrary character string is included in the related information ;
Sending the request request to the selected back-end server;
Including
By the backend server,
In response to a request received from the backend proxy server, acquiring content data of a type corresponding to the user agent or content data of a display format corresponding to the arbitrary character string;
Transmitting the acquired content data to the front-end server;
Including
By the front-end server,
Transmitting the received content data to the mobile terminal.   The method according to claim 3, further comprising changing the stored distribution information.

Images