[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2023173841A1 - 一种同步调度方法、通信装置及通信系统 - Google Patents

一种同步调度方法、通信装置及通信系统 Download PDF

Info

Publication number
WO2023173841A1
WO2023173841A1 PCT/CN2022/137958 CN2022137958W WO2023173841A1 WO 2023173841 A1 WO2023173841 A1 WO 2023173841A1 CN 2022137958 W CN2022137958 W CN 2022137958W WO 2023173841 A1 WO2023173841 A1 WO 2023173841A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packets
synchronized
need
target service
access network
Prior art date
Application number
PCT/CN2022/137958
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 华为技术有限公司
Publication of WO2023173841A1 publication Critical patent/WO2023173841A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows

Definitions

  • the embodiments of the present application relate to the field of communication technology, and in particular, to a synchronization scheduling method, a communication device and a communication system.
  • a service can generate multiple data streams, and users can use one or more terminal devices to (such as glasses, handles, gloves, fingertip devices, exercise mats or fitness rings, etc.) simultaneously receive multiple data streams, including video data streams, audio data streams, and sensory data streams, allowing users to gain more intense
  • the immersion creates an immersive feeling, which greatly enhances the user experience.
  • Embodiments of the present application provide a synchronization scheduling method, communication device, and communication system for realizing synchronization scheduling between multiple QoS flows of the same service, thereby improving user experience.
  • embodiments of the present application provide a synchronization scheduling method, which can be executed by an access network device or a module (such as a chip) applied to the access network device.
  • the method includes: the access network device receives multiple data packets of the target service from the user plane network element, the multiple data packets belong to multiple QoS flows, and the multiple data packets Each data packet in contains QFI, which is used to identify the QoS flow to which the data packet belongs.
  • the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized; the access network device obtains the QoS flow from the multiple QoS flows that need to be synchronized.
  • the access network device starts from the data packets containing the same mark information.
  • the at least two data packets determine at least two target data packets, and the at least two target data packets correspond to at least two QoS flows of the target service that need to be synchronized; the access network device determines at least two target data packets based on the at least two target data packets.
  • the data packets of at least two QoS flows of the target service that need to be synchronized are scheduled synchronously.
  • the access network device synchronizes the data packets of at least two QoS flows of the target service that need to be synchronized according to the at least two target data packets, so that a reasonable sending speed is maintained between multiple QoS flows of the target service. , so that the multiple QoS flows can maintain coordination and improve the user experience.
  • the method is to first identify at least two data packets that may contain at least two QoS flows of the target service that need to be synchronized from multiple data packets of the target service, and then identify the QoS flow from the at least two data packets. At least two target data packets of at least two QoS flows of the target service that need to be synchronized.
  • the search scope of the data packets of at least two QoS flows of the target service that need to be synchronized is narrowed, and the search range is reduced to avoid a large number of data packets.
  • the access network device before the access network device receives multiple data packets of the target service from the user plane network element, the access network device receives an association identifier from the session management network element, and the association identifier is associated with the target.
  • multiple data connection sessions belonging to at least two QoS flows of the target service that need to be synchronized are associated through association identifiers, and the access network device learns that the at least two QoS flows of the target service that need to be synchronized will be in Transmission is carried out in these multiple data connection sessions, but not in other data connection sessions, so that the access network device can determine the marking information for the multiple data connection sessions and send the marking information to the user plane network element, In order to facilitate the user plane network element to add the marking information in the data packets of the QoS flows in the multiple data connection sessions.
  • the access network device determines whether the received data packet contains the tag information and determines that the data packet may be at least two QoS flows of the target service that need to be synchronized, or it may not be at least two QoS flows of the target service that need to be synchronized. , so the access network device can use the marking information to narrow the search range of at least two QoS flows that need to be synchronized for the target service, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the marking information is a group identifier assigned by the access network device, and the group identifier corresponds to the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the access network device allocates the group identifier as marking information, which can ensure the uniqueness of the group identifier and help ensure that the access network device searches for the data packets of at least two QoS flows that need to be synchronized according to the group identifier when searching for the target service.
  • the accuracy and search speed are improved, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the marking information is an access network tunnel endpoint identifier.
  • the access network tunnel endpoint identifier is used to identify a GTP-U tunnel.
  • the GTP-U tunnel is used to transmit at least the target service that needs to be synchronized.
  • the QoS flows in the data connection session to which both QoS flows belong.
  • the access network device allocates the access network tunnel endpoint identifier as marking information.
  • the GTP-U tunnel indicated by the access network tunnel endpoint identifier is used to transmit multiple QoS flows belonging to at least two QoS flows that need to be synchronized for the target service.
  • the QoS flow in the data connection session means that at least two QoS flows of the target service that need to be synchronized are transmitted through the same GTP-U tunnel, so that the access network device only needs to search for the target service in the GTP-U tunnel.
  • At least two QoS flows that need to be synchronized do not need to be searched for at least two QoS flows that need to be synchronized for the target service in other GTP-U tunnels, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the marking information includes an association identifier and the identification information of a network device.
  • the association identifier is associated with the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the network device is the one that generates the association.
  • the combination of the association identifier and the identification information of the network device is used as tag information, which can ensure the uniqueness of the tag information and help ensure that the access network device searches for the target service based on the tag information and synchronizes at least two QoS flows.
  • the accuracy of data packet timing and improved search speed will help improve the speed of synchronization scheduling and improve user experience.
  • the access network device receives the QFIs of at least two QoS flows of the target service that need to be synchronized from the session management network element; wherein the at least two target data packets refer to the QFIs containing the target QFIs.
  • the target QFI is any one of the QFIs of at least two QoS flows that need to be synchronized for the target service.
  • the session management network element sends the QFI of at least two QoS flows of the target service that need to be synchronized to the access network device, so that the access network device can subsequently synchronize the QFI of at least two QoS flows according to the needs of the target service.
  • the at least two target data packets refer to data packets containing a synchronization indication
  • the synchronization indication is used to indicate that the QoS flow to which the data packet belongs is a QoS flow of the target service that requires synchronization.
  • the access network equipment can accurately identify the data packets of at least two QoS flows of the target service that need to be synchronized based on whether the data packets carry synchronization instructions, thereby helping to achieve correct synchronization of the QoS flows of the target service and improving user experience.
  • the access network device performs synchronization scheduling on the data packets of at least two QoS flows of the target service that need to be synchronized based on the at least two target data packets, which specifically includes: the access network device According to the synchronization status information and the frame numbers contained in the at least two target data packets, the data packets of at least two QoS flows of the target service that need to be synchronized are synchronized and scheduled.
  • the synchronization status information is used to indicate that the target is in the synchronization status.
  • the access network equipment can implement packet-granular synchronization scheduling based on the synchronization status information and the frame number in the target data packet, which helps to achieve precise synchronization between at least two QoS flows that need to be synchronized for the target service. Thereby improving user experience.
  • the access network device performs synchronization scheduling on the data packets of at least two QoS flows of the target service that need to be synchronized based on the synchronization status information and the frame numbers contained in the at least two target data packets, Specifically, the access network device determines that at least two QoS flows that need to be synchronized for the target service do not meet the synchronization accuracy based on the synchronization status information and the frame numbers contained in the at least two target data packets, and then adjusts the needs of the target service.
  • the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows that need to be synchronized for the target service in the synchronization state.
  • the access network device determines whether the at least two QoS flows of the target service that need to be synchronized meet the synchronization accuracy. If the synchronization accuracy is not met, the access network device adjusts the sending speed of the data packets of the at least two QoS flows of the target service that need to be synchronized. , since the synchronization precision can be set according to actual needs, this method can achieve the flexibility of synchronization scheduling.
  • the access network device receives the synchronization status information and the synchronization accuracy from the session management network element.
  • the session management network element sends synchronization status information and synchronization accuracy to the access network device, which can realize flexible configuration of synchronization status information and synchronization accuracy.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the above solution can realize synchronous scheduling between multiple QoS flows in the scenario of multiple terminal devices, thereby enhancing user experience.
  • embodiments of the present application provide a synchronization scheduling method, which can be executed by an access network device or a module (such as a chip) applied to the access network device.
  • the method includes: the access network device receives multiple data packets of the target service from the user plane network element, the multiple data packets belong to multiple QoS flows, and the multiple data packets Each data packet in contains QFI, which is used to identify the QoS flow to which the data packet belongs.
  • the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized; the access network device obtains the QoS flow from the multiple QoS flows that need to be synchronized.
  • the data packets are determined to contain at least two data packets with the same access network tunnel endpoint identifier.
  • the at least two data packets correspond to at least two QoS flows of the target service that need to be synchronized.
  • the access network tunnel endpoint identifier is used to identify
  • the target tunnel is a GTP-U tunnel that transmits at least two QoS flows of the target service that need to be synchronized.
  • the at least two QoS flows of the target service that need to be synchronized correspond to data connection sessions; the access network device is based on the At least two data packets, and the data packets of at least two QoS flows of the target service that need to be synchronized are scheduled synchronously.
  • the access network device synchronizes the data packets of at least two QoS flows of the target service that need to be synchronized based on the at least two data packets, so that a reasonable sending speed is maintained between multiple QoS flows of the target service.
  • This maintains coordination among the multiple QoS flows and improves user experience.
  • this method uses a one-step search method to identify at least two data packets of at least two QoS flows of the target service that need to be synchronized from multiple data packets of the target service. Therefore, the synchronization speed can be improved and rapid Synchronous scheduling to further enhance user experience.
  • the access network device before the access network device receives multiple data packets of the target service from the user plane network element, the access network device receives the association identifier from the session management network element and needs to be synchronized with the target service.
  • the QFI of at least two QoS flows the association identifier is associated with the data connection session to which at least two QoS flows of the target service need to be synchronized; the access network device is based on the association identifier and at least two QoS flows of the target service that need to be synchronized.
  • the QFI of each QoS flow determines the access network tunnel endpoint identifier for at least two QoS flows that need to be synchronized for the target service; the access network device sends the access network tunnel endpoint identifier to the user plane network element through the session management network element. Tunnel endpoint identifier.
  • multiple data connection sessions belonging to at least two QoS flows of the target service that need to be synchronized are associated through association identifiers, and the access network device learns that the at least two QoS flows of the target service that need to be synchronized will be in Transmission is performed in the multiple data connection sessions, but not in other data connection sessions, and the access network device learns the target service based on the received QFI of at least two QoS flows that need to be synchronized for the target service.
  • the at least two QoS flows that need to be synchronized are specifically which QoS flows among the multiple data connection sessions.
  • the access network device determines the access network tunnel endpoint identifier for these QoS flows and sends the access network element to the user plane network element.
  • the GTP-U tunnel indicated by the access network tunnel endpoint identifier is dedicated to transmitting at least two QoS flows that need to be synchronized for the target service, so that the QoS flows received by the access network device from the GTP-U tunnel are uniform. There are at least two QoS flows for the target service that need to be synchronized.
  • the access network device does not need to search for at least two QoS flows for the target service that need to be synchronized in other GTP-U tunnels, which helps to improve the speed of synchronization scheduling. , improve user experience.
  • the access network device performs synchronization scheduling on the data packets of at least two QoS flows of the target service that need to be synchronized based on the at least two data packets, which specifically includes: the access network device performs synchronization scheduling based on the at least two data packets.
  • the synchronization status information and the frame numbers contained in the at least two data packets are used to synchronize the data packets of the at least two QoS flows that need to be synchronized for the target service.
  • the synchronization status information is used to indicate that the target service is in the synchronization state. The correspondence between the frame numbers in the data packets of at least two QoS flows that need to be synchronized.
  • the access network equipment can implement packet-granular synchronization scheduling based on the synchronization status information and the frame number in the target data packet, which helps to achieve precise synchronization between at least two QoS flows that need to be synchronized for the target service. Thereby improving user experience.
  • the access network device performs synchronization scheduling on the data packets of at least two QoS flows of the target service that need to be synchronized based on the synchronization status information and the frame numbers contained in the at least two data packets. Specifically, Including: the access network device determines that at least two QoS flows of the target service that need to be synchronized do not meet the synchronization accuracy based on the synchronization status information and the frame numbers contained in the at least two data packets, and then adjusts the flow of the target service that needs to be synchronized.
  • the sending speed of data packets of at least two QoS flows, and the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the access network device determines whether the at least two QoS flows of the target service that need to be synchronized meet the synchronization accuracy. If the synchronization accuracy is not met, the access network device adjusts the sending speed of the data packets of the at least two QoS flows of the target service that need to be synchronized. , since the synchronization precision can be set according to actual needs, this method can achieve the flexibility of synchronization scheduling.
  • the access network device receives the synchronization status information and the synchronization accuracy from the session management network element.
  • the session management network element sends synchronization status information and synchronization accuracy to the access network device, which can realize flexible configuration of synchronization status information and synchronization accuracy.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the above solution can realize synchronous scheduling between multiple QoS flows in the scenario of multiple terminal devices, thereby enhancing user experience.
  • embodiments of the present application provide a synchronization scheduling method, which can be executed by an access network device or a module (such as a chip) applied to the access network device.
  • the method includes: the access network device receives multiple data packets of the target service from the user plane network element, the multiple data packets belong to multiple QoS flows, and the multiple data packets Each data packet in the packet contains QFI, which is used to identify the QoS flow to which the data packet belongs.
  • the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized; the access network device is based on multiple interfaces.
  • the synchronization relationship between the access network tunnel endpoint identifiers determines at least two data packets from the multiple data packets, and each of the at least two data packets also includes the multiple access network tunnel endpoint identifiers. Any access network tunnel endpoint identifier, and the GTP-U tunnels respectively indicated by the multiple access network tunnel endpoint identifiers are used to transmit at least two QoS flows that need to be synchronized for the target service; the access network device starts from the at least The two data packets determine at least two target data packets, and the at least two target data packets correspond to at least two QoS flows of the target service that need to be synchronized; the access network device determines the target data based on the at least two target data packets.
  • the data packets of at least two QoS flows that need to be synchronized for the business are scheduled synchronously.
  • the access network device synchronizes the data packets of at least two QoS flows of the target service that need to be synchronized according to the at least two target data packets, so that a reasonable sending speed is maintained between multiple QoS flows of the target service. , so that the multiple QoS flows can maintain coordination and improve the user experience.
  • the method is to first identify at least two data packets that may contain at least two QoS flows of the target service that need to be synchronized from multiple data packets of the target service, and then identify the QoS flow from the at least two data packets. At least two target data packets of at least two QoS flows of the target service that need to be synchronized.
  • the search scope of the data packets of at least two QoS flows of the target service that need to be synchronized is narrowed, and the search range is reduced to avoid a large number of data packets.
  • the access network device before the access network device receives multiple data packets of the target service from the user plane network element, the access network device receives an association identifier from the session management network element, and the association identifier is associated with the target.
  • the access network device determines the multiple access network tunnel endpoint identifiers for the data connection session to which at least two QoS flows of the target service that need to be synchronized belong,
  • the multiple access network tunnel endpoint identifiers correspond one-to-one to the data connection sessions to which at least two QoS flows of the target service that need to be synchronized belong; the access network device establishes the synchronization relationship based on the association identifier.
  • multiple data connection sessions belonging to at least two QoS flows of the target service that need to be synchronized are associated through association identifiers, and the access network device learns that the at least two QoS flows of the target service that need to be synchronized will be in Transmission is carried out in the multiple data connection sessions, but not in other data connection sessions, so that the access network device can assign access network tunnel endpoint identifiers to the multiple data connection sessions respectively, and establish these access networks. Synchronization relationship between tunnel endpoint identities.
  • the access network device After receiving the data packet, the access network device determines that the data packet may be at least two QoS flows of the target service that need to be synchronized based on the synchronization relationship and the access network tunnel endpoint identifier contained in the data packet, or it may not be the At least two QoS flows of the target service need to be synchronized, so the access network equipment can gradually narrow the search range of at least two QoS flows of the target service that need to be synchronized, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the access network device before the access network device receives multiple data packets of the target service from the user plane network element, the access network device receives data belonging to at least two QoS flows of the target service that need to be synchronized.
  • the connection session determines the multiple access network tunnel endpoint identifiers, and the multiple access network tunnel endpoint identifiers correspond one-to-one to the data connection sessions to which at least two QoS flows of the target service that need to be synchronized belong; the access network device
  • the session management network element sends the multiple access network tunnel endpoint identifiers; the access network device receives the synchronization relationship from the session management network element.
  • the session management network element determines multiple data connection sessions to which at least two QoS flows of the target service need to be synchronized, establishes a synchronization relationship between the access network tunnel endpoint identifiers corresponding to the multiple data connection sessions, and Send the synchronization relationship to the access network device.
  • the access network device determines that the data packet may be a data packet in at least two QoS flows of the target service that need to be synchronized based on the synchronization relationship and the access network tunnel endpoint identifier contained in the data packet.
  • the access network equipment can gradually narrow the search range of at least two QoS flows of the target service that need to be synchronized, thereby helping to improve synchronization scheduling. speed and improve user experience.
  • the access network device receives the QFI of at least two QoS flows that need to be synchronized for the target service from the session management network element; wherein the at least two target data packets refer to the QFIs containing Data packet of the target QFI, which is any one of the QFIs of at least two QoS flows of the target service that need to be synchronized.
  • the session management network element sends the QFI of at least two QoS flows of the target service that need to be synchronized to the access network device, so that the access network device can subsequently synchronize the QFI of at least two QoS flows according to the needs of the target service.
  • the at least two target data packets refer to data packets containing a synchronization indication
  • the synchronization indication is used to indicate that the QoS flow to which the data packet belongs is a QoS flow of the target service that requires synchronization.
  • the access network equipment can accurately identify the data packets of at least two QoS flows of the target service that need to be synchronized based on whether the data packets carry synchronization instructions, thereby helping to achieve correct synchronization of the QoS flows of the target service and improving user experience.
  • the access network device performs synchronization scheduling on the data packets of at least two QoS flows of the target service that need to be synchronized based on the at least two target data packets, which specifically includes: the access network device According to the synchronization status information and the frame numbers contained in the at least two target data packets, the data packets of at least two QoS flows of the target service that need to be synchronized are synchronized and scheduled.
  • the synchronization status information is used to indicate that the target is in the synchronization status.
  • the access network equipment can implement packet-granular synchronization scheduling based on the synchronization status information and the frame number in the target data packet, which helps to achieve precise synchronization between at least two QoS flows that need to be synchronized for the target service. Thereby improving user experience.
  • the access network device performs synchronization scheduling on the data packets of at least two QoS flows of the target service that need to be synchronized based on the synchronization status information and the frame numbers contained in the at least two target data packets, Specifically, the access network device determines that at least two QoS flows that need to be synchronized for the target service do not meet the synchronization accuracy based on the synchronization status information and the frame numbers contained in the at least two target data packets, and then adjusts the needs of the target service.
  • the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows that need to be synchronized for the target service in the synchronization state.
  • the access network device determines whether the at least two QoS flows of the target service that need to be synchronized meet the synchronization accuracy. If the synchronization accuracy is not met, the access network device adjusts the sending speed of the data packets of the at least two QoS flows of the target service that need to be synchronized. , since the synchronization precision can be set according to actual needs, this method can achieve the flexibility of synchronization scheduling.
  • the access network device receives the synchronization status information and the synchronization accuracy from the session management network element.
  • the session management network element sends synchronization status information and synchronization accuracy to the access network device, which can realize flexible configuration of synchronization status information and synchronization accuracy.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the above solution can realize synchronous scheduling between multiple QoS flows in the scenario of multiple terminal devices, thereby enhancing user experience.
  • embodiments of the present application provide a synchronous scheduling method, which can be executed by a user plane network element or a module (such as a chip) applied to a user plane network element.
  • the method includes: the user plane network element receives multiple data packets of target services from the application function network element, the multiple data packets belong to multiple QoS flows, and the multiple QoS flows Including at least two QoS flows of the target service that need to be synchronized; the user plane network element adds marking information and quality of service flow identifier QFI to at least two data packets of the plurality of data packets, and each of the at least two data packets The QFI in each data packet is used to identify the quality of service QoS flow to which the data packet belongs.
  • the marking information corresponds to multiple protocol data unit data connection sessions belonging to at least two QoS flows of the target service that need to be synchronized; the user plane network
  • the element sends a plurality of data packets including at least two data packets of the added marking information and QFI to the access network device.
  • the user plane network element adds tag information to at least two data packets of multiple data packets of the target service, so that the access network device learns based on the tag information that the data packet carrying the tag information is a possible requirement of the target service.
  • the data packets of at least two QoS flows that need to be synchronized, and the data packets that do not carry the tag information are not the data packets of the at least two QoS flows that need to be synchronized for the target service, thereby narrowing the number of at least two QoS flows that need to be synchronized for the target service.
  • the search range of data packets of the QoS flow prevents the access network equipment from blindly searching for the data packets of at least two QoS flows of the target service that need to be synchronized from a large number of QoS flows. Therefore, the synchronization speed can be improved and rapid synchronization scheduling can be achieved, further Improve user experience.
  • the user plane network element receives the marking information from the access network device.
  • the access network device allocates tag information, which can ensure the uniqueness of the tag information and help ensure the accuracy when the access network device searches for data packets of at least two QoS flows that need to be synchronized according to the tag information for the target service. and improve search speed, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the marking information is a group identifier assigned by the access network device, and the group identifier corresponds to the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the access network device allocates the group identifier as marking information, which can ensure the uniqueness of the group identifier and help ensure that the access network device searches for the data packets of at least two QoS flows that need to be synchronized according to the group identifier when searching for the target service.
  • the accuracy and search speed are improved, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the marking information is an access network tunnel endpoint identifier.
  • the access network tunnel endpoint identifier is used to identify a GTP-U tunnel.
  • the GTP-U tunnel is used to transmit at least the target service that needs to be synchronized.
  • the QoS flows in the data connection session to which both QoS flows belong.
  • the access network device allocates the access network tunnel endpoint identifier as marking information.
  • the GTP-U tunnel indicated by the access network tunnel endpoint identifier is used to transmit multiple QoS flows belonging to at least two QoS flows that need to be synchronized for the target service.
  • the QoS flow in the data connection session means that at least two QoS flows of the target service that need to be synchronized are transmitted through the same GTP-U tunnel, so that the access network device only needs to search for the target service in the GTP-U tunnel.
  • At least two QoS flows that need to be synchronized do not need to be searched for at least two QoS flows that need to be synchronized for the target service in other GTP-U tunnels, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the marking information includes an association identifier and the identification information of a network device.
  • the association identifier is associated with the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the network device is the one that generates the association.
  • the combination of the association identifier and the identification information of the network device is used as tag information, which can ensure the uniqueness of the tag information and help ensure that the access network device searches for the target service based on the tag information and synchronizes at least two QoS flows.
  • the accuracy of data packet timing and improved search speed will help improve the speed of synchronization scheduling and improve user experience.
  • the user plane network element receives the QFI of at least two QoS flows that need to be synchronized for the target service from the session management network element; the user plane network element sends the added tag to the access network device.
  • the user plane network element synchronizes the QFI of at least two QoS flows according to the needs of the target service, and before the at least two data packets of the at least two target data A synchronization indication is added to the packet.
  • the at least two target data packets correspond to at least two QoS flows of the target service that need to be synchronized.
  • the synchronization indication is used to indicate that the QoS flow to which the target data packet belongs is the at least two QoS flows of the target service that need to be synchronized. Two QoS flows.
  • the access network equipment can accurately identify the data packets of at least two QoS flows of the target service that need to be synchronized based on whether the data packets carry synchronization instructions, thereby helping to achieve correct synchronization of the QoS flows of the target service and improving user experience.
  • the at least two target data packets each include a frame number, and the frame number is used for synchronization scheduling of at least two QoS flows that require synchronization of the target service.
  • the access network equipment can implement synchronization scheduling at the granularity of data packets based on the frame number in the target data packet, which helps to achieve precise synchronization between at least two QoS flows that need to be synchronized for the target service, thus improving user experience. .
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the above solution can realize synchronous scheduling between multiple QoS flows in the scenario of multiple terminal devices, thereby enhancing user experience.
  • embodiments of the present application provide a synchronization scheduling method, which can be executed by a session management network element or a module (such as a chip) applied to the session management network element.
  • the method includes: the session management network element generates an association identifier, and the association identifier is associated with the data connection session to which at least two QoS flows of the target service that need to be synchronized belong; The access network device sends the association identifier, and the association identifier is used for synchronous scheduling of at least two QoS flows that need to be synchronized for the target service.
  • multiple data connection sessions belonging to at least two QoS flows of the target service that need to be synchronized are associated through association identifiers, and the access network device learns that the at least two QoS flows of the target service that need to be synchronized will be in Transmission is carried out in these multiple data connection sessions, but not in other data connection sessions, which helps the access network device to use this association identifier to narrow the search scope of at least two QoS flows that need to be synchronized for the target service, and then It helps to improve the speed of synchronization scheduling and improve user experience.
  • the session management network element sends synchronization accuracy and synchronization status information to the access network device.
  • the synchronization status information is used to indicate at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the correspondence between the frame numbers in the data packets, and the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the session management network element sends synchronization accuracy and synchronization status information to the access network device, so that the access network device can determine whether at least two QoS flows of the target service that need to be synchronized meet the synchronization accuracy based on the synchronization status information and synchronization accuracy. , when the synchronization accuracy is not met, adjust the sending speed of data packets of at least two QoS flows of the target service that need to be synchronized. Since the synchronization accuracy can be set according to actual needs, this method can achieve the flexibility of synchronization scheduling.
  • the session management network element receives the PCC rule from the policy control network element, where the PCC rule includes the identification information of the target service and the synchronization status information.
  • the session management network element sends the QFI of at least two QoS flows of the target service that need to be synchronized to the user plane network element.
  • embodiments of the present application provide a synchronization scheduling method, which can be executed by a session management network element or a module (such as a chip) applied to the session management network element.
  • the method includes: the session management network element determines the data connection session to which at least two QoS flows of the target service that need to be synchronized belong; the session management network element receives the target from the access network device Multiple access network tunnel endpoint identifiers corresponding to the data connection sessions to which at least two QoS flows of the service need to be synchronized.
  • the data connection sessions to which at least two QoS flows of the target service need to be synchronized belong to the multiple access networks.
  • the session management network element establishes a synchronization relationship between the multiple access network tunnel endpoint identifiers; the session management network element sends the synchronization relationship to the access network device, and the synchronization relationship is used for the target Synchronous scheduling of at least two QoS flows that require synchronization of services.
  • the session management network element determines multiple data connection sessions to which at least two QoS flows of the target service need to be synchronized, establishes a synchronization relationship between the access network tunnel endpoint identifiers corresponding to the multiple data connection sessions, and Send the synchronization relationship to the access network device.
  • the access network device After receiving the data packet, the access network device determines that the data packet may be at least two QoS flows of the target service that need to be synchronized based on the synchronization relationship and the access network tunnel endpoint identifier contained in the data packet, or it may not be the At least two QoS flows of the target service need to be synchronized, so the access network equipment can gradually narrow the search range of at least two QoS flows of the target service that need to be synchronized, which in turn helps to increase the speed of synchronization scheduling and improve user experience.
  • the session management network element sends synchronization accuracy and synchronization status information to the access network device.
  • the synchronization status information is used to indicate at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the correspondence between the frame numbers in the data packets, and the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the session management network element sends synchronization accuracy and synchronization status information to the access network device, so that the access network device can determine whether at least two QoS flows of the target service that need to be synchronized meet the synchronization accuracy based on the synchronization status information and synchronization accuracy. , when the synchronization accuracy is not met, adjust the sending speed of data packets of at least two QoS flows of the target service that need to be synchronized. Since the synchronization accuracy can be set according to actual needs, this method can achieve the flexibility of synchronization scheduling.
  • the session management network element receives the PCC rule from the policy control network element, where the PCC rule includes the identification information of the target service and the synchronization status information.
  • the session management network element sends the QFI of at least two QoS flows of the target service that need to be synchronized to the user plane network element.
  • embodiments of the present application provide a communication device, which may be an access network device or a module (such as a chip) applied in the access network device.
  • the device has the function of realizing any implementation method of the above-mentioned first aspect to the third aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, which may be a user plane network element or a module (such as a chip) applied in a user plane network element.
  • the device has the function of implementing any implementation method of the fourth aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, which may be a session management network element or a module (such as a chip) applied in the session management network element.
  • the device has the function of realizing any implementation method of the fifth aspect or the sixth aspect. This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • embodiments of the present application provide a communication device, including a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory, so that the device executes Any implementation method in the above first to sixth aspects.
  • embodiments of the present application provide a communication device, including units or means for executing each step of any implementation method in the above-mentioned first to sixth aspects.
  • embodiments of the present application provide a communication device, including a processor and an interface circuit.
  • the processor is configured to communicate with other devices through the interface circuit and perform any implementation method in the above-mentioned first to sixth aspects.
  • the processor includes one or more.
  • embodiments of the present application provide a communication device, including a processor coupled to a memory.
  • the processor is configured to call a program stored in the memory to execute any implementation of the above-mentioned first to sixth aspects. method.
  • the memory may be located within the device or external to the device.
  • the processor can be one or more.
  • embodiments of the present application further provide a computer-readable storage medium in which instructions are stored, and when run on a communication device, the instructions in the first to sixth aspects described above are achieved. Any implementation method of is executed.
  • embodiments of the present application further provide a computer program product.
  • the computer program product includes a computer program or instructions.
  • the computer program or instructions are run by a communication device, any one of the above-mentioned first to sixth aspects is enabled.
  • the implementation method is executed.
  • embodiments of the present application further provide a chip system, including: a processor, configured to execute any of the implementation methods in the above-mentioned first to sixth aspects.
  • embodiments of the present application further provide a communication system, including: a user plane network element, and an access network device for performing any of the implementation methods of the first to third aspects; the user plane network element , used to send multiple data packets of the target service to the access network device.
  • the communication system further includes a session management network element that performs any implementation method of the fifth or sixth aspect.
  • embodiments of the present application further provide a communication system, including: an access network device, and a user plane network element for performing any implementation method of the fourth aspect; the access network device is configured to: The user plane network element receives multiple data packets.
  • the communication system further includes a session management network element that performs any implementation method of the fifth or sixth aspect.
  • embodiments of the present application further provide a communication system, including: an access network device for performing any implementation method of the above first to third aspects, and an access network device for performing any implementation method of the above fourth aspect.
  • a communication system including: an access network device for performing any implementation method of the above first to third aspects, and an access network device for performing any implementation method of the above fourth aspect.
  • User plane network element of the method including: an access network device for performing any implementation method of the above first to third aspects, and an access network device for performing any implementation method of the above fourth aspect.
  • the communication system further includes a session management network element that performs any implementation method of the fifth or sixth aspect.
  • Figure 1 is a schematic diagram of the 5G network architecture based on service-based architecture
  • Figure 2(a) is a schematic flow chart of a synchronous scheduling method provided by an embodiment of the present application.
  • Figure 2(b) is a schematic flow chart of a synchronous scheduling method provided by an embodiment of the present application.
  • Figure 2(c) is a schematic flow chart of a synchronous scheduling method provided by an embodiment of the present application.
  • Figure 3(a) is a schematic diagram of an example provided by the embodiment of the present application.
  • Figure 3(b) is an example diagram of GTP-U tunnel allocation provided by the embodiment of the present application.
  • Figure 3(c) is another example diagram of GTP-U tunnel allocation provided by the embodiment of the present application.
  • Figure 3(d) is another example diagram of GTP-U tunnel allocation provided by the embodiment of the present application.
  • Figure 4 is a schematic flow chart of a synchronization scheduling method provided by an embodiment of the present application.
  • Figure 5 is a schematic flow chart of a synchronization scheduling method provided by an embodiment of the present application.
  • Figure 6 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of a synchronization scheduling method provided by an embodiment of the present application.
  • Figure 8 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • Figure 9 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • Figure 10 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • Figure 11 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • Figure 1 is a schematic diagram of the 5G network architecture based on service-based architecture.
  • the 5G network architecture shown in Figure 1 can include terminal equipment, access network and core network. Terminal equipment is connected to the data network (DN) through the access network and core network.
  • DN data network
  • the terminal equipment can be user equipment (UE), mobile station, mobile terminal, etc.
  • Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), and the Internet of Things (internet of things, IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, urban air vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc.
  • the following description takes the UE as an example of a terminal device.
  • the UE appearing anywhere subsequently can also be replaced with a terminal device or other examples of a terminal device.
  • the access network is used to implement access-related functions. It can provide network access functions for authorized users in a specific area, and can determine transmission links of different qualities to transmit user data based on user levels, business needs, etc.
  • the access network forwards control signals and user data between the UE and the core network.
  • the access network may include access network equipment, which may be equipment that provides access for UEs, and may include wireless access network (radio access network, RAN) equipment and wired access network equipment.
  • RAN equipment is mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • RAN equipment can include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, access points, balloon stations, etc.
  • the names of equipment with base station functions may be different.
  • RAN next-generation Node base station
  • gNB next-generation Node base station
  • LTE long term evolution
  • eNB evolved NodeB
  • the access network equipment and UE can be fixed-positioned or mobile. Access network equipment and UE can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky.
  • the embodiments of this application do not limit the application scenarios of access network equipment and UE.
  • the core network is responsible for maintaining the subscription data of the mobile network and providing functions such as session management, mobility management, policy management, and security authentication for UEs.
  • the core network includes but is not limited to one or more of the following network elements: application function (AF) network element, unified data management (UDM) network element, unified data repository (UDR) network element , policy control function (PCF) network element, session management function (SMF) network element, access and mobility management function (AMF) network element, network storage function ( network repository function (NRF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, user plane function (UPF) network element.
  • AF application function
  • UDM unified data management
  • UDR unified data repository
  • PCF policy control function
  • SMF session management function
  • AMF access and mobility management function
  • NRF network storage function
  • AUSF authentication server function
  • NEF network exposure function
  • UPF user plane function
  • the AMF network element is mainly responsible for mobility management in mobile networks, such as user location update, user registration network, user switching, etc.
  • the SMF network element is mainly responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users, selecting UPF that provides message forwarding functions, etc.
  • IP Internet Protocol
  • the UPF network element is mainly responsible for forwarding and receiving user data. It can receive user data from the data network and transmit it to the UE through the access network device. It can also receive user data from the UE through the access network device and forward it to the data network.
  • UDM network elements include functions such as execution and management of contract data and user access authorization.
  • the UDR network element includes access functions for executing contract data, policy data, application data and other types of data.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • AF network element transmits the requirements from the application side to the network side, such as QoS requirements or user status event subscriptions.
  • AF can be a third-party functional entity or an application service deployed by an operator, such as IP Multimedia Subsystem (IMS) voice call service.
  • IMS IP Multimedia Subsystem
  • the PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions.
  • PCF network elements can provide policies, such as QoS policies, slice selection policies, etc., to AMF network elements and SMF network elements.
  • NRF network elements can be used to provide network element discovery functions and provide network element information corresponding to network element types based on requests from other network elements.
  • NRF also provides network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.
  • the AUSF network element is responsible for authenticating the UE and verifying the legitimacy of the UE.
  • DN on which a variety of services can be deployed, can provide data and/or voice services to UEs.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be UEs.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is the internal office network of a company.
  • the mobile phones or computers of employees of the company can be UE.
  • the employees' mobile phones or computers can access information and data resources on the company's internal office network.
  • AF network element UDM network element, UDR network element, PCF network element, SMF network element, AMF network element, NRF network element, AUSF network element, NEF network element, UPF network element can also be referred to as AF and UDM respectively.
  • UDR, PCF, SMF, AMF, NRF, AUSF, NEF UPF.
  • Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Nudr, and Naf are the service interfaces provided by the above-mentioned AUSF, NEF, NRF, AMF, PCF, SMF, UDM, UDR, and AF respectively, and are used to call the corresponding service operations.
  • N1, N2, N3, N4 and N6 are interface serial numbers. The meanings of these interface serial numbers are as follows:
  • N1 The interface between AMF and UE can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from AMF) to UE.
  • NAS non-access stratum
  • N2 The interface between AMF and access network equipment can be used to transmit wireless bearer control information from the core network side to the access network equipment, etc.
  • N3 The interface between the access network equipment and UPF, mainly used to transmit uplink and downlink user plane data between the access network equipment and UPF.
  • N4 The interface between SMF and UPF can be used to transfer information between the control plane and the user plane, including controlling the delivery of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane, as well as user plane information. Report.
  • N6 The interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.
  • the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the above network element or function can be implemented by one device, can be implemented by multiple devices, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.
  • the solution of the embodiment of this application can be applied to the 5G network architecture shown in Figure 1, and can also be applied to the network architecture of future communications, such as the sixth generation (the 6th generation, 6G) network, and this application is not limited to this.
  • the data connection session includes a protocol data unit (PDU) session, an IP Connectivity Access Network (IP-CAN) session or other forms of sessions.
  • PDU protocol data unit
  • IP-CAN IP Connectivity Access Network
  • the QoS flows that need to be synchronized refer to at least two QoS flows that need to be synchronized, that is, two or more QoS flows need to be synchronized.
  • two or more QoS flows need to be synchronized, which specifically refers to the need for synchronization between data packets or data flows of two or more QoS flows.
  • synchronously scheduling the data packets of at least two QoS flows of the target service that need to be synchronized can also be called synchronously scheduling the data flows of at least two QoS flows of the target service that need to be synchronized, or it can be called It is used to synchronize the scheduling of at least two QoS flows of the target service that need to be synchronized, and has the same meaning.
  • the tunnel between the UPF and the base station for transmitting QoS flows may be the GPRS Tunnelling Protocol User Plane (GTP-U).
  • GTP-U GPRS Tunnelling Protocol User Plane
  • GPRS is the general packet radio service.
  • it can also be other tunnels, which are not limited in this application.
  • GTP-U tunnel uses the GTP-U tunnel as an example.
  • the mark information corresponds to the data connection session to which at least two QoS flows of the target service that need to be synchronized belong. It can also be expressed as: the mark information is used to associate the data to which at least two QoS flows of the target service that need to be synchronized belong.
  • the group identifier corresponds to the data connection session to which at least two QoS flows of the target service that need to be synchronized belong. It can also be expressed as: the group identifier is used to associate the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • Figure 2(a) is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application. The method includes the following steps:
  • Step 201a The UPF sends multiple data packets of the target service to the base station.
  • the multiple data packets belong to multiple QoS flows.
  • the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized.
  • the plurality of data packets include data packet 1 to data packet 20, wherein data packet 1 to data packet 5 belong to QoS flow 1, data packet 5 to data packet 10 belong to QoS flow 2, and data packet 11 to data packet 20 belong to QoS flow 3.
  • QoS flow 2 and QoS flow 3 are the QoS flows that need to be synchronized for the target service.
  • the target service here may be, for example, XR service, VR service, or AR service, etc., and part or all of the data streams of the target service need to be scheduled synchronously.
  • the data flow of the target service corresponding to the multiple data packets may be a data flow that needs to be synchronized, or it may be a data flow that does not need to be synchronized.
  • the data flow of the target service can belong to the same session or different sessions.
  • the target service includes audio data stream 1, video data stream 2, perceptual data stream 3 and perceptual data stream 4. Among them, audio data stream 1, video data stream 2 and perceptual data stream 3 need to be synchronized, and perceptual data stream 3 needs to be synchronized.
  • the multiple data packets of the target service sent by the UPF to the base station in step 201a may be the data packets of audio data stream 1, the data packets of video data stream 2, the data packets of sensing data stream 3, or Sense the packets of data stream 4. Therefore, some of the multiple data packets need to be synchronized, and some of the data packets do not need to be synchronized.
  • Each data packet in the plurality of data packets includes a QFI, which is used to identify the QoS flow to which the data packet belongs.
  • the relationship between the data flow of the target service and the QoS flow of the target service is: a data flow of the target service can be mapped into a QoS flow by SMF. Therefore, the above four data flows are mapped to four QoS flows. A unified explanation is given here and will not be repeated later.
  • Step 202a The base station determines at least two data packets that contain the same tag information from the multiple data packets.
  • the marking information corresponds to multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong.
  • the relationship between PDU session and QoS flow is: one PDU session can carry one or more QoS flows.
  • the QoS flows of the target service that need to be synchronized are mapped to multiple PDU sessions for transmission.
  • the multiple PDU sessions can be called sessions that carry the QoS flows of the target service that need to be synchronized.
  • It may also carry QoS flows of the target service that do not require synchronization, or carry QoS flows of other services.
  • the above tag information associates the multiple PDU sessions, and its meaning is: if a data packet of the target service contains the tag information, it indicates that the QoS flow to which the data packet belongs may be the QoS of the target service that needs to be synchronized. flow; if a data packet of the target service does not contain the tag information, it indicates that the QoS flow to which the data packet belongs is not a QoS flow of the target service that needs to be synchronized.
  • the QoS flow of the target service that needs to be synchronized corresponds to one or more UEs, that is, the multiple PDU sessions are PDU sessions of one or more UEs.
  • Figure 3(a) is a schematic diagram of an example provided by the embodiment of the present application.
  • the data streams that need to be synchronized in a certain target service include audio data stream 1, video data stream 2, and perception data stream 3.
  • SMF maps audio data flow 1 to QoS flow 2 and carries it in PDU session 1 of UE1 for transmission. It maps video data flow 2 to QoS flow 4 and carries it in PDU session 2 of UE1 for transmission.
  • Data flow 3 is mapped to QoS flow 8 and carried in PDU session 4 of UE2 for transmission.
  • the PDU session 1 of the UE1 also carries QoS flow 1 and QoS flow 3
  • the PDU session 2 of the UE1 also carries the QoS flow 5
  • the UE1 also establishes a PDU session 3
  • the PDU session 3 carries QoS flow 6 and QoS flow 7.
  • the PDU session 4 of the UE2 also carries QoS flow 9, and the UE2 also establishes a PDU session 5, which carries the QoS flow 10 and the QoS flow 11.
  • the numbers of each PDU session and the numbers of QoS flows in this example do not represent the order, but are just to distinguish each other.
  • UE1 and UE2 can receive or send different data streams of the same target service. For example, in this example, UE1 receives or sends audio data stream 1 and video data stream 2 of the target service, and UE2 receives or sends sensing data stream 3 of the target service.
  • PDU session 1 of UE1 carries QoS flow 1, QoS flow 2 and QoS flow 3;
  • PDU session 2 of UE1 carries QoS flow 4 and QoS flow 5;
  • PDU session 3 of UE1 carries QoS flow 6 and QoS flow 7;
  • PDU session 4 of UE2 carries QoS flow 8 and QoS flow 9;
  • PDU session 5 of UE2 carries QoS flow 10 and QoS flow 11.
  • the above-mentioned QoS flow 2, QoS flow 4 and QoS flow 8 are QoS flows that need to be synchronized for the target service, and are also called QoS flows corresponding to the data flows that need to be synchronized for the target service.
  • the above-mentioned QoS flow 1, QoS flow 3, QoS flow 5 to QoS flow 7, and QoS flow 9 to QoS flow 11 are QoS flows of the target service that do not require synchronization, or QoS flows of other services.
  • the marking information corresponds to the PDU session to which the QoS flow of the target service that needs to be synchronized belongs, such as PDU session 1, PDU session 2, and PDU session 4, or it can be understood that the target is transmitted by PDU session 1, PDU session 2, and PDU session 4.
  • the business requires synchronized QoS flows.
  • the PDU session 1, PDU session 2 and PDU session 4 are not only used to transmit the QoS flow of the target service that does not need to be synchronized, but can also be used to transmit the QoS flow of the target service that does not need to be synchronized or other services.
  • QoS flow such as the above-mentioned QoS flow 1, QoS flow 3, QoS flow 5, QoS flow 9, etc.
  • a UE can use one or more PDU sessions to carry the data stream of the target service. Taking Figure 3(a) as an example, the two PDU sessions of UE1 respectively carry the audio data stream 1 and video of the target service.
  • a PDU session of UE2 carries the sensing data stream 3 of the target service.
  • a PDU session of UE1 can also carry the audio data stream 1 and video data stream 2 of the target service, and a PDU session of UE2 Awareness data flow carrying target services 3.
  • the multiple data packets of the target service sent by the UPF to the base station in the above step 201a include at least the data packets of QoS flow 2, the data packets of QoS flow 4 and the data packets of QoS flow 8. , may also include data packets of QoS flows of the target service that do not require synchronization, such as data packets of QoS flow 1, data packets of QoS flow 3, data packets of QoS flow 6, data packets of QoS flow 7, and so on.
  • At least two data packets containing the same tag information in step 202a belong to some or all of the plurality of data packets, and the at least two data packets include PDU session 1, PDU session 2 or PDU session 4.
  • the at least two data packets of the QoS flow do not include the data packets of the QoS flow in other PDU sessions.
  • step 202a at least two data packets filtered out by the base station from the multiple received data packets are data packets of the QoS flow of the target service that may need to be synchronized, and among the multiple data packets, Other data packets except the at least two data packets are data packets of the QoS flow of the target service that do not require synchronization. Therefore, through this step 202a, the search range of the data packets of the QoS flow of the target service that needs to be synchronized is narrowed, and a blind search for the data packets of the QoS flow of the target service that needs to be synchronized is avoided from a large number of QoS flows.
  • Step 203a The base station determines at least two target data packets from at least two data packets containing the same tag information, and the at least two target data packets correspond to the QoS flows of the target service that require synchronization.
  • the at least two target data packets only include data packets of the QoS flow of the target service that need to be synchronized, and other data packets other than the at least two target data packets in the at least two data packets do not include the target.
  • the business requires synchronized QoS flow packets.
  • the at least two data packets include data packets of QoS flow 1 to QoS flow 5 and data packets of QoS flow 8 to QoS flow 9.
  • the at least two target data packets include QoS flow 2.
  • Data packets, data packets of QoS flow 4 and data packets of QoS flow 8, and the at least two target data packets do not include data packets of QoS flow 1, data packets of QoS flow 3, data packets of QoS flow 5 and QoS flow 9 packets.
  • the data packets of the QoS flow of the target service that need to be synchronized are filtered out from at least two data packets, so that the base station can perform synchronization scheduling according to the data packets of the QoS flow of the target service that need to be synchronized.
  • Step 204a The base station performs synchronous scheduling on the data packets of the QoS flow of the target service that require synchronization based on the at least two target data packets.
  • the base station performs synchronous scheduling on the data packets of the QoS flow of the target service that need to be synchronized according to the synchronization status information and the frame numbers contained in the at least two target data packets, that is, in the at least two target data packets, Each data packet contains a frame number, and the base station performs synchronous scheduling on the data packets of the QoS flow of the target service that need to be synchronized based on the frame number in each data packet and the synchronization status information obtained in advance.
  • the synchronization status information is used to indicate the correspondence between frame numbers in the data packets of the QoS flow of the target service that need to be synchronized in the synchronization status.
  • the base station determines that the QoS flows of the target service that need to be synchronized do not meet the synchronization accuracy, indicating that each QoS flow is not in a synchronized state, and the base station adjusts the target service that needs to be synchronized.
  • the synchronization accuracy is used to indicate the deviation of the frame number of the data packets of the QoS flow that need to be synchronized for the target service in the synchronization state.
  • the base station can allocate more resources to speed up the sending speed of data packets of the QoS flow, or discard unimportant data packets of the QoS flow to speed up the sending speed. The rate at which packets are sent for this QoS flow.
  • the base station can reduce the resources allocated to it to reduce the transmission speed of data packets of the QoS flow, or suspend the transmission of data packets of the QoS flow to reduce the transmission speed of data packets of the QoS flow. sending speed.
  • the base station may not adjust the sending speed of the data packet of the QoS flow of the target service that needs to be synchronized, but sends the data packet according to the current sending speed.
  • the synchronization status information and synchronization accuracy can be pre-configured on the base station, or can be received from the SMF, and the SMF can receive policy charging control (Policy and Charging Control, PCC) rules from the PCF.
  • Policy and Charging Control, PCC Policy and Charging Control
  • the rules include identification information of the target service, synchronization status information and/or synchronization accuracy.
  • the synchronization status information is 5:6:3, when the frame number in the downlink data packet of audio data stream 1 is 50, if the QoS flows corresponding to these data streams remain synchronized, the downlink data packet of video data stream 2
  • the frame number in should be any one from 58 to 62, and the frame number in the downstream data packet of sensing data stream 3 should be any one from 28 to 32. Therefore, in this example, audio data stream 1 and video data stream 2 are synchronized, but perception data stream 3 is not synchronized with audio data stream 1 and video data stream 2, so the transmission of perception data stream 3 can be reduced by speed to keep the QoS flows corresponding to the three data flows synchronized.
  • the base station synchronizes the data packets of the QoS flow of the target service that need to be synchronized according to the at least two target data packets, so that the data packets of the multiple QoS flows of the target service maintain a reasonable sending speed, so that the Coordination between multiple QoS flows improves user experience.
  • the base station when the audio data stream, video data stream and sensory data stream of the VR service are sent to one or more UEs (such as handles, VR glasses, VR fingertip devices) through multiple QoS streams, the base station After the data packets of the QoS streams corresponding to the audio data stream, video data stream and perception data stream are synchronously scheduled, it can be ensured that these QoS streams are sent to one or more UEs at an appropriate speed, so that users can experience video, audio and The synchronization between haptics improves the user experience. On the contrary, if the base station does not perform synchronization scheduling processing, the user will feel the desynchronization between video, audio and tactile sensation, which may cause the user to become dizzy and reduce the user experience.
  • the above marking information is the access network tunnel endpoint identifier (AN TEID).
  • the AN TEID is used to identify the GTP-U tunnel.
  • the GTP-U tunnel is used to transmit the target service that needs to be synchronized.
  • This method is applicable to the scenario where multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong correspond to the same SMF.
  • This method of allocating AN TEID allocates QoS flows that need to be synchronized in the same service to the same GTP-U tunnel, so the base station only needs to detect the data packets in this GTP-U tunnel and identify the need for synchronization. There is no need to identify the data packets that need to be synchronized in other GTP-U tunnels, which helps to improve the accuracy and efficiency of synchronization.
  • SMF/PCF/AF generates an association identifier, and then the SMF sends the association identifier to the base station.
  • the association identifier is associated with multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service.
  • the base station uses the association identifier according to the association identifier. Determine the marking information, that is, AN TEID, for the multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service, and then the base station sends the AN TEID to the UPF through SMF.
  • the base station can normally assign an AN TEID to each PDU session according to existing methods and bind the QFI corresponding to the AN TEID.
  • Figure 3(b) is an example diagram of GTP-U tunnel allocation provided by the embodiment of the present application.
  • This example is a GTP-U tunnel allocation based on the example in Figure 3(a).
  • SMF allocates association identifiers to multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service, and sends the same association identifier to the base station through each PDU session of the multiple PDU sessions, where the multiple PDU sessions correspond to the same of the SMF.
  • the base station When the base station receives the same association identifier corresponding to the multiple PDU sessions, it determines based on the association identifier that the multiple PDU sessions are used to transmit QoS flows that need to be synchronized for the target service, so that the base station allocates the same QoS flow to the multiple PDU sessions.
  • AN TEID which identifies a GTP-U tunnel. Referring to Figure 3(b), the base station allocates the same AN TEID1 to PDU session 1, PDU session 2 and PDU session 4 according to the association identifier. The AN TEID1 is used to identify GTP-U tunnel 1.
  • the base station allocates an AN TEID to each other PDU session according to the existing method, that is, allocates AN TEID2 to PDU session 3.
  • the AN TEID2 is used to identify GTP-U tunnel 2, and allocates AN TEID3 to PDU session 5.
  • the AN TEID3 is used to identify GTP-U tunnel 3.
  • the QFIs of different QoS flows in each GTP-U tunnel are different.
  • the QFIs of the QoS flows in different GTP-U tunnels can be the same or different, and the QFIs of the QoS flows are all allocated by the SMF.
  • AN TEID1 in this example is the above tag information.
  • the base station After the base station allocates the AN TEID, it sends the allocated AN TEID to the UPF through SMF, so that the UPF sends the QoS flow in the corresponding GTP-U tunnel according to the AN TEID. For example, UPF sends QoS flow 1 to QoS flow 5 and QoS flow 8 and QoS flow 9 to the base station in GTP-U tunnel 1, that is, the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 and QoS flow 9 are Add AN TEID1 to the GTP-U header.
  • UPF sends QoS flow 6 and QoS flow 7 to the base station in GTP-U tunnel 2, that is, adds AN TEID2 to the GTP-U header of the data packets of QoS flow 6 and QoS flow 7.
  • UPF sends QoS flow 10 and QoS flow 11 to the base station in GTP-U tunnel 3, that is, adds AN TEID3 to the GTP-U header of the data packets of QoS flow 10 and QoS flow 11.
  • UPF also adds the corresponding QFI to the GTP-U header of the data packet of each QoS flow. Please refer to Figure 3(b) for details.
  • the above step 202a is specifically: the base station identifies at least two data packets carrying AN TEID1 from the multiple received data packets, and the AN TEID1 is the tag information.
  • the above marking information is a group identifier assigned by the base station, and the group identifier corresponds to multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong.
  • Method 2 is applicable to the scenario where multiple PDU sessions belonging to the QoS flows of the target service that need to be synchronized correspond to different SMF/PCF. Of course, it is also applicable to the scenario where the same SMF/PCF corresponds to the same SMF/PCF.
  • SMF/PCF/AF generates association identifiers. For example, if multiple PDU sessions belonging to the QoS flows of the target service that need to be synchronized correspond to the same SMF but correspond to different PCFs, then SMF or AF generates association identifiers. For another example, the target If the multiple PDU sessions to which the QoS flows of the service that need to be synchronized belong correspond to the same PCF but correspond to different SMFs, the PCF or AF will generate an association identifier. For another example, the multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong. Corresponding to the same SMF and the same PCF, the association identifier is generated by SMF, PCF or AF. For another example, if the SMF and PCF of multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service are different, the association is generated by AF. logo.
  • the SMF sends the association identifier to the base station.
  • the association identifier is associated with multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service.
  • the base station uses the association identifier to meet the needs of the target service. Multiple PDU sessions to which the synchronized QoS flows belong determine the marking information, that is, the group identification, and then the base station sends the group identification to the UPF through SMF.
  • the group identifier generated by the base station may be the same as the association identifier, or may be different.
  • the reason why the base station needs to regenerate the group identifier based on the association identifier instead of directly using the association identifier sent by the SMF to the base station is because: there may be multiple SMF/PCF/AF performing synchronous scheduling of different services at the same time, and SMF/PCF/AF
  • the same association identifier may be assigned to PDU sessions corresponding to different services, that is, the association identifier is not unique on the base station side. For example, SMF1 assigns association identifier 1 to the PDU session to which the QoS flow that needs to be synchronized belongs to service 1, and SMF2 assigns association identifier 1 to service 2.
  • the PDU session to which the QoS flow that needs to be synchronized is also assigned association identifier 1.
  • association identifier 1 If the base station directly uses association identifier 1, it will cause the base station to subsequently identify the QoS flow of service 1 that needs to be synchronized based on association identifier 1. Not only the PDU of service 1 The QoS flow that needs to be synchronized is identified in the session, and the QoS flow that needs to be synchronized is also identified in the PDU session of service 2. However, in fact, there is no QoS flow in the PDU session of service 2 that needs to be synchronized with the QoS flow of service 1, causing It wastes resources and may also cause misidentification. The same is true for the synchronization of the QoS flow of business 2.
  • the base station does not use the association identifier assigned by SMF/PCF/AF, but reassigns a group identifier, which can ensure the uniqueness of the group identifier on the base station. Subsequent base stations perform synchronous scheduling based on the unique group identifier.
  • the base station allocates a group ID to the PDU session corresponding to association ID 1 from SMF1, and allocates another group ID to the PDU session corresponding to association ID 1 from SMF2, so the QoS flow of service 1 corresponds to the group ID It is different from the group identifier corresponding to the QoS flow of service 2 and will not be confused with each other.
  • the base station can normally assign an AN TEID to each PDU session according to the existing method, and bind the QFI corresponding to the AN TEID.
  • Figure 3(c) is another example diagram of GTP-U tunnel allocation provided by the embodiment of the present application. This example is a GTP-U tunnel allocation based on the example in Figure 3(a). For example, the base station allocates an AN TEID to each PDU session according to the existing method, that is, allocates AN TEID1 to PDU session 1. The AN TEID1 is used to identify GTP-U tunnel 1, and allocates AN TEID2 to PDU session 2.
  • the AN TEID2 uses To identify GTP-U tunnel 2, PDU session 3 is assigned AN TEID3, which is used to identify GTP-U tunnel 3. PDU session 4 is assigned AN TEID4, which is used to identify GTP-U tunnel 4, which is PDU. Session 5 is assigned AN TEID5, which is used to identify GTP-U Tunnel 5. Among them, the QFIs of different QoS flows in each GTP-U tunnel are different. The QFIs of the QoS flows in different GTP-U tunnels can be the same or different, and the QFIs of the QoS flows are all allocated by the SMF.
  • the base station After the base station allocates the AN TEID and generates the group identifier, it sends the AN TEID and the group identifier to the UPF through SMF, so that the UPF sends the QoS flow in the corresponding GTP-U tunnel according to the AN TEID, and the UPF will also send the QoS flow in the PDU session 1 and PDU Add the group identifier to the GTP-U header of the data packets of each QoS flow in session 2 and PDU session 4.
  • UPF sends QoS flow 1 to QoS flow 3 to the base station in GTP-U tunnel 1, that is, adding AN TEID1 and group identification to the GTP-U header of the data packets from QoS flow 1 to QoS flow 3.
  • UPF sends QoS flow 4 and QoS flow 5 to the base station in GTP-U tunnel 2, that is, adding AN TEID2 and group identification to the GTP-U header of the data packets of QoS flow 4 and QoS flow 5.
  • UPF sends QoS flow 6 and QoS flow 7 to the base station in GTP-U tunnel 3, that is, adds AN TEID3 to the GTP-U header of the data packets of QoS flow 6 and QoS flow 7.
  • UPF sends QoS flow 8 and QoS flow 9 to the base station in GTP-U tunnel 4, that is, adding AN TEID4 and group identification to the GTP-U header of the data packets of QoS flow 8 and QoS flow 9.
  • UPF sends QoS flow 10 and QoS flow 11 to the base station in GTP-U tunnel 5, that is, adds AN TEID5 to the GTP-U header of the data packets of QoS flow 10 and QoS flow 11. Moreover, UPF also adds the corresponding QFI to the GTP-U header of the data packet of each QoS flow. Please refer to Figure 3(c) for details.
  • the above step 202a is specifically: the base station identifies at least two data packets carrying the same group identifier from the multiple received data packets, and the group identifier is the tag information.
  • the above tag information includes the association identifier and the identification information of the network device.
  • the network device is the SMF, PCF or AF that generates the association identifier.
  • Method 3 is applicable to the scenario where multiple PDU sessions belonging to the QoS flows of the target service that need to be synchronized correspond to different SMF/PCFs. Of course, it is also applicable to the scenario where the same SMF/PCF corresponds to the same SMF/PCF.
  • SMF/PCF/AF generates association identifiers. For example, if multiple PDU sessions belonging to the QoS flows of the target service that need to be synchronized correspond to the same SMF but correspond to different PCFs, then SMF or AF generates association identifiers. For another example, the target If the multiple PDU sessions to which the QoS flows of the service that need to be synchronized belong correspond to the same PCF but correspond to different SMFs, the PCF or AF will generate an association identifier. For another example, the multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong. Corresponding to the same SMF and the same PCF, the association identifier is generated by SMF, PCF or AF. For another example, if the SMF and PCF of multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service are different, the association is generated by AF. logo.
  • SMF/PCF/AF After SMF/PCF/AF generates the association identifier, SMF sends the association identifier and the identification information of the network device that generated the association identifier to the UPF and the base station.
  • the association identifier is associated with multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service.
  • the network device is SMF, PCF or AF.
  • the combination of the association identifier and the identification information of the network device is used as the marking information, instead of only using the association identifier as the marking information.
  • the reason is similar to the reason why the base station reassigns the group identifier in the above method 2, both of which are to ensure the marking information.
  • Uniqueness Different SMF/PCF/AF may allocate the same association identifier for the synchronization of QoS flows of different services. Therefore, it is necessary to add the identification information of the SMF/PCF/AF so that the label information remains unique on the base station side.
  • the base station can normally assign an AN TEID to each PDU session according to the existing method, and bind the QFI corresponding to the AN TEID.
  • the GTP-U tunnel allocation example shown in Figure 3(c) above is also applicable to method three.
  • UPF can receive AN TEID from the base station, and also receive mark information from SMF.
  • the mark information includes the association identifier and the identification information of SMF/PCF/AF, so that UPF sends it in the corresponding GTP-U tunnel according to the AN TEID.
  • QoS flow, and UPF will also add the association identifier and SMF/PCF/AF identification information to the GTP-U header of the data packets of each QoS flow in PDU Session 1, PDU Session 2, and PDU Session 4.
  • UPF sends QoS flow 1 to QoS flow 3 to the base station in GTP-U tunnel 1, that is, adds AN TEID1, association identification and SMF/PCF/AF in the GTP-U header of the data packets from QoS flow 1 to QoS flow 3.
  • Identification information UPF sends QoS flow 4 and QoS flow 5 to the base station in GTP-U tunnel 2, that is, adding AN TEID2, association identification and SMF/PCF/AF to the GTP-U header of the data packets of QoS flow 4 and QoS flow 5.
  • Identification information is possible implementation of the base station in GTP-U tunnel 1, that is, adds AN TEID1, association identification and SMF/PCF/AF in the GTP-U header of the data packets from QoS flow 1 to QoS flow 3.
  • Identification information UPF sends QoS flow 4 and QoS flow 5 to the base station in GTP-U tunnel 2, that is, adding AN TEID2, association identification and SMF/
  • UPF sends QoS flow 6 and QoS flow 7 to the base station in GTP-U tunnel 3, that is, adds AN TEID3 to the GTP-U header of the data packets of QoS flow 6 and QoS flow 7.
  • UPF sends QoS flow 8 and QoS flow 9 to the base station in GTP-U tunnel 4, that is, adding AN TEID4, association identification and SMF/PCF/AF to the GTP-U header of the data packets of QoS flow 8 and QoS flow 9. Identification information.
  • UPF sends QoS flow 10 and QoS flow 11 to the base station in GTP-U tunnel 5, that is, adds AN TEID5 to the GTP-U header of the data packets of QoS flow 10 and QoS flow 11. Moreover, UPF also adds the corresponding QFI to the GTP-U header of the data packet of each QoS flow. Please refer to Figure 3(c) for details.
  • the above step 202a is specifically: the base station identifies at least two data packets carrying the same association identifier and the same SMF/PCF/AF identification information from the multiple received data packets, and the association identifier and SMF/ The combination of PCF/AF identification information is label information.
  • the SMF may also send the QFI of the QoS flow of the target service that needs to be synchronized to the base station.
  • the QFI of the QoS flow that needs to be synchronized for the target service sent by the SMF to the base station includes the QFI of QoS flow 2 (i.e. QFI2), the QFI of QoS flow 4 (i.e. QFI4) and the QoS flow 8 QFI (ie QFI6), so that the base station learns the QFI of the QoS flow that needs to be synchronized for the target service.
  • the QFI of the QoS flow that needs to be synchronized for the target service sent by the SMF to the base station includes the QFI of QoS flow 2 (i.e. QFI2), the QFI of QoS flow 4 (i.e. QFI1) and the QoS flow 8 QFI (ie QFI1), so that the base station learns the QFI of the QoS flow that needs to be synchronized for the target service.
  • the above step 203a is specifically: the base station determines the data packet containing the target QFI from at least two data packets.
  • the data packet containing the target QFI is the aforementioned at least two target data packets.
  • the target QFI is Any one of the QFIs of the target service's QoS flow that requires synchronization.
  • the base station obtains the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9 from QoS flow 1 to QoS flow 11,
  • the base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 from the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9, and then the base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 according to QoS flow 2,
  • the data packets of QoS flow 4 and QoS flow 8 are scheduled synchronously with the data packets of the QoS flow of the target service that need to be synchronized.
  • the SMF can also send the QFI of the QoS flow of the target service that needs to be synchronized to the UPF.
  • the QFI of the QoS flow that needs to be synchronized for the target service sent by SMF to UPF includes the QFI of QoS flow 2 (i.e. QFI2), the QFI of QoS flow 4 (i.e. QFI4) and the QoS flow 8 QFI (i.e. QFI6), so that UPF learns the QFI of the QoS flow that needs to be synchronized for the target service.
  • the QFI of the QoS flow that needs to be synchronized for the target service sent by SMF to UPF includes the QFI of QoS flow 2 (i.e. QFI2), the QFI of QoS flow 4 (i.e. QFI1) and the QoS flow QFI of 8 (i.e. QFI1), so that UPF learns the QFI of the QoS flow that needs to be synchronized for the target service.
  • UPF subsequently adds a synchronization indication to the GTP-U header of the data packets of QoS flow 2, QoS flow 4 and QoS flow 8.
  • This synchronization indication is used to indicate that the QoS flow to which the data packet belongs is for the target service. Synchronized QoS flows are required. Therefore, the above-mentioned step 203a is specifically: the base station determines the data packet containing the synchronization indication from at least two data packets, and the data packet containing the synchronization indication is the aforementioned at least two target data packets.
  • the base station obtains the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9 from QoS flow 1 to QoS flow 11, And through the above step 203a, the base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 from the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9, and then the base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 according to QoS flow 2, The data packets of QoS flow 4 and QoS flow 8 are scheduled synchronously with the data packets of the QoS flow of the target service that need to be synchronized.
  • Figure 2(b) is a schematic flowchart of a synchronous scheduling method provided by an embodiment of the present application. The method includes the following steps:
  • Step 201b The UPF sends multiple data packets of the target service to the base station.
  • the multiple data packets belong to multiple QoS flows.
  • the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized.
  • This step 201b is the same as the aforementioned step 201a, and reference may be made to the aforementioned description.
  • Step 202b The base station determines at least two data packets containing the same access network tunnel endpoint identifier (AN TEID) from multiple data packets.
  • AN TEID access network tunnel endpoint identifier
  • the at least two data packets correspond to QoS flows of the target service that need to be synchronized.
  • the AN TEID is used to identify the target tunnel.
  • the target tunnel is a tunnel that transmits the data flow of the QoS flow of the target service that needs to be synchronized (such as a GTP-U tunnel). ), the QoS flow that needs to be synchronized for the target service corresponds to one or more PDU sessions.
  • the at least two data packets are data packets of the QoS flow of the target service that need to be synchronized. Taking Figure 3(a) as an example, the at least two data packets are the data packet of QoS flow 2, the data packet of QoS flow 4 and the data packet of QoS flow 8.
  • the QoS flows of the target service that need to be synchronized are mapped to multiple PDU sessions for transmission.
  • the multiple PDU sessions can be called sessions that carry the QoS flows of the target service that need to be synchronized.
  • the QoS flow of the target service that needs to be synchronized corresponds to one or more UEs, that is, the multiple PDU sessions are PDU sessions of one or more UEs.
  • the base station filters out the data packets of the QoS flow of the target service that need to be synchronized from multiple data packets, so that the base station can perform synchronization scheduling according to the data packets of the QoS flow of the target service that need to be synchronized.
  • Step 203b The base station performs synchronous scheduling on the data packets of the QoS flow of the target service that require synchronization based on at least two data packets.
  • this step 203b is similar to the implementation of the foregoing step 204a, and reference may be made to the foregoing description.
  • the above scheme transmits the data packets of the QoS flow of the target service that need to be synchronized through a dedicated GTP-U tunnel, so that the base station can quickly and easily identify the data packets of the QoS flow that need to be synchronized, and then the base station needs the target service
  • the data packets of the synchronized QoS flow are scheduled synchronously, so that the data packets of the multiple QoS flows of the target service can be maintained at a reasonable sending speed, so that the multiple QoS flows can be coordinated, and the user experience can be improved.
  • the base station when the audio data stream, video data stream and sensory data stream of the VR service are sent to one or more UEs (such as handles, VR glasses, VR fingertip devices) through multiple QoS streams, the base station After the data packets of the QoS streams corresponding to the audio data stream, video data stream and perception data stream are synchronously scheduled, it can be ensured that these QoS streams are sent to one or more UEs at an appropriate speed, so that users can experience video, audio and The synchronization between haptics improves the user experience. On the contrary, if the base station does not perform synchronization scheduling processing, the user will feel the desynchronization between video, audio and tactile sensation, which may cause the user to become dizzy and reduce the user experience.
  • the base station allocates the QoS flows that need to be synchronized in the target service to the same GTP-U tunnel.
  • the QoS flows in the GTP-U tunnel are all QoS flows that need to be synchronized. Therefore, The base station can quickly determine the QoS flow that needs to be synchronized for the target service, which helps to improve the accuracy and efficiency of synchronization.
  • SMF/PCF/AF generates an association identifier, and then the SMF sends the association identifier to the base station.
  • the association identifier is associated with multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong.
  • SMF also sends the association identifier to the base station.
  • the QFI of the QoS flow of the target service that needs to be synchronized The base station identifies the multiple PDU sessions to which the QoS flow of the target service that needs to be synchronized belongs to based on the association identifier, and obtains the QFI of the target service that needs to be synchronized from the multiple PDU sessions. The QFI of the QoS flow, and then the base station allocates the same AN TEID to these QoS flows.
  • the GTP-U tunnel identified by the AN TEID is dedicated to transmitting the QoS flows that need to be synchronized for the target service.
  • the base station sends the AN TEID to the UPF through SMF.
  • the base station can normally allocate AN TEID according to the existing method and bind the AN TEID Corresponding QFI.
  • Figure 3(d) is another example diagram of GTP-U tunnel allocation provided by the embodiment of the present application.
  • This example is a GTP-U tunnel allocation based on the example in Figure 3(a).
  • the SMF allocates association identifiers to multiple PDU sessions to which the QoS flows of the target service that need to be synchronized belong, and sends the same association identifier to the base station through each PDU session of the multiple PDU sessions.
  • the multiple PDU sessions correspond to the same SMF.
  • the SMF also sends the QFI of the QoS flow of the target service that needs to be synchronized to the base station.
  • the base station When the base station receives the same association identifier corresponding to the multiple PDU sessions, it determines multiple PDU sessions for transmitting QoS flows that require synchronization of the target service, and then the base station obtains the needs of the target service from the multiple PDU sessions. QFI of the synchronized QoS flow, and then the base station allocates the same AN TEID to the QoS flow that needs to be synchronized for the target service.
  • the AN TEID identifies a GTP-U tunnel. Referring to Figure 3(d), the base station allocates the same AN TEID1 to QoS flow 2, QoS flow 4 and QoS flow 8 according to the association identifier.
  • the AN TEID1 is used to identify GTP-U tunnel 1.
  • the base station allocates an AN TEID to other QoS flows in PDU session 1, PDU session 2, PDU session 4, and each other PDU session, that is, QoS flow 1 and QoS flow in PDU session 1 3 assigns AN TEID2, which is used to identify GTP-U tunnel 2, and assigns AN TEID3 to QoS flow 5 in PDU session 2, which AN TEID3 is used to identify GTP-U tunnel 3, and assigns AN TEID4 to PDU session 3,
  • the AN TEID4 is used to identify GTP-U tunnel 4
  • QoS flow 9 in PDU session 4 is assigned AN TEID5
  • the AN TEID5 is used to identify GTP-U tunnel 5
  • PDU session 5 is assigned AN TEID6
  • the AN TEID6 is used To identify GTP-U tunnel 6.
  • the QFIs of different QoS flows in each GTP-U tunnel are different.
  • the QFIs of the QoS flows in different GTP-U tunnels can be the same or different, and the QFIs of the QoS flows are all allocated by the SMF.
  • AN TEID1 in this example is the above tag information.
  • the base station After the base station allocates the AN TEID, it sends the allocated AN TEID to the UPF through SMF, so that the UPF sends the QoS flow in the corresponding GTP-U tunnel according to the AN TEID.
  • UPF sends QoS flow 2, QoS flow 4 and QoS flow 8 to the base station in GTP-U tunnel 1, that is, adds AN TEID1 to the GTP-U header of the data packets of QoS flow 2, QoS flow 4 and QoS flow 8.
  • UPF sends QoS flow 1 and QoS flow 3 to the base station in GTP-U tunnel 2, that is, adds AN TEID2 to the GTP-U header of the data packets of QoS flow 1 and QoS flow 3.
  • UPF sends QoS flow 5 to the base station in GTP-U tunnel 3, that is, adds AN TEID3 to the GTP-U header of the data packet of QoS flow 5.
  • UPF sends QoS flow 6 and QoS flow 7 to the base station in GTP-U tunnel 4, that is, adds AN TEID4 to the GTP-U header of the data packets of QoS flow 6 and QoS flow 7.
  • UPF sends QoS flow 9 to the base station in GTP-U tunnel 5, that is, adds AN TEID 5 to the GTP-U header of the data packet of QoS flow 9.
  • UPF sends QoS flow 10 and QoS flow 11 to the base station in GTP-U tunnel 6, that is, adds AN TEID6 to the GTP-U header of the data packets of QoS flow 10 and QoS flow 11.
  • UPF also adds the corresponding QFI to the GTP-U header of the data packet of each QoS flow. Please refer to Figure 3(d) for details.
  • the above step 202b is specifically: the base station identifies at least two data packets carrying AN TEID1 from the multiple data packets received.
  • the AN TEID1 is used to represent the target tunnel, and the target tunnel is dedicated to transmitting the GTP-U tunnel for target services that require synchronized QoS flows.
  • Figure 2(c) is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application. The method includes the following steps:
  • Step 201c The UPF sends multiple data packets of the target service to the base station.
  • the multiple data packets belong to multiple QoS flows.
  • the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized.
  • This step 201c is the same as the aforementioned step 201a, and reference may be made to the aforementioned description.
  • Step 202c The base station determines at least two data packets from multiple data packets based on the synchronization relationship between multiple access network tunnel endpoint identifiers.
  • Each of the at least two data packets contains any one of multiple access network tunnel endpoint identifiers, and the GTP-U tunnels respectively indicated by the multiple access network tunnel endpoint identifiers are all using QoS flows that need to be synchronized for transmitting target services.
  • Step 203c The base station determines at least two target data packets from at least two data packets, and the at least two target data packets correspond to QoS flows of the target service that require synchronization.
  • the at least two target data packets only include data packets of the QoS flow of the target service that need to be synchronized, and other data packets other than the at least two target data packets in the at least two data packets do not include the target.
  • the business requires synchronized QoS flow packets.
  • the at least two data packets include data packets of QoS flow 1 to QoS flow 5 and data packets of QoS flow 8 to QoS flow 9.
  • the at least two target data packets include QoS flow 2.
  • the data packet, the data packet of QoS flow 4 and the data packet of QoS flow 8, and the at least two target data packets do not include the data packet of QoS flow 1, the data packet of QoS flow 3, the data of QoS flow 5 and QoS flow 9 Bag.
  • the data packets of the QoS flow of the target service that need to be synchronized are filtered out from at least two data packets, so that the base station can perform synchronization scheduling according to the data packets of the QoS flow of the target service that need to be synchronized.
  • Step 204c The base station performs synchronous scheduling on the data packets of the QoS flow of the target service that require synchronization based on at least two target data packets.
  • this step 204c is similar to the implementation of the foregoing step 204a, and reference may be made to the foregoing description.
  • the base station synchronizes the data packets of the QoS flow of the target service that need to be synchronized according to the at least two target data packets, so that the data packets of the multiple QoS flows of the target service maintain a reasonable sending speed, so that the Coordination between multiple QoS flows improves user experience.
  • the base station when the audio data stream, video data stream and sensory data stream of the VR service are sent to one or more UEs (such as handles, VR glasses, VR fingertip devices) through multiple QoS streams, the base station After the data packets of the QoS streams corresponding to the audio data stream, video data stream and perception data stream are synchronously scheduled, it can be ensured that these QoS streams are sent to one or more UEs at an appropriate speed, so that users can experience video, audio and The synchronization between haptics improves the user experience. On the contrary, if the base station does not perform synchronization scheduling processing, the user will feel the desynchronization between video, audio and tactile sensation, which may cause the user to become dizzy and reduce the user experience.
  • SMF/PCF/AF generates an association identifier, and then the SMF sends the association identifier to the base station.
  • the association identifier is associated with the QoS flow that needs to be synchronized of the target service.
  • Multiple PDU sessions, and then the base station identifies the multiple PDU sessions to which the QoS flows that need to be synchronized belong to the target service based on the association identifier.
  • the base station allocates an AN TEID to each PDU session according to the existing method, and the base station sends the SMF to the UPF Send the AN TEID.
  • the base station also records the correspondence between the AN TEIDs of the PDU sessions corresponding to the association identifiers. Taking the example in Figure 3(a) as an example, the base station allocates an AN TEID to each PDU session according to the method shown in Figure 3(c). Based on the association identifier, the base station learns that PDU Session 1, PDU Session 2 and PDU Session 4 are used to transmit QoS flows that require synchronization of the target service, and the base station assigns AN TEID1 and AN TEID2 to PDU Session 1, PDU Session 2 and PDU Session 4 respectively.
  • the base station records the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4. It can be understood that the base station determines that the QoS flows of the target services that need to be synchronized will be transmitted in the GTP-U tunnels indicated by AN TEID1, AN TEID2 and AN TEID4, and will not be transmitted in other GTP-U tunnels.
  • the SMF synchronizes multiple PDU sessions to which the QoS flows belong according to the needs of the target service, and the AN TEIDs assigned by the base station to the multiple PDU sessions, Establish a synchronization relationship between AN TEIDs and send the synchronization relationship to the base station.
  • the base station allocates an AN TEID to each PDU session according to the existing method. Taking the example in Figure 3(a) as an example, the base station allocates an AN TEID to each PDU session according to the method shown in Figure 3(c).
  • SMF determines that PDU session 1, PDU session 2 and PDU session 4 are used to transmit QoS flows that require synchronization of the target service, and SMF receives AN TEID1, AN respectively allocated for PDU session 1, PDU session 2 and PDU session 4 from the base station.
  • TEID2 and AN TEID4 the SMF records the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4, and then sends the synchronization relationship to the base station, so that the base station determines that the QoS flow of the target service that needs to be synchronized will be in AN based on the synchronization relationship. It is transmitted in the GTP-U tunnel indicated by TEID1, AN TEID2 and AN TEID4, and will not be transmitted in other GTP-U tunnels.
  • the above step 202c is specifically: based on the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4, the base station identifies at least two packets carrying AN TEID1, AN TEID2 or AN TEID4 from the multiple received data packets.
  • data packets, and the at least two data packets may be data packets of QoS flows of the target service that need to be synchronized.
  • the SMF may also send the QFI of the QoS flow that requires synchronization of the target service to the base station.
  • the QFI of the QoS flow that needs to be synchronized for the target service sent by the SMF to the base station includes the QFI of QoS flow 2 (i.e. QFI2), the QFI of QoS flow 4 (i.e. QFI1) and the QoS flow 8 QFI (ie QFI1), so that the base station learns the QFI of the QoS flow that needs to be synchronized for the target service.
  • the above step 203c is specifically: the base station determines the data packet containing the target QFI from at least two data packets.
  • the data packet containing the target QFI is the aforementioned at least two target data packets.
  • the target QFI is Any one of the QFIs of the target service's QoS flow that requires synchronization.
  • the base station obtains the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9 from QoS flow 1 to QoS flow 11, and through the above step 203c, The base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 from the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9, and then the base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 data packets are synchronously scheduled for the QoS flow data packets of the target service that need to be synchronized.
  • the SMF can also send the QFI of the QoS flow of the target service that needs to be synchronized to the UPF.
  • the QFI of the QoS flow that needs to be synchronized for the target service sent by SMF to UPF includes the QFI of QoS flow 2 (i.e. QFI2), the QFI of QoS flow 4 (i.e. QFI1) and the QoS flow QFI of 8 (i.e. QFI1), so that UPF learns the QFI of the QoS flow that needs to be synchronized for the target service.
  • UPF subsequently adds a synchronization indication to the GTP-U header of the data packets of QoS flow 2, QoS flow 4 and QoS flow 8.
  • This synchronization indication is used to indicate that the QoS flow to which the data packet belongs is for the target service. Synchronized QoS flows are required. Therefore, the above step 203c is specifically: the base station determines the data packet containing the synchronization indication from at least two data packets, and the data packet containing the synchronization indication is the aforementioned at least two target data packets.
  • the base station obtains the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9 from QoS flow 1 to QoS flow 11, and through the above step 203c, The base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 from the data packets of QoS flow 1 to QoS flow 5 and QoS flow 8 to QoS flow 9, and then the base station obtains the data packets of QoS flow 2, QoS flow 4 and QoS flow 8 data packets are synchronously scheduled for the QoS flow data packets of the target service that need to be synchronized.
  • FIGS. 2(a) to 2(c) will be described below with reference to the specific embodiments of FIGS. 4 to 9 .
  • the following embodiments in Figures 4, 5 and 8 are specific examples of the embodiment in Figure 2(a)
  • the following embodiments in Figures 6 and 7 are specific examples of the embodiment in Figure 2(c)
  • the following The embodiment of FIG. 9 is a specific example of the embodiment of FIG. 2(b).
  • FIG. 4 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • multiple PDU sessions belonging to a QoS flow corresponding to a service that need to be synchronized are allocated to the same GTP-U tunnel, so the data packets of the QoS flow corresponding to the service that need to be synchronized are all transmitted through the GTP-U tunnel.
  • the GTP-U tunnel may also transmit data packets of QoS flows corresponding to the service that do not require synchronization, and/or data packets of QoS flows of other services.
  • the data packets received by the base station from the GTP-U tunnel are data packets that may need to be synchronized.
  • the base station further determines the data packets that need to be synchronized from the data packets that may need to be synchronized, and performs synchronization scheduling based on the data packets that need to be synchronized.
  • the method includes the following steps:
  • Step 401a UE1 establishes one or more PDU sessions.
  • Step 401b UE2 establishes one or more PDU sessions.
  • the PDU sessions established by UE1 and UE2 all correspond to the same SMF.
  • the UE1 and UE2 can receive or send different data streams of the same target service.
  • Step 402 The AF sends the identification information of the service and the synchronization information of the service to the PCF.
  • the synchronization information includes the synchronization indication, and includes synchronization status information or the frame rate of each data stream of the service.
  • the synchronization indication is used to indicate that the data flow of the service needs to be synchronized, or to indicate that the QoS flow to which the data packet carrying the synchronization indication belongs is a QoS flow that requires synchronization.
  • the data flow of a service that needs to be synchronized can correspond to the same UE or different UEs.
  • the data flow of a service that needs to be synchronized corresponds to UE1 and UE2 as an example.
  • the synchronization status information is used to indicate the correspondence between frame numbers in the data packets of the data flow of the service in the synchronization status.
  • the frame rate of a data stream indicates the number of frames sent per second by the data stream.
  • different data streams of the same service can correspond to different PCFs.
  • the above audio data stream 1 corresponds to PCF1
  • video data stream 2 corresponds to PCF2
  • perception data stream 3 corresponds to PCF3, or different data streams of the same service. They may also correspond to the same PCF, which is not limited in the embodiments of this application.
  • the AF can send the above synchronization instructions and synchronization status information to different PCFs, or the AF can send synchronization instructions and data corresponding to the PCF in the service to different PCFs respectively.
  • the frame rate of the stream When different data streams of the same service correspond to different PCFs, the AF can send the above synchronization instructions and synchronization status information to different PCFs, or the AF can send synchronization instructions and data corresponding to the PCF in the service to different PCFs respectively.
  • the frame rate of the stream is not limited to the frame rate.
  • Step 403 The PCF sends the PCC rule to the SMF.
  • the PCC rule includes the identification information of the service and the synchronization information of the service.
  • step 403 is to send the PCC rules to the SMF by the multiple PCFs respectively.
  • the PDU session is the PDU session of UE1 or the PDU session of UE2.
  • the audio data stream 1 of a certain service corresponds to the PDU session 1 of UE1
  • the video data stream 2 of the service corresponds to the PDU session 2 of UE1
  • the perception data stream 3 of the service corresponds to the PDU session 2 of UE2.
  • Step 404 The SMF sends the association identifier of the service and the synchronization rule of the service to the base station. Optionally, it also sends the QFI of the QoS flow corresponding to the service that needs to be synchronized.
  • SMF After receiving one or more PCC rules, SMF maps the data flow corresponding to the PCC rule into a QoS flow, and assigns a QFI to each QoS flow. Among them, a data flow can be mapped to a QoS flow, and each QoS flow is carried in a PDU session for transmission.
  • a PDU session can carry one or multiple QoS flows.
  • the association identifier is associated with the PDU session corresponding to the QoS flow of a certain service that needs to be synchronized, that is, the association identifier is identified at the PDU session granularity.
  • PDU sessions corresponding to the same association identifier may be referred to as PDU sessions that require synchronization, or as PDU sessions that include QoS flows that require synchronization.
  • SMF assigns the same association identifier to PDU session 1, PDU session 2 and PDU session 4, which is used to indicate that PDU session 1, PDU session 2 and PDU session 4 corresponding to the same association identifier Contains QoS flows for the same service that need to be synchronized.
  • PDU session 1, PDU session 2 and PDU session 4 correspond to the same PCF
  • the PCF can also assign the same association identifier to PDU session 1, PDU session 2 and PDU session 4 and assign the association identifier to Carried in PCC rules and sent to SMF.
  • the SMF allocates QFI to each QoS flow, it allocates different QFIs to different QoS flows in the associated PDU session.
  • QFI is normally allocated according to the existing method.
  • the QFIs of different QoS flows within the same PDU session are different, and the QFIs of the QoS flows of different PDU sessions can be the same or different.
  • the allocation result is as shown in Figure 3(b).
  • Business synchronization rules include synchronization status information and/or synchronization accuracy.
  • the synchronization status information comes from the PCC rule in step 403, or is calculated by the SMF based on the frame rate of each data stream in the PCC rule in step 403.
  • the synchronization accuracy is used to indicate the deviation of frame numbers in data packets of different data flows (or QoS flows) of the service in the synchronization state. For example, the synchronization accuracy is 2 frames.
  • the synchronization accuracy may be pre-configured on the SMF, or may be obtained by the SMF upon request from other network elements, or may be actively sent to the SMF by other network elements, which is not limited in the embodiments of this application.
  • the SMF may perform the above step 404 respectively for multiple PDU sessions corresponding to the same association identifier.
  • the SMF sends message 1 to the base station.
  • the message 1 includes the association identifier, synchronization rules, and QFI of each QoS flow in the PDU session 1.
  • the SMF sends message 2 to the base station.
  • the message 2 includes the association identifier, synchronization rules. rules and the QFI of each QoS flow in the PDU session 2, the SMF sends a message 3 to the base station.
  • the message 3 includes the association identifier, the synchronization rule and the QFI of each QoS flow in the PDU session 4.
  • the association identifiers in message 1, message 2 and message 3 are the same and the synchronization rules are the same.
  • Step 405 The SMF sends the QFI and synchronization indication of the QoS flow corresponding to the service that needs to be synchronized to the UPF.
  • This step 405 is optional.
  • step 405 needs to be performed.
  • the meaning of this synchronization indication refers to the description of step 404.
  • the UPF receives the synchronization indication, after receiving the data flow of the service that needs to be synchronized from the AF, the UPF encapsulates the synchronization indication in the GTP-U header of the data packet of the QoS flow corresponding to the data flow, and The data packet is sent to the base station, and the base station determines that the data flow needs to be synchronized based on the synchronization indication.
  • UPF receives the data stream of this service from AF that does not require synchronization
  • UPF will not encapsulate the synchronization indication in the GTP-U header of the data packet of the QoS flow corresponding to the data stream.
  • the base station determines that the GTP-U header If no synchronization indication is carried, it is determined that the data flow does not require synchronization.
  • the UPF does not receive the synchronization indication
  • the UPF executes according to the existing method. Therefore, UPF does not sense whether the data flow needs to be synchronized, and the synchronization indication will not be encapsulated in the GTP-U header of the QoS flow packet corresponding to the data flow.
  • the base station After the base station receives the data packet of the QoS flow corresponding to the data flow of the service, it can use other methods to determine that the data flow needs to be synchronized. For example, the base station receives the QFI corresponding to the data flow of the service that needs to be synchronized from the SMF in advance.
  • the base station The QFI in the received data packet belongs to the QFI corresponding to the data flow that needs to be synchronized, then the data flow needs to be synchronized. If the QFI in the data packet received by the base station does not belong to the QFI corresponding to the data flow that needs to be synchronized, then the data flow No synchronization is required.
  • Step 406 The base station allocates the same access network tunnel endpoint identifier (AN TEID) to the PDU sessions corresponding to the same association identifier.
  • AN TEID access network tunnel endpoint identifier
  • This method of allocating AN TEID allocates QoS flows that need to be synchronized in the same service to the same GTP-U tunnel, so the base station only needs to detect the data packets in this GTP-U tunnel and identify the need for synchronization. There is no need to identify the data packets that need to be synchronized in other GTP-U tunnels, which helps to improve the accuracy and efficiency of synchronization.
  • the base station can normally assign an AN TEID to each PDU session according to existing methods and bind the QFI corresponding to the AN TEID.
  • Step 407 The base station sends AN tunnel information to the SMF.
  • the AN tunnel information includes AN TEID.
  • Step 408a SMF sends AN tunnel information to UPF, and the AN tunnel information includes AN TEID.
  • Step 408b UPF sends response information to SMF.
  • the response information is the response to step 408a.
  • Step 409 SMF sends response information to PCF.
  • the response information is the response to step 403.
  • Step 410 PCF sends response information to AF.
  • the response information is the response to step 402.
  • steps 408b, 409, and 410 are all optional steps.
  • Step 411 AF sends the downlink data packet of the service to UPF.
  • This service is the service indicated by the identification information of the service in step 402.
  • the downlink data packet here may be a data packet of the audio data stream 1, a data packet of the video data stream 2, or a data packet of the sensing data stream 3.
  • Step 412 UPF encapsulates the downlink data packet.
  • the UPF adds a GTP-U header to the received downlink data packet.
  • the GTP-U header includes the frame number, QFI and AN TEID.
  • the GTP-U packet header of the downstream data packet of the QoS flow that requires synchronization also includes a synchronization indication.
  • Step 413 UPF sends the downlink data packet to the base station.
  • Step 414 The base station performs synchronous scheduling on the downlink data packets of the service.
  • the base station when the SMF sends the QFI of the QoS flows corresponding to the service that need to be synchronized to the base station in the above step 404, the base station can know in advance which QoS flows of the service need to be synchronized, so the base station can receive these QoS flows. After receiving the downlink data packet, the received downlink data packet is scheduled synchronously.
  • the UPF when the SMF does not send the QFI of the QoS flow corresponding to the service that needs to be synchronized to the base station in the above step 404, and the above step 405 is executed, the UPF performs the following steps on the downlink data packets of the service in the above step 412: During encapsulation, a synchronization indication is added to the GTP-U header of the downlink data packet of the QoS flow that needs to be synchronized, so that the base station can determine whether the downlink data packet needs to be synchronized based on whether the downlink data packet carries a synchronization indication.
  • the QoS flow of a service that requires synchronization is allocated to the same GTP-U tunnel for transmission, so the base station only needs to detect the QoS flow of the service that requires synchronization in one GTP-U tunnel.
  • QoS flow 2, QoS flow 4 and QoS flow 8 that need to be synchronized are all assigned to GTP-U tunnel 1 indicated by AN TEID1 for transmission, so the base station only needs to transmit in GTP-U tunnel 1 Detect the QoS flow that needs to be synchronized for this service.
  • the GTP-U header of downlink data packet 1 carries frame number 1, QFI1, and AN TEID1;
  • the GTP-U header of downlink data packet 2 carries frame number 2, QFI2, AN TEID1, and synchronization indication;
  • the GTP-U header of downlink data packet 3 carries frame number 3, QFI3, and AN TEID1;
  • the GTP-U header of downlink data packet 4 carries frame number 4, QFI4, AN TEID1, and synchronization indication;
  • the GTP-U header of downlink data packet 5 carries frame number 5, QFI5, AN TEID1;
  • the GTP-U header of downlink data packet 6 carries frame number 6, QFI1, and AN TEID2;
  • the GTP-U header of downlink data packet 7 carries frame number 7, QFI2, and AN TEID2;
  • the GTP-U header of downlink data packet 8 carries frame number 8, QFI6, AN TEID1, and synchronization indication;
  • the GTP-U header of downlink data packet 9 carries frame number 9, QFI7, AN TEID1;
  • the GTP-U header of downlink data packet 10 carries frame number 10, QFI1, and AN TEID3.
  • the base station After receiving the above 10 downlink data packets, the base station filters out the downlink data packets carrying AN-TEID1, that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9, and then filters out the downlink data packets carrying AN-TEID1. Synchronize the indicated downlink data packet 2, downlink data packet 4 and downlink data packet 8, and based on the frame numbers in downlink data packet 2, downlink data packet 4 and downlink data packet 8, the data flow (or QoS flow) of the service to synchronize.
  • AN-TEID1 that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9
  • AN-TEID1 filters out the downlink data packets carrying AN-TEID1. Synchronize the indicated downlink data packet 2, downlink data packet 4 and downlink data packet 8, and based on the frame numbers in downlink data packet 2, downlink data packet 4 and downlink data packet 8, the data flow (or QoS
  • the base station after receiving the above 10 downlink data packets, the base station directly filters out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry AN-TEID1 and synchronization indication, and based on the downlink data packet 2, downlink data packet 4 and the frame number in the downlink data packet 8 to synchronize the data flow (or QoS flow) of the service.
  • multiple PDU sessions corresponding to a service that require synchronization of QoS flows are assigned to the same GTP-U tunnel.
  • the GTP-U tunnel is identified by AN TEID.
  • the multiple PDU sessions are bound by the same association identifier.
  • the base station synchronizes the data packets of QoS flows that need to be synchronized, which can ensure the synchronization of different data flows of the same service, thereby improving user experience.
  • the base station since the QoS flows that need to be synchronized are allocated to the same GTP-U tunnel for transmission, the base station only needs to detect the QoS flows that need to be synchronized for the service in one GTP-U tunnel, which can improve the synchronization speed and accuracy. Thereby improving user experience.
  • Figure 5 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • the data packet of a QoS flow corresponding to a service that needs to be synchronized carries a group identifier.
  • the base station determines that the data packet carrying the group identifier is a data packet that may need to be synchronized, and the data packet that does not carry a group identifier is data that does not need to be synchronized. packets, and then the base station further determines the data packets that need to be synchronized from the data packets that carry the group identifier, and performs synchronization scheduling based on the data packets that need to be synchronized.
  • the method includes the following steps:
  • Step 501a UE1 establishes one or more PDU sessions.
  • Step 501b UE2 establishes one or more PDU sessions.
  • the SMFs corresponding to the PDU sessions established by UE1 and UE2 are the same, and the corresponding PCFs are the same or different.
  • the PCFs corresponding to the PDU sessions established by UE1 and UE2 are the same, and the corresponding SMFs are the same or different.
  • the UE1 and UE2 can receive or send different data streams of the same target service.
  • Step 502 The AF sends the identification information of the service and the synchronization information of the service to the PCF.
  • the synchronization information includes the synchronization indication, and includes synchronization status information or the frame rate of each data stream of the service.
  • Step 503 The PCF sends the PCC rule to the SMF.
  • the PCC rule includes the identification information of the service and the synchronization information of the service.
  • the PCF can also assign association identifiers to these PDU sessions, and carry the association identifier and the identification information of the PCF in the PCC rules.
  • the association identifier is associated with the PDU session corresponding to the data stream that needs to be synchronized for a certain service. That is, the optional PCC rule also includes identification information of an association identifier and a PCF, and the PCF is the PCF that generates the association identifier.
  • one PCC rule corresponds to one PDU session
  • the PDU session is the PDU session of UE1 or the PDU session of UE2.
  • the audio data stream 1 of a certain service corresponds to the PDU session 1 of UE1
  • the video data stream 2 of the service corresponds to the PDU session 2 of UE1
  • the sensing data stream 3 of the service corresponds to the PDU session 4 of UE2.
  • Step 504 The SMF sends the service association identifier and the service synchronization rule to the base station.
  • step 504 also sends the QFI of the QoS flow corresponding to the service that needs to be synchronized.
  • step 504 also sends identification information of the PCF.
  • step 504 also sends the identification information of the SMF.
  • SMF After receiving one or more PCC rules, SMF maps the data flow corresponding to the PCC rule into a QoS flow and assigns a QFI to each QoS flow. Among them, a data flow can be mapped to a QoS flow, and each QoS flow is carried in a PDU session for transmission. A PDU session can carry one or multiple QoS flows.
  • the SMF when the SMF allocates QFI to each QoS flow, it allocates QFI to the QoS flow in the PDU session according to the existing method.
  • the SMF needs to ensure that the QFIs of different QoS flows in the same PDU session are different, and that the QFIs of different QoS flows in different PDU sessions are different.
  • the QFI of streams can be the same or different. Taking the example in Figure 3(a) as an example, the QFI allocated by the SMF for the QoS flow in each PDU session can be as shown in Figure 3(c).
  • Business synchronization rules include synchronization status information and/or synchronization accuracy.
  • the meanings of the synchronization status information and synchronization accuracy are as described in other embodiments.
  • the SMF may perform the above step 504 respectively for multiple PDU sessions corresponding to the same association identifier.
  • the SMF sends message 1 to the base station.
  • the message 1 includes the association identifier, synchronization rules, and QFI of each QoS flow in the PDU session 1.
  • the SMF sends message 2 to the base station.
  • the message 2 includes the association identifier, synchronization rules. rules and the QFI of each QoS flow in the PDU session 2, the SMF sends a message 3 to the base station.
  • the message 3 includes the association identifier, the synchronization rule and the QFI of each QoS flow in the PDU session 4.
  • the association identifiers in message 1, message 2 and message 3 are the same and the synchronization rules are the same.
  • Step 505 The base station generates a group identifier based on the association identifier.
  • the base station allocates the group identifier based on the identification information and association identifier of the PCF. For example, PCF1 assigns association identifier 1 to the PDU session to which the QoS flow of service 1 needs to be synchronized, PCF2 assigns association identifier 1 to the PDU session to which the QoS flow of service 2 needs to be synchronized belongs, and PCF3 assigns association identifier 1 to the QoS flow of service 3 that needs to be synchronized.
  • PCF1 assigns association identifier 1 to the PDU session to which the QoS flow of service 1 needs to be synchronized
  • PCF2 assigns association identifier 1 to the PDU session to which the QoS flow of service 2 needs to be synchronized belongs
  • PCF3 assigns association identifier 1 to the QoS flow of service 3 that needs to be synchronized.
  • the PDU session to which it belongs is assigned association identifier 2, then the base station generates group identifier 1 based on the identification information of PCF1 and association identifier 1, generates group identifier 2 based on the identification information of PCF2 and association identifier 1, and generates group identifier 2 based on the identification information of PCF3 and association identifier 2.
  • logo 3 the identification information of PCF1 and association identifier 1
  • group identifier 2 based on the identification information of PCF2 and association identifier 1
  • group identifier 2 based on the identification information of PCF3 and association identifier 2.
  • the base station allocates the group identifier based on the identification information and association identifier of the SMF. For example, SMF1 assigns association identifier 1 to the PDU session to which the QoS flow of service 1 needs to be synchronized, SMF2 assigns association identifier 1 to the PDU session to which the QoS flow of service 2 needs to be synchronized belongs, and SMF3 assigns association identifier 1 to the QoS flow of service 3 that needs to be synchronized.
  • the PDU session to which it belongs is assigned association identifier 2, then the base station generates group identifier 1 based on the identifier information of SMF1 and association identifier 1, generates group identifier 2 based on the identifier information of SMF2 and association identifier 1, and generates group identifier 2 based on the identifier information of SMF3 and association identifier 2.
  • Step 506 The base station sends the group identifier and AN TEID to the SMF.
  • the AN TEID is determined by the base station according to the existing method, that is, each PDU session is assigned an AN TEID and bound to the QFI corresponding to the AN TEID.
  • Step 507a The SMF sends the group identifier and AN TEID to the UPF. Optionally, it also sends the QFI and synchronization indication of the QoS flow corresponding to the service that needs to be synchronized to the UPF.
  • Step 507b UPF sends response information to SMF.
  • the response information is the response to step 507a.
  • Step 508 SMF sends response information to PCF.
  • the response information is the response to step 503.
  • Step 509 PCF sends response information to AF.
  • the response information is a response to step 502.
  • Step 510 AF sends the downlink data packet of the service to UPF.
  • This service is the service indicated by the identification information of the service in step 502 above.
  • the downlink data packet here may be a data packet of the audio data stream 1, a data packet of the video data stream 2, or a data packet of the sensing data stream 3.
  • Step 511 UPF encapsulates the downlink data packet.
  • the UPF adds a GTP-U header to the received downlink data packet.
  • the GTP-U header includes the frame number, QFI, AN TEID and group identification.
  • the UPF receives the QFI and synchronization indication of the QoS flow that needs to be synchronized corresponding to the service from the SMF, the GTP-U header of the downstream data packet of the QoS flow that needs to be synchronized also includes the synchronization indication.
  • Step 512 UPF sends the downlink data packet to the base station.
  • Step 513 The base station performs synchronous scheduling on the downlink data packets of the service.
  • the base station when the SMF sends the QFI of the QoS flows corresponding to the service that need to be synchronized to the base station in the above step 504, the base station can know in advance which QoS flows of the service need to be synchronized, so the base station can receive these QoS flows. After receiving the downlink data packet, the received downlink data packet is scheduled synchronously.
  • the GTP-U header of downlink data packet 1 carries frame number 1, QFI1, AN TEID1, and group ID 1;
  • the GTP-U header of downlink data packet 2 carries frame number 2, QFI2, AN TEID1, group identifier 1, and synchronization indication;
  • the GTP-U header of downlink data packet 3 carries frame number 3, QFI3, AN TEID1, and group ID 1;
  • the GTP-U header of downlink data packet 4 carries frame number 4, QFI1, AN TEID2, group identifier 1, and synchronization indication;
  • the GTP-U header of downlink data packet 5 carries frame number 5, QFI2, AN TEID2, and group ID 1;
  • the GTP-U header of downlink data packet 6 carries frame number 6, QFI1, and AN TEID3;
  • the GTP-U header of downlink data packet 7 carries frame number 7, QFI2, and AN TEID3;
  • the GTP-U header of downlink data packet 8 carries frame number 8, QFI1, AN TEID4, group identifier 1, and synchronization indication;
  • the GTP-U header of downlink data packet 9 carries frame number 9, QFI2, AN TEID4, and group ID 1;
  • the GTP-U header of downlink data packet 10 carries frame number 10, QFI1, and AN TEID5.
  • the base station After receiving the above 10 downlink data packets, the base station filters out the downlink data packets carrying group ID 1, that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9, and then filters out the downlink data packets carrying group ID 1. Synchronize the indicated downlink data packet 2, downlink data packet 4 and downlink data packet 8, and based on the frame numbers in downlink data packet 2, downlink data packet 4 and downlink data packet 8, the data flow (or QoS flow) of the service to synchronize.
  • group ID 1 that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9
  • the base station filters out the downlink data packets carrying group ID 1. Synchronize the indicated downlink data packet 2, downlink data packet 4 and downlink data packet 8, and based on the frame numbers in downlink data packet 2, downlink data packet 4 and downlink data packet 8, the data flow (or QoS flow) of the service to synchronize.
  • the base station after receiving the above 10 downlink data packets, the base station directly filters out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry the group identifier 1 and the synchronization indication, and based on the downlink data packet 2, downlink data packet 4 and the frame number in the downlink data packet 8 to synchronize the data flow (or QoS flow) of the service.
  • step 414 For the specific method for the base station to synchronously schedule the service data flow (or the data packet of the QoS flow), please refer to the description in step 414, which will not be described again.
  • the base station allocates the same group identifier to the PDU sessions of each associated UE according to the association identifier, ensuring that the group identifier corresponding to the associated PDU session is unique.
  • the PDU session corresponding to a group identifier is the PDU session to which the QoS flow corresponding to the same service that needs to be synchronized belongs.
  • the base station receives the QoS flow that needs to be synchronized, it searches for the QoS flow that needs to be synchronized in the PDU session containing the same group identifier and performs synchronization scheduling based on the synchronization rules. This can ensure the synchronization of different data flows of the same service, thereby improving user experience.
  • Figure 6 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • the base station records multiple access network tunnel endpoint identifiers used to transmit data packets corresponding to a service that require synchronized QoS flows, and the base station determines the GTP-U tunnels received from these access network tunnel endpoint identifiers.
  • the data packets are data packets that may need to be synchronized, and then the base station further determines the data packets that need to be synchronized from the data packets that may need to be synchronized, and performs synchronization scheduling based on the data packets that need to be synchronized.
  • the base station determines the synchronization relationship between the multiple access network tunnel endpoint identifiers.
  • the method includes the following steps:
  • Step 601a is the same as step 501a above.
  • Step 601b is the same as step 501b above.
  • Steps 602 to 604 are the same as steps 502 to 504 described above.
  • Step 605 The base station assigns an access network tunnel endpoint identifier (AN TEID) to each PDU session and records the synchronization relationship between AN TEIDs.
  • AN TEID access network tunnel endpoint identifier
  • An implementation method is to allocate an association identifier by SMF/PCF/AF, and then the base station will use the identification information and association identifier of SMF/PCF/AF (that is, the identification information and association identifier of SMF, or the identification information and association identifier of PCF, or AF identification information and association identification), determine the PDU session to which the QoS flow of the service that needs to be synchronized belongs, and establish a synchronization relationship between the AN TEIDs corresponding to these PDU sessions, which indicates that the QoS flow of the service that needs to be synchronized is in these AN TEID is transmitted in the tunnel corresponding to it.
  • the identification information and association identifier of SMF/PCF/AF that is, the identification information and association identifier of SMF, or the identification information and association identifier of PCF, or AF identification information and association identification
  • the base station can also establish a corresponding relationship between the AN TEID and the QFI of the QoS flow that needs to be synchronized.
  • the base station can receive association identifier 1 and SMF/PCF through step 604. /AF identification information, and based on the association identification 1 and the identification information of SMF/PCF/AF, it is determined that the PDU sessions to which the QoS flows that need to be synchronized belong, including PDU session 1, PDU session 2 and PDU session 4. Then the base station also allocates different AN TEIDs to each PDU session of the UE, and the allocation result is shown in Figure 3(c).
  • the base station establishes the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4 based on the associated identifiers. Subsequent QoS flows that need to be synchronized for this service will be transmitted to the AN TEID1, AN TEID2 and AN TEID4 corresponding GTP-U tunnels. base station. If in step 604 above, the SMF also sends the QFI of the QoS flows corresponding to the service that need to be synchronized (i.e., QoS flow 2, QoS flow 4, and QoS flow 8) to the base station, then the base station establishes the following corresponding relationship:
  • the QFI2 is the identification information of QoS flow 2;
  • the QFI1 is the identification information of QoS flow 4;
  • the QFI1 is the identification information of QoS flow 8.
  • Step 606 The base station sends the AN TEID to the SMF.
  • Step 607a The SMF sends the AN TEID to the UPF. Optionally, it also sends the QFI and synchronization indication of the QoS flow corresponding to the service that needs to be synchronized to the UPF.
  • Step 607b UPF sends response information to SMF.
  • the response information is the response to step 607a.
  • Step 608 SMF sends response information to PCF.
  • the response information is the response to step 603.
  • Step 609 PCF sends response information to AF.
  • the response information is a response to step 602.
  • steps 607b, 608, and 609 are all optional steps.
  • Step 610 AF sends the downlink data packet of the service to UPF.
  • This service is the service indicated by the identification information of the service in step 602.
  • Step 611 UPF encapsulates the downlink data packet.
  • the UPF adds a GTP-U header to the received downlink data packet.
  • the GTP-U header includes the frame number, QFI and AN TEID.
  • the UPF receives a synchronization indication from the SMF, the GTP-U header of the downstream data packet of the QoS flow that needs to be synchronized also includes the synchronization indication.
  • Step 612 UPF sends the downlink data packet to the base station.
  • Step 613 The base station performs synchronous scheduling on the downlink data packets of the service.
  • step 607a if the above step 607a does not send the QFI and synchronization indication of the QoS flow corresponding to the service that needs to be synchronized, then the downlink data packets sent by the UPF to the base station do not carry the synchronization indication, and the base station determines the synchronization indication according to AN TEID1, AN TEID2
  • the synchronization relationship between AN TEID4, the corresponding relationship between AN TEID1 and QFI2, the corresponding relationship between AN TEID2 and QFI1, and the corresponding relationship between AN TEID4 and QFI1 synchronously schedule the following types of downlink data packets: carrying AN TEID1 and QFI2
  • the downlink data packet carries AN TEID2 and QFI1
  • the downlink data packet carries AN TEID4 and QFI1.
  • step 607a if the above-mentioned step 607a sends the QFI and synchronization indication of the QoS flow that needs to be synchronized corresponding to the service, then the downlink data packets of the QoS flow that need to be synchronized sent by the UPF to the base station all carry the synchronization indication, then the base station will
  • the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4 performs synchronous scheduling on the following types of downlink data packets: downlink data packets carrying AN TEID1 and synchronization instructions, downlink data packets carrying AN TEID2 and synchronization instructions, and downlink data packets carrying AN TEID4 and sync-indicated downstream packets.
  • the GTP-U header of downlink data packet 1 carries frame number 1, QFI1, and AN TEID1;
  • the GTP-U header of downlink data packet 2 carries frame number 2, QFI2, AN TEID1, and synchronization indication;
  • the GTP-U header of downlink data packet 3 carries frame number 3, QFI3, and AN TEID1;
  • the GTP-U header of downlink data packet 4 carries frame number 4, QFI1, AN TEID2, and synchronization indication;
  • the GTP-U header of downlink data packet 5 carries frame number 5, QFI2, and AN TEID2;
  • the GTP-U header of downlink data packet 6 carries frame number 6, QFI1, and AN TEID3;
  • the GTP-U header of downlink data packet 7 carries frame number 7, QFI2, and AN TEID3;
  • the GTP-U header of downlink data packet 8 carries frame number 8, QFI1, AN TEID4, and synchronization indication;
  • the GTP-U header of downlink data packet 9 carries frame number 9, QFI2, AN TEID4;
  • the GTP-U header of downlink data packet 10 carries frame number 10, QFI1, and AN TEID5.
  • the base station After receiving the above 10 downlink data packets, the base station filters out the downlink data packets carrying AN TEID1, AN TEID2 or AN TEID4, that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9, and then Then filter out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry the synchronization indication, and based on the frame numbers in the downlink data packet 2, downlink data packet 4 and downlink data packet 8, the data flow of the service (or QoS flow) for synchronization.
  • AN TEID1, AN TEID2 or AN TEID4 that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9
  • the base station filters out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry the synchronization indication, and based on the frame numbers in the downlink data packet 2, downlink data packet 4 and downlink data packet 8, the
  • the base station after receiving the above 10 downlink data packets, the base station directly filters out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry synchronization instructions and carry AN TEID1, AN TEID2 or AN TEID4, and based on the downlink data
  • the frame numbers in packet 2, downlink data packet 4 and downlink data packet 8 are used to synchronize the data flow (or QoS flow) of the service.
  • step 414 For the specific method for the base station to synchronize the data flow of the service, please refer to the description in step 414, which will not be described again.
  • the base station generates AN TEIDs for each PDU session and associates the AN TEIDs with synchronization relationships, that is, establishing a synchronization relationship with the AN TEIDs of the PDU sessions to which the QoS flow corresponding to the same service that needs to be synchronized belongs.
  • the base station receives the QoS flow that needs to be synchronized, it searches for the QoS flow that needs to be synchronized in the GTP-U tunnel corresponding to the AN TEID that has established a synchronization relationship and performs synchronization scheduling based on the synchronization rules, which can ensure the synchronization of different data flows of the same service. , thereby improving user experience.
  • Figure 7 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • the base station records multiple access network tunnel endpoint identifiers used to transmit data packets corresponding to a service that require synchronized QoS flows, and the base station determines the GTP-U tunnels received from these access network tunnel endpoint identifiers.
  • the data packets are data packets that may need to be synchronized, and then the base station further determines the data packets that need to be synchronized from the data packets that may need to be synchronized, and performs synchronization scheduling based on the data packets that need to be synchronized.
  • the SMF determines the synchronization relationship between the multiple access network tunnel endpoint identifiers, and sends the synchronization relationship to the base station.
  • the method includes the following steps:
  • Step 701a is the same as step 501a above.
  • Step 701b is the same as step 501b above.
  • Steps 702 to 703 are the same as steps 502 to 503 described above.
  • Step 704 The SMF sends synchronization rules to the base station.
  • Step 705 The base station allocates an access network tunnel endpoint identifier (AN TEID) to each PDU session and sends the AN TEID to the SMF.
  • AN TEID access network tunnel endpoint identifier
  • Step 706 The SMF sends the synchronization relationship between each AN TEID to the base station.
  • An implementation method is that PCF/AF generates an association identifier and sends the association identifier directly or indirectly to SMF. Then SMF determines the PDU sessions to which the QoS flows that need to be synchronized belong based on the association identifier, and establishes the AN TEID corresponding to these PDU sessions. The synchronization relationship between them indicates that the QoS flow of the service that needs to be synchronized is transmitted in the tunnel corresponding to these AN TEIDs, and then the SMF sends the synchronization relationship between these AN TEIDs to the base station. Optionally, the SMF can also send the correspondence between the AN TEID and the QFI of the QoS flow that needs to be synchronized to the base station.
  • Another implementation method is that SMF determines the PDU sessions to which the QoS flows of the service that need to be synchronized belong, and establishes the synchronization relationship between the AN TEIDs corresponding to these PDU sessions, which indicates that the QoS flows of the service that need to be synchronized are in these AN TEIDs. Transmission is carried out in the corresponding tunnel, and then SMF sends the synchronization relationship between these AN TEIDs to the base station.
  • the SMF can also send the correspondence between the AN TEID and the QFI of the QoS flow that needs to be synchronized to the base station.
  • SMF determines (or SMF determines by itself) the PDU session to which the QoS flow of the service that needs to be synchronized belongs based on the association identifier allocated by PCF/AF. Including PDU session 1, PDU session 2 and PDU session 4, SMF establishes the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4. Subsequent QoS flows that need to be synchronized for this service will pass AN TEID1, AN TEID2 and AN TEID4.
  • the corresponding GTP-U tunnel is transmitted to the base station, so SMF sends the synchronization relationship between AN TEID1, AN TEID2 and AN TEID4 to the base station.
  • the SMF can also send the corresponding relationship between the AN TEID and the QFI of the QoS flow that needs to be synchronized to the base station. That is, the SMF sends the following corresponding relationship to the base station:
  • the QFI2 is the identification information of QoS flow 2;
  • the QFI1 is the identification information of QoS flow 4;
  • the QFI1 is the identification information of QoS flow 8.
  • Step 707a is the same as step 607a.
  • Step 707b is the same as step 607b.
  • Step 708 to step 713 are the same as step 608 to step 613.
  • the base station generates AN TEID for each PDU session, and SMF associates the AN TEID with a synchronization relationship. That is, the AN TEID of the PDU session to which the QoS flow corresponding to the same service needs to be synchronized belongs to establish a synchronization relationship, and then SMF Send the synchronization relationship to the base station.
  • the base station receives the QoS flow that needs to be synchronized, it searches for the QoS flow that needs to be synchronized in the tunnel corresponding to the AN TEID that has established a synchronization relationship and performs synchronization scheduling based on the synchronization rules. This can ensure the synchronization of different data flows of the same service, thereby improving user experience.
  • Figure 8 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • the base station records multiple access network tunnel endpoint identifiers used to transmit data packets corresponding to a service that require synchronization of QoS flows and the identification information of the network device that allocates the access network tunnel endpoint identifier.
  • the base station determines that the data packet is a data packet that may need to be synchronized, and then the base station further determines the data that needs to be synchronized from the data packet that may need to be synchronized. Packets, and perform synchronization scheduling according to the data packets that need to be synchronized.
  • the base station determines the synchronization relationship between the multiple access network tunnel endpoint identifiers.
  • the method includes the following steps:
  • Step 801a is the same as step 501a above.
  • Step 801b is the same as step 501b above.
  • Steps 802 to 804 are the same as steps 502 to 504 described above.
  • Step 805 The base station establishes a corresponding relationship between the identification information of the SMF/PCF/AF and the associated identification.
  • the base station assigns different access network tunnel endpoint identifiers (AN TEID) to different PDU sessions.
  • AN TEID access network tunnel endpoint identifiers
  • step 804 also sends the identification information of the SMF, and the base station establishes a corresponding relationship between the identification information of the SMF and the association identifier.
  • the PCF allocates the association identifier
  • both steps 803 and 804 send the identification information of the PCF
  • the base station establishes a corresponding relationship between the identification information of the PCF and the association identifier.
  • the AF allocates the association identifier
  • step 802, step 803, and step 804 all send the identification information of the AF, and the base station establishes a corresponding relationship between the identification information of the AF and the association identifier. Subsequently, if the downlink data packets received by the base station carry the identification information of the SMF/PCF/AF and the associated identification, the base station will perform synchronous scheduling on these downlink data packets.
  • Step 806 The base station sends the AN TEID to the SMF.
  • Step 807a SMF sends AN TEID, association identifier and identification information of SMF/PCF/AF to UPF.
  • the QFI and synchronization indication of the QoS flow corresponding to the service that needs to be synchronized are also sent to the UPF.
  • SMF allocates the association identifier
  • SMF sends the AN TEID, association identifier and SMF identification information to UPF.
  • PCF allocates the association identifier
  • SMF sends AN TEID, association identifier and PCF identification information to UPF.
  • the AF allocates the association identifier
  • the SMF sends the AN TEID, association identifier and AF identification information to the UPF.
  • Step 807b UPF sends response information to SMF.
  • the response information is the response to step 807a.
  • Step 808 SMF sends response information to PCF.
  • the response information is the response to step 803.
  • Step 809 PCF sends response information to AF.
  • the response information is a response to step 802.
  • Step 810 AF sends the downlink data packet of the service to UPF.
  • This service is the service indicated by the identification information of the service in step 802.
  • Step 811 UPF encapsulates the downlink data packet.
  • the UPF adds a GTP-U header to the received downstream data packet of the QoS flow that needs to be synchronized.
  • the GTP-U header includes the frame number, QFI, AN TEID, association identifier and SMF/PCF/AF identification information.
  • the UPF receives a synchronization indication from the SMF
  • the GTP-U header of the downstream data packet of the QoS flow that needs to be synchronized also includes the synchronization indication.
  • Step 812 UPF sends the downlink data packet to the base station.
  • Step 813 The base station performs synchronous scheduling on the downlink data packets of the service.
  • the base station synchronously schedules the following types of downlink data packets based on the corresponding relationship between the identification information of SMF/PCF/AF and the associated identification: downlink data packets carrying the identification information of QFI1, SMF/PCF/AF and associated identification, and the downlink data packets carrying The identification information of QFI2, SMF/PCF/AF and the associated identification downlink data packets.
  • the association identifiers carried in these downlink data packets are the same, and the identification information of SMF/PCF/AF is the same.
  • step 807a if the above step 807a sends the QFI and synchronization indication of the QoS flow corresponding to the service that needs to be synchronized, then the downlink data packets of the QoS flow that need to be synchronized sent by the UPF to the base station all carry the synchronization indication, and the base station will The corresponding relationship between the identification information of SMF/PCF/AF and the association identification, and the downlink data packets carrying the synchronization indication, the identification information of the same SMF/PCF/AF and the same association identification are synchronously scheduled. Among them, the association identifiers carried in these downlink data packets are the same, and the identification information of SMF/PCF/AF is the same.
  • the GTP-U header of downlink data packet 1 carries frame number 1, QFI1, AN TEID1, SMF ID1, and association identifier 1;
  • the GTP-U header of downlink data packet 2 carries frame number 2, QFI2, AN TEID1, SMF ID1, association identifier 1, and synchronization indication;
  • the GTP-U header of downlink data packet 3 carries frame number 3, QFI3, AN TEID1, SMF ID1, and association identifier 1;
  • the GTP-U header of downlink data packet 4 carries frame number 4, QFI1, AN TEID2, SMF ID1, association identifier 1, and synchronization indication;
  • the GTP-U header of downlink data packet 5 carries frame number 5, QFI2, AN TEID2, SMF ID1, and association identifier 1;
  • the GTP-U header of downlink data packet 6 carries frame number 6, QFI1, and AN TEID3;
  • the GTP-U header of downlink data packet 7 carries frame number 7, QFI2, and AN TEID3;
  • the GTP-U header of downlink data packet 8 carries frame number 8, QFI1, AN TEID4, SMF ID1, association identifier 1, and synchronization indication;
  • the GTP-U header of downlink data packet 9 carries frame number 9, QFI2, AN TEID4, SMF ID1, and association identifier 1;
  • the GTP-U header of downlink data packet 10 carries frame number 10, QFI1, and AN TEID5.
  • the base station After receiving the above 10 downlink data packets, the base station filters out the downlink data packets carrying SMF ID1 and association identification 1, that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9, and then selects the downlink data packets. Filter out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry the synchronization indication, and based on the frame numbers in the downlink data packet 2, downlink data packet 4 and downlink data packet 8, the data flow (or QoS flow) for synchronization.
  • SMF ID1 and association identification 1 that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9
  • the base station filters out the downlink data packets carrying SMF ID1 and association identification 1, that is, downlink data packet 1 to downlink data packet 5, as well as downlink data packet 8 and downlink data packet 9, and then selects the downlink data packets. Filter out the downlink data packet 2, downlink data packet 4
  • the base station after receiving the above 10 downlink data packets, the base station directly filters out the downlink data packet 2, downlink data packet 4 and downlink data packet 8 that carry SMF ID1, association identification 1 and synchronization indication, and based on the downlink data packet 2, downlink data packet
  • the frame numbers in data packet 4 and downlink data packet 8 are used to synchronize the data flow (or QoS flow) of the service.
  • step 414 For the specific method for the base station to synchronize the data flow of the service, please refer to the description in step 414, which will not be described again.
  • the base station generates AN TEID for each PDU session, and establishes a corresponding relationship between the identification information of SMF/PCF/AF and the associated identification.
  • the base station determines the QoS flow that needs to be synchronized from the QoS flow that carries the identification information of the SMF/PCF/AF and performs synchronization scheduling based on the synchronization rules, which can ensure the security of different data flows of the same service. synchronization to improve user experience.
  • FIG. 9 is a schematic flowchart of a synchronization scheduling method provided by an embodiment of the present application.
  • multiple PDU sessions belonging to a QoS flow corresponding to a service that need to be synchronized are allocated to the same GTP-U tunnel, so the data packets of the QoS flow corresponding to the service that need to be synchronized are all transmitted through the GTP-U tunnel.
  • the GTP-U tunnel is exclusively used to transmit the data packets of the QoS flow corresponding to the service that need to be synchronized, and does not transmit other data packets.
  • the data packets received by the base station from the GTP-U tunnel are all data packets that need to be synchronized, and the base station performs synchronization scheduling based on the data packets that need to be synchronized.
  • the method includes the following steps:
  • Step 901a is the same as step 401a above.
  • Step 901b is the same as step 401b above.
  • Steps 902 to 903 are the same as steps 402 to 403 described above.
  • Step 904 The SMF sends the association identifier of the service, the synchronization rule of the service, and the QFI of the QoS flow corresponding to the service that needs to be synchronized to the base station.
  • step 404 For the meaning of the association identifier and the synchronization rule, please refer to the description in step 404.
  • step 904 when SMF allocates QFI to each QoS flow, it allocates different QFIs to the QoS flows that need to be synchronized in the associated PDU session. Synchronized QoS flows are allocated QFI according to the existing method, that is, for QoS flows that do not need to be synchronized in the associated PDU session, it is only necessary to ensure that the QFIs of the QoS flows that do not need to be synchronized in the same PDU session are different, and there is no need to ensure that they are different. QoS flows within a PDU session that do not require synchronization have different QFIs. Taking the example in Figure 3(a) as an example, the QFI allocated by the SMF in this embodiment is as shown in Figure 3(d).
  • Step 905 The base station allocates the same access network tunnel endpoint identifier (AN TEID) to the QoS flows that need to be synchronized in the PDU session corresponding to the same association identifier.
  • AN TEID access network tunnel endpoint identifier
  • This method of allocating AN TEID allocates QoS flows that need to be synchronized in the same service to the same GTP-U tunnel, so the base station only needs to detect the data packets in this GTP-U tunnel and identify the need for synchronization. There is no need to identify the data packets that need to be synchronized in other GTP-U tunnels, which helps to improve the accuracy and efficiency of synchronization. Moreover, since the QoS flows in the GTP-U tunnel are all QoS flows that need to be synchronized, the GTP-U tunnel does not contain QoS flows that do not need to be synchronized. Therefore, after UPF receives the data packet from the AF, it does not need to A synchronization indication is added to the packet header, and the base station performs synchronous scheduling on all data packets received on this GTP-U tunnel.
  • the base station can normally assign an AN TEID to each PDU session according to existing methods and bind the QFI corresponding to the AN TEID.
  • the AN TEID allocated by the base station in this embodiment can be as shown in Figure 3(d).
  • Step 906 is the same as step 407 above.
  • Step 907a is the same as step 408a above.
  • Step 907b is the same as step 408b above.
  • Steps 908 to 910 are the same as steps 409 to 411 described above.
  • steps 907b, 908, and 909 are all optional steps.
  • Step 911 UPF encapsulates the downlink data packet.
  • the UPF adds a GTP-U header to the received downlink data packet.
  • the GTP-U header includes the frame number, QFI and AN TEID.
  • Step 912 The UPF sends the downlink data packet to the base station.
  • Step 913 The base station performs synchronous scheduling on the downlink data packets of the service.
  • the base station synchronously schedules downlink data packets in the GTP-U tunnel where the QoS flow that needs to be synchronized is located.
  • the downlink data packets received through the GTP-U tunnel are all downlink data packets that need to be synchronized for the service.
  • the QoS flow of a service that requires synchronization is allocated to the same GTP-U tunnel for transmission, and the GTP-U tunnel does not contain the QoS flow that does not require synchronization. Therefore, the base station only needs to transmit in one GTP-U tunnel. Detect the QoS flow that needs to be synchronized for this service in the U tunnel.
  • QoS flow 2, QoS flow 4 and QoS flow 8 that need to be synchronized are all assigned to GTP-U tunnel 1 indicated by AN TEID1 for transmission, so the base station only needs to transmit in GTP-U tunnel 1 Detect the QoS flow that needs to be synchronized for this service.
  • the GTP-U header of downlink data packet 1 carries frame number 1, QFI1, and AN TEID2;
  • the GTP-U header of downlink data packet 2 carries frame number 2, QFI1, and AN TEID1;
  • the GTP-U header of downlink data packet 3 carries frame number 3, QFI2, and AN TEID2;
  • the GTP-U header of downlink data packet 4 carries frame number 4, QFI2, and AN TEID1;
  • the GTP-U header of downlink data packet 5 carries frame number 5, QFI1, and AN TEID3;
  • the GTP-U header of downlink data packet 6 carries frame number 6, QFI1, and AN TEID4;
  • the GTP-U header of downlink data packet 7 carries frame number 7, QFI2, and AN TEID4;
  • the GTP-U header of downlink data packet 8 carries frame number 8, QFI3, and AN TEID1;
  • the GTP-U header of downlink data packet 9 carries frame number 9, QFI1, and AN TEID5;
  • the GTP-U header of downlink data packet 10 carries frame number 10, QFI1, and AN TEID6.
  • the base station After receiving the above 10 downlink data packets, the base station filters out the downlink data packets carrying AN-TEID1, namely downlink data packet 2, downlink data packet 4 and downlink data packet 8, and based on the downlink data packet 2, downlink data packet 4 and downlink data packet
  • the frame number in the downlink data packet 8 is used to synchronize the data flow (or QoS flow) of the service.
  • step 414 For the specific method for the base station to synchronize the data flow of the service, please refer to the description in step 414, which will not be described again.
  • the QoS flow corresponding to a service that needs to be synchronized is assigned to the same GTP-U tunnel.
  • the GTP-U tunnel is identified by AN TEID.
  • the PDU session to which the QoS flow that needs to be synchronized belongs is bound through the same association identifier. .
  • the base station synchronously schedules QoS flows that need to be synchronized, which can ensure the synchronization of different data flows of the same service, thereby improving user experience.
  • the QoS flows that need to be synchronized are allocated to the same GTP-U tunnel for transmission, and the GTP-U tunnel does not contain QoS flows that do not need to be synchronized, the QoS flows of the GTP-U tunnel all need to be synchronized.
  • QoS flow, and the downstream data packets of the QoS flow do not need to carry synchronization instructions, so the synchronization speed and accuracy can be improved, thereby improving the user experience.
  • the embodiment of Figure 9 has the following differences: In the embodiment of Figure 9, the QoS flows that need to be synchronized are allocated to the same GTP-U tunnel and the GTP-U tunnel QoS flows that do not require synchronization are not included; in the embodiment of Figure 4, QoS flows that require synchronization are allocated to the same GTP-U tunnel, but the GTP-U tunnel may also contain QoS flows that do not require synchronization.
  • the access network equipment, user plane network element or session management network element includes corresponding hardware structures and/or software modules for executing each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software driving the hardware depends on the specific application scenarios and design constraints of the technical solution.
  • Figures 10 and 11 are schematic structural diagrams of possible communication devices provided by embodiments of the present application. These communication devices can be used to implement the functions of access network equipment, user plane network elements or session management network elements in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be an access network device, a user plane network element or a session management network element, or it may be a module applied to the access network device, user plane network element or session management network element (such as chips).
  • the communication device 1000 shown in FIG. 10 includes a processing unit 1010 and a transceiver unit 1020.
  • the communication device 1000 is used to implement the functions of the access network device, user plane network element or session management network element in the above method embodiment.
  • the transceiver unit 1020 is used to receive multiple data packets of the target service from the user plane network element, and the multiple data packets belong to multiple QoS flow, each data packet in the plurality of data packets contains QFI, the QFI is used to identify the QoS flow to which the data packet belongs, and the plurality of QoS flows include at least two QoS flows of the target service that need to be synchronized; processing Unit 1010, configured to determine at least two data packets containing the same mark information from the plurality of data packets, the mark information corresponding to multiple data connection sessions to which at least two QoS flows of the target service that need to be synchronized belong; from The at least two data packets determine at least two target data packets, and the at least two target data packets correspond to at least two QoS flows of the target service that need to be synchronized; and based on the at least two target data packets, the at least two target data packets
  • the transceiver unit 1020 is also configured to receive an association identifier from the session management network element before receiving multiple data packets of the target service from the user plane network element.
  • the association identifier is associated with the target service.
  • the processing unit 1010 is also configured to determine the mark information according to the association identifier for the data connection session to which at least two QoS flows that need to be synchronized belong to the target service; send and receive Unit 1020 is also configured to send the marking information to the user plane network element through the session management network element.
  • the marking information is a group identifier assigned by the access network device, and the group identifier corresponds to the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the marking information is an access network tunnel endpoint identifier.
  • the access network tunnel endpoint identifier is used to identify a GTP-U tunnel.
  • the GTP-U tunnel is used to transmit at least the target service that needs to be synchronized.
  • the QoS flows in the data connection session to which both QoS flows belong.
  • the marking information includes an association identifier and the identification information of a network device.
  • the association identifier is associated with the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the network device is the one that generates the association.
  • the transceiver unit 1020 is also configured to receive the QFI of at least two QoS flows of the target service that need to be synchronized from the session management network element; wherein the at least two target data packets refer to the QFIs containing Data packet of the target QFI, which is any one of the QFIs of at least two QoS flows of the target service that need to be synchronized.
  • the at least two target data packets refer to data packets containing a synchronization indication
  • the synchronization indication is used to indicate that the QoS flow to which the data packet belongs is a QoS flow of the target service that requires synchronization.
  • the processing unit 1010 is specifically configured to synchronize and schedule at least two QoS flows of the target service that need to be synchronized according to the synchronization status information and the frame numbers contained in the at least two target data packets.
  • the synchronization status information is used to indicate the correspondence between the frame numbers in the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization status.
  • the processing unit 1010 is specifically configured to determine, based on the synchronization status information and the frame numbers contained in the at least two target data packets, that at least two QoS flows of the target service that need to be synchronized do not meet the synchronization accuracy, Then adjust the sending speed of the data packets of the at least two QoS flows of the target service that need to be synchronized.
  • the synchronization accuracy is used to indicate the frame number of the data packets of the at least two QoS flows of the target service that need to be synchronized in the synchronization state. deviation.
  • the transceiver unit 1020 is also used to receive the synchronization status information and the synchronization accuracy from the session management network element.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the transceiver unit 1020 is used to receive multiple data packets of the target service from the user plane network element, and the multiple data packets belong to multiple QoS flow, each data packet in the plurality of data packets contains QFI, the QFI is used to identify the QoS flow to which the data packet belongs, and the plurality of QoS flows include at least two QoS flows of the target service that need to be synchronized; processing Unit 1010, configured to determine at least two data packets containing the same access network tunnel endpoint identifier from the plurality of data packets, the at least two data packets corresponding to at least two QoS flows of the target service that need to be synchronized, the The access network tunnel endpoint identifier is used to identify the target tunnel.
  • the target tunnel is a GTP-U tunnel that transmits at least two QoS flows of the target service that need to be synchronized.
  • the at least two QoS flows of the target service that need to be synchronized correspond to data connections. session; and synchronously scheduling at least two QoS flows of the target service that need to be synchronized according to the at least two data packets.
  • the transceiver unit 1020 is also configured to receive an association identifier from the session management network element and at least one of the target services that needs to be synchronized before receiving multiple data packets of the target service from the user plane network element.
  • the QFI of the two QoS flows, the association identifier associates the data connection sessions to which at least two QoS flows of the target service need to be synchronized;
  • the processing unit 1010 is also configured to associate the association identifier with at least two QoS flows of the target service that need to be synchronized.
  • the QFI of each QoS flow determines the access network tunnel endpoint identifier for at least two QoS flows that need to be synchronized for the target service; the transceiver unit 1020 is also used to send the access network element to the user plane network element through the session management network element.
  • the endpoint identifier of the incoming tunnel is also used to send the access network element to the user plane network element through the session management network element.
  • the processing unit 1010 is specifically configured to synchronize and schedule at least two QoS flows of the target service that need to be synchronized according to the synchronization status information and the frame numbers contained in the at least two data packets.
  • the status information is used to indicate the correspondence between the frame numbers in the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the processing unit 1010 is specifically configured to determine, based on the synchronization status information and the frame numbers contained in the at least two data packets, that at least two QoS flows of the target service that need to be synchronized do not meet the synchronization accuracy, then Adjust the sending speed of the data packets of at least two QoS flows of the target service that need to be synchronized.
  • the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of the at least two QoS flows of the target service that need to be synchronized in the synchronization state. .
  • the transceiver unit 1020 is also configured to receive the synchronization status information and the synchronization accuracy from the session management network element.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the transceiver unit 1020 is used to receive multiple data packets of the target service from the user plane network element, and the multiple data packets belong to multiple QoS flow, each data packet in the plurality of data packets contains QFI, the QFI is used to identify the QoS flow to which the data packet belongs, and the plurality of QoS flows include at least two QoS flows of the target service that need to be synchronized; processing Unit 1010, configured to determine at least two data packets from the plurality of data packets according to the synchronization relationship between the plurality of access network tunnel endpoint identifiers, and each of the at least two data packets also includes the plurality of data packets.
  • the GTP-U tunnels respectively indicated by the multiple access network tunnel end point identifiers are used to transmit at least two QoS flows that need to be synchronized for the target service. ; Determining at least two target data packets from the at least two data packets, the at least two target data packets corresponding to at least two QoS flows of the target service that need to be synchronized; and according to the at least two target data packets, for the target At least two QoS flows of the business that need to be synchronized are scheduled synchronously.
  • the transceiver unit 1020 is also configured to receive an association identifier from the session management network element before receiving multiple data packets of the target service from the user plane network element.
  • the association identifier is associated with the target service.
  • the processing unit 1010 is also configured to determine the multiple access network tunnel endpoint identifiers for the data connection session to which at least two QoS flows that need to be synchronized belong to the target service,
  • the plurality of access network tunnel endpoint identifiers are in one-to-one correspondence with the data connection sessions to which at least two QoS flows of the target service that need to be synchronized belong; and the synchronization relationship is established based on the association identifier.
  • the processing unit 1010 is also configured to, before the transceiver unit 1020 receives multiple data packets of the target service from the user plane network element, at least two QoS flows of the target service that need to be synchronized belong to
  • the data connection session determines the multiple access network tunnel endpoint identifiers, and the multiple access network tunnel endpoint identifiers correspond one-to-one to the data connection sessions to which at least two QoS flows of the target service that need to be synchronized belong; the transceiver unit 1020 also Used to send the plurality of access network tunnel endpoint identifiers to the session management network element; and to receive the synchronization relationship from the session management network element.
  • the transceiver unit 1020 is also configured to receive QFIs of at least two QoS flows that need to be synchronized for the target service from the session management network element; wherein the at least two target data packets refer to A data packet containing a target QFI, which is any one of the QFIs of at least two QoS flows that need to be synchronized for the target service.
  • the at least two target data packets refer to data packets containing a synchronization indication
  • the synchronization indication is used to indicate that the QoS flow to which the data packet belongs is a QoS flow of the target service that requires synchronization.
  • the processing unit 1010 is specifically configured to synchronize and schedule at least two QoS flows of the target service that need to be synchronized according to the synchronization status information and the frame numbers contained in the at least two target data packets.
  • the synchronization status information is used to indicate the correspondence between the frame numbers in the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization status.
  • the processing unit 1010 is specifically configured to determine, based on the synchronization status information and the frame numbers contained in the at least two target data packets, that at least two QoS flows of the target service that need to be synchronized do not meet the synchronization accuracy, Then adjust the sending speed of the data packets of the at least two QoS flows of the target service that need to be synchronized.
  • the synchronization accuracy is used to indicate the frame number of the data packets of the at least two QoS flows of the target service that need to be synchronized in the synchronization state. deviation.
  • the transceiver unit 1020 is also configured to receive the synchronization status information and the synchronization accuracy from the session management network element.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the transceiver unit 1020 is used to receive multiple data packets of the target service from the application function network element, and the multiple data packets belong to multiple QoS flows, the multiple QoS flows include at least two QoS flows of the target service that need to be synchronized; the processing unit 1010 is configured to add marking information and a quality of service flow identifier QFI to at least two data packets of the multiple data packets.
  • the QFI in each of the at least two data packets is used to identify the quality of service QoS flow to which the data packet belongs, and the marking information corresponds to multiple protocol data belonging to the at least two QoS flows of the target service that need to be synchronized.
  • the unit data connection session; the transceiver unit 1020 is also configured to send multiple data packets containing the at least two data packets with added tag information and QFI to the access network device.
  • the transceiver unit 1020 is also configured to receive the tag information from the access network device.
  • the marking information is a group identifier assigned by the access network device, and the group identifier corresponds to the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the marking information is an access network tunnel endpoint identifier.
  • the access network tunnel endpoint identifier is used to identify a GTP-U tunnel.
  • the GTP-U tunnel is used to transmit at least the target service that needs to be synchronized.
  • the QoS flows in the data connection session to which both QoS flows belong.
  • the marking information includes an association identifier and the identification information of a network device.
  • the association identifier is associated with the data connection session to which at least two QoS flows of the target service that need to be synchronized belong.
  • the network device is the one that generates the association.
  • the transceiver unit 1020 is also configured to receive the QFI of at least two QoS flows that need to be synchronized for the target service from the session management network element; the processing unit 1010 is also configured to transmit the QFI to the target service through the transceiver unit 1020.
  • the QFI of at least two QoS flows is synchronized according to the needs of the target service, and at least two data packets of the at least two data packets are synchronized.
  • the at least two target data packets correspond to at least two QoS flows of the target service that need to be synchronized.
  • the synchronization indication is used to indicate that the QoS flow to which the target data packet belongs belongs to the target service. At least two QoS flows need to be synchronized.
  • the at least two target data packets each include a frame number, and the frame number is used for synchronization scheduling of at least two QoS flows that require synchronization of the target service.
  • At least two QoS flows of the target service that need to be synchronized correspond to multiple terminal devices.
  • the processing unit 1010 is used to generate an association identifier.
  • the association identifier is associated with the data connection to which at least two QoS flows of the target service that need to be synchronized belong.
  • Session; transceiver unit 1020 configured to send the association identifier to the access network device, where the association identifier is used for synchronous scheduling of at least two QoS flows that require synchronization of the target service.
  • the transceiver unit 1020 is also configured to send synchronization accuracy and synchronization status information to the access network device.
  • the synchronization status information is used to indicate at least two of the target services that need to be synchronized in the synchronization status.
  • the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the transceiver unit 1020 is also configured to receive PCC rules from the policy control network element, where the PCC rules include the identification information of the target service and the synchronization status information.
  • the transceiver unit 1020 is also configured to send QFIs of at least two QoS flows of the target service that need to be synchronized to the user plane network element.
  • the processing unit 1010 is used to determine the data connection session to which at least two QoS flows of the target service that need to be synchronized belong; the transceiver unit 1020 is used to For receiving multiple access network tunnel endpoint identifiers corresponding to the data connection sessions to which the at least two QoS flows of the target service that need to be synchronized belong to, from the access network device, the data to which the at least two QoS flows of the target service that need to be synchronized belong.
  • connection session has a one-to-one correspondence with the multiple access network tunnel endpoint identifiers; the processing unit 1010 is also used to establish a synchronization relationship between the multiple access network tunnel endpoint identifiers; the transceiver unit 1020 is also used to send a message to the access network The device sends the synchronization relationship, which is used for synchronization scheduling of at least two QoS flows of the target service that need to be synchronized.
  • the transceiver unit 1020 is also configured to send synchronization accuracy and synchronization status information to the access network device.
  • the synchronization status information is used to indicate at least two of the target services that need to be synchronized in the synchronization status.
  • the synchronization accuracy is used to indicate the deviation of the frame numbers of the data packets of at least two QoS flows of the target service that need to be synchronized in the synchronization state.
  • the transceiver unit 1020 is also configured to receive PCC rules from the policy control network element, where the PCC rules include the identification information of the target service and the synchronization status information.
  • the transceiver unit 1020 is also configured to send QFIs of at least two QoS flows of the target service that need to be synchronized to the user plane network element.
  • the communication device 1100 shown in FIG. 11 includes a processor 1110 and an interface circuit 1120.
  • the processor 1110 and the interface circuit 1120 are coupled to each other.
  • the interface circuit 1120 may be a transceiver or an input-output interface.
  • the communication device 1100 may also include a memory 1130 for storing instructions executed by the processor 1110 or input data required for the processor 1110 to run the instructions or data generated after the processor 1110 executes the instructions.
  • the processor 1110 is used to realize the function of the above processing unit 1010
  • the interface circuit 1120 is used to realize the function of the above transceiver unit 1020.
  • processor in the embodiment of the present application can be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application-specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory In memory, register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage media may be located in an ASIC. Additionally, the ASIC can be located in the base station or terminal. Of course, the processor and the storage medium may also exist as discrete components in the base station or terminal.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a base station, a user equipment, or other programmable device.
  • the computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • the computer program or instructions may be transmitted from a website, computer, A server or data center transmits via wired or wireless means to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media.
  • the available media may be magnetic media, such as floppy disks, hard disks, and tapes; optical media, such as digital video optical disks; or semiconductor media, such as solid-state hard drives.
  • the computer-readable storage medium may be volatile or nonvolatile storage media, or may include both volatile and nonvolatile types of storage media.
  • “at least one” refers to one or more, and “plurality” refers to two or more.
  • “And/or” describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects before and after are an “or” relationship; in the formula of this application, the character “/” indicates that the related objects before and after are a kind of "division” Relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种同步调度方法、通信装置及通信系统。该方法包括：接入网设备接收来自用户面网元的目标业务的多个数据包；接入网设备从多个数据包中确定包含有相同标记信息的至少两个数据包；接入网设备从包含有相同标记信息的至少两个数据包确定至少两个目标数据包，该至少两个目标数据包对应目标业务的需要同步的至少两个QoS流；接入网设备根据至少两个目标数据包对目标业务的需要同步的至少两个QoS流的数据包进行同步调度。该方案，接入网设备对目标业务的需要同步的至少两个QoS流的数据包进行同步调度，使得目标业务的多个QoS流的数据包之间保持合理的发送速度，提升了用户体验。

Description

一种同步调度方法、通信装置及通信系统
相关申请的交叉引用
本申请要求在2022年03月18日提交中国专利局、申请号为202210270603.8、申请名称为“一种同步调度方法、通信装置及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种同步调度方法、通信装置及通信系统。
背景技术
在扩展现实(extended reality，XR)、虚拟现实(virtual reality，VR)或增强现实(augmented reality，AR)的应用场景中，一个业务可以产生多个数据流，用户可以通过一个或多个终端设备(如眼镜、手柄、手套、指尖装置、运动垫或健身环等)同时接收该多个数据流，该多个数据流包括视频数据流、音频数据流以及感知数据流，使得用户获得更加强烈的沉浸感，产生身临其境的感觉，极大增强了用户体验。
发明内容
本申请实施例提供一种同步调度方法、通信装置及通信系统，用于实现同一业务的多个QoS流之间的同步调度，从而提升用户体验。
第一方面，本申请实施例提供一种同步调度方法，该方法可以由接入网设备或应用于接入网设备的模块(如芯片)来执行。以接入网设备执行该方法为例，该方法包括：接入网设备接收来自用户面网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；该接入网设备从该多个数据包中确定包含有相同标记信息的至少两个数据包，该标记信息对应该目标业务的需要同步的至少两个QoS流所属的数据连接会话；该接入网设备从包含有相同标记信息的该至少两个数据包确定至少两个目标数据包，该至少两个目标数据包对应该目标业务的需要同步的至少两个QoS流；该接入网设备根据该至少两个目标数据包，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
上述方案，接入网设备根据该至少两个目标数据包对目标业务的需要同步的至少两个QoS流的数据包进行同步调度，使得该目标业务的多个QoS流之间保持合理的发送速度，使得该多个QoS流之间保持协调，提升了用户体验。并且，该方法是先从目标业务的多个数据包中识别出可能包含目标业务的需要同步的至少两个QoS流的至少两个数据包，然后再从该至少两个数据包中识别出该目标业务的需要同步的至少两个QoS流的至少两个目标数据包，通过两步搜索的方法，缩小了该目标业务的需要同步的至少两个QoS流的数据包的搜索范围，避免从大量的QoS流中盲目搜索该目标业务的需要同步的至少两个QoS流的数据包，因而可以提升同步速度，实现快速同步调度，进一步提升用户体验。
一种可能的实现方法中，该接入网设备接收来自用户面网元的目标业务的多个数据包之前，该接入网设备接收来自会话管理网元的关联标识，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话；该接入网设备根据该关联标识，为该目标业务的需要同步的至少两个QoS流所属的数据连接会话确定该标记信息；该接入网设备通过该会话管理网元向该用户面网元发送该标记信息。
上述方案，通过关联标识将目标业务的需要同步的至少两个QoS流所属的多个数据连接会话进行关联，接入网设备根据关联标识获知该目标业务的需要同步的至少两个QoS流将在该多个数据连接会话中进行传输，而不会在其它数据连接会话中进行传输，从而接入网设备可以为该多个数据连接会话确定标记信息，并向用户面网元发送该标记信息，以便于用户面网元在该多个数据连接会话内的QoS流的数据包中添加该标记信息。接入网设备根据收到的数据包中是否包含该标记信息，判断该数据包可能是该目标业务的需要同步的至少两个QoS流，或者不是该目标业务的需要同步的至少两个QoS流，因而接入网设备可以通过标记信息缩小目标业务的需要同步的至少两个QoS流的搜索范围，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该标记信息是由该接入网设备分配的组标识，该组标识对应该目标业务的需要同步的至少两个QoS流所属的数据连接会话。
上述方案，由接入网设备分配组标识作为标记信息，可以保证组标识的唯一性，有助于保证接入网设备根据组标识搜索目标业务的需要同步的至少两个QoS流的数据包时的准确性和提升搜索速度，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该标记信息是接入网隧道端点标识，该接入网隧道端点标识用于标识GTP-U隧道，该GTP-U隧道用于传输该目标业务的需要同步的至少两个QoS流所属的数据连接会话中的QoS流。
上述方案，接入网设备分配接入网隧道端点标识作为标记信息，该接入网隧道端点标识指示的GTP-U隧道用于传输该目标业务的需要同步的至少两个QoS流所属的多个数据连接会话中的QoS流，也即将目标业务的需要同步的至少两个QoS流通过同一个GTP-U隧道进行传输，从而接入网设备只需要在该GTP-U隧道内搜索该目标业务的需要同步的至少两个QoS流，不需要在其它GTP-U隧道内搜索该目标业务的需要同步的至少两个QoS流，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该标记信息包括关联标识和网络设备的标识信息，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话，该网络设备是生成该关联标识的会话管理网元、策略控制网元或应用功能网元。
上述方案，将关联标识和网络设备的标识信息的组合作为标记信息，可以保证标记信息的唯一性，有助于保证接入网设备根据标记信息搜索目标业务的需要同步的至少两个QoS流的数据包时的准确性和提升搜索速度，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该接入网设备从会话管理网元接收该目标业务的需要同步的至少两个QoS流的QFI；其中，该至少两个目标数据包指的是包含有目标QFI的数据包，该目标QFI是该目标业务的需要同步的至少两个QoS流的QFI中的任一个。
上述方案，会话管理网元将目标业务的需要同步的至少两个QoS流的QFI发送至接入网设备，使得接入网设备后续可以根据目标业务的需要同步的至少两个QoS流的QFI，准 确识别出目标业务的需要同步的至少两个QoS流的数据包，从而有助于实现目标业务的QoS流的正确同步，可以提升用户体验。
一种可能的实现方法中，该至少两个目标数据包指的是包含有同步指示的数据包，该同步指示用于指示该数据包所属的QoS流是该目标业务的需要同步的QoS流。
上述方案，接入网设备可以根据数据包是否携带同步指示，准确识别出目标业务的需要同步的至少两个QoS流的数据包，从而有助于实现目标业务的QoS流的正确同步，可以提升用户体验。
一种可能的实现方法中，该接入网设备根据该至少两个目标数据包，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，具体包括：该接入网设备根据同步状态信息和该至少两个目标数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
上述方案，接入网设备根据同步状态信息和目标数据包中的帧号，可以实现数据包粒度的同步调度，有助于实现目标业务的需要同步的至少两个QoS流之间的精度同步，从而提升用户体验。
一种可能的实现方法中，该接入网设备根据同步状态信息和该至少两个目标数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，具体包括：该接入网设备根据同步状态信息和该至少两个目标数据包包含的帧号，确定该目标业务的需要同步的至少两个QoS流不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
上述方案，接入网设备判断目标业务的需要同步的至少两个QoS流是否满足同步精度，当不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，由于可以实现根据实际需要设定同步精度，因而该方法可以实现同步调度的灵活性。
一种可能的实现方法中，该接入网设备接收来自会话管理网元的该同步状态信息和该同步精度。
上述方案，由会话管理网元向接入网设备发送同步状态信息和同步精度，可以实现同步状态信息和同步精度的灵活配置。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
上述方案可以实现在多个终端设备的场景下的多个QoS流之间的同步调度，因而可以增强用户体验。
第二方面，本申请实施例提供一种同步调度方法，该方法可以由接入网设备或应用于接入网设备的模块(如芯片)来执行。以接入网设备执行该方法为例，该方法包括：接入网设备接收来自用户面网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；该接入网设备从该多个数据包中确定包含有相同接入网隧道端点标识的至少两个数据包，该至少两个数据包对应该目标业务的需要同步的至少两个QoS流，该接入网隧道端点标识用于标识目标隧道，该目标隧道是传输该目标业务的需要同步的至少两个QoS流的GTP-U隧道，该目标业务的需要同步的至少两个QoS流对应数据连接会话；该接入网设备根据该至少两个数据包，对该目标业务 的需要同步的至少两个QoS流的数据包进行同步调度。
上述方案，接入网设备根据该至少两个数据包对目标业务的需要同步的至少两个QoS流的数据包进行同步调度，使得该目标业务的多个QoS流之间保持合理的发送速度，使得该多个QoS流之间保持协调，提升了用户体验。并且，该方法是通过一步搜索的方法，从该目标业务的多个数据包中识别出该目标业务的需要同步的至少两个QoS流的至少两个数据包，因而可以提升同步速度，实现快速同步调度，进一步提升用户体验。
一种可能的实现方法中，该接入网设备接收来自用户面网元的目标业务的多个数据包之前，该接入网设备接收来自会话管理网元的关联标识和该目标业务的需要同步的至少两个QoS流的QFI，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话；该接入网设备根据该关联标识和该目标业务的需要同步的至少两个QoS流的QFI，为该目标业务的需要同步的至少两个QoS流确定该接入网隧道端点标识；该接入网设备通过该会话管理网元向该用户面网元发送该接入网隧道端点标识。
上述方案，通过关联标识将目标业务的需要同步的至少两个QoS流所属的多个数据连接会话进行关联，接入网设备根据关联标识获知该目标业务的需要同步的至少两个QoS流将在该多个数据连接会话中进行传输，而不会在其它数据连接会话中进行传输，并且接入网设备根据收到的该目标业务的需要同步的至少两个QoS流的QFI，获知该目标业务的需要同步的至少两个QoS流具体是该多个数据连接会话的中的哪些QoS流，接入网设备为这些QoS流确定接入网隧道端点标识，并向用户面网元发送该接入网隧道端点标识，该接入网隧道端点标识指示的GTP-U隧道专用于传输该目标业务的需要同步的至少两个QoS流，从而接入网设备从该GTP-U隧道接收的QoS流均是该目标业务的需要同步的至少两个QoS流，接入网设备不需要在其它GTP-U隧道内搜索该目标业务的需要同步的至少两个QoS流，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该接入网设备根据该至少两个数据包，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，具体包括：该接入网设备根据同步状态信息和该至少两个数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
上述方案，接入网设备根据同步状态信息和目标数据包中的帧号，可以实现数据包粒度的同步调度，有助于实现目标业务的需要同步的至少两个QoS流之间的精度同步，从而提升用户体验。
一种可能的实现方法中，该接入网设备根据同步状态信息和该至少两个数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，具体包括：该接入网设备根据同步状态信息和该至少两个数据包包含的帧号，确定该目标业务的需要同步的至少两个QoS流不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
上述方案，接入网设备判断目标业务的需要同步的至少两个QoS流是否满足同步精度，当不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，由于可以实现根据实际需要设定同步精度，因而该方法可以实现同步调度的灵活性。
一种可能的实现方法中，该接入网设备接收来自会话管理网元的该同步状态信息和该 同步精度。
上述方案，由会话管理网元向接入网设备发送同步状态信息和同步精度，可以实现同步状态信息和同步精度的灵活配置。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
上述方案可以实现在多个终端设备的场景下的多个QoS流之间的同步调度，因而可以增强用户体验。
第三方面，本申请实施例提供一种同步调度方法，该方法可以由接入网设备或应用于接入网设备的模块(如芯片)来执行。以接入网设备执行该方法为例，该方法包括：接入网设备接收来自用户面网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；该接入网设备根据多个接入网隧道端点标识之间的同步关系，从该多个数据包中确定至少两个数据包，该至少两个数据包中的每个数据包还包含该多个接入网隧道端点标识中的任一接入网隧道端点标识，该多个接入网隧道端点标识分别指示的GTP-U隧道均用于传输该目标业务的需要同步的至少两个QoS流；该接入网设备从该至少两个数据包确定至少两个目标数据包，该至少两个目标数据包对应该目标业务的需要同步的至少两个QoS流；该接入网设备根据该至少两个目标数据包，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
上述方案，接入网设备根据该至少两个目标数据包对目标业务的需要同步的至少两个QoS流的数据包进行同步调度，使得该目标业务的多个QoS流之间保持合理的发送速度，使得该多个QoS流之间保持协调，提升了用户体验。并且，该方法是先从目标业务的多个数据包中识别出可能包含目标业务的需要同步的至少两个QoS流的至少两个数据包，然后再从该至少两个数据包中识别出该目标业务的需要同步的至少两个QoS流的至少两个目标数据包，通过两步搜索的方法，缩小了该目标业务的需要同步的至少两个QoS流的数据包的搜索范围，避免从大量的QoS流中盲目搜索该目标业务的需要同步的至少两个QoS流的数据包，因而可以提升同步速度，实现快速同步调度，进一步提升用户体验。
一种可能的实现方法中，该接入网设备接收来自用户面网元的目标业务的多个数据包之前，该接入网设备接收来自会话管理网元的关联标识，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话；该接入网设备为该目标业务的需要同步的至少两个QoS流所属的数据连接会话确定该多个接入网隧道端点标识，该多个接入网隧道端点标识与该目标业务的需要同步的至少两个QoS流所属的数据连接会话一一对应；该接入网设备根据该关联标识，建立该同步关系。
上述方案，通过关联标识将目标业务的需要同步的至少两个QoS流所属的多个数据连接会话进行关联，接入网设备根据关联标识获知该目标业务的需要同步的至少两个QoS流将在该多个数据连接会话中进行传输，而不会在其它数据连接会话中进行传输，从而接入网设备可以为该多个数据连接会话分别分配接入网隧道端点标识，并建立这些接入网隧道端点标识之间的同步关系。接入网设备在收到数据包后，根据该同步关系以及数据包中包含的接入网隧道端点标识，判断该数据包可能是该目标业务的需要同步的至少两个QoS流，或者不是该目标业务的需要同步的至少两个QoS流，因而接入网设备可以逐步缩小目标业务的需要同步的至少两个QoS流的搜索范围，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该接入网设备接收来自用户面网元的目标业务的多个数据包之前，该接入网设备为该目标业务的需要同步的至少两个QoS流所属的数据连接会话确定该多个接入网隧道端点标识，该多个接入网隧道端点标识与该目标业务的需要同步的至少两个QoS流所属的数据连接会话一一对应；该接入网设备向会话管理网元发送该多个接入网隧道端点标识；该接入网设备从该会话管理网元接收该同步关系。
上述方案，会话管理网元确定目标业务的需要同步的至少两个QoS流所属的多个数据连接会话，建立该多个数据连接会话分别对应的接入网隧道端点标识之间的同步关系，并将该同步关系发送至接入网设备。接入网设备在收到数据包后，根据该同步关系以及数据包中包含的接入网隧道端点标识，判断该数据包可能是该目标业务的需要同步的至少两个QoS流中的数据包，或者不是该目标业务的需要同步的至少两个QoS流中的数据包，因而接入网设备可以逐步缩小目标业务的需要同步的至少两个QoS流的搜索范围，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该接入网设备接收来自该会话管理网元的该目标业务的需要同步的至少两个QoS流的QFI；其中，该至少两个目标数据包指的是包含有目标QFI的数据包，该目标QFI是该目标业务的需要同步的至少两个QoS流的QFI中的任一个。
上述方案，会话管理网元将目标业务的需要同步的至少两个QoS流的QFI发送至接入网设备，使得接入网设备后续可以根据目标业务的需要同步的至少两个QoS流的QFI，准确识别出目标业务的需要同步的至少两个QoS流的数据包，从而有助于实现目标业务的QoS流的正确同步，可以提升用户体验。
一种可能的实现方法中，该至少两个目标数据包指的是包含有同步指示的数据包，该同步指示用于指示该数据包所属的QoS流是该目标业务的需要同步的QoS流。
上述方案，接入网设备可以根据数据包是否携带同步指示，准确识别出目标业务的需要同步的至少两个QoS流的数据包，从而有助于实现目标业务的QoS流的正确同步，可以提升用户体验。
一种可能的实现方法中，该接入网设备根据该至少两个目标数据包，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，具体包括：该接入网设备根据同步状态信息和该至少两个目标数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
上述方案，接入网设备根据同步状态信息和目标数据包中的帧号，可以实现数据包粒度的同步调度，有助于实现目标业务的需要同步的至少两个QoS流之间的精度同步，从而提升用户体验。
一种可能的实现方法中，该接入网设备根据同步状态信息和该至少两个目标数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流的数据包进行同步调度，具体包括：该接入网设备根据同步状态信息和该至少两个目标数据包包含的帧号，确定该目标业务的需要同步的至少两个QoS流不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
上述方案，接入网设备判断目标业务的需要同步的至少两个QoS流是否满足同步精度，当不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度， 由于可以实现根据实际需要设定同步精度，因而该方法可以实现同步调度的灵活性。
一种可能的实现方法中，该接入网设备接收来自会话管理网元的该同步状态信息和该同步精度。
上述方案，由会话管理网元向接入网设备发送同步状态信息和同步精度，可以实现同步状态信息和同步精度的灵活配置。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
上述方案可以实现在多个终端设备的场景下的多个QoS流之间的同步调度，因而可以增强用户体验。
第四方面，本申请实施例提供一种同步调度方法，该方法可以由用户面网元或应用于用户面网元的模块(如芯片)来执行。以用户面网元执行该方法为例，该方法包括：用户面网元接收来自应用功能网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；该用户面网元在该多个数据包的至少两个数据包中添加标记信息和服务质量流标识QFI，该至少两个数据包的每个数据包中的QFI用于标识该数据包所属的服务质量QoS流，该标记信息对应该目标业务的需要同步的至少两个QoS流所属的多个协议数据单元数据连接会话；该用户面网元向接入网设备发送包含添加的标记信息和QFI的至少两个数据包的多个数据包。
上述方案，用户面网元在目标业务的多个数据包的至少两个数据包中添加标记信息，使得接入网设备根据该标记信息，获知携带该标记信息的数据包是目标业务的可能需要同步的至少两个QoS流的数据包，而未携带该标记信息的数据包不是该目标业务的需要同步的至少两个QoS流的数据包，从而缩小了该目标业务的需要同步的至少两个QoS流的数据包的搜索范围，避免接入网设备从大量的QoS流中盲目搜索该目标业务的需要同步的至少两个QoS流的数据包，因而可以提升同步速度，实现快速同步调度，进一步提升用户体验。
一种可能的实现方法中，该用户面网元接收来自该接入网设备的该标记信息。
上述方案，由接入网设备分配标记信息，可以保证标记信息的唯一性，有助于保证接入网设备根据标记信息搜索目标业务的需要同步的至少两个QoS流的数据包时的准确性和提升搜索速度，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该标记信息是由该接入网设备分配的组标识，该组标识对应该目标业务的需要同步的至少两个QoS流所属的数据连接会话。
上述方案，由接入网设备分配组标识作为标记信息，可以保证组标识的唯一性，有助于保证接入网设备根据组标识搜索目标业务的需要同步的至少两个QoS流的数据包时的准确性和提升搜索速度，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该标记信息是接入网隧道端点标识，该接入网隧道端点标识用于标识GTP-U隧道，该GTP-U隧道用于传输该目标业务的需要同步的至少两个QoS流所属的数据连接会话中的QoS流。
上述方案，接入网设备分配接入网隧道端点标识作为标记信息，该接入网隧道端点标识指示的GTP-U隧道用于传输该目标业务的需要同步的至少两个QoS流所属的多个数据连接会话中的QoS流，也即将目标业务的需要同步的至少两个QoS流通过同一个GTP-U隧道进行传输，从而接入网设备只需要在该GTP-U隧道内搜索该目标业务的需要同步的至少两个QoS流，不需要在其它GTP-U隧道内搜索该目标业务的需要同步的至少两个QoS 流，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该标记信息包括关联标识和网络设备的标识信息，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话，该网络设备是生成该关联标识的会话管理网元、策略控制网元或应用功能网元。
上述方案，将关联标识和网络设备的标识信息的组合作为标记信息，可以保证标记信息的唯一性，有助于保证接入网设备根据标记信息搜索目标业务的需要同步的至少两个QoS流的数据包时的准确性和提升搜索速度，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该用户面网元接收来自会话管理网元的该目标业务的需要同步的至少两个QoS流的QFI；该用户面网元向接入网设备发送包含添加的标记信息和QFI的至少两个数据包的多个数据包之前，该用户面网元根据该目标业务的需要同步的至少两个QoS流的QFI，在该至少两个数据包的至少两个目标数据包中添加同步指示，该至少两个目标数据包对应该目标业务的需要同步的至少两个QoS流，该同步指示用于指示该目标数据包所属的QoS流是该目标业务的需要同步的至少两个QoS流。
上述方案，接入网设备可以根据数据包是否携带同步指示，准确识别出目标业务的需要同步的至少两个QoS流的数据包，从而有助于实现目标业务的QoS流的正确同步，可以提升用户体验。
一种可能的实现方法中，该至少两个目标数据包均包含帧号，该帧号用于该目标业务的需要同步的至少两个QoS流的同步调度。
上述方案，接入网设备根据目标数据包中的帧号，可以实现数据包粒度的同步调度，有助于实现目标业务的需要同步的至少两个QoS流之间的精度同步，从而提升用户体验。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
上述方案可以实现在多个终端设备的场景下的多个QoS流之间的同步调度，因而可以增强用户体验。
第五方面，本申请实施例提供一种同步调度方法，该方法可以由会话管理网元或应用于会话管理网元的模块(如芯片)来执行。以会话管理网元执行该方法为例，该方法包括：会话管理网元生成关联标识，该关联标识关联目标业务的需要同步的至少两个QoS流所属的数据连接会话；该会话管理网元向接入网设备发送该关联标识，该关联标识用于该目标业务的需要同步的至少两个QoS流的同步调度。
上述方案，通过关联标识将目标业务的需要同步的至少两个QoS流所属的多个数据连接会话进行关联，接入网设备根据关联标识获知该目标业务的需要同步的至少两个QoS流将在该多个数据连接会话中进行传输，而不会在其它数据连接会话中进行传输，有助于接入网设备通过该关联标识缩小目标业务的需要同步的至少两个QoS流的搜索范围，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该会话管理网元向该接入网设备发送同步精度和同步状态信息，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
上述方案，会话管理网元向接入网设备发送同步精度和同步状态信息，从而接入网设备可以根据同步状态信息和同步精度，判断目标业务的需要同步的至少两个QoS流是否满 足同步精度，当不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，由于可以实现根据实际需要设定同步精度，因而该方法可以实现同步调度的灵活性。
一种可能的实现方法中，该会话管理网元接收来自策略控制网元的PCC规则，该PCC规则包括该目标业务的标识信息和该同步状态信息。
一种可能的实现方法中，该会话管理网元向用户面网元发送该目标业务的需要同步的至少两个QoS流的QFI。
第六方面，本申请实施例提供一种同步调度方法，该方法可以由会话管理网元或应用于会话管理网元的模块(如芯片)来执行。以会话管理网元执行该方法为例，该方法包括：会话管理网元确定目标业务的需要同步的至少两个QoS流所属的数据连接会话；该会话管理网元从接入网设备接收该目标业务的需要同步的至少两个QoS流所属的数据连接会话对应的多个接入网隧道端点标识，该目标业务的需要同步的至少两个QoS流所属的数据连接会话与该多个接入网隧道端点标识一一对应；该会话管理网元建立该多个接入网隧道端点标识之间的同步关系；该会话管理网元向接入网设备发送该同步关系，该同步关系用于该目标业务的需要同步的至少两个QoS流的同步调度。
上述方案，会话管理网元确定目标业务的需要同步的至少两个QoS流所属的多个数据连接会话，建立该多个数据连接会话分别对应的接入网隧道端点标识之间的同步关系，并将该同步关系发送至接入网设备。接入网设备在收到数据包后，根据该同步关系以及数据包中包含的接入网隧道端点标识，判断该数据包可能是该目标业务的需要同步的至少两个QoS流，或者不是该目标业务的需要同步的至少两个QoS流，因而接入网设备可以逐步缩小目标业务的需要同步的至少两个QoS流的搜索范围，进而有助于提升同步调度的速度，提升用户体验。
一种可能的实现方法中，该会话管理网元向该接入网设备发送同步精度和同步状态信息，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
上述方案，会话管理网元向接入网设备发送同步精度和同步状态信息，从而接入网设备可以根据同步状态信息和同步精度，判断目标业务的需要同步的至少两个QoS流是否满足同步精度，当不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，由于可以实现根据实际需要设定同步精度，因而该方法可以实现同步调度的灵活性。
一种可能的实现方法中，该会话管理网元接收来自策略控制网元的PCC规则，该PCC规则包括该目标业务的标识信息和该同步状态信息。
一种可能的实现方法中，该会话管理网元向用户面网元发送该目标业务的需要同步的至少两个QoS流的QFI。
第七方面，本申请实施例提供一种通信装置，该装置可以是接入网设备或应用于接入网设备中的模块(如芯片)。该装置具有实现上述第一方面至第三方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，本申请实施例提供一种通信装置，该装置可以是用户面网元或应用于用户 面网元中的模块(如芯片)。该装置具有实现上述第四方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，本申请实施例提供一种通信装置，该装置可以是会话管理网元或应用于会话管理网元中的模块(如芯片)。该装置具有实现上述第五方面或第六方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机指令，当该装置运行时，该处理器执行该存储器存储的计算机指令，以使该装置执行上述第一方面至第六方面中的任意实现方法。
第十一方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第六方面中的任意实现方法的各个步骤的单元或手段(means)。
第十二方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述第一方面至第六方面中的任意实现方法。该处理器包括一个或多个。
第十三方面，本申请实施例提供一种通信装置，包括与存储器耦合的处理器，该处理器用于调用所述存储器中存储的程序，以执行上述第一方面至第六方面中的任意实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器可以是一个或多个。
第十四方面，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在通信装置上运行时，使得上述第一方面至第六方面中的任意实现方法被执行。
第十五方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序或指令，当计算机程序或指令被通信装置运行时，使得上述第一方面至第六方面中的任意实现方法被执行。
第十六方面，本申请实施例还提供一种芯片系统，包括：处理器，用于执行上述第一方面至第六方面中的任意实现方法。
第十七方面，本申请实施例还提供一种通信系统，包括：用户面网元，和用于执行上述第一方面至第三方面的任意实现方法的接入网设备；该用户面网元，用于向该接入网设备发送目标业务的多个数据包。
一种可能的实现方法中，该通信系统还包括执行上述第五方面或第六方面的任意实现方法的会话管理网元。
第十八方面，本申请实施例还提供一种通信系统，包括：接入网设备，和用于执行上述第四方面的任意实现方法的用户面网元；该接入网设备，用于从该用户面网元接收多个数据包。
一种可能的实现方法中，该通信系统还包括执行上述第五方面或第六方面的任意实现方法的会话管理网元。
第十九方面，本申请实施例还提供一种通信系统，包括：用于执行上述第一方面至第三方面的任意实现方法的接入网设备，和用于执行上述第四方面的任意实现方法的用户面网元。
一种可能的实现方法中，该通信系统还包括执行上述第五方面或第六方面的任意实现 方法的会话管理网元。
附图说明
图1为基于服务化架构的5G网络架构示意图；
图2(a)为本申请实施例提供的一种同步调度方法的流程示意图；
图2(b)为本申请实施例提供的一种同步调度方法的流程示意图；
图2(c)为本申请实施例提供的一种同步调度方法的流程示意图；
图3(a)为本申请实施例提供的示例的示意图；
图3(b)为本申请实施例提供的GTP-U隧道分配的一个示例图；
图3(c)为本申请实施例提供的GTP-U隧道分配的另一个示例图；
图3(d)为本申请实施例提供的GTP-U隧道分配的另一个示例图；
图4为本申请实施例提供的一种同步调度方法流程示意图；
图5为本申请实施例提供的一种同步调度方法流程示意图；
图6为本申请实施例提供的一种同步调度方法流程示意图；
图7为本申请实施例提供的一种同步调度方法流程示意图；
图8为本申请实施例提供的一种同步调度方法流程示意图；
图9为本申请实施例提供的一种同步调度方法流程示意图；
图10为本申请实施例提供的一种通信装置示意图；
图11为本申请实施例提供的一种通信装置示意图。
具体实施方式
图1为基于服务化架构的5G网络架构示意图。图1所示的5G网络架构中可包括终端设备、接入网以及核心网。终端设备通过接入网和核心网接入数据网络(data network，DN)。
终端设备可以是用户设备(user equipment，UE)、移动台、移动终端等。终端设备可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、城市空中交通工具(如无人驾驶机、直升机等)、轮船、机器人、机械臂、智能家居设备等。以下以UE作为终端设备的一个示例进行说明，后续任意地方出现的UE也可以替换为终端设备或终端设备的其它示例。
接入网用于实现接入有关的功能，可以为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等确定不同质量的传输链路以传输用户数据。接入网在UE与核心网之间转发控制信号和用户数据。接入网可以包括接入网设备，接入网设备可以是为UE提供接入的设备，可以包括无线接入网(radio access network，RAN)设备和有线接入网设备。RAN设备，主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。RAN设备可以包括各种形式的基站，例如宏基站，微基站(也可称为小站)，中继站，接入点，气球站等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在5G系统中，称为RAN或者 下一代基站(next-generation Node basestation，gNB)，在长期演进(long term evolution，LTE)系统中，称为演进的节点B(evolved NodeB，eNB或eNodeB)。
接入网设备和UE可以是固定位置的，也可以是可移动的。接入网设备和UE可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对接入网设备和UE的应用场景不做限定。
核心网负责维护移动网络的签约数据，为UE提供会话管理、移动性管理、策略管理以及安全认证等功能。核心网中包括但不限于以下一个或多个网元：应用功能(application function，AF)网元、统一数据管理(unified data management，UDM)网元、统一数据库(unified data repository，UDR)网元、策略控制功能(policy control function，PCF)网元、会话管理功能(session management function，SMF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、网络存储功能(network repository function，NRF)网元、鉴权服务器功能(authentication server function，AUSF)网元、网络开放功能(network exposure function，NEF)网元、用户面功能(user plane function，UPF)网元。
AMF网元，主要负责移动网络中的移动性管理，例如用户位置更新、用户注册网络、用户切换等。
SMF网元，主要负责移动网络中的会话管理，例如会话建立、修改、释放。具体功能例如为用户分配互联网协议(internet protocol，IP)地址，选择提供报文转发功能的UPF等。
UPF网元，主要负责用户数据的转发和接收，可以从数据网络接收用户数据，通过接入网络设备传输给UE；还可以通过接入网设备从UE接收用户数据，转发至数据网络。
UDM网元，包含执行管理签约数据、用户接入授权等功能。
UDR网元，包含执行签约数据、策略数据、应用数据等类型数据的存取功能。
NEF网元，主要用于支持能力和事件的开放。
AF网元，传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP Multimedia Subsystem，IMS)语音呼叫业务。
PCF网元，主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。PCF网元可以向AMF网元、SMF网元提供策略，例如QoS策略、切片选择策略等。
NRF网元，可用于提供网元发现功能，基于其它网元的请求，提供网元类型对应的网元信息。NRF还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
AUSF网元，负责对UE进行鉴权，验证UE的合法性。
DN，其上可部署多种业务，可为UE提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为UE，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为UE，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
其中，AF网元、UDM网元、UDR网元、PCF网元、SMF网元、AMF网元、NRF网 元、AUSF网元、NEF网元、UPF网元，也可以分别简称为AF、UDM、UDR、PCF、SMF、AMF、NRF、AUSF、NEF、UPF。
图1中Nausf、Nnef、Nnrf、Namf、Npcf、Nsmf、Nudm、Nudr、Naf分别为上述AUSF、NEF、NRF、AMF、PCF、SMF、UDM、UDR、AF提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4以及N6为接口序列号，这些接口序列号的含义如下：
1)、N1：AMF与UE之间的接口，可以用于向UE传递非接入层(non access stratum，NAS)信令(如包括来自AMF的QoS规则)等。
2)、N2：AMF与接入网设备之间的接口，可以用于传递核心网侧至接入网设备的无线承载控制信息等。
3)、N3：接入网设备与UPF之间的接口，主要用于传递接入网设备与UPF间的上下行用户面数据。
4)、N4：SMF与UPF之间的接口，可以用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS规则、流量统计规则等的下发以及用户面的信息上报。
5)、N6：UPF与DN的接口，用于传递UPF与DN之间的上下行用户数据流。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。作为一种可能的实现方法，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
本申请实施例的方案可以应用于图1所示的5G网络架构，也可以应用于未来通信的网络架构，如第六代(the 6th generation，6G)网络中，本申请对此不限定。
本申请实施例中，数据连接会话包括协议数据单元(protocol data unit，PDU)会话、IP连接接入网络(IP Connectivity Access Network，IP-CAN)会话或其它形式的会话，为便于说明，本申请实施例后续均以PDU会话为例进行说明。
本申请实施例中，需要同步的QoS流，指的是需要同步的至少两个QoS流，也即两个或两个以上的QoS流之间需要同步。其中，两个或两个以上的QoS流之间需要同步，具体指的是两个或两个以上的QoS流的数据包或数据流之间需要同步。
本申请实施例中，对目标业务的需要同步的至少两个QoS流的数据包进行同步调度，也可以称为对目标业务的需要同步的至少两个QoS流的数据流进行同步调度，或者称为对目标业务的需要同步的至少两个QoS流进行同步调度，其具有相同的含义。
本申请实施例中，UPF与基站之间的用于传输QoS流的隧道，可以是GPRS隧道协议用户面(GRPS Tunnelling Protocol User Plane，GTP-U)，GPRS是通用无线分组业务(general packet radio service)的简称，或者也可以是其它隧道，本申请不做限定。为便于说明，以下以GTP-U隧道为例进行说明。
本申请实施例中，标记信息对应目标业务的需要同步的至少两个QoS流所属的数据连接会话，也可以表述为：标记信息用于关联目标业务的需要同步的至少两个QoS流所属的数据连接会话。组标识对应目标业务的需要同步的至少两个QoS流所属的数据连接会话，也可以表述为：组标识用于关联目标业务的需要同步的至少两个QoS流所属的数据连接会话。
图2(a)为本申请实施例提供的一种同步调度方法的流程示意图，该方法包括以下步骤：
步骤201a，UPF向基站发送目标业务的多个数据包，该多个数据包属于多个QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流。
例如，该多个数据包包括数据包1至数据包20，其中，数据包1至数据包5属于QoS流1，数据包5至数据包10属于QoS流2，数据包11至数据包20属于QoS流3。其中，QoS流2和QoS流3是该目标业务的需要同步的QoS流。
这里的目标业务比如可以是XR业务、VR业务或AR业务等，该目标业务的部分或全部数据流需要进行同步调度。
该多个数据包对应的该目标业务的数据流，可能是需要同步的数据流，也可能是不需要同步的数据流。该目标业务的数据流可以属于同一个会话，也可以属于不同的会话。例如，该目标业务包括音频数据流1、视频数据流2、感知数据流3以及感知数据流4，其中，音频数据流1、视频数据流2和感知数据流3之间需要同步，感知数据流4不需要同步，则该步骤201a中UPF向基站发送的该目标业务的多个数据包，可能是音频数据流1的数据包、视频数据流2的数据包、感知数据流3的数据包或感知数据流4的数据包。因此，该多个数据包中有的数据包需要同步，有的数据包不需要同步。
该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流。
其中，目标业务的数据流与目标业务的QoS流的关系是：目标业务的一个数据流可以被SMF映射为一个QoS流。因此上述4个数据流映射为4个QoS流。这里做统一说明，后面不再赘述。
步骤202a，基站从该多个数据包中确定包含有相同标记信息的至少两个数据包。
该标记信息对应该目标业务的需要同步的QoS流所属的多个PDU会话。其中，PDU会话与QoS流之间的关系是：一个PDU会话中可以承载一个或多个QoS流。
该实施例中，目标业务的需要同步的QoS流被映射至多个PDU会话中进行传输，该多个PDU会话可以称为承载有该目标业务的需要同步的QoS流的会话，当然该PDU会话中也可能会承载该目标业务的不需要同步的QoS流，或者承载其它业务的QoS流。上述标记信息将该多个PDU会话进行关联，其含义为：如果该目标业务的某个数据包中包含有该标记信息，表明该数据包所属的QoS流可能是该目标业务的需要同步的QoS流；如果该目标业务的某个数据包中不包含有该标记信息，表明该数据包所属的QoS流不是该目标业务的需要同步的QoS流。
其中，该目标业务的需要同步的QoS流对应一个或多个UE，也即该多个PDU会话是一个或多个UE的PDU会话。
下面结合具体示例进行说明。图3(a)为本申请实施例提供的示例的示意图。假设某个目标业务中的需要同步的数据流包括音频数据流1、视频数据流2和感知数据流3。SMF将音频数据流1映射为QoS流2，且承载在UE1的PDU会话1中进行传输，将视频数据流2映射为QoS流4，且承载在UE1的PDU会话2中进行传输，以及将感知数据流3映射为QoS流8，且承载在UE2的PDU会话4中进行传输。并且，该UE1的PDU会话1还承载有QoS流1和QoS流3，该UE1的PDU会话2还承载有QoS流5，该UE1还建立有PDU会话3，该PDU会话3承载有QoS流6和QoS流7。该UE2的PDU会话4还承载有QoS流9，该UE2还建立有PDU会话5，该PDU会话5承载有QoS流10和QoS流11。需要说明的是，该示例中各个PDU会话的编号、QoS流的编号不代表顺序，只是为了互相加以区分。其中，该UE1与UE2的关系是：该UE1和UE2可以接收或发送同一 个目标业务的不同数据流。比如在该示例中，UE1接收或发送目标业务的音频数据流1和视频数据流2，UE2接收或发送该目标业务的感知数据流3。
因此，该目标业务的各个数据流与UE的PDU会话、QoS流的关系如下所示：
UE1的PDU会话1中承载有QoS流1、QoS流2和QoS流3；
UE1的PDU会话2中承载有QoS流4和QoS流5；
UE1的PDU会话3中承载有QoS流6和QoS流7；
UE2的PDU会话4中承载有QoS流8和QoS流9；
UE2的PDU会话5中承载有QoS流10和QoS流11。
上述QoS流2、QoS流4和QoS流8是该目标业务的需要同步的QoS流，也称为该目标业务的需要同步的数据流所对应的QoS流，上述QoS流1、QoS流3、QoS流5至QoS流7，以及QoS流9至QoS流11是该目标业务的不需要同步的QoS流，或是其它业务的QoS流。
由于该目标业务的需要同步的数据流被映射到QoS流2、QoS流4和QoS流8，该QoS流2属于PDU会话1，该QoS流4属于PDU会话2，该QoS流8属于PDU会话4，因此标记信息对应目标业务的需要同步的QoS流所属PDU会话，比如PDU会话1、PDU会话2和PDU会话4，或者理解为由PDU会话1、PDU会话2和PDU会话4来传输该目标业务的需要同步的QoS流。需要说明的是，该PDU会话1、PDU会话2和PDU会话4不仅仅用于传输该目标业务的需要同步的QoS流，还可以用于传输该目标业务的不需要同步的QoS流或其它业务的QoS流，如上述QoS流1、QoS流3、QoS流5、QoS流9等。本申请实施例中，一个UE中可以使用一个或多个PDU会话承载目标业务的数据流，以图3(a)为例，UE1的两个PDU会话分别承载目标业务的音频数据流1和视频数据流2，UE2的一个PDU会话承载目标业务的感知数据流3，在其它示例中，也可以由UE1的一个PDU会话承载目标业务的音频数据流1和视频数据流2，UE2的一个PDU会话承载目标业务的感知数据流3。
基于该图3(a)的示例，则上述步骤201a中UPF向基站发送的该目标业务的多个数据包至少包括QoS流2的数据包、QoS流4的数据包以及QoS流8的数据包，还可能包括该目标业务的不需要同步的QoS流的数据包，例如QoS流1的数据包、QoS流3的数据包、QoS流6的数据包、QoS流7的数据包等等。该步骤202a中的包含有相同标记信息的至少两个数据包属于该多个数据包中的部分或全部数据包，该至少两个数据包包括PDU会话1、PDU会话2或PDU会话4中的QoS流的数据包，该至少两个数据包不包括其它PDU会话中的QoS流的数据包。
可以理解为，通过该步骤202a，基站从收到的多个数据包中筛选出的至少两个数据包是该目标业务的可能需要同步的QoS流的数据包，而该多个数据包中的除去该至少两个数据包之外的其它数据包是该目标业务的不需要同步的QoS流的数据包。因此通过该步骤202a，缩小了该目标业务的需要同步的QoS流的数据包的搜索范围，避免从大量的QoS流中盲目搜索该目标业务的需要同步的QoS流的数据包。
步骤203a，基站从包含有相同标记信息的至少两个数据包确定至少两个目标数据包，该至少两个目标数据包对应该目标业务的需要同步的QoS流。
也即，该至少两个目标数据包仅包括该目标业务的需要同步的QoS流的数据包，该至少两个数据包中除去该至少两个目标数据包之外的其它数据包不包括该目标业务的需要 同步的QoS流的数据包。以图3(a)为例，该至少两个数据包包括QoS流1至QoS流5的数据包以及QoS流8至QoS流9的数据包，该至少两个目标数据包包括QoS流2的数据包、QoS流4的数据包以及QoS流8的数据包，且该至少两个目标数据包不包括QoS流1的数据包、QoS流3的数据包、QoS流5的数据包和QoS流9的数据包。
通过该步骤203a，从至少两个数据包中筛选出该目标业务的需要同步的QoS流的数据包，以便于基站可以根据该目标业务的需要同步的QoS流的数据包执行同步调度。
步骤204a，基站根据该至少两个目标数据包，对目标业务的需要同步的QoS流的数据包进行同步调度。
一种实现方法中，基站根据同步状态信息和该至少两个目标数据包包含的帧号，对目标业务的需要同步的QoS流的数据包进行同步调度，也即该至少两个目标数据包中的每个数据包均包含一个帧号，则基站根据该每个数据包中的帧号，以及预先获取到的同步状态信息，对目标业务的需要同步的QoS流的数据包进行同步调度。其中，该同步状态信息用于指示在同步状态下该目标业务的需要同步的QoS流的数据包中的帧号之间的对应关系。基站根据同步状态信息和至少两个目标数据包包含的帧号，如果确定该目标业务的需要同步的QoS流不满足同步精度，表明各个QoS流未处于同步状态则基站调整目标业务的需要同步的QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的QoS流的数据包的帧号的偏差。比如，针对发送速度偏慢的QoS流的数据包，基站可以为其分配更多的资源以促进该QoS流的数据包的发送速度，或对该QoS流的不重要的数据包进行丢弃以促进该QoS流的数据包的发送速度。针对发送速度偏快的QoS流的数据包，基站可以减少为其分配的资源以降低该QoS流的数据包的发送速度，或者暂缓该QoS流的数据包的发送以降低该QoS流的数据包的发送速度。如果确定该目标业务的需要同步的QoS流满足同步精度，则基站可以不调整目标业务的需要同步的QoS流的数据包的发送速度，而是按照当前的发送速度进行数据包的发送。其中，该同步状态信息、同步精度可以是预配置在基站上的，也可以是从SMF接收到的，而SMF可以接收来自PCF的策略计费控制(Policy and Charging Control，PCC)规则，该PCC规则中包括目标业务的标识信息，以及包括同步状态信息和/或同步精度。
下面结合图3(a)的示例进行说明。假设同步精度为2帧，且音频数据流1的帧率、视频数据流2的帧率和感知数据流3的帧率分别为50帧/秒，60帧/秒，30帧/秒，则基站收到的同步状态信息为5:6:3，该同步状态信息表示在同步状态下，当音频数据流1的帧号为5的倍数时，视频数据流2和感知数据流3的帧号分别为6、3的相同倍数。在某个时间段内，基站收到的音频数据流1、视频数据流2和感知数据流3分别对应的QoS流的下行数据包中的帧号分别为：50、61、35。由于同步状态信息为5:6:3，因此当音频数据流1的下行数据包中的帧号为50时，如果这些数据流对应的QoS流保持同步状态，则视频数据流2的下行数据包中的帧号应该是58至62中的任一个，感知数据流3的下行数据包中的帧号应该是28至32中的任一个。因此，该示例中音频数据流1与视频数据流2之间是同步的，但感知数据流3没有与音频数据流1和视频数据流2保持同步，因此可以通过降低该感知数据流3的发送速度，以使得该3个数据流对应的QoS流保持同步。
上述方案，基站根据该至少两个目标数据包对目标业务的需要同步的QoS流的数据包进行同步调度，使得该目标业务的多个QoS流的数据包之间保持合理的发送速度，使得该多个QoS流之间保持协调，提升了用户体验。以VR场景为例，当VR业务的音频数据流、 视频数据流和感知数据流通过多个QoS流发送至一个或多个UE(如手柄、VR眼镜、VR指尖装置)时，基站对该音频数据流、视频数据流和感知数据流所对应的QoS流的数据包进行同步调度之后，可以保证这些QoS流以合适的速度发送至一个或多个UE，从而用户可以感受到视频、音频和触觉之间的同步，提升了用户体验。反之，如果基站没有做同步调度处理，用户将会感受到视频、音频和触觉之间的不同步，这可能会导致用户可能产生眩晕，降低用户体验。
下面对上述图2(a)的实施例，给出多种不同的具体实现方法。
方法一，上述标记信息是接入网隧道端点标识(access network Tunnel Endpoint Identifier，AN TEID)，该AN TEID用于标识GTP-U隧道，该GTP-U隧道用于传输该目标业务的需要同步的QoS流所属的多个PDU会话中的QoS流。其中，GPRS是通用无线分组业务(general packet radio service)的简称。
该方法一适用于目标业务的需要同步的QoS流所属的多个PDU会话对应相同SMF的场景。
该分配AN TEID的方法，将同一业务中需要进行同步的QoS流分配到同一个GTP-U隧道中，从而基站只需要对该条GTP-U隧道中的数据包进行检测，识别出需要进行同步的数据包，不需要在其它GTP-U隧道中去识别需要同步的数据包，有助于提升同步的准确性和效率。一种实现方法中，SMF/PCF/AF生成关联标识，然后由SMF向基站发送该关联标识，该关联标识关联该目标业务的需要同步的QoS流所属的多个PDU会话，基站根据该关联标识为该目标业务的需要同步的QoS流所属的多个PDU会话确定标记信息，即AN TEID，然后基站通过SMF向UPF发送该AN TEID。
对于其它PDU会话，基站可以根据现有方法为每个PDU会话正常分配一个AN TEID，并绑定该AN TEID对应的QFI。
图3(b)为本申请实施例提供的GTP-U隧道分配的一个示例图。该示例是在图3(a)的示例基础上进行的GTP-U隧道分配。比如SMF为目标业务的需要同步的QoS流所属的多个PDU会话分配关联标识，并通过该多个PDU会话的各个PDU会话，向基站发送相同的关联标识，其中，该多个PDU会话对应相同的该SMF。基站收到该多个PDU会话对应的相同的该关联标识，则根据关联标识，确定该多个PDU会话用于传输目标业务的需要同步的QoS流，从而基站为该多个PDU会话分配同一个AN TEID，该AN TEID标识了一个GTP-U隧道。参考图3(b)，基站根据关联标识，为PDU会话1、PDU会话2和PDU会话4分配了相同的AN TEID1，该AN TEID1用于标识GTP-U隧道1。并且基站按照现有方法，为其它每个PDU会话分配一个AN TEID，即为PDU会话3分配AN TEID2，该AN TEID2用于标识GTP-U隧道2，以及为PDU会话5分配AN TEID3，该AN TEID3用于标识GTP-U隧道3。其中，每个GTP-U隧道内的不同QoS流的QFI不同，不同GTP-U隧道内的QoS流的QFI可以相同也可以不同，且QoS流的QFI均是由SMF分配的。其中，该示例中的AN TEID1即为上述标记信息。
基站在分配AN TEID之后，通过SMF将分配的AN TEID发送给UPF，从而UPF根据AN TEID在相应的GTP-U隧道中发送QoS流。比如，UPF在GTP-U隧道1中向基站发送QoS流1至QoS流5以及QoS流8和QoS流9，即在QoS流1至QoS流5以及QoS流8和QoS流9的数据包的GTP-U包头中添加AN TEID1。UPF在GTP-U隧道2中向基站发送QoS流6和QoS流7，即在QoS流6和QoS流7的数据包的GTP-U包头中添加 AN TEID2。UPF在GTP-U隧道3中向基站发送QoS流10和QoS流11，即在QoS流10和QoS流11的数据包的GTP-U包头中添加AN TEID3。并且，UPF还在各个QoS流的数据包的GTP-U包头中添加相应的QFI，具体参考图3(b)。
基于该示例，则上述步骤202a具体为：基站从收到的多个数据包中识别出携带AN TEID1的至少两个数据包，该AN TEID1即为标记信息。
方法二，上述标记信息是由基站分配的组标识，组标识对应目标业务的需要同步的QoS流所属的多个PDU会话。
该方法二适用于目标业务的需要同步的QoS流所属的多个PDU会话对应不同SMF/PCF的场景，当然也适用于对应相同SMF/PCF的场景。
比如SMF/PCF/AF生成关联标识，比如，目标业务的需要同步的QoS流所属的多个PDU会话对应相同的SMF，但对应不同的PCF，则由SMF或AF生成关联标识，再比如，目标业务的需要同步的QoS流所属的多个PDU会话对应相同的PCF，但对应不同的SMF，则由PCF或AF生成关联标识，再比如，目标业务的需要同步的QoS流所属的多个PDU会话对应相同的SMF和相同的PCF，则由SMF、PCF或AF生成关联标识，再比如，目标业务的需要同步的QoS流所属的多个PDU会话对应的SMF和PCF均不同，则由AF生成关联标识。
SMF/PCF/AF生成关联标识之后，由SMF向基站发送该关联标识，该关联标识关联该目标业务的需要同步的QoS流所属的多个PDU会话，基站根据该关联标识为该目标业务的需要同步的QoS流所属的多个PDU会话确定标记信息，即组标识，然后基站通过SMF向UPF发送该组标识。其中，基站生成的组标识可以与关联标识相同，也可以不同。
之所以需要基站根据关联标识重新生成组标识，而不是直接使用SMF发送给基站的关联标识，是因为：可能有多个SMF/PCF/AF同时执行不同业务的同步调度，且SMF/PCF/AF可能为不同的业务对应的PDU会话分配了相同的关联标识，即该关联标识在基站侧不唯一，比如SMF1为业务1的需要同步的QoS流所属的PDU会话分配关联标识1，SMF2为业务2的需要同步的QoS流所属的PDU会话也分配关联标识1，如果基站直接使用关联标识1，则将导致基站后续根据关联标识1识别业务1的需要同步的QoS流时，不仅在业务1的PDU会话中识别需要同步的QoS流，还会在业务2的PDU会话中识别需要同步的QoS流，但实际上业务2的PDU会话中并没有需要与业务1的QoS流进行同步的QoS流，造成资源浪费，同时还可能造成错误识别，对于业务2的QoS流的同步也是如此。
该方法二中，基站不沿用SMF/PCF/AF分配的关联标识，而是重新分配一个组标识，可以保证基站上的组标识的唯一性，后续基站根据该唯一的组标识进行同步调度。在上述示例中，基站为来自SMF1的对应关联标识1的PDU会话分配一个组标识，以及为来自SMF2的对应关联标识1的PDU会话分配另一个组标识，因此业务1的QoS流对应的组标识与业务2的QoS流对应的组标识不同，相互之间不会混淆。
基于该方法二，基站可以根据现有方法为每个PDU会话正常分配一个AN TEID，并绑定该AN TEID对应的QFI。图3(c)为本申请实施例提供的GTP-U隧道分配的另一个示例图。该示例是在图3(a)的示例基础上进行的GTP-U隧道分配。比如基站按照现有方法，为每个PDU会话分配一个AN TEID，即为PDU会话1分配AN TEID1，该AN TEID1用于标识GTP-U隧道1，为PDU会话2分配AN TEID2，该AN TEID2用于标识GTP-U隧 道2，为PDU会话3分配AN TEID3，该AN TEID3用于标识GTP-U隧道3，为PDU会话4分配AN TEID4，该AN TEID4用于标识GTP-U隧道4，为PDU会话5分配AN TEID5，该AN TEID5用于标识GTP-U隧道5。其中，每个GTP-U隧道内的不同QoS流的QFI不同，不同GTP-U隧道内的QoS流的QFI可以相同也可以不同，且QoS流的QFI均是由SMF分配的。
基站在分配AN TEID以及生成组标识之后，通过SMF将AN TEID以及组标识发送给UPF，从而UPF根据AN TEID在相应的GTP-U隧道中发送QoS流，并且UPF还会在PDU会话1、PDU会话2和PDU会话4内的各个QoS流的数据包的GTP-U包头中添加组标识。UPF在GTP-U隧道1中向基站发送QoS流1至QoS流3，即在QoS流1至QoS流3的数据包的GTP-U包头中添加AN TEID1和组标识。UPF在GTP-U隧道2中向基站发送QoS流4和QoS流5，即在QoS流4和QoS流5的数据包的GTP-U包头中添加AN TEID2和组标识。UPF在GTP-U隧道3中向基站发送QoS流6和QoS流7，即在QoS流6和QoS流7的数据包的GTP-U包头中添加AN TEID3。UPF在GTP-U隧道4中向基站发送QoS流8和QoS流9，即在QoS流8和QoS流9的数据包的GTP-U包头中添加AN TEID4和组标识。UPF在GTP-U隧道5中向基站发送QoS流10和QoS流11，即在QoS流10和QoS流11的数据包的GTP-U包头中添加AN TEID5。并且，UPF还在各个QoS流的数据包的GTP-U包头中添加相应的QFI，具体参考图3(c)。
基于该示例，则上述步骤202a具体为：基站从收到的多个数据包中识别出携带相同组标识的至少两个数据包，该组标识即为标记信息。
方法三，上述标记信息包括关联标识和网络设备的标识信息，该网络设备是生成关联标识的SMF、PCF或AF。
该方法三适用于目标业务的需要同步的QoS流所属的多个PDU会话对应不同SMF/PCF的场景，当然也适用于对应相同SMF/PCF的场景。
比如SMF/PCF/AF生成关联标识，比如，目标业务的需要同步的QoS流所属的多个PDU会话对应相同的SMF，但对应不同的PCF，则由SMF或AF生成关联标识，再比如，目标业务的需要同步的QoS流所属的多个PDU会话对应相同的PCF，但对应不同的SMF，则由PCF或AF生成关联标识，再比如，目标业务的需要同步的QoS流所属的多个PDU会话对应相同的SMF和相同的PCF，则由SMF、PCF或AF生成关联标识，再比如，目标业务的需要同步的QoS流所属的多个PDU会话对应的SMF和PCF均不同，则由AF生成关联标识。
SMF/PCF/AF生成关联标识之后，由SMF向UPF和基站发送关联标识以及生成该关联标识的网络设备的标识信息，该关联标识关联该目标业务的需要同步的QoS流所属的多个PDU会话，该网络设备为SMF、PCF或AF。
其中，使用关联标识和网络设备的标识信息的组合作为标记信息，而不是仅使用关联标识作为标记信息，其原因与上述方法二中基站重新分配组标识的原因类似，均是为了保证标记信息的唯一性。不同SMF/PCF/AF可能为不同业务的QoS流的同步分配了相同关联标识，因此需要再增加SMF/PCF/AF的标识信息，以使得标记信息在基站侧保持唯一。
基于该方法三，基站可以根据现有方法为每个PDU会话正常分配一个AN TEID，并绑定该AN TEID对应的QFI。上述图3(c)所示的GTP-U隧道分配示例也适用于该方法三。
UPF一方面可以从基站收到AN TEID，以及还从SMF收到标记信息，该标记信息包 括关联标识和SMF/PCF/AF的标识信息，从而UPF根据AN TEID在相应的GTP-U隧道中发送QoS流，并且UPF还会在PDU会话1、PDU会话2和PDU会话4内的各个QoS流的数据包的GTP-U包头中添加关联标识和SMF/PCF/AF的标识信息。UPF在GTP-U隧道1中向基站发送QoS流1至QoS流3，即在QoS流1至QoS流3的数据包的GTP-U包头中添加AN TEID1、关联标识和SMF/PCF/AF的标识信息。UPF在GTP-U隧道2中向基站发送QoS流4和QoS流5，即在QoS流4和QoS流5的数据包的GTP-U包头中添加AN TEID2、关联标识和SMF/PCF/AF的标识信息。UPF在GTP-U隧道3中向基站发送QoS流6和QoS流7，即在QoS流6和QoS流7的数据包的GTP-U包头中添加AN TEID3。UPF在GTP-U隧道4中向基站发送QoS流8和QoS流9，即在QoS流8和QoS流9的数据包的GTP-U包头中添加AN TEID4、关联标识和SMF/PCF/AF的标识信息。UPF在GTP-U隧道5中向基站发送QoS流10和QoS流11，即在QoS流10和QoS流11的数据包的GTP-U包头中添加AN TEID5。并且，UPF还在各个QoS流的数据包的GTP-U包头中添加相应的QFI，具体参考图3(c)。
基于该示例，则上述步骤202a具体为：基站从收到的多个数据包中识别出携带相同关联标识及相同SMF/PCF/AF的标识信息的至少两个数据包，该关联标识和SMF/PCF/AF的标识信息的组合即为标记信息。
基于上述方法一、方法二或方法三，在一种实现方法中，SMF还可以向基站发送该目标业务的需要同步的QoS流的QFI。以图3(b)的示例为例，SMF向基站发送的该目标业务的需要同步的QoS流的QFI包括QoS流2的QFI(即QFI2)、QoS流4的QFI(即QFI4)和QoS流8的QFI(即QFI6)，从而基站获知该目标业务的需要同步的QoS流的QFI。以图3(c)的示例为例，SMF向基站发送的该目标业务的需要同步的QoS流的QFI包括QoS流2的QFI(即QFI2)、QoS流4的QFI(即QFI1)和QoS流8的QFI(即QFI1)，从而基站获知该目标业务的需要同步的QoS流的QFI。基于该实现方法，上述步骤203a具体是：基站从至少两个数据包中确定包含有目标QFI的数据包，该包含有目标QFI的数据包即为前述至少两个目标数据包，该目标QFI是目标业务的需要同步的QoS流的QFI中的任一个。以图3(b)或图3(c)为例，通过上述步骤202a，基站从QoS流1至QoS流11中获取QoS流1至QoS流5以及QoS流8至QoS流9的数据包，并通过上述步骤203a，基站从QoS流1至QoS流5以及QoS流8至QoS流9的数据包中获取QoS流2、QoS流4和QoS流8的数据包，然后基站根据QoS流2、QoS流4和QoS流8的数据包对目标业务的需要同步的QoS流的数据包进行同步调度。
基于上述方法一、方法二或方法三，在另一种实现方法中，SMF还可以向UPF发送该目标业务的需要同步的QoS流的QFI。以图3(b)的示例为例，SMF向UPF发送的该目标业务的需要同步的QoS流的QFI包括QoS流2的QFI(即QFI2)、QoS流4的QFI(即QFI4)和QoS流8的QFI(即QFI6)，从而UPF获知该目标业务的需要同步的QoS流的QFI。以图3(c)的示例为例，SMF向UPF发送的该目标业务的需要同步的QoS流的QFI包括QoS流2的QFI(即QFI2)、QoS流4的QFI(即QFI1)和QoS流8的QFI(即QFI1)，从而UPF获知该目标业务的需要同步的QoS流的QFI。基于该实现方法，UPF后续在QoS流2、QoS流4和QoS流8的数据包的GTP-U包头中还添加同步指示，该同步指示用于指示该数据包所属的QoS流是目标业务的需要同步的QoS流。因此，上述步骤203a具体是：基站从至少两个数据包中确定包含有同步指示的数据包，该包含有同步指示的数据包 即为前述至少两个目标数据包。以图3(b)或图3(c)为例，通过上述步骤202a，基站从QoS流1至QoS流11中获取QoS流1至QoS流5以及QoS流8至QoS流9的数据包，并通过上述步骤203a，基站从QoS流1至QoS流5以及QoS流8至QoS流9的数据包中获取QoS流2、QoS流4和QoS流8的数据包，然后基站根据QoS流2、QoS流4和QoS流8的数据包对目标业务的需要同步的QoS流的数据包进行同步调度。
图2(b)为本申请实施例提供的一种同步调度方法的流程示意图，该方法包括以下步骤：
步骤201b，UPF向基站发送目标业务的多个数据包，该多个数据包属于多个QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流。
该步骤201b同前述步骤201a，可参考前述描述。
步骤202b，基站从多个数据包中确定包含有相同接入网隧道端点标识(AN TEID)的至少两个数据包。
该至少两个数据包对应目标业务的需要同步的QoS流，该AN TEID用于标识目标隧道，该目标隧道是传输该目标业务的需要同步的QoS流的数据流的隧道(比如GTP-U隧道)，该目标业务的需要同步的QoS流对应一个或多个PDU会话。该至少两个数据包为该目标业务的需要同步的QoS流的数据包。以图3(a)为例，该至少两个数据包为QoS流2的数据包、QoS流4的数据包以及QoS流8的数据包。
该实施例中，目标业务的需要同步的QoS流被映射至多个PDU会话中进行传输，该多个PDU会话可以称为承载有该目标业务的需要同步的QoS流的会话，当然该PDU会话中也可能会承载该目标业务的不需要同步的QoS流，或者承载其它业务的QoS流。其中，该目标业务的需要同步的QoS流对应一个或多个UE，也即该多个PDU会话是一个或多个UE的PDU会话。
通过该步骤202b，基站从多个数据包中筛选出该目标业务的需要同步的QoS流的数据包，以便于基站可以根据该目标业务的需要同步的QoS流的数据包执行同步调度。
步骤203b，基站根据至少两个数据包，对目标业务的需要同步的QoS流的数据包进行同步调度。
该步骤203b的实现与前述步骤204a的实现类似，可参考前述描述。
上述方案，将目标业务的需要同步的QoS流的数据包通过一个专用的GTP-U隧道进行传输，使得基站可以快速便捷地识别出需要同步的QoS流的数据包，然后基站对目标业务的需要同步的QoS流的数据包进行同步调度，使得该目标业务的多个QoS流的数据包之间保持合理的发送速度，使得该多个QoS流之间保持协调，提升了用户体验。以VR场景为例，当VR业务的音频数据流、视频数据流和感知数据流通过多个QoS流发送至一个或多个UE(如手柄、VR眼镜、VR指尖装置)时，基站对该音频数据流、视频数据流和感知数据流所对应的QoS流的数据包进行同步调度之后，可以保证这些QoS流以合适的速度发送至一个或多个UE，从而用户可以感受到视频、音频和触觉之间的同步，提升了用户体验。反之，如果基站没有做同步调度处理，用户将会感受到视频、音频和触觉之间的不同步，这可能会导致用户可能产生眩晕，降低用户体验。
上述图2(b)的实施例中，基站将目标业务中需要进行同步的QoS流分配到同一个GTP-U隧道中，该GTP-U隧道中的QoS流均是需要同步的QoS流，从而基站可以快速确定该目标业务的需要同步的QoS流，有助于提升同步的准确性和效率。一种实现方法中， SMF/PCF/AF生成关联标识，然后由SMF向基站发送该关联标识，该关联标识关联该目标业务的需要同步的QoS流所属的多个PDU会话，SMF还向基站发送该目标业务的需要同步的QoS流的QFI，基站根据该关联标识识别出该目标业务的需要同步的QoS流所属的多个PDU会话，并从该多个PDU会话中获取该目标业务的需要同步的QoS流的QFI，进而基站为这些QoS流分配相同的AN TEID，该AN TEID标识的GTP-U隧道专用于传输该目标业务的需要同步的QoS流。基站通过SMF向UPF发送该AN TEID。
针对其它PDU会话，以及该关联标识对应的PDU会话中的除去该目标业务的需要同步的QoS流之外的其它QoS流，基站可以根据现有方法为正常分配AN TEID，并绑定该AN TEID对应的QFI。
图3(d)为本申请实施例提供的GTP-U隧道分配的另一个示例图。该示例是在图3(a)的示例基础上进行的GTP-U隧道分配。SMF为目标业务的需要同步的QoS流所属的多个PDU会话分配关联标识，并通过该多个PDU会话的各个PDU会话，向基站发送相同的关联标识。该多个PDU会话对应相同的该SMF。以及，SMF还向基站发送该目标业务的需要同步的QoS流的QFI。基站收到该多个PDU会话对应的相同的该关联标识，则确定用于传输目标业务的需要同步的QoS流的多个PDU会话，然后基站从该多个PDU会话中获取该目标业务的需要同步的QoS流的QFI，然后基站为该目标业务的需要同步的QoS流分配同一个AN TEID，该AN TEID标识了一个GTP-U隧道。参考图3(d)，基站根据关联标识，为QoS流2、QoS流4和QoS流8分配了相同的AN TEID1，该AN TEID1用于标识GTP-U隧道1。并且基站按照现有方法，为PDU会话1、PDU会话2、PDU会话4中的其它QoS流，以及其它每个PDU会话分别分配一个AN TEID，即为PDU会话1中的QoS流1和QoS流3分配AN TEID2，该AN TEID2用于标识GTP-U隧道2，为PDU会话2中的QoS流5分配AN TEID3，该AN TEID3用于标识GTP-U隧道3，为PDU会话3分配AN TEID4，该AN TEID4用于标识GTP-U隧道4，为PDU会话4中的QoS流9分配AN TEID5，该AN TEID5用于标识GTP-U隧道5，以及为PDU会话5分配AN TEID6，该AN TEID6用于标识GTP-U隧道6。其中，每个GTP-U隧道内的不同QoS流的QFI不同，不同GTP-U隧道内的QoS流的QFI可以相同也可以不同，且QoS流的QFI均是由SMF分配的。其中，该示例中的AN TEID1即为上述标记信息。
基站在分配AN TEID之后，通过SMF将分配的AN TEID发送给UPF，从而UPF根据AN TEID在相应的GTP-U隧道中发送QoS流。UPF在GTP-U隧道1中向基站发送QoS流2、QoS流4和QoS流8，即在QoS流2、QoS流4和QoS流8的数据包的GTP-U包头中添加AN TEID1。UPF在GTP-U隧道2中向基站发送QoS流1和QoS流3，即在QoS流1和QoS流3的数据包的GTP-U包头中添加AN TEID2。UPF在GTP-U隧道3中向基站发送QoS流5，即在QoS流5的数据包的GTP-U包头中添加AN TEID3。UPF在GTP-U隧道4中向基站发送QoS流6和QoS流7，即在QoS流6和QoS流7的数据包的GTP-U包头中添加AN TEID4。UPF在GTP-U隧道5中向基站发送QoS流9，即在QoS流9的数据包的GTP-U包头中添加AN TEID5。UPF在GTP-U隧道6中向基站发送QoS流10和QoS流11，即在QoS流10和QoS流11的数据包的GTP-U包头中添加AN TEID6。并且，UPF还在各个QoS流的数据包的GTP-U包头中添加相应的QFI，具体参考图3(d)。
基于该示例，则上述步骤202b具体为：基站从收到的多个数据包中识别出携带AN TEID1的至少两个数据包，该AN TEID1用于表示目标隧道，该目标隧道是专用于传输该 目标业务的需要同步的QoS流的GTP-U隧道。
图2(c)为本申请实施例提供的一种同步调度方法的流程示意图，该方法包括以下步骤：
步骤201c，UPF向基站发送目标业务的多个数据包，该多个数据包属于多个QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流。
该步骤201c同前述步骤201a，可参考前述描述。
步骤202c，基站根据多个接入网隧道端点标识之间的同步关系，从多个数据包中确定至少两个数据包。
该至少两个数据包中的每个数据包包含多个接入网隧道端点标识中的任一接入网隧道端点标识，该多个接入网隧道端点标识分别指示的GTP-U隧道均用于传输目标业务的需要同步的QoS流。
步骤203c，基站从至少两个数据包确定至少两个目标数据包，至少两个目标数据包对应目标业务的需要同步的QoS流。
也即，该至少两个目标数据包仅包括该目标业务的需要同步的QoS流的数据包，该至少两个数据包中除去该至少两个目标数据包之外的其它数据包不包括该目标业务的需要同步的QoS流的数据包。以图3(a)为例，该至少两个数据包包括QoS流1至QoS流5的数据包以及QoS流8至QoS流9的数据包，该至少两个目标数据包包括QoS流2的数据包、QoS流4的数据包以及QoS流8的数据包，且该至少两个目标数据包不包括QoS流1的数据包、QoS流3的数据包、QoS流5和QoS流9的数据包。
通过该步骤203c，从至少两个数据包中筛选出该目标业务的需要同步的QoS流的数据包，以便于基站可以根据该目标业务的需要同步的QoS流的数据包执行同步调度。
步骤204c，基站根据至少两个目标数据包，对目标业务的需要同步的QoS流的数据包进行同步调度。
该步骤204c的实现与前述步骤204a的实现类似，可参考前述描述。
上述方案，基站根据该至少两个目标数据包对目标业务的需要同步的QoS流的数据包进行同步调度，使得该目标业务的多个QoS流的数据包之间保持合理的发送速度，使得该多个QoS流之间保持协调，提升了用户体验。以VR场景为例，当VR业务的音频数据流、视频数据流和感知数据流通过多个QoS流发送至一个或多个UE(如手柄、VR眼镜、VR指尖装置)时，基站对该音频数据流、视频数据流和感知数据流所对应的QoS流的数据包进行同步调度之后，可以保证这些QoS流以合适的速度发送至一个或多个UE，从而用户可以感受到视频、音频和触觉之间的同步，提升了用户体验。反之，如果基站没有做同步调度处理，用户将会感受到视频、音频和触觉之间的不同步，这可能会导致用户可能产生眩晕，降低用户体验。
一种实现方法中，基于上述图2(c)的实施例，SMF/PCF/AF生成关联标识，然后由SMF向基站发送该关联标识，该关联标识关联该目标业务的需要同步的QoS流所属的多个PDU会话，然后基站根据该关联标识识别出该目标业务的需要同步的QoS流所属的多个PDU会话，基站按照现有方法为每个PDU会话分配一个AN TEID，基站通过SMF向UPF发送该AN TEID。并且，基站还记录该关联标识对应的PDU会话的AN TEID之间的对应关系。以图3(a)的示例为例，基站则是按照图3(c)所示的方法为每个PDU会话分配一个AN TEID。基站根据关联标识获知PDU会话1、PDU会话2和PDU会话4用于传输目标业务 的需要同步的QoS流，且基站为PDU会话1、PDU会话2和PDU会话4分别分配了AN TEID1、AN TEID2和AN TEID4，则基站记录AN TEID1、AN TEID2和AN TEID4之间的同步关系。可以理解为，基站确定目标业务的需要同步的QoS流将会在AN TEID1、AN TEID2和AN TEID4所指示的GTP-U隧道中传输，而不会再其它GTP-U隧道中传输。
另一种实现方法中，基于上述图2(c)的实施例，SMF根据该目标业务的需要同步的QoS流所属的多个PDU会话，以及基站为该多个PDU会话分别分配的AN TEID，建立AN TEID之间的同步关系，并将同步关系发送至基站。其中，基站是按照现有方法为每个PDU会话分配一个AN TEID。以图3(a)的示例为例，基站则是按照图3(c)所示的方法为每个PDU会话分配一个AN TEID。SMF确定PDU会话1、PDU会话2和PDU会话4用于传输目标业务的需要同步的QoS流，且SMF从基站收到为PDU会话1、PDU会话2和PDU会话4分别分配的AN TEID1、AN TEID2和AN TEID4，则SMF记录AN TEID1、AN TEID2和AN TEID4之间的同步关系，然后向基站发送该同步关系，从而基站根据该同步关系，确定目标业务的需要同步的QoS流将会在AN TEID1、AN TEID2和AN TEID4所指示的GTP-U隧道中传输，而不会再其它GTP-U隧道中传输。
基于该示例，则上述步骤202c具体为：基站根据AN TEID1、AN TEID2和AN TEID4之间的同步关系，从收到的多个数据包中识别出携带AN TEID1、AN TEID2或AN TEID4的至少两个数据包，该至少两个数据包可能是该目标业务的需要同步的QoS流的数据包。
在一种实现方法中，SMF还可以向基站发送该目标业务的需要同步的QoS流的QFI。以图3(c)的示例为例，SMF向基站发送的该目标业务的需要同步的QoS流的QFI包括QoS流2的QFI(即QFI2)、QoS流4的QFI(即QFI1)和QoS流8的QFI(即QFI1)，从而基站获知该目标业务的需要同步的QoS流的QFI。基于该实现方法，上述步骤203c具体是：基站从至少两个数据包中确定包含有目标QFI的数据包，该包含有目标QFI的数据包即为前述至少两个目标数据包，该目标QFI是目标业务的需要同步的QoS流的QFI中的任一个。以图3(c)为例，通过上述步骤202c，基站从QoS流1至QoS流11中获取QoS流1至QoS流5以及QoS流8至QoS流9的数据包，并通过上述步骤203c，基站从QoS流1至QoS流5以及QoS流8至QoS流9的数据包中获取QoS流2、QoS流4和QoS流8的数据包，然后基站根据QoS流2、QoS流4和QoS流8的数据包对目标业务的需要同步的QoS流的数据包进行同步调度。
在另一种实现方法中，SMF还可以向UPF发送该目标业务的需要同步的QoS流的QFI。以图3(c)的示例为例，SMF向UPF发送的该目标业务的需要同步的QoS流的QFI包括QoS流2的QFI(即QFI2)、QoS流4的QFI(即QFI1)和QoS流8的QFI(即QFI1)，从而UPF获知该目标业务的需要同步的QoS流的QFI。基于该实现方法，UPF后续在QoS流2、QoS流4和QoS流8的数据包的GTP-U包头中还添加同步指示，该同步指示用于指示该数据包所属的QoS流是目标业务的需要同步的QoS流。因此，上述步骤203c具体是：基站从至少两个数据包中确定包含有同步指示的数据包，该包含有同步指示的数据包即为前述至少两个目标数据包。以图3(c)为例，通过上述步骤202c，基站从QoS流1至QoS流11中获取QoS流1至QoS流5以及QoS流8至QoS流9的数据包，并通过上述步骤203c，基站从QoS流1至QoS流5以及QoS流8至QoS流9的数据包中获取QoS流2、QoS流4和QoS流8的数据包，然后基站根据QoS流2、QoS流4和QoS流8的数据包对目标业务的需要同步的QoS流的数据包进行同步调度。
下面结合图4至图9的具体实施例，对上述图2(a)至图2(c)的实施例进行说明。其中，以下图4、图5和图8的实施例是图2(a)的实施例的具体示例，以下图6和图7的实施例是图2(c)的实施例的具体示例，以下图9的实施例是图2(b)的实施例的具体示例。
图4为本申请实施例提供的一种同步调度方法流程示意图。该实施例，将一个业务对应的需要同步的QoS流所属的多个PDU会话分配到同一个GTP-U隧道，因此该业务对应的需要同步的QoS流的数据包都通过该GTP-U隧道传输，并且，该GTP-U隧道还可能传输该业务对应的不需要同步的QoS流的数据包，和/或其它业务的QoS流的数据包。基站从该GTP-U隧道收到的数据包是可能需要同步的数据包，然后基站从可能需要同步的数据包中进一步确定需要同步的数据包，并根据需要同步的数据包进行同步调度。
该方法包括以下步骤：
步骤401a，UE1建立一个或多个PDU会话。
步骤401b，UE2建立一个或多个PDU会话。
其中，UE1与UE2建立的PDU会话均对应同一个SMF。该UE1和UE2可以接收或发送同一个目标业务的不同数据流。
上述步骤401a与步骤402a的顺序不限。
步骤402，AF向PCF发送业务的标识信息和该业务的同步信息，该同步信息包括同步指示，以及包括同步状态信息或该业务的各个数据流的帧率。
该同步指示用于指示该业务的数据流需要同步，或者用于指示携带该同步指示的数据包所属的QoS流是需要同步QoS流。其中，一个业务的需要同步的数据流可以对应同一个UE，也可以对应不同UE，本申请实施例以一个业务的需要同步的数据流对应UE1和UE2为例进行说明。
该同步状态信息用于指示在同步状态下该业务的数据流的数据包中的帧号之间的对应关系。
一个数据流的帧率用于指示该数据流每秒发送的帧数。
需要说明的是，同一个业务的不同数据流可以对应不同的PCF，比如，上述音频数据流1对应PCF1，视频数据流2对应PCF2，感知数据流3对应PCF3，或者同一个业务的不同数据流也可以对应同一个PCF，本申请实施例对此不限定。
当同一个业务的不同数据流对应不同的PCF，则AF可以向不同的PCF均发送上述同步指示和同步状态信息，或者AF向不同的PCF分别发送同步指示和该业务中与该PCF对应的数据流的帧率。
步骤403，PCF向SMF发送PCC规则，该PCC规则包括业务的标识信息和该业务的同步信息。
如果该业务的多个数据流分别对应不同的PCF，则该步骤403是由多个PCF分别向SMF发送PCC规则。
一个PCC规则对应一个PDU会话。该PDU会话是UE1的PDU会话或UE2的PDU会话。示例性地，参考图3(a)，某个业务的音频数据流1对应UE1的PDU会话1，该业务的视频数据流2对应UE1的PDU会话2，该业务的感知数据流3对应UE2的PDU会话4。
步骤404，SMF向基站发送业务的关联标识和业务的同步规则，可选的，还发送该业务对应的需要同步的QoS流的QFI。
SMF收到一个或多个PCC规则之后，将该PCC规则对应的数据流映射为QoS流，且 为每个QoS流分配一个QFI。其中，一个数据流可以映射为一个QoS流，每个QoS流承载在一个PDU会话中进行传输，一个PDU会话可以承载一个或多个QoS流。
其中，关联标识关联某个业务的需要同步的QoS流对应的PDU会话，即关联标识是标识在PDU会话粒度上的。对应相同关联标识的PDU会话可以称为需要同步的PDU会话，或称为包含需要同步的QoS流的PDU会话。以图3(a)的示例为例，SMF为PDU会话1、PDU会话2和PDU会话4分配相同的关联标识，用于表示对应相同关联标识的PDU会话1、PDU会话2和PDU会话4中包含同一业务的需要同步的QoS流。需要说明的是，如果该PDU会话1、PDU会话2和PDU会话4对应相同的PCF，则也可以由PCF为PDU会话1、PDU会话2和PDU会话4分配相同的关联标识并将该关联标识携带于PCC规则中发给SMF。
该实施例中，SMF为各个QoS流分配QFI时，是为关联的PDU会话内的不同QoS流分配不同的QFI。针对其它PDU会话的QoS流，则按照现有方法正常分配QFI，比如，同一个PDU会话内的不同QoS流的QFI不同，不同PDU会话的QoS流的QFI可以相同也可以不同。以图3(a)的示例为例，则在该实施例中，分配结果如图3(b)所示。
业务的同步规则包括同步状态信息和/或同步精度。该同步状态信息来自步骤403的PCC规则，或者是SMF根据步骤403的PCC规则中的各个数据流的帧率计算得到的。该同步精度用于指示在同步状态下该业务的不同数据流(或QoS流)的数据包中的帧号的偏差。例如该同步精度为2帧。该同步精度可以是预配置在SMF上的，或者是SMF从其它网元请求获得的，或者是其它网元主动发送给SMF的，本申请实施例对此不限定。
一种实现方法中，SMF可以针对对应相同关联标识的多个PDU会话，分别执行上述步骤404。以上述示例为例，SMF向基站发送消息1，该消息1包括关联标识、同步规则以及该PDU会话1中的各个QoS流的QFI，SMF向基站发送消息2，该消息2包括关联标识、同步规则以及该PDU会话2中的各个QoS流的QFI，SMF向基站发送消息3，该消息3包括关联标识、同步规则以及该PDU会话4中的各个QoS流的QFI。其中，消息1、消息2以及消息3中的关联标识相同且同步规则相同。
步骤405，SMF向UPF发送该业务对应的需要同步的QoS流的QFI以及同步指示。
该步骤405可选。当基站根据UPF发送的数据包的GTP-U包头中是否封装有同步指示来判断该业务的数据流是否需要同步，则需要执行该步骤405。该同步指示的含义参考步骤404的描述。
如果UPF收到该同步指示，当UPF从AF收到该业务的需要同步的数据流后，将该同步指示封装在该数据流对应的QoS流的数据包的GTP-U包头中，并将该数据包发送给基站，基站根据该同步指示确定该数据流需要同步。当UPF从AF收到该业务的不需要同步的数据流，UPF不会将该同步指示封装在该数据流对应的QoS流的数据包的GTP-U包头中，基站确定该GTP-U包头中未携带同步指示，则确定该数据流不需要同步。
如果UPF未收到该同步指示，当UPF从AF收到该业务的数据流，UPF按照现有方法执行。因此UPF不感知该数据流是否需要同步，该数据流对应的QoS流的数据包的GTP-U包头中不会封装有该同步指示。基站收到该业务的数据流对应的QoS流的数据包后，可以采用其它方法判断该数据流需要同步，比如基站预先从SMF接收到该业务的需要同步的数据流对应的QFI，因此如果基站收到的数据包中的QFI属于需要同步的数据流对应的QFI，则该数据流需要同步，如果基站收到的数据包中的QFI不属于需要同步的数据流 对应的QFI，则该数据流不需要同步。
步骤406，基站为对应相同关联标识的PDU会话分配相同的接入网隧道端点标识(AN TEID)。
该分配AN TEID的方法，将同一业务中需要进行同步的QoS流分配到同一个GTP-U隧道中，从而基站只需要对该条GTP-U隧道中的数据包进行检测，识别出需要进行同步的数据包，不需要在其它GTP-U隧道中去识别需要同步的数据包，有助于提升同步的准确性和效率。对于其它PDU会话，基站可以根据现有方法为每个PDU会话正常分配一个AN TEID，并绑定该AN TEID对应的QFI。
以图3(a)为例，则基站为PDU会话分配AN TEID的结果如图3(b)所示。
步骤407，基站向SMF发送AN隧道信息，该AN隧道信息包括AN TEID。
步骤408a，SMF向UPF发送AN隧道信息，该AN隧道信息包括AN TEID。
步骤408b，UPF向SMF发送响应信息。
该响应信息是针对步骤408a的响应。
步骤409，SMF向PCF发送响应信息。
该响应信息是针对步骤403的响应。
步骤410，PCF向AF发送响应信息。
该响应信息是针对步骤402的响应。
上述步骤408b、步骤409、步骤410均为可选步骤。
步骤411，AF向UPF发送业务的下行数据包。
该业务即为上述步骤402的业务的标识信息所指示的业务。
以前述示例为例，这里的下行数据包可以是音频数据流1的数据包、视频数据流2的数据包或感知数据流3的数据包。
步骤412，UPF对下行数据包进行封装。
UPF对收到的下行数据包添加GTP-U包头，该GTP-U包头包括帧号、QFI和AN TEID。可选的，如果执行上述步骤405，则需要同步的QoS流的下行数据包的GTP-U包头还包括同步指示。
步骤413，UPF向基站发送下行数据包。
步骤414，基站对该业务的下行数据包进行同步调度。
一种实现方法中，当上述步骤404中SMF向基站发送该业务对应的需要同步的QoS流的QFI，则基站可以预先获知该业务的哪些QoS流需要同步，因此基站可以在收到这些QoS流的下行数据包之后，对收到的下行数据包进行同步调度。
另一种实现方法中，当上述步骤404中SMF没有向基站发送该业务对应的需要同步的QoS流的QFI，且执行了上述步骤405，则UPF在上述步骤412对该业务的下行数据包进行封装时，会在需要同步的QoS流的下行数据包的GTP-U包头中添加同步指示，从而基站可以根据下行数据包是否携带同步指示来判断该下行数据包是否需要同步。
该实施例中，一个业务的需要同步的QoS流被分配到同一个GTP-U隧道中进行传输，因此基站只需要在一个GTP-U隧道中检测该业务的需要同步的QoS流。以图3(b)为例，需要同步的QoS流2、QoS流4和QoS流8均被分配到AN TEID1指示的GTP-U隧道1中进行传输，因此基站只需要在GTP-U隧道1中检测该业务的需要同步的QoS流。
以图3(b)的示例为例，假设UPF在需要同步的QoS流的下行数据包中添加同步指示， 且在一段时间内基站收到下行数据包1至下行数据包10，该10个下行数据包的GTP-U包头包含的信息分别如下：
下行数据包1的GTP-U包头中携带帧号1、QFI1、AN TEID1；
下行数据包2的GTP-U包头中携带帧号2、QFI2、AN TEID1、同步指示；
下行数据包3的GTP-U包头中携带帧号3、QFI3、AN TEID1；
下行数据包4的GTP-U包头中携带帧号4、QFI4、AN TEID1、同步指示；
下行数据包5的GTP-U包头中携带帧号5、QFI5、AN TEID1；
下行数据包6的GTP-U包头中携带帧号6、QFI1、AN TEID2；
下行数据包7的GTP-U包头中携带帧号7、QFI2、AN TEID2；
下行数据包8的GTP-U包头中携带帧号8、QFI6、AN TEID1、同步指示；
下行数据包9的GTP-U包头中携带帧号9、QFI7、AN TEID1；
下行数据包10的GTP-U包头中携带帧号10、QFI1、AN TEID3。
基站收到上述10个下行数据包后，筛选出携带AN-TEID1的下行数据包，即下行数据包1至下行数据包5，以及下行数据包8和下行数据包9，然后再从中筛选出携带同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
或者，基站收到上述10个下行数据包后，直接筛选出携带AN-TEID1和同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
上述方案，一个业务对应的需要同步的QoS流所属的多个PDU会话被分配到同一个GTP-U隧道，该GTP-U隧道由AN TEID标识，该多个PDU会话通过同一个关联标识进行绑定。基站对需要同步的QoS流的数据包进行同步调度，可以保证同一业务的不同数据流的同步，从而提升用户体验。并且，由于需要同步的QoS流被分配到同一个GTP-U隧道中进行传输，因此基站只需要在一个GTP-U隧道中检测该业务的需要同步的QoS流，可以提升同步速度和准确率，从而提升用户体验。
图5为本申请实施例提供的一种同步调度方法流程示意图。该实施例，一个业务对应的需要同步的QoS流的数据包中携带组标识，基站确定携带组标识的数据包是可能需要同步的数据包，不携带组标识的数据包是不需要同步的数据包，然后基站从携带组标识的数据包中进一步确定需要同步的数据包，并根据需要同步的数据包进行同步调度。
该方法包括以下步骤：
步骤501a，UE1建立一个或多个PDU会话。
步骤501b，UE2建立一个或多个PDU会话。
其中，UE1与UE2建立的PDU会话对应的SMF相同，且对应的PCF相同或不同。或者，UE1与UE2建立的PDU会话对应的PCF相同，且对应的SMF相同或不同。该UE1和UE2可以接收或发送同一个目标业务的不同数据流。
上述步骤501a与步骤502a的顺序不限。
步骤502，AF向PCF发送业务的标识信息和该业务的同步信息，该同步信息包括同步指示，以及包括同步状态信息或该业务的各个数据流的帧率。
其中、同步指示、同步状态信息以及帧率的含义可以参考前述步骤402中的描述，不 再赘述。
步骤503，PCF向SMF发送PCC规则，该PCC规则包括业务的标识信息和该业务的同步信息。
其中，如果该业务的需要同步的多个数据流所属的PDU会话对应相同的PCF，则该PCF还可以为这些PDU会话分配关联标识，并将该关联标识和PCF的标识信息携带于PCC规则中发送给SMF，关联标识关联某个业务的需要同步的数据流对应的PDU会话。也即，可选的该PCC规则还包括关联标识和PCF的标识信息，该PCF即为生成该关联标识的PCF。
其中，一个PCC规则对应一个PDU会话，该PDU会话是UE1的PDU会话或UE2的PDU会话。示例性地，某个业务的音频数据流1对应UE1的PDU会话1，该业务的视频数据流2对应UE1的PDU会话2，该业务的感知数据流3对应UE2的PDU会话4。
步骤504，SMF向基站发送业务的关联标识和业务的同步规则。
可选的，该步骤504还发送该业务对应的需要同步的QoS流的QFI。
可选的，如果是PCF生成关联标识，该步骤504还发送PCF的标识信息。
可选的，如果是SMF生成关联标识，该步骤504还发送SMF的标识信息。
SMF收到一个或多个PCC规则之后，将该PCC规则对应的数据流映射为QoS流，且为每个QoS流分配一个QFI。其中，一个数据流可以映射为一个QoS流，每个QoS流承载在一个PDU会话中进行传输，一个PDU会话可以承载一个或多个QoS流。
该实施例中，SMF为各个QoS流分配QFI时，按照现有方法为PDU会话内的QoS流分配QFI，SMF需要保证同一PDU会话内的不同QoS流的QFI不同，不同PDU会话内的不同QoS流的QFI可以相同也可以不同。以图3(a)的示例为例，则SMF为各个PDU会话内的QoS流分配的QFI可以如图3(c)所示。
业务的同步规则包括同步状态信息和/或同步精度。该同步状态信息和同步精度的含义如其它实施例所述。
一种实现方法中，SMF可以针对对应相同关联标识的多个PDU会话，分别执行上述步骤504。以上述示例为例，SMF向基站发送消息1，该消息1包括关联标识、同步规则以及该PDU会话1中的各个QoS流的QFI，SMF向基站发送消息2，该消息2包括关联标识、同步规则以及该PDU会话2中的各个QoS流的QFI，SMF向基站发送消息3，该消息3包括关联标识、同步规则以及该PDU会话4中的各个QoS流的QFI。其中，消息1、消息2以及消息3中的关联标识相同且同步规则相同。
步骤505，基站根据关联标识，生成组标识。
该组标识的含义可以参考图2(a)的实施例中的相关描述，不再赘述。
一种实现方法，如果是由PCF分配关联标识，则基站根据PCF的标识信息和关联标识，分配组标识。比如，PCF1为业务1的需要同步的QoS流所属的PDU会话分配关联标识1，PCF2为业务2的需要同步的QoS流所属的PDU会话分配关联标识1，PCF3为业务3的需要同步的QoS流所属的PDU会话分配关联标识2，则基站根据PCF1的标识信息和关联标识1生成组标识1，根据PCF2的标识信息和关联标识1生成组标识2，根据PCF3的标识信息和关联标识2生成组标识3。
另一种实现方法，如果是由SMF分配关联标识，则基站根据SMF的标识信息和关联标识，分配组标识。比如，SMF1为业务1的需要同步的QoS流所属的PDU会话分配关联标识1，SMF2为业务2的需要同步的QoS流所属的PDU会话分配关联标识1，SMF3 为业务3的需要同步的QoS流所属的PDU会话分配关联标识2，则基站根据SMF1的标识信息和关联标识1生成组标识1，根据SMF2的标识信息和关联标识1生成组标识2，根据SMF3的标识信息和关联标识2生成组标识3。
步骤506，基站向SMF发送组标识和AN TEID。
该AN TEID是基站根据现有方法确定的，即为每个PDU会话分配一个AN TEID，并绑定该AN TEID对应的QFI。
以图3(a)的示例为例，则基站为各个PDU会话分配AN TEID的结果可以如图3(c)所示。
步骤507a，SMF向UPF发送组标识和AN TEID，可选的，还向UPF发送该业务对应的需要同步的QoS流的QFI以及同步指示。
步骤507b，UPF向SMF发送响应信息。
该响应信息是针对步骤507a的响应。
步骤508，SMF向PCF发送响应信息。
该响应信息是针对步骤503的响应。
步骤509，PCF向AF发送响应信息。
该响应信息是针对步骤502的响应。
上述步骤507b、步骤508、步骤509均为可选步骤。
步骤510，AF向UPF发送业务的下行数据包。
该业务即为上述步骤502的业务的标识信息所指示的业务。
以前述示例为例，这里的下行数据包可以是音频数据流1的数据包、视频数据流2的数据包或感知数据流3的数据包。
步骤511，UPF对下行数据包进行封装。
UPF对收到的下行数据包添加GTP-U包头，该GTP-U包头包括帧号、QFI、AN TEID和组标识。可选的，如果UPF从SMF收到该业务对应的需要同步的QoS流的QFI以及同步指示，则需要同步的QoS流的下行数据包的GTP-U包头还包括同步指示。
步骤512，UPF向基站发送下行数据包。
步骤513，基站对该业务的下行数据包进行同步调度。
一种实现方法中，当上述步骤504中SMF向基站发送该业务对应的需要同步的QoS流的QFI，则基站可以预先获知该业务的哪些QoS流需要同步，因此基站可以在收到这些QoS流的下行数据包之后，对收到的下行数据包进行同步调度。
另一种实现方法中，当上述步骤504中SMF没有向基站发送该业务对应的需要同步的QoS流的QFI，且上述步骤507a中向UPF发送了该业务对应的需要同步的QoS流的QFI以及同步指示，则UPF在上述步骤511对该业务的下行数据包进行封装时，会在需要同步的QoS流的下行数据包的GTP-U包头中添加同步指示，从而基站可以根据下行数据包是否携带同步指示来判断该下行数据包是否需要同步。
以图3(c)的示例为例，假设UPF在业务1的需要同步的QoS流的下行数据包中添加组标识1和同步指示，且在一段时间内基站收到下行数据包1至下行数据包10，该10个下行数据包的GTP-U包头包含的信息分别如下：
下行数据包1的GTP-U包头中携带帧号1、QFI1、AN TEID1、组标识1；
下行数据包2的GTP-U包头中携带帧号2、QFI2、AN TEID1、组标识1、同步指示；
下行数据包3的GTP-U包头中携带帧号3、QFI3、AN TEID1、组标识1；
下行数据包4的GTP-U包头中携带帧号4、QFI1、AN TEID2、组标识1、同步指示；
下行数据包5的GTP-U包头中携带帧号5、QFI2、AN TEID2、组标识1；
下行数据包6的GTP-U包头中携带帧号6、QFI1、AN TEID3；
下行数据包7的GTP-U包头中携带帧号7、QFI2、AN TEID3；
下行数据包8的GTP-U包头中携带帧号8、QFI1、AN TEID4、组标识1、同步指示；
下行数据包9的GTP-U包头中携带帧号9、QFI2、AN TEID4、组标识1；
下行数据包10的GTP-U包头中携带帧号10、QFI1、AN TEID5。
基站收到上述10个下行数据包后，筛选出携带组标识1的下行数据包，即下行数据包1至下行数据包5，以及下行数据包8和下行数据包9，然后再从中筛选出携带同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
或者，基站收到上述10个下行数据包后，直接筛选出携带组标识1和同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
其中，基站对业务的数据流(或QoS流的数据包)进行同步调度的具体方法可以参考步骤414中的描述，不再赘述。
上述方案，基站根据关联标识为相关联的各个UE的PDU会话分配相同的组标识，确保相关联的PDU会话对应的组标识是唯一的。一个组标识对应的PDU会话即为同一个业务对应的需要同步的QoS流所属的PDU会话。基站在收到需要同步的QoS流时，在含有相同组标识的PDU会话中寻找需要同步的QoS流并结合同步规则进行同步调度，可以保证同一业务的不同数据流的同步，从而提升用户体验。
图6为本申请实施例提供的一种同步调度方法流程示意图。该实施例，基站记录用于传输一个业务对应的需要同步的QoS流的数据包的多个接入网隧道端点标识，基站确定从这些接入网隧道端点标识对应的GTP-U隧道收到的数据包为可能需要同步的数据包，然后基站从可能需要同步的数据包中进一步确定需要同步的数据包，并根据需要同步的数据包进行同步调度。该实施例中，由基站确定该多个接入网隧道端点标识之间的同步关系。
该方法包括以下步骤：
步骤601a，同上述步骤501a。
步骤601b，同上述步骤501b。
步骤602至步骤604，同上述步骤502至步骤504。
步骤605，基站为每个PDU会话分配一个接入网隧道端点标识(AN TEID)，并记录AN TEID之间的同步关系。
一种实现方法，由SMF/PCF/AF分配关联标识，则基站根据SMF/PCF/AF的标识信息和关联标识(也即SMF的标识信息和关联标识，或者PCF的标识信息和关联标识，或者AF的标识信息和关联标识)，确定业务的需要同步的QoS流所属的PDU会话，并建立这些PDU会话对应的AN TEID之间的同步关系，其表明该业务的需要同步的QoS流是在这些AN TEID对应的隧道中进行传输的。可选的，如果上述步骤604中，SMF还向基站发送该业务对应的需要同步的QoS流的QFI，则基站还可以建立AN TEID与需要同步的QoS 流的QFI之间的对应关系。
以图3(a)的示例为例，假设SMF/PCF/AF为PDU会话1、PDU会话2和PDU会话4分配了关联标识1，则基站可以通过步骤604收到关联标识1和SMF/PCF/AF的标识信息，并根据关联标识1和SMF/PCF/AF的标识信息，确定业务的需要同步的QoS流所属的PDU会话包括PDU会话1、PDU会话2和PDU会话4。然后基站还为UE的各个PDU会话分别分配不同的AN TEID，分配结果如图3(c)所示。并且，基站根据关联标识，建立AN TEID1、AN TEID2和AN TEID4之间的同步关系，后续该业务的需要同步的QoS流将会通过AN TEID1、AN TEID2和AN TEID4对应的GTP-U隧道传输至基站。如果上述步骤604中SMF还向基站发送该业务对应的需要同步的QoS流(即QoS流2、QoS流4和QoS流8)的QFI，则基站建立如下对应关系：
1)、AN TEID1、AN TEID2和AN TEID4之间的同步关系；
2)、AN TEID1与QFI2的对应关系，该QFI2是QoS流2的标识信息；
3)、AN TEID2与QFI1的对应关系，该QFI1是QoS流4的标识信息；
4)、AN TEID4与QFI1的对应关系，该QFI1是QoS流8的标识信息。
步骤606，基站向SMF发送AN TEID。
步骤607a，SMF向UPF发送AN TEID，可选的，还向UPF发送该业务对应的需要同步的QoS流的QFI以及同步指示。
步骤607b，UPF向SMF发送响应信息。
该响应信息是针对步骤607a的响应。
步骤608，SMF向PCF发送响应信息。
该响应信息是针对步骤603的响应。
步骤609，PCF向AF发送响应信息。
该响应信息是针对步骤602的响应。
上述步骤607b、步骤608、步骤609均为可选步骤。
步骤610，AF向UPF发送业务的下行数据包。
该业务即为上述步骤602的业务的标识信息所指示的业务。
步骤611，UPF对下行数据包进行封装。
UPF对收到的下行数据包添加GTP-U包头，该GTP-U包头包括帧号、QFI和AN TEID。可选的，如果UPF从SMF收到同步指示，则需要同步的QoS流的下行数据包的GTP-U包头还包括同步指示。
步骤612，UPF向基站发送下行数据包。
步骤613，基站对该业务的下行数据包进行同步调度。
一种实现方法中，如果上述步骤607a不发送该业务对应的需要同步的QoS流的QFI以及同步指示，则UPF向基站发送的下行数据包均不携带同步指示，则基站根据AN TEID1、AN TEID2和AN TEID4之间的同步关系，AN TEID1与QFI2的对应关系，AN TEID2与QFI1的对应关系，以及AN TEID4与QFI1的对应关系，对以下类型的下行数据包进行同步调度：携带AN TEID1和QFI2的下行数据包，携带AN TEID2和QFI1的下行数据包，携带AN TEID4和QFI1的下行数据包。
另一种实现方法中，如果上述步骤607a发送该业务对应的需要同步的QoS流的QFI以及同步指示，则UPF向基站发送的需要同步的QoS流的下行数据包均携带同步指示， 则基站根据AN TEID1、AN TEID2和AN TEID4之间的同步关系，对以下类型的下行数据包进行同步调度：携带AN TEID1和同步指示的下行数据包，携带AN TEID2和同步指示的下行数据包，携带AN TEID4和同步指示的下行数据包。
以图3(a)的示例为例，假设UPF在业务1的需要同步的QoS流的下行数据包中均添加同步指示，且在一段时间内基站收到下行数据包1至下行数据包10，该10个下行数据包的GTP-U包头包含的信息分别如下：
下行数据包1的GTP-U包头中携带帧号1、QFI1、AN TEID1；
下行数据包2的GTP-U包头中携带帧号2、QFI2、AN TEID1、同步指示；
下行数据包3的GTP-U包头中携带帧号3、QFI3、AN TEID1；
下行数据包4的GTP-U包头中携带帧号4、QFI1、AN TEID2、同步指示；
下行数据包5的GTP-U包头中携带帧号5、QFI2、AN TEID2；
下行数据包6的GTP-U包头中携带帧号6、QFI1、AN TEID3；
下行数据包7的GTP-U包头中携带帧号7、QFI2、AN TEID3；
下行数据包8的GTP-U包头中携带帧号8、QFI1、AN TEID4、同步指示；
下行数据包9的GTP-U包头中携带帧号9、QFI2、AN TEID4；
下行数据包10的GTP-U包头中携带帧号10、QFI1、AN TEID5。
基站收到上述10个下行数据包后，筛选出携带AN TEID1、AN TEID2或AN TEID4的下行数据包，即下行数据包1至下行数据包5，以及下行数据包8和下行数据包9，然后再从中筛选出携带同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
或者，基站收到上述10个下行数据包后，直接筛选出携带同步指示，以及携带AN TEID1、AN TEID2或AN TEID4的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
其中，基站对该业务的数据流进行同步调度的具体方法可以参考步骤414中的描述，不再赘述。
上述方案，基站为各个PDU会话生成AN TEID，并将具有同步关系的AN TEID进行关联，也即将同一个业务对应的需要同步的QoS流所属的PDU会话的AN TEID建立同步关系。基站在收到需要同步的QoS流时，在建立了同步关系的AN TEID对应的GTP-U隧道中寻找需要同步的QoS流并结合同步规则进行同步调度，可以保证同一业务的不同数据流的同步，从而提升用户体验。
图7为本申请实施例提供的一种同步调度方法流程示意图。该实施例，基站记录用于传输一个业务对应的需要同步的QoS流的数据包的多个接入网隧道端点标识，基站确定从这些接入网隧道端点标识对应的GTP-U隧道收到的数据包为可能需要同步的数据包，然后基站从可能需要同步的数据包中进一步确定需要同步的数据包，并根据需要同步的数据包进行同步调度。该实施例中，由SMF确定该多个接入网隧道端点标识之间的同步关系，并将同步关系发送给基站。
该方法包括以下步骤：
步骤701a，同上述步骤501a。
步骤701b，同上述步骤501b。
步骤702至步骤703，同上述步骤502至步骤503。
步骤704，SMF向基站发送同步规则。
该同步规则的含义可以参考前述实施例的描述。
步骤705，基站为每个PDU会话分配一个接入网隧道端点标识(AN TEID)，并向SMF发送AN TEID。
步骤706，SMF向基站发送各个AN TEID之间的同步关系。
一种实现方法，PCF/AF生成关联标识并将关联标识直接或间接发送给SMF，则SMF根据关联标识，确定业务的需要同步的QoS流所属的PDU会话，并建立这些PDU会话对应的AN TEID之间的同步关系，其表明该业务的需要同步的QoS流是在这些AN TEID对应的隧道中进行传输的，然后SMF向基站发送这些AN TEID之间的同步关系。可选的，SMF还可以向基站发送AN TEID与需要同步的QoS流的QFI之间的对应关系。
另一种实现方法，SMF确定业务的需要同步的QoS流所属的PDU会话，并建立这些PDU会话对应的AN TEID之间的同步关系，其表明该业务的需要同步的QoS流是在这些AN TEID对应的隧道中进行传输的，然后SMF向基站发送这些AN TEID之间的同步关系。可选的，SMF还可以向基站发送AN TEID与需要同步的QoS流的QFI之间的对应关系。
假设SMF为QoS流分配的QFI以及基站分配的AN TEID如图3(c)所示，SMF根据PCF/AF分配的关联标识确定(或者SMF自行确定)业务的需要同步的QoS流所属的PDU会话包括PDU会话1、PDU会话2和PDU会话4，则SMF建立AN TEID1、AN TEID2和AN TEID4之间的同步关系，后续该业务的需要同步的QoS流将会通过AN TEID1、AN TEID2和AN TEID4对应的GTP-U隧道传输至基站，因此SMF向基站发送AN TEID1、AN TEID2和AN TEID4之间的同步关系。可选的，SMF还可以向基站发送AN TEID与需要同步的QoS流的QFI之间的对应关系，也即SMF向基站发送如下对应关系：
1)、AN TEID1、AN TEID2和AN TEID4之间的同步关系；
2)、AN TEID1与QFI2的对应关系，该QFI2是QoS流2的标识信息；
3)、AN TEID2与QFI1的对应关系，该QFI1是QoS流4的标识信息；
4)、AN TEID4与QFI1的对应关系，该QFI1是QoS流8的标识信息。
步骤707a，同步骤607a。
步骤707b，同步骤607b。
步骤708至步骤713，同步骤608至步骤613。
上述步骤707b、步骤708、步骤709均为可选步骤。
上述方案，基站为各个PDU会话生成AN TEID，并由SMF将具有同步关系的AN TEID进行关联，也即将同一个业务对应的需要同步的QoS流所属的PDU会话的AN TEID建立同步关系，然后SMF向基站发送该同步关系。基站在收到需要同步的QoS流时，在建立了同步关系的AN TEID对应的隧道中寻找需要同步的QoS流并结合同步规则进行同步调度，可以保证同一业务的不同数据流的同步，从而提升用户体验。
图8为本申请实施例提供的一种同步调度方法流程示意图。该实施例，基站记录用于传输一个业务对应的需要同步的QoS流的数据包的多个接入网隧道端点标识以及分配该 接入网隧道端点标识的网络设备的标识信息，当基站收到的数据包中包含该接入网隧道端点标识和该网络设备的标识信息，则基站确定该数据包为可能需要同步的数据包，然后基站从可能需要同步的数据包中进一步确定需要同步的数据包，并根据需要同步的数据包进行同步调度。该实施例中，由基站确定该多个接入网隧道端点标识之间的同步关系。
该方法包括以下步骤：
步骤801a，同上述步骤501a。
步骤801b，同上述步骤501b。
步骤802至步骤804，同上述步骤502至步骤504。
步骤805，基站建立SMF/PCF/AF的标识信息，与关联标识的对应关系。
基站为不同PDU会话分配不同的接入网隧道端点标识(AN TEID)。
如果是SMF分配关联标识，则步骤804还发送SMF的标识信息，基站建立SMF的标识信息与关联标识的对应关系。如果是PCF分配关联标识，则步骤803和步骤804均发送PCF的标识信息，基站建立PCF的标识信息与关联标识的对应关系。如果是AF分配关联标识，则步骤802、步骤803和步骤804均发送AF的标识信息，基站建立AF的标识信息与关联标识的对应关系。后续，如果基站收到的下行数据包中携带该SMF/PCF/AF的标识信息以及该关联标识，则基站将会对这些下行数据包进行同步调度。
步骤806，基站向SMF发送AN TEID。
步骤807a，SMF向UPF发送AN TEID，关联标识以及SMF/PCF/AF的标识信息。可选的，还向UPF发送该业务对应的需要同步的QoS流的QFI以及同步指示。
如果是SMF分配关联标识，则SMF向UPF发送AN TEID，关联标识以及SMF的标识信息。如果是PCF分配关联标识，则SMF向UPF发送AN TEID，关联标识以及PCF的标识信息。如果是AF分配关联标识，则SMF向UPF发送AN TEID，关联标识以及AF的标识信息。
步骤807b，UPF向SMF发送响应信息。
该响应信息是针对步骤807a的响应。
步骤808，SMF向PCF发送响应信息。
该响应信息是针对步骤803的响应。
步骤809，PCF向AF发送响应信息。
该响应信息是针对步骤802的响应。
上述步骤807b、步骤808、步骤809均为可选步骤。
步骤810，AF向UPF发送业务的下行数据包。
该业务即为上述步骤802的业务的标识信息所指示的业务。
步骤811，UPF对下行数据包进行封装。
UPF对收到的需要同步的QoS流的下行数据包添加GTP-U包头，该GTP-U包头包括帧号、QFI、AN TEID、关联标识和SMF/PCF/AF的标识信息。可选的，如果UPF从SMF收到同步指示，则需要同步的QoS流的下行数据包的GTP-U包头还包括同步指示。
步骤812，UPF向基站发送下行数据包。
步骤813，基站对该业务的下行数据包进行同步调度。
以图3(c)为例，一种实现方法中，如果上述步骤807a不发送该业务对应的需要同步的QoS流的QFI以及同步指示，则UPF向基站发送的下行数据包均不携带同步指示，基站根 据SMF/PCF/AF的标识信息与关联标识的对应关系，对以下类型的下行数据包进行同步调度：携带QFI1、SMF/PCF/AF的标识信息以及关联标识的下行数据包，以及携带QFI2、SMF/PCF/AF的标识信息以及关联标识的下行数据包。其中，这些下行数据包中携带的关联标识相同，且SMF/PCF/AF的标识信息相同。
另一种实现方法中，如果上述步骤807a发送该业务对应的需要同步的QoS流的QFI以及同步指示，则UPF向基站发送的需要同步的QoS流的下行数据包均携带同步指示，则基站根据SMF/PCF/AF的标识信息与关联标识的对应关系，对携带同步指示、相同SMF/PCF/AF的标识信息以及相同关联标识的下行数据包进行同步调度。其中，这些下行数据包中携带的关联标识相同，且SMF/PCF/AF的标识信息相同。
以图3(c)的示例为例，假设UPF在业务1的需要同步的QoS流的下行数据包中均添加同步指示，由SMF1分配关联标识1，SMF1的标识信息为SMF ID1，且在一段时间内基站收到下行数据包1至下行数据包10，该10个下行数据包的GTP-U包头包含的信息分别如下：
下行数据包1的GTP-U包头中携带帧号1、QFI1、AN TEID1、SMF ID1、关联标识1；
下行数据包2的GTP-U包头中携带帧号2、QFI2、AN TEID1、SMF ID1、关联标识1、同步指示；
下行数据包3的GTP-U包头中携带帧号3、QFI3、AN TEID1、SMF ID1、关联标识1；
下行数据包4的GTP-U包头中携带帧号4、QFI1、AN TEID2、SMF ID1、关联标识1、同步指示；
下行数据包5的GTP-U包头中携带帧号5、QFI2、AN TEID2、SMF ID1、关联标识1；
下行数据包6的GTP-U包头中携带帧号6、QFI1、AN TEID3；
下行数据包7的GTP-U包头中携带帧号7、QFI2、AN TEID3；
下行数据包8的GTP-U包头中携带帧号8、QFI1、AN TEID4、SMF ID1、关联标识1、同步指示；
下行数据包9的GTP-U包头中携带帧号9、QFI2、AN TEID4、SMF ID1、关联标识1；
下行数据包10的GTP-U包头中携带帧号10、QFI1、AN TEID5。
基站收到上述10个下行数据包后，筛选出携带SMF ID1和关联标识1的下行数据包，即下行数据包1至下行数据包5，以及下行数据包8和下行数据包9，然后再从中筛选出携带同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
或者，基站收到上述10个下行数据包后，直接筛选出携带SMF ID1、关联标识1和同步指示的下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
其中，基站对该业务的数据流进行同步调度的具体方法可以参考步骤414中的描述，不再赘述。
上述方案，基站为各个PDU会话生成AN TEID，并建立SMF/PCF/AF的标识信息与关联标识的对应关系。基站在收到需要同步的QoS流时，从携带有该SMF/PCF/AF的标识信息的QoS流中确定需要同步的QoS流并结合同步规则进行同步调度，可以保证同一业务的不同数据流的同步，从而提升用户体验。
图9为本申请实施例提供的一种同步调度方法流程示意图。该实施例，将一个业务对应的需要同步的QoS流所属的多个PDU会话分配到同一个GTP-U隧道，因此该业务对应的需要同步的QoS流的数据包都通过该GTP-U隧道传输，并且该GTP-U隧道专用于传输该业务对应的需要同步的QoS流的数据包，不传输其它数据包。基站从该GTP-U隧道收到的数据包均是需要同步的数据包，基站根据需要同步的数据包进行同步调度。
该方法包括以下步骤：
步骤901a，同上述步骤401a。
步骤901b，同上述步骤401b。
步骤902至步骤903，同上述步骤402至步骤403。
步骤904，SMF向基站发送业务的关联标识、业务的同步规则以及该业务对应的需要同步的QoS流的QFI。
其中，关联标识和同步规则的含义，可以参考步骤404中的描述。
与前述步骤404所不同的是：该步骤904中，SMF为各个QoS流分配QFI时，是为关联的PDU会话内的需要同步的QoS流分配不同的QFI，对于关联的PDU会话内的不需要同步的QoS流则按照现有方法分配QFI，也即针对关联的PDU会话内的不需要同步的QoS流，只需要保证同一PDU会话内的不需要同步的QoS流的QFI不同，不需要保证不同PDU会话内的不需要同步的QoS流的QFI不同。以图3(a)的示例为例，则该实施例中SMF分配的QFI如图3(d)所示。
步骤905，基站为对应相同关联标识的PDU会话内的需要同步的QoS流分配相同的接入网隧道端点标识(AN TEID)。
该分配AN TEID的方法，将同一业务中需要进行同步的QoS流分配到同一个GTP-U隧道中，从而基站只需要对该条GTP-U隧道中的数据包进行检测，识别出需要进行同步的数据包，不需要在其它GTP-U隧道中去识别需要同步的数据包，有助于提升同步的准确性和效率。并且，由于该GTP-U隧道中的QoS流均是需要同步的QoS流，该GTP-U隧道不包含不需要同步的QoS流，因此UPF从AF收到数据包后，不需要在GTP-U包头中添加同步指示，基站对这条GTP-U隧道上接收到的所有数据包都进行同步调度处理。
对于其它PDU会话，基站可以根据现有方法为每个PDU会话正常分配一个AN TEID，并绑定该AN TEID对应的QFI。
以图3(a)的示例为例，则该实施例中基站分配的AN TEID可以如图3(d)所示。
步骤906，同上述步骤407。
步骤907a，同上述步骤408a。
步骤907b，同上述步骤408b。
步骤908至步骤910，同上述步骤409至步骤411。
上述步骤907b、步骤908、步骤909均为可选步骤。
步骤911，UPF对下行数据包进行封装。
UPF对收到的下行数据包添加GTP-U包头，该GTP-U包头包括帧号、QFI和AN TEID。
步骤912，UPF向基站发送下行数据包。
步骤913，基站对该业务的下行数据包进行同步调度。
基站对需要同步的QoS流所在的GTP-U隧道内的下行数据包进行同步调度，通过该GTP-U隧道接收的下行数据包均是该业务的需要同步的下行数据包。
该实施例中，一个业务的需要同步的QoS流被分配到同一个GTP-U隧道中进行传输，且该GTP-U隧道中不包含不需要同步的QoS流，因此基站只需要在一个GTP-U隧道中检测该业务的需要同步的QoS流。以图3(d)为例，需要同步的QoS流2、QoS流4和QoS流8均被分配到AN TEID1指示的GTP-U隧道1中进行传输，因此基站只需要在GTP-U隧道1中检测该业务的需要同步的QoS流。
以图3(d)的示例为例，假设在一段时间内基站收到下行数据包1至下行数据包10，该10个下行数据包的GTP-U包头包含的信息分别如下：
下行数据包1的GTP-U包头中携带帧号1、QFI1、AN TEID2；
下行数据包2的GTP-U包头中携带帧号2、QFI1、AN TEID1；
下行数据包3的GTP-U包头中携带帧号3、QFI2、AN TEID2；
下行数据包4的GTP-U包头中携带帧号4、QFI2、AN TEID1；
下行数据包5的GTP-U包头中携带帧号5、QFI1、AN TEID3；
下行数据包6的GTP-U包头中携带帧号6、QFI1、AN TEID4；
下行数据包7的GTP-U包头中携带帧号7、QFI2、AN TEID4；
下行数据包8的GTP-U包头中携带帧号8、QFI3、AN TEID1；
下行数据包9的GTP-U包头中携带帧号9、QFI1、AN TEID5；
下行数据包10的GTP-U包头中携带帧号10、QFI1、AN TEID6。
基站收到上述10个下行数据包后，筛选出携带AN-TEID1的下行数据包，即下行数据包2、下行数据包4和下行数据包8，并根据下行数据包2、下行数据包4和下行数据包8中的帧号，对该业务的数据流(或QoS流)进行同步。
其中，基站对该业务的数据流进行同步调度的具体方法可以参考步骤414中的描述，不再赘述。
上述方案，一个业务对应的需要同步的QoS流被分配到同一个GTP-U隧道，该GTP-U隧道由AN TEID标识，该需要同步的QoS流所属的PDU会话通过同一个关联标识进行绑定。基站对需要同步的QoS流进行同步调度，可以保证同一业务的不同数据流的同步，从而提升用户体验。并且，由于需要同步的QoS流被分配到同一个GTP-U隧道中进行传输，且该GTP-U隧道中不包含不需要同步的QoS流，因此该GTP-U隧道的QoS流均是需要同步的QoS流，且QoS流的下行数据包不需要携带同步指示，因此可以提升同步速度和准确率，从而提升用户体验。
该图9的实施例与上述图4的实施例相比，具有以下不同：该图9的实施例中，需要同步的QoS流被分配到同一个GTP-U隧道中且该GTP-U隧道中不包含不需要同步的QoS流；图4的实施例中，需要同步的QoS流被分配到同一个GTP-U隧道中，但该GTP-U隧道中可能还包含不需要同步的QoS流。
可以理解的是，为了实现上述实施例中功能，接入网设备、用户面网元或会话管理网元包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图10和图11为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中接入网设备、用户面网元或会话管理网元的功能，因此也 能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是接入网设备、用户面网元或会话管理网元，也可以是应用于接入网设备、用户面网元或会话管理网元的模块(如芯片)。
图10所示的通信装置1000包括处理单元1010和收发单元1020。通信装置1000用于实现上述方法实施例中接入网设备、用户面网元或会话管理网元的功能。
当该通信装置1000用于实现上述方法实施例中的接入网设备的功能，收发单元1020，用于接收来自用户面网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；处理单元1010，用于从该多个数据包中确定包含有相同标记信息的至少两个数据包，该标记信息对应该目标业务的需要同步的至少两个QoS流所属的多个数据连接会话；从该至少两个数据包确定至少两个目标数据包，该至少两个目标数据包对应该目标业务的需要同步的至少两个QoS流；并根据该至少两个目标数据包，对该目标业务的需要同步的至少两个QoS流进行同步调度。
一种可能的实现方法中，收发单元1020，还用于在接收来自用户面网元的目标业务的多个数据包之前，接收来自会话管理网元的关联标识，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话；处理单元1010，还用于根据该关联标识，为该目标业务的需要同步的至少两个QoS流所属的数据连接会话确定该标记信息；收发单元1020，还用于通过该会话管理网元向该用户面网元发送该标记信息。
一种可能的实现方法中，该标记信息是由该接入网设备分配的组标识，该组标识对应该目标业务的需要同步的至少两个QoS流所属的数据连接会话。
一种可能的实现方法中，该标记信息是接入网隧道端点标识，该接入网隧道端点标识用于标识GTP-U隧道，该GTP-U隧道用于传输该目标业务的需要同步的至少两个QoS流所属的数据连接会话中的QoS流。
一种可能的实现方法中，该标记信息包括关联标识和网络设备的标识信息，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话，该网络设备是生成该关联标识的会话管理网元、策略控制网元或应用功能网元。
一种可能的实现方法中，收发单元1020，还用于从会话管理网元接收该目标业务的需要同步的至少两个QoS流的QFI；其中，该至少两个目标数据包指的是包含有目标QFI的数据包，该目标QFI是该目标业务的需要同步的至少两个QoS流的QFI中的任一个。
一种可能的实现方法中，该至少两个目标数据包指的是包含有同步指示的数据包，该同步指示用于指示该数据包所属的QoS流是该目标业务的需要同步的QoS流。
一种可能的实现方法中，处理单元1010，具体用于根据同步状态信息和该至少两个目标数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流进行同步调度，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
一种可能的实现方法中，处理单元1010，具体用于根据同步状态信息和该至少两个目标数据包包含的帧号，确定该目标业务的需要同步的至少两个QoS流不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
一种可能的实现方法中，收发单元1020，还用于接收来自会话管理网元的该同步状态 信息和该同步精度。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
当该通信装置1000用于实现上述方法实施例中的接入网设备的功能，收发单元1020，用于接收来自用户面网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；处理单元1010，用于从该多个数据包中确定包含有相同接入网隧道端点标识的至少两个数据包，该至少两个数据包对应该目标业务的需要同步的至少两个QoS流，该接入网隧道端点标识用于标识目标隧道，该目标隧道是传输该目标业务的需要同步的至少两个QoS流的GTP-U隧道，该目标业务的需要同步的至少两个QoS流对应数据连接会话；以及根据该至少两个数据包，对该目标业务的需要同步的至少两个QoS流进行同步调度。
一种可能的实现方法中，收发单元1020，还用于在接收来自用户面网元的目标业务的多个数据包之前，接收来自会话管理网元的关联标识和该目标业务的需要同步的至少两个QoS流的QFI，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话；处理单元1010，还用于根据该关联标识和该目标业务的需要同步的至少两个QoS流的QFI，为该目标业务的需要同步的至少两个QoS流确定该接入网隧道端点标识；收发单元1020，还用于通过该会话管理网元向该用户面网元发送该接入网隧道端点标识。
一种可能的实现方法中，处理单元1010，具体用于根据同步状态信息和该至少两个数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流进行同步调度，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
一种可能的实现方法中，处理单元1010，具体用于根据同步状态信息和该至少两个数据包包含的帧号，确定该目标业务的需要同步的至少两个QoS流不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
一种可能的实现方法中，收发单元1020，还用于接收来自会话管理网元的该同步状态信息和该同步精度。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
当该通信装置1000用于实现上述方法实施例中的接入网设备的功能，收发单元1020，用于接收来自用户面网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个数据包中的每个数据包包含QFI，该QFI用于标识该数据包所属的QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；处理单元1010，用于根据多个接入网隧道端点标识之间的同步关系，从该多个数据包中确定至少两个数据包，该至少两个数据包中的每个数据包还包含该多个接入网隧道端点标识中的任一接入网隧道端点标识，该多个接入网隧道端点标识分别指示的GTP-U隧道均用于传输该目标业务的需要同步的至少两个QoS流；从该至少两个数据包确定至少两个目标数据包，该至少两个目标数据包对应该目标业务的需要同步的至少两个QoS流；以及根据该至少两个目标数据包，对该目标业务的需要同步的至少两个QoS流进行同步调度。
一种可能的实现方法中，收发单元1020，还用于在接收来自用户面网元的目标业务的多个数据包之前，接收来自会话管理网元的关联标识，该关联标识关联该目标业务的需要 同步的至少两个QoS流所属的数据连接会话；处理单元1010，还用于为该目标业务的需要同步的至少两个QoS流所属的数据连接会话确定该多个接入网隧道端点标识，该多个接入网隧道端点标识与该目标业务的需要同步的至少两个QoS流所属的数据连接会话一一对应；以及根据该关联标识，建立该同步关系。
一种可能的实现方法中，处理单元1010，还用于在收发单元1020接收来自用户面网元的目标业务的多个数据包之前，为该目标业务的需要同步的至少两个QoS流所属的数据连接会话确定该多个接入网隧道端点标识，该多个接入网隧道端点标识与该目标业务的需要同步的至少两个QoS流所属的数据连接会话一一对应；收发单元1020，还用于向会话管理网元发送该多个接入网隧道端点标识；以及从该会话管理网元接收该同步关系。
一种可能的实现方法中，收发单元1020，还用于接收来自该会话管理网元的该目标业务的需要同步的至少两个QoS流的QFI；其中，该至少两个目标数据包指的是包含有目标QFI的数据包，该目标QFI是该目标业务的需要同步的至少两个QoS流的QFI中的任一个。
一种可能的实现方法中，该至少两个目标数据包指的是包含有同步指示的数据包，该同步指示用于指示该数据包所属的QoS流是该目标业务的需要同步的QoS流。
一种可能的实现方法中，处理单元1010，具体用于根据同步状态信息和该至少两个目标数据包包含的帧号，对该目标业务的需要同步的至少两个QoS流进行同步调度，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
一种可能的实现方法中，处理单元1010，具体用于根据同步状态信息和该至少两个目标数据包包含的帧号，确定该目标业务的需要同步的至少两个QoS流不满足同步精度，则调整该目标业务的需要同步的至少两个QoS流的数据包的发送速度，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
一种可能的实现方法中，收发单元1020，还用于接收来自会话管理网元的该同步状态信息和该同步精度。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
当该通信装置1000用于实现上述方法实施例中的用户面网元的功能，收发单元1020，用于接收来自应用功能网元的目标业务的多个数据包，该多个数据包属于多个QoS流，该多个QoS流包括该目标业务的需要同步的至少两个QoS流；处理单元1010，用于在该多个数据包的至少两个数据包中添加标记信息和服务质量流标识QFI，该至少两个数据包的每个数据包中的QFI用于标识该数据包所属的服务质量QoS流，该标记信息对应该目标业务的需要同步的至少两个QoS流所属的多个协议数据单元数据连接会话；收发单元1020，还用于向接入网设备发送包含添加的标记信息和QFI的该至少两个数据包的多个数据包。
一种可能的实现方法中，收发单元1020，还用于接收来自该接入网设备的该标记信息。
一种可能的实现方法中，该标记信息是由该接入网设备分配的组标识，该组标识对应该目标业务的需要同步的至少两个QoS流所属的数据连接会话。
一种可能的实现方法中，该标记信息是接入网隧道端点标识，该接入网隧道端点标识用于标识GTP-U隧道，该GTP-U隧道用于传输该目标业务的需要同步的至少两个QoS流所属的数据连接会话中的QoS流。
一种可能的实现方法中，该标记信息包括关联标识和网络设备的标识信息，该关联标识关联该目标业务的需要同步的至少两个QoS流所属的数据连接会话，该网络设备是生成 该关联标识的会话管理网元、策略控制网元或应用功能网元。
一种可能的实现方法中，收发单元1020，还用于接收来自会话管理网元的该目标业务的需要同步的至少两个QoS流的QFI；处理单元1010，还用于在通过收发单元1020向接入网设备发送包含添加的标记信息和QFI的至少两个数据包的多个数据包之前，根据该目标业务的需要同步的至少两个QoS流的QFI，在该至少两个数据包的至少两个目标数据包中添加同步指示，该至少两个目标数据包对应该目标业务的需要同步的至少两个QoS流，该同步指示用于指示该目标数据包所属的QoS流是该目标业务的需要同步的至少两个QoS流。
一种可能的实现方法中，该至少两个目标数据包均包含帧号，该帧号用于该目标业务的需要同步的至少两个QoS流的同步调度。
一种可能的实现方法中，该目标业务的需要同步的至少两个QoS流对应多个终端设备。
当该通信装置1000用于实现上述方法实施例中的会话管理网元的功能，处理单元1010，用于生成关联标识，该关联标识关联目标业务的需要同步的至少两个QoS流所属的数据连接会话；收发单元1020，用于向接入网设备发送该关联标识，该关联标识用于该目标业务的需要同步的至少两个QoS流的同步调度。
一种可能的实现方法中，收发单元1020，还用于向该接入网设备发送同步精度和同步状态信息，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
一种可能的实现方法中，收发单元1020，还用于接收来自策略控制网元的PCC规则，该PCC规则包括该目标业务的标识信息和该同步状态信息。
一种可能的实现方法中，收发单元1020，还用于向用户面网元发送该目标业务的需要同步的至少两个QoS流的QFI。
当该通信装置1000用于实现上述方法实施例中的会话管理网元的功能，处理单元1010，用于确定目标业务的需要同步的至少两个QoS流所属的数据连接会话；收发单元1020，用于从接入网设备接收该目标业务的需要同步的至少两个QoS流所属的数据连接会话对应的多个接入网隧道端点标识，该目标业务的需要同步的至少两个QoS流所属的数据连接会话与该多个接入网隧道端点标识一一对应；处理单元1010，还用于建立该多个接入网隧道端点标识之间的同步关系；收发单元1020，还用于向接入网设备发送该同步关系，该同步关系用于该目标业务的需要同步的至少两个QoS流的同步调度。
一种可能的实现方法中，收发单元1020，还用于向该接入网设备发送同步精度和同步状态信息，该同步状态信息用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系，该同步精度用于指示在同步状态下该目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
一种可能的实现方法中，收发单元1020，还用于接收来自策略控制网元的PCC规则，该PCC规则包括该目标业务的标识信息和该同步状态信息。
一种可能的实现方法中，收发单元1020，还用于向用户面网元发送该目标业务的需要同步的至少两个QoS流的QFI。
有关上述处理单元1010和收发单元1020更详细的描述可以直接参考上述方法实施例中相关描述直接得到，这里不加赘述。
图11所示的通信装置1100包括处理器1110和接口电路1120。处理器1110和接口电路1120之间相互耦合。可以理解的是，接口电路1120可以为收发器或输入输出接口。可选的，通信装置1100还可以包括存储器1130，用于存储处理器1110执行的指令或存储处理器1110运行指令所需要的输入数据或存储处理器1110运行指令后产生的数据。
当通信装置1100用于实现上述方法实施例时，处理器1110用于实现上述处理单元1010的功能，接口电路1120用于实现上述收发单元1020的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于基站或终端中。当然，处理器和存储介质也可以作为分立组件存在于基站或终端中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、基站、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (32)

  1. 一种同步调度方法，其特征在于，包括：
    接入网设备接收来自用户面网元的目标业务的多个数据包，所述多个数据包属于多个服务质量QoS流，所述多个数据包中的每个数据包包含服务质量流标识QFI，所述QFI用于标识所述数据包所属的QoS流，所述多个QoS流包括所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备从所述多个数据包中确定包含有相同标记信息的至少两个数据包，所述标记信息对应所述目标业务的需要同步的至少两个QoS流所属的数据连接会话；
    所述接入网设备从所述包含有相同标记信息的至少两个数据包确定至少两个目标数据包，所述至少两个目标数据包对应所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备根据所述至少两个目标数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
  2. 如权利要求1所述的方法，其特征在于，所述接入网设备接收来自用户面网元的目标业务的多个数据包之前，还包括：
    所述接入网设备接收来自会话管理网元的关联标识，所述关联标识关联所述目标业务的需要同步的至少两个QoS流所属的数据连接会话；
    所述接入网设备根据所述关联标识，为所述目标业务的需要同步的至少两个QoS流所属的数据连接会话确定所述标记信息；
    所述接入网设备通过所述会话管理网元向所述用户面网元发送所述标记信息。
  3. 如权利要求1或2所述的方法，其特征在于，
    所述标记信息是由所述接入网设备分配的组标识，所述组标识对应所述目标业务的需要同步的至少两个QoS流所属的数据连接会话。
  4. 如权利要求1或2所述的方法，其特征在于，
    所述标记信息是接入网隧道端点标识，所述接入网隧道端点标识用于标识通用无线分组业务隧道协议用户面GTP-U隧道，所述GTP-U隧道用于传输所述目标业务的需要同步的至少两个QoS流所属的数据连接会话中的QoS流。
  5. 如权利要求1所述的方法，其特征在于，
    所述标记信息包括关联标识和网络设备的标识信息，所述关联标识关联所述目标业务的需要同步的至少两个QoS流所属的数据连接会话，所述网络设备是生成所述关联标识的会话管理网元、策略控制网元或应用功能网元。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，还包括：
    所述接入网设备从会话管理网元接收所述目标业务的需要同步的至少两个QoS流的QFI；
    其中，所述至少两个目标数据包是包含有目标QFI的数据包，所述目标QFI是所述目标业务的需要同步的至少两个QoS流的QFI中的任一个。
  7. 如权利要求1至5中任一项所述的方法，其特征在于，
    所述至少两个目标数据包是包含有同步指示的数据包，所述同步指示用于指示所述数据包所属的QoS流是所述目标业务的需要同步的QoS流。
  8. 如权利要求1至7中任一项所述的方法，其特征在于，所述接入网设备根据所述至少两个目标数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，包括：
    所述接入网设备根据同步状态信息和所述至少两个目标数据包包含的帧号，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，所述同步状态信息用于指示在同步状态下所述目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
  9. 如权利要求8所述的方法，其特征在于，所述接入网设备根据同步状态信息和所述至少两个目标数据包包含的帧号，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，包括：
    所述接入网设备根据同步状态信息和所述至少两个目标数据包包含的帧号，确定所述目标业务的需要同步的至少两个QoS流不满足同步精度，则调整所述目标业务的需要同步的至少两个QoS流的数据包的发送速度，所述同步精度用于指示在同步状态下所述目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
  10. 一种同步调度方法，其特征在于，包括：
    接入网设备接收来自用户面网元的目标业务的多个数据包，所述多个数据包属于多个服务质量QoS流，所述多个数据包中的每个数据包包含服务质量流标识QFI，所述QFI用于标识所述数据包所属的QoS流，所述多个QoS流包括所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备从所述多个数据包中确定包含有相同接入网隧道端点标识的至少两个数据包，所述至少两个数据包对应所述目标业务的需要同步的至少两个QoS流，所述接入网隧道端点标识用于标识目标隧道，所述目标隧道是传输所述目标业务的需要同步的至少两个QoS流的通用无线分组业务隧道协议用户面GTP-U隧道，所述目标业务的需要同步的至少两个QoS流对应多个数据连接会话；
    所述接入网设备根据所述至少两个数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
  11. 如权利要求10所述的方法，其特征在于，所述接入网设备接收来自用户面网元的目标业务的多个数据包之前，还包括：
    所述接入网设备接收来自会话管理网元的关联标识和所述目标业务的需要同步的至少两个QoS流的QFI，所述关联标识关联所述目标业务的需要同步的至少两个QoS流所属的数据连接会话；
    所述接入网设备根据所述关联标识和所述目标业务的需要同步的至少两个QoS流的QFI，为所述目标业务的需要同步的至少两个QoS流确定所述接入网隧道端点标识；
    所述接入网设备通过所述会话管理网元向所述用户面网元发送所述接入网隧道端点标识。
  12. 如权利要求10或11所述的方法，其特征在于，所述接入网设备根据所述至少两个数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，包括：
    所述接入网设备根据同步状态信息和所述至少两个数据包包含的帧号，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，所述同步状态信息用于指示在同步状态下所述目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
  13. 如权利要求12所述的方法，其特征在于，所述接入网设备根据同步状态信息和所述至少两个数据包包含的帧号，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，包括：
    所述接入网设备根据同步状态信息和所述至少两个数据包包含的帧号，确定所述目标业务的需要同步的至少两个QoS流不满足同步精度，则调整所述目标业务的需要同步的至少两个QoS流的数据包的发送速度，所述同步精度用于指示在同步状态下所述目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
  14. 一种同步调度方法，其特征在于，包括：
    接入网设备接收来自用户面网元的目标业务的多个数据包，所述多个数据包属于多个服务质量QoS流，所述多个数据包中的每个数据包包含服务质量流标识QFI，所述QFI用于标识所述数据包所属的QoS流，所述多个QoS流包括所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备根据多个接入网隧道端点标识之间的同步关系，从所述多个数据包中确定至少两个数据包，所述至少两个数据包中的每个数据包还包含所述多个接入网隧道端点标识中的任一接入网隧道端点标识，所述多个接入网隧道端点标识分别指示的通用无线分组业务隧道协议用户面GTP-U隧道均用于传输所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备从所述至少两个数据包确定至少两个目标数据包，所述至少两个目标数据包对应所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备根据所述至少两个目标数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
  15. 如权利要求14所述的方法，其特征在于，所述接入网设备接收来自用户面网元的目标业务的多个数据包之前，还包括：
    所述接入网设备接收来自会话管理网元的关联标识，所述关联标识关联所述目标业务的需要同步的至少两个QoS流所属的数据连接会话；
    所述接入网设备为所述目标业务的需要同步的至少两个QoS流所属的数据连接会话确定所述多个接入网隧道端点标识，所述多个接入网隧道端点标识与所述目标业务的需要同步的至少两个QoS流所属的数据连接会话一一对应；
    所述接入网设备根据所述关联标识，建立所述同步关系。
  16. 如权利要求14所述的方法，其特征在于，所述接入网设备接收来自用户面网元的目标业务的多个数据包之前，还包括：
    所述接入网设备为所述目标业务的需要同步的至少两个QoS流所属的数据连接会话确定所述多个接入网隧道端点标识，所述多个接入网隧道端点标识与所述目标业务的需要同步的至少两个QoS流所属的数据连接会话一一对应；
    所述接入网设备向会话管理网元发送所述多个接入网隧道端点标识；
    所述接入网设备从所述会话管理网元接收所述同步关系。
  17. 如权利要求14至16中任一项所述的方法，其特征在于，还包括：
    所述接入网设备接收来自所述会话管理网元的所述目标业务的需要同步的至少两个QoS流的QFI；
    其中，所述至少两个目标数据包指的是包含有目标QFI的数据包，所述目标QFI是所 述目标业务的需要同步的至少两个QoS流的QFI中的任一个。
  18. 如权利要求14至17中任一项所述的方法，其特征在于，
    所述至少两个目标数据包指的是包含有同步指示的数据包，所述同步指示用于指示所述数据包所属的QoS流是所述目标业务的需要同步的QoS流。
  19. 如权利要求14至18中任一项所述的方法，其特征在于，所述接入网设备根据所述至少两个目标数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，包括：
    所述接入网设备根据同步状态信息和所述至少两个目标数据包包含的帧号，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，所述同步状态信息用于指示在同步状态下所述目标业务的需要同步的至少两个QoS流的数据包中的帧号之间的对应关系。
  20. 如权利要求19所述的方法，其特征在于，所述接入网设备根据同步状态信息和所述至少两个目标数据包包含的帧号，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度，包括：
    所述接入网设备根据同步状态信息和所述至少两个目标数据包包含的帧号，确定所述目标业务的需要同步的至少两个QoS流不满足同步精度，则调整所述目标业务的需要同步的至少两个QoS流的数据包的发送速度，所述同步精度用于指示在同步状态下所述目标业务的需要同步的至少两个QoS流的数据包的帧号的偏差。
  21. 一种同步调度方法，其特征在于，包括：
    用户面网元接收来自应用功能网元的目标业务的多个数据包，所述多个数据包属于多个服务质量QoS流，所述多个QoS流包括所述目标业务的需要同步的至少两个QoS流；
    所述用户面网元在所述多个数据包的至少两个数据包中添加标记信息和服务质量流标识QFI，所述至少两个数据包的每个数据包中的QFI用于标识所述数据包所属的QoS流，所述标记信息对应所述目标业务的需要同步的至少两个QoS流所属的数据连接会话；
    所述用户面网元向接入网设备发送包含添加的所述标记信息和QFI的至少两个数据包的多个数据包。
  22. 如权利要求21所述的方法，其特征在于，
    所述用户面网元接收来自所述接入网设备的所述标记信息。
  23. 如权利要求21或22所述的方法，其特征在于，
    所述标记信息是由所述接入网设备分配的组标识，所述组标识对应所述目标业务的需要同步的至少两个QoS流所属的数据连接会话。
  24. 如权利要求21或22所述的方法，其特征在于，
    所述标记信息是接入网隧道端点标识，所述接入网隧道端点标识用于标识通用无线分组业务隧道协议用户面GTP-U隧道，所述GTP-U隧道用于传输所述目标业务的需要同步的至少两个QoS流所属的数据连接会话中的QoS流。
  25. 如权利要求21所述的方法，其特征在于，
    所述标记信息包括关联标识和网络设备的标识信息，所述关联标识关联所述目标业务的需要同步的至少两个QoS流所属的数据连接会话，所述网络设备是生成所述关联标识的会话管理网元、策略控制网元或应用功能网元。
  26. 如权利要求21至25中任一项所述的方法，其特征在于，还包括：
    所述用户面网元接收来自会话管理网元的所述目标业务的需要同步的至少两个QoS流的QFI；
    所述用户面网元向接入网设备发送包含添加的所述标记信息和QFI的至少两个数据包的多个数据包之前，还包括：
    所述用户面网元根据所述目标业务的需要同步的至少两个QoS流的QFI，在所述至少两个数据包的至少两个目标数据包中添加同步指示，所述至少两个目标数据包对应所述目标业务的需要同步的至少两个QoS流，所述同步指示用于指示所述目标数据包所属的QoS流是所述目标业务的需要同步的至少两个QoS流。
  27. 如权利要求26所述的方法，其特征在于，所述至少两个目标数据包均包含帧号，所述帧号用于所述目标业务的需要同步的至少两个QoS流的同步调度。
  28. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至9中任一项所述的方法，或用于实现如权利要求10至13中任一项所述的方法，或用于实现如权利要求14至20中任一项所述的方法，或用于实现如权利要求21至27中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机可读程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至27中任一项所述方法。
  30. 一种通信系统，其特征在于，包括：用户面网元，和用于执行权利要求1至9、或10至13、或14至20中任一项所述方法的接入网设备；
    所述用户面网元，用于向所述接入网设备发送目标业务的多个数据包。
  31. 一种同步调度方法，其特征在于，包括：
    用户面网元向接入网设备发送目标业务的多个数据包，所述多个数据包属于多个服务质量QoS流，所述多个数据包中的每个数据包包含服务质量流标识QFI，所述QFI用于标识所述数据包所属的QoS流，所述多个QoS流包括所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备从所述多个数据包中确定包含有相同标记信息的至少两个数据包，所述标记信息对应所述目标业务的需要同步的至少两个QoS流所属的数据连接会话；
    所述接入网设备从所述包含有相同标记信息的至少两个数据包确定至少两个目标数据包，所述至少两个目标数据包对应所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备根据所述至少两个目标数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
  32. 一种同步调度方法，其特征在于，包括：
    用户面网元向接入网设备发送目标业务的多个数据包，所述多个数据包属于多个服务质量QoS流，所述多个数据包中的每个数据包包含服务质量流标识QFI，所述QFI用于标识所述数据包所属的QoS流，所述多个QoS流包括所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备根据多个接入网隧道端点标识之间的同步关系，从所述多个数据包中确定至少两个数据包，所述至少两个数据包中的每个数据包还包含所述多个接入网隧道端 点标识中的任一接入网隧道端点标识，所述多个接入网隧道端点标识分别指示的通用无线分组业务隧道协议用户面GTP-U隧道均用于传输所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备从所述至少两个数据包确定至少两个目标数据包，所述至少两个目标数据包对应所述目标业务的需要同步的至少两个QoS流；
    所述接入网设备根据所述至少两个目标数据包，对所述目标业务的需要同步的至少两个QoS流的数据包进行同步调度。
PCT/CN2022/137958 2022-03-18 2022-12-09 一种同步调度方法、通信装置及通信系统 WO2023173841A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210270603.8A CN116828580A (zh) 2022-03-18 2022-03-18 一种同步调度方法、通信装置及通信系统
CN202210270603.8 2022-03-18

Publications (1)

Publication Number Publication Date
WO2023173841A1 true WO2023173841A1 (zh) 2023-09-21

Family

ID=88022148

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/137958 WO2023173841A1 (zh) 2022-03-18 2022-12-09 一种同步调度方法、通信装置及通信系统

Country Status (2)

Country Link
CN (1) CN116828580A (zh)
WO (1) WO2023173841A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113596929A (zh) * 2020-04-30 2021-11-02 华为技术有限公司 一种通信方法及装置
WO2022026649A1 (en) * 2020-07-30 2022-02-03 Weihua Qiao Synchronization for multiple data flows
WO2022048773A1 (en) * 2020-09-04 2022-03-10 Nokia Solutions And Networks Oy Method and apparatus to synchronize radio bearers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113596929A (zh) * 2020-04-30 2021-11-02 华为技术有限公司 一种通信方法及装置
WO2022026649A1 (en) * 2020-07-30 2022-02-03 Weihua Qiao Synchronization for multiple data flows
WO2022048773A1 (en) * 2020-09-04 2022-03-10 Nokia Solutions And Networks Oy Method and apparatus to synchronize radio bearers

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "QoS Framework Update", 3GPP DRAFT; R2-1800543 DRAFT CR QOS FRAMEWORK UPDATE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Vancouver, Canada; 20180122 - 20180126, 12 January 2018 (2018-01-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051386205 *

Also Published As

Publication number Publication date
CN116828580A (zh) 2023-09-29

Similar Documents

Publication Publication Date Title
US11463280B2 (en) Communication method and device
US10973000B2 (en) Message sending method and apparatus
JP2020508597A (ja) 情報フィードバック方法および装置
WO2021140464A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
WO2022033558A1 (zh) 一种中继管理方法及通信装置
CN113573355B (zh) 通信方法和装置
CN113630902B (zh) 基于网络服务质量的数据包传输方法及相关设备
KR20230008870A (ko) 통신 방법, 장치, 및 시스템
WO2019024650A1 (zh) 一种资源配置方法和装置
WO2021069552A1 (en) Identifying time sensitive network streams within a 3gpp qos flow
WO2023116772A1 (zh) 一种卫星切换方法、装置、存储介质和芯片系统
WO2024174752A1 (zh) 一种数据传输方法及装置
CN112636884B (zh) 一种消息传输方法和装置
WO2023173841A1 (zh) 一种同步调度方法、通信装置及通信系统
WO2022267652A1 (zh) 一种通信方法、通信装置及通信系统
WO2022257629A1 (zh) 一种无线通信方法及通信装置
WO2023284551A1 (zh) 通信方法、装置和系统
WO2018054336A1 (zh) 消息的发送方法和装置
CN114424498B (zh) 数据传输方法、装置、系统和存储介质
US20230038925A1 (en) Qos flow configuration for user equipment to user equipment communications
WO2021174376A1 (zh) 一种通信方法及装置
WO2021042381A1 (zh) 一种通信方法、装置及系统
WO2024012376A1 (zh) 一种通信方法、通信装置及通信系统
WO2023179331A1 (zh) 一种发送数据包的方法、通信装置及通信系统
WO2023185402A1 (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: 22931850

Country of ref document: EP

Kind code of ref document: A1