JP2016189538A - Connection control device, connection control system, connection control program, and connection control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a connection control device, connection control system, connection control program, and connection control method that allow a terminal device to perform packet communication, and also to provide a connection control device, connection control system, connection control program, and connection control method that allow a terminal device to obtain effective APN information.SOLUTION: A connection control device comprises a processor that performs control so as to receive a connection request transmitted from a terminal device, and to transmit effective network connection destination information to the terminal device when the received connection request does not include network connection destination information specifying a connection destination to a network or includes ineffective network connection destination information.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a connection control device, a connection control system, a connection control program, and a connection control method.

  In recent years, SIM (Subscriber Identity Module) -free terminal devices and terminal devices provided by MVNO (Mobile Virtual Network Operator) operators have become widespread. The user can use the terminal device overseas by purchasing a SIM card of an overseas local business operator and inserting the SIM card into the terminal device. Alternatively, the user can use the terminal device by purchasing a SIM card of an MVNO operator and inserting the SIM card into the terminal device.

  In such a terminal device, an APN (Access Point Name) may be set by the user himself / herself. The APN is, for example, a character string that specifies a connection destination when performing packet communication by connecting a terminal device to a network. For example, the user sets APN for the terminal device by inputting APN information to the terminal device. By setting the APN, the terminal device can access the network, and packet communication (or data communication) via the network becomes possible.

  As a technique related to such mobile communication, for example, there are the following techniques. That is, the mobile station transmits a PDN (Packed Data Network) connectivity request including an APN for local IP (Internet Protocol) access to an MME (Mobility Management Entity), and establishes a PDN connection in the MME based on the request. Technology.

  According to this technique, the home base station owner or the like can set access authority for each service for a plurality of services provided using the local IP access function of the home base station.

  In this technique, the mobile station acquires APN information assigned to the home base station when connected to the home base station by SMS (Short Message Service).

  In addition, the gateway node determines whether or not there is a mobile VPN (Virtual Private Network) service request from the connection destination information included in the control signal transmitted from the mobile terminal, and when the request is detected, the IP address of the gateway node is set to the subscriber node. There is also a technique for notifying a mobile terminal via a network.

  According to this technology, a mobile VPN service can be provided without using a mobile tunnel in an IPv6 mobile packet network.

JP 2012-249318 A JP 2001-326697 A

  However, the APN setting by the user himself may not be performed because the user feels troublesome. Alternatively, an incorrect APN setting may be performed due to an input error by the user or an inability to obtain updated APN information. In either case, the terminal device cannot perform packet communication because the APN is not set correctly.

  Regarding the technology for acquiring APN information by SMS as described above, for example, when a user makes a contract without an SMS option, the terminal device cannot use SMS and cannot acquire APN information by SMS. In this case, the terminal device cannot perform packet communication.

  In addition, regarding the technique for notifying the IP address of the gateway node from the gateway node via the subscriber node, there is no discussion about how to obtain the APN information. Accordingly, packet communication may not be performed even with this technique.

  Accordingly, one disclosure is to provide a connection control device, a connection control system, a connection control program, and a connection control method that can perform packet communication in a terminal device.

  In addition, one disclosure is to provide a connection control device, a connection control system, a connection control program, and a connection control method that enable acquisition of valid APN information in a terminal device.

  According to one disclosure, the connection control device receives a connection request transmitted from a terminal device, and the received connection request does not include network connection destination information specifying a connection destination to the network or is not effective When the network connection destination information is included, the processor includes a processor that controls to transmit the valid network connection destination information to the terminal device.

  According to one disclosure, it is possible to provide a connection control device, a connection control system, a connection control program, and a connection control method that can perform packet communication in a terminal device. Further, according to one disclosure, it is possible to provide a connection control device, a connection control system, a connection control program, and a connection control method that can acquire correct APN information in a terminal device.

FIG. 1 is a diagram illustrating a configuration example of a connection control system. FIG. 2 is a diagram illustrating a configuration example of a communication system. 3A is a diagram illustrating a terminal device, and FIG. 3B is a diagram illustrating a configuration example of a base station device. FIG. 4A illustrates each configuration example of HSS, MME, SGW, and PDN GW, and FIG. 4B illustrates a configuration example of the APN information notification server. FIG. 5 is a diagram illustrating an example of the entire sequence. FIG. 6 is a diagram illustrating an example of the entire sequence. FIG. 7 is a diagram illustrating an example of the entire sequence. 8A is a diagram illustrating a configuration example of the HSS correspondence table, and FIG. 8B is a diagram illustrating a configuration example of the SGW correspondence table. FIG. 9 is a flowchart showing an operation example of the terminal. FIG. 10 is a flowchart showing an operation example of the terminal. FIG. 11 is a flowchart showing an operation example of HSS. FIG. 12 is a flowchart illustrating an operation example of the SGW. FIG. 13 is a flowchart illustrating an operation example of the SGW. FIG. 14 is a flowchart showing an operation example of the APN information notification server. FIG. 15 is a diagram illustrating a configuration example of a communication system. FIG. 16 is a diagram illustrating a configuration example of a 3GPP AAA server. FIG. 17 is a diagram illustrating an example of the entire sequence. FIG. 18 is a diagram illustrating an example of the entire sequence. FIG. 19 is a diagram illustrating an example of the entire sequence. 20A is an HSS correspondence table, FIG. 20B is an SGW correspondence table, FIG. 20C is an AAA correspondence table, and FIG. 20D is a diagram illustrating configuration examples of an APN correspondence table. FIG. 21 is a flowchart showing an operation example of the APN information notification server.

  Hereinafter, modes for carrying out the present invention will be described.

[First Embodiment]
A first embodiment will be described. FIG. 1 shows a configuration example of a connection control system 10 in the first embodiment. The connection control system 10 includes a terminal device 100 and a connection control device 300.

  The terminal device 100 is a movable communication terminal such as a feature phone or a smartphone. The terminal device 100 includes a second processor 103. The terminal device 100 can be inserted with a SIM card, and the terminal device can be used with the SIM card. Such a terminal device 100 may be referred to as a SIM free terminal device, for example.

  When connecting to the network, the second processor 103 transmits a connection request to the connection control device. The connection request does not include network connection destination information or is network connection destination information that is not valid. As the network connection destination information, for example, there is APN information. The network connection destination information that is not valid is, for example, network connection destination information that is not the network connection destination information of the network contracted by the user who uses the terminal device 100. Network connection destination information that is not valid may be set when a user who uses the terminal device 100 erroneously inputs the network connection destination information.

  The connection control device 300 includes a first processor 305. The first processor 305 receives a connection request, and when the received connection request does not include network connection destination information or includes invalid network connection destination information, the first processor 305 displays valid network connection destination information. Control to transmit to the terminal device 100.

  The valid network connection destination information includes, for example, network connection destination information indicating the connection destination of the network contracted by the user, updated network connection destination information, and the like.

  For example, when the user does not set network connection destination information for the terminal device 100 or sets wrong network connection destination information, the network connection destination information is not included or is not valid. A connection request is transmitted from the terminal device 100.

  There are a plurality of control methods. For example, the connection control device 300 holds connection information of valid network connection destination information, and transmits the connection information to the transfer control device when the connection request is received. The transfer control device sets a connection path from the terminal device 100 to the information notification device based on the connection information, and notifies the terminal device 100 of valid network connection destination information from the information communication device. The connection information may be address information of the information notification device, or may be address information of a gateway device connected to the information notification device.

  As described above, in the first embodiment, for example, even when the user does not set network connection destination information or sets network connection destination information that is not valid, the connection control device 300 controls the terminal device 100. Valid network connection destination information is transmitted.

  Therefore, in the connection control system 10 according to the first embodiment, the terminal device 100 can connect to a network by making a connection request using valid network connection destination information, via the network. Packet communication can be performed. The terminal device 100 can also acquire valid APN information.

[Second Embodiment]
Next, a second embodiment will be described.

<Configuration example of communication system>
A configuration example of the communication system according to the second embodiment will be described. FIG. 2 is a diagram illustrating a configuration example of a communication system (or a connection control system, hereinafter sometimes referred to as “communication system”) 10.

  The communication system 10 is a terminal device (or UE (User Equipment), hereinafter sometimes referred to as “terminal”) 100, a base station device (or eNB (evolved Node B), hereinafter sometimes referred to as “base station”). 200. The communication system 10 includes an HSS (Home Subscriber Service) 300, an MME (Mobility Management Entity) 400, and an SGW (Serving Gateway) 500. Further, the communication system 10 includes a PDN GW (Packet Data Network Gateway) (A) 600-A, a PDN GW (B) 600-B, and networks 700-A and 700-B.

  Note that a network including the base station 200, the HSS 300, the MME 400, the SGW 500, and the PDN GW (A) 600-A and (B) 600-B may be referred to as a core network, for example.

  The terminal 100 is a movable communication terminal such as a feature phone, a smartphone, a tablet, a personal computer, or a game device. For example, the terminal 100 is a SIM (Subscriber Identity Module Card) -free terminal, a terminal provided by an MVNO (Mobile Virtual Network Operator, a virtual mobile communication carrier, hereinafter sometimes referred to as “MVNO”) carrier, or the like. It is. A SIM-free terminal is, for example, a terminal that can be used regardless of the type of SIM card. For example, the user can use the obtained SIM card by inserting it into the terminal 100. The SIM card is, for example, an IC (Integrated Circuit) card in which information such as a line number and an identification number that is distinguished from other SIM cards is stored. Information such as a line number stored in the SIM card may be referred to as SIM information, for example. The terminal 100 in the second embodiment is, for example, a terminal that can insert such a SIM card and can be used using the SIM card.

  Note that the MVNO operator is, for example, an operator that does not have a physical communication line network and provides a communication service by borrowing from an operator who owns the communication line network. A terminal provided by such an operator can be used using a SIM card provided by the operator.

  The base station 200 provides various services such as a call service and a web browsing service to the terminal 100 located in the service providing range. The base station 200 and the terminal 100 are wireless sections, and the base station 200 provides various services to the terminal 100 by exchanging wireless signals with the terminal 100.

  For example, the HSS 300 manages contract information of a subscriber who receives a service, and performs authentication for the terminal 100 (or a user who uses the terminal 100) based on the contract information. The HSS 300 is also a subscriber information management device, for example.

  For example, the MME 400 manages control signals and also manages the location of the terminal 100. The MME 400 is also a location management device, for example.

  A control channel that handles control signals or a function group thereof may be referred to as, for example, C-Plane (Control Plane). In FIG. 2, arrows indicated by solid lines represent exchange of control signals on the C-Plane. In addition, a traffic channel handling user data or a function group thereof may be referred to as U-Plane (User Plane), for example. In FIG. 2, an arrow indicated by a dotted line represents exchange of user data on the U-Plane.

  The SGW 500 sends, for example, an access request from the terminal 100 to the network (A) 700-A, the network (A) 700-A or the network (B) 700-B (or PDN GW (A) 600-A or PDN GW. (B) Transfer (or switch) to 600-B). The SGW 500 is also a transfer control device (or service control device), for example.

  The PDN GW (A) 600-A is connected to the network (A) 700-A and functions as a gateway connecting the network (A) 700-A and the core network.

  The PDN GW (B) 600-B is connected to the network 700-B and functions as a gateway that connects the network (B) 700-B and the core network.

  The PDN GW (A) 600-A and the PDN GW (B) 600-B are also access control devices, for example.

  The network (A) 700-A is, for example, a PDN (Packet Data Network) owned by a communication carrier or MVNO operator. A terminal 100 (or a user who uses the terminal 100) contracted with such a provider is connected to the network 700-A via the PDN GW (A) 600-A, and performs packet communication with a server or the like in the network 700-A. I do. Since such a network (A) 700-A is external to the core network, it may be referred to as an external network, for example.

  The communication carrier is, for example, a company that owns a physical communication network and provides communication services using such a communication network. A communication carrier operator and an MVNO operator may be collectively referred to as a service provider, for example.

  The network (B) 700-B is a dedicated network including the APN information notification server device 800, for example. The network (B) 700-B may be a PDN provided by a service provider, for example.

  The APN information notification server device (or information notification device, which may be hereinafter referred to as “APN information notification server”) 800 holds valid APN information and transmits valid APN information. The terminal 100 in which the APN setting is not correctly performed is guided to the APN information notification server 800 via the PDN GW (B) 600-B, and the APN information notification server 800 is effective for such a terminal 100. APN information is transmitted.

  The APN (or APN information) is, for example, a character string that specifies a connection destination when the terminal 100 is connected to a network (core network or network (A) 700-A) to perform packet communication. It is also network connection destination information that specifies the connection destination to the network. As an APN of the network (A) 700-A, for example, there is “Web # 1” that designates the PDN GW (A) 600-A (or the network (A) 700-A). Such an APN is a character string that identifies the service provider because it varies depending on the service provider. In the following description, APN and APN information are used without particular distinction.

  The APN information corresponds to the network connection destination information in the first embodiment, for example.

  Hereinafter, a configuration example of each device from the terminal 100 to the APN information notification server 800 will be described.

<1.1 Configuration example of terminal device>
FIG. 3A is a diagram illustrating a configuration example of the terminal 100. The terminal 100 includes an antenna 101, a wireless unit 102, a processor 103, an audio input / output unit 104, a memory 105, a touch sensor 108, and a display unit 109.

  The antenna 101 exchanges radio signals with the base station 200.

  The wireless unit 102 converts user data or the like output from the processor 103 into a wireless signal, and outputs the converted wireless signal to the antenna 101. In addition, the wireless unit 102 extracts user data and the like from the wireless signal output from the antenna 101 and outputs the extracted user data and the like to the processor 103.

  The processor 103 is, for example, a processing unit or a control unit that controls the terminal 100. The processor 103 reads out a program stored in a ROM (Read Only Memory) 106 and executes the read program to execute various processes and functions. For example, the processor 103 generates a C-PLANE connection request and a U-PLANE connection request, and transmits the generated connection requests to the base station 200. Details of functions or processing performed by the processor 103 will be described in an operation example.

  The processor 103 corresponds to, for example, the second processor 103 in the first embodiment.

  The audio input / output unit 104 converts the voice data output from the processor 103 into voice and outputs the voice to the user, or converts voice from the user into voice data and outputs the voice data to the processor 103.

  The memory 105 includes a ROM 106 and a RAM (Random Access Memory) 107.

  The touch sensor 108 is a sensor that detects, for example, that the user touches the touch screen displayed on the display unit 109 on the screen.

  The display unit 109 is, for example, a liquid crystal monitor, and displays an image, a touch screen, or the like under the control of the processor 103.

  The setting of APN is performed as follows, for example. That is, the user inputs APN information by operating the touch screen. The processor 103 detects APN information input by the user via the touch sensor 108, and stores the detected APN information in the RAM 107. Alternatively, the processor 103 receives the APN information via the wireless unit 102, stores the APN information in the RAM 107, and stores the information selected by the user by reading from the RAM 107 and storing the information selected by the user in the RAM 107 when setting the APN. Settings may be made. For example, the processor 103 reads the APN information from the RAM 107, and transmits an access request including the APN information to the base station 200, thereby enabling packet communication.

<1.2 Configuration example of base station apparatus>
FIG. 3B is a diagram illustrating a configuration example of the base station 200. The base station 200 includes an antenna 201, a wireless unit 202, a processor 203, a display unit 204, an input unit 205, a RAM 206, and an HDD (Hard Disk Drive) 207.

  The antenna 201 exchanges radio signals with the terminal 100.

  The wireless unit 202 converts user data or the like output from the processor 203 into a wireless signal, and outputs the converted wireless signal to the antenna 201. The wireless unit 202 also extracts user data and the like from the wireless signal output from the antenna 201, and outputs the extracted user data and the like to the processor 203.

  The processor 203 is, for example, a processing unit or a control unit that controls the base station 200. The processor 203 reads out a program stored in the RAM 206 and executes the read program to execute various processes and functions. For example, the processor 203 receives a C-PLANE connection request and a U-PLANE connection request transmitted from the terminal 100, and transmits these received connection requests to the MME 400 and the SGW 500. Details of functions or processing performed by the processor 203 will be described in an operation example.

  The display unit 204 is a liquid crystal monitor, for example, and displays information stored in the RAM 206 and the HDD 207. The input unit 205 is, for example, a keyboard or a touch screen displayed on the display unit 204.

<1.3 HSS configuration example>
FIG. 4A shows a configuration example of the HSS 300. The HSS 300 includes a display unit 301, an input unit 302, a RAM 303, an HDD 304, a processor 305, and a communication IF (Interface) 306.

  The display unit 301 is a liquid crystal monitor, for example, and displays information stored in the RAM 303 and the HDD 304 under the control of the processor 305. The input unit 302 is, for example, a keyboard or a touch screen displayed on the display unit 301.

  The processor 305 is a processing unit or a control unit that controls the HSS 300. The processor 305 executes various processes and functions in the HSS 300 by reading the program stored in the RAM 303 and executing the read program.

  The processor 305 corresponds to the first processor 305 in the first embodiment, for example.

  For example, the following processing is performed. That is, the processor 305 receives a connection authentication request from the MME 400 and authenticates the terminal 100. Further, the processor 305 determines whether or not valid APN information is included in the connection authentication request, and according to the determination result, the address information (hereinafter referred to as PDN GW (A) 600-A, (B) 600-B). , Which may be referred to as “PDN GW address information”) from the HDD 304, and transmits the address information to the SGW 500 via the MME 400. Details of functions or processing performed by the processor 305 will be described in an operation example.

  The HDD 304 stores, for example, contract information and an HSS correspondence table. The HSS correspondence table is, for example, a table that stores the correspondence between APN information and PDN GW address information. Details of the HSS correspondence table will be described later.

  The communication IF 306 converts the control signal output from the processor 305 into a format that can be output to the outside, and transmits the converted control signal and the like to the MME 400. The communication IF 306 receives a signal in a predetermined format transmitted from the MME 400, extracts a control signal from the received signal, and outputs the extracted control signal to the processor 305.

<1.4 MME configuration example>
FIG. 4A also illustrates a configuration example of the MME 400. The MME 400 includes a display unit 401, an input unit 402, a RAM 403, an HDD 404, a processor 405, and a communication IF 406.

  The functions of the display unit 401 and the input unit 402 are the same as those of the display unit 301 and the input unit 302 of the HSS 300, for example.

  The processor 405 is a processing unit or a control unit that controls the MME 400, for example. The processor 405 reads out the program stored in the RAM 403 and executes the read program to execute various processes and functions. For example, the following processing is performed. That is, the processor 405 receives the C-PLANE connection request transmitted from the terminal 100 from the base station 200, generates a connection authentication request for the received request, and transmits the generated connection authentication request to the HSS 300. Further, the processor 405 receives the PDN GW address information transmitted from the HSS 300, and transmits the received address information to the SGW 500. Details of processing or functions performed by the processor 405 will be described in an operation example.

  The communication IF 406 converts the data and control signals output from the processor 405 into a format that can be output to the outside, and transmits the converted data and control signals to the base station 200, the HSS 300, and the SGW 500. The communication IF 406 receives a signal in a predetermined format output from the base station 200, HSS 300, and SGW 500, extracts data and control signals from the received signal, and outputs the extracted data and the like to the processor 405.

<1.5 SGW configuration example>
FIG. 4A also illustrates a configuration example of the SGW 500. The SGW 500 includes a display unit 501, an input unit 502, a RAM 503, an HDD 504, a processor 505, and a communication IF 506.

  The functions of the display unit 501 and the input unit 502 are the same as, for example, the display unit 301 and the input unit 302 of the HSS 300, respectively.

  The processor 505 is, for example, a processing unit or a control unit that controls the SGW 500. The processor 505 reads out a program stored in the RAM 503, and executes various functions by executing the read program. For example, the processor 505 transmits the access request transmitted from the terminal 100 to the PDN GW (A) 600-A or the PDN GW (B) 600-B according to the PDN GW address information received from the MME 400. Details of processing or functions performed by the processor 505 will be described in an operation example.

  The HDD 504 stores an SGW correspondence table and the like. The SGW correspondence table is, for example, a table storing a correspondence relationship between line numbers and PDN GW address information. Details of the SGW correspondence table will be described later.

  The communication IF 506 converts the data and control signals output from the processor 505 into a format that can be output to the outside, and converts the converted data and control signals to the base station 200, the MME 400, the PDN GW (A) 600-A, (B) Transmit to 600-B. Further, the communication IF 506 receives a signal in a predetermined format output from the base station 200, the MME 400, the PDN GW (A) 600-A, and (B) 600-B, and extracts data, a control signal, and the like from the received signal. The extracted data or the like is output to the processor 505.

<1.6 PDN GW configuration example>
FIG. 4A illustrates a configuration example of the PDN GW (A) 600-A and (B) 600-B. The PDN GW (A) 600-A and the PDN GW (B) 600-B may be collectively referred to as a PDN GW 600.

  The PDN GW 600 includes a display unit 601, an input unit 602, a RAM 603, an HDD 604, a processor 605, and a communication IF 606.

  For example, the display unit 601 and the input unit 602 are the same as the display unit 301 and the input unit 302 of the HSS 300, respectively.

  The processor 605 is a processing unit or a control unit that controls the PDN GW 600, for example. The processor 605 reads out the program stored in the RAM 603 and executes various processes and functions by executing the read program. For example, the processor 605 transfers the access request transmitted from the terminal 100 to the destination network (A) 700-A, (B) 700-B (or the APN information notification server 800). Details of processing or functions performed by the processor 605 will be described in an operation example.

  The communication IF 606 converts the data output from the processor 605 into a format that can be output to the outside, and transmits the converted data to the SGW 500, the network (A) 700-A, and the APN information notification server 800. The communication IF 606 receives a signal in a predetermined format transmitted from the network (A) 700-A or the APN information notification server 800, extracts data from the received signal, and outputs the extracted data to the processor 605. To do.

<1.7 APN Information Notification Server>
FIG. 4B is a diagram illustrating a configuration example of the APN information notification server 800. The APN information notification server 800 includes a display unit 801, an input unit 802, a RAM 803, an HDD 804, a processor 805, and a communication IF 806.

  For example, the display unit 801 and the input unit 802 are the same as the display unit 301 and the input unit 302 of the HSS 300, respectively.

  The processor 805 is a processing unit or a control unit that controls the APN information notification server 800. The processor 805 reads out the program stored in the RAM 803 and executes the read program to execute various processes and functions. For example, the processor 805 performs the following processing. That is, when the processor 805 receives the access request transmitted from the terminal 100, the processor 805 transmits HTML (Hyper Text Markup Language) data that prompts downloading of the APN setting application to the terminal 100. Further, when receiving the download request for the application transmitted from the terminal 100, the processor 805 transmits the APN setting application installation file data including valid APN information to the terminal 100. Such HTML data and installation file data are stored in the HDD 804, for example. Details of processing or functions performed by the processor 805 will be described in an operation example.

  The communication IF 806 converts the data output from the processor 805 into a format that can be output to the outside, and transmits the converted data to the PDN GW (B) 600-B. The communication IF 806 receives a signal in a predetermined format transmitted from the PDN GW (B) 600 -B, extracts data from the received signal, and outputs the extracted data to the processor 805.

<Operation example>
Next, an operation example will be described. Operation examples will be described in the following order.
<2.1 Overall sequence example>
<2.2 Example of operation of each device>
<2.2.1 Example of terminal operation>
<2.2.2 HSS operation example>
<2.2.3 SGW operation example>
<Example of operation of 2.2.4 APN information notification server>

<2.1 Overall sequence example>
5 to 7 show an example of the entire sequence in the communication system 10. 8A shows an example of an HSS correspondence table, and FIG. 8B shows an example of an SGW correspondence table.

  5 to 7, the base station 200 is omitted. A base station 200 exists between the terminal 100 and the MME 400, wireless signals are exchanged in a wireless section between the terminal 100 and the base station 200, and control signals and the like are exchanged in a wired section between the base station 200 and the MME 400. Description of such operations is omitted. In addition, there is a base station 200 between the terminal 100 and the SGW 500. In this case as well, there is processing such as conversion from a radio signal to data or the like, but this will be omitted.

  In the following operation examples, for “request signal” (or request message), “response signal” (or response message), “address information” (or address), etc., “request”, “response”, “address” May be referred to as "."

  When starting the connection to the communication system 10, the terminal 100 transmits a C-PLANE connection request to the MME 400 via the base station 200 (S10). In response to the C-PLANE connection request, the terminal 100 requests connection to the core network or the network (A) 700-A. The C-PLANE connection request may include the line number and APN information of the terminal 100, and may not include the APN information. Depending on the APN setting made by the user in the terminal 100, the APN information may or may not be included in the C-PLANE connection request.

  When receiving the C-PLANE connection request, the MME 400 transmits a connection authentication request to the HSS 300 (S11). For example, the MME 400 extracts the line number and APN information of the terminal 100 included in the C-PLANE connection request, generates a connection authentication request including these pieces of information, and transmits the generated connection authentication request to the HSS 300. When the APN information is not included in the C-PLANE connection request, the APN information is not included in the connection authentication request.

  The C-PLANE connection request and the connection authentication request may be referred to as “connection requests”, for example.

  When receiving the connection authentication request, the HSS 300 determines whether or not the terminal 100 is a contracted terminal (S12). For example, the HSS 300 holds contract information of the terminal 100 (or contract information of a user who uses the terminal 100), and the line number included in the received connection authentication request matches the line number included in the contract information. If it does not match, it may be determined as “terminal without contract”.

  When the HSS 300 determines that the terminal 100 subject to the connection authentication request is not a contracted terminal (No in S12), the HSS 300 transmits a response indicating that it is not a contract target terminal to the MME 400 (S13).

  When receiving the response, the MME 400 decides to reject (or reject) the C-PLANE connection request (S10), and transmits a response indicating that to the terminal 100 (S15). When receiving the response, the terminal 100 ends the C-PLANE connection process (S16).

  On the other hand, when the HSS 300 determines that the terminal 100 is a contracted terminal (Yes in S12), the HSS 300 determines whether valid APN information is included in the connection authentication request (S20). The HSS 300 performs such determination based on the HSS correspondence table.

  FIG. 8A is a diagram illustrating an example of the HSS correspondence table 3041. The HSS correspondence table 3041 stores, for example, the correspondence between APN information and PDN GW address information. In the example of FIG. 8A, when the APN information is “Web # 1,” the PDN GW address information is “A”. This “A” represents the address information of the PDN GW (A) 600-A, and the APN information “Web # 1” corresponding to “A” is the network (A) 700- provided by the service provider. This indicates that the APN information is valid for A. Accordingly, the HSS 300 determines whether or not the APN information is valid based on whether or not it matches “Web # 1” stored in the HSS correspondence table 3041.

  That is, the HSS 300 determines that the APN information is valid when the APN information extracted from the connection authentication request matches “Web # 1” (Yes in S20 in FIG. 5). On the other hand, the HSS 300 is effective when the connection authentication request does not include APN information or includes invalid APN information (the APN information extracted from the request does not match “Web # 1”). It is determined that it is not APN information (No in S20).

  When the connection authentication request includes valid APN information (Yes in S20), the HSS 300 reads the PDN GW address corresponding to the APN information from the HSS correspondence table 3041 (S21). In the example of FIG. 8A, the HSS 300 reads the address information “A” of the PDN GW (A) 600-A.

  Next, the HSS 300 transmits the address information of the read PDN GW (A) 600-A to the MME 400 (S22).

  When the MME 400 receives the address information of the PDN GW (A) 600-A, the MME 400 transmits the received address information to the SGW 500 (S23).

  When the SGW 500 receives the address information of the PDN GW (A) 600-A, the SGW 500 stores the received address information of the PDN GW (A) 600-A in the SGW correspondence table 5041 (S25).

  FIG. 8B is a diagram illustrating an example of the SGW correspondence table 5041. The SGW correspondence table 5041 stores the line number of the terminal 100 (or SIM card) and the address information notified from the HSS 300. In the example of FIG. 8B, the terminal 100 with the line number “090-9999-9999” stores “A” (= address information of PDN GW (A) 600-A) as the address information notified from the HSS 300. Represents an example.

  Note that the line number of the terminal 100 may be transmitted together with the address information transmitted from the HSS 300.

  Returning to FIG. 5, the MME 400 decides to accept (or permit) the C-PLANE connection request (S10) after transmitting the address information of the PDN GW (A) 600-A to the SGW 500 (S26). Is sent to the terminal 100 (S27).

  Upon receiving the response, the terminal 100 completes the C-PLANE connection (S28) and transmits a U-PLANE connection request to the SGW 500 (S29). The U-PLANE connection request may be referred to as a “connection request”, for example.

  When the SGW 500 receives the U-PLANE connection request, the SGW 500 connects the U-PLANE of the terminal 100 to the PDN GW (A) 600-A (S30).

  For example, the U-PLANE connection request includes the line number of the terminal 100, and when the SGW 500 receives the request, the address corresponding to the line number is selected from the HSS correspondence table 3041 using the line number of the terminal 100 as a key. Read information. In the example of FIG. 8B, the SGW 500 reads the address information “A” of the PDN GW (A) 600-A corresponding to the line number “090-9999-9999”. Then, the SGW 500 sets a connection line (for example, a line bearer) with the PDN GW (A) 600-A. Thereby, the path | route from the terminal 100 (or SGW500) to PDN GW (A) 600-A is set.

  When the SGW 500 connects the U-PLANE of the terminal 100 to the PDN GW (A) 600-A, the SGW 500 transmits a response indicating the connection to the terminal 100 (S31).

  Upon receiving the response, the terminal 100 confirms that the U-PLANE connection has been made normally and completes the U-PLANE connection (S32). And the terminal 100 transmits the access request regarding HTTP access to the network (A) 700-A (S33). The terminal 100 can perform packet communication via the network (A) 700-A provided by the service provider.

  On the other hand, when valid APN information is not included in the connection authentication request (No in S20), the HSS 300 reads the address information of the PDN GW (B) 600-B (S40).

  As shown in FIG. 8 (A), the PSS GW address information “B” is stored in the HSS correspondence table 3041 when valid APN information is not included in the connection request. This address information “B” represents the address of the PDN GW (B) 600-B. In such a case, the HSS 300 reads the PDN GW address information “B”.

  Returning to FIG. 6, the HSS 300 transmits the read address information of the PDN GW (B) 600-B to the MME 400 (S41).

  MME400 will transmit to SGW500, if the address information of PDN GW (B) 600-B is received (S42).

  The SGW 500 stores the received address information of the PDN GW (B) 600-B in the SGW correspondence table 5041 (S43).

  FIG. 8B shows an example of the SGW correspondence table 5041 after the address information of the PDN GW (B) 600-B is stored. In the example of FIG. 8B, the address information of the PDN GW (B) 600-B is stored for the line number “080-9999-9999” in which the APN of the network (C) is set by mistake. Represents. In addition, an example is shown in which address information of PDN GW (B) 600-B is stored for a line number “070-9999-9999” that does not include APN information in the connection request. The line number may be transmitted from the HSS 300 to the SGW 500 via the MMW 400 together with the address information of the PDN GW (B) 600-B.

  Returning to FIG. 6, when the MME 400 transmits the address information of the PDN GW (B) 600 -B to the SGW 500 (S 42), the MME 400 decides to accept the C-PLNAE connection request (S 10) (S 44). The response shown is transmitted to the terminal 100 (S45).

  Upon receiving the response, the terminal 100 completes the C-PLANE connection (S46) and transmits a U-PLANE connection request to the SGW 500 (S47).

  When the SGW 500 receives the U-PLANE connection request, the SGW 500 connects the U-PLANE of the terminal 100 to the PDN GW (B) 600-B (S48).

  For example, the following processing is performed. That is, the SGW 500 reads the PDN GW address “B” corresponding to the line number included in the U-PLANE connection request (S47) from the SGW correspondence table 5041. Then, the SGW 500 sets a line connection (for example, a line bearer) with the PDN GW (B) 600-B. Thereby, the path | route from the terminal 100 (or SGW500) to PDN GW (B) 600-B is set.

  In the PDN GW (B) 600-B, it is assumed that the U-PLANE path to the APN information notification server 800 has been set. As an example of route setting, for example, rewriting of a destination address is available. For example, the PDN GW (B) 600-B rewrites the destination address information from the PDN GW (B) 600-B to the APN information notification server 800 in response to a request addressed to the PDN GW (B) 600-B. You may perform processes, such as. Accordingly, the U-PLANE path connection from the SGW 500 to the PDN GW (B) 600-B causes the terminal 100 (or SGW 500) to the PDN GW (B) 600-B and the PDN GW (B) 600-B to APN information. A U-PLANE route to the notification server 800 is set.

  Therefore, the address information of the PDN GW (B) 600-B transmitted by the HSS 300 is, for example, connection information to the APN information notification server 800.

  Next, the SGW 500 transmits a response indicating the connection to the terminal 100 (S50).

  Upon receiving the response, the terminal 100 completes the U-PLANE connection (S51) and performs HTTP access using the browser (S52). For example, the terminal 100 detects the operation of the touch sensor 108 by the user and accesses the web page.

  Next, the terminal 100 transmits an access request to the APN information notification server 800 via the PDN GW (B) 600-B (S53).

  When the access request is received, the APN information notification server 800 reads out HTML data for prompting the download of the file data (or program data) of the APN setting application from the HDD 804 (S54). The APN information notification server 800 transmits the HTML data to the terminal 100 (S55).

  Upon receiving the HTML data, the terminal 100 displays a screen for prompting the download of the file data of the APN setting application on the display unit 109 using a browser (S56).

  Next, when the user performs an operation for downloading the file data, the terminal 100 detects the operation and transmits a download request for the file data to the APN information notification server 800 (S58).

  Upon receiving the download request, the APN information notification server 800 reads the APN setting application installation file data from the HDD 804 (S60), and transmits the installation file data to the terminal 100 (S61). The installation file data includes, for example, APN information “Web # 1” of PDN GW (A) 600-A as valid PAN information.

  Next, the terminal 100 receives the installation file data (S62), stores (or installs) the installation file data in the RAM 107 (S63), and executes the APN setting application (S64). The terminal 100 reads the valid APN information “Web # 1” of the PDN GW (A) 600 -A from the installation file data by executing the APN setting application, and stores the APN information in the RAM 107. Thereby, for example, valid APN information is set (S65).

  Thereafter, the terminal 100 makes a C-PLANE connection request (S10) using the APN information “Web # 1”, so that the connection request is accepted in the HSS 300 because the APN information is valid (Yes in S20). (S26, S27). After that, according to the flow shown in FIG. 5, the terminal 100 can perform packet communication via the network (A) 700-A.

<2.2 Example of operation of each device>
Next, an operation example in each device of the terminal 100, the HSS 300, the SGW 500, and the APN information notification server 800 will be described. In the description of the operation example in each apparatus, there is a description that overlaps with <2.1 Overall sequence example>, and thus may be briefly described.

<2.2.1 Example of terminal operation>
FIG. 9 is a flowchart showing an operation example of the terminal 100. The flowchart illustrated in FIG. 9 is performed by the processor 103 of the terminal 100, for example.

  When starting the process (S100), the terminal 100 determines whether or not the correct APN setting has been made (S101). Here, the case where the correct APN setting is made is, for example, the case where the correct APN is set. The case where the correct APN setting is not made is, for example, the case where the APN is not set or the correct APN is not set. Such a determination may be made, for example, based on whether the processor 103 stores APN information in the RAM 107 or whether flag information indicating that APN setting has been performed is stored.

  When the correct APN setting is made (Yes in S101), the terminal 100 generates a C-PLANE connection request and transmits the generated C-PLANE connection request to the MME 400 (S102).

  Next, the terminal 100 determines whether or not the C-PLANE connection request has been accepted (S103). For example, even if the terminal 100 has received a response indicating that the C-PLANE connection request has been accepted (S27 in FIG. 5) or received a response indicating that it has been rejected (S15 in FIG. 5) Good.

  When the terminal 100 determines that the C-PLANE connection request is not accepted (S103), the terminal 100 confirms the failure (NG) of the C-PLANE connection request (S104), displays out-of-service, and ends the series of processes (S105). , S106). The out-of-service display is an example, and the terminal 100 may end the series of processes without displaying the out-of-service display. For example, when the terminal 100 is not a terminal contracted by a service provider, a terminal whose contract period has passed, or a terminal whose service has been stopped due to non-payment of charges, a C-PLANE connection request is not accepted (For example, No to S15 in S12 of FIG. 5).

  On the other hand, when the C-PLANE connection request is accepted (YES in S103), the terminal 100 completes the C-PLANE connection (S107) and transmits the U-PLANE connection request to the SGW 500 (S108).

  Next, when the terminal 100 receives a response (S31 in FIG. 5) indicating the completion of connection to the network (A) 700-A in response to the U-PLANE connection request, the terminal 100 completes the U-PLANE connection (S110). . Then, the terminal 100 is in a state where data communication (or packet communication) is possible (S111), and the series of processing ends (S112).

  On the other hand, when the correct APN setting is not made (No in S101), the terminal 100 transmits a C-PLANE connection request to the MME 400 (S115), and determines whether or not the C-PLANE connection request has been accepted. (S116).

  When the C-PLANE connection request is not accepted (No in S116), the terminal 100 performs the processes after S104. Also in this case, the C-PLANE connection request may not be accepted in the case of a terminal that has not contracted with the service provider or a terminal whose contract period has passed.

  When the C-PLANE connection request is accepted (Yes in S116), the terminal 100 completes the C-PLANE connection (S117 in FIG. 10) and transmits the U-PLANE connection request (S118).

  Next, when receiving a response (S45 in FIG. 6) indicating acceptance to the U-PLANE connection request, the terminal 100 completes the U-PLANE connection (S120) and becomes ready for data communication (S121). .

  Next, the terminal 100 transmits an access request for performing HTTP access using a browser (S122).

  Next, the terminal 100 determines whether a SIM information request has been received (S123). This SIM information request will be described in the third embodiment. In the second embodiment, the terminal 100 does not receive the SIM information request (No in S123) and proceeds to the process of S125.

  In step S125, the terminal 100 receives HTML data for prompting the download of the APN setting application, and displays a display screen for prompting the download of the APN setting application on the display unit 109 based on the data (S125).

  Next, the terminal 100 determines whether or not an APN setting application download operation has been performed on the display screen (S126). For example, the touch sensor 108 may detect an operation for downloading an APN setting application on the display screen, notify the processor 103 of the operation, and determine whether or not the processor 103 has received this notification.

  When determining that the download operation of the APN setting application is not performed (No in S126), the terminal 100 waits until the download operation is performed.

  On the other hand, when determining that the download operation of the APN setting application has been performed (Yes in S126), the terminal 100 transmits a download request for the APN setting application, and downloads the file data for installing the APN setting application (S127).

  Next, the terminal 100 stores the APN setting application installation file data in the RAM 107 and installs the APN setting application (S128).

  Next, the terminal 100 reads the APN setting application program included in the APN setting application installation file data and executes the program (S129).

  The terminal 100 sets the APN information of the PDN GW (A) 600-A by executing the program (S131). For example, by executing the program, the terminal 100 reads and reads APN information (for example, APN information “Web # 1” of the PDN GW (A) 600-A) included in the downloaded installation file. The issued APN information is stored in the RAM 107.

  And the terminal 100 complete | finishes a series of processes (S132).

<2.2.2 HSS operation example>
FIG. 11 is a flowchart illustrating an operation example of the HSS 300. The flowchart shown in FIG. 11 is performed by the processor 305 of the HSS 300, for example.

  When the process starts (S140), the HSS 300 receives a C-PLANE connection request (or connection authentication request) and APN information from the terminal 100 (S141). The APN information may be included in the C-PLANE connection request, or may be transmitted together with the C-PLANE connection information.

  Next, the HSS 300 determines whether there is valid APN information (S142). For example, the processor 305 determines as follows. That is, the processor 305 determines that there is valid APN information if the APN information (for example, “Web # 1”) of the updated PDN GW (A) 600-A is included. On the other hand, when the connection request includes no APN information or invalid APN information, the processor 305 determines that there is no valid APN information.

  When there is valid APN information (Yes in S142), the HSS 300 sends the address information (eg, “A”) of the PDN GW (A) 600-A corresponding to the APN information (eg, “Web # 1”) to the SGW 500. Notification is made (S143). And HSS300 complete | finishes a series of processes.

  On the other hand, when there is no valid APN information (No in S142), the HSS 300 notifies the SGW 500 of the address information (eg, “B”) of the PDN GW (B) 600-B (S145). And HSS300 complete | finishes a series of processes (S144).

<2.2.3 SGW operation example>
12 and 13 are diagrams illustrating an operation example of the SGW 500. The flowcharts shown in FIGS. 12 and 13 are performed by the processor 505 of the SGW 500, for example. The flowchart shown in FIG. 12 represents an operation example in which the PDN GW address information is stored in the SGW correspondence table 5041. In the flowchart shown in FIG. 13, after the PDN GW address information is stored in the SGW correspondence table 5041, the PDN GW (A) 600 -A and (B) 600 -B are sent based on the U-PLANE connection request from the terminal 100. An operation example for setting the path of is shown.

  As shown in FIG. 12, when the processing starts (S150), the SGW 500 receives the line number of the terminal 100 and the PDN GW address information from the HSS 300 via the MME 400.

  In this case, there are the following two cases as PDN GW address information.

  That is, when valid APN information is included in the C-PLANE connection request transmitted from the terminal 100, in the case of the PDN GW address information “A” received from the HSS 300 (S22 and S23 in FIG. 5, S143 in FIG. 11). ).

  The other is the case where valid APN information is not included in the C-PLANE connection request transmitted from the terminal 100, or the case of the PDN GW address information “B” received from the HSS 300 (S41, S42 in FIG. 11 S145).

  Returning to FIG. 12, next, the SGW 500 stores the received line number and PDN GW address information in the SGW correspondence table 5041 (S152). For example, FIG. 8B shows an example of the SGW correspondence table 5041 after storing such information.

  Returning to FIG. 12, next, the SGW 500 ends a series of processing (S153).

  After storing the line number and PDN GW address information in the SGW correspondence table 5041, the SGW 500 starts processing (S160 in FIG. 13) and receives the U-PLANE connection request transmitted from the terminal 100 via the base station 200. (S161).

  Next, the SGW 500 refers to the SGW correspondence table 5041 (S162), and determines whether or not the line number of the terminal 100 making the connection request is stored in the SGW correspondence table 5041 (S163).

  When the line number of the terminal 100 is not stored in the SGW correspondence table 5041 (No in S163), the SGW 500 proceeds to the process of S162 and repeats the above-described process.

  On the other hand, when the line number of the terminal 100 is stored in the SGW correspondence table 5041 (Yes in S163), the SGW 500 determines whether or not the PDN GW address information is stored in the SGW correspondence table 5041 (S164).

  The SGW 500 stores the line number of the terminal 100, but when the PDN GW address information corresponding to the line number is not stored in the SGW correspondence table 5041 (No in S164), the U-PLANE transmitted from the terminal 100 The connection request is rejected (S168). For example, the SGW 500 may be rejected due to elapse of a contract period or non-payment of fees. The SGW 500 generates a response indicating that the U-PLANE connection request is rejected, and transmits the response to the terminal 100 that has transmitted the U-PLANE connection request.

  On the other hand, when the PDN GW address information corresponding to the line number is stored in the SGW correspondence table 5041 (Yes in S164), the SGW 500 accepts the U-PLANE connection request transmitted from the terminal 100 and indicates that fact. A response is transmitted to the terminal 100 (S165).

  Next, the SGW 500 connects the U-PLANE of the terminal 100 to the DPN GW (PDN GW (A) 600-A or PDN GW (B) 600-B) having the PDN GW address information specified by the HSS 300 (S166). ).

  Then, the SGW 500 ends the series of processes (S167).

<Example of operation of 2.2.4 APN information notification server>
FIG. 14 is a flowchart showing an operation example of the APN information notification server 800. In the flowchart shown in FIG. 14, when processing is started (S170), an access request related to HTTP access is received from the terminal 100 (S171). This access request corresponds to, for example, S53 in FIG.

  Next, in response to the access request, the APN information notification server 800 transmits, to the terminal 100, HTML data that displays a display screen that prompts the user to download the APN setting application (S172).

  Next, the APN information notification server 800 receives the download request for requesting the download of the APN setting application transmitted from the terminal 100 (S173).

  Next, in response to the download request, the APN information notification server 800 transmits file data for installing an APN setting application (S174). For example, the processor 805 reads the installation file data stored in the HDD 804 and transmits it to the terminal 100.

  Then, the APN information notification server 800 ends the series of processes (S175).

  Hereinafter, an effect in the second embodiment will be described. For example, a user who uses the terminal 100 may not be able to set APN information or may set incorrect APN information. In this case, the HSS 300 operates so as not to notify the SGW 500 of the address of the PDN GW to which the terminal 100 should be connected. As a result, the U-PLANE connection request of the terminal 100 is rejected by the SGW 500. In this case, the terminal 100 cannot perform packet notification via the network (A) 700-A.

  However, in the second embodiment, the HSS 300 transmits valid APN information to the terminal 100 when APN information is not included in the connection request or when invalid APN information is included in the connection request. I try to control it. As a control method, for example, the HSS 300 transmits the address information of the PDN GW (B) 600-B to the SGW 500 (S41 in FIG. 6).

  As a result, a connection path from the terminal 100 to the PDN GW (B) 600-B is set in the SGW 500, and the APN information notification server 800 uses this path to enable effective APN information (for example, “Web # 1”) to the terminal 100. Send.

  The HSS 300 transmits the address information of the PDN GW (B) 600-B to the SGW 500 via the MME 400, so that, for example, the connection path from the terminal 100 to the APN information notification server 800 is set in the SGW 500. The HSS 300 takes the lead in setting the connection path from the terminal 100 to the APN information notification server 800.

  Therefore, the terminal 100 can acquire valid APN information from the APN information notification server 800 even when the APN information is not set or the APN information is set by mistake. Therefore, the terminal 100 can access the network (A) 700-A provided by the service provider using the valid APN information, and perform packet communication via the network (A) 700-A.

  Another example in the second embodiment will be described. In the example described above, the example in which the APN information notification server 800 is arranged in the network (B) 700-B has been described. For example, instead of PDN GW (B) 600-B, an APN information notification server 800 may be arranged. In this case, the APN information notification server 800 is directly connected to the SGW 500, and the HSS 300 replaces the address information of the PDN GW (B) 600-B (S40 to S41 in FIG. 5 and S145 in FIG. 11). May be sent to the SGW 500. When the SGW 500 receives the U-PLANE connection request, the SGW 500 sets a connection path from the SGW 500 (or the terminal 100) to the APN information notification server 800, and the APN information notification server 800 can transmit valid APN information to the terminal 100. It becomes.

[Third Embodiment]
Next, a third embodiment will be described. In the second embodiment, for example, one example of the network (A) 700-A has been described as the packet communication network provided by the service provider. In the third embodiment, an example in which there are a plurality of packet communication networks provided by a service provider will be described.

  FIG. 15 is a diagram illustrating a configuration example of a communication system (or connection control system) 10 according to the third embodiment. The communication system 10 may further be referred to as a PDN GW (C) 600-C, a network (C) 700-C, and a 3GPP AAA (3rd Generation Partnership Project Authentication Authorization Accounting) server device (hereinafter, “AAA server”). ) 900.

  The service provider that provides the network (A) 700-A is different from the service provider that provides the network (C) 700-C. The former is “service provider A” and the latter is “service provider”. It may be referred to as “person B”.

  The PDN GW (C) 600-C is a gateway device that connects a core network and a network (C) 700-C that is an external network (PDN). The PDN GW (C) 600-C is an access control device that connects the core network to the network (A) 700-A or the network (C) 700.

  The AAA server 900 performs, for example, authentication, authorization, and accounting for network access of a user who uses the terminal 100. The AAA server 900 holds contract information regarding the user, for example. The AAA server 900 is also an authentication device, for example.

  FIG. 16 is a diagram illustrating a configuration example of the AAA server 900. The AAA server 900 includes a display unit 901, an input unit 902, a RAM 903, an HDD 904, a processor 905, and a communication IF 906.

  The functions of the display unit 901 and the input unit 902 are the same as, for example, the display unit 301 and the input unit 302 of the HSS 300, respectively.

  The processor 905 is, for example, a processing unit or a control unit that controls the AAA server 900. The processor 905 reads out the program stored in the RAM 903 and executes various processes and functions by executing the read program. For example, the processor 905 receives the contract information acquisition request transmitted from the APN information notification server 800, reads the corresponding contract information from the HDD 904, and transmits the contract information to the APN information notification server 800. Details of processing or functions performed by the processor 905 will be described in an operation example.

  The communication IF 906 converts data and control signals output from the processor 905 into a format that can be output to the outside, and transmits the converted data and control signals to the HSS 300 and the PDN GW (B) 600-B. The communication IF 906 receives a signal in a predetermined format transmitted from the HSS 300 or the PDN GW (B) 600-B, extracts data, a control signal, and the like from the received signal, and outputs the extracted data to the processor 905. To do.

  17 to 19 show examples of the entire sequence in the third embodiment. 17 to 19, the same reference numerals are assigned to the same processing portions as those in the second embodiment. The processing and functions of the AAA server 900 are performed by the processor 905, for example. The processing and functions of the APN information notification server 800 are similarly performed by the processor 805, for example.

  In the third embodiment, the PDN GW address information (S180 to S181 in FIG. 17) transmitted by the HSS 300 when valid APN information is included in the connection request is the PDN GW (A) 600-A or PDN. This is address information of GW (C) 600-C.

  FIG. 20A is a diagram illustrating an example of the HSS correspondence table 3041. When the APN information is “Web # 1,” the HSS 300 addresses the address information “A” of the PDN GW (A) 600-A, and when the APN information is “Web # 2,” the address of the PDN GW (C) 600-C. Information “C” is transmitted. When the HSS 300 receives the invalid APN information, the HSS 300 transmits the address information “B” of the PDN GW (B) 600-B, as in the second embodiment.

  Returning to FIG. 17, when the SGW 500 receives PDN GW address information (for example, “A” or “C”) (S181), the received PDN GW address information is stored in the SGW correspondence table 5041 (S182).

  FIG. 20B is a diagram illustrating an example of the SGW correspondence table 5041 according to the third embodiment. In this example, “A” is stored as PDN GW address information for the line number “090-9999-9999”, and “C” is stored as PDN GW address information for “080-9999-9999”. . In the former example, valid APN information of the network (A) 700-A is included in the connection request, and in the latter example, valid APN information of the network (C) 700-C is included in the connection request. This is an example.

  The line number “070-9999-9999” is an example in which a valid APN is not included in the connection request and the address information “B” of the PDN GW (B) 600-B is stored. When the SGW 500 receives the PDN GW address information “B” from the HSS 300 via the MME 400 (S42 in FIG. 18), the SGW 500 stores the address information in the SGW correspondence table 5041 (S43).

  In the third embodiment, upon receiving an access request (S53 in FIG. 18) from the terminal 100, the APN information notification server 800 requests SIM information from the terminal 100 (S186).

  When the APN information notification server 800 receives the SIM information from the terminal 100 (S187), the APN information notification server 800 transmits the received SIM information to the AAA server 900 via the PDN GW (B) 600-B, and acquires the contract information from the AAA server 900. (S188 in FIG. 19).

  FIG. 20C shows an example of the AAA correspondence table 9041 stored in the HDD 904 of the AAA server 900. The information stored in the AAA correspondence table 9041 is stored as contract information when the user contracts for the SIM card or the terminal 100, for example. The AAA correspondence table 9041 stores the correspondence between SIM line numbers and contract network names. In the example of FIG. 20C, an example of the line number is shown as the SIM information. However, for example, an identification number unique to the SIM card may be used. “Network (C)” is stored as the contract network name for the line number “070-9999-9999” for which the APN information is not set correctly. This represents that the user of the line number “070-9999-9999” is contracted with a service provider that provides the network (C) 700-C. In this case, a user who uses the line number “070-9999-9999” by contract may contract with the service provider “A”, and the contract network name in that case is “network (A)”. . Upon receiving the SIM information (line number in the example of FIG. 20C), the AAA server 900 reads the contract network name corresponding to the SIM information from the AAA correspondence table 9041, and uses the read contract network name as the contract information. It transmits to the information notification server 800.

  Referring back to FIG. 19, the APN information notification server 800 selects an APN setting application appropriate for the contract based on the APN correspondence table (S190).

  FIG. 20D shows an example of the APN correspondence table 8041. The APN correspondence table 8041 is stored in the HDD 804, for example. The APN correspondence table 8041 stores the correspondence between the contract network name and the APN setting application name. In the example of FIG. 20D, “application A” is set as the APN setting application name corresponding to the contract network name “network (A)”, and “application C” is set as the APN setting application name corresponding to “network (C)”. Remembered. The APN information notification server 800 reads the corresponding APN setting application name based on the contract information acquired from the AAA server 900 (contract network name in the example of FIG. 20D). The read APN setting application name is “appropriate APN setting application”.

  Returning to FIG. 19, next, the APN information notification server 800 reads out HTML data for displaying a screen for prompting the download of the APN setting application from the HDD 804, and transmits it to the terminal 100 (S191, S55). In this case, the screen for prompting the download of “application (A)” may be different from the screen for prompting the download of “app (C)” according to the contract network name. In this case, the HTML data transmitted to the terminal 100 may be different HTML data corresponding to the contract network name.

  Upon receiving a download request from the terminal 100, the APN information notification server 800 reads installation file data of the selected APN setting application (“application A” or “application C” in the example of FIG. 20D), 100 is transmitted to S100 (S192, S61).

  By executing the APN setting program included in the installation file data, the terminal 100 reads APN information included in the file data and stores it in the RAM 107 (S193).

  Therefore, when the user makes a contract with the service provider “A” that provides the network (A) 700-A, the terminal 100 uses valid APN information (for example, first connection destination information) of the network (A) 700-A. Or “Web # 1”). When the user contracts with the service provider “B” that provides the network (C) 700-C, the terminal 100 uses the valid APN information (for example, the second connection destination) of the network (C) 700-C. Information or “Web # 2”). These APN information are valid APN information, and the terminal 100 transmits a connection request to the HSS 300 using this APN information, so that the PDN GW (A) 600-A, (C) 600 that is the connection destination in the HSS 300 Access to -C is guided.

  FIG. 10 is a flowchart illustrating an operation example of the terminal 100 according to the third embodiment, and FIG. 21 is a flowchart illustrating an operation example of the APN information notification server 800 according to the third embodiment.

  The terminal 100 transmits an access request by HTTP access to the SGW 500 using a browser (S122), and then the terminal 100 determines whether a SIM information request is requested (S123). This process is, for example, a process corresponding to S186 in FIG.

  When receiving the SIM information request, the terminal 100 determines that the SIM information is requested (Yes in S123), reads the SIM information stored in the RAM 107, and transmits the read SIM information (S124). For example, when the SIM card is inserted into the terminal 100, the SIM information stored in the memory of the SIM card is read out by the processor 103 and stored in the RAM 107. Subsequent processing is the same as in the second embodiment.

  As shown in FIG. 21, when the APN information notification server 800 starts processing (S200), it receives an access request by HTTP access transmitted from the terminal 100 (S171). This process corresponds to, for example, S53 in FIG.

  Next, the APN information notification server 800 requests SIM information from the terminal 100 (S201). As the SIM information, for example, a line number assigned to the SIM card may be requested.

  Next, the APN information notification server 800 receives SIM information from the terminal 100 (S202), and acquires contract information from the AAA server 900 based on the SIM information (S203).

  Next, the APN information notification server 800 selects an APN setting application corresponding to the contract information (S204), and transmits HTML data for prompting the download of the selected APN setting application to the terminal 100 (S205).

  Next, the APN information notification server 800 receives the download request transmitted from the terminal 100 (S206), and transmits the APN setting application installation file data corresponding to the download request to the terminal 100 (S207).

  Then, the APN information notification server 800 ends the series of processes (S208).

  Also in the third embodiment, as in the second embodiment, when the APN information is not included in the connection request or the APN information that is not valid is included in the connection request, the HSS 300 has the valid APN information. Is transmitted to the terminal 100. As a control method, for example, the HSS 300 transmits the address information of the PDN GW (B) 600-B to the SGW 500, so that a connection path from the SGW 500 (or from the terminal 100) to the APN information notification server 800 is set. (S41 in FIG. 17). As a result, the APN information notification server 800 can transmit valid APN information (for example, “Web # 1”) to the terminal 100.

  Therefore, the terminal 100 can acquire valid APN information even when APN information is not set or APN information is set by mistake. Therefore, the terminal 100 can perform packet communication via the network (A) 700-A provided by the service provider using the APN information.

  In this case, in the HSS 300, the address information of the PDN GW (B) 600-B is transmitted to the SGW 500, and the route is set in the SGW 500. Then, the APN information notification server 800 acquires the SIM information by using the route, and the corresponding network (A) 700-A or network (C) 700-C (or PDN GW (A) 600-A or PDN GW (C) 600 -C) APN information is transmitted to terminal 100. Accordingly, the HSS 300 controls the SGW 500 and the APN information notification server 800 so as to transmit the corresponding APN information to the terminal 100 based on the SIM information received from the terminal 100.

  Also in the third embodiment, similar to the second embodiment, the APN information notification server 800 may be used instead of the PDN GW (B) 600-B. In this case, when the HSS 300 does not receive valid APN information, the HSS 300 transmits the address information of the APN information notification server 800 to the SGW 500.

[Other embodiments]
In the second and third embodiments, the HSS 300 determines whether or not valid APN information is included, and when valid APN information is not included, the address information of the PDN GW (B) 600-B (No to S41 in S20 of FIG. 6, No to S41 in S20 of FIG. 17, etc.). For example, such determination and transmission of address information may be performed in the base station 200, the MME 400, the SGW 500, or the AAA server 900. For example, in the case of the base station 200, upon receiving notification from the HSS 300 that the terminal is a contracted terminal, the base station 200 makes a determination based on the connection request (S10) from the terminal 100, and the address information of the PDN GW (B) 600-B May be notified to the SGW 500. Thereafter, it can be carried out in the same manner as in the second and third embodiments.

  In the second and third embodiments, the example in which the APN information notification server 800 notifies the terminal 100 of valid APN information has been described (S61 in FIG. 7, S61 in FIG. 19, etc.). For example, the function of notifying such valid APN information may be provided in the base station 200, the HSS 300, the MME 400, the SGW 500, or the AAA server 900, for example. For example, when the base station 200 receives a download request (S58 in FIG. 7) from the terminal 100, the installation file data stored in the HDD 207 is read and transmitted to the terminal 100. In this case, when the SGW 500 receives the U-PLANE connection request from the terminal 100, the SGW 500 may be configured to connect the U-PLANE to the APN information notification server 800 that transmits valid APN information.

  Further, regarding the processors 103, 203, 305, 405, 505, 605, and 905 described in the second and third embodiments, a CPU (Central Processing Unit), a DSP (Digital Signal Processing), an FPGA (Field Programmable Gate). Array) or other controllers.

  The above is summarized as an appendix.

(Appendix 1)
The connection request transmitted from the terminal device is received, and the received network connection destination information that specifies the network connection destination is not included in the received connection request or the network connection destination information that is not valid is included. A connection control device comprising: a processor that controls to transmit the valid network connection destination information to the terminal device.

(Appendix 2)
The connection according to claim 1, wherein the processor sets a connection path from the terminal device to the information notification device based on connection information to the information notification device that transmits the valid network connection destination information. Control device.

(Appendix 3)
The processor transmits connection information to an information notification device that transmits the valid network connection destination information to a transfer control device that transfers an access request transmitted from the terminal device to the network. The connection control apparatus according to 1.

(Appendix 4)
The connection control device according to appendix 3, wherein the connection information is address information of a gateway device connected to the information notification device.

(Appendix 5)
The connection control device according to appendix 3, wherein the connection information is address information of the information notification device.

(Appendix 6)
The network is a communication carrier that owns a communication network and provides communication services using the communication network, or an MVNO (Mobile Virtual Network) that provides communication services by borrowing a communication network from the carrier. Operator) The connection control device according to appendix 1, which is a network provided by a business operator.

(Appendix 7)
The connection control device according to appendix 1, wherein the connection control device is a subscriber information management device that manages contract information of a subscriber who receives a service.

(Appendix 8)
The network includes first and second networks;
The processor includes: first network connection destination information representing the effective network connection destination information to the first network or the second network based on SIM (Subscriber Identity Module) information received from the terminal device The connection control device according to appendix 1, wherein the second network connection destination information representing the effective network connection destination information is transmitted to the terminal device.

(Appendix 9)
The processor transmits the SIM information to an authentication device holding first or second network name information accessible by the terminal device, and the first or second network name information corresponding to the SIM information is transmitted. Supplementary note 8 characterized in that control is performed so that the first or second connection destination information received from the authentication device and corresponding to the received first or second network name information is transmitted to the terminal device. The connection control device described.

(Appendix 10)
The first and second networks have a communication line network and use the communication line network to provide a communication service, or borrow a communication line network from the carrier company to provide a communication service. 9. The connection control device according to appendix 8, wherein the connection control device is a network provided for each MVNO (Mobile Virtual Network Operator) operator.

(Appendix 11)
The connection control apparatus according to appendix 1, wherein the network connection destination information is APN (Access Point Name) information.

(Appendix 12)
A terminal device;
In a connection control system comprising a connection control device,
The connection control device includes:
The connection request transmitted from the terminal device is received, and the received network connection destination information that specifies the network connection destination is not included in the received connection request or the network connection destination information that is not valid is included. A first processor for controlling to transmit the valid network connection destination information to the terminal device when
The terminal control device includes a second processor that receives the valid network connection destination information.

(Appendix 13)
13. The connection control system according to appendix 12, further comprising an information notification device including a second processor that transmits the effective network connection destination information to the terminal device under the control of the connection control device.

(Appendix 14)
A connection control program to be executed by a computer in the connection control device,
The connection request transmitted from the terminal device is received, and the received network connection destination information that specifies the network connection destination is not included in the received connection request or the network connection destination information that is not valid is included. A connection control program for causing a computer to execute a process of controlling to transmit the valid network connection destination information to the terminal device.

(Appendix 15)
A connection control method in a connection control device having a processor,
The network connection destination information received when the processor receives a connection request transmitted from a processor terminal device, and the received connection request does not include network connection destination information specifying a network connection destination, or is not valid When the connection control method is included, control is performed to transmit the valid network connection destination information to the terminal device.

10: Communication system 100: Terminal device 103: Processor 105: Memory 108: Touch sensor 109: Display unit 200: Base station device 203: Processor 206: RAM 207: HDD
300: HSS 303: RAM
304: HDD 305: Processor 400: MME 403: RAM
404: HDD 405: Processor 500: SGW 503: RAM
504: HDD 505: processor 600) (600-A to 600-C): PDN GW (PDN GW (A) to PDN GW (C))
603: RAM 604: HDD
605: Processor 800: APN information notification server device 803: RAM 804: HDD
805: Processor 900: 3GPP AAA server device 903: RAM 904: HDD
905: Processor 3041: HSS correspondence table 5041: SGW correspondence table 8041: APN correspondence table 9041: AAA correspondence table

Claims (9)

The connection request transmitted from the terminal device is received, and the received network connection destination information that specifies the network connection destination is not included in the received connection request or the network connection destination information that is not valid is included. A connection control device comprising: a processor that controls to transmit the valid network connection destination information to the terminal device.   The said processor sets the connection path | route from the said terminal device to the said information notification apparatus based on the connection information to the information notification apparatus which transmits the said effective network connection destination information. Connection control device.   The processor transmits connection information to an information notification device that transmits the valid network connection destination information to a transfer control device that transfers an access request transmitted from the terminal device to the network. Item 4. The connection control device according to Item 1.   4. The connection control device according to claim 3, wherein the connection information is address information of a gateway device connected to the information notification device.   The connection control device according to claim 3, wherein the connection information is address information of the information notification device. The network includes first and second networks;
The processor includes: first network connection destination information representing the effective network connection destination information to the first network or the second network based on SIM (Subscriber Identity Module) information received from the terminal device The connection control apparatus according to claim 1, wherein control is performed so that second network connection destination information representing the valid network connection destination information is transmitted to the terminal device. A terminal device;
In a connection control system comprising a connection control device,
The connection control device includes:
The connection request transmitted from the terminal device is received, and the received network connection destination information that specifies the network connection destination is not included in the received connection request or the network connection destination information that is not valid is included. A first processor for controlling to transmit the valid network connection destination information to the terminal device when
The terminal control device includes a second processor that receives the valid network connection destination information. A connection control program to be executed by a computer in the connection control device,
The connection request transmitted from the terminal device is received, and the received network connection destination information that specifies the network connection destination is not included in the received connection request or the network connection destination information that is not valid is included. A connection control program for causing a computer to execute a process of controlling to transmit the valid network connection destination information to the terminal device. A connection control method in a connection control device having a processor,
The network connection destination information received when the processor receives a connection request transmitted from a processor terminal device, and the received connection request does not include network connection destination information specifying a network connection destination, or is not valid When the connection control method is included, control is performed to transmit the valid network connection destination information to the terminal device.

Images