COMMUNICATION DEVICE, COMMUNICATION DEVICE METHOD, TERMINAL DEVICE, AND TERMINAL DEVICE METHOD

Abstract

The objective of the present invention is to provide a communication device with which it is possible to prevent a sudden increase in traffic on a mobile communication network capable of providing a communication service when a disaster has occurred. A communication device (1) according to the present disclosure is provided with a transmitting unit (2) which transmits list information indicating a network available in the event of a disaster, if identification information of a terminal device is associated with a priority terminal, and does not transmit the list information if the identification information is not associated with a priority terminal.

Description

[Technical Field]

[0001] The present disclosure relates to a communication device, a communication device method, a terminal device, a terminal device method, a communication system, and a non-transitory computer-readable medium. [Background technology]

[0002] In the event of a disaster, when a failure occurs in a mobile communication network managed by a certain telecommunications carrier, a connection form is being considered that allows a communication terminal to connect to a mobile communication network managed by another telecommunications carrier instead of the mobile communication network where the failure occurred.

[0003] Non-Patent Document 1 discloses that a mobile communication network distributes PLMN list information including PLMNs (Public Land Mobile Networks) that can be used in the event of a disaster to a communication terminal. In the event of a disaster, the communication terminal can connect to a PLMN (a mobile communication network managed by another communication carrier) included in the PLMN list instead of the mobile communication network where the failure occurred, and can receive communication services.

[0004] Non-Patent Document 2 discloses the flow of registration processing for UE (User Equipment). The UE receives a Registration Accept message indicating completion of registration processing in a mobile communication network. The Registration Accept message includes PLMN list information including PLMNs (Public Land Mobile Networks) that can be used in the event of a disaster. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 23.501 V17.3.0 (2021-12) [Non-patent document 2] 3GPP TS 23.502 V17.3.0 (2021-12) Summary of the Invention [Problem to be solved by the invention]

[0006] However, when the communication systems disclosed in Non-Patent Documents 1 and 2 are used, in the event of a disaster, many communication terminals using the PLMN where the failure occurred will simultaneously attempt to connect to another PLMN, which will cause a problem of a sudden increase in traffic in the other PLMNs, resulting in congestion.

[0007] In view of the above-mentioned problems, one of the objectives of the present disclosure is to provide a communication device, a communication device method, a terminal device, a terminal device method, a communication system, and a non-transitory computer-readable medium that can prevent a sudden increase in traffic in a mobile communication network that can provide communication services when a disaster occurs. [Means for solving the problem]

[0008] The communication device according to the first aspect includes a transmitting unit that transmits list information indicating networks available for use in the event of a disaster when the identification information of the terminal device is associated with a priority terminal, and does not transmit the list information when the identification information is not associated with the priority terminal.

[0009] A communication device method according to a second aspect transmits list information indicating networks available for use in the event of a disaster when the identification information of a terminal device is associated with a priority terminal, and does not transmit the list information when the identification information is not associated with the priority terminal.

[0010] A terminal device according to a third aspect includes a receiving unit that receives list information indicating networks that can be used in the event of a disaster when the device's identification information is associated with a priority terminal, and a transmitting unit that transmits a registration request message to the network indicated in the list information in the event of a disaster.

[0011] A method of a terminal device according to a fourth aspect includes, when the identification information of the terminal device is associated with a priority terminal, receiving list information indicating networks that can be used in the event of a disaster, and, in the event of a disaster, transmitting a registration request message to the network indicated in the list information.

[0012] A communication system according to a fifth aspect includes a communication device that transmits list information indicating networks available for use in the event of a disaster when the identification information of the terminal device is associated with a priority terminal, and does not transmit the list information when the identification information is not associated with the priority terminal, and a terminal device that receives the list information indicating networks available for use in the event of a disaster when the identification information of the terminal device is associated with a priority terminal, and transmits a registration request message to the network indicated in the list information when a disaster occurs.

[0013] The program according to the sixth aspect transmits list information indicating networks available for use in the event of a disaster when the identification information of a terminal device is associated with a priority terminal, and does not transmit the list information when the identification information is not associated with the priority terminal. [Effects of the Invention]

[0014] The present disclosure provides a communication device, a communication device method, a terminal device, a terminal device method, a communication system, and a non-transitory computer-readable medium that can prevent a sudden increase in traffic in a mobile communication network that can provide communication services when a disaster occurs. [Brief explanation of the drawings]

[0015] [Figure 1A] FIG. 1 is a configuration diagram of a communication device according to a first embodiment. [Figure 1B] FIG. 2 is a configuration diagram of a terminal device according to the first embodiment. [Figure 2] FIG. 10 is a configuration diagram of a communication device according to a second embodiment. [Figure 3] 10 is a flowchart of a communication process according to the second embodiment. [Figure 4] FIG. 10 is a configuration diagram of a communication system according to a third embodiment. [Figure 5] FIG. 11 is a diagram showing the flow of registration processing according to the third embodiment. [Figure 6] FIG. 11 is a diagram showing the flow of registration processing according to a modification of the third embodiment. [Figure 7] FIG. 11 is a diagram showing the flow of registration processing according to a modification of the third embodiment. [Figure 8] FIG. 11 is a diagram showing the flow of registration processing according to a modification of the third embodiment. [Figure 9] 2A and 2B are configuration diagrams of a communication device and a terminal device according to respective embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0016] (Embodiment 1) Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. FIG. 1A shows a configuration example of a communication device 1 according to a first embodiment. The communication device 1 may be a computer device that operates when a processor executes a program stored in a memory. The communication device 1 has a transmission unit 2. The transmission unit 2 may be software or a module that performs processing when a processor executes a program stored in a memory. Alternatively, the transmission unit 2 may be hardware such as a circuit or a chip.

[0017] The transmitter 2 transmits list information indicating networks available for use in the event of a disaster when the identification information of the terminal device is associated with a priority terminal, and does not transmit the list information when the identification information is not associated with a priority terminal.

[0018] The identification information of the terminal device may be information that uniquely identifies the terminal device. Alternatively, the identification information of the terminal device may be information that uniquely identifies the user who uses the terminal device. The priority terminal may be a terminal device that requires priority use, such as for emergency services, medical services, fire services, police services, and the maintenance and management of lifelines (electricity, water, gas, public institutions).

[0019] Terminal devices connect to networks provided by telecommunications carriers and use communication services. However, if a disaster occurs and a failure occurs in the network provided by a telecommunications carrier, the terminal devices will be unable to connect to the network provided by that telecommunications carrier and will be unable to use the communication services. In such a case, the terminal devices can continue to use the communication services by connecting to another network instead of the failed network. In other words, the network available to the terminal devices in the event of a disaster is a network that can provide communication services to the terminal devices instead of the failed network. Furthermore, the network available to the terminal devices in the event of a disaster may be a network provided by a telecommunications carrier other than the one that provided the network the terminal devices were using before the disaster.

[0020] The list information includes identification information of at least one network different from the network to which the communication device 10 belongs.

[0021] Next, a configuration example of the terminal device 5 according to the first embodiment will be described with reference to FIG. 1B. The terminal device 5 may be a computer device that operates when a processor executes a program stored in a memory. The terminal device 5 has a receiving unit 6 and a transmitting unit 7. The receiving unit 6 and the transmitting unit 7 may be software or a module that performs processing when a processor executes a program stored in a memory. Alternatively, the receiving unit 6 and the transmitting unit 7 may be hardware such as a circuit or a chip.

[0022] When the identification information of the terminal device 5 is associated with the priority terminal, the receiving unit 6 receives list information indicating networks that can be used in the event of a disaster. For example, the receiving unit 6 receives the list information from the communication device 1.

[0023] When a disaster occurs, the transmitter 7 transmits a registration request message to the network indicated in the list information.

[0024] As described above, the communication device 1 according to the first embodiment transmits list information to terminal devices associated with a priority terminal. On the other hand, the communication device 1 according to the first embodiment does not transmit list information to terminal devices not associated with a priority terminal. As a result, when a disaster occurs, only terminal devices having list information transmit registration request messages to the network. Terminal devices that are not priority terminals can be prevented from connecting to a network that is available when a disaster occurs. As a result, the number of terminal devices that can connect to a network that is available when a disaster occurs can be limited. Sending registration request messages only by priority terminals can reduce the possibility of congestion (traffic concentration) compared to when list information is sent to all terminal devices and when a disaster occurs, all terminal devices having list information transmit registration request messages. (Embodiment 2) Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. FIG. 2 shows a configuration example of a communication device 10 according to a second embodiment. The communication device 10 corresponds to the communication device 1 in the first embodiment. The communication device 10 may be a computer device that operates when a processor executes a program stored in a memory. The communication device 10 may be a node device that constitutes a mobile communication network.

[0025] The communication device 10 has a management unit 11 and a communication unit 12. The communication unit 12 may be composed of a transmission unit and a reception unit. The management unit 11 and the communication unit 12 may be software or modules that are executed by a processor executing a program stored in a memory. Alternatively, the management unit 11 and the communication unit 12 may be hardware such as a circuit or a chip.

[0026] The management unit 11 manages list information indicating networks that can be used by terminal devices when a disaster occurs. Alternatively, the management unit 11 may store the list information as a storage unit. The terminal devices may be computer devices with communication functions, such as mobile terminals, wireless terminals, smartphone terminals, tablet terminals, IoT (Internet of Things) terminals, MTC (Machine Type Communication) terminals, and user terminals.

[0027] The list information managed by the management unit 11 includes identification information for at least one network different from the network to which the communication device 10 belongs. The management unit 11 may receive the list information via a network from another communication device that manages the list information. Alternatively, the management unit 11 may manage the list information input to the communication device 10 by an administrator of the communication device 10 or the like.

[0028] The communication unit 12 receives identification information of the terminal device. If the identification information is associated with a priority terminal, the communication unit 12 transmits list information to the terminal device. If the identification information indicates that the terminal device is not associated with a priority terminal, the communication unit 12 does not transmit the list information to the terminal device.

[0029] The identification information of the terminal device may be information that uniquely identifies the terminal device. Alternatively, the identification information of the terminal device may be information that uniquely identifies the user who uses the terminal device. The priority terminal may be a terminal device that can connect to a connectable network in the event of a disaster. In other words, the priority terminal may be a terminal device that can connect to a network included in the list information in the event of a disaster. The identification information of the terminal device that corresponds to the priority terminal may be managed in a database that manages the identification information of the terminal device that corresponds to the priority terminal. For example, the database may manage only the identification information of the terminal device that corresponds to the priority terminal, or the identification information of the terminal device that corresponds to the priority terminal may be managed separately from the identification information of the terminal device that does not correspond to the priority terminal.

[0030] The communication device 10 may manage the database, or another communication device may manage the database. When the communication device 10 manages the database, the management unit 11 may manage the database. When a communication device other than the communication device 10 manages the database, the communication device 10 may inquire of the other communication device whether or not the identification information received from the terminal device is associated with the priority terminal.

[0031] Not transmitting the list information to the terminal device may mean that the communication unit 12 transmits a message to the terminal device indicating that the list information is not set.

[0032] Next, a flowchart of the communication process according to the second embodiment will be described with reference to FIG. 3. First, the communication unit 12 receives identification information of the terminal device (S11). Next, if the identification information of the terminal device is associated with a priority terminal (S12), the communication unit 12 obtains list information from the management unit 11 and transmits the list information to the terminal device (S13). The list information includes information indicating at least one network that can be used by the terminal device in the event of a disaster. If the identification information of the terminal device is not associated with a priority terminal (S12), the communication unit 12 does not transmit the list information to the terminal device (S14).

[0033] As described above, the communication device transmits list information to terminal devices that are priority terminals, and does not transmit list information to terminal devices that are not priority terminals. This makes it possible to prevent terminal devices that are not priority terminals from connecting to a network different from the network they were connected to before the disaster, when a disaster occurs. By limiting the number of terminal devices that can be connected to a network that provides communication services instead of a network that has experienced a failure due to a disaster, it is possible to prevent a sudden increase in traffic on the network that provides communication services.

[0034] (Embodiment 3) Next, a configuration example of a communication system according to the third embodiment will be described with reference to Fig. 4. The communication system in Fig. 4 includes a 5th Generation Core network (5GC) 20, a gNode B (gNB) 30, a 5GC 40, and a gNB 50.

[0035] gNB30 and gNB50 correspond to base stations that support 5G, a wireless communication standard defined by 3GPP (3rd Generation Partnership Project). gNB30 forms a communication area 70. Also, while FIG. 4 shows that gNB50 also forms a communication area 70 like gNB30, the communication area formed by gNB50 may be an area that overlaps with part of the communication area 70. Alternatively, the communication area formed by gNB50 may be an area that includes the communication area 70. UE61 and UE62 are present within the communication area 70.

[0036] UE 61 and UE 62 correspond to the terminal devices in embodiment 1. UE is used as a general term for terminal devices in 3GPP. In addition, in embodiment 3 and onward, UE 61 will be described as a priority terminal, and UE 62 will be described as a general terminal different from the priority terminal.

[0037] Here, the communication system in Fig. 4 includes a communication system managed by two telecommunications carriers. For example, telecommunications carrier A may manage 5GC20 and gNB30, and telecommunications carrier B may manage 5GC40 and gNB50. The configuration of 5GC40 is substantially the same as the configuration of 5GC20, so a detailed description will be omitted. However, 5GC20 may have a different redundant configuration from 5GC40, and for example, the number of node devices constituting 5GC40 may be different from the number of node devices constituting 5GC20.

[0038] 4 shows an example in which gNB30 and gNB50 are different devices, gNB30 and gNB50 may be the same device. In other words, 5GC20 and 5GC40 may share one gNB.

[0039] The 5GC 20 includes an Access and Mobility management Function (AMF) entity 21, a Session Management Function (SMF) entity 22, an Authentication Server Function (AUSF) entity 23, an Equipment Identity Register (EIR) 24, a Unified Data Management (UDM) entity 25, and a Policy Control Function (PCF) entity 26. The AMF entity 21 will be referred to as the AMF 21 in the following description. The SMF entity 22 will be referred to as the SMF 22 in the following description. The AUSF entity 23 will be referred to as the AUSF 23 in the following description. The UDM entity 25 will be referred to as the UDM 25 in the following description. The PCF entity 26 will be referred to as the PCF 26 in the following description. The AMF, SMF, AUSF, EIR, and UDM are devices that make up the core network. The EIR, UDM, or AUSF is also referred to as a storage device, a server, or a management device. The storage device, server, or management device may be a computer device with communication capabilities. The entities may also be referred to as nodes or devices.

[0040] The AMF 21 performs mobility management for the UE 61 and the UE 62. Furthermore, the AMF 21 performs authentication processing for the UE 61 and the UE 62. The authentication processing for the UE may be, for example, authentication processing for a SIM (Subscriber Identity Module) mounted in the UE. The SMF 22 performs session management for the UE 61 and the UE 62. The AUSF 23 performs authentication processing for the UE 61 and the UE 62 together with the AMF 21.

[0041] The EIR 24 manages terminal numbers related to the UEs 61 and 62. The terminal numbers may be, for example, PEIs (Permanent Equipment Identifiers). The UDM 25 manages authentication certificate information used in authentication processing of the UEs 61 and 62. Furthermore, the UDM 25 manages subscriber information or user information related to the UEs 61 and 62. The PCF 26 performs policy control in the communication system provided by the communication carrier A.

[0042] Next, the flow of the registration process according to the third embodiment will be described with reference to Fig. 5. Note that the registration process shown in Fig. 5 is obtained by extracting the parts necessary for explaining the present disclosure from the registration procedure disclosed in Figure 4.2.2.2.2-1 of 3GPP TS 23.502 V17.3.0, and by adding processes related to the present disclosure.

[0043] First, UE 61 transmits a Registration Request message to AMF 21 via 5G-RAN (5G-Radio Access Network) (S21). 5G-RAN is an access network that supports the wireless communication standard 5G, and specifically includes a gNB 30 or a communication device not specified in 3GPP. In the description from FIG. 5 onwards, a gNB is used as a specific device that constitutes 5G-RAN. The Registration Request message includes a PEI, a PLMN (Public Land Mobile Network) ID, and parameters used for authentication. The PEI corresponds to identification information of a terminal device. The PLMN ID is an ID that identifies a communication network system. For example, the PLMN ID included in the Registration Request message may be an ID that indicates a communication network system provided by communication carrier A.

[0044] Next, the UE 61, the AMF 21, the AUSF 23, and the UDM 25 execute authentication processing for the UE 61 (S22). When the AMF 21, the AUSF 23, and the UDM 25 authenticate the UE 61, the AUSF 23 transmits security-related information to the AMF 21.

[0045] Next, the AMF 21 executes N5g-eir_EquipmentIdentityCheck_Get service processing, which is authentication processing related to the terminal device used as the UE 61, together with the EIR 24 (S23). The authentication processing related to the terminal device may be, for example, checking the PEI of the UE 61. The EIR 24 may manage a PEI indicating an unauthorized terminal. Furthermore, the EIR 24 may check whether the PEI of the UE 61 received from the AMF 21 is included in the PEI indicating an unauthorized terminal. Alternatively, when the EIR 24 manages a PEI that does not correspond to an unauthorized terminal, the EIR 24 may check whether the PEI of the UE 61 received from the AMF 21 is included in the PEI that does not correspond to an unauthorized terminal. Here, it is assumed that the EIR 24 transmits to the AMF 21 a check result that the terminal device used as the UE 61 does not correspond to an unauthorized terminal.

[0046] An unauthorized terminal may be, for example, a terminal device that is not permitted to use a network managed by a telecommunications carrier A.

[0047] Next, the AMF 21 transmits a message requesting a priority terminal number check to the EIR 24 (S24). The AMF 21 transmits a message including the PEI of the UE 61 to the EIR 24.

[0048] Next, the EIR 24 checks whether the PEI of the UE 61 corresponds to a priority terminal (S25). The EIR 24 manages the PEIs of priority terminals. The EIR 24 may manage a list of PEIs of priority terminals in a database, or may manage information in the database that distinguishes between PEIs of priority terminals and PEIs that do not correspond to priority terminals. For example, the EIR 24 may check whether the PEI of the UE 61 is included in the PEIs of priority terminals that are managed. In other words, the EIR 24 may check whether the PEI of the UE 61 matches the PEI of a priority terminal that is managed.

[0049] Next, EIR 24 transmits a response message including the check result to AMF 21 (S26). In step S26, EIR 24 transmits a response message including the check result indicating that UE 61 is a priority terminal to AMF 21. Note that, if UE 61 is not a priority terminal, EIR 24 may transmit a response message including the check result indicating that UE 61 is not a priority terminal to AMF 21.

[0050] Next, the AMF 21 registers with the UDM 25 by using Nudm_UECM_Registration (S27). Specifically, the AMF 21 notifies the UDM 25 that the UE 61 is present in the communication area of ​​the gNB 30 managed by the AMF 21 by using a message used in Nudm_UECM_Registration. In other words, the AMF 21 notifies the UDM 25 of information to be registered in the AMF 21 used by the UE 61.

[0051] Next, the AMF 21 acquires subscriber data related to the UE 61 from the UDM 25 using Nudm_SDM_Get (S28). The AMF 21 manages, in a management unit, list information indicating networks available to the UE 61 in the event of a disaster. The AMF 21 may also store the list information in a storage unit. The list information managed by the AMF 21 may be included in the subscriber data (subscriber information) acquired from the UDM. The list information includes at least one PLMN.

[0052] Next, AMF 21 checks whether the check result received in step S26 indicates that UE 61 is a priority terminal (S29). Here, since it is assumed that UE 61 is a priority terminal, AMF 21 transmits a Registration Accept message including list information to UE 61 via gNB 30 (S30). As a result, the registration process of UE 61 to AMF 21 is completed, and UE 61 holds the list information. Also, if it is determined in step S29 that the UE that transmitted the Registration Request message is not a priority terminal, AMF 21 transmits a Registration Accept message not including list information to the UE (S30).

[0053] If a disaster occurs after the completion of the Registration process and UE61 is no longer able to communicate via gNB30 and 5GC20, UE61 transmits a Registration Request message to a gNB other than gNB30, in which a PLMN included in the list information is set. For example, UE61 may transmit to gNB50 a Registration Request message in which a parameter indicating Disaster Roaming Registration is set as the Registration type and a PLMN that can be used during a disaster is set. UE61 may also transmit the Registration Request message by including information such as an indication or flag indicating that the identification information of its own device is associated with a priority terminal. 5GC40, which has received the Registration Request message via gNB50, may be provided with a mechanism for determining whether to register UE61 using the information set in the Registration Request message. At this time, a communication device (e.g., EIR, UDM, AMF, AUSF, etc.) in 5GC40 may check whether UE61 is associated with a priority terminal based on information such as the indication and flag transmitted from UE61, and determine whether to register. When the registration process in 5GC 40 is completed, UE 61 can communicate via gNB 50 and 5GC 40 instead of gNB 30 and 5GC 20. In other words, UE 61 can be provided with communication services by gNB 50 and 5GC 40.

[0054] As described above, the EIR 24 according to the third embodiment uses the terminal number of the UE 61 that has transmitted the Registration Request message to check whether the terminal device used as the UE 61 is a priority terminal. Furthermore, if the UE 61 is a priority terminal, the AMF 21 transmits to the UE 61 list information indicating networks that the terminal device can use when a disaster occurs, and does not transmit the list information to UEs that are not priority terminals. This makes it possible to limit the UEs that hold the list information compared to when the AMF 21 transmits the list information to all UEs that have permitted Registration. As a result, when a disaster occurs, it is possible to reduce the number of UEs that register with PLMNs included in the list information, thereby preventing congestion (traffic concentration) from occurring in the PLMNs included in the list information.

[0055] Furthermore, UDM25 may associate list information including information indicating a different network with each UE. In this case, UDM25 transmits list information associated with UE61 in step S28. In the registration process for a priority terminal different from UE61, UDM25 transmits list information different from the list information transmitted to UE61. The different list information is list information in which the networks included in the list information are different. As a result, in the event of a disaster, each UE corresponding to a priority terminal will be registered to a different network. As a result, it is possible to reduce the possibility of congestion occurring in the PLMN included in the list information compared to when the same list information is transmitted to multiple priority terminals.

[0056] (Modification of the third embodiment) Next, a modified example of the Registration process in Fig. 5 will be described using Fig. 6. In Fig. 5, an example in which EIR 24 checks whether UE 61 corresponds to a priority terminal or not has been described, but in Fig. 6, a process flow in which UDM 25 checks whether UE 61 corresponds to a priority terminal or not will be described. Steps S31 to S35 in Fig. 6 are the same as steps S21 to S23, S27, and S28 in Fig. 5, and therefore detailed description thereof will be omitted.

[0057] After the AMF 21 acquires the subscriber data related to the UE 61 from the UDM 25 in step S35, the AMF 21 transmits a message requesting a priority terminal number check to the UDM 25 (S36). The AMF 21 transmits a message including the terminal number of the UE 61 to the UDM 25. The terminal number may be a PEI.

[0058] Next, UDM25 checks whether the terminal number of UE61 corresponds to a priority terminal (S37). UDM25 manages the terminal numbers of priority terminals. UDM25 may manage the terminal numbers corresponding to priority terminals using a database similar to EIR24 in FIG. 5. UDM25 checks whether the terminal number of UE61 is included in the terminal numbers of priority terminals.

[0059] Next, the UDM 25 transmits a response message including the check result to the AMF 21 (S38). In step S38, the UDM 25 transmits to the AMF 21 a response message including the check result indicating that the UE 61 is a priority terminal.

[0060] Steps S39 and S40 are similar to steps S29 and S30 in FIG. 5, and therefore detailed description thereof will be omitted.

[0061] As shown in Figure 6, UDM25 checks whether UE61 is a priority terminal and sends the check result to AMF21, so that AMF21 can send list information only to priority terminals, similar to the processing in Figure 5.

[0062] Next, a modified example of the Registration process in Fig. 5 and Fig. 6 will be described with reference to Fig. 7. Fig. 5 describes an example in which EIR 24 checks whether UE 61 corresponds to a priority terminal. Furthermore, Fig. 6 describes an example in which UDM 25 checks whether UE 61 corresponds to a priority terminal. Fig. 7 describes an example in which AMF 21 checks whether UE 61 corresponds to a priority terminal.

[0063] Steps S41 to S45 in FIG. 7 are similar to steps S21 to S23, S27, and S28 in FIG. 5, and therefore detailed description thereof will be omitted.

[0064] In step S45, after AMF 21 acquires subscriber data related to UE 61 from UDM 25, AMF 21 transmits a message requesting a priority terminal number list to UDM 25 (S46). The priority terminal number list is information including terminal numbers of priority terminals, and includes, for example, at least one terminal number managed as a priority terminal.

[0065] Next, in response to the message received in step S46, UDM25 transmits a response message including a priority terminal number list to AMF21 (S47). Next, AMF21 checks whether the terminal number of UE61 corresponds to a priority terminal by using the priority terminal number list (S48). Here, since it is assumed that UE61 is a priority terminal, AMF21 transmits a Registration Accept message including list information to UE61 (S49). The list information that AMF21 includes in the Registration Accept message is the list information received from UDM25 in step S45, which indicates networks that can be used by terminal devices in the event of a disaster. As a result, the registration process of UE61 to AMF21 is completed, and UE61 holds the list information. Furthermore, if it is determined in step S48 that the UE that transmitted the Registration Request message is not a priority terminal, AMF21 transmits a Registration Accept message not including list information to the UE (S49).

[0066] As shown in Fig. 7, the AMF 21 acquires the priority terminal number list from the UDM 25 and checks whether the UE 61 corresponds to a priority terminal. As a result, the AMF 21 can transmit list information only to the priority terminal, similar to the processes in Figs. 5 and 6.

[0067] Next, a modified example of the Registration process of Fig. 5 to Fig. 7 will be described with reference to Fig. 8. Fig. 5 describes an example in which EIR 24 checks whether UE 61 corresponds to a priority terminal. Furthermore, Fig. 6 describes an example in which UDM 25 checks whether UE 61 corresponds to a priority terminal. Furthermore, Fig. 7 describes an example in which AMF 21 checks whether UE 61 corresponds to a priority terminal. Fig. 8 describes an example in which AUSF 23 checks whether UE 61 corresponds to a priority terminal.

[0068] 5, detailed description of steps S51 and S52 will be omitted. When the AMF 21, AUSF 23, and UDM 25 complete the authentication process for UE 61, the AMF 21 transmits a message to the AUSF 23 requesting a priority terminal number check (S53). The AMF 21 transmits a message including the terminal number of UE 61 to the AUSF 23.

[0069] Next, the AUSF 23 checks whether the terminal number of the UE 61 corresponds to a priority terminal (S54). The AUSF 23 manages the terminal numbers of priority terminals. The AUSF 23 may manage the terminal numbers corresponding to priority terminals using a database similar to the EIR 24 in FIG. 5. For example, the AUSF 23 checks whether the terminal number of the UE 61 is included in the terminal numbers of priority terminals.

[0070] Next, the AUSF 23 transmits a response message including the check result to the AMF 21 (S55). In step S55, the UDM 25 transmits to the AMF 21 a response message including the check result indicating that the UE 61 is a priority terminal.

[0071] Steps S56 to S60 are similar to steps S23 and S27 to S30 in FIG. 5, and therefore detailed description thereof will be omitted.

[0072] As shown in Figure 8, AUSF23 checks whether UE61 is a priority terminal and transmits the check result to AMF21, so that AMF21 can transmit list information only to priority terminals, similar to the processing in Figure 5.

[0073] 9 is a block diagram showing an example of the configuration of the communication device 10, the AMF 21 (hereinafter referred to as the communication device 10, etc.), and the terminal device described in the above-mentioned embodiment. Referring to FIG. 9, the communication device 10, etc., and the terminal device include a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 may be used to communicate with a network node. The network interface 1201 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series. IEEE stands for Institute of Electrical and Electronics Engineers.

[0074] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processes of the communication device 10 and the like described using flowcharts in the above-described embodiments. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0075] The memory 1203 is configured by a combination of volatile memory and non-volatile memory. The memory 1203 may include storage located remotely from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O (Input / Output) interface (not shown).

[0076] 9, the memory 1203 is used to store software modules. The processor 1202 reads and executes these software modules from the memory 1203, thereby performing the processing of the communication device 10 and the like described in the above-described embodiment.

[0077] As described using FIG. 9, each of the processors of the communication device 10, etc. in the above-described embodiments executes one or more programs including a group of instructions for causing a computer to perform the algorithm described using the drawings.

[0078] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0079] The present disclosure is not limited to the above-described embodiment, and various modifications can be made without departing from the spirit and scope of the present disclosure. Furthermore, the above-described embodiments may be used in combination.

[0080] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes. (Appendix 1) A communication device having a transmitting unit that transmits list information indicating networks that can be used in the event of a disaster when the identification information of a terminal device is associated with a priority terminal, and does not transmit the list information when the identification information is not associated with the priority terminal. (Appendix 2) 2. The communication device according to claim 1, wherein the transmitting unit transmits the list information to the terminal device via a base station. (Appendix 3) 3. The communication device according to claim 1, further comprising a receiving unit that receives the identification information from another device. (Appendix 4) 4. The communication device according to claim 1, further comprising a management unit that manages the list information. (Appendix 5) 5. The communication device according to claim 1, further comprising a storage unit that stores the list information. (Appendix 6) The communication device according to any one of Supplementary Notes 1 to 5, wherein the identification information is information that identifies the terminal device or information that identifies a user who uses the terminal device. (Appendix 7) The receiving unit receiving a registration request message including the identification information from the terminal device; The transmission unit A communication device as described in Appendix 3, wherein, when the identification information is associated with the priority terminal, a response message including the list information is sent to the terminal device in response to the registration request message, and when the identification information is not associated with the priority terminal, the communication device sends the response message not including the list information to the terminal device. (Appendix 8) The list information is 8. A communications device according to any one of claims 1 to 7, comprising at least one Public Land Mobile Network (PLMN). (Appendix 9) The transmission unit transmitting the identification information of the terminal device to a management device that manages the identification information of the priority terminal; The receiving unit 4. The communication device according to claim 3, further comprising: receiving, from the management device, a determination result as to whether or not identification information of the terminal device is managed as the priority terminal. (Appendix 10) The receiving unit receiving information indicating a list of identification information of the priority terminal from a management device that manages a list of identification information of the priority terminal; 4. The communication device according to claim 3, further comprising a determination unit that determines whether or not identification information of the terminal device is included in the list of identification information of priority terminals. (Appendix 11) The management device 11. The communications device of claim 9 or 10, which is an Equipment Identity Register (EIR), a Unified Data Management (UDM) entity, or an Authentication Server Function (AUSF) entity. (Appendix 12) The receiving unit A communication device as described in Supplementary Note 3, which receives a registration request message including the identification information from the terminal device, and receives subscriber information of the terminal device and the list information from a UDM entity that manages subscriber information of the terminal device. (Appendix 13) When the identification information of the terminal device is associated with a priority terminal, transmitting list information indicating networks available for use in the event of a disaster; A method for a communication device, wherein the list information is not transmitted if the identification information is not associated with the priority terminal. (Appendix 14) A method for a communication device as described in Supplementary Note 13, in which the list information is transmitted to the terminal device via a base station. (Appendix 15) 15. A method for a communication device according to claim 13 or 14, wherein the identification information is received from another device. (Appendix 16) A method for a communication device described in any one of Appendices 13 to 15, wherein the identification information is information that identifies the terminal device or information that identifies a user who uses the terminal device. (Appendix 17) a receiving unit that receives list information indicating networks that can be used when a disaster occurs when the identification information of the device itself is associated with a priority terminal; a transmitting unit that transmits a registration request message to the network indicated in the list information when a disaster occurs. (Appendix 18) the receiving unit receives the list information from a first base station; 18. The terminal device according to claim 17, wherein the transmission unit transmits the registration request message to a second base station different from the first base station. (Appendix 19) 19. The terminal device according to claim 17, wherein the identification information is information that identifies the terminal device or information that identifies a user who uses the terminal device. (Appendix 20) When the identification information of the own device is associated with a priority terminal, receiving list information indicating networks that can be used in the event of a disaster; A method for a terminal device, in the event of a disaster, transmitting a registration request message to a network indicated in the list information. (Appendix 21) receiving the list information from a first base station; A method of a terminal device described in Supplementary Note 20, wherein the registration request message is sent to a second base station different from the first base station. (Appendix 22) 22. The method for a terminal device according to claim 20 or 21, wherein the identification information is information that identifies the terminal device or information that identifies a user who uses the terminal device. (Appendix 23) a communication device that transmits list information indicating networks that can be used when a disaster occurs when identification information of a terminal device is associated with a priority terminal, and does not transmit the list information when the identification information of the terminal device is not associated with the priority terminal; A communication system comprising a terminal device that, when its own identification information is associated with a priority terminal, receives list information indicating networks available in the event of a disaster, and, when a disaster occurs, transmits a registration request message to the network indicated in the list information. (Appendix 24) The communication device 24. A communication system as described in claim 23, wherein the list information is transmitted to the terminal device via a base station. (Appendix 25) When the identification information of the terminal device is associated with a priority terminal, transmitting list information indicating networks available for use in the event of a disaster; A non-transitory computer-readable medium storing a program that causes a computer to execute the following: not transmitting the list information if the identification information is not associated with the priority terminal. [Explanation of symbols]

[0081] 1. Communications equipment 2. Transmitter 5 Terminal Devices 6. Receiving section 7. Transmitter 10. Communications equipment 11 Management Department 12 Communications Department 20 5GC 21 AMF 22 SMF 23 AUSF 24 EIR 25 UDM 26 PCF 30 gNB 40 5GC 50 gNB 61UE 62UE 70 communication areas

Claims

1. A communication device, receiving means for receiving a registration request message including identification information of the terminal device from the base station; a transmitting means for transmitting, to the terminal device via the base station, a registration accept message including list information indicating networks that are different from the network to which the communication device belongs and that can be used in the event of a disaster, when the identification information of the terminal device is associated with a priority terminal, and for transmitting, to the terminal device via the base station, a registration accept message that does not include the list information, when the identification information of the terminal device is not associated with the priority terminal.

2. The list information is The communication device of claim 1 , comprising at least one Public Land Mobile Network (PLMN).

3. A method for a communication device, comprising: receiving a registration request message from a base station, the registration request message including identification information of the terminal device; When the identification information of the terminal device is associated with a priority terminal, a registration accept message including list information indicating a network that is different from a network to which the communication device belongs and that can be used in the event of a disaster is transmitted to the terminal device via the base station; A method for a communication device, comprising: if the identification information is not associated with the priority terminal, transmitting a registration accept message not including the list information to the terminal device via the base station.

4. The method for a communication device according to claim 3 , wherein the identification information is information for identifying the terminal device or information for identifying a user who uses the terminal device.

5. A terminal device, a transmitting means for transmitting a first registration request message including identification information of the terminal device to a communication device in the network via a first base station; receiving means for receiving, when the identification information of the terminal device in the communication device is associated with a priority terminal, from the communication device via the first base station, a registration accept message including list information indicating a network that is different from the network and that can be used in the event of a disaster; When a disaster occurs, the transmitting means transmits a second registration request message including identification information of the terminal device to the different network indicated in the list information via a second base station different from the first base station.

6. The terminal device according to claim 5 , wherein the identification information is information for identifying the terminal device or information for identifying a user who uses the terminal device.

7. A method for a terminal device, comprising: transmitting a first registration request message including identification information of the terminal device to a communication device in the network via a first base station; When the identification information of the terminal device is associated with a priority terminal in the communication device, a registration accept message including list information indicating a network that is different from the network and that can be used in the event of a disaster is received from the communication device via the first base station; A method for a terminal device, in the event of a disaster, transmitting a second registration request message including identification information of the terminal device to the different network indicated in the list information via a second base station different from the first base station.

8. The method for a terminal device according to claim 7 , wherein the identification information is information for identifying the terminal device or information for identifying a user who uses the terminal device.

Images