JP4813330B2 - Communication control method, control node, and communication control apparatus - Google Patents

Description

  The present invention relates to a communication control method, a control node, and a communication control apparatus.

Non-Patent Document 1 describes the specifications of 3GPP (3rd Generation Partnership Project), which is a standard for mobile communication systems. According to Non-Patent Document 1, a plurality of telephone numbers can be registered for one IMSI (International Mobile User Identity) recorded in a SIM (Subscriber Identification Module) of one mobile device.
3GPP TS31.102 4.2.26, Version 6.15.0, [online], [retrieved on 16 October 2006], Retrieved from the Internet: <URL: http: //www.3gpp.org/ftp/Specs/2006-09 /Rel-6/31_series/31102-6f0.zip>.

  As described above, in the 3GPP standard, a plurality of telephone numbers can be registered for one IMSI. However, for a service provider that permits packet connection only to one of the plurality of telephone numbers, a telephone number other than the telephone number permitted for such packet connection is used. If a packet connection request is made, the packet connection is rejected. Accordingly, an object of the present invention is to provide a communication control method, a control node, and a communication control apparatus capable of performing packet communication by connecting to a service provider even when a plurality of telephone numbers are registered in one mobile device. The purpose is to provide.

  The present invention permits packet connection with a mobile device having a plurality of telephone numbers set for each of a plurality of communication networks according to the telephone number of the mobile device set in a predetermined communication network among the plurality of communication networks. The mobile station identification information and the notification number are stored in response to a packet transmission request from the mobile station that includes a service provider and a notification number to be notified to the call destination of the mobile station and includes the mobile station identification information. The mobile switching area of the mobile station that transmits a packet connection request to a service provider including a control node that transmits a packet connection request transmitted from the mobile switching area to the service provider, and a telephone number and identification information are associated with each other A communication control method for roaming that is held in the communication control method, and a reception step in which a control node receives a packet connection request from a visited exchange; When the notification number included in the packet connection request is not used in a communication network that permits packet connection, the control node inquires the communication control device about the telephone number using the identification information of the mobile device included in the packet connection request. In response to the inquiry, the communication node notifies the control node of the telephone number corresponding to the identification information of the mobile device, and the control node uses the telephone number notified in the notification step to And a transmission step of transmitting a packet connection request. Then, after the reception step, if the notification number included in the packet connection request is used in a communication network that permits packet connection, control is performed in the transmission step without passing through the inquiry step and the notification step. The node transmits a packet connection request to the service provider using the notification number.

  In addition, the present invention provides the notification number transmitted from the mobile switch of the mobile device that holds the notification number to be notified to the call destination of the mobile device having a plurality of telephone numbers set for a plurality of communication networks. And packet connection request of the mobile device including identification information of the mobile device is permitted for packet connection with the mobile device according to a telephone number of the mobile device set in a predetermined communication network among a plurality of communication networks. When the control node transmits to the service provider, the receiving means for receiving the packet connection request from the visited exchange, and the notification number included in the packet connection request is not used in the communication network permitted for the packet connection. Inquiry means for inquiring the telephone number to the communication control device that holds the telephone number and the identification information in association with each other using the identification information of the mobile device included in the packet connection request Depending using a telephone number corresponding to the identification information notified from the communication control device moving machine, and transmitting means for transmitting a packet connection request to the service provider, characterized in that.

  As described above, when the telephone number permitted by the service provider for the packet connection with the mobile device and the notification number of the mobile device are different from each other, the control node transmits the packet from the roaming communication control device that holds the telephone number. Get a phone number. Therefore, packet communication can be performed even for a service provider that permits packet connection only to one telephone number among a plurality of telephone numbers registered in one mobile device.

  The present invention also relates to a roaming communication control apparatus that is connected to the control node and holds a plurality of telephone numbers of one mobile station set for each of a plurality of communication networks. When an inquiry from the control node is received from the control node regarding one of the numbers for which packet connection is permitted by the service provider, the telephone number is notified to the control node. Accordingly, a mobile device in which a plurality of telephone numbers are set for each of a plurality of communication networks can perform packet communication with a service provider that permits packet connection to one of the plurality of telephone numbers. .

  According to the present invention, even when a plurality of telephone numbers are registered in one mobile device, packet communication can be performed by connecting to a service provider.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings. In the description of the drawings, if possible, the same elements are denoted by the same reference numerals, and redundant description is omitted. With reference to FIG. 1, the structure of the communication control system 1 which concerns on embodiment is demonstrated. The communication control system 1 includes a mobile device 10, an SGSN 20 (Serving GPRS Support Node), a GGSN 30 (Gate GPRS Support Node), a roaming GW 40 (GateWay), an HLR_own network 50 (Home Location Register), an HLR_other network 60, a DNS 70 (Domain Name System) and ISP 80 (Internet Service Provider). The SGSN 20 performs wireless communication with the mobile device 10 and is wired to the GGSN 30, the roaming GW 40, and the DNS 70. The GGSN 30 is wired to the roaming GW 40 and the ISP 80. The roaming GW 40 is wired to the HLR_own network 50 and the HLR_other network 60.

  The mobile device 10 is a communication terminal such as a mobile phone, and the IMSI (“IMSI: own network” described later) representing the identification information of the mobile device 10 recorded in the SIM of the mobile device 10 has a plurality of telephone numbers. Registration is possible. Hereinafter, the local network means a communication network with which the mobile device 10 is contracted. The other network means a communication network other than the own network. Hereinafter, a predetermined other network is assumed. The communication network in which the mobile device 10 is located is either the own network or another network, but in the embodiment, the own network will be described as a communication network in which the mobile device 10 is located. Here, the description “A: B” means “A set to B”. For example, the description “IMSI: own network” means “IMSI (Mobile Station ISDN number definition) set in the own network”, and the description “MSISDN: own network” is “set in the own network”. "MSISDN". Also, the description “IMSI: other network” means “IMSI set in another network”, and the description “MSISDN: other network” means “MSISDN set in another network”. is doing. In the following, the telephone number may be referred to as MSISDN.

  The SGSN 20 is a visited switch for packet communication provided in a communication network in which the mobile device 10 is located. The SGSN 20 holds “IMSI: own network” and the notification number (“MSISDN: notification number”) of the mobile device 10 to be notified to the call destination of the mobile device 10. When the SGSN 20 receives a transmission request for a packet including “IMSI: own network” from the mobile device 10, the SGSN 20 performs address resolution processing based on the “IMSI: own network”. This address resolution process is a process for acquiring a GGSN address that is a global IP address of the GGSN 30 that transmits a packet connection request to the ISP 80. Since the DNS 70 provided in the own network has the GGSN address, the SGSN 20 provides the DNS 70 with the own network based on “IMSI: own network” included in the packet transmission request from the mobile device 10. The GGSN address of the received GGSN 30 is inquired (address resolution request). Then, the SGSN 20 transmits a packet connection request for the ISP 80 to the GGSN 30 in response to the packet transmission request from the mobile device 10. This packet connection request includes “IMSI: own network” and “MSISDN: notification number”. When the communication network in which the mobile device 10 is located is another network, the address resolution request transmitted from the SGSN 20 is sent to the DNS provided in the other network (that is, the communication network in which the mobile device 10 is located). To the DNS 70 provided in the local network. In this case, the SGSN 20 is an exchange provided in another network.

  The GGSN 30 is a packet communication control node provided in its own network. The GGSN 30 is a control node that transmits this packet connection request to the ISP 80 that permits the packet connection with the mobile device 10 in response to the packet connection request of the mobile device 10 transmitted from the SGSN 20.

  The roaming GW 40 is a communication control device that performs roaming processing between a plurality of communication networks such as a communication network in which the mobile device 10 is located, a local network, and other networks. The roaming GW 40 performs an attach / position registration process shown in the sequence of FIG. The roaming GW 40 records the MSISDN designated by the mobile device 10 as the MSISDN notified to the call destination of the mobile device 10 in its own memory. The roaming GW 40 receives a plurality of subscriber information for the mobile device 10 transmitted from each of a plurality of communication networks (the local network and other networks) in response to the attach / location registration request of the mobile device 10. The roaming GW 40 notifies the call destination of the mobile station 10 of the MSISDN that matches the MSISDN recorded in the memory among the plurality of MSISDNs included in each of the received plurality of subscriber information. Set to. The roaming GW 40 transmits subscriber information including the set notification number to the SGSN 20. When the roaming GW 40 performs the attach / location registration process, a plurality of subscriber information for the mobile device 10 is recorded in its own memory, and any one of the plurality of MSISDNs for the mobile device 10 is used as a notification number. Recorded in SGSN20.

  In addition, the roaming GW 40 associates the MSISDN (IMSI: own network) of the mobile device 10 set in the communication network (own network) to which the ISP 80 permits packet connection with the mobile device 10 with “IMSI: own network”. Hold. When the roaming GW 40 receives a subscriber information acquisition request (including “IMSI: own network”) for the mobile device 10 in its own network from the GGSN 30, the roaming GW 40 sends a response to the subscriber information acquisition request to the GGSN 30. Do. This response includes “MSISDN: own network” which is the MSISDN of the mobile device 10 set in the communication network (own network) in which the packet connection with the mobile device 10 is permitted by the ISP 80.

  The HLR_own network 50 is an HLR provided in the own network, and manages subscriber information of the mobile device 10 including IMSI and MSISDN. The IMSI and MSISDN of the mobile device 10 managed by the HLR_own network 50 are referred to as “IMSI: own network” and “MSISDN: own network”, respectively. The HLR_other network 60 is an HLR provided in the other network, and manages subscriber information of the mobile device 10 including IMSI and MSISDN. The IMSI and MSISDN of the mobile device 10 managed by the HLR_other network 60 are referred to as “IMSI: other network” and “MSISDN: other network”, respectively. The subscriber information includes contract plan information and contract service information of the subscriber, IMSI, MSISDN, and the like, and includes various information related to the contract of the mobile device 10.

  The DNS 70 is a DNS provided in the own network, and holds the GGSN address of the GGSN 30 provided in the own network. When the DNS 70 receives the address resolution request (query about the GGSN address of the GGSN 30) from the SGSN 20, the DNS 70 transmits an address resolution response including the GGSN address to the SGSN 20. The ISP 80 is a service provider that provides various services such as downloading of content data to the mobile device 10 and the like, and permits packet connection with the mobile device 10 according to the MSISDN in the mobile device 10's own network. The ISP 80 does not permit the packet connection to the MSISDN of the mobile device 10 in a communication network other than its own network. That is, in the embodiment, the MSISDN for which the packet connection with the mobile device 10 is permitted by the ISP 80 is the MSISDN of the own network (“MSISDN: own network”).

  Next, the configuration of the GGSN 30 will be described with reference to FIGS. As shown in FIG. 2, the GGSN 30 physically includes a CPU 31, a RAM 32, a ROM 33, an input device 34, an output device 35, and a communication device 36, which are connected to a bus 37. The CPU 31 centrally controls the GGSN 30 by loading predetermined computer software stored in a built-in memory such as the ROM 33 into the RAM 32 and executing it. The input device 34 is a data input device and outputs input data to the CPU 31. The output device 35 is a display device such as an LCD, and displays data input from the CPU 31 on the LCD or the like. The communication device 36 has an interface for performing communication among the SGSN 20, the roaming GW 40, the ISP 80, and the like.

  The CPU 31 implements a plurality of functions shown in FIG. FIG. 3 is a block diagram showing functions of the GGSN 30 realized by the CPU 31. The GGSN 30 functionally includes a reception unit 311 (reception unit), an inquiry unit 312 (inquiry unit), and a transmission unit 313 (transmission unit). The receiving unit 311 to the transmitting unit 313 are functions realized by the CPU 31 executing the above-described computer software and operating the components of the GGSN 30 illustrated in FIG. In particular, the CPU 31 uses the reception unit 311 to the transmission unit 313 to execute processing (packet transmission control processing) performed by the GGSN 30 illustrated in FIG.

  The receiving unit 311 receives a packet connection request including the notification number of the mobile device 10 (“MSISDN: notification number”) and the “IMSI: own network” of the mobile device 10 from the SGSN 20. This packet connection request is created by the SGSN 20 in response to a packet transmission request from the mobile device 10.

  When the “MSISDN: notification number” included in the packet connection request received by the reception unit 311 is not used in the communication network (local network) permitted to connect by the ISP 80, the inquiry unit 312 The “IMSI: own network” inquiry (subscriber information acquisition request) is made to the roaming GW 40 using “IMSI: own network” included in the request. This subscriber information acquisition request includes “IMSI: own network”. That is, in the case of MSISDN in which “MSISDN: number for notification” is used in a communication network (local network) that is permitted to connect to the packet by ISP 80, the inquiry unit 312 does not request acquisition of subscriber information of mobile device 10. In the case of MSISDN in which “MSISDN: notification number” is used in a communication network (other network) in which packet connection is not permitted by ISP 80, an inquiry unit 312 makes a request for acquiring subscriber information of mobile device 10. Is called. In this case, the GGSN 30 can determine whether the list of MSISDNs belonging to the communication network permitted by the ISP 80 for packet connection (“MSISDN: own network” is used in the communication network permitted by the ISP 80 for packet connection). The inquiry unit 312 refers to this list and determines whether or not “MSISDN: notification number” is used in a communication network (local network) permitted for packet connection by the ISP 80. Determine whether.

  The transmission unit 313 is notified from the roaming GW 40 in response to the subscriber information acquisition request by the inquiry unit 312 and belongs to the MSISDN corresponding to “IMSI: own network” of the mobile device 10 (which belongs to a communication network in which packet connection is permitted from the ISP 80). A packet connection request (including “MSISDN: own network”) is transmitted to the ISP 80 using “MSISDN: own network”).

  Next, the attach / position registration process according to the embodiment will be described with reference to FIG. FIG. 4 is a sequence for explaining the attach / position registration process. First, the roaming GW 40 records the MSISDN designated by the user from the mobile device 10 as the MSISDN notified to the callee of the mobile device 10 in the memory of the own device (designated telephone number recording step). The designated MSISDN is, for example, the MSISDN of the local network or another network, and is transmitted from the mobile device 10 to the roaming GW 40 via the SGSN 20.

  Thereafter, the mobile device 10 transmits an attach / location registration request including “IMSI: own network” to the SGSN 20 (step S1). The SGSN 20 receives this transmission, and receives “IMSI: own network” and “vrrNumber: The attach / position registration request including “MSC” is transmitted to the roaming GW 40 (step S2). Here, vlrNumber means a number for identifying a VLR (Visitor Location Register). After step S2, the roaming GW 40 is transmitted from each of a plurality of communication networks (own network and other networks) in response to the attach / location registration request of the mobile device 10 transmitted from the mobile device 10 via the SGSN 20. A plurality of subscriber information (subscriber information for each communication network) is received (steps S3 to S6, subscriber information receiving step).

  In this subscriber information reception step, the roaming GW 40 first starts attachment / location registration to its own network (step S3). In step S <b> 3, the roaming GW 40 converts “vlrNumber: MSC” included in the attach / location registration request transmitted from the SGSN 20 into “vlrNumber: roaming GW”. After this conversion, the roaming GW 40 executes attach / position registration to its own network (step S4). In step S <b> 4, the roaming GW 40 transmits an attach / location registration request including “IMSI: own network” and “vlrNumber: roaming GW” to the HLR_own network 50. In response to the attach / location registration request, the HLR_own network 50 downloads subscriber information for the mobile device 10 managed by the HLR_own network 50 to the roaming GW 40. This downloaded subscriber information includes “IMSI: own network” and “MSISDN: own network”. Thereafter, the roaming GW 40 transmits a subscriber information download response to the HLR_own network 50, and the HLR_own network 50 transmits an attach / location registration response to the roaming GW 40 in response to this response. The attach / location registration response includes “hlrNumber: HLR_own network” (step S4). Here, hlrNumber means a number for identifying the HLR.

  After the attach / position registration to the own network as described above, the roaming GW 40 starts the attach / position registration to another network (step S5). In this step S5, the roaming GW 40 converts “IMSI: own network” included in the attach / location registration request transmitted from the SGSN 20 into “IMSI: other network”, and converts “vlrNumber: MSC” to “vrrNumber: To "Roaming GW". After this conversion, the roaming GW 40 executes attachment / location registration to another network (step S6).

  In step S 6, the roaming GW 40 first transmits an attach / location registration request including “IMSI: other network” and “vlrNumber: roaming GW” to the HLR_other network 60. In response to the attach / location registration request, the HLR_other network 60 downloads subscriber information for the mobile device 10 managed by the HLR_other network 60 to the roaming GW 40. This downloaded subscriber information includes “IMSI: other network” and “MSISDN: other network”. Thereafter, the roaming GW 40 transmits a subscriber information download response to the HLR_other network 60, and the HLR_other network 60 transmits an attach / location registration response to the roaming GW 40 in response to this response. This attach / location registration response includes “hlrNumber: HLR_other network” (step S6).

  After step S6, the roaming GW 40 performs roaming in the designated telephone number recording step among the MSISDNs included in each of the plurality of subscriber information acquired from the HLR_own network 50 and the HLR_other network 60 in steps S3 to S6. The MSISDN that matches the MSISDN recorded in the memory of the GW 40 is set as a notification number to be notified to the call destination of the mobile device 10 (step S7, notification number setting step). The set MSISDN is “MSISDN: number for notification”. “MSISDN: Notification Number” is “MSISDN: Local Network” when the notification number is MSISDN of the local network, and “MSISDN: Other Network” when the notification number is MSISDN of the other network. In this step S7, the subscriber information including the notification number of the mobile device 10 is stored in its own memory in association with a plurality of subscriber information for the mobile device 10.

  After step S7, the roaming GW 40 downloads subscriber information including “IMSI: own network” and “MSISDN: notification number” to the SGSN 20 (step S8, subscriber information transmission step). After step S8, the SGSN 20 stores “IMSI: own network” and “MSISDN: notification number” included in the subscriber information downloaded from the roaming GW 40 in the VLR of the SGSN 20 (step S9, notification number recording step). The subscriber information download response is transmitted to the roaming GW 40 (step S10). Further, after step S8, the SGSN 20 associates “IMSI: own network” and “MSISDN: notification number” with the MSRN of the mobile device 10 and stores them in the VLR.

  After receiving the subscriber information download response from the SGSN 20 after step S10, the roaming GW 40 sets “hlrNumber: roaming GW” (step S11), and attaches “hlrNumber: roaming GW” to the location / registration response. Are transmitted to the SGSN 20 (step S12), and the SGSN 20 transmits the attach / location registration response to the mobile device 10 in response to the response from the roaming GW 40 (step S13). Through the process in step S13, the mobile device 10 can confirm the completion of the series of attach / position registration processes described above. Each time the attach / location registration process shown in the sequence of FIG. 4 is performed by the roaming GW 40, a plurality of subscriber information for the mobile device 10 recorded in the memory of the roaming GW 40 and set for each communication network is updated. The

  Next, packet transmission control processing (communication control processing) according to the embodiment will be described with reference to FIG. FIG. 5 is a sequence for explaining this packet transmission control process. The packet transmission control process shown in the sequence of FIG. 5 is performed after the attach / position registration process shown in the sequence of FIG. First, the mobile device 10 transmits a packet transmission request for the ISP 80 to the SGSN 20 (step S21). This packet transmission request includes “IMSI: own network”. After step S21, when receiving a packet transmission request including “IMSI: own network” from the mobile device 10, the SGSN 20 performs address resolution processing based on “IMSI: own network” (step S22).

  The SGSN 20 makes an inquiry (address resolution request) of the GGSN address of the GGSN 30 provided in the own network to the DNS 70 (step S23). When the DNS 70 receives the address resolution request transmitted from the SGSN 20 in step S23, the DNS 70 transmits a response to the address resolution to the SGSN 20 (step S24). This response includes the GGSN address of GGSN30. When the SGSN 20 receives a response to the address resolution including the GGSN address from the DNS 70 in step S24, the SGSN 20 transmits a packet connection request to the ISP 80 to the GGSN 30 using the GGSN address (step S25).

  This packet connection request includes “IMSI: own network” and “MSISDN: notification number”. When the communication network in which the mobile device 10 is located is another network, the address resolution request transmitted from the SGSN 20 is transmitted to the DNS 70 via the DNS provided in the other network. That is, the SGSN 20 inquires of the DNS 70 about the GGSN address of the GGSN 30 provided in its own network (request for address resolution) via the DNS of the other network (step S23). When the DNS 70 receives the address resolution request transmitted from the SGSN 20 in step S23 via the DNS of the other network, the DNS 70 transmits a response to this address resolution to the SGSN 20 via the DNS of the other network (step S24).

  After step S25, when the reception unit 311 of the GGSN 30 receives the packet connection request transmitted from the SGSN 20 (step S26, reception step), the inquiry unit 312 is included in the packet connection request received by the reception unit 311. When the “MSISDN: notification number” is not used in the communication network (local network) permitted to connect to the packet by the ISP 80, the process of converting the MSISDN into the local network “MSISDN: local network” is started. First, the “IMSI: own network” inquiry (subscriber information acquisition request) is made to the roaming GW 40 using “IMSI: own network” included in the packet connection request (step S27, inquiry step). Note that in the case of MSISDN in which “MSISDN: notification number” is used in a communication network (local network) that is permitted to connect to the packet by ISP 80, the inquiry unit 312 does not request acquisition of subscriber information of the mobile device 10. Further, the process proceeds to step S29 without passing through step S28, and a packet connection request to the ISP 80 is made using "MSISDN: own network". The subscriber information acquisition request includes “IMSI: own network”.

  In step S27, the inquiry unit 312 transmits a subscriber information acquisition request including “IMSI: own network” to the roaming GW 40 (step S27, inquiry step), and the roaming GW 40 receives the subscriber information after step S27. When the acquisition request is received from the GGSN 30, “MSISDN: own network” is acquired based on “IMSI: own network” included in the subscriber information acquisition request, and a response (subscriber information) including this “MSISDN: own network” is acquired. (Response to the acquisition request) is transmitted to the GGSN 30 (step S28, transmission step).

  After receiving a response to the subscriber information acquisition request from the roaming GW 40, the transmission unit 313 transmits the packet connection request of the mobile device 10 to the ISP 80 using “MSISDN: own network” included in this response ( Step S29). This packet connection request includes “MSISDN: own network” acquired from the roaming GW 40. After step S29, upon receiving the packet connection request from the GGSN 30, the ISP 80 permits the packet connection with the mobile device 10 based on “MSISDN: own network” included in the packet connection request. Conventional packet transmission control (step S30).

  Next, the effect of GGSN30 which concerns on embodiment is demonstrated. It is transmitted from the SGSN 20 that holds a notification number to be notified to the call destination of the mobile device 10 having a plurality of MSISDNs set for each of a plurality of communication networks, and this notification number and the IMSI (“IMSI: own network” The packet connection request of the mobile device 10 including “”) is transmitted to the mobile device 10 according to the MSISDN (“MSISDN: own network”) of the mobile device 10 set in the local network among the plurality of communication networks. The GGSN 30 according to the embodiment that transmits to the permitted ISP 80 includes a reception unit 311, an inquiry unit 312, and a transmission unit 313. The receiving unit 311 receives a packet connection request including the notification number from the SGSN 20. The inquiry unit 312 determines that the notification number included in the packet connection request is not used in the local network to which packet connection is permitted (the communication network to which “MSISDN: local network” belongs) (for example, the packet connection request is set by the ISP 80). The determination is made based on the list of MSISDNs belonging to the permitted communication network.) The MSISDN that is permitted to connect the packet by using the IMSI (“IMSI: own network”) of the mobile device 10 included in the packet connection request. And “IMSI: own network” are associated with each other and the roaming GW 40 is inquired of this telephone number. Then, the transmission unit 313 uses the “MSISDN: own network” corresponding to the “IMSI: own network” of the mobile device 10 notified from the roaming GW 40 in response to this MSISDN inquiry, and connects the packet connection of the mobile device 10 to the ISP 80. Send a request.

  As described above, when the MSISDN permitted to connect to the mobile device 10 by the ISP 80 and the notification number of the mobile device 10 are different from each other, the GGSN 30 acquires the MSISDN from the roaming GW 40 that holds the MSISDN. Therefore, packet communication can be performed also for the ISP 80 that permits packet connection only to one MSISDN among a plurality of MSISDNs registered in the mobile device 10.

  Furthermore, the effect of the roaming GW 40 will be described. The roaming GW 40, which is connected to the GGSN 30 and holds a plurality of MSISDNs of the mobile station 10 set for each of a plurality of communication networks, sends an inquiry from the GGSN 30 to one MSISDN that is permitted to connect to the packet by the ISP 80. When received, this MSISDN is notified to this inquiry source (GGSN 30). Accordingly, the mobile device 10 in which a plurality of MSISDNs are set for each of a plurality of communication networks can perform packet communication with the ISP 80 that permits packet connection to one telephone number of the plurality of MSISDNs.

It is a figure which shows the structure of the communication control system which concerns on embodiment. It is a figure which shows the structure of GGSN which concerns on embodiment. It is a figure which shows the structure of GGSN which concerns on embodiment. It is a sequence for demonstrating the attachment and position registration process which concerns on embodiment. It is a sequence for demonstrating the packet transmission control process which concerns on embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Communication control system, 10 ... Mobile station, 20 ... SGSN, 30 ... GGSN, 31 ... CPU, 32 ... RAM, 33 ... ROM, 34 ... Input device, 35 ... Output device, 36 ... Communication device, 37 ... Bus, 40 ... roaming GW, 50 ... HLR_own network, 60 ... HLR_other network, 70 ... DNS, 80 ... ISP, 311 ... reception unit, 312 ... inquiry unit, 313 ... transmission unit.

Claims (4)

A service provider that permits packet connection with a mobile device having a plurality of telephone numbers set for each of a plurality of communication networks in accordance with a telephone number of the mobile device set in a predetermined communication network among the plurality of communication networks; The mobile station identification information and the notification number in response to a packet transmission request from the mobile station that holds a notification number to be notified to the call destination of the mobile station and includes the mobile station identification information A mobile switching station that transmits a packet connection request to the service provider, a control node that transmits the packet connection request transmitted from the visiting switch to the service provider, the telephone number, and the identification A communication control method using a roaming communication control device that holds information in association with each other,
A receiving step in which the control node receives the packet connection request from the serving exchange;
When the notification number included in the packet connection request is not used in the communication network permitted for the packet connection, the control node uses the identification information of the mobile device included in the packet connection request to communicate with the communication node. An inquiry step for inquiring the telephone number of the control device;
In response to the inquiry, the communication control device notifies the control node of the telephone number corresponding to the identification information of the mobile device;
A communication control method, comprising: a transmission step in which the control node transmits the packet connection request to the service provider using the telephone number notified in the notification step.   After the receiving step, when the notification number included in the packet connection request is used in a communication network permitted for the packet connection, without passing through the inquiry step and the notification step, The communication control method according to claim 1, wherein in the transmission step, the control node transmits the packet connection request to the service provider using the notification number. The notification number and the identification of the mobile device transmitted from the local exchange of the mobile device holding the notification number to be notified to the call destination of the mobile device having a plurality of telephone numbers set for each of a plurality of communication networks A packet connection request of the mobile device including information is transmitted to a service provider that permits packet connection with the mobile device according to a telephone number of the mobile device set in a predetermined communication network among the plurality of communication networks. A control node,
Receiving means for receiving the packet connection request from the visited exchange;
When the notification number included in the packet connection request is not used in the communication network permitted for the packet connection, using the identification information of the mobile device included in the packet connection request, the telephone number and the Inquiry means for inquiring of the telephone number to a communication control device that holds the identification information in association with each other;
Transmission means for transmitting the packet connection request to the service provider using the telephone number notified from the communication control device in response to the inquiry and corresponding to the identification information of the mobile device. Control node. A communication control device for roaming connected to the control node according to claim 3 and holding a plurality of telephone numbers of one mobile station set for each of a plurality of communication networks,
The communication control device, wherein when receiving an inquiry from the control node of one of the plurality of telephone numbers for which a packet connection is permitted by a service provider, the communication node is notified of the telephone number.

Images