Core network device, fault monitoring terminal, fault monitoring method and fault monitoring system

The core network device optimizes wireless communication availability by dynamically managing resource allocation for fault monitoring, ensuring resources are available for mobile terminals while maintaining effective failure detection.

JP7584722B2Active Publication Date: 2024-11-15MITSUBISHI ELECTRIC CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024552309
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-12-15
Publication Date
2024-11-15
Estimated Expiration
2042-12-15

AI Technical Summary

Technical Problem

Existing wireless communication systems face reduced availability due to increased downtime when monitoring terminals are installed within the communication area of a base station, as it allocates wireless resources to monitoring, thereby reducing resources available for mobile terminals.

Method used

A core network device that includes a communication status monitoring unit to monitor communication between a base station and a mobile terminal, stopping fault monitoring during data transmission and resuming it when no data is being transmitted, using a fault monitoring control unit to instruct the base station to allocate and reallocate resources.

Benefits of technology

This approach improves the availability of wireless communication systems by ensuring sufficient wireless resources are available for mobile terminals while still detecting communication failures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584722000001
    Figure 0007584722000001
  • Figure 0007584722000002
    Figure 0007584722000002
  • Figure 0007584722000003
    Figure 0007584722000003
Patent Text Reader

Abstract

A core network device (120) is characterized by comprising: a UPF (139) serving as a communication situation monitoring unit that monitors the communication situation between a base station and a mobile terminal; and an NWDAF (134) serving as a failure monitoring control unit that, on the basis of the communication situation, instructs the base station to stop and resume monitoring by a failure monitoring terminal, which is provided in a communication area of the base station and which monitors whether or not a wireless communication failure has occurred in the base station, such that monitoring by the failure monitoring terminal is stopped in a first period when data is transmitted between the base station and the mobile terminal, and monitoring by the failure monitoring terminal is performed in a second period when data is not transmitted between the base station and the mobile terminal.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a core network device, a fault monitoring terminal, a fault monitoring method, and a fault monitoring system that monitor wireless communication faults in a wireless communication system. [Background technology]

[0002] In a wireless communication system, a fault monitoring function is provided to achieve high availability. For example, Patent Document 1 discloses a method for monitoring wireless communication faults in a connected wireless network by a mobile terminal. The mobile terminal can provide an application with network status information used to control communication with the wireless network by having a diagnostic module receive a diagnostic message from a modem via a diagnostic interface and process the received diagnostic message. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5518957 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above conventional technology, since a fault can be detected only when a mobile terminal is present within the communication area of ​​a base station, in a use case where a mobile terminal is not present within the communication area for a long period of time, the communication interruption time may increase and the availability of the wireless communication system may decrease. For this reason, it is possible to install a monitoring terminal for fault monitoring within the communication area of ​​the base station and use this monitoring terminal to monitor wireless communication faults of the base station. However, simply installing the monitoring terminal causes wireless resources to be constantly assigned to the monitoring terminal, which makes it impossible to secure sufficient wireless resources for the mobile terminal, resulting in a problem that the availability of the wireless communication system may decrease.

[0005] The present disclosure has been made in consideration of the above, and aims to provide a core network device that can improve the availability of a wireless communication system. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objectives, the core network device disclosed herein is characterized by comprising a communication status monitoring unit that monitors the communication status between a base station and a mobile terminal, and a fault monitoring control unit that instructs the base station to stop and resume monitoring by the fault monitoring terminal, which is installed within the communication area of ​​the base station and monitors whether a wireless communication failure has occurred at the base station, during a first period when data is being transmitted between the base station and the mobile terminal, based on the communication status, and to perform monitoring by the fault monitoring terminal during a second period when data is not being transmitted between the base station and the mobile terminal. Effect of the Invention

[0007] The core network device according to the present disclosure has an effect of improving the availability of a wireless communication system. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing a configuration of a fault monitoring system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing a first example of a hardware configuration of the first core network device shown in FIG. 1; [Diagram 3] FIG. 2 is a diagram showing a second example of the hardware configuration of the first core network device shown in FIG. 1; [Figure 4] FIG. 2 is a diagram showing a first example of a hardware configuration of the second core network device shown in FIG. 1; [Diagram 5] FIG. 2 is a diagram showing a second example of the hardware configuration of the second core network device shown in FIG. 1; [Figure 6] FIG. 1 shows a functional configuration of a core network device. [Figure 7]FIG. 2 is a diagram showing a first example of a hardware configuration of the fault monitoring terminal shown in FIG. [Figure 8] FIG. 2 is a diagram showing a second example of the hardware configuration of the fault monitoring terminal shown in FIG. 1. [Figure 9] FIG. 1 is a diagram showing a first example of a functional configuration of a fault monitoring terminal. [Figure 10] FIG. 2 is a diagram showing a second example of a functional configuration of a fault monitoring terminal. [Figure 11] FIG. 1 is a first sequence diagram for explaining an operation of the fault monitoring system according to the first embodiment; [Figure 12] FIG. 2 is a second sequence diagram for explaining the operation of the fault monitoring system according to the first embodiment; [Figure 13] FIG. 1 illustrates an example of a lookup table used by a first core network device. [Figure 14] FIG. 1 is a diagram showing a configuration of a fault monitoring system according to a first modified example. [Figure 15] FIG. 13 is a diagram showing a configuration of a fault monitoring system according to a second modified example. [Figure 16] FIG. 11 is a sequence diagram for explaining the operation of the fault monitoring system according to the second embodiment. [Figure 17] FIG. 11 is a sequence diagram for explaining the operation of the fault monitoring system according to the third embodiment. [Figure 18] FIG. 13 is a sequence diagram for explaining the operation of the fault monitoring system according to the fourth embodiment. [Figure 19] FIG. 13 is a sequence diagram for explaining the operation of the fault monitoring system according to the fifth embodiment. [Figure 20] FIG. 13 is a diagram showing a configuration of a fault monitoring system according to a sixth embodiment. [Figure 21] FIG. 21 is a diagram showing a first example of a hardware configuration of the first core network device shown in FIG. 20. [Figure 22] FIG. 21 is a diagram showing a second example of the hardware configuration of the first core network device shown in FIG. 20. [Diagram 23] FIG. 21 is a diagram showing a first example of a hardware configuration of the second core network device shown in FIG. 20. [Figure 24]FIG. 21 is a diagram showing a second example of the hardware configuration of the second core network device shown in FIG. 20. [Diagram 25] FIG. 13 is a first sequence diagram for explaining an operation of the fault monitoring system according to the sixth embodiment; [Figure 26] FIG. 23 is a second sequence diagram for explaining the operation of the fault monitoring system according to the sixth embodiment; [Figure 27] FIG. 13 is a diagram showing a configuration of a fault monitoring system according to a third modified example. [Figure 28] FIG. 13 is a diagram showing a configuration of a fault monitoring system according to a fourth modified example. [Figure 29] FIG. 13 is a diagram showing a configuration of a fault monitoring system according to a fifth modified example. [Diagram 30] FIG. 13 is a sequence diagram for explaining the operation of the fault monitoring system according to the seventh embodiment. [Diagram 31] FIG. 13 is a sequence diagram for explaining the operation of the fault monitoring system according to the eighth embodiment. [Diagram 32] FIG. 13 is a sequence diagram for explaining the operation of the fault monitoring system according to the ninth embodiment. [Diagram 33] FIG. 23 is a sequence diagram for explaining the operation of the fault monitoring system according to the tenth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, a core network device, a fault monitoring terminal, a fault monitoring method, and a fault monitoring system according to embodiments of the present disclosure will be described in detail with reference to the drawings.

[0010] Embodiment 1 1 is a diagram showing a configuration of a fault monitoring system 1 according to a first embodiment. Here, a fault monitoring system 1 is described that monitors wireless communication faults occurring in a wireless communication system that is a local 5G system having an on-board terminal 420 that is a mobile terminal mounted on a train 400 and moves with the progress of the train 400, and a base station 240 installed in a station 200. The wireless communication system configured by the on-board terminal 420 and the base station 240 is used for ground-to-vehicle communication such as platform monitoring in the railway business, and is used for the purpose of complementing a private railway network.

[0011] Since base stations 240 are installed in a plurality of stations 200, in the following description, when distinguishing between stations 200, stations 200-1, 200-2, and so on are distinguished by adding a hyphen and a number after the reference symbol. When there is no need to distinguish between the plurality of stations 200, they are simply referred to as stations 200. Also, as in the case of station 200, when there is no need to distinguish between a plurality of components having similar functions, only the reference symbol attached to each component is written, and when there is no need to distinguish between a plurality of components having similar functions, a hyphen and a number is added after the reference symbol attached to each component to distinguish between the components.

[0012] The fault monitoring system 1 includes a first core network device 120A, a fault monitoring server 140, and a DN (Data Network) 160, which are installed in the common part 100. The fault monitoring system 1 also includes a second core network device 120B installed in each station 200, and a fault monitoring terminal 220 installed within the communication area of ​​a base station 240. Specifically, the second core network device 120B-1, the fault monitoring terminal 220-1, and the base station 240-1 are installed in the station 200-1. The second core network device 120B-2, the fault monitoring terminal 220-2, and the base station 240-2 are installed in the station 200-2.

[0013] The first core network device 120A and the fault monitoring server 140 communicate with each other via the Naf interface. The fault monitoring terminal 220-1 and the base station 240-1 communicate with each other via 5G wireless. The fault monitoring terminal 220-1 and the fault monitoring server 140 communicate with each other via an interface for the fault monitoring server. The base station 240-1 and the second core network device 120B-1 communicate with each other via the N3 interface. The base station 240-1 and the first core network device 120A communicate with each other via the N1 interface and the N2 interface. The second core network device 120B-1 and the first core network device 120A communicate with each other via the N4 interface. The second core network device 120B-1 and the fault monitoring server 140 communicate with each other via the N6 interface. The second core network device 120B-1 and the DN160 communicate with each other via the N6 interface.

[0014] The second core network device 120B-2, the fault monitoring terminal 220-2, and the base station 240-2 installed in the station 200-2 communicate within the station 200-2 and between the station 200-2 and the common part 100, similar to the devices installed in the station 200-1. Although not shown, the specific details are as follows. The fault monitoring terminal 220-2 and the base station 240-2 communicate by 5G wireless. The fault monitoring terminal 220-2 and the fault monitoring server 140 communicate by an interface for the fault monitoring server. The base station 240-2 and the second core network device 120B-2 communicate by an N3 interface. The base station 240-2 and the first core network device 120A communicate by an N1 interface and an N2 interface. The second core network device 120B-2 and the first core network device 120A communicate by an N4 interface. The second core network device 120B-2 and the fault monitoring server 140 communicate with each other via the N6 interface. The second core network device 120B-2 and the DN 160 communicate with each other via the N6 interface.

[0015] An on-board terminal 420 is installed on the train 400. When the on-board terminal 420 is present within the communication area of ​​each base station 240, it communicates with the base station 240 constituting the communication area in which it is present by 5G wireless. Note that, here, it is assumed that the train 400 is traveling in a direction from station 200-1 toward station 200-2. Also, although only one train 400 is shown in FIG. 1, it is assumed that each of the multiple trains 400 is equipped with an on-board terminal 420. Also, one train 400 may be equipped with multiple on-board terminals 420.

[0016] The fault monitoring system 1 has a function of monitoring a wireless communication fault in a wireless communication system having a base station 240 and an on-board terminal 420. When monitoring a wireless communication fault based on a wireless signal transmitted by the on-board terminal 420, if the on-board terminal 420 is not in the communication area of ​​the base station 240, the fault cannot be monitored. Therefore, the fault monitoring system 1 has a fault monitoring terminal 220 fixed in the communication area of ​​the base station 240. By using the fault monitoring terminal 220, it becomes possible to monitor a wireless communication fault even during a period when the on-board terminal 420 is not in the communication area. However, when the fault monitoring terminal 220 is constantly connected to the base station 240, the wireless resources of the base station 240 are assigned, so that there may be a case where the wireless resources of the on-board terminal 420 cannot be sufficiently secured. Therefore, in order to improve the availability of the wireless communication system, the fault monitoring system 1 has a function of reducing or releasing the wireless resources allocated to the fault monitoring terminal 220 installed within the communication area of ​​the base station 240 during a first period when the on-board terminal 420 is communicating with the base station 240, thereby stopping monitoring of wireless communication faults by the fault monitoring terminal 220, and reserving the wireless resources for the on-board terminal 420, and monitoring for wireless communication faults using the fault monitoring terminal 220 during a second period when the on-board terminal 420 is not communicating with the base station 240.

[0017] Fig. 2 is a diagram showing a first example of a hardware configuration of the first core network device 120A shown in Fig. 1. In the first example, the first core network device 120A has an N1 / N2 interface termination unit 121 which is a communication interface connected to the base station 240, a memory 122 which stores information used in the first core network device 120A, an N4 interface termination unit 123 which is a communication interface connected to the second core network device 120B, a CPU (Central Processing Unit) 124 which is a general-purpose processing circuit, a power supply circuit 125 which can supply power to each unit of the first core network device 120A, and a Naf interface termination unit 126 which is a communication interface connected to the fault monitoring server 140. The memory 122 may be, for example, a non-volatile or volatile semiconductor memory such as a Random Access Memory (RAM), a Read Only Memory (ROM), a flash memory, an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM (registered trademark)), a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a Digital Versatile Disk (DVD), etc.

[0018] Fig. 3 is a diagram showing a second example of the hardware configuration of the first core network device 120A shown in Fig. 1. In the second example, the first core network device 120A has an N1 / N2 interface termination unit 121, an N4 interface termination unit 123, a power circuit 125, a Naf interface termination unit 126, and a processing circuit 127. In the second example, the first core network device 120A has a processing circuit 127, which is a dedicated hardware, instead of the CPU 124 and memory 122 of the first example. The processing circuit 127 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination of these.

[0019] Fig. 4 is a diagram showing a first example of the hardware configuration of the second core network device 120B shown in Fig. 1. In the first example, the second core network device 120B has an N3 interface termination unit 261 which is a communication interface connected to the base station 240, a memory 262 which stores information used in the second core network device 120B, an N4 interface termination unit 263 which is a communication interface connected to the first core network device 120A, a CPU 264 which is a general-purpose processing circuit, a power supply circuit 265 which can supply power to each unit of the second core network device 120B, and an N6 interface termination unit 266 which is a communication interface connected to the fault monitoring server 140 and the DN160.

[0020] Fig. 5 is a diagram showing a second example of the hardware configuration of the second core network device 120B shown in Fig. 1. In the second example, the second core network device 120B has an N3 interface termination unit 261, an N4 interface termination unit 263, a power supply circuit 265, an N6 interface termination unit 266, and a processing circuit 267. In the second example, the second core network device 120B has the processing circuit 267, which is dedicated hardware, instead of the CPU 264 and memory 262 of the first example.

[0021] Fig. 6 is a diagram showing the functional configuration of core network device 120. The functions of core network device 120 are realized by a first core network device 120A and a second core network device 120B, which are multiple devices in terms of hardware, as shown in Fig. 1.

[0022] The core network device 120 includes an AUSF (Authentication Server Function) 131 that authenticates subscribers, a PCF (Policy Control Function) 132 that performs policy control, a UDM (Unified Data Management) 133 that holds subscriber-related information, a NWDAF (NetWork Data Analytics Function) 134 that performs network data analysis, an AMF (Access and Mobility management Function) 135 that performs mobility management, a SMF (Session Management Function) 136 that performs session management, a UDR (Unified Data Repository) 137 that registers subscriber-related information, an AF (Application Function) 138 that operates as an external application server, and a UPF (User Plane Function) 139 that forwards user data packets. Note that the NFs (Network Functions) shown here are merely examples, and the core network device 120 may be realized with fewer NFs than those shown in FIG. 6, or may be realized with more NFs than those shown in FIG. 6.

[0023] Of the NFs shown in Fig. 6, the NFs other than the UPF 139 are realized by the first core network device 120A, and the function of the UPF 139 is realized by the second core network device 120B. Note that the functions of the AUSF 131, the PCF 132, the UDM 133, the NWDAF 134, the AMF 135, the SMF 136, the UDR 137, and the AF 138 may be realized by the first core network device 120A shown in Fig. 2 using the CPU 124 and a program, or may be realized by the first core network device 120A shown in Fig. 3 using dedicated hardware. In the case of the first core network device 120A shown in Fig. 2, the functions of AUSF131, PCF132, UDM133, NWDAF134, AMF135, SMF136, UDR137 and AF138 can be realized by the CPU 124 reading and executing a program from the memory 122 storing the program describing the functions of AUSF131, PCF132, UDM133, NWDAF134, AMF135, SMF136, UDR137 and AF138. In the case of the first core network device 120A shown in Fig. 3, the functions of AUSF131, PCF132, UDM133, NWDAF134, AMF135, SMF136, UDR137 and AF138 are implemented as the processing circuit 127.

[0024] Note that some of the functions of AUSF 131, PCF 132, UDM 133, NWDAF 134, AMF 135, SMF 136, UDR 137, and AF 138 may be realized by dedicated circuits, and some of the functions may be realized by programs and the CPU 124.

[0025] The function of UPF139 may be realized by the second core network device 120B shown in FIG. 4 using the CPU264 and a program, or may be realized by the second core network device 120B shown in FIG. 5 using dedicated hardware. In the case of the second core network device 120B shown in FIG. 4, the function of UPF139 is described as a program and stored in the memory 262. The CPU264 can realize the function of UPF139 by reading and executing the program stored in the memory 262. In the case of the second core network device 120B shown in FIG. 5, the function of UPF139 is implemented as a processing circuit 267. Note that a part of the function of UPF139 may be realized by a dedicated circuit, and a part may be realized by the program and CPU264. The program executed by CPU124 and CPU264 may be provided in a state stored in a storage medium, or may be provided via a communication path such as the Internet.

[0026] Fig. 7 is a diagram showing a first example of a hardware configuration of the fault monitoring terminal 220 shown in Fig. 1. In the first example, the fault monitoring terminal 220 has a communication module 221 which is a wireless communication interface with the base station 240, a memory 222 which stores information used in the fault monitoring terminal 220, a CPU 223 which is a general-purpose processing circuit, a power supply circuit 224 which can supply power to each part of the fault monitoring terminal 220, and a fault monitoring server interface termination unit 225 which is a communication interface connected to the fault monitoring server 140.

[0027] Fig. 8 is a diagram showing a second example of the hardware configuration of the fault monitoring terminal 220 shown in Fig. 1. In the second example, the fault monitoring terminal 220 has a communication module 221, a power supply circuit 224, a fault monitoring server interface termination unit 225, and a processing circuit 226. In the second example, the fault monitoring terminal 220 has the processing circuit 226, which is dedicated hardware, instead of the memory 222 and CPU 223 in the first example.

[0028] 9 is a diagram showing a first example of the functional configuration of the fault monitoring terminal 220. The fault monitoring terminal 220 has a wireless transceiver 231 that performs a transmission and reception procedure of 5G wireless, a control unit 232 that controls 5G wireless, a fault monitoring server transceiver 233 that performs a transmission and reception procedure when transmitting a wireless communication failure determination result to the fault monitoring server 140, and a fault monitoring unit 234 that monitors and determines a wireless communication failure.

[0029] The functions of the wireless transmission / reception unit 231, the control unit 232, the transmission / reception unit for the fault monitoring server 233, and the fault monitoring unit 234 may be realized by the fault monitoring terminal 220 shown in FIG. 7 using the CPU 223 and a program, or may be realized by the fault monitoring terminal 220 shown in FIG. 8 using dedicated hardware. In the case of the fault monitoring terminal 220 shown in FIG. 7, the functions of the wireless transmission / reception unit 231, the control unit 232, the transmission / reception unit for the fault monitoring server 233, and the fault monitoring unit 234 are written as a program and stored in the memory 222. The CPU 223 can realize the functions of the wireless transmission / reception unit 231, the control unit 232, the transmission / reception unit for the fault monitoring server 233, and the fault monitoring unit 234 by reading and executing the program stored in the memory 222. In the case of the fault monitoring terminal 220 shown in FIG. 8, the functions of the wireless transmission / reception unit 231, the control unit 232, the transmission / reception unit for the fault monitoring server 233, and the fault monitoring unit 234 are implemented as a processing circuit 226. Note that some of the functions of the wireless transmission / reception unit 231, the control unit 232, the transmission / reception unit for fault monitoring server 233, and the fault monitoring unit 234 may be realized by dedicated circuits, and some may be realized by programs and the CPU 223. The programs executed by the CPU 223 may be provided in a state stored in a storage medium, or may be provided via a communication path such as the Internet.

[0030] 10 is a diagram showing a second example of the functional configuration of the fault monitoring terminal 220. In the second example, the functions of the fault monitoring terminal 220 are realized by being divided into two devices, a first fault monitoring terminal 220A and a second fault monitoring terminal 220B. The first fault monitoring terminal 220A has a wireless transmission / reception unit 231 and a control unit 232. The second fault monitoring terminal 220B has a terminal connection unit 235 which is an interface connecting to the first fault monitoring terminal 220A, a fault monitoring server transmission / reception unit 233, and a fault monitoring unit 234. In addition, while FIG. 10 shows one first fault monitoring terminal 220A and one second fault monitoring terminal 220B, the first fault monitoring terminal 220A needs to be installed within the communication area of ​​the base station 240, whereas the installation location of the second fault monitoring terminal 220B does not have to be within the communication area of ​​the base station 240. Therefore, a configuration may be used in which one second fault monitoring terminal 220B is provided for each of a plurality of first fault monitoring terminals 220A installed at each base station 240.

[0031] FIG. 11 is a first sequence diagram for explaining the operation of the fault monitoring system 1 according to the first embodiment. FIG. 12 is a second sequence diagram for explaining the operation of the fault monitoring system 1 according to the first embodiment. The operation shown in FIG. 12 is executed following the operation shown in FIG. 11. At the start of the operation shown in FIG. 11, the train 400 is moving in the traveling direction shown in FIG. 1 and is before arriving at the station 200-1. The train 400 has not arrived at the station 200-2, and the fault monitoring terminal 220-2 is to monitor a wireless communication fault. First, the fault monitoring terminal 220-2 establishes an RRC (Radio Resource Control) connection between the fault monitoring terminal 220-2 and the base station 240-2 (step S001). The fault monitoring terminal 220-2 establishes a PDU session with the second core network device 120B-2 via the AMF 135 and SMF 136 by performing a PDU (Packet Data Unit) session establishment procedure in the C-Plane (Control Plane) via the base station 240-2 (step S002).

[0032] The fault monitoring terminal 220-2 transmits fault monitoring data to the fault monitoring server 140 in the U-Plane (User Plane) via the base station 240-2 and the second core network device 120B-2 (step S003). At this time, when the fault monitoring terminal 220-2 detects at least one of a decrease in radio wave intensity, an RRC connection failure, a decrease in packet arrival rate, and a decrease in throughput, it performs fault detection to detect these events as wireless communication faults (step S004). When the fault monitoring terminal 220-2 detects a wireless communication fault, it notifies the fault by transmitting a wireless communication fault determination result to the fault monitoring server 140 operating as the AF 138 via the interface termination unit 225 for the fault monitoring server (step S005).

[0033] Here, the train 400 arrives at the station 200-1 (step S006). Since the on-board terminal 420 enters the communication area of ​​the base station 240-1, radio resources are allocated between the on-board terminal 420 and the base station 240-1, and an RRC connection is established (step S007). The on-board terminal 420 establishes a PDU session with the second core network device 120B-1 via the AMF 135 and SMF 136 by performing a PDU session establishment procedure in the C-Plane via the base station 240-1 (step S008).

[0034] The on-board terminal 420 transmits data to the DN 160 in the U-Plane via the base station 240-1 and the second core network device 120B-1 (step S009). The train 400 departs from the station 200-1 (step S010). When the train 400 advances and the on-board terminal 420 leaves the communication area of ​​the base station 240-1, the second core network device 120B-1 detects that data transmission between the on-board terminal 420 and the base station 240-1 has stopped (step S011). The second core network device 120B-1 monitors the data transmission status for each GTP (GPRS Tunneling Protocol) tunneling ID (IDentification). For example, when the second core network device 120B-1 detects that a state in which no data transmission has been performed from either the on-board terminal 420 or the base station 240-1 continues for a predetermined time, it can detect this as a stop of data transmission. The second core network device 120B-1 notifies the SMF 136 that it has detected a data transmission stop at the N4 interface through the N4 interface termination unit 263 based on the URR (Usage Reporting Rule) (step S012). The SMF 136 transfers the notification from the UPF 139 of the second core network device 120B-1 (step S013).

[0035] When the NWDAF 134 receives the notification from the UPF 139 via the SMF 136, it selects a base station 240 for which wireless communication fault monitoring is to be stopped based on the received notification (step S014). At this time, the NWDAF 134 holds the reference table shown in Fig. 13 and can select the base station 240 for which wireless communication fault monitoring is to be stopped according to the reference table.

[0036] FIG. 13 is a diagram showing an example of a reference table used by the first core network device 120A. The reference table associates information for identifying the second core network device 120B, which is the "notification source" that transmits the notification that data transmission stop has been detected, the base station 240, which is the "subject to stop wireless communication fault monitoring", and the base station 240, which is the "subject to resume wireless communication fault monitoring". Here, the installation positions of the base station 240 and the fault monitoring terminal 220, and the traveling direction of the train 400 are predetermined. In addition, the notification is transmitted when the "data transmission stop" is detected in the second core network device 120B, which is the source. Therefore, the base station 240 installed in the station 200 where the train 400 is scheduled to arrive next after the station 200 where the second core network device 120B, which is the "notification source", is installed becomes the "subject to stop wireless communication fault monitoring", and the base station 240 installed in the station 200 where the second core network device 120B, which is the "notification source", is installed becomes the "subject to resume wireless communication fault monitoring". Specifically, when the "notification sender" is the second core network device 120B-1, the "subject to stop wireless communication fault monitoring" is the "base station 240-2" and the "subject to resume wireless communication fault monitoring" is the "base station 240-1." Also, when the "notification sender" is the second core network device 120B-2, the "subject to stop wireless communication fault monitoring" is the "base station 240-3" and the "subject to resume wireless communication fault monitoring" is the "base station 240-2." Although not shown, the base station 240-3 is installed at station 200-3 where the train 400 is scheduled to arrive next after station 200-2.

[0037] Return to the description of FIG. 11. In step S014, since the "notification transmission source" is the second core network device 120B-1, the "base station 240-2" is selected as the "subject of wireless communication fault monitoring to be stopped." The NWDAF 134 outputs a wireless resource release instruction to the AMF 135 to instruct the "base station 240-2" selected as the "subject of wireless communication fault monitoring to be stopped" to release the wireless resource of the fault monitoring terminal 220-1 (step S015). The AMF 135 transmits a wireless resource release request to the base station 240-2 (step S016), and the base station 240-2 releases the wireless resource that was allocated to the fault monitoring terminal 220-2 (step S017). Note that, here, as a method of stopping monitoring of wireless communication faults, the wireless resource that was allocated to the fault monitoring terminal 220 is released, but the wireless resource that is allocated to the fault monitoring terminal 220 may be reduced, or the traffic of the fault monitoring data transmitted by the fault monitoring terminal 220 may be reduced. The fault monitoring terminal 220-2 is controlled so as not to spontaneously reconnect the wireless connection after the wireless resources are released (step S018).

[0038] 12. Based on the notification received from the SMF 136 in step S013, the NWDAF 134 selects a target for restarting wireless communication fault monitoring (step S019). At this time, a reference table such as that shown in FIG. 13 is used. In step S019, the "notification source" is the second core network device 120B-1, so the "base station 240-1" is selected as the "target for restarting wireless communication fault monitoring". The NWDAF 134 instructs the AMF 135 to page the base station 240-1 that is the target for restarting wireless communication fault monitoring (step S020). The AMF 135 pages the base station 240-1 (step S021), and the base station 240-1 pages the fault monitoring terminal 220-1 (step S022). As a result, wireless resources are reallocated to the fault monitoring terminal 220-1.

[0039] Here, wireless communication fault monitoring is resumed by reallocating wireless resources through paging, but wireless communication fault monitoring may be resumed by increasing the allocation of wireless resources or by increasing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal 220-1.

[0040] After the wireless resources are reallocated, the fault monitoring terminal 220-1 resumes fault monitoring (step S023) and transmits fault monitoring data (step S024). When the wireless connection between the fault monitoring terminal 220-1 and the base station 240-1 is cut off, the AMF 135 detects the fault (step S025), and the AMF 135 notifies the fault monitoring server 140 of the fault by transmitting the result of the wireless communication fault determination through the Naf interface (step S026).

[0041] When train 400 arrives at station 200-2 (step S027), an RRC connection is established between the on-board terminal 420 and the base station 240-2 (step S028) in a similar procedure to steps S007 to S009, a PDU session is established between the on-board terminal 420 and the second core network device 120B-2 (step S029), and data transmission is performed between the on-board terminal 420, the base station 240-2, the second core network device 120B-2, and DN 160 (step S030).

[0042] When the train 400 departs from the station 200-2 (step S031) and the on-board terminal 420 leaves the communication area of ​​the base station 240-2, data transmission stops. After this, the same procedures as those from step S011 onwards are repeatedly performed.

[0043] Here, we have described a fault monitoring system 1 configured in such a manner that one base station 240, one second core network device 120B, and one fault monitoring terminal 220 are installed in one station 200, as shown in FIG. 1, but the system configuration is not limited to the example shown in FIG. 1.

[0044] FIG. 14 is a diagram showing a configuration of a fault monitoring system 1A according to a first modified example. In the fault monitoring system 1A, a plurality of base stations 240 are installed in one station 200, and one second core network device 120B is installed for each base station 240. In this case, in order to distinguish each of the plurality of base stations 240-1 installed in the station 200-1, a hyphen and a number are added after the common code "240-1" to distinguish each of the base stations 240. Four base stations 240-1-1 to 240-1-4 are installed in the station 200-1. Each base station 240 may be provided for each platform, or multiple base stations 240 may be provided in the same platform, such as the base station 240-1-3 and the base station 240-1-4. Four second core network devices 120B-1-1 to 120B-1-4 are provided corresponding to the base stations 240-1-1 to 240-1-4, respectively. Base stations 240-2-1 to 240-2-4 and second core network devices 120B-2-1 to 120B-2-4 are installed in station 200-2.

[0045] FIG. 15 is a diagram showing a configuration of a fault monitoring system 1B according to a second modified example. In the fault monitoring system 1B, a plurality of base stations 240 are installed in one station 200, and one second core network device 120B is installed for the plurality of base stations 240. In the example of FIG. 15, four base stations 240-1-1 to 240-1-4 and two second core network devices 120B-1-1 and 120B-1-2 are installed in the station 200-1. The second core network device 120B-1-1 is connected to the base station 240-1-1 and the base station 240-1-2, and the second core network device 120B-1-2 is connected to the base station 240-1-3 and the base station 240-1-4.

[0046] Furthermore, eight base stations 240-2-1 to 240-2-8 and a second core network device 120B-2-1 are installed in station 200-2. Second core network device 120B-2-1 is connected to each of base stations 240-2-1 to 240-2-8.

[0047] Eight base stations 240-3-1 to 240-3-8 are installed in station 200-3, eight base stations 240-4-1 to 240-4-8 are installed in station 200-4, and eight base stations 240-5-1 to 240-5-8 are installed in station 200-5. Also, a second core network device 120B-4 is installed, which is connected to each of the 24 base stations 240-3-1 to 240-3-8, 240-4-1 to 240-4-8, and 240-5-1 to 240-5-8. The location where the second core network device 120B-4 is installed is not particularly limited.

[0048] As shown in Fig. 14 and Fig. 15, the second core network device 120B may be installed one for one base station 240, or one for multiple base stations 240. The installation range of multiple base stations 240 connected to one second core network device 120B is not limited, and may be for each platform of a station 200, for each station 200, or for multiple stations 200. These installation methods may be mixed. Although omitted in Fig. 14 and Fig. 15, one or more fault monitoring terminals 220 are installed for one base station 240, and are installed within the communication area of ​​the corresponding base station 240.

[0049] As described above, according to embodiment 1, the core network device 120 comprises the UPF 139 of the second core network device 120B which is a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420 which is a mobile terminal, and the NWDAF 134 of the first core network device 120A which is a fault monitoring control unit that instructs the base station 240 to stop and resume monitoring by the fault monitoring terminal 220, which is installed within the communication area of ​​the base station 240 and monitors whether a wireless communication failure has occurred in the base station 240, during a first period when data is being transmitted between the base station 240 and the on-board terminal 420, based on the communication status, and to perform monitoring by the fault monitoring terminal 220 during a second period when data is not being transmitted between the base station 240 and the on-board terminal 420. As a result, during a first period when the base station 240 is transmitting data to the on-board terminal 420, the monitoring by the fault monitoring terminal 220 is stopped, and during a second period when the base station 240 is not transmitting data to the on-board terminal 420, the monitoring by the fault monitoring terminal 220 is performed. Therefore, during the first period, it is possible to secure sufficient wireless resources for the on-board terminal 420, and even during a second period when the base station 240 cannot communicate with the on-board terminal 420, the fault monitoring terminal 220 can detect a wireless communication failure of the base station 240. Therefore, it is possible to improve the availability of the wireless communication system constituted by the base station 240 and the on-board terminal 420.

[0050] When the communication status monitoring unit UPF139 satisfies the notification criterion that "UPF139 of the second core network device 120B detects that data transmission from the base station 240 to the fault monitoring terminal 220 has stopped for more than a predetermined period of time," it outputs a notification to the fault monitoring control unit NWDAF134.

[0051] Here, the base station 240 monitors the communication status for each GTP tunneling ID, which is a tunneling identifier for identifying a tunneled communication path for communicating with the on-board terminal 420. The base station 240 also stops monitoring by the fault monitoring terminal 220 by releasing the radio resources of the fault monitoring terminal 220, reducing the allocation of radio resources to the fault monitoring terminal 220, or reducing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal 220. The base station 240 also resumes monitoring by the fault monitoring terminal 220 by reallocating radio resources to the fault monitoring terminal 220, increasing the radio resources allocated to the fault monitoring terminal 220, or increasing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal 220.

[0052] In addition, the core network device 120 further includes an AMF 135, which is a terminal management unit that detects a wireless connection break between the base station 240 and the fault monitoring terminal 220 based on the fault monitoring data transmitted by the fault monitoring terminal 220 and transmits the detection result to the fault monitoring server 140.

[0053] According to the first embodiment, the fault monitoring terminal 220 includes a wireless transmission / reception unit 231 that transmits and receives wireless signals to and from the base station 240, a control unit 232 that controls not to spontaneously reconnect after disconnecting the wireless connection with the base station 240, a fault monitoring unit 234 that transmits and receives fault monitoring data to and from the base station 240 to monitor whether or not a wireless communication failure has occurred in the base station 240, and a fault monitoring server transmission / reception unit 233 that notifies the fault monitoring server 140 of the determination result of the occurrence or absence of a wireless communication failure. The fault monitoring unit 234 detects at least one of a decrease in radio wave intensity, an RCC connection failure, a decrease in packet arrival rate, and a decrease in throughput as a wireless communication failure.

[0054] Embodiment 2 In the above-mentioned embodiment 1, the notification criterion of the notification used by the NWDAF 134 to select the target for stopping and restarting the wireless communication fault monitoring is "detection in the UPF 139 of the second core network device 120B that the data transmission from the base station 240 to the fault monitoring terminal 220 has been stopped for a predetermined time or more". In the embodiment 2, this notification criterion is "detection in the AMF 135 of the first core network device 120A that the wireless disconnection state between the base station 240 and the on-board terminal 420 has continued for a predetermined time or more". The AMF 135 can determine whether the notification criterion is satisfied by using, for example, a timer. Note that, in the following, the system configuration in the embodiment 2 is the same as the configuration of the fault monitoring system 1 shown in FIG. 1, and the configuration of each device of the fault monitoring system 1 is also the same as that in the embodiment 1.

[0055] FIG. 16 is a sequence diagram for explaining the operation of the fault monitoring system 1 according to the second embodiment. Although omitted in FIG. 16, the operation from step S001 to step S010 is the same as that of the first embodiment described in FIG. 11. When the train 400 departs from the station 200-1 in step S010 and the on-board terminal 420 leaves the communication area of ​​the base station 240-1, data transmission stops. At this time, the AMF 135 monitors the data transmission status between the base station 240-1 and the on-board terminal 420, and detects that a wireless disconnection state has continued for a predetermined time or more between the base station 240-1 and the on-board terminal 420 (step S101). The AMF 135 outputs a notification to the NWDAF 134 through the Naf interface (step S102). The NWDAF 134 selects a target for which wireless communication fault monitoring is to be stopped based on the notification from the AMF 135 (step S014). Although omitted in FIG. 16, the operations from step S014 onwards are the same as those of embodiment 1 described in FIG. 11 and FIG. 12, except that when selecting a target for resuming wireless communication fault monitoring in step S019, the determination is made based on the notification output in step S102.

[0056] As described above, according to embodiment 2, the core network device 120 can realize a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420, which is a mobile terminal, by the AMF 135 of the first core network device 120A.

[0057] When the AMF 135, which is a communication status monitoring unit, satisfies the notification criterion that "AMF 135 of the first core network device 120A detects that the wireless disconnection state between the base station 240 and the on-board terminal 420 has continued for a predetermined time or longer," it outputs a notification to the NWDAF 134, which is a fault monitoring control unit. According to the second embodiment, it is possible to achieve the same effects as those of the first embodiment.

[0058] Embodiment 3 In the above-mentioned embodiment 1, the notification criterion of the notification used by the NWDAF 134 to select the target for stopping and restarting the wireless communication fault monitoring is "detection in the UPF 139 of the second core network device 120B that the data transmission from the base station 240 to the fault monitoring terminal 220 has been stopped for a predetermined time or more". In the embodiment 2, this notification criterion is "detection in the AMF 135 of the first core network device 120A that the wireless disconnection state between the base station 240 and the on-board terminal 420 has continued for a predetermined time or more". In the embodiment 3, the notification criterion is "reception of a packet from the on-board terminal 420 in the UPF 139 of the second core network device 120B". In the following, the system configuration in the embodiment 3 is the same as the configuration of the fault monitoring system 1 shown in FIG. 1, and the configuration of each device of the fault monitoring system 1 is also the same as that in the embodiment 1.

[0059] Fig. 17 is a sequence diagram for explaining the operation of the fault monitoring system 1 according to the third embodiment. Although omitted in Fig. 17, the operation from step S001 to step S010 is the same as that of the first embodiment described in Fig. 11. After step S010, the same operation as that from step S027 to step S030 of the first embodiment described in Fig. 12 is performed. When the on-board terminal 420 starts data transmission with the DN160 via the base station 240-2 and the second core network device 120B-2, the second core network device 120B-2 monitors the data transmission status for each GTP tunneling ID, and detects that a packet from the on-board terminal 420 has been received, thereby detecting that data transmission has started between the on-board terminal 420 and the base station 240-2 (step S201).

[0060] Based on the URR, the second core network device 120B-2 outputs a notification to the SMF 136 via the N4 interface termination unit 263 via the N4 interface (step S202). The SMF 136 transfers the notification from the second core network device 120B-2 to the NWDAF 134 (step S013). The NWDAF 134 selects a target for which wireless communication fault monitoring is to be stopped based on the notification from the second core network device 120B-2 received from the SMF 136 (step S014). Although omitted in FIG. 17, from step S014 onwards, the operations of steps S015 to S026 shown in FIG. 11 and FIG. 12 and the operation of step S031 following step S026 are performed. At this time, when selecting a target for which wireless communication fault monitoring is to be resumed in step S019, it is the same as in the first embodiment described in FIG. 11, except that the determination is based on the notification output by the second core network device 120B-2 in step S202.

[0061] As described above, according to embodiment 3, the core network device 120 can realize a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420, which is a mobile terminal, by the UPF 139 of the second core network device 120B.

[0062] When the UPF 139, which is a communication status monitoring unit, satisfies the notification criterion that "the UPF 139 of the second core network device 120B has received a packet from the on-board terminal 420", it outputs a notification to the NWDAF 134, which is a fault monitoring control unit. According to the third embodiment, it is possible to achieve the same effects as those of the first embodiment.

[0063] Embodiment 4 In the above-mentioned embodiment 1, the notification criterion of the notification used by the NWDAF 134 to select the target of the stop and restart of the wireless communication fault monitoring is "detection in the UPF 139 of the second core network device 120B that the data transmission from the base station 240 to the fault monitoring terminal 220 has been stopped for a predetermined time or more". In the embodiment 2, this notification criterion is "detection in the AMF 135 of the first core network device 120A that the wireless disconnection state between the base station 240 and the on-board terminal 420 has continued for a predetermined time or more". In the embodiment 3, the notification criterion is "reception of a packet from the on-board terminal 420 in the UPF 139 of the second core network device 120B". In the embodiment 4, the notification criterion is "allocation of wireless resources to the on-board terminal 420 by the base station 240 in the AMF 135 of the first core network device 120A". In the following, it is assumed that the system configuration in the fourth embodiment is the same as the configuration of the fault monitoring system 1 shown in FIG.

[0064] FIG. 18 is a sequence diagram for explaining the operation of the fault monitoring system 1 according to the fourth embodiment. Although omitted in FIG. 18, the operations from step S001 to step S010 are the same as those of the first embodiment described in FIG. 11. After step S010, the same operations as those of steps S027 and S028 of the first embodiment described in FIG. 12 are performed. At this time, the AMF 135 monitors the wireless resource allocation status of the base station 240-2 and detects the wireless resource allocation to the on-board terminal 420 by the base station 240-2 (step S301). The AMF 135 outputs a notification to the NWDAF 134 via the Naf interface (step S102). The NWDAF 134 selects a target for which wireless communication fault monitoring is to be stopped based on the notification from the AMF 135 (step S014). Although omitted in Fig. 18, after step S014, the operations of steps S015 to S026 shown in Fig. 11 and the operations of steps S029 to S031 following step S026 are performed. Note that, at this time, when selecting a target for restarting wireless communication fault monitoring in step S019, the selection is made based on the notification output by the AMF 135 in step S102, and is the same as in the first embodiment described in Fig. 11.

[0065] As described above, according to embodiment 4, the core network device 120 can realize a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420, which is a mobile terminal, by the AMF 135 of the first core network device 120A.

[0066] When the AMF 135, which is a communication status monitoring unit, satisfies the notification criterion that "in the AMF 135 of the first core network device 120A, the base station 240 has assigned radio resources to the on-board terminal 420", it outputs a notification to the NWDAF 134, which is a fault monitoring control unit. According to the fourth embodiment, it is possible to achieve the same effects as those of the first embodiment.

[0067] Embodiment 5. In the above-mentioned embodiment 1, the notification criterion of the notification used by the NWDAF 134 to select the target for stopping and restarting the wireless communication fault monitoring is "detection in the UPF 139 of the second core network device 120B that the data transmission from the base station 240 to the fault monitoring terminal 220 has been stopped for a predetermined time or more". In the embodiment 2, this notification criterion is "detection in the AMF 135 of the first core network device 120A that the wireless disconnection state between the base station 240 and the on-board terminal 420 has continued for a predetermined time or more". In the embodiment 3, the notification criterion is "reception of a packet from the on-board terminal 420 in the UPF 139 of the second core network device 120B". In the embodiment 4, the notification criterion is "allocation of wireless resources to the on-board terminal 420 by the base station 240 in the AMF 135 of the first core network device 120A". In the fifth embodiment, the notification criterion is "detection in the AMF 135 of the first core network device 120A that the base station 240 has started the C-Plane procedure with the on-board terminal 420." Note that in the following, the system configuration in the fifth embodiment is the same as the configuration of the fault monitoring system 1 shown in Fig. 1, and the configurations of the devices in the fault monitoring system 1 are also the same as those in the first embodiment.

[0068] FIG. 19 is a sequence diagram for explaining the operation of the fault monitoring system 1 according to the fifth embodiment. Although omitted in FIG. 19, the operations from step S001 to step S010 are the same as those of the first embodiment described in FIG. 11. After step S010, the operations from step S027 to step S29 of the first embodiment described in FIG. 11 are performed. At this time, the AMF 135 detects the start of the C-Plane procedure by the on-board terminal 420 and the base station 240-2 (step S401). The AMF 135 outputs a notification to the NWDAF 134 through the Naf interface (step S102). The NWDAF 134 selects a target for which wireless communication fault monitoring is to be stopped based on the notification from the AMF 135 (step S014). Although omitted in FIG. 19, after step S014, the operations from step S015 to step S026 shown in FIG. 11 and the operations from step S029 to step S031 following step S026 are performed. At this time, when selecting the target for restarting wireless communication fault monitoring in step S019, the process is the same as in embodiment 1 described in FIG. 11, except that the determination is based on the notification output by AMF 135 in step S102.

[0069] As described above, according to embodiment 5, the core network device 120 can realize a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420, which is a mobile terminal, by the AMF 135 of the first core network device 120A.

[0070] When the AMF 135, which is a communication status monitoring unit, satisfies the notification criterion that "AMF 135 of the first core network device 120A detects that the base station 240 has started the C-Plane procedure with the on-board terminal 420," it outputs a notification to the NWDAF 134, which is a fault monitoring control unit. According to the fifth embodiment, it is possible to achieve the same effects as those of the first embodiment.

[0071] Embodiment 6 FIG. 20 is a diagram showing a configuration of a fault monitoring system 1C according to the sixth embodiment. In the fault monitoring system 1 according to the first embodiment, the function of the core network device 120 shown in FIG. 6 is realized by dividing it into a first core network device 120A having a function other than UPF and a second core network device 120B having a function of UPF. In contrast, in the fault monitoring system 1C according to the sixth embodiment, the function of the core network device 120 shown in FIG. 6 is realized by dividing it into a first core network device 120C having a function other than UPF and SMF and a second core network device 120D having a function of UPF and SMF. The first core network device 120C is installed in the common part 100, and the second core network device 120D is installed in the station 200. Hereinafter, the parts different from the first embodiment will be mainly described, and the description of the matters common to the first embodiment will be omitted.

[0072] The fault monitoring system 1C has a first core network device 120C instead of the first core network device 120A of the fault monitoring system 1, and has a second core network device 120D instead of the second core network device 120B. Accordingly, the first core network device 120C and the second core network device 120D communicate with each other via an SBI (Service Based Interface). Also, the fault monitoring server 140 and the second core network device 120D communicate with each other via a Naf interface or an N6 interface.

[0073] Fig. 21 is a diagram showing a first example of a hardware configuration of the first core network device 120C shown in Fig. 20. The first core network device 120C has an SBI interface termination unit 128 which is a communication interface connected to the second core network device 120D, instead of the N4 interface termination unit 123 of the first core network device 120A shown in Fig. 2.

[0074] Fig. 22 is a diagram showing a second example of the hardware configuration of the first core network device 120C shown in Fig. 20. The first core network device 120C has an SBI interface termination unit 128 which is a communication interface connected to the second core network device 120D, instead of the N4 interface termination unit 123 of the first core network device 120A shown in Fig. 3. In the second example shown in Fig. 22, the first core network device 120C has a processing circuit 127 which is dedicated hardware, instead of the CPU 124 and memory 122 of the first example shown in Fig. 21.

[0075] Fig. 23 is a diagram showing a first example of a hardware configuration of the second core network device 120D shown in Fig. 20. The second core network device 120D has an SBI interface termination unit 268 which is a communication interface connected to the first core network device 120C, and a Naf interface termination unit 269 which is a communication interface connected to the fault monitoring server 140, instead of the N4 interface termination unit 263 of the second core network device 120B shown in Fig. 4.

[0076] Fig. 24 is a diagram showing a second example of the hardware configuration of the second core network device shown in Fig. 20. The second core network device 120D has an SBI interface termination unit 268 which is a communication interface connected to the first core network device 120C, and a Naf interface termination unit 269 which is a communication interface connected to the fault monitoring server 140, instead of the N4 interface termination unit 263 of the second core network device 120B shown in Fig. 5. In the second example shown in Fig. 24, the second core network device 120D has a processing circuit 267 which is dedicated hardware, instead of the CPU 264 and memory 262 of the first example shown in Fig. 23.

[0077] In the sixth embodiment, the functional configuration of the core network device 120 is the same as that shown in FIG. 6, the hardware configuration of the fault monitoring terminal 220 is the same as that of the example described using FIG. 7 and FIG. 8, and the functional configuration of the fault monitoring terminal 220 is the same as that of the example described using FIG. 9 and FIG. 10.

[0078] FIG. 25 is a first sequence diagram for explaining the operation of the fault monitoring system 1C according to the sixth embodiment. FIG. 26 is a second sequence diagram for explaining the operation of the fault monitoring system according to the sixth embodiment. The operation shown in FIG. 26 is executed following the operation shown in FIG. 25. Note that FIGS. 25 and 26 show an example in which the operation shown in FIGS. 11 and 12 is performed in the fault monitoring system 1C shown in FIG. 20. Below, the parts different from FIGS. 11 and 12 will be mainly explained, and the explanation of the parts similar to the first embodiment will be omitted.

[0079] The operations from step S501 to step S518 shown in Fig. 25 are the same as the operations from step S001 to step S018 shown in Fig. 11, except that the SMF 136 is provided in the second core network devices 120D-1 and 120D-2. Specific differences will be described below. In step S502, the fault monitoring terminal 220-2 establishes a PDU session with the second core network device 120D-2 via the AMF 135 of the first core network device 120C by performing a PDU session establishment procedure in the C-Plane via the base station 240-2. In addition, in step S508, the on-board terminal 420 establishes a PDU session with the second core network device 120D-1 via the AMF of the first core network device 120C by performing a PDU session establishment procedure in the C-Plane. Moreover, since the SMF 136 is provided in the second core network device 120D, in step S512, a notification is sent from the UPF 139 in the second core network device 120D-1 to the SMF 136. Moreover, in step S513, the notification is transferred from the SMF 136 of the second core network device 120D-1 to the NWDAF 134 of the first core network device 120C using the Naf interface.

[0080] The operations from step S519 to step S531 shown in Figure 26 are the same as those from step S019 to step S031 shown in Figure 12, except that the SMF 136 is provided in the second core network devices 120D-1, 120D-2. Specific differences are explained below. In step S529, the on-board terminal 420 establishes a PDU session with the second core network device 120D-2 via the AMF of the first core network device 120C by performing a PDU session establishment procedure in the C-Plane.

[0081] Fig. 27 is a diagram showing the configuration of a fault monitoring system 1D according to a third modified example. The third modified example has second core network devices 120D-1-1 to 120D-1-4 instead of the second core network devices 120B-1-1 to 120B-1-4 of the first modified example shown in Fig. 14, and has second core network devices 120D-2-1 to 120D-2-4 instead of the second core network devices 120B-2-1 to 120B-2-4.

[0082] Fig. 28 is a diagram showing a configuration of a fault monitoring system 1E according to a fourth modified example. The fourth modified example has second core network devices 120D-1-1 to 120D-1-2, 120D-2-1, and 120D-4 instead of the second core network devices 120B-1-1 to 120B-1-2, 120B-2-1, and 120B-4 of the second modified example shown in Fig. 15. In the fault monitoring system 1E according to the fourth modified example, a plurality of base stations 240 are installed in one station 200, and one second core network device 120D is installed for the plurality of base stations 240, as in the second modified example.

[0083] In the above, the second core network device 120D has the functions of UPF and SMF, but the device having the UPF function and the device having the SMF function may be physically separated. Fig. 29 is a diagram showing the configuration of a fault monitoring system 1F according to a fifth modified example. In the fifth modified example, one second core network device 120B having the UPF function is installed for one base station 240, and one second core network device 120E having the SMF function is installed for multiple second core network devices 120B.

[0084] As described above, in the sixth embodiment, the functions of the core network device 120 as shown in FIG. 6 can be realized by dividing them into the second core network device 120D having the functions of UPF and SMF and the first core network device 120C having functions other than UPF and SMF. In the fault monitoring system 1C according to the sixth embodiment, as in the first embodiment, the fault monitoring terminal 220 stops monitoring during the first period when the base station 240 transmits data to the on-board terminal 420, and the fault monitoring terminal 220 performs monitoring during the second period when the base station 240 does not transmit data to the on-board terminal 420. Therefore, in the first period, it is possible to secure sufficient wireless resources for the on-board terminal 420, and even in the second period when the base station 240 cannot communicate with the on-board terminal 420, the fault monitoring terminal 220 can detect a wireless communication fault of the base station 240. Therefore, it is possible to improve the availability of the wireless communication system configured by the base station 240 and the on-board terminal 420.

[0085] Embodiment 7 In the above-mentioned sixth embodiment, the notification criterion of the notification used by the NWDAF 134 to select the target for stopping and restarting the wireless communication fault monitoring is "detection in the UPF 139 of the second core network device 120D that the data transmission from the base station 240 to the fault monitoring terminal 220 has been stopped for a predetermined time or more". In the seventh embodiment, the notification criterion is "detection in the AMF 135 of the first core network device 120C that the wireless disconnection state between the base station 240 and the on-board terminal 420 has continued for a predetermined time or more", as in the second embodiment. The AMF 135 can determine whether the notification criterion is satisfied by using, for example, a timer. In the following, the system configuration in the seventh embodiment is the same as the configuration of the fault monitoring system 1C shown in FIG. 20, and the configuration of each device of the fault monitoring system 1C is also the same as that in the sixth embodiment.

[0086] Fig. 30 is a sequence diagram for explaining the operation of the fault monitoring system 1C according to the seventh embodiment. Here, the operation shown in Fig. 30 is the same as the operation of the second embodiment shown in Fig. 16, except that the subject of the operation is the first core network device 120C instead of the first core network device 120A, and the second core network device 120D instead of the second core network device 120B. The operations of steps S509, S510, S601, S602, and S514 shown in Fig. 30 are the same as the operations of steps S009, S010, S101, S102, and S014 shown in Fig. 16.

[0087] As described above, according to embodiment 7, a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420, which is a mobile terminal, can be realized by the AMF 135 of the first core network device 120C.

[0088] Embodiment 8 In the eighth embodiment, the notification criterion for the notification used by the NWDAF 134 to select the target for suspending and resuming wireless communication fault monitoring is "the UPF 139 of the second core network device 120D has received a packet from the on-board terminal 420." Note that in the following, the system configuration in the eighth embodiment is the same as the configuration of the fault monitoring system 1C shown in Fig. 20, and the configurations of the devices in the fault monitoring system 1C are also the same as those in the sixth embodiment.

[0089] FIG. 31 is a sequence diagram for explaining the operation of the fault monitoring system 1C according to the eighth embodiment. Here, the operation shown in FIG. 31 is the same as the operation of the third embodiment shown in FIG. 17, except that the subject of the operation is the first core network device 120C instead of the first core network device 120A, and the second core network device 120D instead of the second core network device 120B. The operations of steps S510, S527 to S530, S701, S702, S513, and S514 shown in FIG. 31 are the same as the operations of steps S010, S027 to S030, S201, S202, S013, and S014 shown in FIG. 17. Moreover, the operations of steps S510, S527 to S530, S513, and S514 shown in FIG. 31 are the same as the operations described in the sixth embodiment using the same reference numerals. Hereinafter, the differences from the third embodiment will be mainly described.

[0090] In step S702, since the SMF 136 of the notification destination is provided in the second core network device 120D-2, the UPF 139 of the second core network device 120D-2 outputs the notification to the SMF 136 of the second core network device 120D-2 based on the URR. In addition, in step S513, the notification is transferred from the SMF 136 of the second core network device 120D-2 to the NWDAF 134 of the first core network device 120C using the Naf interface.

[0091] As described above, according to embodiment 8, a communication status monitoring unit that monitors the communication status between base station 240 and on-board terminal 420, which is a mobile terminal, can be realized by UPF 139 of second core network device 120D.

[0092] Embodiment 9 In the ninth embodiment, the notification criterion for the notification used by the NWDAF 134 to select a target for suspending and resuming wireless communication fault monitoring is "that the base station 240 has allocated wireless resources to the on-board terminal 420 in the AMF 135 of the first core network device 120C." Note that in the following, the system configuration in the ninth embodiment is the same as the configuration of the fault monitoring system 1C shown in Fig. 20, and the configurations of the devices in the fault monitoring system 1C are also the same as those in the sixth embodiment.

[0093] Fig. 32 is a sequence diagram for explaining the operation of the fault monitoring system 1C according to the ninth embodiment. Here, the operation shown in Fig. 32 is the same as the operation of the fourth embodiment shown in Fig. 18, except that the subject of the operation is the first core network device 120C instead of the first core network device 120A, and the second core network device 120D instead of the second core network device 120B. The operations of steps S510, S527, S528, S801, S802, and S514 shown in Fig. 32 are the same as the operations of S010, S027, S028, S301, S102, and S014 shown in Fig. 18.

[0094] As described above, according to embodiment 9, a communication status monitoring unit that monitors the communication status between base station 240 and on-board terminal 420, which is a mobile terminal, can be realized by AMF 135 of first core network device 120C.

[0095] Embodiment 10 In the tenth embodiment, the notification criterion for the notification used by the NWDAF 134 to select a target for stopping and resuming wireless communication fault monitoring is "detection in the AMF 135 of the first core network device 120C that the base station 240 has started the C-Plane procedure with the on-board terminal 420." Note that in the following, the system configuration in the tenth embodiment is the same as the configuration of the fault monitoring system 1C shown in Fig. 20, and the configuration of each device of the fault monitoring system 1C is also the same as that in the sixth embodiment.

[0096] Fig. 33 is a sequence diagram for explaining the operation of the fault monitoring system 1C according to the tenth embodiment. Here, the operation shown in Fig. 33 is the same as the operation of the sixth embodiment shown in Fig. 19, except that the subject of the operation is the first core network device 120C instead of the first core network device 120A, and the second core network device 120D instead of the second core network device 120B. The operations of steps S510, S527 to S529, S901, S902, and S514 shown in Fig. 33 are the same as the operations of S010, S027 to S029, S401, S102, and S014 shown in Fig. 19.

[0097] As described above, according to embodiment 10, a communication status monitoring unit that monitors the communication status between the base station 240 and the on-board terminal 420, which is a mobile terminal, can be realized by the AMF 135 of the first core network device 120C.

[0098] The configurations shown in the above embodiments are merely examples, and may be combined with other known technologies, or the embodiments may be combined with each other. Also, parts of the configurations may be omitted or modified without departing from the spirit of the invention.

[0099] For example, in the above, the fault monitoring systems 1, 1A, 1B, 1C, 1D, 1E, and 1F for monitoring wireless communication faults in a wireless communication system configured with an on-board terminal 420 mounted on a train 400 and a base station 240 installed in a station 200 have been described, but the scope of application of the technology of the present disclosure is not limited to such an example. The mobile terminal is not limited to the on-board terminal 420 mounted on the train 400, but may be a mobile terminal. In addition, the base station 240 is not limited to one installed in the station 200. However, it is effective to apply the present disclosure to a wireless communication system in which communication areas configured by each of the multiple base stations 240 are linearly connected, a mobile terminal travels within the communication area along a predetermined route, and communicates with each base station 240 when it enters the communication area of ​​the base station 240, and a second period during which the mobile terminal does not transmit data to the base station 240 is longer than a first period during which the mobile terminal transmits data. For example, the fault monitoring systems 1, 1A, 1B, 1C, 1D, 1E, and 1F disclosed herein can also be applied to a wireless communication system consisting of a base station 240 installed on a highway or along a bus route and a mobile terminal mounted in a vehicle. [Explanation of symbols]

[0100] 1, 1A, 1B, 1C, 1D, 1E, 1F Fault monitoring system, 100 Common unit, 120 Core network device, 120A, 120C First core network device, 120B, 120B-1, 120B-2, 120B-1-1 to 120B-1-4, 120B-2-1 to 120B-2-4, 120B-4, 120D, 120D-1, 120D-2, 120D-1-1 to 120D-1-4, 120D-2-1 to 120D-2-4, 120D-4 Second core network device, 121 N1 / N2 interface termination unit, 122, 222, 262 Memory, 123, 263 N4 interface termination unit, 124, 223, 264 CPU, 125, 224, 265 Power supply circuit, 126, 269 Naf interface termination unit, 127, 226, 267 Processing circuit, 128, 268 SBI interface termination unit, 131 AUSF, 132 PCF, 133 UDM, 134 NWDAF, 135 AMF, 136 SMF, 137 UDR, 138 AF, 139 UPF, 140 Fault monitoring server, 160 DN, 200, 200-1 to 200-5 Station, 220, 220-1, 220-2 Fault monitoring terminal, 220A First fault monitoring terminal, 220B Second fault monitoring terminal, 221 Communication module, 225 Fault monitoring server interface termination unit, 231 Wireless transmission / reception unit, 232 Control unit, 233 Fault monitoring server transmission / reception unit, 234 Fault monitoring unit, 235 Terminal connection unit, 240, 240-1, 240-2, 240-1-1 to 240-1-4, 240-2-1 to 240-2-8, 240-3-1 to 240-3-8, 240-4-1 to 240-4-8, 240-5-1 to 240-5-8 base stations, 261 N3 interface termination unit, 266 N6 interface termination unit, 400 train, 420 on-board terminal.

Claims

1. a communication status monitoring unit that monitors a communication status between a base station and a mobile terminal; a fault monitoring control unit that instructs the base station to stop and resume monitoring by a fault monitoring terminal that is installed within the communication area of ​​the base station and monitors whether or not a wireless communication fault has occurred at the base station during a first period when data is being transmitted between the base station and the mobile terminal based on the communication status, and to perform monitoring by the fault monitoring terminal during a second period when data is not being transmitted between the base station and the mobile terminal; A core network device comprising:

2. The base station transmits data to the mobile terminal through a tunneled communication path; 2. The core network device according to claim 1, wherein the communication status monitoring unit monitors the communication status for each tunneling identifier of the communication path.

3. The core network device according to claim 1, characterized in that the communication status monitoring unit outputs a notification to the fault monitoring control unit when it detects that data transmission from the base station has stopped for a predetermined period of time, when the base station and the mobile terminal have continued to be in a wireless disconnected state for a predetermined period of time, when it receives a packet from the mobile terminal, when the base station has assigned wireless resources to the mobile terminal, or when it detects that the base station has started a control plane procedure with the mobile terminal.

4. The core network device according to claim 1, characterized in that the base station stops monitoring by the fault monitoring terminal by releasing radio resources of the fault monitoring terminal, reducing the allocation of radio resources to the fault monitoring terminal, or reducing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal.

5. The core network device according to claim 1, characterized in that the base station resumes monitoring by the fault monitoring terminal by reallocating radio resources to the fault monitoring terminal by paging, increasing the radio resources allocated to the fault monitoring terminal, or increasing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal.

6. a terminal management unit that detects a wireless connection interruption between the base station and the fault monitoring terminal based on the fault monitoring data transmitted by the fault monitoring terminal and transmits the detection result to a fault monitoring server; The core network device according to claim 1 , further comprising:

7. a wireless transceiver unit for transmitting and receiving wireless signals to and from a base station; a fault monitoring unit that transmits and receives fault monitoring data between the base station and the fault monitoring unit to monitor whether or not a wireless communication fault has occurred in the base station; a fault monitoring server transceiver unit for notifying a fault monitoring server of a result of the determination of whether or not a wireless communication fault has occurred; a control unit that controls the wireless transceiver unit in accordance with an instruction to stop monitoring by the fault monitoring unit during a first period when data is being transmitted between the base station and the mobile terminal, and to cause the fault monitoring unit to perform monitoring during a second period when data is not being transmitted between the base station and the mobile terminal, and controls the wireless transceiver unit not to spontaneously reconnect after a wireless connection with the base station is disconnected; A fault monitoring terminal comprising:

8. 8. The fault monitoring terminal according to claim 7, wherein the fault monitoring unit detects at least one of a decrease in radio wave intensity, a radio resource control connection fault, a decrease in packet arrival rate, and a decrease in throughput as the wireless communication fault.

9. A core network device monitors a communication status between a base station and a mobile terminal, and before data transmission between the base station and the mobile terminal is started, stops monitoring of wireless communication failures by a failure monitoring terminal installed within a communication area of ​​the base station; a step of causing the core network device to resume monitoring of wireless communication failures by the failure monitoring terminal, which had stopped monitoring, after the communication between the mobile terminal and the base station is terminated; When the fault monitoring terminal detects a wireless communication fault, the fault monitoring terminal notifies the fault monitoring server; Including, A fault monitoring method, characterized in that the fault monitoring terminal controls the terminal so as not to spontaneously reconnect the terminal to the base station after the radio connection with the base station is cut off.

10. The base station transmits data to the mobile terminal through a tunneled communication path; 10. The fault monitoring method according to claim 9, wherein the monitoring of the communication status is performed for each tunneling identifier of the communication path.

11. The fault monitoring method according to claim 9, further comprising: monitoring the communication status; and when it is detected that data transmission from the base station has stopped for a predetermined period of time; when the base station and the mobile terminal have continued in a wireless disconnected state for a predetermined period of time; when a packet has been received from the mobile terminal; when the base station has assigned wireless resources to the mobile terminal; or when it is detected that the base station has started a control plane procedure with the mobile terminal, outputting a notification and determining the timing for stopping and resuming monitoring by the fault monitoring terminal based on the notification.

12. The fault monitoring method according to claim 9, characterized in that monitoring by the fault monitoring terminal is stopped by releasing wireless resources of the fault monitoring terminal, reducing the allocation of wireless resources of the fault monitoring terminal, or reducing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal.

13. The fault monitoring method according to claim 9, characterized in that monitoring by the fault monitoring terminal is resumed by reallocating radio resources to the fault monitoring terminal, increasing the radio resources allocated to the fault monitoring terminal, or increasing the traffic of fault monitoring data transmitted and received by the fault monitoring terminal.

14. In the core network device, detecting a wireless connection interruption between the base station and the fault monitoring terminal based on fault monitoring data transmitted by the fault monitoring terminal, and transmitting a detection result to a fault monitoring server; The fault monitoring method according to claim 9, further comprising:

15. 10. The fault monitoring method according to claim 9, wherein the fault monitoring terminal detects at least one of a decrease in radio wave intensity, a radio resource control connection failure, a decrease in packet arrival rate, and a decrease in throughput as the wireless communication fault.

16. A fault monitoring system for monitoring a wireless communication fault in a wireless communication system having a base station and a mobile terminal that wirelessly communicates with the base station, comprising: a fault monitoring terminal installed within the communication area of ​​the base station; A core network device; Equipped with The core network device includes: a communication status monitoring unit that monitors a communication status between a base station and a mobile terminal; a fault monitoring control unit that instructs the base station to stop and resume monitoring by a fault monitoring terminal that is installed within the communication area of ​​the base station and monitors whether or not a wireless communication fault has occurred in the base station during a first period when data is being transmitted between the base station and the mobile terminal based on the communication status, and to perform monitoring by the fault monitoring terminal during a second period when data is not being transmitted between the base station and the mobile terminal; A fault monitoring system comprising:

Citation Information

Patent Citations

  • Dew point measuring device

    JP1980018957A

  • Radio base station device, radio system, and failure detection method

    JP2015133672A

  • Wireless communication system and redundant base station

    JP2017073645A

  • Satellite communication device, management device, monitoring system, and monitoring method

    WO2016203553A1