WO2022193127A1 - 业务调度方法、装置及系统 - Google Patents

业务调度方法、装置及系统 Download PDF

Info

Publication number
WO2022193127A1
WO2022193127A1 PCT/CN2021/081070 CN2021081070W WO2022193127A1 WO 2022193127 A1 WO2022193127 A1 WO 2022193127A1 CN 2021081070 W CN2021081070 W CN 2021081070W WO 2022193127 A1 WO2022193127 A1 WO 2022193127A1
Authority
WO
WIPO (PCT)
Prior art keywords
time
service
data packet
network device
interval
Prior art date
Application number
PCT/CN2021/081070
Other languages
English (en)
French (fr)
Inventor
孙海洋
余芳
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2021/081070 priority Critical patent/WO2022193127A1/zh
Publication of WO2022193127A1 publication Critical patent/WO2022193127A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a service scheduling method, device, and system.
  • Ethernet for Control Automation Technology is a real-time industrial Ethernet technology proposed by German BECKHOFF Automation Company in 2003. Because it has the characteristics of high speed, high accuracy, and time delay sensitivity, it is more and more widely used.
  • TSC assistance information TSC assistance information
  • TSCAI TSC assistance information
  • the TSCAI includes the flow direction, periodicity and burst arrival time of the TSC service.
  • the centralized control point sends the information of generating the TSCAI to the network side, and the network side generates the TSCAI according to the information of generating the TSCAI. In other words, the centralized control point can control the arrival time window of the traffic flow.
  • EtherCAT services are not necessarily periodic, and cannot control the arrival time window of service flows based on centralized control points. Therefore, the existing 5GS method to ensure that RAN devices can schedule delay-sensitive services more efficiently and in a timely manner cannot be used for EtherCAT services. . Further, if the existing method of 5GS to ensure that RAN equipment can schedule delay-sensitive services more efficiently and in a timely manner cannot be used for EtherCAT services, 5GS does not know when there is uplink data for EtherCAT services in the case of uplink transmission. Capacity and resources cannot be reserved all the time, so 5GS may not be able to schedule EtherCAT service data in time. If the terminal device misses a scheduling opportunity, the next scheduling will likely exceed the delay requirement of the EtherCAT service.
  • the embodiments of the present application provide a service scheduling method, apparatus, and system, which are used to ensure that access network equipment performs service scheduling more efficiently and in a timely manner.
  • a service scheduling method is provided, and a communication device executing the service scheduling method may be an access network device; it may also be a module applied in the access network device, such as a chip or a chip system.
  • the following description takes the execution subject as an access network device as an example.
  • the interval time for the access network device to receive from the session management entity is the time from the start time to the time when the terminal device sends the uplink data packet of the first service
  • the start time is the time when the terminal device receives the The time of the downlink data packet corresponding to the uplink data packet of the first service or the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device; the access network device according to the start time and the interval time, perform scheduling of uplink data packets of the first service.
  • the access network device can schedule the uplink data packets of the first service according to the start time and the interval between the start time and the time when the terminal device sends the uplink data packets of the first service.
  • Access network equipment can schedule services more efficiently and in a timely manner, such as scheduling of delay-sensitive services. Specifically, for example, based on this solution, when the first service is a delay-sensitive service, the terminal device misses a scheduling opportunity, and the next scheduling will likely exceed the delay requirement of the first service, or the first service can be avoided. When the service is delay-sensitive, the access network equipment cannot perform correct scheduling.
  • the access network device performs scheduling of uplink data packets of the first service according to the start time and interval, including: the access network device according to the start time and interval time, the scheduling of the uplink data packets of the first service is performed at the first time; wherein, the first time is the time interval after the start time; or, the first time is the time within the first time interval , the first time interval includes the time interval after the start time and the interval time.
  • the access network device can perform scheduling of uplink data packets of the first service at a determined time (ie, the first time), so that timely scheduling of delay-sensitive services can be ensured.
  • the access network device performs scheduling of uplink data packets of the first service according to the start time and the interval time, including: the access network device receives data from the first service. Acknowledgement ACK data packet of the downlink data packet of the first service of the terminal device; according to the start time and the interval time, the access network device performs scheduling of the uplink data packet of the first service at the second time, the second time
  • the time is the time when the interval after the start time is less than or equal to (the interval time - the transmission time of the ACK data packet between the terminal device and the access network device).
  • the embodiment of the present application provides a method for determining the time point for performing the scheduling of the uplink data packet of the first service in a scenario where an ACK data packet exists, so that in a scenario where an ACK data packet exists, the access network device can also determine The scheduling of the uplink data packets of the first service is performed at the time (ie, the second time), so the timely scheduling of the delay-sensitive service can be ensured.
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service
  • the method further includes: an access network device The time when the terminal device receives the downlink data packet is determined according to the time when the access network device sends the downlink data packet and the air interface delay. Based on this solution, the time when the terminal device receives the downlink data packet of the first service can be determined.
  • a service scheduling method is provided, and the communication apparatus for executing the service scheduling method may be a first network device; it may also be a module applied in the first network device, such as a chip or a chip system.
  • the following description will be given by taking the execution subject as the first network device as an example.
  • the first network device determines the interval, which is the time from the start time to the time when the terminal device sends the uplink data packet of the first service, and the start time is when the terminal device receives the uplink of the first service
  • the second network device can obtain the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service.
  • the access network device may execute the first step according to the start time and the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service.
  • the scheduling of uplink data packets of a service thus ensures that the access network equipment can perform service scheduling more efficiently and in a timely manner, such as scheduling of delay-sensitive services.
  • the first network device is a network data analysis function entity
  • the second network device is a policy control entity or a session management entity.
  • determining the interval time by the first network device includes: determining the interval time by the first network device according to at least one of the following information: the interval time from the policy control entity or the application function entity The type of the first service or the service description of the first service, the packet sending frequency of the uplink data packet of the first service from the terminal device or the packet receiving frequency of the downlink data packet corresponding to the uplink data packet of the first service, from the The processing time of the terminal device of the terminal device for the downlink data packet or the time when the terminal device receives the downlink data packet, the device type of the terminal device from the terminal device or the session management entity or the application function entity, or The flow identifier of the quality of service flow QoS Flow corresponding to the first service from the access network device. Based on this solution, the first network device can obtain the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service.
  • the first network device is the policy control entity
  • the second network device is the session management entity
  • determining the interval time by the first network device includes: determining the interval time by the first network device according to at least one of the following information: Type or service description of the first service, the packet sending frequency of the uplink data packet of the first service from the terminal device or the packet receiving frequency of the downlink data packet corresponding to the uplink data packet of the first service, from the terminal device.
  • the processing time of the downlink data packet by the terminal device or the time when the terminal device receives the downlink data packet, the device type of the terminal device from the terminal device or the session management entity or the application function entity, or from the access The flow identifier of the QoS Flow corresponding to the first service of the network device.
  • the first network device can obtain the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service.
  • the first network device is the policy control entity
  • the second network device is the session management entity
  • the first network device sends the interval to the second network device
  • the time includes: the policy control entity sends a first charging policy rule to the session management entity, where the first charging policy rule includes the interval time.
  • the interval time is a binding parameter in the first charging policy rule.
  • the session management entity can be made to determine whether there is a charging policy rule with the same binding parameters as the binding parameters of the first charging policy rule in the existing charging policy rules bound by the QoS Flow; if so, The session management entity binds the first charging policy rule to the existing QoS Flow; or, if it does not exist, the session management entity creates a QoS Flow corresponding to the first service according to the first charging policy rule, and assigns the first charging policy to the QoS Flow corresponding to the first service. The rule is bound to the QoS Flow corresponding to the created first service.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • a service scheduling method is provided, and a communication device executing the service scheduling method can be a session management entity; or a module applied in the session management entity, such as a chip or a chip system.
  • the following description takes the execution subject as the session management entity as an example for description.
  • the session management entity receives the interval time, the interval time is the time from the start time to the time when the terminal device sends the uplink data packet of the first service, and the start time is when the terminal device receives the uplink data of the first service.
  • the access network device can obtain the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service, and further, the access network device can execute the first step according to the start time and the interval time.
  • the scheduling of the uplink data packets of the service thus ensures that the access network equipment can perform service scheduling in a more efficient and timely manner, such as scheduling of delay-sensitive services.
  • receiving the interval time by the session management entity includes: receiving the interval time from the policy control entity or the network data analysis function entity by the session management entity.
  • the session management entity receiving the interval time from the policy control entity includes: the session management entity receives the first charging policy rule from the policy control entity, the first accounting The fee policy rule includes this interval.
  • the service scheduling method provided by the embodiment of the present application further includes: a session management entity creates a quality of service flow QoS Flow corresponding to the first service according to the first charging policy rule , and bind the first charging policy rule to the created QoS Flow corresponding to the first service.
  • a session management entity creates a quality of service flow QoS Flow corresponding to the first service according to the first charging policy rule , and bind the first charging policy rule to the created QoS Flow corresponding to the first service.
  • the interval time is a binding parameter in the first charging policy rule
  • the service scheduling method provided by this embodiment of the present application further includes: the session management entity determines that the existing In the charging policy rules bound by the QoS Flow, whether there is a charging policy rule with the same binding parameters as the binding parameters of the first charging policy rule; if so, the session management entity will use the first charging policy The rule is bound to the existing QoS Flow; or, if it does not exist, the session management entity creates a QoS Flow corresponding to the first service according to the first charging policy rule, and binds the first charging policy rule to The created QoS Flow corresponding to the first service.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • a service scheduling method may be an access network device; it may also be a module applied in the access network device, such as a chip or a chip system.
  • the following description takes the execution subject as an access network device as an example.
  • the access network device receives the first indication information from the session management entity; the access network device determines the interval time according to the first indication information, and the interval time is from the start time to the time when the terminal device sends the uplink data packet of the first service The start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service or the access network device sends the uplink data of the first service to the terminal device.
  • the access network device performs scheduling of the uplink data packet of the first service according to the start time and the interval time.
  • the access network device can know that the data transmission interval time of the first service is fixed, and further, after the access network device determines the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service, The access network device can schedule the uplink data packets of the first service according to the start time and interval time, thus ensuring that the access network device can schedule services more efficiently and in a timely manner, such as scheduling of delay-sensitive services.
  • the first indication information is used to indicate that the data transmission interval of the first service is fixed.
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service; the access network device according to the first indication information, and determining the interval time includes: the access network device obtains at least one set of time information according to the first indication information, and each set of time information in the at least one set of time information includes the time when the terminal device receives the first service.
  • the access network device can obtain the interval time from the start time to the time when the terminal device sends the uplink data packet of the first service by self-learning.
  • the starting time point is the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device;
  • the access network device The device determining the interval time according to the first indication information includes: the access network device obtains at least one group of time information according to the first indication information, and each group of time information in the at least one group of time information includes the access network The time when the device sends the downlink data packet of the first service to the terminal device and the time when the terminal device sends the uplink data packet corresponding to the downlink data packet of the first service; the access network device determines according to the at least one set of time information the interval time. Based on this solution, the access network device can obtain the interval time from the start time to the time when the terminal device sends the uplink data packet of the first service by self-learning.
  • the access network device performs scheduling of the uplink data packets of the first service according to the start time and the interval time, including: the access network device according to the start time and the interval time. start time and the interval time, and perform the scheduling of the uplink data packets of the first service at the first time; wherein, the first time is the time interval after the start time; or, the first time is the first time The time in a time interval, the first time interval includes the time interval after the start time and the interval time.
  • the access network device can perform scheduling of uplink data packets of the first service at a determined time (ie, the first time), so that timely scheduling of delay-sensitive services can be ensured.
  • the access network device performs scheduling of uplink data packets of the first service according to the start time and the interval time, including: the access network device receives data from the first service. Acknowledgement ACK data packet of the downlink data packet of the first service of the terminal device; according to the start time and the interval time, the access network device performs scheduling of the uplink data packet of the first service at the second time, the second time
  • the time is the time when the interval after the start time is less than or equal to (the interval time - the transmission time of the ACK data packet between the terminal device and the access network device).
  • the embodiment of the present application provides a method for determining the time point for performing the scheduling of the uplink data packet of the first service in a scenario where an ACK data packet exists, so that in a scenario where an ACK data packet exists, the access network device can also determine The scheduling of the uplink data packets of the first service is performed at the time (ie, the second time), so the timely scheduling of the delay-sensitive service can be ensured.
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service
  • the service scheduling method provided by the embodiment of the present application It also includes: the access network device determines the time when the terminal device receives the downlink data packet according to the time when the access network device sends the downlink data packet and the air interface delay. Based on this solution, the time when the terminal device receives the downlink data packet of the first service can be determined.
  • a service scheduling method is provided, and a communication device executing the service scheduling method may be a session management entity; or a module applied in the session management entity, such as a chip or a chip system.
  • the following description takes the execution subject as the session management entity as an example for description.
  • the session management entity receives the second indication information from the policy control entity, and the second indication information is used for a fixed data transmission interval of the first service, and the interval time is from the start time to the terminal device sending the uplink data packets of the first service
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service or the access network device sends the uplink data of the first service to the terminal device.
  • the session management entity sends first indication information to the access network device, where the first indication information is used to indicate that the data transmission interval of the first service is fixed.
  • the access network device can know that the data transmission interval time of the first service is fixed, and further, after the access network device determines the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service, The access network device can schedule the uplink data packets of the first service according to the start time and interval time, thus ensuring that the access network device can schedule services more efficiently and in a timely manner, such as scheduling of delay-sensitive services.
  • the first indication information is used to indicate that the data transmission interval of the first service is fixed.
  • the second indication information is used to indicate that the data transmission interval of the first service is fixed.
  • the session management entity receives the second indication information from the policy control entity, including: the session management entity receives the first charging policy rule from the policy control entity, the first charging policy rule The charging policy rule includes the second indication information.
  • the service scheduling method provided by the embodiment of the present application further includes: a session management entity creates a quality of service flow QoS Flow corresponding to the first service according to the first charging policy rule , and bind the first charging policy rule to the created QoS Flow corresponding to the first service.
  • a session management entity creates a quality of service flow QoS Flow corresponding to the first service according to the first charging policy rule , and bind the first charging policy rule to the created QoS Flow corresponding to the first service.
  • the second indication information is a binding parameter in the first charging policy rule
  • the service scheduling method provided in this embodiment of the present application further includes: the session management entity determines In the existing charging policy rules bound by QoS Flow, whether there is a charging policy rule with the same binding parameters as the binding parameters of the first charging policy rule; The charging policy rule is bound to the existing QoS Flow; or, if it does not exist, the session management entity creates the QoS Flow corresponding to the first service according to the first charging policy rule, and binds the first charging policy rule Set to the QoS Flow corresponding to the created first service.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • the first service includes: an Ethernet control automation technology EtherCAT service, an interactive service, or an extended reality XR service.
  • a communication apparatus for implementing the above method.
  • the communication device may be the access network device in the first aspect or the fourth aspect, or a device including the access network device; or, the communication device may be the first network device in the second aspect, or includes The device of the first network device; or, the communication device may be the session management entity in the third aspect or the fifth aspect, or a device including the session management entity.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication apparatus may include a processing module and a transceiver module.
  • the transceiver module also referred to as a transceiver unit, is used to implement the sending and/or receiving functions in any of the above aspects and any possible implementation manners.
  • the transceiver module can be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the processing module may be used to implement the processing functions in any of the foregoing aspects and any possible implementation manners thereof.
  • the processing module can be, for example, a processor.
  • the transceiver module includes a transmitting module and a receiving module, which are respectively used to implement the transmitting and receiving functions in any of the above aspects and any possible implementation manners thereof.
  • a communication device comprising: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute the method according to any one of the preceding aspects according to the instruction.
  • the communication device may be the access network device in the first aspect or the fourth aspect, or a device including the access network device; or, the communication device may be the first network device in the second aspect, or includes The device of the first network device; or, the communication device may be the session management entity in the third aspect or the fifth aspect, or a device including the session management entity.
  • the communication device further includes a memory for storing necessary program instructions and data.
  • the communication device is a chip or a chip system.
  • the communication device when it is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a communication device comprising: a processor and an interface circuit; the interface circuit is used to receive a computer program or instruction and transmit it to the processor; the processor is used to execute the computer program or instruction to enable the communication
  • the apparatus performs a method as described in any of the above aspects.
  • the communication device is a chip or a chip system.
  • the communication device when it is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer can execute the method described in any one of the above aspects.
  • a computer program product comprising instructions which, when run on a computer, enable the computer to perform the method of any of the preceding aspects.
  • a communication system in an eleventh aspect, includes an access network device for executing the service scheduling method described in the first aspect, and a communication system for executing the service scheduling method described in the third aspect. Session management entity.
  • the communication provision further includes a first network device for executing the service scheduling method described in the above first aspect.
  • a twelfth aspect provides a communication system, the communication system includes an access network device for executing the service scheduling method described in the fourth aspect, and a communication system for executing the service scheduling method described in the fifth aspect. Session management entity.
  • 1 is a schematic diagram of data transmission of an EtherCAT service provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram 1 of the networking of the EtherCAT service provided by the embodiment of the present application.
  • FIG. 3 is a second networking schematic diagram of the EtherCAT service provided by the embodiment of the present application.
  • Figure 4 is a schematic diagram of the 5G QoS model based on QoS flow proposed by the 5G system
  • FIG. 5a is a schematic diagram of a service-oriented architecture of an existing 5G network
  • Fig. 5b is a schematic diagram of a reference point-based 5G network architecture corresponding to Fig. 5a;
  • 5c is a schematic diagram of a frame structure in an LTE system
  • Figure 5d is a schematic diagram of a frame structure in a 5G system
  • FIG. 6 is a schematic diagram 1 of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 7 is a second schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 8 is a third schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a service scheduling method provided by an embodiment of the present application.
  • 11a is a schematic diagram 1 of a first time interval provided by an embodiment of the present application.
  • 11b is a second schematic diagram of a first time interval provided by an embodiment of the present application.
  • 11c is a schematic diagram 3 of a first time interval provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of another service scheduling method provided by an embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another service scheduling method provided by an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of another service scheduling method provided by an embodiment of the present application.
  • FIG. 15 is a schematic flowchart of another service scheduling method provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of another communication apparatus provided by an embodiment of the present application.
  • TSC is a high reliability and availability communication service supporting deterministic communication and/or synchronous communication. It involves providing quality of service (QoS) characteristics such as bounds (or thresholds or limits) for delay, loss and reliability for packet transport.
  • QoS quality of service
  • the end systems and relay/transport nodes can be strictly synchronized (eg clock synchronization).
  • EtherCAT has the characteristics of high speed, high accuracy, and delay sensitivity, and supports a variety of device connection topologies. Among them, EtherCAT uses the same physical and data link layer, its slave node uses a dedicated control chip, and the master node uses a standard Ethernet controller.
  • the master node is the only node that is allowed to send data frames, and the slave stations can only forward data frames. That is, the data frame is like a train, starting from the master node, passing through each slave node, putting down or bringing the data for the slave node, and finally returning to the master node.
  • Each slave node has 4 ports, so there will be no data conflict, which can ensure the timely scheduling of business data. For example, referring to Figure 1, after the data frame is sent by the master node 1, the data for each slave node is put down or brought on in the process of the slave node 1, the slave node 2, and the slave node 3.
  • the data frame returns from node 3, passes through slave node 2 and slave node 1 in sequence, and then returns to master node 1.
  • the slave node 1, the slave node 2, and the slave node 3 all include 4 ports, the data frames will not conflict, and the timely scheduling of service data can be ensured.
  • the master node may be referred to as a master device, a master station, a master EtherCAT device, a master Ethernet device, or a distributed clock (DC) master station, etc.
  • the slave node may be referred to as A slave device, a slave station, a slave EtherCAT device, a slave Ethernet device, or a DC slave node, etc., are described here in a unified manner, which is not limited in this embodiment of the present application.
  • the networking modes of the master node and the slave node are described below with reference to FIG. 2 and FIG. 3 .
  • the networking mode of the master node and the slave node may include a direct connection mode or an open mode.
  • the connection between the master node 1 and the slave node 1, the slave node 2, and the slave node 3 can be directly connected without going through a switch.
  • the open mode can be connected between the master node 1 and the slave node 1, the slave node 2, and the slave node 3 through a switch (switch), and also through the segment address slave node (segment address slave device) 1.
  • the connection between the master node 2 and the slave node 4, the slave node 5, and the slave node 6 passes through the switch, and can also pass through the segment address slave node 2.
  • the switch may also be connected to a device with other functions, such as a generic etherment device, which is not specifically limited in this embodiment of the present application.
  • a PDU session is an association between a terminal device and a data network (DN) for providing a PDU connection service.
  • DN data network
  • a 5G QoS model based on QoS Flow (QoS Flow) is proposed, as shown in Figure 4.
  • the 5G QoS model supports guaranteed bit rate (guaranteed bit rate, GBR) QoS Flow (ie GBR QoS Flow) and non-guaranteed bit rate (non-guaranteed bit rate, non-GBR) QoS Flow (ie non-GBR QoS Flow) ).
  • Packets controlled by the same QoS Flow receive the same transmission processing (such as scheduling, or admission thresholds, etc.).
  • one or more PDU sessions can be established with the 5G network.
  • One or more QoS Flows can be established in each PDU session.
  • a QoS Flow is identified by a QoS Flow identifier (QFI), that is, a QFI uniquely identifies a QoS Flow in a session.
  • QFI QoS Flow identifier
  • a PDU session and a general packet radio service (general packet radio service, GPRS) tunneling protocol user plane (GPRS tunneling protocol user plane, GTP-U) between the RAN device and the user plane function (user plane function, UPF) Tunnels correspond one-to-one;
  • one QoS Flow corresponds to one radio bearer between the terminal device and the RAN device, and one radio bearer can correspond to one or more QoS Flows.
  • QoS profile whether a QoS Flow is a GBR QoS Flow or a non-GBR QoS Flow is determined by the corresponding QoS profile (QoS profile).
  • the corresponding QoS file contains the following QoS parameters: 5G QoS identifier (5G QoS identifier, 5QI), allocation and retention priority (ARP), guaranteed flow bit rate (guaranteed flow bit rate, GFBR) and maximum flow bit rate (MFBR), optionally including QoS notification control (QNC).
  • 5G QoS identifier 5G QoS identifier, 5QI
  • ARP allocation and retention priority
  • guaranteed flow bit rate guaranteed flow bit rate
  • GFBR guaranteed flow bit rate
  • MFBR maximum flow bit rate
  • QNC QoS notification control
  • the GBR QoS Flow can be divided into a GRB QoS Flow that requires notification control and a GBR QoS Flow that does not require notification control.
  • the RAN device For the GBR QoS Flow that requires notification control, when the RAN device detects that the corresponding QoS Flow resources cannot be satisfied, the RAN device notifies the session management function (SMF) of the event. Further SMF can initiate QoS Flow deletion or modification flow.
  • SMF session management function
  • the corresponding QoS file contains the following QoS parameters: 5QI and ARP; optionally, the reflective QoS attribute (RQA).
  • 5QI is a scalar used to index to the corresponding 5G QoS feature.
  • 5QI is divided into standardized 5QI, pre-configured 5QI and dynamically allocated 5QI.
  • standardized 5QI there is a one-to-one correspondence with a set of standardized 5G QoS characteristic values; for the pre-configured 5QI, the corresponding 5G QoS characteristic values are pre-configured on the radio access network (RAN) equipment; for dynamic
  • the assigned 5QI and the corresponding 5G QoS features are sent by the core network device to the RAN device through the QoS file.
  • ARP includes priority, preemption capability and preemption capability.
  • GFBR stands for the bit rate expected to be provided to the GBR QoS Flow.
  • MFBR limits the bit rate provided to the GBR QoS Flow, i.e. the maximum bit rate provided to the GBR QoS Flow. If this bit rate is exceeded, packets can be dropped.
  • RQA is used to indicate that the service transmitted using the corresponding QoS Flow uses reverse QoS.
  • the QNC is used to instruct the RAN device whether to notify the network side when the GFBR cannot be satisfied within the usage period of the QoS Flow.
  • the 5G system also introduces QoS parameters at the aggregation level, such as user equipment (UE)-aggregate maximum bit rate (AMBR), session AMBR (session-AMBR) ) and slice maximum bitrate, etc.
  • UE user equipment
  • AMBR enhanced bit rate
  • session AMBR session-AMBR
  • slice maximum bitrate etc.
  • UE-AMBR is used to control the aggregate bit rate of all non-GBR QoS Flows of terminal equipment, and the control is performed by RAN equipment.
  • the RAN device controls the uplink (uplink, UL) and downlink (downlink, DL) UE-AMBR, and performs traffic shaping, such as discarding data packets exceeding the quota.
  • session-AMBR is used to control the aggregated maximum bit rate of all non-GBR QoS Flows in one PDU session of the terminal device, and the control is performed by the terminal device and the UPF.
  • the terminal device controls the uplink (Uplink, UL) Session-AMBR to perform traffic shaping, such as discarding data packets exceeding the quota.
  • UPF controls UL and downstream (downlink, DL) Session-AMBR, and performs traffic shaping, such as discarding packets that exceed the quota.
  • the maximum bit rate of the slice is used to control the maximum bit rate of all QoS Flows of the terminal device in a network slice (slice), and the control is performed by the terminal device, the RAN device or the UPF.
  • RAN equipment controls UL and DL slice-MBR, performs traffic shaping, such as dropping packets that exceed the quota.
  • the binding mechanism is to associate the service data flow (defined by the service data flow (SDF) template in the policy and charging control (PCC) rules) with the QoS Flow that transmits the service data flow process.
  • SDF service data flow
  • PCC policy and charging control
  • the first step, session binding, is to make a one-to-one correspondence between the AF session and the PDU session.
  • session binding is to make a one-to-one correspondence between the AF session and the PDU session.
  • PCC rule authorization is performed by the PCF, authorizes the PCC rule, and assigns QoS parameters to the PCC rule.
  • PCC rule authorization is performed by the PCF, authorizes the PCC rule, and assigns QoS parameters to the PCC rule.
  • the third step, QoS Flow binding associates the PCC rule with the QoS Flow in the PDU session. Bind with at least one of the following bind parameters:
  • ARP for a related description, please refer to the above QoS parameter section, which will not be repeated here.
  • the PCC rule includes one or more of the following parameters, one or more of the following parameters can also be used as binding parameters:
  • QNC the related description can refer to the above-mentioned QoS parameter part, which will not be repeated here.
  • Priority indicates the priority of scheduling resources in the QoS flow. Priority should be used to differentiate QoS flows from the same end device, and also to differentiate QoS flows from different end devices.
  • Average window the average window is only used for GBR QoS Flow, which represents the duration of calculating GFBR and MFBR.
  • MDBV indicates the maximum amount of data required to be served by the 5G access network within a packet delay budget (PDB). Among them, the PDB defines the upper limit of the time that a data packet can be delayed in transmission between the terminal device and the UPF network element with the N6 interface.
  • PDB packet delay budget
  • the above-mentioned priority, average window or maximum data burst volume may also be parameters in the QoS attribute corresponding to the above-mentioned 5QI, which is not specifically limited here.
  • the interval time may be used as a binding parameter, wherein the start time The start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service or the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device; or, if the PCC rules includes the indication information used to indicate that the data transmission interval of the first service is fixed or the indication information used to indicate that the data transmission interval of the first service is fixed, then the indication information can be used as a binding parameter. No specific limitation is made.
  • FIG. 5a is a schematic diagram of a service-oriented architecture of an existing 5G network.
  • the 5G network includes RAN equipment, UPF, access and mobility management function (core access and mobility management function, AMF), SMF, authentication server function (authentication server function, AUSF), network slice selection function (network slice selection function, NSSF), Network Exposure Function (NEF), Network Exposure Function Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), Unified data repository (UDR), application function (application function, AF) or charging function (charging function, CHF), etc.
  • FIG. 5G network includes RAN equipment, UPF, access and mobility management function (core access and mobility management function, AMF), SMF, authentication server function (authentication server function, AUSF), network slice selection function (network slice selection function, NSSF), Network Exposure Function (NEF), Network Exposure Function Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), Unified data repository (UDR), application function
  • NWDAF network data analytics function
  • the terminal device accesses the 5G network through the RAN device, the terminal device communicates with the AMF through the N1 interface (N1 for short); the RAN device communicates with the AMF through the N2 interface (N2 for short); the RAN device communicates with the AMF through the N3 interface ( N3 for short) communicates with the UPF; the SMF communicates with the UP through the N4 interface (N4 for short), and the UPF accesses the DN through the N6 interface (N6 for short).
  • the control plane functions such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, CHF or AF shown in FIG.
  • the service interface provided by AUSF is Nausf
  • the service interface provided by AMF is Namf
  • the service interface provided by SMF is Nsmf
  • the service interface provided by NSSF is Nnssf
  • the service interface provided by NEF is Nnef
  • the service interface provided by NRF is Nnrf
  • the service interface provided by PCF is Npcf
  • the service interface provided by UDM is Nudm
  • the service interface provided by UDR is Nudr
  • the service interface provided by CHF is Nchf
  • the service interface provided by AF externally Naf.
  • FIG. 5b is a schematic diagram of a reference point-based 5G network architecture corresponding to FIG. 5a.
  • the terminal device accesses the 5G network through the RAN device, the terminal device communicates with the AMF through the N1 interface (N1 for short); the RAN device communicates with the AMF through the N2 interface (N2 for short); the RAN device communicates with the AMF through the N3 interface (N3 for short) ) communicates with the UPF; different UPFs communicate through the N9 interface (N9 for short); the UPF accesses the DN through the N6 interface (N6 for short).
  • SMF communicates with UPF through N4 interface (N4 for short); AMF network element communicates with SMF through N11 interface (N11 for short); AMF communicates with UDM through N8 interface (N8 for short); AMF communicates with AUSF through N12 interface (N12 for short) Communication; AMF communicates with PCF through N15 interface (N15 for short); AMF communicates with NSSF through N22 interface (N22 for short); different AMFs communicate through N14 interface (N14 for short); SMF communicates with PCF through N7 interface (N7 for short) ; SMF communicates with UDM through N10 interface (N10 for short); SMF communicates with NEF through N29 interface (N29 for short); SMF communicates with NRF through Nnrf interface (Nnrf for short); SMF communicates with CHF through Nchf interface (Nchf for short); PCF It communicates with NEF through N5 interface (N5 for short); UDR communicates with PCF through N36 interface (N36 for short); U
  • TSCAI includes the flow direction, period information and/or burst arrival time of the TSC service.
  • the centralized control point sends the information of generating the TSCAI to the network side, and the network side generates the TSCAI according to the information of generating the TSCAI. Further, the network side (such as SMF) needs to send the TSCAI corresponding to the QoS Flow to the RAN.
  • the RAN reserves resources in advance for scheduling according to the period and the burst arrival time.
  • a radio frame is defined to include 10 subframes (subframes), each subframe is 1 millisecond (ms) in length, and each subframe includes two time slots (slots), each slot is 0.5ms.
  • the number of symbols included in each slot is related to the length of a cyclic prefix (CP) in a subframe. If the CP is a normal CP, each slot includes 7 symbols, and each subframe consists of 14 symbols.
  • each subframe can be serial numbered #0, #1, # 2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12, #13 symbols.
  • each slot includes 6 OFDM symbols, and each subframe consists of 12 symbols.
  • each subframe may have serial numbers #0, #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11.
  • the size of a physical resource block is defined as one time slot in the time domain and 180 kHz in the frequency domain.
  • PRB physical resource block
  • a PRB includes a total of 84 or 72 resource elements (REs), and REs can be It is uniquely identified by an index pair (k, l), where k is the subcarrier index and l is the symbol index.
  • the PRBs are numbered in the frequency domain, that is, the PRB index or the PRB sequence number.
  • a PRB pair (PRB pair) is defined as a pair of PRBs with the same PRB index or PRB sequence number in two time slots in a subframe.
  • a radio frame is defined to include 10 subframes, the length of each subframe is 1 millisecond (ms), and each subframe includes one or more time slots.
  • one PRB is defined to include 12 subcarriers in the frequency domain, and the PRBs are numbered in the frequency domain, that is, the PRB index or the PRB sequence number, as described above.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one (a) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • words such as "first” and "second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner to facilitate understanding.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • a communication system 60 provided in an embodiment of the present application includes an access network device 601 and a session management entity 602 .
  • the access network device 601 and the session management entity 602 may communicate directly or communicate through the forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the session management entity 602 is used to send an interval time to the access network device 601, and the interval time is from the start time to the terminal device sending the first service The time between the times of the upstream packets.
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service or the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device.
  • the access network device 601 is configured to receive the interval time from the session management entity 602, and perform scheduling of uplink data packets of the first service according to the start time and the interval time.
  • the communication system 60 provided in this embodiment of the present application further includes a first network device 603 .
  • the first network device 603 is configured to send the interval time to the session management entity 602 after determining the interval time.
  • the session management entity 602 is configured to receive the interval time from the first network device 603 .
  • the first network device 603 is a network data analysis function entity or a policy control entity.
  • the communication system 60 provided in this embodiment of the present application further includes a second network device 604 .
  • the first network device 603 is configured to send the interval time to the second network device 604 after determining the interval time.
  • the second network device 604 is configured to receive the interval time from the first network device 603 and send the interval time to the session management entity 602 .
  • the session management entity 602 is configured to receive the interval time from the first network device 603 .
  • the first network device 603 is a network data analysis function entity
  • the second network device 604 is a policy control entity.
  • the session management entity 602 is configured to send the first indication information to the access network device 601 .
  • the access network device 601 is configured to receive the first indication information from the session management entity 602, and after determining the interval time according to the first indication information, perform scheduling of uplink data packets of the first service according to the start time and the interval time .
  • the interval time is the time from the start time to the time when the terminal device sends the uplink data packet of the first service
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service or receives The time when the network access device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device.
  • the communication system 60 provided in this embodiment of the present application further includes a policy control entity 605 .
  • the policy control entity 605 is configured to send second indication information to the session management entity 602, where the second indication information is used to indicate that the data transmission interval of the first service is fixed or the second indication information is used to indicate the first data transmission interval with a fixed data transmission interval. business.
  • the session management entity 602 is configured to receive the second indication information from the policy control entity 605, and determine the first indication information according to the second indication information.
  • the access network device in this embodiment of the present application may be any communication device with a wireless transceiver function that is used to communicate with a terminal device.
  • the access network equipment includes but is not limited to: evolved node B (evolved node B, eNB), baseband unit (baseband unit, BBU), access point (access point, wireless fidelity, WIFI) system AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission receiver point (TRP), etc.
  • the access network device may also be a RAN device in a 5G system, for example, the RAN device includes a gNB or TRP or TP, or one or a group (including multiple antenna panels) antenna panels of a base station in the 5G system.
  • the RAN device may also be a network node that constitutes a gNB or TP, such as a BBU, or a distributed unit (distributed unit, DU).
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (active antenna unit, AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implementing functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the terminal equipment (terminal equipment) in this embodiment of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, or a user terminal.
  • terminal terminal
  • wireless communication device user agent, user device, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, Personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or future evolved PLMNs
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDAs Personal digital assistants
  • handheld devices with wireless communication capabilities computing devices or other processing devices connected to wireless modems
  • in-vehicle devices wearable devices
  • terminal devices in future 5G networks or future evolved PLMNs are not limited in this embodiment of the present application.
  • the terminal may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving Wireless terminals, wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • a wearable device may also be referred to as a wearable smart device, which is a general term for intelligently designing everyday wearable devices using wearable technology and developing wearable devices, such as glasses, Gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the communication system 60 shown in FIG. 6 to FIG. 8 may be applicable to the 5G network currently under discussion, and may also be applicable to other future networks, etc., which is not specifically limited in this embodiment of the present application.
  • the network element or entity corresponding to the above-mentioned access network device may be the one described in FIG. 5 a or FIG. 5 b .
  • the master node (and x slave nodes, where x is a natural number) in the EtherCAT may be located in a certain location in the 5G network DN, transmits data between the N6 interface and the UPF, one or more slave nodes in EtherCAT can correspond to the terminal equipment in the 5G network, which is described here in a unified manner, and will not be repeated below.
  • the access network device, the session management entity, the first network device, or the policy control entity in this embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device, which is implemented in this application. This example is not specifically limited.
  • the related functions of the access network device, the session management entity, the first network device, or the policy control entity in this embodiment of the present application may be implemented by one device, or jointly implemented by multiple devices, or may be implemented by one device. It is implemented by one or more functional modules in the device, which is not specifically limited in this embodiment of the present application. It is to be understood that the above-mentioned functions can be either network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (eg, a cloud platform). Virtualization capabilities.
  • FIG. 9 is a schematic structural diagram of a communication apparatus 900 according to an embodiment of the present application.
  • the communication device 900 includes one or more processors 901, a communication line 902, and at least one communication interface (in FIG. 9, the communication interface 904 and one processor 901 are used as an example for illustration only), optional
  • the memory 903 may also be included.
  • the processor 901 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 902 may include a path for connecting the various components.
  • the communication interface 904 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (wireless local area networks, WLAN) and the like.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 904 can also be a transceiver circuit located in the processor 901, so as to realize the signal input and signal output of the processor.
  • the memory 903 may be a device having a storage function. For example, it may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of storage devices that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being stored by a computer any other medium taken, but not limited to this.
  • the memory may exist independently and be connected to the processor through communication line 902 .
  • the memory can also be integrated with the processor.
  • the memory 903 is used for storing computer-executed instructions for executing the solution of the present application, and the execution is controlled by the processor 901 .
  • the processor 901 is configured to execute the computer-executed instructions stored in the memory 903, thereby implementing the service scheduling method provided in the embodiment of the present application.
  • the processor 901 may also perform processing-related functions in the service scheduling method provided by the following embodiments of the present application, and the communication interface 904 is responsible for communicating with other devices or communication networks. This is not specifically limited in the application examples.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as application code, which is not specifically limited in the embodiment of the present application.
  • the processor 901 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 9 .
  • the communication apparatus 900 may include multiple processors, such as the processor 901 and the processor 908 in FIG. 9 .
  • processors can be a single-core processor or a multi-core processor.
  • the processor here may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or artificial intelligence Processors and other types of computing devices that run software, each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the communication apparatus 900 may further include an output device 905 and an input device 906 .
  • the output device 905 is in communication with the processor 901 and can display information in a variety of ways.
  • the output device 905 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector) Wait.
  • Input device 906 is in communication with processor 901 and can receive user input in a variety of ways.
  • the input device 906 may be a mouse, a keyboard, a touch screen device, a sensor device, or the like.
  • the above-mentioned communication apparatus 900 may also be sometimes referred to as a communication apparatus, which may be a general-purpose device or a dedicated device.
  • the communication device 900 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the above-mentioned terminal device, the above-mentioned network device, or a 9 devices of similar structure.
  • PDA personal digital assistant
  • This embodiment of the present application does not limit the type of the communication apparatus 900 .
  • the first service in the following embodiments of the present application may be a flow granularity service, which is described with QoS flow granularity in the embodiment; it may also be a service of other granularity, such as a session granularity service, which is described in the implementation
  • a session granularity service which is described in the implementation
  • the granularity of the PDU session is used for description; the description is uniformly described here, and this embodiment of the present application does not specifically limit this.
  • a service scheduling method provided by an embodiment of the present application is as follows.
  • the session management entity sends an interval time to an access network device.
  • the access network device receives the interval time from the session management entity.
  • the interval time is the time from the start time to the time when the terminal device sends the uplink data packet of the first service
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service or The time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device.
  • the minimum time unit (or granularity) of the interval time in this embodiment of the present application may be seconds (s), or may be a time unit of smaller granularity such as a radio frame, subframe, or time slot.
  • a radio frame subframe
  • time slot time slot
  • the minimum time unit (or granularity) is used as a time slot for illustration, which is described in a unified manner here, and will not be repeated below.
  • the start time is time slot 1
  • the time when the terminal device sends the uplink data packet of the first service is time slot 3 after 2 time slots
  • the interval time is 2 time slots.
  • serial number of the time slot in the above example is only used to distinguish the time slot, and does not limit the radio frame or subframe to which it belongs, and is described here in a unified manner, which is applicable to all the embodiments of this application, and will not be repeated in the following. .
  • the access network device performs scheduling of uplink data packets of the first service according to the start time and the interval time.
  • the first service in this embodiment of the present application may be applied to any service with an "interval time” feature (that is, the processing time of the application layer or the terminal device is fixed, and the uplink data packet is returned after a fixed time after receiving the downlink data packet; or , after the network transmits a data packet for a fixed time, it will definitely receive a response data packet) services, such as delay-sensitive services (data packets of this type of service are no longer valuable or less valuable when the delivery exceeds the delay requirement).
  • the delay-sensitive service in the embodiment of the present application may be an aperiodic delay-sensitive service or a periodic delay-sensitive service, which is not specifically limited in the embodiment of the present application.
  • the first service in the embodiment of the present application includes: an EtherCAT service, an automation control service, a power distribution service, an interactive service, or an extended reality (extended reality, XR) service and other aperiodic delay-sensitive services.
  • EtherCAT service an automation control service
  • a power distribution service an interactive service
  • extended reality (extended reality, XR) service and other aperiodic delay-sensitive services.
  • the service scheduling method provided by the embodiment of the present application further includes: an access network.
  • the device determines the time when the terminal device receives the downlink data packet according to the time when the access network device sends the downlink data packet and the air interface delay.
  • the access network device can determine that the time when the terminal device receives the downlink data packet is time slot 4.
  • step S1002 includes: according to the start time and the interval time, the access network device performs scheduling of the uplink data packets of the first service at the first time.
  • the first time is the time at the interval time after the start time.
  • the start time is time slot 1 and the interval time is 3 time slots
  • the first time is time slot 4.
  • the first time is the time in the first time interval
  • the first time interval includes the time at the interval time after the start time.
  • the first time interval may be obtained by taking the first time as a reference and offset by one time interval forward and backward, as shown in FIG. 11a; or, the first time interval may be the first time as the starting time , obtained by offsetting a time period backward, as shown in FIG. 11b; or, the first time interval may be obtained by taking the first time as the end time, and offsetting it forward by a time period, as shown in FIG. 11c
  • this application implements The example does not specifically limit the form of the first time interval.
  • the first time is time slot 3, and is shifted forward by 2 time slots and shifted backward by 1 time slot, the first time interval is time slot 1 to time slot 4.
  • the first time interval is time slot 1 to time slot 4 .
  • the first time interval is time slot 1 to time slot 4 .
  • step S1002 includes: the access network device receives an acknowledgement (acknowledgement, ACK) data packet of the downlink data packet of the first service from the terminal device; , perform the scheduling of the uplink data packets of the first service at the second time, and the second time is when the interval after the start time is less than or equal to (interval time - the transmission time of the ACK data packet between the terminal device and the access network device) time.
  • acknowledgement acknowledgement
  • the downlink data packet of the first service may be a downlink data packet, that is, each downlink data packet of the first service has an ACK data packet; or, the downlink data packet of the first service may be It is a plurality of downlink data packets, that is, a plurality of downlink data packets of the first service share one ACK data packet, which is not specifically limited in this embodiment of the present application.
  • the start time is time slot 1
  • the interval time is 3 time slots
  • the transmission time of the ACK data packet between the terminal device and the access network device is 1 time slot
  • each downlink of the first service If the data packets all have ACK data packets, the second time may be time slot 3 of radio frame 2 .
  • the start time is time slot 1
  • the interval time is 3 time slots
  • the transmission time of the ACK data packet between the terminal device and the access network device is 1 time slot
  • the multiple times of the first service The two downlink data packets share one ACK data packet, and the second time may be time slot 2.
  • the scheduling of the uplink data packet of the first service performed by the access network device can be understood as the access network device performing (or enabling) the communication between the terminal device and the access network device.
  • the uplink data transmission includes, for example, that the access network device performs (or enables) the terminal device to send the uplink data packet of the first service to the access network device, which is described here uniformly and will not be repeated below.
  • the access network device may execute the uplink data of the first service according to the start time and the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service Packet scheduling, thus ensuring that access network equipment can schedule services more efficiently and in a timely manner, such as scheduling of delay-sensitive services.
  • the first service is a delay-sensitive service
  • the terminal device misses a scheduling opportunity, and the next scheduling will likely exceed the delay requirement of the first service, or the first service can be avoided.
  • the access network equipment cannot perform correct scheduling. It should be noted that this example is applicable to other embodiments of the present application, which are uniformly described here, and will not be repeated below.
  • the following exemplarily provides an implementation manner for a session management entity to obtain an interval time.
  • the service scheduling method provided by this embodiment of the present application further includes the following steps:
  • the first network device determines the interval time.
  • the first network device is a network data analysis functional entity.
  • step S1003 includes: the first network device determines the interval according to at least one of the following information: the type of the first service or the service description of the first service from the policy control entity or the application function entity, the service description of the first service from the terminal device The packet sending frequency of the uplink data packet of the first service or the packet receiving frequency of the downlink data packet corresponding to the uplink data packet of the first service, the processing time of the terminal device from the terminal device to the downlink data packet, or the terminal device receiving the downlink data packet time, the device type of the terminal device from the terminal device or the session management entity or the application function entity, or the flow identifier of the QoS Flow corresponding to the first service from the access network device.
  • the first network device is a policy control entity.
  • step S1003 includes: the first network device determines the interval according to at least one of the following information: the type of the first service from the application function entity or the service description of the first service, the first service from the terminal device The packet sending frequency of the uplink data packet or the packet receiving frequency of the downlink data packet corresponding to the uplink data packet of the first service, the processing time of the terminal device on the downlink data packet from the terminal device or the time when the terminal device receives the downlink data packet, from The device type of the terminal device or the session management entity or the terminal device of the application function entity, or the flow identifier of the QoS Flow corresponding to the first service from the access network device.
  • the first network device sends the interval time to the session management entity.
  • the session management entity receives the interval time from the first network device.
  • the first network device may directly send the interval time to the session management entity, or may send the interval time to the session management entity through the second network device, which is not specifically limited in this embodiment of the present application.
  • the first network device is a network data analysis function entity
  • the network data analysis function entity may send the interval time to the session management entity through the policy control entity.
  • the policy control entity sending the interval time to the session management entity includes: the policy control entity sends the first charging policy rule to the session management entity, the first accounting Fee policy rules include interval time.
  • the session management entity receiving the interval time from the first network device includes: the session management entity receiving the first charging policy rule from the first network device.
  • the service scheduling method provided in the embodiment of the present application may further include: the session management entity according to the first charging policy The rule creates the QoS Flow corresponding to the first service, and binds the first charging policy rule to the QoS Flow corresponding to the created first service. That is, in this solution, when the first charging policy rule includes the interval time, the session management entity binds the first charging policy rule to the QoS Flow corresponding to the first service created according to the first charging policy rule.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • the interval time may be a binding parameter in the first charging policy rule.
  • the binding parameters reference may be made to the preamble part of the specific implementation manner, which will not be repeated here.
  • the service scheduling method provided in this embodiment of the present application may further include: the session management entity determines an existing charging policy bound by the QoS Flow. In the rule, whether there is a charging policy rule whose binding parameter is the same as the binding parameter of the first charging policy rule; if so, the session management entity binds the first charging policy rule to the existing QoS Flow; or, If it does not exist, the session management entity creates the QoS Flow corresponding to the first service according to the first charging policy rule, and binds the first charging policy rule to the QoS Flow corresponding to the created first service.
  • the session management entity when the binding parameter in the first charging policy rule includes the interval time, if there is a difference between the binding parameter and the first charging policy rule in the existing charging policy rule bound by QoS Flow, the session management entity binds the first charging policy rule to the existing QoS Flow; otherwise, the session management entity binds the first charging policy rule to the first charging policy rule according to the first charging policy rule.
  • the QoS Flow corresponding to the created first service.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • the first service is a service of QoS flow granularity as an example for description.
  • the policy control entity may also send the interval time to the session management entity in other ways.
  • the interval time is carried in the session-related policy information sent by the policy control entity to the session management entity. This application implements The example does not specifically limit this.
  • the session management entity can obtain the interval time. Further, the session management entity can send the interval time to the access network device, so that the access network device can use the start time and the interval time between the start time and the time when the terminal device sends the uplink data packet of the first service. , the scheduling of the uplink data packets of the first service is performed, thus ensuring that the access network equipment can perform service scheduling more efficiently and in a timely manner, such as scheduling of delay-sensitive services.
  • the above steps S1003-S1004 are only exemplary to provide an implementation manner of obtaining the interval time of the session management entity.
  • the session management entity can also obtain the interval time in other ways, for example, the session management entity can obtain the interval time according to local configuration (such as the data network name (DNN) where the current session is located) and/or a single network slice of the network slice where the current session is located.
  • the selection assistance information (single network slice selection assistance information, S-NSSAI)) determines the interval time, which is not specifically limited in this embodiment of the present application.
  • the actions of the session management entity in the above steps S1001 to S1004 may be executed by the processor 901 in the communication device 900 shown in FIG. 9 by calling the application code stored in the memory 903 to instruct the session management entity to execute.
  • the action of the access network device can be performed by the processor 901 in the communication apparatus 900 shown in FIG. 9 calling the application program code stored in the memory 903 to instruct the access network device to execute, the actions of the first network device in the above steps S1001 to S1004
  • the processor 901 in the communication apparatus 900 shown in FIG. 9 may call the application code stored in the memory 903 to instruct the first network device to execute, which is not limited in this embodiment.
  • the session management entity sends first indication information to an access network device.
  • the access network device receives the first indication information from the session management entity.
  • the first indication information is used to indicate that the data transmission interval of the first service is fixed.
  • the first indication information may be explicit indication information.
  • a bit is defined, and the bit value is "1" to indicate that the data transmission interval of the first service is fixed, or the bit value of "0" indicates that the data transmission interval of the first service is fixed.
  • the first indication information may be implicit indication information.
  • the first indication information may be a service indication with a fixed data transmission interval, such as an EtherCAT indication, an interactive service indication, or an XR service indication. Specific restrictions.
  • the access network device determines the interval time according to the first indication information. For the description of the interval time, reference may be made to the embodiment shown in FIG. 10 , which will not be repeated here.
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service.
  • Step S1202 includes: the access network device obtains at least one set of time information according to the first indication information, and each set of time information in the at least one set of time information includes the time when the terminal device receives the downlink data packet of the first service and the time when the terminal device sends the downlink data packet.
  • the starting time point is the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device.
  • Step S1202 includes: the access network device obtains at least one set of time information according to the first indication information, and each set of time information in the at least one set of time information includes the time when the access network device sends the downlink data packet of the first service to the terminal device and the time when the terminal device sends the uplink data packet corresponding to the downlink data packet of the first service; the access network device determines, according to at least one set of time information, the downlink corresponding to the uplink data packet of the first service sent from the access network device to the terminal device The time between the time of the data packet and the time when the terminal device sends the uplink data packet of the first service.
  • the access network device may send the downlink data packet of the first service to the terminal device according to the time at which the multiple groups of access network devices send the downlink data packet of the first service and the uplink data corresponding to the downlink data packet of the first service sent by the terminal device.
  • the time of the package is learned from the interval time.
  • the access network device performs scheduling of uplink data packets of the first service according to the start time and the interval time.
  • step S1203 For the specific implementation of step S1203, reference may be made to step S1202 in the embodiment described in FIG. 10, and details are not described herein again.
  • the access network device can know that the data transmission interval of the first service is fixed, and then the time between the access network device determining the start time and the time when the terminal device sends the uplink data packet of the first service After the interval time, the access network device can schedule the uplink data packets of the first service according to the start time and the interval time, thus ensuring that the access network device can schedule services more efficiently and in a timely manner, such as time delay Scheduling of sensitive business.
  • the following exemplarily provides an implementation manner for the session management entity to obtain the first indication information.
  • the service scheduling method provided by this embodiment of the present application further includes the following steps:
  • the policy control entity sends second indication information to the session management entity.
  • the session management entity receives the second indication information from the policy control entity.
  • the second indication information is used to indicate that the data transmission interval of the first service is fixed.
  • the second indication information may be explicit indication information.
  • a bit is defined, and the bit value is "1" to indicate that the data transmission interval of the first service is fixed, or the bit value of "0" indicates that the data transmission interval of the first service is fixed.
  • the second indication information may be implicit indication information.
  • the second indication information may be a service indication with a fixed data transmission interval, such as an EtherCAT indication, an interactive service indication, or an XR service indication. Specific restrictions.
  • sending the second indication information to the session management entity by the policy control entity includes: the policy control entity sends the second charging policy rule to the session management entity, and the second charging policy rule includes the second indication information.
  • the session management entity receiving the second indication information from the policy control entity includes: the session management entity receives the second charging policy rule from the policy control entity.
  • the service scheduling method provided in the embodiment of the present application may further include: the session management entity according to the second charging policy rule. Create the QoS Flow corresponding to the first service, and bind the second charging policy rule to the QoS Flow corresponding to the created first service. That is, in this solution, when the second charging policy rule includes the second indication information, the session management entity binds the first charging policy rule to the QoS corresponding to the first service created according to the first charging policy rule Flow.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • the second indication information may be a binding parameter in the second charging policy rule.
  • binding parameters For the related description of the binding parameters, reference may be made to the preamble part of the specific implementation manner, which will not be repeated here.
  • the service scheduling method provided in this embodiment of the present application may further include: the session management entity determines the existing QoS Flow binding In the charging policy rule, whether there is a charging policy rule whose binding parameter is the same as the binding parameter of the second charging policy rule;
  • the session management entity binds the second charging policy rule to the existing QoS Flow; or, if it does not exist, the session management entity creates the QoS Flow corresponding to the first service according to the second charging policy rule, and sets the The second charging policy rule is bound to the QoS Flow corresponding to the created first service.
  • the session management entity binds the second charging policy rule to the existing QoS Flow; otherwise, the session management entity binds the second charging policy rule to the charging policy rule according to the second charging policy.
  • the QoS Flow corresponding to the first service created by the policy rule.
  • the access network device cannot identify the relevant rules, so it cannot Optimizing the scheduling of access network equipment or leading to wrong scheduling. Based on this solution, the problem of untimely scheduling that may be caused by binding the first service and other services to the same QoS Flow can be avoided, further ensuring that the access network device schedules the first service in a more efficient and timely manner.
  • the first service is a service of QoS flow granularity as an example for description.
  • the policy control entity may also send the second indication information to the session management entity in other ways, for example, the second indication information is carried in the session-related policy information sent by the policy control entity to the session management entity , which is not specifically limited in the embodiments of the present application.
  • the session management entity determines the first indication information according to the second indication information.
  • the second indication information and the first indication information may be the same or different, which is not specifically limited in this embodiment of the present application.
  • the session management entity may acquire the first indication information. Further, the session management entity may send the first indication information to the access network device, so that the access network device learns that the data transmission interval of the first service is fixed according to the first indication information.
  • steps S1204-S1205 are only exemplary to provide an implementation manner for the session management entity to obtain the first indication information.
  • the session management entity may also obtain the first indication information in other ways, for example, the session management entity determines the first indication information or the session management entity according to local configuration (such as the DNN where the current session is located and/or the S-NSSAI where the current session is located)
  • the first indication information from other network elements or devices before the policy control entity is received, which is not specifically limited in this embodiment of the present application.
  • the actions of the session management entity in the above steps S1201 to S1205 may be executed by the processor 901 in the communication device 900 shown in FIG. 9 by calling the application code stored in the memory 903 to instruct the session management entity to execute.
  • the action of the access network device can be executed by the processor 901 in the communication apparatus 900 shown in FIG. 9 by calling the application code stored in the memory 903 to instruct the access network device to execute, and the actions of the policy control entity in the above steps S1201 to S1205 can be
  • the processor 901 in the communication device 900 shown in FIG. 9 invokes the application code stored in the memory 903 to instruct the policy control entity to execute, which is not limited in this embodiment.
  • the service scheduling method described in Fig. 10 or Fig. 12 will be exemplarily described below by taking the communication system described in Fig. 6 to Fig. 8 applied to the 5G network shown in Fig. 5a or Fig. 5b as an example.
  • a service scheduling method provided by the embodiment of the present application includes the following steps:
  • the PCF After acquiring the interval time, the PCF sends the interval time to the SMF. Accordingly, the SMF receives the interval time from the PCF.
  • the manner in which the PCF acquires the interval time may be determined by the PCF itself, or the PCF receives the interval time from the NWDAF or the AF, which is not specifically limited in this embodiment of the present application.
  • the PCF or the NWDAF determines the interval time reference may be made to the manner in which the first network device determines the interval time in step S1003 of the embodiment shown in FIG. 10 , which will not be repeated in this embodiment of the present application.
  • the interval time may be carried in the PCC rule sent by the PCF to the SMF.
  • the SMF after receiving the PCC rule from the PCF, the SMF can create a QoS Flow corresponding to the first service according to the PCC rule, and bind the PCC rule to the created QoS Flow corresponding to the first service. . That is, in this solution, when the PCC rule includes the interval time, the SMF binds the PCC rule to the QoS Flow corresponding to the first service created according to the PCC rule.
  • the embodiment shown in FIG. 10 which will not be repeated here.
  • the interval time may be used as a binding parameter in the PCC rule.
  • binding parameters reference may be made to the preamble part of the specific implementation manner, which will not be repeated here.
  • the SMF can determine whether there is a binding parameter and the PCC rule in the PCC rule bound by the QoS Flow.
  • the binding parameters are the same as the PCC rules.
  • the processing method in the case where there is a PCC rule with the same binding parameters as the binding parameters of the PCC rule or no PCC rule with the same binding parameters as the PCC rule can refer to the description in FIG. 10 The relevant descriptions in the embodiments are not repeated here.
  • the SMF may also send an acknowledgement message to the PCF, which is not specifically limited in this embodiment of the present application.
  • the first service is a service of QoS flow granularity as an example for description.
  • the PCF can also send the interval time to the SMF in other ways.
  • the interval time is carried in the PDU Session related policy information (PDU Session related policy information) sent by the PCF to the SMF body.
  • PDU Session related policy information PDU Session related policy information
  • the SMF sends the interval time to the RAN device. Accordingly, the RAN device receives the interval time from the SMF.
  • the SMF may send the interval time as a parameter of the QoS attribute to the RAN device, which is not specifically limited in the embodiment of the present application.
  • the RAN device performs scheduling of uplink data packets of the first service according to the start time and the interval time.
  • step S1303 For the specific implementation of step S1303, reference may be made to step S1002 in the embodiment described in FIG. 10 , and details are not described herein again.
  • the actions of the SMF in the above steps S1301 to S1303 can be executed by the processor 901 in the communication apparatus 900 shown in FIG. 9 by calling the application code stored in the memory 903 to instruct the SMF to execute, and the actions of the RAN device in the above steps S1301 to S1303
  • the processor 901 in the communication apparatus 900 shown in FIG. 9 may call the application code stored in the memory 903 to instruct the RAN device to execute, and the actions of the PCF in the above steps S1301 to S1303 may be executed by the communication apparatus 900 shown in FIG. 9 .
  • the processor 901 calls the application code stored in the memory 903 to instruct the PCF to execute, which is not limited in this embodiment.
  • another service scheduling method includes the following steps:
  • the NWDAF determines the interval time, it sends the interval time to the SMF. Accordingly, the SMF receives the interval time from the NWDAF.
  • interval time and the manner in which the NWDAF determines the interval time may refer to the embodiment described in FIG. 10 , which will not be repeated here.
  • the SMF may also send an acknowledgement message to the NWDAF, which is not specifically limited in this embodiment of the present application.
  • the SMF sends the interval time to the RAN device. Accordingly, the RAN device receives the interval time from the SMF.
  • the SMF may send the interval time as a parameter of the QoS attribute to the RAN device, which is not specifically limited in the embodiment of the present application.
  • the RAN device performs scheduling of uplink data packets of the first service according to the start time and the interval time.
  • step S1403 For the specific implementation of step S1403, reference may be made to step S1002 in the embodiment described in FIG. 10, and details are not described herein again.
  • the NWDAF can also interact with the SMF through the PCF, that is, the embodiment of the present application can also take the first network device as the NWDAF and the second network device as the PCF as an example, the specific implementation is the same as that shown in FIG. 14 .
  • the described embodiments are similar, and are not repeated here.
  • the actions of the SMF in the above steps S1401 to S1403 can be executed by the processor 901 in the communication apparatus 900 shown in FIG. 9 by calling the application code stored in the memory 903 to instruct the SMF to execute, and the actions of the RAN device in the above steps S1401 to S1403
  • the application code stored in the memory 903 may be called by the processor 901 in the communication apparatus 900 shown in FIG. 9 to instruct the RAN device to execute, and the actions of the NWDAF in the above steps S1401 to S1403 may be executed by the communication apparatus 900 shown in FIG. 9 .
  • the processor 901 calls the application code stored in the memory 903 to instruct the NWDAF to execute, which is not limited in this embodiment.
  • the business scheduling method includes the following steps:
  • the PCF sends the second indication information to the SMF.
  • the SMF receives the second indication information from the PCF.
  • the second indication information is used to indicate that the data transmission interval of the first service is fixed, and the related description may refer to the embodiment shown in FIG. 12 , which will not be repeated here.
  • the PCF may acquire the service type from the AF, which is not specifically limited in this embodiment of the present application.
  • the second indication information may be carried in the PCC rule sent by the PCF to the SMF.
  • the SMF can create a QoS Flow corresponding to the first service according to the PCC rule, and bind the PCC rule to the created QoS Flow corresponding to the first service. That is, in this solution, when the PCC rule includes the second indication information, the SMF binds the PCC rule to the QoS Flow corresponding to the first service created according to the PCC rule.
  • the PCC rule includes the second indication information
  • the SMF binds the PCC rule to the QoS Flow corresponding to the first service created according to the PCC rule.
  • the second indication information may be used as a binding parameter in the PCC rule.
  • binding parameters reference may be made to the preamble part of the specific implementation manner, which will not be repeated here.
  • the SMF can determine whether there is a binding parameter in the PCC rule bound by the existing QoS Flow that is related to the PCC rule.
  • the binding parameters of the PCC rules are the same as the PCC rules.
  • the processing method in the case where there is a PCC rule with the same binding parameters as the binding parameters of the PCC rule or no PCC rule with the same binding parameters as the PCC rule can refer to FIG. 12 . The relevant descriptions in the embodiments are not repeated here.
  • the SMF may also send a confirmation message to the PCF, which is not specifically limited in this embodiment of the present application.
  • the first service is a service of QoS flow granularity as an example for description.
  • the PCF can also send the second indication information to the SMF in other ways.
  • the second indication information is carried in the PDU Session related policy information sent by the PCF to the SMF body. , the embodiments of the present application do not specifically limit this.
  • the SMF determines the first indication information according to the second indication information.
  • the first indication information is used to indicate that the data transmission interval of the first service is fixed, and the related description may refer to the embodiment shown in FIG. 12 , which will not be repeated here.
  • step S1502 For the related description of step S1502, reference may be made to step S1205 in the embodiment shown in FIG. 12, and details are not repeated here.
  • the SMF sends the first indication information to the RAN device.
  • the RAN device receives the first indication information from the SMF.
  • the RAN device determines the interval time according to the first indication information.
  • the description of the interval time and the manner in which the RAN device determines the interval time according to the first indication information may refer to the embodiment shown in FIG. 10 , and details are not repeated here.
  • the RAN device performs scheduling of uplink data packets of the first service according to the start time and the interval time.
  • step S1505 For the specific implementation of step S1505, reference may be made to step S1002 in the embodiment described in FIG. 10 , and details are not repeated here.
  • the actions of the SMF in the above steps S1501 to S1505 can be executed by the processor 901 in the communication apparatus 900 shown in FIG. 9 by calling the application code stored in the memory 903 to instruct the SMF to execute, and the actions of the RAN device in the above steps S1501 to S1505
  • the application code stored in the memory 903 may be called by the processor 901 in the communication apparatus 900 shown in FIG. 9 to instruct the RAN device to execute, and the actions of the PCF in the above steps S1501 to S1505 may be executed by the communication apparatus 900 shown in FIG. 9 .
  • the processor 901 calls the application code stored in the memory 903 to instruct the PCF to execute, which is not limited in this embodiment.
  • the methods and/or steps implemented by the session management entity may also be implemented by components (such as chips or circuits) that can be used in the session management entity; the methods and/or steps implemented by the access network device and/or steps may also be implemented by components (such as chips or circuits) that can be used for access network equipment; methods and/or steps implemented by first network equipment or policy control entities may also be implemented by first network equipment or A component (eg chip or circuit) implementation of the policy control entity.
  • an embodiment of the present application further provides a communication device, and the communication device may be the access network device in the above method embodiment, or a device including the above access network device, or a component that can be used for the access network device; Alternatively, the communication device may be the session management entity in the above method embodiments, or a device including the above session management entity, or a component usable for the session management entity; or, the communication device may be the first one in the above method embodiments. A network device, or a device including the above-mentioned first network device, or a component usable in the first network device.
  • the communication apparatus includes corresponding hardware structures and/or software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • FIG. 16 shows a schematic structural diagram of a communication device 160 .
  • the communication device 160 includes a transceiver module 1601 and a processing module 1602 .
  • the transceiver module 1601 may also be called a transceiver unit to implement a transceiver function, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the transceiver module 1601 is used to receive the interval time from the session management entity. The time of the downlink data packet corresponding to the uplink data packet of the service or the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device.
  • the processing module 1602 is configured to perform scheduling of uplink data packets of the first service according to the start time and the interval time.
  • the processing module 1602 is specifically configured to: perform scheduling of uplink data packets of the first service at the first time according to the start time and the interval time.
  • the first time is the time at the interval time after the start time; or, the first time is the time in the first time interval, and the first time interval includes the time at the interval time after the start time.
  • the processing module 1602 is specifically configured to: receive the ACK data packet of the downlink data packet of the first service from the terminal device through the transceiver module 1601;
  • the second time is the time when the interval after the start time is less than or equal to (interval time-transmission time of the ACK data packet between the terminal device and the access network device).
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service; the processing module 1602 is further configured to determine according to the time when the access network device sends the downlink data packet and the air interface delay The time when the terminal device receives the downlink data packet.
  • the transceiver module 1601 is configured to receive the first indication information from the session management entity.
  • the processing module 1602 is configured to determine the interval time according to the first indication information, the interval time is the time from the start time to the time when the terminal device sends the uplink data packet of the first service, and the start time is the time when the terminal device receives the first service.
  • the processing module 1602 is further configured to perform scheduling of uplink data packets of the first service according to the start time and the interval time.
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service.
  • the processing module 1602 is configured to determine the interval time according to the first indication information, including: obtaining at least one group of time information according to the first indication information, and each group of time information in the at least one group of time information includes that the terminal device receives the first service The time of the downlink data packet and the time when the terminal device sends the uplink data packet corresponding to the downlink data packet of the first service; the interval time is determined according to at least one set of time information.
  • the starting time point is the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device; the processing module 1602 is configured to determine the interval time according to the first indication information, including: Acquire at least one set of time information according to the first indication information, where each set of time information in the at least one set of time information includes the time when the access network device sends the downlink data packet of the first service to the terminal device and the time when the terminal device sends the first service.
  • the time of the uplink data packet corresponding to the downlink data packet; the interval time is determined according to at least one set of time information.
  • the processing module 1602 is configured to perform scheduling of the uplink data packets of the first service according to the start time and the interval time, including: according to the start time and the interval time, execute the uplink data of the first service at the first time Packet scheduling; wherein, the first time is the time at the interval time after the start time; or, the first time is the time in the first time interval, and the first time interval includes the time at the interval time after the start time.
  • the processing module 1602 is configured to perform scheduling of the uplink data packets of the first service according to the start time and the interval time, including: receiving, through the transceiver module 1601, an acknowledgement ACK of the downlink data packets of the first service from the terminal device Data packets; according to the start time and interval time, perform the scheduling of the uplink data packets of the first service at the second time, and the second time is that the interval after the start time is less than or equal to (interval time - ACK data packets are sent between the terminal device and the receiving device). transmission time between connected devices).
  • the start time is the time when the terminal device receives the downlink data packet corresponding to the uplink data packet of the first service; the processing module 1602 is further configured to determine according to the time when the access network device sends the downlink data packet and the air interface delay The time when the terminal device receives the downlink data packet.
  • the processing module 1602 is used to determine the interval time, the interval time is the time from the start time to the time when the terminal device sends the uplink data packet of the first service, and the start time is the time when the terminal device receives the uplink data packet of the first service The time of the corresponding downlink data packet or the time when the access network device sends the downlink data packet corresponding to the uplink data packet of the first service to the terminal device.
  • the transceiver module 1601 is configured to send an interval time to the second network device, where the interval time is used to perform scheduling of uplink data packets of the first service.
  • the first network device is a network data analysis function entity
  • the second network device is a policy control entity or a session management entity.
  • the processing module 1602 is specifically configured to: determine the interval according to at least one of the following information: the type of the first service from the policy control entity or the application function entity or the service description of the first service, the first service from the terminal device The packet sending frequency of the uplink data packet or the packet receiving frequency of the downlink data packet corresponding to the uplink data packet of the first service, the processing time of the terminal device from the terminal device to the downlink data packet or the time when the terminal device receives the downlink data packet, from the terminal device The device type of the terminal device of the device or the session management entity or the application function entity, or the flow identifier of the QoS Flow corresponding to the first service from the access network device.
  • the first network device is a policy control entity
  • the second network device is a session management entity
  • the processing module 1602 is specifically configured to: determine the interval time according to at least one of the following information: the type of the first service from the application function entity or the service description of the first service, and the duration of the uplink data packet of the first service from the terminal device.
  • the packet sending frequency or the receiving frequency of the downlink data packet corresponding to the uplink data packet of the first service, the processing time of the downlink data packet by the terminal device from the terminal device or the time when the terminal device receives the downlink data packet, from the terminal device or session management The device type of the terminal device of the entity or the application function entity, or the flow identifier of the QoS Flow corresponding to the first service from the access network device.
  • the transceiver module 1601 is specifically configured to: send the first charging policy rule to the session management entity, where the first charging policy rule includes the interval time.
  • the communication apparatus 160 is presented in the form of dividing each functional module in an integrated manner.
  • Module herein may refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and/or other device that may provide the functions described above.
  • the communication device 160 may take the form of the communication device 900 shown in FIG. 8 .
  • the processor 901 in the communication apparatus 900 shown in FIG. 8 may invoke the computer execution instructions stored in the memory 903 to cause the communication apparatus 900 to execute the service scheduling method in the foregoing method embodiment.
  • the functions/implementation process of the transceiver module 1601 and the processing module 1602 in FIG. 16 can be implemented by the processor 901 in the communication apparatus 900 shown in FIG. 8 calling the computer execution instructions stored in the memory 903 .
  • the function/implementation process of the processing module 1602 in FIG. 16 can be implemented by the processor 901 in the communication device 900 shown in FIG. 8 calling the computer-executed instructions stored in the memory 903, and the function of the transceiver module 1601 in FIG. 16 can be implemented.
  • the implementation process can be implemented through the communication interface 904 in the communication device 900 shown in FIG. 8 .
  • the communication device 160 provided in this embodiment can execute the above-mentioned service scheduling method, the technical effect that can be obtained can be referred to the above-mentioned method embodiment, and details are not repeated here.
  • one or more of the above modules or units may be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built into a SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the internal processing of the processor may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (Programmable Logic Device) , or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD Programmable Logic Device
  • the hardware can be CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, Any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • DSP digital signal processing
  • MCU microcontroller unit
  • ASIC any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • an embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled to the memory through the interface, and when the at least one processor executes the computer program or instruction in the memory , the method in any of the above method embodiments is executed.
  • the communication device further includes a memory.
  • the chip system may be composed of chips, or may include chips and other discrete devices, which are not specifically limited in this embodiment of the present application.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供业务调度方法、装置及系统，用于保证接入网设备更高效和及时地进行业务调度。方法包括：接入网设备接收来自会话管理实体的间隔时间，该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间或者该接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；接入网设备根据该起始时间和该间隔时间，执行该第一业务的上行数据包的调度。

Description

业务调度方法、装置及系统 技术领域
本申请涉及通信技术领域，尤其涉及业务调度方法、装置及系统。
背景技术
以太网控制自动化技术(Ethernet for Control Automation Technology，EtherCAT)是由德国BECKHOFF自动化公司于2003年提出的实时工业以太网技术。由于它具有高速、高准确性、时延敏感等特点，因此应用越来越广泛。
现有的第五代系统(5th generation system，5GS)中，对于时延敏感通信(time sensitive communication，TSC)业务，为了传输此类业务，无线接入网(radio access network，RAN)设备需要感知业务的一些特性，并根据这些特性进行调度，以此来保证RAN设备更高效和及时地调度时延敏感业务。这些特性被称为TSC辅助信息(TSC assistance information，TSCAI)。其中，TSCAI中包括TSC业务的流方向、周期性和突发到达时间。具体地，集中控制点将生成TSCAI的信息发送给网络侧，网络侧根据生成TSCAI的信息生成TSCAI。换言之，集中控制点可以控制业务流的到达时间窗口。
然而，EtherCAT业务不一定是周期性的，也无法基于集中控制点控制业务流的到达时间窗口，因此现有的5GS保证RAN设备更高效和及时地调度时延敏感业务的方法无法用于EtherCAT业务。进一步的，若现有的5GS保证RAN设备更高效和及时地调度时延敏感业务的方法无法用于EtherCAT业务，由于上行传输情况下，5GS不知道何时有EtherCAT业务的上行数据，为了保证网络容量又不能一直预留资源，因此5GS不一定能够及时调度EtherCAT业务的数据。若终端设备错过一次调度机会，下次调度则会大概率超过EtherCAT业务的时延要求。
因此，如何保证RAN设备更高效和及时地进行业务调度，例如保证RAN设备及时地调度EtherCAT等非周期性时延敏感业务，是目前亟待解决的问题。
发明内容
本申请实施例提供业务调度方法、装置及系统，用于保证接入网设备更高效和及时地进行业务调度。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种业务调度方法，执行该业务调度方法的通信装置可以为接入网设备；也可以为应用于接入网设备中的模块，例如芯片或芯片系统。下面以执行主体为接入网设备为例进行描述。接入网设备接收来自会话管理实体的间隔时间，该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间或者该接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；接入网设备根据该起始时间和该间隔时间，执行该第一业务的上行数据包的调度。基于该方案，接入网设备可以根据起始时间以及起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间，执行第一业务的上行数据包的调度，因此保证了接 入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。具体地，例如基于本方案，可以避免第一业务为时延敏感业务时，终端设备错过一次调度机会，下次调度则会大概率超过第一业务的时延要求的问题，或者可以避免第一业务为时延敏感业务时，接入网设备无法执行正确调度的问题。
结合上述第一方面，在一种可能的实现方式中，接入网设备根据起始时间和间隔时间，执行第一业务的上行数据包的调度，包括：接入网设备根据起始时间和间隔时间，在第一时间执行第一业务的上行数据包的调度；其中，该第一时间为该起始时间之后间隔该间隔时间的时间；或者，该第一时间为第一时间区间内的时间，该第一时间区间内包括该起始时间之后间隔该间隔时间的时间。换言之，本申请实施例中，接入网设备可以在确定的时间(即第一时间)执行第一业务的上行数据包的调度，因此能够保证时延敏感业务的及时调度。
结合上述第一方面，在一种可能的实现方式中，接入网设备根据该起始时间和该间隔时间，执行该第一业务的上行数据包的调度，包括：接入网设备接收来自该终端设备的该第一业务的下行数据包的确认ACK数据包；接入网设备根据该起始时间和该间隔时间，在第二时间执行该第一业务的上行数据包的调度，该第二时间为该起始时间之后间隔小于或者等于(该间隔时间-该ACK数据包在该终端设备和该接入网设备之间的传输时间)的时间。本申请实施例提供了存在ACK数据包的场景下，执行该第一业务的上行数据包的调度的时间点的确定方式，使得存在ACK数据包的场景下，接入网设备也可以在确定的时间(即第二时间)执行第一业务的上行数据包的调度，因此能够保证时延敏感业务的及时调度。
结合上述第一方面，在一种可能的实现方式中，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间，该方法还包括：接入网设备根据该接入网设备发送该下行数据包的时间以及空口时延确定该终端设备接收到该下行数据包的时间。基于该方案，可以确定出终端设备接收到第一业务的下行数据包的时间。
第二方面，提供了一种业务调度方法，执行该业务调度方法的通信装置可以为第一网络设备；也可以为应用于第一网络设备中的模块，例如芯片或芯片系统。下面以执行主体为第一网络设备为例进行描述。第一网络设备确定间隔时间，该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间或者接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；第一网络设备向第二网络设备发送该间隔时间，其中，该间隔时间用于执行该第一业务的上行数据包的调度。基于该方案，第二网络设备可以获得起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间。进而，第二网络设备向接入网设备发送间隔时间之后，接入网设备可以根据起始时间以及起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。相关示例可参考上述第一方面，在此不再赘述。
结合上述第二方面，在一种可能的实现方式中，第一网络设备为网络数据分析功能实体，第二网络设备为策略控制实体或者会话管理实体。
结合上述第二方面，在一种可能的实现方式中，第一网络设备确定该间隔时间，包括：第一网络设备根据以下至少一个信息确定该间隔时间：来自策略控制实体或应用功能实体的该第一业务的类型或该第一业务的业务描述，来自该终端设备的该第一业务的上行数据包的发包频率或该第一业务的上行数据包对应的下行数据包的收包频率，来自该终端设备的该终端设备对该下行数据包的处理时间或者该终端设备接收到该下行数据包的时间，来自该终端设备或者会话管理实体或者该应用功能实体的该终端设备的设备类型，或者来自该接入网设备的该第一业务对应的服务质量流QoS Flow的流标识。基于该方案，第一网络设备可以获得起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间。
结合上述第二方面，在一种可能的实现方式中，第一网络设备为该策略控制实体，第二网络设备为会话管理实体。
结合上述第二方面，在一种可能的实现方式中，第一网络设备确定该间隔时间，包括：第一网络设备根据以下至少一个信息确定该间隔时间：来自应用功能实体的该第一业务的类型或该第一业务的业务描述，来自该终端设备的该第一业务的上行数据包的发包频率或该第一业务的上行数据包对应的下行数据包的收包频率，来自该终端设备的该终端设备对该下行数据包的处理时间或者该终端设备接收到该下行数据包的时间，来自该终端设备或者会话管理实体或者该应用功能实体的该终端设备的设备类型，或者来自该接入网设备的该第一业务对应的QoS Flow的流标识。基于该方案，第一网络设备可以获得起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间。
结合上述第二方面，在一种可能的实现方式中，该第一网络设备为该策略控制实体，该第二网络设备为该会话管理实体；该第一网络设备向第二网络设备发送该间隔时间，包括：策略控制实体向该会话管理实体发送第一计费策略规则，该第一计费策略规则包括该间隔时间。
结合上述第二方面，在一种可能的实现方式中，该间隔时间为该第一计费策略规则中的绑定参数。基于该方案，可以使得会话管理实体确定已有QoS Flow绑定的计费策略规则中，是否存在绑定参数与第一计费策略规则的绑定参数均相同的计费策略规则；若存在，会话管理实体将第一计费策略规则绑定至已有QoS Flow；或者，若不存在，会话管理实体根据第一计费策略规则创建第一业务对应的QoS Flow，并将第一计费策略规则绑定至创建的第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
第三方面，提供了一种业务调度方法，执行该业务调度方法的通信装置可以为会话管理实体；也可以为应用于会话管理实体中的模块，例如芯片或芯片系统。下面以执行主体为会话管理实体为例进行描述。会话管理实体接收间隔时间，该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，该起始时间为 该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间或者该接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；会话管理实体向该接入网设备发送该间隔时间，其中，该间隔时间用于执行该第一业务的上行数据包的调度。基于该方案，接入网设备可以获得起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间，进而，接入网设备可以根据起始时间和间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。相关示例可参考上述第一方面，在此不再赘述。
结合上述第三方面，在一种可能的实现方式中，会话管理实体接收间隔时间，包括：会话管理实体接收来自策略控制实体或者该网络数据分析功能实体的该间隔时间。
结合上述第三方面，在一种可能的实现方式中，会话管理实体接收来自策略控制实体的该间隔时间，包括：会话管理实体接收来自策略控制实体的第一计费策略规则，该第一计费策略规则包括该间隔时间。
结合上述第三方面，在一种可能的实现方式中，本申请实施例提供的业务调度方法还包括：会话管理实体根据该第一计费策略规则创建该第一业务对应的服务质量流QoS Flow，并将该第一计费策略规则绑定至创建的该第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
结合上述第三方面，在一种可能的实现方式中，该间隔时间为该第一计费策略规则中的绑定参数，本申请实施例提供的业务调度方法还包括：会话管理实体确定已有QoS Flow绑定的计费策略规则中，是否存在绑定参数与该第一计费策略规则的绑定参数均相同的计费策略规则；若存在，该会话管理实体将该第一计费策略规则绑定至该已有QoS Flow；或者，若不存在，该会话管理实体根据该第一计费策略规则创建该第一业务对应的QoS Flow，并将该第一计费策略规则绑定至创建的该第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
第四方面，提供了一种业务调度方法，执行该业务调度方法的通信装置可以为接入网设备；也可以为应用于接入网设备中的模块，例如芯片或芯片系统。下面以执行主体为接入网设备为例进行描述。接入网设备接收来自会话管理实体的第一指示信息；接入网设备根据该第一指示信息，确定间隔时间，该间隔时间为从起始时间到终端设备发送该第一业务的上行数据包的时间之间的时间，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间或者该接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；接入网设备根据该起始时间和该间隔时间，执行该第一业务的上行数据包的调度。基于该方案，接入网设备可以获 知第一业务的数据传输间隔时间固定，进而在接入网设备确定起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间之后，接入网设备可以根据起始时间和间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。相关示例可参考上述第一方面，在此不再赘述。
结合上述第四方面，在一种可能的实现方式中，第一指示信息用于指示第一业务的数据传输间隔时间固定。
结合上述第四方面，在一种可能的实现方式中，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间；接入网设备根据该第一指示信息，确定该间隔时间，包括：接入网设备根据该第一指示信息，获取至少一组时间信息，该至少一组时间信息中的每组时间信息包括该终端设备接收到该第一业务的下行数据包的时间和该终端设备发送该第一业务的下行数据包对应的上行数据包的时间；接入网设备根据该至少一组时间信息，确定该间隔时间。基于该方案，接入网设备可以自学习得到起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间。
结合上述第四方面，在一种可能的实现方式中，该起始时间点为该接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；接入网设备根据该第一指示信息，确定该间隔时间，包括：接入网设备根据该第一指示信息，获取至少一组时间信息，该至少一组时间信息中的每组时间信息包括该接入网设备向该终端设备发送该第一业务的下行数据包的时间和该终端设备发送该第一业务的下行数据包对应的上行数据包的时间；接入网设备根据该至少一组时间信息，确定该间隔时间。基于该方案，接入网设备可以自学习得到起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间。
结合上述第四方面，在一种可能的实现方式中，接入网设备根据该起始时间和该间隔时间，执行该第一业务的上行数据包的调度，包括：接入网设备根据该起始时间和该间隔时间，在第一时间执行该第一业务的上行数据包的调度；其中，该第一时间为该起始时间之后间隔该间隔时间的时间；或者，该第一时间为第一时间区间内的时间，该第一时间区间内包括该起始时间之后间隔该间隔时间的时间。换言之，本申请实施例中，接入网设备可以在确定的时间(即第一时间)执行第一业务的上行数据包的调度，因此能够保证时延敏感业务的及时调度。
结合上述第四方面，在一种可能的实现方式中，接入网设备根据该起始时间和该间隔时间，执行该第一业务的上行数据包的调度，包括：接入网设备接收来自该终端设备的该第一业务的下行数据包的确认ACK数据包；接入网设备根据该起始时间和该间隔时间，在第二时间执行该第一业务的上行数据包的调度，该第二时间为该起始时间之后间隔小于或者等于(该间隔时间-该ACK数据包在该终端设备和该接入网设备之间的传输时间)的时间。本申请实施例提供了存在ACK数据包的场景下，执行该第一业务的上行数据包的调度的时间点的确定方式，使得存在ACK数据包的场景下，接入网设备也可以在确定的时间(即第二时间)执行第一业务的上行数据包的调度，因此能够保证时延敏感业务的及时调度。
结合上述第四方面，在一种可能的实现方式中，该起始时间为该终端设备接收到 该第一业务的上行数据包对应的下行数据包的时间，本申请实施例提供的业务调度方法还包括：该接入网设备根据该接入网设备发送该下行数据包的时间以及空口时延确定该终端设备接收到该下行数据包的时间。基于该方案，可以确定出终端设备接收到第一业务的下行数据包的时间。
第五方面，提供了一种业务调度方法，执行该业务调度方法的通信装置可以为会话管理实体；也可以为应用于会话管理实体中的模块，例如芯片或芯片系统。下面以执行主体为会话管理实体为例进行描述。会话管理实体接收来自策略控制实体的第二指示信息，该第二指示信息用于第一业务的数据传输间隔时间固定，该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，该起始时间为该终端设备接收到该第一业务的上行数据包对应的下行数据包的时间或者该接入网设备向该终端设备发送该第一业务的上行数据包对应的下行数据包的时间；会话管理实体向该接入网设备发送第一指示信息，该第一指示信息用于指示该第一业务的数据传输间隔时间固定。基于该方案，接入网设备可以获知第一业务的数据传输间隔时间固定，进而在接入网设备确定起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间之后，接入网设备可以根据起始时间和间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。相关示例可参考上述第一方面，在此不再赘述。
结合上述第五方面，在一种可能的实现方式中，第一指示信息用于指示第一业务的数据传输间隔时间固定。
结合上述第五方面，在一种可能的实现方式中，第二指示信息用于指示第一业务的数据传输间隔时间固定。
结合上述第五方面，在一种可能的实现方式中，会话管理实体接收来自策略控制实体的第二指示信息，包括：会话管理实体接收来自策略控制实体的第一计费策略规则，该第一计费策略规则包括该第二指示信息。
结合上述第五方面，在一种可能的实现方式中，本申请实施例提供的业务调度方法还包括：会话管理实体根据该第一计费策略规则创建该第一业务对应的服务质量流QoS Flow，并将该第一计费策略规则绑定至创建的该第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
结合上述第五方面，在一种可能的实现方式中，该第二指示信息为该第一计费策略规则中的绑定参数，本申请实施例提供的业务调度方法还包括：会话管理实体确定已有QoS Flow绑定的计费策略规则中，是否存在绑定参数与该第一计费策略规则的绑定参数均相同的计费策略规则；若存在，该会话管理实体将该第一计费策略规则绑定至该已有QoS Flow；或者，若不存在，该会话管理实体根据该第一计费策略规则创建该第一业务对应的QoS Flow，并将该第一计费策略规则绑定至创建的该第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间 的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
结合上述第一方面至第五方面中的任一方面，在一种可能的实现方式中，第一业务包括：以太网控制自动化技术EtherCAT业务、交互式业务或者扩展现实XR业务。
第六方面，提供了一种通信装置用于实现上述方法。该通信装置可以为上述第一方面或第四方面中的接入网设备，或者包含上述接入网设备的装置；或者，该通信装置可以为上述第二方面中的第一网络设备，或者包含上述第一网络设备的装置；或者，该通信装置可以为上述第三方面或第五方面中的会话管理实体，或者包含上述会话管理实体的装置。该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
结合上述第六方面，在一些可能的实现中，该通信装置可以包括处理模块和收发模块。该收发模块，也可以称为收发单元，用以实现上述任一方面及其任意可能的实现方式中的发送和/或接收功能。该收发模块可以由收发电路，收发机，收发器或者通信接口构成。该处理模块，可以用于实现上述任一方面及其任意可能的实现方式中的处理功能。该处理模块例如可以为处理器。
结合上述第六方面，在一些可能的实现中，收发模块包括发送模块和接收模块，分别用于实现上述任一方面及其任意可能的实现方式中的发送和接收功能。
第七方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中的指令之后，根据该指令执行如上述任一方面所述的方法。该通信装置可以为上述第一方面或第四方面中的接入网设备，或者包含上述接入网设备的装置；或者，该通信装置可以为上述第二方面中的第一网络设备，或者包含上述第一网络设备的装置；或者，该通信装置可以为上述第三方面或第五方面中的会话管理实体，或者包含上述会话管理实体的装置。
结合上述第七方面，在一种可能的实现方式中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。
结合上述第七方面，在一种可能的实现方式中，该通信装置为芯片或芯片系统。可选的，该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
第八方面，提供了一种通信装置，包括：处理器和接口电路；接口电路，用于接收计算机程序或指令并传输至处理器；处理器用于执行所述计算机程序或指令，以使该通信装置执执行如上述任一方面所述的方法。
结合上述第八方面，在一种可能的实现方式中，该通信装置为芯片或芯片系统。可选的，该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
其中，第六方面至第十方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面至第五方面中任一方面或任一方面中不同设计方式所带来的技术效果，此处不再赘述。
第十一方面，提供了一种通信系统，该通信系统包括用于执行上述第一方面所述的业务调度方法的接入网设备、以及用于执行上述第三方面所述的业务调度方法的会话管理实体。
结合上述第十一方面，在一种可能的实现方式中，该通信提供还包括用于执行上述第一方面所述的业务调度方法的第一网络设备。
第十二方面，提供了一种通信系统，该通信系统包括用于执行上述第四方面所述的业务调度方法的接入网设备、以及用于执行上述第五方面所述的业务调度方法的会话管理实体。
附图说明
图1为本申请实施例提供的EtherCAT业务的数据传输示意图；
图2为本申请实施例提供的EtherCAT业务的组网示意图一；
图3为本申请实施例提供的EtherCAT业务的组网示意图二；
图4为5G系统提出的基于QoS流的5G QoS模型示意图；
图5a为现有的5G网络的服务化架构示意图；
图5b为图5a对应的基于参考点的5G网络架构示意图；
图5c为LTE系统中帧结构示意图；
图5d为5G系统中帧结构示意图；
图6为本申请实施例提供的通信系统的架构示意图一；
图7为本申请实施例提供的通信系统的架构示意图二；
图8为本申请实施例提供的通信系统的架构示意图三；
图9为本申请实施例提供的通信装置的结构示意图；
图10为本申请实施例提供的一种业务调度方法的流程示意图；
图11a为本申请实施例提供的第一时间区间的示意图一；
图11b为本申请实施例提供的第一时间区间的示意图二；
图11c为本申请实施例提供的第一时间区间的示意图三；
图12为本申请实施例提供的另一种业务调度方法的流程示意图；
图13为本申请实施例提供的又一种业务调度方法的流程示意图；
图14为本申请实施例提供的又一种业务调度方法的流程示意图；
图15为本申请实施例提供的又一种业务调度方法的流程示意图；
图16为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
为方便理解本申请实施例的方案，首先给出相关概念的简要介绍如下：
第一，TSC
TSC是一种支持确定性通信和/或同步通信的高可靠性和可用性的通信服务。它涉 及为分组传输(packet transport)提供延迟、丢失和可靠性的界限(或阈值或限制)等服务质量(quality of service，QoS)特性。在这种情况下，端系统(end systems)和中继/传输节点可以严格同步(比如时钟同步)。
第二，EtherCAT简介：
EtherCAT具有高速、高准确性、时延敏感等特点，支持多种设备连接拓扑结构。其中，EtherCAT使用相同的物理和数据链路层，其从节点使用专用的控制芯片，主节点使用标准的以太网控制器。
EtherCAT中，主节点是唯一允许发送数据帧的节点，子站只能转发数据帧。即，数据帧就像火车一样，从主节点开出，途经各个从节点，将对于从节点的数据放下或者带上，最后回到主节点。每个从节点都有4个端口，所以不会有数据冲突，可以保证业务数据的及时调度。比如，结合图1，数据帧经主节点1发出后，途径从节点1，从节点2，以及从节点3的过程中，将对于各个从节点的数据放下或者带上。然后，数据帧从节点3返回，依次经过从节点2和从节点1之后回到主节点1。其中，从节点1，从节点2，以及从节点3均包括4个端口，数据帧不会产生冲突，可以保证业务数据的及时调度。
需要说明的是，本申请实施例中，主节点可以称为主设备、主站、主EtherCAT设备、主以太网设备、或分布式时钟(distributed clock，DC)主站等，从节点可称为从设备、从站、从EtherCAT设备、从以太网设备、或DC从节点等，在此统一说明，本申请实施例对此不进行限定。
下面结合图2和图3对主节点和从节点的组网模式进行阐述。
示例性地，主节点和从节点的组网模式可以包括直连模式或开放模式等。结合图2，直连模式可以为主节点1与从节点1，从节点2，以及从节点3之间的连接不经过交换机，直接连接。结合图3，开放模式可以为主节点1与从节点1，从节点2，以及从节点3之间的连接经过交换机(switch)，还可以经过段地址从节点(segment address slave device)1。主节点2与从节点4，从节点5，以及从节点6之间的连接经过交换机，还可以经过段地址从节点2。可选地，交换机还可以连接具有其他功能的设备，如通用以太网设备(generic etherment device)，本申请实施例对此不做具体限定。
第三，分组数据单元(packet data unit，PDU)会话：
PDU会话为终端设备与数据网络(data network，DN)之间的一个关联，用于提供一个PDU连接服务。
第四，QoS模型：
在5G系统中，为了保证业务端到端的服务质量，提出了基于QoS流(QoS Flow)的5G QoS模型，如图4所示。该5G QoS模型支持保证比特率(guaranteed bit rate，GBR)的QoS Flow(即GBR QoS Flow)和非保证比特率(non-guaranteed bit rate，non-GBR)的QoS Flow(即non-GBR QoS Flow)。使用同一个QoS Flow控制的数据包接受相同的传输处理(如调度、或准入门限等)。
如图4所示，对于一个终端设备，可以与5G网络建立一个或者多个PDU会话。每个PDU会话中可以建立一个或者多个QoS Flow。一个QoS Flow由一个QoS流标识(QoS Flow identifier，QFI)识别，即QFI在会话中唯一标识一个QoS Flow。其中， 一个PDU会话与RAN设备和用户面功能(user plane function，UPF)之间的一个通用分组无线服务(general packet radio service，GPRS)隧道协议用户面(GPRS tunneling protocol user plane，GTP-U)隧道一一对应；一个QoS Flow对应终端设备和RAN设备之间的一个无线承载，而一个无线承载可以对应一个或多个QoS Flow。
其中，一个QoS Flow为GBR QoS Flow还是non-GBR QoS Flow，由对应的QoS文件(QoS profile)确定。
对于GBR QoS Flow，对应的QoS文件包含以下QoS参数：5G QoS标识(5G QoS identifier，5QI)、分配和预留优先级(allocation and retention priority，ARP)、保证流比特率(guaranteed flow bit rate，GFBR)和最大流比特率(maximum flow bit rate，MFBR)，可选的包含QoS通知控制(QoS notification control，QNC)。具体地，根据QoS文件是否包含QNC可以将GBR QoS Flow分为需要notification control的GRB QoS Flow和不需要notification control的GBR QoS Flow。对于需要notification control的GBR QoS Flow，当RAN设备检测到对应的QoS Flow资源不能被满足时，RAN设备通知会话管理功能(session management function，SMF)该事件。进一步的SMF可以发起QoS Flow删除或者修改流程。对于Non-GBR QoS Flow，对应的QoS文件包含以下QoS参数：5QI和ARP；可选的包含反转QoS属性(reflective QoS attribute，RQA)。
上述QoS参数的定义如下：
5QI是一个标量，用于索引到对应的5G QoS特征。5QI分为标准化的5QI、预配置的5QI和动态分配的5QI。对于标准化的5QI，与一组标准化的5G QoS特征值一一对应；对于预配置的5QI，对应的5G QoS特征值预配置在无线接入网设备(radio access network，RAN)设备上；对于动态分配的5QI，对应的5G QoS特征由核心网设备通过QoS文件发送给RAN设备。
ARP包含优先等级、抢占能力和被抢占能力。
GFBR代表期望提供给GBR QoS Flow(流)的比特率。
MFBR限制提供给GBR QoS Flow的比特率，即提供给GBR QoS Flow的最大比特率。如超过该比特率时，数据包可以被丢弃。
RQA用于指示使用对应QoS Flow传输的业务使用反转QoS。
QNC用于指示RAN设备在QoS Flow的使用期内当GFBR不能满足时是否通知网络侧。
除去上述QoS Flow级别的QoS参数，5G系统中还引入了聚合级别的QoS参数，如用户设备(user equipment，UE)-聚合最大比特率(aggregate maximum bit rate，AMBR)、会话AMBR(session-AMBR)以及切片最大比特率(slice maximum bitrate)等。
其中，UE-AMBR用于控制终端设备的所有non-GBR QoS Flow的聚合比特率，由RAN设备执行控制。例如，RAN设备控制上行(uplink，UL)和下行(downlink，DL)UE-AMBR，进行流量整形，如丢弃超过限额的数据包。
session-AMBR用于控制终端设备的一个PDU会话中的所有non-GBR QoS Flow的聚合最大比特率，由终端设备和UPF执行控制。例如，终端设备控制上行(Uplink，UL)Session-AMBR，进行流量整形，如丢弃超过限额的数据包。UPF控制UL和下行 (downlink，DL)Session-AMBR，进行流量整形，如丢弃超过限额的数据包。
切片最大比特率用于控制终端设备在一个网络切片(slice)内所有QoS Flow的最大比特率，由终端设备、RAN设备或UPF执行控制。例如，RAN设备控制UL和DL slice-MBR，进行流量整形，如丢弃超过限额的数据包。
第五，绑定机制：
绑定机制是将服务数据流(在策略和计费控制(policy and charging control，PCC)规则中通过业务数据流(service data flow，SDF)模板定义)与传输服务数据流的QoS Flow相关联的过程。现有的绑定机制包括下述三个步骤：
第一步，会话绑定(session binding)，即将AF会话和PDU会话做一一对应，具体可参考现有的实现方式，在此不再赘述。
第二步，PCC规则授权(PCC rule authorization)，由PCF来执行，对PCC规则做授权，为PCC规则分配QoS参数，具体可参考现有的实现方式，在此不再赘述。
第三步，QoS流绑定(QoS Flow binding)，即将PCC规则与PDU会话内的QoS Flow进行关联。使用以下至少一个绑定参数执行绑定：
1、5QI，相关描述可参考上述QoS参数部分，在此不再赘述。
2、ARP，相关描述可参考上述QoS参数部分，在此不再赘述。
或者，可选的，若PCC规则中包括以下参数中的一个或多个，则以下参数中的一个或多个也可以作为绑定参数：
3、QNC，相关描述可参考上述QoS参数部分，在此不再赘述。
4、优先级，优先级指示在QoS流中调度资源的优先级。优先级应用于区分同一终端设备的QoS流，并且还应用于区分来自不同终端设备的QoS流。
5、平均窗口，平均窗口只用于GBR QoS Flow，代表计算GFBR和MFBR的持续时间。
6、MDBV，MDBV表示要求5G接入网在一个分组延时估算(packet delay budget，PDB)之内要服务的最大数据量。其中，PDB定义了一个数据包在终端设备和有N6接口的UPF网元之间传递所能被延迟的时间上限。
当然，上述的优先级、平均窗口或最大数据突发量也可以是上述5QI对应的QoS属性中的参数，在此不作具体限定。
可选的，本申请实施例中，若PCC规则中包括起始时间到终端设备发送第一业务的上行数据包的时间之间的时间间隔，则该间隔时间可以作为绑定参数，其中，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间；或者，若PCC规则中包括用于指示第一业务的数据传输间隔时间固定的指示信息或者用于指示数据传输间隔时间固定的第一业务的指示信息，则该指示信息可以作为绑定参数，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例中，具有上述不同绑定参数属性的PCC规则一定会被绑定到不同的QoS Flow，在此统一说明，以下不再赘述。
第六，5G系统架构：
图5a为现有的5G网络的服务化架构示意图。该5G网络包括RAN设备、UPF、 接入和移动性管理功能(core access and mobility management function，AMF)、SMF、认证服务器功能(authentication server function，AUSF)、网络切片选择功能(network slice selection function，NSSF)、网络开放功能(network exposure function，NEF)、网络功能存储功能(network exposure function Repository Function，NRF)、策略控制功能(policy control function，PCF)、统一数据管理(unified data management，UDM)、统一数据存储(unified data repository，UDR)、应用功能(application function，AF)或者计费功能(charging function，CHF)等。需要说明的是，图5a仅是示例性给出了5G网络中网元或实体的一些举例，该5G网络还可以包括网络数据分析功能(network data analytics function，NWDAF)等一些图5a未示意出的网元或实体，本申请实施例对此不做具体限定。
其中，如图5a所示，终端设备通过RAN设备接入5G网络，终端设备通过N1接口(简称N1)与AMF通信；RAN设备通过N2接口(简称N2)与AMF通信；RAN设备通过N3接口(简称N3)与UPF通信；SMF通过N4接口(简称N4)与UP通信，UPF通过N6接口(简称N6)接入DN。此外，图5a所示的AUSF、AMF、SMF、NSSF、NEF、NRF、PCF、UDM、UDR、CHF或者AF等控制面功能采用服务化接口进行交互。比如，AUSF对外提供的服务化接口为Nausf；AMF对外提供的服务化接口为Namf；SMF对外提供的服务化接口为Nsmf；NSSF对外提供的服务化接口为Nnssf；NEF对外提供的服务化接口为Nnef；NRF对外提供的服务化接口为Nnrf；PCF对外提供的服务化接口为Npcf；UDM对外提供的服务化接口为Nudm；UDR对外提供的服务化接口为Nudr；CHF对外提供的服务化接口为Nchf；AF对外提供的服务化接口为Naf。相关功能描述以及接口描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
图5b为图5a对应的基于参考点的5G网络架构示意图。如图5b所示，终端设备通过RAN设备接入5G网络，终端设备通过N1接口(简称N1)与AMF通信；RAN设备通过N2接口(简称N2)与AMF通信；RAN设备通过N3接口(简称N3)与UPF通信；不同UPF之间通过N9接口(简称N9)通信；UPF通过N6接口(简称N6)接入DN。此外，SMF通过N4接口(简称N4)与UPF通信；AMF网元通过N11接口(简称N11)与SMF通信；AMF通过N8接口(简称N8)与UDM通信；AMF通过N12接口(简称N12)与AUSF通信；AMF通过N15接口(简称N15)与PCF通信；AMF通过N22接口(简称N22)与NSSF通信；不同AMF之间通过N14接口(简称N14)通信；SMF通过N7接口(简称N7)与PCF通信；SMF通过N10接口(简称N10)与UDM通信；SMF通过N29接口(简称N29)与NEF通信；SMF通过Nnrf接口(简称Nnrf)与NRF通信；SMF通过Nchf接口(简称Nchf)与CHF通信；PCF通过N5接口(简称N5)与NEF通信；UDR通过N36接口(简称N36)与PCF通信；UDR通过N37接口(简称N37)与NEF通信；UDM通过N13接口(简称N13)与AUSF通信；UDM通过N29接口(简称N29)与NRF通信。
第七，TSCAI：
现有的5GS中，对于TSC业务，为了传输此类业务，RAN设备需要感知业务的一些特性，并根据这些特性进行调度，以此来保证RAN设备更高效和及时地调度时 延敏感业务。这些特性被称为TSCAI。其中，TSCAI中包括TSC业务的流方向、周期信息和/或突发到达时间，相关介绍可参考表一。
表一
Figure PCTCN2021081070-appb-000001
具体地，集中控制点将生成TSCAI的信息发送给网络侧，网络侧根据生成TSCAI的信息生成TSCAI。进一步的，网络侧(如SMF)需要将QoS Flow对应的TSCAI发送给RAN。RAN根据周期以及突发到达时间提前预留好资源进行调度。
第八，无线帧和子帧：
长期演进(long term evolution，LTE)系统中，定义一个无线帧包括10个子帧(subframe)，每个子帧的长度为1毫秒(ms)，每个子帧包括两个时隙(slot)，每个slot为0.5ms。每个slot包括的符号的个数与子帧中循环前缀(cyclic prefix，CP)的长度相关。若CP为普通(normal)CP，则每个slot包括7个符号，每个子帧由14个符号组成，例如，如图5c所示，每个子帧可以由序号分别为#0，#1，#2，#3，#4，#5，#6，#7，#8，#9，#10，#11，#12，#13的符号组成。若CP为长(extended)CP，则每个slot包括6个OFDM符号，每个子帧由12个符号组成，例如，如图5d所示，每个子帧可以由序号分别为#0，#1，#2，#3，#4，#5，#6，#7，#8，#9，#10，#11的符号组成。此外，定义一个物理资源块(physical resource block，PRB)的大小为时域上的一个时隙，频域上的180kHz。当子载波间隔为15kHz时，如图1或图2所示，一个PRB在频域上包括12个子载波，此时一个PRB共包含84个或72个资源单元(resource element，RE)，RE可以由索引对(k，l)唯一标识，其中，k为子载波索引，l为符号索引。同时，在频域上对PRB进行编号，即为PRB索引或PRB序号。定义一个PRB对(PRB pair)为在一个子帧上的两个时隙的PRB索引或PRB序号相同的一对PRB。
目前的5G系统中，定义一个无线帧包括10个子帧，每个子帧的长度为1毫秒(ms)，每个子帧包括一个或多个时隙。此外，定义一个PRB在频域上包括12个子载波,在频域上对PRB进行编号，即为PRB索引或PRB序号，如上所述。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b， 或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图6所示，为本申请实施例提供的一种通信系统60，包括接入网设备601和会话管理实体602。其中，接入网设备601和会话管理实体602之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不做具体限定。
结合图6所述的通信系统60，一种可能的实现方式中，会话管理实体602，用于向接入网设备601发送间隔时间，该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间。起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间。接入网设备601，用于接收来自会话管理实体602的间隔时间，并根据起始时间和间隔时间，执行第一业务的上行数据包的调度。该方案的具体实现以及技术效果将在后续方法实施例中详细阐述，在此不再赘述。
可选的，如图7所示，本申请实施例提供的通信系统60还包括第一网络设备603。第一网络设备603，用于确定间隔时间之后，向会话管理实体602发送间隔时间。会话管理实体602，用于接收来自第一网络设备603的间隔时间。示例性的，第一网络设备603为网络数据分析功能实体或策略控制实体。
可选的，如图7所示，本申请实施例提供的通信系统60还包括第二网络设备604。第一网络设备603，用于确定间隔时间之后，向第二网络设备604发送间隔时间。第二网络设备604，用于接收来自第一网络设备603的间隔时间，并向会话管理实体602发送间隔时间。会话管理实体602，用于接收来自第一网络设备603的间隔时间。示例性的，第一网络设备603为网络数据分析功能实体，第二网络设备604为策略控制实体。
结合图6所述的通信系统60，另一种可能的实现方式中，会话管理实体602，用于向接入网设备601发送第一指示信息。接入网设备601，用于接收来自会话管理实体602的第一指示信息，并根据第一指示信息，确定间隔时间之后，根据起始时间和间隔时间，执行第一业务的上行数据包的调度。该间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上 行数据包对应的下行数据包的时间。该方案的具体实现及技术效果将在后续方法实施例中详细阐述，在此不再赘述。
可选的，如图8所示，本申请实施例提供的通信系统60还包括策略控制实体605。策略控制实体605，用于向会话管理实体602发送第二指示信息，第二指示信息用于指示第一业务的数据传输间隔时间固定或者第二指示信息用于指示数据传输间隔时间固定的第一业务。会话管理实体602，用于接收来自策略控制实体605的第二指示信息，并根据第二指示信息确定第一指示信息。
可选的，本申请实施例中的接入网设备可以是用于与终端设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved node B，eNB)，基带单元(baseband unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者传输接收点(transmission receiver point，TRP)等。该接入网设备还可以为5G系统中的RAN设备，该RAN设备例如包括gNB或TRP或TP，或者5G系统中的基站的一个或一组(包括多个天线面板)天线面板。此外，该RAN设备还可以为构成gNB或TP的网络节点，如BBU，或分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。此外，gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。
可选的，本申请实施例中的终端设备(terminal equipment)可以指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、UE、终端(terminal)、无线通信设备、用户代理、用户装置、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的PLMN中的终端设备或者未来车联网中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，终端可以是手机、平板电脑、带无线收发功能的电脑、虚拟现实终端设备、增强现实终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程手术中的无线终端、智能电网中的无线终端、运输安全中的无线终端、智慧城市中的无线终端、智慧家庭中的无线终端等。
作为示例而非限定，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备， 是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
可选的，图6至图8所示的通信系统60可以适用于目前正在讨论的5G网络，也可以适用于未来的其他网络等，本申请实施例对此不做具体限定。
示例性的，以图6至图8所示的通信系统60适用于目前正在讨论的5G网络为例，则上述接入网设备所对应的网元或者实体可以为图5a或图5b所述的5G网络中的RAN设备；上述会话管理实体所对应的网元或者实体可以为图5a或图5b所述的5G网络中的SMF；上述策略控制实体所对应的网元或者实体可以为图5a或图5b所述的5G网络中的PCF；上述网络数据分析功能实体所对应的网元或者实体可以为5G网络中的NWDAF。
需要说明的是，当本申请实施例中的第一业务为EtherCAT业务时，在5G网络场景下，EtherCAT中的主节点(和x个从节点，x为自然数)可以位于5G网络中的某个DN，通过N6接口和UPF之间传递数据，EtherCAT中的一个或多个从节点可以对应5G网络中的终端设备，在此统一说明，以下不再赘述。
可选的，本申请实施例中的接入网设备、会话管理实体、第一网络设备或者策略控制实体也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中的接入网设备、会话管理实体、第一网络设备或者策略控制实体的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的接入网设备、会话管理实体、第一网络设备或者策略控制实体的相关功能可以通过图9中的通信装置900来实现。图9所示为本申请实施例提供的通信装置900的结构示意图。该通信装置900包括一个或多个处理器901，通信线路902，以及至少一个通信接口(图9中仅是示例性的以包括通信接口904，以及一个处理器901为例进行说明)，可选的还可以包括存储器903。
处理器901可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路902可包括一通路，用于连接不同组件之间。
通信接口904，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口904也可以是位于处理器901内的收 发电路，用以实现处理器的信号输入和信号输出。
存储器903可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路902与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器903用于存储执行本申请方案的计算机执行指令，并由处理器901来控制执行。处理器901用于执行存储器903中存储的计算机执行指令，从而实现本申请实施例中提供的业务调度方法。
或者，可选的，本申请实施例中，也可以是处理器901执行本申请下述实施例提供的业务调度方法中的处理相关的功能，通信接口904负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器901可以包括一个或多个CPU，例如图9中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置900可以包括多个处理器，例如图9中的处理器901和处理器908。这些处理器中的每一个可以是一个单核(single-core)处理器，也可以是一个多核(multi-core)处理器。这里的处理器可以包括但不限于以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。
在具体实现中，作为一种实施例，通信装置900还可以包括输出设备905和输入设备906。输出设备905和处理器901通信，可以以多种方式来显示信息。例如，输出设备905可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备906和处理器901通信，可以以多种方式接收用户的输入。例如，输入设备906可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信装置900有时也可以称为通信装置，其可以是一个通用设备或者是一个专用设备。例如通信装置900可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备、上述终端设备、上述网络设备、或具有图9中类似结构的设备。本申请实施例不限定通信装置900的类型。
下面将结合附图，对本申请实施例提供的业务调度方法进行说明。
需要说明的是，本申请下述实施例中的第一业务可以是流粒度的业务，在实施例中以QoS流粒度进行描述；也可能是其他粒度的业务，如会话粒度的业务，在实施例中以PDU会话粒度进行描述；在此统一说明，本申请实施例对此不做具体限定。
如图10所示，为本申请实施例提供的一种业务调度方法，如下所述。
S1001、会话管理实体向接入网设备发送间隔时间。相应的，接入网设备接收来自会话管理实体的间隔时间。
其中，间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间。
可选的，本申请实施例中的间隔时间的最小时间单元(或粒度)可以为秒(s)，也可以为无线帧、子帧或者时隙等更小粒度的时间单元，本申请实施例对此不做具体限定。其中，无线帧、子帧或者时隙的相关介绍可参考具体实施方式前序部分，在此不再赘述。此外，需要说明的是，以下各示例均以最小时间单元(或粒度)为时隙进行示意，在此统一说明，以下不再赘述。
示例性的，假设起始时间为时隙1，终端设备发送第一业务的上行数据包的时间为2个时隙后的时隙3，则间隔时间为2个时隙。
需要说明的是，上述示例中的时隙的序号仅用来区分时隙，不限制其所属的无线帧或者子帧，在此统一说明，该说明适用于本申请所有实施例，后续不再赘述。
S1002、接入网设备根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
可选的，本申请实施例中的第一业务可以为应用于任何具有“间隔时间”特征(即应用层或终端设备处理时间固定，收到下行数据包在固定时间后返回上行数据包；或者，网络传递一个数据包固定时间后，一定会收到一个响应数据包)的业务，例如时延敏感业务(该类型业务的数据包在传递超过时延要求时不再有价值或价值降低)。其中，本申请实施例中的时延敏感业务可以为非周期性时延敏感业务，也可以为周期性时延敏感业务，本申请实施例对此不做具体限定。
示例性的，本申请实施例中的第一业务包括：EtherCAT业务、自动化控制业务、配电业务、交互式业务或者扩展现实(extended reality，XR)业务等非周期性时延敏感业务。
可选的，本申请实施例中，当起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间时，本申请实施例提供的业务调度方法还包括：接入网设备根据接入网设备发送下行数据包的时间以及空口时延确定终端设备接收到下行数据包的时间。
示例性的，假设接入网设备发送下行数据包的时间为时隙1，空口时延为3个时隙，则接入网设备可以确定终端设备接收到下行数据包的时间为时隙4。
一种可能的实现方式中，步骤S1002包括：接入网设备根据起始时间和间隔时间，在第一时间执行所述第一业务的上行数据包的调度。
一种可能的实现方式中，第一时间为起始时间之后间隔间隔时间的时间。
示例性的，假设起始时间为时隙1，间隔时间为3个时隙，则第一时间为时隙4。
另一种可能的实现方式中，第一时间为第一时间区间内的时间，第一时间区间内 包括起始时间之后间隔间隔时间的时间。需要说明的是，本申请实施例中的第一时间区间的确定方式有多种。比如，第一时间区间可以是以第一时间为基准，向前和向后各偏移一个时间段获得，如图11a所示；或者，第一时间区间可以是以第一时间为起始时间，向后偏移一个时间段获得，如图11b所示；或者，第一时间区间可以是以第一时间为结束时间，向前偏移一个时间段获得，如图11c所示，本申请实施例对第一时间区间的形式不做具体限定。
示例性的，结合图11a，假设第一时间为时隙3，向前偏移2个时隙，向后偏移1个时隙，则第一时间区间为时隙1至时隙4。
或者，示例性的，结合图11b，假设第一时间为时隙1，偏移时间为3个时隙，则第一时间区间为时隙1至时隙4。
或者，示例性的，结合图11c，假设第一时间为时隙4，偏移时间为3个时隙，则第一时间区间为时隙1至时隙4。
另一种可能的实现方式中，步骤S1002包括：接入网设备接收来自终端设备的第一业务的下行数据包的确认(acknowledgement，ACK)数据包；接入网设备根据起始时间和间隔时间，在第二时间执行第一业务的上行数据包的调度，第二时间为起始时间之后间隔小于或者等于(间隔时间-ACK数据包在终端设备和接入网设备之间的传输时间)的时间。
可选的，本申请实施例中，第一业务的下行数据包可以是一个下行数据包，即第一业务的每个下行数据包都有ACK数据包；或者，第一业务的下行数据包可以是多个下行数据包，即第一业务的多个下行数据包共用一个ACK数据包，本申请实施例对此不做具体限定。
示例性的，假设起始时间为时隙1，间隔时间为3个时隙，ACK数据包在终端设备和接入网设备之间的传输时间为1个时隙，第一业务的每个下行数据包都有ACK数据包，则第二时间可以为无线帧2的时隙3。
或者，示例性的，假设起始时间为时隙1，间隔时间为3个时隙，ACK数据包在终端设备和接入网设备之间的传输时间为1个时隙，第一业务的多个下行数据包共用一个ACK数据包，则第二时间可以为时隙2。
需要说明的是，本申请实施例中，接入网设备执行第一业务的上行数据包的调度(scheduling)可以理解为接入网设备进行(或使能)终端设备和接入网设备之间的上行数据传输，例如包括接入网设备进行(或使能)终端设备向接入网设备发送第一业务的上行数据包，在此统一说明，以下不再赘述。
本申请实施例提供的业务调度方法中，接入网设备可以根据起始时间以及起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。具体地，例如基于本方案，可以避免第一业务为时延敏感业务时，终端设备错过一次调度机会，下次调度则会大概率超过第一业务的时延要求的问题，或者可以避免第一业务为时延敏感业务时，接入网设备无法执行正确调度的问题。需要说明的是，该示例适用于本申请其他实施例，在此统一说明，以下不再赘述。
下面示例性提供一种会话管理实体获取间隔时间的实现方式。
一种可能的实现方式中，如图10所示，在步骤S1001之前，本申请实施例提供的业务调度方法还包括如下步骤：
S1003、第一网络设备确定间隔时间。
一种可能的实现方式中，第一网络设备为网络数据分析功能实体。此时，可选的，步骤S1003包括：第一网络设备根据以下至少一个信息确定间隔时间：来自策略控制实体或应用功能实体的第一业务的类型或第一业务的业务描述，来自终端设备的第一业务的上行数据包的发包频率或第一业务的上行数据包对应的下行数据包的收包频率，来自终端设备的该终端设备对下行数据包的处理时间或者终端设备接收到下行数据包的时间，来自终端设备或者会话管理实体或者应用功能实体的终端设备的设备类型，或者来自接入网设备的第一业务对应的QoS Flow的流标识。
一种可能的实现方式中，第一网络设备为策略控制实体。此时，可选的，步骤S1003包括：第一网络设备根据以下至少一个信息确定间隔时间：来自应用功能实体的第一业务的类型或第一业务的业务描述，来自终端设备的第一业务的上行数据包的发包频率或第一业务的上行数据包对应的下行数据包的收包频率，来自终端设备的该终端设备对下行数据包的处理时间或者终端设备接收到下行数据包的时间，来自终端设备或者会话管理实体或者应用功能实体的终端设备的设备类型，或者来自接入网设备的第一业务对应的QoS Flow的流标识。
S1004、第一网络设备向会话管理实体发送间隔时间。相应的，会话管理实体接收来自第一网络设备的间隔时间。
可选的，本申请实施例中，第一网络设备可以直接向会话管理实体发送间隔时间，也可以通过第二网络设备向会话管理实体发送间隔时间，本申请实施例对此不做具体限定。示例性的，第一网络设备为网络数据分析功能实体时，网络数据分析功能实体可以通过策略控制实体向会话管理实体发送间隔时间。
可选的，本申请实施例中，第一网络设备为策略控制实体时，策略控制实体向会话管理实体发送间隔时间包括：策略控制实体向会话管理实体发送第一计费策略规则，第一计费策略规则包括间隔时间。相应的，会话管理实体接收来自第一网络设备的间隔时间，包括：会话管理实体接收来自第一网络设备的第一计费策略规则。
可选的，本申请实施例中，会话管理实体接收来自第一网络设备的第一计费策略规则之后，本申请实施例提供的业务调度方法还可以包括：会话管理实体根据第一计费策略规则创建第一业务对应的QoS Flow，并将第一计费策略规则绑定至创建的第一业务对应的QoS Flow。即，该方案中，在第一计费策略规则包括间隔时间的情况下，会话管理实体将第一计费策略规则绑定至根据第一计费策略规则创建的第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
一种可能的实现方式中，间隔时间可以为第一计费策略规则中的绑定参数。绑定参数的相关描述可参考具体实施方式前序部分，在此不再赘述。
可选的，在间隔时间为第一计费策略规则中的绑定参数的情况下，本申请实施例提供的业务调度方法还可以包括：会话管理实体确定已有QoS Flow绑定的计费策略规则中，是否存在绑定参数与第一计费策略规则的绑定参数均相同的计费策略规则；若存在，会话管理实体将第一计费策略规则绑定至已有QoS Flow；或者，若不存在，会话管理实体根据第一计费策略规则创建第一业务对应的QoS Flow，并将第一计费策略规则绑定至创建的第一业务对应的QoS Flow。即，该方案中，在第一计费策略规则中的绑定参数包括间隔时间的情况下，若已有QoS Flow绑定的计费策略规则中存在绑定参数与第一计费策略规则的绑定参数均相同的计费策略规则，会话管理实体将第一计费策略规则绑定至已有QoS Flow；否则会话管理实体将第一计费策略规则绑定至根据第一计费策略规则创建的第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
需要说明的是，上述实施例以第一业务为QoS流粒度的业务为例进行说明。当第一业务为其他粒度的业务时，策略控制实体也可以通过其他方式向会话管理实体发送间隔时间，比如间隔时间携带在策略控制实体向会话管理实体发送的会话相关策略信息中，本申请实施例对此不做具体限定。
基于上述方案，会话管理实体可以获取间隔时间。进一步的，会话管理实体可以将间隔时间发送给接入网设备，以使得接入网设备可以根据起始时间以及起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。
需要说明的是，上述步骤S1003-S1004仅是示例性的提供一种会话管理实体获取间隔时间的实现方式。当然，会话管理实体还可以通过其他方式获取间隔时间，比如会话管理实体根据本地配置(如当前会话所在的数据网络名称(data network name，DNN)和/或当前会话所在的网络切片的单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI))确定间隔时间，本申请实施例对此不做具体限定。
其中，上述步骤S1001至S1004中会话管理实体的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令会话管理实体执行，上述步骤S1001至S1004中接入网设备的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令接入网设备执行，上述步骤S1001至S1004中第一网络设备的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令第一网络设备执行，本实施例对此不作任何限制。
如图12所示，为本申请实施例提供的另一种业务调度方法，如下所述。
S1201、会话管理实体向接入网设备发送第一指示信息。相应的，接入网设备接收 来自会话管理实体的第一指示信息。
其中，第一指示信息用于指示第一业务的数据传输间隔时间固定。第一业务的相关描述可参考图10所述的实施例，在此不再赘述。
可选的，本申请实施例中，第一指示信息可以为显式的指示信息。比如，定义一个比特位，比特值为“1”表示第一业务的数据传输间隔时间固定，或者比特值为“0”表示第一业务的数据传输间隔时间固定。
或者，可选的，本申请实施例中，第一指示信息可以为隐式的指示信息。比如，第一指示信息可以为数据传输间隔时间固定的业务指示，如EtherCAT指示，交互式业务指示、或者XR业务指示等，指示该业务的数据传输间隔时间固定，本申请实施例对此不做具体限定。
S1202、接入网设备根据第一指示信息，确定间隔时间。其中，间隔时间的相关描述可参考图10所述的实施例，在此不再赘述。
一种可能的实现方式中，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间。步骤S1202包括：接入网设备根据第一指示信息，获取至少一组时间信息，至少一组时间信息中的每组时间信息包括终端设备接收到第一业务的下行数据包的时间和终端设备发送第一业务的下行数据包对应的上行数据包的时间；接入网设备根据至少一组时间信息，确定从终端设备接收到第一业务的上行数据包对应的下行数据包的时间到终端设备发送第一业务的上行数据包的时间之间的时间。也就是说，本申请实施例中，接入网设备可以根据多组终端设备接收到第一业务的下行数据包的时间和终端设备发送第一业务的下行数据包对应的上行数据包的时间自学习得到间隔时间。
另一种可能的实现方式中，起始时间点为接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间。步骤S1202包括：接入网设备根据第一指示信息，获取至少一组时间信息，至少一组时间信息中的每组时间信息包括接入网设备向终端设备发送第一业务的下行数据包的时间和终端设备发送第一业务的下行数据包对应的上行数据包的时间；接入网设备根据至少一组时间信息，确定从接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间到终端设备发送第一业务的上行数据包的时间之间的时间。也就是说，本申请实施例中，接入网设备可以根据多组接入网设备向终端设备发送第一业务的下行数据包的时间和终端设备发送第一业务的下行数据包对应的上行数据包的时间自学习得到间隔时间。
S1203、接入网设备根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
步骤S1203的具体实现可参考图10所述的实施例步骤S1202，在此不再赘述。
本申请实施例提供的业务调度方法中，接入网设备可以获知第一业务的数据传输间隔时间固定，进而在接入网设备确定起始时间到终端设备发送第一业务的上行数据包的时间之间的间隔时间之后，接入网设备可以根据起始时间和间隔时间，执行第一业务的上行数据包的调度，因此保证了接入网设备更高效和及时地进行业务调度，例如时延敏感业务的调度。
下面示例性的提供一种会话管理实体获取第一指示信息的实现方式。
一种可能的实现方式中，如图12所示，在步骤S1201之前，本申请实施例提供的 业务调度方法还包括如下步骤：
S1204、策略控制实体向会话管理实体发送第二指示信息。相应的，会话管理实体接收来自策略控制实体的第二指示信息。
其中，第二指示信息用于指示第一业务的数据传输间隔时间固定。
可选的，本申请实施例中，第二指示信息可以为显式的指示信息。比如，定义一个比特位，比特值为“1”表示第一业务的数据传输间隔时间固定，或者比特值为“0”表示第一业务的数据传输间隔时间固定。
或者，可选的，本申请实施例中，第二指示信息可以为隐式的指示信息。比如，第二指示信息可以为数据传输间隔时间固定的业务指示，如EtherCAT指示，交互式业务指示、或者XR业务指示等，指示该业务的数据传输间隔时间固定，本申请实施例对此不做具体限定。
可选的，本申请实施例中，策略控制实体向会话管理实体发送第二指示信息包括：策略控制实体向会话管理实体发送第二计费策略规则，第二计费策略规则包括第二指示信息。相应的，会话管理实体接收来自策略控制实体的第二指示信息，包括：会话管理实体接收来自策略控制实体的第二计费策略规则。
可选的，本申请实施例中，会话管理实体接收来自策略控制实体的第二计费策略规则之后，本申请实施例提供的业务调度方法还可以包括：会话管理实体根据第二计费策略规则创建第一业务对应的QoS Flow，并将第二计费策略规则绑定至创建的第一业务对应的QoS Flow。即，该方案中，在第二计费策略规则包括第二指示信息的情况下，会话管理实体将第一计费策略规则绑定至根据第一计费策略规则创建的第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
一种可能的实现方式中，第二指示信息可以为第二计费策略规则中的绑定参数。绑定参数的相关描述可参考具体实施方式前序部分，在此不再赘述。
可选的，在第二指示信息为第二计费策略规则中的绑定参数的情况下，本申请实施例提供的业务调度方法还可以包括：会话管理实体确定已有QoS Flow绑定的计费策略规则中，是否存在绑定参数与第二计费策略规则的绑定参数均相同的计费策略规则；
若存在，会话管理实体将第二计费策略规则绑定至已有QoS Flow；或者，若不存在，会话管理实体根据第二计费策略规则创建所述第一业务对应的QoS Flow，并将第二计费策略规则绑定至创建的第一业务对应的QoS Flow。即，该方案中，在第二计费策略规则中的绑定参数包括第二指示信息的情况下，若已有QoS Flow绑定的计费策略规则中存在绑定参数与第二计费策略规则的绑定参数均相同的计费策略规则，会话管理实体将第二计费策略规则绑定至已有QoS Flow；否则会话管理实体将第二计费策略规则绑定至根据第二计费策略规则创建的第一业务对应的QoS Flow。具体地，假如不同性质的业务(例如不具有该间隔时间和具有间隔时间的业务，或者间隔时间不同的业务)被绑定到同一QoS Flow，则接入网设备无法识别出相关规律，从而不能优化接 入网设备的调度或导致错误的调度。基于该方案，可以避免第一业务与其他业务绑定到同一个QoS Flow可能导致的调度不及时的问题，进一步保证了接入网设备更高效和及时地调度时第一业务。
需要说明的是，上述实施例以第一业务为QoS流粒度的业务为例进行说明。当第一业务为其他粒度的业务时，策略控制实体也可以通过其他方式向会话管理实体发送第二指示信息，比如第二指示信息携带在策略控制实体向会话管理实体发送的会话相关策略信息中，本申请实施例对此不做具体限定。
S1205、会话管理实体根据第二指示信息确定第一指示信息。
可选的，本申请实施例中，第二指示信息与第一指示信息可以相同，也可以不相同，本申请实施例对此不做具体限定。
基于上述方案，会话管理实体可以获取第一指示信息。进一步的，会话管理实体可以向接入网设备发送第一指示信息，以使得接入网设备根据第一指示信息，获知第一业务的数据传输间隔时间固定。
需要说明的是，上述步骤S1204-S1205仅是示例性的提供一种会话管理实体获取第一指示信息的实现方式。当然，会话管理实体还可以通过其他方式获取第一指示信息，比如会话管理实体根据本地配置(如当前会话所在的DNN和/或当前会话所在的S-NSSAI)确定第一指示信息或者会话管理实体接收来自策略控制实体之前的其他网元或设备的第一指示信息，本申请实施例对此不做具体限定。
其中，上述步骤S1201至S1205中会话管理实体的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令会话管理实体执行，上述步骤S1201至S1205中接入网设备的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令接入网设备执行，上述步骤S1201至S1205中策略控制实体的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令策略控制实体执行，本实施例对此不作任何限制。
下面将以图6至图8所述的通信系统应用于如图5a或图5b所示的5G网络为例，对图10或图12所述的业务调度方法进行示例性说明。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
结合图10所述的业务调度方法，以图7所述的通信系统应用于如图5a或图5b所示的5G网络，第一网络设备为PCF，不存在第二网络设备为例，如图13所示，为本申请实施例提供的一种业务调度方法，包括如下步骤：
S1301、PCF获取间隔时间后，向SMF发送间隔时间。相应的，SMF接收来自PCF的间隔时间。
其中，间隔时间的相关描述可参考图10所述的实施例，在此不再赘述。
可选的，本申请实施例中，PCF获取间隔时间的方式可以是由PCF自身确定的，或者PCF接收来自NWDAF或者AF的间隔时间，本申请实施例对此不做具体限定。其中，PCF或者NWDAF确定间隔时间的方式可参考图10所述的实施例步骤S1003 中第一网络设备确定间隔时间的方式，本申请实施例在此不再赘述。
可选的，本申请实施例中，间隔时间可以携带在PCF向SMF发送的PCC规则中。
可选的，本申请实施例中，SMF接收来自PCF的PCC规则之后，可以根据该PCC规则创建第一业务对应的QoS Flow，并将该PCC规则绑定至创建的第一业务对应的QoS Flow。即，该方案中，在PCC规则包括间隔时间的情况下，SMF将该PCC规则绑定至根据该PCC规则创建的第一业务对应的QoS Flow。相关技术效果可参考图10所述的实施例，在此不再赘述。
可选的，本申请实施例中，间隔时间可以作为PCC规则中的绑定参数。绑定参数的相关描述可参考具体实施方式前序部分，在此不再赘述。
可选的，在间隔时间为PCC规则中的绑定参数的情况下，SMF接收来自PCF的PCC规则之后，可以确定已有QoS Flow绑定的PCC规则中，是否存在绑定参数与该PCC规则的绑定参数均相同的PCC规则。其中，存在绑定参数与该PCC规则的绑定参数均相同的PCC规则或者不存在绑定参数与该PCC规则的绑定参数均相同的PCC规则的情况下的处理方式可参考图10所述的实施例中的相关描述，在此不再赘述。
可选的，SMF接收来自PCF的间隔时间之后，还可以向PCF发送确认消息，本申请实施例对此不做具体限定。
需要说明的是，上述实施例以第一业务为QoS流粒度的业务为例进行说明。当第一业务为其他粒度的业务时，PCF也可以通过其他方式向SMF发送间隔时间，比如间隔时间携带在PCF向SMF体发送的PDU会话相关策略信息(PDU Session related policy information)中，本申请实施例对此不做具体限定。
S1302、SMF向RAN设备发送间隔时间。相应的，RAN设备接收来自SMF的间隔时间。
可选的，本申请实施例中，SMF可以将间隔时间作为QoS属性的一个参数发送给RAN设备，本申请实施例对此不做具体限定。
S1303、RAN设备根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
步骤S1303的具体实现可参考图10所述的实施例步骤S1002，在此不再赘述。
其中，图13所述的实施例的技术效果可参考图10所述的实施例，在此不再赘述。
其中，上述步骤S1301至S1303中SMF的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令SMF执行，上述步骤S1301至S1303中RAN设备的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令RAN设备执行，上述步骤S1301至S1303中PCF的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令PCF执行，本实施例对此不作任何限制。
结合图10所述的业务调度方法，以图7所述的通信系统应用于如图5a或图5b所示的5G网络，第一网络设备为NWDAF，不存在第二网络设备为例，如图14所示，为本申请实施例提供的另一种业务调度方法，包括如下步骤：
S1401、NWDAF确定间隔时间后，向SMF发送间隔时间。相应的，SMF接收来自NWDAF的间隔时间。
其中，间隔时间的相关描述以及NWDAF确定间隔时间的方式可参考图10所述的 实施例，在此不再赘述。
可选的，SMF接收来自NWDAF的间隔时间之后，还可以向NWDAF发送确认消息，本申请实施例对此不做具体限定。
S1402、SMF向RAN设备发送间隔时间。相应的，RAN设备接收来自SMF的间隔时间。
可选的，本申请实施例中，SMF可以将间隔时间作为QoS属性的一个参数发送给RAN设备，本申请实施例对此不做具体限定。
S1403、RAN设备根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
步骤S1403的具体实现可参考图10所述的实施例步骤S1002，在此不再赘述。
需要说明的是，本申请实施例中，NWDAF也可以通过PCF与SMF交互，即本申请实施例也可以以第一网络设备为NWDAF，第二网络设备为PCF为例，具体实现与图14所述的实施例类似，在此不再赘述。
其中，图14所述的实施例的技术效果可参考图10所述的实施例，在此不再赘述。
其中，上述步骤S1401至S1403中SMF的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令SMF执行，上述步骤S1401至S1403中RAN设备的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令RAN设备执行，上述步骤S1401至S1403中NWDAF的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令NWDAF执行，本实施例对此不作任何限制。
结合图10所述的业务调度方法，以图8所述的通信系统应用于如图5a或图5b所示的5G网络为例，如图15所示，为本申请实施例提供的又一种业务调度方法，包括如下步骤：
S1501、PCF向SMF发送第二指示信息。相应的，SMF接收来自PCF的第二指示信息。
其中，第二指示信息用于指示第一业务的数据传输间隔时间固定，相关描述可参考图12所述的实施例，在此不再赘述。
可选的，PCF可以从AF获取业务类型，本申请实施例对此不做具体限定。
可选的，本申请实施例中，第二指示信息可以携带在PCF向SMF发送的PCC规则中。
可选的，SMF接收来自PCF的PCC规则之后，可以根据该PCC规则创建第一业务对应的QoS Flow，并将该PCC规则绑定至创建的第一业务对应的QoS Flow。即，该方案中，在PCC规则包括第二指示信息的情况下，SMF将该PCC规则绑定至根据该PCC规则创建的第一业务对应的QoS Flow。相关技术效果可参考图10所述的实施例，在此不再赘述。
可选的，本申请实施例中，第二指示信息可以作为PCC规则中的绑定参数。绑定参数的相关描述可参考具体实施方式前序部分，在此不再赘述。
可选的，在第二指示信息为PCC规则中的绑定参数的情况下，SMF接收来自PCF的PCC规则之后，可以确定已有QoS Flow绑定的PCC规则中，是否存在绑定参数与该PCC规则的绑定参数均相同的PCC规则。其中，存在绑定参数与该PCC规则的绑 定参数均相同的PCC规则或者不存在绑定参数与该PCC规则的绑定参数均相同的PCC规则的情况下的处理方式可参考图12所述的实施例中的相关描述，在此不再赘述。
可选的，SMF接收来自PCF的第二指示信息之后，还可以向PCF发送确认消息，本申请实施例对此不做具体限定。
需要说明的是，上述实施例以第一业务为QoS流粒度的业务为例进行说明。当第一业务为其他粒度的业务时，PCF也可以通过其他方式向SMF发送第二指示信息，比如第二指示信息携带在PCF向SMF体发送的PDU会话相关策略信息(PDU Session related policy information)中，本申请实施例对此不做具体限定。
S1502、SMF根据第二指示信息确定第一指示信息。
其中，第一指示信息用于指示第一业务的数据传输间隔时间固定，相关描述可参考图12所述的实施例，在此不再赘述。
步骤S1502的相关描述可参考图12所述的实施例步骤S1205，在此不再赘述。
S1503、SMF向RAN设备发送第一指示信息。相应的，RAN设备接收来自SMF的第一指示信息。
S1504、RAN设备根据第一指示信息，确定间隔时间。其中，间隔时间的相关描述以及RAN设备根据第一指示信息，确定间隔时间的方式可参考图10所述的实施例，在此不再赘述。
S1505、RAN设备根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
步骤S1505的具体实现可参考图10所述的实施例步骤S1002，在此不再赘述。
其中，图15所述的实施例的技术效果可参考图12所述的实施例，在此不再赘述。
其中，上述步骤S1501至S1505中SMF的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令SMF执行，上述步骤S1501至S1505中RAN设备的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令RAN设备执行，上述步骤S1501至S1505中PCF的动作可以由图9所示的通信装置900中的处理器901调用存储器903中存储的应用程序代码以指令PCF执行，本实施例对此不作任何限制。
可以理解的是，以上各个实施例中，由会话管理实体实现的方法和/或步骤，也可以由可用于会话管理实体的部件(例如芯片或者电路)实现；由接入网设备实现的方法和/或步骤，也可以由可用于接入网设备的部件(例如芯片或者电路)实现；由第一网络设备或者策略控制实体实现的方法和/或步骤，也可以由可用于第一网络设备或者策略控制实体的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置可以为上述方法实施例中的接入网设备，或者包含上述接入网设备的装置，或者为可用于接入网设备的部件；或者，该通信装置可以为上述方法实施例中的会话管理实体，或者包含上述会话管理实体的装置，或者为可用于会话管理实体的部件；或者，该通信装置可以为上述方法实施例中的第一网络设备，或者包含上述第一网络设备的装置，或者为可用于第一网络设备的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的 实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图16示出了一种通信装置160的结构示意图。该通信装置160包括收发模块1601和处理模块1602。所述收发模块1601，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
其中，以通信装置160为上述方法实施例中的接入网设备为例：
收发模块1601，用于接收来自会话管理实体的间隔时间，间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间。处理模块1602，用于根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
可选的，处理模块1602具体用于：根据起始时间和间隔时间，在第一时间执行第一业务的上行数据包的调度。其中，第一时间为起始时间之后间隔间隔时间的时间；或者，第一时间为第一时间区间内的时间，第一时间区间内包括起始时间之后间隔间隔时间的时间。
可选的，处理模块1602具体用于：通过收发模块1601接收来自终端设备的第一业务的下行数据包的确认ACK数据包；根据起始时间和间隔时间，在第二时间执行第一业务的上行数据包的调度，第二时间为起始时间之后间隔小于或者等于(间隔时间-ACK数据包在终端设备和接入网设备之间的传输时间)的时间。
可选的，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间；处理模块1602，还用于根据接入网设备发送下行数据包的时间以及空口时延确定终端设备接收到下行数据包的时间。
或者，以通信装置160为上述方法实施例中的接入网设备为例：
收发模块1601，用于接收来自会话管理实体的第一指示信息。处理模块1602，用于根据第一指示信息，确定间隔时间，间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间。处理模块1602，还用于根据起始时间和间隔时间，执行第一业务的上行数据包的调度。
可选的，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间。处理模块1602，用于根据第一指示信息，确定间隔时间，包括：根据第一指示信息，获取至少一组时间信息，至少一组时间信息中的每组时间信息包括终端设备接收到第一业务的下行数据包的时间和终端设备发送第一业务的下行数据包对应的上行数据包的时间；根据至少一组时间信息，确定间隔时间。
可选的，起始时间点为接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间；处理模块1602，用于根据第一指示信息，确定间隔时间，包括：根据第一指示信息，获取至少一组时间信息，至少一组时间信息中的每组时间信息包 括接入网设备向终端设备发送第一业务的下行数据包的时间和终端设备发送第一业务的下行数据包对应的上行数据包的时间；根据至少一组时间信息，确定间隔时间。
可选的，处理模块1602，用于根据起始时间和间隔时间，执行第一业务的上行数据包的调度，包括：根据起始时间和间隔时间，在第一时间执行第一业务的上行数据包的调度；其中，第一时间为起始时间之后间隔间隔时间的时间；或者，第一时间为第一时间区间内的时间，第一时间区间内包括起始时间之后间隔间隔时间的时间。
可选的，处理模块1602，用于根据起始时间和间隔时间，执行第一业务的上行数据包的调度，包括：通过收发模块1601接收来自终端设备的第一业务的下行数据包的确认ACK数据包；根据起始时间和间隔时间，在第二时间执行第一业务的上行数据包的调度，第二时间为起始时间之后间隔小于或者等于(间隔时间-ACK数据包在终端设备和接入网设备之间的传输时间)的时间。
可选的，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间；处理模块1602，还用于根据接入网设备发送下行数据包的时间以及空口时延确定终端设备接收到下行数据包的时间。
或者，以通信装置160为上述方法实施例中的第一网络设备为例：
处理模块1602，用于确定间隔时间，间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，起始时间为终端设备接收到第一业务的上行数据包对应的下行数据包的时间或者接入网设备向终端设备发送第一业务的上行数据包对应的下行数据包的时间。收发模块1601，用于向第二网络设备发送间隔时间，其中，间隔时间用于执行第一业务的上行数据包的调度。
可选的，第一网络设备为网络数据分析功能实体，第二网络设备为策略控制实体或者会话管理实体。
可选的，处理模块1602具体用于：根据以下至少一个信息确定间隔时间：来自策略控制实体或应用功能实体的第一业务的类型或第一业务的业务描述，来自终端设备的第一业务的上行数据包的发包频率或第一业务的上行数据包对应的下行数据包的收包频率，来自终端设备的终端设备对下行数据包的处理时间或者终端设备接收到下行数据包的时间，来自终端设备或者会话管理实体或者应用功能实体的终端设备的设备类型，或者来自接入网设备的第一业务对应的QoS Flow的流标识。
可选的，第一网络设备为策略控制实体，所述第二网络设备为会话管理实体。
可选的，处理模块1602具体用于：根据以下至少一个信息确定间隔时间：来自应用功能实体的第一业务的类型或第一业务的业务描述，来自终端设备的第一业务的上行数据包的发包频率或第一业务的上行数据包对应的下行数据包的收包频率，来自终端设备的终端设备对下行数据包的处理时间或者终端设备接收到下行数据包的时间，来自终端设备或者会话管理实体或者应用功能实体的终端设备的设备类型，或者来自接入网设备的第一业务对应的QoS Flow的流标识。
可选的，收发模块1601具体用于：向会话管理实体发送第一计费策略规则，第一计费策略规则包括间隔时间。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信装置160以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置160可以采用图8所示的通信装置900的形式。
比如，图8所示的通信装置900中的处理器901可以通过调用存储器903中存储的计算机执行指令，使得通信装置900执行上述方法实施例中的业务调度方法。
具体的，图16中的收发模块1601和处理模块1602的功能/实现过程可以通过图8所示的通信装置900中的处理器901调用存储器903中存储的计算机执行指令来实现。或者，图16中的处理模块1602的功能/实现过程可以通过图8所示的通信装置900中的处理器901调用存储器903中存储的计算机执行指令来实现，图16中的收发模块1601的功能/实现过程可以通过图8中所示的通信装置900中的通信接口904来实现。
由于本实施例提供的通信装置160可执行上述业务调度方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。在一种可能的实现方式中，该通信装置还包括存储器。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或 无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (43)

  1. 一种业务调度方法，其特征在于，所述方法包括：
    接入网设备接收来自会话管理实体的间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述接入网设备根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度。
  2. 根据权利要求1所述的方法，其特征在于，所述接入网设备根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度，包括：
    所述接入网设备根据所述起始时间和所述间隔时间，在第一时间执行所述第一业务的上行数据包的调度；其中，所述第一时间为所述起始时间之后间隔所述间隔时间的时间；或者，所述第一时间为第一时间区间内的时间，所述第一时间区间内包括所述起始时间之后间隔所述间隔时间的时间。
  3. 根据权利要求1所述的方法，其特征在于，所述接入网设备根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度，包括：
    所述接入网设备接收来自所述终端设备的所述第一业务的下行数据包的确认ACK数据包；
    所述接入网设备根据所述起始时间和所述间隔时间，在第二时间执行所述第一业务的上行数据包的调度，所述第二时间为所述起始时间之后间隔小于或者等于(所述间隔时间-所述ACK数据包在所述终端设备和所述接入网设备之间的传输时间)的时间。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间，所述方法还包括：
    所述接入网设备根据所述接入网设备发送所述下行数据包的时间以及空口时延确定所述终端设备接收到所述下行数据包的时间。
  5. 一种业务调度方法，其特征在于，所述方法包括：
    第一网络设备确定间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述第一网络设备向第二网络设备发送所述间隔时间，其中，所述间隔时间用于执行所述第一业务的上行数据包的调度。
  6. 根据权利要求5所述的方法，其特征在于，所述第一网络设备为网络数据分析功能实体，所述第二网络设备为策略控制实体或者会话管理实体。
  7. 根据权利要求6所述的方法，其特征在于，所述第一网络设备确定所述间隔时间，包括：
    所述第一网络设备根据以下至少一个信息确定所述间隔时间：
    来自策略控制实体或应用功能实体的所述第一业务的类型或所述第一业务的业务 描述，来自所述终端设备的所述第一业务的上行数据包的发包频率或所述第一业务的上行数据包对应的下行数据包的收包频率，来自所述终端设备的所述终端设备对所述下行数据包的处理时间或者所述终端设备接收到所述下行数据包的时间，来自所述终端设备或者会话管理实体或者所述应用功能实体的所述终端设备的设备类型，或者来自所述接入网设备的所述第一业务对应的服务质量流QoS Flow的流标识。
  8. 根据权利要求5所述的方法，其特征在于，所述第一网络设备为策略控制实体，所述第二网络设备为会话管理实体。
  9. 根据权利要求8所述的方法，其特征在于，所述第一网络设备确定所述间隔时间，包括：
    所述第一网络设备根据以下至少一个信息确定所述间隔时间：
    来自应用功能实体的所述第一业务的类型或所述第一业务的业务描述，来自所述终端设备的所述第一业务的上行数据包的发包频率或所述第一业务的上行数据包对应的下行数据包的收包频率，来自所述终端设备的所述终端设备对所述下行数据包的处理时间或者所述终端设备接收到所述下行数据包的时间，来自所述终端设备或者会话管理实体或者所述应用功能实体的所述终端设备的设备类型，或者来自所述接入网设备的所述第一业务对应的QoS Flow的流标识。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第一网络设备向第二网络设备发送所述间隔时间，包括：
    所述策略控制实体向所述会话管理实体发送第一计费策略规则，所述第一计费策略规则包括所述间隔时间。
  11. 根据权利要求10所述的方法，其特征在于，所述间隔时间为所述第一计费策略规则中的绑定参数。
  12. 一种业务调度方法，其特征在于，所述方法包括：
    接入网设备接收来自会话管理实体的第一指示信息；
    所述接入网设备根据所述第一指示信息，确定间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述接入网设备根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度。
  13. 根据权利要求12所述的方法，其特征在于，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间；
    所述接入网设备根据所述第一指示信息，确定所述间隔时间，包括：
    所述接入网设备根据所述第一指示信息，获取至少一组时间信息，所述至少一组时间信息中的每组时间信息包括所述终端设备接收到所述第一业务的下行数据包的时间和所述终端设备发送所述第一业务的下行数据包对应的上行数据包的时间；
    所述接入网设备根据所述至少一组时间信息，确定所述间隔时间。
  14. 根据权利要求12所述的方法，其特征在于，所述起始时间点为所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述接入网设备根据所述第一指示信息，确定所述间隔时间，包括：
    所述接入网设备根据所述第一指示信息，获取至少一组时间信息，所述至少一组时间信息中的每组时间信息包括所述接入网设备向所述终端设备发送所述第一业务的下行数据包的时间和所述终端设备发送所述第一业务的下行数据包对应的上行数据包的时间；
    所述接入网设备根据所述至少一组时间信息，确定所述间隔时间。
  15. 根据权利要求12-14任一项所述的方法，其特征在于，所述接入网设备根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度，包括：
    所述接入网设备根据所述起始时间和所述间隔时间，在第一时间执行所述第一业务的上行数据包的调度；其中，所述第一时间为所述起始时间之后间隔所述间隔时间的时间；或者，所述第一时间为第一时间区间内的时间，所述第一时间区间内包括所述起始时间之后间隔所述间隔时间的时间。
  16. 根据权利要求12-14任一项所述的方法，其特征在于，所述接入网设备根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度，包括：
    所述接入网设备接收来自所述终端设备的所述第一业务的下行数据包的确认ACK数据包；
    所述接入网设备根据所述起始时间和所述间隔时间，在第二时间执行所述第一业务的上行数据包的调度，所述第二时间为所述起始时间之后间隔小于或者等于(所述间隔时间-所述ACK数据包在所述终端设备和所述接入网设备之间的传输时间)的时间。
  17. 根据权利要求12-16任一项所述的方法，其特征在于，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间，所述方法还包括：
    所述接入网设备根据所述接入网设备发送所述下行数据包的时间以及空口时延确定所述终端设备接收到所述下行数据包的时间。
  18. 根据权利要求12-17任一项所述的方法，其特征在于，所述第一指示信息用于指示所述第一业务的数据传输间隔时间固定。
  19. 根据权利要求12-18任一项所述的方法，其特征在于，所述第一业务包括：以太网控制自动化技术EtherCAT业务、交互式业务或者扩展现实XR业务。
  20. 一种接入网设备，其特征在于，所述接入网设备包括：收发模块和处理模块；
    所述收发模块，用于接收来自会话管理实体的间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述处理模块，用于根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度。
  21. 根据权利要求20所述的接入网设备，其特征在于，所述处理模块具体用于：
    根据所述起始时间和所述间隔时间，在第一时间执行所述第一业务的上行数据包的调度；其中，所述第一时间为所述起始时间之后间隔所述间隔时间的时间；或者，所述第一时间为第一时间区间内的时间，所述第一时间区间内包括所述起始时间之后 间隔所述间隔时间的时间。
  22. 根据权利要求20所述的接入网设备，其特征在于，所述处理模块具体用于：
    通过所述收发模块接收来自所述终端设备的所述第一业务的下行数据包的确认ACK数据包；根据所述起始时间和所述间隔时间，在第二时间执行所述第一业务的上行数据包的调度，所述第二时间为所述起始时间之后间隔小于或者等于(所述间隔时间-所述ACK数据包在所述终端设备和所述接入网设备之间的传输时间)的时间。
  23. 一种第一网络设备，其特征在于，所述第一网络设备包括：处理模块和收发模块；
    所述处理模块，用于确定间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述收发模块，用于向第二网络设备发送所述间隔时间，其中，所述间隔时间用于执行所述第一业务的上行数据包的调度。
  24. 根据权利要求23所述的第一网络设备，其特征在于，所述第一网络设备为网络数据分析功能实体，所述第二网络设备为策略控制实体或者会话管理实体。
  25. 根据权利要求24所述的第一网络设备，其特征在于，所述处理模块具体用于：
    根据以下至少一个信息确定所述间隔时间：
    来自策略控制实体或应用功能实体的所述第一业务的类型或所述第一业务的业务描述，来自所述终端设备的所述第一业务的上行数据包的发包频率或所述第一业务的上行数据包对应的下行数据包的收包频率，来自所述终端设备的所述终端设备对所述下行数据包的处理时间或者所述终端设备接收到所述下行数据包的时间，来自所述终端设备或者会话管理实体或者所述应用功能实体的所述终端设备的设备类型，或者来自所述接入网设备的所述第一业务对应的服务质量流QoS Flow的流标识。
  26. 根据权利要求23所述的第一网络设备，其特征在于，所述第一网络设备为策略控制实体，所述第二网络设备为会话管理实体。
  27. 根据权利要求26所述的第一网络设备，其特征在于，所述处理模块具体用于：
    根据以下至少一个信息确定所述间隔时间：
    来自应用功能实体的所述第一业务的类型或所述第一业务的业务描述，来自所述终端设备的所述第一业务的上行数据包的发包频率或所述第一业务的上行数据包对应的下行数据包的收包频率，来自所述终端设备的所述终端设备对所述下行数据包的处理时间或者所述终端设备接收到所述下行数据包的时间，来自所述终端设备或者会话管理实体或者所述应用功能实体的所述终端设备的设备类型，或者来自所述接入网设备的所述第一业务对应的QoS Flow的流标识。
  28. 一种接入网设备，其特征在于，所述接入网设备包括：处理模块和收发模块；
    所述收发模块，用于接收来自会话管理实体的第一指示信息；
    所述处理模块，用于根据所述第一指示信息，确定间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述处理模块，还用于根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度。
  29. 根据权利要求28所述的接入网设备，其特征在于，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间；所述处理模块，用于根据所述第一指示信息，确定所述间隔时间，包括：
    根据所述第一指示信息，获取至少一组时间信息，所述至少一组时间信息中的每组时间信息包括所述终端设备接收到所述第一业务的下行数据包的时间和所述终端设备发送所述第一业务的下行数据包对应的上行数据包的时间；根据所述至少一组时间信息，确定所述间隔时间。
  30. 根据权利要求28所述的接入网设备，其特征在于，所述起始时间点为所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；所述处理模块，用于根据所述第一指示信息，确定所述间隔时间，包括：
    根据所述第一指示信息，获取至少一组时间信息，所述至少一组时间信息中的每组时间信息包括所述接入网设备向所述终端设备发送所述第一业务的下行数据包的时间和所述终端设备发送所述第一业务的下行数据包对应的上行数据包的时间；根据所述至少一组时间信息，确定所述间隔时间。
  31. 一种通信装置，其特征在于，所述通信装置包括：处理器和存储器；
    所述存储器用于存储计算机执行指令，当所述处理器执行所述计算机执行指令时，以使所述通信装置执行如权利要求1-4或5-11或12-19中任一项所述的方法。
  32. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收计算机执行指令并传输至所述处理器；
    所述处理器用于执行所述计算机执行指令，以使所述通信装置执行如权利要求1-4或5-11或12-19中任一项所述的方法。
  33. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，当所述计算机程序被计算机执行时使得所述计算机执行权利要求1-4或5-11或12-19中任一项所述的方法。
  34. 一种计算机程序产品，其特征在于，包括：指令，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求1-4或5-11或12-19中任一项所述的方法。
  35. 一种通信系统，其特征在于，所述通信系统包括接入网设备和会话管理实体；
    所述会话管理实体，用于向所述接入网设备发送间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述接入网设备，用于接收来自所述会话管理实体的所述间隔时间，并根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度。
  36. 根据权利要求35所述的通信系统，其特征在于，所述通信系统还包括第一网络设备；
    所述第一网络设备，用于确定所述间隔时间，并向所述会话管理实体发送所述间隔时间。
  37. 根据权利要求36所述的通信系统，其特征在于，所述第一网络设备为网络数据分析功能实体或策略控制实体。
  38. 根据权利要求35所述的通信系统，其特征在于，所述通信系统还包括第一网络设备和第二网络设备；
    所述第一网络设备，用于确定所述间隔时间，并向所述第二网络设备发送所述间隔时间；
    所述第二网络设备，用于向所述会话管理实体发送所述间隔时间。
  39. 根据权利要求38所述的通信系统，其特征在于，所述第一网络设备为网络数据分析功能实体，所述第二网络设备为策略控制实体。
  40. 一种通信系统，其特征在于，所述通信系统包括接入网设备和会话管理实体；
    所述会话管理实体，用于向所述接入网设备发送第一指示信息；
    所述接入网设备，用于接收来自所述会话管理实体的所述第一指示信息，并根据所述第一指示信息，确定间隔时间，所述间隔时间为从起始时间到终端设备发送第一业务的上行数据包的时间之间的时间，所述起始时间为所述终端设备接收到所述第一业务的上行数据包对应的下行数据包的时间或者所述接入网设备向所述终端设备发送所述第一业务的上行数据包对应的下行数据包的时间；
    所述接入网设备，还用于根据所述起始时间和所述间隔时间，执行所述第一业务的上行数据包的调度。
  41. 根据权利要求40所述的通信系统，其特征在于，所述通信系统还包括策略控制实体；
    所述策略控制实体，用于所述会话管理实体发送第二指示信息；
    所述会话管理实体，用于接收来自所述策略控制实体的所述第二指示信息，并根据所述第二指示信息，确定所述第一指示信息。
  42. 根据权利要求41所述的通信系统，其特征在于，所述第二指示信息用于指示所述第一业务的数据传输间隔时间固定。
  43. 根据权利要求40-42任一项所述的通信系统，其特征在于，所述第一指示信息用于指示所述第一业务的数据传输间隔时间固定。
PCT/CN2021/081070 2021-03-16 2021-03-16 业务调度方法、装置及系统 WO2022193127A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/081070 WO2022193127A1 (zh) 2021-03-16 2021-03-16 业务调度方法、装置及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/081070 WO2022193127A1 (zh) 2021-03-16 2021-03-16 业务调度方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2022193127A1 true WO2022193127A1 (zh) 2022-09-22

Family

ID=83321783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/081070 WO2022193127A1 (zh) 2021-03-16 2021-03-16 业务调度方法、装置及系统

Country Status (1)

Country Link
WO (1) WO2022193127A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110830268A (zh) * 2018-08-13 2020-02-21 华为技术有限公司 通信方法和通信装置
US20200120536A1 (en) * 2018-10-15 2020-04-16 Qualcomm Incorporated Timing information for multiple periodic traffic streams sharing a same quality of service

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110830268A (zh) * 2018-08-13 2020-02-21 华为技术有限公司 通信方法和通信装置
US20200120536A1 (en) * 2018-10-15 2020-04-16 Qualcomm Incorporated Timing information for multiple periodic traffic streams sharing a same quality of service

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced support of Industrial Internet of Things (IIoT) in the 5G System (5GS) (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-20, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.4.0, 29 June 2020 (2020-06-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 56, XP051924137 *
NOKIA, NOKIA SHANGHAI BELL, CATT, SAMSUNG: "KI#X, New Sol: Survival Time for Deterministic Applications", 3GPP DRAFT; S2-2004329, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200601 - 20200612, 28 May 2020 (2020-05-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051892265 *

Similar Documents

Publication Publication Date Title
WO2020253456A1 (zh) 数据传输的方法、管理服务质量流的方法、设备及介质
US20210337404A1 (en) Service continuity implementation method, apparatus, and system
EP3675551B1 (en) Method and system for detecting quality of service of service
CN110831033B (zh) 服务质量监测方法、设备及系统
US11463346B2 (en) Data processing method, device, and system
WO2020088253A1 (zh) 用于无线回传网络的数据传输方法和装置
WO2021031672A1 (zh) 通知服务质量信息的方法、设备及系统
WO2022048505A1 (zh) 多流关联传输的方法、装置及系统
WO2021227559A1 (zh) 通信方法、装置及系统
WO2020147440A1 (zh) 数据用量上报的方法、装置及系统
CN112019363B (zh) 确定业务传输需求的方法、设备及系统
WO2021159724A1 (zh) 通信方法、装置及系统
WO2022193127A1 (zh) 业务调度方法、装置及系统
WO2021228163A1 (zh) 确定资源的方法、装置及系统
WO2024109556A1 (zh) 一种通信方法及装置
WO2023179172A1 (zh) 通信方法及装置
WO2020192263A1 (zh) 计费规则绑定的方法、设备及系统
WO2024104253A1 (zh) 通信方法、装置和系统
WO2023143255A1 (zh) 一种通信方法及装置
WO2021046746A1 (zh) 上报会话管理信息的方法、设备及系统
WO2020034922A1 (zh) 服务质量监测方法、设备及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21930723

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21930723

Country of ref document: EP

Kind code of ref document: A1