JP2014209676A - Communication device, communication method, and radio communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To avoid load concentration to a management server by efficiently processing a large amount of control signals transmitted by a large amount of terminals for an M2M use.SOLUTION: In a radio communication network that exchanges control signals for authentication or the like between a radio terminal and a management server via a base station, an M2M gateway 13 is installed between the terminal and the base station or between the base station and the management server. The M2M gateway 13 waits for data transmission requests from other terminals with the same use as a first terminal triggered by a data transmission request from the first terminal, after the elapse of an allowable certain period, transmits the data transmission requests in bulk to the base station or the management server, thereby reduces the exchange of control signals among the M2M gateway and the base station and the management server compared with the case where the requests are serially processed at the time of request from each terminal, and reduces a processing load on the management server.

Description

  The present invention relates to a communication apparatus and method, and a wireless communication system, and in particular, includes a terminal using a mobile network, an M2M (Machine to Machine) gateway that performs processing related to control signals thereof, a base station, and a management server. The present invention relates to a network control technology for M2M.

  In fields such as energy management, environmental monitoring, smart cities, smart communities, and smart mobility, the use of information collected from various devices scattered in social infrastructure, processing, and feeding back the results to social infrastructure will expand in the future. Expected. In this application, it is the M2M network that collects information from devices scattered in social infrastructure and transmits feedback information.

  In general, a mobile network of a communication carrier is often used for the M2M network. This is because it is costly to construct a wired network as a private network in various social infrastructure applications (eg, power, railway, energy management). Therefore, it is considered that mobile terminals are installed in a huge amount of devices scattered in the social infrastructure and connected to the M2M network which is a mobile network.

  However, the devices scattered in the social infrastructure perform communication for aggregating information periodically according to the purpose of use. For example, in a smart meter (electric power meter having a function of transmitting a meter reading value by communication) in the power field, it is conceivable to transmit the meter reading value to a data center of an electric power company every 30 minutes. Considering the example of a domestic power company, there are tens of millions of subscribers in the jurisdiction, so if all the electricity meters are replaced with smart meters and all of them communicate using the mobile network, every 30 minutes It is assumed that tens of millions of transmission start processes (call processes) occur almost simultaneously for the transmission of a very small meter reading value (about 200B: estimated). Call processing is established by a plurality of exchanges (control signals) between the management server of the mobile network and the mobile terminal attached to the smart meter, and thereafter data communication becomes possible. For this reason, a large amount of control signals may need to be exchanged for very little data communication. In fact, in the current mobile network, as seen in the failure of NTT Docomo's smart phone provider service sp mode that occurred on 'November 12th, there are cases where failures occur due to the simultaneous start of communication by many terminals. stay up.

  As a first conventional technique, Patent Document 1 shown below provides a method for efficiently managing MTC terminals on the assumption that the number of MTC (Machine Type Communication) terminals is enormous. Here, in the MTC gateway, the timing of intermittent communication related to paging of the MTC terminal, etc. is held, and an operation corresponding to the DRX cycle of the terminal is performed, and an operation of returning an ACK on behalf of the M2M in order to reduce the delay time. Further, the control signal can be reduced by connecting the MTC gateway to the base station as a representative of the terminal.

  Further, as a second conventional technique, Patent Document 2 shown below is an invention for performing fairness of communication opportunities between a plurality of portable terminals for each packet from each terminal. Here, a control server that caches terminal location information and route information is arranged above a plurality of base stations. In addition, the transmission amount per unit time is controlled and smoothed by performing transmission control based on the cache for each packet from the terminal.

JP 2012-124603 A JP 2009-206805 A

In the first prior art, when the control signal with the terminal is reduced by the MTC gateway, it is during communication from the base station to the terminal by paging, and it is difficult to adapt to the information collection system as seen in M2M. It is done.
In the second prior art, no reference is made to the control signal, and temporary information such as location information of the terminal is recorded in the gateway server in order to ensure fairness of data traffic between the M2M terminals. For this reason, it is considered that the control signal generated by the connection from the M2M terminal or the like cannot be reduced. As described above, according to the conventional technology, data leveling with respect to an increase in traffic due to M2M and management efficiency of M2M terminals connected in large quantities based on identifiers of connected terminals are achieved. For this reason, the subject that the process of the control signal emitted from a terminal concentrates on a management server remains.

  Therefore, in view of the above points, the present invention provides a communication device and method for efficiently processing a control signal emitted from a terminal, and a wireless communication system, focusing on the characteristics of a method for using a terminal for M2M use. For the purpose.

According to the first solution of the present invention,
A communication device,
For each use or application, a first list that stores one or more terminal IDs and an upper limit of waiting time;
Upon receipt of a data transmission request including a terminal ID from a terminal, one or a plurality of data including a terminal ID from one or a plurality of other terminals with the same use or application as the terminal is referred to the first list. Waiting for a transmission request, and for each use or application, after the elapse of the upper limit value stored in the first list, an aggregated data transmission request in which a plurality of data transmission requests are collected is used for authentication of the plurality of terminals. A processing unit to transmit;
A communication device is provided.

According to the second solution of the present invention,
A communication method in a communication device,
The communication device
When receiving a data transmission request including a terminal ID from a terminal, for each use or application, refer to the first list storing one or more terminal IDs and an upper limit value of a waiting time,
Waiting for one or more data transmission requests containing terminal IDs from one or more other terminals of the same application or application as the terminal,
For each use or application, after elapse of the upper limit value stored in the first list, the aggregate data transmission request including a plurality of the data transmission requests is transmitted for authentication of the plurality of terminals. A communication method is provided.

According to the third solution of the present invention,
A wireless communication system,
A communication device installed between a terminal and a base station or between the base station and a management server, for authentication of the terminal between the terminal and the management server via the base station Exchange signals,
The communication device
For each use or application, a first list that stores one or more terminal IDs and an upper limit of waiting time;
Upon receipt of a data transmission request including a terminal ID from a terminal, one or a plurality of data including a terminal ID from one or a plurality of other terminals with the same use or application as the terminal is referred to the first list. Waiting for a transmission request, and for each use or application, after the elapse of the upper limit value stored in the first list, an aggregated data transmission request in which a plurality of data transmission requests are collected is used for authentication of the plurality of terminals. A processing unit to transmit;
A wireless communication system is provided.

  Advantageous Effects of Invention According to the present invention, it is possible to provide a communication apparatus and method and a wireless communication system for efficiently processing a control signal emitted from a terminal, paying attention to characteristics of a method for using a terminal for M2M use.

1 is a system configuration diagram according to a first embodiment of the present invention. It is a block diagram of an M2M gateway. It is a figure which shows the flow at the time of the data communication in the mobile network of related technology. It is a figure which shows the flow at the time of the data communication in 1st Example of this invention. It is a figure explaining the structural example of the terminal profile list which a M2M gateway holds in a local database. It is a figure explaining the structural example of the data transmission request list classified by use which a M2M gateway hold | maintains in a local database. It is a figure which shows the processing flow in an M2M gateway. It is a system block diagram by the 2nd Example of this invention. It is a figure which shows the flow at the time of the data communication in the 2nd Example of this invention.

A. Overview

In this embodiment, in a mobile network that exchanges control signals for authentication and the like from a wireless terminal via a base station, between the terminal and the base station, or between the base station and the management server M2M gateway installed between the two. The M2M gateway has a list of terminals connected to the base station in an attached local database, and the list is used for transmitting usage (application), communication cycle, and data transmission request as M2M for each terminal. The upper limit value of the waiting time is described. The M2M gateway refers to the list when receiving a data transmission request from the first terminal, and waits for a data transmission request from another terminal of the same use as the first terminal. The M2M gateway makes a data transmission request to the base station or the management server after elapse of an allowable fixed period (upper limit value), so that the M2M gateway and the base station perform processing sequentially at the time of request from each terminal. It is possible to reduce the exchange of control signals between the management servers or between the M2M gateway management servers and reduce the processing load on the management server.
In addition, although an example in which a mobile terminal is used as a terminal will be described, the present invention and this embodiment can be applied to an appropriate terminal such as a wireless terminal.

Embodiments of the present invention will be described below with reference to the drawings.

B. First embodiment

1. system

FIG. 1 is a system configuration diagram according to a first embodiment of the present invention.
In FIG. 1, a mobile terminal 12 connected to a device 11 for M2M use (for example, a smart meter) is connected to an M2M gateway 13 and a base station 14 via a mobile carrier's mobile network. The base station 14 is connected to a management server 15 serving as an exit from the mobile network to the general network, and communicates with the communication destination 16 (for example, a data center of an electric power company collecting smart meter data) via the general network. Connected. Examples of communication standards used in mobile networks include third generation (3G) UMTS (Universal Mobile Telecommunication System), fourth generation (4G) LTE (Long Term Evolution), and the like. In this embodiment, the mobile terminal 12 and the M2M gateway 13 communicate with each other via a mobile network. However, for example, a wireless LAN (Local Area Network) represented by IEEE 802.11 or IEEE 802.15.4 is used. Extra small radio represented by the above may be used.

FIG. 2 is a block diagram showing an embodiment of the M2M gateway. In the figure, M2M gateways 13 and 24 comprise a first network communication interface (I / F) 81 and a second network communication I / F 82, and a central processing unit (connected to an internal bus 83 connecting them) A central processing unit (CPU) 84, a timer 85, a calculation memory (local database) 86 as a storage unit, and a program storage memory 87 as a storage unit for storing a program executed by the CPU 84 are provided. Here, in the first embodiment, the first network communication interface 81 corresponds to the mobile terminal 12, and the second network communication interface 82 corresponds to the communication interface with the base station 14. In the second embodiment to be described later, the first network communication interface 81 corresponds to a communication interface with the base station 23, and the second network communication interface 82 corresponds to a communication interface with the management server 25. The various lists to be described in detail may be stored and stored in either the calculation memory 86 or the program storage memory 87 constituting the storage unit. The program storage memory 87 includes a function 88 for waiting for a data transmission request, details of which will be described later with reference to FIG. 6, a function 89 for relaying an authentication response from the base station 14 (or the management server 25), and data communication. Each program for realizing the function 810 or the like for relaying data is sometimes stored. On the other hand, the computing memory 86 is provided with areas such as a terminal profile list 811 described later in FIG. 5A and an application-specific data transmission request list 812 described later in FIG. 5B according to the execution status of each program. As will be described later with reference to FIG. 6, the timer 85 includes a plurality of use-specific waiting timers 813 and a time measurement function.

2. Action

(1) Operation Example of Configuration of Related Technology FIG. 3 is a diagram illustrating a flow at the time of data communication in the mobile network of the related technology.
As shown in FIG. 3, in the related art mobile network, when it is desired to perform data transmission from the mobile terminal A, the mobile terminal A transmits a data transmission request including a terminal ID and transmission destination identification information to the base station ( 31). Upon receiving the data transmission request, the base station further transfers it to the management server (32). Based on the data transmission request or the like, the management server refers to the attached common database 33, authenticates the transmission source (mobile terminal A) from the terminal ID, specifies the transmission destination (power company data center, etc.) IP address, transmission source The processing such as specifying the communication path from the destination to the destination is performed (34). In the common database 33, terminal setting information, location information, billing information, and the like can be set in advance. The management server returns an authentication response and a response such as a data communication route (route information) to the base station (35). The base station further transfers it to the portable terminal A (36). After receiving the response, the portable terminal A starts data communication with a transmission destination (such as a power company data center) (37).

  The mobile terminal may not include the transmission destination identification information in the data transmission request. In addition, the management server may not perform processing such as identification of a transmission destination (such as a data center of a power company) IP address, identification of a communication path from the transmission source to the transmission destination, and a route in response. Information may not be included.

It should be noted that once the above-described authentication flow is performed, continuous data transmission is possible. However, when the time during which data is not transmitted has exceeded a certain time (T_ndata), the above-mentioned authentication becomes invalid and data is transmitted again. When attempting transmission, it is necessary to repeat the above flow from the beginning. Although the setting of the value of T_ndata differs depending on the communication carrier, many are on the order of several seconds to several minutes. As in the case of the smart meter described above, for example, when the meter reading value is sent every 30 minutes to the data center of the electric power company or the like, the transmission interval is longer than T_ndata. It is assumed that it is necessary to start from the beginning. Further, as described above, even when the number of M2M-use terminals is very large, it is assumed that the entire flow needs to be repeated N times for N terminals. The problem is that the band of the mobile network is compressed by the exchange of such control signals, which may interfere with data communication of general users.

(2) Operation Example by System Configuration of First Embodiment FIG. 4 is a diagram showing a flow at the time of data communication in the first embodiment of the present invention.
As shown in FIG. 4, when the M2M gateway 13 described above with reference to FIG. 1 receives the data transmission request 41 including the terminal ID and the destination identification information from the portable terminal A, it is stored in the attached local database 86. Referring to the terminal profile list, the terminal waits for a data transmission request from another terminal based on the list of belonging terminal IDs belonging to the same application as the terminal (43). Specific contents of the waiting operation will be described below.

FIG. 5A is a diagram for explaining a configuration example of the terminal profile list 811 held in the local database 86 by the M2M gateway 13.
As shown in FIG. 5A, the terminal profile list 811 includes, for each communication use of the M2M terminal, the belonging terminal IDs 503 (A in the present embodiment) of all mobile terminals that are installed under the base station and operate normally. , B, etc.) are registered. In the terminal profile list 811, for each application, a number 501, an application 502, a communication cycle 504 of a data transmission request transmitted by each mobile terminal, and a plurality of data transmission requests from the M2M gateway to the management server are collected. The upper limit value 505 of the waiting time until transmission is also registered. Note that the data such as the number 501, the application 502, the upper limit value 505, and the like are examples, and appropriate values can be registered in advance. Although “application 502” is mainly described as an example, the present invention is not limited to this, and other appropriate types such as an application can be used.

FIG. 5B is a diagram illustrating a configuration example of the use-specific data transmission request list 812 held in the local database 86 by the M2M gateway 13.
As shown in FIG. 5B, one or a plurality of usage-specific data transmission request lists 812 are provided for each usage, and usage 511 is described at the top of each list. The list includes a registered terminal ID 512 that stores the terminal ID that received the data transmission request during the meeting, and a registration time 513 in the list.

FIG. 6 is a diagram showing a processing flow in the M2M gateway 13.
As shown in FIG. 6, the M2M gateway 13 always waits for a data transmission request from the subordinate mobile terminal 12 (61). For example, when the CPU 84 receives a data transmission request including the terminal ID from the portable terminal A via the first network communication I / F 81 (62), the CPU 84 stores the terminal profile stored in the attached local database 86. With reference to the list 811, according to the terminal ID, a list of affiliated terminal IDs 503 registered for each usage is searched to identify the usage to which the mobile terminal belongs (63). Next, the CPU 84 confirms whether or not the use-specific data transmission request list 812 of the use to which the mobile terminal specified earlier belongs is already registered in the attached local database 86 (64). When the registration is in the local database 86, the CPU 84 adds the terminal ID of the portable terminal to the registered terminal ID 512 in the use-specific data transmission request list 812 for the purpose to which the portable terminal belongs, and sets the timer 85 to the timer 85. The time when the terminal ID is added is registered (65) at the registration time 513, and the process returns to the standby state (61). On the other hand, if the application-specific data transmission request list 812 for the application to which the mobile terminal identified earlier is not registered in the local database 86 attached at step 64, the CPU 84 is assigned to the mobile terminal. The application-specific data transmission request list 812 is newly registered in the local database 86. Here, the CPU 84 registers the usage specified in step 63 in the usage 511 in the list and the terminal ID of the terminal in the registration terminal ID 512. The CPU 84 refers to the timer 85 and registers the registration time 513. To do. The CPU 84 extracts the upper limit value 505 of the waiting time for the use from the terminal profile list 811, sets the upper limit value as the waiting time timer 813 for each use, and starts measurement (66).

The CPU 84 of the M2M gateway 13 manages the waiting time timer 813 for each use in a waiting state, and when the timer for any use exceeds the upper limit value (67), it is added to the use-specific data transmission request list 812 for that use. The data transmission requests for the terminals described at that time are combined into one data transmission request (aggregated data transmission request), and the data is transmitted to the base station 14 or the management server 25 via the second network communication I / F 82. (68). Note that the upper limit value 505 of the waiting time can be set in advance with a minimum margin so that data transmission can be completed before exceeding the allowable delay of the application to which the mobile terminal belongs. In addition, the aggregate data transmission request can be one data including a plurality of terminal IDs.

  Returning to FIG. 4, the operation after step 44 will be described. The operation in step 68 in FIG. 6 corresponds to step 44 in FIG. As described above, when the use-specific waiting time timer 813 exceeds the upper limit value, the CPU 84 determines the terminal IDs of one or a plurality of terminals (mobile terminal A and mobile terminal B in this embodiment) received during the period, and The data transmission requests including the transmission destination identification information are collected into a single message (aggregated data transmission request) and transmitted to the base station 14 (44). The base station 14 transfers it to the management server 15 (45). When the management server 15 receives the data transmission request, the management server 15 refers to the attached common database 46, and based on each terminal ID and transmission destination identification information, the authentication of the transmission source and the transmission destination IP address for each of the terminal A and the terminal B Processing such as identification and identification of a route during data communication from the transmission source to the transmission destination is performed (47). In the common database 46, terminal setting information, location information, billing information, and the like can be set in advance. Thereafter, the management server 15 returns the authentication response of the mobile terminals A and B and information such as the data communication path (route information) to the base station 14 (48). Upon receiving the response, the base station 14 further forwards it to the M2M gateway 13 (49). The M2M gateway 13 transfers the collectively received responses to the mobile terminal A and the mobile terminal B, respectively (50, 51). After receiving the response, the mobile terminal A and the mobile terminal B start data communication with the communication destination 16 (such as a data center of an electric power company) based on the information (52).

The mobile terminal 12, the M2M gateway 13, and the base station 14 may not include the transmission destination identification information in the data transmission request. Further, the management server 15 may not perform processing such as identification of a transmission destination (such as a data center of a power company) IP address, identification of a communication path from the transmission source to the transmission destination, or the like. 15, the base station 14 and the M2M gateway 13 may not include the route information in the response. The aggregate data transmission request may be composed of a plurality of messages instead of one message.

According to the present embodiment, the exchange of control signals between the mobile terminal and the management server can be reduced, and the processing load concentration of the management server can be avoided. In addition, as in this embodiment, by processing data transmission requests of a plurality of terminals belonging to the same application collectively, compared to the case of sequentially processing at the time of request from each terminal, between the M2M gateway ⇔ base station ⇔ management server It is possible to reduce the exchange of control signals and reduce the processing load on the management server.

C. Second embodiment

FIG. 7 is a system configuration diagram according to the second embodiment of the present invention.
In FIG. 7, a mobile terminal 22 connected to a device 21 for M2M use (for example, a smart meter) is connected to a base station 23 via a mobile carrier network (for example, 3G such as UMTS, 4G such as LTE). Connected. The base station 23 is connected to a management server 25 serving as an exit from the mobile network to the general network via the M2M gateway 24, and a communication destination 26 (for example, a data center of a power company) via the general network. Connected to. In this embodiment, the base station 23, the M2M gateway 24, and the management server 25 are connected in order. However, the base station 23 and the M2M gateway 24 may be mounted as separate hardware in the same device. The software may be implemented as separate software that operates on the same hardware.

In the second embodiment, the configuration diagram of the M2M gateway shown in FIG. 2 and the lists shown in FIGS. 5A and 5B are the same as those in the first embodiment. Further, regarding the processing flow in the M2M gateway 13 shown in FIG. 6, the transmission source of the data transmission request is changed from the mobile terminal 12 to the base station 23, and the transmission destination of the data transmission request is changed from the base station 14 to the management server 25. Is common to the first embodiment.

FIG. 8 is a diagram showing a flow during data communication in the second embodiment of the present invention.
As shown in FIG. 2 described above, in the second system configuration, the M2M gateway 24 is located between the base station 23 and the management server 25. Therefore, communication between the base station 23 and the M2M gateway 24 is exchanged for each terminal. Only the communication between the M2M gateway 24 and the management server 25 is exchanged for a plurality of terminals.

The mobile terminal 12, the M2M gateway 13, and the base station 14 may not include the transmission destination identification information in the data transmission request. Further, the management server 15 may not perform processing such as identification of a transmission destination (such as a data center of a power company) IP address, identification of a communication path from the transmission source to the transmission destination, or the like. 15, the base station 14 and the M2M gateway 13 may not include the route information in the response.

According to the present embodiment, the exchange of control signals between the mobile terminal and the management server can be reduced, and the processing load concentration of the management server can be avoided. In addition, as in this embodiment, by collectively processing data transmission requests of a plurality of terminals belonging to the same application, the control signal between the M2M gateway and the management server is compared with the case of sequentially processing at the time of request from each terminal. It is possible to reduce communication and reduce the processing load on the management server.

D. Appendix

In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

11, 21 M2M devices 12 and 22 such as meters Mobile terminals 13 and 24 M2M gateways 14 and 23 Base stations 15 and 25 Management servers 16 and 26 Communication destination (data center of electric power company, etc.)
31, 32, 41, 42 Data transmission request 33, 46 Common database 34, 47 Source authentication processing 35, 36, 50, 51 Authentication response, route information 37, 52 Data communication 43 Waiting based on the belonging terminal ID, etc. Process 44, 45 (Summary for multiple terminals) Data transmission request 48, 49 (Summary for multiple terminals) Authentication response, route information 61 Standby state 62 Data transmission request reception 63 List search and application specification 64 Data transmission request list by application Retrieval of data 65 Addition to data transmission request list by usage 66 New registration of data transmission request list by usage 67 Timer measurement 68 Data transmission request for multiple terminals 86 Local database

Claims (15)

A communication device,
For each use or application, a first list that stores one or more terminal IDs and an upper limit of waiting time;
Upon receipt of a data transmission request including a terminal ID from a terminal, one or a plurality of data including a terminal ID from one or a plurality of other terminals with the same use or application as the terminal is referred to the first list. Waiting for a transmission request, and for each use or application, after the elapse of the upper limit value stored in the first list, an aggregated data transmission request in which a plurality of data transmission requests are collected is used for authentication of the plurality of terminals. A processing unit to transmit;
A communication device comprising:
The communication device according to claim 1,
When the processing unit accepts the data transmission request from the terminal, the processing unit refers to the first list, specifies the usage or application to which the terminal belongs, according to the terminal ID,
The processing unit registers, for each use or application, the terminal ID of the terminal and the registration time at which the data transmission request is received,
The processing unit compares the elapsed time from the registration time with the upper limit value for each use or application, and collects the plurality of data transmission requests received from the terminals of the plurality of registered terminal IDs, and sends the aggregated data transmission request. A communication device characterized by being created.
The communication device according to claim 2,
A second list for storing the terminal ID and the registration time for each use or application;
The processing unit stores the terminal ID of the terminal that received the data transmission request during the waiting time and the received registration time in the second list for each use or application,
The processing unit obtains an upper limit value of the waiting time for each use or application from the first list, starts measurement by setting the upper limit value as a waiting time timer for each use,
When any of the use-specific queuing timers exceeds the upper limit, the processing unit collects data transmission requests of terminals having a plurality of terminal IDs registered in the second list of the use or application, A communication apparatus that creates and transmits the aggregated data transmission request including a plurality of terminal IDs registered in the second list.
The communication device according to claim 3,
When the processing unit receives the data transmission request from the terminal, the processing unit checks whether the second list of uses or applications that are the same as the use or application of the terminal is already registered,
If already registered, the processing unit registers a terminal ID and a registration time in the second list for each use or application,
On the other hand, if there is no registration, the processing unit newly registers the second list of usages or applications of the terminal, and starts measurement by the usage-specific waiting timer according to the upper limit value. Communication device.
The communication device according to claim 1,
The processing unit transmits the aggregated data transmission request to a management server for executing authentication of a transmission source using a terminal ID.
The communication device according to claim 5, wherein
The processing unit receives each authentication result of the plurality of terminals determined by the management server based on the aggregated data transmission request from the management server, and transmits the authentication result to each of the plurality of terminals. A communication device characterized by the above.
The communication device according to claim 1,
The communication apparatus is characterized in that the upper limit value is set in advance to a value at which transmission of the aggregate data transmission request can be completed before an allowable delay for transmitting a data transmission request for each application or application is exceeded.
The communication device according to claim 1,
The communication device, wherein the data transmission request and the aggregated data transmission request include transmission destination identification information.
The communication device according to claim 8, wherein
The management server receives the route information of each terminal obtained based on the destination identification information included in the aggregated data transmission request together with the authentication result, and transmits the route information and the authentication result to each of the terminals. A communication device.
The communication device according to claim 1,
The communication apparatus is provided between the terminal, which is a wireless terminal, and the base station, or between the base station and the management server.
A communication method in a communication device,
The communication device
When receiving a data transmission request including a terminal ID from a terminal, for each use or application, refer to the first list storing one or more terminal IDs and an upper limit value of a waiting time,
Waiting for one or more data transmission requests containing terminal IDs from one or more other terminals of the same application or application as the terminal,
For each use or application, after elapse of the upper limit value stored in the first list, the aggregate data transmission request including a plurality of the data transmission requests is transmitted for authentication of the plurality of terminals. Communication method.
A wireless communication system,
A communication device installed between a terminal and a base station or between the base station and a management server, for authentication of the terminal between the terminal and the management server via the base station Exchange signals,
The communication device
For each use or application, a first list that stores one or more terminal IDs and an upper limit of waiting time;
Upon receipt of a data transmission request including a terminal ID from a terminal, one or a plurality of data including a terminal ID from one or a plurality of other terminals with the same use or application as the terminal is referred to the first list. Waiting for a transmission request, and for each use or application, after the elapse of the upper limit value stored in the first list, an aggregated data transmission request in which a plurality of data transmission requests are collected is used for authentication of the plurality of terminals. A processing unit to transmit;
A wireless communication system.
The wireless communication system according to claim 12,
The terminal is connected to the communication device via a wireless communication network;
The communication device is connected to the base station via a wireless communication network;
The base station is connected to the management server, and is connected to a communication destination device via a destination network.
The wireless communication system according to claim 12,
The terminal is connected to the base station via a wireless communication network;
The base station is connected to the management server via the communication device,
The wireless communication system, wherein the management server is connected to a communication destination device via a communication network.
The wireless communication system according to claim 12,
The base station and the communication device are separate devices, mounted as separate hardware in the same device, or mounted as separate software that operates on the same hardware. A wireless communication system.

Images