Wireless resource scheduling method and apparatus, network device, and storage medium

Abstract

Embodiments of the present application provide a wireless resource scheduling method and device, a network device and a storage medium. The method comprises: receiving sensing data corresponding to at least one service sent by a second network device; the sensing data comprises at least one of the following: service direction, service priority, service stage, time delay level, time delay data, data length, historical data; and allocating a target subcarrier spacing for a first service and / or a target time slot ratio for a second service according to the sensing data. The wireless resource scheduling method can allocate a high subcarrier spacing for a key service with a high time delay level, and adjust the time slot ratio of the service according to the service direction, etc. Different granularities of resource scheduling can be performed for different services, the resource scheduling is refined, and the high real-time performance of service data transmission is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, specifically to a wireless resource scheduling method, apparatus, network device, and storage medium. Background Technology

[0002] Existing 5G industrial scheduling solutions follow the common 5G NR frame structure, employing fixed subcarriers and fixed time slot ratios. Resources are scheduled by the Media Access Control (MAC) layer based on fixed time slots, with Time Division Duplex (TDD) time slot ratios configured statically or semi-statically via Radio Resource Control (RRC). This approach offers strong stability and good compatibility, meeting the needs of conventional industrial monitoring and low-speed control services. However, its scheduling mechanism is designed for public mobile communications and is not optimized for the real-time timing characteristics of industrial closed-loop services, resulting in insufficient dynamic adaptation capabilities and significant closed-loop response latency. Therefore, it cannot meet the low-latency, high-reliability, and high-synchronization transmission requirements of industrial service closed loops based on the Sub-6GHz or U6GHz bands while maintaining compatibility with standard 5G protocol stacks. Summary of the Invention

[0003] At least one embodiment of this application provides a wireless resource scheduling method, apparatus, network device, and storage medium to solve the problem that the existing technology, which uses fixed subcarriers and fixed time slot ratios, cannot meet the requirements of low-latency services for fine-grained resource scheduling.

[0004] To solve the above-mentioned technical problems, this application is implemented as follows:

[0005] In a first aspect, embodiments of this application provide a wireless resource scheduling method, applied to a first network device, comprising:

[0006] Receive sensing data corresponding to at least one service sent by a second network device; the sensing data includes at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data;

[0007] Based on the perceived data, a target subcarrier spacing is allocated for the first service, and / or a target time slot allocation is allocated for the second service.

[0008] Optionally, based on the perceived data, allocating a target subcarrier interval for the first service map includes:

[0009] If the first service is a first service type, a first subcarrier interval is allocated to the first service;

[0010] If the first service is a second service type, a second subcarrier interval is allocated to the first service;

[0011] The service type is determined based on the service direction, service priority, service stage, and latency level; the first subcarrier interval is greater than the second subcarrier interval.

[0012] Optionally, the delay data includes at least one of the following:

[0013] Transmission delay, air interface waiting delay, direction waiting delay, queuing waiting delay, edge processing delay, and protocol processing delay.

[0014] Optionally, based on the perceived data, a target time slot allocation is assigned to the second service, including:

[0015] Based on the perceived data, first data is determined; the first data includes at least one of the following: the length of the uplink service queue, the length of the downlink service queue, the remaining latency budget, and the historical latency jitter;

[0016] Based on the first data and the stage to which the service belongs, the target time slot allocation is assigned to the service.

[0017] Optionally, based on the first data and the stage to which the service belongs, the target time slot allocation is assigned to the service, including:

[0018] When the length of the uplink service queue is greater than the length of the downlink service queue, and the service belongs to a stage where uplink data is concentrated, a first time slot allocation is assigned to the service.

[0019] When the length of the uplink service queue is less than the length of the downlink service queue, and the service belongs to a downlink data concentration phase, a second time slot allocation is assigned to the service.

[0020] In this case, the uplink time slot ratio of the first time slot allocation is higher than the uplink time slot ratio of the second time slot allocation.

[0021] Optionally, the method further includes:

[0022] The third service is determined based on the perceived data; the third service is a service with a latency level higher than a preset level.

[0023] The service data of the third service is sent to the target terminal via a direct transmission link;

[0024] The direct transmission link is a transmission link established between the distributed unit of the first network device and the terminal through a virtual network card interface.

[0025] Optionally, the service data of the third service is sent to the target terminal via a direct transmission link, including:

[0026] Identify the target IP address in the business data;

[0027] The target terminal is determined based on the target IP and the mapping data; the mapping data is the correspondence between the terminal and the physical layer terminal identifier pre-stored in the first network device.

[0028] The data header of the business data for the first business type is encapsulated; the data header includes: the identifier of the target terminal, the data length, the serial number, and the data type;

[0029] The encapsulated business data is sent to the target terminal via a direct transmission link;

[0030] The first network device and the terminal are configured with corresponding IP addresses.

[0031] Secondly, embodiments of this application provide a wireless resource scheduling device, applied to a first network device, comprising:

[0032] The receiving module is used to receive sensing data corresponding to at least one service sent by the second network device; the sensing data includes at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data;

[0033] The allocation module is used to allocate a target subcarrier interval for the first service and / or allocate a target time slot ratio for the second service based on the sensed data.

[0034] Thirdly, embodiments of this application provide a network device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the wireless resource scheduling method as described above.

[0035] Fourthly, embodiments of this application provide a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of the wireless resource scheduling method described above.

[0036] Compared with existing technologies, the wireless resource scheduling method, apparatus, network device, and storage medium provided in this application distinguish services based on received sensing data including at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data. Different subcarrier intervals are allocated to different services, and / or different time slot ratios are allocated to different services. This allows for the allocation of higher subcarrier intervals to critical services with high latency levels, and the adjustment of time slot ratios based on service direction, enabling resource scheduling at different granularities for different services. This achieves refined resource scheduling and improves the real-time performance of service data transmission. Attached Figure Description

[0037] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0038] Figure 1 This is a schematic diagram illustrating the interaction between a network device and a terminal according to an embodiment of this application;

[0039] Figure 2 This is a schematic diagram illustrating the steps of the wireless resource scheduling method according to an embodiment of this application when applied to a first network device;

[0040] Figure 3 This is a schematic diagram of the system on which the wireless resource scheduling method of this application is implemented;

[0041] Figure 4 This is a schematic diagram of the overall process of the wireless resource scheduling method according to an embodiment of this application;

[0042] Figure 5 This is a logical schematic diagram of the wireless resource scheduling method according to an embodiment of this application;

[0043] Figure 6 This is a schematic diagram of the structure of a network device according to an embodiment of this application.

[0044] Figure 7 This is a schematic diagram of the structure of a network device according to another embodiment of this application. Detailed Implementation

[0045] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0046] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc.; an indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0047] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0048] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11, a first network device 12, and a second network device 13. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application. The first network device 12 may include access network devices or core network devices, and the second network device 13 is an edge network device, which may include access network devices. The access network device can also be referred to as a Radio Access Network (RAN) device, a Radio Access Network function, or a Radio Access Network unit. Access network devices may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.In this context, a base station may be referred to as a Node B (NB), an Evolved Node B (eNB), a Next Generation Node B (gNB), a New Radio Node B (NR Node B), an Access Point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a Radio Base Station, a Radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The base station is not limited to any specific technical terminology. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.

[0049] Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0050] To enable those skilled in the art to better understand the embodiments of this application, the following description is provided first:

[0051] With the popularization of 5G and industrial networked control technologies, industrial robots, AGVs, and various sensing terminals have been widely used in intelligent manufacturing. Industrial scenarios require rapid reporting and feedback of sensing, status, and control data to form a closed loop of "perception-decision-execution," which places extremely high demands on the latency, reliability, and dynamic resource scheduling capabilities of wireless communication.

[0052] Existing 5G NR resource scheduling schemes based on fixed subcarrier spacing and fixed time slot allocation adopt the common 5G NR frame structure, with multiple fixed 30kHz subcarrier spacings. Resources are scheduled by the MAC layer based on fixed time slots, and the TDD time slot allocation is configured statically or semi-statically via RRC. This approach offers strong stability and good compatibility, meeting the needs of conventional industrial monitoring and low-speed control services. However, its scheduling mechanism is designed for public mobile communications and is not optimized for the real-time timing characteristics of industrial closed-loop services, resulting in insufficient dynamic adaptation capabilities and significant closed-loop response latency. Furthermore, latency-sensitive services must wait for time slot boundaries before being scheduled for transmission, generating additional queuing latency, which severely impacts the closed-loop response speed and control stability of industrial high-frequency sensing reporting and control command issuance.

[0053] The Sub6GHz band includes: F band (1880-1920MHz), A band (2010-2025MHz), and n77 / 78 (Cband); the U6GHz band includes: 6425-7125 MHz, which can meet the requirements of industrial business closed loop for low latency, high reliability, and high synchronization transmission.

[0054] Current industrial 5G service data requires encapsulation and processing through multiple protocol stacks such as SDAP, PDCP, and RLC. While protocol layering ensures system integrity and universality, it introduces significant processing latency. Current mainstream latency optimization methods only shorten network forwarding paths through UPF (User-Defined Frame) deployment and local traffic offloading, without optimizing the protocol layering overhead at the terminal and air interface. The caching, queuing, and retransmission mechanisms of higher-level protocols further exacerbate latency, failing to meet the ultra-low latency and high real-time requirements of industrial closed-loop control services.

[0055] This application is applicable to multi-agent collaborative systems in intelligent manufacturing workshops, describing the collaborative operation of fixed robotic arms, mobile robotic arms, automated guided vehicles (AGVs), edge servers, base stations, sensors, and communication units in a real industrial environment. In this scenario, the fixed robotic arm is mainly responsible for workpiece operation and task connection between the assembly area and the finished product area. The mobile robotic arm is mounted on the AGV platform and, combined with the communication unit and depth camera, realizes mobile operation, environmental perception, and task execution. The base station is responsible for wireless access, resource scheduling, and data forwarding, and the base station antenna is responsible for wireless signal transmission and reception. The edge server is responsible for processing perceived information, calculating tasks, and generating control commands, thus forming a closed-loop interactive link of "on-site perception—wireless transmission—edge decision-making—execution control".

[0056] This application provides a wireless resource scheduling method and apparatus. The method and apparatus are based on the same concept, and since the principles by which they solve the problem are similar, their implementations can be referred to interchangeably; repeated details will not be repeated.

[0057] like Figure 2 As shown in the embodiment of this application, a wireless resource scheduling method, when applied to a first network device, includes the following method:

[0058] Step 201: Receive sensing data corresponding to at least one service sent by the second network device; the sensing data includes at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data;

[0059] Step 202: Based on the perceived data, allocate a target subcarrier interval for the first service, and / or allocate a target time slot ratio for the second service.

[0060] Optionally, the sensing data is obtained by jointly sensing the multimodal data of the second network device;

[0061] Furthermore, the multimodal data includes: environmental status information, equipment status information, and closed-loop business status information continuously collected by AGVs, robotic arms, cameras, and various sensors in the industrial site.

[0062] Furthermore, after the multimodal data is uploaded to the second network device, the second network device identifies the current service load direction, the urgency of critical services, and the closed-loop stage.

[0063] Optionally, a target subcarrier spacing is allocated for the first service, including:

[0064] The first service is mapped to the resource pool of the target subcarrier interval.

[0065] Optionally, the service direction includes: the service corresponding to the data that needs to be transmitted uplink or the service corresponding to the data that needs to be transmitted downlink;

[0066] The business processes are divided into the following stages: uplink sensing stage and downlink control stage; for example, the industrial high-frequency sensing and reporting stage and the control command issuance stage.

[0067] The wireless resource scheduling method of this application, based on received sensing data including at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data, distinguishes services, allocates different subcarrier intervals to different services, and / or allocates different time slot ratios to different services. It can allocate higher subcarrier intervals to critical services such as those with high latency levels, and adjust the time slot ratios of services according to their direction, enabling resource scheduling at different granularities for different services, achieving refined resource scheduling, and improving the high real-time performance of service data transmission.

[0068] In this embodiment of the application, it is set at time The sensing state vector (the multimodal data) received by the first network device is The edge controller (the second network device) extracts scheduling features based on the perception state vector to obtain the resource scheduling state vector:

[0069] ;

[0070] in, The mapping function represents the mapping from the perception state to the scheduling state; the mapping result includes at least: the current business direction, the priority of key businesses, the closed-loop stage of the business, and whether it needs to enter the high time resolution resource pool.

[0071] To characterize the directional characteristics of current business, the proportion of upstream business is defined as:

[0072] ;

[0073] The corresponding percentage of business in the downstream direction is:

[0074] ;

[0075] in, and Representing time respectively Upstream service arrival rate and downstream service arrival rate.

[0076] Therefore, the system can be based on , Information such as the remaining latency budget of the business can be used to determine whether the current stage is "centralized feedback of perception information", "centralized issuance of control instructions" or "two-way high load stage", thereby providing a basis for subsequent dynamic resource scheduling.

[0077] Optionally, based on the perceived data, allocating a target subcarrier interval for the first service map includes:

[0078] If the first service is a first service type, a first subcarrier interval is allocated to the first service;

[0079] If the first service is a second service type, a second subcarrier interval is allocated to the first service;

[0080] The service type is determined based on the service direction, service priority, service stage, and latency level; the first subcarrier interval is greater than the second subcarrier interval.

[0081] In this embodiment, resource pools corresponding to different subcarrier spacings (SCS) are dynamically allocated to different services based on the service type and closed-loop stage.

[0082] Optionally, the first service type is a critical service with a service priority higher than a preset priority, a service stage of perception feedback or control command, and a latency level higher than a preset level.

[0083] The second type of business is a normal business whose business priority is lower than the preset priority, whose business stage is data monitoring, log uploading, and whose latency level is lower than the preset level.

[0084] Optionally, the first subcarrier spacing is greater than or equal to 30 kHz SCS; the second subcarrier spacing is greater than or equal to 120 kHz SCS.

[0085] In this embodiment, the services are first identified and classified based on the perceived data. For ordinary services, such as periodic device status reporting, log transmission, non-critical video streams, or ordinary data services, the system prioritizes mapping them to the regular time slot resource pool corresponding to the 30kHz SCS. For critical services, such as perceived information feedback, control command issuance, and collaborative synchronization messages, the system prioritizes mapping them to the high temporal resolution resource pool corresponding to the 120 kHz SCS.

[0086] Optionally, based on the perceived data, a target time slot allocation is assigned to the second service, including:

[0087] Based on the perceived data, first data is determined; the first data includes at least one of the following: the length of the uplink service queue, the length of the downlink service queue, the remaining latency budget, and the historical latency jitter;

[0088] Based on the first data and the stage to which the service belongs, the target time slot allocation is assigned to the service.

[0089] In this embodiment of the application, after allocating different subcarrier intervals to different services, the time slot ratio of time division duplex is further adjusted in real time according to the changes in service direction.

[0090] For example, during the stage where sensing terminals centrally report environmental information, the system increases the uplink time slot ratio and prioritizes configuring newly added uplink resources in the high SCS resource pool; during the stage where the edge controller completes the decision and generates a large number of control commands to be issued, the system increases the downlink time slot ratio; during the bidirectional high load stage, the system achieves real-time direction switching through dynamic time slots and high-priority queues.

[0091] Optionally, based on the first data and the stage to which the service belongs, the target time slot allocation is assigned to the service, including:

[0092] When the length of the uplink service queue is greater than the length of the downlink service queue, and the service belongs to a stage where uplink data is concentrated, a first time slot allocation is assigned to the service.

[0093] When the length of the uplink service queue is less than the length of the downlink service queue, and the service belongs to a downlink data concentration phase, a second time slot allocation is assigned to the service.

[0094] In this case, the uplink time slot ratio of the first time slot allocation is higher than the uplink time slot ratio of the second time slot allocation.

[0095] Optionally, the service phases in the uplink data set may include: the phase where sensing terminals centrally report environmental information, the phase where the length of the uplink service queue is greater than a preset length, and the phase where the uplink service arrival rate is higher than a preset proportion.

[0096] The service phases in the downlink data set may include: the phase in which the second network device completes the decision and generates a large number of control commands to be issued, the phase in which the downlink service queue length is greater than a preset length, and the phase in which the downlink service arrival rate is higher than a preset ratio.

[0097] It should be noted that after identifying the service status, the system dynamically allocates resource pools corresponding to different subcarrier spacings (SCS) for different services based on the service type and closed-loop stage. Ordinary services and non-critical status monitoring services are preferentially mapped to the 30kHz resource pool; sensing backhaul services, control command services, and other high-priority closed-loop coordination services are preferentially mapped to the 120kHz resource pool. This design is based on the principle that the larger the subcarrier spacing and the shorter the time slot length, the lower the average waiting delay for the service to wait for the next scheduling moment.

[0098] For an NR system, let the waveform parameter set numberology parameter be... Then the subcarrier spacing It can be represented as:

[0099] ;

[0100] Corresponding standard time slot length It can be represented as:

[0101] ;

[0102] Therefore, when the system switches from a 30 kHz subcarrier spacing to a 120 kHz subcarrier spacing:

[0103] ;

[0104] ;

[0105] If we assume that the arrival times of services follow a uniform distribution within a time slot, then the average waiting time for services to wait until the next available scheduling time is approximately:

[0106] ;

[0107] Therefore, the average latency under the 30kHz and 120kHz configurations are approximately as follows:

[0108] ;

[0109] .

[0110] As shown above, increasing the subcarrier spacing can significantly reduce the basic latency caused by critical services waiting for complete time slot boundaries. Therefore, for high dynamic area services, sensing backhaul services, and control transmission services identified by the camera, the system prioritizes mapping them to resource pools with higher SCS (Segment Class Separation) to improve air interface time resolution and shorten latency.

[0111] It should be noted that, considering that the uplink sensing backhaul service and the downlink control command service have obvious phased and directional change characteristics in the industrial closed-loop process, this application adjusts the uplink time slot ratio and downlink time slot ratio in the time-division duplex configuration in real time according to the current sensing status, the length of the uplink and downlink key service queues, the urgency of the key services, the edge decision status, and the historical latency jitter.

[0112] For example, suppose there are a total of [number] cases within a time-division duplex configuration cycle. There are 10 time slots, of which the number of uplink time slots is 10. The number of downlink time slots is ,but:

[0113] ;

[0114] The uplink timeslot percentage can be defined as:

[0115] ;

[0116] The downlink time slot percentage can be defined as:

[0117] ;

[0118] If the additional average waiting time caused by limited directional resources is approximated as being inversely proportional to the available directional time slot density, then for a certain direction... The average directional waiting time can be expressed as:

[0119] ;

[0120] in, This indicates the proportion of time slots in the current resource pool for that direction. As can be seen from the expression, under the same subcarrier spacing configuration, when the proportion of time slots in a certain direction increases, the average waiting time for services in that direction to reach the "next available time slot in the same direction" will decrease.

[0121] To dynamically adjust according to business load and The uplink resource demand score is defined as follows:

[0122] ;

[0123] The downlink resource demand score is defined as follows:

[0124] ;

[0125] in, and These represent the lengths of the uplink and downlink critical business queues, respectively. and These represent the urgency of key business tasks in the corresponding areas. and These represent the remaining delay budget, and These represent the directional time delay jitter statistics, respectively. These are the weighting coefficients.

[0126] Furthermore, the uplink slot percentage can be dynamically updated as follows:

[0127] ;

[0128] The corresponding downlink time slot percentage is:

[0129] ;

[0130] The ratio of uplink to downlink practice indicates that when the system is in the stage of centralized feedback of perceived information, Increase the number of uplink time slots to improve the uplink time slot ratio; when the system is in the control command centralized issuance phase... This increases the proportion of downlink time slots. The unlimited resource scheduling method in this application embodiment enables wireless directional resource allocation to better match the service directional needs of different stages of the industrial closed loop, and reduces directional congestion and queue backlog.

[0131] Optionally, the method further includes:

[0132] The third service is determined based on the perceived data; the third service is a service with a latency level higher than a preset level.

[0133] The service data of the third service is sent to the target terminal via a direct transmission link;

[0134] The direct transmission link is a transmission link established between the distributed unit of the first network device and the terminal through a virtual network card interface.

[0135] Optionally, the service data of the third service is sent to the target terminal via a direct transmission link, including:

[0136] Identify the target IP address in the business data;

[0137] The target terminal is determined based on the target IP and the mapping data; the mapping data is the correspondence between the terminal and the physical layer terminal identifier pre-stored in the first network device.

[0138] The data header of the business data for the first business type is encapsulated; the data header includes: the identifier of the target terminal, the data length, the serial number, and the data type;

[0139] The encapsulated business data is sent to the target terminal via a direct transmission link;

[0140] The first network device and the terminal are configured with corresponding IP addresses.

[0141] Optionally, the mapping data refers to the mapping relationship between the terminal IP address and the physical layer terminal identifier.

[0142] In this embodiment, considering that service data in the traditional 5G user plane protocol stack typically needs to go through multiple processing stages such as Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and core network user plane forwarding, which can easily introduce significant protocol processing latency and forwarding overhead, the system establishes a physical layer direct transmission channel for latency-sensitive critical services (such as services of the first service type) to compress the transmission path and reduce unnecessary protocol processing. Subsequently, virtual network interface cards are introduced on the base station distribution unit (DU) side and the terminal side, respectively, enabling upper-layer services to access the direct transmission link in the form of standard IP data. By maintaining the mapping relationship between the terminal IP address and the physical layer terminal identifier, the system achieves rapid location and forwarding of service data to the target terminal.

[0143] Once critical business data enters the direct transmission channel, the system performs lightweight header encapsulation on the data during physical layer scheduling and directly sends it to the physical layer transmission link for subsequent transmission, without needing to undergo layer-by-layer processing by higher-layer user plane protocol entities. On the receiving side, after signal demodulation and decoding, the system identifies, decapsulates, and restores the payload of the directly transmitted data, then delivers the data to the upper-layer application via a virtual network interface card, thus forming an efficient, transparent, and fast data path between the sending and receiving ends.

[0144] It should be noted that, in order to meet the needs of both standard and critical services operating in parallel, the system retains the standard 5G protocol stack processing flow for standard services, while adopting a combination of variable layer transmission mechanism and edge-side user plane sinking for critical services. This effectively reduces the latency of closed-loop communication for critical services and improves the real-time transmission capability and system operating efficiency of industrial closed-loop services without compromising the existing overall network architecture and standard compatibility.

[0145] Optionally, the delay data includes at least one of the following:

[0146] Transmission delay, air interface waiting delay, direction waiting delay, queuing waiting delay, edge processing delay, and protocol processing delay.

[0147] For example, in order to simultaneously reflect the joint impact of subcarrier spacing and uplink / downlink time slot ratio on service latency, the average waiting latency of critical services on the air interface side can be approximated as follows:

[0148] ;

[0149] in, Indicates the first One business, This indicates the numeric parameter corresponding to the resource pool mapped to this service. This indicates the percentage of time slots in the current resource pool for the direction to which this service belongs.

[0150] Substituting the standard timeslot length into the average waiting time on the air interface side, we can further obtain:

[0151] ;

[0152] Therefore, increasing the numerology parameter corresponding to SCS... This can reduce waiting latency and increase the proportion of time slots in the business direction. This also reduces waiting latency. Therefore, this application combines dynamic subcarrier spacing allocation with dynamic uplink / downlink time slot allocation, which can work together to reduce air interface waiting latency.

[0153] Furthermore, when considering the service transmission process, in addition to air interface waiting delay, it is also necessary to consider service transmission delay, queuing waiting delay, edge processing delay, and protocol processing delay. Let the... The data packet length for each key business function is bit, in the allocated bandwidth The received signal-to-noise ratio is If the transmission occurs on a resource, its approximate transmission rate can be written as:

[0154] ;

[0155] Therefore, the first The transmission latency for each service is:

[0156] ;

[0157] If we further consider queuing delays Edge processing latency and protocol processing delay Then the closed-loop communication latency of critical business operations can be expressed as:

[0158]

[0159] Substituting the average waiting time on the air interface side into the closed-loop communication delay, we get:

[0160] ;

[0161] Therefore, the perception-assisted dynamic resource scheduling in this invention mainly reduces the latency of closed-loop communication for critical services in the following ways:

[0162] By dynamically increasing the subcarrier spacing corresponding to key services, the reduction ;

[0163] By dynamically adjusting the uplink and downlink time slot ratio, the corresponding direction's... ;

[0164] Reduce protocol stack processing latency through subsequent layer-changing transport mechanisms. .

[0165] like Figure 3 This is a schematic diagram of the system upon which the wireless resource scheduling method of this application is based;

[0166] like Figure 4 and Figure 5 As shown, the wireless resource scheduling method of this application embodiment includes:

[0167] First, the industrial terminal in the workshop generates various business data. The system completes edge-side business identification through multi-source sensing and collection. Then, it determines the business type. If it belongs to time-sensitive business such as control sensing synchronization, a 120kHz high SCS resource pool is allocated. If it belongs to non-critical business such as ordinary monitoring and logging, a 30kHz regular resource pool is allocated to complete the dynamic subcarrier interval differentiation allocation.

[0168] After subcarrier resource allocation is completed, dynamic TDD time window and MAC layer scheduling are executed. The uplink and downlink time slot ratio is adjusted in real time based on uplink and downlink queue load, latency budget, and service jitter to match the resource requirements of the service direction. Then, the service level is determined a second time. For ultra-low latency critical services, the IP is captured by virtual network card, the target terminal UE is located, and a lightweight PHY direct transmission header is encapsulated and sent via the variable layer direct transmission link. For ordinary services, the PDCP / RLC / MAC four-layer protocol encapsulation is fully executed and sent through the standard PHY channel.

[0169] Both types of data are uniformly transmitted via the RU (Radio Unit) over the air interface. Upon arrival at the UE (User Equipment), the physical layer demodulates the data and distinguishes the frame type. If the frame is identified as a direct transmission frame, the PHY header is stripped and forwarded to the upper layer. For ordinary standard frames, the protocol is parsed layer by layer before being handed over to the application terminal. Finally, the upper layer completes the closed-loop service processing of perception, decision-making, and control, and this round of scheduling and transmission process ends.

[0170] The unlimited resource scheduling method in this application embodiment connects three core optimization mechanisms: dynamic subcarrier spacing allocation, dynamic TDD time slot allocation, and physical layer variable direct transmission. It quantifies and coordinates time slot length and uplink / downlink scheduling opportunities, reducing service time slot waiting, directional queuing, and multi-layer protocol processing latency without consuming additional spectrum bandwidth, while being compatible with the parallel operation of traditional 5G standard services.

[0171] This application reduces basic waiting latency by dynamically increasing the subcarrier spacing corresponding to critical services, reduces directional waiting and queuing latency by dynamically adjusting the uplink and downlink time slot ratio, and further reduces protocol processing latency through subsequent variable layer transmission mechanisms. Therefore, it can more effectively compress the closed-loop communication latency of critical services as a whole.

[0172] The various methods of the embodiments of this application have been described above. Apparatus for implementing the above methods will now be provided.

[0173] like Figure 6 As shown in the illustration, this application also provides a wireless resource scheduling device 500, applied to a first network device, comprising:

[0174] The receiving module 601 is used to receive sensing data corresponding to at least one service sent by the second network device; the sensing data includes at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data;

[0175] The allocation module 602 is used to allocate a target subcarrier interval for the first service and / or allocate a target time slot ratio for the second service based on the sensing data.

[0176] The wireless resource scheduling device in this application distinguishes services based on received sensing data including at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data. It allocates different subcarrier intervals and / or different time slot ratios to different services. This allows for the allocation of higher subcarrier intervals to critical services with high latency levels and the adjustment of time slot ratios based on service direction, enabling finer-grained resource scheduling for different services and improving the real-time performance of service data transmission.

[0177] Another embodiment of the network device in this application, such as Figure 7 As shown, it includes a transceiver 710, a processor 700, a memory 720, and a program or instructions stored in the memory 720 and executable on the processor 700; when the processor 700 executes the program or instructions, it implements the various processes of the above-described wireless resource scheduling method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0178] The transceiver 710 is used to receive and send data under the control of the processor 700.

[0179] Among them, Figure 7 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 700) and memory (memory 720). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 710 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 700 during operation.

[0180] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described wireless resource scheduling method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0181] This application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes of the above-described wireless resource scheduling method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0182] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0183] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of 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 this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The 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 (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0184] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A wireless resource scheduling method, applied to a first network device, characterized in that, include: Receive sensing data corresponding to at least one service sent by a second network device; the sensing data includes at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data; Based on the perceived data, a target subcarrier spacing is allocated for the first service, and / or a target time slot allocation is allocated for the second service.

2. The method according to claim 1, characterized in that, Based on the perceived data, a target subcarrier interval is allocated to the first service map, including: If the first service is a first service type, a first subcarrier interval is allocated to the first service; If the first service is a second service type, a second subcarrier interval is allocated to the first service; The service type is determined based on the service direction, service priority, service stage, and latency level; the first subcarrier interval is greater than the second subcarrier interval.

3. The method according to claim 2, characterized in that, The latency data includes at least one of the following: Transmission delay, air interface waiting delay, direction waiting delay, queuing waiting delay, edge processing delay, and protocol processing delay.

4. The method according to claim 1, characterized in that, Based on the perceived data, a target time slot allocation is assigned to the second service, including: Based on the perceived data, first data is determined; the first data includes at least one of the following: the length of the uplink service queue, the length of the downlink service queue, the remaining latency budget, and the historical latency jitter; Based on the first data and the stage to which the service belongs, the target time slot allocation is assigned to the service.

5. The method according to claim 4, characterized in that, Based on the first data and the stage to which the service belongs, the target time slot allocation is assigned to the service, including: When the length of the uplink service queue is greater than the length of the downlink service queue, and the service belongs to a stage where uplink data is concentrated, a first time slot allocation is assigned to the service. When the length of the uplink service queue is less than the length of the downlink service queue, and the service belongs to a downlink data concentration phase, a second time slot allocation is assigned to the service. In this case, the uplink time slot ratio of the first time slot allocation is higher than the uplink time slot ratio of the second time slot allocation.

6. The method according to claim 2, characterized in that, The method further includes: The third service is determined based on the perceived data; the third service is a service with a latency level higher than a preset level. The service data of the third service is sent to the target terminal via a direct transmission link; The direct transmission link is a transmission link established between the distributed unit of the first network device and the terminal through a virtual network card interface.

7. The method according to claim 6, characterized in that, Sending the service data of the third service to the target terminal via a direct transmission link includes: Identify the target IP address in the business data; The target terminal is determined based on the target IP and the mapping data; the mapping data is the correspondence between the terminal and the physical layer terminal identifier pre-stored in the first network device. The data header of the business data for the first business type is encapsulated; the data header includes: the identifier of the target terminal, the data length, the serial number, and the data type; The encapsulated business data is sent to the target terminal via a direct transmission link; The first network device and the terminal are configured with corresponding IP addresses.

8. A wireless resource scheduling device, applied to a first network device, characterized in that, include: The receiving module is used to receive sensing data corresponding to at least one service sent by the second network device; the sensing data includes at least one of the following: service direction, service priority, service stage, latency level, latency data, data length, and historical data; The allocation module is used to allocate a target subcarrier interval for the first service and / or allocate a target time slot ratio for the second service based on the sensed data.

9. A network device, characterized in that, include: Transceiver, processor, memory, and programs or instructions stored in the memory and executable on the processor; When the processor executes the program or instructions, it implements the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 7.

Images