Apparatus, methods, and programs 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 Art

[0002] The number of devices connected to computer networks such as the Internet has been increasing, and the concept of the Internet of Things, in which all things are networked, has been spreading. Wireless communication services for networking devices have conventionally been directly provided by MNOs (mobile network operators) having a wireless communication infrastructure to end users. In recent years, however, operators called MVNOs (mobile virtual network operators) have been providing unique wireless communication services to end users using the wireless communication infrastructure of MNOs. An MVNE (mobile virtual network enabler), which provides support services for smooth operation of MVNOs, may intervene between MNOs and MVNOs, and in some cases, the MVNE receives SIMs from MNOs and provides them to MVNOs.

[0003] An MVNE or an MVNO that provides a wireless communication service for networked devices (hereinafter referred to as "IoT devices") may have its own communication infrastructure for providing access to a computer network such as an IP (Internet Protocol) network, thereby attempting to set communication quality such as communication speed and communication capacity according to price and meet various needs.

Summary of the Invention

Problems to be Solved by the Invention

[0004] In order to utilize the data collected from IoT devices using such services, users have had to build their own systems on the 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 significant burden. Furthermore, in order to use existing services such as SaaS, the format of the data transmitted from IoT devices must match the format of the service in question. However, this often does not happen, and ultimately a system for format conversion processing is required.

[0006] This invention has been made in view of the above problems, and its purpose is to enable data processing of data transmitted from IoT devices before it enters the 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] To achieve this objective, a first aspect of the present invention provides a data processing method in a node constituting a core network comprising a first piece of equipment that communicates with a base station and a second piece of equipment configured to receive data from an IoT device from the first piece of equipment via U-plane communication and transmit it to an IP network, the method comprising the steps of: the node receiving data from the IoT device; the node determining, based on the TEID included in the header of the data, whether or not there is a program associated with a SIM installed in the IoT device; and the node executing the program on the data if there is a program associated with the SIM, wherein the program has limitations on the processing it can perform.

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

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

[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 the following: an API that changes the destination of the data payload or the modified data thereof when predetermined conditions are met; an API that discards the data payload or the modified data thereof when predetermined conditions are met; and an API that transmits the modified data payload to the IoT device when predetermined conditions are met.

[0011] Furthermore, a fifth aspect of the present invention is characterized in that, in any of the second to fourth embodiments, the program has a restriction on the input data, and the input data includes data received from the IoT device, data associated with the SIM, and data associated with the session identified by the TEID.

[0012] Furthermore, 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 the information set in the SIM and the information set in the group to which the SIM belongs.

[0013] Furthermore, a seventh aspect of the present invention is characterized in that, in any of the first to sixth aspects, the node has first and second instances 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] Furthermore, an eighth aspect of the present invention is characterized in that, in the seventh aspect, the executable process is limited to a predetermined range of available computing resources of the second instance.

[0015] Furthermore, a ninth aspect of the present invention is a program for causing a node constituting a core network, which comprises a first piece of equipment that communicates with a base station and a second piece of equipment configured to receive data from an IoT device from the first piece of equipment via U-plane communication and transmit it to an IP network, to execute a method for processing data from the IoT device, wherein the method includes the steps of: the node receiving data from the IoT device; the node determining, based on the TEID included in the header of the data, whether or not there is a program associated with a SIM installed in the IoT device; and the node executing the program on the data if there is a program associated with the SIM, and the program is characterized in that the executable processing is predetermined.

[0016] Furthermore, a tenth aspect of the present invention is a node constituting a core network comprising a first piece of equipment that communicates with a base station, and a second piece of equipment configured to receive data from an IoT device from the first piece of equipment via U-plane communication and transmit it to an IP network, wherein the node receives data from the IoT device, determines whether or not there is a program associated with a SIM installed in the IoT device based on the TEID included in the header of the data, and if there is a program associated with the SIM, executes the program on the data, and the program has predetermined executable processes. [Effects of the Invention]

[0017] According to one aspect of the present invention, by imposing certain constraints on user code that can be executed on any node constituting the core network, it becomes possible to process data transmitted from IoT devices in the core network 110 before it goes out onto the IP network. [Brief explanation of the drawing]

[0018] [Figure 1] This figure shows a communication system according to a first embodiment of the present invention. [Figure 2] It is a sequence diagram according to the first embodiment of the present invention. [Figure 3] It is a diagram showing an example of cloud facilities according to the first embodiment of the present invention. [Figure 4] It is a diagram showing another example of cloud facilities according to the first embodiment of the present invention. [Figure 5] It is a sequence diagram according to the second embodiment of the present invention.

Mode for Carrying Out the Invention

[0019] Hereinafter, embodiments 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 the 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 configured to receive data from the IoT device 130 from the MNO facility 111 and transmit it to the IP network 140. Although two base stations are shown in FIG. 1, one of them will be described as an example. Also, although a large number of IoT devices 130 are shown in FIG. 1 by the SIMs (Subscriber Identity Modules) mounted on them, one of these will be described as an example.

[0021] In this specification, "MNO facility" means a facility for communication owned by an MNO, and "cloud facility" means a 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 according to demand on the network. For example, a 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. The cloud facility 112 is a node owned by an MVNE or MVNO, and is preferably an instance on the public cloud.

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

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

[0024] In this specification, "SIM" can be a physical SIM card, but can also be a semiconductor chip incorporated in the IoT device 130 (also called "eSIM"). It is also possible to install software in a secure area within the module of the IoT device 130 and store identifiers such as IMSI (International Mobile Subscriber Identity) on the software, and various modes are conceivable.

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

[0026] At base station 120, the wireless header is removed from the received data, and if it is 4G, a GTP-U header is added before transmitting it to MNO equipment 111 (S202). MNO equipment 111 then forwards the received data to cloud equipment 112 (S203).

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

[0028] Specifically, when a session is generated through communication on the C plane, a TEID representing each session is also generated, and the association between the TEID and the SIM used for communication on the U plane (hereinafter also referred to as the "first association") is stored in the cloud equipment 112 or a storage device or storage medium accessible to the cloud equipment 112. Furthermore, for the SIM used for communication on the U plane, an association (hereinafter also referred to as the "second association," which may include a specification of which user code should be executed if execution is required) indicating whether or not a program pre-specified by the user (hereinafter also referred to as the "user code") should be executed is stored in the cloud equipment 112 or a storage device or storage medium accessible to the cloud equipment 112. Based on the TEID contained in the header of the data received by the cloud equipment 112, the first and second associations are referenced, and the program is executed on the payload as necessary. Here, the first and second associations are described as separate, but they may be integrated into a single association, as long as the user code to be executed can be identified in some way based on the TEID. Furthermore, while this specification uses TEID as an identifier to identify a SIM, other identifiers may also be used if they can identify the SIM and the user code associated with the SIM.

[0029] Subsequently, the cloud equipment 112 adds the necessary headers to the converted payload and sends it to the application server 140 on the IP network (S205). In this case, as an example, in addition to converting the payload, the transport layer protocol can also 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. The above description does not explicitly state whether the user code deletes and adds headers, but in addition to modifying the payload, at least one of the deletion and addition of headers may be performed by the execution of the user code. Alternatively, instructions for adding headers may be written in the user code to another program, and the protocol conversion may be performed by that other program on the payload after the modification process by the user code.

[0030] As will be explained in more detail later, user codes have restrictions on the data that can be entered into them and the processes that can be executed. Therefore, even if user-created user codes can be executed on the cloud facility 112, the risk to security is mitigated.

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

[0032] Please note that unless the word "only" is explicitly stated, such as "based only on," "depending only on," or "in the case of only," it is assumed in this specification that additional information may also be considered. Also, please note that, for example, the statement "if a, then b" does not necessarily mean "always b in the case of a" or "b immediately after a," unless explicitly stated otherwise. Furthermore, the statement "each a constituting A" does not necessarily mean that A is composed of multiple components, but rather includes the possibility that the component is singular.

[0033] Furthermore, even if not explicitly stated herein, it is assumed that in aspects of the present invention, the data that can be entered into the user code and the processes that the user code can execute are limited to only a portion of those described herein.

[0034] Furthermore, for the sake of clarity, even if there are aspects of operation in some method, program, terminal, device, server, or system (hereinafter referred to as "method, etc.") that differ from the operation described herein, each aspect of the present invention is intended to cover the same operation as any of the operations described herein, and the existence of operation different from the operation described herein does not mean that such method, etc. is outside the scope of each aspect of the present invention.

[0035] Furthermore, while the user code is executed in the cloud equipment 112 as described above, the user code may also be executed in conjunction with one or more processes defined in any node within the core network 110. Specifically, the MNO equipment 111, such as an SGW, can execute the user code as needed based on the header of the data received from the base station 120 before forwarding the data. In addition, while the nodes constituting the core network in U-plane communication are the SGW and PGW in the case of 4G, it is also conceivable to deploy other network equipment such as routers, proxy servers, and load balancers. The user code can also be executed in these network equipment. The node executing the user code needs to have a direct or indirect correspondence between the TEID and the executable user code, and to have access to the data that can be input into the user code.

[0036] Furthermore, in this specification, the equipment called SGW in 4G is referred to as "MNO equipment," and the equipment called PGW is referred to as "cloud equipment." More generally, the former is sometimes referred to as "first equipment" and the latter as "second equipment." In this case, "first equipment" does not necessarily have to be equipment owned by a business operator that is not an MNO, as long as it performs the same role as the "MNO equipment" described above.

[0037] User Code Details User code executed on the cloud facility 112 can be specified by uploading it to the user of the communication service provided by the cloud facility 112. User code is uploaded from the user terminal 320 either directly to the cloud facility 112 or via an intermediary server 310 that can communicate with the cloud facility 112. User code can be a program in a predetermined binary or text format; for example, in binary format it can be in WebAssembly format, and in text format it can be in script formats such as Python or Javascript®.

[0038] The cloud equipment 112 comprises 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 memory or a hard disk. It can be configured by executing a program for each of these processes. The cloud equipment 112 may include one or more devices, computers, or servers. The program may also include one or more programs and can be recorded on a computer-readable storage medium to become a non-transient program product. The program is stored in the storage unit 112-3 or a storage medium 112-4 accessible from the cloud equipment 112 and can be executed by the processing unit 112-2. Uploaded user code is also stored in the storage unit 112-3 of the cloud equipment 112 or in a storage medium 112-4 accessible from the cloud equipment 112 via a computer network. Although not shown, the MNO equipment 111 can have a similar configuration.

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

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

[0041] In the cloud facility 112, at least one of the data that can be input to the user code and the processing that the user code can execute is restricted. In this embodiment, it is preferable that the data that can be used by the user code is restricted to data received by the cloud facility 112 and predetermined metadata. In this embodiment, it is preferable that the processing that can be executed by the user code is restricted to processing that can be executed within a predetermined CPU time and within a predetermined upper limit of memory. It is also preferable to pre-define and restrict the APIs (Application Programming Interfaces) that can be called within the user code.

[0042] The specified metadata includes data associated with or linked to each SIM, and identifies the SIM used in the communication based on the TEID included in the header of the data received by the cloud equipment 112 via communication on the U-plane. This metadata includes information set by the user for the SIM, information set by the user for the group to which the SIM belongs, etc. More specifically, it includes the SIM's IMSI, the SIM's name, the group's name, and the source IP address.

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

[0044] Restrictions on the computing resources available to user code include, for example, limiting CPU time to a predetermined number of seconds (e.g., 1, 2, or 3 seconds) and memory size to a predetermined number of megabytes (e.g., 32 MB or 128 MB). User code is permitted to use the computing resources of the cloud facility 112, such as CPU and memory, within the predetermined limits to perform various calculations. Examples of calculations include arithmetic operations, arithmetic functions, conditional statements such as if statements, and loops such as for statements.

[0045] Examples of APIs that can be called within user code include APIs for logging the user code's operation, APIs for saving at least a portion of the payload, APIs for retrieving saved data, and APIs for changing the payload's destination. By restricting the callable APIs, or more generally, the instructions that can be written within user code to other programs, it is possible to prevent users from directly accessing the OS or middleware on the OS that constitute the user code's execution environment to view files, or attempting to access IP networks such as the internet to send data to unauthorized servers, without being granted permission.

[0046] The second device 112 can determine whether user code can be executed by referring to the association between each SIM and the APIs that can be called within the user code. More specifically, the second device 112 determines whether the SIM to which the user code is associated has been granted permission to call each API declared as an import within the user code, and if an API for which permission has not been granted is declared as an import, the user code will not be executed. User code can perform various processes by calling APIs provided by the OS of the cloud device 112 or middleware on that OS, and in this embodiment, since APIs for which permission has not been granted cannot be called, even if users are allowed to freely write user code, there is little possibility that the functionality of the cloud device 112 will be disrupted.

[0047] Furthermore, by separating the instance responsible for communication processing from the instance responsible for conversion processing of the payload, the user code is executed on the latter instance, and the possibility of unexpectedly calling APIs provided by the OS or middleware on the OS of the instance responsible for communication processing, thereby disrupting the communication processing functions of the cloud facility 112, can be further reduced. In addition, by separating them in this way, the possibility of the user code unexpectedly using the computing resources of the instance responsible for communication processing, thereby disrupting the communication processing functions of the cloud facility 112, can be reduced. In other words, there is an advantage to not performing communication processing for data transmission to the IP network in the instance that performs conversion processing of the payload.

[0048] Example of user code This section describes examples of how user code can process payloads.

[0049] If the IoT device 130 has a button, the payload indicating that the button has been pressed can be processed into meaningful information. For example, "single press," "double press," and "long press" can be assigned meanings such as "clock in," "clock out," and "break," respectively, and then received by an external server 140 on the IP network.

[0050] Furthermore, if the IoT device 130 is equipped with a temperature sensor and a humidity sensor, meaningful information can be added to the payload containing the temperature data and humidity data acquired from each sensor. For example, a discomfort index determined by temperature and humidity can be calculated and added, or metadata linked to the SIM installed in the IoT device 130 can be read and any of the data contained therein can be added. Users can register the name of the SIM, the name of the person responsible for managing the SIM, etc., as metadata for that SIM. In addition, users can set a temperature threshold as metadata, and if the temperature represented by the temperature data included in the payload exceeds that threshold, a flag can be added to that temperature data.

[0051] Conversely, outliers, invalid values, etc., can be excluded from the payload. This reduces the processing required on the external server 150.

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

[0053] Furthermore, if the payload received from the IoT device 130 contains data with units such as seconds or temperature, the units can be converted. This allows the user code to absorb differences in data format due to the specifications of each IoT device and transmit them to the external server 140. Conversely, if there are multiple SaaS services as partners, it is also possible to convert the data included in the payload according to each partner.

[0054] Furthermore, binary data transmitted from the IoT device 130 in any proprietary format can be converted into JSON format. The user code allows for parsing even data with complex conditional branching, and the data can be converted into a format that can be interpreted by the external server 140, such as JSON, before being transmitted to the external server 140.

[0055] Furthermore, the system can obtain the location information of the IoT device 130 using metadata linked to the SIM card installed in the IoT device 130, and send the payload to the external server 140 if the device has moved to a specific location or range. If necessary, an API to change the destination of the payload is called within the user code. In addition, since the payload is sent to the external server 140 only when the above conditions are met, an API is called within the user code to discard the payload and prevent it from being sent to the external server 140 if the predetermined conditions are not met.

[0056] (Second embodiment) In the first embodiment, the description assumed that user code was executed on data from the IoT device 130 and then sent to an external server 140 outside the core network. However, depending on the type of data transmitted from the IoT device 130, it may be necessary to return a response to the IoT device 130 after executing the user code. In such cases, it is preferable to execute the user code at a node within the core network 110 that is physically close to the IoT device 130 in order to reduce latency and achieve a fast response.

[0057] Figure 5 shows a sequence diagram according to a second embodiment of the present invention. First, the IoT device 130 transmits data to the base station 120 with the required header added to the payload (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 predetermined SIM based on the TEID included in the header of the received data, and if it is associated, executes a pre-specified program on the payload of the data (S503). The correspondence between the TEID and the user code to be executed, as described in the first embodiment, should be accessible to the MNO equipment 111 as well.

[0058] For example, image data may be transmitted from the IoT device 130 as a payload, and the MNO equipment 111 may respond by performing image processing such as overlaying relatively simple AR images like arrows, lines, borders, characters, and decorations, within the limits of the computing resources allowed by the user code. Alternatively, voice data may be transmitted from the IoT device 130 as a payload, and the MNO equipment 111 may respond by performing voice processing such as translation and speech synthesis, within the limits of the computing resources allowed by the user code. Alternatively, it is conceivable to include the required model data in the payload and generate the data by executing the calculations described in the user code on the model data. Compared to performing such data processing on an external server 140 outside the core network, a transmission delay of about 100 msec may occur, but this can be significantly reduced. In particular, in 5G, the effect of executing the user code on a node close to the IoT device 130 within the core network 110, or more preferably on the node closest to the IoT device 130 in communication on the U-plane, is significant.

[0059] In this embodiment, after the conversion process for the payload, a response is sent to the IoT device 130 via the base station 120 (S504) (S505). Therefore, the user code executed by the MNO equipment 111 must be authorized to make API calls to send responses from the MNO equipment 111 in communication over the U-plane.

[0060] Furthermore, all the variations described in the first embodiment for any node constituting the cloud equipment 112 or the core network 110 are also applicable to the MNO equipment 111. [Explanation of Symbols]

[0061] 110 Communication Systems 111 First Equipment 112 Second facility 112-1 Communications Department 112-2 Processing Unit 112-3 Storage section 112-4 Storage medium 120 base station 130 IoT devices 140 External Servers 310 Intervening Server 320 user terminals 412-1 First instance 412-2 Second instance

Claims

1. A data processing method in equipment constituting a core network comprising a first piece of equipment and a second piece of equipment configured to receive data from IoT devices from the first piece of equipment via U-plane communication and transmit it to an IP network, The equipment includes a step of determining whether a program specified by the user exists, which is associated with a session identifier indicating a session on the U-plane and is included in the header of the data received from the IoT device. The equipment, if it has a program, includes the step of causing the program to perform processing on the data. Includes.

2. The method according to claim 1, The aforementioned program has limitations on the types of operations it can perform.

3. The method according to claim 1, The aforementioned program has limitations on the types of data that can be input.

4. A program for causing equipment constituting a core network, which comprises a first piece of equipment and a second piece of equipment configured to receive data from IoT devices from the first piece of equipment via U-plane communication and transmit it to an IP network, to execute a method for processing data from the IoT devices, wherein the method is: The equipment includes a step of determining whether a program specified by the user exists, which is associated with a session identifier indicating a session on the U-plane and is included in the header of the data received from the IoT device. The equipment, if it has a program, includes the step of causing the program to perform processing on the data. Includes.

5. Equipment comprising a first piece of equipment and a second piece of equipment configured to receive data from IoT devices from the first piece of equipment via U-plane communication and transmit it to an IP network, A program associated with a session identifier indicating a session on the U-plane, included in the header of the data received from the IoT device, which determines whether or not a program specified by the user exists. If the aforementioned program exists, the system is configured to have the program perform the processing on the aforementioned data.

Images