A transmission method and system of state update data packet in internet of things

Abstract

A kind of transmission method and system of state update data packet in Internet of Things, each Internet of Things equipment is connected to base station by 5G wireless network, and state update data packet is sent to Internet of Things application server, comprising: UPF network element loads each state update data packet received into a Capsu le frame and is compressed, then the compressed Capsu le frame is placed in the queue in the queue in the queue, simultaneously, according to the queuing order from the queue in the queue in the queue multiple Capsu le frames are taken to constitute a QUIC data packet, and the QUIC data packet is encapsulated and forwarded to edge proxy server;Edge proxy server is split from each QUIC data packet received All Capsu le frames, then each Capsu le frame is decompressed and restored into state update data packet, and is forwarded to corresponding Internet of Things application server.The present application relates to the field of computer technology, can efficiently transmit the state update data packet in mass Internet of Things scene, to guarantee the network service demand of state update task in mass Internet of Things scene.

Description

TECHNICAL FIELD

[0001] The present application relates to a method and system for transmitting state update data packets in an Internet of Things, and relates to the technical field of computer technology. BACKGROUND

[0002] Massive Internet of Things communication can support large-scale access of Internet of Things devices and reliable communication network connection without human intervention, and is committed to providing extensive coverage and network services supporting massive connection requirements for low-power and low-complexity Internet of Things communication devices, which has great market potential and will create a new business model. With the development of 5G and future 5G and above networks, Internet of Things type communication is receiving more and more attention. It is estimated that there are 3.9 billion machine type communication devices accessing the network by 2023, and will play a significant role in many fields such as industrial automation, smart medicine, environmental monitoring, smart cities, and smart homes.

[0003] In the massive Internet of Things scenario, in order to complete the remote control task, the Internet of Things device needs to send data packets containing state update data to update the device state information in the server. The data packets in the massive Internet of Things have three characteristics: first, the data packets have the characteristics of short packet communication, and the data size of the state update information is often only hundreds of bits, which makes the load utilization rate of the data packet very low. Second, the generation method of the state update data has randomness, because the Internet of Things device usually generates state update data due to changes in the external environment, which makes the generation time interval of the data packet very random, causing the distribution of the state update traffic to have randomness. Third, the flow direction of the state update traffic has concentration, because the Internet of Things application is usually deployed on the edge cloud or central cloud, so the state update traffic of the massive Internet of Things device usually flows to the data center.

[0004] The requirement report of the Third Generation Partnership Project points out that the transmission task of the state update data packet in the massive Internet of Things scenario has strict delay and information freshness requirements. However, with the increase in the number of Internet of Things devices accessing the network, the computing and communication burden of the network access point is huge, and the randomness of the state update traffic causes traffic fluctuations on the backbone network router, causing a state update data storm, causing the delay of the Internet of Things application to surge, and ultimately causing the state update to be suspended, so that the Internet of Things application cannot work normally. Therefore, the existing network scheduling and management technology cannot meet the heterogeneous requirements of the state update task in the massive Internet of Things scenario.

[0005] Therefore, how to efficiently transmit the state update data packet in the massive Internet of Things scenario, so as to guarantee the network service requirements of the state update task in the massive Internet of Things scenario, has become a technical problem that technical personnel focus on. SUMMARY

[0006] In view of the above, the purpose of the present application is to provide a transmission method and system for state update data packets in the Internet of Things, which can efficiently transmit state update data packets in a massive Internet of Things scenario, thereby guaranteeing the network service demand of state update tasks in the massive Internet of Things scenario.

[0007] In order to achieve the above purpose, the present application provides a transmission method for state update data packets in the Internet of Things, each Internet of Things device is connected to a base station through a 5G wireless network and sends a state update data packet to an Internet of Things application server, comprising:

[0008] Step one, the UPF network element loads each received state update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into a forwarding queue for queuing, at the same time, a plurality of Capsule frames are taken out from the forwarding queue in order to form a QUIC data packet, and the QUIC data packet is encapsulated and forwarded to the edge proxy server;

[0009] Step two, the edge proxy server separates all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame to restore it to a state update data packet, and forwards it to the corresponding Internet of Things application server.

[0010] In order to achieve the above purpose, the present application also provides a transmission system for state update data packets in the Internet of Things, comprising a UPF network element, an edge proxy server, a plurality of Internet of Things devices and a plurality of Internet of Things application servers, wherein:

[0011] The Internet of Things device is connected to the base station through the 5G wireless network and sends the state update data packet to the Internet of Things application server;

[0012] The UPF network element receives the state update data packet sent by the Internet of Things device, loads each state update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into a forwarding queue for queuing, at the same time, a plurality of Capsule frames are taken out from the forwarding queue in order to form a QUIC data packet, and the QUIC data packet is encapsulated and forwarded to the edge proxy server;

[0013] The edge proxy server separates all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame to restore it to a state update data packet, and forwards it to the corresponding Internet of Things application server;

[0014] The Internet of Things application server receives the state update data packet sent by the Internet of Things device to update the state of the Internet of Things device accordingly.

[0015] To achieve the above object, the application further provides a computing device, comprising:

[0016] a memory and a processor;

[0017] The memory is used for storing computer executable instructions, and the processor is used for executing the computer executable instructions, which realize the steps of the transmission method of the state update data packet in the Internet of Things when executed by the processor.

[0018] To achieve the above object, the application further provides a computer readable storage medium, which stores computer executable instructions, which realize the steps of the transmission method of the state update data packet in the Internet of Things when executed by the processor.

[0019] Compared with the prior art, the application has the beneficial effects that: the application is based on the QUIC (Quick UDP Internet Connection) protocol, and is deployed in the container in the user plane network element UPF (User Plane Function) of the core network and the proxy node container at the edge side of the operator backbone network, an upper layer tunnel is established between the two end container nodes, the state update traffic is scheduled and managed, the application can be started or stopped at any time according to the demand of the operator as a network middleware, and supports elastic expansion and container deployment, and can also customize the traffic policy according to the demand; the application processes the state update data packet by using the lossless aggregation and compression mechanism, reduces the number of data packets and the number of bytes passing through the operator network, based on the customized modification of the QUIC protocol, the application can realize the lossless aggregation and accurate segmentation of short data packets of different sizes, and by maintaining a dynamic compression table at both ends of the tunnel, the state update data packet can be automatically compressed and restored, the aggregation and compression mechanism accelerates the transmission of the state update data packet, and the user and the upper layer application are not aware of the whole process; the application also designs a low complexity algorithm for scheduling the state update traffic based on information freshness, since the state update traffic is all application traffic, and the traffic has strong randomness, the commonly used priority-based scheduling algorithm and flow completion time-based scheduling algorithm are difficult to perceive the importance of the traffic, and the information freshness is an index for measuring the state update process, by using the scheduling algorithm based on the information freshness, the application realizes the performance improvement of the whole state update system, and meets the demand of the Internet of Things application for updating the state. BRIEF DESCRIPTION OF DRAWINGS

[0020] Figure 1 is a flow chart of a transmission method of a state update data packet in the Internet of Things according to an exemplary embodiment of the application.

[0021] Figure 2is an example embodiment of the present application Figure 1 In step one, the UPF network element loads each received state update data packet into a Capsule frame and compresses it.

[0022] Figure 3 is a structure diagram of a state update data packet transmission system in an Internet of Things according to an example embodiment of the present application.

[0023] Figure 4 is a structure diagram of a computer device according to an example embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical scheme and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings.

[0025] As Figure 1 shown, the present application provides a state update data packet transmission method in an Internet of Things, each Internet of Things device is connected to a base station through a 5G wireless network and sends a state update data packet to an Internet of Things application server deployed in the cloud, including:

[0026] Step one, the UPF network element loads each received state update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into a to-be-forwarded queue for queuing, at the same time, takes multiple Capsule frames from the to-be-forwarded queue in the queuing order to constitute a QUIC data packet, and forwards the encapsulated QUIC data packet to an edge proxy server;

[0027] Step two, the edge proxy server divides all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame to restore it into a state update data packet, and forwards it to the corresponding Internet of Things application server.

[0028] The application is based on the construction of upper layer forwarding tunnel based on the QUIC protocol, and the tunnel is deployed on the UPF network element side in the 5G core network and the edge proxy server of the operator backbone network. A large number of Internet of Things devices are connected to the base station through the 5G wireless network, and the state update data packet whose destination address points to the Internet of Things application deployed in the cloud is sent. According to the structure of the 5G core network, all state update flows need to pass through the UPF network element, so the application is designed in the export side network card queue of the UPF network element, and the state update flow is captured based on the kernel flow filtering technology, and each state update data packet is sent into the container of the tunnel entrance. The tunnel exit is deployed in the edge proxy server on the data center side, which is responsible for restoring each data packet in the tunnel into the original state update data packet sent by the Internet of Things device, and further forwarding. The whole process is transparent to the Internet of Things application and user, realizes the lossless acceleration of the state update flow, overcomes the increase of delay caused by the state update data storm, and guarantees the network service quality requirements of a large number of Internet of Things devices for stable low delay.

[0029] It should be explained that a network connection will be established between the Internet of Things device and the Internet of Things application deployed in the cloud, and the Internet of Things device will continuously send its own state update data to the Internet of Things application in the form of state update data packet, which is defined as a state update flow. Taking the "temperature sensor" as an example, the Internet of Things device will send the collected temperature data to the Internet of Things application, usually in two forms: periodic sending (such as every 1s), or event-driven (such as the temperature changes from 20 degrees to 30 degrees). After receiving the new state update data packet, the Internet of Things application will use the new state update data to overwrite the old state update data, thereby realizing state update. The application mainly faces the Internet of Things devices connected to the Internet through 5G, and all data packets transmitted through 5G need to pass through the 5G core network. The UPF network element is responsible for the management and forwarding of all data packets in the 5G core network, and is the network element that all flows must pass through.

[0030] The QUIC protocol used by the application to construct the upper layer forwarding tunnel is a connection-oriented transmission protocol. QUIC performs version negotiation and encrypted transmission handshake at the same time when establishing a connection, which makes the first establishment of QUIC connection only need to spend 1-RTT, and only need to perform 0-RTT handshake when re-establishing the connection. The data transmission of QUIC connection is carried out by exchanging data packets, and the QUIC data packet is transmitted in the UDP data report. The data packet with a short header in the QUIC protocol is used to transmit data, each data packet is composed of a small amount of unencrypted header information and encrypted load, and the header information includes connection ID, data packet number and the like. The load of the QUIC packet is usually composed of a frame sequence, and the load of each QUIC packet contains at least one frame and can contain data frames from different data streams.

[0031] The QUIC protocol is constructed at the application layer, which makes it deployed as part of an application, allows it to be personalized for various applications, and ensures that it can be versioned when the application is updated. The QUIC protocol runs based on the UDP protocol, which ensures that the QUIC data packet can safely pass through the firewall and middleware, while the QUIC data packet is forced to be authenticated and encrypted, which can effectively prevent the middleware from stealing and modifying the data information. Therefore, the application is implemented based on the QUIC protocol and its data packet extension, without modifying the kernel, and is easy to deploy. And the tunnel between the UPF network element side and the edge proxy server is also an encrypted QUIC connection, which can fully guarantee the security of data transmission.

[0032] The state update data packet sent by the Internet of Things device will enter the cache queuing queue when it reaches the network intermediate device such as the router or the switch. Due to the concentrated flow direction of the state update traffic, a single network intermediate device may simultaneously receive traffic from a large number of heterogeneous Internet of Things devices, and different Internet of Things devices produce state update data at different frequencies. Therefore, the length of the queuing queue of the network intermediate device presents a sharp fluctuation, and when a group of state update data bursts in a short time, the queue length will increase sharply. Since the network intermediate device cannot process a large number of data packets in a short time, the state update data packet queuing delay increases sharply, so that the state update data cannot reach the server in time, and the state update task cannot meet the demand. In order to solve this problem, the application designs a capsule aggregation and lossless compression mechanism: when the traffic aggregation function is started, the state update data packet will be filtered out according to the IP address characteristics of the target traffic, and each state update data packet will be put into the Capsule frame of the QUIC protocol as a load. Since a single QUIC data packet can contain multiple frames, an aggregated QUIC data packet will load multiple Capsule frames queued in the queuing queue, which are composed of state update data packets, thereby completing aggregation. Then, the aggregated data packet is sent to the edge proxy server through the QUIC network connection between the UPF side tunnel entrance and the edge proxy server tunnel exit. Finally, when the aggregated QUIC data packet reaches the edge proxy server, each aggregated data packet will be accurately segmented according to the Capsule frame header indication, and the segmented data packet will be handed over to the corresponding state update task according to the data packet header indication. By aggregating data packets, the application can reduce the number of data packets to be sent in the network intermediate device, and relieve the computing and communication pressure of the queuing queue. And the application provides a data packet compression function, which can reduce the number of bytes of the network card exit by compressing the size of the data packet, thereby breaking the forwarding performance bottleneck of the network intermediate device and accelerating the transmission of the data packet.

[0033] As further optional implementation, the application can further use compression function in tunnel for state update flow to reduce network load, i.e. a dynamic compression table is maintained at both UPF network element and edge proxy server, and the dynamic compression table is used to save hash mapping relationship between Flow ID field of each Capsule frame and IP packet header five-tuple of contained state update data packet. As shown in Figure 2 Figure 1 In step one, UPF network element loads each received state update data packet into a Capsule frame, which can further include:

[0034] Step 11, UPF network element receives each state update data packet, reads IP packet header five-tuple of the state update data packet, judges whether the read IP packet header five-tuple exists in its dynamic compression table, if not, it indicates that the state update flow to which the state update data packet belongs is not registered, and continues to step 12; if yes, it indicates that the state update flow to which the state update data packet belongs is registered, and continues to step 13.

[0035] Step 12, UPF network element uses hash function to assign a Flow ID for the read IP packet header five-tuple, and then registers the hash mapping relationship between the read IP packet header five-tuple and the assigned Flow ID into its dynamic compression table, and then continues to step 13.

[0036] Step 13, UPF network element extracts state update data from the state update data packet, writes into frame payload of a Capsule frame, extracts Flow ID corresponding to IP packet header five-tuple of the state update data packet from its dynamic compression table, and then fills the extracted Flow ID into Flow ID field of frame header of the Capsule frame.

[0037] At this point, UPF network element completes the encapsulation of Capsule frame, and it needs to be noted that, in addition to Flow ID field and field identifying frame length, frame header of Capsule frame also contains necessary information of original IP data packet (in case of TCP, it also includes sequence number, ACK number and sliding window, etc.), and frame payload contains encrypted original state update data.

[0038] As further optional implementation, a coding stream and a decoding stream are further established between UPF network element and edge proxy server, and the coding stream and the decoding stream are used to synchronize content of dynamic compression tables at both ends, and step 12 can further include:

[0039] ​UPF network element sends a set of structure bodies containing the hash mapping relationship of IP packet header quintuple and the Flow ID allocated to it to the edge proxy server through the encoding stream, the edge proxy server registers the hash mapping relationship of IP packet header quintuple and Flow ID in its dynamic compression table, and then returns the ACK message through the decoding stream to indicate that it has completed the registration of the state update stream, when the UPF network element receives the ACK information sent by the decoding stream, it also registers the corresponding hash mapping relationship of IP packet header quintuple and Flow ID in its dynamic compression table.

[0040] Massive Internet of Things devices implement accurate judgment and decision implementation by sending state update data packets to Internet of Things applications deployed in the cloud. In the state update process, information freshness is used as an indicator to measure state update. Information age is usually calculated to judge information freshness. The larger the information age, the lower the information freshness, which means the worse the state update process. The smaller the information age, the higher the information freshness, which means the better the state update process. Information age is defined as the time when the state update data packet arrives at the destination, minus the time when the state update data packet is generated. In order to better standardize the information age, the average information age is usually used as an indicator, that is, the information age is integrated and divided by the length of the time window. In order to measure the information age of the entire system, the present application regards each state update stream as a state update process, adds the average information age of all Internet of Things devices, and then divides by the total number of devices to obtain the system average information age.

[0041] There are mainly two kinds of existing traffic scheduling algorithms. The first is to schedule based on data packet priority, for example, to distinguish the priority of data packets based on the DSCP of the IP packet header. However, according to the applicant's statistics of existing traffic, the state update data packets sent by massive Internet of Things devices are all marked as "default application data", so the importance of massive state update data packets cannot be intuitively distinguished. The second is to schedule based on flow completion time, and the scheduling goal is to minimize the flow completion time, but the importance of state update flow has no direct relationship with the duration of the flow, and is related to the urgency of the demand of the Internet of Things application for state update. Therefore, unlike existing traffic scheduling algorithms, the present application designs a traffic scheduling algorithm for massive Internet of Things scenarios with the indicator of minimizing information freshness.

[0042] According to data analysis, if the minimum system average age is taken as the scheduling algorithm target, due to the existence of calculus, the scheduling algorithm will prefer to send the status update stream of the Internet of Things device with a larger generation period first. However, the generation period is not directly related to the urgency of the demand of the Internet of Things application for the status update, so taking the minimum system average age as the scheduling target will damage the fairness of the network scheduling algorithm. Therefore, the application also proposes a new index for measuring the influence of the network on the system status update, that is, the normalized system average age. By normalizing the average age and the age of the traffic generation process, the normalized system average age can be obtained. The smaller the normalized system average age is, the better the performance of the network on the entire status update system, that is, the current network management algorithm is more beneficial to the status update.

[0043] In summary, further as an optional implementation manner, the application takes the minimum normalized system average age as the scheduling target, and designs a new traffic scheduling algorithm, so that the intermediate device in the network can perceive the demand of the Internet of Things application for updating the status and perform scheduling based on the demand. Figure 1 In step one, the UPF network element puts the compressed Capsule frame into the to-be-forwarded queue for queuing, and can further include:

[0044] In step A1, the UPF network element calculates the age expectation of the status update stream to which the status update data packet in the Capsule frame belongs according to the IP packet header five-tuple of the status update data packet: Among them, is the calculation time period of the age expectation, that is, a time period with as the time length and the generation time of the status update data packet contained in the Capsule frame as the end time, can be set according to actual business needs, is the age expectation of the status update stream to which the status update data packet contained in the Capsule frame belongs during , t i and t i-1 are the generation times of the i-th and i-1-th status update data packets pkt i and pkt i-1 of the status update stream to which the status update data packet contained in the Capsule frame belongs during , and n is the total number of all status update data packets of the status update stream to which the status update data packet contained in the Capsule frame belongs during ;

[0045] In step A2, the UPF network element calculates the information freshness perception scheduling operator of the status update data packet contained in the Capsule frame: wherein O perator is the information freshness-aware scheduling operator of the status update data packet contained in the Capsule frame, M is the generation time interval of the status update data packet contained in the Capsule frame, t and t' are the generation times of the status update data packet contained in the Capsule frame and the previous status update data packet of the status update stream to which the status update data packet belongs, respectively, and size is the length of the status update data packet contained in the Capsule frame, and then the compressed Capsule frame is inserted into the corresponding position in the to-be-forwarded queue using a binary insertion algorithm according to the size of the information freshness-aware scheduling operator value of the status update data packet contained in all Capsule frames in the to-be-forwarded queue.

[0046] The larger the Operator is, the greater the influence of the status update data packet on the status update is, and the more urgent the status update demand of the Internet of Things application is, so the larger the Operator of the status update data packet is, and the earlier the queuing order of the status update data packet in the to-be-forwarded queue is, so that the status update data packet can be sent preferentially.

[0047] Further, as an optional implementation, Figure 1 In step one, the UPF network element takes out a plurality of Capsule frames from the to-be-forwarded queue in the queuing order to constitute a QUIC data packet, and encapsulates and forwards the QUIC data packet to the edge proxy server, which can further include:

[0048] Step B1, the UPF network element takes out the first Capsule frame from the to-be-forwarded queue in the queuing order and puts it into the QUIC data packet;

[0049] Step B2, the UPF network element judges whether the remaining load length of the QUIC data packet is greater than the length of the next Capsule frame in the to-be-forwarded queue, if yes, the next Capsule frame is taken out from the to-be-forwarded queue and put into the QUIC data packet, and then step B2 is turned to; if not, the QUIC data packet is encapsulated and forwarded to the edge proxy server.

[0050] The UPF network element takes out the Capsule frames from the to-be-forwarding queue in the order of queuing and puts them into a QUIC data packet for packaging. According to the load length of the QUIC data packet (usually the maximum segment size, MSS), each QUIC data packet can aggregate multiple Capsule frames with state update data. The UPF network element will put as many Capsule frames as possible into a single QUIC data packet, but in order to ensure the integrity of the data, the UPF network element will not split a single Capsule frame. In this way, when the remaining load length of the QUIC data packet is not enough to put in the next Capsule frame, the UPF network element will complete the packaging of the QUIC data packet and forward it to the edge proxy server, and then start the packaging process of the next QUIC data packet. For example, the maximum load length of the QUIC data packet is usually set to 1370 bytes, and if the length of each compressed Capsule frame with state update data is 100 bytes, then one QUIC can hold 13 Capsule frames.

[0051] Further, as an optional implementation, when the QUIC data packet arrives at the edge proxy server, step two can further include:

[0052] The edge proxy server divides the QUIC data packet into multiple Capsule frames according to the length field in the frame header of each Capsule frame in the received QUIC data packet, reads the Flow ID from the frame header of each divided Capsule frame, queries the dynamic compression table to obtain the IP packet header quintuple corresponding to the Flow ID, reads the state update data from the load of each Capsule frame, and finally restores the original state update data packet based on the IP packet header quintuple and the state update data, and forwards it to the corresponding Internet of Things application server.

[0053] In this way, when a state update data packet that has been registered in the table arrives at the tunnel entrance, its original packet header is replaced by the Flow ID field in the Capsule frame, and when the Capsule frame arrives at the tunnel exit and is parsed, the Flow ID field is restored to the quintuple, thereby reconstructing the original state update data packet. Since the state update data packet is mainly composed of short packets, the length of the packet header in the short packet results in a low effective payload utilization rate of the bandwidth. The application can greatly reduce the number of bytes of the state update traffic by compressing the packet header information, thereby reducing the forwarding pressure of the network intermediate devices of the operator.

[0054] As Figure 3As shown, the application is a state update data packet transmission system in the Internet of Things, which comprises a UPF network element, an edge proxy server, a plurality of Internet of Things devices and a plurality of Internet of Things application servers, wherein:

[0055] The Internet of Things device is connected to the base station through the 5G wireless network and sends the state update data packet to the Internet of Things application server deployed in the cloud;

[0056] The UPF network element is a functional unit in the 5G core network responsible for managing, scheduling and forwarding bidirectional traffic, receives the state update data packet sent by the Internet of Things device, loads each state update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the queuing queue for queuing, at the same time, takes out a plurality of Capsule frames from the queuing queue according to the queuing order to constitute a QUIC data packet, and then encapsulates and forwards the QUIC data packet to the edge proxy server;

[0057] The edge proxy server is an edge service node deployed in different regions, responsible for communication with users in its geographical vicinity, divides all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame to restore it to a state update data packet, and forwards it to the corresponding Internet of Things application server;

[0058] The Internet of Things application server is usually an elastic resource server deployed in the cloud or self-built data, and runs the Internet of Things application program, receives the state update data packet sent by the Internet of Things device, updates the state of the Internet of Things device according to the state update data packet, so as to make decisions based on the latest state information of the Internet of Things device.

[0059] Referring to Figure 4 , Figure 4 is a structural block diagram of a computing device 400 according to an exemplary embodiment of the present specification. The components of the computing device 400 include but are not limited to a memory 410 and a processor 420. The processor 420 is connected to the memory 410 through a bus 430, and a database 450 is used to save data.

[0060] The computing device 400 also includes an access device 440 that enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or combinations of these and / or other types of networks that are known in the art. The access device 440 can include one or more of any type of network interface (for example, a network interface card (NIC)), wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and / or the like.

[0061] In one embodiment of the present specification, the above-mentioned components of the computing device 400 and other components not shown in the Figure 4 may be connected to each other, for example, through a bus. It should be understood that Figure 4 The computing device structure diagram shown is for the purpose of example only, and is not a limitation on the scope of the present specification. Other components can be added or replaced as needed by those skilled in the art.

[0062] The computing device 400 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (for example, a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, and the like), a mobile phone (for example, a smartphone), a wearable computing device (for example, a smart watch, smart glasses, and the like), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 400 can also be a mobile or stationary server or cloud server, and the like.

[0063] The processor 420 is configured to execute computer-executable instructions, which, when executed by the processor, implement the steps of the above-mentioned method for transmitting state update data packets in an Internet of Things.

[0064] The above is a schematic scheme of the computing device of the embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the transmission method of the state update data packet in the Internet of Things belong to the same concept, and the details of the technical scheme of the computing device that are not described in detail can be seen from the description of the technical scheme of the transmission method of the state update data packet in the Internet of Things.

[0065] An embodiment of the present specification further provides a computer readable storage medium storing computer executable instructions, which, when executed by a processor, implement the steps of the transmission method of the state update data packet in the Internet of Things.

[0066] The above is a schematic scheme of the computer readable storage medium of the embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the transmission method of the state update data packet in the Internet of Things belong to the same concept, and the details of the technical scheme of the storage medium that are not described in detail can be seen from the description of the technical scheme of the transmission method of the state update data packet in the Internet of Things or the system.

[0067] An embodiment of the present specification further provides a computer program, which, when executed in a computer, causes the computer to perform the steps of the transmission method of the state update data packet in the Internet of Things.

[0068] The above is a schematic scheme of the computer program of the embodiment. It should be noted that the technical scheme of the computer program and the technical scheme of the transmission method of the state update data packet in the Internet of Things belong to the same concept, and the details of the technical scheme of the computer program that are not described in detail can be seen from the description of the technical scheme of the transmission method of the state update data packet in the Internet of Things or the system.

[0069] The above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the acts or steps recited in the claims can be performed in a different order than the order in which they are recited and still achieve desirable results. In addition, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing can be advantageous.

[0070] The computer readable medium can include any entity or apparatus capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, software distribution medium, etc.

[0071] It should be noted that, for the foregoing method embodiments, in order to facilitate description, they are all described as a combination of a series of actions, but those skilled in the art should know that the present application is not limited to the order of the actions described, because according to the present application, certain steps can be performed in other order or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0072] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for transmitting a state update data packet in an Internet of Things, characterized in that, Each Internet of Things device is connected to a base station through a 5G wireless network and sends a state update data packet to an Internet of Things application server, including: Step one, the UPF network element loads each received state update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the pending forwarding queue for queuing, at the same time, a plurality of Capsule frames are taken out from the pending forwarding queue in the queuing order to constitute a QUIC data packet, and the QUIC data packet is encapsulated and forwarded to the edge proxy server; Step two, the edge proxy server splits all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame to restore it to a state update data packet, and forwards it to the corresponding Internet of Things application server, In step one, the UPF network element puts the compressed Capsule frame into the pending forwarding queue for queuing, further comprising: Step A1, the UPF network element calculates the age expectation of the state update flow to which the state update data packet contained in the Capsule frame belongs according to the IP packet header quintuple of the state update data packet: wherein, is the calculation period of the age expectation, that is, a time period ending at is a time period with a time length and ending at the generation time of the state update data packet contained in the Capsule frame, is the age expectation of the state update flow to which the state update data packet contained in the Capsule frame belongs during , , are respectively the generation times of the i-th and i-1-th state update data packets of the state update flow to which the state update data packet contained in the Capsule frame belongs during , , , and n is the total number of all state update data packets of the state update flow to which the state update data packet contained in the Capsule frame belongs during . Step A2, the UPF network element calculates the information freshness-aware scheduling operator of the status update data packet contained in the Capsule frame: , , is the information freshness-aware scheduling operator of the status update data packet contained in the Capsule frame, is the generation time interval of the status update data packet contained in the Capsule frame, , are the generation times of the status update data packet contained in the Capsule frame and the previous status update data packet of the status update stream to which the status update data packet belongs, respectively, is the length of the status update data packet contained in the Capsule frame, and then according to the size of the information freshness-aware scheduling operator value of the status update data packet contained in all Capsule frames in the to-be-forwarded queue, the compressed Capsule frame is inserted into the corresponding position in the to-be-forwarded queue using a binary insertion algorithm.

2. The method of claim 1, wherein, The UPF network element and the edge proxy server maintain a dynamic compression table at both ends respectively, and the dynamic compression table is used to save the hash mapping relationship between the Flow ID field of each Capsule frame and the IP packet header five tuple of the state update data packet contained therein, in step one, the UPF network element loads each received state update data packet into a Capsule frame, further comprising: Step 11, the UPF network element receives each state update data packet, reads the IP packet header five tuple of the state update data packet, and judges whether the read IP packet header five tuple exists in the dynamic compression table of itself, if not, it indicates that the state update flow to which the state update data packet belongs is not registered, and step 12 is continued; If yes, it indicates that the state update flow to which the state update data packet belongs has been registered, and step 13 is continued; Step 12, the UPF network element uses a hash function to assign a Flow ID for the read IP packet header five tuple, and then registers the hash mapping relationship between the read IP packet header five tuple and the Flow ID assigned to it in the dynamic compression table of itself and the edge proxy server respectively, and then continues step 13; Step 13, the UPF network element extracts state update data from the state update data packet and writes it into the frame payload of a Capsule frame, and extracts the Flow ID corresponding to the IP packet header five tuple of the state update data packet from the dynamic compression table of itself, and then fills the extracted Flow ID into the Flow ID field of the frame header of the Capsule frame.

3. The method of claim 2, wherein, The UPF network element and the edge proxy server further establish an encoding stream and a decoding stream between them, and the encoding stream and the decoding stream are used to synchronize the contents of the dynamic compression tables at both ends, and step 12 further comprises: The UPF network element sends a set of structure bodies containing the hash mapping relationship of the IP packet header quintuple and the Flow ID allocated thereto to the edge proxy server through the encoding stream, the edge proxy server registers the hash mapping relationship of the IP packet header quintuple and the Flow ID in the dynamic compression table of itself, and then returns the ACK message through the decoding stream to indicate that it has completed the registration of the state update stream, when the UPF network element receives the ACK information sent by the decoding stream, it also registers the corresponding hash mapping relationship of the IP packet header quintuple and the Flow ID in the dynamic compression table of itself.

4. The method of claim 1, wherein, In step one, the UPF network element takes out a plurality of Capsule frames from the to-be-forwarded queue in the queuing order to constitute a QUIC data packet, and forwards the encapsulated QUIC data packet to the edge proxy server, further comprising: Step B1, the UPF network element takes out the first Capsule frame from the to-be-forwarded queue in the queuing order and puts it into the QUIC data packet; Step B2, the UPF network element judges whether the remaining load length of the QUIC data packet is greater than the length of the next Capsule frame in the to-be-forwarded queue, if yes, continue to take out the next Capsule frame from the to-be-forwarded queue and put it into the QUIC data packet, and then go to step B2; if not, encapsulate the QUIC data packet and forward it to the edge proxy server.

5. The method of claim 1, wherein, Step two further comprises: The edge proxy server divides the QUIC data packet into a plurality of Capsule frames according to the length field in the frame header of each Capsule frame in the received QUIC data packet, reads the Flow ID from the frame header of each Capsule frame obtained after division, queries the dynamic compression table to obtain the IP packet header quintuple corresponding to the Flow ID, reads the state update data from the load of each Capsule frame, and finally restores the original state update data packet based on the IP packet header quintuple and the state update data, and forwards it to the corresponding Internet of Things application server.

6. A system for transmitting status update data packets in the Internet of Things, characterized in that: The system is used to execute the transmission method of the state update data packet in the Internet of Things as claimed in claim 1, and the system comprises a UPF network element, an edge proxy server, a plurality of Internet of Things devices and a plurality of Internet of Things application servers, wherein: The Internet of Things device is connected to the base station through the 5G wireless network, and sends the state update data packet to the Internet of Things application server; The UPF network element receives the state update data packet sent by the Internet of Things device, loads each state update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the to-be-forwarded queue for queuing, and takes out a plurality of Capsule frames from the to-be-forwarded queue in the queuing order to constitute a QUIC data packet, and then encapsulates the QUIC data packet and forwards it to the edge proxy server; An edge proxy server splits all Capsule frames from each received QUIC data packet, then decompresses and restores each Capsule frame into a state update data packet, and forwards the state update data packet to a corresponding IoT application server; An IoT application server receives a state update data packet sent by an IoT device to update the state of the IoT device accordingly.

7. A computing device, comprising: Comprise: a memory and a processor; the memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions, and the computer executable instructions, when executed by the processor, implement the steps of the state update data packet transmission method in the IoT network according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer executable instructions, when executed by the processor, implement the steps of the state update data packet transmission method in the IoT network according to any one of claims 1-5.

Images