CN113709802A

CN113709802A - Method and device for supporting data transmission

Info

Publication number: CN113709802A
Application number: CN202010438324.9A
Authority: CN
Inventors: 柯小婉
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-05-21
Filing date: 2020-05-21
Publication date: 2021-11-26
Also published as: WO2021233419A1

Abstract

The embodiment of the application provides a method and equipment for supporting data transmission, wherein the method comprises the following steps: determining or obtaining first information, the first information comprising at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT); sending the first information; wherein the first capability information indicates whether the terminal supports DS-TT. In the embodiment of the application, before data arrives at the network, the network can know the data arrival time in advance, and when the data source end and/or the data target end are in the terminal, deterministic transmission of the data is supported.

Description

Method and device for supporting data transmission

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method and equipment for supporting data transmission.

Background

Many data of the data entity on the terminal are also time-sensitive, have high requirements on time delay and have the deterministic characteristic of periodic transmission. How to support deterministic transmission of data is a problem to be solved when the data source and/or destination is within the terminal.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method and a device for supporting data transmission, which solve the problem of how to support a terminal as a data source end and/or a data target end to support time-sensitive deterministic transmission.

In a first aspect, an embodiment of the present application provides a method for supporting data transmission, which is applied to a communication device, and includes:

determining or obtaining first information, the first information comprising at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

sending the first information;

wherein the first capability information indicates whether the terminal supports a device side time-sensitive converter (DS-TT).

In a second aspect, an embodiment of the present application provides a method for supporting data transmission, including:

when the third condition is met, setting the retention time between the terminal and the DS-TT as the retention time inside the terminal or zero;

and sending the stay time between the terminal and the DS-TT.

In a third aspect, an embodiment of the present application provides a method for supporting data transmission, which is applied to a communication device, and includes:

obtaining first information, the first information comprising at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

according to the first information, performing a first operation, the first operation comprising at least one of:

confirming the time when the radio access network RAN can start to schedule uplink data;

confirming the time at which the data can be sent to the network at the terminal;

confirming time delay between a terminal and a network;

forwarding the first information;

In a fourth aspect, an embodiment of the present application provides a communication device, including:

a determining module or an obtaining module, configured to determine or obtain first information, where the first information includes at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

the first sending module is used for sending the first information;

wherein the first capability information indicates whether the terminal supports DS-TT.

In a fifth aspect, an embodiment of the present application provides a terminal, including:

the processing module is used for setting the retention time between the terminal and the DS-TT to be the retention time inside the terminal or zero when the third condition is met;

and the second sending module is used for sending the stay time between the terminal and the DS-TT.

In a sixth aspect, an embodiment of the present application provides a communication device, including:

an obtaining module, configured to obtain first information, where the first information includes at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

an execution module, configured to execute a first operation according to the first information, where the first operation includes at least one of:

confirming the time when RAN can start to schedule uplink data;

confirming time delay between a terminal and a network;

forwarding the first information;

In a seventh aspect, an embodiment of the present application provides a communication device, including: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, performs the steps of the method of supporting data transfer as set forth in the first, second or third aspect.

In an eighth aspect, an embodiment of the present application provides a readable storage medium, which is characterized in that the readable storage medium stores a program, and the program, when executed by a processor, implements the steps of the method for supporting data transmission according to the first aspect, the second aspect, or the third aspect.

In a ninth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect, the second aspect, or the third aspect.

In the embodiment of the application, before data arrives at the network, the network can know the data arrival time in advance, and when the data source end and/or the data target end are in the terminal, deterministic transmission of the data is supported.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings.

In the drawings:

FIG. 1 is a schematic diagram of a time sensitive network;

FIG. 2 is a flowchart of a method for supporting data transmission according to an embodiment of the present application;

fig. 3 is a second flowchart of a method for supporting data transmission according to an embodiment of the present application;

fig. 4 is a third flowchart of a method for supporting data transmission according to an embodiment of the present application;

FIG. 5 is a fourth flowchart of a method for supporting data transmission according to an embodiment of the present application;

fig. 6 is one of schematic diagrams of a communication device of an embodiment of the present application;

fig. 7 is a schematic diagram of a terminal according to an embodiment of the present application;

fig. 8 is a second schematic diagram of a communication device according to an embodiment of the present application;

fig. 9 is a third schematic diagram of a communication device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Existing time sensitive networks are plant-specific devices (End Station). The UE, TT and network form a bridge, and the interconnection of the devices behind the TT is supported to be different. The UE only provides a path for wireless access, and details of the wireless access are shielded.

Applications on the UE have many data that are also time sensitive and have deterministic characteristics for periodic transmissions. Time sensitive networks may also be applied to support deterministic transfers.

Problem 1: in order to support deterministic transmission, it is necessary to let the RAN know the time when data is ready to be scheduled by the RAN in advance before the data reaches a Radio Access Network (RAN), and for downlink data, the time delay when the data reaches the RAN is time delay, and for uplink data, the time when the data starts to be scheduled by the RAN at a Uu port is time delay. Due to time sensitivity of data, the retention time of data forwarding inside the terminal cannot be ignored. The problem of how to determine when data is ready to be scheduled by the RAN needs to be solved.

Problem 2: a Core Network (CN) needs to determine a maximum scheduling delay for the RAN, where the delay needs to meet a communication requirement between a time-sensitive application client and a server. Therefore, the network needs to determine the delay overhead between the terminal and the network for the application and disclose the delay overhead to the application. Therefore, the application can determine how long the data is sent in advance, and the deterministic transmission of the data can be guaranteed, and the data can arrive at the target end point by point on time. And constructing time delay between the terminal and the network, wherein the retention time of data forwarding in the terminal is not negligible. The problem of how to determine the time delay between the terminal and the network needs to be solved.

Referring to fig. 1, a time sensitive network is illustrated, and the main communication network element devices are introduced as follows:

UE: user Equipment, terminal. The terminal may include: data entities (such as an application Client (APP Client) and a chipset (Chip Set)), data of the application may be time-sensitive data and have a deterministic characteristic of periodic transmission.

AMF: access and Mobility Management Function.

UPF: user Plan Function, User plane Function.

SMF: session Management Function, Session Management Function.

AF: application Function, Application Function.

PCF: policy Control Function, Policy Control Function.

NEF: network Exposure Function, Network open Function.

NG-RAN: 5G access network.

NW-TT: network TSN Translator, Network side time sensitive Translator.

App Server: an application server.

A section of time delay: terminal internal residence time.

B, section time delay: and time delay between the terminal and the wireless access network. The time delay between the terminal and the radio access network may represent the time required for data to pass through the terminal and the radio access network.

C, time delay: time delay between the radio access network and the UPF and/or NW-TT. The time delay between the radio access network and the UPF and/or NW-TT may represent the time required for data to pass through the radio access network and the UPF and/or NW-TT.

The Packet Delay Budget (PDB) may be equal to the sum of the Delay of section B and the Delay of section C.

D, time delay: UPF and/or NW-TT latency and inter-data entity server latency. The UPF and/or NW-TT time delay and the data entity inter-server time delay can represent the time required for data to pass through the UPF and/or NW-TT time delay and the data entity server

The time delay between the application client and the application server is equal to the sum of the time delay of the section A, the time delay of the section B, the time delay of the section C and the time delay of the section D.

For the uplink data, the time when the application client sends out the data plus the a-segment delay may be the time when the RAN can schedule the uplink data.

Therefore, the internal residence time of the terminal can be determined through the reporting of the A-segment time delay and/or the data arrival time, so that the RAN can know the data arrival time or the data ready scheduling time in advance before the data arrive at the RAN, resources are reserved in advance, and the deterministic transmission of the data is supported.

In an optional embodiment of the present application, the terminal internal stay time refers to a time that data stays inside or passes through the terminal when the data is forwarded.

In an alternative embodiment of the present application, the data entity may comprise a source of said data and/or a target of the data. The data entity may include an Application (e.g., Application Client) of the terminal.

In an alternative embodiment of the invention, the data may comprise data that requires deterministic transmission or time sensitive data.

In an alternative embodiment of the present application, the dwell time between the terminal and the DS-TT is the time required for data to pass between the terminal and the DS-TT. The time required for data to pass between the terminal and the DS-TT includes the time required for data to pass between the terminal and the port of the DS-TT. The terminal-to-DS-TT dwell time may also be referred to as terminal-to-gateway and/or DS-TT inter-delay.

In an alternative embodiment of the present application, the delay between the terminal and the gateway and/or the NW-TT is the time required for data to pass between the DS-TT and the gateway and/or the NW-TT. It may also be referred to as a terminal-to-gateway and/or NW-TT stay time. In one embodiment, the delay between the terminal and the gateway and/or the NW-TT does not include the terminal internal dwell time. The time delay between the terminal and the gateway and/or the NW-TT is the time delay between the UU port of the terminal and the gateway and/or the NW-TT. In another embodiment, the time delay between the terminal and the gateway and/or the NW-TT comprises the terminal internal stay time.

In an alternative embodiment of the present application, the time delay between the terminal and the gateway and/or the NW-TT is a PDB configured for the network, and does not include the internal processing time of the terminal. In an alternative embodiment of the present invention, the delay between the terminal and the gateway and/or the NW-TT is the sum of the PDB and the internal processing time of the terminal.

In an optional embodiment of the present application, whether the terminal supports the device-side time-sensitive converter DS-TT or not includes at least one of the following: whether the terminal comprises the device side time sensitive converter DS-TT or not and whether the terminal supports interconnection and intercommunication with the device side time sensitive converter DS-TT or not.

In an optional embodiment of the present application, the terminal supports the device-side time-sensitive converter DS-TT, and includes at least one of the following: the terminal comprises a device side time sensitive converter DS-TT, and the terminal supports interconnection and intercommunication with the device side time sensitive converter DS-TT.

In an optional embodiment of the present application, the terminal not supporting the device-side time-sensitive converter DS-TT includes at least one of the following: the terminal does not contain the device side time sensitive converter DS-TT, and the terminal does not support interconnection and intercommunication with the device side time sensitive converter DS-TT.

In an optional implementation manner of the present application, the source of the data and/or the target of the data not being connected through the TT includes: and the source end of the data and/or the target end of the data are/is not connected to the network through the TT. The TT comprises DS-TT or NW-TT. For example, the application on the terminal directly transmits and receives data to and from the network through the terminal, is not connected with the terminal through the DS-TT, and is connected with the network through the terminal.

In the embodiments of the present application, the data packet and the data may be mixed and represent the same meaning.

Optionally, the obtaining may be understood as obtaining from configuration, receiving after a request, obtaining by self-learning without learning, deriving the obtaining according to information that is not received, or obtaining after processing the received information, which may be determined according to actual needs, and is not limited in this embodiment of the application. For example, when a certain capability indication sent by the device is not received, it can be deduced that the device does not support the capability.

Optionally, the sending may include broadcasting, broadcasting in a system message, and returning after responding to the request.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The techniques described herein are not limited to Long Time Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems.

The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies.

In one embodiment of the present application, a communication device may include at least one of: communication network element equipment and a terminal.

In an embodiment of the present application, the communication network element may include at least one of: a core network element and a radio access network element.

In the embodiment of the present application, the core network element (CN element) may include, but is not limited to, at least one of the following: core network equipment, core network nodes, core network functions, core network elements, Mobility Management Entity (MME), Access Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), serving gateway (serving GW, SGW), PDN Gateway (PDN Gateway), Policy Control Function (Policy Control Function, PCF), Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF), GPRS service Support Node (Serving GPRS Support Node, SGSN), Gateway GPRS Support Node (GGSN), Unified Data Management (UDM), Unified Data storage (UDR), Home Subscriber Server (HSS), and Data entity Function (Application Function, AF).

In the embodiment of the present application, the RAN network element may include, but is not limited to, at least one of the following: radio Access Network equipment, Radio Access Network nodes, Radio Access Network functions, Radio Access Network units, 3GPP Radio Access Networks, Non-3GPP Radio Access Networks, Centralized Units (CUs), Distributed Units (DU), base stations, evolved Node bs (eNB), 5G base stations (gNB), Radio Network Controllers (RNC), base stations (NodeB), Non-3GPP Inter Working functions (N3 IWF), Access Control (AC) nodes, Access Point (Access Point, AP) devices or Wireless Local Area Networks (WLAN) nodes, N3 IWF.

The Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, an evolved Node B (eNB or e-NodeB) in LTE, and a 5G Base Station (gNB), and the embodiment of the present invention is not limited thereto.

In the embodiment of the present application, the terminal may include a relay supporting the terminal function and/or a terminal supporting the relay function. The terminal may also be referred to as a terminal Device or a User Equipment (UE), where the terminal may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or a vehicle-mounted Device, and it should be noted that a specific type of the terminal is not limited in this embodiment of the application.

Referring to fig. 2, an embodiment of the present application provides a method for supporting data transmission, where an execution subject of the method may be a communication device, and the method includes one of the following: the terminal and the communication network element device (such as SMF, AMF, PCF, NEF, or AF) may include the following specific steps: step 201 and step 202

Step 201: determining or obtaining first information, which may include at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

step 202: sending first information;

for example, the communication device is a terminal, and the terminal may send the first information to a communication network element device, such as an AMF or an SMF.

In one embodiment, the first information sent by the terminal may include at least one of the following: the first capability information, the terminal internal stay time, the data arrival time, and the information of the source end and/or the target end of the data.

In another embodiment, the first information sent by the terminal may include at least one of the following: the first capability information, the terminal internal stay time, and the information of the source end and/or the target end of the data.

For example, the communication device is NEF or AF. In one embodiment, the first information sent by the NEF or the AF may include: data arrival time, source of data and/or destination of data.

For example, the communication device is an AMF or an SMF. In one embodiment, the AMF or SMF acquires the first information from the terminal and then transmits the acquired first information to the other communication network device.

The first capability information indicates whether the terminal supports a Device-Side time-sensitive converter (DS-TT).

In this embodiment, the terminal internal stay time may refer to a time that data stays or passes inside the terminal when the data is forwarded.

Optionally, the terminal internal residence time may include one of:

(1) the time required for forwarding data between the Uu port of the terminal and the data entity of the terminal;

(2) the time required for forwarding data between the terminal access layer and the data entity of the terminal;

wherein the data entity comprises a source of the data and/or a target of the data.

The data entity may comprise an Application of the terminal (e.g. Application, or Application client, or Application server).

Thus, in some embodiments, the terminal internal residence time may include one of:

(1) the time required for forwarding data between the Uu port of the terminal and the application of the terminal;

(2) and the time required for forwarding data between the terminal access layer and the terminal application is shortened.

Optionally, the time required for forwarding data between the terminal access stratum and the data entity of the terminal may include at least one of:

(1) the terminal needs time from the time when the network receives the data to the time when the terminal sends the data to the data entity of the terminal;

(2) the time required for sending data to the terminal access layer by the data entity of the terminal;

(3) the time required for the data entity of the terminal to send data to the terminal access layer and send the data out of the network; and the number of the first and second groups,

(4) the time required for the data entity of the terminal to send data to the terminal access layer to send the data out of the network is subtracted by the time waiting for network scheduling.

It is easy to understand that the time required for forwarding data between the terminal access layer and the data entity of the terminal is, for example, 0.5 second, and the time for waiting for network scheduling is 0.4 second; the time required for the data entity of the terminal to send out data to the terminal access stratum to send out data to the network may be 0.9 seconds. The time (0.5 second) required for forwarding data between the terminal access layer and the data entity of the terminal may be the time (0.9 second) required for the data entity of the terminal to send data to the terminal access layer and send the data out to the network, minus the time (0.4 second) for waiting for network scheduling.

In one embodiment, the time required for forwarding the data packet between the terminal access layer and the terminal application may include at least one of the following:

(1) the terminal receives data from the network and the time required by the application sent to the terminal is up;

(2) the time required for the application of the terminal to send data to the ready of the access layer of the terminal;

(3) the time required for the application of the terminal to send data to the terminal access layer and send the data out of the network; and the number of the first and second groups,

(4) the time required for the terminal application to send data out to the network by the terminal access layer minus the time waiting for network scheduling.

It will be appreciated that the time (e.g., 0.5 seconds) required for forwarding a data packet between the terminal access stratum and the terminal's application may be the time (0.9 seconds) required for the terminal's application to send data out to the terminal access stratum and out to the network minus the time (0.4 seconds) for waiting for network scheduling.

It will be appreciated that the data entities described above may include: a source of data and/or a destination of data.

In some embodiments, the information of the source end of the data and/or the target end of the data is used to indicate that the source end of the data and/or the target end of the data is in the terminal;

and/or

For indicating that the source of said data and/or the target of the data is not connected by the time sensitive communication converter TT.

In some embodiments, the data arrival time comprises: the uplink data arrival time.

Wherein, the uplink data arrival time may include one of the following:

(1) the time at which the data is generated and/or sent out of the data entity; and the number of the first and second groups,

(2) the time at which the data can be scheduled by the network at the terminal;

(3) the time at which the data can be sent to the network at the terminal.

In an alternative embodiment, the Time when the data entity is generated and/or transmitted is the uplink data Arrival Time of the service level, which may be embodied as the uplink data Arrival Time (e.g. TSN QoS Burst Arrival Time) in the QoS requirement of the Time sensitive communication network.

In an alternative embodiment, the Time when the data can be scheduled by the network at the terminal or the Time when the data can be transmitted to the network at the terminal is the uplink data Arrival Time from the RAN perspective, which may be embodied as the uplink data Arrival Time (e.g., TSN QoS Burst Arrival Time) in the Time-sensitive communication assistance information.

It will be appreciated that the sum of the terminal internal dwell time and (1) the time that data is generated and/or transmitted at the data entity may be equivalent to (2) the time that data can be scheduled at the terminal by the network.

It will be appreciated that the sum of the terminal internal dwell time and (1) the time that the data is generated and/or transmitted at the data entity may be equivalent to (3) the time that the data can be transmitted to the network at the terminal.

Optionally, when the uplink data arrival time is a time when the data can be scheduled by the network at the terminal or a time when the data can be sent to the network at the terminal, the value of the terminal internal stay time is zero or the terminal internal stay time is not sent.

Optionally, the data may include at least one of the following at a time when the terminal can be scheduled by the network:

(1) the time when the data reaches the access layer of the terminal;

(2) data arrives at the terminal access layer ready time;

(3) the time when the data arrives at the terminal access layer and begins to wait for network scheduling;

optionally, the time when the data arrives at the terminal access stratum and starts waiting for network scheduling refers to the time when the data arrives at the terminal access stratum and is ready to start waiting for RAN scheduling.

(4) The time of data reaching a Uu port of the terminal; and the number of the first and second groups,

(5) the data arrives at the beginning of the Uu port of the terminal for the scheduled time.

Optionally, the time for starting waiting for scheduling when the data arrives at the Uu port of the terminal is the time for the RAN to start waiting for scheduling when the data arrives at the Uu port of the terminal ready.

Optionally, the time at which the terminal can transmit data to the network may include at least one of:

(1) the time when the data reaches the access layer of the terminal;

(2) data arrives at the terminal access layer ready time;

(3) time of data arrival at the Uu port of the terminal.

In one embodiment, when the uplink data arrival time is the time when data is generated/transmitted in the data entity, the RAN can start scheduling the uplink data as the uplink data arrival time-terminal internal residence time.

In another embodiment, when the uplink data arrival time is a time when data can be scheduled by the network at the terminal or a time when data can be transmitted to the network at the terminal, the time when the RAN can start scheduling uplink data is the uplink data arrival time. That is, the terminal internal dwell time may be set to zero.

In one embodiment, the time at which data can be scheduled by the network at the terminal may refer to the time at which the data is ready for the RAN to schedule transmission to the RAN for the data.

In one embodiment, the time when data can be sent to the network at the terminal may refer to the time when data is ready to be sent to the RAN at any time.

In one embodiment, the terminal-to-DS-TT dwell time is set to the terminal internal dwell time

In some embodiments, step 202 may comprise: and if the first condition is met, the first information is sent.

Optionally, the meeting the first condition comprises at least one of: (1) the source end of the data and/or the target end of the data are/is in the terminal;

(2) the source end of the data and/or the target end of the data are applications of the terminal;

(3) the source end of the data and/or the target end of the data are not connected through the TT; and the number of the first and second groups,

(4) the uplink data arrival time is the time when data can be scheduled by the network at the terminal or the time when data can be sent to the network at the terminal.

In some embodiments, step 201 may include at least one of:

(1) when the second condition is met, setting the arrival time of the uplink data as the sum of the time of the data generated and/or sent out in the data entity and the residence time in the terminal;

(2) when the second condition is confirmed to be met, setting a value of the stay time inside the terminal or the stay time between the terminal and the DS-TT to be zero, where meeting the second condition may include at least one of:

(1) the uplink data arrival time is the time when the data can be scheduled by the network at the terminal or the time when the data can be sent to the network at the terminal;

(2) the source end of the data and/or the target end of the data are/is in the terminal;

(3) the source end of the data and/or the target end of the data are not connected through the TT.

Optionally, the inter-terminal-to-gateway and/or NW-TT delay may be a pre-configured inter-terminal-to-gateway and/or NW-TT delay (e.g., PDB). In one embodiment, the delay between the terminal and the gateway and/or the NW-TT does not include terminal internal dwell time. In another embodiment, the delay between the terminal and the gateway and/or the NW-TT comprises a terminal internal stay time.

In embodiments of the present application, the data may comprise data that requires deterministic transmission or time sensitive data.

Referring to fig. 3, an embodiment of the present application provides a method for supporting data transmission, where an execution main body of the method includes a terminal, and the method includes the specific steps of: step 301 and step 302.

Step 301: confirming that a third condition is met, and setting the stay time between the terminal and the DS-TT as the stay time inside the terminal or zero;

in one embodiment, the terminal to DS-TT interface dwell time comprises terminal to DS-TT interface dwell time. An operation of setting the terminal-to-DS-TT inter-dwell time as terminal internal dwell time or zero, for example, setting the terminal-to-DS-TT inter-port dwell time as terminal internal dwell time or zero.

Step 302: the dwell time between the transmitting terminal and the DS-TT.

In some embodiments, satisfying the third condition may include at least one of:

(1) the source end of the data and/or the target end of the data are/is in the terminal;

Specifically, the data may be specifically as described in the embodiment of fig. 2 at the time when the terminal can be scheduled by the network.

Specifically, the time when the terminal can send the data to the network may be specifically as described in the embodiment of fig. 2.

In embodiments of the present application, the data may include data that needs to be transmitted deterministically or time-sensitive data.

In some embodiments, the terminal internal residence time may include one of:

(2) the time required for forwarding data between the terminal access layer and the data entity of the terminal.

Wherein the data entity comprises a source of the data and/or a target of the data. The data entity may comprise an Application of the terminal (e.g. Application, or Application client, or Application server).

1 third set

Referring to fig. 4, an embodiment of the present application provides a method for supporting data transmission, where an execution subject of the method may include a communication network element device, such as an SMF, an AMF, a PCF, a NEF, or an AF, and the specific steps include: step 401 and step 402.

Step 401: obtaining first information, the first information comprising at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

the first information is specifically described in the embodiment of fig. 2, and is not described in detail again.

In some embodiments, the data arrival time in the first information comprises: the arrival time of uplink data; .

Wherein, the uplink data arrival time may include one of the following:

(2) the time at which the data can be scheduled by the network at the terminal;

(3) the time at which the data can be sent to the network at the terminal.

Step 402: according to the first information, performing a first operation, the first operation comprising at least one of:

(1) confirming the time when RAN can start to schedule uplink data;

(2) confirming the time delay between the terminal and the network (such as the time delay of section B and the time delay of section C in figure 1);

(3) confirming the time at which the data can be sent to the network at the terminal;

(4) and forwarding the first information.

In an alternative embodiment, the Time when the RAN can start scheduling the uplink data or the Time when the data can be transmitted to the network at the terminal is the uplink data Arrival Time from the RAN perspective, which may be embodied as the uplink data Arrival Time (e.g., TSN QoS Burst Arrival Time) in the Time-sensitive communication assistance information.

Wherein the first capability information indicates whether the terminal supports a device side time-sensitive converter (DS-TT) or whether a data entity of the terminal is connected through the DS-TT.

Optionally, the time delay between the terminal and the network includes: the time required for data forwarding between the terminal and the network.

In one embodiment, the time delay between the terminal and the network includes the time during which the data stays in the network. Such as the time required for data forwarding from the Uu port of the terminal to the N6 port.

In another embodiment, the time delay between the terminal and the network may further include the time for which the data stays inside the terminal.

In one embodiment, the delay between the endpoint and the network, which may form a bridge with the network, is also referred to as a bridge delay (e.g., a 5GS bridge delay).

In another embodiment, the terminal, network and time sensitive adapter form a bridge.

In some embodiments, the terminal internal residence time may include one of:

In embodiments of the present application, the data may include data that requires deterministic transmission or data sensitive data.

In some embodiments, the information of the source end of the data and/or the target end of the data is used to indicate that the source end of the data and/or the target end of the data is within the terminal; and/or indicating that the source of the data and/or the target of the data are not connected through the TT.

In some embodiments, the data arrival time comprises: the arrival time of uplink data;

wherein, the uplink data arrival time may include one of the following:

(1) the time at which the data is generated and/or sent out of the data entity;

(2) the time at which the data can be scheduled by the network at the terminal;

(3) the time at which the data can be sent to the network at the terminal.

(1) the time when the data reaches the access layer of the terminal;

(2) data arrives at the terminal access layer ready time;

(1) the time when the data reaches the access layer of the terminal;

(2) data arrives at the terminal access layer ready time;

(3) time of data arrival at the Uu port of the terminal.

Optionally, when it is determined that the fourth condition is satisfied, determining that the time during which the RAN can start scheduling the uplink data is the uplink data arrival time plus the terminal internal residence time. It is understood that the uplink data arrival time may be a time point, such as 12 points 0 minutes 0 seconds; the terminal internal residence time is a duration, e.g., 0.5 second; the time that the RAN can start scheduling uplink data is 12 points 0 minutes 0.5 seconds.

Optionally, when it is determined that the fourth condition is satisfied, the time that the acknowledgment data can be sent to the network at the terminal is the uplink data arrival time plus the terminal internal residence time. It is understood that the uplink data arrival time may be a time point such as 12 points 0 minutes 0 seconds; the terminal internal residence time is a time period, for example, 0.5 second. The time when the data can be transmitted to the network at the terminal is 12 o' clock 0.5 seconds. Wherein satisfying the fourth condition may include at least one of:

(1) the uplink data arrival time is the time when data is generated/sent out in a data entity;

(3) the value of the terminal internal stay time or the stay time between the terminal and the DS-TT is not zero;

(4) the terminal does not support the device side time sensitive converter DS-TT;

(5) the source of the data and/or the target of the data are not connected through the TT.

Optionally, when it is determined that the fifth condition is satisfied, determining that the time at which the RAN can start scheduling the uplink data is the uplink data arrival time;

optionally, when it is determined that the fifth condition is satisfied, determining that the time that the data can be sent to the network at the terminal is the uplink data arrival time;

wherein satisfying the fifth condition may include at least one of:

(3) the retention time inside the terminal or between the terminal and the DS-TT takes a value of zero;

Optionally, when it is determined that the sixth condition is satisfied, determining that the time delay between the terminal and the network is the time delay between the terminal and the gateway and/or the NW-TT, and/or determining that the time delay between the terminal and the network does not include the internal retention time of the terminal;

optionally, the inter-terminal-to-gateway and/or NW-TT delay may be a pre-configured inter-terminal-to-gateway and/or NW-TT delay (e.g., PDB). In one embodiment, the delay between the terminal and the gateway and/or the NW-TT does not include terminal internal dwell time.

Wherein satisfying the sixth condition may comprise at least one of:

(2) the source end of the data and/or the target end of the data are/is in the terminal; and the number of the first and second groups,

(3) the stay time inside the terminal or between the terminal and the DS-TT is zero.

Optionally, when it is determined that the seventh condition is satisfied, determining that the time delay between the terminal and the network is the time delay between the terminal and the gateway and/or the NW-TT plus the terminal internal stay time, and/or determining that the time delay between the terminal and the network includes the terminal internal stay time;

wherein satisfying the seventh condition comprises at least one of:

(5) the source end of the data and/or the target end of the data are not connected through the TT; .

Wherein, the time delay between the terminal and the gateway and/or the NW-TT can comprise one of the following:

(1) time required for data forwarding between the terminal and the gateway and/or the NW-TT;

(2) packet Delay Budget (PDB) or configured Delay; and the number of the first and second groups,

(3) and staying for the time inside the gateway and/or the NW-TT when the data is forwarded.

Referring to fig. 5, a flow of a method for supporting data transmission is illustrated, and the specific steps include: step 1 to step 15.

Step 1: the UE sends a PDU session setup request to an Access and Mobility Management Function (AMF).

Optionally, the UE may send the first information to the AMF, as described in the embodiment of fig. 2 in detail

For example, the UE sends a Non-Access-Stratum (NAS) message to the AMF, where the NAS message includes a Protocol Data Unit (PDU) session establishment request.

Wherein, the PDU conversation establishment request comprises: the first information.

Optionally, the first information is specifically described in the embodiment of fig. 2.

For example, the first information may include first capability information and/or terminal internal stay time; the first capability information may indicate whether the UE supports DS-TT, and the terminal internal stay time may include: and the time required for data forwarding between the Uu interface of the terminal and the data entity of the terminal.

Step 2: the AMF sends a PDU Session _ create SM context message to a Session Management Function (SMF). Optionally, the AMF sends the acquired first information to the SMF.

The first information acquired from the UE or the AMF may include at least one of: the first capability information, the terminal internal stay time, and the information of the source end and/or the target end of the data.

In addition, the SMF may obtain other first information, such as data arrival time, from the PCF, NEF, AF; alternatively, the SMF may obtain the data arrival time from the UE or the AMF;

in addition, the SMF may pre-configure to obtain other first information, such as delay between the terminal and the gateway and/or NW-TT;

optionally, the SMF executes the first operation according to the first information, which is specifically described in the embodiment of fig. 4 and is not described herein again.

Illustratively, the first operation includes at least one of:

(1) confirming the time when RAN can start to schedule uplink data;

(2) the time at which the data can be sent to the network at the terminal is confirmed.

And step 3: the SMF selects a User Plane Function (UPF).

The SMF sends the N4 session establishment to the selected UPF.

And 4, step 4: SMF registers terminals to Unified Data Manager (UDM). The SMF may also obtain and subscribe to subscription data of the terminal.

And 5: the SMF acquires a Policy of the terminal from a Policy Control Function (PCF).

The SMF sends the acquired first information to the PCF, NEF, or AF. The first information includes at least one of:

the first capability information, the terminal internal stay time, and the information of the source end and/or the target end of the data.

The PCF sends the first information to an Application Function (AF) or NEF.

Optionally, the PCF, the NEF, or the AF performs the first operation according to the first information, which is specifically described in the embodiment of fig. 4 and is not described herein again.

Illustratively, the first operation includes: confirming the time delay between the terminal and the network (such as the time delay of section B and the time delay of section C in figure 1);

optionally, the PCF sends the time delay between the terminal and the network to the NEF or the AF.

Optionally, the NEF sends the time delay between the terminal and the network to the AF.

Optionally, the AF sends the inter-terminal-to-Network delay (which may also be referred to as bridge delay) to a Centralized Network Controller (CNC).

Step 6: the SMF sends an N1N2 message to the AMF.

The N1N2 message includes a NAS message for PDU session setup accept.

And 7: and the AMF sends a PDU session resource establishment request message to the RAN network element.

The N1N2 message includes a NAS message for PDU session establishment.

And 8: and the RAN network element sends an RRC reconfiguration request to the UE.

Wherein the request may be a NAS message including a PDU session setup command.

And step 9: and the UE returns an RRC reconfiguration response to the RAN network element.

Step 10: and the RAN network element returns a PDU session resource establishment response to the AMF.

Step 11: the AMF sends an SM context update request to the MF.

Step 12: the SMF sends an N4 session update, also referred to as an N4 session modification, to the UPF.

Step 13: the UE sends an uplink NAS message to the AMF.

Wherein the message indicates that the PDU session setup is complete.

Step 14: the SMF sends an SM context update response to the AMF.

Step 15: the SMF sends an N4 session update, also referred to as an N4 session modification, to the UPF.

Referring to fig. 6, an embodiment of the present application provides a communication device 600, including:

a determining module or obtaining module 601, configured to determine or obtain first information, where the first information includes at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

a first sending module 602, configured to send the first information;

Optionally, the terminal internal residence time is one of:

the time required for forwarding data between the Uu port of the terminal and the data entity of the terminal;

the time required for forwarding data between the terminal access layer and the data entity of the terminal;

Optionally, the information of the source end and/or the target end of the data is used to indicate that the source end and/or the target end of the data is in the terminal; and/or indicating that the source of the data and/or the target of the data are not connected through the TT.

Optionally, the data arrival time includes: the uplink data arrival time.

Wherein the uplink data arrival time comprises one of: the time when the data is generated and/or sent out in the data entity, the time when the data can be scheduled by the network at the terminal, and the time when the data can be sent to the network at the terminal;

Optionally, the first sending module 602 is further configured to: when the first condition is met, the first information is sent;

wherein the meeting the first condition comprises at least one of:

the source end of the data and/or the target end of the data are/is in the terminal;

the source end of the data and/or the target end of the data are applications of the terminal;

the source end of the data and/or the target end of the data are not connected through TT;

the uplink data arrival time is the time when data can be scheduled by the network at the terminal or the time when data can be sent to the network at the terminal.

Optionally, the determining module or the obtaining module 601 is further configured to perform at least one of the following:

when the second condition is met, setting the arrival time of the uplink data as the sum of the time of the data generated and/or sent out in the data entity and the residence time in the terminal;

when a second condition is confirmed to be met, setting the value of the stay time inside the terminal or the stay time between the terminal and the DS-TT to be zero, wherein the meeting of the second condition comprises at least one of the following items:

the uplink data arrival time is the time that data can be scheduled by a network at a terminal or the time that the data can be sent to the network at the terminal;

the source end of the data and/or the target end of the data are not connected through the TT.

The communication device provided in the embodiment of the present application may execute the method embodiment shown in fig. 2, which has similar implementation principles and technical effects, and this embodiment is not described herein again.

Referring to fig. 7, an embodiment of the present application provides a communication device 700, including:

a processing module 701, configured to set a retention time between the terminal and the DS-TT to be an internal retention time of the terminal or zero when it is determined that the third condition is satisfied;

a second sending module 702, configured to send the dwell time between the terminal and the DS-TT.

Optionally, the satisfying a third condition comprises at least one of:

The terminal provided in the embodiment of the present application may execute the method embodiment shown in fig. 3, which has similar implementation principles and technical effects, and this embodiment is not described herein again.

Referring to fig. 8, an embodiment of the present application provides a communication device 800, where the communication device includes:

an obtaining module 801, configured to obtain first information, where the first information includes at least one of: the method comprises the steps that first capability information, terminal internal stay time, data arrival time, information of a data source end and/or a data target end, and time delay between a terminal and a gateway and/or an NW-TT (NW-TT);

an executing module 802, configured to execute a first operation according to the first information, where the first operation includes at least one of:

confirming the time when RAN can start to schedule uplink data;

confirming time delay between a terminal and a network;

forwarding the first information;

Optionally, the terminal internal residence time includes one of:

Optionally, the data arrival time includes: the arrival time of uplink data;

wherein the uplink data arrival time comprises one of: the time at which the data is generated and/or transmitted at the data entity, the time at which the data can be scheduled by the network at the terminal, and the time at which the data can be transmitted to the network at the terminal.

Optionally, when it is determined that the fourth condition is satisfied, determining that the time during which the RAN can start scheduling the uplink data is the sum of the arrival time of the uplink data and the internal residence time of the terminal;

and/or

When the fourth condition is met, the time that the data can be sent to the network at the terminal is determined as the sum of the arrival time of the uplink data and the internal retention time of the terminal;

wherein the satisfying a fourth condition comprises at least one of:

the uplink data arrival time is the time when data is generated/sent out in a data entity;

the source end of the data and/or the target end of the data are/is in the terminal

The value of the terminal internal stay time or the stay time between the terminal and the DS-TT is not zero;

the terminal does not support the device side time sensitive converter DS-TT;

the source of the data and/or the target of the data are not connected through the TT.

and/or

When the fifth condition is met, the time that the data can be sent to the network at the terminal is confirmed to be the arrival time of the uplink data;

wherein the meeting a fifth condition comprises at least one of:

the retention time inside the terminal or between the terminal and the DS-TT takes a value of zero;

the terminal does not support the device side time sensitive converter DS-TT;

Optionally, when the sixth condition is confirmed to be met, confirming that the time delay between the terminal and the network is the time delay between the terminal and the gateway and/or the NW-TT, and/or confirming that the time delay between the terminal and the network does not include the internal residence time of the terminal;

wherein the sixth condition being met comprises at least one of:

the uplink data arrival time is the time when the data can be scheduled by the network at the terminal or the time when the data can be sent to the network at the terminal;

the terminal does not support the device side time sensitive converter DS-TT;

wherein the meeting of the seventh condition comprises at least one of:

the terminal does not support the device side time sensitive converter DS-TT;

The communication device provided in the embodiment of the present application may execute the method embodiment shown in fig. 4, which has similar implementation principles and technical effects, and this embodiment is not described herein again.

Referring to fig. 9, fig. 9 is a structural diagram of a communication device of a data entity according to an embodiment of the present application, and as shown in fig. 9, the communication device 900 includes: a processor 901, a transceiver 902, a memory 903, and a bus interface, wherein:

in one embodiment of the present invention, the communication device 900 further comprises: a program stored on the memory 903 and executable on the processor 901, which when executed by the processor 901 performs the steps in the embodiments shown in fig. 2 or fig. 3 or fig. 4.

In fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 901 and various circuits of memory represented by memory 903 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 902 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium, it being understood that the transceiver 902 is an optional component.

The processor 901 is responsible for managing a bus architecture and general processing, and the memory 903 may store data used by the processor 901 in performing operations.

The communication device provided in the embodiment of the present application may execute the method embodiment shown in fig. 2, fig. 3, or fig. 4, which has similar implementation principle and technical effect, and this embodiment is not described herein again.

An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement each process of the method embodiment shown in fig. 2 or fig. 3 or fig. 4, and the same technical effect can be achieved, and details are not repeated here to avoid repetition.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read-Only Memory (ROM), Erasable programmable Read-Only Memory (EPROM), electrically Erasable programmable Read-Only Memory (EEPROM), registers, a hard disk, a removable hard disk, a compact disc Read-Only Memory (cd-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by program instructions. These program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

The instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.

Claims

1. A method for supporting data transmission, applied to a communication device, is characterized by comprising the following steps:

sending the first information;

2. The method of claim 1, wherein the terminal internal residence time is one of:

3. The method according to claim 1, wherein the information of the source end and/or the target end of the data is used to indicate that the source end and/or the target end of the data is in the terminal;

and/or the presence of a gas in the gas,

4. The method of claim 1, wherein the data arrival time comprises: the arrival time of uplink data;

5. The method of claim 4, wherein the uplink data arrival time is a time when data can be scheduled by a network at a terminal or a time when data can be sent to the network at the terminal, and the terminal internal stay time is zero or no terminal internal stay time is sent.

6. The method of claim 1, wherein the sending the first information comprises:

when the first condition is met, the first information is sent;

wherein the meeting the first condition comprises at least one of:

7. The method of claim 1, wherein the operation of determining the first information comprises at least one of:

when the second condition is confirmed to be met, setting the value of the retention time inside the terminal or the retention time between the terminal and the DS-TT as zero;

wherein the meeting of the second condition comprises at least one of:

8. A method for supporting data transmission is applied to a terminal, and is characterized by comprising the following steps:

and sending the stay time between the terminal and the DS-TT.

9. The method of claim 8, wherein satisfying the third condition comprises at least one of:

10. A method for supporting data transmission, applied to a communication device, is characterized by comprising the following steps:

confirming time delay between a terminal and a network;

forwarding the first information;

11. The method of claim 10, wherein the terminal internal dwell time comprises one of:

12. The method according to claim 10, wherein the information of the source end and/or the target end of the data is used to indicate that the source end and/or the target end of the data is in the terminal;

and/or the presence of a gas in the gas,

indicating that the source of the data and/or the target of the data is not connected through the TT.

13. The method of claim 10, wherein the data arrival time comprises: the arrival time of uplink data;

14. The method of claim 10, wherein the confirming when the RAN can begin scheduling uplink data comprises:

when the condition that the uplink data meets the fourth condition is confirmed, confirming that the time that the RAN can start to schedule the uplink data is the sum of the arrival time of the uplink data and the internal residence time of the terminal;

and/or

The time when the confirmation data can be sent to the network at the terminal comprises the following steps:

wherein the satisfying a fourth condition comprises at least one of:

the terminal does not support the device side time sensitive converter DS-TT;

15. The method of claim 10, wherein the confirming when the RAN can begin scheduling uplink data comprises:

when the fifth condition is met, determining that the time when the RAN can start to schedule the uplink data is the uplink data arrival time;

and/or

wherein the meeting a fifth condition comprises at least one of:

the terminal does not support the device side time sensitive converter DS-TT;

16. The method of claim 10, wherein determining the time delay between the terminal and the network comprises:

when the sixth condition is confirmed to be met, confirming that the time delay between the terminal and the network is the time delay between the terminal and the gateway and/or the network side time sensitive converter NW-TT, and/or confirming that the time delay between the terminal and the network does not contain the internal staying time of the terminal;

wherein the sixth condition being met comprises at least one of:

the terminal does not support the device side time sensitive converter DS-TT;

17. The method of claim 10, wherein determining the time delay between the terminal and the network comprises:

when the seventh condition is confirmed to be met, confirming that the time delay between the terminal and the network is the sum of the time delay between the terminal and the gateway and/or the NW-TT and the internal terminal staying time, and/or confirming that the time delay between the terminal and the network comprises the internal terminal staying time;

wherein the meeting of the seventh condition comprises at least one of:

the terminal does not support the device side time sensitive converter DS-TT;

18. A communication device, comprising:

the first sending module is used for sending the first information;

19. A terminal, comprising:

20. A communication device, comprising:

confirming the time when RAN can start to schedule uplink data;

confirming time delay between a terminal and a network;

21. A communication device, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of supporting data transmission according to any of claims 1 to 17.

22. A readable storage medium, characterized in that the readable storage medium has stored thereon a program which, when being executed by a processor, carries out the steps of the method of supporting data transmission according to any one of claims 1 to 17.