Method and system for transmitting state updating data packet in Internet of Things

The QUIC-based data packet aggregation and compression method addresses the challenges of status update delays in massive IoT scenarios by enhancing network efficiency and ensuring timely delivery of status updates.

CN119071320AActive Publication Date: 2024-12-03BEIJING UNIV OF POSTS & TELECOMM
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411094264.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-09
Publication Date
2024-12-03
Estimated Expiration
2044-08-09

AI Technical Summary

Technical Problem

Existing network scheduling and management technologies struggle to meet the heterogeneous requirements of status update tasks in massive IoT scenarios, leading to delays and termination of IoT applications due to traffic fluctuations and random data generation.

Method used

A method and system utilizing the QUIC protocol to aggregate and compress status update data packets through a UPF network element and edge proxy server, implementing lossless compression and scheduling based on information freshness to ensure timely delivery.

Benefits of technology

The solution accelerates status update data transmission, reduces network load, and maintains stable, low-latency network services by aggregating and compressing data packets, ensuring efficient delivery and meeting IoT application demands.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071320A_ABST
    Figure CN119071320A_ABST
Patent Text Reader

Abstract

A method and system for transmitting a state update data packet in the Internet of Things, each Internet of Things device is connected to a base station through a 5G wireless network, and sends the state update data packet to an Internet of Things application server, and the method comprises the following steps: a UPF network element loads each received state update data packet into a Capsu frame and compresses the Capsu frame, then, the compressed Capsu frames are put into a queue to be forwarded for queuing, meanwhile, a plurality of Capsu frames are taken out from the queue to be forwarded according to a queuing sequence to form a QUIC data packet, and the QUIC data packet is packaged and then forwarded to an edge proxy server; and the edge proxy server divides all Capsu frames from each received QUIC data packet, decompresses each Capsu frame, restores the Capsu frame into a state updating data packet, and forwards the state updating data packet to the corresponding Internet of Things application server. The invention relates to the technical field of computers, and can efficiently transmit state updating data packets in massive Internet of Things scenes, thereby ensuring network service requirements of state updating tasks in massive Internet of Things scenes.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a method and system for transmitting a status update data packet in an Internet of Things, and relates to the technical field of computers. Background Art

[0002] Massive IoT communications can support large-scale access to IoT devices and reliable communication network connections without human intervention. It is committed to providing low-power and low-complexity IoT communication devices with wide coverage and network services that support massive connection needs. This has great market potential and will create a new business model. With the development of 5G and future 5G and above networks, IoT type communications have received more and more attention. It is estimated that by 2023, 3.9 billion machine-type communication devices will be connected to the network, and will play a significant role in many fields such as industrial automation, smart healthcare, environmental monitoring, smart cities, and smart homes.

[0003] In the massive IoT scenario, in order to complete the remote control task, the IoT device needs to periodically send data packets containing status update data to update the device status information in the server. Data packets in the massive IoT have three characteristics: First, data packets have the characteristics of short packet communication, and the data size of the status update information is often only a few hundred bits, which makes the load utilization of the data packet very low. Second, the generation method of the status update data is random, because IoT devices are usually driven by changes in the external environment to generate status update data, which makes the generation time interval of the data packet very random, resulting in random distribution of the status update traffic. Third, the flow direction of the status update traffic is centralized, because IoT applications are usually deployed on edge clouds or central clouds, so the status update traffic of massive IoT devices usually flows to the data center.

[0004] The requirements report of the 3rd Generation Partnership Project points out that the transmission task of status update data packets in massive IoT scenarios has strict delay and information freshness requirements. However, with the increase of IoT devices connected to the network, the computing and communication burden of network access points is huge, and the randomness of status update traffic leads to traffic fluctuations on backbone network routers, causing status update data storms, causing a surge in delays in IoT applications, and ultimately leading to the termination of status updates, making IoT applications unable to work properly. Therefore, existing network scheduling and management technologies are difficult to meet the heterogeneous requirements of status update tasks for network conditions in massive IoT scenarios.

[0005] Therefore, how to efficiently transmit status update data packets in massive IoT scenarios, thereby ensuring the network service requirements of status update tasks in massive IoT scenarios, has become a technical issue that technical personnel have focused on. Summary of the invention

[0006] In view of this, the purpose of the present invention is to provide a method and system for transmitting status update data packets in the Internet of Things, which can efficiently transmit status update data packets in massive Internet of Things scenarios, thereby ensuring the network service requirements of status update tasks in massive Internet of Things scenarios.

[0007] In order to achieve the above object, the present invention provides a method for transmitting a status update data packet in an Internet of Things, wherein each Internet of Things device is connected to a base station via a 5G wireless network and sends a status update data packet to an Internet of Things application server, including:

[0008] Step 1: The UPF network element loads each received status update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the queue to be forwarded for queuing, and at the same time, takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and encapsulates the QUIC data packet and forwards it to the edge proxy server;

[0009] Step 2: The edge proxy server splits all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame and restores it into a state update data packet, and forwards it to the corresponding IoT application server.

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

[0011] IoT devices connect to the base station via the 5G wireless network and send status update packets to the IoT application server;

[0012] The UPF network element receives the status update data packets sent by the IoT device, loads each status update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the queue to be forwarded for queuing, and at the same time, takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and then encapsulates the QUIC data packet and forwards it to the edge proxy server;

[0013] The edge proxy server splits all capsule frames from each received QUIC data packet, then decompresses each capsule frame and restores it into a state update data packet, and forwards it to the corresponding IoT application server;

[0014] The IoT application server receives status update data packets sent by IoT devices to update the status of IoT devices accordingly.

[0015] In order to achieve the above object, the present invention further provides a computing device, comprising:

[0016] Memory and processor;

[0017] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for transmitting status update data packets in the Internet of Things are implemented.

[0018] In order to achieve the above-mentioned object, the present invention also provides a computer-readable storage medium, which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the method for transmitting status update data packets in the Internet of Things are implemented.

[0019] Compared with the prior art, the beneficial effects of the present invention are as follows: the present invention is based on the QUIC (Quick UDP Internet Connection) protocol, and is deployed on the container in the user plane network element UPF (User Plane Function) of the core network, and on the proxy node container on the edge side of the operator's backbone network. An upper-layer tunnel is established between the container nodes at both ends to schedule and manage the status update traffic. As a network middleware, the present invention can be started or shut down at any time according to the needs of the operator, and supports elastic expansion and containerized deployment, and can also customize traffic policies according to needs; the present invention uses lossless aggregation and compression mechanisms to process status update data packets, reducing the number of data packets and bytes passing through the operator's network. Based on the customized modification of the QUIC protocol, the present invention can achieve lossless aggregation and precise segmentation of short data packets of different sizes, and by maintaining dynamic compression tables at both ends of the tunnel, The state update data packets can be automatically compressed and restored, and the aggregation and compression mechanism accelerates the transmission of the state update data packets, and users and upper-layer applications are unaware of the entire process; the present invention also designs a low-complexity algorithm for scheduling 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 algorithms and flow completion time-based scheduling algorithms are difficult to perceive the importance of traffic. Information freshness is an indicator for measuring the state update process. Through the scheduling algorithm based on information freshness, the present invention achieves an improvement in the performance of the entire state update system and meets the update status requirements of Internet of Things applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 The present invention is a flowchart of a method for transmitting a status update data packet in an Internet of Things, shown in an exemplary embodiment of the present invention.

[0021] Figure 2An exemplary embodiment of the present invention is shown Figure 1 In step 1, the UPF network element loads each received status update data packet into a Capsule frame and compresses it.

[0022] Figure 3 It is a structural schematic diagram of a transmission system of a status update data packet in an Internet of Things shown in an exemplary embodiment of the present invention.

[0023] Figure 4 It is a schematic diagram of the structure of a computer device according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0024] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below with reference to the accompanying drawings.

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

[0026] Step 1: The UPF network element loads each received status update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the queue to be forwarded for queuing, and at the same time, takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and encapsulates the QUIC data packet and forwards it to the edge proxy server;

[0027] Step 2: The edge proxy server splits all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame and restores it into a state update data packet, and forwards it to the corresponding IoT application server.

[0028] The present invention constructs an upper layer forwarding tunnel based on the QUIC protocol, and the two sides of the tunnel are respectively deployed on the UPF network element side in the 5G core network and in the edge proxy server of the operator backbone network. A large number of IoT devices are connected to the base station through the 5G wireless network, and send status update data packets with the destination address pointing to the IoT application deployed in the cloud. According to the structure of the 5G core network, all status update traffic needs to pass through the UPF network element. Therefore, the present invention is designed in the network card queue on the egress side of the UPF network element, and the status update traffic is captured based on the kernel traffic filtering technology, and each status update data packet is sent to the container at the entrance of the tunnel. The tunnel exit is deployed in the edge proxy server on the data center side, which is responsible for restoring the data packets in each tunnel to the original status update data packets sent by the IoT device, and further forwarding them. The whole process is transparent to IoT applications and users, realizes lossless acceleration of status update traffic, overcomes the delay increase caused by the status update data storm, and guarantees the demand of massive IoT devices for stable and low-latency network service quality.

[0029] It needs to be explained that a network connection will be established between the IoT device and the IoT application deployed in the cloud. The IoT device continuously sends its own status update data to the IoT application in the form of status update data packets in the network connection. The network connection is defined as a status update flow. Taking the "temperature sensor" as an example, the IoT device will send the collected temperature data to the IoT application, usually in two forms: periodic transmission (for example, every 1s), or event-driven (for example, the temperature changes drastically from 20 degrees to 30 degrees). After receiving a new status update data packet, the IoT application will use the new status update data to overwrite the old status update data, thereby realizing the status update. The present invention is mainly aimed at IoT devices that access the Internet through 5G, and all data packets transmitted through 5G must 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 traffic must pass through.

[0030] The QUIC protocol used by the present invention to construct the upper-layer forwarding tunnel is a connection-oriented transmission protocol. When establishing a connection, QUIC simultaneously performs version negotiation and encrypted transmission handshake, which makes the initial establishment of the QUIC connection only take 1-RTT, and only requires a 0-RTT handshake when re-establishing the connection. The data transmission of the QUIC connection is carried out by exchanging data packets, and the QUIC data packets are transmitted in UDP datagrams. The QUIC protocol uses data packets with short headers to transmit data. Each data packet consists of a small amount of unencrypted header information and an encrypted payload. The header information contains the connection ID, data packet number, and other content. The payload of a QUIC packet is usually composed of a frame sequence. The payload of each QUIC packet contains at least one frame and may contain data frames from different data streams.

[0031] The QUIC protocol is built at the application layer, which allows it to be deployed as part of the application, allowing it to be personalized for various applications and ensuring that it can be iterated when the application is updated. The QUIC protocol runs based on the UDP protocol, which ensures that QUIC data packets can safely pass through firewalls and middleware. At the same time, QUIC data packets are forced to be authenticated and encrypted, which can effectively prevent the middleware from stealing and modifying data information. Therefore, the present invention is based on the QUIC protocol and its data packet extension implementation, does not require kernel modification, and is easy to deploy. In addition, the tunnel between the UPF network element side and the edge proxy server is also an encrypted QUIC connection, which can fully ensure the security of data transmission.

[0032] When the status update data packets sent by IoT devices arrive at network intermediate devices such as routers or switches, they will enter the cached forwarding queue for queuing. Since the flow of status update traffic is relatively concentrated, a single network intermediate device may receive traffic from a large number of heterogeneous IoT devices at the same time, and different IoT devices produce status update data at different frequencies. Therefore, the length of the queue to be forwarded of the network intermediate device fluctuates violently. When a group of status update data arrives suddenly in a short period of time, the queue length will increase sharply. Since the network intermediate device cannot process a large number of data packets in a short period of time, the queuing delay of the status update data packet will increase sharply, making it impossible for the status update data to reach the server in time, and the status update task cannot meet the demand. In order to solve this problem, the present invention 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 placed in 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 composed of state update data packets queued in the queue to be forwarded, thereby completing the aggregation; then the QUIC network connection between the UPF side tunnel entrance and the edge proxy server tunnel exit is used to send the aggregated data packet to the edge proxy server; finally, when the aggregated QUIC data packet arrives at the edge proxy server, each aggregated data packet will be accurately segmented according to the indication of the Capsule frame header, and the segmented data packet will be handed over to the corresponding state update task according to the indication of the data packet header. By aggregating data packets, the present invention can reduce the number of data packets to be sent in the network intermediate device and alleviate the calculation and communication pressure of the queue to be forwarded. In addition, the present invention provides a data packet compression function. By compressing the size of the data packet, the number of bytes at the network card exit can be reduced, thereby breaking the forwarding performance bottleneck of the network intermediate device and accelerating the transmission of data packets.

[0033] As an optional implementation, the present invention can further use compression function for the status update flow in the tunnel to reduce the network load, that is, the UPF network element and the edge proxy server respectively maintain a dynamic compression table, which is used to store the hash mapping relationship between the Flow ID field of each Capsule frame and the IP header quintuple of the included status update data packet. Figure 2 As shown, Figure 1 In step 1, the UPF network element loads each received status update data packet into a Capsule frame, which may further include:

[0034] Step 11, the UPF network element receives each status update data packet, reads the IP header quintuple of the status update data packet, and determines whether the read IP header quintuple exists in its own dynamic compression table. If not, it means that the status update flow to which the status update data packet belongs is not registered, and proceed to step 12; if yes, it means that the status update flow to which the status update data packet belongs is registered, and proceed to step 13;

[0035] Step 12: The UPF network element uses a hash function to assign a Flow ID to the read IP header quintuple, and then registers the hash mapping relationship between the read IP header quintuple and the assigned Flow ID to their respective dynamic compression tables with the edge proxy server, and then proceeds to step 13;

[0036] Step 13: The UPF network element extracts the status update data from the status update data packet, writes it into the frame payload of a Capsule frame, extracts the FlowID corresponding to the IP header quintuple of the status update data packet from its own dynamic compression table, and then fills the extracted Flow ID into the Flow ID field of the frame header of the Capsule frame.

[0037] At this point, the UPF network element has completed the encapsulation of the Capsule frame. It should be noted that in addition to the Flow ID field and the field identifying the frame length, the frame header of the Capsule frame also contains the necessary information of the original IP data packet (taking TCP as an example, it also includes the sequence number, ACK number, and sliding window, etc.), and the frame payload contains the encrypted original status update data.

[0038] As an optional implementation, a coding stream and a decoding stream are further established between the UPF network element and the edge proxy server, and the coding stream and the decoding stream are used to synchronize the contents of the dynamic compression table at both ends. Step 12 may further include:

[0039] The UPF network element sends a set of structures containing the hash mapping relationship between the IP header quintuple and the Flow ID assigned to it to the edge proxy server through the encoded flow. The edge proxy server registers the hash mapping relationship between the IP header quintuple and the Flow ID in its own dynamic compression table, and then returns an ACK message through the decoded flow to indicate that it has completed the registration of the status update flow. When the UPF network element receives the ACK information sent by the decoded flow, it also registers the corresponding hash mapping relationship between the IP header quintuple and the Flow ID in its own dynamic compression table.

[0040] Massive IoT devices send status update packets to IoT applications deployed in the cloud to achieve accurate judgment and implementation of decisions. In the status update process, information freshness is an indicator used to measure status updates, and the information age is usually calculated to judge the information freshness. The older the information age, the lower the information freshness, which means the worse the status update process. The younger the information age, the higher the information freshness, which means the better the status update process. Information age is defined as the time when the status update packet arrives at the destination minus the time when the status update 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 divided by the length of the time window after calculus. In order to measure the information age of the entire system, the present invention regards each status update stream as a status update process, adds the average information age of all IoT devices, and divides it by the total number of devices to obtain the average information age of the system.

[0041] There are two main types of existing traffic scheduling algorithms. The first is to schedule based on data packet priority, such as distinguishing the priority of data packets based on the DSCP of the IP packet header. However, according to the applicant's statistics on existing traffic, the status update data packets sent by massive IoT devices are all marked as "default application data", so the importance of massive status 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. However, the importance of the status update flow has no direct relationship with the duration of the flow, but is related to the urgency of the IoT application's demand for status updates. Therefore, unlike existing traffic scheduling algorithms, the present invention designs a traffic scheduling algorithm for massive IoT scenarios with minimizing information freshness as an indicator.

[0042] According to data analysis, if minimizing the average system age is used as the goal of the scheduling algorithm, due to the existence of calculus, the scheduling algorithm will prefer to give priority to sending the status update stream of IoT devices with a larger generation cycle. However, the generation cycle has no direct relationship with the urgency of the IoT application's demand for status updates. Therefore, minimizing the average system age as a scheduling goal will undermine the fairness of the network scheduling algorithm. Therefore, the present invention also proposes a new indicator for measuring the impact of the network on the system status update, that is, the normalized average system age. By normalizing the average age with the age of the traffic generation process, the normalized average system age can be obtained. The smaller the normalized average system age, the better the network's performance impact on the entire status update system, which means that the current network management algorithm is more conducive to status updates.

[0043] In summary, as an optional implementation, the present invention takes minimizing the normalized average system age as the scheduling goal and designs a new traffic scheduling algorithm so that the network intermediate device can perceive the need for IoT application update status and perform scheduling based on this. Figure 1 In step 1, the UPF network element puts the compressed Capsule frame into a queue to be forwarded, which may further include:

[0044] Step A1: The UPF network element calculates the expected age of the state update flow to which the state update data packet contained in the Capsule frame belongs based on the five-tuple of the IP header of the state update data packet: in, is the expected calculation period of age, that is, The duration is a time period starting from the generation time of the status update data packet contained in the Capsule frame. It can be set according to actual business needs. The status update flow to which the status update data packet contained in the Capsule frame belongs is Age expectation during the period, t i ,t i-1 The status update flow to which the status update data packet contained in the Capsule frame belongs is The i-th and i-1-th state update packets pkt during the period i 、pkt i-1 The generation time of the state update packet contained in the Capsule frame is n, and the state update flow to which the state update packet belongs is n. The total number of all status update packets during the period;

[0045] Step A2: The UPF network element calculates the scheduling operator for information freshness awareness of the status update data packet contained in the Capsule frame: Among them, O perator is the scheduling operator aware of the information freshness of the status update data packets contained in the Capsule frame, M is the generation time interval of the status update data packets contained in the Capsule frame, t and t′ are respectively the generation time of the status update data packet contained in the Capsule frame and the previous status update data packet of the status update flow to which the status update data packet belongs, size is the length of the status update data packet contained in the Capsule frame, and then according to the size of the scheduling operator aware of the information freshness of the status update data packets contained in all Capsule frames in the queue to be forwarded, the compressed Capsule frame is inserted into the corresponding position in the queue to be forwarded using the binary insertion algorithm.

[0046] The larger the Operator is, the greater the impact of the status update data packet on the status update, and the more urgent the status update demand of its IoT application is. Therefore, the larger the Operator of the status update data packet is, the higher its queue order in the queue to be forwarded is, so it can be sent first.

[0047] As a further optional implementation, Figure 1 In step 1, the UPF network element takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and encapsulates the QUIC data packet and forwards it to the edge proxy server, which may further include:

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

[0049] Step B2, the UPF network element determines whether the remaining load length of the QUIC data packet is greater than the length of the next Capsule frame in the queue to be forwarded. If so, it continues to take out the next Capsule frame from the queue to be forwarded and put it into the QUIC data packet, and then goes to step B2; 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 queue to be forwarded from front to back in the queue order and puts them into the QUIC data packet for packaging. According to the payload length of the QUIC data packet (usually the maximum segment length MSS, i.e., Maximum Segment Size), each QUIC data packet can aggregate multiple Capsule frames carrying 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 payload length of the QUIC data packet is not enough to put in the next Capsule frame, the UPF network element will complete the encapsulation of the QUIC data packet, forward the QUIC data packet to the edge proxy server, and then start the encapsulation process of the next QUIC data packet. For example, the maximum payload length of the QUIC data packet is usually set to 1370 bytes. If the length of each compressed Capsule frame carrying the state update data packet is 100 bytes, then one QUIC can be filled with 13 Capsule frames.

[0051] As an optional implementation, when the QUIC data packet arrives at the edge proxy server, step 2 may 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 Capsule frame after division, queries its own dynamic compression table to obtain the IP header quintuple corresponding to the Flow ID, and reads the status update data from the payload of each Capsule frame. Finally, based on the IP header quintuple and the status update data, it restores the original status update data packet and forwards it to the corresponding IoT 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 data packet header is replaced by the Flow ID field in the Capsule frame. When the Capsule frame arrives at the tunnel exit and is parsed, the Flow ID field is restored to a five-tuple, thereby reconstructing the original state update data packet. Since the state update data packet is mainly composed of short packets, the length of the header in the short packet causes the effective load utilization of the bandwidth to be low. The present invention can greatly reduce the number of bytes of the state update traffic by compressing the header information, thereby reducing the forwarding pressure of the operator's network intermediate equipment.

[0054] like Figure 3As shown, the present invention provides a transmission system for status update data packets in the Internet of Things, including a UPF network element, an edge proxy server, multiple Internet of Things devices and multiple Internet of Things application servers, wherein:

[0055] IoT devices connect to the base station via the 5G wireless network and send status update packets to the IoT 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. It receives status update packets sent by IoT devices, loads each status update packet into a Capsule frame and compresses it, and then puts the compressed Capsule frame into the queue to be forwarded for queuing. At the same time, it takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC packet, and then encapsulates the QUIC packet and forwards it to the edge proxy server;

[0057] The edge proxy server is an edge service node deployed in different regions. It is responsible for communicating with users in its geographical vicinity. It splits all capsule frames from each received QUIC data packet, decompresses each capsule frame, restores it to a state update data packet, and forwards it to the corresponding IoT application server.

[0058] The IoT application server is usually an elastic resource server deployed on the cloud or in self-built data, and runs IoT applications. It receives status update data packets sent by IoT devices to update the status of IoT devices accordingly, so that decisions can be made based on the latest status information of IoT devices.

[0059] See also Figure 4 , Figure 4 4 is a block diagram of a computing device 400 shown in an exemplary embodiment of this 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 via a bus 430, and the database 450 is used to store 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 a combination of communication networks such as the Internet. The access device 440 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of 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 the like.

[0061] In one embodiment of the present specification, the above components of the computing device 400 and Figure 4 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 4 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0062] The computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a PC. The computing device 400 may also be a mobile or stationary server or a cloud server, etc.

[0063] The processor 420 is used to execute the following computer executable instructions, which, when executed by the processor, implement the steps of the above-mentioned method for transmitting a status update data packet in the Internet of Things.

[0064] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the method for transmitting a status update data packet in the Internet of Things are of the same concept, and the details not described in detail in the technical scheme of the computing device can be found in the description of the technical scheme of the method for transmitting a status update data packet in the Internet of Things.

[0065] An embodiment of the present specification also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the above-mentioned method for transmitting a status update data packet in the Internet of Things.

[0066] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the above-mentioned method for transmitting a status update data packet in the Internet of Things belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the method or system for transmitting a status update data packet in the Internet of Things.

[0067] An embodiment of the present specification also provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned method for transmitting a status update data packet in the Internet of Things.

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

[0069] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0070] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0071] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0072] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for transmitting a status update data packet in an Internet of Things, characterized in that: Each IoT device connects to the base station via the 5G wireless network and sends a status update packet to the IoT application server, including: Step 1: The UPF network element loads each received status update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the queue to be forwarded for queuing, and at the same time, takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and encapsulates the QUIC data packet and forwards it to the edge proxy server; Step 2: The edge proxy server splits all Capsule frames from each received QUIC data packet, then decompresses each Capsule frame and restores it into a state update data packet, and forwards it to the corresponding IoT application server.

2. The method according to claim 1, characterized in that The UPF network element and the edge proxy server each maintain a dynamic compression table, which is used to store the hash mapping relationship between the Flow ID field of each Capsule frame and the five-tuple IP header of the state update data packet contained therein. In step 1, the UPF network element loads each received state update data packet into a Capsule frame, which further includes: Step 11, the UPF network element receives each status update data packet, reads the IP header quintuple of the status update data packet, and determines whether there is a read IP header quintuple in its own dynamic compression table. If not, it means that the status update flow to which the status update data packet belongs is not registered, and proceeds to step 12; If yes, it means that the status update flow to which the status update data packet belongs has been registered, and proceed to step 13; Step 12, the UPF network element uses a hash function to assign a Flow ID to the read IP header quintuple, and then registers the hash mapping relationship between the read IP header quintuple and the assigned FlowID to their respective dynamic compression tables with the edge proxy server, and then proceeds to step 13; Step 13: The UPF network element extracts the status update data from the status update data packet, writes it into the frame payload of a Capsule frame, extracts the Flow ID corresponding to the IP header quintuple of the status update data packet from its own dynamic compression table, and then fills the extracted Flow ID into the Flow ID field of the frame header of the Capsule frame.

3. The method according to claim 2, characterized in that A coding stream and a decoding stream are also established between the UPF network element and the edge proxy server, and the coding stream and the decoding stream are used to synchronize the contents of the dynamic compression tables at both ends. Step 12 further includes: The UPF network element sends a set of structures containing the hash mapping relationship between the IP header quintuple and the Flow ID assigned to it to the edge proxy server through the encoded flow. The edge proxy server registers the hash mapping relationship between the IP header quintuple and the FlowID in its own dynamic compression table, and then returns an ACK message through the decoded flow to indicate that it has completed the registration of the status update flow. When the UPF network element receives the ACK information sent by the decoded flow, it also registers the corresponding hash mapping relationship between the IP header quintuple and the Flow ID in its own dynamic compression table.

4. The method according to claim 1, characterized in that: In step 1, the UPF network element puts the compressed Capsule frame into the queue to be forwarded, which further includes: Step A1: The UPF network element calculates the expected age of the state update flow to which the state update data packet contained in the Capsule frame belongs based on the five-tuple of the IP header of the state update data packet: in, is the expected calculation period of age, that is, The duration is a time period starting from the generation time of the status update data packet contained in the Capsule frame. The status update flow to which the status update data packet contained in the Capsule frame belongs is Age expectation during the period, t i ,t i-1 The status update flow to which the status update data packet contained in the Capsule frame belongs is The i-th and i-1-th state update packets pkt during the period i 、pkt i-1 The generation time of the state update packet contained in the Capsule frame is n, and the state update flow to which the state update packet belongs is n. The total number of all status update packets during the period; Step A2: The UPF network element calculates the scheduling operator for information freshness awareness of the status update data packet contained in the Capsule frame: M=tt′, where Operator is the scheduling operator aware of the information freshness of the status update data packets contained in the Capsule frame, M is the generation time interval of the status update data packets contained in the Capsule frame, t and t′ are respectively the generation time of the status update data packet contained in the Capsule frame and the previous status update data packet of the status update flow to which the status update data packet belongs, and size is the length of the status update data packet contained in the Capsule frame. Then, according to the size of the scheduling operator value aware of the information freshness of the status update data packets contained in all Capsule frames in the queue to be forwarded, the compressed Capsule frame is inserted into the corresponding position in the queue to be forwarded using the binary insertion algorithm.

5. The method according to claim 1, characterized in that In step 1, the UPF network element takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and encapsulates the QUIC data packet and forwards it to the edge proxy server, further including: Step B1: The UPF network element takes out the first Capsule frame from the queue to be forwarded according to the queuing order and puts it into the QUIC data packet; Step B2, the UPF network element determines whether the remaining load length of the QUIC data packet is greater than the length of the next Capsule frame in the queue to be forwarded. If so, it continues to take out the next Capsule frame from the queue to be forwarded and put it into the QUIC data packet, and then goes to step B2; if not, the QUIC data packet is encapsulated and forwarded to the edge proxy server.

6. The method according to claim 1, characterized in that Step 2 further includes: 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 FlowID from the frame header of each Capsule frame after division, queries its own dynamic compression table to obtain the IP header quintuple corresponding to the FlowID, and reads the status update data from the payload of each Capsule frame. Finally, based on the IP header quintuple and the status update data, the original status update data packet is restored and forwarded to the corresponding IoT application server.

7. A transmission system for status update data packets in the Internet of Things, characterized in that: It includes UPF network elements, edge proxy servers, multiple IoT devices and multiple IoT application servers, including: IoT devices connect to the base station via the 5G wireless network and send status update packets to the IoT application server; The UPF network element receives the status update data packets sent by the IoT device, loads each status update data packet into a Capsule frame and compresses it, then puts the compressed Capsule frame into the queue to be forwarded for queuing, and at the same time, takes out multiple Capsule frames from the queue to be forwarded in the queuing order to form a QUIC data packet, and then encapsulates the QUIC data packet and forwards it to the edge proxy server; The edge proxy server splits all capsule frames from each received QUIC data packet, then decompresses each capsule frame and restores it into a state update data packet, and forwards it to the corresponding IoT application server; The IoT application server receives status update data packets sent by IoT devices to update the status of IoT devices accordingly.

8. A computing device, characterized in that include: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for transmitting status update data packets in the Internet of Things described in any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium, characterized in that: It stores computer executable instructions, which, when executed by a processor, implement the steps of the method for transmitting status update data packets in the Internet of Things as described in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Estimating quality metric for latency sensitive traffic flows in communication networks

    CN114009089A

  • Chargeable wireless sensor network node work scheduling method based on information freshness

    CN115802518A

  • Data transmission controller and method for generating data transmission messages according to modified QUIC protocol

    CN116888948A

  • Communication method and communication device

    CN117014951A

  • Data transmission method and system of Internet of Things equipment

    CN117676697A