JP7507566B2 - Wireless communication unit - Google Patents

Description

This invention relates to a wireless communication unit in which the functions of a base station device and a core network (EPC) are integrated into a portable housing, and which is capable of performing wireless network communication with a mobile terminal in accordance with a communication protocol stack defined by 3GPP (Third Generation Partnership Project).

In wireless communication networks based on high-speed communication standards based on 3GPP specifications (for example, LTE (Long Term Evolution) or WiMAX (Worldwide Interoperability for Microwave Access)), it is essential to construct an EPC (Evolved Packet Core) that accommodates a wireless communication access network within the area, and wireless base stations to which mobile terminals connect are controlled for sending and receiving IP packets via the EPC. On the other hand, with the spread of mobile terminals such as mobile phones, smartphones, and tablet PCs, there is an increasing demand to use mobile terminals in areas where the infrastructure of EPCs and wireless base stations is not in place, such as at sea, in depopulated areas, or in areas where communication functions have been lost due to disasters, etc. (hereinafter referred to as "wireless undeveloped areas").

To meet these demands, for example, Patent Document 1 proposes a combined wireless communication unit that integrates a wireless base station and a core network (EPC). By installing such a wireless communication unit in a wireless non-equipped area as described above, a small communication area can be created by the wireless base station module contained in the unit, and the EPC module in the unit controls the higher-level communications, making it possible to carry out 3GPP-specification wireless communications between multiple mobile terminals connected to the wireless base station module.

JP 2016-12841 A

Wireless communication units such as the one described above have a complex configuration because the wireless base station module and EPC module are integrated, and there is a problem that it is difficult to accurately grasp the operating status and operating environment of each module. For example, if an abnormality occurs, it is very time-consuming to identify the cause using only the error information output by the wireless base station module and the EPC module individually. Another drawback is that it is difficult to grasp the relationship with the operating environment inside the housing (for example, the temperature inside the housing).

The objective of the present invention is to provide a method for consolidating and understanding the operating status and operating environment of each component in a wireless communication system in which a wireless base station module and an EPC module are integrated inside a portable housing, thereby making it easier to understand the cause of any abnormalities that may occur.

In order to solve the above problems, a first wireless communication unit of the present invention comprises: a communication main unit including a wireless base station module that performs wireless communication with a mobile terminal based on 3GPP specifications; and an EPC (Evolved Packet Core) module that is connected to the wireless base station module by wire and performs upper network control for the wireless base station module;
a power supply module for supplying an operating voltage to the communication main unit;
a portable housing that integrally houses the communication main body and the power supply module;
an integrated control module provided within the portable housing and connected to the communication main unit by wire, the integrated control module including a communication log acquisition unit that acquires communication logs generated in association with execution of wireless communication processing in the wireless base station module and the EPC module from the wireless base station module and the EPC module as operation status information of the communication main unit, a communication log aggregation storage unit that collectively stores the acquired communication logs from the wireless base station module and the communication logs from the EPC module, and a communication log storage content output unit that outputs communication log data stored in the communication log aggregation storage unit ;
The communication log aggregation and memory unit is characterized in that it selectively stores abnormality logs, which indicate that the operating status of the radio base station module and the EPC module is abnormal, from among the communication logs generated by the radio base station module and the EPC module .
A second wireless communication unit of the present invention includes a communication main unit including a wireless base station module that performs wireless communication with a mobile terminal based on 3GPP specifications, and an EPC (Evolved Packet Core) module that is wired connected to the wireless base station module and performs upper network control for the wireless base station module;
a power supply module for supplying an operating voltage to the communication main unit;
a portable housing that integrally houses the communication main body and the power supply module;
an integrated control module provided within the portable housing and connected to the communication main unit by wire, the integrated control module including a communication log acquisition unit that acquires communication logs generated in association with execution of wireless communication processing in the wireless base station module and the EPC module from the wireless base station module and the EPC module as operation status information of the communication main unit, a communication log aggregation storage unit that collectively stores the acquired communication logs from the wireless base station module and the communication logs from the EPC module, and a communication log storage content output unit that outputs communication log data stored in the communication log aggregation storage unit;
The portable housing is provided with an operating environment information acquisition unit that acquires operating environment information of the communication main unit, and the overall control module is provided with an operating environment abnormality determination unit that determines whether an operating environment abnormality has occurred in the communication main unit based on the operating environment information, and the communication log aggregation memory unit also stores the abnormality determination result made by the operating environment abnormality determination unit.

In the first wireless communication unit of the present invention, the wireless base station module and the EPC module can each be provided with an abnormality log identification unit that identifies whether the generated communication log is an abnormality log, and an abnormality log transfer unit that transfers the identified abnormality log to the overall control module. The communication log acquisition unit of the overall control module can be configured to acquire the abnormality log transferred from the abnormality log transfer unit as a communication log.

The first and second wireless communication units of the present invention can be configured to be connected to a general control module and include a storage device mounting section to which a removable storage device is mounted, and a communication log data write control section that writes the communication log data output by the communication log storage content output section to the removable storage device via the storage device mounting section. On the other hand, the general control module may be provided with a LAN interface that connects an external terminal device to a LAN in a wired or wireless manner, and a communication log data transfer control section that transfers the communication log data output by the communication log storage content output section to the external terminal device via the LAN interface.

In the second wireless communication unit of the present invention, the operating environment information acquisition unit can be configured to acquire operating environment information of the communication main unit in the portable housing so as to include internal temperature information of the portable housing. In this case, a cooling device for cooling the internal space of the portable housing is provided, and the operating environment abnormality determination unit can be configured to determine that an operating environment abnormality has occurred when at least one of the following is true: operating state information of the cooling device indicates an operating abnormality of the cooling device, or internal temperature information of the portable housing exceeds a limit temperature. Also, the wireless communication unit of the present invention can be provided with a cooling device for cooling the internal space of the portable housing, and the operating environment abnormality determination unit can be configured to determine that an operating environment abnormality has occurred when at least one of the following is true: operating state information of the cooling device indicates an operating abnormality of the cooling device, or internal temperature information of the portable housing exceeds a limit temperature. Furthermore, the wireless communication unit of the present invention can be configured to be provided with a rechargeable battery that supplies a battery voltage to the power supply module, the operating environment information acquisition unit acquires operating environment information that further includes information related to the charging state and operating state of the rechargeable battery as battery state information, and the operating environment abnormality determination unit determines that an operating environment abnormality has occurred when the remaining battery charge reflected in the battery state information falls below a threshold. In this case, the power supply module is provided with an external power supply voltage receiving unit that receives an external power supply voltage, the operating environment information acquisition unit acquires operating environment information that further includes power receiving state information of the external power supply voltage receiving unit, and the operating environment abnormality determination unit can be configured to determine that an operating environment abnormality has occurred when the remaining battery charge reflected in the battery state information falls below a threshold when the power receiving state information indicates that the external power supply voltage is not being received.

The first and second wireless communication units of the present invention may be provided with a plurality of operating environment information acquisition nodes including an internal temperature information acquisition node that acquires internal temperature information of the portable housing. The overall control module may include a first network interface to which the base station computer and the EPC computer of the communication main body are connected via a first network, and a second network interface to which the plurality of operating environment information acquisition nodes are connected via a second network, the operating environment information acquisition unit communicates and acquires operating environment information from the operating environment information acquisition node via the second network interface, and the main body startup command transmission unit may be configured to transmit a main body startup command to the communication main body via the first network interface.

The second network is configured to connect a plurality of operating environment information acquisition nodes as slave nodes to a master node included in a second network interface, the operating environment information acquisition unit includes an acquisition target information request destination notifying unit that notifies the master node of the request destination of the acquisition target information, the master node sends an information request command to the second network in a form of addressing the slave node that is the request destination, and the slave node corresponding to the specified address acquires the information request command and transmits the acquisition target information indicated by the information request command to the master node via the second network. Specifically, the first network is, for example, a local area network (LAN), and the second network is an ^I2C network.

In addition, when a module support plate is provided inside the portable housing, one main surface of the module support plate is defined as a module mounting surface, and the module support plate is arranged horizontally so that the module mounting surface is on the upper side, the direction rising vertically from the module mounting surface is defined as the up-down direction. In a first direction defined along the module mounting surface, an airflow inlet is formed in the side wall portion of the first end side of the portable housing in the first direction, while an airflow outlet is formed in the side wall portion of the second end side, and a cooling fan constituting a cooling device is attached to the airflow inlet, and by operating the cooling fan, outside air is taken in through the airflow inlet and the airflow outlet is Outside air flows in a first direction inside the portable housing as cooling air and is then discharged from the airflow outlet. On the module mounting surface of the module support plate, a group of wireless drive system modules including a wireless base station module and a power supply module are arranged on the side closer to the airflow inlet in the flow direction of the cooling air, and a group of control system modules including an EPC module and a general control module are arranged on the side closer to the airflow outlet. As temperature sensors, a first temperature sensor is arranged in the occupied space of the wireless drive system module group, and a second temperature sensor is arranged in the occupied space of the control system module group.

The wireless communication unit of the present invention has a general control module that is wired to the communication main unit and includes a communication log acquisition unit that acquires communication logs generated in the wireless base station module and the EPC module as wireless communication processing is executed in the wireless base station module and the EPC module from the wireless base station module and the EPC module as operation status information of the communication main unit, a communication log aggregation memory unit that collectively stores the acquired communication logs from the wireless base station module and the communication logs from the EPC module, and a communication log storage content output unit that outputs the communication log data stored in the communication log aggregation memory unit. Since the communication logs of the wireless base station module and the EPC module can be collectively managed by the general control module, the operation status of each module can be collectively grasped, and it is also easy to grasp the cause of an abnormality when it occurs.

1 is a schematic diagram showing the concept of a wireless communication unit of the present invention; FIG. 2 is a block diagram showing an example of an electrical configuration of the wireless communication unit of FIG. 1 . FIG. 3 is another block diagram showing the configuration of FIG. 2 together with a power supply system. 3 is an explanatory diagram showing a connection structure of each master node and slave node in FIG. 2 by an I ² C network and a frame structure in I ² C communication; 1 is a conceptual diagram of an IP packet structure. FIG. 1 is a diagram conceptually illustrating a protocol stack of a 3GPP control plane. FIG. 1 is a diagram conceptually illustrating a 3GPP user plane protocol stack. FIG. 1 is a diagram conceptually illustrating 3GPP downlink channel mapping. FIG. 13 is a diagram conceptually showing uplink channel mapping. FIG. 1 is a conceptual diagram showing the relationship between frequency band channels and resource blocks. 11 is a flowchart showing a process flow of a master node in a read mode in I ² C communication. 11 is a flowchart showing a process flow of a write mode of a master node in I ² C communication. 6 is a flowchart showing the processing flow of a start-up sequence in the control firmware of the overall control module. 10 is a flowchart showing the flow of an abnormality analysis process. 10 is a flowchart showing the process flow of a normal termination sequence. 16 is a flowchart showing the procedure of the termination process of FIG. 15 . 6 is a flowchart showing the flow of an abnormality handling process during operation in the control firmware of the overall control module. 10 is a flowchart showing the flow of power supply switching processing. FIG. 4 is a diagram showing an example of the configuration of an alarm LED; 13A and 13B are diagrams showing modified examples of the manner of acquiring information from a cooling fan. FIG. 4 is a side view showing an example of an arrangement of modules inside the portable housing. Also a plan view. FIG. FIG. FIG. 4 is a side view showing details of the operation of the cooling fan and the airflow guide plate. 11 is a flowchart showing the flow of a communication log recording process in the wireless base station module and the EPC module. 11 is a flowchart showing the flow of abnormality log acquisition and aggregation processing of the overall control firmware. FIG. 4 is a diagram for explaining types of error logs. FIG. 4 is a schematic diagram showing an example of a storage format of abnormality log data in a communication log aggregation storage unit; FIG. 13 is a diagram showing a first output example of a GUI screen in an external PC. FIG. 11 is a diagram showing a second output example. FIG. 2 is a diagram showing an example of the electrical configuration of a mobile terminal device. FIG. 13 is a diagram showing an example of a GUI screen output in a mobile terminal device. FIG. 13 is a diagram showing an example of a password entry screen on the mobile terminal device. FIG. 13 is a diagram showing an example of a password change screen on the mobile terminal device. FIG. 13 is a communication processing flow diagram for password authentication. FIG. 13 is a flowchart showing a communication process for changing a password. FIG. 13 is a diagram showing an example of a communication log data output destination selection screen in an external PC. 10 is a flowchart showing the flow of a communication log data transfer process.

Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.
FIG. 1 is a schematic diagram conceptually illustrating an example of a wireless communication unit of the present invention. The wireless communication unit 1 is configured to perform wireless communication with a plurality of UEs (mobile terminal devices) 5 according to a communication protocol stack of a method defined by 3GPP (LTE in this embodiment, but other methods such as WiMAX may also be used). The wireless communication unit 1 is installed and used in wireless non-developed areas where EPC and wireless base stations are not developed as infrastructure, such as on the sea, in depopulated areas, or in areas where communication functions have been lost due to disasters, etc. The wireless communication unit 1 can procure power supply voltage from a battery, a private power generation device, etc., as described later, and can easily build a private wireless network that does not depend on a public network. Each UE 5 is connected to the wireless communication unit 1 by a wireless bearer 57.

The wireless communication unit 1 has a wireless base station module (wireless base station or eNodeB (evolved NodeB)) 4 and an EPC (Evolved Packet Core) module 3 that is wired to the wireless base station module 4 and functions as a higher-level network control unit for the wireless base station module 4. The EPC module 3 has an MME (Mobility Management Entity) 2 that serves as a gateway on the control plane side, an S-GW (Serving Gateway) 6 that serves as a gateway on the user plane side, and a P-GW (PDN (Packet Data Network) Gateway) 7 that is located at the junction with an upstream network element (here, a router 8) and manages IP addresses toward the upstream network element side. The router 8 connects to an application server (not shown) via an external network 60 (e.g., the Internet) wirelessly (e.g., satellite communication) or wired, and performs the function of acquiring content data such as terminal applications and videos (images). On the control plane side, the wireless base station module (eNodeB) 4 is connected to the MME 2 via the S1-MME interface. Also, on the user plane side, the wireless base station module 4 is connected to the S-GW 6 via the S1-U interface. The S-GW 6 is connected to the P-GW 7 via the S5 interface.

Figure 2 is a block diagram showing an example of the electrical configuration of the wireless communication unit 1. The wireless communication unit 1 has a portable housing 23 in which the EPC module 3, wireless base station module 4, overall control module 9, and power supply module 22 are housed together with peripheral components. The portable housing 23 is also provided with cooling fans 14A and 14B (cooling devices) for cooling the inside. The EPC module 3 and wireless base station module 4 together make up the communication main unit.

The EPC module 3 is mainly composed of an EPC computer 300. The EPC computer 300 is composed of a CPU 301, a RAM 302 which is a program execution area, a mask ROM 303 (which stores firmware for controlling microcomputer hardware peripherals that do not require permanent rewriting; the same applies below), and an internal bus 306 which interconnects them. A non-volatile storage device whose contents can be electrically rewritten, such as a flash memory 305, is connected to the internal bus 306 as an EPC function program storage unit, and the EPC communication firmware 305a (EPC function program) including an LTE protocol stack for EPC, and the programs of the MME entity 305b, S-GW entity 305c, and P-GW entity 305d which virtually realize the functions of the MME 2, S-GW 6, and P-GW 7 in FIG. 2 using the LTE protocol stack as a platform, and the software router 305e for realizing the functions of the router 8 in FIG. 1 are installed here. In addition, an Ethernet interface 304, which is a LAN interface, is connected to the internal bus 306. Note that in the above configuration, the MME 2, S-GW 6, and P-GW 7 in FIG. 2 are configured as virtual functional entities whose functions are realized by software on computer hardware, but each may be configured by independent hardware logic.

The wireless base station module 4 is mainly composed of a wireless base station computer 400. The wireless base station computer 400 is composed of a CPU 401, a RAM 402 which serves as a program execution area, a mask ROM 403, and an internal bus 406 which interconnects them. A flash memory 405 is connected to the internal bus 406 as a base station function program storage unit, and stores base station communication firmware 405a (base station function program) including an LTE protocol stack for wireless base stations. In addition, a wireless communication unit 412 for wirelessly connecting to UE 5 by establishing a wireless bearer, and an Ethernet interface 408 are connected to the internal bus 406.

The overall control module 9 is mainly composed of an overall control computer 900. The overall control computer 900 is composed of a CPU 901, a RAM 902 serving as a program execution area, a mask ROM 903, and an internal bus 906 connecting them to each other. A flash memory 905 is connected to the internal bus 906, and an overall control firmware 905a is stored therein. An Ethernet interface 904 (first interface), an input/output unit (I/O) 909, and a WiFi module 908 are also connected to the internal bus 906. In addition, in order to expand the function of the overall control module 9, a control board 13 that integrates control signals input and output to the overall control module 9 is separately provided. The control board 13 is equipped with an I ² C (Inter-Integrated Circuit) bus master 907 (second interface, master node) and an extended input/output unit (I/O) 910, which are each connected to the input/output unit (I/O) 909 of the overall control module 9. In a broad sense, the control board 13 can be regarded as one component of the overall control module 9 .

The EPC computer 300, the wireless base station computer 400, and the overall control computer 900 are connected by Ethernet interfaces 304, 408, and 904 via an Ethernet bus 32 (or a LAN cable) through a switching hub (e.g., an L2 switch) 11. That is, the EPC computer 300, the wireless base station computer 400, and the overall control computer 900 are connected to a LAN via the switching hub 11, and are capable of network communication with each other according to the Internet Protocol (IP).

The power supply module 22 supplies power supply voltage to each component such as the EPC module 3, the wireless base station module 4, the overall control module 9, the switching hub 11, and the cooling fans 14A and 14B, and receives the original voltage from the external power supply 26 (e.g., commercial AC: AC 100V) and the rechargeable battery 21 (e.g., a lithium-ion rechargeable battery or a nickel-hydrogen rechargeable battery) via the battery controller 24. In this embodiment, the AC voltage of the external power supply 26 is converted to a DC voltage (DC 12V) by the AC/DC converter 25 and supplied to the power supply module 22. The power receiving state (received voltage) from the external power supply 26 (AC/DC converter 25) is monitored by the external voltage monitoring unit 16 provided on the board of the power supply module 22.

The battery voltage of the rechargeable battery 21 is converted to a stabilized direct current voltage (DC 12V) by the battery controller 24 and supplied to the power supply module 22. This allows the wireless communication unit 1 to autonomously obtain the driving power supply voltage from the rechargeable battery 21, and it can be used without problems even in installation locations where external power supply voltages such as commercial AC cannot be used (for example, disaster areas where a power outage has occurred). The portable housing 23 is, for example, a box made of metal or reinforced resin.

The battery controller 24 is configured as a commercially available I ² C device, and multiple rechargeable batteries 21 are mounted in parallel and detachably. When the output voltage of the rechargeable battery 21 drops due to discharge, the rechargeable battery 21 can be removed from the battery controller 24 and another charged rechargeable battery 21 can be attached. At this time, each rechargeable battery 21 can be hot-swapped on the battery controller 24. When the power supply module 22 is receiving power from the external power supply 26, the battery controller 24 can charge the rechargeable battery 21 with the external power supply voltage. Furthermore, when the power supply module 22 is receiving power from the external power supply 26 and the power supply is cut off due to a power outage, the wireless communication unit 1 can continue to operate without momentary interruption by switching to receiving power from the rechargeable battery 21 (described later).

The power supply module 22 is equipped with a plurality of stabilized DC power supply circuits (not shown) with different output voltages in order to correspond to a plurality of DC power supply voltages required by each component. FIG. 3 shows the form of power supply to each component in the wireless communication unit 1, where the circle marks on the frame of each component indicate power supply terminals, and the dashed lines connecting them indicate power supply lines. In this embodiment, DC 3.5V is distributed and input to the EPC module 3, whose main hardware is only the EPC computer 300, and DC 5V is input to the switching hub 11 having a switching drive unit, via the backplane 12. DC 3.5V is input to the wireless base station module 4 having the wireless communication unit 412, and DC 5V is input to the general control module 9 having the WiFi module 908. In FIG. 3, the square marks on the frame of each component indicate LAN ports, and the solid lines (single lines) connecting them indicate the Ethernet bus (or LAN cable) 32 forming the first network. Furthermore, the ■ marks on the frame of each component indicate I ² C ports, and the solid (double) lines connecting them indicate the I ² C bus 52 forming the second network. Also, the ● marks indicate ports for external connection (and corresponding terminals on the components). Specifically, the external port group 31A of the software router 8 includes an APP port (a port for connecting to an application server), an MNT port (a port for connecting to an operation management LAN of the wireless communication unit 1), and a BH port (a backhaul port for connecting to the Internet, etc.). Also, the external port group 31B of the wireless base station module 4 is for connecting an antenna 413 to the wireless communication unit 412 in FIG. 2. The TRx1 port is a connection port for a common transmission/reception antenna, and the Rx2 port is a connection port for a common transmission/reception antenna and a receiving antenna that forms a diversity reception (in FIG. 2, the antenna 413 consisting of these multiple antenna groups is illustrated in a simplified form as one antenna).

Next, as shown in Fig. 2, a power switch 65, a control switch 66, and a plurality of LEDs 60 forming an abnormality notification unit are provided on the portable housing 23. The power switch 65 and the control switch 66 are connected to an expansion input/output unit 910 on the control board 13. The plurality of LEDs 60 are also connected to an LED driver 17 configured as an ^I2C device via a current adjustment resistor 62 (see Fig. 3). As shown in Fig. 3, the signal lines of the power switch 65 and the control switch 66 are pulled up by a signal power supply voltage Vcc via a resistor 67, and a binary switch signal reflecting the switch open/close state is input to the expansion input/output unit 910. Among these, the switch signal input by the operation of the power switch 65 serves as a main start signal, and is used as a command signal for starting up the EPC communication firmware 305a and the base station communication firmware 405a collectively (the expansion input/output unit 910 functions as a main start signal reception unit). The switch signal input by the operation of the control switch 66 is used for system reset and other control inputs.

On the other hand, the wireless base station module 4 is provided with a first temperature sensor (hereinafter, also referred to as "temperature sensor 1" in the drawings) 15A, and the control board 13 described later is provided with a second temperature sensor (hereinafter, also referred to as "temperature sensor 2" in the drawings) 15B. Below, an example of the internal structure of the wireless communication unit 1 will be described together with the arrangement of each module, the temperature sensors 15A, 15B, and the cooling fans 14A, 14B. FIG. 21 is a side view showing the internal structure of the wireless communication unit 1, and FIG. 22 is a plan view. In the longitudinal direction (first direction: left-right direction in the drawing) of the portable housing 23, an airflow inlet 23y is formed in the side wall part on the first end side (left side), and the cooling fans 14A, 14B are attached here. Specifically, as shown in FIG. 22, a pair of cooling fans 14A, 14B are arranged at a predetermined interval in the width direction (second direction: up-down direction in the drawing) of the portable housing 23. On the other hand, as shown in FIG. 22, an airflow outlet 23w is formed in the side wall portion at the second end (right side) in the longitudinal direction of the portable housing 23, and is covered by an air filter 23f. When the cooling fans 14A and 14B are operated, outside air FA is taken in through the airflow inlet 23y, and after circulating inside the portable housing 23 in the longitudinal direction as cooling air, it is discharged from the airflow outlet 23w.

A bottom support plate 233 is disposed on the bottom of the portable housing 23. A duplexer 404 is attached to the top surface of the bottom support plate 233. As shown in FIG. 2, the duplexer 404 is disposed directly below the transmit/receive antenna included in the antenna 413 of the wireless communication unit 412, and is a component that electrically separates the antenna transmit path from the antenna receive path to prevent strong transmit waves from flowing into the receive side. In the case of a wireless base station, the transmit wave output is high, for example, around 100 to 250 W, so a large low-pass filter component made of a cavity filter or the like is included. The duplexer 404 has a large spatial dimension, but generates little heat. Therefore, it is desirable to place it on the top surface of the bottom of the portable housing 23, as shown in FIG. 21.

Next, an intermediate support plate 234 is disposed above the bottom support plate 233 as a module support plate. The bottom support plate 233 and the intermediate support plate 234 are connected to each other by a plurality of support columns 235 disposed on the outer periphery of the plate surface. The upper surface of the intermediate support plate 234 forms a module mounting surface, and in the flow direction (longitudinal direction, first direction) of the cooling air inside the portable housing 23, a group of wireless drive system modules including the wireless base station module 4 and the power supply module 22 are disposed on the upstream side (the side closer to the airflow inlet 23y), and a group of control system modules including the EPC module 3, the general control module 9, and the control board 13 are disposed on the downstream side (the side closer to the airflow outlet 23w). By disposing the group of wireless drive system modules with a large amount of heat generation on the windward side of the cooling air, it is possible to effectively cool the group of wireless drive system modules, and by isolating the group of control system modules on the leeward side, it is possible to prevent excessive temperature rise of the group of control system modules. The temperature sensors 15A and 15B are arranged such that the first temperature sensor 15A is disposed in the space occupied by the wireless drive system modules, and the second temperature sensor 15B is disposed in the space occupied by the control system modules. In the following description, the vertical direction is defined for convenience as the direction rising vertically from the upper surface (module mounting surface) of the intermediate support plate 234 (module support plate) when it is placed horizontally, but the orientation of the module mounting surface in the portable housing 23 is not limited to the horizontal direction, and for example, the module mounting surface may be inclined or perpendicular to the horizontal plane.

By arranging the first temperature sensor 15A in the occupied space of the wireless drive system modules that generate a large amount of heat during operation and detecting the temperature, it is possible to grasp the behavior of the wireless drive system modules as a heat source in the portable housing 23. On the other hand, by arranging the second temperature sensor 15B in the occupied space of the control system modules that generate a small amount of heat during operation and detecting the temperature, it is possible to accurately grasp whether the cooling effect on the control system modules is sufficiently achieved even with the cooling air that has passed through the wireless drive system modules. In addition, by combining temperature detection near the heat source (wireless drive system modules) and temperature detection at a position away from the heat source downstream in the air flow direction as described above, it may be easier to identify the cause when a temperature abnormality occurs in the portable housing 23. For example, when the cooling fans 14A and 14B stop due to an abnormality, a unique behavior occurs in which the temperature detected by the first temperature sensor 15A close to the heat source immediately begins to rise, and then the temperature detected by the second temperature sensor 15B rises with a slight delay. Furthermore, if an overcurrent occurs in the control system module group due to a short circuit or the like, the temperature detected by the first temperature sensor 15A does not change significantly, whereas the temperature detected by the second temperature sensor 15B, which detects heat generation in the control system module group, begins to rise rapidly. By referring to the difference in temperature detection behavior of the two temperature sensors 15A and 15B as described above, information that contributes to identifying the cause of the temperature abnormality can be easily obtained.

The wireless base station module 4 and the power supply module 22 are arranged adjacent to each other vertically on the module mounting surface (upper surface) of the intermediate support plate 234 so that the main surfaces of the component mounting boards 4s, 22s overlap each other in a plan view, and a cooling air circulation gap 231 is formed between them. The cooling fans 14A, 14B are attached to the portable housing 23 in such a manner that a part of the cooling air can be blown into the cooling air circulation gap 231. By arranging the wireless base station module 4 and the power supply module 22, which form a wireless drive system module group that generates a large amount of heat, adjacently as described above, the area occupied by the wireless drive system module group on the module mounting surface in the portable housing 23 can be reduced, contributing to the compactness of the wireless communication unit 1. And, even though the wireless base station module 4 and the power supply module 22, which generate a large amount of heat, are arranged adjacently, the heat generated by both can be more effectively discharged by sending the cooling air to the cooling air circulation gap 231 formed between them, and the temperature of the wireless drive system module group can be more effectively prevented from rising excessively.

As shown in FIG. 21, the power supply module 22 has a board 22s on which components (including a coil 22i, a capacitor 22c, a DC/DC conversion IC 22d, etc.) are mounted. Similarly, the wireless base station module 4 has multiple boards 4s on which components (including power semiconductor elements 4a such as power amplifier elements) are mounted. These boards 22s, 4s are connected to each other vertically by support parts 232.

In addition, the power supply module 22 is disposed below the module mounting surface of the intermediate support plate 234, and the wireless base station module 4 is disposed above it. The cooling air from the cooling fans 14A and 14B is divided into a first airflow CFA toward the cooling air gap 231 and a second airflow CFB toward the opposite side of the cooling air gap 231 (i.e., the top surface of the wireless base station module 4 in FIG. 21) in the normal direction of the board 4s of the wireless base station module 4. This allows the cooling air to be distributed above and below the wireless base station module 4, which generates a particularly large amount of heat, enabling more efficient cooling. When the transmission output of the wireless base station module 4 is, for example, 100 to 250 W, it is preferable that the speed of the cooling air from the cooling fans 14A and 14B is about 1 to 2 m/s.

The power semiconductor element 4a of the wireless base station module 4 is mounted on the upper surface of the wireless base station module 4, that is, on the uppermost one of the multiple boards 4s, and a heat sink plate 4h made of a metal such as aluminum is provided in close contact with the upper surface of the power semiconductor element 4a. A plurality of metal heat dissipation fins 4f are integrally formed on the upper surface of the heat sink plate 4h in a form that rises vertically from the upper surface of the heat sink plate 4h. As shown in FIG. 22, the longitudinal direction of the heat dissipation fins 4f is arranged in accordance with the longitudinal direction of the portable housing 23 (the blowing direction of the cooling air), and the gap between adjacent heat dissipation fins 4f, 4f forms a passage 4k for the cooling air (see FIG. 24). This can significantly improve the cooling efficiency of the power semiconductor element 4a by the second airflow CFB in FIG. 21.

As shown in FIG. 21, the cooling fans 14A and 14B are attached to the portable housing 23 so that the extension of the rotation axis J of the fan blades 14p passes through the middle of the height direction of the side of the wireless drive system module group. Each of the cooling fans 14A and 14B has a base part 14b that houses the fan drive motor and the like, and a main body part 14m that is integrated with the base part 14b and houses the fan blades 14p. The main body part 14m is attached to the base part 14b so that the extension of the rotation axis J of the fan blades 14p is inclined upward so as to enter the inside of the cooling air circulation gap 231. As a result, the cooling air of the cooling fans 14A and 14B can efficiently blow the first airflow CFA into the cooling air circulation gap 231 from the diagonally downward side, while the second airflow CFB can be guided at a relatively large flow rate to the upper side of the wireless base station module 4 (the side where the heat sink plate 4h and the heat dissipation fins 4f are provided) far from the module mounting surface.

On the front side of the cooling fans 14A and 14B in the airflow direction, an airflow guide plate 14s is provided to divide the cooling air into the first airflow CFA and the second airflow CFB. The airflow guide plate 14s is arranged with its plate surface inclined upward from the rotation axis J of the fan rotor blades 14p so that the second airflow CFB is guided to the upper surface side of the wireless drive system module. This allows the second airflow CFB to be more efficiently guided to the upper surface side of the wireless drive system module group (the upper surface side of the wireless base station module 4 in the example of FIG. 21), promoting the cooling of the wireless drive system module group. As shown in FIG. 24, the airflow guide plate 14s has mounting arm parts 14sf integrated at both ends, and the mounting arm parts 14sf are fixed to the base parts 14b of the cooling fans 14A and 14B by fastening members 14t such as screws.

Also, as shown in FIG. 21, a shielding plate 4p is attached to the upper surface side of the heat dissipation fin 4f of the wireless base station module 4. The shielding plate 4p can also be made of metal. As shown in FIG. 24, by providing this shielding plate 4p, the above-mentioned cooling air passage 4k is formed between adjacent heat dissipation fins 4f, 4f with a square cross section whose upper part is blocked by the shielding plate 4p. As shown in FIG. 25, if the shielding plate 4p does not exist, the second airflow CFB blown diagonally from below to the entrance part of the passage 4k will blow up the passage 4k, and it is difficult to form a flow of cooling air along the plate surface of the heat sink plate 4h. However, if the shielding plate 4p is provided, the second airflow CFB is prevented from passing upward, and the flow inside the passage 4k becomes dominant, allowing the second airflow CFB to come into contact with the plate surface of the heat sink plate 4h more efficiently. In addition, an edge effect occurs when the second airflow CFB hits the edge of the entrance side of the shielding plate 4p from diagonally below, and the flow is narrowed and accelerated by the Karman vortex generated near the entrance inside the passage 4k, resulting in a pressure reduction effect that is expected to draw the airflow into the passage 4k.

Returning to FIG. 21, the EPC module 3, the overall control module 9, the switching hub 11, and the control board 13 that form the control system module group are arranged downstream of the wireless drive system module group (wireless base station module 4 and power supply module 22) in the direction of cooling air blowing. Of these, the overall control module 9 and the control board 13 are directly attached to the intermediate support plate 234. FIG. 23 shows the mounting layout of each board on the upper surface (module mounting surface) of the intermediate support plate 234, and when the direction perpendicular to the longitudinal direction (air blowing direction, left-right direction in the drawing) of the portable housing 23 within the module mounting surface is defined as the depth direction, the board of the overall control module 9 and the control board 13 are assembled adjacent to each other on the intermediate support plate 234 in the depth direction downstream of the power supply module 22 in the air blowing direction.

Furthermore, four columnar board support frames 236 are erected on the downstream side of the power supply modules 22 in the air blowing direction. As shown in FIG. 21, the boards of the EPC module 3 and the switching hub 11 are attached to the board support frames 236 in this order from below, at the four corner positions, while forming gaps for air blowing.

Next, the temperature sensors 15A and 15B are attached to the internal temperature monitoring devices 85A and 85B (upper part of FIG. 4) that constitute the drive status information acquisition node, and play a role in acquiring the internal temperature information of the portable housing 23 as the operating environment information of the communication main body. As shown in FIG. 21, the temperature sensors 15A and 15B are both mounted on the boards that constitute the internal temperature monitoring devices 85A and 85B. The first temperature sensor 15A is mounted on the side of the wireless base station module 4 together with the board of the internal temperature monitoring device 85A. The second temperature sensor 15B is mounted on the board 907s of the I ² C bus master 907 that is erected on the control board 13 together with the board of the internal temperature monitoring device 85B (the board 907s is considered to belong to the control board 13 in a broad sense). Both the temperature sensors 15A and 15B are arranged so as to detect the temperature at the side positions in the depth direction of the wireless drive system module group and the control system module group.

On the other hand, the cooling fans 14A, 14B incorporate fan operation monitoring devices 84A, 84B (top of Figure 4: cooling device operating status information acquisition node, slave node) which serve as operating status information acquisition nodes, and serve to monitor and acquire, for example, the fan rotation speed, temperature, and operating current value as operating environment information of the communication main unit. The external voltage monitoring unit 16 also serves as an operating status information acquisition node, and serves to monitor and acquire the received voltage from the AC/DC converter 25 of the power supply module 22 as operating environment information. Furthermore, the battery controller 24 also serves as an operating status information acquisition node, and serves to monitor and acquire the remaining battery (BTT), battery voltage, and battery temperature as operating environment information.

4, the fan operation monitoring devices 84A, 84B, internal temperature monitoring devices 85A, 85B, external voltage monitoring unit 16, and battery controller 24, which constitute operating environment information acquisition nodes, are configured as slave nodes of ^I2C communication. On the other hand, the ^I2C bus master 907 on the control board 13 functions as a master node in ^I2C communication, and constitutes an operating environment information acquisition unit to which the above-mentioned slave nodes (operating environment information acquisition nodes) are connected via the ^I2C bus 52 and which acquires operating environment information from each slave node in the form of a detection log.

In this way, the network (second network) for acquiring the operating environment information is separated from the communication network (first network) connecting the overall control module 9 and the communication main unit (base station computer 400 and EPC computer 300), so that the communication sequence for acquiring the operating environment information can be separated from the complex communication sequence required for controlling the communication main unit itself, and the operating environment information can be acquired more easily and smoothly. In addition, by providing a master node on the second network interface side, transmitting an information request command from the master node to the slave node in a form that addresses the slave node that is the operating environment information acquisition node, and transmitting the operating environment information from the slave node in response to this, the sequence does not become complicated when acquiring the operating environment information from multiple devices, and the operating environment information can be collected more efficiently. If an I ² C network is used as such a second network, it is possible to easily control transmission and reception by serial communication even for relatively large operating environment information, and complicated input/output port control processing is not required.

An outline of ^I2C communication will be described below. In ^I2C communication, a master node ( ^I2C bus master 907) and slave nodes are clearly distinguished, and the master node takes the lead in control. The ^I2C bus 52 that connects the master node and slave nodes consists of two lines, a clock line SCL and a data line SDA, and a binary data signal is serially transferred on the data line SDA based on the clock signal transmitted by the master node via the clock line SCL. Each slave node has a unique address, and when information is transmitted, an acknowledge signal (ACK) is always returned from the destination node to the source node.

4 shows the structure of a data frame 1100 for I ² C communication. The data frame 1100 includes the following fields.
Address field 1101: The address of the slave node to which data is to be transferred is transferred in 7 or 10 bits. The information transfer direction of the address field 1101 is always from master (M) to slave (S). All slave nodes receive the address based on this clock, and only the slave node whose address matches its own address continues to send and receive thereafter. Different addresses are assigned to the fan operation monitoring devices 84A, 84B, internal temperature monitoring devices 85A, 85B, external voltage monitoring unit 16, and battery controller 24, which constitute the operating environment information acquisition nodes, and the addresses also function as information for identifying the type of device from which operating environment information is to be acquired.
R/W field 1102: 1 bit of R/W mode information is transferred. When the R/W mode information is "0", it indicates information input from the slave (S) to the master (M) (Read mode: reading information from the slave node), and when the R/W mode information is "1", it indicates information output from the master (M) to the slave (S) (Write mode: writing information to the slave node). The transfer direction is from the master (M) to the slave (S).
ACK 1103: This is an acknowledge signal for transmission and reception of the R/W field, and the transfer direction is master (M) <- slave (S) in the read mode, and master (M) -> slave (S) in the write mode.
Data field 1104: 1 byte (8 bits) of information (data or command) is transferred. The transfer direction is master (M) → slave (S) in read mode, and master (M) ← slave (S) in write mode. If the content is a command, the type of operating environment information to be acquired for each device constituting a slave node (for example, in the case of the battery controller 24, the remaining battery level, battery voltage, temperature, etc.) is specified by the command uniquely associated with the type.
ACK 1105: This is an acknowledge signal for the transmission and reception of a data field, and the transfer direction is master (M) <- slave (S) in the read mode, and master (M) -> slave (S) in the write mode.
If the total size of the information to be transferred is larger than the size of the data field 1104, the information is divided into a plurality of data fields 1104 and then transferred.

11 shows the process flow of the master node in the Read mode. In S151, the ^I2C bus (SCL and SAD) is set to the information transfer start state (Start Condition), and in S152, the address of the slave node to which the information is requested is output, and "0" is output as the R/W mode information. If an ACK is input in S153, the process proceeds to S154, where data (or a command) from the slave node is input (if there is no ACK, the process proceeds to error processing in S159). If the data (or command) is input normally in S155, the process proceeds to S156, where an ACK is returned to the slave node (if the data is not input normally, the process proceeds to error processing in S159). If the input of all data is not completed in S157, the process returns to S154, and the following process is repeated. On the other hand, if the input of all data is completed in S157, the process proceeds to S158, where the ^I2C bus is set to the information transfer end state (Stop Condition), and the process ends.

12 shows the process flow of the master node in the Write mode. In S101, the ^I2C bus is set to the Start Condition, and in S102, the address of the slave node to which information is to be transferred is output, and "1" is output as the R/W mode information. If an ACK is input in S103, the process proceeds to S104, where data (or a command) is output (if there is no ACK, the process proceeds to error processing in S108). If an ACK is received from the slave node in S105, the process proceeds to S106, where it is confirmed whether the output of all data has been completed. If not, the process returns to S104, and the following process is repeated. On the other hand, if the output of all data has been completed in S106, the process proceeds to S107, where the ^I2C bus is set to the information transfer end state (Stop Condition), and the process ends.

The following is an overview of the 3GPP-specification communication method. Figure 5 is a schematic diagram showing the structure of an IP packet used for data transmission between UE 5 and wireless communication unit 1. IP packet 1300 consists of IP header 1301 and payload 1302, and IP header 1301 contains a PDU identification number, data source address 1301a, destination address 1301b, etc. Furthermore, ToS (Type of Service) field 1301c is formed in IP header 1301. ToS field 1301c specifies the packet transfer priority and the type of communication.

Figures 6 and 7 show the 3GPP-specification radio protocol stack that is the basis for the EPC communication firmware 305a or the base station communication firmware 405a. Figure 6 shows the user plane protocol stack, and Figure 7 shows the control plane protocol stack. The radio protocol stack is divided into layers 1 to 3 of the OSI reference model, with layer 1 being the PHY (physical) layer. Layer 2 includes the MAC (Medium Access Control) layer, the RLC (Radio Link Control) layer, and the PDCP (Packet Data Convergence Protocol) layer. Layer 3 includes the RRC (Radio Resource Control) layer and the NAS (Non-Access Stratum) layer.

The roles of each layer are as follows:
PHY layer: Performs encoding/decoding, modulation/demodulation, antenna mapping/demapping, and resource mapping/demapping.
MAC layer: Performs data priority control, retransmission control processing by HARQ, random access procedures, etc. Data and control signals are transmitted via a transport channel between the MAC layer of the UE 5 and the MAC layer of the radio base station module 4. The MAC layer of the radio base station module 4 includes a scheduler that determines the uplink and downlink transport formats (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be assigned to the UE 5.

RLC layer: Using the functions of the MAC layer and the PHY layer, data is transmitted to the RLC layer on the receiving side. Data and control signals are transmitted between the RLC layer of the UE 5 and the RLC layer of the radio base station module 4 via logical channels.
PDCP layer: Performs PDU header compression/decompression, and encryption/decryption.
RRC layer: defined only in the control plane that handles control signals. Messages (RRC messages) for various settings are transmitted between the RRC layer of the UE 5 and the RRC layer of the radio base station module 4. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. If there is a connection (RRC connection) between the RRC of the UE 5 and the RRC of the radio base station module 4, the UE 5 is in RRC connected mode, and if not, it is in RRC idle mode.

The above layers are used in both the control plane and the user plane. On the other hand, only in the control plane, the UE 5 and MME 2 are provided with a NAS layer that performs session management, mobility management, and the like, which is even higher than the RRC layer. In addition, the user data transmission interface with the EPC module 3 side of the radio base station module 4 is provided with a GTP-U (GPRS (General Packet Radio Service) Tunneling Protocol for User Plane) layer. The GTP-U layer is used to identify the UE 5 to which it is connected and the radio bearer to be used.

Next, Fig. 8 shows downlink channel mapping. Here, the mapping relationship between the logical channel (Downlink Logical Channel), the transport channel (Downlink Transport Channel) and the physical channel (Downlink Physical Channel) is shown. Each will be explained in order below.
- DTCH (Dedicated Traffic Channel) is a dedicated logical channel for the transmission of data. DTCH is mapped to the transport channel DLSCH (Downlink Shared Channel).
Dedicated Control Channel (DCCH): A logical channel for transmitting dedicated control information between the UE 5 and the network. The DCCH is used when the UE 5 has an RRC connection with the radio base station module 4. The DCCH is mapped to the DLSCH.
CCCH (Common Control Channel): A logical channel for transmission control information between the UE 5 and the radio base station module 4. The CCCH is used when the UE 5 does not have an RRC connection with the radio base station module 4. The CCCH is mapped to the DLSCH.
BCCH (Broadcast Control Channel): A logical channel for distributing system information. The BCCH is mapped to the BCH (Broadcast Channel) or DLSCH, which are transport channels.
PCCH (Paging Control Channel): A logical channel for reporting paging information and changes in system information. The PCCH is mapped to the Paging Channel (PCH), which is a transport channel.

Moreover, the mapping relationship between the transport channels and the physical channels is as follows:
DLSCH and PCH: Mapped to the Physical Downlink Shared Channel (PDSCH). DLSCH supports HARQ, link adaptation and dynamic resource allocation.
- BCH: Mapped to PBCH (Physical Broadcast Channel).

Fig. 9 shows uplink channel mapping. As in Fig. 8, it shows the mapping relationship between the logical channel (Downlink Logical Channel), the transport channel (Downlink Transport Channel) and the physical channel (Downlink Physical Channel). Each will be described in order below.
CCCH (Common Control Channel): A logical channel used to transmit control information between the UE 5 and the EPC module 3, and is used by a UE 5 that does not have a Radio Resource Control (RRC) connection with the EPC module 3.
DCCH (Dedicated Control Channel): A point-to-point bidirectional logical channel used to transmit individual control information between the UE 5 and the EPC module 3. The dedicated control channel DCCH is used by the UE 5 having an RRC connection.
- DTCH (Dedicated Traffic Channel): A one-to-one bidirectional logical channel, which is dedicated to a specific UE and is used for the transfer of user information.

ULSCH (Uplink Shared Channel): A transport channel that supports HARQ, dynamic adaptive radio link control, and discontinuous transmission (DTX).
- RACH (Random Access Channel): A transport channel on which restricted control information is transmitted.

PUCCH (Physical Uplink Control Channel): A physical channel used for notifying the radio base station module 4 of response information (ACK (Acknowledge)/NACK (Negative acknowledge)) to downlink data, downlink radio quality information (CQI: Channel Quality Indicator), and a transmission request for uplink data (Scheduling Request: SR).
PUSCH (Physical Uplink Shared Channel): A physical channel used to transmit uplink data.
PRACH (Physical Random Access Channel): A physical channel mainly used for transmitting a random access preamble for acquiring transmission timing information (transmission timing command) from the UE 5 to the radio base station module 4. The random access preamble transmission is performed in the random access procedure.

As shown in FIG. 9, in the uplink, the transport channels and physical channels are mapped as follows: The uplink transmission/reception channel ULSCH is mapped to the physical uplink transmission/reception channel PUSCH. The random access channel RACH is mapped to the physical random access channel PRACH. The physical uplink control channel PUCCH is used as a physical channel alone. In addition, the common control channel CCCH, the dedicated control channel DCCH, and the dedicated traffic channel DTCH are mapped to the uplink transmission/reception channel ULSCH.

In the downlink of the LTE system, the UE 5 wirelessly connects to the radio base station module 4 by using Orthogonal Frequency-Division Multiplexing (OFDM) access (OFDMA). The OFDMA method is characterized as a two-dimensional multiplexing access method that combines frequency division multiplexing and time division multiplexing. Specifically, subcarriers on the orthogonal frequency axis and time axis are divided and allocated to the UE 5, and the orthogonal subcarriers on the frequency axis are divided so that the signal of each subcarrier becomes zero (0 point). By dividing the subcarriers and allocating them on the frequency axis, it is possible to select another subcarrier that is not affected even if a certain subcarrier is affected by fading, so that the user can use a better subcarrier according to the wireless environment, and the wireless quality can be maintained.

In the OFDMA system, resource blocks (hereinafter also referred to as RBs) defined on a virtual plane spanned by a frequency axis and a time axis are adopted as radio resources. As shown in FIG. 10, RBs are defined as blocks obtained by dividing the above plane into a matrix of 180 kHz/0.5 msec, and each resource block RB includes 12 adjacent subcarriers spaced at 15 kHz intervals on the frequency axis and one slot (7 symbols) of a frame on the time axis. Two adjacent RBs (1 msec) on the time axis are assigned to UE5 as a set. On the other hand, in the uplink of the LTE system, resource blocks RBs of a similar concept are used as radio resources, except that SC-FDM (Single Carrier Frequency-Division Multiplexing) access (SC-FDMA) is adopted. In OFDMA, one resource block is divided into 12 subcarriers (bandwidth: 15 kHz) on the frequency axis, whereas SC-FDMA is a single-carrier method in which no division into subcarriers occurs.

The overall control module 9 can realize the following functional operations by executing the overall control firmware 905a.
Acquires operation status information of the communication main unit from the communication main unit (operation status information acquisition unit). Specifically, a communication log generated in association with the execution of wireless communication processing in the wireless base station module 4 and the EPC module 3 is acquired from the wireless base station module 4 and the EPC module 3 as operation status information of the communication main unit (communication log acquisition unit).
A GUI data generating unit generates GUI data for displaying the state of each component inside the portable housing, which state is indicated by the operating state information and the operating environment information, on a GUI screen for each component.
- Holds GUI data so that it can be read and accessed from an external terminal device (GUI server section).
Based on the operating environment information acquired by the operating environment information acquisition unit (I ² C bus master 907 ), it is determined whether or not a predetermined operating environment abnormality has occurred (operating environment abnormality determination unit).
Only when it is determined that no abnormality has occurred in the operating environment, a main body start-up command is sent to the communication main body (main body start-up command sending section).
When an abnormality occurs in the operating environment, an abnormality in the operating environment is notified (abnormality notification unit).
- After the base station function program and EPC function program are launched in the communication main body, if the operating environment abnormality determination unit determines that an operating environment abnormality has occurred, it instructs the communication main body to execute a close process for the base station function program stored in the base station function program memory unit and the EPC function program (EPC communication firmware 305a) stored in the EPC function program memory unit (flash memory 305), and then performs a power cut-off process for the communication main body (anomaly response processing unit during operation).

The LED 60 in FIG. 2 has a function of an abnormality notification section, and includes, for example, one as shown in FIG.
Power LED 60A: indicates the operating state of the power switch 65. For example, when the power supply module 22 is in a power receiving state, the power LED 60A lights up when the power supply switch 65 is turned on, and goes out when the power supply switch 65 is turned off.
Operation LED 60B: Notifies whether the communication main unit (EPC module 3 and wireless base station module 4) is receiving power and is in startup operation (whether the EPC communication firmware 305a and the base station communication firmware 405a are running). For example, it lights up when startup operation is in progress and turns off when not.
Fan LED 60C: For example, the LED 60C is turned on when an abnormality occurs in the cooling fans 14A, 14B, and is turned off otherwise.
Temperature LED 60D: For example, the LED 60D is turned on when there is an abnormality in the temperatures detected by the temperature sensors 15A and 15B, and is turned off otherwise.
Battery LED 60E: For example, this lights up when it becomes difficult to supply power normally from the battery 21, for example when the remaining charge of the rechargeable battery 21 falls below a threshold, and is turned off otherwise.
External power supply LED 60F: Lights up when there is an input from the external power supply 26, and turns off when there is no input.

The details of the function realization process by the overall control firmware 905a will be described below with reference to a flowchart. In FIG. 2, when the user presses the power switch 65 in FIG. 2 in a power-off state, a main start signal is input to the input/output unit 909 of the overall control computer 900. FIG. 13 shows the process flow of the start sequence when starting the operation of the wireless communication unit 1. When the main start signal is detected in S201, it is determined that the power is ON, and in S202, the overall control computer 900 (overall control firmware 905a) is started. In S203, the I ² C bus master 907 is notified that the power is ON. The I ² C bus master 907 transmits a command to turn on the power LED 60A to the LED driver 17 by I ² C communication. The LED driver 17 receives this command and turns on the power LED 60A in T203.

Next, in S204, the ^I2C bus master 907 is instructed to collect detection logs from the battery controller 24. The ^I2C bus master 907 transmits a detection log collection command to the battery controller 24 by ^I2C communication. The battery controller 24 receives this and transmits a detection log (operating environment information). In S205, the ^I2C bus master 907 receives the detection log from the battery controller 24.

Similarly, in S206, the ^I2C bus master 907 is instructed to collect detection logs from the cooling fans 14A, 14B (fan operation monitoring devices 84A, 84B) and the temperature sensors 15A, 15B (internal temperature monitoring devices 85A, 85B). The ^I2C bus master 907 transmits a detection log collection command to the fan operation monitoring devices 84A, 84B and the internal temperature monitoring devices 85A, 85B via ^I2C communication. The fan operation monitoring devices 84A, 84B and the internal temperature monitoring devices 85A, 85B receive this and transmit detection logs (operating environment information). In S207, the ^I2C bus master 907 receives the detection logs from the fan operation monitoring devices 84A, 84B and the internal temperature monitoring devices 85A, 85B.

In S208, the received detection log is analyzed to determine whether or not there is an abnormality. FIG. 14 shows the details. In S2081, the detection logs of the first temperature sensor 15A and the second temperature sensor 15B are analyzed. For both temperature sensors, a "normal" state is determined when the detected temperature d is equal to or lower than the upper limit value dmax.

In S2082, the detection log of the cooling fans 14A, 14B (fan operation monitoring devices 84A, 84B) is analyzed. The conditions for determining that the operation of the cooling fans 14A, 14B is normal are as follows.
The rotation speed u is within the normal range (umin≦u≦umax: umin is the minimum permissible rotation speed, and umax is the maximum permissible rotation speed). The rotation speed can be detected by a rotation sensor such as a rotary encoder (neither is shown). If the rotation speed u is less than umin, it means that the drive motors of the cooling fans 14A, 14B are not rotating normally due to a broken wire or other factors, and there is a risk that the inside of the portable housing 23 will not be sufficiently cooled and will become hot. On the other hand, if the rotation speed u exceeds umax, there is a possibility that an excessive current will flow through the drive motors of the cooling fans 14A, 14B due to a short circuit or the like, causing them to run out of control and leading to a breakdown.
The temperature Tf is within the normal range (Tf≦Tfmax: Tfmax is the maximum allowable temperature). If the temperature Tf exceeds Tfmax, it means that the drive motors of the cooling fans 14A, 14B are abnormally hot due to a malfunction such as overload, which may lead to breakdowns. The temperature of the cooling fans 14A, 14B can be detected by, for example, a temperature sensor (not shown) that detects the temperature of the housing surface of the drive motor.

- The current If is within the normal range (Ifmin ≤ If ≤ Ifmax: Ifmin is the minimum allowable current value, and Ifmax is the maximum allowable current value). If the current If is less than Ifmin, it means that the drive motors of the cooling fans 14A, 14B are not rotating normally due to a broken wire or other factors, and there is a risk that the inside of the portable housing 23 will not be cooled sufficiently and will become hot. On the other hand, if the current If exceeds Ifmax, excessive current will flow through the drive motors of the cooling fans 14A, 14B due to a short circuit or the like, causing them to go out of control and leading to a breakdown.

It is possible to omit detection of either the rotation speed u or the current If, but detecting both may be beneficial in identifying the cause of an abnormality in the rotation of the cooling fans 14A, 14B more accurately. For example, when the current If exceeds Ifmax and the rotation speed u is umin, it is possible that the drive motor is energized, but the rotation of the fan is forcibly prevented by a foreign object or a malfunction in the transmission system, resulting in an overloaded state. On the other hand, when the current If is less than Imin and the rotation speed u is less than umin, there is a high possibility of a broken wire or a power supply abnormality. When multiple cooling fans are provided as in this embodiment, it is desirable to perform similar monitoring for each cooling fan.

As a simpler form, when simply monitoring whether the cooling fans 14A, 14B are operating, it may not be necessary to configure the cooling fans 14A, 14B as ^I2C devices accompanied by the fan operation monitoring devices 84A, 84B. For example, as shown in Fig. 20, the drive current value SF of the cooling fans 14A, 14B may be converted into a voltage signal by, for example, a shunt resistor 14R, and this voltage signal may be input to the overall control module 9 as a binary detection signal SF indicating the operation/stop of the cooling fans 14A, 14B (in this embodiment, it is input to the extended input/output unit 910).

Returning to FIG. 14, in S2083, the detection log of the battery controller 24 is analyzed.
The conditions for an operation to be judged as normal are as follows:
The remaining battery charge Cr is maintained at or above the specified lower limit Crmin.
- Battery voltage Vb is within the normal range (Vbmin≦Vb≦Vbmax: Vbmin is the minimum allowable battery voltage, and Vbmax is the maximum allowable battery voltage). When the battery voltage Vb is below Vbmin, it may be that the battery is low on charge, or that the battery itself is broken or not installed, causing no battery voltage to be output. When the battery voltage exceeds Vbmax, it may be that a short circuit from another power source has occurred in the battery output circuit or some other problem has occurred.
The battery temperature Tb is equal to or lower than the maximum allowable temperature Tbmax. If the battery temperature Tb exceeds Tbmax, there is a possibility that the battery is overheating due to operation outside the specifications of the rechargeable battery, such as overcharging or over-discharging.

Then, in S2084, it is checked whether all of the above analysis items are normal. If even one is abnormal, the process proceeds to S2085 where an abnormality determination is made. On the other hand, if all analysis items are normal in S2084, the process proceeds to S2086 where a normality determination is made.

Returning to Fig. 13, if the determination in S209 is not abnormal (i.e., if the determination is normal), in accordance with the IP protocol, a start-up instruction command (main body start-up command) for starting the EPC communication firmware (EPC function program) 305a is transmitted to the EPC computer 300 in S210 via the switching hub 11 and the Ethernet bus 32 (LAN, first network) in Fig. 2. The EPC computer 300 receives this command and starts the system, and the EPC communication firmware 305a is started, and if the start-up process is normally completed, returns a start-up completion notification to the overall control module 9. In addition, in S211, a start-up instruction command (main body start-up command) for starting the base station communication firmware (base station function program) 405a is similarly transmitted to the wireless base station computer 400. The wireless base station computer 400 receives this command and starts the system, and starts the base station communication firmware 405a, and returns a start-up completion notification to the overall control module 9. In S212, the overall control module 9 checks whether the EPC computer 300 and the radio base station computer 400 have been started normally based on whether the startup completion notification has been received. If normal startup is confirmed, the process proceeds to S213, where the ^I2C bus master 907 is notified of normal startup. In response to this, the ^I2C bus master 907 transmits an LED lighting command indicating "operation" to the LED driver 17. This causes the LED driver 17 to light up the LED 60B in FIG. 19 (T213).

On the other hand, if an abnormality is determined in S209, the processes of S210 and S211 are not executed. That is, a start instruction command (main body start-up command) is not sent to the EPC computer 300 and the wireless base station computer 400, and the start-up process of the EPC communication firmware 305a and the base station communication firmware 405a, that is, the start-up process of the communication main body including the EPC module 3 and the wireless base station module 4, is not performed. Instead, the process proceeds to S214, and the I ² C bus master 907 is notified of the occurrence of an abnormality. The I ² C bus master 907 receives this and transmits an LED lighting command indicating "abnormality" to the LED driver 17. Specifically, the type of the device in which the abnormality occurred (temperature sensor, cooling fan, and battery) is notified to the I ² C bus master 907 in the abnormality analysis process of FIG. 14, and the I ² C bus master 907 transmits a command to light the LED corresponding to the device in which the abnormality occurred to the LED driver 17.

As a result, for example, if at least one of the cooling fans 14A, 14B experiences the above-mentioned abnormality (one or more), LED 60C in FIG. 19 lights up. Also, if an abnormality occurs in the temperature detected by at least one of the temperature sensors 15A, 15B, LED 60D lights up. Furthermore, if the battery controller 24 detects the above-mentioned abnormality (one or more), LED 60E in FIG. 19 lights up. Note that if there are multiple devices with abnormalities, the corresponding LEDs light up simultaneously. On the other hand, when the above-mentioned abnormality occurs, LED 60B indicating "operation" is not lit.

In the method of the above embodiment, if any abnormality occurs in the operating environment of the communication main unit, the startup process of the communication firmware of the EPC module 3 and the wireless base station module 4 is postponed. For example, if the temperature inside the portable housing 23 rises and the temperature detected by the temperature sensors 15A and 15B becomes abnormal, the operation of the EPC computer 300 or the wireless base station computer 400 is more likely to become unstable, and the wireless base station module 4 and the EPC module 3 may malfunction or act as a source of radio interference for other wireless systems. However, by detecting an abnormality in the operating environment, including an abnormal internal temperature, when the wireless communication unit is started and preventing the start-up of the communication main unit, the above-mentioned problems can be effectively prevented.

On the other hand, even if the temperature detected by the temperature sensors 15A, 15B does not indicate an abnormality, if an abnormality such as a stoppage occurs in the cooling fans 14A, 14B, cooling inside the housing will not progress, which will inevitably lead to temperature abnormalities and similar malfunctions. Therefore, as described above, by acquiring internal temperature information inside the portable housing 23 as well as operating status information of the cooling fan (cooling device), and detecting an abnormality when the wireless communication unit 1 is started up and preventing the start up of the communication main unit, the above malfunctions can be prevented even more effectively.

Although the EPC communication firmware 305a (EPC function program) and the base station communication firmware 405a (base station function program) are stored in a non-volatile memory such as a flash memory whose contents can be rewritten, during operation, some of the stored contents may be changed, including rewriting of setting parameters. Therefore, the occurrence of a temperature abnormality may lead to the destruction of part of the software data due to program runaway, etc. However, by adopting the above method, such destruction of software data can be made less likely. In particular, in the above configuration in which the EPC computer 300 and the wireless base station computer 400 start up together with a single push of the power switch 65, the communication firmware 305a and 405a of both computers can be extremely effectively protected from runaway, destruction, etc. by being equipped with a function that detects the occurrence of an abnormality and stops the start-up as appropriate.

Next, in the method of the above embodiment, the state of the rechargeable battery 21 is also acquired by the battery controller 24 as operating environment information, and if an abnormality occurs, the startup process of the communication firmware of the EPC module 3 of the communication main unit and the wireless base station module 4 is blocked. Specifically, regardless of the detected temperature of the temperature sensors 15A, 15B and the presence or absence of an abnormality in the cooling fans 14A, 14B, if a battery abnormality is detected, the startup process of the communication firmware is blocked.

In an environment where the wireless communication unit 1 operates on a battery, if the EPC communication firmware 305a (EPC function program) and the base station communication firmware 405a (base station function program) attempt to start up when normal power supply from the battery is not possible due to, for example, insufficient remaining power, the software data may be corrupted due to a power cut while the programs are running. Therefore, by preventing the start-up process of the communication firmware when a battery abnormality is detected, this malfunction can be effectively prevented.

In particular, when the receiving voltage information (power receiving state information) indicated by the detection log of the external voltage monitoring unit 16 in FIG. 4 indicates that the external power supply voltage is not being received normally (for example, when it indicates approximately 0 V), the external power supply voltage cannot be used as a backup, so it is particularly desirable to avoid the startup process of the communication firmware of the communication main unit when a battery abnormality is detected. In this case, when the external power supply voltage is being received, it is possible to configure the communication main unit to execute the startup process of the communication firmware while using the external power supply voltage, even if a battery abnormality is detected.

On the other hand, even if the external power supply voltage is being received normally, it is also possible to configure the communication main unit to avoid starting up the communication firmware when a battery abnormality is detected. When the communication main unit is executing the start-up process of the communication firmware while using the external power supply voltage, if the reception of the external power supply voltage is interrupted due to a power outage or the like, if a battery abnormality occurs, it will be impossible to secure the power supply voltage to continue the start-up process of the communication firmware, and there is a possibility that the above-mentioned software data will be destroyed. Therefore, by configuring as described above, it is possible to protect the software data from destruction even in the event of a power outage or the like during the communication firmware start-up process.

Next, Fig. 15 shows a termination sequence of the wireless communication unit 1 under normal conditions by the overall control firmware 905a. In S401, when the power switch 65 in Fig. 2 is pressed while the wireless communication unit 1 is in an activated state, the process proceeds to S402, where termination processing is executed. Fig. 16 shows details of the termination processing, and in S4021, a termination instruction command for terminating (closing) the EPC communication firmware (EPC function program) 305a is transmitted to the EPC computer 300 via the switching hub 11 and the Ethernet bus 32 (LAN, first network) in Fig. 2 according to the IP protocol. In response to this, the EPC computer 300 proceeds to a closing process, closes the EPC communication firmware 305a, and returns a termination completion notification to the overall control module 9 if the termination processing is normally completed. In addition, in S4022, a termination instruction command for terminating (closing) the base station communication firmware (base station function program) 405a is transmitted to the wireless base station computer 400 in the same manner. In response to this, the wireless base station computer 400 transitions to a termination (close) process, closes the base station communication firmware 405a, and returns a termination completion notification to the overall control module 9 if the termination process is completed normally. In S4023, the overall control module 9 checks whether the EPC computer 300 and the wireless base station computer 400 have been terminated normally based on whether the termination notification has been received. If normal termination is confirmed, the process proceeds to S4024, where it notifies the I ² C bus master 907 of normal termination. In response to this, the I ² C bus master 907 transmits an LED turn-on command indicating "termination" to the LED driver 17. This causes the LED driver 17 to turn off the LEDs 60A (power) and 60B (operation) in FIG. 19. Then, the process of the overall control module 9 proceeds to S4025, where the termination process of the overall control computer is performed, and the power is shut off.

On the other hand, if the termination is not normal in S4023 (i.e., if an abnormality is determined), the process proceeds to S4026, where the ^I2C bus master 907 is notified of the occurrence of an abnormality. In response to this in T4026, the ^I2C bus master 907 performs processing to keep LED 60A (power) in Fig. 19 lit and turn off LED 60B (operation). By keeping LED 60A lit, the user can know that the termination process of the communication main unit was not completed normally. In this case, for example, the configuration may be such that forced termination processing is executed by pressing and holding the power switch 65.

Next, once each communication firmware (EPC communication firmware and base station communication firmware) of the communication main unit has started up normally, the overall control firmware 905a continues the process of collecting the above-mentioned operating environment information, and also collects and consolidates the communication logs recorded by the EPC module 3 and wireless base station module 4 that constitute the communication main unit.

Figure 26 shows the flow of communication log recording processing by the EPC module 3 and the wireless base station module 4. The protocol stacks of the EPC module 3 and the wireless base station module 4 have already been explained in Figures 6 and 7, and communication processing is performed by the protocol stack corresponding to each layer. Specifically, primitives are sent and received between adjacent upper and lower layers. The primitives are exchanged each time a communication event occurs, and the contents are uniquely determined by the type of communication event. The primitives exchanged each time a communication event occurs are associated with specific information of the layer involved in the primitive transmission and reception (e.g., the destination layer), specific information of the transmission and reception direction (upper layer or lower layer), and information on the event occurrence time, and this is stored in a buffer in the communication module as a communication log.

As shown in FIG. 2, in the EPC module 3, a communication log buffer 302a is formed in the RAM 302 as the above-mentioned buffer. In addition, in the wireless base station module 4, a communication log buffer 402a is formed in the RAM 402 as the above-mentioned buffer. These buffer memory areas are configured, for example, as FIFO (First In First Out) memory areas, and store a fixed number of communication logs while updating them.

Here, the above communication logs are generated even for communication events when the flow of communication processing is normal, and in a mobile communication system involving a large number of UEs 5, it is not preferable to record all of the communication logs that are generated continuously, since this consumes extra memory area. Therefore, the wireless base station module 4 and the EPC module 3 are equipped with the function of an abnormality log identification unit that identifies whether the communication log generated is an abnormality log or not. In this case, it is desirable to classify the types of communication logs recorded in the communication log buffer 302a or 402a based on their relevance to the occurrence of an abnormality, extract or aggregate communication logs that are closely related to the occurrence of an abnormal state that has a particularly large impact as abnormal logs, and selectively store them in the abnormality log memory. As shown in FIG. 2, the EPC module 3 has an abnormality log memory 302b formed in the RAM 302. The wireless base station module 4 also has an abnormality log memory 402b formed in the RAM 402.

Figure 26 is a flowchart showing the flow of communication log recording processing in the EPC module 3 and the wireless base station module 4. When a communication event is executed in S701, the primitive generated in S702 is acquired as a communication log and stored in the above-mentioned communication log buffer. In S703, it is identified whether or not the communication log is an abnormal log, and if it is an abnormal log, the process proceeds to S704 and the communication log contents are stored in the abnormal log memory. On the other hand, if the communication log is not an abnormal log in S703, S704 is skipped. Thereafter, the above processing is repeated until it is terminated in S705. In other words, the wireless base station module 4 and the EPC module 3 have the function of an abnormal log identification unit that identifies whether or not the communication log being generated is an abnormal log.

Next, the overall control module 9 executes the overall control firmware 905a to selectively acquire an abnormality log indicating that the operation state of the wireless base station module 4 and the EPC module 3 is abnormal, among the communication logs generated by the wireless base station module 4 and the EPC module 3. Specifically, by executing the abnormality log acquisition and aggregation process included in the overall control firmware 905a, the abnormality logs recorded individually by the EPC module 3 or the wireless base station module 4 are periodically acquired and aggregated. The communication process for acquiring the abnormality log is executed according to the IP protocol via the switching hub 11 and the Ethernet bus 32 (LAN, first network) in FIG. 2 (at this time, the Ethernet interface (LAN interface) of the overall control module 9 functions as the communication log acquisition unit). FIG. 27 shows the flow of the process, and in S801, the EPC module 3 and the wireless base station module 4 are requested to transmit the abnormality log. The EPC module 3 and the wireless base station module 4 read the abnormality log stored in the abnormality log memory 302b to 402b and transfer it to the overall control module 9. In addition, the data of the abnormality log that has already been transferred to the overall control module 9 is erased from the abnormality log memory 302b to 402b as needed. The overall control module 9 receives the abnormality log in S802.

As shown in FIG. 2, the overall control module 9 secures a communication log aggregation storage unit 905c in the flash memory 905, and in S803, stores the received abnormal log (communication log) therein (i.e., a function of selectively storing abnormal logs among the communication logs generated by the wireless base station module 4 and the EPC module 3 is realized). FIG. 28 shows an example of an abnormal log type, each of which is associated with an abnormal log code (abnormal log type specific information). Specifically, examples of abnormal log types include protocol error (IV001), transaction service not supported (IV002), receive buffer overflow (IV003), retransmission timeout (IV004), transmission service discarded (IV005), base station system abnormality (IV101), and EPC system abnormality (IV102) (the abnormal log code is in parentheses). For example, an abnormal log related to a retransmission timeout is recorded as an abnormal log that aggregates communication logs related to retransmission control when they are transmitted and received a certain number of times in succession. In addition, the base station system abnormality (IV101) and the EPC system abnormality (IV102) are defined as abnormality logs of the termination target level that are the conditions for executing the abnormal termination process of the communication main body (EPC module 3 and wireless base station module 4).

The results of abnormality determination made using the above-mentioned operating environment information collected using an ^I2C network or the like are also stored in the communication log aggregation storage unit 905c as abnormality logs in a broad sense. In Fig. 28, the corresponding abnormality logs include base station temperature abnormality (temperature abnormality detected by the first temperature sensor 15A, IV201), base station downstream temperature abnormality (temperature abnormality detected by the second temperature sensor 15B, IV202), cooling fan abnormality (IV203), external power supply abnormality (IV204), and battery abnormality (IV205).

FIG. 29 shows an example of the contents stored in the communication log aggregation memory unit 905c, in which the date and time of occurrence of the abnormality log, the address of the node that sent the abnormality log as occurrence location identification information (if the node that sent the abnormality log is the EPC module 3 or the wireless base station module 4, the IP address, and if the node that sent the abnormality log is an ^I2C slave node, the address of the slave node), the type of module or device, and the abnormality log code are associated with each other and stored in chronological order.

All communication logs generated by the EPC module 3 and the wireless base station module 4 may be transferred to the overall control module 9, and the overall control module 9 may execute a process to identify whether the transferred communication logs are abnormal logs or not. However, considering that a new processing load is generated for transferring communication logs to the overall control module 9, it is desirable to perform the identification process separately in the EPC module 3 and the wireless base station module 4, as described above.

Next, Fig. 17 shows the flow of processing by the general control firmware 905a when each communication firmware (EPC communication firmware and base station communication firmware) of the communication main unit starts up normally once and then an abnormality occurs during operation. This processing is repeatedly executed at a predetermined time interval by, for example, timer processing. In S501, the I 2 C bus master 907 is instructed to collect detection logs from the cooling fans 14A, 14B (fan operation monitoring devices 84A, 84B), the temperature sensors 15A, 15B (internal temperature monitoring devices 85A, 85B) and the battery controller 24, and in S502, the detection logs of ^{each device are received from the I 2 C} bus master 907. This step is the same as the processing from S204 to S207 in Fig. 13. Then, in S503, the same abnormality analysis processing as in Fig. 14 is performed. If an abnormality is determined in S505, the process proceeds to S506 and the end processing in Fig. 16 is executed.

The result of the abnormality analysis process in S503 (FIG. 14) is stored in the communication log aggregation storage unit 905c as an abnormality log as described above. In the abnormality analysis process, a warning threshold level, which is a preliminary step to the termination process, may be set for the acquired operating environment information, and a warning judgment may be made based on a comparison with the warning threshold level. For example, in the case of a temperature abnormality, a warning upper limit value dmax' is set as a warning threshold level on the lower side than the upper limit value dmax described above, and a warning judgment is made when the detected temperature d exceeds the warning upper limit value dmax' and falls below the upper limit value dmax (in this case, as described later, the termination process is not performed, and only a warning is issued). The above-mentioned concept of warning judgment can be implemented for other types of operating environment information in the same way, and in that case, the result of the warning judgment is also stored in the communication log aggregation storage unit 905c.

Returning to FIG. 17, if the result of S505 is normal, the process proceeds to S507, where the abnormality logs from the EPC module 3 and base station module 4 are read from the communication log aggregation storage unit 905c and referenced. If an abnormality log with a level set as a target for executing the aforementioned termination process, such as a base station system abnormality (IV101) or an EPC system abnormality (IV102) at the most recent time, is detected in S508, the process similarly proceeds to S506, and the termination process of FIG. 16 is executed.

As described above, if an operating environment abnormality occurs in the communication main unit after the base station communication firmware 405a (base station function program) and the EPC communication firmware 305a (EPC function program) are started up, the power is cut off after the termination process for both firmware is performed, so that software data can be protected from destruction even in the event of the above abnormality.

FIG. 18 shows the flow of processing by the overall control firmware 905a for switching between the external power supply and the battery power supply for the power supply module 22. This processing is also repeatedly executed at a predetermined time interval. In S601, the I ² C bus master 907 is instructed to acquire a detection log related to the receiving voltage from the external voltage monitoring unit 16 (FIG. 4). In S602, the detection log is received from the I ² C bus master 907. In S603, if the detection log indicates that power is being received, the process proceeds to S604, where the I ² C bus master 907 is notified that external power is being received. In response to this, the I ² C bus master 907 transmits a command to turn on the LED indicating "external power being received" to the LED driver 17. As a result, the LED driver 17 turns on the LED 60F (external power supply) in FIG. 19 (T604).

On the other hand, if the detection log does not indicate that power is being received in S603, the process proceeds to S606, where the ^I2C bus master 907 is notified that no external power is being received. The ^I2C bus master 907 receives this and transmits a command to turn off the LED indicating "power being received from an external power source" to the LED driver 17. This causes the LED driver 17 to turn off the LED 60F (external power source) in Fig. 19 (T606). The process then proceeds to S605, where the power source is switched to the rechargeable battery 21.

2, the overall control firmware 905a of the overall control module 9 has a function of creating GUI data for displaying images on the screen of a display device so that the operating state information and operating environment information of the communication main unit can be identified by related components in the portable housing for a terminal node connected to the overall control module 9 via IP based on the contents of the operating environment information being acquired and the stored contents of the communication log aggregation memory unit 905c (GUI data creation unit). Specifically, the GUI data creation unit creates GUI data so that a GUI screen can be displayed by a Web browser on an external terminal device. In addition, a GUI server unit 905b is formed in the flash memory 905, and the above GUI data is stored and held in the GUI server unit 905b so that it can be read and accessed from an external terminal device. Specifically, the GUI data creation unit has the function of displaying battery status information in a GUI, which indicates the operating status of the wireless base station module 4 and EPC module 3 that constitute the communication main body, the operating status of the cooling fans 14A and 14B, the detected temperatures of the temperature sensors 15A and 15B, the power receiving status of the external power source 26 (see FIG. 3) of the power source module 22, and the operating status of the rechargeable battery 21.

As shown in FIG. 2, the terminal nodes that are the targets of GUI display are, for example, an external PC 911 connected to the overall control module 9 via a wired LAN through an Ethernet interface 904, and a UE (mobile terminal device) 5 connected to the overall control module 9 via a wireless LAN through a WiFi module 908. By pre-installing web browser software or a terminal application with a web browser function in these terminal nodes, the above-mentioned GUI display can be displayed on an image display device such as a monitor mounted on the terminal node. In other words, the Ethernet interface 904 and the WiFi module 908 function as a GUI data transmission unit that transmits GUI data held by the GUI server unit 905b to the external PC 911 and the UE 5 (external terminal device).

For example, as shown in FIG. 2, the external PC 911 is equipped with an input unit 912 such as a keyboard or a touch panel, and a monitor 913. With web browser software running, the node specific information (IP address or URL) of the overall control module 9 can be input from the input unit 912, thereby making it possible to access the overall control module 9 via an IP connection. Then, in response to this access, the overall control module 9 distributes GUI data to the external PC 911.

The external PC 911 downloads GUI data from the overall control module 9 (the GUI server section 905b) and displays, for example, a GUI screen G as shown in Fig. 30 on the monitor 913 in a web browser. The GUI screen G has display fields DF4, DF3, DF14A, DF14B, DF15A, DF15B, DF16, and DF24 formed thereon to individually display the operating or detection status of each component or device of the wireless base station module 4, the EPC module 3, the cooling fans 14A, 14B (fan operation monitoring devices 84A, 84B), the temperature sensors 15A, 15B (internal temperature monitoring devices 85A, 85B), the external voltage monitoring section 16, and the rechargeable battery 21 (battery controller 24). The aforementioned GUI data creation unit creates text information TJ indicating the operating status or detection status of each component or device based on the contents of the detection log acquired by the corresponding operating status information acquisition node or the stored contents of the communication log aggregation and storage unit 905c, and displays it in the corresponding display field.

For the wireless base station module 4 and the EPC module 3, when an abnormality log indicating the occurrence of an abnormality is not stored in the communication log aggregation storage unit 905c, information indicating that the communication state is normal (for example, "normal communication in progress") is displayed. Also, when the detection log of the drive state information acquisition node indicates an abnormality or a caution state, or when an abnormality log (including a communication log indicating a caution state) is stored in the communication log aggregation storage unit 905c, the corresponding display field is switched from a normal display state to a caution display state or an abnormal display state. For example, in the example shown in FIG. 31, each display field is displayed in a different color depending on the state (specifically, normal: blue, caution: yellow, abnormal: red, etc.). In addition to or separately from the color of the display field, the display color of the text information TJ may be set to be different depending on the state. In FIG. 31, the cooling fan 14A is stopped and the wireless base station module 4 and the EPC module 3 are performing termination processing, and the corresponding display fields DF14A, DF4, and DF3 are in an abnormal display state.

Figure 32 is a block diagram showing an example of the electrical configuration of UE (mobile terminal device) 5. UE 5 is configured as a smartphone equipped with a microcomputer 100 as the processing main body. Microcomputer 100 is composed of a CPU 101, RAM 102 which serves as a program execution area, ROM 103, input/output unit 104, and bus 106 which interconnects them. In addition, flash memory 105 is connected to bus 106, in which communication firmware 105a for constructing the operating environment of UE 5 and terminal application 105b are installed.

The monitor 109 is connected to the input/output unit 104 via a graphic controller 1091. A touch panel 110, which constitutes an input unit, is superimposed on the monitor 109, and various information required for controlling the operation of the UE5 is input in cooperation with various software operation units (such as buttons and icons: see Figures 13 to 17) displayed on the monitor 109. The touch panel 110 is connected to the input/output unit 104 via a touch panel controller 110A. A camera 111 for taking still images or videos is connected to the input/output unit 104. Furthermore, a wireless communication unit 112 is connected to the bus 106. The UE5 is wirelessly connected to the wireless base station module 4 of the wireless communication unit 1 in Figure 2 via the terminal wireless bearer 57 via the wireless communication unit 112.

As shown in FIG. 2, by connecting the UE 5 to the overall control module 9 via the WiFi module 908 via LAN and launching the terminal application 105b, a GUI screen G similar to that of FIG. 30 can be displayed on the monitor 109 as shown in FIG. 33. This allows a user to easily grasp the current operating status of the wireless communication unit 1 from the GUI screen G by installing the terminal application 105b in the UE 5 that he or she owns, which can be useful for maintenance work and troubleshooting work for the wireless communication unit 1.

In this embodiment, when accessing (logging in) to the GUI server unit 905b from the UE 5 to display the GUI screen G, authentication using a password is required. To enter a password, the password entry screen shown in FIG. 34 is read from the menu of the terminal application 105b, and the password is entered as authentication information in a window 110W using, for example, a soft keyboard 110k displayed on the screen, and the password is wirelessly transmitted to the overall control module 9 by operating a send button (password confirmation operation unit) 110B to execute authentication processing. That is, the overall control firmware 905a of the overall control module 9 realizes the functions of a password reception unit that receives a password entry from an external terminal device, an authentication processing unit that performs authentication processing based on the received password, and an access permission unit that allows the external terminal device to access the GUI server unit only if the result of the authentication processing is positive.

Figure 36 shows the process flow in this case, where UE5 (terminal) launches a terminal application at J101 and calls up a password screen. A password is entered at J102 and transmitted at J103. The overall control module 9 receives this and performs authentication by comparing it with the password registered in the password storage unit 905d of the flash memory 905 at J104. The authentication result is transmitted to the UE5 at J105. If the authentication result is positive at J106, the overall control module 9 is requested to transmit GUI data at J107. The overall control module 9 receives the request and transmits the GUI data to the UE5 at J108. The UE5 uses the GUI data to display a GUI screen on the monitor 109.

Next, the process when the user wants to change the password will be described. In this case, two processes, authentication using the old password and input of the new password, are required, and the following unique security method is adopted to prevent unauthorized password changes by spoofing or remote operation. That is, as shown in FIG. 35, the password change screen shown in FIG. 34 is read from the menu of the terminal application 105b, and the old password is input as authentication information in the window 110W1 using the soft keyboard 110k, and the new password is input in the window 110W2. After that, by operating the send button (password transmission operation unit) 110B, the above two passwords are wirelessly transmitted to the general control module 9 and the authentication process is executed. At this time, the operation of the send button 110B on the UE 5 side is valid only when a specific condition is satisfied between the operation state of the auxiliary operation unit (control switch 66 (FIG. 2) in this embodiment) provided on the portable housing 23 of the wireless communication unit 1.

In this embodiment, specifically, the operation of the send button 110B is considered valid when the control switch 66 is operated at the same time. This method is particularly effective in preventing unauthorized password changes by remote operation, since it requires the operator of the UE 5 to enter the password into the wireless communication unit 1 within reach. That is, the overall control firmware 905a of the overall control module 9 realizes the functions of a password change request acceptance unit that accepts a password change request from an external terminal device, an auxiliary operation unit that is scheduled to be operated when the password change request is accepted, an auxiliary operation unit operation state detection unit that detects the operation state of the auxiliary operation unit when the password change request is accepted, and a password change permission unit that permits the password change only if operation of the auxiliary operation unit is detected when the password change request is accepted.

Figure 37 shows the flow of the password change process in this case, where in J201, the terminal application is launched and the password change screen is called up. In J202, the pre-change password is entered, and in J203, the post-change password is entered, and in J204, the password is transmitted by operating the send button 110B (password change request operation unit). The overall control module 9 receives these passwords and checks the operation state of the control switch 66 at the time of reception in J205. If the operation of the control switch 66 cannot be confirmed in J206, the process proceeds to J209, where the authentication is rejected. On the other hand, if the operation of the control switch 66 can be confirmed, the process proceeds to J207, where the received pre-change password is compared with the password registered in the password storage unit 905d for authentication. In J208, if the authentication result is positive, that is, if the password matches the pre-change password, the process proceeds to J210, where the received post-change password is registered in the password storage unit 905d. The pre-change password in the password storage unit 905d is, for example, overwritten and erased. The authentication result is sent to UE5 at J211. If the result received at J211 is positive, for example, the monitor 109 displays a message indicating that the password change has been completed. On the other hand, if the result is negative, the process returns to J202 and the user re-enters the password.

If the user forgets the password and is unable to log in, for example, a password initialization process is performed (this corresponds to a "password change process" since the registered password is changed). In this password initialization process, for example, a temporary password is issued and notified to the UE5 from the general control module 9 via the WiFi module 908, and the processes of Fig. 35 and Fig. 37 are similarly performed by replacing the "password before change" with the "temporary password" and the "password after change" with the "new password". In addition, a simpler password initialization process may omit the issuance and authentication process of the "temporary password", and allow password initialization (registration of a new password) by pressing the send button 110B (password change request operation unit: in this case, the name may be "initialization button" or the like) on the UE5 side simultaneously with the operation of the control switch 66 (auxiliary operation unit).

Next, the contents stored in the communication log aggregation memory unit 905c in FIG. 2 (see also FIG. 29) can be downloaded as communication log (abnormality log) data in one go by a terminal node such as the external PC 911 or UE 5 mentioned above. By configuring the communication logs (abnormality logs) acquired at each point in the wireless communication unit 1 to be aggregated in the communication log aggregation memory unit 905c of the overall control module 9 and outputted in one go, the communication log (abnormality log) data can be used as diagnostic information (diagnosis data) for the entire wireless communication unit 1, making it easy to analyze trends in malfunctions and identify the causes of failures.

The destination of the communication log data is selected and input on the transfer destination device selection screen of the terminal node (for example, monitor 913 in the case of external PC 913, monitor 109 in the case of UE5) as shown in FIG. 38. In the figure, reference numeral 913A indicates a selection button for UE5 (smartphone, external terminal device), and reference numeral 913B indicates a selection button for USB memory (removable storage device). When UE5 is selected, the communication log data is wirelessly transmitted to UE5 via WiFi module 908 (LAN interface) (function of communication log data transfer control unit). The communication log data is downloaded in UE5, and the contents can be displayed, for example, on monitor 109 (FIG. 32). On the other hand, a USB memory mounting unit 915 (storage device mounting unit) is connected to the bus 906 of the general control computer 900 in FIG. 2, and a USB memory 914 (removable storage device) can be mounted thereon. When the USB memory is selected as the output destination of the communication log data, the USB memory mounting unit 915 is designated as the data transmission destination, and the communication log data is transferred and written to the USB memory 914 mounted therein (communication log data writing control unit). Note that, for example, a USB memory mounted on the external PC 911 may be selected as the output destination of the communication log data by path designation. FIG. 39 is a flowchart showing the flow of the communication log data transfer process in the overall control firmware 905a in this case. In S901, the transfer destination device selection screen of FIG. 32 is displayed. In S902, the output destination device selection input is accepted. In S903, the transfer destination port (or node, path) is specified according to the input contents. In S904, it is confirmed whether the transfer destination device is ready. If the preparation is completed in S905, proceed to S906 and start the transfer of the communication log data. On the other hand, if the preparation is not completed in S905, return to S904 and retry the following process.

The above describes an embodiment of the present invention, but it is merely an example and the present invention is not limited to this.

1 Wireless communication unit 2 MME
3 EPC module 4 Wireless base station module 4a Power semiconductor element 4f Heat dissipation fin 4h Heat sink plate 4k Passage 4p Shielding plate 4s Mounting board 5 UE (mobile terminal)
6 S-GW
7 P-GW
8 Router 9 General control module 11 Switching hub 12 Backplane 13 Control board 14A Cooling fan (cooling device)
14b Base portion 14B Cooling fan (cooling device)
14m Main body 14p Fan rotor 14R Shunt resistor 14s Airflow guide plate 14sf Mounting arm 14t Fastening member 15A Temperature sensor 15B Temperature sensor 16 External voltage monitoring unit 17 LED driver 21 Rechargeable battery 22 Power supply module 22c Capacitor 22i Coil 22s Mounting board 23 Portable housing 23f Air filter 23w Airflow outlet 23y Airflow inlet 24 Battery controller (slave node)
25 AC/DC converter 26 External power supply 31A External port group 31B External port group 32 Ethernet bus (first network)
52 I2C bus (second network)
57 Radio bearer 60 LED (abnormality notification unit)
62 Current adjustment resistor 65 Power switch 66 Control switch 67 Resistor 84A Fan operation monitoring device (cooling device operation status information acquisition node, slave node)
84B Fan operation monitoring device (cooling device operation status information acquisition node, slave node)
85A Internal temperature monitoring device (internal temperature information acquisition node, slave node)
85B Internal temperature monitoring device (internal temperature information acquisition node, slave node)
100 Microcomputer 101 CPU
102 RAM
104 Duplexer 105 Flash memory 105a Communication firmware 105b Terminal application 106 Bus 109 Monitor 110 Touch panel 110B Send button (password confirmation operation section)
110k Soft keyboard 110W1, 110W2 Window 111 Camera 112 Wireless communication unit 231 Cooling air circulation gap 232 Support section 233 Bottom support plate 234 Intermediate support plate (module assembly support plate)
235 Support part 236 Substrate support frame 300 EPC computer 301 CPU
302 RAM
302a: communication log buffer 302b: error log memory 303: mask ROM
304 Ethernet interface 305 Flash memory 305a EPC communication firmware 305b MME entity 305c S-GW entity 305d P-GW entity 305e Software router 306 Internal bus 400 Radio base station computer 401 CPU
402 RAM
402a: communication log buffer 402b: error log memory 403: mask ROM
404 Duplexer 405 Flash memory 405a Base station communication firmware 406 Internal bus 408 Ethernet interface 412 Wireless communication unit 413 Antenna 900 General control computer 901 CPU
902 RAM
903 Mask ROM
904 Ethernet interface (first interface, main body startup command transmission unit)
905 Flash memory 905a Overall control firmware (operating environment abnormality determination unit, operating abnormality response processing unit)
905b GUI server unit 905c Communication log aggregation storage unit 905d Password storage unit 906 Internal bus 907 I2C bus master (second interface, master node)
907s Board 908 WiFi module 909 Input/output unit (main start signal receiving unit)
910 Expansion input/output unit (I/O)
911 External PC
912 wireless communication unit 913 monitor 914 USB memory 915 USB memory mounting unit 1091 graphic controller 1100 data frame 1101 address field 1102 R/W field 1104 data field 1300 IP packet 1301 IP header 1301a source address 1301b destination address 1301c ToS field 1302 payload

Claims (9)

a communication main unit including a wireless base station module that performs wireless communication based on 3GPP specifications with a mobile terminal, and an EPC (Evolved Packet Core) module that is wired connected to the wireless base station module and performs upper network control for the wireless base station module;
a power supply module for supplying an operating voltage to the communication main unit;
a portable housing that integrally houses the communication main body and the power supply module;
an overall control module provided within the portable housing and connected to the communication main unit by wire, the overall control module including: a communication log acquisition unit that acquires, by communication, a communication log generated in association with execution of wireless communication processing by the wireless base station module and the EPC module from the wireless base station module and the EPC module as operation status information of the communication main unit; a communication log aggregation storage unit that collectively stores the acquired communication log from the wireless base station module and the communication log from the EPC module; and a communication log storage content output unit that outputs communication log data stored in the communication log aggregation storage unit ;
A wireless communication unit characterized in that the communication log aggregation and memory unit selectively stores abnormality logs from among the communication logs generated by the wireless base station module and the EPC module, the abnormality logs indicating that the operating status of the wireless base station module and the EPC module is abnormal. The wireless base station module and the EPC module are each provided with an abnormality log identification unit that identifies whether the communication log to be generated is the abnormality log, and an abnormality log transfer unit that transfers the abnormality log identified for the overall control module to the overall control module,
2. The wireless communication unit according to claim 1 , wherein the communication log acquisition section of the general control module acquires the abnormality log transferred from the abnormality log transfer section as the communication log. a communication main unit including a wireless base station module that performs wireless communication based on 3GPP specifications with a mobile terminal, and an EPC (Evolved Packet Core) module that is wired connected to the wireless base station module and performs upper network control for the wireless base station module;
a power supply module for supplying an operating voltage to the communication main unit;
a portable housing that integrally houses the communication main body and the power supply module;
an overall control module provided within the portable housing and connected to the communication main unit by wire, the overall control module including: a communication log acquisition unit that acquires, by communication, a communication log generated in association with execution of wireless communication processing by the wireless base station module and the EPC module from the wireless base station module and the EPC module as operation status information of the communication main unit; a communication log aggregation storage unit that collectively stores the acquired communication log from the wireless base station module and the communication log from the EPC module; and a communication log storage content output unit that outputs communication log data stored in the communication log aggregation storage unit;
A wireless communication unit comprising an operating environment information acquisition unit that acquires operating environment information of the communication main unit within the portable housing, and the overall control module is provided with an operating environment abnormality determination unit that determines whether an operating environment abnormality has occurred in the communication main unit based on the operating environment information, and the communication log aggregation and memory unit also stores the abnormality determination result made by the operating environment abnormality determination unit. 4. The wireless communication unit according to claim 3 , wherein the operating environment information acquisition section acquires operating environment information of the communication main body section in the portable housing, the operating environment information including internal temperature information of the portable housing. 5. The wireless communication unit of claim 4, further comprising a cooling device for cooling the internal space of the portable housing, and the operating environment abnormality determination unit determines that an operating environment abnormality has occurred when at least one of the following is true: operating status information of the cooling device indicates an operating abnormality of the cooling device, or internal temperature information of the portable housing exceeds a limit temperature. A wireless communication unit as described in any one of claims 3 to 5, wherein a rechargeable battery is provided to supply a battery voltage to the power supply module, the operating environment information acquisition unit acquires the operating environment information which further includes information relating to the charging state and operating state of the rechargeable battery as battery status information, and the operating environment abnormality determination unit determines that an operating environment abnormality has occurred when the remaining battery charge reflected in the battery status information falls below a threshold value. The wireless communication unit of claim 6, wherein the power supply module is provided with an external power supply voltage receiving unit that receives an external power supply voltage, the operating environment information acquisition unit acquires the operating environment information that further includes power receiving status information of the external power supply voltage receiving unit, and the operating environment abnormality determination unit determines that an operating environment abnormality has occurred when the remaining battery charge reflected in the battery status information falls below a threshold value when the power receiving status information indicates that the external power supply voltage is not being received. a storage device mounting section that is connected to the overall control module and to which a removable storage device is attached;
8. The wireless communication unit according to claim 1 , further comprising: a communication log data writing control unit that writes the communication log data output by the communication log memory content output unit to the removable memory device via the memory device mounting unit. A wireless communication unit as described in any one of claims 1 to 8, wherein the overall control module is provided with a LAN interface for connecting an external terminal device to a LAN via a wired or wireless manner, and a communication log data transfer control unit for transferring the communication log data output by the communication log memory content output unit to the external terminal device via the LAN interface.

Images