JP4467340B2 - Server device - Google Patents

Description

  The present invention relates to a server device in a mobile communication system that can be connected to the Internet from a mobile terminal such as a mobile phone.

2. Description of the Related Art Conventionally, mobile communication systems that can connect to the Internet from mobile terminals such as mobile phones have been operated. However, in the conventional mobile communication system, a unique specification is adopted for each mobile communication carrier. For example, a mobile communication provider provides a unique service by using a uniquely defined HTTP extension header.
In recent years, so-called third-generation mobile phone services are being introduced. In this third-generation mobile communication system, standardization is being promoted so that the same mobile terminal can be used in common all over the world. The WAP (Wireless Application Protocol) and MMS (Multimedia Messaging Service) standards are adopted as common specifications (Non-patent Document 1).
The WAP Forum Ltd., "WAP 2.0 Technical White Paper", [online], (Jan. 18, 2002), [searched on November 15, 2003], Internet <URL: http://www.wapforum.org/what /WAPWhite_Paper1.pdf>

In mobile communication systems, web gateways (WGWs) that mediate requests from clients to the origin server when accessing the web are provided in each region. When using a web service, a mobile terminal compatible with the original standard is connected to the Internet via a WGW in the region to which the mobile terminal belongs.
When the third generation service is started, a mobile terminal corresponding to a standard provided by each mobile carrier and a mobile terminal compatible with WAP / MMS (hereinafter simply referred to as “WAP compatible terminal”). ) And exist.
However, the WAP compatible terminal does not correspond to the standard unique to the mobile communication carrier, and is not designed to select and use the WGW in the area to which the terminal belongs.
Therefore, for example, when a user of a WAP-compatible terminal contracted in Tokyo uses a web service in Hokkaido, the request will be processed by the WGW in Hokkaido. Traffic processing based on it becomes impossible. As a result, a difference occurs in the load on the server, and as a whole, system resources are wasted.

  Therefore, an object of the present invention is to provide a server device that can prevent waste of system resources by processing a user request with an appropriate gateway device.

In order to achieve the above object, a server device of the present invention is a server device connected to a gateway device provided between a mobile communication network and an IP network such as the Internet and the mobile communication network, The gateway device is provided for each region, and when receiving an HTTP request for requesting content on an origin server connected to the IP network from a mobile terminal connected to the mobile communication network, Means for acquiring a domain name corresponding to the user's subscription area from a database for managing information relating to the user of the mobile terminal; and when the domain name is not specified in the HTTP request, the acquired domain name is the HTTP By complementing the request's host header, the HTTP request It said provided corresponding to the region and has a means for routing to the gateway device.
The domain name corresponding to the user's subscription area is acquired by referring to a database that manages information related to the user of the mobile terminal using the IMSI or MSISDN of the user as a key.

According to the server device of the present invention, for example, a request from a subscriber contracted in Tokyo is processed by a gateway device in Tokyo, regardless of the area where the subscriber uses the web service, and a request from a subscriber in Osaka. Is processed by an Osaka gateway device, it becomes possible to process traffic based on the prediction of the number of subscribers for each WGW, and waste of system resources can be prevented. Therefore, the ubiquity and irregularity risk of receiving requests can be avoided, and the server configuration and processing performance based on subscriber prediction can be fully utilized.
It is also possible to acquire statistical information for each subscriber area with high accuracy.

FIG. 1 is a block diagram showing the overall configuration of an embodiment of a mobile communication system of the present invention.
In this figure, 1 is a mobile terminal (UE: User Equipment) such as a mobile phone, 2 is a radio base station (BTS: Base Transceiver Station) to which the mobile terminal 1 is connected, and 3 is a plurality of radio base stations 2. Radio base station controller (RNC) to be managed (RNC) 4 is a mobile service switching center (MSC) that performs call connection control and service control of the mobile terminal 1, and 5 is the radio base station control A gateway (SGSN: Serving GPRS Support Node) between the device (RNC) 3 and the core network (packet network), and 6 is a gateway (GGSN: Gateway GPRS Support Node) between the core network (packet network) and the IP network.

7 terminates the WAP2.0 protocol from the mobile terminal (UE) 1 and transfers it to the origin server side using HTTP (HyperText Transfer Protocol) (WAP-GW: WAP-Gateway), and A server having a proxy server (JSP: J-Phone Scheme Proxy) that coordinates the WAP standard function and the extended function by the mobile carrier by converting the received request into an appropriate format and sending it to the subsequent stage. Device (WAP-GW and JSP).
8 includes a RADIUS server 8a that terminates the RADIUS Accounting protocol from the GGSN 6 and performs session management and session log generation for each user, and WAP / MMS service subscribers use services such as web and mail. Information management server (R2M: RADIUS & Repository Manager) that centrally manages user information and information related to mobile terminal capabilities and provides necessary information in response to requests from clients (such as server device 7) is there.

  Reference numeral 9 denotes a directory server (DIR) that centrally manages all subscriber information. This subscriber information is shared between all generations and all regions, and the DIR 9 is the information source of the DRS 10. Reference numeral 10 denotes a directory replica server (DRS) that copies subscriber information locally from the DIR 9 at regular intervals (for example, every minute) and maintains the subscriber information in response to a query request. Provide information. As a result, even when DIR 9 fails, services (except for order entry) can be continuously provided.

11, 12 and 13 are Web gateways (WGWs) connected to the subsequent stage of the server device (WAP-GW and JSP) 7 and mediating requests from clients with the origin server 15. , Provided for each region. In this figure, three WGWs 11 to 13 are representatively shown, but actually, a larger number (for example, nine) WGWs are provided.
Further, reference numeral 14 denotes the Internet, to which an origin server (origin server: a server in which a specified resource exists or is generated) 15 such as a content provider is connected.

A sequence when a web service is used from a mobile terminal in the mobile communication system of the present invention configured as described above will be described with reference to FIG.
When a user agent (UA) such as a web browser operating on the mobile terminal (UE) 1 acquires web content, “1) Activate PDP Context Request” is sent to the SGSN 5.
The SGSN 5 receives “1)“ Activate PDP Context Request ”from the mobile terminal 1, generates“ 2) Create PDP Context Request ”, and sends it to the GGSN 6.

  Upon receiving “2) Create PDP Context Request”, the GGSN 6 issues an IP address to be assigned to the mobile terminal 1, and sends a RADIUS accounting request “3) Radius Accounting to the RADIUS server 8 a in the information management server (R2M) 8. Request (Accounting-start) "is sent. In the RADIUS accounting request, the issued IP address, MSISDN (Mobile Station ISDN number) of the mobile terminal 1 or IMSI (International Mobile Subscriber Identity) are attached.

  Upon receiving “3) Radius Accounting Request (Accounting-start)”, the RADIUS server 8a manages the information attached thereto as session information for each user and “4) Radius Accounting Replication” as the server device (WAP). -GW and JSP) 7 to hold a copy (replica) of the session information. Here, the held session information includes at least the IP address, MSISDN, and IMSI of the client (UE).

  Further, the R2M8 sends “5) acquisition User-Profile” to the directory replica server (DRS) 10 and acquires the user information (User-Profile) of the user using MSISDN or IMSI as a key. The user information acquired at this time can be all items of the entry or only specified items (MSISDN, IMSI, user ID (UID), WAP subscriber flag, and subscriber area code are essential). At this time, the subscriber area code acquired from the DRS 10 is stored as a corresponding domain name using a predetermined conversion table.

When the RADIUS server 8 a receives a response “Radius Accounting Replication Res” corresponding to the “4) Radius Accounting Replication” from the WAP-GW and JSP 7, it sends “Radius Accounting Res” to the GGSN 6. In response, the GGSN 6 transmits “Create PDP Context Response” to which the IP address assigned to the client (UE) is attached to the SGSN 5.
Thereafter, a TCP (Transmission Control Protocol) handshake is performed between the user agent (UA) and the WAP-GW and JSP 7 to establish a TCP session.
When the TCP session is established, the user agent sends an HTTP request “6) HTTP Req” for acquiring content from the origin server 15. The header of the HTTP request includes at least URI (Request-URI), user agent information (User-Agent), or profile information (UA-Prof) indicating the UE capability of the origin server 15 that is a destination of content acquisition. include.

  The WAP-GW and JSP 7 that received “6) HTTP Req refer to the session information replica stored as described above, the corresponding session information replica exists, and the subscriber information matches. The HTTP request is accepted only when the request is made. If UA-Prof information is included in the received header of “6) HTTP Req”, the profile information related to the mobile terminal 1 that transmitted “6) HTTP Req” is complemented.

As described above, the user agent in the mobile terminal corresponding to the mobile carrier's own standard sends out various HTTP extension headers uniquely defined by the mobile carrier, but in the WAP compatible terminal, Such an extension header cannot be transmitted. Therefore, using the profile information stored in R2M8, the mobile terminal information that is lacking in the extension header of the received HTTP request is complemented and transferred to the subsequent node. As a result, a service equivalent to a mobile terminal compatible with a mobile carrier's original standard can be provided to a WAP compatible terminal.
In other words, the WAP-GW and JSP 7 that have received the HTTP request “6) HTTP Req” from UE1, which is a WAP-compatible terminal, perform profile information acquisition and complement “7) acquisition & Complement Profile” with the R2M8. . That is, the profile information related to the user cached in R2M8 is acquired, and the mobile terminal information (UE-Profile) required in the extension header of “6) HTTP Req is insufficient is acquired. The HTTP extension header is complemented based on the mobile terminal information (UE-Profile) of the profile information.

Next, the WAP-GW and JSP 7 transmit “8) HTTP Req” to which at least the extension header and the Request-URI are attached to any of the WGWs 11 to 13.
Here, in the present invention, in the processing of “7) acquisition & complement profile”, a domain name corresponding to the region to which the user belongs is acquired. If only the host name is specified in the Request-URI or Host / Domain Part of the host header in “6) HTTP Req” and the domain name is not specified, the acquired domain name is included in the HTTP request. Complementing the host header, an HTTP request “8) HTTP Req” is sent to the WGW corresponding to the area.

FIG. 3 is a diagram for explaining the situation. As described above, the WAP-GW and the JSP 7 acquire a domain name indicating the region to which the user belongs from the R2M8 based on the MSISDN or IMSI obtained from the stored session information replica. If the HTTP request is a request from a WAP-compatible terminal and the domain name is not specified in the host header, the acquired domain name is complemented with the Host header of “8) HTTP Req”. As a result, the HTTP request is routed to the WGWs 11 to 13 corresponding to the region to which the user belongs. For example, in the illustrated example, when the contract subscription area of the user is Kansai and the domain name is “k.aaaaaa.ne.jp”, “k.aaaaaa.ne” is added to the host header of the HTTP request from the user. “.jp” is complemented, and the request is routed to the WGW 11 (“k.aaaaaa.ne.jp”) corresponding to the Kansai region.
The WGW 11 that has received the HTTP request establishes a TCP session with the origin server 15, and sends the HTTP request to the origin server 15.
In this way, an HTTP request is transmitted to the origin server 15 via the WGWs 11 to 13 corresponding to the region to which the user belongs.

The origin server 15 sends an HTTP response that returns the requested content to the WGWs 11-13. At this time, the origin server 15 can know the performance of the mobile terminal 1 by referring to the extension header of the HTTP request, and returns content corresponding to the performance so that the performance of the mobile terminal 1 can be fully exhibited. can do.
The WGW that has received the HTTP response from the origin server 15 relays the HTTP response to the WAP-GW and JSP 7.
In this way, the WAP-GW and JSP 7 that acquired the content requested from the mobile terminal 1 refer to the mobile terminal information indicating the performance of the mobile terminal 1 that requested the content, and if necessary, this mobile terminal information. The content conversion processing is performed so that the performance of the mobile terminal 1 can be fully exhibited based on the above.
Next, the WAP-GW and JSP 7 send an HTTP response that returns the converted content to the user agent via the GGSN 6.
The user agent that has received the HTTP response displays the acquired content, and the TCP session between the user agent and the WAP-GW and JSP 7 is terminated. Next, Radius Accounting Req (Accounting-stop) is transmitted from the GGSN 6 in response to a communication termination request for terminating communication from the user agent. The RADIUS server 8 a that has received this request discards the corresponding RADIUS information and sends Radius Accounting Res to the GGSN 6. Thereby, the communication between the user agent and the server device (WAP-GW and JSP) 7 is completed.

Thus, even a request from a WAP-compatible terminal can receive the same service as a request from a mobile terminal corresponding to the mobile carrier's own standard.
An HTTP request from a WAP-compatible terminal is also routed to a web gateway in the region to which it belongs, and it is possible to prevent waste of system resources.

It is a block diagram which shows the whole structure of the mobile communication system of this invention. It is a figure which shows the principal part of a sequence when utilizing a web service from a mobile terminal. It is a figure for demonstrating the routing to WGW.

Explanation of symbols

  1: mobile terminal (UE), 2: radio base station (BTS), 3: radio base station controller (RNC), 4: mobile communication switching center (MSC), 5: gateway (SGSN), 6: gateway (GGSN) ), 7: Server device (WAP-GW and JSP), 8: Information management server (R2M), 8a: RADIUS server, 9: Directory server (DIR), 10: Directory replica server (DRS), 11, 12, 13: Web gateway (WGW), 14: Internet, 15: Origin server

Claims (2)

A gateway device provided between a mobile communication network and an IP network such as the Internet, and a server device connected to the mobile communication network,
The gateway device is provided for each region,
When an HTTP request for requesting content on an origin server connected to the IP network is received from a mobile terminal connected to the mobile communication network, the user from the database that manages information related to the user of the mobile terminal means for obtaining a domain name that corresponds to the subscription area of,
When the not specified domain name in the HTTP request, by complementing the domain name the acquired host header of the HTTP request, the HTTP request to the gateway device provided corresponding to the region And a routing device. The domain name corresponding to the user's subscription area is obtained by referring to a database that manages information related to the user of the mobile terminal using the IMSI or MSISDN of the user as a key. Item 2. The server device according to Item 1.

Images