Device, method and program for data processing

Abstract

To provide a communication system capable of providing IoT devices with access to an IP network, the communication system enabling data processing of data transmitted from the IoT device, prior to the data going out onto the IP network.SOLUTION: First, an IoT device 130 transmits, to a base station 120, data which comprises a payload to which a required header has been added (S201). In the case of 4G, the base station 120 adds a GTP-U header and transmits the same to an MNO facility 111 (S202). The MNO facility 111 forwards the received data to a cloud facility 112 (S203). Further, on the basis of the TEID contained in the header of the received data, the cloud facility 112 runs a pre-specified program on the payload of the data, as necessary (S204). Thereafter, the cloud facility 112 adds a required header to the payload after conversion, and transmits the same to an application server 140 on the IP network (S205).SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to an apparatus, a method and a program for data processing, and more particularly to an apparatus, a method and a program for data processing in a core network. [Background technology]

[0002] As the number of devices connected to computer networks such as the Internet increases, the idea of ​​the Internet of Things, in which all things are networked, is becoming more widespread. Wireless communication services for networking devices have traditionally been provided directly to end users by MNOs (mobile network operators) that own wireless communication infrastructure, but in recent years, operators called MVNOs (mobile virtual network operators) have been using the MNO's wireless communication infrastructure to provide their own wireless communication services to end users. Between the MNO and MVNO, there is an MVNE (mobile virtual network service provider) that provides support services to help MVNOs run their business smoothly, and in some cases the MVNE receives SIM cards from the MNO and then provides them to the MVNO.

[0003] MVNEs or MVNOs that provide wireless communication services for networked devices (hereinafter referred to as "IoT devices") may have their own communications infrastructure to provide access to computer networks such as IP (Internet Protocol) networks, and thereby attempt to meet various needs by setting communication quality, such as communication speed and communication capacity, according to price. Summary of the Invention [Problem to be solved by the invention]

[0004] In order to utilize data collected from IoT devices using such services, users had to build their own systems on an IP network or select existing services to perform data processing such as analysis on a server on the IP network.

[0005] However, building a new system is a big burden. Also, in order to use various existing services such as SaaS, the format of the data sent from the IoT device must match the format of the service in question, but this is often not the case, and a system for format conversion processing is ultimately required.

[0006] The present invention has been made in consideration of these problems, and its purpose is to enable data processing of data transmitted from an IoT device before it enters an IP network in a communication system, communication method, and program configured to provide IoT devices with access to an IP network. [Means for solving the problem]

[0007] In order to achieve this object, a first aspect of the present invention is a method of data processing in a node constituting a core network comprising a first facility for communicating with a base station and a second facility configured to receive data from an IoT device from the first facility via communication on a U-plane and transmit the data to an IP network, comprising the steps of: the node receiving data from the IoT device; the node determining, based on a TEID included in a header of the data, whether or not there is a program associated with a SIM installed in the IoT device; and, if there is a program associated with the SIM, the node executing the program on the data, wherein the program is characterized in that the processes that can be executed are restricted.

[0008] Furthermore, a second aspect of the present invention is characterized in that, in the first aspect, the executable processing includes computational processing using computing resources of the node, and an API that is associated with the SIM and pre-authorized.

[0009] A third aspect of the present invention is characterized in that, in the second aspect, the pre-authorized API includes an API that performs protocol conversion of a transport layer or an application layer of the data.

[0010] Furthermore, a fourth aspect of the present invention is characterized in that in the second or third aspect, the pre-authorized API includes at least one of an API that changes the destination of the payload of the data or modified data thereof when a predetermined condition is met, an API that discards the payload of the data or modified data thereof when a predetermined condition is met, and an API that transmits the modified payload of the data to the IoT device when a predetermined condition is met.

[0011] Furthermore, a fifth aspect of the present invention is characterized in that, in any one of the second to fourth aspects, the program restricts the data that can be input, and the data that can be input includes data received from the IoT device, data linked to the SIM, and data linked to a session identified by the TEID.

[0012] Moreover, a sixth aspect of the present invention is characterized in that, in the fifth aspect, the data associated with the SIM includes at least one of information set in the SIM and information set in a group to which the SIM belongs.

[0013] Moreover, a seventh aspect of the present invention is characterized in that, in any of the first to sixth aspects, the node has a first and a second instance on a public cloud, the reception is performed by the first instance, and the execution of the program is performed by the second instance.

[0014] Moreover, an eighth aspect of the present invention is characterized in that, in the seventh aspect, the executable process is such that the available computing resources of the second instance are limited within a predetermined range.

[0015] A ninth aspect of the present invention is a program for causing a node constituting a core network having a first facility for communicating with a base station and a second facility configured to receive data from an IoT device from the first facility by communication on a U-plane and transmit the data to an IP network to execute a method for performing data processing on data from the IoT device, the method including a step of the node receiving data from the IoT device, a step of the node determining whether or not there is a program associated with a SIM installed in the IoT device based on a TEID included in a header of the data, and a step of the node executing the program on the data if there is a program associated with the SIM, the program being characterized in that executable processes are predetermined.

[0016] In addition, a tenth aspect of the present invention is a node constituting a core network having a first facility for communicating with a base station and a second facility configured to receive data from an IoT device from the first facility by communication on a U-plane and transmit the data to an IP network, the node receiving data from the IoT device and determining whether or not there is a program associated with a SIM installed in the IoT device based on a TEID included in a header of the data, and if there is a program associated with the SIM, executing the program on the data, and the program has predetermined executable processes. Effect of the Invention

[0017] According to one aspect of the present invention, by imposing certain restrictions on user code that can be executed at any node constituting the core network, data processing is possible on data transmitted from an IoT device in the core network 110 before it leaves the IP network. [Brief description of the drawings]

[0018] [Figure 1] 1 is a diagram showing a communication system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a sequence diagram according to the first embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram illustrating an example of cloud facility according to the first embodiment of the present invention. [Figure 4] FIG. 4 is a diagram illustrating another example of the cloud facility according to the first embodiment of the present invention. [Diagram 5] FIG. 11 is a sequence diagram according to the second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0020] (First embodiment) Fig. 1 shows a communication system according to a first embodiment of the present invention. The communication system 110 includes an MNO facility 111 that communicates with a base station 120, and a cloud facility 112 that is configured to receive data from an IoT device 130 from the MNO facility 111 and transmit the data to an IP network 140. Although two base stations are shown in Fig. 1, one of the base stations will be described as an example. Also, although many IoT devices 130 are shown in Fig. 1 by their installed SIMs (Subscriber Identity Modules), one of the base stations will be described as an example.

[0021] In this specification, "MNO facility" refers to facility for communication owned by an MNO, and "cloud facility" refers to facility on the cloud. Here, "cloud" refers to a system that can dynamically provision and provide computing resources such as CPU, memory, storage, and network bandwidth on a network according to demand. For example, the cloud can be used by AWS (registered trademark) or the like. Also, "public cloud" refers to a cloud that can be used by multiple tenants. Cloud facility 112 is a node owned by an MVNE or MVNO, and is preferably an instance on a public cloud.

[0022] Here, the communication system according to the present embodiment targets communication on the U-plane, and in 4G, the first facility 111 corresponds to the SGW, and the second facility 112 corresponds to the PGW. In 5G, the functions on the C-plane and the functions on the U-plane are separated, and it is being discussed that the functions on the U-plane are aggregated in a node called UPF, and the boundary between the functions carried out in the MNO facility 111 and the functions carried out in the cloud facility 112 is not necessarily clear, but this point does not affect the description of the features of the present invention. The functions carried out in the MNO facility 111 and the cloud facility 112 are sometimes referred to as the "core network." In addition, the base station 120 corresponds to the eNodeB in 4G, and the gNodeB in 5G.

[0023] The cloud facility 112 can transmit data from an IoT device 130 to an external server 140 outside the core network via an IP network, and in this embodiment, as described below, if the data is associated with a specific SIM, a pre-specified program is executed to modify the payload of the data.

[0024] In this specification, a "SIM" can refer to a physical SIM card, but can also refer to a semiconductor chip (also called an "eSIM") embedded in IoT device 130, or it can be software installed in a secure area within a module of IoT device 130 and an identifier such as an IMSI (International Mobile Subscriber Identity) stored in the software; various forms are possible.

[0025] 2 shows a sequence diagram according to the first embodiment of the present invention. First, the IoT device 130 transmits data with a required header added to the payload to the base station 120 (S201). In one example, the payload of the data is added with a UDP header, an IP header, and a wireless header. Examples of the payload include image data in a predetermined format, compressed binary data, etc., which will be described later.

[0026] The base station 120 removes the wireless header from the received data, and if it is 4G, adds a GTP-U header and transmits it to the MNO equipment 111 (S202). The MNO equipment 111 transfers the received data to the cloud equipment 112 (S203).

[0027] Then, the cloud facility 112 determines whether the received data is associated with a specific SIM based on a Tunneling Endpoint ID (TEID) included in the header of the data, and if associated, executes a pre-specified program on the payload of the data (S204).

[0028] Specifically, when a session is generated by communication on the C-plane, a TEID representing each session is also generated, and a correspondence between the TEID and a SIM used for communication on the U-plane (hereinafter also referred to as a "first correspondence") is stored in the cloud facility 112 or a storage device or storage medium accessible to the cloud facility 112. Furthermore, for the SIM used for communication on the U-plane, a correspondence as to whether or not a program (hereinafter also referred to as a "user code") designated in advance by a user should be executed (hereinafter also referred to as a "second correspondence", which may include a designation of which user code should be executed if the program should be executed) is stored in the cloud facility 112 or a storage device or storage medium accessible to the cloud facility 112, and the cloud facility 112 executes a program for the payload as necessary by referring to the first and second correspondences based on the TEID included in the header of the data received by the cloud facility 112. Here, the first and second correspondences are described as separate, but they may be integrated into a single correspondence, and it is sufficient if the user code to be executed can be identified based on the TEID in some way. In addition, in this specification, the TEID is used as an identifier for identifying a SIM, but it is also possible to use an identifier other than the TEID as long as it can identify the SIM and the user code associated with the SIM.

[0029] Thereafter, the cloud facility 112 adds a required header to the converted payload and transmits it to the application server 140 on the IP network (S205). At this time, as an example, in addition to converting the payload, the transport layer protocol can be converted from TCP to UDP or from UDP to TCP. Also, as an example, the application layer protocol can be converted, such as from HTTP to HTTPS. In the above description, it is not explicitly stated whether the user code deletes and adds a header, but in addition to changing the payload, at least one of deleting and adding a header may be performed by the execution of the user code. Also, an instruction to another program regarding the addition of a header may be written in the user code, and the other program may perform protocol conversion on the payload after the change processing by the user code.

[0030] Although the details will be described later, the data that can be input to the user code and the processes that the user code can execute are limited, so that even if the cloud facility 112 allows execution of user codes freely created by users, security risks are suppressed.

[0031] As described above, by imposing certain restrictions on the user code that can be executed in cloud facilities 112 such as PGW, it is possible to allow the user code to be executed within the core network 110 before going out to the IP network, thereby removing the burden of building a new system on the IP network from users who wish to utilize data collected from IoT devices.

[0032] It should be noted that unless the word "only" is used, such as "based only on," "depending only on," or "only in the case of," this specification assumes that additional information may be taken into consideration. As an example, it should be noted that the phrase "do b when a" does not necessarily mean "do b always when a" or "do b immediately after a" unless expressly stated. In addition, the phrase "each a constituting A" does not necessarily mean that A is composed of multiple components, but includes the case where the component is singular.

[0033] It is further noted that, even if not explicitly stated in this specification, it is contemplated as an aspect of the present invention that the data that can be input to the user code and the processes that the user code can execute are limited to only a portion of those described in this specification.

[0034] Also, just to be clear, even if there is an aspect of a method, program, terminal, device, server or system (hereinafter referred to as a "method, etc.") that performs an operation different from that described in this specification, each aspect of the present invention is directed to an operation that is the same as any of the operations described in this specification, and the existence of an operation different from that described in this specification does not make the method, etc. outside the scope of each aspect of the present invention.

[0035] In the above description, the user code is executed in the cloud facility 112, but the user code may be executed in association with one or more processes defined in any node in the core network 110. Specifically, the user code may be executed as necessary based on the header of data received from the base station 120 in the MNO facility 111 such as an SGW before the data is forwarded. In addition, the nodes constituting the core network in the communication on the U-plane are the SGW and PGW in the case of 4G, but it is also possible to place network facilities such as routers, proxy servers, and load balancers in addition to these. The user code may be executed in these network facilities. The node that executes the user code needs to be able to directly or indirectly associate the TEID with the executable user code and to access data that can be input to the user code.

[0036] In addition, in this specification, the equipment called SGW in 4G is called "MNO equipment" and the equipment called PGW is called "cloud equipment", but more generally, the former is called "first equipment" and the latter is called "second equipment". In this case, the "first equipment" may be equipment owned by a business operator that is not necessarily an MNO, as long as it plays the same role as the above-mentioned "MNO equipment".

[0037] User Code Details The user code to be executed on the cloud facility 112 can be specified by uploading it by a user of the communication service provided by the cloud facility 112. The user code is uploaded from a user terminal 320 directly to the cloud facility 112 or via an intermediate server 310 capable of communicating with the cloud facility 112. The user code can be a program in a predetermined binary format or text format, and examples of the user code include a WebAssembly format in the case of a binary format and a script format such as Python or Javascript (registered trademark) in the case of a text format.

[0038] The cloud facility 112 includes a communication unit 112-1 such as a communication interface, a processing unit 112-2 such as a processor or CPU, and a storage unit 112-3 including a storage device or storage medium such as a memory or a hard disk, and can be configured by executing a program for performing each process. The cloud facility 112 may include one or more devices, computers, or servers. The program may include one or more programs, and may be recorded in a computer-readable storage medium to form a non-transient program product. The program may be stored in the storage unit 112-3 or a storage medium 112-4 accessible from the cloud facility 112, and may be executed by the processing unit 112-2. The uploaded user code is also stored in the storage unit 112-3 of the cloud facility 112 or a storage medium 112-4 accessible by the cloud facility 112 via a computer network. Although not shown, the MNO facility 111 may also be configured in a similar manner.

[0039] In FIG. 3, the user code is stored and executed using the computing resources of the cloud facility 112. However, as shown in FIG. 4, in the cloud facility 112, a server or instance 412-1 (corresponding to a "first instance") for executing a communication process of receiving data from the IoT device 130 from the MNO facility 111 and transmitting the data to the IP network and a separate server or instance 412-2 (corresponding to a "second instance") can be prepared. In this case, it is preferable because it is possible to further improve security as described later. When the user code is executed in an instance separate from the instance for executing the communication process, the separate instance may be referred to as the cloud facility 112 including the separate instance, or the separate instance may be referred to as an instance located outside the cloud facility 112. In this specification, the separate instance may be referred to as the "cloud facility".

[0040] A user code can be associated with one or more SIMs when uploaded by a user. In the case of 4G, the cloud facility 112 can identify the SIM used for communication on the U-plane based on the GTP-U header and refer to the association to identify the user code to be executed. The association between the SIM and the user code may be directly associated, or indirectly associated by determining a group to which each SIM belongs and associating the group with the user code. In this case, it is possible to change the user code to be operated on a group basis. It is also possible to indirectly associate the SIM with the IoT device in which the SIM is installed and the user code.

[0041] In the cloud facility 112, at least one of the data that can be input to the user code and the processes that the user code can execute is restricted. In this embodiment, the data available to the user code is preferably restricted to data received by the cloud facility 112 and predetermined metadata. In this embodiment, the processes that can be executed by the user code are preferably restricted to processes that can be executed within a predetermined CPU time and with memory of a predetermined upper limit size. In addition, it is preferable to predetermine and restrict APIs (Application Programming Interfaces) that can be called in the user code.

[0042] The predetermined metadata includes data linked or associated with each SIM, and includes information set by the user about the SIM, information set by the user about the group to which the SIM belongs, etc., that is, the SIM's IMSI, SIM name, group name, source IP address, etc., that is, the SIM used in the communication is identified based on the TEID included in the header of data received by the cloud facility 112 through communication on the U-plane.

[0043] The metadata includes data linked or associated with each session, such as information that the cloud facility 112 holds about a session identified by a TEID included in the header, time information that the cloud facility 112 assigns when receiving data, etc. The cloud facility 112 may hold, for example, an identifier of the base station 120 to which the IoT device 130 is connected, or alternatively, may infer location information of the IoT device 130 from the identifier and store the location information as metadata in the storage unit 112-3 of the cloud facility 112 or in a storage device or storage medium 112-4 accessible from the cloud facility 112.

[0044] Restrictions on the computing resources that the user code can use include, for example, limiting CPU time to a predetermined number of seconds, such as 1, 2, or 3 seconds, and limiting the upper memory size to a predetermined number of MB, such as 32 MB or 128 MB. The user code is permitted to use computing resources such as the CPU and memory of the cloud facility 112 within a predetermined range to execute various types of computational processing. Examples of computational processing include arithmetic operations, arithmetic functions, conditional judgment using if statements, and loops using for statements.

[0045] Examples of the predetermined APIs that can be called within the user code include an API for leaving an operation log of the user code, an API for saving at least a part of the payload, an API for retrieving the saved data, an API for changing the destination of the payload, etc. By restricting the callable APIs, or more generally, the instructions to other programs that can be written within the user code, it is possible to prevent an unauthorized user from directly accessing the OS or middleware on the OS that constitutes the execution environment of the user code to view files or from accessing an IP network such as the Internet to send data to an unauthorized server without being granted authority.

[0046] The second facility 112 can determine whether or not the user code can be executed by referring to the correspondence between each SIM and an API that can be called in the user code. More specifically, the second facility 112 determines whether or not the SIM associated with the user code is authorized to call each API for each API declared as imported in the user code, and does not execute the user code if an API for which no authorization has been granted is declared as imported. The user code can perform various processes by calling APIs provided by the OS of the cloud facility 112 or middleware on the OS. In this embodiment, since an API for which no authorization has been granted cannot be called, even if the user is allowed to freely write the user code, there is a low possibility that the functions of the cloud facility 112 will be impaired.

[0047] Furthermore, when the instance responsible for communication processing is separated from the instance responsible for conversion processing of the payload, the user code is executed by the latter instance, and it is possible to further reduce the possibility that the OS of the instance responsible for communication processing or an API provided by middleware on the OS is unexpectedly called, causing a disruption to the communication processing function of the cloud facility 112. Also, by separating them in this way, it is possible to reduce the possibility that the user code will unexpectedly use the computing resources of the instance responsible for communication processing, causing a disruption to the communication processing function of the cloud facility 112. In other words, there is an advantage in not performing communication processing for transmitting data to an IP network in the instance that performs conversion processing on the payload.

[0048] User Code Example An example of possible operations on the payload by user code is described below.

[0049] If the IoT device 130 is provided with a button, the payload representing the pressing of the button can be processed into meaningful information. As an example, a "single press," a "double press," and a "long press" can be given the meanings of "clock in," "clock out," and "break," respectively, and then received by the external server 140 on the IP network.

[0050] Furthermore, if the IoT device 130 is provided with a temperature sensor and a humidity sensor, meaningful information can be added to a payload including temperature data and humidity data acquired from the temperature sensor and humidity sensor. As an example, a discomfort index determined by temperature and humidity can be calculated and added, or metadata associated with a SIM mounted in the IoT device 130 can be read and any data included therein can be added. The user can register the name of the SIM, the name of the person responsible for managing the SIM, and the like, as metadata for the SIM. Furthermore, the user can set a temperature threshold as metadata, and if the temperature represented by the temperature data included in the payload exceeds the threshold, a flag can be added to the temperature data.

[0051] Conversely, outliers, invalid values, etc. can be excluded from the payload, thereby reducing the amount of processing in the external server 150.

[0052] In addition, it is possible to decompress data transmitted in a compressed format from the IoT device 130. This makes it possible to reduce the amount of data communication by the IoT device 130.

[0053] Also, when the payload received from the IoT device 130 includes data having units such as seconds or temperature, the unit can be converted. This allows the user code to absorb differences in data formats resulting from the specifications of each IoT device and transmit the data to the external server 140. Conversely, when multiple SaaS services exist as link destinations, it is also possible to convert the data included in the payload for each link destination.

[0054] In addition, binary data transmitted from the IoT device 130 in an arbitrary proprietary format can be converted to JSON format. Depending on the user code, even data in a format with complex conditional branching can be parsed, and the data can be converted into a format that can be interpreted by the external server 140, such as JSON format, before being transmitted to the external server 140.

[0055] In addition, the location information of the IoT device 130 can be obtained using metadata linked to the SIM installed in the IoT device 130, and the payload can be transmitted to the external server 140 on the condition that the IoT device 130 has moved to a specific location or range. If necessary, an API for changing the destination of the payload is called in the user code. In addition, in order to transmit the payload to the external server 140 only when the above-mentioned conditions are satisfied, an API for discarding the payload and not transmitting it to the external server 140 when the specified conditions are not satisfied is called in the user code.

[0056] Second Embodiment In the first embodiment, it has been explained on the premise that the data from the IoT device 130 is transmitted to the external server 140 outside the core network after executing the user code, but depending on the type of data transmitted from the IoT device 130, it may be required to return a response to the IoT device 130 after executing the user code. In such a case, it is preferable to execute the user code at a node in the core network 110 that is physically close to the IoT device 130 in order to reduce delays and achieve high-speed responses.

[0057] FIG. 5 shows a sequence diagram according to the second embodiment of the present invention. First, the IoT device 130 transmits data with a required header added to the payload to the base station 120 (S501). The base station 120 removes the wireless header from the received data, and if it is 4G, adds a GTP-U header and transmits it to the MNO equipment 111 (S502). The MNO equipment 111 determines whether the data is associated with a specific SIM based on the TEID included in the header of the received data, and if associated, executes a pre-specified program on the payload of the data (S503). It is sufficient if the MNO equipment 111 can also refer to the association between the TEID and the user code to be executed described in the first embodiment.

[0058] For example, image data is sent from the IoT device 130 as a payload, and within the scope of the computing resources allowed for the user code in the MNO facility 111, image processing such as superimposing relatively simple AR images such as arrows, lines, frames, characters, and decorations is performed to respond. Also, voice data is sent from the IoT device 130 as a payload, and within the scope of the computing resources allowed for the user code in the MNO facility 111, voice processing such as translation and voice synthesis is performed to respond. Alternatively, it is possible to include required model data in the payload and generate the user code by executing the arithmetic processing described in the user code on the model data. Compared to the case where such data processing is performed by the external server 140 outside the core network, a transmission delay of about 100 msec may occur, but this can be significantly reduced, and especially in 5G, the effect of executing the user code at a node close to the IoT device 130 in the core network 110, more preferably at the node closest to the IoT device 130 in the core network 110 in communication on the U-plane, is remarkable.

[0059] In this embodiment, after the conversion process on the payload, a response is returned to the IoT device 130 (S505) via the base station 120 (S504), so the user code executed in the MNO equipment 111 needs to be authorized to make an API call to send a response from the MNO equipment 111 in communication on the U-plane.

[0060] In the first embodiment, all of the variations described for the cloud facility 112 or any node constituting the core network 110 can also be applied to the MNO facility 111. [Explanation of symbols]

[0061] 110 Communication Systems 111 First Facility 112 Second Facility 112-1 Communications Department 112-2 Processing section 112-3 Storage section 112-4 Storage medium 120 base station 130 IoT devices 140 External Server 310 Intermediate Server 320 User Terminals 412-1 First Instance 412-2 Second Instance

Claims

1. A method of data processing in a core network including a first facility and a second facility configured to receive data from an IoT device from the first facility through communication on a U-plane and transmit the data to an IP network, comprising: The facility determines whether or not there is a program associated with the IoT device and designated by a user, based on a session identifier included in a header of data received from the IoT device and indicating a session on the U-plane; a step of causing the program to execute processing on the data when the program is present; Includes.

2. 2. The method of claim 1 , The programs are limited in the processes they can execute.

3. 2. The method of claim 1 , The program has limitations on the data that can be entered.

4. A program for causing a core network comprising a first facility and a second facility configured to receive data from an IoT device from the first facility via communication on a U-plane and transmit the data to an IP network to execute a method for performing data processing on data from the IoT device, the method comprising: The facility determines whether or not there is a program associated with the IoT device and designated by a user, based on a session identifier included in a header of data received from the IoT device and indicating a session on the U-plane; a step of causing the program to execute processing on the data when the program is present; Includes.

5. A core network including a first facility and a second facility configured to receive data from an IoT device from the first facility through communication on a U-plane and transmit the data to an IP network, determining whether or not there is a program associated with the IoT device and designated by a user, based on a session identifier included in a header of data received from the IoT device and indicating a session on the U-plane; When the program is present, the program is configured to execute processing on the data.

Images