JP2005267015A - Server device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a server device capable of flexibly restraining browsing. <P>SOLUTION: A proxy server part 7b holds restrained URL lists 41-43 storing URL of web pages having educationally harmful effect by each group. When HTTP request is received from a user agent through a WAP gateway 7a, a user acquires the restrained URL list name on which the access is limited by the user, in reference to the access information 44 storing the restrained URL list names on which the access is restrained by each user, and determines whether the Request-URI included in the HTTP request is included in the restrained URL list or not. When it is included in the designated restrained URL list, an error response is returned to the user agent. <P>COPYRIGHT: (C)2005,JPO&NCIPI

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.
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>

Conventionally, in a web service in a mobile communication system as described above, browsing of a specific web page can be restricted. That is, each user can set whether or not to suppress browsing of an unfavorable web page, and when the user selects to suppress browsing, the user does not want to browse The URL described in the list in which the URL (uniform resource locator) of the page is described cannot be accessed.
However, the above list is set system-wide, and for each user, detailed settings are set such that a specific group or genre is desired to be suppressed but other groups or genres need not be suppressed. I couldn't.
In addition, when the third generation service is started, a mobile terminal that has been provided with a mobile terminal compatible with the standard of each mobile carrier and a mobile terminal that supports WAP / MMS (hereinafter simply referred to as “WAP compatible”). Terminal ")). For such WAP-compatible terminals, it is required that the user can flexibly suppress browsing.

  Accordingly, an object of the present invention is to provide a server device that can flexibly suppress browsing.

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, Means for storing a plurality of suppression target lists in which URLs whose access should be suppressed are recorded, and a browsing restriction target list for designating a target for which browsing is restricted for each user by the suppression target list; and the mobile communication network When an HTTP request for requesting content on an origin server connected to the IP network is received from a connected mobile terminal, the user is set with reference to the browsing restriction target list of the user And means for restricting access to the URL.
The inhibition target list is provided for each genre.

  According to the server device of the present invention, each user can arbitrarily select a list to be inhibited, and the user's selection can be varied.

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) that centrally manages user information and information (UE-Profile) related to mobile terminal capabilities, etc., and provides necessary information in response to requests from clients (such as server device 7) & Repository Manager).

  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.

  A web gateway (WGW) 11 is connected to the subsequent stage of the server device (WAP-GW and JSP) 7 and mediates a request from a client with the origin server 13. Reference numeral 12 denotes the Internet, to which an origin server (Origin Server: a server in which a designated resource exists or is generated) 13 such as a content provider is connected.

The information management server (R2M) 8 will be described with reference to FIG. In the figure, the server device (WAP-GW and JSP) 7 is divided into a WAP gateway unit (WAP-GW) 7a and a proxy server unit (JSP) 7b. Further, the RADIUS server 8a in the R2M8 is not clearly shown.
As shown in the figure, the R2M 8 includes a database (RAD Master) 20 that holds session information for each user managed by the RADIUS server 8a, and a user ID (UID: User) uniquely assigned to the mobile carrier assigned to the subscriber. ID) etc., whether or not the user has agreed, and whether or not the user has URL (Uniform Resource Locators) to be suppressed, self-care profile (Selfcare-Profile) information consisting of unique information related to user settings CC / PP specification (http://www.w3.org/) that stores the model name and performance and capability parameters of the mobile terminal 1 for each model. CC / PP Repository (Composite Capability / Preference Profile Repository) 22 which is a database compliant with Mobile / CCPP /) and the self A mobile terminal manufacturer in which mobile terminal information (UE-Profile) including care DB21, the CC / PP repository 22, the directory replica server (DRS) 10, or information indicating model information and performance is stored. Referring to the profile repository (Profile Repository) 30 that is the database being constructed, session information (Acct-Profile) for the user during the session, user agent profile information (UA-Profile), mobile terminal information (UE -Profile), self-care profile information (Selfcare-Profile), and profile information (Profile) 23 that is cached in memory for the duration of the session by creating profile information consisting of user information (User-Profile) In response to a request from the proxy server (JSP) 7b or the like. It is made to be able to provide information flexibly.
Here, information such as the MSISDN (subscriber telephone number) of the user and a URL deterrence flag indicating whether or not the user has set deterrence of access to a specific web page is recorded in the self-care DB 21. Yes.

The proxy server unit 7b stores a plurality of lists (inhibition URL lists) in which URLs whose contents are not preferable for education are recorded by group or genre (inhibition URL list). Also stored is access information for each user in which the target URL is designated by information indicating the suppression URL list.
FIG. 3 is a diagram illustrating the suppression URL list and the access information.
In this figure, 41 to 43 are deterrence URL lists, 41 is a URL list of web pages with violent depiction, 42 is a URL list of web pages with sexual depiction, and 43 is a dating site. Each URL list, such as a URL list, is created for each genre and stored in the proxy server unit 7b. It should be noted that web pages other than those listed here, such as Internet casinos, can also be targeted for inhibition. Moreover, it is not restricted to the group divided according to genre, It is good also as a group by another reference | standard.
Reference numeral 44 denotes access information for each user stored in the R2M8. As shown in this figure, for each MSISDN indicating each user, the suppression URL list to be the suppression target is recorded. In the illustrated example, the URL included in the suppression URL list 41 and 42 is set as a suppression target for the user of MSISDN1, and the URL recorded in the suppression URL list 41 is the suppression target for the user of MSISDN2. Yes. In this example, the suppression URL list designated by each user is stored using MSISDN as a key, but IMSI or UID may be used.

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.
When the mobile terminal 1 is a WAP compatible terminal and only the international identification number (IMSI: International Mobile Subscriber Identity) assigned to the subscriber of the mobile terminal 1 is attached to the “Activate PDP Context Request”, the SGSN 5 An inquiry request is sent to the HLR (not shown) by this IMSI, and the mobile terminal ISDN (Mobile Station ISDN number) is acquired. Then, “2) Create PDP Context Request” with IMSI and MSISDN attached is generated and sent to GGSN 6.

  The GGSN 6 that has received “2) Create PDP Context Request” authenticates the user and sends a RADIUS accounting request “3) Radius Accounting Request (Accounting-start)” to the RADIUS server 8a in the information management server (R2M) 8. Is sent out. The issued IP address, MSISDN or IMSI is attached to the RADIUS accounting request.

  Upon receiving “3” Radius Accounting Request (Accounting-start) ”, the RADIUS server 8a registers the information attached thereto in the database (RAD Master) 20 as session information for each user ((1) in FIG. 2). At the same time, "4" Radius Accounting Replication "is sent to the WAP-GW 7a of the server device 7 to hold a copy (replica) of the session information ((2) in FIG. 2). Here, the held session information includes at least the IP address, MSISDN, and IMSI of the client (UE). The RADIUS server 8a generates “5) Save Profile Request” and sends it to the profile unit 23 of the information management server (R2M) 8 to save the session information.

The profile unit 23 of the R2M8 sends “6) acquisition User-Profile” to the directory replica server (DRS) 10 and acquires user information (User-Profile) of the user using MSISDN or IMSI as a key. The User-Profile 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 required). . The items to be acquired can be added / deleted by a setting file or the like.
Furthermore, with MSISDN or IMSI as a key, whether self-care information (Selfcare-Profile) from the self-care DB 21, that is, whether the user has agreed to notification of a user ID (UID), etc., whether the user has a URL to be regulated In addition to acquiring unique information relating to user settings such as the mobile terminal information (UE-Profile) from the CC / PP repository 22 ((3) in FIG. 2). When there is no entry for which the inquiry is requested in the CC / PP repository 22, an inquiry is made to the profile repository 30 and the mobile terminal information (UE-Profile) is stored in the CC / PP repository 22. . The profile unit 23 caches the acquired information and the aforementioned user agent information in the memory as profile information.

When the RADIUS server 8a receives the response “Radius Accounting Replication Res” corresponding to the “4” Radius Accounting Replication ”from the WAP-GW 7a, 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 gateway 7a to establish a TCP session.
When the TCP session is established, the user agent transmits an HTTP request “7) HTTP Req” for acquiring content from the origin server 13 ((4) in FIG. 2). The header of the HTTP request includes an IP address (client IP address) issued from the GGSN 6, a URI (Request-URI) of the origin server 13 that is a destination of content acquisition, and user agent information (User-Agent) Or at least user agent profile information (UA-Profile) is included.

  The WAP-GW 7a that has received the “7) HTTP Req refers to the session information replica stored as described above, the corresponding session information replica exists, and the subscriber information matches. Only when the HTTP request is accepted. Then, the HTTP request “8) HTTP Req” including Request-URI, MSISDN, and IMSI in the header is passed to the proxy server unit 7b. Here, if the received “7) HTTP Req” header includes user agent information or UA-Profile information, the WAP-GW 7 a sends the user agent information or UA-Profile information to the profile unit 23. The profile information related to the mobile terminal 1 that sent “7) HTTP Req” is complemented.

  The proxy server unit 7b that has received “8) HTTP Req performs profile information acquisition and complement“ 9) acquisition & complement profile ”with the profile unit 23 of the R2M8. That is, the profile information relating to the user cached in the profile unit 23 is acquired ((5) in FIG. 2). Here, when the URL suppression flag in the self-care profile information is set, the access information (44 in FIG. 3) is referenced with the user's MSISDN as a key, and the user should restrict access. The suppression URL list name set as is acquired. Then, it is determined whether or not the Request-URI included in the HTTP request matches the URL in the set suppression URL list. If they match, an error response ( HTTP Status Code 403 Forbidden) is returned. In this way, it is possible to suppress browsing of undesirable web pages.

When Request-URI is not included in the suppression URL list set by the user (not subject to suppression), the mobile terminal information (UE-Profile) is complemented to the extension header of “8) HTTP Req” If necessary, the HTTP extension header is supplemented based on the mobile terminal information (UE-Profile) of the profile information acquired from the profile unit 23 ((6) in FIG. 2). ).
That is, a user agent in a mobile terminal corresponding to a mobile carrier's own standard sends out various HTTP extension headers uniquely defined by the mobile carrier, but in a WAP-compatible terminal, It is not possible to send an extended header. Therefore, when the specified character string is included in a part of the User-Agent header of the HTTP request, the proxy server unit 7b determines that the mobile terminal that sent the HTTP request It is determined that the mobile terminal is compatible with the standard, and when it is not included, it is determined that the terminal is a WAP compatible terminal. For HTTP requests from WAP-compatible terminals, the profile information stored in the profile unit 23 or the like is used to complement the mobile terminal information that is lacking in the extension header of the received HTTP request, and so on. Transfer to the 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.

Next, the proxy server unit 7b transmits “10) HTTP Req” to which at least the extension header and the Request-URI are attached to the origin server 13 via the WGW 11 ((7) in FIG. 2).
The origin server 13 sends an HTTP response for returning the requested content to the proxy server unit 7b ((8) in FIG. 2). At this time, the origin server 13 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.
In this way, the proxy server unit 7b that has acquired the content requested from the mobile terminal 1 refers to the mobile terminal information indicating the performance of the mobile terminal 1 that requested the content, and if necessary, Based on this, content conversion processing is performed so that the performance of the mobile terminal 1 can be fully exhibited (FIG. 2 (9)).
Next, the WAP-GW 7a sends an HTTP response for returning the converted content to the user agent via the GGSN 6 ((10) in FIG. 2).
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 7a 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.

  As described above, according to the present invention, a plurality of types of deterrence URL lists corresponding to groups such as genres are created, and each user can arbitrarily set which group belongs to a deterrence target. Can do. Therefore, it is possible to restrict access flexibly. For example, when using a suppression URL list that each user has created independently, the burden of creating the suppression URL list is heavy, and it is necessary to maintain a suppression URL list for each user. However, according to the present invention, it is possible to restrict access flexibly with a minimum amount of information.

It is a block diagram which shows the whole structure of the mobile communication system of this invention. It is a figure for demonstrating an information management server (R2M). It is a figure which shows the example of a suppression URL list and access information. It is a figure which shows the principal part of a sequence when using a web service from a mobile terminal.

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), 7a: WAP gateway unit (WAP-GW), 7b: Proxy server unit (JSP), 8: Information management server (R2M), 8a: RADIUS server, 9: Directory server (DIR), 10: Directory replica server (DRS), 11: Web gateway (WGW), 12: Internet, 13: Origin server, 41, 42, 43: Deterrence URL list, 44: Each User access information

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,
Means for storing a plurality of suppression target lists in which URLs whose access should be suppressed are recorded, and a browsing restriction target list for designating a target for which browsing is restricted for each user by the suppression target list;
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, refer to the browsing restriction target list of the user, and And a means for restricting access to a URL set for the user.   The server device according to claim 1, wherein the inhibition target list is provided for each genre.

Images