Method and apparatus for allocating communication resources, storage medium and electronic device
By dynamically adjusting resource quotas at the IoT gateway based on preset resource configuration information and device feedback, the problem of unreasonable allocation of communication resources in IoT devices is solved, enabling timely transmission of emergency communications and rational utilization of resources.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- ZHEJIANG DAHUA TECH CO LTD
- Filing Date
- 2026-03-06
- Publication Date
- 2026-07-03
AI Technical Summary
In IoT device communication scenarios, when multiple business data are mixed and communicated, the unreasonable allocation of communication resources leads to the inability to transmit emergency communication data in a timely manner, and existing technologies have failed to effectively solve this problem.
By determining the initial resource quota at the IoT gateway based on preset resource configuration information, and combining the priority adjustment information and resource usage information of IoT devices, the target resource quota for different business sessions can be dynamically adjusted to achieve reasonable allocation.
It solves the problem of unreasonable allocation of communication resources in IoT terminal networks, ensures timely transmission of emergency communication data, and improves the utilization efficiency and stability of communication resources.
Smart Images

Figure CN121792467B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of Internet of Things (IoT) communication technology, and more specifically, to a method and apparatus for allocating communication resources, a storage medium, and an electronic device. Background Technology
[0002] In IoT device communication scenarios, the end-point network consists of IoT devices and IoT gateways. Data communication from IoT devices requires partial processing through the gateway before transmission within the network. When multiple business data are mixed in communication, the data is treated equally during transmission and processing. Therefore, when network resources such as bandwidth, software, and hardware are strained, communication resources cannot be allocated rationally according to business needs, leading to a general impact on the transmission rate of all business data. If an IoT device experiences an emergency requiring urgent communication, this inefficient resource allocation further prevents or delays the transmission of emergency communication data.
[0003] Regarding the relevant technologies, the problem of unreasonable allocation of communication resources caused by the equal processing of all data by IoT terminal networks has not yet been effectively solved.
[0004] Therefore, it is necessary to improve the relevant technology to overcome the aforementioned defects. Summary of the Invention
[0005] This invention provides a method and apparatus for allocating communication resources, a storage medium, and an electronic device to at least solve the problem of unreasonable allocation of communication resources caused by the equal processing of all data in IoT terminal networks.
[0006] According to one aspect of the present invention, a method for allocating communication resources is provided, applied to an Internet of Things (IoT) gateway, comprising: determining initial resource quotas for different service sessions established between an IoT device and the IoT gateway based on preset resource configuration information, wherein the different service sessions correspond to different service types; after allocating communication resources according to the initial resource quotas, obtaining priority adjustment information fed back by the IoT device when the communication quality of the service sessions with the IoT gateway changes, and obtaining resource usage information monitored by the IoT gateway; adjusting the initial resource quotas according to the priority adjustment information and the resource usage information to obtain target resource quotas for the different service sessions.
[0007] In an exemplary embodiment, the resource configuration information includes reserved resource quotas, session base resource quotas configured for each service type, session resource quota limits, preset session numbers, and preset service priorities. Determining the initial resource quotas for different service sessions established between the IoT device and the IoT gateway based on the preset resource configuration information includes: determining the allocable resource quota in the communication resources, wherein the allocable resource quota is the difference between the total communication resource quota and the reserved resource quota, and the reserved communication resources corresponding to the reserved resource quota are only allocated to emergency service sessions; allocating base resources to the different service sessions according to the session base resource quota, wherein the number of service sessions for each service type does not exceed the preset session number; determining the remaining resource quota of the communication resources based on the difference between the allocable resource quota and the base resource quota already allocated to the different service sessions; and allocating the remaining communication resources to the different service sessions according to the preset service priorities.
[0008] In an exemplary embodiment, allocating communication resources of the remaining resource quota to different service sessions according to the preset service priority includes: determining a target priority corresponding to a target service type and a target weight corresponding to the target priority according to the preset service priority information; determining a first quota based on the product of a target ratio and the remaining resource quota, wherein the target ratio is the ratio of the target weight to the total weight; determining a service resource quota limit for the target service type based on the number of service sessions of the target service type and the session resource quota limit for the target service type; and allocating communication resources to service sessions of the target service type based on the service resource quota limit and the first quota.
[0009] In an exemplary embodiment, allocating communication resources for a service session of the target service type based on the service resource quota limit and the first quota includes: when it is determined that the first quota is less than the service resource quota limit, allocating the communication resources of the first quota to the service session of the target service type; when it is determined that the first quota is greater than the service resource quota limit, allocating the communication resources of the service resource quota limit to the service session of the target service type.
[0010] In an exemplary embodiment, when it is determined that the first quota is less than the upper limit of the service resource quota, allocating the communication resources of the first quota to the service session of the target service type includes: obtaining a session-aware tag from a data link layer frame sent by the IoT device through the service session of the target service type, wherein the session-aware tag includes a session identifier and session priority information; obtaining session priority information of the service session of the target service type according to the session-aware tag, wherein the session priority information includes a session priority and a session weight corresponding to the session priority; and allocating the communication resources of the first quota to the service session of the target service type according to the session weight of the service session of the target service type.
[0011] In an exemplary embodiment, adjusting the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions includes: obtaining a service-aware tag from a data link layer frame sent by the IoT device through a service session of a target service type; obtaining the priority adjustment information from the service-aware tag, wherein the priority adjustment information includes the target service type in the service-aware tag and the adjusted service priority of the target service type, wherein the IoT device increases the service priority of the target service type to obtain the adjusted service priority when the communication quality of the service session of the target service type is reduced; and reallocating the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
[0012] In an exemplary embodiment, adjusting the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions further includes: when it is determined that the utilization rate of communication resources for a service session of the target service type, as indicated by the resource usage information, is less than a preset utilization rate within a preset time period, reducing the service priority of the target service type to obtain an adjusted service priority; and reallocating the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
[0013] In an exemplary embodiment, adjusting the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions further includes: determining the communication resource usage quota of the service session of the target service type at multiple time nodes within a preset period according to the resource usage information; determining the predicted communication resource usage quota of the service session of the target service type at a target time node in the next preset period according to the communication resource usage quota at multiple time nodes within the preset period; and determining the target resource quota according to the predicted communication resource usage quota at the target time node in the next preset period.
[0014] According to another aspect of the present invention, a communication resource allocation apparatus is also provided, comprising: a determining module, configured to determine initial resource quotas for different service sessions established between an IoT device and an IoT gateway based on preset resource configuration information, wherein the different service sessions correspond to different service types; an acquiring module, configured to, after allocating communication resources according to the initial resource quotas, acquire priority adjustment information fed back by the IoT device when the communication quality of the service sessions with the IoT gateway changes, and acquire resource usage information monitored by the IoT gateway; and an adjusting module, configured to adjust the initial resource quotas according to the priority adjustment information and the resource usage information to obtain target resource quotas for the different service sessions.
[0015] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, wherein the computer program is configured to execute the above-described method for allocating communication resources when it is run.
[0016] According to another aspect of the present invention, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the communication resource allocation method through the computer program.
[0017] This invention determines the initial resource quotas for different service sessions established between IoT devices and IoT gateways based on preset resource configuration information, where different service sessions correspond to different service types. After allocating communication resources according to the initial resource quotas, it acquires priority adjustment information fed back by the IoT devices when the communication quality of the service sessions with the IoT gateway changes, as well as resource usage information monitored by the IoT gateway. The initial resource quotas are then adjusted based on the priority adjustment information and resource usage information to obtain the target resource quotas for different service sessions. By adopting the above technical solution, after the initial allocation of communication resources according to the preset resource configuration information, the allocation of communication resources is dynamically adjusted based on the feedback from the IoT devices and the resource usage information monitored by the gateway. This solves the problem in related technologies where the equal processing of all data by IoT terminal networks leads to unreasonable allocation of communication resources, thereby achieving the effect of reasonable allocation of IoT communication resources. Attached Figure Description
[0018] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with the description thereof, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:
[0019] Figure 1 This is a hardware structure block diagram of a computer terminal that executes the communication resource allocation method according to an embodiment of the present invention;
[0020] Figure 2 This is a flowchart of a communication resource allocation method according to an embodiment of the present invention;
[0021] Figure 3 This is a schematic diagram of the network structure of the Internet of Things according to an embodiment of the present invention;
[0022] Figure 4 This is a schematic diagram of a resource allocation strategy according to an embodiment of the present invention;
[0023] Figure 5 This is a schematic diagram of the data link layer frame processing flow according to an embodiment of the present invention;
[0024] Figure 6 This is a schematic diagram of the emergency service processing flow according to an embodiment of the present invention;
[0025] Figure 7 This is a schematic diagram of the resource scope according to an embodiment of the present invention;
[0026] Figure 8 This is a schematic diagram of the allocation process for a new service session according to an embodiment of the present invention;
[0027] Figure 9 This is a schematic diagram of the priority adjustment process according to an embodiment of the present invention;
[0028] Figure 10 This is a schematic diagram of the real-time resource utilization monitoring and adjustment process according to an embodiment of the present invention;
[0029] Figure 11 This is a schematic diagram of a predictive dynamic adjustment of resource allocation process according to an embodiment of the present invention;
[0030] Figure 12 This is a schematic diagram of the architecture of an Internet of Things (IoT) device according to an embodiment of the present invention;
[0031] Figure 13 This is a schematic diagram of the architecture of an IoT gateway according to an embodiment of the present invention;
[0032] Figure 14 This is a schematic diagram of the strategy engine execution flow according to an embodiment of the present invention;
[0033] Figure 15 This is a structural block diagram of a communication resource allocation device according to an embodiment of the present invention. Detailed Implementation
[0034] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0035] It should be noted that the terms and terms such as "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0036] The methods and embodiments provided in this invention can be executed on a computer terminal or similar computing device. Taking running on a computer terminal as an example, Figure 1 This is a hardware structure block diagram of a computer terminal that executes the communication resource allocation method according to embodiments of the present invention. For example... Figure 1As shown, a computer terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor unit (MPU) or a programmable logic device (PLD)) and a memory 104 configured to store data are also shown. In one exemplary embodiment, the computer terminal may further include a transmission device 106 configured for communication and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 1 The more or fewer components shown, or having the same Figure 1 Equivalent functions or ratios shown Figure 1 The functions shown have more different configurations.
[0037] The memory 104 may be configured to store computer programs, such as application software programs and modules, like the computer program corresponding to the communication resource allocation method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, thereby implementing the aforementioned method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0038] The transmission device 106 is configured to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer terminal. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module configured to communicate with the Internet wirelessly.
[0039] This embodiment provides a method for allocating communication resources. Figure 2 This is a flowchart of a communication resource allocation method according to an embodiment of the present invention, the process including the following steps:
[0040] Step S202: Determine the initial resource quota for different service sessions established between the IoT device and the IoT gateway based on preset resource configuration information, wherein the different service sessions correspond to different service types;
[0041] Optionally, for example, the different service types mentioned above include video transmission, sensor data reporting, command issuance, etc. Each service type can have multiple service sessions. The preset resource configuration information above configures static resource allocation rules for service sessions of different service types. Then, the initial resource quota of different service sessions is determined according to the resource allocation rules, and the initial communication resource allocation is performed according to the initial resource quota.
[0042] Step S204: After allocating communication resources according to the initial resource quota, obtain the priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and obtain the resource usage information monitored by the IoT gateway.
[0043] Optionally, when an IoT device senses a change in the latency or packet loss rate of a certain service session, it may proactively report a priority adjustment request. Adjusting the service priority affects the resource allocation for service sessions of that service type; a higher priority allocates more communication resources to that service type. The aforementioned resource usage information includes the actual communication resources used by different service sessions of different service types, including both real-time and long-term resource usage information.
[0044] Step S206: Adjust the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions.
[0045] Optionally, the target resource quota mentioned above is an adjusted allocation. The target resource quota for different service sessions will be dynamically adjusted according to changes in the communication quality and resource usage of IoT devices to ensure the reasonable allocation of communication resources.
[0046] Through the above steps, the initial resource quotas for different service sessions established between IoT devices and IoT gateways are determined based on preset resource configuration information. Different service sessions correspond to different service types. After allocating communication resources according to the initial resource quotas, priority adjustment information fed back by the IoT devices when the communication quality of their service sessions with the IoT gateway changes, as well as resource usage information monitored by the IoT gateway, are obtained. The initial resource quotas are adjusted based on the priority adjustment information and resource usage information to obtain the target resource quotas for different service sessions. Using this technical solution, after the initial allocation of communication resources based on preset resource configuration information, the allocation of communication resources is dynamically adjusted based on feedback from the IoT devices and resource usage information monitored by the gateway. This solves the problem in related technologies where the equal processing of all data in IoT terminal networks leads to unreasonable allocation of communication resources, thereby achieving the effect of rational allocation of IoT communication resources.
[0047] In an exemplary embodiment, the resource configuration information includes reserved resource quotas, session base resource quotas configured for each service type, session resource quota limits, preset session numbers, and preset service priorities. Determining the initial resource quotas for different service sessions established between the IoT device and the IoT gateway based on the preset resource configuration information includes: determining the allocable resource quota in the communication resources, wherein the allocable resource quota is the difference between the total communication resource quota and the reserved resource quota, and the reserved communication resources corresponding to the reserved resource quota are only allocated to emergency service sessions; allocating base resources to the different service sessions according to the session base resource quota, wherein the number of service sessions for each service type does not exceed the preset session number; determining the remaining resource quota of the communication resources based on the difference between the allocable resource quota and the base resource quota already allocated to the different service sessions; and allocating the remaining communication resources to the different service sessions according to the preset service priorities.
[0048] Optionally, in the above embodiments, the reserved resource quota in the resource configuration information is a dedicated resource quota reserved to cope with emergencies and is only used for data transmission of emergency services. A basic session resource quota, a maximum session resource quota, a preset number of sessions, and a preset service priority are configured for each service type. The basic session resource quota is the resource quota required to ensure the most basic operational needs of the service type's sessions; the maximum session resource quota represents the maximum resource quota that can be allocated to sessions of this service type; the preset number of sessions represents the maximum number of sessions allowed to be established for this service type; and the preset service priority represents the priority of resource allocation for this service. Initial allocation is based on the preset priority, and subsequent allocations will be dynamically adjusted based on communication quality and resource usage information.
[0049] Optionally, in the above embodiments, when initially allocating communication resources, the reserved resource quota is first removed, then the basic resource quota is allocated to all service sessions, and then the remaining resources are weighted and allocated to service sessions of different service types according to service priority.
[0050] In an exemplary embodiment, allocating communication resources of the remaining resource quota to different service sessions according to the preset service priority includes: determining a target priority corresponding to a target service type and a target weight corresponding to the target priority according to the preset service priority information; determining a first quota based on the product of a target ratio and the remaining resource quota, wherein the target ratio is the ratio of the target weight to the total weight; determining a service resource quota limit for the target service type based on the number of service sessions of the target service type and the session resource quota limit for the target service type; and allocating communication resources to service sessions of the target service type based on the service resource quota limit and the first quota.
[0051] In an exemplary embodiment, allocating communication resources for a service session of the target service type based on the service resource quota limit and the first quota includes: when it is determined that the first quota is less than the service resource quota limit, allocating the communication resources of the first quota to the service session of the target service type; when it is determined that the first quota is greater than the service resource quota limit, allocating the communication resources of the service resource quota limit to the service session of the target service type.
[0052] Optionally, in the above embodiments, the remaining communication resources are weighted and allocated to service sessions of different service types according to service priority. Taking a target service type as an example, such as a video service, the service priority of the service is first obtained from the resource configuration information, and then the target weight mapped to that priority is obtained. The weight can be predefined; for example, services with higher priorities have larger weight values. Subsequently, the proportion of the target weight in the total weight of all eligible service types is calculated to obtain the target ratio. The target ratio is multiplied by the remaining resource quota to obtain the first quota that should theoretically be allocated to the target service type. At the same time, to ensure that the allocation is controlled, it is necessary to calculate the upper limit of the service resource quota for the target service type, which is specifically determined by the product of the number of service sessions of the target service type and the upper limit of the session resource quota for the target service type.
[0053] If the first quota is less than or equal to the service resource quota limit for that service type, it indicates that the resource amount calculated according to priority weight is within its reasonable limit. In this case, the gateway can allocate all resources of the first quota to the service sessions of that target service type. Conversely, if the first quota is greater than the service resource quota limit, it means that the theoretical allocation calculated according to weight exceeds the service resource quota limit set for this type of service. In this case, the gateway will limit the allocation to within the service resource quota limit, and the excess will not be allocated. For example, a video service should receive 15Mbps of bandwidth (first quota) according to weight, but the service resource quota limit calculated by multiplying the current number of sessions by the single session limit is 12Mbps. In this case, the final allocation will be based on 12Mbps. This mechanism prevents high-priority services from monopolizing communication resources without restriction, ensuring the stability and fairness of communication resource allocation.
[0054] In an exemplary embodiment, when it is determined that the first quota is less than the upper limit of the service resource quota, allocating the communication resources of the first quota to the service session of the target service type includes: obtaining a session-aware tag from a data link layer frame sent by the IoT device through the service session of the target service type, wherein the session-aware tag includes a session identifier and session priority information; obtaining session priority information of the service session of the target service type according to the session-aware tag, wherein the session priority information includes a session priority and a session weight corresponding to the session priority; and allocating the communication resources of the first quota to the service session of the target service type according to the session weight of the service session of the target service type.
[0055] Optionally, in the above embodiments, after determining to allocate the first amount of communication resources to the service sessions of the target service type, it is also necessary to determine how to allocate them to each service session of that service type. Therefore, it is necessary to first determine the session priority and corresponding weight of each service session of that service type. This information needs to be obtained from the data link layer frames transmitted between the IoT device and the IoT gateway in the service session. Specifically, a session-aware tag can be added to the data link layer frame. The session-aware tag carries the session ID, session priority and corresponding session weight. Then, the weighted allocation is performed according to the session weight, and the first amount of communication resources is allocated to the service sessions under the target service type.
[0056] Optionally, in the above embodiments, when it is determined that the first quota is greater than the upper limit of the service resource quota, the process of allocating the communication resources of the upper limit of the service resource quota to the service session of the target service type is the same as the process of allocating the communication resources of the first quota to the service session of the target service type, and will not be repeated here.
[0057] In an exemplary embodiment, adjusting the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions includes: obtaining a service-aware tag from a data link layer frame sent by the IoT device through a service session of a target service type; obtaining the priority adjustment information from the service-aware tag, wherein the priority adjustment information includes the target service type in the service-aware tag and the adjusted service priority of the target service type, wherein the IoT device increases the service priority of the target service type to obtain the adjusted service priority when the communication quality of the service session of the target service type is reduced; and reallocating the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
[0058] Optionally, in the above embodiments, when an IoT device senses a decline in communication quality during a service session with the gateway (e.g., the application layer detects increased transmission latency), its transmission control layer will proactively increase the priority of the service type. The device adds a service-aware tag to the data link layer frame it sends outwards, encapsulating the service ID and the adjusted higher service priority. Upon receiving the data frame, the IoT gateway parses the service-aware tag to obtain the priority adjustment information initiated by the IoT device. This information clearly indicates the target service type requiring adjustment and the adjusted service priority. The gateway will then trigger resource reallocation calculations based on the adjusted service priority and other configuration rules in the resource configuration information, reallocating communication resources to obtain the target resource quota after responding to the device's request. This mechanism achieves linkage between device-side perception and gateway-side scheduling, enabling rapid response to and optimization of localized communication quality degradation.
[0059] In an exemplary embodiment, adjusting the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions further includes: when it is determined that the utilization rate of communication resources for a service session of the target service type, as indicated by the resource usage information, is less than a preset utilization rate within a preset time period, reducing the service priority of the target service type to obtain an adjusted service priority; and reallocating the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
[0060] Optionally, in the above embodiments, the IoT gateway uses a monitoring module to continuously monitor the actual utilization rate of allocated communication resources for each service session. For example, if the gateway detects that a service session of a certain target service type has consistently used less than 60% of the resources allocated to it within the last 30 seconds, it will determine that the session is currently wasting resources. At this time, the gateway will proactively reduce the service priority of that target service type (or directly reduce the priority of that specific session). Subsequently, based on this reduced priority, the gateway re-executes the resource allocation algorithm, reduces the resource quota allocated to that service type or session, and releases the recovered resources back to the system's idle resource pool. The resulting new target resource quota is more in line with actual needs, improves overall resource utilization, and avoids resource hoarding.
[0061] In an exemplary embodiment, adjusting the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions further includes: determining the communication resource usage quota of the service session of the target service type at multiple time nodes within a preset period according to the resource usage information; determining the predicted communication resource usage quota of the service session of the target service type at a target time node in the next preset period according to the communication resource usage quota at multiple time nodes within the preset period; and determining the target resource quota according to the predicted communication resource usage quota at the target time node in the next preset period.
[0062] Optionally, in the above embodiments, the IoT gateway collects and analyzes historical resource usage data over a long period. Specifically, based on resource usage information, it calculates the typical communication resource usage of a target service type's business sessions at various regular time points (e.g., every 5 minutes) within one or more complete preset periods (e.g., days, weeks, months). By analyzing this time-series data (e.g., using time series prediction algorithms), it can predict the predicted communication resource usage of the business session at a specific target time point (e.g., 9:00 AM on the next working day) in the next similar period. Based on this predicted usage, the resource quota is adjusted in advance before the target time point arrives to determine the target resource quota. For example, if the gateway learns that video traffic from office cameras always surges during the 9:00 AM clock-in period on working days, it can increase the resource quota for video services around 8:55 AM in advance, thereby smoothly coping with peak traffic and avoiding delays and lag caused by temporary adjustments.
[0063] Obviously, the embodiments described above are merely some embodiments of the present invention, and not all embodiments. To better understand the above-described method for allocating communication resources, the process is explained below with reference to embodiments, but this is not intended to limit the technical solutions of the embodiments of the present invention. Specifically:
[0064] In an optional embodiment, an IoT network structure is as follows: Figure 3 As shown, the IoT device and IoT gateway are physically connected. The data link layer provides data transmission support, and the IoT gateway can communicate with external networks. Resource adjustment and interaction between the IoT device and IoT gateway are achieved by transmitting data link layer frames at the data link layer. Service sessions of different service types are established between the IoT device and IoT gateway. For example... Figure 4 As shown, communication resources are allocated to different service types and service sessions based on static and dynamic configuration strategies. The static configuration strategy includes basic resource quotas and emergency communication quotas for each service type and session. The dynamic strategy includes dynamic or predictive adjustments to resource allocation based on autonomous feedback from communication devices, real-time communication resource monitoring, and long-term communication resource monitoring.
[0065] In an optional embodiment, the static resource configuration sets reserved resource values for communication of emergency services, and configures parameters as shown in Table 1 for each service type.
[0066] Table 1
[0067]
[0068] Specifically, the total base resource amount and the maximum upper limit resource amount under the maximum number of sessions for all services should be less than the total system resources; the maximum upper limit resource amount under the maximum number of sessions for all services should be less than the total system resources; and the number of sessions for each service type should not exceed the maximum number of sessions. These constraints ensure that, after dynamic adjustments, objects (referring to services or sessions) can meet the most basic operational requirements, while also guaranteeing that the dynamic adjustments will not exceed the system resource limit.
[0069] In one optional embodiment, the dynamic configuration strategy includes device-side dynamic strategies and gateway-side dynamic strategies. On the device side, based on actual application layer communication quality factors such as latency, the allocation parameters are dynamically adjusted and synchronized to the IoT gateway via the data link layer. The IoT gateway then dynamically adjusts its strategies accordingly. The gateway-side dynamic strategy dynamically adjusts resource allocation through real-time resource monitoring, considering actual service and session resource utilization, and identifies burst transmission patterns within a period through periodic resource monitoring, executing predictive dynamic adjustment strategies based on these patterns.
[0070] In an optional embodiment, the IoT device and the IoT gateway achieve resource adjustment interaction by transmitting data link layer frames at the data link layer, wherein the main structure of the data link layer frame is shown in Table 2.
[0071] Table 2
[0072]
[0073] Optionally, the above data link layer frame structure is for illustrative purposes only, and more fields can be added according to actual needs.
[0074] In an optional embodiment, the processing flow of the IoT gateway for the aforementioned data link layer frames is as follows: Figure 5 As shown, the IoT gateway receives data link layer frames sent by IoT devices, parses service-aware tags and session-aware tags, and the gateway's policy engine allocates communication resources based on the parsed information and static configuration. It should be noted that the above-mentioned communication resources are a general term and can be further subdivided into communication resources, hardware resources, and software resources.
[0075] In an optional embodiment, the processing flow for emergency services is as follows: Figure 6 As shown, when the gateway receives an emergency service, it triggers a hardware interrupt. If other transmission processes are currently in progress, they are paused and the emergency service is processed instead. Once the emergency service is completed, other transmission processes are resumed to normal operation.
[0076] In an optional embodiment, resource allocation is performed layer by layer according to resource scope, such as... Figure 7 As shown, the resource scope is divided into system domain, service domain and session domain. The system domain corresponds to all communication resources. Then, the service domain manages and allocates the resource quotas of each service according to the service type. In the session domain, the quota of each session in the total service resources is managed and allocated.
[0077] In an optional embodiment, the allocation rules for communication resources are as follows:
[0078] First allocation: Based on the static configuration, the reserved resource values for communication used for emergency services are removed.
[0079] Second allocation: Allocate basic resource quotas to all service sessions. In this stage, the service quota for each service type is the product of the number of sessions for that service and the basic resource quota for that service session.
[0080] The third allocation: Within the assigned scope, the remaining bandwidth is then weighted according to the priority determination weights, while also being limited by the service resource quota limit (determined based on the resource quota limit for a single session of the service and the number of sessions). For example: Total dynamic service quota = MIN(service weight / (existing total service weight) × remaining bandwidth, service resource quota limit).
[0081] If there are still free resources, they will be stored in the free resource pool and will not be allocated again.
[0082] In an optional embodiment, the allocation process for a new service session is as follows: Figure 8 As shown, it includes the following steps:
[0083] 1. The IoT gateway establishes a new business session with the IoT device;
[0084] 2. Check if the service type of this service session already has a resource quota. If yes, proceed to step 3; otherwise, proceed to step 5.
[0085] 3. Assess whether the existing total quota for this business type is sufficient to accommodate the basic guarantee resources for new sessions. If yes, proceed to step 4; otherwise, proceed to step 5.
[0086] 4. Perform the third allocation as described above, then proceed to step 9 to end the process;
[0087] 5. Check if the system's current idle resource pool has enough resources to allocate basic guarantee resources to the new session. If yes, proceed to step 6; otherwise, proceed to steps 7-8.
[0088] 6. Allocate basic guarantee resources for the new session from the idle resource pool, and execute step 9 to end the process;
[0089] 7. Perform the second allocation globally.
[0090] 8. Perform the third allocation globally, then execute step 9 to end the process;
[0091] 9. End the process.
[0092] Optionally, if a business session is to be deleted, the resource quota of that session is reclaimed and returned to the idle resource pool of its respective scope.
[0093] In one optional embodiment, dynamically adjusting the allocation of communication resources includes three cases:
[0094] a. Priority adjustments can be dynamically initiated by the communication participants. For example, when the application layer detects significant communication latency, it can attempt to adjust priorities. Specifically, this includes increasing the priority of service types to allocate more quotas and accelerate communication transmission; and adjusting session priorities to allocate more quotas within their respective service types to accelerate communication transmission. The priority adjustment process is as follows: Figure 9 As shown, the specific steps include:
[0095] 1. The IoT gateway receives priority adjustment information from IoT devices;
[0096] 2. Re-trigger the third allocation calculation mentioned above;
[0097] 3. If there are free resources in the scope, proceed to step 4; otherwise, proceed to step 6.
[0098] 4. If allocating idle resources can satisfy the results of the three allocations after adjusting the priority, then proceed to step 5; otherwise, proceed to step 6.
[0099] 5. Allocate resources from available resources for the objects requesting priority adjustments;
[0100] 6. All assets will be redistributed a third time;
[0101] In the above embodiments, prioritizing the use of idle resources to meet dynamic adjustment needs can ensure the stability of current services.
[0102] b. Real-time resource utilization is monitored to dynamically adjust resource allocation. This is executed by the IoT gateway, which monitors the utilization rate of corresponding objects (business types or sessions) in real time and automatically executes the reclamation process when the conditions are met. The reclamation condition is that, within the monitoring window, the used resources are less than the resource quota after the third allocation minus a constant coefficient (the reclamation condition can also be set to be below a preset utilization rate). The priority of the object is automatically reduced, and a third allocation is retried, targeting only that object. The reduced quota is placed in the idle resource pool. The specific process is as follows: Figure 10 As shown, it includes the following steps:
[0103] 1. The IoT gateway monitors real-time resource usage;
[0104] 2. Determine whether the monitored object has insufficient utilization and meets the recycling conditions. If yes, proceed to step 3; otherwise, proceed to step 5 to end the process.
[0105] 3. Reduce the priority of the object and perform a third allocation of the object;
[0106] 4. Add the recovered resources to the idle resource pool;
[0107] 5. End the process.
[0108] c. Predictive dynamic adjustment of resource allocation, executed by the IoT gateway, analyzes time-series resource data of monitored objects within daily, weekly, and monthly periodic windows using a time detection model to predict patterns of sudden resource demand. Before the corresponding time arrives, it dynamically adjusts the resource quotas of the objects in advance to cope with upcoming surges in demand. For example, if the gateway learns that video traffic from office cameras always surges during the 9:00 AM clock-in period on weekdays, it can increase the resource quota for video services around 8:55 AM in advance, thus smoothly handling peak traffic and avoiding delays and lag caused by last-minute adjustments. Optionally, the process of predictive dynamic adjustment of resource allocation is as follows: Figure 11 As shown, it includes the following steps:
[0109] 1. Runtime detection model: This model analyzes long-term resource usage data based on time prediction algorithms to obtain the resource usage patterns of the monitored object within daily, weekly, and monthly periodic windows, and then predicts the resource requirements of the monitored object at different time nodes.
[0110] 2. Determine whether the quota of the monitored object meets the model prediction value. If yes, no adjustment is made, and step 8 is executed to end the process; otherwise, step 3 is executed.
[0111] 3. Determine if there are any free resources. If yes, proceed to step 4; otherwise, proceed to step 5.
[0112] 4. Temporarily borrow available resources and execute step 8 to end the process;
[0113] 5. Determine whether it is possible to preempt the resources allocated in the third round for low-priority services. If yes, proceed to step 6; otherwise, proceed to step 7.
[0114] 6. Temporarily borrow resources from low-priority services, then execute step 8 to end the process;
[0115] 7. Adjust the priority of the monitored objects and redistribute all objects a third time;
[0116] 8. End the process.
[0117] In the above embodiments, prioritizing the borrowing of resources from idle or low-priority resources can ensure the stability of other services and reduce the impact on the overall business.
[0118] In an optional embodiment, such as Figure 12 As shown, the architecture of an IoT device consists of an application layer, a transmission control layer, and a data link layer. The transmission control layer receives data and quality events transmitted from the application layer, adjusts the service-aware tags and session-aware tags in the data link layer frames, and implements dynamic adjustment strategies. The communication quality monitoring component monitors the quality of service communication and session communication. When a change in communication quality is detected, it generates relevant quality events and synchronizes them to the transmission control layer, achieving multi-layered integrated control with upper-layer monitoring and lower-layer control.
[0119] In an optional embodiment, such as Figure 13 As shown, the architecture of the IoT gateway includes:
[0120] The data link layer is used to implement new data link layer protocols, as well as to implement resource control and management.
[0121] The monitoring module is used to monitor resource usage based on two dimensions: business type and session, and feeds the monitoring results back to the policy engine. For example, the monitoring results of resource utilization in a monitoring period are shown in Table 3.
[0122] Table 3
[0123]
[0124] The model engine uses algorithmic models to analyze the characteristics of object resource usage information over time and feeds the analysis results back to the strategy engine. For example, it generates business profiles based on business resource time-series data and identifies business time-specific characteristics through these profiles.
[0125] The policy engine, based on events and resource usage monitoring results from IoT devices, schedules different policies to generate policy actions and sends these actions to the data link layer to control resource allocation. The specific process is as follows: Figure 14 As shown, it includes the following steps:
[0126] 1. Input Events: The policy engine receives event notifications that require resource adjustments. Event sources include:
[0127] Device-side request: Priority adjustment request control frame sent by IoT device (due to communication quality degradation).
[0128] The monitoring module reports: resource utilization events (such as idle resources of a certain session) reported by the monitoring daemon process.
[0129] Model engine prediction: Predictive strategy instructions issued by the model engine (such as predicting that a business peak is approaching).
[0130] System management events: such as new session establishment, session termination, etc.
[0131] 2. The strategy engine assesses whether the current system resource status supports the adjustments required by the execution event and performs a feasibility analysis, including:
[0132] Global resource status: Whether the system's total idle resource pool is sufficient.
[0133] Local resource status: current quota, utilization rate, and static configuration constraints of the target service / session.
[0134] Impact assessment: The potential impact on other services / sessions if adjustments are made.
[0135] Output judgment: Provides a basis for selecting the execution strategy in the next step. If the judgment is satisfied, step 3 is executed; otherwise, the process ends.
[0136] 3. Execute strategies: Based on the event type and resource detection results, select and execute adjustment strategies. For example, in response to device priority adjustment requests, lower the priority or reclaim quotas for monitored idle resources, and pre-allocate resources or increase priority in advance for predicted events.
[0137] 4. Execute policy actions, which include:
[0138] At the software level: Adjust system scheduling parameters to speed up the scheduling of relevant business sessions and increase execution time, etc.
[0139] At the hardware level: Adjust hardware encoding and decoding scheduling, increase the encoding order of relevant service sessions, and speed up the process.
[0140] At the communication level: adjusting the order of business session transmission, increasing transmission speed, and increasing communication bandwidth, etc.
[0141] Through the above embodiments, an innovative collaborative optimization scheme is proposed for communication scenarios in IoT edge networks. By employing an end-to-end collaborative control mechanism between IoT devices and IoT gateways, unified management and dynamic optimization of multi-dimensional communication resources are achieved. This ensures the real-time and reliable transmission of urgent and high-priority business data, effectively preventing overall business degradation during network congestion; improves the overall resource utilization of the system; and through predictive dynamic adjustment strategies, proactively pre-configures resources based on historical data patterns to smoothly handle business peaks and reduce resource idleness. Furthermore, it enhances the adaptability and intelligence of IoT edge networks, enabling adaptive adjustment of resource allocation strategies based on real-time status and future trends, thereby achieving overall optimal service quality and resource efficiency in complex and ever-changing IoT business environments.
[0142] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.
[0143] This embodiment also provides a communication resource allocation device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware implementations, or a combination of software and hardware, are also possible and contemplated.
[0144] Figure 15 This is a structural block diagram of a communication resource allocation apparatus according to an embodiment of the present invention, the apparatus comprising:
[0145] The determining module 1502 is used to determine the initial resource quota of different service sessions established between the IoT device and the IoT gateway according to the preset resource configuration information, wherein the different service sessions correspond to different service types;
[0146] The acquisition module 1504 is used to acquire, after allocating communication resources according to the initial resource quota, priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and resource usage information monitored by the IoT gateway.
[0147] The adjustment module 1506 is used to adjust the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions.
[0148] The communication resource allocation device of this invention determines the initial resource quota for different service sessions established between an IoT device and an IoT gateway based on preset resource configuration information, wherein different service sessions correspond to different service types. After allocating communication resources according to the initial resource quota, priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and resource usage information monitored by the IoT gateway are obtained. The initial resource quota is adjusted according to the priority adjustment information and resource usage information to obtain the target resource quota for different service sessions. By adopting the above technical solution, after the initial allocation of communication resources according to the preset resource configuration information, the allocation of communication resources is dynamically adjusted according to the feedback from the IoT device and the resource usage information monitored by the gateway. This solves the problem in related technologies where the equal processing of all data by the IoT terminal network leads to unreasonable allocation of communication resources, thereby achieving the effect of reasonable allocation of IoT communication resources.
[0149] In an exemplary embodiment, the resource configuration information includes reserved resource quotas, session base resource quotas configured for each service type, session resource quota upper limits, preset session quantity, and preset service priority. A determining module 1502 is used to determine the allocatable resource quota in the communication resources, wherein the allocatable resource quota is the difference between the total communication resource quota and the reserved resource quota, and the reserved communication resources corresponding to the reserved resource quota are only allocated to emergency service sessions; allocate base resources to different service sessions according to the session base resource quota, wherein the number of service sessions for each service type does not exceed the preset session quantity; determine the remaining resource quota of the communication resources according to the difference between the allocatable resource quota and the base resource quota already allocated to the different service sessions; and allocate the remaining resource quota of the communication resources to the different service sessions according to the preset service priority.
[0150] In an exemplary embodiment, the determining module 1502 is configured to: determine a target priority corresponding to a target service type and a target weight corresponding to the target priority based on the preset service priority information; determine a first quota based on the product of a target ratio and the remaining resource quota, wherein the target ratio is the ratio of the target weight to the total weight; determine a service resource quota limit for the target service type based on the number of service sessions of the target service type and the session resource quota limit for the target service type; and allocate communication resources for the service sessions of the target service type based on the service resource quota limit and the first quota.
[0151] In an exemplary embodiment, the determining module 1502 is configured to allocate communication resources of the first quota to a service session of the target service type when it is determined that the first quota is less than the upper limit of the service resource quota; and to allocate communication resources of the upper limit of the service resource quota to a service session of the target service type when it is determined that the first quota is greater than the upper limit of the service resource quota.
[0152] In an exemplary embodiment, the determining module 1502 is configured to obtain a session-aware tag from a data link layer frame sent by the IoT device through a service session of the target service type, wherein the session-aware tag includes a session identifier and session priority information; obtain session priority information of the service session of the target service type based on the session-aware tag, wherein the session priority information includes a session priority and a session weight corresponding to the session priority; and allocate the first amount of communication resources to the service session of the target service type according to the session weight of the service session of the target service type.
[0153] In an exemplary embodiment, the adjustment module 1506 is configured to obtain a service-aware tag from a data link layer frame sent by the IoT device through a service session of a target service type; obtain priority adjustment information from the service-aware tag, wherein the priority adjustment information includes a target service type in the service-aware tag and an adjusted service priority for the target service type, wherein the IoT device increases the service priority of the target service type to obtain the adjusted service priority when the communication quality of the service session of the target service type is reduced; and reallocate the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
[0154] In an exemplary embodiment, the adjustment module 1506 is configured to, when it is determined that the utilization rate of communication resources for a service session of a target service type, as indicated by the resource usage information, is less than a preset utilization rate within a preset time period, reduce the service priority of the target service type to obtain an adjusted service priority; and reallocate the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
[0155] In an exemplary embodiment, the adjustment module 1506 is configured to determine, based on the resource usage information, the communication resource usage quota of a service session of a target service type at multiple time points within a preset period; determine, based on the communication resource usage quota at multiple time points within the preset period, the predicted communication resource usage quota of the service session of the target service type at a target time point within the next preset period; and determine the target resource quota based on the predicted communication resource usage quota at the target time point within the next preset period.
[0156] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:
[0157] S1, determine the initial resource quota for different service sessions established between the IoT device and the IoT gateway according to the preset resource configuration information, wherein the different service sessions correspond to different service types;
[0158] S2, after allocating communication resources according to the initial resource quota, obtain priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and obtain resource usage information monitored by the IoT gateway;
[0159] S3, adjust the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions.
[0160] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.
[0161] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.
[0162] Embodiments of the present invention also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.
[0163] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:
[0164] S1, determine the initial resource quota for different service sessions established between the IoT device and the IoT gateway according to the preset resource configuration information, wherein the different service sessions correspond to different service types;
[0165] S2, after allocating communication resources according to the initial resource quota, obtain priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and obtain resource usage information monitored by the IoT gateway;
[0166] S3, adjust the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions.
[0167] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.
[0168] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.
[0169] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.
[0170] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for allocating communication resources, characterized in that, Applications in IoT gateways include: The initial resource quotas for different service sessions established between the IoT device and the IoT gateway are determined based on preset resource configuration information, wherein the different service sessions correspond to different service types; After allocating communication resources according to the initial resource quota, the priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and the resource usage information monitored by the IoT gateway are obtained. The initial resource quota is adjusted based on the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions; The process of adjusting the initial resource quota based on the priority adjustment information and the resource usage information to obtain the target resource quota for different service sessions includes: Obtain the service-aware tag from the data link layer frame sent by the IoT device through a service session of the target service type; The priority adjustment information is obtained from the service-aware tag, wherein the priority adjustment information includes the target service type in the service-aware tag and the adjusted service priority of the target service type. When the communication quality of the service session of the target service type is reduced, the IoT device increases the service priority of the target service type to obtain the adjusted service priority. Based on the adjusted service priority and the resource configuration information, the communication resources are reallocated to the service sessions of the target service type to obtain the target resource quota.
2. The method for allocating communication resources according to claim 1, characterized in that, The resource configuration information includes reserved resource quotas, basic session resource quotas, session resource quota limits, preset session counts, and preset service priorities configured for each service type. Based on the preset resource configuration information, the initial resource quotas for different service sessions established between the IoT device and the IoT gateway are determined, including: Determine the allocable resource quota in the communication resources, wherein the allocable resource quota is the difference between the total quota of the communication resources and the reserved resource quota, and the reserved communication resources corresponding to the reserved resource quota are only allocated to emergency service sessions; Basic resources are allocated to different service sessions according to the session basic resource quota, wherein the number of service sessions for each service type does not exceed the preset number of sessions; The remaining resource quota of the communication resources is determined based on the difference between the allocable resource quota and the basic resource quota already allocated to the different service sessions; The remaining communication resources are allocated to different service sessions according to the preset service priority.
3. The method for allocating communication resources according to claim 2, characterized in that, According to the preset service priority, the remaining resource quota of communication resources is allocated to the different service sessions, including: Determine the target priority corresponding to the target business type and the target weight corresponding to the target priority based on the preset business priority; The first quota is determined by multiplying the target ratio by the remaining resource quota, wherein the target ratio is the ratio of the target weight to the total weight; The upper limit of the service resource quota for the target service type is determined based on the number of service sessions for the target service type and the upper limit of the session resource quota for the target service type. The communication resources are allocated to the service session of the target service type based on the upper limit of the service resource quota and the first quota.
4. The method for allocating communication resources according to claim 3, characterized in that, Based on the service resource quota limit and the first quota, the communication resources are allocated to the service session of the target service type, including: If it is determined that the first quota is less than the upper limit of the service resource quota, the communication resources of the first quota will be allocated to the service session of the target service type; If it is determined that the first quota is greater than the upper limit of the service resource quota, the communication resources of the upper limit of the service resource quota are allocated to the service session of the target service type.
5. The method for allocating communication resources according to claim 4, characterized in that, If it is determined that the first quota is less than the upper limit of the service resource quota, the communication resources of the first quota are allocated to the service session of the target service type, including: The session-aware tag is obtained from the data link layer frame sent by the IoT device through the service session of the target service type, wherein the session-aware tag includes session identifier and session priority information; The session priority information of the business session of the target business type is obtained according to the session awareness tag, wherein the session priority information includes the session priority and the session weight corresponding to the session priority; The first amount of communication resources is allocated to the service sessions of the target service type according to the session weight of the service sessions of the target service type.
6. The method for allocating communication resources according to claim 1, characterized in that, Adjusting the initial resource quota based on the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions, further comprising: If the resource usage information indicates that the communication resource utilization rate of a service session of the target service type is less than the preset utilization rate within a preset time period, the service priority of the target service type is reduced to obtain the adjusted service priority. Based on the adjusted service priority and the resource configuration information, the communication resources are reallocated to the service sessions of the target service type to obtain the target resource quota.
7. The method for allocating communication resources according to claim 1, characterized in that, Adjusting the initial resource quota based on the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions, further comprising: Based on the resource usage information, determine the communication resource usage quota of the target service type service session at multiple time points within a preset period; Based on the communication resource usage quota at multiple time points within a preset period, the predicted communication resource usage quota for the service session of the target service type at the target time point in the next preset period is determined. The target resource quota is determined based on the predicted usage of communication resources at the target time node in the next preset period.
8. A communication resource allocation device, characterized in that, include: The determination module is used to determine the initial resource quota of different service sessions established between IoT devices and IoT gateways based on preset resource configuration information, wherein the different service sessions correspond to different service types; The acquisition module is used to acquire, after allocating communication resources according to the initial resource quota, priority adjustment information fed back by the IoT device when the communication quality of the service session with the IoT gateway changes, and resource usage information monitored by the IoT gateway. The adjustment module is used to adjust the initial resource quota according to the priority adjustment information and the resource usage information to obtain the target resource quota for the different service sessions; The adjustment module is further configured to obtain a service-aware tag from the data link layer frame sent by the IoT device through a service session of the target service type; obtain the priority adjustment information from the service-aware tag, wherein the priority adjustment information includes the target service type in the service-aware tag and the adjusted service priority of the target service type, wherein the IoT device increases the service priority of the target service type to obtain the adjusted service priority when the communication quality of the service session of the target service type is reduced; and reallocate the communication resources for the service session of the target service type according to the adjusted service priority and the resource configuration information to obtain the target resource quota.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method described in any one of claims 1 to 7.
10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 7 through the computer program.