JP6340345B2 - Network system, configuration method thereof, and program - Google Patents

Description

  The present invention relates to a platform network system for providing M2M (Machine to Machine) service using telecommunications technology, a configuration method thereof, and a program.

  IP (Internet Protocol) represented by the Internet is widely used. On the other hand, in the field of sensor networks, non-IP protocols represented by Zigbee (registered trademark) are becoming widespread, and requests for connection to the cloud are increasing.

  In order to connect and manage these non-IP sensor networks to the cloud, it is necessary to enable routing between IP / non-IP. In order to ensure reachability across different networks, an ID / locator separation architecture that separates terminal identifiers (IDs) and terminal connection positions (locators) has been proposed (Non-Patent Document 1).

  LISP (Locator / Identifier Separation Protocol), HIP (Host Identity Protocol), HIMALIS (Heterogeneity Inclusion and Mobility Adaptation through Locator ID Separation) as an ID / locator separation method that realizes address resolution for routing between multiple networks Etc. have been studied (Non-Patent Document 2). LISP and HIP assume a connection between IP networks, and HIMARIS assumes a connection between IP / non-IP networks. Depending on the device that refers to the locator, it can be broadly divided into the following three types.

Configuration (1)
Configuration (1) is a method in which the end terminal itself recognizes and refers to a new ID or locator that has been separated. When a plurality of networks are connected, the protocol is common (for example, IP), and the end terminal performs address resolution across the plurality of networks by referring to DNS or the like. This corresponds to HIP that introduces a new ID called Host Identity, but the M2M terminal itself needs to interpret and refer to it, which increases the burden of adding functions to the M2M device. Further, since HIP is closed in the IP space, when a plurality of networks are connected, application to the M2M area NW from different IP to non-IP is not assumed.

Configuration (2)
Configuration (2) is a method of recognizing and referring to a new ID and locator in both the end terminal and the GW apparatus. For example, in HIMALIS, routing in which different types of IP / non-IP NWs are connected is assumed. A common ID layer for ID and locator address resolution needs to be implemented in common on all NW devices such as M2M terminals and GW devices. Again, as with configuration (1), new functions added to M2M devices The burden is inevitable.

Configuration (3)
Configuration (3) is a method in which only the GW device arranged at the boundary of a plurality of networks solves the separation of the ID and the locator and realizes routing to the M2M device. There is a merit of not giving an impact to the end terminal (here, the M2M terminal). LISP can be said to be one of them, but it is a technique for closing addresses in an IP space in a plurality of IP networks and resolving an address, so that it is difficult to apply to a non-IP M2M area NW as it is.

New generation network architecture with ID / locator separation, http://www.nict.go.jp/publication/researcher/pdf_data/01/01/014_017.pdf Ved P. Kafle, Yusuke Fukushima, Kenji Fujikawa and Hiroaki Harai, “ID-Based Communication Framework for New Generation Networks” ICUFN 2014.

  When the conventional technology of the above configuration (1) or (2) is applied to the entire network, “addition of an ID layer is necessary for all network devices (hereinafter referred to as NW devices)” “Mapping Server ( In the following, it is necessary to refer to the MS), which increases the burden of updating the existing NW device. Further, from the viewpoint that the conventional technology of the above configuration (3) does not give a burden of adding a new function to the M2M device, there is a configuration (3) that can be closed to the transit network between the PF server and the M2M-GW and perform address resolution. Although it is considered effective, it is difficult to apply to non-IP M2M area NW.

  Furthermore, with the configuration technology of configuration (1) or (2) or (3) alone, a global locator provides a direct access path from the application server to the M2M device, so there is a large security risk for low-function M2M devices. Become.

  An object of the present invention is to provide an end-to-end M2M service between an M2M device and an application server, regardless of IP / non-IP, in addition to improving the security for the M2M device with a simple configuration. An object of the present invention is to provide a network system, a configuration method therefor, and a program.

  In order to achieve the above object, one aspect of the present invention is a network system that executes an M2M service between an application server connected to a first communication network and a device connected to a second communication network. Storage means for storing a device ID sent from the application server to identify the device, and when receiving a connection request from the device, the storage means is referred to based on the device ID included in the connection request. Based on this reference result, a connection processing means for establishing a connection for performing the M2M service using the device ID between the application server and the device, and an operation from the application server When receiving a request, the device and the previous And an application server so that and a connection relay means for relaying.

  Another aspect of the present invention is a network system configuration method for executing an M2M service between an application server connected to a first communication network and a device connected to a second communication network, A relay server device provided on a cloud that can connect the first communication network and the second communication network stores a device ID sent from the application server and identifying the device in a database, and requests connection from the device The relay server device refers to the database based on the device ID included in the connection request, and based on the reference result, the device ID is transmitted between the application server and the device. For executing M2M services using GIS Establishing a connection to perform, when receiving the operation request from the application server, the relay server apparatus, so that relays and the device and the application server.

  Furthermore, one aspect of the present invention provides a relay server device of a network system that executes an M2M service between an application server connected to a first communication network and a device connected to a second communication network. Storage means for storing a device ID for identifying the device sent from the server, and when receiving a connection request from the device, the storage means is referred to based on the device ID included in the connection request, and the reference result Based on connection processing means for establishing a connection for performing communication for executing the M2M service using the device ID between the application server and the device, and when receiving an operation request from the application server, The device and the application A program for operating as a connection relay means for relaying a server.

  According to the present invention, it becomes possible to provide an end-to-end M2M service between an M2M device and an application server regardless of whether the M2M area network is IP / non-IP, and the application server can use the IP network as it is. Therefore, it is possible to avoid the burden of updating NW devices located on the application server side from the M2M-PF server including the application server.

  In addition, the state of the M2M device, sensor acquisition values, and the like are centrally managed on the PF server, and only the operation at the application level is accepted from the application server. Security risk can be reduced by not directly providing reachability to M2M devices at the layer.

  By applying the present invention, M2M across IP / non-IP without adding / changing functions to M2M devices and M2M applications equipped with commercially available M2M modules used in existing silo-type M2M solutions System construction is possible.

The figure which shows the structure of the network system of this invention. The figure which shows the comparative example of a protocol stack. The figure which shows the protocol stack which concerns on the 1st Embodiment of this invention. The figure which shows the protocol stack which concerns on the 2nd Embodiment of this invention. The figure which shows the Example of a protocol stack. The figure which shows the example of an authentication sequence in this invention. The figure which shows the network structural example at the time of M2M device movement. The figure which shows the example of ID / locator mapping sequence at the time of M2M device movement. The figure which shows the example of ID / locator mapping sequence at the time of M2M device movement. The figure which shows the structure of the network system which concerns on the 3rd Embodiment of this invention. The figure which shows the protocol stack which concerns on the 3rd Embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a schematic configuration diagram showing an embodiment of a network system according to a first embodiment and a second embodiment of the present invention to be described later. This system assumes a network divided into three domains: M2M area networks NW1 and NW2, a wide area network (mobile / fixed access / core network) NW3 as a cloud, and an IP network NW4 such as the Internet / ISP network.

  In the M2M area networks NW1 and NW2, M2M devices 11-1 to 11-i (i is an integer) such as sensors with communication functions, which are the operation targets of the M2M application, are arranged.

  Gateways (M2M-GW) 12-1 and 12-2 at the boundary between the M2M area networks NW1 and NW2 and the wide area network NW3, and an M2M-PF server (hereinafter referred to as PF server) between the wide area network NW3 and the IP network NW4 Is placed.

  M2M-GWs 12-1 and 12-2 are gateways (HGW, smart phone, etc.) between the wide area networks NW3-M2M area networks NW1 and NW2, and management of participation in the M2M area networks NW1 and NW2 and issuance of local locators, And makes an authentication request to the PF server 13.

  The PF server 13 holds a database (PF-DB) 131 and centrally holds and manages the states of the M2M devices 11-1 to 11-i, sensor acquisition values, and the like. The PF server 13 authenticates the M2M devices 11-1 to 11-i.

  In a section between the M2M area networks NW1 and NW2 and the wide area network NW3, an ID layer that can be referred to in common is introduced to perform ID-based communication. The mapping server (hereinafter referred to as MS) 14 arranged in the wide area network NW3, based on the update information from the PF server 13 and the M2M-GWs 12-1 and 12-2, all the M2M devices 11- under the M2M-PF. 1-11-i ID / locator management is performed.

  The device resources on the PF-DB 131 of the PF server 13 are performed at the CRUD operation level at the application level from the APP servers 15-1 and 15-2 based on, for example, the REST (Representational State Transfer) architecture. Protocols based on the REST architecture include HTTP (Hypertext Transfer Protocol) and CoAP (Constrained Application Protocol).

  The APP servers 15-1 and 15-2 are application servers owned by M2M operators and end users. The APP servers 15-1 and 15-2 perform management update of device resource information on the PF-DB 131 by CRUD operation or the like, pre-registration of M2M devices 11-1 to 11-i, and M2M device 11-1. 11-i-PF server 13 route policy is designated and set.

Hereinafter, the operation in the above configuration will be described.
As shown in FIG. 2A, in the case of all IP networks, IP addresses can be used for all networks as identifiers of the M2M devices 11-1 to 11-i. However, when non-IP sensor networks such as Zigbee (registered trademark) are used as the M2M area networks NW1 and NW2, the reachability to the M2M devices 11-1 to 11-i cannot be managed end-to-end.

  On the other hand, as shown in FIG. 2B, when a non-IP M2M area network is used, the network layer is separated into an ID layer (L3-ID) and a locator layer (L3-L), so that different networks can be mixed. Even under the environment (here, the M2M area networks NW1 and NW2 and the wide area network NW3), reachability to the M2M devices 11-1 to 11-i can be secured using the device ID. However, it is necessary to newly add ID layers to all NW devices and to refer to the MS 14 from all NW devices, which increases the burden of renewing existing NW facilities.

  Therefore, in this embodiment, the PF server 13 is provided with a connection processing function 132 and a connection relay function 133 in addition to the PF-DB 131.

  When the connection processing function 132 receives a participation request from the M2M device 11-1 via the M2M-GW 12-1, the device ID is registered by referring to the PF-DB 131 based on the device ID included in the participation request. In this case, as shown in FIG. 5, the device ID and the locator for specifying the connection position of the M2M device 11-1 are associated with each other and registered in the MS 14, and communication using the device ID on the sublayer of the network layer (L3) is performed. Establish a connection.

  When the connection relay function 133 receives an operation request (CRUD operation or the like) from the APP server 15-1 via the application layer (L4), the protocol between the network layer and the application layer is used by using the PF-DB 131 as a cache. By performing conversion (layer conversion), the M2M device 11-1 and the application server 15-1 are relayed.

  In this way, an IP address and an identifier for Zigbee (registered trademark) are not used, and a common device ID is used, regardless of whether the M2M area networks NW1 and NW2 are IP / non-IP or not. M2M service can be provided between APP servers.

  FIG. 6 shows an example of an authentication sequence in the first embodiment and the second embodiment of the present invention.

  When a device registration operation is performed on the PF-DB 131 by the operator of the APP server 15-1 (step ST51), a device registration request is transmitted from the APP server 15-1 to the PF-DB 131 on the PF server 13 ( S1). Then, the PF server 13 registers the ID of the M2M device 11-1 in the PF-DB 131 (step ST41), and transmits a device registration response to the requesting APP server 15-1 (S2).

  On the other hand, when an M2M service participation request is generated due to installation (for example, power-on) or movement of the M2M device 11-1 (step ST11), the M2M device 11-1 sends an M2M-GW 12-1 on the M2M area network NW1. A participation request is sent (S3). When there is a participation request, the M2M-GW 12-1 first assigns a (local) locator (step ST21), transmits a participation response to the requesting M2M device 11-1 (S4), and the M2M device 11 The authentication request including the device ID and locator of −1 is transmitted to the PF server 13 (S5).

  When receiving the authentication request from the M2M-GW 12-1, the PF server 13 refers to the PF-DB 131 based on the device ID included in the authentication request and determines whether or not the device ID is registered (step) ST42). Here, when it is not registered (No), the PF server 13 transmits an authentication failure response to the M2M-GW 12-1 (S6). Then, the M2M-GW 12-1 cancels the local locator assignment for the M2M device 11-1 (step ST22), and transmits an authentication failure response to the M2M device 11-1 (S7). The fact that the authentication has failed is notified on the software or application program on the M2M device 11-1 (step ST12).

  On the other hand, if registered in step ST42 (Yes), the PF server 13 transmits a mapping request to the MS 14 (S8). When receiving the mapping request from the PF server 13, the MS 14 registers the device ID and locator of the M2M device 11-1 included in the mapping request (step ST31), and returns a mapping response to the PF server 13 (S9).

  The PF server 13 transmits an authentication pass response including information regarding the encryption key as a device ID, a locator, and an authentication response to the M2M device 11-1 via the M2M-GW 12-1 (S10, S11). Finally, notification of successful authentication is sent to the software and application program on the M2M device 11-1 (step ST13).

  Thereafter, a communication connection for performing the M2M service is established between the M2M device 12-1 and the PF server 13 using the device ID and the locator.

  FIG. 7 shows a network configuration example when the M2M device is moved.

  Here, it is assumed that the M2M device moves from the M2M area network NW1 to the M2M area network NW2. Other configurations are the same as the network configuration shown in FIG.

8 and 9 show an example of an ID / locator mapping sequence when the M2M device is moved.
When an M2M service participation request is generated due to installation (for example, power-on) or movement of the M2M device 11-1 (step ST14), the M2M device 11-1 requests to participate in the M2M-GW 12-1 on the M2M area network NW1. Is sent (S11). When there is a participation request, the M2M-GW 12-1 first assigns a (local) locator (Loc1) (step ST23), transmits a participation response to the requesting M2M device 11-1 (S12), An authentication request including the device ID and locator (Loc1) of the M2M device 11-1 is transmitted to the PF server 13 (S13).

  When receiving the authentication request from the M2M-GW 12-1, the PF server 13 refers to the PF-DB 131 based on the device ID included in the authentication request and determines whether or not the device ID is registered. If so, a mapping request is transmitted to the MS 14 (S14). Upon receiving the mapping request from the PF server 13, the MS 14 registers the device ID and locator (Loc1) of the M2M device 11-1 included in the mapping request (step ST32), and returns a mapping response to the PF server 13 ( S15).

  The PF server 13 transmits an authentication pass response including a device ID, a locator (Loc1), and information on the encryption key (Key) as an authentication response to the M2M device 11-1 via the M2M-GW 12-1 (S16, S17). . Thereafter, a communication connection for performing the M2M service is established between the M2M device 12-1 and the PF server 13 using the device ID and locator (Loc1) (step ST15).

  Here, it is assumed that the M2M device 11-1 has moved from the M2M area network NW1 to the M2M area network NW2 (step ST16). Then, a participation request is sent from the M2M device 11-1 to the M2M-GW 12-2 on the M2M area network NW2 (S18). When there is a participation request, the M2M-GW 12-2 first allocates a (local) locator (Loc2) (step ST24) and transmits a participation response to the requesting M2M device 11-1 (S19). A mapping update request including the device ID and locator (Loc2) of the M2M device 11-1 is transmitted to the PF server 13 (S20).

  When receiving the mapping update request from the M2M-GW 12-2, the PF server 13 transmits the mapping request to the MS 14 (S21). Upon receiving the mapping request from the PF server 13, the MS 14 registers the device ID and locator (Loc2) of the M2M device 11-1 included in the mapping request (step ST33), and returns a mapping response to the PF server 13 ( S22).

  The PF server 13 transmits an authentication pass response including the device ID, a locator (Loc2), and information on the encryption key (Key) as an authentication response to the M2M device 11-1 via the M2M-GW 12-2 (S23, S24). . Thereafter, a communication connection for performing the M2M service is established between the M2M device 12-1 and the PF server 13 using the device ID and locator (Loc2) (step ST17).

  Subsequently, the PF server 13 transmits a locator (Loc1) status confirmation request to the M2M-GW 12-1 (S25). When the PF server 13 receives the state confirmation response returned from the M2M-GW 12-1 (S26), if the link between the M2M device and the M2M-GW 12-1 is disconnected based on the state confirmation response, the PF server 13 maps to the MS 14 A request is transmitted (S27).

  When receiving the mapping request from the PF server 13, the MS 14 deletes the locator (Loc1) registered in the MS 14 (step ST34), and returns a mapping response to the PF server 13 (S28).

  The PF server 13 transmits a locator deletion request including the locator (Loc1) to the M2M-GW 12-1 (S29). Then, the M2M-GW 12-1 deletes the locally held locator (Loc1) (step ST25). Subsequently, the PF server 13 transmits a mapping deletion request including the locator (Loc1) to the M2M device 11-1 via the M2M-GW 12-2 (S30, S31). Thereafter, the M2M device 11-1 deletes the locator (Loc1) held in the routing table (step ST18). Accordingly, after establishing a communication connection with the movement of the M2M device 11-1 with the PF server 13, it is confirmed whether or not the link by the original Loc1 is disconnected, and the communication connection by Loc1 is disconnected. be able to.

(First embodiment)
FIG. 3 is a diagram showing a protocol stack according to the first embodiment of the present invention.

  In the first embodiment, ID / locator separation is performed only between the M2M device and the PF server, and the ID layer is an L3 sublayer.

  The M2M device 11-1 having established a communication connection with the PF server 13 via the M2M-GW 12-1 detects, for example, the movement of the sensing object, and the device ID for identifying the device itself, the sensing object Is transmitted to the PF server 13 via the M2M-GW 12-1.

  The PF server 13 extracts the state, sensor acquisition value, and the like of the M2M device 11-1 from the information sent from the M2M device 11-1, and stores the state, sensor acquisition value, and the like of the M2M device 11-1 in the M2M device 11-1. Are registered in the PF-DB 131 in association with the device ID. Further, the PF server 13 extracts the state of the M2M devices 11-2 to 11-i, sensor acquisition values, and the like from the information sent from the M2M devices 11-2 to 11-i, and M2M devices 11-2 to 11-i. Are registered in the PF-DB 131 in association with the device IDs of the M2M devices 11-2 to 11-i.

  The APP server 15-1 performs the CRUD operation on the PF server 13 via the application layer (L 4), thereby acquiring the status and sensor acquisition of each M2M device 11-1 to 11-i registered in the PF-DB 131. An entity for storing a value can be created (Create), a sensor acquisition value can be acquired (Read), updated (Update), or deleted (Delete).

  As described above, according to the first embodiment, the states and sensor acquisition values of the M2M devices 11-1 to 11-i are centrally managed on the PF-DB 131 on the PF server 13, and the APP server By adopting a configuration that accepts only CRUD operations and the like at the application level from 15-1, the APP server 15-1 side does not directly provide reachability to the M2M device 11-1 at the network layer. Security risk can be reduced. As a result, even in the M2M service in which the scale of the M2M area networks NW1 and NW2 is large, the IP network NW4 in which the application server 15-1 is installed can be easily constructed while using the existing equipment. By reducing the coupling between the M2M area network NW1 / NW2 and the IP network NW4, it is possible to provide a service with reduced security risk. In addition, in the wide area network NW3 section, in order to reduce security risk, the existing L2 / L3 tunneling protocol is applied, and logical routing is not performed between the M2M-GW 12-1 and the PF server 13. You can also.

  In the first embodiment, the ID / locator separation is performed in the wide area network NW3 and the M2M area networks NW1 and NW2, and only ID-based communication between the M2M device and the M2M-GW-PF server is allowed. Thus, the reachability from the PF server 13 to the M2M device 11-1 can be centrally managed in the network layer. Therefore, the M2M area networks NW1 and NW2 can provide an end-to-end M2M service between the M2M device 11-1 and the application server 15-1 without depending on IP / non-IP.

  Furthermore, in the first embodiment, since the APP server 15-1 side can use the IP network NW4, application to an existing corporate network or the Internet is facilitated.

(Second Embodiment)
FIG. 4 is a diagram showing a protocol stack according to the second embodiment of the present invention.

  In the second embodiment, ID / locator separation is performed only between the M2M device and the PF server, and the ID layer is an L4 sublayer.

  In the second embodiment, the basic configuration, operation, and role of each device are the same as when the ID layer is an L3 sublayer. However, by realizing the ID layer above L4 (a level that can be controlled by the OS (Operation System) of each NW device), an existing L2 / L3-compatible NW device can be used in an intermediate router between the M2M device and the PF server. Can be utilized.

(Third embodiment)
FIG. 10 is a schematic configuration diagram showing an embodiment of a network system according to the third embodiment of the present invention. FIG. 11 is a diagram showing a protocol stack according to the third embodiment of the present invention.

  In the third embodiment, the basic configuration, operation, and role of each device are the same as those in the first embodiment and the second embodiment of the present invention. However, instead of performing common ID-based communication between the M2M devices 11-1 to 11-i and the PF server 13, the M2M-GW apparatus 12-1 includes the protocol conversion function 121-1, and the protocol conversion function By providing 121-2 in the M2M-GW apparatus 12-2, ID communication between the M2M devices 11-1 to 11-i and the M2M-GW apparatuses 12-1 and 12-2 (in FIG. M communication) and ID communication between the M2M-GW apparatuses 12-1 and 12-2 and the PF server 13 (denoted as ID (W) here) can be performed.

  The protocol conversion functions 121-1 and 121-2 are ID communication protocols for non-IP networks in order to establish a connection between the APP servers 15-1 and 15-2 and the M2M devices 11-1 to 11-i. And the ID communication protocol for the IP network. In this case, the M2M-GW apparatuses 12-1 and 12-2 store, for example, a table representing correspondence between ID (M) and ID (W) in a memory (not shown).

  By adopting the configuration of the third embodiment, an ID (M that is a unique communication protocol (for example, a network protocol represented by Zigbee) inherently possessed by a non-IP network without using a new ID communication protocol is used. ) Can be applied as it is, and a new ID communication protocol can be configured by only ID (W). In addition, in the wide area network NW3 and the M2M area networks NW1 and NW2 sections, M2M devices similar to those in the first embodiment and the second embodiment of the present invention are used by using the protocol conversion functions 121-1, 121-2. By realizing ID-based communication between the M2M-GW-PF servers, the reachability from the PF server 13 to the M2M device 11-1 can be centrally managed in the network layer. Therefore, the M2M area networks NW1 and NW2 can provide an end-to-end M2M service between the M2M device 11-1 and the application server 15-1 without depending on IP / non-IP.

(Other embodiments)
The individual processes described in the PF server 13 can be processed by software using a computer program. In this case, the program can be recorded on a recording medium or provided through a network.

  In short, the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, you may combine suitably the component covering different embodiment.

11-1 to 11-i ... M2M devices 12-1, 12-2 ... M2M-GW
13: PF server 15-1, 15-2 ... Application server (APP server)
121-1, 121-2 ... Protocol conversion function 131 ... Database (PF-DB)
132 ... Connection processing function 133 ... Connection relay function NW1, NW2 ... M2M area network NW3 ... Wide area network NW4 ... IP network

Claims (8)

A network system for executing an M2M service between an application server connected to a first communication network and a device connected to a second communication network,
Storage means for storing a device ID sent from the application server to identify the device;
When receiving a connection request from the device, the storage unit is referred to based on the device ID included in the connection request, and the device ID is determined between the application server and the device based on the reference result. A connection processing means for establishing a connection for performing communication for executing the M2M service using;
A network system comprising connection relay means for relaying between the device and the application server when receiving an operation request from the application server. The connection processing means associates and stores the device ID and a locator that specifies a connection position of the device with respect to the second communication network in the mapping unit. Establish a connection,
When the device moves from the first locator of the second communication network to the second locator, the device ID and the device ID and the first connection using the first locator are established and the device ID and Connection changing means for establishing a second connection using the second locator and erasing the first locator stored in the mapping unit when the first connection is disconnected; The network system according to claim 1, further comprising:   The network system according to claim 1, wherein the connection processing unit establishes the connection on a sublayer of the network layer.   The network system according to claim 1, wherein the connection processing unit establishes the connection on a sublayer of an application layer. The connection processing means includes protocol conversion means for performing protocol conversion of the device ID for establishing a connection between the application server and the device;
The network system according to claim 1, further comprising:   The connection relay means acquires information on the device by communication with the device via the connection, manages the information in the storage means in association with the device ID, and responds to an operation request from the application server. The network system according to claim 1, wherein information about the device is acquired from the storage unit. A network system configuration method for executing an M2M service between an application server connected to a first communication network and a device connected to a second communication network,
A relay server device provided on a cloud capable of connecting the first communication network and the second communication network stores a device ID sent from the application server to identify the device in a database;
When receiving a connection request from the device, the relay server apparatus refers to the database based on a device ID included in the connection request, and based on the reference result, between the application server and the device. Establishing a connection for performing communication for executing the M2M service using the device ID,
A method for configuring a network system, wherein when the operation request is received from the application server, the relay server device relays the device and the application server. A relay server apparatus of a network system that executes an M2M service between an application server connected to the first communication network and a device connected to the second communication network is a device that is sent from the application server and identifies the device Storage means for storing the ID;
When receiving a connection request from the device, the storage unit is referred to based on the device ID included in the connection request, and the device ID is determined between the application server and the device based on the reference result. A connection processing means for establishing a connection for performing communication for executing the M2M service using;
A program that operates as a connection relay unit that relays between the device and the application server when receiving an operation request from the application server.