JP5659599B2 - Mobile communication system, subscriber control server, and subscriber information operation method - Google Patents

Description

  The present invention relates to a mobile communication system, a subscriber control server, and a subscriber information operation method.

  FIG. 36 is a configuration diagram of a mobile communication system described in Non-Patent Document 1, for example, a mobile communication system 1 of 3GPP (3rd Generation Partnership Project). The mobile communication system 1 is managed by a mobile operator that provides mobile communication services. The mobile communication system 1 includes at least a mobile terminal 100, a subscriber management server 200, and a mobility management node 300.

  The mobile terminal includes a radio interface and connects to the core network via a radio base station (not shown in FIG. 36). In addition, the mobile terminal 100 includes a slot for inserting a UICC (Universal Integrated Circuit Card). The UICC stores a subscriber ID (Identifier) for identifying the subscriber. The mobile terminal 100 stores this subscriber ID in the connection request signal and notifies the core network. Examples of the subscriber ID include IMSI (International Mobile Subscriber Identity).

  The subscriber management server 200 manages subscriber information related to subscribers. The subscriber management server 200 corresponds to HSS (Home Subscriber Server) in, for example, 3GPP.

  FIG. 37 is a diagram showing the contents of the subscriber information managed by the subscriber management server 200 as described in Non-Patent Document 1. The subscriber information is database-managed using a subscriber ID (for example, IMSI) as a key, and includes basic contract information, connection destination PDN (Packet Data Network) information, and the like. The basic contract information includes information such as a charging method, access restriction, femtocell (CSG ID: Closed Subscriber Group ID) that can be connected, and the maximum total bit rate (Aggregated Max Bit Rate) that the mobile terminal 100 can use. Further, the connection destination PDN information is managed as a PDN subscription context for each connection destination PDN. Each PDN subscription context includes detailed information such as charging and communication quality.

  The mobility management node 300 mediates authentication processing of the mobile terminal 100 and controls communication of the mobile terminal 100. The communication control policy in the mobility management node 300 is determined based on the subscriber information corresponding to the subscriber ID notified from the mobile terminal 100. Then, the mobility management node 300 acquires subscriber information from the subscriber management server 200. The mobility management node 300 corresponds to MME (Mobility Management Entity) in 3GPP, for example.

  FIG. 38 shows the contents described in Non-Patent Document 1, and describes the processing of the mobile communication system 1 (processing from connection request transmission of the mobile terminal 100 to determination of the communication control policy of the mobility management node 300). FIG.

  The mobile terminal 100 transmits a connection request (Attach Request in the case of 3GPP) to the mobility management node 300 during the initial connection process (step S100). In this case, the subscriber ID (for example, IMSI) of the mobile terminal 100 is stored in the connection request.

  The mobility management node 300 transmits a subscriber information request including the above subscriber ID (Update Location Request in the case of 3GPP) to the subscriber management server 200 (step S101).

  The subscriber management server 200 searches the database to obtain subscriber information corresponding to the subscriber ID stored in the received subscriber information request (step S102). The subscriber management server 200 manages the movement of a subscriber information response (Update Location Ack in the case of 3GPP) including the subscriber ID stored in the subscriber information request and the subscriber information corresponding to the subscriber ID. It transmits to the node 300 (step S103).

  The mobility management node 300 applies the subscriber information as a communication control policy for the subscriber ID, and establishes a communication path (bearer) based on the communication control policy (step S104).

  On the other hand, although not shown in FIG. 38, when the communication environment of the mobile terminal 100 is changed after the connection process is completed, the mobile terminal 100 requests the mobile management node 300 to update the communication environment including the subscriber ID. Can also be sent. Examples of the communication environment update request include, for example, Tracking Area Update Request and Routing Area Update Request in 3GPP. As a result, the communication control policy of the mobility management node 300 is updated according to the subscriber information managed by the subscriber management server 200, and the mobility management node 300 communicates with the communication path ( (Bearer) is updated or updated.

  On the other hand, Patent Document 1 describes a subscriber information management server that manages subscriber information of a wireless communication service. Further, Patent Document 2 describes that when a failure occurs in a certain network device, an operation ID, which is a unique code, is given to the administrator who manages the network device from the network management apparatus side. To do.

3GPP TS 23.401 V9.4.0 “General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN)”

JP 2009-207008 A JP 2005-141772 A

  In the technique described in Non-Patent Document 1 described with reference to FIGS. 36 to 38, the determination of the communication control policy for the mobile terminal 100 of the mobility management node 300 is based on the subscriber information managed by the subscriber management server 200. It is determined. Therefore, when adding, deleting, or changing a communication control policy, it is necessary to add, delete, or change subscriber information on the subscriber management server 200. However, in the case of the technique described in Non-Patent Document 1, when changing the subscriber information, an authentication process is required to determine whether the change authority is held. Also, changing the subscriber information requires complicated input processing such as selection and determination of change items. From the above, it is not easy for the user to operate (addition, deletion, or change) of the subscriber information. Furthermore, when changing subscriber information, it may be necessary to prepare for connection to a subscriber change site managed by a mobile operator. That is, there is a problem that the subscriber information cannot be operated at the time of initial connection.

  On the other hand, even if only the techniques described in Patent Document 1 and Patent Document 2 or a combination thereof, the above-described problem (that is, the operation of subscriber information is not easy and the timing is limited) is solved. It is difficult.

  An object of the present invention is to provide a mobile communication system, a subscriber control server, and a subscriber information operation method capable of operating subscriber information easily at any timing including the initial connection. .

  The mobile communication system of the present invention includes a subscriber management server that manages subscriber information for each subscriber identifier, and a subscriber control server that can operate the subscriber information, and the subscriber control server includes: A database that stores the operation content for the subscriber information in association with a right identifier for identifying the operation content, and is transmitted from a predetermined communication node via the subscriber management server by referring to the database. A control unit that specifies an operation content corresponding to the right identifier included in the request signal, and transmits the specified operation content to the subscriber management server, wherein the subscriber management server includes: The subscriber information is operated based on the received operation content.

  The subscriber control server of the present invention stores an operation content for subscriber information held in the subscriber management server in association with a right identifier for identifying the operation content, and refers to the database. Control means for specifying an operation content corresponding to the right identifier included in a request signal transmitted from a predetermined communication node via the subscriber management server and transmitting the specified operation content to the subscriber management server; Is provided.

  In the subscriber information operation method of the present invention, the operation contents for the subscriber information held in the subscriber management server are stored in a database in association with a right identifier for identifying the operation contents, and the database is referred to. The operation content corresponding to the right identifier included in the request signal transmitted from the predetermined communication node via the subscriber management server is specified, and the specified operation content is transmitted to the subscriber management server, In the subscriber management server, the subscriber information is operated based on the specified operation content.

  According to the present invention, it is possible to easily operate subscriber information at an arbitrary timing including the initial connection.

1 is a system configuration diagram for explaining a configuration example of a mobile communication system according to a first embodiment of the present invention. It is a block diagram explaining the structural example of the subscriber control server shown in FIG. It is an example of the content of the control right ID content management table which comprises the subscriber control server shown in FIG. FIG. 4 is a detailed view of subscriber control parameters managed by a control right ID content management table 402 shown in FIG. 3. It is an example of the content of the control right ID provision subscriber management table which comprises the subscriber control server shown in FIG. It is a block diagram explaining the structural example of the mobile terminal shown in FIG. It is a block diagram explaining the structural example of the movement management node shown in FIG. It is a block diagram explaining the structural example of the subscriber management server shown in FIG. It is an example of the content of the control information management table which comprises the subscriber management server shown in FIG. It is an example of the content of the subscriber information management table after control information provision which comprises the subscriber management server shown in FIG. It is a flowchart which shows the operation example (operation | movement from input of a control authority ID to transmission of a connection request) of the mobile terminal of 1st Embodiment. It is a flowchart which shows the operation example (operation | movement from reception of a connection request to transmission of a subscriber information request) of the mobility management node of 1st Embodiment. It is a flowchart which shows the operation example (operation | movement until receiving a subscriber information request | requirement and transmitting a subscriber information response) of the subscriber management server of 1st Embodiment. It is a flowchart which shows the operation example (detailed operation at the time of updating the subscriber information management table after control information provision) of the subscriber management server of 1st Embodiment. It is a flowchart which shows the operation example (operation | movement from reception of a subscriber control information request | requirement to transmission of a subscriber control information response) of the subscriber control server of 1st Embodiment. Example of Operation of Mobile Communication System of First Embodiment (Operation at the time of initial connection of mobile terminal, more specifically, from connection request transmission of mobile terminal until communication control policy of mobile management node is applied FIG. 6 is a sequence diagram for explaining a process. It is a block diagram for demonstrating the structural example of the mobile terminal of the 2nd Embodiment of this invention. It is a block diagram for demonstrating the structural example of the movement management node of the 2nd Embodiment of this invention. It is a flowchart which shows the operation example (operation | movement at the time of acquiring a subscriber information update trigger) of the mobile terminal of the 2nd Embodiment of this invention. It is a flowchart which shows the operation example (operation | movement at the time of acquiring a subscriber information update request from a mobile terminal) of the movement management node of the 2nd Embodiment of this invention. It is a block diagram for demonstrating the structural example of the subscriber control server of the 3rd Embodiment of this invention. It is a figure which shows the content managed by the control right ID content management table which comprises the subscriber control server shown in FIG. It is a flowchart which shows the operation example of the subscriber control server of the 3rd Embodiment of this invention. It is a block diagram for demonstrating the structural example of the subscriber control server of the 4th Embodiment of this invention. It is a figure which shows the content managed by the control right ID content management table which comprises the subscriber control server shown in FIG. It is a block diagram for demonstrating the structural example of the subscriber management server of the 4th Embodiment of this invention. It is a figure which shows the content managed by the control information management table which comprises the subscriber management server shown in FIG. It is a flowchart which shows the operation example of the subscriber management server of the 4th Embodiment of this invention. It is a system block diagram explaining the structural example of the mobile communication system 10 which concerns on the 5th Embodiment of this invention. FIG. 30 is a block diagram for explaining a configuration example of a radio base station shown in FIG. 29. An example of the content of the control right ID setting policy management DB shown in FIG. 30 is shown. An example of the content of the connection request parameter change content management DB shown in FIG. 30 is shown. FIG. 10 is a flowchart showing an operation example of the radio base station according to the fifth embodiment (operation when receiving a connection request from a mobile terminal and setting a control right ID and changing a request parameter for the connection request); . An operation example of the mobile communication system according to the fifth embodiment (processing operation when a radio base station receives a connection request for the mobile terminal and transmits a connection request to the mobility management node when the mobile terminal is connected) will be described. FIG. It is a system block diagram for demonstrating the structural example of the mobile communication system which concerns on the 6th Embodiment of this invention. 1 is a configuration diagram of a mobile communication system described in Non-Patent Document 1. FIG. It is a figure which shows the content of the subscriber information which the subscriber management server of the mobile communication system shown in FIG. 36 manages. FIG. 37 is a sequence diagram for explaining processing of the mobile communication system shown in FIG. 36 (processing from transmission of a connection request of a mobile terminal to determination of a communication control policy of a mobility management node).

[First Embodiment]
FIG. 1 is a system configuration diagram for explaining a configuration example of a mobile communication system 10 according to the first embodiment of the present invention. The basic difference between the mobile communication system 10 and the mobile communication system 1 shown in FIG. 36 is that a subscriber control server 400A is newly added. Further, the mobile terminal 110A, the subscriber management server 210A, and the mobile management node 310A are added to the mobile terminal 100, the subscriber management server 200, and the mobile management node 300 shown in FIG. 36 in accordance with the addition of the subscriber control server 400A. On the other hand, functions described later are added to each.

  FIG. 2 is a block diagram illustrating a configuration example of the subscriber control server 400A illustrated in FIG. The subscriber control server 400A includes a subscriber control information management DB (DataBase) 401A, a subscriber control request receiving unit 404, a subscriber control information determining unit 405, a control right granting subscriber registration unit 406, and a subscriber control. Information notification unit 407.

  The subscriber control information management DB 401A includes a control right ID (Identifier) content management table 402 and a control right ID granting subscriber management table 403.

  FIG. 3 shows an example of the contents of the control right ID content management table 402. The control right ID content management table 402 manages subscriber control parameters using the control right ID as a key. Here, the subscriber control parameter describes the content to be controlled (also referred to as operation) for the subscriber information managed by the subscriber management server 210A. The control right ID is an ID for identifying a subscriber control parameter (control (operation content) on subscriber information).

  FIG. 4 is a detailed view of the subscriber control parameters managed by the control right ID content management table 402. The subscriber control parameters include a control type and control content (setting value) for each item of subscriber information managed by the subscriber management server 210A. Examples of control types include addition, deletion, and change. It is also possible to handle a plurality of items for one subscriber control information.

  The subscriber control parameter for the PDN subscription context includes a parameter serving as a reference for specifying a PDN subscription context to be controlled from among a plurality of PDN contexts. That is, the subscriber control parameter for the PDN subscription context includes control target PDN subscription context identification information and PDN subscription context control content corresponding to the control target PDN subscription context identification information.

  FIG. 5 shows an example of the contents of the control right ID granting subscriber management table 403. The control right ID granting subscriber management table 403 manages predetermined information using a control right ID and a subscriber ID to which a subscriber control parameter corresponding to the control right ID is assigned as a key. Here, as an example of the management information, it can be time information at which the grant of the control right ID to the subscriber ID is started.

  Returning to the description of FIG. 2, the subscriber control request receiving unit 404 receives the “subscriber control information request” transmitted from the subscriber management server 210A, and extracts the control right ID and the subscriber ID from the request. Then, the extracted control right ID and subscriber ID are notified to the subscriber control information determination unit 405.

  The subscriber control information determination unit 405 acquires the control right ID and the subscriber ID from the subscriber control request reception unit 404. The subscriber control information determination unit 405 searches the control right ID content management table 402 of the subscriber control information management DB 401A using the control right ID as a key, and acquires the corresponding subscriber control parameter. The subscriber control information determination unit 405 notifies the control right granting subscriber registration unit 406 of the control right ID, the subscriber ID, and the subscriber control parameter.

  The control right granting subscriber registration unit 406 sets a time (granting start time) at which control right ID granting is started for one or more subscriber IDs registered in the control right ID granting subscriber management table 403. To do. For example, the control right granting subscriber registration unit 406 can set the current time information as the grant start time. Then, the control right granting subscriber registration unit 406 notifies the subscriber control information notification unit 407 of the control right ID, the subscriber ID, and the subscriber control parameter corresponding to the control right ID.

  The subscriber control information notifying unit 407 transmits a subscriber control information response including the control right ID acquired from the control right granting subscriber registration unit 406, the subscriber ID, and the subscriber control parameter corresponding to the control right ID to the subscriber. Notify the management server 210A. The subscriber control information response is response information to the subscriber control information request.

  FIG. 6 is a block diagram illustrating a configuration example of the mobile terminal 110A illustrated in FIG. FIG. 6 shows only functions related to the addition of the subscriber control server 400A. The mobile terminal 110A includes at least a control right ID input unit 111 and a control right ID setting unit 112.

  The control right ID input unit 111 is means for taking the control right ID into the mobile terminal 110A. As a method for capturing the control right ID, for example, a method in which a user inputs using a user interface, a method of acquiring from the mobile communication system 10, a method of acquiring by infrared communication, a method of acquiring by reading a QR code, or NFC A method of obtaining by (Near Field Communication) can be exemplified. Of course, the method for acquiring the control right ID is not limited to the above-described methods. The control right ID input unit 111 notifies the control right ID setting unit 112 of the acquired control right ID.

  The control right ID setting unit 112 requests a connection request (at the time of 3GPP, Attach Request in the case of 3GPP) transmitted by the mobile terminal 110A from an entity (for example, a mobile terminal) on the mobile communication system to control subscriber information. A first subscriber information control field is provided for discriminating that the user is in charge. Then, the control right ID setting unit 112 inputs the control right ID as it is input from the control right ID input unit 111 or the control right ID selected by the control right ID setting unit 112 itself into the first subscriber information control field. To store. The connection request in which the control right ID is set in the first subscriber information control field is transmitted to the mobility management node 310A via communication means not shown in FIG.

  FIG. 7 is a block diagram illustrating a configuration example of the mobility management node 310A illustrated in FIG. FIG. 7 shows only functions related to the addition of the subscriber control server 400A. The mobility management node 310A includes at least a subscriber information control field check unit 311 and a control right ID setting unit 312.

  The subscriber information control field check unit 311 checks whether or not the connection request transmitted from the mobile terminal 110A is the first subscriber information control field. When the first subscriber information control field exists, the subscriber information control field check unit 311 extracts the control right ID stored in the first subscriber information control field, and sends the control right ID to the control right ID setting unit 312. Notice.

  The control right ID setting unit 312 provides a second subscriber information control field in the subscriber information request (Update Location Request in the case of 3GPP) transmitted to the subscriber management server 210A. The control right ID setting unit 312 stores the control right ID acquired from the subscriber information control field check unit 311 in the second subscriber information control field. The subscriber information request in which the control right ID is set in the second subscriber information control field is transmitted to the subscriber management server 210A via communication means not shown in FIG.

  FIG. 8 is a block diagram illustrating a configuration example of the subscriber management server 210A illustrated in FIG. FIG. 8 shows only functions related to the addition of the subscriber control server 400A.

  The subscriber management server 210A includes a subscriber information management DB 211, a subscriber information control field check unit 215, a subscriber control information acquisition unit 216, a subscriber control information registration unit 217, and a subscriber information update unit 218. At least.

  The subscriber information management DB 211 includes a default subscriber information management table 212, a control information management table 213, and a subscriber information management table 214 after adding control information.

  The default subscriber information management table 212 is subscriber information managed by a general subscriber management server (see, for example, FIG. 36).

  FIG. 9 is an example of the contents of the control information management table 213. The control information management table 213 uses the subscriber ID and the control right ID to be given to the subscriber ID as a main key, the subscriber control parameter corresponding to the control right ID, and the identifier of the subscriber control server that acquired the control right ID Manage.

  FIG. 10 shows an example of the contents of the subscriber information management table 214 after the addition of control information. The subscriber information management table 214 after the control information is added gives the subscriber control parameters registered in the control information management table 213 to the default subscriber information management table 212 using the subscriber ID (for example, IMSI) as a key. Information is managed for each item. It also manages the control right ID assigned to each subscriber information item.

  Returning to the description of FIG. 8, the subscriber information control field check unit 215 checks whether or not the second subscriber information control field exists in the subscriber information request transmitted from the mobility management node 310A. When the second subscriber information control field exists, the subscriber information control field check unit 215 includes the control right ID stored in the second subscriber information control field and the subscriber included in the subscriber information request. The subscriber ID is notified to the subscriber control information acquisition unit 216.

  The subscriber control information acquisition unit 216 transmits a subscriber control information request including the control right ID and the subscriber ID acquired from the subscriber information control field check unit 215 to the subscriber control server 400A. Further, the subscriber control information acquisition unit 216 receives a subscriber control information response including a subscriber control parameter corresponding to the control right ID from the subscriber control server 400A. Further, the subscriber control information acquisition unit 216 notifies the subscriber control information registration unit 217 of the control right ID, the subscriber ID, and the subscriber control parameter corresponding to the control right ID.

The subscriber control information registration unit 217 registers the subscriber ID, the control right ID, and the subscriber control parameter acquired from the subscriber control information acquisition unit 216 in the control information management table 213. Further, the subscriber control information registration unit 217 notifies the subscriber information update unit 218 of a subscriber information update request including the subscriber ID. The subscriber information update unit 218 receives the subscriber control information registration unit 217 from the subscriber control information registration unit 217. The default subscriber information is acquired from the default subscriber information management table 212 using the subscriber ID as a key. Also, the subscriber information update unit 218 acquires a subscriber control parameter corresponding to the subscriber ID from the control information management table 213 using the subscriber ID as a key. Then, the subscriber information update unit 218 applies the subscriber control parameter to the default subscriber information, and registers the application result in the subscriber information management table 214 after the control information is given. Then, a subscriber information response including the post-control information-added subscriber information stored in the post-control-information-added subscriber information management table 214 is transmitted from the subscriber management server 210A to the mobility management node 310A.

  FIG. 11 is a flowchart illustrating an operation example (operation from input of a control authority ID to transmission of a connection request) of the mobile terminal 110A according to the first embodiment.

  The control right ID input unit 111 takes in the control right ID into the mobile terminal 110A by a predetermined acquisition method (for example, input using a user interface) (step S200). The control right ID input unit 111 notifies the control right ID setting unit 112 of the acquired control right ID.

  The control right ID setting unit 112 stores the control right ID notified from the control right ID input unit 111 in the connection request (Attach Request) transmitted by the mobile terminal 110A at the start of the initial connection (step S201). Specifically, the control right ID setting unit 112 provides a first subscriber information control field in the connection request, and stores the control right ID in the first subscriber information control field. The connection request in which the control right ID is set in the first subscriber information control field is transmitted from the mobile terminal 110A to the mobility management node 310A.

  FIG. 12 is a flowchart illustrating an operation example (operation from reception of a connection request to transmission of a subscriber information request) of the mobility management node 310A according to the first embodiment.

  First, the mobility management node 310A receives a connection request from the mobile terminal 110A (step S300). The subscriber information control field check unit 311 checks whether or not a control right ID exists in the first subscriber information control field of the received connection request (step S301). If the control right ID does not exist (No determination in step S301), it can be determined that it is not necessary to control the subscriber information, so the control right ID is not set for the subscriber information request transmitted to the subscriber management server 210A. The process ends. On the other hand, when the control right ID exists (Yes in step S301), the control right ID setting unit 312 sends the control right ID acquired from the first subscriber information control field check unit 311 to the subscriber management server 210A. Processing for setting in the subscriber information request to be transmitted is executed (step S302). Specifically, the control right ID setting unit 312 provides a second subscriber information control field in the subscriber information request, and stores the acquired control right ID in the second subscriber information control field. . The subscriber information request in which the control right ID is set in the second subscriber information control field is transmitted from the mobility management node 310A to the subscriber management server 210A.

  FIG. 13 is a flowchart illustrating an operation example (operation until receiving a subscriber information request and transmitting a subscriber information response) of the subscriber management server 210A of the first embodiment.

  First, the subscriber management server 210A receives a subscriber information request from the mobility management node 310A (step S400). The subscriber information control field check unit 215 checks whether the control right ID exists in the second subscriber information control field of the subscriber information request transmitted from the mobility management node 310A (step S401).

  When the control right ID exists (Yes in step S401), the subscriber control information acquisition unit 216 sends a subscriber control information request including the control right ID acquired from the subscriber information control field check unit 215 and the subscriber ID. And transmitted to the subscriber control server 400A (step S402). Thereafter, the subscriber management server 210A receives a subscriber control information response as a result of the subscriber control information request from the subscriber control server 400A. The subscriber control information acquisition unit 216 determines whether there is a subscriber control parameter corresponding to the control right ID stored in the subscriber control information response (step S403).

  If there is a corresponding subscriber control parameter (Yes in step S403), the subscriber control information registration unit 217 acquires the subscriber ID, control right ID, and control right ID acquired from the subscriber control information acquisition unit 216. Is registered in the control information management table 213 (step S404). The subscriber information update unit 218 updates the post-control information-added subscriber information management table 214 with reference to the default subscriber information management table 212 and the control information management table 213 (step S405). Then, a subscriber information response including subscriber information after adding control information stored in the subscriber information management table 214 after adding control information is transmitted from the subscriber management server 210A to the mobility management node 310A (step S406). .

  On the other hand, when the control right ID does not exist (No determination in step S401) and when the corresponding subscriber control parameter does not exist (No determination in step S403), the process of step S406 is executed. However, in this case, the subscriber information response transmitted from the subscriber management server 210A to the mobile management node 310A does not include the subscriber information after the addition of control information.

  FIG. 14 is a flowchart showing an operation example of the subscriber management server 210A of the first embodiment (detailed operation when updating the subscriber information management table 214 after the addition of control information).

  The subscriber information update unit 218 obtains default subscriber information from the default subscriber information management table 212 using the subscriber ID stored in the subscriber information request received from the mobility management node 310A as a key (step S500). . Next, the subscriber information update unit 218 acquires a subscriber control parameter corresponding to the subscriber ID from the control information management table 213 using the subscriber ID as a key (step S501). Then, the subscriber information update unit 218 applies the subscriber control parameter acquired from the control information management table 213 to the default subscriber information acquired from the default subscriber information management table 212, and joins after adding control information. Registered in the person information management table 214 (step S502). Then, a subscriber information response including the post-control information-added subscriber information stored in the post-control-information-added subscriber information management table 214 is transmitted from the subscriber management server 210A to the mobility management node 310A.

  FIG. 15 is a flowchart illustrating an operation example (operation from reception of a subscriber control information request to transmission of a subscriber control information response) of the subscriber control server 400A of the first embodiment.

  First, the subscriber control request receiving unit 404 receives a “subscriber control information request” transmitted from the subscriber management server 210A (step S600). The subscriber control information determination unit 405 acquires a control right ID from the subscriber control request reception unit 404. The subscriber control information determination unit 405 searches the control right ID content management table 402 of the subscriber control information management DB 401A using this control right ID as a key, and determines whether there is a subscriber control parameter corresponding to the control right ID. (Step S601).

  When the corresponding subscriber control parameter does not exist (No determination in step S601), the subscriber control information notification unit 407 sends a subscriber control information response including information that the subscriber control parameter does not exist to the subscriber server 210A. Notification is made (step S602).

  On the other hand, when the corresponding subscriber control parameter exists (Yes in step S601), the control right granting subscriber registration unit 406 registers the subscriber who has been given the control right (step S603). Specifically, the control right granting subscriber registration unit 406 starts the granting of the control right ID to the subscriber ID in the control right ID granting subscriber management table 403 of the subscriber control information management DB 401A ( (Giving start time), the current time information is registered.

  The subscriber control information notifying unit 407 transmits a subscriber control information response including the control right ID acquired from the control right granting subscriber registration unit 406, the subscriber ID, and the subscriber control parameter corresponding to the control right ID to the subscriber. Notify the management server 210A.

  FIG. 16 is an operation example of the mobile communication system 10 according to the first embodiment (operation at the time of initial connection of the mobile terminal 110A, and more specifically, communication from the connection request transmission of the mobile terminal 110A to the mobility management node 310A. FIG. 10 is a sequence diagram for explaining a process until a control policy is applied.

  Assuming that the initial connection process starts, it is assumed that the control right ID is input to the mobile terminal 110A via the control right ID input unit 111.

  First, the control right ID setting unit 112 of the mobile terminal 110A transmits a connection request (Attach Request) in which the control right ID is stored in the first subscriber information control field to the mobility management node 310A (step S700).

  The control right ID setting unit 312 of the mobility management node 310A provides a second subscriber information control field in the subscriber information request (Update Location Request) transmitted to the subscriber management server 210A, and the subscriber information control field check unit 311. The control right ID acquired from the above is stored. The subscriber information request in which the control right ID is set in the second subscriber information control field is eventually transmitted from the mobility management node 310A to the subscriber management server 210A (step S701).

  The subscriber control information acquisition unit 216 of the subscriber management server 210A transmits a subscriber control information request including the control right ID and the subscriber ID acquired from the subscriber information control field check unit 215 to the subscriber control server 400A. (Step S702).

  The subscriber control request receiving unit 404 of the subscriber control server 400A receives the subscriber control information request transmitted from the subscriber management server 210A, and controls the control right ID and the subscriber stored in the subscriber information control request. Extract the ID. The subscriber control information determination unit 405 acquires a subscriber control parameter corresponding to the control right ID from the control right ID content management table 402 of the subscriber control information management DB 401A using the extracted control right ID as a key (step S703). ).

  The control right granting subscriber registration unit 406 of the subscriber control server 400A registers the subscriber to which the control right ID is assigned (step S704). The control right granting subscriber registration unit 406 sets a time (granting start time) at which control right ID granting is started for one or more subscriber IDs registered in the control right ID granting subscriber management table 403. To do. For example, the control right granting subscriber registration unit 406 sets the current time information as the grant start time.

  The subscriber control server 400A notifies the subscriber management server 210A of a subscriber control information response including a control right ID, a subscriber ID, and a subscriber control parameter corresponding to the control right ID (step S705). Specifically, the subscriber control information notifying unit 407 of the subscriber control server 400A includes a control right ID acquired from the control right granting subscriber registration unit 406, a subscriber ID, and a subscriber control parameter corresponding to the control right ID. The subscriber control server 210A is notified of a subscriber control information response including

  The subscriber control information registration unit 217 of the subscriber management server 210A stores the subscriber ID acquired from the subscriber control information acquisition unit 216, the control right ID, and the subscriber control parameters corresponding to the control right ID in the control information management table 213. Registration is performed (step S706).

  The subscriber information update unit 218 of the subscriber management server 210A updates the subscriber information management table 214 after giving control information with reference to the default subscriber information management table 212 and the control information management table 213 (step S707).

  Then, a subscriber information response (Update Location Ack) including the post-control information-added subscriber information stored in the post-control-information-added subscriber information management table 214 is transmitted from the subscriber management server 210A to the mobility management node 310A. (Step S706).

  Next, in step S709, the mobility management node 310 that has acquired the subscriber information response in step S708 applies the subscriber ID and subscriber information stored in the acquired subscriber information response as a communication control policy, and A communication path (bearer) is established based on the communication control policy.

  In the first embodiment described above, the subscriber control server 400A includes a database that stores operation contents (subscriber control parameters) for subscriber information in association with control right IDs for identifying the operation contents. . Then, the subscriber control server 400A refers to this database to specify the operation content corresponding to the control right ID received from the predetermined communication node (for example, the mobile terminal 110A) via the subscriber management server 210A. . The specified operation content is transmitted to the subscriber management server 210A, and the subscriber information is updated based on the operation content.

  That is, it is possible to change the communication environment of the mobile terminal 110A simply by notifying the mobile communication system 10 of the control right ID issued by the mobile operator from the mobile terminal 110A. Therefore, the user can easily perform operations (addition, deletion, change, etc.) of subscriber information without performing authentication and complicated setting processing.

  In addition, transmission of the control right ID from a predetermined communication node (for example, the mobile terminal 110A) to the subscriber control server 400A is performed using an existing request signal (for example, Attach Request, Update Location Request, or the like). That is, the subscriber information can be operated at an arbitrary timing including the initial connection. For example, the subscriber information (communication control policy) can be changed before the mobile terminal 110A completes the connection, not limited to the initial connection.

  Further, it is possible to use the service provider so that the control right ID acquired from the mobile operator is distributed to the mobile terminals to be controlled. In this case, the mobile terminal can be controlled in accordance with the intention of the service provider.

[Second Embodiment]
The difference of the second embodiment from the first embodiment is that the control timing of subscriber information is different. In the first embodiment, the control of the subscriber information at the time of connection request (initial connection) of the mobile terminal 110A has been described, but in the second embodiment, the subscriber at an arbitrary timing after completion of the initial connection is described. Information control will be described.

  In order to realize the above functions, the configurations (and operations) of the mobile terminal and the mobility management node are different from those of the first embodiment. Therefore, in the following description, the description of the configuration that is not changed from the first embodiment (that is, the subscriber management server and the subscriber control server) is omitted.

  FIG. 17 is a block diagram for explaining a configuration example of the mobile terminal 110B of the second embodiment. The difference between the mobile terminal 110B and the mobile terminal 110A of the first embodiment (see FIG. 6) is that a subscriber information update trigger reception unit 120 and a subscriber information update request transmission unit 121 are newly added. . Since the other components are the same as those of the mobile terminal 110A shown in FIG. 6, the same reference numerals as those in FIG. 6 are given in FIG. 17, and the description thereof will be omitted.

  The subscriber information update trigger reception unit 120 receives a trigger for requesting update of subscriber information. The subscriber information update trigger reception unit 120 that has received the trigger transmits a trigger occurrence notification to the subscriber information update request transmission unit 121. The trigger for requesting the update of the subscriber information includes a case where the user inputs using the user interface, a case where the control right ID is input to the control right ID input unit 111, a case where a specific condition is satisfied, and the like. be able to. Of course, the type of trigger is not limited to these. Further, the subscriber information update trigger reception unit 120 holds the control right ID input in advance by the control right ID input unit 111, and performs this control when transmitting a trigger occurrence notification to the subscriber information update request transmission unit 121. The right ID is also notified.

  When the subscriber information update request transmission unit 121 obtains the trigger generation notification including the control right ID from the subscriber information update trigger reception unit 120, the subscriber information update request transmission unit 121 stores the control right ID and the subscription stored in the UICC of the mobile terminal 110B. "Subscriber information update request" including the subscriber ID is transmitted to the mobility management node 310B. The “subscriber information update request” may be defined as a new signal. Alternatively, a subscriber information update request can be made by providing a subscriber information control field in an existing signal and storing the control right ID in the subscriber information control field. As an example of the existing signal, in the case of 3GPP, for example, Tracking Area Update Request, Tracking Area Update Request, or PDN Connection Request can be cited.

  FIG. 18 is a block diagram for explaining a configuration example of the mobility management node 310B of the second embodiment. The mobility management node 310B includes at least a subscriber information update request receiving unit 320 and a subscriber information request processing starting unit 321.

  The subscriber information update request receiving unit 320 receives a subscriber information update request from the mobile terminal 110B. The subscriber information update request receiving unit 320 notifies the subscriber information request processing start unit 321 of the control right ID extracted from the subscriber information update request.

  The subscriber information request processing start unit 321 executes the following processing at the timing of receiving the control right ID from the subscriber information update request receiving unit 320 (that is, the timing at which a trigger is generated). In this case, the subscriber information request processing start unit 321 provides a subscriber information control field in the subscriber information request (for example, Update Location Request), and receives the received control right ID and subscriber ID. Store in control field. Then, the subscriber information request processing start unit 321 transmits this subscriber information request to the subscriber management server 210A.

  FIG. 19 is a flowchart illustrating an operation example (operation when a subscriber information update trigger is acquired) of the mobile terminal 110B of the second embodiment.

  When the subscriber information update trigger receiving unit 120 receives a trigger for requesting update of the subscriber information, the subscriber information update trigger receiving unit 120 updates the subscriber information with a trigger occurrence notification including the control right ID input in advance by the control right ID input unit 111. It transmits to the request transmission part 121 (step S1000).

  When receiving the trigger occurrence notification, the subscriber information update request transmission unit 121 stores the control right ID and the subscriber ID stored in the UICC of the mobile terminal 110B in the subscriber information update request (step S1001). ). If the subscriber information update request is an existing signal defined in 3GPP, the subscriber information update request transmission unit 121 provides a subscriber information control field, and sets the control right ID and the subscriber ID in the subscription signal. Stored in the user information control field. The subscriber information update request transmission unit 121 transmits a subscriber information update request including the control right ID and the subscriber ID to the mobility management node 310B (step S1002).

  FIG. 20 is a flowchart illustrating an operation example of the mobility management node 310B according to the second embodiment (operation when a subscriber information update request is acquired from the mobile terminal 110B).

  The subscriber information update request receiving unit 320 receives a subscriber information update request from the mobile terminal 110B (step S1100). The subscriber information update request receiving unit 320 extracts the control right ID stored in the subscriber information update request and notifies the subscriber information request processing start unit 321 of the control right ID. When the subscriber information update request is an existing signal defined by 3GPP, the subscriber information update request receiving unit 320 extracts the control right ID stored in the subscriber information control field.

  The subscriber information request processing start unit 321 provides a subscriber information control field in the subscriber information request at the timing when the control right ID is received from the subscriber information update request receiving unit 320, and the received control right ID and the subscriber The ID is stored in this subscriber information control field (step S1101). Then, the subscriber information request processing start part 321 transmits this subscriber information request to the subscriber management server 210A (step S1102).

  Since the flow of processing after the mobility management node 310B transmits a subscriber information request to the subscriber management server 210A is the same as that in the first embodiment, a description thereof will be omitted.

  According to the second embodiment described above, it is possible to operate subscriber information not only at the time of initial connection but also at an arbitrary timing. For example, the subscriber information (communication control policy) can be changed before the mobile terminal 110B completes the connection.

  In the second embodiment described above, the case where the subscriber information update request is transmitted via the mobility management node 310B is described as an example, but the present invention is not limited to this. For example, by constructing an interface in which the mobile terminal 110B and the subscriber control server 400A can directly communicate, a subscriber information update request is transmitted directly to the subscriber control server 400A without going through the mobility management node 310B. It is also possible to do.

[Third Embodiment]
In the first embodiment, the case where the subscriber control server 400A applies the subscriber control parameter corresponding to the control right ID to the subscriber who submitted the control right ID has been described. The third embodiment is characterized in that a subscriber control parameter corresponding to a control right ID is applied based on a condition for applying the control right ID.

  In order to realize the above features, in the case of this embodiment, the configuration (and operation) of the subscriber control server is different from that of the first embodiment. Therefore, in the following description, the description of the configuration that is not changed from the first embodiment is omitted.

  FIG. 21 is a block diagram for explaining a configuration example of the subscriber control server 400C of the third embodiment. The subscriber control server 400C further adds a control right ID content management table 420 and a control right grant condition determination unit 421 to the subscriber control server 400A (see FIG. 2) in the first embodiment. It becomes composition. In FIG. 21, the subscriber control information management DB including the control right ID content management table 420 is referred to as a subscriber control information management DB 401C.

  FIG. 22 is a diagram showing the contents managed by the control right ID contents management table 420. In the control right ID content management table 420, a control right granting condition is added to the control right ID content management table 402 (see FIG. 3) of the first embodiment. The control right granting condition is a condition for determining whether or not the subscriber control parameter corresponding to the control right ID may be given to the subscriber who is sending the subscriber control information request. As the control right granting condition, it is possible to set a plurality of conditions for one control right ID. The control right granting condition is acquired together when the subscriber control information determining unit 405 acquires the subscriber control parameter corresponding to the control right ID.

  Returning to the description of FIG. 21, the control right grant condition determination unit 421 controls the control right for the subscriber who has requested the subscriber control based on the control right grant condition stored in the control right ID content management table 420. It is determined whether or not the subscriber control parameter corresponding to the ID may be given.

  FIG. 23 is a flowchart showing an operation example of the subscriber control server 400C.

  The subscriber control information determination unit 405 acquires the subscriber control parameter and the control right granting condition corresponding to the control right ID stored in the subscriber control request from the control right ID content management table 420 (step S1200).

  The control right grant condition determination unit 421 proceeds with the determination from the first condition of the control right grant condition acquired by the subscriber control information determination unit 405 (step S1201).

  Here, a specific method of condition determination will be described. For example, a case where the number of persons who can be assigned a control right ID is limited as in condition 1 of the control right ID content management table 420 shown in FIG. In this case, the control right granting condition determining unit 421 checks the number of subscribers to whom the subscriber control parameter corresponding to the control right ID of the control right ID granting subscriber management table 403 is assigned, and whether or not the limit is exceeded. Judging. On the other hand, if the condition is such that the grant to a specific subscriber is not possible as in condition 2, the control right grant condition determining unit 421 determines that the subscriber ID and condition 2 stored in the subscriber control information request are in accordance with condition 2. Judgment is made by matching with a defined subscriber ID.

  If the condition is not satisfied (No determination in step S1201), it is determined that the control right cannot be granted, and the process ends.

  On the other hand, if the condition is satisfied (Yes in step S1201), the control right grant condition determination unit 421 advances the determination target of the control right grant condition to the next condition (step S1202). The control right grant condition determination unit 421 checks whether or not the following condition exists (step S1203). If the next condition does not exist (No determination in step S1203), it can be determined that all the control right granting conditions corresponding to the control right ID stored in the subscriber control information request are satisfied. Therefore, the control right granting condition determining unit 421 determines that the subscriber control parameter corresponding to the control right ID can be assigned to the subscriber ID stored in the subscriber control information request (step S1204). ).

  In the third embodiment described above, the subscriber control server control 400C automatically determines whether or not to assign a subscriber control parameter corresponding to the submitted control right ID based on the control right granting condition. To do. Therefore, even after the control right ID is distributed, it is possible to restrict the subscribers to whom the subscriber control parameter is applied. For example, it is possible to execute high value-added communication control in line with the service provider's intention, such as being able to provide a specific communication service only to a specific subscriber in a specific area.

[Fourth Embodiment]
The fourth embodiment is characterized in that it corresponds to a case where a plurality of control authority IDs are exercised for one subscriber ID, and the control items of the subscriber control parameters to be applied overlap.

  In order to realize the above features, in this embodiment, the configurations (and operations) of the subscriber control server and the subscriber management server are different from those in the first embodiment. Therefore, in the following description, the description of the configuration that is not changed from the first embodiment is omitted.

  FIG. 24 is a block diagram for explaining a configuration example of a subscriber control server 400D according to the fourth embodiment of the present invention. The difference between the subscriber control server 400D and the subscriber control server 400A (see FIG. 2) in the first embodiment is in the control right ID content management table 430. In FIG. 24, the subscriber control information management DB including the control right ID content management table 430 is referred to as a subscriber control information management DB 401D.

  FIG. 25 is a diagram showing the contents managed by the control right ID contents management table 430. As understood from FIG. 25, the priority of management information is added to the control right ID content management table 430 with respect to the control right ID content management table 402 (see FIG. 3) of the first embodiment. .

  As for the above priority, when a plurality of control authority IDs are exercised for one subscriber ID and there are overlapping control items in a plurality of subscriber control parameters to be applied, which control right ID is reflected preferentially This is information that serves as a reference for determining whether it is okay. Accordingly, a priority is set for each control right ID. The priority is acquired together when the subscriber control information determination unit 405 acquires the subscriber control parameter corresponding to the control right ID, and the subscriber management server 210D receives the priority as the information related to the control right ID. Sent.

  FIG. 26 is a block diagram for explaining a configuration example of the subscriber management server 210D according to the fourth embodiment of this invention. An additional element of the subscriber management server 210D from the subscriber management server 210A (see FIG. 8) of the first embodiment is a duplication update policy 230, and a change is in the control information management table 231 and the subscriber information update unit 232. is there.

  When the subscriber information update unit 232 updates the subscriber information management table 214 after adding control information, there are a plurality of subscriber control parameters to be applied to one subscriber ID, and the plurality of subscriber control parameters are duplicated. There may be control items to be The duplicate update policy 230 describes a policy for determining which control right ID is applied to a subscriber control parameter when there are a plurality of control parameters and there are duplicate control items. For example, the control authority ID registered in the control information management table 231 at the beginning or last may be applied with priority, or a specific control right ID may be reflected with priority.

  In the duplicate update policy 230 of this embodiment, it is described that a control right ID having a small priority value registered in the control information management table 231 is reflected preferentially.

  FIG. 27 is a diagram showing the contents managed by the control information management table 231 constituting the subscriber management server 210D shown in FIG. As understood from FIG. 27, the control information management table 231 includes a subscriber control information response acquired from the subscriber control server 400D in the management information of the control information management table 213 (see FIG. 9) of the first embodiment. An item of priority corresponding to the control right ID stored in is added.

  Returning to the description of FIG. 26, the subscriber information update unit 232 has a plurality of subscriber control parameters to be applied when updating the subscriber information in addition to the function of the subscriber information update unit 218 of the first embodiment. A check function is provided for checking whether there is a duplicate control item in a plurality of subscriber control parameters. When there are overlapping control items, the subscriber information updating unit 232 refers to the duplication determination policy 230 and determines a subscriber control parameter to be applied.

  FIG. 28 is a flowchart illustrating an operation example of the subscriber management server 210D according to the fourth embodiment of this invention.

  The subscriber information update unit 232 acquires default subscriber information from the default subscriber information management table 212 using the subscriber ID as a key (step S1300).

  The subscriber information update unit 232 acquires a subscriber control parameter and priority corresponding to the subscriber ID from the control information management table 231 using the subscriber ID as a key (step S1301).

  The subscriber information update unit 232 checks whether there are a plurality of subscriber control parameters corresponding to the subscriber ID from the control information management table 231 using the subscriber ID as a key (step S1302).

  When there are a plurality of subscriber control parameters (Yes in step S1302), the subscriber information update unit 232 converts the control information management table 231 to a plurality of subscriber control parameters corresponding to the subscriber ID using the subscriber ID as a key. On the other hand, it is checked whether there are overlapping control items (step S1303).

  When there are a plurality of overlapping control items (Yes in step S1303), the subscriber information update unit 232 acquires a policy for determining a control right ID to be applied from the duplication update policy 230 (step S1304). In the duplicate update policy 230 of this embodiment, it is described that a control right ID having a small priority value registered in the control information management table 231 is reflected preferentially.

  The subscriber information updating unit 232 determines which control right ID is applied to the overlapping subscriber control parameter based on the overlapping update policy 230 (step S1306). In the case of this embodiment, a control right ID having a smaller priority value registered in the control information management table 231 is used for overlapping control items.

  The subscriber information update unit 232 applies the subscriber control parameter determined in step S1306 to the default subscriber information acquired in step S1300, and registers it in the subscriber information management table 214 after adding control information (step S1300). S1307).

On the other hand, when there are not a plurality of subscriber control parameters (No determination in step S1302) and there are a plurality of overlapping control items (No determination in step S1303),
The subscriber information update unit 232 executes the following processing. The subscriber information update unit 232 applies the subscriber control parameter acquired in step S1301 to the default subscriber information acquired in step S1300. Then, the subscriber information update unit 232 registers the information for each item to which the subscriber control parameter is applied and the control right ID given for each subscriber information item in the subscriber information management table 214 after the control information is given (step S1305). ).

  In the fourth embodiment described above, when there are a plurality of subscriber control parameters to be applied to one subscriber ID and there are duplicate control items in the plurality of subscriber control parameters, which control right ID Decide whether to apply the corresponding subscriber control parameters. Therefore, even when the content of the service provided by the service provider is advanced and the subscriber control parameters are complicated, the optimum communication control policy can be applied easily and reliably.

[Fifth Embodiment]
In the case of the first embodiment, by submitting the control right ID from the mobile terminal 110A, the subscriber information of the user of the mobile terminal 110A is controlled by the subscriber control parameter corresponding to the control right ID. On the other hand, in the fifth embodiment, the radio base station 500 holds the control right ID, and the subscriber information of the user of the mobile terminal connected to the radio base station 500 is used as the control right ID held by the radio base station 500. It is characterized in that it is controlled by a corresponding subscriber control parameter. The radio base station 500 also performs processing for changing the communication environment of the mobile terminal by changing the parameters of the connection request and the communication environment update request transmitted from the mobile terminal.

  FIG. 29 is a system configuration diagram illustrating a configuration example of a mobile communication system 10E according to the fifth embodiment of the present invention. The mobile communication system 10E further includes a radio base station 500. In the first embodiment, since the radio base station itself has no characteristics, the radio base station is not described. However, in this embodiment, since the radio base station 500 has characteristics, in FIG. Decided to show. In the case of this embodiment, since the mobile terminal 100 does not need to hold and transmit the control right ID, the mobile terminal shown in FIG. 29 is an existing mobile terminal 100 (for example, the mobile terminal shown in FIG. 36). To do. Other components (subscriber management server, mobility management node, subscriber control server) are the same as those in the first embodiment. Note that the radio base station 500 corresponds to eNodeB (evolved NodeB): macro cell and Home eNodeB: femto cell in 3GPP, for example.

  FIG. 30 is a block diagram for explaining a configuration example of the radio base station 500. Generally, a radio base station has a basic function of receiving a connection request from a mobile terminal and transferring the connection request to a mobility management node. Therefore, in FIG. 30, the basic function is not described, and only a new function is described.

  The radio base station 500 includes a control right ID setting policy management DB 501, a connection request receiving unit 502, a control right ID setting unit 503, a connection request parameter change content management DB 504, a connection request parameter changing unit 505, and a connection request transmission. Part 506 at least.

  FIG. 31 shows an example of the contents of the control right ID setting policy management DB 501. The control right ID setting policy management DB 501 stores determination conditions for determining a control right ID to be given to the connection request of the mobile terminal 100. Examples of the granting conditions include a condition for determining a control right ID to be given for each time zone, a condition for determining a control right ID to be given according to the characteristics of the mobile terminal 100 that transmits the connection request, and the mobile terminal 100 The condition etc. which determine control right ID according to the parameter of the connection request which transmits can be mentioned. In the present embodiment, a condition for determining a control right ID to be given by a subscriber ID of a connection request transmitted from the mobile terminal 100 is registered.

  Returning to the description of FIG. 30, the connection request receiving unit 502 receives a connection request transmitted from the mobile terminal 100 and notifies the control right ID setting unit 503 of the connection request. The control right ID setting unit 503 determines which control right ID is assigned to the connection request received by the connection request receiving unit 502 with reference to the control ID setting policy management DB 501. Further, the control right ID setting unit 503 has a function of providing a subscriber information control field for the connection request and storing the determined control right ID in the subscriber information control field.

  FIG. 32 shows an example of the contents of the connection request parameter change content management DB 504. The connection request parameter change content management DB 504 stores conditions and change values for changing parameters stored in the connection request of the mobile terminal 100 or the communication environment update request. In the present embodiment, a case where a value for changing an APN (Access Point name) indicating a PDN of a connection destination stored in the connection request is stored by the subscriber ID of the connection request transmitted by the mobile terminal 100. Take an example.

  Returning to the description of FIG. 30 again, the connection request parameter changing unit 505 determines the change content of the parameter of the connection request received by the connection request receiving unit 502 with reference to the connection request parameter change content management DB 504, and the determined change. The contents are set in the connection request. The connection request transmission unit 506 transmits the connection request prepared by the control right ID setting unit 505 to the mobility management node 310.

  FIG. 33 is an operation example of the radio base station 500 of the fifth embodiment (operation when receiving a connection request from the mobile terminal 100, setting a control right ID and changing a request parameter for the connection request) Is a flowchart showing.

  The connection request receiving unit 502 receives a connection request from the mobile terminal 100 (step S1400). The control right ID setting unit 503 refers to the control right ID setting policy management DB 501 and determines which control right ID is assigned to the connection request received by the connection request reception unit 502 (step S1401). In this embodiment, the control right ID to be granted is determined by the subscriber ID stored in the connection request. The control right ID setting unit 503 provides a subscriber information control field for the connection request received in step S1400, and stores the control right ID determined in step S1401 in the subscriber information control field (step S1402).

  The connection request parameter changing unit 505 refers to the connection request parameter change content management DB 504, and determines a change content for the parameter of the connection request received by the connection request receiving unit 502 (step S1403). In this embodiment, a value for changing the connection destination APN stored in the connection request is determined by the subscriber ID of the connection request transmitted by the mobile terminal 100.

  The connection request transmission unit 504 changes the parameter based on the change content of the connection request parameter determined in step S1403 as the subsequent request (step S1404). In this embodiment, the connection destination APN stored in the connection request is changed.

  The connection request transmission unit 504 transmits the connection request prepared by the control right ID setting unit 503 in step S1402 to the mobility management node 310A (step S1405).

  FIG. 34 is an operation example of the mobile communication system 10E of the fifth embodiment (when the mobile terminal 100 is connected, the radio base station 500 receives the connection request for the mobile terminal 100 and transmits a connection request to the mobility management node 310A. It is a sequence diagram for explaining a processing operation until.

  The mobile terminal 100 transmits a connection request to the radio base station 500 (step S1500). The control right ID setting unit 503 of the radio base station 500 determines a control right ID to be granted with reference to the grant conditions stored in the control right ID setting policy management DB 501 for the received connection request (step) S1501). Then, the control right ID setting unit 503 provides a subscriber information control field for the connection request, and stores the determined control right ID in the subscriber information control field.

  The connection request parameter change unit 505 of the radio base station 500 refers to the connection request parameter change content management DB 504 and determines the change content for the connection request parameter (step S1502). The connection request transmission unit 504 changes the parameter based on the determined change content of the connection request parameter.

  The connection request transmission unit 504 of the radio base station 500 transmits the connection request including the determined control right ID and the parameter changed to the mobility management node 310A (step S1503).

  Since the process after the mobility management node 310A receives the connection request from the mobile terminal is the same as that in the first embodiment, the description thereof is omitted.

  According to the fifth embodiment described above, the control right ID can be distributed to the radio base station instead of being distributed to the end user (for example, the mobile terminal). In this case, the subscriber information is manipulated (change of the communication control policy) by the control right ID determined by the radio base station. That is, according to the fifth embodiment, it is possible to cope with a service mode in which a communication control policy is changed mainly by a radio base station rather than a mobile terminal.

  Note that the radio base station 500 of the fifth embodiment described above includes a case where the connection request transmitted from the mobile terminal 100 is transferred to the mobility management node, and the connection request is not necessarily terminated at the radio base station 500. It is not limited to the case.

  In the fifth embodiment described above, in response to a connection request and a communication environment change request from the mobile terminal 100, the wireless communication station 500 can set a control right ID and change a request parameter.

  In the fifth embodiment described above, it is also possible for the radio base station 500 to perform only the process of setting the control right ID in response to the connection request and the communication environment change request from the mobile terminal 100. In this case, the radio base station 500 can eliminate the connection request parameter change content management DB 504 and the connection request parameter change unit 505.

[Sixth Embodiment]
FIG. 35 is a system configuration diagram for explaining a configuration example of a mobile communication system 600 according to the sixth embodiment of the present invention. The mobile communication system 600 includes a communication node 602 that transmits a predetermined request signal, a subscriber management server 604 that manages subscriber information for each subscriber identifier, a subscriber control server 606 that can operate the subscriber information, Is provided. The subscriber control server 606 includes a database 700 that stores operation contents for subscriber information in association with a right identifier for identifying the operation contents. Furthermore, the subscriber control server 606 specifies the operation content corresponding to the right identifier included in the request signal transmitted from the predetermined communication node 602 via the subscriber management server 604 by referring to the database 700, A control unit 702 that transmits the specified operation content to the subscriber management server 604 is provided. The subscriber management server 604 operates the subscriber information based on the operation content received from the subscriber control server 606.

  According to the sixth embodiment described above, it is possible to easily operate subscriber information at an arbitrary timing including the initial connection.

  By the way, there are various communication control policies that can be controlled for the mobile terminal. Therefore, the first to sixth embodiments described above can be applied to a service for changing the communication environment of a user's mobile terminal as an extension of a charging charge service using a prepaid card.

  In addition, the service provider distributes the control right ID when using the service of the mobile terminal, so that the mobile terminal can temporarily control the communication environment according to the service provider's intention when using the service of the service provider. It is. For example, the first usage example is an example in which the call function is temporarily limited when passing through the gate of a concert hall. The second usage example is an example in which a communication fee is free for a specific service access. The third usage example is an example that enables connection to a specific femtocell. In other words, the provision of added value for mobile services and the creation of new services can be expected.

  In addition, the first to sixth embodiments described above can be controlled and operated by a computer circuit (not shown) (for example, a CPU (Central Processing Unit)) based on a control program. In such a case, these control programs are stored in, for example, a storage medium (for example, a ROM (Read Only Memory) or a hard disk) or an external storage medium (for example, a removable medium or a removable disk). And read and executed by the computer circuit.

DESCRIPTION OF SYMBOLS 10, 10E Mobile communication system 100, 110A, 110B Mobile terminal 111 Control right ID input part 112 Control right ID setting part 120 Subscriber information update trigger reception part 121 Subscriber information update request transmission part 210A, 210D Subscriber management server 211 Subscription Information management DB
212 Default subscriber information management table 213 Control information management table 214 Subscriber information management table after control information is added 215 Subscriber information control field check unit 216 Subscriber control information acquisition unit 217 Subscriber control information registration unit 218 Subscriber information update unit 230 Duplicate update policy 231 Control information management table 232 Subscriber information update unit 310A, 310B Mobility management node 311 Subscriber information control field check unit 312 Control right ID setting unit 320 Subscriber information update request reception unit 321 Start of subscriber information request processing Part 400A, 400C, 400D Subscriber control server 401A, 401C, 401D Subscriber control information management DB
402 Control right ID content management table 403 Control right ID grant subscriber management table 404 Subscriber control request reception unit 405 Subscriber control information determination unit 406 Control right grant subscriber registration unit 407 Subscriber control information notification unit 420 Control right ID content Management table 421 Control right grant condition determination unit 430 Control right ID content management table 500 Wireless base station 501 Control right ID setting policy management DB
502 connection request receiving unit 503 control right ID setting unit 504 connection request parameter change content management DB
505 Connection request parameter change unit 506 Connection request transmission unit 600 Mobile communication system 602 Communication node 604 Subscriber management server 606 Subscriber control server 700 Database 702 Control unit

Claims (9)

A subscriber management server for managing subscriber information for each subscriber identifier;
A subscriber control server capable of operating the subscriber information;
With
The subscriber control server, a database that stores in association with the operation content for the subscriber information, and rights identifier to identify the operation content, and a grant condition indicating whether or not may be granted the operation content And identifying the operation content corresponding to the right identifier included in the request signal transmitted from the predetermined communication node via the subscriber management server by referring to the database, and associating with the identified operation content when was the grant condition is satisfied, and a control unit which transmits specified the operation content to the subscriber management server,
The mobile communication system, wherein the subscriber management server operates the subscriber information based on operation content received from the subscriber control server.   The mobile communication system according to claim 1, wherein the communication node is a mobile terminal.   The mobile communication system according to claim 2, wherein the request signal is a connection request signal transmitted by the mobile terminal when connection is started.   The mobile communication system according to claim 2, wherein the request signal is a request signal transmitted at an arbitrary timing after the mobile terminal is connected.   The mobile communication system according to claim 4, wherein the post-connection request signal is a subscriber information update request signal.   The mobile communication system according to claim 1, wherein the communication node is a radio base station.   7. The mobile communication according to claim 6, wherein the radio base station holds a plurality of the right identifiers and determines a right identifier to be given to a connection request from a mobile terminal according to a predetermined condition. system. Database that stores in association with the operation content to the subscriber information held in subscriber management server, and rights identifier to identify the operation content, and a grant condition indicating whether or not may be granted the operation content When,
By referring to the database, the operation content corresponding to the right identifier included in the request signal transmitted from the predetermined communication node via the subscriber management server is specified and associated with the specified operation content subscriber control server, wherein the when the grant condition is satisfied, and a control means for transmitting the identified the operation content to the subscriber management server. Stored in a database in association with the operation content to the subscriber information held in subscriber management server, and rights identifier to identify the operation content, and a grant condition indicating whether or not may be granted the operation content And
By referring to the database, the operation content corresponding to the right identifier included in the request signal transmitted from the predetermined communication node via the subscriber management server is specified and associated with the specified operation content when the grant condition is satisfied, it sends the identified the operation content to the subscriber management server,
The subscriber information operation method, wherein the subscriber information is operated based on the specified operation content in the subscriber management server.

Images