JP7489785B2 - Access destination determination device - Google Patents

Description

One aspect of the present disclosure relates to an access destination determination device that determines the network to be accessed by a mobile device that performs mobile communication.

The following Patent Document 1 discloses a remote control server that determines the access destination of a mobile phone depending on the state of the access destination of the mobile phone.

JP 2004-246811 A

However, the remote control server described above is unable to determine an access destination based on the technology supported by a mobile phone (mobile device), rather than on the state of the access destination.

Therefore, it is desirable for a mobile device to determine its access destination based on the technology it supports.

An access destination determination device according to one aspect of the present disclosure is an access destination determination device that determines, as an access destination for a mobile device performing mobile communications, a network that utilizes a coexistence technology that enables communication in a network in which multiple network protocols coexist, and includes an acquisition unit that acquires at least one of identification information that identifies the mobile device or correspondence information that indicates a coexistence technology that the mobile device supports, a determination unit that determines the coexistence technology that the mobile device supports based on at least one of the identification information or the correspondence information acquired by the acquisition unit, and a determination unit that determines, as an access destination for the mobile device, the network that utilizes the coexistence technology determined by the determination unit.

In this aspect, the coexistence technology that the mobile device supports is determined based on at least one of the acquired identification information and the correspondence information, and the network that uses the determined coexistence technology is determined as the access destination of the mobile device. In other words, it is possible to determine the access destination according to the technology that the mobile device supports.

According to one aspect of the present disclosure, a mobile device can determine an access destination according to the technology it supports.

1 is a diagram illustrating an example of a system configuration of an access destination determination system including an access destination determination device according to an embodiment. FIG. 2 is a diagram illustrating an example of a functional configuration of an access destination determination device according to an embodiment. FIG. 13 is a diagram illustrating an example of a table of type information. FIG. 13 is a diagram illustrating an example of a table of determination information. FIG. 13 illustrates an example of a table of access destination information. 11 is a flowchart illustrating an example of an access destination determination process executed by the access destination determination device according to the embodiment. 10 is a sequence diagram showing a part of an example of an access destination determination process executed by the access destination determination system according to the embodiment. FIG. 11 is a flowchart illustrating a part of an example of an access destination determination process executed by the access destination determination system according to the embodiment. 9 is a modified example of the flowchart of FIG. 8 . FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer used in the access destination determination device according to the embodiment.

Below, the embodiments of the present disclosure will be described in detail with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals, and duplicated descriptions will be omitted. In addition, the embodiments of the present disclosure in the following description are specific examples of the present invention, and the present invention is not limited to these embodiments unless otherwise specified to limit the present invention.

FIG. 1 is a diagram showing an example of a system configuration of an access destination determination system 7 including an access destination determination device (MME1) according to an embodiment. As shown in FIG. 1, the access destination determination system 7 includes an MME1, a UE2, a P-GW3, a PDN4, an HSS5, and a DNS6. Each component of the access destination determination system 7 may be composed of a plurality of components. For example, as shown in FIG. 1, the access destination determination system 7 includes UE2a, UE2b, UE2c, etc. (collectively referred to as "UE2") as UE2, and P-GW3a, P-GW3b, P-GW3c, P-GW3d, etc. (collectively referred to as "P-GW3") as P-GW3. The access destination determination system 7 is assumed to be a system conforming to a general mobile communication system such as 5G, which is a fifth generation mobile communication system, but is not limited thereto. The access destination determination system 7 may further include components included in a general mobile communication system. For example, the access destination determination system 7 may further include an evolved Node B (eNB), a serving gateway (S-GW), and a policy and charging rules function (PCRF) in 5G.

As shown in FIG. 1, in the access destination determination system 7, the MME1 and UE2 are communicatively connected to each other via a network (e.g., a wireless network) and can transmit and receive information to and from each other. In addition, the MME1 is communicatively connected to each other via a network (e.g., a wired network) and can transmit and receive information to and from each other.

The MME1 is a (logical) node or device that controls the mobility of UE2 and establishes and deletes bearers. For example, the MME1 determines PDN4 (including P-GW3, which is the connection point with the PDN4) as the access destination of UE2. In the embodiment, the MME1 is assumed to be an MME (Mobility Management Entity) in 5G, but is not limited to this. The MME1 is assumed to have the standard functions of an MME in 5G, but is not limited to this. Details of the MME1 will be described later.

UE2 is a terminal that performs mobile communication in a mobile communication system. In the embodiment, UE2 is assumed to be UE (User Equipment) in 5G, but is not limited to this. UE2 is assumed to have functions that UE in 5G has as standard, but is not limited to this.

The UE2 stores in advance, in a memory or the like provided in the UE2, identification information that identifies the UE2. The identification information is, for example, IMEISV (International Mobile Equipment Identifier (IMEI) Software Version). The UE2 transmits the identification information to the MME1 (via a wireless base station such as an eNB) at any time. For example, the UE2 transmits the identification information to the MME1 when making an access (connection) request (attach) to the access destination determination system 7.

UE2 stores compatibility information, which is information indicating the coexistence technologies supported by UE2, in a memory or the like provided in UE2. Note that the compatibility information may include information indicating one or more coexistence technologies.

A coexistence technology is a technology that enables multiple nodes or devices to communicate with each other through a network in which multiple network protocols coexist (one network protocol and one or more other network protocols coexist). The coexistence technology may be a technology that enables communication in a network in which at least IPv4 (Internet Protocol version 4) and IPv6 (Internet Protocol version 6) coexist. The coexistence technology includes a transition technology that is used when transitioning from one network protocol (e.g., IPv4) to another network protocol (e.g., IPv6). Examples of coexistence technologies include DNS64 and NAT64, which are technologies for accessing an IPv4 network from an IPv6 network, and 464XLAT, MAP (MAP-E and MAP-T), and DS-Lite, which ensure accessibility to an IPv4 network beyond an IPv6 network.

The correspondence information may be, for example, the text of the name of the coexistence technology (such as "DNS64", "NAT64", "464XLAT", "MAP-E", "MAP-T", and "DS-Lite"), or it may be a bit value corresponding to a particular coexistence technology.

The correspondence information may be configurable by a user of UE2 (such as a user who carries UE2 or a user who has a contract for mobile communications using UE2) or an application of UE2 (software installed on UE2). In other words, the user of UE2 or an application of UE2 may set or change the correspondence information in UE2 (dynamically) at any time.

UE2 transmits the compatibility information to MME1 (via a radio base station such as an eNB) at any timing. For example, UE2 transmits the compatibility information to MME1 when making an access request to the access destination determination system 7. Note that UE2 may transmit the identification information and the compatibility information to MME1 at the same time, or may transmit the identification information and the compatibility information to MME1 at separate timings.

The P-GW3 is a gateway (logical node or device) that performs IP address assignment, protocol conversion, packet forwarding, etc. The P-GW3 is a connection point with the PDN4, and performs connection (access) between the UE2 and the PDN4. In the embodiment, the P-GW3 is assumed to be a P-GW (Packet Data Network Gateway) in 5G, but is not limited to this. The P-GW3 is assumed to have the standard functions of a P-GW in 5G, but is not limited to this.

PDN4 is a network, more specifically an external network (for example, a network outside the core network of the mobile communication system). PDN4 includes a network using a coexistence technology. PDN4 may be a collection of multiple networks, in which case at least one of the networks may use a coexistence technology. For example, PDN4 may include a network based on IPv6 and a network based on IPv4, and 464XLAT, which is a coexistence technology for IPv6 and IPv4, may be used in PDN4. In the embodiment, PDN4 is assumed to be a PDN (Packet Data Network) in 5G, but is not limited to this. Note that the access destination determination system 7 may not include PDN4 (because PDN4 is an "external" network), and the MME1 may determine PDN4 outside the access destination determination system 7 as the access destination of the UE2.

HSS5 is a user (subscriber) information database in the mobile communication system, and manages authentication information, location information, and the like. HSS5 stores a user profile, which is profile information of a user of UE2. The user profile may include PDN Type. PDN Type indicates an access IP version to an APN (Access Point Name), which is an access point name (of PDN4). The value of PDN Type may include three types: "IPv4", "IPv6", and "IPv4v6" (dual stack). In the user profile, the PDN Type may be preset for each user or for each UE2 of the user. In the embodiment, the HSS5 is assumed to be a 5G HSS (Home Subscriber Server), but is not limited thereto. The HSS5 is assumed to have the standard functions of a 5G HSS, but is not limited thereto.

DNS6 is a database that manages access destinations. In the embodiment, DNS6 is assumed to be a 5G DNS (Domain Name System), but is not limited to this. DNS6 is assumed to have the standard functions of a 5G DNS, but is not limited to this.

As described above, the MME1 may determine, as the access destination for the UE2, a (specific) PDN4 (including the P-GW3, which is the connection point to the PDN4) that utilizes coexistence technology, which is technology that enables communication in a network where multiple network protocols coexist. Details of the MME1 are described below.

Figure 2 is a diagram showing an example of the functional configuration of the MME1 according to the embodiment. As shown in Figure 2, the MME1 includes an acquisition unit 10 (acquisition unit), a storage unit 11, a determination unit 12 (determination unit), a decision unit 13 (decision unit), and an access unit 14.

Each functional block of MME1 is assumed to function within MME1, but this is not limited to the above. For example, some of the functional blocks of MME1 may function in a node or device different from MME1, within a node or device that is network-connected to MME1, while appropriately sending and receiving information with MME1. In addition, some functional blocks of MME1 may not be present, multiple functional blocks may be integrated into one functional block, or one functional block may be decomposed into multiple functional blocks.

The following describes each function of MME1 shown in Figure 2.

The acquisition unit 10 acquires at least one of the identification information and the correspondence information (hereinafter referred to as "acquired information" as appropriate). That is, the acquisition unit 10 may acquire only the identification information, may acquire only the correspondence information, may acquire the identification information and the correspondence information, may acquire the identification information and other information (other than the correspondence information), may acquire the correspondence information and other information (other than the identification information), or may acquire the identification information, the correspondence information, and other information (other than the identification information and the correspondence information). The acquisition unit 10 may acquire at least the identification information.

The acquisition unit 10 may acquire the acquisition information from the UE 2 via the network, from other nodes or devices via the network, or from a memory of the MME 1 where the information is stored in advance.

The acquisition unit 10 may acquire the acquisition information at any timing. For example, the acquisition unit 10 may acquire the acquisition information at the timing when the UE2 or another node or device transmits the acquisition information to the MME1, or at the timing when the UE2 makes an access request to the access destination determination system 7 (i.e., the timing when the UE2 transmits the acquisition information to the MME1), or at a timing designated in advance by an administrator of the MME1 or the access destination determination system 7, or may acquire the acquisition information periodically.

The acquisition unit 10 may store the acquired information in the storage unit 11, or may output the information to the determination unit 12.

The storage unit 11 stores the acquired information acquired by the acquisition unit 10.

The storage unit 11 may store type information, which is information used when determining the PDN Type of UE2. FIG. 3 is a diagram showing an example of a table of type information. The example of the table of type information shown in FIG. 3 is a correspondence table between the PDN Type supported by UE2 (three types: "IPv4", "IPv6", and "IPv4v6") and the PDN Type set in the user profile (three types: "IPv4", "IPv6", and "IPv4v6"). For example, if the PDN Type supported by UE2 is "IPv4" and the PDN Type set in the user profile is "IPv4", the value "IPv4" of the cell where the row where the PDN Type supported by UE2 is "IPv4" and the column where the PDN Type set in the user profile is "IPv4" intersect is determined (by the determination unit 12, etc.) as the PDN Type of UE2. Similarly, if the PDN type supported by UE2 is "IPv6" and the PDN type set in the user profile is "IPv4v6", "IPv6" is determined (by the determination unit 12, etc.) as the PDN type of UE2.

The storage unit 11 may store judgment information, which is information used in the judgment by the judgment unit 12. FIG. 4 is a diagram showing an example of a table of judgment information. In the example of the table of judgment information shown in FIG. 4, the value of "IMEISV" for identifying UE2, the value of "v6 single" indicating whether or not UE2 supports IPv6 (a specified network protocol) (whether or not there is a problem with communication using only IPv6) (such as "Yes" indicating support, or "No" indicating no support), and the value of "v6 compatible NW" indicating a coexistence technology that enables communication in a network where IPv4 and IPv6 (multiple network protocols) coexist (such as text indicating the name of the coexistence technology) are associated. Note that one or more values of "v6 compatible NW" may be associated.

For example, the first line of the example table of determination information indicates that UE2 with an IMEISV of "1234568790123456" supports IPv6 (there is no problem with communication using only IPv6, or communication using only IPv6 is possible) and supports "464XLAT" (communication with a network using 464XLAT is possible). The second line of the example table indicates that UE2 with an IMEISV of "2345687901234567" does not support IPv6 (there is a problem with communication using only IPv6, or communication using only IPv6 is impossible). The third line of the example table indicates that UE2 with an IMEISV of "3456879012345678" supports IPv6, but there is no compatible coexistence technology.

The storage unit 11 may store access destination information, which is information used by the determination unit 13 to determine an access destination. FIG. 5 is a diagram showing an example of a table of access destination information. In the example table of access destination information shown in FIG. 5, a "service parameter" which is a parameter indicating a service of an access destination is associated with an "access destination" which indicates an access destination. One or more values of the "access destination" may be associated. The access destination information may further be associated with an "APN name" which identifies an APN.

For example, the first line of the example table of access destination information indicates that if the service parameters correspond to "x-3gpp-pgw:x-s5-gtp", then "P-GW3a" is determined (by the determination unit 13, etc.) as a candidate access destination. The second line of the example table indicates that if the service parameters correspond to "x-3gpp-pgw:x-s5-gtp", then "P-GW3b" is determined (by the determination unit 13, etc.) as a candidate access destination. The third line of the example table indicates that if the service parameters correspond to "x-3gpp-pgw:x-s5-gtp+nc-v6", then "P-GW3c" is determined (by the determination unit 13, etc.) as a candidate access destination. Furthermore, the fourth line of the example table indicates that if the service parameter corresponds to "x-3gpp-pgw:x-s5-gtp+nc-v6.464xlat", then "P-GW3d" is determined (by the determination unit 13, etc.) as a candidate access destination. Note that the character string following "+nc-" in the service parameter, for example, "v6" and "v6.464xlat" in the above example, is a value (network capability value) indicating the capability of the network related to the associated "access destination".

The storage unit 11 may also store any information used in calculations in the MME1 and the results of calculations in the MME1. The information stored by the storage unit 11 may be referenced by each function of the MME1 as appropriate.

The determination unit 12 determines the coexistence technology supported by the UE2 based on the acquired information (at least one of the identification information or the correspondence information) acquired (input) by the acquisition unit 10 or the acquired information stored by the storage unit 11. That is, the determination unit 12 may determine the coexistence technology supported by the UE2 based on the identification information, may determine the coexistence technology supported by the UE2 based on the correspondence information, may determine the coexistence technology supported by the UE2 based on the identification information and the correspondence information, may determine the coexistence technology supported by the UE2 based on the identification information and other information (other than the correspondence information), may determine the coexistence technology supported by the UE2 based on the correspondence information and other information (other than the identification information), or may determine the coexistence technology supported by the UE2 based on the identification information, the correspondence information, and other information (other than the identification information and the correspondence information). The determination unit 12 may determine one or more (including multiple) coexistence technologies as the coexistence technologies supported by the UE2. The determination unit 12 outputs information related to the determined coexistence technology to the determination unit 13.

For example, the determination unit 12 may determine that the coexistence technology indicated by the value of "v6 compatible NW" associated with the identification information ("IMEISV") acquired by the acquisition unit 10 in the example table of determination information shown in FIG. 4 is the coexistence technology supported by UE2. In addition, for example, the determination unit 12 may determine that the coexistence technology indicated by the compatibility information acquired by the acquisition unit 10 is the coexistence technology supported by UE2.

The determination unit 12 may further determine whether or not the UE2 supports a network protocol included in the multiple network protocols based on the identification information acquired by the acquisition unit 10. The determination unit 12 may also determine whether or not the UE2 supports a network protocol included in the multiple network protocols based on the identification information acquired by the acquisition unit 10, and determine the coexistence technology supported by the UE2 when it is determined that the UE2 supports the network protocol (as described above). The determination unit 12 may output the determination result (whether or not the UE2 supports a network protocol included in the multiple network protocols) to the decision unit 13.

For example, in the example table of determination information shown in FIG. 4, if the value of "v6 single" associated with the identification information ("IMEISV") acquired by the acquisition unit 10 is "Yes", the determination unit 12 may determine that UE2 supports IPv6, and if the value is "No", the determination unit 12 may determine that UE2 does not support IPv6.

The determination unit 12 may calculate the coexistence technology supported by UE2 based on the identification information acquired by the acquisition unit 10, and may also calculate the coexistence technology supported by UE2 based on the support information acquired by the acquisition unit 10, and determine the coexistence technology supported by UE2 based on the two calculations.

For example, in the example table of determination information shown in FIG. 4, the determination unit 12 may calculate (extract) the coexistence technology indicated by one or more values of "v6 compatible NW" associated with the identification information ("IMEISV") acquired by the acquisition unit 10, and may calculate (extract) one or more coexistence technologies indicated by the correspondence information acquired by the acquisition unit 10, and determine the intersection or union of the coexistence technologies calculated by each calculation as the coexistence technology supported by UE2.

The determination unit 13 determines PDN4, which utilizes the coexistence technology determined by the determination unit 12, as the access destination of UE2. Note that determining PDN4 also includes determining P-GW3 (gateway), which is the connection point with PDN4. In other words, determining PDN4 as the access destination means determining the PDN4 network itself, a node or device constituting PDN4, or a node or device that is a relay point for access to PDN4, as the access destination. The determination unit 13 outputs information about the determined access destination to the access unit 14.

For example, when information related to the coexistence technology determined by the determination unit 12 is input from the determination unit 12, the determination unit 13 determines the P-GW3 (or the PDN4 to which the P-GW3 is the connection point) indicated by the "access destination" associated with the "service parameter" including the name related to the coexistence technology indicated by the information in the example table of access destination information shown in FIG. 5, as the access destination of UE2. For example, when the coexistence technology determined by the determination unit 12 is "464XLAT", the determination unit 13 determines the P-GW3d, which is the "access destination" associated with the "service parameter" including the name "464xlat" (network capability value) in the example table of access destination information shown in FIG. 5, as the access destination of UE2.

The determination unit 13 may determine the PDN4 using the coexistence technology (enabling communication in a network where one network protocol and one or more other network protocols coexist) determined by the determination unit 12 as the access destination to be accessed by the UE2 using the one network protocol. More specifically, the determination unit 13 may determine the PDN4 using the coexistence technology (enabling communication in a network where at least IPv4 and IPv6 coexist) determined by the determination unit 12 as the access destination to be accessed by the UE2 using IPv6.

For example, the determination unit 13 determines the network protocol used by UE2 using existing technology, and when determining the access destination of UE2, determines PDN4 using coexistence technology that enables communication in a network where the determined network protocol coexists. Also, for example, the determination unit 13 determines the network protocol supported by UE2 based on the determination result input from the determination unit 12 (whether UE2 supports a network protocol included in multiple network protocols), and determines PDN4 using coexistence technology that enables communication in a network where the determined network protocol coexists.

When the determination unit 12 determines that the UE 2 is compatible (with a network protocol included in the multiple network protocols), the determination unit 13 may determine the PDN 4 using the coexistence technology determined by the determination unit 12 as the access destination of the UE 2. For example, when the determination result (whether the UE 2 is compatible with a network protocol included in the multiple network protocols) is input from the determination unit 12, the determination unit 13 may determine the PDN 4 using the coexistence technology determined by the determination unit 12 as the access destination of the UE 2 if the determination result indicates that the UE 2 is compatible (with a network protocol included in the multiple network protocols). In addition, when the determination result indicates that the UE 2 is not compatible, the determination unit 13 may determine the PDN 4 other than the PDN 4 using the coexistence technology determined by the determination unit 12 as the access destination of the UE 2.

The access unit 14 causes the UE 2 to access the access destination determined by the determination unit 13. For example, when information regarding the access destination (determined by the determination unit 13) is input from the determination unit 13, the access unit 14 causes the UE 2 to access the access destination indicated by the information. The method of accessing is the same as that used in a general mobile communication system.

Next, an example of the access destination determination process executed by MME1 will be described with reference to FIG. 6. FIG. 6 is a flowchart showing an example of the access destination determination process executed by MME1.

First, the acquisition unit 10 acquires acquisition information (at least one of identification information for identifying UE2 and compatibility information indicating the coexistence technology supported by UE2) (step S1, acquisition step). Next, the determination unit 12 determines the coexistence technology supported by UE2 based on the acquisition information acquired in S1 (step S2, determination step). Next, the decision unit 13 decides that the PDN4 using the coexistence technology determined in S2 is to be the access destination for UE2 (step S3, decision step).

Next, a specific example of the access destination determination process executed by the access destination determination system 7 will be described with reference to Figures 7 to 9.

Figure 7 is a sequence diagram showing a part of an embodiment of the access destination determination process executed by the access destination determination system 7. Figure 7 shows a scene of the Attach Procedure in a mobile communication system, but the same applies to the case of the PDN Connectivity Procedure.

First, UE2 sends an EMM_Attach Request to MME1 (step S10). The EMM_Attach Request may include a PDN Type (supported by UE2), or may include at least one of a PDN Type or corresponding information (supported by UE2). MME1 (acquisition unit 10) may acquire information (such as a PDN Type, or at least one of a PDN Type or corresponding information) included in the EMM_Attach Request sent in S10, and store and hold it in a storage unit 11, etc. Next, MME1 sends an EMM_Security Mode Command to UE2 (step S11). Next, UE2 sends EMM_Security Mode Complete to MME1 (step S12). EMM_Security Mode Complete may include an IMEISV, which is identification information of UE2. The MME1 (acquisition unit 10) may acquire information (such as IMEISV) included in the EMM_Security Mode Complete sent in S12, and store and hold it in the storage unit 11 or the like. Next, the MME1 transmits an ESM_ESM Information Request to the UE2 (step S13). Next, the UE2 transmits an ESM_ESM Information Response to the MME1 (step S14). The ESM_ESM Information Response may include an APN indicating the access destination requested by the UE2 (user). The MME1 (acquisition unit 10) may acquire information (APN) included in the ESM_ESM Information Response sent in S14, and store and hold it in the storage unit 11 or the like.

Next, MME1 transmits Diameter_ULR to HSS5 (step S15). Next, HSS5 transmits Diameter_ULA to MME1 (step S16). Diameter_ULA may include a user profile stored in HSS5 or PDN Type (set in the user profile). MME1 (acquisition unit 10) may acquire information (user profile or PDN Type) included in Diameter_ULA transmitted in S16, and store and hold it in storage unit 11 or the like. Next, MME1 (determination unit 12 and decision unit 13) decides the access destination of UE2 (step S17). Details of the decision of the access destination in S17 will be described with reference to Figures 8 and 9.

Figure 8 is a flowchart showing part of an embodiment of the access destination determination process executed by the access destination determination system 7. Specifically, Figure 8 is a flowchart showing the details of the process of the MME 1 in S17 of Figure 7.

First, the determination unit 12 performs a Requested PDN type determination (step S20). Specifically, the determination unit 12 determines the PDN type of UE2 based on the PDN type supported by UE2 acquired in S10 of FIG. 7, the PDN type set in the user profile acquired in S16 of FIG. 7, and the type information stored by the storage unit 11 (see the example table of type information shown in FIG. 3) (the specific determination method is as described above). If the PDN type of UE2 is determined to be "IPv4v6" in S20 (S20: IPv4v6), the determination unit 12 then performs a v6 single compatibility determination (step S21). Specifically, the determination unit 12 determines whether or not the UE 2 supports IPv6 (v6 single support (Bit = 1) or v6 single non-support (Bit = 0 (default))) based on the identification information of the UE 2 acquired in S12 of FIG. 7 and the determination information stored by the storage unit 11 (see the example table of determination information shown in FIG. 4) (the specific determination method is as described above). Note that v6 single support may mean that operation in a v6 single stack is possible.

If it is determined in S21 that UE2 supports IPv6 (v6 single support) (S21: v6 single support), or if it is determined in S20 that the PDN Type of UE2 is "IPv6" (S20: IPv6), the determination unit 12 then performs v6-compatible NW determination (step S22). Specifically, the determination unit 12 determines whether UE2 supports 464XLAT (464XLAT target call or 464XLAT non-target call) based on the identification information of UE2 acquired in S12 of FIG. 7 and the determination information stored by the storage unit 11 (see the table example of the determination information shown in FIG. 4), or based on the correspondence information acquired in S10 of FIG. 7 (the specific determination method is as described above). Note that in S22, only 464XLAT is determined as a coexistence technology, but this is not limited to this, and one or more arbitrary coexistence technologies may be determined.

If it is determined in S22 that UE2 is compatible with 464XLAT (464XLAT target call) (S22: 464XLAT target call), the determination unit 13 then performs a new P-GW3 selection process (search target: +nc-v6.464xlat) (step S23). Specifically, the determination unit 13 selects (determines) a P-GW3 (GW candidate) that is compatible with 464XLAT and is to be an access destination candidate for UE2 based on the access destination information stored by the storage unit 11 (see the example table of access destination information shown in FIG. 5). For example, the determination unit 13 selects, as a GW candidate, P-GW3d, which is an "access destination" associated with a "service parameter" that includes the text "+nc-v6.464xlat" (or network capability value "v6.464xlat") indicating compatibility with 464XLAT, in the example table of access destination information shown in FIG. 5. Note that a plurality of GW candidates may be selected. In addition, in selecting the access destination candidate, the selection may be further based on the network protocol used by UE2. In addition, in selecting the access destination candidate, the selection may be further based on the APN acquired in S14 of FIG. 7 and the APN associated with the access destination information.

On the other hand, if it is determined in S22 that UE2 does not support 464XLAT (464XLAT non-target call) (S22: 464XLAT non-target call), the determination unit 13 then performs a new P-GW3 selection process (search target: +nc-v6) (step S24). Specifically, the determination unit 13 selects (determines) a P-GW3 (GW candidate) that does not support 464XLAT and is to be an access destination candidate for UE2 based on the access destination information stored by the storage unit 11 (see the access destination information table example shown in FIG. 5). For example, the determination unit 13 selects, as a GW candidate, the P-GW3c that is the "access destination" associated with the "service parameter" that includes the text "+nc-v6" (excluding "+nc-v6.464xlat") (or the network capability value "v6") indicating that 464XLAT is not supported in the access destination information table example shown in FIG. 5. Note that a plurality of GW candidates may be selected. In addition, in selecting the access destination candidate, the selection may be further based on the network protocol used by UE2. In addition, in selecting the access destination candidate, the selection may be further based on the APN acquired in S14 of FIG. 7 and the APN associated with the access destination information.

Following S23 or S24, the determination unit 13 determines whether there is a GW candidate in the search results (step S25). Specifically, the determination unit 13 determines whether there is a GW candidate (selected so far). If it is determined in S25 that there is no GW candidate (S25: no GW candidate), if it is determined in S20 that the PDN Type of UE2 is "IPv4" (S20: IPv4), or if it is determined in S21 that UE2 does not support IPv6 (v6 single not supported) (S21: v6 single not supported), the determination unit 13 then performs an existing P-GW3 selection process (step S26). Specifically, for example, the determination unit 13 determines a P-GW3 that supports IPv4 or IPv4v6 as the access destination of UE2. On the other hand, if it is determined in S25 that there is a GW candidate (S25: GW candidate present), the determination unit 13 then performs a new P-GW3 selection process (step S27). Specifically, for example, the determination unit 13 determines a P-GW3 (such as a P-GW3 that supports IPv6 only) included in the GW candidates as the access destination for UE2.

Figure 9 is a modified version of the flowchart in Figure 8. Specifically, Figure 9 is a flowchart in which the order of the determinations in S21 and S22 in Figure 8 is reversed. S20a to S27a in Figure 9 correspond to S20 to S27 in Figure 8, respectively (with the "a" removed from the reference numerals), and the processing content is almost the same. Below, the differences will be mainly explained.

If it is determined in S20a that the PDN Type of UE2 is "IPv4v6" or "IPv6" (S20a: IPv4v6, IPv6), proceed to S22a. After S23a or S24a, proceed to S21a. If it is determined in S21a that UE2 supports IPv6 (v6 single support) (S21a: v6 single support), proceed to S25a.

Next, we will explain the effects of the MME1 according to the embodiment.

The MME1, which determines the PDN4 using a coexistence technology that enables communication in a network where multiple network protocols coexist as the access destination of a UE2 performing mobile communication, includes an acquisition unit 10 that acquires at least one of identification information that identifies the UE2 or correspondence information indicating the coexistence technology that the UE2 supports, a determination unit 12 that determines the coexistence technology that the UE2 supports based on at least one of the identification information or correspondence information acquired by the acquisition unit 10, and a determination unit 13 that determines the PDN4 using the coexistence technology determined by the determination unit 12 as the access destination of the UE2. With this configuration, the coexistence technology that the UE2 supports is determined based on at least one of the acquired identification information or correspondence information, and the PDN4 using the determined coexistence technology is determined as the access destination of the UE2. In other words, it is possible to determine the access destination according to the technology (coexistence technology) that the UE2 supports.

In addition, in the MME1, the coexistence technology is a technology that enables communication in a network in which one network protocol and one or more other network protocols coexist, and the determination unit 13 may determine the PDN4 that uses the coexistence technology determined by the determination unit 12 as the access destination to be accessed by the UE2 using the one network protocol. With this configuration, the UE2 can more reliably access the determined access destination using the one network protocol.

In addition, in the MME1, the coexistence technology may be a technology that enables communication in a network in which at least IPv4 and IPv6 coexist. With this configuration, the PDN4 in which IPv4 and IPv6 coexist can be determined as the access destination for the UE2.

In addition, in the MME1, the determination unit 13 may determine the PDN4 using the coexistence technology determined by the determination unit 12 as the access destination for the UE2 to access using IPv6. With this configuration, the UE2 can access the determined PDN4 (where IPv4 and IPv6 coexist) using IPv6.

Furthermore, according to the MME1, the acquisition unit 10 acquires at least the identification information, and the determination unit 12 may determine whether or not the UE2 supports a network protocol included in the multiple network protocols based on the identification information acquired by the acquisition unit 10, and determine the coexistence technology supported by the UE2 when it is determined that the UE2 supports the network protocol included in the multiple network protocols. With this configuration, it is guaranteed that the UE2 supports a network protocol included in the multiple network protocols, so that the UE2 can more reliably access the determined access destination. Furthermore, if the UE2 does not support a network protocol included in the multiple network protocols, the determination of the coexistence technology can be omitted, thereby speeding up processing.

Furthermore, according to the MME1, the acquisition unit 10 acquires at least the identification information, and the determination unit 12 further determines whether or not the UE2 supports a network protocol included in the multiple network protocols based on the identification information acquired by the acquisition unit 10, and the decision unit 13 may determine, when the determination unit 12 determines that the UE2 supports the network protocol, the PDN4 that utilizes the coexistence technology determined by the determination unit 12 as the access destination of the UE2. With this configuration, it is guaranteed that the UE2 supports a network protocol included in the multiple network protocols, so that the UE2 can more reliably access the determined access destination.

Furthermore, according to the MME1, the acquisition unit 10 acquires the identification information and the correspondence information, and the determination unit 12 calculates the coexistence technology supported by the UE2 based on the identification information acquired by the acquisition unit 10, and calculates the coexistence technology supported by the UE2 based on the correspondence information acquired by the acquisition unit 10, and may determine the coexistence technology supported by the UE2 based on these two calculations. With this configuration, the coexistence technology is determined based on both the identification information and the correspondence information, so that a more accurate coexistence technology can be determined. As a result, a more appropriate access destination can be determined.

Furthermore, according to the MME1, the correspondence information may be configurable by the user of the UE2 or an application of the UE2. With this configuration, the correspondence information can be dynamically configured. As a result, for example, by dynamically configuring the correspondence information according to the situation of the UE2 or the situation of the user of the UE2, it is possible to determine an appropriate access destination according to the situation.

Here, the background art will be described. In a mobile communication network, a mobile device can support either or both of IPv4 and IPv6. Also, a core network can support either or both of IPv4 and IPv6 depending on the characteristics of the accessed PDN. For example, a mobile device that supports only IPv4 can access a PDN that supports IPv4, but cannot access a PDN that supports IPv6. Also, a mobile device that supports only IPv6 can access a PDN that supports IPv6, but cannot access a PDN that supports IPv4. Also, a mobile device that supports both IPv4 and IPv6 can access a PDN that supports IPv4, and can also access a PDN that supports IPv6.

IPv6 to IPv4 transition technologies include DNS64/NAT64, which is a technology for connecting from an IPv6 network to IPv4 (technology for ensuring reachability), and 464XLAT (a location where NAT session (state) management is performed (CPE (Customer Premises Equipment) or ISP (Internet Services Provider)) (same below): ISP side stateful, translation), MAP-E (ISP side stateless, encapsulation), MAP-T (ISP side stateless, translation), and DS-Lite (ISP side stateful, encapsulation), which ensures connectivity to IPv4 beyond the IPv6 network (backbone) (such as performing IPv4 communication on IPv6). In DNS64/NAT64, for example, DNS64 is installed in an IPv6 network, and NAT64 is installed at the connection point between the IPv6 network and the IPv4 network, and 64 conversion (RFC6146 (NAT64)) is performed by NAT64. However, for example, DNS64/NAT64 cannot handle the case where IPv4 is directly used without using DNS. In a mobile communication network, the problem of NAT64/DNS64 can be solved by having the function of CPE in the terminal. For example, when a mobile device that communicates by IPv4 goes beyond an ISP of an IPv6 network and accesses the Internet of an IPv4 network, 46 conversion (RFC7915) is performed by a CLAT (Customer-side Translator) at the connection point between the mobile device and the ISP, and 64 conversion (RFC6146 (NAT64)) is performed by a PALT (Provider-side Translator) at the connection point between the ISP and the Internet. However, not all mobile devices have this function. Additionally, supported technologies may change depending on the capabilities of the mobile device.

Here, when migrating to IPv6 due to the exhaustion of IPv4, it is possible for a mobile communication network to assign only IPv6 to a mobile station and connect an IPv6-compatible mobile station to an IPv6-compatible PDN. On the other hand, when operating with IPv6 only, it is necessary to ensure reachability to an IPv4 network. In order to migrate to IPv6, there are issues such as wanting to ensure connectivity to an IPv4 network even with only IPv6, wanting to ensure connectivity to IPv4 when IPv6-only even if IPv6 is supported, and wanting to operate with IPv6 only as much as possible, but in such cases, how to access IPv4. As a technology for this, various methods have been proposed, such as DNS64/NAT64, MAP-E, 464XLAT, and DS-Lite. However, as mentioned above, each technology has its disadvantages, and it is necessary to use them according to the purpose and support situation. For example, when dealing with NAT64/DNS64, there is an issue that connection cannot be made when an IPv4 address is directly entered. As a countermeasure, IPv4/IPv6 dualstack or a combination of other technologies are candidates. On the other hand, IPv4/IPv6 dualstack does not solve the problem of IPv4 exhaustion, but it may be desirable in some cases. When combined with other transition technologies (464XLAT, DS-Lite, MAP, etc.), the way the network handles it varies depending on which technology the mobile device supports. However, it is unclear which transition technology the mobile device supports. In other words, it is not possible to use each technology separately in the mobile communication network. This is because there is no way to know which transition technology the mobile device supports.

In the embodiment, the MME1 determines the transition technology supported by the UE2 from the terminal type (identification information) and connects the UE2 to the appropriate PDN4. The MME1 also receives support capabilities (support information) from the UE2 and connects the UE2 to the appropriate PDN. The determination unit 12 may determine which model the UE2 is. The determination unit 12 may determine the access destination APN or the PDN Type of the UE2. The determination unit 12 may determine whether the UE2 is an IPv6-compatible terminal or not. The determination unit 12 may combine the determination results by the above-mentioned determination unit 12 to determine whether access is possible. The MME1 may also select a P-GW3 according to the values of the terminal type (identification information) or terminal capabilities (support information) and the PDN Type. If the result of PDN Type determination shows that IPv6 is available, the MME1 may access the P-GW3 that has IPv6 network capabilities, and may also access an appropriate IPv6 network based on the terminal type or terminal capabilities. The MME1 can handle any coexistence technology with one network (core network). The MME1 can allow a UE2 capable of communicating using IPv6 to access IPv4 if there is a problem with the communication. The MME1 can also be called a method for selecting an IPv6-only NW (network).

The MME1 may include a call control signal transmitting/receiving unit that transmits and receives call control signals to and from the UE2, HSS5, S-GW, etc., a control unit that controls the entire MME1, an analysis unit that analyzes packets that are transmitted and received, and a condition determination unit that performs condition determination based on the analyzed packets. The UE2 may include a call control signal transmitting/receiving unit that transmits and receives call control signals to and from the MME1, etc., a control unit that controls the entire UE2, and a terminal capability holding unit that holds terminal capabilities (compatible information).

In response to an access request to an APN, the MME1 determines which PDN4 the MME1 should access based on the contract (user profile) or supported capabilities, which provides the following benefits: (1) A UE2 that supports IPv6 but has problems operating in IPv6-only mode can be operated in a dual stack of IPv4 and IPv6 (see v6 single compatibility determination above). (2) When operating in IPv6-only mode, a UE2 that supports various transition technologies can be allowed to access a compatible network (see v6-compatible network determination above).

The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional blocks may be realized by combining the one device or the multiple devices with software.

Functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on the method of realization for either of these.

For example, the MME1 in one embodiment of the present disclosure may function as a computer that performs processing of the access destination determination method of the present disclosure. FIG. 10 is a diagram showing an example of the hardware configuration of the MME1 according to one embodiment of the present disclosure. The above-mentioned MME1 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

In the following description, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of MME1 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

The functions of MME1 are realized by loading specific software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communications by communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned acquisition unit 10, judgment unit 12, decision unit 13, and access unit 14 may be realized by the processor 1001.

The processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. The programs used are those that cause the computer to execute at least some of the operations described in the above-mentioned embodiments. For example, the storage unit 11 may be realized by a control program stored in the memory 1002 and running on the processor 1001, and may be similarly realized for other functional blocks. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

The memory 1002 is a computer-readable recording medium, and may be composed of at least one of, for example, a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned acquisition unit 10, judgment unit 12, decision unit 13, and access unit 14, etc., may be realized by the communication device 1004.

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).

In addition, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

The MME1 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

Notification of information is not limited to the aspects/embodiments described in this disclosure and may be performed using other methods.

Each aspect/embodiment described in this disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other suitable systems, and next-generation systems extended based on these. In addition, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

The processing steps, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

Information, etc. may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input/output via multiple network nodes.

The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.

The determination may be based on a value represented by one bit (0 or 1), a Boolean (true or false) value, or a comparison of numerical values (e.g., a comparison with a predetermined value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched depending on the execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended as an illustrative example and does not have any limiting meaning on the present disclosure.

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Software, instructions, information, etc. may also be transmitted and received via a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave), then these wired and/or wireless technologies are included within the definition of a transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, radio resources may be indicated by an index.

The names used for the parameters described above are not limiting in any way. Furthermore, the formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure.

In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

A mobile station may be called a transmitting device, a receiving device, a communication device, etc. The mobile station may be a device mounted on a moving object, the moving object itself, etc. The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). The mobile station also includes devices that do not necessarily move during communication operations. For example, the mobile station may be an IoT (Internet of Things) device such as a sensor.

The terms "determining" and "determining" as used in this disclosure may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. "Determining" and "determining" may also include resolving, selecting, choosing, establishing, comparing, and the like. In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Also, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

The terms "connected" and "coupled", or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using designations such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are in the plural form.

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

1...MME, 2...UE, 3...P-GW, 4...PDN, 5...HSS, 6...DNS, 7...access destination determination system, 10...acquisition unit, 11...storage unit, 12...determination unit, 13...determination unit, 14...access unit.

Claims (8)

An access destination determination device that determines a network using a coexistence technology that enables communication in a network in which a plurality of network protocols coexist as an access destination of a mobile device that performs mobile communication, comprising:
an acquisition unit that acquires at least one of identification information for identifying the mobile device and correspondence information indicating the coexistence technology supported by the mobile device;
a determination unit that determines the coexistence technology supported by the mobile device based on at least one of the identification information and the correspondence information acquired by the acquisition unit;
a determination unit that determines the network using the coexistence technology determined by the determination unit as an access destination of the mobile station;
An access destination determination device comprising: The coexistence technology is a technology that enables communication in a network in which one network protocol and one or more other network protocols coexist,
the determination unit determines the network using the coexistence technology determined by the determination unit as an access destination to be accessed by the mobile device using the one network protocol.
2. The access destination determination device according to claim 1. The access destination determination device according to claim 1 or 2, wherein the coexistence technology is a technology that enables communication in a network in which at least IPv4 (Internet Protocol version 4) and IPv6 (Internet Protocol version 6) coexist. The access destination determination device according to claim 3, wherein the determination unit determines the network using the coexistence technology determined by the determination unit as the access destination to be accessed by the mobile device using the IPv6. The acquisition unit acquires at least the identification information,
the determination unit determines whether the mobile device supports a network protocol included in the plurality of network protocols based on the identification information acquired by the acquisition unit, and determines the coexistence technology supported by the mobile device when it is determined that the network protocol is supported.
5. The access destination determination device according to claim 1. The acquisition unit acquires at least the identification information,
The determination unit further determines whether or not the mobile device supports a network protocol included in the plurality of network protocols based on the identification information acquired by the acquisition unit;
when the determination unit determines that the coexistence technology is supported, the determination unit determines, as an access destination of the mobile station, the network using the coexistence technology determined by the determination unit.
5. The access destination determination device according to claim 1. The acquisition unit acquires the identification information and the correspondence information,
the determination unit calculates the coexistence technology supported by the mobile device based on the identification information acquired by the acquisition unit, and calculates the coexistence technology supported by the mobile device based on the correspondence information acquired by the acquisition unit, and determines the coexistence technology supported by the mobile device based on the two calculations.
7. The access destination determination device according to claim 1. The correspondence information is configurable by a user of the mobile device or an application of the mobile device.
8. The access destination determination device according to claim 1.

Images