WO2014155503A1 - Dispositif, système, et programme de traitement d'informations - Google Patents

Dispositif, système, et programme de traitement d'informations Download PDF

Info

Publication number
WO2014155503A1
WO2014155503A1 PCT/JP2013/058675 JP2013058675W WO2014155503A1 WO 2014155503 A1 WO2014155503 A1 WO 2014155503A1 JP 2013058675 W JP2013058675 W JP 2013058675W WO 2014155503 A1 WO2014155503 A1 WO 2014155503A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile
session
mobile terminal
network
line network
Prior art date
Application number
PCT/JP2013/058675
Other languages
English (en)
Japanese (ja)
Inventor
黒瀬　義敏
Original Assignee
富士通株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社 filed Critical 富士通株式会社
Priority to PCT/JP2013/058675 priority Critical patent/WO2014155503A1/fr
Publication of WO2014155503A1 publication Critical patent/WO2014155503A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed

Definitions

  • This technology relates to a technology for controlling connection through a mobile network.
  • One document describes an example of a mobile terminal having means for accessing a mobile network and a WLAN (Wireless Local Area Network) network.
  • a mobile terminal when a mobile terminal enters the WLAN area, control is performed so that the connection is switched from the mobile network to the WLAN network.
  • a mobile terminal having a means for accessing a plurality of mobile line networks has an advantage that communication processing can be speeded up by selecting a mobile line network having a high communication speed. Further, when one mobile network is disconnected, there is an advantage that communication can be resumed by reconnecting to the other mobile network.
  • the purpose of this technology is, in one aspect, to prevent a communication failure via a mobile network.
  • An information processing apparatus includes: a determination unit that determines whether or not the first mobile line network is appropriate based on a connection status with each of a plurality of mobile terminals via the first mobile line network; A mobile unit connected via the first mobile line network with an instruction to switch to a connection via another mobile line network when it is determined that the use of the first mobile line network is inappropriate A notification unit that notifies at least one mobile terminal of the terminals.
  • FIG. 1 is a diagram illustrating a network configuration example of a connection control system.
  • FIG. 2 is a diagram illustrating an example of a mobile terminal database.
  • FIG. 3 is a diagram showing a PPP (Point-to-Point Protocol) connection procedure.
  • FIG. 4 is a diagram illustrating an example of the session management database.
  • FIG. 5 is a diagram illustrating an example of a session.
  • FIG. 6 is a diagram illustrating a module configuration example of the authentication server.
  • FIG. 7 is a diagram illustrating an example of the overall processing flow of the authentication server.
  • FIG. 8 is a diagram showing a process (A) flow for each mobile network.
  • FIG. 9 is a diagram illustrating an example of a region.
  • FIG. 10 is a diagram illustrating an example of a cutting rate calculation processing flow.
  • FIG. 11 is a diagram illustrating an example of a continuous session determination processing flow.
  • FIG. 12 is a diagram illustrating an example of a disconnected session determination processing flow.
  • FIG. 13 is a diagram illustrating a determination process (A) flow.
  • FIG. 14 is a diagram illustrating an example of a notification process (A) flow.
  • FIG. 15 is a diagram illustrating an example of a sequence of a mobile terminal.
  • FIG. 16 is a diagram illustrating a module configuration example of the authentication server according to the second embodiment.
  • FIG. 17 is a diagram illustrating an example of a priority setting process flow.
  • FIG. 18 is a diagram illustrating an example of a notification process (B) flow.
  • FIG. 19 is a diagram illustrating a module configuration example of the authentication server according to the third embodiment.
  • FIG. 20 is a diagram showing a process (B) flow for each mobile network.
  • FIG. 21 is a diagram illustrating an example of an average packet loss rate calculation processing flow.
  • FIG. 22 is a diagram illustrating a determination process (B) flow.
  • FIG. 23 is a diagram illustrating a module configuration example of the authentication server according to the fourth embodiment.
  • FIG. 24 is a diagram showing a process (C) flow for each mobile network.
  • FIG. 25 is a diagram illustrating an example of an average delay time calculation processing flow.
  • FIG. 26 is a diagram illustrating a determination processing (C) flow.
  • FIG. 27 is a diagram illustrating a module configuration example of the authentication server according to the fifth embodiment.
  • FIG. 28 is a diagram showing a process (D) flow for each mobile network.
  • FIG. 29 is a diagram illustrating an example of an average radio wave intensity calculation process flow.
  • FIG. 30 is a diagram illustrating a determination process (D) flow.
  • FIG. 31 is a functional block
  • FIG. 1 shows a network configuration example of the connection control system.
  • the integrated network 103 is connected to the first mobile network 105, the second mobile network 107, and the third mobile network 109. Between the integrated network 103 and the first mobile line network 105, between the integrated network 103 and the second mobile line network 107, and between the integrated network 103 and the third mobile line network 109, for example, a dedicated line or They are connected by VPN (Virtual Private Network).
  • the connection control system is operated by a virtual mobile service provider, for example.
  • the integrated network 103 is provided with an authentication server 101.
  • the mobile terminal 121 such as the portable mobile terminal 121a and the in-vehicle mobile terminal 121b sets each mobile line by setting a SIM card (Subscriber Identity Module Card) for the mobile line network.
  • SIM card Subscriber Identity Module Card
  • a PPP connection is established with the authentication server 101 via the network.
  • a mobile terminal 121 having a mechanism for setting a plurality of SIM cards is targeted.
  • the first mobile network 105 has a plurality of first base stations 111.
  • a mobile terminal 121 that has set up a SIM card for the first mobile network 105 is connected to the first base station 111 by radio communication, and via the first mobile network 105 and the integrated network 103, A PPP connection is established with the authentication server 101.
  • the second mobile network 107 has a plurality of second base stations 113.
  • the mobile terminal 121 that has set up a SIM card for the second mobile network 107 is connected to the second base station 113 by radio communication, and the second mobile network 107 and the integrated network 103 are used.
  • a PPP connection is established with the authentication server 101.
  • the third mobile network 109 has a plurality of third base stations 115.
  • a mobile terminal 121 that has set up a SIM card for the third mobile network 109 is connected to the third base station 115 by wireless communication, and is connected via the third mobile network 109 and the third base station 115.
  • the authentication server 101 is connected by PPP.
  • the authentication server 101 manages data related to the mobile terminal using the mobile terminal database.
  • FIG. 2 shows an example of the mobile terminal database.
  • the mobile terminal database has a record for each mobile terminal.
  • the record has fields for mobile terminal ID (Identifier), management data related to the first mobile network, management data related to the second mobile network, and management data related to the third mobile network.
  • the mobile terminal ID is information for identifying the mobile terminal 121.
  • the management data related to the first mobile line network includes the SIM card of the first mobile line network, the telephone number of the first mobile line network, the PPP login ID of the first mobile line network, and the PPP of the first mobile line network.
  • information indicating whether or not the SIM card of the first mobile line network is set is stored.
  • the telephone number field defined in the SIM card of the first mobile line network is stored in the telephone number field of the first mobile line network.
  • the login ID used in the PPP connection by the SIM card of the first mobile network is stored in the PPP login ID field of the first mobile network.
  • a password used for PPP connection by the SIM card of the first mobile network is stored.
  • the management data relating to the second mobile network includes the SIM card of the second mobile network, the telephone number of the second mobile network, the PPP login ID of the second mobile network, and the PPP of the second mobile network.
  • Information indicating whether or not a SIM card for the second mobile line network is set is stored in the SIM card field for the second mobile line network.
  • a telephone number determined for the SIM card of the second mobile line network is stored.
  • the login ID used in the PPP connection by the SIM card of the second mobile network is stored in the PPP login ID field of the second mobile network.
  • a password used for PPP connection by the SIM card of the second mobile network is stored.
  • the management data related to the third mobile network includes the SIM card of the third mobile network, the telephone number of the third mobile network, the PPP login ID of the third mobile network, and the PPP of the third mobile network.
  • the SIM card field of the third mobile line network information indicating whether or not the SIM card of the third mobile line network is set is stored.
  • the telephone number field of the third mobile line network a telephone number determined for the SIM card of the third mobile line network is stored.
  • PPP login ID field of the third mobile line network a login ID used for PPP connection by the SIM card of the third mobile line network is stored.
  • PPP password field of the third mobile network a password used for PPP connection by the SIM card of the third mobile network is stored.
  • the SIM card of the first mobile line network and the SIM card of the second mobile line network are set in the mobile terminal identified by the mobile terminal ID “M001”. However, the SIM card of the third mobile line network is not set.
  • the first record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the first mobile line network set in the mobile terminal identified by the mobile terminal ID “M001” is “ 090-001-0001 ".
  • the first record shown in FIG. 2 is a login ID used for PPP connection by the SIM card of the first mobile line network set in the mobile terminal identified by the mobile terminal ID “M001”.
  • the first record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the second mobile network set in the mobile terminal identified by the mobile terminal ID “M001” is “ 090-002-0001 ".
  • the first record shown in FIG. 2 has a login ID used for PPP connection by the SIM card of the second mobile network set in the mobile terminal identified by the mobile terminal ID “M001”.
  • the management data field relating to the third mobile line network is invalid. . Therefore, valid data is not shown.
  • the SIM card of the first mobile line network and the SIM card of the third mobile line network are set in the mobile terminal identified by the mobile terminal ID “M002”. However, the SIM card of the second mobile line network is not set.
  • the second record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the first mobile line network set in the mobile terminal identified by the mobile terminal ID “M002” is “ 090-001-0002 ".
  • the login ID used for the PPP connection by the SIM card of the first mobile network set in the mobile terminal identified by the mobile terminal ID “M002” is:
  • the password used for PPP connection by the SIM card of the first mobile network set in the mobile terminal identified by the mobile terminal ID “M002” is “asdf5678”. It shows that there is.
  • the second record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the third mobile network set in the mobile terminal identified by the mobile terminal ID “M002” is “ 090-003-0002 ".
  • the second record shown in FIG. 2 is a login ID used for PPP connection by the SIM card of the third mobile network set in the mobile terminal identified by the mobile terminal ID “M002”.
  • the password used for PPP connection by the SIM card of the third mobile network set in the mobile terminal identified by the mobile terminal ID “M002” is “lkjh6543”, indicating “IJKL0002”. It shows that there is.
  • the management data field relating to the second mobile network is invalid. . Therefore, valid data is not shown.
  • the SIM card of the first mobile line network is set in the mobile terminal identified by the mobile terminal ID “M003”. This shows that the SIM card and the SIM card of the third mobile network are not set.
  • the third record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the first mobile line network set in the mobile terminal identified by the mobile terminal ID “M003” is “ 090-001-0003 ".
  • the login ID used for the PPP connection by the SIM card of the first mobile network set in the mobile terminal identified by the mobile terminal ID “M003” is:
  • the password used for the PPP connection by the SIM card of the first mobile circuit network set in the mobile terminal identified by the mobile terminal ID “M003”, which is “ABCD0003”, is “zxcv4321”. Show.
  • the management data field relating to the second mobile line network is invalid. . Therefore, valid data is not shown.
  • the management data field regarding the third mobile network is invalid. . Therefore, valid data is not shown.
  • the fourth record shown in FIG. 2 indicates that the mobile terminal identified by the mobile terminal ID “M004” includes a SIM card for the first mobile line network, a SIM card for the second mobile line network, 3 shows that a SIM card for a mobile network is set.
  • the fourth record shown in FIG. 2 indicates that the telephone number set for the SIM card of the first mobile network set in the mobile terminal identified by the mobile terminal ID “M004” is “ 090-001-0004 ".
  • the fourth record shown in FIG. 2 is a login ID used for PPP connection by the SIM card of the first mobile network set in the mobile terminal identified by the mobile terminal ID “M004”.
  • the fourth record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the second mobile network set in the mobile terminal identified by the mobile terminal ID “M004” is “ 090-002-0004 ".
  • the fourth record shown in FIG. 2 is a login ID used for PPP connection by the SIM card of the second mobile line network set in the mobile terminal identified by the mobile terminal ID “M004”. It is “EFGH0004” and the password used for PPP connection by the SIM card of the second mobile network set in the mobile terminal identified by the mobile terminal ID “M004” is “bnmo 7890”. Show.
  • the fourth record shown in FIG. 2 indicates that the telephone number specified for the SIM card of the third mobile network set in the mobile terminal identified by the mobile terminal ID “M004” is “ 090-003-0004 ".
  • the fourth record shown in FIG. 2 is a login ID used for PPP connection by the SIM card of the third mobile network set in the mobile terminal identified by the mobile terminal ID “M004”. It is “IJKL0004” and the password used for PPP connection by the SIM card of the third mobile network set in the mobile terminal identified by the mobile terminal ID “M004” is “vcxz4321”. Show.
  • FIG. 3 shows the PPP connection procedure.
  • the process proceeds to the link establishment phase (S303).
  • the link establishment phase S303
  • predetermined packets are exchanged between the mobile terminal 121 and the authentication server 101, and a link is established.
  • authentication is performed by an authentication protocol such as PAP (Password Authentication Protocol) or CHAP (Challenge Handshake Authentication Protocol).
  • PAP Password Authentication Protocol
  • CHAP CHAP (Challenge Handshake Authentication Protocol).
  • the link stop (S313) is a state in which the communication system is not physically or electrically operating.
  • the authentication server 101 distinguishes the connection state related to the session by the transition of these phases.
  • the authentication server 101 manages data related to a session using a session management database.
  • FIG. 4 shows an example of the session management database.
  • the session management database has a record for each session.
  • the record has fields for session ID, mobile network type, PPP login ID, connection start time, state, connection end time, and current position.
  • Information for identifying a session is stored in the session ID field.
  • the mobile network type field stores the type of the mobile network that is the session communication medium.
  • the login ID used in the PPP connection is stored in the PPP login ID field.
  • the connection start time field stores the time when the connection related to the session is started.
  • the status field stores the status of the connection related to the session.
  • the connection end time field stores the time when the connection related to the session is ended.
  • the current position field stores information indicating the current position of the mobile terminal related to the session.
  • the current position is specified by position information measured by the mobile terminal 121 using a GPS (Global Positioning System) function and a location of the base station to which the mobile terminal 121 is connected.
  • the current position is updated as needed.
  • GPS Global Positioning System
  • the session specified by the session ID “S001” is logged in via the “first mobile network” with the PPP login ID “ABCD0101” and connected to “time T1”. Indicates that has started.
  • the first record shown in FIG. 4 indicates that the session specified by the session ID “S001” is “connected” and the current location of the mobile terminal is specified by “X1: Y1”. ing. Since “connected”, no value is set in the connection end time field.
  • the session specified by the session ID “S002” is logged in via the “second mobile network” with the PPP login ID “EFGH0101” and connected to “time T1”. Indicates that has started.
  • the second record shown in FIG. 4 indicates that the connection related to the session specified by the session ID “S002” is “disconnected” at “time T3”.
  • the current position of the mobile terminal is specified by “X2: Y2”.
  • the session specified by the session ID “S003” is logged in via the “third mobile network” with the PPP login ID “IJKL0101” and connected to “time T1”. Indicates that has started.
  • the third record shown in FIG. 4 indicates that the connection related to the session specified by the session ID “S003” was “normally terminated” at “time T3”.
  • the current position of the mobile terminal is specified by “X3: Y3”.
  • the session specified by the session ID “S004” is logged in via the “first mobile network” with the PPP login ID “ABCD0102” and connected to “time T2”. Indicates that has started.
  • the fourth record shown in FIG. 4 indicates that the session specified by the session ID “S004” is “connected” and the current location of the mobile terminal is specified by “X4: Y4”. ing. Since “connected”, no value is set in the connection end time field.
  • the session specified by the session ID “S005” is logged in via the “second mobile network” with the PPP login ID “EFGH0102” and connected to “time T2”. Indicates that has started.
  • the fifth record shown in FIG. 4 indicates that the connection related to the session specified by the session ID “S005” is “disconnected” at “time T3”.
  • the current position of the mobile terminal is specified by “X5: Y5”.
  • the session identified by the session ID “S006” is logged in via the “third mobile network” with the PPP login ID “IJKL0102” and connected to “time T2”. Indicates that has started.
  • the sixth record shown in FIG. 4 indicates that the connection related to the session specified by the session ID “S006” was “normally terminated” at “time T3”.
  • the current position of the mobile terminal is specified by “Y6: Y6”.
  • FIG. 5 shows a session managed by the session management database shown in FIG.
  • the session 501 corresponds to the session shown in the first record of the session management database shown in FIG.
  • the session 503 corresponds to the session shown in the second record of the session management database shown in FIG.
  • the session 505 corresponds to the session shown in the third record of the session management database shown in FIG.
  • the session 507 corresponds to the session shown in the fourth record of the session management database shown in FIG.
  • the session 509 corresponds to the session shown in the fifth record of the session management database shown in FIG.
  • the session 511 corresponds to the session shown in the sixth record of the session management database shown in FIG.
  • a session in which the connection state continues from the reference time to the current time is referred to as a continuous session.
  • session 501 is a continuous session.
  • a session that is connected at the reference time and disconnected by the current time is called a disconnected session.
  • session 503 is a disconnected session.
  • the disconnection rate is obtained by dividing the sum of the number of continuing sessions and the number of disconnected sessions by the number of disconnected sessions. In the process of calculating the cutting rate, the number of sessions 505 to 511 is not used.
  • FIG. 6 shows a module configuration example of the authentication server 101.
  • the authentication server 101 includes a communication control unit 601, a storage area 603, a specifying unit 613, a calculation unit (A) 615a, a determination unit (A) 617a, a notification unit (A) 619a, a transmission unit 621, A receiving unit 623.
  • a mobile terminal DB (Database) 605 In the storage area 603, a mobile terminal DB (Database) 605, a session management DB 607, an area table 609, and a cutting rate table 611 are provided.
  • the mobile terminal DB 605 and the area table 609 are set in advance.
  • the communication control unit 601 controls communication with the mobile terminal 121.
  • the communication control unit 601 controls PPP connection with the mobile terminal 121.
  • the communication control unit 601 updates the session management DB 607 as needed.
  • the storage area 603 is an area for storing data used by the authentication server 101.
  • the mobile terminal DB 605 is as described above with reference to FIG.
  • the session management DB 607 is as described above with reference to FIG.
  • the area table 609 defines a partial area covered by the first base station 111, the second base station 113, and the third base station 115.
  • the region table 609 includes information for specifying a region range for each region.
  • the cutting rate table 611 the cutting rate for each region is written.
  • the specifying unit 613 specifies a mobile network and a region to be processed in the processing in the authentication server 101.
  • the calculation unit (A) 615a calculates a cutting rate for each region.
  • the determination unit (A) 617a determines whether to notify a switching instruction based on the cutting rate.
  • the notification unit (A) 619a notifies the mobile terminal 121 of a switching instruction.
  • the transmission unit 621 transmits data (for example, a switching instruction) to the mobile terminal 121, for example.
  • the receiving unit 623 receives data from the mobile terminal 121, for example.
  • FIG. 7 shows an example of the overall processing flow of the authentication server 101.
  • the identifying unit 613 identifies one unprocessed mobile network (S701).
  • the identifying unit 613 sequentially identifies mobile network, for example.
  • the mobile line network specified by the specifying unit 613 is processed in units of mobile line networks. (S703).
  • FIG. 8 shows a process (A) flow for each mobile network.
  • the identifying unit 613 identifies one unprocessed area among the areas managed in the area table 609 (S801).
  • the authentication server 101 manages the ranges covered by the first base station 111, the second base station 113, and the third base station 115 according to the areas stored in the area table 609.
  • FIG. 9 shows examples of areas.
  • FIG. 9 shows examples of a wide area, a middle area, and a narrow area.
  • the range covered by the first base station 111, the second base station 113, and the third base station 115 is divided into a plurality of wide areas.
  • wide area A and wide area B are shown.
  • each wide area is divided into a plurality of middle areas.
  • the wide area A includes a middle area A and a middle area B.
  • the wide area B includes a middle area C and a middle area D.
  • each middle region is divided into a plurality of narrow regions.
  • the middle region A includes narrow regions A to D.
  • the middle region B includes narrow regions E to H.
  • the middle region C includes narrow regions I to L.
  • the middle region D includes narrow regions M to P.
  • a wide area corresponds to a country
  • a middle area corresponds to a prefecture
  • a narrow area corresponds to a municipality.
  • the level of the area is not limited to this example. You may make it set in arbitrary ranges.
  • the areas are hierarchically defined by the inclusion relation, but the inclusion relation between the areas may not be provided. Further, the regions may overlap each other.
  • one of the wide area, middle area, and narrow area shown in FIG. 9 is specified.
  • the specifying unit 613 sequentially specifies a wide area, then sequentially specifies a middle area, and further sequentially specifies a narrow area.
  • the area may be specified according to other rules.
  • the calculation unit (A) 615a performs a cutting rate calculation process for the specified region (S803).
  • FIG. 10 shows an example of a cutting rate calculation processing flow.
  • the calculation unit (A) 615a identifies one unprocessed session among the sessions managed by the session management DB 607 (S1001). For example, the calculation unit (A) 615a sequentially specifies the records managed by the session management DB 607.
  • the calculation unit (A) 615a determines whether or not the mobile network is used as a communication medium for the session (S1003). Specifically, the calculation unit (A) 615a determines whether or not the mobile network identified in S701 of FIG. 7 is set in the mobile network type field included in the session record. To do. When the mobile network specified in S701 of FIG. 7 is set in the mobile network type field included in the record of the session, the mobile network is used as the communication medium of the session. It is determined that On the other hand, when the mobile line network specified in S701 of FIG. 7 is not set in the mobile line network type field included in the record of the session, the mobile line network is used as the communication medium of the session. It is determined that it is not used.
  • the session is not involved in the disconnection rate calculation, and the process proceeds to S1019 without performing the processes after S1005.
  • the calculation unit (A) 615a determines whether the location of the mobile terminal related to the session is included in the area. Determination is made (S1005). The location information of the mobile terminal related to the session is acquired from the current location field included in the session record. Further, the range of the area is specified based on information included in the area table 609.
  • the calculation unit (A) 615a performs a continuous session determination process (S1007).
  • FIG. 11 shows an example of a continuous session determination process flow.
  • the calculation unit (A) 615a obtains a reference time (S1101).
  • the reference time is a time that goes back a predetermined period from the current time.
  • the predetermined period is a period that serves as a reference when determining that the period is continued.
  • the calculation unit (A) 615a specifies the reference time by subtracting a predetermined period from the current time.
  • the calculation unit (A) 615a determines whether or not the connection start time is before the reference time (S1103).
  • the connection start time is acquired from the connection start time field included in the record of the session.
  • the calculation unit (A) 615a determines that the connection session is not a continuous session (S1105).
  • the calculation unit (A) 615a determines whether or not the session is being connected (S1107). Specifically, when “connected” is set in the state field included in the record of the session, the calculation unit (A) 615a determines that the session is connected.
  • the calculation unit (A) 615a determines that the session is not a continuous session (S1105).
  • the calculation unit (A) 615a determines that the session is a continuous session (S1109).
  • calculation unit (A) 615a branches the process depending on the result of the continuous session determination (S1009).
  • the calculation unit (A) 615a increments the number of denominators (S1011).
  • the number of denominators is an internal parameter used in the cutting rate calculation process.
  • the calculation unit (A) 615a performs a disconnection session determination process (S1013).
  • FIG. 12 shows an example of a disconnection session determination process flow.
  • the calculation unit (A) 615a obtains a reference time (S1201).
  • the calculation unit (A) 615a specifies the reference time by subtracting a predetermined period from the current time, as in S1101.
  • the calculation unit (A) 615a may use the reference time specified in S1101 again.
  • the calculation unit (A) 615a determines whether or not the connection start time is earlier than the reference time, as in S1103 (S1203). Similar to S1103, the connection start time is acquired from the connection start time field included in the record of the session.
  • the calculation unit (A) 615a determines that the connection start time is not a disconnected session (S1205).
  • the calculation unit (A) 615a determines whether or not the session is disconnected (S1207). Specifically, the calculation unit (A) 615a determines that the session is disconnected when “disconnected” is set in the state field included in the record of the session.
  • the calculation unit (A) 615a determines that the session is not a disconnected session (S1205).
  • the calculation unit (A) 615a determines that the session is a disconnected session (S1209).
  • calculation unit (A) 615a finishes the disconnected session determination process, the calculation unit (A) 615a returns to S1015 in FIG.
  • calculation unit (A) 615a branches the process depending on the result of the disconnection session determination (S1015).
  • the calculation unit (A) 615a increments the number of denominators and the number of numerators (S1017).
  • the number of molecules is an internal parameter used in the cutting rate calculation process.
  • the session is not a disconnected session, it is a session that does not serve as a basis for calculating the disconnection rate, and the process proceeds to S1019.
  • the calculation unit (A) 615a determines whether or not there is an unprocessed session (S1019). If it is determined that there is an unprocessed session, the process returns to S1001.
  • the calculation unit (A) 615a calculates the cleavage rate by dividing the number of numerators by the number of denominators (S1021). When the cutting rate is calculated, the calculation unit (A) 615a finishes the cutting rate calculation process, and returns to the process of S805 illustrated in FIG.
  • the determination unit (A) 617a performs a determination process (A) (S805).
  • FIG. 13 shows a determination process (A) flow.
  • the determination unit (A) 617a determines whether the cutting rate exceeds a threshold value (S1301). If it is determined that the cutting rate exceeds the threshold value, the determination unit (A) 617a determines to “notify” the switching instruction (S1303). If it is determined that the cutting rate does not exceed the threshold value, the determination unit (A) 617a determines that the switching instruction is “not notified” (S1305).
  • the determination unit (A) 617a finishes the determination process (A) the process returns to the process of S807 illustrated in FIG.
  • the notification unit (A) 619a branches the process depending on whether it is determined as “notify” or “not notify” in the determination process (A) (S807).
  • the determination process (A) determines “not notify”
  • the notification unit (A) 619a proceeds to the process of S811 without performing the notification process (A).
  • the notification unit (A) 619a performs the notification process (A) (S809).
  • FIG. 14 shows an example of the notification process (A) flow.
  • a switching instruction is notified to the mobile terminals existing in the area.
  • the notification unit (A) 619a identifies one unprocessed session among the sessions managed by the session management DB 607 (S1401). For example, the notification unit (A) 619a sequentially specifies the records managed by the session management DB 607.
  • the notification unit (A) 619a determines whether or not the mobile network identified in S701 of FIG. 7 is used as the communication medium of the session identified in S1401 (S1403). Specifically, the notification unit (A) 619a determines whether or not the mobile network identified in S701 of FIG. 7 is set in the mobile network type field included in the session record. To do. When the mobile network specified in S701 of FIG. 7 is set in the mobile network type field included in the record of the session, the mobile network is used as the communication medium of the session. It is determined that On the other hand, when the mobile line network specified in S701 of FIG. 7 is not set in the mobile line network type field included in the record of the session, the mobile line network is used as the communication medium of the session. It is determined that it is not used.
  • the session is not a notification target, and the process proceeds to S1411 without performing the processes after S1405.
  • the notification unit (A) 619a identifies the position of the mobile terminal related to the session in S801 of FIG. It is determined whether it is included in the area (S1405).
  • the location information of the mobile terminal related to the session is acquired from the current location field included in the session record. Further, the range of the area is specified based on information included in the area table 609.
  • the session is not a notification target, and the process proceeds to S1411 without performing the processes after S1407.
  • the notification unit (A) 619a identifies the mobile terminal 121 related to the session (S1407). For example, the notification unit (A) 619a reads the mobile network type and the PPP login ID from the field included in the record related to the session of the session management DB 607. The notifying unit (A) 619a records in the mobile terminal DB 605 that the PPP login ID included in the data relating to the mobile network identified by the read mobile network type matches the read PPP login ID. Search for. The retrieved record is a record related to the mobile terminal.
  • the notification unit (A) 619a notifies a switching instruction to the identified mobile terminal 121 (S1409). At this time, the notification unit (A) 619a causes the transmission unit 621 to transmit a switching instruction.
  • the transmission unit 621 transmits a switching instruction to the mobile terminal 121 by means such as IP (Internet Protocol) data communication, e-mail or short message service.
  • IP Internet Protocol
  • the notification unit (A) 619a determines whether or not there is an unprocessed session (S1411). If it is determined that there is an unprocessed session, the process returns to S1401.
  • the notification unit (A) 619a finishes the notification process (A) and proceeds to the process of S811 shown in FIG.
  • the identifying unit 613 determines whether or not there is an unprocessed area (S811). If it is determined that there is an unprocessed area, the process returns to S801 to continue the process for other areas. If it is determined that there is no unprocessed area, the process (A) for each mobile network is terminated, and the process returns to S705 shown in FIG.
  • the identifying unit 613 determines whether there is an unprocessed mobile network (S705). If it is determined that there is an unprocessed mobile line network, the process returns to S701 to continue processing for another mobile line network. If it is determined that there is no unprocessed mobile network, the entire process is terminated.
  • the whole process may be repeated periodically. Alternatively, the entire process may be performed when an instruction for the process is received.
  • the specifying unit 613 may specify an area corresponding to the area or an area included in the area in S801.
  • FIG. 15 shows an exemplary sequence of the mobile terminal 121.
  • the mobile terminal 121 has a receiving unit 1511 and a switching unit 1513.
  • the reception unit 1511 waits for reception of a switching instruction from the authentication server 101 (S1501).
  • the receiving unit 1511 passes the switching instruction to the switching unit 1513.
  • the switching unit 1513 When the switching unit 1513 receives the switching instruction, the switching unit 1513 identifies a newly connected mobile network, that is, a switching destination mobile network (S1503). In the present embodiment, the switching unit 1513 identifies a mobile line network other than the mobile line network currently used. The switching unit 1513 switches the mobile network (S1505). For example, the switching unit 1513 ends the old session after establishing a new session with the authentication server 101 via the switching destination mobile network.
  • a switching destination mobile network S1503
  • the switching unit 1513 identifies a mobile line network other than the mobile line network currently used.
  • the switching unit 1513 switches the mobile network (S1505). For example, the switching unit 1513 ends the old session after establishing a new session with the authentication server 101 via the switching destination mobile network.
  • the connection is switched to the connection via another mobile network before a failure actually occurs, and the communication trouble is Can be prevented.
  • FIG. 16 shows a module configuration example of the authentication server 101 according to the second embodiment.
  • the storage area 603 according to the second embodiment includes a priority table 1601. Further, the authentication server 101 according to the second embodiment further includes a prioritization unit 1603.
  • the priority order table 1601 is a table showing the priority order of the mobile network.
  • the prioritizing unit 1603 sets priorities for each mobile line network.
  • the authentication server 101 has a notification unit (B) 619b instead of the above-described notification unit (A) 619a.
  • the priority order setting process by the prioritization unit 1603 will be described.
  • the priority order setting process is performed periodically, for example.
  • priority order setting processing may be performed when an instruction is received.
  • FIG. 17 shows an example of the priority setting process flow.
  • the prioritization unit 1603 calculates the achievement rate for each mobile network (S1701). For example, when the priority setting unit 1603 sets a target for the ratio of the number of sessions using each mobile network, the ratio of the number of sessions currently used to the number of sessions corresponding to the target ratio is set. Achievement rate. The achievement rate may be set based on another index.
  • the prioritization unit 1603 sets priorities for the mobile network group in descending order of achievement rate (S1703). Specifically, the prioritizing unit 1603 writes the priority order for each mobile network in the priority order table 1601.
  • the priority order is an example of priority.
  • a notification process (B) is performed instead of the notification process (A) by the notification unit (A) 619a.
  • FIG. 18 shows an example of the notification process (B) flow.
  • the notification unit (B) 619b identifies one unprocessed session (S1801), as in the process of S1401 illustrated in FIG.
  • the notification unit (B) 619b determines whether the mobile line network specified in S701 of FIG. 7 is used as the communication medium of the session, similarly to the processing of S1403 shown in FIG. 14 (S1803). ).
  • the session is not a notification target, and the process proceeds to S1819 without performing the processes after S1805.
  • the notification unit (B) 619b determines that the mobile terminal related to the session is the same as the process of S1405 illustrated in FIG. Is determined to be included in the area specified in S801 of FIG. 8 (S1805).
  • the notification unit (B) 619b specifies the mobile terminal related to the session. (S1807).
  • the notification unit (B) 619b reads the mobile network type and the PPP login ID from the field included in the record related to the session of the session management DB 607.
  • the notifying unit (B) 619b records in the mobile terminal DB 605 that the PPP login ID included in the data related to the mobile network specified by the read mobile network type matches the read PPP login ID. Search for.
  • the retrieved record is a record related to the mobile terminal.
  • the notifying unit (B) 619b identifies the mobile network in which the SIM card is already set in the record related to the mobile terminal (S1809).
  • the identified mobile network is a candidate for the switching destination.
  • the notification unit (B) 619b sends the telephone number, PPP login ID, and PPP password shown in FIG.
  • the body terminal 121 may be set with a SIM card. Further, the notification unit (B) 619b may specify the mobile network in which the SIM card is set.
  • the notification unit (B) 619b determines whether there is a candidate mobile network (S1811). If it is determined that there is no candidate mobile network, the switching instruction is not notified, and the process proceeds to S1819.
  • the notification unit (B) 619b further determines whether the number of candidate mobile networks is one or more (S1813). .
  • the notifying unit (B) 619b does not designate the switching-destination mobile circuit network, and the process of S1409 shown in FIG. Similarly, the switching instruction is notified to the mobile terminal 121 specified in S1807 (S1817).
  • the notification unit (B) 619b selects the mobile circuit network to be switched to (S1815). For example, the notification unit (B) 619b selects a switching destination mobile network in accordance with the priority order set in the priority order table 1601. However, the notification unit (B) 619b may specify the switching destination mobile network by another method.
  • the notification unit (B) 619b includes information indicating the switching destination mobile network in the switching instruction. Then, the notification unit (B) 619b notifies the switching instruction to the identified mobile terminal 121 in the same manner as the processing of S1409 shown in FIG. 14 (S1817).
  • the notifying unit (B) 619b determines whether there is an unprocessed session (S1819). If it is determined that there is an unprocessed session, the process returns to S1801.
  • the notification unit (B) 619b finishes the notification process (B) and proceeds to the process of S811 shown in FIG.
  • FIG. 19 shows a module configuration example of the authentication server 101 according to the third embodiment.
  • the storage area 603 according to the third embodiment includes an average packet loss rate table 1901.
  • FIG. 19 shows an example in which the average packet loss rate table 1901 is replaced with the disconnection rate table 611, an average packet loss rate table 1901 may be added. In the average packet loss rate table 1901, the average packet loss rate for each region is written.
  • the session management DB 607 includes a packet loss rate for each session.
  • the communication control unit 601 collects the packet loss rate measured by the mobile terminal 121 from the mobile terminal 121.
  • the communication control unit 601 may measure the packet loss rate in communication with the mobile terminal 121.
  • the authentication server 101 includes a calculation unit (B) 615b instead of the calculation unit (A) 615a described above.
  • the calculation unit (B) 615b calculates an average packet loss rate for each region.
  • the authentication server 101 includes a determination unit (B) 617b instead of the determination unit (A) 617a described above.
  • the determination unit (B) 617b determines whether to notify a switching instruction based on the average packet loss rate.
  • the notification unit 619 may be the above-described notification unit (A) 619a or the notification unit (B) 619b.
  • the process (B) for each mobile network is performed in S703 shown in FIG.
  • FIG. 20 shows a process (B) flow for each mobile network.
  • the specifying unit 613 specifies one unprocessed area among the areas managed in the area table 609 (S801). .
  • the calculation unit (B) 615b performs an average packet loss rate calculation process for the specified area (S2001).
  • the average packet loss rate is an average of packet loss rates in the mobile terminal 121 included in the area and connected via the mobile network.
  • FIG. 21 shows an example of an average packet loss rate calculation processing flow.
  • the calculation unit (B) 615b identifies one unprocessed session among the sessions managed by the session management DB 607 (S2101). For example, the calculation unit (B) 615b sequentially specifies the records managed by the session management DB 607.
  • the calculation unit (B) 615b determines whether or not the mobile line network specified in S701 of FIG. 7 is used as the communication medium of the session (S2103). Specifically, similarly to S1003 shown in FIG. 10, the calculation unit (B) 615b adds the mobile line identified in S701 of FIG. 7 to the mobile line network type field included in the record of the session. It is determined whether a network is set.
  • the session is not involved in calculating the average packet loss rate, and the process proceeds to S2111 without performing the processes after S2105.
  • the calculation unit (B) 615b determines the position of the mobile terminal related to the session in the same manner as S1005 shown in FIG. Is included in the area specified in S801 of FIG. 20 (S2105).
  • the calculation unit (B) 615b adds the packet loss rate of the session to the total (S2107).
  • the packet loss rate of the session is acquired from the average packet loss rate table 1901.
  • the sum is an internal parameter used in the average packet loss rate calculation process.
  • calculation unit (B) 615b increments the number of sessions (S2109).
  • the calculation unit (B) 615b determines whether there is an unprocessed session (S2111). If it is determined that there is an unprocessed session, the process returns to S2101.
  • the calculation unit (B) 615b calculates the average packet loss rate by dividing the total by the number of sessions (S2113). When the average packet loss rate is calculated, the calculation unit (B) 615b finishes the average packet loss rate calculation processing and returns to the processing of S2003 shown in FIG.
  • FIG. 22 shows a determination process (B) flow.
  • the determination unit (B) 617b determines whether or not the average packet loss rate exceeds the threshold (S2201). If it is determined that the average packet loss rate exceeds the threshold, the determination unit (B) 617b determines to “notify” the switching instruction (S2203). If it is determined that the average packet loss rate does not exceed the threshold, the determination unit (B) 617b determines that the switching instruction is “not notified” (S2205).
  • FIG. 23 shows a module configuration example of the authentication server 101 according to the fourth embodiment.
  • the storage area 603 according to the fourth embodiment includes an average delay time table 2301.
  • FIG. 23 shows an example in which the average delay time table 2301 is replaced with the disconnection rate table 611 and the average packet loss rate table 1901, the average delay time table 2301 may be added. In the average delay time table 2301, the average delay time for each region is written.
  • the session management DB 607 includes a delay time for each session.
  • the communication control unit 601 collects the delay time measured by the mobile terminal 121 from the mobile terminal 121.
  • the communication control unit 601 may measure a delay time in communication with the mobile terminal 121.
  • the authentication server 101 includes a calculation unit (C) 615c instead of the calculation unit (A) 615a and the calculation unit (B) 615b described above.
  • the calculation unit (C) 615c calculates an average delay time for each region.
  • the authentication server 101 includes a determination unit (C) 617c instead of the determination unit (A) 617a and the determination unit (B) 617b described above.
  • the determination unit (C) 617c determines whether to issue a switching instruction based on the average delay time.
  • the notification unit 619 may be the above-described notification unit (A) 619a or the notification unit (B) 619b.
  • the processing (C) for each mobile network is performed in S703 shown in FIG.
  • FIG. 24 shows a process (C) flow for each mobile network.
  • the specifying unit 613 manages the area table 609. One unprocessed area is identified among the existing areas (S801).
  • the calculation unit (C) 615c performs an average delay time calculation process for the identified area (S2401).
  • the average delay time is an average of delay times in the mobile terminal 121 included in the area and connected via the mobile network.
  • FIG. 25 shows an example of an average delay time calculation processing flow.
  • the calculation unit (C) 615c identifies one unprocessed session among the sessions managed by the session management DB 607 (S2501). For example, the calculation unit (C) 615c sequentially specifies the records managed by the session management DB 607.
  • the calculating unit (C) 615c determines whether or not the mobile network identified in S701 of FIG. 7 is used as the communication medium of the session (S2503). Specifically, similarly to S1003 shown in FIG. 10, the calculation unit (C) 615c adds the mobile line specified in S701 of FIG. 7 to the mobile line network type field included in the record of the session. It is determined whether a network is set.
  • the session is not involved in calculating the average delay time, and the process proceeds to S2511 without performing the processes after S2505.
  • the calculation unit (C) 615c determines the position of the mobile terminal related to the session as in S1005 shown in FIG. Is included in the area specified in S801 of FIG. 24 (S2505).
  • the session is not involved in the calculation of the average delay time, and the process proceeds to S2511 without performing the processes after S2507. .
  • the calculation unit (C) 615c adds the delay time of the session to the total (S2507).
  • the sum is an internal parameter used in the average delay time calculation process.
  • calculation unit (C) 615c increments the number of sessions (S2509).
  • the calculation unit (C) 615c determines whether there is an unprocessed session (S2511). If it is determined that there is an unprocessed session, the process returns to S2501.
  • the calculation unit (C) 615c calculates the average delay time by dividing the total by the number of sessions (S2513). When the average delay time is calculated, the calculation unit (C) 615c finishes the average delay time calculation process, and returns to the process of S2403 shown in FIG.
  • the determination unit (C) 617c performs a determination process (C) (S2403).
  • FIG. 26 shows a determination process (C) flow.
  • the determination unit (C) 617c determines whether or not the average delay time exceeds the threshold value (S2601). If it is determined that the average delay time exceeds the threshold, the determination unit (C) 617c determines to “notify” the switching instruction (S2603). If it is determined that the average delay time does not exceed the threshold, the determination unit (C) 617c determines that the switching instruction is “not notified” (S2605).
  • FIG. 27 shows a module configuration example of the authentication server 101 according to the fifth embodiment.
  • the storage area 603 according to the fifth embodiment includes an average radio wave intensity table 2701.
  • FIG. 27 shows an example in which the average radio wave intensity table 2701 is replaced with the cutting rate table 611, the average packet loss rate table 1901, and the average delay time table 2301, but an average radio wave intensity table 2701 may be added. In the average radio wave intensity table 2701, the average radio wave intensity for each region is written.
  • the session management DB 607 includes the radio wave intensity for each session.
  • the mobile terminal 121 measures the radio field intensity related to reception from the base station, and the communication control unit 601 collects the radio field intensity from the mobile terminal 121.
  • the authentication server 101 includes a calculation unit (D) 615d instead of the calculation unit (A) 615a, the calculation unit (B) 615b, and the calculation unit (C) 615c. .
  • the calculation unit (D) 615d calculates an average radio wave intensity for each region.
  • the authentication server 101 includes a determination unit (D) 617d instead of the determination unit (A) 617a, the determination unit (B) 617b, and the determination unit (C) 617c. .
  • the determination unit (D) 617d determines whether to issue a switching instruction based on the average radio wave intensity.
  • the notification unit 619 may be the above-described notification unit (A) 619a or the notification unit (B) 619b.
  • the processing (D) for each mobile network is performed in S703 shown in FIG.
  • FIG. 28 shows a process (D) flow for each mobile network.
  • S801 in the process (A) for each mobile network shown in FIG. 8 S801 in the process (B) for each mobile network shown in FIG. 20, and the process for each mobile network shown in FIG.
  • the specifying unit 613 specifies one unprocessed area among the areas managed in the area table 609 (S801).
  • the calculation unit (D) 615d performs an average radio wave intensity calculation process for the specified area (S2801).
  • the average radio wave intensity is an average of radio wave intensity in the mobile terminal 121 included in the area and connected via the mobile network.
  • FIG. 29 shows an example of an average radio wave intensity calculation process flow.
  • the calculation unit (D) 615d identifies one unprocessed session among the sessions managed by the session management DB 607 (S2901). For example, the calculation unit (D) 615d sequentially specifies the records managed by the session management DB 607.
  • the calculation unit (D) 615d determines whether or not the mobile line network specified in S701 of FIG. 7 is used as the communication medium of the session (S2903). Specifically, similarly to S1003 shown in FIG. 10, the calculation unit (D) 615d adds the mobile line specified in S701 of FIG. 7 to the mobile line network type field included in the record of the session. It is determined whether a network is set.
  • the session does not relate to the calculation of the average radio wave intensity, and the process proceeds to S2911 without performing the processes after S2905.
  • the calculation unit (D) 615d determines the position of the mobile terminal related to the session as in S1005 shown in FIG. Is included in the area specified in S801 of FIG. 28 (S2905).
  • the session is not involved in the calculation of the average radio wave intensity, and the process proceeds to S2911 without performing the processes after S2907. .
  • the calculation unit (D) 615d adds the radio field intensity of the session to the total (S2707).
  • the sum is an internal parameter used in the average radio wave intensity calculation process.
  • calculation unit (D) 615d increments the number of sessions (S2909).
  • the calculation unit (D) 615d determines whether or not there is an unprocessed session (S2911). If it is determined that there is an unprocessed session, the process returns to S2901.
  • the calculation unit (D) 615d calculates the average radio wave intensity by dividing the total by the number of sessions (S2913). When the average radio wave intensity is calculated, the calculation unit (D) 615d finishes the average radio wave intensity process and returns to the process of S2803 shown in FIG.
  • the determination unit (D) 617d performs a determination process (D) (S2803).
  • FIG. 30 shows a determination process (D) flow.
  • the determination unit (D) 617d determines whether or not the average radio wave intensity is below a threshold value (S3001). If it is determined that the average radio wave intensity is below the threshold, the determination unit (D) 617d determines that “notify” the switching instruction (S3003). If it is determined that the average radio field intensity is not below the threshold, the determination unit (D) 617d determines that the switching instruction is “not notified” (S3005).
  • the present technology has been described above, but the present technology is not limited to this.
  • the functional block configuration described above may not match the actual program module configuration.
  • each storage area described above is an example, and the configuration as described above is not necessarily required. Further, in the processing flow, the processing order can be changed if the processing result does not change. Further, it may be executed in parallel.
  • the authentication server 101 described above is a computer device, and as shown in FIG. 31, a memory 2501, a CPU (Central Processing Unit) 2503, a hard disk drive (HDD: Hard Disk Drive) 2505, and a display device 2509.
  • a display control unit 2507 connected to the computer, a drive device 2513 for a removable disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519.
  • An operating system (OS: Operating System) and an application program for performing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503.
  • OS Operating System
  • the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 according to the processing content of the application program, and performs a predetermined operation. Further, data in the middle of processing is mainly stored in the memory 2501, but may be stored in the HDD 2505. In an embodiment of the present technology, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above and programs such as the OS and application programs. .
  • the information processing apparatus determines whether or not the first mobile line network is appropriate based on the connection status with each of a plurality of mobile terminals via the first mobile line network. And an instruction to switch to connection via another mobile line network when it is determined that the use of the first mobile line network is inappropriate.
  • a notification unit that notifies at least one mobile terminal among the mobile terminals.
  • the determination unit may specify a plurality of mobile terminals located within a predetermined area. Further, the notification unit may specify at least one mobile terminal located in a predetermined area.
  • the information processing apparatus may further include a prioritizing unit that assigns a priority to each of the plurality of mobile circuit networks based on the usage status of each of the plurality of mobile circuit networks. Further, the notification unit may select the second mobile network based on the priority, and include information indicating the selected second mobile network in the instruction.
  • the information processing apparatus may further include a control unit that controls connection authentication with the mobile terminal and a calculation unit that calculates a disconnection rate based on a control history related to connection authentication. . Further, the connection status may be a status related to a disconnection rate in the connection.
  • connection status may be a status related to the packet loss rate in the connection, a status related to the delay time in the connection, or a status related to the strength of the radio wave received by the mobile terminal.
  • a program for causing a computer to carry out the processing described above such as a flexible disk, an optical disk such as a CD-ROM, a magneto-optical disk, a semiconductor memory (for example, ROM). Or a computer-readable storage medium such as a hard disk or a storage device. Note that data being processed is temporarily stored in a storage device such as a RAM.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Dans l'un de ses modes de réalisation, la présente invention se rapporte à un dispositif de traitement d'informations comprenant : un module de détermination qui est utilisé pour déterminer, sur la base de l'état de connexion avec chacun d'une pluralité de terminaux mobiles qui sont connectés via un premier réseau mobile à commutation de circuits, si l'utilisation du premier réseau mobile à commutation de circuits est appropriée, ou non ; et un module de notification qui, quand l'utilisation du premier réseau mobile à commutation de circuits n'est pas jugée appropriée, transmet à au moins l'un des terminaux mobiles de la pluralité de terminaux mobiles qui sont connectés via le premier réseau mobile à commutation de circuits, une instruction qui commande d'exécuter une commutation à une connexion exécutée via un autre réseau mobile à commutation de circuits. La solution technique décrite dans la présente invention permet d'éviter l'échec d'une communication exécutée via un réseau mobile à commutation de circuits.
PCT/JP2013/058675 2013-03-26 2013-03-26 Dispositif, système, et programme de traitement d'informations WO2014155503A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2013/058675 WO2014155503A1 (fr) 2013-03-26 2013-03-26 Dispositif, système, et programme de traitement d'informations

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2013/058675 WO2014155503A1 (fr) 2013-03-26 2013-03-26 Dispositif, système, et programme de traitement d'informations

Publications (1)

Publication Number Publication Date
WO2014155503A1 true WO2014155503A1 (fr) 2014-10-02

Family

ID=51622593

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/058675 WO2014155503A1 (fr) 2013-03-26 2013-03-26 Dispositif, système, et programme de traitement d'informations

Country Status (1)

Country Link
WO (1) WO2014155503A1 (fr)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004349834A (ja) * 2003-05-20 2004-12-09 Nippon Telegr & Teleph Corp <Ntt> ユーザ端末の接続制御方法および接続制御サーバ
JP2006020270A (ja) * 2004-06-04 2006-01-19 Ntt Docomo Inc ハンドオーバー制御装置、無線リソース管理装置、ネットワークリソース管理装置、移動通信システム及びハンドオーバー制御方法
WO2007066577A1 (fr) * 2005-12-08 2007-06-14 Sharp Kabushiki Kaisha Système de communication radio et méthode de communication radio
JP2008085792A (ja) * 2006-09-28 2008-04-10 Ntt Software Corp 接続端末数均衡化装置及び接続端末数均衡化方法
JP2008118171A (ja) * 2006-10-31 2008-05-22 Fujitsu Ltd 移動体通信ネットワークにおける輻輳制御方法および装置
JP2008259046A (ja) * 2007-04-06 2008-10-23 Matsushita Electric Ind Co Ltd 無線制御装置、無線基地局、通信端末装置及び強制ハンドオーバー方法
JP2011151610A (ja) * 2010-01-21 2011-08-04 Ntt Docomo Inc 移動通信システム、ネットワーク装置及び移動通信方法
JP2012231334A (ja) * 2011-04-26 2012-11-22 Ntt Docomo Inc 移動通信システムにおける基地局及び基地局において使用される方法

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004349834A (ja) * 2003-05-20 2004-12-09 Nippon Telegr & Teleph Corp <Ntt> ユーザ端末の接続制御方法および接続制御サーバ
JP2006020270A (ja) * 2004-06-04 2006-01-19 Ntt Docomo Inc ハンドオーバー制御装置、無線リソース管理装置、ネットワークリソース管理装置、移動通信システム及びハンドオーバー制御方法
WO2007066577A1 (fr) * 2005-12-08 2007-06-14 Sharp Kabushiki Kaisha Système de communication radio et méthode de communication radio
JP2008085792A (ja) * 2006-09-28 2008-04-10 Ntt Software Corp 接続端末数均衡化装置及び接続端末数均衡化方法
JP2008118171A (ja) * 2006-10-31 2008-05-22 Fujitsu Ltd 移動体通信ネットワークにおける輻輳制御方法および装置
JP2008259046A (ja) * 2007-04-06 2008-10-23 Matsushita Electric Ind Co Ltd 無線制御装置、無線基地局、通信端末装置及び強制ハンドオーバー方法
JP2011151610A (ja) * 2010-01-21 2011-08-04 Ntt Docomo Inc 移動通信システム、ネットワーク装置及び移動通信方法
JP2012231334A (ja) * 2011-04-26 2012-11-22 Ntt Docomo Inc 移動通信システムにおける基地局及び基地局において使用される方法

Similar Documents

Publication Publication Date Title
US11330646B2 (en) Method and system for network slice identification and selection
CN110120878B (zh) 获取链路质量的方法和装置
CN108616959B (zh) 一种通信方法、接入网设备、核心网设备和用户设备
US20200137621A1 (en) Method and system for admission control with network slice capability
CN107820291B (zh) 网络切片控制方法及相关设备
JP6835975B2 (ja) 通信方法、端末及びアクセスネットワークデバイス
KR20120024875A (ko) 로컬 인터넷 프로토콜 액세스에 의한 홈 네트워크 기지국으로부터의 외향 핸드오버 동안의 서비스 지속성
KR102415208B1 (ko) V2x 서비스뿐만 아니라 v2x 애플리케이션을 위한 엔티티, 네트워크, 및 사용자 장비
WO2007078102A1 (fr) Procede d&#39;assignation de bande de frequence, module d&#39;assignation de frequence et serveur de police dans le systeme internet portable sans fil
US20220060942A1 (en) Network Nodes for Handling Non-Fulfillment of QoS Requirements
KR20220024103A (ko) 무선 네트워크에서 긴급 서비스들을 처리하기 위한 방법 및 장치
CN109076362A (zh) 一种终端移动性模式的管理方法及装置
EP4009708A1 (fr) Procédé et dispositif de gestion et de commande d&#39;accès de tranche de réseau dans un système de communication sans fil
US20130083689A1 (en) Ownership requests for access points
EP3700258B1 (fr) Procédé et appareil de traitement d&#39;échec d&#39;établissement de liaison, et support de stockage informatique
CN111600916B (zh) 无人机控制方法、装置及系统
CN104349269A (zh) 一种更新策略控制功能信息的方法、装置和系统
WO2014155503A1 (fr) Dispositif, système, et programme de traitement d&#39;informations
JP6506190B2 (ja) 無線通信システム、制御方法及び制御局装置
EP3790316B1 (fr) Procédé et dispositif d&#39;acquisition de capacité de terminal
JP6355528B2 (ja) ゲートウェイ装置
EP4049471B1 (fr) Puce, appareil et procédé permettant de maintenir une connexion à au moins un réseau
CN103533612A (zh) 接入网切换方法、接入网络发现和选择功能实体和终端
CN114916090A (zh) 用于移动通信的方法及用户设备
WO2012173528A1 (fr) Traitement d&#39;offres de connexion d&#39;opérateurs dans un réseau de télécommunication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13879686

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13879686

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP