Resource scheduling method, system, device and storage medium

Abstract

The application discloses a resource scheduling method, system, device and storage medium, wherein the method comprises the following steps: reporting a terminal side time delay jitter parameter; receiving uplink resources allocated by a network side; and transmitting uplink data according to the uplink resources. Therefore, the allocation of the uplink resources is performed according to the terminal side time delay jitter parameter, the uplink resources are accurately scheduled, and the deterministic transmission of the uplink data is ensured.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a resource scheduling method, system, device and storage medium. Background Technology

[0002] Typically, mobile communication networks use uplink shared resources for communication. The network side allocates uplink resources to the terminal side, and the terminal side sends and transmits data based on these uplink resources. When uplink data arrives in the buffer at the terminal side, it is sent immediately if there are uplink resources available to accommodate the data transmission. If there are no uplink resources, the terminal side requests uplink resource scheduling to send the data in the buffer as quickly as possible.

[0003] In related technologies, when uplink data is scheduled for uplink resources on the terminal side, the arrival time of uplink data may be inaccurate due to terminal-side latency jitter. For example, after the mobile network is integrated with the Internet, the latency between the converter and the user terminal may cause the network side to estimate the arrival time of uplink data inaccurately, which will prevent real-time scheduling and affect the real-time performance of data transmission. Summary of the Invention

[0004] This application provides a resource scheduling method, system, device, and storage medium to solve the technical problem of uplink resource scheduling latency mentioned in the background art.

[0005] According to a first aspect of this application, a resource scheduling method is provided, applied to a terminal side, the method comprising: reporting terminal-side latency jitter parameters; receiving uplink resources allocated by the network side; and transmitting uplink data according to the uplink resources.

[0006] Optionally, the terminal-side latency jitter parameter is used to indicate: the latency jitter between the node connected to the TSN and the 5G system and DS-TT; or, the latency jitter between DS-TT and the terminal; or, the sum of the latency jitter between the node connected to the TSN and the 5G system and DS-TT and the latency jitter between DS-TT and the terminal.

[0007] Optionally, the terminal-side latency jitter parameters include the following parameters: terminal-side latency jitter range; or, terminal-side latency jitter upper limit; or, terminal-side latency jitter average value; or, terminal-side latency jitter average value and upper limit value.

[0008] Optionally, the reporting of terminal-side latency jitter parameters can be achieved by sending terminal auxiliary information RRC signaling containing terminal-side latency jitter parameters; or sending RRC signaling containing only terminal-side latency jitter parameters; or sending MAC layer control commands containing terminal-side latency jitter parameters.

[0009] Optionally, before reporting the terminal-side latency jitter parameters, the method further includes: receiving a terminal-side latency jitter reporting request sent by the network side; and reporting the terminal-side latency jitter parameters to the network side according to the terminal-side latency jitter reporting request.

[0010] Optionally, the reporting of terminal-side latency jitter parameters includes: obtaining a threshold parameter for reporting terminal-side latency jitter; comparing the terminal-side latency jitter parameters with the threshold parameter; and reporting the terminal-side latency jitter parameters when the comparison result meets a preset condition.

[0011] Optionally, obtaining the threshold parameter for terminal-side latency jitter reporting includes: receiving the threshold parameter configured by the network side; or, obtaining the threshold parameter according to a preset value in the protocol.

[0012] Optionally, reporting the terminal-side latency jitter parameter when the comparison result meets the preset conditions includes: reporting the terminal-side latency jitter parameter when it is known from the comparison result that the terminal-side latency jitter parameter exceeds the threshold parameter.

[0013] Optionally, reporting the terminal-side latency jitter parameter when it is known from the comparison result that the terminal-side latency jitter parameter exceeds the threshold parameter includes: when the threshold parameter is the maximum latency jitter threshold, reporting the terminal-side latency jitter parameter when it is known from the comparison result that the maximum value of the terminal-side latency jitter exceeds the maximum jitter threshold.

[0014] Optionally, the step of reporting the terminal-side latency jitter parameter when it is known from the comparison result that the terminal-side latency jitter parameter exceeds the threshold parameter includes: when the threshold parameter is a latency jitter change threshold, reporting the terminal-side latency jitter parameter when it is known from the comparison result that the change value of the terminal-side latency jitter parameter exceeds the latency jitter change threshold.

[0015] Optionally, the change value of the terminal-side latency jitter parameter includes: the average change value of terminal-side latency jitter configured according to a preset protocol, or the maximum change value of terminal-side latency jitter, or the minimum change value of terminal-side latency jitter.

[0016] Optionally, the reporting of terminal-side latency jitter parameters includes: obtaining a trigger time limit; starting a timer after the last reporting of terminal-side latency jitter parameters; and reporting terminal-side latency jitter parameters when the timer's duration reaches or exceeds the trigger time limit.

[0017] Optionally, the reporting of terminal-side latency jitter parameters includes: reporting terminal-side latency jitter parameters when a preset reporting trigger event is detected in the current scenario.

[0018] Optionally, the step of detecting that the current scenario meets the preset reporting trigger event includes: detecting that the terminal device enters the connected state from the idle state or the disconnected state; or detecting that the terminal device undergoes cell handover; or detecting that the terminal TSN clock changes.

[0019] According to a second aspect of this application, a resource scheduling method is provided, applied to the network side, the method comprising: receiving terminal-side latency jitter parameters reported by the terminal side; allocating uplink resources to the terminal side according to the terminal-side latency jitter parameters; and receiving uplink data sent by the terminal side according to the uplink resources.

[0020] Optionally, before the terminal-side delay jitter parameters reported by the receiving terminal, the following is included:

[0021] Send a terminal-side latency jitter reporting request to the terminal side.

[0022] Optionally, sending a terminal-side latency jitter reporting request to the terminal side includes: triggering the sending of a terminal-side latency jitter reporting request to the terminal side when the current scenario is detected to meet preset service conditions.

[0023] Optionally, allocating uplink resources to the terminal side based on the terminal-side latency jitter parameters includes: obtaining the service data transmission characteristics of the terminal side; and allocating uplink resources to the terminal side based on the terminal-side latency jitter parameters and the service data transmission characteristics.

[0024] Optionally, allocating uplink resources to the terminal side based on the terminal-side latency jitter parameters includes: configuring multiple sets of uplink resources for the terminal side based on the terminal-side latency jitter parameters.

[0025] According to a third aspect of this application, a resource scheduling device is provided, applied to a terminal side. The device includes: a reporting module for reporting terminal-side latency jitter parameters; a first receiving module for receiving uplink resources allocated by the network side; and a transmission module for transmitting uplink data according to the uplink resources.

[0026] Optionally, the reported terminal-side latency jitter parameter is used to indicate: the latency jitter between the node connected to the TSN and the 5G system and DS-TT; or, the latency jitter between DS-TT and the terminal; or, the sum of the latency jitter between the node connected to the TSN and the 5G system and DS-TT and the latency jitter between DS-TT and the terminal.

[0027] Optionally, the terminal-side latency jitter parameters include the following parameters: terminal-side latency jitter range; or, terminal-side latency jitter upper limit; or, terminal-side latency jitter average value; or, terminal-side latency jitter average value and upper limit value.

[0028] Optionally, the reporting module sends the terminal-side latency jitter parameters using the following methods: sending terminal auxiliary information RRC signaling containing the terminal-side latency jitter parameters; or sending RRC signaling containing only the terminal-side latency jitter parameters; or sending MAC layer control commands containing the terminal-side latency jitter parameters.

[0029] Optionally, it further includes: a second receiving module, configured to receive a terminal-side latency jitter reporting request sent by the network side; the reporting module is further configured to report terminal-side latency jitter parameters to the network side according to the terminal-side latency jitter reporting request.

[0030] Optionally, the reporting module is specifically used to: obtain a threshold parameter for terminal-side latency jitter reporting; compare the terminal-side latency jitter parameter with the threshold parameter; and report the terminal-side latency jitter parameter when the comparison result meets a preset condition.

[0031] Optionally, the reporting module is specifically used to: receive the threshold parameters configured by the network side; or, obtain the threshold parameters according to a preset value in the protocol.

[0032] Optionally, the reporting module is specifically used to: report the terminal-side latency jitter parameter when it is known from the comparison result that the terminal-side latency jitter parameter exceeds the threshold parameter.

[0033] Optionally, the reporting module is specifically used to: when the threshold parameter is the maximum threshold of latency jitter, and when it is known from the comparison result that the maximum value of latency jitter on the terminal side exceeds the maximum jitter threshold, report the latency jitter parameter on the terminal side.

[0034] Optionally, the reporting module is specifically used to: when the threshold parameter is a latency jitter change threshold, and when it is known from the comparison result that the change value of the latency jitter parameter on the terminal side exceeds the latency jitter change threshold, report the latency jitter parameter on the terminal side.

[0035] Optionally, the change value of the terminal-side latency jitter parameter includes: the average change value of terminal-side latency jitter configured according to a preset protocol, or the maximum change value of terminal-side latency jitter, or the minimum change value of terminal-side latency jitter.

[0036] Optionally, the reporting module is specifically used to: obtain the trigger time limit; start a timer after the last reporting of terminal-side latency jitter parameters; and report the terminal-side latency jitter parameters when the timer's timing reaches or exceeds the trigger time limit.

[0037] Optionally, the reporting module is specifically used to: report terminal-side latency jitter parameters when a preset reporting trigger event is detected in the current scenario.

[0038] Optionally, the reporting module is specifically used to: detect when the terminal device enters the connected state from the idle state or the disconnected state; or, detect when the terminal device undergoes cell handover; or, detect when the terminal TSN clock changes.

[0039] According to a fourth aspect of this application, a resource scheduling apparatus is provided, applied on the network side. The apparatus includes: a third receiving module for receiving terminal-side latency jitter parameters reported by the terminal side; a configuration module for allocating uplink resources to the terminal side according to the terminal-side latency jitter parameters; and a fourth receiving module for receiving uplink data sent by the terminal side according to the uplink resources.

[0040] Optionally, it further includes: a sending module, configured to send a terminal-side latency jitter reporting request to the terminal side before the terminal-side latency jitter parameters reported by the receiving terminal side.

[0041] Optionally, the sending module is specifically used to: trigger the sending of a terminal-side latency jitter reporting request to the terminal side when the current scenario is detected to meet preset business conditions.

[0042] Optionally, the configuration module is specifically used to: obtain the service data transmission characteristics of the terminal side; and allocate uplink resources to the terminal side according to the terminal side latency jitter parameters and the service data transmission characteristics.

[0043] Optionally, the configuration module is specifically used to: configure multiple sets of uplink resources for the terminal side according to the terminal-side latency jitter parameters.

[0044] According to a fifth aspect of this application, a resource scheduling system is provided, comprising: a terminal side, including the resource scheduling device as described in the third aspect above; and a network side, including the resource scheduling device as described in the fourth aspect above.

[0045] According to a sixth aspect of this application, a processor-readable storage medium is provided, the processor-readable storage medium storing a computer program for causing the processor to perform the method described in the first aspect above, or the method described in the second aspect above.

[0046] This application has at least the following technical effects:

[0047] During uplink data transmission, the terminal side reports the terminal-side latency jitter parameters, and the network side performs precise uplink resource scheduling based on the experimental jitter parameters, thus meeting the real-time requirements of uplink data transmission.

[0048] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0049] The accompanying drawings are provided for a better understanding of this solution and do not constitute a limitation of this application. Wherein:

[0050] Figure 1 This is a schematic diagram of the system architecture for the integration of 5G network and industrial internet according to the first embodiment of this application;

[0051] Figure 2 This is a schematic diagram of the structure of a resource scheduling system according to the second embodiment of this application;

[0052] Figure 3 This is a flowchart illustrating a resource scheduling method according to a third embodiment of this application;

[0053] Figure 4(a) is a schematic diagram of resource scheduling according to the fourth embodiment of this application;

[0054] Figure 4(b) is a schematic flowchart of a resource scheduling method according to the fifth embodiment of this application;

[0055] Figure 5 This is a schematic diagram of a resource scheduling process according to the sixth embodiment of this application;

[0056] Figure 6 This is a schematic flowchart of a resource scheduling method according to the seventh embodiment of this application;

[0057] Figure 7 This is a schematic diagram of the resource scheduling method according to the eighth embodiment of this application;

[0058] Figure 8 This is a schematic diagram of the structure of a resource scheduling device according to the ninth embodiment of this application;

[0059] Figure 9 This is a schematic diagram of the structure of a resource scheduling device according to the tenth embodiment of this application;

[0060] Figure 10 This is a schematic diagram of the structure of a resource scheduling device according to the eleventh embodiment of this application;

[0061] Figure 11 This is a schematic diagram of the structure of a resource scheduling device according to the twelfth embodiment of this application. Detailed Implementation

[0062] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0063] In this application's embodiments, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0064] In this embodiment of the invention, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0065] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0066] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0067] It should be noted that the network connection channel establishment method described above, which focuses on the core network equipment side, is also applicable to the core network equipment in the embodiments of this application. Its implementation principle and technical effect are the same, and will not be repeated here.

[0068] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0069] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0070] The technical solutions provided in this application can be applied to various systems, especially 5G systems. These various systems all include terminal devices and network devices.

[0071] The terminal device involved in the embodiments of this application may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The name of the terminal device may differ in different systems; for example, in a 5G system, the terminal device may be called User Equipment (UE). The network device involved in the embodiments of this application may be a base station, which may include multiple cells providing services to the terminal. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network devices involved in the embodiments of this application may be evolved network devices (eNBs or e-NodeBs) in long term evolution (LTE) systems, 5G base stations (gNBs) in 5G network architectures (next generation systems), relay nodes, or IAB donors or IAB nodes in IAB architectures; however, this application embodiment is not limited to any particular type. In some network structures, network devices may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may also be geographically separated.

[0072] As mentioned in the background section, there is a latency jitter issue when transmitting uplink data on the terminal side. Both 4G and 5G systems employ uplink shared resources, where the network allocates specific uplink resources to the terminal. These uplink resources can include time-frequency resources and transmission formats. The terminal then transmits uplink data using these allocated resources. When uplink data arrives in the buffer on the terminal side, it is immediately transmitted if there are sufficient uplink resources to accommodate the data transmission. If no uplink resources are available, the terminal requests uplink resource scheduling to expedite the transmission of the buffered data.

[0073] This process also applies to point-to-point transmission scenarios between terminals, such as vehicle-to-everything (V2X) information exchange. That is, when data arrives at the terminal cache, the terminal sends the cached data on the nearest available transmission resource. If there is no available resource, the terminal can also request resource scheduling to send the cached data.

[0074] Network-side resource allocation methods include dynamic scheduling and continuous resource allocation (Configured Grant, CG). Continuous resource allocation is the most effective means to meet the latency requirements of business data transmission. The network side can configure continuous scheduling resources for the terminal side according to the arrival cycle and arrival time of business data, so as to realize that business data can be transmitted as soon as it arrives, minimizing air interface latency.

[0075] In related technologies, interconnecting mobile networks with the Industrial Internet has become mainstream. The Industrial Internet employs a Time Synchronization Network (TSN). As a typical deterministic network, the Industrial Internet has precise control over the arrival and transmission of service data, thus enabling accurate resource allocation and transmission. 5G systems integrate this technology using a bridge approach within the Time-Sensitive Networking (TSN) framework of the IEEE protocol. The system architecture is referenced... Figure 1 Since the 5G system synchronizes internally via the 5G clock and the TSN network synchronizes via the TSN network clock, the node for clock conversion between the 5G system and the TSN is the terminal-side TSN converter (DS-TT) on the terminal side and the network-side TSN converter (NW-TT) on the network side. During the time conversion process, latency jitter may be introduced between the external network and 5G.

[0076] Among them, continue to refer to Figure 1 In that Figure 1 In the system architecture shown, the latency jitter may include latency jitter between the TSN bridge and DS-TT, and latency jitter between DS-TT and UE. This latency jitter is called terminal-side latency jitter, which causes uplink data transmission delay or downlink data reception delay at the TSN network.

[0077] To address the data transmission latency issue, this application proposes a method for the terminal to report its latency jitter parameters to the network side, enabling the network side to schedule uplink resources based on these latency jitter parameters.

[0078] like Figure 2As shown in the embodiments of this application, the resource scheduling system involved includes a terminal side 1000 and a network side 2000. To facilitate the explanation of the resource scheduling method in these embodiments, the following description focuses on the terminal side. The terminal side can be understood as the terminal device mentioned above, and will not be elaborated further here.

[0079] Specifically, such as Figure 3 As shown, the resource scheduling method applied to the terminal side 1000 includes:

[0080] Step 101: Report the terminal-side latency jitter parameters.

[0081] It is understandable that the latency jitter parameter is a parameter that may cause delays during uplink data transmission on the terminal side, as referenced... Figure 1 This latency jitter parameter can be used to indicate the latency jitter between the node connected to the TSN and the 5G system and the DS-TT; or, the latency jitter between the DS-TT and the terminal; or, the sum of the latency jitter between the node connected to the TSN and the 5G system and the latency jitter between the DS-TT and the terminal. The nodes connected to the 5G system include TSN bridges, etc. The specific latency jitter parameters—whether between the node connected to the TSN and the 5G system and the DS-TT, or between the DS-TT and the terminal—depend on whether the connection objects are compatible. If compatible, the corresponding latency jitter is 0.

[0082] In some possible embodiments, the latency jitter parameter on the terminal side is estimated. Therefore, in order to ensure the availability of the latency jitter parameter, the latency jitter parameter on the terminal side may include a latency jitter range on the terminal side, that is, the latency jitter parameter is a range including the minimum latency and the maximum latency, rather than being displayed at a specific point. Alternatively, the latency jitter parameter may be the upper limit of the jitter latency on the terminal side, that is, the maximum latency, in which case the minimum latency is 0 by default. Or, the latency jitter parameter on the terminal side may be the average latency jitter value on the terminal side.

[0083] In this embodiment, when the terminal-side latency jitter parameter is the terminal-side latency jitter average, it can be calculated by taking the average of the latency jitter parameters of multiple periods under the historical period of the terminal side.

[0084] Furthermore, after obtaining the terminal-side latency jitter parameters, the terminal-side latency jitter parameters are sent to the corresponding network side.

[0085] It should be noted that the method of reporting terminal-side latency jitter parameters may differ in different application scenarios. In some possible embodiments, terminal auxiliary information RRC signaling containing terminal-side latency jitter parameters is sent.

[0086] In some other possible embodiments, RRC signaling containing only terminal-side delay jitter parameters is transmitted.

[0087] In some other possible embodiments, a MAC layer control command containing terminal-side latency jitter parameters is sent.

[0088] Of course, in actual implementation, the terminal side can report the terminal side latency jitter parameters proactively or in response to the reporting request from the network side.

[0089] In one embodiment of this application, as shown in Figure 4(a), a terminal-side latency jitter reporting request is received from the network side. This latency jitter reporting request can be a pre-agreed code or signaling, etc., and the terminal-side latency jitter parameters are reported to the network side according to the terminal-side latency jitter reporting request. The network side can send the terminal-side latency jitter reporting request during service establishment, reconstruction, or update, or it can be set based on the application needs of the network side, such as triggering the sending of the terminal-side latency jitter reporting request after a certain period of time, or after the accumulated received and transmitted uplink data reaches a certain data volume within a certain period of time.

[0090] In another embodiment of this application, the terminal-side latency jitter parameters can be actively reported according to a preset period. Specifically, a trigger time limit is obtained, which can be understood as the duration of the aforementioned period. Then, a timer is started after the last reporting of the terminal-side latency jitter parameters. When the timer's countdown reaches or exceeds the trigger time limit, the terminal-side latency jitter parameters are reported.

[0091] In another embodiment of this application, as shown in FIG4(b), a trigger event for reporting terminal-side latency jitter parameters can be preset, so that when the current scenario is detected to meet the preset reporting trigger event, the terminal-side latency jitter parameters are reported.

[0092] In this embodiment, if the terminal device is detected to enter a connected state from an idle or disconnected state, it is considered that the terminal device has an uplink data transmission request, and thus, the terminal is considered to have entered a trigger event state. Alternatively, if the terminal device is detected to be in a cell handover situation, it is considered that the uplink environment of the terminal has changed, which may cause latency jitter, and therefore, the terminal is considered to have entered a trigger event state. Or, if a change in the terminal's TSN clock is detected, the changed TSN clock may be inconsistent with the clock in the mobile network, which may cause latency jitter, and therefore, the terminal is considered to have entered a trigger event state.

[0093] Step 102: Receive uplink resources allocated by the network side.

[0094] Step 103: Transmit uplink data according to uplink resources.

[0095] In this embodiment, after reporting the terminal-side latency jitter parameters, the network side receives uplink resources scheduled in real time based on the terminal-side latency jitter parameters, and then sends uplink data based on the uplink resources, ensuring the real-time uplink data upload.

[0096] Therefore, the resource scheduling method in this embodiment schedules uplink resources based on the terminal-side latency jitter parameters, avoiding uplink latency on the terminal side and ensuring deterministic transmission of uplink data.

[0097] Based on the above embodiments, the process of the terminal side reporting terminal-side latency jitter parameters can differ in different application scenarios, as shown in the following examples:

[0098] In some possible examples, such as Figure 5 As shown, a threshold parameter for terminal-side latency jitter reporting is obtained. This threshold parameter can be a time threshold since the last reported latency jitter parameter, a maximum threshold for the latency jitter parameter, or a threshold for the change in latency jitter parameter relative to the last reported latency jitter parameter. Then, the terminal-side latency jitter parameter is compared with the threshold parameter. If the comparison result meets preset conditions, the terminal-side latency jitter parameter is reported. The reported threshold parameter can be obtained from a preset value in the protocol, or it can be received from a threshold parameter configured on the network side, i.e., the threshold parameter is configured on the network side.

[0099] In some possible examples, when it is determined from the comparison results that the terminal-side latency jitter parameter exceeds the threshold parameter, the terminal-side latency jitter parameter is reported.

[0100] For example, if the threshold parameter is the terminal-side latency jitter change value, when the change of the terminal-side latency jitter mean, maximum or minimum value (whichever is used can be selected according to the scenario needs or preset) exceeds the threshold value, the terminal-side latency jitter parameter is reported.

[0101] For example, if the threshold parameter is the time since the last time the terminal reported the terminal-side delay jitter, the terminal starts timer T1 when reporting the delay jitter parameter. After T1 reaches or exceeds the threshold parameter, the terminal-side delay jitter parameter is triggered to be reported. If the terminal-side delay jitter parameter is triggered to be reported, the terminal-side delay jitter parameter is reported to the base station.

[0102] In some possible embodiments, when the comparison results show that the terminal-side latency jitter parameter exceeds a threshold parameter a certain number of times, the terminal-side latency jitter parameter is reported when the number of times exceeds a preset threshold within a preset time period.

[0103] In some possible embodiments, when the threshold parameter is the maximum latency jitter threshold, if it is known from the comparison result that the maximum latency jitter value on the terminal side exceeds the maximum jitter threshold, the latency jitter parameter on the terminal side is reported.

[0104] In some possible embodiments, when the threshold parameter is a latency jitter change threshold, if the comparison result indicates that the change value of the terminal-side latency jitter parameter exceeds the latency jitter change threshold, the terminal-side latency jitter parameter is reported. In this embodiment, the change value of the terminal-side latency jitter parameter includes:

[0105] According to the preset protocol settings, or the average change value of terminal-side latency jitter configured on the network side, or the maximum change value of terminal-side latency jitter, or the minimum change value of terminal-side latency jitter.

[0106] Therefore, the resource scheduling method of this application embodiment allows the terminal side to flexibly report terminal-side latency jitter parameters, ensuring that terminal-side latency jitter parameters are reported in various scenarios where uplink data transmission latency may occur. This facilitates timely real-time scheduling of uplink resources by the network side, ensuring the real-time transmission of uplink data.

[0107] The resource scheduling method of this application embodiment will now be described in detail below, focusing on the network side. In this application embodiment, the network side can be understood as the network device mentioned above, such as an access network node that allocates transmission resources, or a scheduling terminal, etc., which will not be elaborated further here.

[0108] Figure 6 This is a flowchart of a resource scheduling method according to another embodiment of this application, such as... Figure 6 As shown, the resource scheduling method includes:

[0109] Step 201: Receive the terminal-side latency jitter parameters reported by the terminal side.

[0110] Terminal-side latency jitter parameters can be actively reported by the terminal or requested by the network. In one embodiment of this application, before receiving the terminal latency jitter parameters reported by the terminal, the network sends a terminal-side latency jitter reporting request to the terminal device. For example, when the current scenario is detected to meet preset service conditions, the network triggers the sending of a terminal-side latency jitter reporting request to the terminal. These service conditions can be triggered when the service is established, rebuilt, or updated, or they can be set based on the application needs of the network side, such as after a certain period of time, or after the accumulated received and transmitted uplink data reaches a certain amount of data transmission within a certain period of time, the network triggers the sending of a terminal-side latency jitter reporting request.

[0111] The method for reporting terminal-side latency jitter parameters can be referred to in the above embodiments, and will not be repeated here.

[0112] Step 202: Allocate uplink resources to the terminal side based on the terminal-side latency jitter parameters.

[0113] Among them, uplink resources are allocated to the terminal side based on the terminal-side latency jitter parameters. These uplink resources include network transmission resources, data transmission formats, etc.

[0114] In one embodiment of this application, a deep learning model can be pre-built. The input of the deep learning model is the terminal-side latency jitter parameter, and the output is uplink resources. Thus, the terminal-side latency jitter parameter can be input into the deep learning model to obtain the corresponding uplink resources.

[0115] Of course, in actual implementation, uplink resources may be related not only to the terminal-side latency jitter parameters but also to the transmission characteristics of the service data. These transmission characteristics can include the transmission speed and transmission method of the service data. Therefore, in one embodiment of this application, the service data transmission characteristics of the terminal side are obtained, and then uplink resources are configured for the terminal side based on the terminal-side latency jitter parameters and the service data transmission characteristics. For example, a first normalized value of the terminal-side latency jitter parameters and a second normalized value of the service data transmission characteristics are determined. Based on a preset correspondence between the normalized values ​​of the terminal-side latency jitter parameters and uplink resources, a first uplink resource corresponding to the first normalized value is determined. Based on a preset correspondence between the normalized values ​​of the service data transmission characteristics and uplink resources, a second uplink resource corresponding to the second normalized value is determined. The uplink resources of the terminal side are determined based on the sum of the first and second uplink resources.

[0116] For example, a deep learning model can be pre-learned. The input of this deep learning model is the terminal-side latency jitter parameters and service data transmission characteristics. The terminal-side latency jitter parameters and service data transmission characteristics are then input into the deep learning model to obtain the uplink resources output by the deep learning model.

[0117] Step 203: Receive uplink data sent by the receiving terminal based on uplink resources.

[0118] In this embodiment, the receiving terminal sends uplink data based on uplink resources. Since the uplink resources are scheduled according to the uplink jitter parameters of the terminal, the uplink data can be transmitted deterministically.

[0119] It is easy to understand that uplink resources are actually estimated based on uplink jitter parameters on the terminal side. Therefore, if there is still a delay between the uplink resources and the upload time of the uplink data on the terminal side, it will still cause uplink data transmission delay. Therefore, in one embodiment of this application, in order to avoid the delay problem, multiple sets of uplink resources can be configured for the terminal side according to the terminal side latency jitter parameters. That is, a relatively large range of uplink resources is configured according to the terminal side latency jitter parameters to ensure that the transmission of uplink data can match the corresponding uplink resources. Here, multiple sets of uplink resources can be understood as a relatively wide time range for providing uplink resources.

[0120] For example, such as Figure 7 As shown, when there are three or more uplink resources, deterministic transmission of uplink data can be achieved regardless of whether the uplink resource falls within the resource range corresponding to uplink resource 1 (CG1 in the figure), uplink resource 2 (CG2 in the figure), or uplink resource 3 (CG3 in the figure), ensuring the real-time transmission of uplink data. Figure 7 In this context, T represents the business cycle corresponding to the uplink data. T can be milliseconds or subframes, etc., and the arrival time offset is ΔT (which can be expressed as how many milliseconds or subframes the offset is relative to the start of each cycle).

[0121] Therefore, the resource scheduling method in this application embodiment schedules uplink resources on the base station side according to the latency jitter parameters on the terminal side, ensuring the real-time transmission of uplink data.

[0122] To implement the above embodiments, this application also proposes a resource scheduling device applied to the terminal side, such as... Figure 8 As shown, the resource scheduling device includes: a reporting module 1100, a first receiving module 200, and a transmission module 1300, wherein,

[0123] The reporting module 1100 is used to report terminal-side latency jitter parameters;

[0124] The first receiving module 1200 is used to receive uplink resources allocated by the network side;

[0125] The transmission module 1300 is used to transmit uplink data according to uplink resources.

[0126] In one embodiment of this application, the reported terminal-side latency jitter parameter is used to indicate:

[0127] The latency jitter between the TSN and the node connecting to the 5G system and DS-TT; or...

[0128] The latency jitter between DS-TT and the terminal; or...

[0129] The sum of latency jitter between the TSN and the 5G system's node and DS-TT, and latency jitter between DS-TT and the terminal.

[0130] In one embodiment of this application, the terminal-side latency jitter parameter includes the following parameters:

[0131] Terminal-side latency jitter range; or,

[0132] Terminal-side latency jitter limit; or,

[0133] Average latency jitter on the terminal side; or

[0134] Average and upper limit of terminal-side latency jitter.

[0135] In one embodiment of this application, the reporting module 1100 transmits the terminal-side latency jitter parameters using the following transmission method:

[0136] Send terminal assistance information RRC signaling containing terminal-side latency jitter parameters; or,

[0137] Send RRC signaling containing only terminal-side delay jitter parameters; or,

[0138] Send MAC layer control commands containing terminal-side latency jitter parameters.

[0139] In one embodiment of this application, such as Figure 9 As shown, in Figure 8 Based on the above, the resource scheduling device further includes: a second receiving module 1400, wherein,

[0140] In this embodiment, the second receiving module 1400 is used to receive a terminal-side latency jitter reporting request sent by the network side;

[0141] In this embodiment, the reporting module 1100 is also used to report the terminal-side latency jitter parameters to the network side according to the terminal-side latency jitter reporting request.

[0142] In one embodiment of this application, the reporting module 1100 is specifically used for:

[0143] Obtain the threshold parameters for terminal-side latency jitter reporting;

[0144] The terminal-side latency jitter parameter is compared with the threshold parameter, and the terminal-side latency jitter parameter is reported when the comparison result meets the preset conditions.

[0145] In this embodiment, the reporting module 1100 is specifically used for:

[0146] Receive threshold parameters configured on the network side; or,

[0147] The threshold parameters are obtained according to the preset values ​​in the protocol.

[0148] In this embodiment, the reporting module 1100 is specifically used for:

[0149] When it is determined from the comparison results that the terminal-side latency jitter parameter exceeds the threshold parameter, the terminal-side latency jitter parameter is reported.

[0150] In this embodiment, the reporting module 1100 is specifically used for:

[0151] When the threshold parameter is the maximum threshold for latency jitter, if the comparison result shows that the maximum value of latency jitter on the terminal side exceeds the maximum threshold for jitter, the latency jitter parameter on the terminal side is reported.

[0152] In this embodiment, the reporting module 1100 is specifically used for:

[0153] When the threshold parameter is the latency jitter change threshold, if the change value of the latency jitter parameter on the terminal side exceeds the latency jitter change threshold based on the comparison result, the latency jitter parameter on the terminal side is reported.

[0154] In this embodiment, the change values ​​of the terminal-side latency jitter parameter include:

[0155] According to the preset protocol settings, or the average change value of terminal-side latency jitter configured on the network side, or the maximum change value of terminal-side latency jitter, or the minimum change value of terminal-side latency jitter.

[0156] In this embodiment, the reporting module 1100 is specifically used for:

[0157] Get the trigger time limit;

[0158] After the last reporting of terminal-side latency jitter parameters, a timer is started. When the timer's countdown time reaches or exceeds the trigger time limit, the terminal-side latency jitter parameters are reported.

[0159] In this embodiment, the reporting module 1100 is specifically used for:

[0160] When a preset reporting trigger event is detected, the terminal-side latency jitter parameters are reported.

[0161] In this embodiment, the reporting module 1100 is specifically used for:

[0162] When the terminal device is detected to have transitioned from an idle or disconnected state to a connected state; or,

[0163] When a cell handover is detected on the terminal-side device; or,

[0164] If a change in the TSN clock on the terminal side is detected.

[0165] It should be noted that the resource scheduling device centralized on the terminal side provided in this embodiment of the invention can realize all the method steps centralized on the terminal side implemented in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0166] To implement the above embodiments, this application also proposes a resource scheduling device applied on the network side. Figure 10 This is a schematic diagram of the structure of a resource scheduling device according to an embodiment of this application, as shown below. Figure 10 As shown, the resource scheduling device includes: a third receiving module 2100, a configuration module 2200, and a fourth receiving module 2300, wherein...

[0167] The third receiving module 2100 is used to receive terminal-side delay jitter parameters reported by the terminal side;

[0168] Configuration module 2200 is used to allocate uplink resources to the terminal side based on the terminal side latency jitter parameters;

[0169] The fourth receiving module 2300 is used to receive uplink data sent by the terminal side according to uplink resources.

[0170] In one embodiment of this application, such as Figure 11 As shown, in Figure 10 Based on the above, the resource scheduling device further includes: a sending module 2400, wherein,

[0171] The sending module 2400 is used to send a terminal-side latency jitter reporting request to the terminal side before receiving the terminal-side latency jitter parameters reported by the terminal side.

[0172] In this embodiment, the sending module 2400 is specifically used for:

[0173] When the current scenario and other preset business conditions are met, a terminal latency jitter reporting request is triggered and sent to the terminal side.

[0174] In one embodiment of this application, the configuration module 2200 is specifically used for:

[0175] Obtain the business data transmission characteristics on the terminal side;

[0176] Uplink resources are allocated to the terminal side based on the terminal-side latency jitter parameters and service data transmission characteristics.

[0177] In one embodiment of this application, the configuration module 2200 is specifically used for:

[0178] Configure multiple sets of uplink resources on the terminal side based on the terminal-side latency jitter parameters.

[0179] It should be noted that the resource scheduling device centralized on the network side provided in this embodiment of the invention can implement all the method steps centralized on the network side implemented in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0180] This application also provides a processor-readable storage medium storing a computer program for causing a processor to execute the resource scheduling method described in this application. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0181] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0182] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0183] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0184] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0185] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A resource scheduling method applied to a terminal side, characterized in that, The method comprises: reporting a terminal-side delay jitter parameter; receiving an uplink resource allocated by a network side; transmitting uplink data according to the uplink resource; the terminal-side delay jitter parameter comprises: a terminal-side delay jitter interval; or a terminal-side delay jitter upper limit; or a terminal-side delay jitter average value; or a terminal-side delay jitter average value and an upper limit; the reporting of the terminal-side delay jitter parameter comprises: reporting the terminal-side delay jitter parameter when it is detected that a current scenario meets a preset reporting trigger event; the reporting of the terminal-side delay jitter parameter when it is detected that the current scenario meets the preset reporting trigger event comprises: when it is detected that a terminal-side device enters a connected state from an idle state or a non-connected state; or when it is detected that the terminal-side device performs cell switching; or when it is detected that a terminal-side TSN clock is changed.

2. The method of claim 1, wherein, the terminal-side delay jitter parameter is used to indicate: a delay jitter between a time synchronization network (TSN) and a node connected to a 5G system to a terminal-side TSN translator (DS-TT); or a delay jitter between the DS-TT and the terminal; or a sum of a delay jitter between the TSN and the node connected to the 5G system to the DS-TT and a delay jitter between the DS-TT and the terminal. the reporting of the terminal-side delay jitter parameter adopts the following sending mode:

3. The method of claim 1, wherein, sending terminal assistance information RRC signaling containing the terminal-side delay jitter parameter; or sending RRC signaling containing only the terminal-side delay jitter parameter; or sending a medium access control layer (MAC) layer control command containing the terminal-side delay jitter parameter. before the reporting of the terminal-side delay jitter parameter, the method further comprises:

4. The method of claim 1, wherein, receiving a terminal-side delay jitter reporting request sent by the network side; reporting the terminal-side delay jitter parameter to the network side according to the terminal-side delay jitter reporting request. the reporting of the terminal-side delay jitter parameter comprises:

5. The method of claim 1, wherein, obtaining a threshold parameter for terminal-side delay jitter reporting; comparing the terminal-side delay jitter parameter with the threshold parameter, and reporting the terminal-side delay jitter parameter when a comparison result meets a preset condition. the obtaining of the threshold parameter for terminal-side delay jitter reporting comprises:

6. The method of claim 5, wherein, receiving the threshold parameter configured by the network side; or obtaining the threshold parameter according to a protocol preset value. the reporting of the terminal-side delay jitter parameter when the comparison result meets the preset condition comprises:

7. The method of claim 6, wherein, reporting the terminal-side delay jitter parameter when it is learned from the comparison result that the terminal-side delay jitter parameter exceeds the threshold parameter. the reporting of the terminal-side delay jitter parameter when it is learned from the comparison result that the terminal-side delay jitter parameter exceeds the threshold parameter comprises:

8. The method of claim 7, wherein, when the threshold parameter is a delay jitter maximum threshold, reporting the terminal-side delay jitter parameter when it is learned from the comparison result that a terminal-side delay jitter maximum value exceeds the delay jitter maximum threshold. the reporting of the terminal-side delay jitter parameter when it is learned from the comparison result that the terminal-side delay jitter parameter exceeds the threshold parameter comprises:

9. The method of claim 8, wherein, ​ When the threshold parameter is a delay jitter variation threshold, the terminal-side delay jitter parameter is reported when it is learned according to the comparison result that the variation value of the terminal-side delay jitter parameter exceeds the delay jitter variation threshold.

10. The method of claim 9, wherein, The variation value of the terminal-side delay jitter parameter includes: According to a preset protocol setting, or a terminal-side delay jitter mean value variation value, or a terminal-side delay jitter maximum variation value, or a terminal-side delay jitter minimum variation value, configured by the network side.

11. The method of claim 1, wherein, The reported terminal-side delay jitter parameter includes: Obtaining a triggering time limit; Starting a timer after the last reported terminal-side delay jitter parameter, and reporting the terminal-side delay jitter parameter when the timing time of the timer reaches or exceeds the triggering time limit. 12.A resource scheduling method applied to a network side, characterized in that, The method includes: Receiving a terminal-side delay jitter parameter reported by a terminal side; Allocating uplink resources for the terminal side according to the terminal-side delay jitter parameter; Receiving uplink data sent by the terminal side according to the uplink resources; The terminal-side delay jitter parameter includes: Terminal-side delay jitter interval; or Terminal-side delay jitter upper limit; or Terminal-side delay jitter mean value; or Terminal-side delay jitter mean value and upper limit; Before receiving the terminal-side delay jitter parameter reported by the terminal side, it includes: When it is detected that the current scenario meets the preset service condition, triggering sending a terminal-side delay jitter reporting request to the terminal side; When it is detected that the current scenario meets the preset service condition, it includes: In the case of detecting that the terminal-side device enters the connected state from the idle state or the non-connected state; Or, in the case of detecting that the terminal-side device occurs cell switching; Or, in the case of detecting that the terminal-side TSN clock changes.

13. The method of claim 12, wherein, The terminal-side delay jitter parameter includes: Obtaining the service data transmission characteristics of the terminal side; Allocating uplink resources for the terminal side according to the terminal-side delay jitter parameter and the service data transmission characteristics.

14. The method of claim 12, wherein, The terminal-side delay jitter parameter includes: Configuring multiple sets of uplink resources for the terminal side according to the terminal-side delay jitter parameter.

15. A resource scheduling apparatus, applied to a terminal side, characterized in that, The device includes: A reporting module for reporting a terminal-side delay jitter parameter; A first receiving module for receiving uplink resources allocated by the network side; A transmission module for transmitting uplink data according to the uplink resources; The terminal-side delay jitter parameter includes: Terminal-side delay jitter interval; or Terminal-side delay jitter upper limit; or Terminal-side delay jitter mean value; or Terminal-side delay jitter mean value and upper limit; The reporting module is specifically used for: Reporting the terminal-side delay jitter parameter when it is detected that the current scenario meets the preset reporting trigger event; The reporting module is specifically used for: In the case of detecting that the terminal-side device enters the connected state from the idle state or the non-connected state; Or, In the case of detecting that the terminal-side device occurs cell switching; Or, In the case of detecting that the terminal-side TSN clock changes.

16. The apparatus of claim 15, wherein, The terminal-side delay jitter parameter is used to indicate: a delay jitter between a node connected with the TSN and the 5G system and a DS-TT on a terminal side; a delay jitter between the DS-TT and the terminal; or a sum of the delay jitter between the node connected with the TSN and the 5G system and the DS-TT on the terminal side and the delay jitter between the DS-TT and the terminal.

17. The apparatus of claim 15, wherein, The reporting module sends the terminal-side delay jitter parameter in the following sending mode: sending terminal assistance information RRC signaling containing the terminal-side delay jitter parameter; or sending RRC signaling containing only the terminal-side delay jitter parameter; or sending a medium access control layer (MAC) layer control command containing the terminal-side delay jitter parameter.

18. The apparatus of claim 15, wherein, Further comprising: a second receiving module configured to receive a terminal-side delay jitter reporting request sent by the network side.

19. The apparatus of claim 15, wherein, The reporting module is specifically configured to: obtain a threshold parameter for reporting the terminal-side delay jitter; compare the terminal-side delay jitter parameter with the threshold parameter, and report the terminal-side delay jitter parameter when a comparison result meets a preset condition.

20. The apparatus of claim 19, wherein, The reporting module is specifically configured to: receive the threshold parameter configured by the network side; or obtain the threshold parameter according to a protocol preset value.

21. The apparatus of claim 19, wherein, The reporting module is specifically configured to: report the terminal-side delay jitter parameter when it is learned from the comparison result that the terminal-side delay jitter parameter exceeds the threshold parameter.

22. The apparatus of claim 19, wherein, The reporting module is specifically configured to: report the terminal-side delay jitter parameter when it is learned from the comparison result that a maximum value of the terminal-side delay jitter exceeds a maximum threshold of the delay jitter, the threshold parameter being the maximum threshold of the delay jitter.

23. The apparatus of claim 21, wherein, The reporting module is specifically configured to: report the terminal-side delay jitter parameter when it is learned from the comparison result that a change value of the terminal-side delay jitter parameter exceeds a change threshold of the delay jitter, the threshold parameter being the change threshold of the delay jitter.

24. The apparatus of claim 23, wherein, The change value of the terminal-side delay jitter parameter includes: a change value of a mean value of the terminal-side delay jitter, a maximum change value of the terminal-side delay jitter, or a minimum change value of the terminal-side delay jitter, which is set according to a preset protocol or configured by the network side.

25. The apparatus of claim 24, wherein, The reporting module is specifically configured to: obtain a triggering time limit; start a timer after last reporting the terminal-side delay jitter parameter, and report the terminal-side delay jitter parameter when a timing time of the timer reaches or exceeds the triggering time limit. 26.A resource scheduling apparatus applied to a network side, characterized in that, The apparatus includes: a third receiving module configured to receive a terminal-side delay jitter parameter reported by a terminal side; a configuration module configured to allocate uplink resources to the terminal side according to the terminal-side delay jitter parameter; a fourth receiving module configured to receive uplink data sent by the terminal side according to the uplink resources; The terminal-side delay jitter parameter includes: a terminal-side delay jitter interval; or a terminal-side delay jitter upper limit; or a terminal-side delay jitter mean value; or a terminal-side delay jitter mean value and upper limit; a sending module configured to send, before receiving the terminal-side delay jitter parameter reported by the terminal side, In a case where it is detected that a preset service condition is met, a terminal-side time delay jitter reporting request is triggered to be sent to the terminal side; the detection of the preset service condition includes: in a case where it is detected that the terminal-side device enters a connected state from an idle state or a non-connected state; or, in a case where it is detected that the terminal-side device performs cell switching; or, in a case where it is detected that the terminal-side TSN clock is changed.

27. The apparatus of claim 26, wherein, The configuration module is specifically configured to: Obtain service data transmission characteristics of the terminal side; According to the terminal-side time delay jitter parameter and the service data transmission characteristics, uplink resources are allocated to the terminal side.

28. The apparatus of claim 26, wherein, The configuration module is specifically configured to: According to the terminal-side time delay jitter parameter, multiple sets of uplink resources are configured for the terminal side.

29. A resource scheduling system, characterized by The network side comprises the resource scheduling device according to any one of claims 26-28. The processor readable storage medium stores a computer program, and the computer program is used to make the processor execute the method in any one of claims 1-11 or the method in any one of claims 12-14. ​ 30. A processor-readable storage medium, comprising: ​

Images