Data transmission method, apparatus, and device

Abstract

The present disclosure relates to the technical field of communications, and provides a data transmission method, apparatus, and device. The data transmission method comprises: on the basis of local time, performing timestamp identification on an uplink data packet; and sending the identified uplink data packet to a base station.

Description

Data transmission method, device and equipment

[0001] This disclosure claims priority to a Chinese patent application filed with the Patent Office of China on June 26, 2023, with application number 202310759498.9 and application name “A Data Transmission Method, Device and Equipment,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present disclosure relates to the field of communication technology, and in particular to a data transmission method, apparatus, and device. Background Art

[0003] In current technology, the User Plan Function (UPF) primarily identifies Protocol Data Unit (PDU) sets to assist the 5th Generation (5G) Radio Access Network (NG-RAN) in resource scheduling. However, there is no solution for the User Equipment (UE) to process uplink data (for example, it cannot timestamp the uplink data stream) to assist the base station in synchronous resource scheduling.

[0004] As described above, the related art has problems such as the UE being unable to assist the base station in performing synchronous resource scheduling by marking timestamps for uplink data flows.

[0005] Summary of the Invention

[0006] The present disclosure aims to provide a data transmission method, apparatus and device to solve the problem in the related art that a UE cannot assist a base station in performing synchronous resource scheduling by marking a timestamp for an uplink data stream.

[0007] In order to solve the above technical problems, an embodiment of the present disclosure provides a data transmission method, which is applied to a terminal, including:

[0008] Timestamp the uplink data packets according to the local time;

[0009] Send the marked uplink data packet to the base station.

[0010] In some embodiments, before timestamping the uplink data packet according to the local time, the method further includes:

[0011] Receive target time related information sent by network equipment;

[0012] Adjust the local time according to the target time related information until it is synchronized with the target server time or the target clock source;

[0013] The timestamp marking of the uplink data packet according to the local time includes:

[0014] timestamp an uplink data packet corresponding to at least one data stream according to the adjusted local time;

[0015] The data flow is an associated data flow; the associated data flow is a data flow for the terminal to execute a target service, or a data flow for the terminal and other terminals to jointly execute a target service.

[0016] In some embodiments, the target time related information is carried in at least one of the following information:

[0017] Network Time Protocol NTP messages;

[0018] Stream synchronization control strategy.

[0019] In some embodiments, timestamping the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes:

[0020] Using the first method, timestamping the uplink data packets corresponding to at least one data stream according to the adjusted local time;

[0021] The first method includes at least one of the following:

[0022] Mark the timestamp in the protocol data unit (PDU) IP header;

[0023] Mark the timestamp in the Packet Data Convergence Protocol (PDCP) header;

[0024] The timestamp is marked in the radio link layer control protocol RLC header.

[0025] In some embodiments, timestamping the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes:

[0026] Using a first marking granularity, and according to the adjusted local time, timestamp an uplink data packet corresponding to at least one data flow;

[0027] The first marking granularity includes at least one of the following:

[0028] Frame granularity;

[0029] Protocol data unit set granularity;

[0030] Protocol Data Unit (PDU) granularity.

[0031] In some embodiments, before receiving the target time related information sent by the network device, the method further includes:

[0032] Send synchronization request to network device;

[0033] The synchronization request is used to request synchronization of the terminal to a target server.

[0034] In some embodiments, the target time related information is target server information, and the data transmission method further includes:

[0035] Receive the stream synchronization control strategy sent by the network device;

[0036] The sending of a synchronization request to the network device includes:

[0037] Send a synchronization request to the network device according to the target server information.

[0038] The present disclosure also provides a data transmission method, which is applied to a network device and includes:

[0039] determining target time related information for providing a reference time for at least one terminal;

[0040] sending the target time related information to the at least one terminal;

[0041] The terminal is a terminal corresponding to at least one data flow, and the data flow is an associated data flow; the associated data flow refers to a data flow for a terminal to execute a target service, or refers to a data flow for at least two terminals to jointly execute a target service.

[0042] In some embodiments, the target time related information is carried in at least one of the following information:

[0043] Network Time Protocol NTP messages;

[0044] Stream synchronization control strategy.

[0045] In some embodiments, determining target time-related information for providing a reference time for at least one terminal includes:

[0046] receiving a synchronization request sent by at least one terminal;

[0047] determining, based on the synchronization request, target time related information for providing a reference time for at least one terminal;

[0048] The synchronization request is used to request synchronization with a target server.

[0049] In some embodiments, determining, based on the synchronization request, target time-related information for providing a reference time for at least one terminal includes:

[0050] Replacing the first destination address in the packet header of the synchronization request with the address of the target server and sending the request to the target server; receiving response information from the target server and obtaining target time related information for providing a reference time for at least one terminal;

[0051] Alternatively, target time related information for providing reference time for at least one terminal is obtained according to the synchronization request and a timestamp marked by the target clock source.

[0052] In some embodiments, before determining target time related information for providing a reference time for at least one terminal according to the synchronization request, the method further includes:

[0053] In the case where at least one data flow is determined to be a related data flow, information of the target server or information of the target clock source is determined.

[0054] In some embodiments, when the first target address of the packet header of the synchronization request is replaced with the address of the target server, before sending the target time related information to the at least one terminal, the method further includes:

[0055] Replacing the second destination address of the packet header of the response information with the first destination address to obtain a first request response;

[0056] The sending the target time related information to the at least one terminal includes:

[0057] Sending the first request response to the terminal that sends the synchronization request.

[0058] In some embodiments, the timestamp based on the target clock source marking includes: a first timestamp and a second timestamp based on the target clock source marking;

[0059] The first timestamp is the first time when the network device receives the synchronization request; and the second timestamp is the second time when the network device sends a response corresponding to the synchronization request.

[0060] In some embodiments, the target time related information is target server information, and the data transmission method further includes:

[0061] Sending stream synchronization control strategy to the terminal;

[0062] Wherein, the stream synchronization control strategy includes: target server information.

[0063] The present disclosure also provides a data transmission device, which is a terminal and includes a memory, a transceiver, and a processor.

[0064] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0065] Timestamp the uplink data packets according to the local time;

[0066] The marked uplink data packet is sent to the base station through the transceiver.

[0067] In some embodiments, the operations further include:

[0068] Before timestamping the uplink data packet according to the local time, receiving target time related information sent by the network device through the transceiver;

[0069] Adjust the local time according to the target time related information until it is synchronized with the target server time or the target clock source;

[0070] The timestamp marking of the uplink data packet according to the local time includes:

[0071] timestamp an uplink data packet corresponding to at least one data stream according to the adjusted local time;

[0072] The data flow is an associated data flow; the associated data flow is a data flow for the terminal to execute a target service, or a data flow for the terminal and other terminals to jointly execute a target service.

[0073] In some embodiments, the target time related information is carried in at least one of the following information:

[0074] Network Time Protocol NTP messages;

[0075] Stream synchronization control strategy.

[0076] In some embodiments, timestamping the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes:

[0077] Using the first method, timestamping the uplink data packets corresponding to at least one data stream according to the adjusted local time;

[0078] The first method includes at least one of the following:

[0079] Mark the timestamp in the protocol data unit (PDU) IP header;

[0080] Mark the timestamp in the Packet Data Convergence Protocol (PDCP) header;

[0081] The timestamp is marked in the radio link layer control protocol RLC header.

[0082] In some embodiments, timestamping the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes:

[0083] Using a first marking granularity, and according to the adjusted local time, timestamp an uplink data packet corresponding to at least one data flow;

[0084] The first marking granularity includes at least one of the following:

[0085] Frame granularity;

[0086] Protocol data unit set granularity;

[0087] Protocol Data Unit (PDU) granularity.

[0088] In some embodiments, the operations further include:

[0089] Before receiving the target time related information sent by the network device, sending a synchronization request to the network device through the transceiver;

[0090] The synchronization request is used to request synchronization of the terminal to a target server.

[0091] In some embodiments, the target time related information is target server information, and the operation further includes:

[0092] Receiving, via the transceiver, a stream synchronization control strategy sent by a network device;

[0093] The sending of a synchronization request to the network device includes:

[0094] Send a synchronization request to the network device according to the target server information.

[0095] The present disclosure also provides a data transmission device, which is a network device and includes a memory, a transceiver, and a processor.

[0096] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0097] determining target time related information for providing a reference time for at least one terminal;

[0098] sending, via the transceiver, the target time related information to the at least one terminal;

[0099] The terminal is a terminal corresponding to at least one data flow, and the data flow is an associated data flow; the associated data flow refers to a data flow for a terminal to execute a target service, or refers to a data flow for at least two terminals to jointly execute a target service.

[0100] In some embodiments, the target time related information is carried in at least one of the following information:

[0101] Network Time Protocol NTP messages;

[0102] Stream synchronization control strategy.

[0103] In some embodiments, determining target time-related information for providing a reference time for at least one terminal includes:

[0104] receiving, by the transceiver, a synchronization request sent by at least one terminal;

[0105] determining, based on the synchronization request, target time related information for providing a reference time for at least one terminal;

[0106] The synchronization request is used to request synchronization with a target server.

[0107] In some embodiments, determining, based on the synchronization request, target time-related information for providing a reference time for at least one terminal includes:

[0108] Replacing the first destination address in the packet header of the synchronization request with the address of the target server and sending the request to the target server via the transceiver; receiving response information from the target server via the transceiver to obtain target time related information for providing a reference time for at least one terminal;

[0109] Alternatively, target time related information for providing reference time for at least one terminal is obtained according to the synchronization request and a timestamp marked by the target clock source.

[0110] In some embodiments, the operations further include:

[0111] Before determining target time related information for providing reference time for at least one terminal according to the synchronization request, when at least one data stream is determined to be an associated data stream, information of the target server or information of the target clock source is determined.

[0112] In some embodiments, the operations further include:

[0113] In a case where the first destination address of the packet header of the synchronization request is replaced with the address of the target server, before sending the target time related information to the at least one terminal, the second destination address of the packet header of the response information is replaced with the first destination address to obtain a first request response;

[0114] The sending the target time related information to the at least one terminal includes:

[0115] Sending the first request response to the terminal that sends the synchronization request.

[0116] In some embodiments, the timestamp based on the target clock source marking includes: a first timestamp and a second timestamp based on the target clock source marking;

[0117] The first timestamp is the first time when the network device receives the synchronization request; and the second timestamp is the second time when the network device sends a response corresponding to the synchronization request.

[0118] In some embodiments, the target time related information is target server information, and the operation further includes:

[0119] sending a stream synchronization control strategy to a terminal via the transceiver;

[0120] Wherein, the stream synchronization control strategy includes: target server information.

[0121] The present disclosure also provides a data transmission device, which is applied to a terminal and includes:

[0122] A first processing unit, configured to timestamp an uplink data packet according to a local time;

[0123] The first sending unit is configured to send a marked uplink data packet to a base station.

[0124] In some embodiments, it further includes:

[0125] The first receiving unit is configured to receive target time related information sent by the network device before timestamping the uplink data packet according to the local time;

[0126] A first adjustment unit, configured to adjust the local time according to the target time related information until the local time is synchronized with the time of the target server or the target clock source;

[0127] The timestamp marking of the uplink data packet according to the local time includes:

[0128] timestamp an uplink data packet corresponding to at least one data stream according to the adjusted local time;

[0129] The data flow is an associated data flow; the associated data flow is a data flow for the terminal to execute a target service, or a data flow for the terminal and other terminals to jointly execute a target service.

[0130] In some embodiments, the target time related information is carried in at least one of the following information:

[0131] Network Time Protocol NTP messages;

[0132] Stream synchronization control strategy.

[0133] In some embodiments, timestamping the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes:

[0134] Using the first method, timestamping the uplink data packets corresponding to at least one data stream according to the adjusted local time;

[0135] The first method includes at least one of the following:

[0136] Mark the timestamp in the protocol data unit (PDU) IP header;

[0137] Mark the timestamp in the Packet Data Convergence Protocol (PDCP) header;

[0138] The timestamp is marked in the radio link layer control protocol RLC header.

[0139] In some embodiments, timestamping the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes:

[0140] Using a first marking granularity, and according to the adjusted local time, timestamp an uplink data packet corresponding to at least one data flow;

[0141] The first marking granularity includes at least one of the following:

[0142] Frame granularity;

[0143] Protocol data unit set granularity;

[0144] Protocol Data Unit (PDU) granularity.

[0145] In some embodiments, it further includes:

[0146] a second sending unit, configured to send a synchronization request to the network device before receiving target time related information sent by the network device;

[0147] The synchronization request is used to request synchronization of the terminal to a target server.

[0148] In some embodiments, the target time related information is target server information, and the data transmission device further includes:

[0149] A second receiving unit, configured to receive a flow synchronization control strategy sent by a network device;

[0150] The sending of a synchronization request to the network device includes:

[0151] Send a synchronization request to the network device according to the target server information.

[0152] The present disclosure also provides a data transmission device, which is applied to a network device and includes:

[0153] A first determining unit, configured to determine target time related information for providing a reference time for at least one terminal;

[0154] A third sending unit, configured to send the target time related information to the at least one terminal;

[0155] The terminal is a terminal corresponding to at least one data flow, and the data flow is an associated data flow; the associated data flow refers to a data flow for a terminal to execute a target service, or refers to a data flow for at least two terminals to jointly execute a target service.

[0156] In some embodiments, the target time related information is carried in at least one of the following information:

[0157] Network Time Protocol NTP messages;

[0158] Stream synchronization control strategy.

[0159] In some embodiments, determining target time-related information for providing a reference time for at least one terminal includes:

[0160] receiving a synchronization request sent by at least one terminal;

[0161] determining, based on the synchronization request, target time related information for providing a reference time for at least one terminal;

[0162] The synchronization request is used to request synchronization with a target server.

[0163] In some embodiments, determining, based on the synchronization request, target time-related information for providing a reference time for at least one terminal includes:

[0164] Replacing the first destination address in the packet header of the synchronization request with the address of the target server and sending the request to the target server; receiving response information from the target server and obtaining target time related information for providing a reference time for at least one terminal;

[0165] Alternatively, target time related information for providing reference time for at least one terminal is obtained according to the synchronization request and a timestamp marked by the target clock source.

[0166] In some embodiments, it further includes:

[0167] The second determining unit is configured to determine the target server information or the target clock source information when it is determined that at least one data stream is an associated data stream before determining the target time related information for providing a reference time for at least one terminal according to the synchronization request.

[0168] In some embodiments, it further includes:

[0169] a second processing unit, configured to, after replacing the first destination address of the packet header of the synchronization request with the address of the target server, replace the second destination address of the packet header of the response information with the first destination address before sending the target time related information to the at least one terminal, thereby obtaining a first request response;

[0170] The sending the target time related information to the at least one terminal includes:

[0171] Sending the first request response to the terminal that sends the synchronization request.

[0172] In some embodiments, the timestamp based on the target clock source marking includes: a first timestamp and a second timestamp based on the target clock source marking;

[0173] The first timestamp is the first time when the network device receives the synchronization request; and the second timestamp is the second time when the network device sends a response corresponding to the synchronization request.

[0174] In some embodiments, the target time related information is target server information, and the data transmission device further includes:

[0175] A third sending unit, configured to send a stream synchronization control policy to a terminal;

[0176] Wherein, the stream synchronization control strategy includes: target server information.

[0177] An embodiment of the present disclosure further provides a readable storage medium, wherein the readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the above-mentioned terminal side or network device side method.

[0178] The beneficial effects of the above technical solutions disclosed herein are as follows:

[0179] In the above scheme, the data transmission method uses the terminal to timestamp the uplink data packet according to the local time; sends the marked uplink data packet to the base station; and can support the terminal to timestamp the uplink data stream, thereby assisting the base station in performing synchronous resource scheduling, which effectively solves the problem in related technologies that the UE cannot assist the base station in performing synchronous resource scheduling by timestamping the uplink data stream. BRIEF DESCRIPTION OF THE DRAWINGS

[0180] FIG1 is a schematic diagram of a wireless communication system architecture according to an embodiment of the present disclosure;

[0181] FIG2 is a flowchart of a data transmission method according to an embodiment of the present disclosure;

[0182] FIG3 is a second flow chart of a data transmission method according to an embodiment of the present disclosure;

[0183] FIG4 is a schematic diagram of a first embodiment of a data transmission method according to an embodiment of the present disclosure;

[0184] FIG5 is a second schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;

[0185] FIG6 is a third schematic diagram of a specific implementation flow of the data transmission method according to an embodiment of the present disclosure;

[0186] FIG7 is a first structural diagram of a data transmission device according to an embodiment of the present disclosure;

[0187] FIG8 is a second structural diagram of a data transmission device according to an embodiment of the present disclosure;

[0188] FIG9 is a first structural diagram of a data transmission device according to an embodiment of the present disclosure;

[0189] FIG10 is a second structural diagram of the data transmission device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0190] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0191] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0192] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.

[0193] It is explained here that the technical solutions provided by the embodiments of the present disclosure can be applicable to a variety of systems, especially 5G systems. For example, applicable systems can be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G new air interface (NR) systems, etc. These various systems all include terminal devices and base stations. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5G System, 5GS), etc.

[0194] Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present disclosure may be applied. The wireless communication system includes a terminal device (also referred to as a terminal) and a base station.

[0195] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, or a user device, but is not limited in the embodiments of the present disclosure.

[0196] The base station involved in the embodiments of the present disclosure may include multiple cells that provide services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The base station can be used to interchange received air frames with Internet Protocol (IP) packets, and act as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The base station can also coordinate the attribute management of the air interface. For example, the base station involved in the embodiments of the present disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB) in Wide-band Code Division Multiple Access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (the next generation Node B, gNB) in the 5G network architecture, a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. In some network structures, the base station may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0197] The base station and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO. It can also use diversity transmission, precoding transmission, or beamforming transmission.

[0198] The following first introduces the contents involved in the solution provided by the embodiment of the present disclosure.

[0199] (1) Main network functions in the 5G system (5GS) architecture;

[0200] Access and Mobility Management Function (AMF): used for registration, connection management, etc.

[0201] User Plan Function (UPF): An external Protocol Data Unit (PDU) session node that interconnects with the data network and is used for message routing and forwarding.

[0202] Session Management Function (SMF): used for session establishment and deletion, user plane selection and control, UE IP allocation, etc.

[0203] Network Exposure Function (NEF): Provides functions related to securely exposing services and capabilities provided by the 3rd Generation Partnership Project (3GPP) network to external networks.

[0204] Application Function (AF): Used to interact with the 3GPP core network to provide services. Based on operator deployment, trusted AFs can interact directly with relevant network functions (NFs), while untrusted AFs cannot interact directly with NFs and must use an open framework through the NEF.

[0205] Policy Control Function (PCF): Supports a unified policy framework to manage network behavior and provides policy rules for execution by the control plane NF.

[0206] Network Repository Function (NRF): Supports service discovery.

[0207] Unified Data Management (UDM): used to store UE information, such as subscription information and information about established PDU sessions.

[0208] Radio Access Network (RAN): used for UE to access the network.

[0209] (2) 5G Extended Reality (XR);

[0210] In current 5G networks, there are more and more high data rate and low latency (HDRLL) services, such as mobile multimedia services, cloud augmented reality (AR) or virtual reality (VR), cloud gaming, video-based remote-controlled machines or drones, and real-time digital twins.

[0211] 5G networks require the transmission of different types of service data, and the data units transmitted between peer layers are typically PDUs. The data units involved in the XR service transmission data flow are as follows:

[0212] PDU set: A media unit of an XR service, which may contain a frame, or one or more slices, slice segments, or tiles.

[0213] Data frame: can contain one or more PDU sets.

[0214] Data packet: can be a PDU. A PDU set or data frame can contain one or more data packets (PDUs).

[0215] (3) Network Time Protocol (NTP);

[0216] NTP is a currently defined time synchronization protocol. It is used to synchronize time between distributed time servers and clients. The purpose of using NTP is to synchronize the clocks of all devices with the clock on the network, ensuring that all devices on the network maintain consistent clocks and can provide multiple applications based on a unified time. NTP obtains time from atomic clocks, observatories, satellites, or the internet. An NTP client sends a time request and exchanges time with a time server. As a result of this exchange, the client calculates the time delay and the corresponding offset value, and adjusts the synchronization with the server time.

[0217] (4) resource scheduling;

[0218] Currently, 5G XR supports AF to provide a common ID (universal identifier) ​​to configure the multi-data flow requirements for a single UE or multiple UEs to the network, implement policy enhancements to support multi-flow collaborative transmission on the control plane, and ensure that the transmission delay difference of multiple data flows is within a certain range. In addition, the UPF can identify PDU sets and mark PDU set related information (including PDU Set Sequence Number, End PDU of the PDU Set, PDU SN within a PDU Set, PDU Set Size in bytes, PDU Set Importance, etc.) on the user plane General Packet Radio Service Tunnelling Protocol (GPRS Tunnelling Protocol for the user plane, GTP-U) and send it to the 5G Radio Access Network (NG-RAN) to assist NG-RAN in resource scheduling at the PDU Set granularity.

[0219] In current technologies, it is impossible to perform user plane time synchronization and coordinated processing for associated data streams (eg, multiple data streams associated with a specific service) sent by the same or different terminals (User Equipment, UE), and the base station cannot perform synchronous resource scheduling.

[0220] Based on the foregoing, embodiments of the present disclosure provide a data transmission method, apparatus, and device to address the related art issue of a UE being unable to assist a base station in synchronous resource scheduling by timestamping uplink data streams. The method, apparatus, and device are based on the same patent application concept. Since the principles underlying the problems solved by the method, apparatus, and device are similar, their implementations can be referenced to each other, and any repetitions will not be repeated.

[0221] The data transmission method provided in the embodiment of the present disclosure is applied to a terminal, as shown in FIG2 , and includes:

[0222] Step 21: Timestamp the uplink data packet according to the local time;

[0223] Step 22: Send the marked uplink data packet to the base station.

[0224] The data transmission method provided by the embodiment of the present disclosure uses a terminal to timestamp the uplink data packet according to the local time; sends the marked uplink data packet to the base station; and can support the terminal to timestamp the uplink data stream, thereby assisting the base station in performing synchronous resource scheduling, which effectively solves the problem in related technologies that the UE cannot assist the base station in performing synchronous resource scheduling by timestamping the uplink data stream.

[0225] Furthermore, before timestamping the uplink data packet according to the local time, it also includes: receiving target time-related information sent by the network device; adjusting the local time according to the target time-related information until it is synchronized with the time of the target server or the target clock source; timestamping the uplink data packet according to the local time includes: timestamping the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein the data stream is an associated data stream; the associated data stream is a data stream for the terminal to execute the target service, or a data stream for the terminal and other terminals to jointly execute the target service.

[0226] This allows the terminal to timestamp the associated data stream based on the synchronized time, better assisting the base station in scheduling synchronization resources. The target time-related information includes a timestamp based on the target server's time or target clock source, and may also include, but is not limited to, relevant information about the target server, such as address information.

[0227] The target time related information is carried in at least one of the following information: a Network Time Protocol NTP message; a stream synchronization control strategy.

[0228] This can support multiple modes of transmitting target time related information.

[0229] In an embodiment of the present disclosure, the timestamp marking of the uplink data packet corresponding to at least one data stream according to the adjusted local time includes: adopting a first method to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein, the first method includes at least one of the following: marking the timestamp in the protocol data unit network association PDU IP header; marking the timestamp in the packet data convergence protocol PDCP header; marking the timestamp in the radio link layer control protocol (Radio Link Control, RLC) header.

[0230] This allows for multiple timestamps to be supported.

[0231] Among them, the timestamp marking of the uplink data packet corresponding to at least one data stream according to the adjusted local time includes: using a first marking granularity to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein, the first marking granularity includes at least one of the following: frame granularity; protocol data unit set granularity; protocol data unit PDU granularity.

[0232] This can support timestamp marking at multiple granularities. Among them, the marking at the frame granularity may include: the absolute time of the local clock corresponding to the moment when the first data packet of each data frame is received is used as the timestamp corresponding to the data frame; the timestamps of all data packets in each data frame are the same, but not limited to this. The marking at the PDU set granularity may include: the absolute time of the local clock corresponding to the moment when the first data packet of each PDU set is received is used as the timestamp corresponding to the PDU set; the timestamps of all data packets in each PDU set are the same, but not limited to this. The marking at the PDU granularity may include: determining the order of data packets based on the timestamp and sequence number contained in the real-time transport protocol (RTP) header, and marking the timestamps in sequence, but not limited to this.

[0233] Furthermore, before receiving the target time related information sent by the network device, it also includes: sending a synchronization request to the network device; wherein the synchronization request is used to request that the terminal be synchronized to the target server.

[0234] This allows the terminal to proactively synchronize time.

[0235] Among them, the target time related information is the target server information, and the data transmission method also includes: receiving the stream synchronization control strategy (carrying the target time related information) sent by the network device; sending a synchronization request to the network device includes: sending a synchronization request to the network device according to the target server information.

[0236] In this way, the synchronization request can be accurately initiated. The target server information can be the target server address, but is not limited thereto.

[0237] The present disclosure also provides a data transmission method, which is applied to a network device, as shown in FIG3 , and includes:

[0238] Step 31: Determine target time related information for providing a reference time for at least one terminal;

[0239] Step 32: Send the target time related information to the at least one terminal; wherein the terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to perform a target service, or refers to a data stream for at least two terminals to jointly perform a target service.

[0240] The terminal may adjust the local time (of the terminal) according to the reference time (corresponding to the terminal adjusting the local time according to the target time related information), but the present invention is not limited thereto.

[0241] The data transmission method provided by the embodiment of the present disclosure determines target time related information for providing a reference time for at least one terminal; sends the target time related information to the at least one terminal; wherein the terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to perform a target service, or refers to a data stream for at least two terminals to jointly perform a target service; it can support the time synchronization of the terminal and mark the uplink data stream with a timestamp accordingly, thereby assisting the base station in performing synchronous resource scheduling, which well solves the problem in the related technology that the UE cannot assist the base station in performing synchronous resource scheduling by marking the uplink data stream with a timestamp.

[0242] The target time related information is carried in at least one of the following information: a Network Time Protocol NTP message; a stream synchronization control strategy.

[0243] This can support multiple modes of transmitting target time related information.

[0244] In an embodiment of the present disclosure, determining target time-related information for providing a reference time for at least one terminal includes: receiving a synchronization request sent by at least one terminal; determining target time-related information for providing a reference time for at least one terminal based on the synchronization request; wherein the synchronization request is used to request synchronization with a target server.

[0245] This allows the terminal to proactively synchronize time.

[0246] The method of determining target time-related information for providing a reference time for at least one terminal based on the synchronization request includes: (1) replacing the first target address of the packet header of the synchronization request with the address of the target server and sending the information to the target server; receiving response information from the target server to obtain target time-related information for providing a reference time for at least one terminal; or (2) obtaining target time-related information for providing a reference time for at least one terminal based on the synchronization request and a timestamp marked by a target clock source.

[0247] In this way, target time related information can be obtained in multiple ways.

[0248] Furthermore, before determining target time related information for providing reference time for at least one terminal according to the synchronization request, it also includes: when determining that at least one data stream is an associated data stream, determining information of the target server or information of the target clock source.

[0249] This supports accurate acquisition of target time related information.

[0250] In an embodiment of the present disclosure, when the first target address of the packet header of the synchronization request is replaced with the address of the target server, before sending the target time related information to the at least one terminal, it also includes: replacing the second target address of the packet header of the response information with the first target address to obtain a first request response; sending the target time related information to the at least one terminal includes: sending the first request response (carrying the target time related information) to the terminal that sends the synchronization request.

[0251] This allows target time related information to be fed back to the terminal.

[0252] Among them, the timestamp based on the target clock source mark includes: a first timestamp and a second timestamp based on the target clock source mark; wherein, the first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

[0253] In this way, the target time-related information can be accurately obtained based on the timestamp marked by the target clock source.

[0254] Furthermore, the target time related information is target server information, and the data transmission method further includes: sending a stream synchronization control strategy to the terminal; wherein the stream synchronization control strategy includes: target server information.

[0255] This can support the terminal to accurately initiate a synchronization request. The target server information can be the target server address, but is not limited thereto.

[0256] The data transmission method provided in the embodiment of the present disclosure is illustrated below with an example, where the target server is an NTP (Network Time Protocol) time server and the target clock source is a 5G clock.

[0257] In response to the above technical problems, the embodiments of the present disclosure provide a data transmission method, which can be specifically implemented as a method for supporting stream synchronization, which can support the 5G system to time synchronize data streams sent by the same or different UEs, and mark timestamps based on different methods and granularities to assist the base station in optimizing resource scheduling. Specifically: This solution mainly synchronizes a group of UEs (whether the UE belongs to a group can be determined based on the UE ID and / or packet detection rule (Packet Detection Rule, PDR)) (synchronize to the same clock source). Among them, the synchronization method includes at least one of the following:

[0258] 1) The UPF (corresponding to the above-mentioned network device) obtains the NTP time server request synchronization information from (a group of) UEs (corresponding to the above-mentioned reception of the synchronization request sent by at least one terminal), replaces the destination address (corresponding to the above-mentioned first destination address) of the (NTP time server request synchronization information) data packet header with the same NTP (time) server address (corresponding to the address of the above-mentioned target server), and implements time synchronization of a group of associated UEs to the same clock source (the same NTP time server);

[0259] 2) The UPF obtains the NTP time server synchronization request information from (a group of) UEs, and uses the 5G clock (clock) as the clock source to mark the timestamp in the NTP information (i.e., the NTP time server synchronization request information) (corresponding to the timestamp marked based on the target clock source, to obtain target time related information for providing reference time for at least one terminal), thereby achieving time synchronization of a group of associated UEs to the same clock source (5G clock);

[0260] 3) The AF or PCF (corresponding to the above network device) sends a UE policy (corresponding to the above stream synchronization control policy) to the UE, which includes the NTP time server address (corresponding to the above target server information) to achieve time synchronization of a group of associated UEs to the same clock source (the same NTP time server).

[0261] Afterwards, the UE can send the timestamp-marked data packet to the NG-RAN based on the synchronized time (corresponding to the above-mentioned timestamping of the uplink data packet corresponding to at least one data stream according to the adjusted local time; and sending the marked uplink data packet to the base station).

[0262] Among them, there are three ways for the UE to mark the timestamp (corresponding to the first method mentioned above): 1) mark the timestamp in the PDU IP header and send it to the NG-RAN through the Uu interface (the interface between the terminal and the base station); 2) mark the timestamp in the Packet Data Convergence Protocol (PDCP) header and send it to the NG-RAN through the NR-Uu (the interface between the terminal and the base station); 3) mark the timestamp in the Radio Link Control Protocol (RLC) header and send it to the NG-RAN through the NR-Uu.

[0263] The following is a specific example of this solution.

[0264] Example 1

[0265] This embodiment introduces that the UE sends an application layer request (corresponding to the above-mentioned synchronization request) to request synchronization information from the NTP time server. The UPF obtains requests from different UEs and replaces the destination address of the data packet header with the same NTP (time) server address (corresponding to replacing the first destination address of the synchronization request header with the address of the target server) to achieve time synchronization of a group of associated UEs to the same clock source (the same NTP (time) server). This solution indicates the same NTP address through the user plane. Specifically, as shown in Figure 4, it includes the following steps:

[0266] 0. The control plane network function NF (such as AF, PCF, AMF or SMF) configures flow synchronization processing instructions to the UPF, gNB, and UE respectively.

[0267] 1. The UE sends an NTP message (this message corresponds to the above synchronization request) to the NTP time server. The message contains an Originate timestamp field whose value is T1, that is, the time when the UE sent the message is T1.

[0268] Specifically, the UE sends an NTP message to the NTP time server through the UPF:

[0269] (1) The UE sends an NTP message to the UPF.

[0270] (2) The UPF receives the NTP message and determines, based on the PDR and / or UE ID, that the data stream sent by the UE needs to be synchronized (for example, determining the specific target NTP time server to which synchronization is required), to determine the target NTP time server address. In some embodiments, the UPF obtains the PDR, UE ID, target NTP time server address (for example, IP address, port number), stream synchronization processing instructions, etc. based on policy control and charging (PCC) rules. The target NTP (time) server address can also be locally configured.

[0271] UPF replaces the destination address of the NTP message data packet (corresponding to the first destination address above, such as: NTP1 IP, port number 1) with the target NTP time server address (corresponding to the address of the target server above, such as: NTP2 IP, port number 2).

[0272] (3) UPF sends the NTP message to the target NTP time server.

[0273] The above (2) and (3) correspond to replacing the first target address of the packet header of the synchronization request with the address of the target server and sending it to the target server.

[0274] 2. The UPF receives an NTP message from the target NTP time server (corresponding to the above-mentioned receipt of the response information from the target server, and obtaining target time-related information for providing a reference time for at least one terminal). The received NTP message includes timestamp information (for example, the Receive timestamp field in the NTP message header marks the time T2 when the message was received, and the Transmit timestamp field marks the time T3 when the NTP message was sent).

[0275] In some embodiments, the UPF replaces the destination address of the packet header of the received NTP reply message (i.e., the received NTP message) (corresponding to the above-mentioned second destination address, such as: NTP2 IP, port number 2) with the address indicated by the original UE (i.e., the source NTP server address, corresponding to the above-mentioned first destination address, such as: NTP1 IP, port number 1); corresponding to the above-mentioned replacement of the second destination address of the packet header of the response information with the first destination address, a first request response is obtained.

[0276] 3. The UPF replies the NTP message to the UE; this may correspond to sending the first request response to the terminal that sent the synchronization request.

[0277] 4. The UE adjusts the local time based on the timestamp included in the NTP message to synchronize with the target NTP time server (corresponding to the above-mentioned adjustment of the local time according to the target time-related information until it is synchronized with the time of the target server).

[0278] Specifically, the UE may determine that synchronization processing and / or timestamp need to be performed on this data stream based on the synchronization processing indication received from the SMF or AMF (the indication may be: the SMF calls the N1N2 message transmission Namf_Communication_N1N2MessageTransfer to transmit the non-access layer (NAS)-session management (SM) protocol containing the synchronization processing indication to the UE through the AMF, or the SMF sends it to the AMF, and then the AMF sends it to the UE through the non-access layer mobility management (NAS-MM) protocol). The UE timestamps the uplink data packet based on the adjusted local time.

[0279] There are three ways for the UE to mark the timestamp (corresponding to the first way described above, the uplink data packet corresponding to at least one data flow is timestamped according to the adjusted local time):

[0280] 1) Mark the timestamp in the PDU IP header and send it to the NG-RAN via the Uu interface;

[0281] 2) Mark the timestamp in the PDCP header and send it to the NG-RAN via NR-Uu;

[0282] 3) Mark the timestamp in the RLC header and send it to NG-RAN via NR-Uu.

[0283] The timestamp marking granularity may be one of the following three types (corresponding to the first marking granularity described above, the uplink data packet corresponding to at least one data flow is timestamped according to the adjusted local time):

[0284] 1) Frame granularity: The absolute time of the local clock corresponding to the moment the first data packet of each data frame is received is used as the timestamp of the data frame. The timestamp of all data packets in each data frame is the same.

[0285] 2) PDU set granularity: The absolute time of the local clock corresponding to the moment the first packet of each PDU set is received is used as the timestamp corresponding to the PDU set. The timestamp of all packets in each PDU set is the same.

[0286] 3) PDU granularity: The order of data packets is determined based on the timestamp and sequence number contained in the Real-time Transport Protocol (RTP) header, and the timestamps are marked in sequence.

[0287] 5. The UE sends the timestamp-marked uplink data packet to the NG-RAN (corresponding to the above-mentioned sending of the marked uplink data packet to the base station).

[0288] 6. NG-RAN receives the uplink data flow sent by the UE and performs resource synchronization scheduling based on the QoS profile (quality of service file) received from the SMF or AMF.

[0289] Example 2

[0290] This embodiment describes a scenario in which a UE sends an application layer request (corresponding to the synchronization request described above) to an NTP time server for synchronization information. The UPF receives requests from different UEs to timestamp the NTP information using the 5G clock as the clock source and responds to the UEs via application layer NTP information, thereby synchronizing a group of associated UEs to the same clock source (5G clock). This solution uses the user plane to indicate the 5G clock. Specifically, as shown in Figure 5, it includes the following steps:

[0291] 0. The Control Plane NF (such as AF, PCF, AMF or SMF) configures flow synchronization processing instructions to the UPF, gNB, and UE respectively.

[0292] 1. The UE sends an NTP message (clock synchronization message) to the NTP time server. The message contains the Originate timestamp field, whose value is T1, that is, the time when the UE sent the message is T1. Specifically, the UE sends the message to the NTP time server, and the destination address of the message is the time NTP server. It can be understood that the network (UPF) is an information transmission channel, that is, the UE sends the message to the NTP time server through the UPF.

[0293] 2. The UPF receives the NTP message and determines, based on the PDR and / or UE ID, that the data stream sent by the UE needs to be synchronized (e.g., to the 5G clock). In some embodiments, the UPF obtains the PDR, UE ID, and stream synchronization indication based on PCC rules.

[0294] The UPF synchronizes the UE with the 5G clock (local clock) as the clock source. Specifically, the timestamp is marked in the NTP packet header based on the 5G clock, including: marking the time T2 (corresponding to the above-mentioned first timestamp) of the received message in the Receive timestamp field of the NTP message header, and marking the time T3 (corresponding to the above-mentioned second timestamp) of the sending NTP message in the Transmit timestamp field; corresponding to the above-mentioned synchronization request and the timestamp marked based on the target clock source, the target time-related information for providing a reference time for at least one terminal is obtained; the timestamp marked based on the target clock source includes: the first timestamp and the second timestamp marked based on the target clock source; wherein the first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

[0295] 3. The UPF sends the NTP message marked with the timestamp to the UE; this corresponds to the above-mentioned sending of the target time related information to the at least one terminal.

[0296] 4. The UE adjusts the local time based on the timestamp contained in the NTP message to synchronize with the 5G clock (corresponding to adjusting the local time based on the target time-related information until the target clock source is synchronized). The UE timestamps the uplink data packet based on the adjusted local time.

[0297] There are three ways for the UE to mark the timestamp (corresponding to the first way described above, the uplink data packet corresponding to at least one data flow is timestamped according to the adjusted local time):

[0298] 1) Mark the timestamp in the PDU IP header and send it to the NG-RAN via the Uu interface;

[0299] 2) Mark the timestamp in the PDCP header and send it to the NG-RAN via NR-Uu;

[0300] 3) Mark the timestamp in the RLC header and send it to NG-RAN via NR-Uu.

[0301] The timestamp marking granularity may be one of the following three types (corresponding to the first marking granularity described above, the uplink data packet corresponding to at least one data flow is timestamped according to the adjusted local time):

[0302] 1) Frame granularity: The absolute time of the local clock corresponding to the moment the first data packet of each data frame is received is used as the timestamp of the data frame. The timestamp of all data packets in each data frame is the same.

[0303] 2) PDU set granularity: The absolute time of the local clock corresponding to the moment the first packet of each PDU set is received is used as the timestamp corresponding to the PDU set. The timestamp of all packets in each PDU set is the same.

[0304] 3) PDU granularity: The order of data packets is determined based on the timestamp and sequence number contained in the Real-time Transport Protocol (RTP) header, and the timestamps are marked in sequence.

[0305] 5. The UE sends the timestamp-marked uplink data packet to the NG-RAN (corresponding to the above-mentioned sending of the marked uplink data packet to the base station).

[0306] 6. NG-RAN receives the uplink data flow sent by the UE and performs resource synchronization scheduling based on the QoS profile (quality of service file) received from the SMF or AMF.

[0307] Example 3

[0308] This embodiment describes how the AF or PCF (corresponding to the aforementioned network device) sends a UE policy (corresponding to the aforementioned stream synchronization control policy) to a group of UEs associated with a specific application, indicating the NTP time server address (i.e., synchronizing to a specific NTP time server). This solution uses the control plane to indicate the same NTP address. Specifically, as shown in Figure 6, it includes the following steps:

[0309] 1. The AF sends the flow control policy (corresponding to the above-mentioned flow synchronization control policy) to the PCF. The flow control policy includes the target NTP time server information (corresponding to the above-mentioned target time-related information, such as IP address, port number) and AF Identifier.

[0310] 2. PCF calls the Namf_Communication_N1N2MessageTransfer service operation to send the flow control policy to AMF.

[0311] 3. The AMF sends the UE Policy container containing the flow control policy to the UE (corresponding to the above-mentioned sending of the flow synchronization control policy to the terminal). Steps 1-3 can be performed before or after the PDU session is established, and are not limited here.

[0312] 4. The UE synchronizes to the target NTP and identifies the timestamp. Specifically, based on the received policy (target NTP time server information), the UE sends an NTP message to the target NTP time server to synchronize to the target NTP time server (for details, see steps 1 to 4 of Example 1, but are not limited thereto). The UE timestamps the uplink data packet based on the adjusted local time.

[0313] There are three ways for the UE to mark the timestamp (corresponding to the first way described above, the uplink data packet corresponding to at least one data flow is timestamped according to the adjusted local time):

[0314] 1) Mark the timestamp in the PDU IP header and send it to the NG-RAN via the Uu interface;

[0315] 2) Mark the timestamp in the PDCP header and send it to the NG-RAN via NR-Uu;

[0316] 3) Mark the timestamp in the RLC header and send it to NG-RAN via NR-Uu.

[0317] The timestamp marking granularity may be one of the following three types (corresponding to the first marking granularity described above, the uplink data packet corresponding to at least one data flow is timestamped according to the adjusted local time):

[0318] 1) Frame granularity: The absolute time of the local clock corresponding to the moment the first data packet of each data frame is received is used as the timestamp of the data frame. The timestamp of all data packets in each data frame is the same.

[0319] 2) PDU set granularity: The absolute time of the local clock corresponding to the moment the first packet of each PDU set is received is used as the timestamp corresponding to the PDU set. The timestamp of all packets in each PDU set is the same.

[0320] 3) PDU granularity: The order of data packets is determined based on the timestamp and sequence number contained in the Real-time Transport Protocol (RTP) header, and the timestamps are marked in sequence.

[0321] 5. The UE sends the timestamp-marked uplink data packet to the NG-RAN (corresponding to the above-mentioned sending of the marked uplink data packet to the base station).

[0322] 6. NG-RAN receives the uplink data flow sent by the UE and performs resource synchronization scheduling based on the Quality of Service (QoS) profile received from the SMF or AMF.

[0323] Based on the above, the solutions provided by the embodiments of the present disclosure involve the following contents:

[0324] 1. UE side;

[0325] 1. The UE timestamps the uplink data packet based on the synchronized time.

[0326] 2. Before executing 1, the UE synchronizes to the target NTP time server based on the received policy (target NTP time server information).

[0327] 3. Based on 1, there are three ways for the UE to mark the timestamp, including marking the timestamp in the PDU IP header, PDCP header and / or RLC header.

[0328] 4. Based on 1, there are three granularities for UE timestamp marking: frame granularity, PDU set granularity, and PDU granularity.

[0329] 2. UPF side;

[0330] 1. The UPF modifies the destination address of the NTP time server synchronization request packet header sent by the UE, and replaces it with the same NTP (time) server address (corresponding to the above embodiment 1).

[0331] 2. The UPF modifies the timestamp in the header of the NTP time server synchronization request packet sent by the UE, and uses the 5G clock as the clock source to mark the timestamp in the NTP information (corresponding to the above-mentioned embodiment 2).

[0332] 3. Before executing 1 or 2, the UPF confirms that the UE belongs to a specific association group and needs to synchronize this data stream (for example, it can subsequently determine the specific target NTP time server or 5G clock to which synchronization needs to be performed); corresponding to the above-mentioned case of determining that at least one data stream is an associated data stream, determining the information of the target server or the information of the target clock source.

[0333] 4. Based on 1, the UPF replaces the destination address in the header of the received NTP reply message data packet with the address originally indicated by the UE (corresponding to the above-mentioned first destination address).

[0334] 5. Based on 2, UPF marks the time when the message is received in the Receive timestamp field of the NTP message header, and marks the time when the NTP message is sent in the Transmit timestamp field.

[0335] 3. Control plane function (such as AF, PCF or SMF) side;

[0336] The AF, PCF, or SMF sends a UE policy to the UE, which includes the NTP time server address, to ensure that a group of associated UEs are synchronized to the same clock source (the same NTP time server).

[0337] It should be noted that the aforementioned group of UEs does not necessarily refer to multiple UEs. This solution is intended for synchronization of associated data streams. If multiple data streams (associated data streams) are from the same UE, then the operation in the aforementioned embodiment is to adjust the local time for each data stream, timestamp the data packet, and then transmit it, but this is not a limitation. Furthermore, the relevant content between the aforementioned embodiments can be referenced across each other, and the relevant content between the terminal side and the network device side can also be referenced across each other. Any repetitions will not be repeated here.

[0338] In summary, the present disclosure proposes a method that supports the 5G system to time synchronize data streams (including XR or non-XR data streams, encrypted data or non-encrypted data) sent by the same or different UEs, and to mark timestamps based on different methods and granularities to assist the base station in optimizing resource scheduling.

[0339] The embodiment of the present disclosure further provides a data transmission device, which is a terminal, as shown in FIG7 , including a memory 71 , a transceiver 72 , and a processor 73 :

[0340] The memory 71 is used to store computer programs; the transceiver 72 is used to send and receive data under the control of the processor 73; the processor 73 is used to read the computer program in the memory 71 and perform the following operations:

[0341] Timestamp the uplink data packets according to the local time;

[0342] The marked uplink data packet is sent to the base station through the transceiver 72.

[0343] The data transmission device provided in the embodiment of the present disclosure timestamps the uplink data packet according to the local time through the terminal; sends the marked uplink data packet to the base station; and can support the terminal to timestamp the uplink data stream, thereby assisting the base station in performing synchronous resource scheduling, which effectively solves the problem in related technologies that the UE cannot assist the base station in performing synchronous resource scheduling by timestamping the uplink data stream.

[0344] Specifically, the transceiver 72 is used to receive and send data under the control of the processor 73.

[0345] In FIG7 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 73 and various circuits of memory represented by memory 71. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 72 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 74 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0346] The processor 73 is responsible for managing the bus architecture and general processing, and the memory 71 can store data used by the processor 73 when performing operations.

[0347] In some embodiments, the processor 73 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0348] The processor calls the computer program stored in the memory to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0349] Furthermore, the operation also includes: before timestamping the uplink data packet according to the local time, receiving target time-related information sent by the network device through the transceiver; adjusting the local time according to the target time-related information until it is synchronized with the time of the target server or the target clock source; timestamping the uplink data packet according to the local time includes: timestamping the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein the data stream is an associated data stream; the associated data stream is a data stream for the terminal to execute the target service, or a data stream for the terminal and other terminals to jointly execute the target service.

[0350] The target time related information is carried in at least one of the following information: a Network Time Protocol NTP message; a stream synchronization control strategy.

[0351] In an embodiment of the present disclosure, the timestamp marking of the uplink data packet corresponding to at least one data stream according to the adjusted local time includes: adopting a first method to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein, the first method includes at least one of the following: marking the timestamp in the protocol data unit network association PDU IP header; marking the timestamp in the packet data convergence protocol PDCP header; marking the timestamp in the radio link layer control protocol RLC header.

[0352] Among them, the timestamp marking of the uplink data packet corresponding to at least one data stream according to the adjusted local time includes: using a first marking granularity to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein, the first marking granularity includes at least one of the following: frame granularity; protocol data unit set granularity; protocol data unit PDU granularity.

[0353] Furthermore, the operation also includes: before receiving the target time related information sent by the network device, sending a synchronization request to the network device through the transceiver; wherein the synchronization request is used to request synchronization of the terminal to the target server.

[0354] In the embodiment of the present disclosure, the target time related information is target server information, and the operation also includes: receiving the stream synchronization control strategy sent by the network device through the transceiver; sending a synchronization request to the network device includes: sending a synchronization request to the network device according to the target server information.

[0355] It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can implement all the method steps implemented by the above-mentioned terminal-side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0356] The present disclosure also provides a data transmission device, which is a network device, as shown in FIG8 , including a memory 81 , a transceiver 82 , and a processor 83 :

[0357] The memory 81 is used to store computer programs; the transceiver 82 is used to send and receive data under the control of the processor 83; the processor 83 is used to read the computer program in the memory 81 and perform the following operations:

[0358] determining target time related information for providing a reference time for at least one terminal;

[0359] sending the target time related information to the at least one terminal via the transceiver 82;

[0360] The terminal is a terminal corresponding to at least one data flow, and the data flow is an associated data flow; the associated data flow refers to a data flow for a terminal to execute a target service, or refers to a data flow for at least two terminals to jointly execute a target service.

[0361] The data transmission device provided by the embodiment of the present disclosure determines target time related information for providing a reference time for at least one terminal; sends the target time related information to the at least one terminal; wherein the terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to perform a target service, or refers to a data stream for at least two terminals to jointly perform a target service; it can support the time synchronization of the terminal and mark the uplink data stream with a timestamp accordingly, thereby assisting the base station in performing synchronous resource scheduling, which well solves the problem in the related technology that the UE cannot assist the base station in performing synchronous resource scheduling by marking the uplink data stream with a timestamp.

[0362] Specifically, the transceiver 82 is used to receive and send data under the control of the processor 83.

[0363] In FIG8 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 83 and various circuits of memory represented by memory 81. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 82 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. The processor 83 is responsible for managing the bus architecture and general processing, and the memory 81 may store data used by the processor 83 when performing operations.

[0364] The processor 83 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0365] The target time related information is carried in at least one of the following information: a Network Time Protocol NTP message; a stream synchronization control strategy.

[0366] In an embodiment of the present disclosure, the determination of target time-related information for providing a reference time for at least one terminal includes: receiving a synchronization request sent by at least one terminal through the transceiver; determining target time-related information for providing a reference time for at least one terminal based on the synchronization request; wherein the synchronization request is used to request synchronization with a target server.

[0367] The method of determining target time related information for providing reference time for at least one terminal based on the synchronization request includes: (1) replacing the first target address of the packet header of the synchronization request with the address of the target server, and sending the target time related information to the target server through the transceiver; receiving the response information of the target server through the transceiver to obtain target time related information for providing reference time for at least one terminal; or (2) obtaining target time related information for providing reference time for at least one terminal based on the synchronization request and the timestamp marked by the target clock source.

[0368] Furthermore, the operation also includes: before determining the target time-related information for providing reference time for at least one terminal according to the synchronization request, when it is determined that at least one data stream is an associated data stream, determining the information of the target server or the information of the target clock source.

[0369] In an embodiment of the present disclosure, the operation also includes: when the first target address of the packet header of the synchronization request is replaced with the address of the target server, before sending the target time related information to the at least one terminal, the second target address of the packet header of the response information is replaced with the first target address to obtain a first request response; sending the target time related information to the at least one terminal includes: sending the first request response to the terminal that sends the synchronization request.

[0370] Among them, the timestamp based on the target clock source mark includes: a first timestamp and a second timestamp based on the target clock source mark; wherein, the first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

[0371] In the embodiment of the present disclosure, the target time related information is target server information, and the operation further includes: sending a stream synchronization control strategy to the terminal through the transceiver; wherein the stream synchronization control strategy includes: target server information.

[0372] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned network device side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0373] The present disclosure also provides a data transmission device, which is applied to a terminal, as shown in FIG9 , and includes:

[0374] The first processing unit 91 is configured to timestamp the uplink data packet according to the local time;

[0375] The first sending unit 92 is configured to send the marked uplink data packet to the base station.

[0376] The data transmission device provided in the embodiment of the present disclosure uses the terminal to timestamp the uplink data packet according to the local time; sends the marked uplink data packet to the base station; and can support the terminal to timestamp the uplink data stream, thereby assisting the base station in performing synchronous resource scheduling, which effectively solves the problem in related technologies that the UE cannot assist the base station in performing synchronous resource scheduling by timestamping the uplink data stream.

[0377] Furthermore, the data transmission device also includes: a first receiving unit, used to receive target time-related information sent by the network device before timestamping the uplink data packet according to the local time; a first adjustment unit, used to adjust the local time according to the target time-related information until it is synchronized with the time of the target server or the target clock source; timestamping the uplink data packet according to the local time, including: timestamping the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein the data stream is an associated data stream; the associated data stream is a data stream for the terminal to execute the target service, or a data stream for the terminal and other terminals to jointly execute the target service.

[0378] The target time related information is carried in at least one of the following information: a Network Time Protocol NTP message; a stream synchronization control strategy.

[0379] In the embodiment of the present disclosure, the timestamp identification of the uplink data packet corresponding to the at least one data stream according to the adjusted local time includes: adopting a first manner to timestamp identification of the uplink data packet corresponding to the at least one data stream according to the adjusted local time;

[0380] The first method includes at least one of the following: marking the timestamp in the protocol data unit (PDU) IP header; marking the timestamp in the packet data convergence protocol (PDCP) header; marking the timestamp in the radio link layer control protocol (RLC) header.

[0381] Among them, the timestamp marking of the uplink data packet corresponding to at least one data stream according to the adjusted local time includes: using a first marking granularity to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time; wherein, the first marking granularity includes at least one of the following: frame granularity; protocol data unit set granularity; protocol data unit PDU granularity.

[0382] Furthermore, the data transmission device also includes: a second sending unit, used to send a synchronization request to the network device before receiving the target time related information sent by the network device; wherein, the synchronization request is used to request that the terminal be synchronized to the target server.

[0383] In an embodiment of the present disclosure, the target time-related information is target server information, and the data transmission device also includes: a second receiving unit for receiving a stream synchronization control strategy sent by a network device; sending a synchronization request to the network device includes: sending a synchronization request to the network device according to the target server information.

[0384] It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can implement all the method steps implemented by the above-mentioned terminal-side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0385] The present disclosure also provides a data transmission device, which is applied to a network device, as shown in FIG10 , and includes:

[0386] The first determining unit 101 is configured to determine target time related information for providing a reference time for at least one terminal;

[0387] The third sending unit 102 is configured to send the target time related information to the at least one terminal;

[0388] The terminal is a terminal corresponding to at least one data flow, and the data flow is an associated data flow; the associated data flow refers to a data flow for a terminal to execute a target service, or refers to a data flow for at least two terminals to jointly execute a target service.

[0389] The data transmission device provided by the embodiment of the present disclosure determines target time related information for providing a reference time for at least one terminal; sends the target time related information to the at least one terminal; wherein the terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to perform a target service, or refers to a data stream for at least two terminals to jointly perform a target service; it can support the time synchronization of the terminal and mark the uplink data stream with a timestamp accordingly, thereby assisting the base station in performing synchronous resource scheduling, which well solves the problem in the related technology that the UE cannot assist the base station in performing synchronous resource scheduling by marking the uplink data stream with a timestamp.

[0390] The target time related information is carried in at least one of the following information: a Network Time Protocol NTP message; a stream synchronization control strategy.

[0391] In an embodiment of the present disclosure, determining target time-related information for providing a reference time for at least one terminal includes: receiving a synchronization request sent by at least one terminal; determining target time-related information for providing a reference time for at least one terminal based on the synchronization request; wherein the synchronization request is used to request synchronization with a target server.

[0392] The method of determining target time-related information for providing a reference time for at least one terminal based on the synchronization request includes: (1) replacing the first target address of the packet header of the synchronization request with the address of the target server and sending the information to the target server; receiving response information from the target server to obtain target time-related information for providing a reference time for at least one terminal; or (2) obtaining target time-related information for providing a reference time for at least one terminal based on the synchronization request and a timestamp marked by a target clock source.

[0393] Furthermore, the data transmission device also includes: a second determination unit, which is used to determine the information of the target server or the information of the target clock source when it is determined that at least one data stream is an associated data stream before determining the target time-related information for providing a reference time for at least one terminal based on the synchronization request.

[0394] In an embodiment of the present disclosure, the data transmission device further includes: a second processing unit, which is used to replace the first target address of the packet header of the synchronization request with the address of the target server, and before sending the target time related information to the at least one terminal, replace the second target address of the packet header of the response information with the first target address to obtain a first request response; sending the target time related information to the at least one terminal includes: sending the first request response to the terminal that sends the synchronization request.

[0395] Among them, the timestamp based on the target clock source mark includes: a first timestamp and a second timestamp based on the target clock source mark; wherein, the first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

[0396] In the embodiment of the present disclosure, the target time related information is target server information, and the data transmission device further includes: a third sending unit, configured to send a stream synchronization control strategy to the terminal; wherein the stream synchronization control strategy includes: target server information.

[0397] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned network device side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0398] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0399] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0400] An embodiment of the present disclosure further provides a non-transitory readable storage medium storing a computer program, wherein the computer program is used to enable a processor to execute the above-mentioned terminal side or network device side method.

[0401] The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as compact discs (CD), digital video discs (DVD), Blu-ray discs (BD), high-definition versatile discs (HVD), etc.), and semiconductor storage (such as ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND (Non-volatile Memory Device) FLASH), solid-state drives (SSD)), etc.

[0402] Among them, the implementation embodiments of the above-mentioned methods on the terminal side or the network device side are all applicable to the embodiments of the non-transitory readable storage medium and can also achieve the same technical effects.

[0403] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0404] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0405] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0406] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0407] It should be noted that it should be understood that the division of the above modules is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by a processing element; or they can all be implemented in the form of hardware; or some modules can be implemented in the form of software called by a processing element, and some modules can be implemented in the form of hardware. For example, the determination module can be a separately established processing element, or it can be integrated into a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and called by a processing element of the above-mentioned device to perform the functions of the above-mentioned determination module. The implementation of other modules is similar. In addition, these modules can all or partly be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the hardware integrated logic circuit in the processor element or by instructions in the form of software.

[0408] For example, each module, unit, sub-unit or sub-module can be one or more integrated circuits configured to implement the above method, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented by scheduling program code through a processing element, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0409] The terms "first," "second," and the like in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure described herein may be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units need not be limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, for example, A and / or B and / or C, means that seven situations are included: A alone, B alone, C alone, both A and B present, both B and C present, both A and C present, and all A, B, and C present. Similarly, the use of "at least one of A and B" in the specification and claims should be understood to mean "A alone, B alone, or both A and B present."

[0410] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. A data transmission method, applied to a terminal, the method comprising: Timestamp the uplink data packets according to the local time; Send the marked uplink data packet to the base station.

2. The data transmission method according to claim 1, wherein: Before timestamping the uplink data packet according to the local time, the following steps are also included: Receiving target time related information sent by network equipment; According to the target time related information, the local time is adjusted until it is synchronized with the time of the target server or the target clock source; The step of timestamping the uplink data packet according to the local time includes: Performing a timestamp on an uplink data packet corresponding to at least one data stream according to the adjusted local time; The data flow is an associated data flow; the associated data flow is a data flow for the terminal to execute a target service, or a data flow for the terminal and other terminals to jointly execute a target service.

3. The data transmission method according to claim 2, wherein: The target time related information is carried in at least one of the following information: Network Time Protocol NTP messages; Stream synchronization control strategy.

4. The data transmission method according to claim 2, wherein: The step of timestamping an uplink data packet corresponding to at least one data stream according to the adjusted local time includes: In a first manner, a timestamp is performed on an uplink data packet corresponding to at least one data stream according to the adjusted local time; The first method includes at least one of the following: Mark the timestamp in the protocol data unit (PDU) IP header; Mark the timestamp in the Packet Data Convergence Protocol (PDCP) header; The timestamp is marked in the radio link layer control protocol RLC header.

5. The data transmission method according to claim 2, wherein: The step of timestamping an uplink data packet corresponding to at least one data stream according to the adjusted local time includes: Using a first marking granularity, and according to the adjusted local time, timestamp an uplink data packet corresponding to at least one data flow; The first marking granularity includes at least one of the following: Frame granularity; Protocol data unit set granularity; Protocol Data Unit (PDU) granularity.

6. The data transmission method according to claim 2, wherein: Before receiving the target time related information sent by the network device, it also includes: Send synchronization request to network device; The synchronization request is used to request synchronization of the terminal to a target server.

7. The data transmission method according to claim 6, wherein: The target time related information is target server information, and the data transmission method further includes: Receive the stream synchronization control strategy sent by the network device; The sending of a synchronization request to the network device comprises: According to the target server information, a synchronization request is sent to the network device.

8. A data transmission method, applied to a network device, the method comprising: determining target time related information for providing a reference time for at least one terminal; Sending the target time related information to the at least one terminal; The terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to execute a target service, or refers to a data stream for at least two terminals to jointly execute a target service.

9. The data transmission method according to claim 8, wherein: The target time related information is carried in at least one of the following information: Network Time Protocol NTP messages; Stream synchronization control strategy.

10. The data transmission method according to claim 8, wherein: The determining of target time related information for providing a reference time for at least one terminal includes: receiving a synchronization request sent by at least one terminal; Determine, according to the synchronization request, a target time phase for providing a reference time for at least one terminal. About information; The synchronization request is used to request synchronization with a target server.

11. The data transmission method according to claim 10, wherein: The determining, according to the synchronization request, target time related information for providing a reference time for at least one terminal comprises: Replacing the first target address of the packet header of the synchronization request with the address of the target server and sending the address to the target server; receiving response information from the target server to obtain target time related information for providing reference time for at least one terminal; Alternatively, target time related information for providing reference time for at least one terminal is obtained according to the synchronization request and a timestamp marked by a target clock source.

12. The data transmission method according to claim 11, wherein: Before determining, according to the synchronization request, target time related information for providing a reference time for at least one terminal, the method further includes: In the case where at least one data stream is determined to be a related data stream, information of the target server or information of the target clock source is determined.

13. The data transmission method according to claim 11, wherein: In the case where the first target address of the packet header of the synchronization request is replaced with the address of the target server, before sending the target time related information to the at least one terminal, the method further includes: Replacing the second target address of the packet header of the response information with the first target address to obtain a first request response; The sending the target time related information to the at least one terminal includes: The first request response is sent to the terminal that sends the synchronization request.

14. The data transmission method according to claim 11, wherein: The timestamp based on the target clock source mark includes: a first timestamp and a second timestamp based on the target clock source mark; The first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

15. The data transmission method according to claim 8, wherein: The target time related information is target server information, and the data transmission method further includes: Sending stream synchronization control strategy to the terminal; Wherein, the stream synchronization control strategy includes: target server information.

16. A data transmission device, the data transmission device being a terminal, comprising a memory, a transceiver, and a processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Timestamp the uplink data packets according to the local time; The marked uplink data packet is sent to the base station through the transceiver.

17. The data transmission device according to claim 16, wherein: The operations also include: Before timestamping the uplink data packet according to the local time, receiving target time related information sent by the network device through the transceiver; According to the target time related information, the local time is adjusted until it is synchronized with the time of the target server or the target clock source; The step of timestamping the uplink data packet according to the local time includes: Performing a timestamp on an uplink data packet corresponding to at least one data stream according to the adjusted local time; The data flow is an associated data flow; the associated data flow is a data flow for the terminal to execute a target service, or a data flow for the terminal and other terminals to jointly execute a target service.

18. The data transmission device according to claim 17, wherein: The target time related information is carried in at least one of the following information: Network Time Protocol NTP messages; Stream synchronization control strategy.

19. The data transmission device according to claim 17, wherein: The step of timestamping an uplink data packet corresponding to at least one data stream according to the adjusted local time includes: In a first manner, a timestamp is performed on an uplink data packet corresponding to at least one data stream according to the adjusted local time; The first method includes at least one of the following: Mark the timestamp in the protocol data unit (PDU) IP header; Mark the timestamp in the Packet Data Convergence Protocol (PDCP) header; The timestamp is marked in the radio link layer control protocol RLC header.

20. The data transmission device according to claim 17, wherein: The step of timestamping an uplink data packet corresponding to at least one data stream according to the adjusted local time includes: Using a first marking granularity, and according to the adjusted local time, timestamp an uplink data packet corresponding to at least one data flow; The first marking granularity includes at least one of the following: Frame granularity; Protocol data unit set granularity; Protocol Data Unit (PDU) granularity.

21. The data transmission device according to claim 17, wherein: The operations also include: Before receiving the target time related information sent by the network device, sending a synchronization request to the network device through the transceiver; The synchronization request is used to request synchronization of the terminal to a target server.

22. The data transmission device according to claim 21, wherein: The target time related information is target server information, and the operation further includes: Receiving, by the transceiver, a stream synchronization control strategy sent by a network device; The sending of a synchronization request to the network device comprises: According to the target server information, a synchronization request is sent to the network device.

23. A data transmission device, the data transmission device being a network device, wherein: Including memory, transceiver, processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: determining target time related information for providing a reference time for at least one terminal; sending, by the transceiver, the target time related information to the at least one terminal; The terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to execute a target service, or refers to a data stream for at least two terminals to jointly execute a target service.

24. The data transmission device according to claim 23, wherein: The target time related information is carried in at least one of the following information: Network Time Protocol NTP messages; Stream synchronization control strategy.

25. The data transmission device according to claim 23, wherein: The determining of target time related information for providing a reference time for at least one terminal includes: Receiving, by the transceiver, a synchronization request sent by at least one terminal; Determining, according to the synchronization request, target time related information for providing a reference time for at least one terminal; The synchronization request is used to request synchronization with a target server.

26. The data transmission device according to claim 25, wherein: The determining, according to the synchronization request, target time related information for providing a reference time for at least one terminal comprises: Replacing the first target address of the packet header of the synchronization request with the address of the target server and sending the address to the target server through the transceiver; receiving the response information of the target server through the transceiver to obtain the target time related information for providing a reference time for at least one terminal; Alternatively, target time related information for providing reference time for at least one terminal is obtained according to the synchronization request and a timestamp marked by a target clock source.

27. The data transmission device according to claim 26, wherein: The operations also include: Before determining target time related information for providing reference time for at least one terminal according to the synchronization request, when at least one data stream is determined to be an associated data stream, information of the target server or information of the target clock source is determined.

28. The data transmission device according to claim 26, wherein: The operations also include: In the case where the first target address of the packet header of the synchronization request is replaced with the address of the target server, before sending the target time related information to the at least one terminal, the second target address of the packet header of the response information is replaced with the first target address to obtain a first request response; The sending the target time related information to the at least one terminal includes: The first request response is sent to the terminal that sends the synchronization request.

29. The data transmission device according to claim 26, wherein: The timestamp based on the target clock source mark includes: a first timestamp and a second timestamp based on the target clock source mark; The first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

30. The data transmission device according to claim 23, wherein: The target time related information is target server information, and the operation further includes: Sending a stream synchronization control strategy to a terminal via the transceiver; Wherein, the stream synchronization control strategy includes: target server information.

31. A data transmission device, applied to a terminal, the data transmission device comprising: A first processing unit, configured to timestamp an uplink data packet according to a local time; The first sending unit is used to send a marked uplink data packet to a base station.

32. The data transmission device according to claim 31, further comprising: A first receiving unit is used to receive target time related information sent by a network device before timestamping an uplink data packet according to a local time; A first adjustment unit, configured to adjust the local time according to the target time related information until the local time is synchronized with the time of the target server or the target clock source; The first processing unit is used to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time; The data flow is an associated data flow; the associated data flow is a data flow for the terminal to execute a target service, or a data flow for the terminal and other terminals to jointly execute a target service.

33. The data transmission device according to claim 32, wherein: The target time related information is carried in at least one of the following information: Network Time Protocol NTP messages; Stream synchronization control strategy.

34. The data transmission device according to claim 32, wherein: The first processing unit is used to timestamp the uplink data packet corresponding to at least one data stream according to the adjusted local time in a first manner; The first method includes at least one of the following: Mark the timestamp in the protocol data unit (PDU) IP header; Mark the timestamp in the Packet Data Convergence Protocol (PDCP) header; The timestamp is marked in the radio link layer control protocol RLC header.

35. The data transmission device according to claim 32, wherein: The first processing unit is used to use a first marking granularity to timestamp an uplink data packet corresponding to at least one data flow according to the adjusted local time; The first marking granularity includes at least one of the following: Frame granularity; Protocol data unit set granularity; Protocol Data Unit (PDU) granularity.

36. The data transmission device according to claim 32, further comprising: The second sending unit is used to send a synchronization request to the network device before receiving the target time related information sent by the network device; wherein the synchronization request is used to request to synchronize the terminal to the target server.

37. The data transmission device according to claim 36, wherein the target time related information is target server information, and the data transmission device further comprises: A second receiving unit, configured to receive a flow synchronization control strategy sent by a network device; The second sending unit is used to send a synchronization request to the network device according to the target server information.

38. A data transmission device, applied to a network device, the data transmission device comprising: A first determining unit, configured to determine target time related information for providing a reference time for at least one terminal; A third sending unit, configured to send the target time related information to the at least one terminal; The terminal is a terminal corresponding to at least one data stream, and the data stream is an associated data stream; the associated data stream refers to a data stream for a terminal to execute a target service, or refers to a data stream for at least two terminals to jointly execute a target service.

39. The data transmission device according to claim 38, wherein: The target time related information is carried in at least one of the following information: Network Time Protocol NTP messages; Stream synchronization control strategy.

40. The data transmission device according to claim 38, wherein: The first determination unit is used to receive a synchronization request sent by at least one terminal; according to the synchronization request, determine target time related information used to provide a reference time for at least one terminal; wherein the synchronization request is used to request synchronization with a target server.

41. The data transmission device according to claim 40, wherein: The first determining unit is used for: The first target address of the packet header of the synchronization request is replaced with the address of the target server, and send it to the target server; receive the response information of the target server, and obtain the target time related information used to provide the reference time for at least one terminal; Alternatively, target time related information for providing reference time for at least one terminal is obtained according to the synchronization request and a timestamp marked by a target clock source.

42. The data transmission device according to claim 41, further comprising: The second determination unit is used to determine the information of the target server or the information of the target clock source when it is determined that at least one data stream is an associated data stream before determining the target time related information for providing a reference time for at least one terminal according to the synchronization request.

43. The data transmission device according to claim 41, further comprising: A second processing unit is configured to replace the first target address of the packet header of the synchronization request with the address of the target server, and before sending the target time related information to the at least one terminal, replace the second target address of the packet header of the response information with the first target address to obtain a first request response; The third sending unit is used to send the first request response to the terminal that sends the synchronization request.

44. The data transmission device according to claim 41, wherein: The timestamp based on the target clock source mark includes: a first timestamp and a second timestamp based on the target clock source mark; The first timestamp is: the first time when the network device receives the synchronization request; the second timestamp is: the second time when the network device sends a response corresponding to the synchronization request.

45. The data transmission device according to claim 41, wherein: The target time related information is target server information, and the data transmission device further includes: A third sending unit, used for sending a stream synchronization control strategy to a terminal; Wherein, the stream synchronization control strategy includes: target server information.

46. ​​A readable storage medium storing a computer program, wherein the computer program is configured to cause a processor to execute the method according to any one of claims 1 to 15.

Images