CN115250504A

CN115250504A - Data transmission method and device and computer readable storage medium

Info

Publication number: CN115250504A
Application number: CN202110462046.5A
Authority: CN
Inventors: 韩立锋
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2021-04-27
Filing date: 2021-04-27
Publication date: 2022-10-28
Also published as: WO2022228322A1

Abstract

A data transmission method, a data transmission device and a computer-readable storage medium are provided, and the method comprises the following steps: obtaining terminal capability information, wherein the terminal capability information is used for indicating XR (X ray Rate) capabilities supported by the UE and/or the HMD; determining a transmission delay according to the terminal capability information, wherein the transmission delay is used for indicating the maximum time length from the time when the network equipment receives the data to the time when the network equipment sends the data; and sending the transmission time delay. The invention can accurately determine the QoS of the XR service according to the XR service processing capacity of the terminal, and particularly reasonably determine the distribution of transmission delay at each transmission node, thereby enhancing the transmission of XR service data.

Description

Data transmission method and device and computer readable storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method and apparatus, and a computer-readable storage medium.

Background

The Extended Reality (XR) technology, which is a combination of Virtual Reality (VR), augmented Reality (AR), and Mixed Reality (MR), can merge a physical environment and a Virtual environment together, or provide a Virtual experience environment that is completely immersive, and has a wide application prospect in The Fifth-Generation mobile communication technology (5G).

The Service transmitted based on the XR technology may be referred to as an XR Service, and when configuring Quality of Service (QoS) for the XR Service, an existing network only considers access layer capability of User Equipment (UE), which may easily cause inaccurate QoS configured for the XR Service. Inaccurate QoS may increase the transmission delay of data, affect the timeliness of data transmission, and further affect user experience.

Disclosure of Invention

The technical problem solved by the invention is how to accurately determine the QoS of the XR service so as to enhance the transmission of the XR service.

To solve the foregoing technical problem, an embodiment of the present invention provides a data transmission method, including: obtaining terminal capability information, wherein the terminal capability information is used for indicating XR (X ray Rate) capabilities supported by the UE and/or the HMD; determining a transmission delay according to the terminal capability information, wherein the transmission delay is used for indicating the maximum time length from the time when the network equipment receives the data to the time when the network equipment sends the data; and sending the transmission time delay.

Optionally, the terminal capability information includes UE capability information and HMD capability information, wherein the UE capability information is used for indicating XR capabilities supported by the UE, and the HMD capability information is used for indicating XR capabilities supported by the HMD.

Optionally, the acquiring the terminal capability information includes: and receiving the UE capability information reported by the UE and receiving the HMD capability information reported by the HMD.

Optionally, the acquiring the terminal capability information includes: acquiring the terminal capability information from a base station; or acquiring the terminal capability information from an XR application server.

Optionally, the acquiring the terminal capability information includes: and acquiring the terminal capability information from the SMF.

Optionally, the data transmission method further includes: reporting the terminal capability information to an XR application server; and/or reporting a data transmission advance to an XR application server, wherein the data transmission advance is determined based on the terminal capability information.

Optionally, the terminal capability information includes at least one of: type of UE combined with HMD; combining the UE with the HMD, and processing time of the needed XR service; UE combined with HMD, required XR service handling capability; the UE, in conjunction with the HMD, requires XR traffic processing time after Uu port transmission.

Optionally, the determining a transmission delay according to the terminal capability information includes: acquiring the display time of the XR frame corresponding to the data in the HMD; determining a latest time instant when the XR frame arrives at the UE or the transmission delay according to the terminal capability information and the display time instant of the XR frame in the HMD.

Optionally, the acquiring a display time of the XR frame corresponding to the data in the HMD includes: receiving, from an XR application server, a total transmission delay and a transmission time of an nth XR frame before the XR frame, where the total transmission delay is a maximum allowable delay from when the XR application server transmits the data to when the data reaches an application layer of the UE, and N is a natural number; and determining the display time of the XR frame corresponding to the data in the HMD according to the total transmission time delay and the sending time of the Nth XR frame before the XR frame.

Optionally, the determining a transmission delay according to the terminal capability information includes: receiving, from an XR application server, a latest time when an XR frame corresponding to the data arrives at the UE or the transmission delay, where the latest time when the XR frame arrives at the UE is determined according to the terminal capability information and a display time of the XR frame in the HMD.

Optionally, the data transmission method further includes: and when the XR service is started, performing clock synchronization with the UE, the HMD, the base station and the XR application server.

To solve the above technical problem, an embodiment of the present invention further provides a data transmission device, including: an obtaining module, configured to obtain terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; a determining module, configured to determine a transmission delay according to the terminal capability information, where the transmission delay is used to indicate a maximum duration between when a network device receives the data and when the network device sends the data; and the sending module is used for sending the transmission delay.

In order to solve the above technical problem, an embodiment of the present invention further provides a data transmission method, including: acquiring transmission delay, wherein the transmission delay is used for indicating the maximum time length from the time when network equipment receives the data to the time when the network equipment sends the data, the transmission delay is determined according to terminal capability information, and the terminal capability information is used for indicating XR (X-ray diffraction) capability supported by UE (user equipment) and/or HMD (HMD); and transmitting the data according to the transmission delay.

Optionally, the obtaining the transmission delay includes: and receiving the transmission delay from the SMF.

Optionally, the obtaining the transmission delay includes: acquiring the terminal capability information and the display time of the XR frame corresponding to the data in the HMD; determining a latest time instant when the XR frame arrives at the UE or the transmission delay according to the terminal capability information and the display time instant of the XR frame in the HMD.

Optionally, the acquiring a display time of the XR frame corresponding to the data in the HMD includes: receiving a total transmission delay and a sending time of an Nth XR frame before the XR frame from an XR application server, wherein the total transmission delay is the transmission delay from the XR application server to UE, and N is a natural number; and determining the display time of the XR frame corresponding to the data in the HMD according to the total transmission time delay and the sending time of the Nth XR frame before the XR frame.

Optionally, the transmitting the data according to the transmission delay includes: and after receiving the data, transmitting the data by taking the latest moment when the XR frame reaches the UE as a constraint.

Optionally, the data transmission method further includes: and when the XR service is started, performing clock synchronization with the UE, the HMD, the SMF and the XR application server.

Optionally, the terminal capability information includes at least one of: type of UE combined with HMD; the UE is combined with the HMD, and the needed XR service processing time is shortened; the UE is combined with the HMD, and needed XR service processing capacity is achieved; the UE, in conjunction with the HMD, requires XR traffic processing time after Uu port transmission.

To solve the above technical problem, an embodiment of the present invention further provides a data transmission device, including: an obtaining module, configured to obtain a transmission delay, where the transmission delay is used to indicate a maximum duration between when a network device receives the data and when the network device sends the data, and the transmission delay is determined according to terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; and the transmission module is used for transmitting the data according to the transmission delay.

In order to solve the foregoing technical problem, an embodiment of the present invention further provides a data transmission method, including: obtaining terminal capability information, wherein the terminal capability information is used for indicating XR (X ray Rate) capabilities supported by the UE and/or the HMD; and reporting the terminal capability information.

Optionally, the data transmission method further includes: receiving data, wherein the data is transmitted according to transmission delay, the transmission delay is used for indicating the maximum time length from the time when network equipment receives the data to the time when the network equipment sends the data, and the transmission delay is determined according to terminal capability information.

Optionally, the acquiring the terminal capability information includes: acquiring capability information of the HMD; and generating the terminal capability information according to the capability information of the HMD and the capability information of the UE.

Optionally, the data transmission method further includes: receiving data; acquiring the display time of the XR frame corresponding to the data in the HMD; determining a latest time or transmission delay of the XR frame to the HMD according to the HMD capability information and the display time of the XR frame in the HMD; transmitting the data with the latest time or transmission delay of the XR frame to the HMD as a constraint.

Optionally, the data transmission method further includes: receiving data; receiving a latest moment or transmission delay reported by the HMD for transmitting the XR frame to the HMD, wherein the latest moment or transmission delay for transmitting the XR frame to the HMD is determined according to the capability information of the HMD and the display moment of the XR frame corresponding to the data in the HMD; transmitting the data with the latest time or transmission delay of the XR frame to the HMD as a constraint.

Optionally, the reporting of the terminal capability information includes: and reporting the terminal capability information to a base station, an XR application server or an SMF.

Optionally, the terminal capability information includes at least one of: the type of UE combined with HMD; combining the UE with the HMD, and processing time of the needed XR service; UE combined with HMD, required XR service handling capability; the UE, in conjunction with the HMD, requires XR traffic processing time after Uu port transmission.

Optionally, the data transmission method further includes: when the XR service is started, the clock is synchronized with the base station, HMD, SMF and XR application server.

To solve the above technical problem, an embodiment of the present invention further provides a data transmission device, including: an obtaining module, configured to obtain terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; and the reporting module is used for reporting the terminal capability information.

To solve the above technical problem, an embodiment of the present invention further provides a computer-readable storage medium, which is a non-volatile storage medium or a non-transitory storage medium, and has a computer program stored thereon, where the computer program is executed by a processor to perform the steps of the above method.

In order to solve the above technical problem, an embodiment of the present invention further provides a data transmission apparatus, including a memory and a processor, where the memory stores a computer program executable on the processor, and the processor executes the steps of the method when executing the computer program.

Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:

on a network side, such as an SMF side in a network, an embodiment of the present invention provides a data transmission method, including: acquiring terminal capability information, wherein the terminal capability information is used for indicating XR (X-ray diffraction) capabilities supported by the UE and/or the HMD; determining a transmission delay according to the terminal capability information, wherein the transmission delay is used for indicating the maximum time length from the time when the network equipment receives the data to the time when the network equipment sends the data; and sending the transmission delay.

By adopting the embodiment, the QoS of the XR service can be accurately determined according to the XR service processing capacity of the terminal, and particularly, the distribution of transmission delay at each transmission node is reasonably determined, so that the transmission of XR service data is enhanced. Specifically, the QoS of the XR service is determined according to the acquired terminal capability information. Furthermore, accurate QoS can facilitate reasonable distribution of delay budget, so that the distribution condition of the total transmission delay at each transmission node is reasonably determined.

On a network side, such as a base station side in a network, an embodiment of the present invention further provides a data transmission method, including: acquiring transmission delay, wherein the transmission delay is used for indicating the maximum time length from the time when network equipment receives the data to the time when the network equipment sends the data, the transmission delay is determined according to terminal capability information, and the terminal capability information is used for indicating XR (X-ray diffraction) capability supported by UE (user equipment) and/or HMD (HMD); and transmitting the data according to the transmission delay. Therefore, for the transmission node, whether the jitter occurs at the time when the transmission node receives the data or not, the latest time when the data is transmitted at the air interface can be determined based on the received transmission delay, so that the data is prevented from being transmitted too late.

On the UE side, an embodiment of the present invention further provides a data transmission method, including: acquiring terminal capability information, wherein the terminal capability information is used for indicating XR (X-ray diffraction) capabilities supported by the UE and/or the HMD; and reporting the terminal capability information. By adopting the embodiment, the UE actively reports the terminal capability information to the network so that the network side determines the transmission delay budget.

Drawings

FIG. 1 is a first data transmission schematic in the prior art;

FIG. 2 is a diagram of a second data transmission principle in the prior art;

fig. 3 illustrates three types of combinations of UE and HMD involved in XR service in the prior art;

fig. 4 is a flowchart of a data transmission method according to a first embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a data transmission apparatus according to a second embodiment of the present invention;

fig. 6 is a flowchart of a data transmission method according to a third embodiment of the present invention;

fig. 7 is a schematic structural diagram of a data transmission device according to a fourth embodiment of the present invention;

fig. 8 is a flowchart of a data transmission method according to a fifth embodiment of the present invention;

fig. 9 is a schematic structural diagram of a data transmission apparatus according to a sixth embodiment of the present invention;

FIG. 10 is a signaling interaction diagram of an exemplary application scenario in accordance with an embodiment of the present invention;

FIG. 11 is a schematic diagram of signaling interaction of a variation of phase 1 in the application scenario shown in FIG. 10;

FIG. 12 is a signaling interaction diagram of a first variation of phase 2 in the application scenario of FIG. 10;

FIG. 13 is a signaling interaction diagram of a second variation of phase 2 in the application scenario of FIG. 10;

fig. 14 is a schematic signaling interaction diagram of a third variation of phase 2 in the application scenario shown in fig. 10.

Detailed Description

As background art, the existing network does not know the capability of the terminal to process XR service data in advance, and thus cannot determine the distribution condition of the transmission delay budget of the XR service at each transmission node, and cannot accurately determine QoS.

Specifically, video data (also called XR service data) transmitted by an XR service is generated from an XR Application Server (XR APP Server), enters a third Generation Partnership Project (3 GPP) network through an Internet Protocol (IP) network, is finally transmitted to a terminal through a core network router and a base station, and is displayed to a user by the terminal. The network elements through which XR traffic data passes throughout the transmission are shown in fig. 1 or fig. 2. Fig. 1 shows a transmission flow of XR service data when an edge cloud (edge cloud) is not adopted in a network. Specifically, after receiving XR service data sent by the XR application server, the IP network directly transmits the XR service data to the UE through a User Plane Function (UPF) and a base station (e.g., a gNB). Fig. 2 shows a transmission flow of XR service data when the network adopts an edge cloud. Specifically, the XR service data sent by the XR application server is received by the IP network and then sent to the UPF, the XR service data is subjected to UPF and then to some application layer processing (such as rendering, synthesis, and the like) by the edge cloud, and the XR service data subjected to the edge cloud processing is transmitted to the UE by the base station.

On the other hand, in the existing network transmission service data flow, since the functional parameters of the UE are different, the 3GPP protocol defines many optional functions, such as whether to support 1024 Quadrature Amplitude Modulation (QAM), whether to support multiple connections, and the like. Correspondingly, after the UE accesses the network, the base station can configure appropriate wireless parameters for the UE according to the UE capability.

Currently, there are three types of terminals involved in XR determined by 3GPP, and the distribution of functions involved is shown in fig. 3. In this embodiment, the term "terminal" refers to a combination result of a UE and a Head Mounted Display (HMD), where the UE is a receiving end of XR service data, typically a 5G terminal, such as a 5G mobile phone (5G phone), and the HMD is a presenting end of XR service data, such as AR glasses (AR glass).

Referring to fig. 3, for the type 1 terminal, the type of terminal is an HMD, i.e. the UE and HMD are integrated. A type 1 terminal integrally performs all functions of a terminal side including rendering, composition, decoding, etc., and finally presents video and audio to a user. That is to say, after receiving XR service data transmitted by a User to Network interface Universal (Uu) interface (Uu interface for short) through a Network, the terminal of type 1 locally completes all function processing at the terminal side and then locally presents an XR frame (i.e., a video frame of the XR service). Since all functions are performed at the terminal, the terminal of type 1 is cumbersome and uncomfortable to wear.

With continued reference to fig. 3, for type 2 terminals, the UE is also grouped with the HMD. But unlike the terminal of type 1, the terminal of type 2 performs a simpler function, i.e. only decoding. And the other XR service data processing is completed by the edge cloud, such as rendering, synthesis and the like. That is to say, XR service data transmitted by the network is subjected to partial function processing by the edge cloud, and then transmitted to the terminal of type 2 through the Uu port, and the terminal of type 2 locally performs the remaining partial function processing and then locally presents the video frame. The type 2 terminal carries less functions than the type 1 terminal, and is therefore lighter and more comfortable to use.

With continued reference to fig. 3, for a type 3 terminal, the UE and HMD are physically separated, with data being transmitted between the two over Wi-Fi. This allows most of the data processing functions to be placed on the UE side, such as rendering and compositing, while the HMD is only responsible for decoding. That is to say, after the 5G mobile phone receives XR service data transmitted by the network through the Uu port, after the 5G mobile phone locally completes partial function processing, the XR service data is transmitted to the HMD through the Wi-Fi, and after the HMD locally completes the remaining partial function processing, the frame of video frame is presented to the user. In this way, the HMD in the type 3 terminal is as thin and light as the type 2 terminal, and comfortable to use.

As can be seen from fig. 3, when the network transmits XR service data to the terminal, the position of the time window reserved for Uu port data transmission may be different according to the type of the terminal. Assuming that the total downlink delay budget (i.e., the end-to-end transmission delay of the application layer) of a video frame is 30 milliseconds (ms), the results of the delay allocation performed by the network are different for different types of terminals.

For a type 1 terminal, 10ms is required for HMD to complete rendering, composition, decoding, etc., and 10ms is required for uu port transmission. The UPF must pass the data of the video frame to the base station 10ms in advance.

For a type 2 terminal, 5ms is required for HMD to complete decoding and 10ms is required for uu port transmission. The UPF must pass the data of the video frame to the base station 15ms ahead.

For a type 3 terminal, 5ms is needed for HMD to complete decoding, 1ms is needed for wi-Fi transmission, and 3ms is needed for UE to complete rendering and synthesis. The UPF must pass the data for the video frame to the base station 16ms in advance.

If the network does not know the type of the combination of the UE and the HMD in advance, the distribution of the service delay at each transmission node cannot be determined, and the QoS cannot be accurately determined.

According to the specification of the existing protocol, after the UE establishes a connection with the base station, the base station requests the UE capability information from an Access and Mobility Management Function (AMF) in the core network. If the UE is connected with the network for the first time and the AMF does not store the UE capability information, the base station requests the UE for the information. After the UE reports the self capability information, the base station configures the wireless parameters matched with the capability for the UE. And then, the base station uploads the capability information of the UE to the AMF for storage. Thereafter, the UE maintains its capability information in the AMF even though it is disconnected from the base station. After the UE establishes connection with the base station next time, the base station only needs to acquire the UE capability information from the AMF, and the UE does not need to be reported.

In the prior art, when a service is established, a base station obtains QoS information of the service, which includes a delay budget parameter, which means "maximum tolerable delay of each data packet at an air interface". In the service transmission process, the base station starts timing from the time when the UPF receives the data packet, and if the data packet is not transmitted out after the maximum allowable time delay, the base station abandons the transmission. That is, the base station takes the time at which the packet arrives as the start time of the "maximum allowable delay".

However, the existing protocol specifies that the capability information reported by the UE only relates to the access layer capability of the UE and does not relate to the XR processing capability of the UE, so that the problem of delay budget allocation of XR services cannot be solved.

The XR service has a large data volume and is dense in data packets. Therefore, packets may experience queuing congestion within the IP network or within the UPF before reaching the base station, causing jitter in the timing of the arrival of the packets at the base station.

If a certain delay of "XR application server to HMD" is to be achieved, i.e. a fixed application layer end-to-end transmission delay. The "maximum allowable delay" of each packet in the air is actually different for the base station when the packet with jitter at the arrival time is received. For example, for a packet arriving late at the base station, its "maximum allowable delay" at the air interface becomes smaller. For another example, for a data packet arriving earlier at the base station, the "maximum allowable delay" at the air interface is larger.

However, according to the existing QoS architecture, the base station cannot sense the packet jittering when arriving at itself, and thus cannot realize the flexible "maximum allowable delay".

In addition, for different types of terminals, after receiving the data packet, the processing time required for processing the data packet is different before displaying the data packet by the HMD. If the processing time length required by the UE cannot be determined before determining the "maximum transmission delay", the "maximum transmission delay" of the data packet cannot be accurately determined.

To solve the foregoing technical problem, an embodiment of the present invention provides a data transmission method, including: acquiring terminal capability information, wherein the terminal capability information is used for indicating XR (X-ray diffraction) capabilities supported by the UE and/or the HMD; determining a transmission delay according to the terminal capability information, wherein the transmission delay is used for indicating the maximum time length from the time when the network equipment receives the data to the time when the network equipment sends the data; and sending the transmission delay.

In order to make the aforementioned objects, features and advantages of the present invention more comprehensible, embodiments accompanying figures are described in detail below.

Fig. 4 is a flowchart of a data transmission method according to a first embodiment of the present invention.

The embodiment can be applied to an XR scene, and the data transmitted by the embodiment is XR service data. In an XR scenario, XR video generated by an XR application server is transmitted to a terminal through a network and is presented, and the data corresponds to one or more XR frames in the XR video.

The present embodiment may be applied to the network side, as performed by a network device of the network side. The network device may include a node in a core network, such as an AMF or a Session Management Function (SMF) in the core network.

One or more nodes in the core network may be understood as transfer nodes through which data is transferred from the XR application server to the terminal.

By adopting the embodiment, the time delay budgets of the transmission nodes can be reasonably distributed according to the XR data processing capacity of the terminal on the premise of meeting the total transmission time delay, and the data is prevented from being transmitted to the terminal too late. Wherein, the total transmission delay is a maximum allowable delay from the point when the XR application server sends the XR service data to the point when the XR service data reaches the application layer of the UE, and N is a natural number. The total transmission delay, which may also be referred to as an application layer end-to-end transmission delay, is related to the service characteristics, and may be determined at the time of starting the XR service and notified to the core network by the XR application server. The core network reasonably distributes the delay budget of each transmission node based on the total transmission delay so as to ensure that the data can reach the UE within the end-to-end transmission delay of the application layer.

In a specific implementation, the transmission method provided in steps S101 to S103 may be executed by a chip having a data transmission function in the network device, or may be executed by a baseband chip in the network device.

Specifically, referring to fig. 4, the data transmission method according to this embodiment may include the following steps:

step S101, terminal capability information is obtained, wherein the terminal capability information is used for indicating XR (X-ray diffraction) capability supported by UE (user equipment) and/or HMD (HMD);

step S102, determining a transmission delay according to the terminal capability information, wherein the transmission delay is used for indicating the maximum time length between the time when the network equipment receives the data and the time when the network equipment sends the data;

and step S103, sending the transmission time delay.

In one implementation, the terminal capability information includes UE capability information indicating XR capabilities supported by the UE and HMD capability information indicating XR capabilities supported by the HMD.

In particular, the terminal capability information may include types of the UE in combination with the HMD, such as the three types illustrated in fig. 3 above, as well as other extended types that may be defined in the future. Such as replacing a Wi-Fi connection in a type 3 terminal with a wired connection, etc. Correspondingly, the network side can determine XR service processing time required by combining the UE and the HMD according to the type reported by the UE.

Further, the terminal capability information may include XR service processing time required for the UE to engage with the HMD. That is, the UE may directly report the XR service processing time required for combining itself with the HMD. For example, the XR transaction processing time required for the UE to engage with the HMD may be the sum of the time required for the UE to complete a portion of the functional processing and the time required for the HMD to complete the remainder of the functional processing, and may also include the time required to transfer data between the UE and the HMD. The functions that the UE and the HMD need to perform may refer to the related description in fig. 3, which is not repeated herein.

In the UE and HMD combination, the required XR service processing time may be average time, maximum time, variance, or the like.

Further, the terminal capability information may include XR service processing capabilities required by the UE in conjunction with the HMD. For example, a maximum of X bytes (bytes) of data per second can be processed, and for example, a maximum of Y video frames (i.e., XR frames) per second can be processed.

Further, the terminal capability information may include XR service processing time required by the UE in conjunction with the HMD after Uu port transmission. For the type 1 terminal, the processing time after Uu port transmission is the time length required for rendering, synthesizing and decoding. For the type 2 terminal, the processing time after Uu port transmission is the time length required for decoding. For a type 3 terminal, the processing time after Uu port transmission is the sum of the time lengths required for rendering, composition, wi-Fi transmission, and decoding.

In a specific implementation, the network side may store, in advance, terminal capability information reported by the UE that has been connected historically, and correspondingly, the step S101 may include the steps of: and searching a preset database to obtain the terminal capability information associated with the UE, wherein the preset database records the association relationship between the UE and the terminal capability information.

Specifically, the preset database may be stored in the AMF. For example, the UE reports the terminal capability information when initially accessing the network, and the network stores the terminal capability information in a preset database of the AMF. When the UE accesses the network again, the network side directly acquires the terminal capability information reported by the UE from the AMF without reporting the terminal capability information again.

Further, the preset database may store an association relationship between the unique identifier of the UE and the terminal capability information. When step S101 is executed, a preset database is searched according to the unique identifier of the UE currently accessing the network and needing XR service, so as to obtain the associated terminal capability information.

In a variation, taking a split-connected UE such as a type 3 terminal and HMD as an example, different terminal capability information may be generated by connecting the same UE to different HMDs, or by using different transmission schemes (e.g., wi-Fi transmission or wired connection) between the UE and the HMDs.

Correspondingly, the same UE in the preset database can be associated with a plurality of pieces of terminal capability information, and the terminal capability information is respectively connected with different HMDs correspondingly or scenes of the HMDs in different modes.

When step S101 is executed, the corresponding terminal capability information is searched in the preset database according to the unique identifier of the UE currently accessing the network and needing XR service and the unique identifier of the HMD to which the UE is currently connected.

Or, when step S101 is executed, the corresponding terminal capability information is searched in the preset database according to the unique identifier of the UE currently accessing the network and needing XR service, and the specific connection mode between the UE and the HMD.

In a variation, the step S101 may include the steps of: and receiving the terminal capability information reported by the UE.

For example, for a UE initially accessing a network, since the AMF does not store the terminal capability information of the UE, the UE needs to report the terminal capability information to the network.

For another example, the terminal capability information may not be stored in the AMF, and the UE actively reports the terminal capability information each time the UE accesses the network.

Further, the HMD may report its own capability information to the network side by itself. Accordingly, in step S101, the SMF may receive the UE capability information reported by the UE and receive the HMD capability information reported by the HMD.

Further, the specific process of the network side receiving the terminal capability information reported by the UE may include: and receiving the terminal capability information reported by the UE from a base station. That is, the UE reports the terminal capability information to the base station, and the base station reports the terminal capability information to one or more nodes of the core network step by step, and finally reports the terminal capability information to the XR application server. This example is a bottom-up reporting procedure.

For example, the base station may report the terminal capability information reported by the UE to the AMF, the SMF, and a Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF for short), respectively.

Or, the network side may receive the terminal capability information reported by the UE from an XR application server. That is, the UE reports the terminal capability information to the XR application server, and the terminal capability information is transmitted to the core network and the base station by the XR application server stage by stage. This example is a top-to-bottom reporting procedure.

For example, the 5G core network nodes such as PCRF, SMF, and AMF may learn the terminal capability information from the XR application server side, and then notify the base station. Alternatively, the base station may not know the terminal capability information of the terminal. Correspondingly, when the XR service is established, the QoS of the XR service is determined by the core network node, and the base station only needs to execute the operation according to the QoS.

In one implementation, after step S101, the SMF may further perform the steps of: and reporting the terminal capability information to an XR application server. So that the XR application server takes into account the actual processing capabilities of the terminal when determining the QoS for the terminal's XR traffic.

For example, according to the terminal capability information, the XR application server may know the time length required for the terminal to process the video frame, so as to determine the appropriate data transmission advance. The data transmission advance is that the XR application server needs to send out a data packet of the XR frame x milliseconds (ms) before the display time of the XR frame in the HMD.

Further, the data transmission advance may be a time length required for the terminal side to process the XR frame. Alternatively, the data transmission advance may be such that the XR application server is required to send out the frame data xms before the display time at which the HMD displays the XR frame.

Alternatively, the XR application server may not know the terminal capability information of the terminal. This is because the UE and HMD perform the same functions regardless of the type of terminal. For a particular function, whether placed in UE-side processing or HMD-side processing, it may be imperceptible to the XR application server.

In a variation, in response to the terminal capability information obtained in step S101, the SMF may calculate the data transmission advance and report the data transmission advance to the XR application server.

For example, according to the combination of the UE and the HMD in the terminal capability information, the required XR service processing time, the AMF or the SMF may calculate the data transmission advance and notify the data transmission advance to the XR application server.

For type 1 terminals, the core network node (e.g., AMF) may determine the time margin left for the XR application server based on the XR traffic handling capabilities reported by the terminal. Specifically, the time length in the terminal capability information acquired at step S101 at this time may be the time required for rendering, synthesizing, and decoding.

For a type 2 terminal, the core network node may determine the time margin left for the XR application server in combination with the processing capability of the edge cloud and the XR service processing capability reported by the terminal. Specifically, the time length in the terminal capability information acquired at step S101 at this time may be the time required for decoding.

For a type 3 terminal, the core network node may determine the time margin left for the XR application server in combination with the XR service processing capabilities reported by the terminal. Specifically, the time length in the terminal capability information acquired in step S101 at this time may be the time required for decoding.

In one implementation, the step S102 may include the steps of: acquiring the display time of the XR frame corresponding to the data in the HMD; determining a latest time instant when the XR frame arrives at the UE or the transmission delay according to the terminal capability information and the display time instant of the XR frame in the HMD.

Specifically, the display time of the XR frame in the HMD may be notified to the core network node by the XR application server through a session start procedure.

Further, the SMF determines the time required by the terminal to process the data packet according to the acquired terminal capability information, and in combination with the display time of the XR frame in the HMD, it can calculate the time when the XR frame needs to reach the terminal at the latest, that is, the latest time when the XR frame reaches the UE. The latest time can be understood as the latest time of Uu port transmission.

Further, according to the transmission delay and the time when the XR frame is received, the latest time when the XR frame reaches the UE can be calculated.

In one implementation, the display time of the XR frame in the HMD may be self-calculated by the network side.

Specifically, the network side may receive the total transmission delay and the transmission time of the nth XR frame before the XR frame from the XR application server. Then, according to the total transmission delay and the sending time of the Nth XR frame before the XR frame, the display time of the XR frame corresponding to the data in the HMD is determined.

Wherein the data may correspond to one or more XR frames, wherein a display time of each XR frame in the HMD is determined based on the total transmission latency and a transmission time of an Nth XR frame prior to the XR frame.

Further, the information obtained from the XR application server may also include XR frame intervals to derive the transmission time and display time for each frame.

Therefore, on a network side, such as an SMF side in a network, by using the embodiment, the QoS of the XR service can be accurately determined according to the XR service processing capability of the terminal, and particularly, the distribution of transmission delay to each transmission node is reasonably determined, so that the transmission of XR service data is enhanced. Specifically, the QoS of the XR service is determined according to the acquired terminal capability information. Furthermore, accurate QoS can be beneficial to reasonably allocating delay budget, so that the allocation condition of the total transmission delay at each transmission node is reasonably determined.

In a variation on the embodiment shown in fig. 4, the data transmission method shown in fig. 4 may be performed by the XR application server. Specifically, the XR application server may execute steps S101 to S103 shown in fig. 4 to determine a transmission delay according to the acquired terminal capability information, and send the transmission delay to the SMF.

Further, the terminal capability information may be directly obtained from the UE and the HMD. Alternatively, the step S101 may include the steps of: and acquiring the terminal capability information from the SMF.

Further, the display time of the XR frame in the HMD may be calculated by the XR application server and then notified to the network side. Accordingly, the latest time when the XR frame corresponding to the data arrives at the UE or the transmission delay may be determined by the XR application server and then notified to the SMF.

Specifically, the terminal capability information of the terminal may be directly reported to the XR application server or reported to the XR application server through the network side. Therefore, the XR application server may determine the latest time when the XR frame arrives at the UE or the transmission delay and notify the base station through the core network when the XR service is started, according to the emission time of the XR frame, the total transmission delay, and the processing time of the XR frame in the UE and the HMD.

Accordingly, the network side may receive the latest time when the XR frame corresponding to the data arrives at the UE from the XR application server, and notify the base station.

Fig. 5 is a schematic structural diagram of a data input device according to a second embodiment of the present invention. Those skilled in the art understand that the data transmission device 2 of the present embodiment may be used to implement the method technical solution described in the above embodiment of fig. 4.

Specifically, referring to fig. 5, the data transmission device 2 according to this embodiment may include: an obtaining module 21, configured to obtain terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; a determining module 22, configured to determine a transmission delay according to the terminal capability information, where the transmission delay is used to indicate a maximum duration between when a network device receives the data and when the network device sends the data; a sending module 23, configured to send the transmission delay.

For more details of the operation principle and the operation mode of the data transmission device 2, reference may be made to the related description in fig. 4, which is not described herein again.

In a specific implementation, the data transmission device 2 may correspond to a Chip having a data transmission function in a network device, or correspond to a Chip having a data processing function, such as a System-On-a-Chip (SOC), a baseband Chip, or the like; or the chip module group is corresponding to the network equipment and comprises a chip with a data transmission function; or to a chip module having a chip with a data processing function, or to a network device.

In a specific implementation, each module/unit included in each apparatus and product described in the foregoing embodiments may be a software module/unit, may also be a hardware module/unit, or may also be a part of a software module/unit and a part of a hardware module/unit.

For example, for each device or product applied to or integrated into a chip, each module/unit included in the device or product may be implemented by hardware such as a circuit, or at least a part of the module/unit may be implemented by a software program running on a processor integrated within the chip, and the rest (if any) part of the module/unit may be implemented by hardware such as a circuit; for each device and product applied to or integrated with the chip module, each module/unit included in the device and product may be implemented by hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least part of the modules/units may be implemented by a software program running on a processor integrated inside the chip module, and the rest (if any) part of the modules/units may be implemented by hardware such as a circuit; for each device and product applied to or integrated in the terminal, each module/unit included in the device and product may be implemented by hardware such as a circuit, different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least part of the modules/units may be implemented by a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules/units may be implemented by hardware such as a circuit.

Fig. 6 is a flowchart of a data transmission method according to a third embodiment of the present invention. The embodiment of fig. 6 may be applied on the network side, as performed by a network device on the network side. The network device may include a base station. The SMF implementing the embodiment shown in fig. 4 described above sends a transmission delay to the base station, which implements this embodiment to transmit XR service data to the UE.

In a specific implementation, the transmission method provided in steps S201 to S202 described below may be executed by a chip having a data transmission function in the network device, or may be executed by a baseband chip in the network device.

Specifically, referring to fig. 6, the data transmission method according to this embodiment may include the following steps:

step S201, obtaining a transmission delay, wherein the transmission delay is used for indicating the maximum time length between the time when the network equipment receives the data and the time when the network equipment sends the data, the transmission delay is determined according to terminal capability information, and the terminal capability information is used for indicating XR (X-ray diffraction) capability supported by the UE and/or the HMD;

step S202, transmitting the data according to the transmission delay.

Those skilled in the art understand that the steps S201 to S202 can be regarded as execution steps corresponding to the steps S101 to S103 described in the above embodiment shown in fig. 4, and the two steps are complementary in specific implementation principle and logic. Therefore, the explanation of the terms in the present embodiment may refer to the description related to the embodiment shown in fig. 4, and will not be repeated herein.

In one implementation, step S201 may include: receiving the transmission delay from the SMF.

In one variation, step S201 may include: acquiring the terminal capability information and the display time of the XR frame corresponding to the data in the HMD; determining the latest time or the transmission delay of the XR frame to reach the UE according to the terminal capability information and the display time of the XR frame in the HMD.

For example, the base station may determine the time required by the terminal to process the data packet according to the terminal capability information reported by the UE, and further calculate the latest time when the XR frame reaches the UE according to the display time of the XR frame notified by the SMF in the HMD.

Further, the base station may acquire the terminal capability information from the UE. Alternatively, the base station may acquire the terminal capability information from the core network.

Further, the base station may receive from the XR application server the total transmission delay and the time of transmission of the nth XR frame prior to said XR frame. Then, the display time of the XR frame corresponding to the data in the HMD is determined according to the total transmission time delay and the sending time of the Nth XR frame before the XR frame.

In one implementation, step S202 may include: and after receiving the data, transmitting the data by taking the latest moment when the XR frame reaches the UE as a constraint.

Specifically, as a transmission node, after receiving the data, the base station transmits the data with the constraint of the latest time when the XR frame corresponding to the data arrives at the UE.

For example, if the data is received after the latest time when the XR frame corresponding to the data arrives at the UE, the base station does not transmit the data any more.

Therefore, after the base station receives the data, whether the time of receiving the data is jittered or not can be determined based on the embodiment at the latest time of the data transmission at the air interface so as to reasonably determine the subsequent execution logic. Further, after the base station knows the latest time when the XR frame reaches the UE, the base station can dynamically determine the "maximum allowable delay" of data transmission over the air interface even if the data received from the gateway jitters.

Fig. 7 is a schematic structural diagram of a data transmission apparatus according to a fourth embodiment of the present invention. Those skilled in the art understand that the data transmission device 3 according to this embodiment may be used to implement the method technical solution described in the embodiment of fig. 6.

Specifically, referring to fig. 7, the data transmission device 3 according to this embodiment may include: an obtaining module 31, configured to obtain a transmission delay, where the transmission delay is used to indicate a maximum duration between when a network device receives the data and when the network device sends the data, and the transmission delay is determined according to terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; and a transmission module 32, configured to transmit the data according to the transmission delay.

For more details of the operation principle and the operation mode of the data transmission device 3, reference may be made to the related description in fig. 7, which is not repeated here.

In a specific implementation, the data transmission device 3 may correspond to a Chip having a data transmission function in a network device, or correspond to a Chip having a data processing function, such as a System-On-a-Chip (SOC), a baseband Chip, or the like; or the chip module group is corresponding to the network equipment and comprises a chip with a data transmission function; or to a chip module having a chip with a data processing function, or to a network device.

For example, for each device or product applied to or integrated into a chip, each module/unit included in the device or product may be implemented by hardware such as a circuit, or at least a part of the module/unit may be implemented by a software program running on a processor integrated within the chip, and the rest (if any) part of the module/unit may be implemented by hardware such as a circuit; for each device or product applied to or integrated with the chip module, each module/unit included in the device or product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be implemented by using a software program running on a processor integrated within the chip module, and the rest (if any) of the modules/units may be implemented by using hardware such as a circuit; for each device and product applied to or integrated in the terminal, each module/unit included in the device and product may be implemented by hardware such as a circuit, different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least part of the modules/units may be implemented by a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules/units may be implemented by hardware such as a circuit.

Fig. 8 is a flowchart of a data transmission method according to a fifth embodiment of the present invention. The embodiment of fig. 8 may be applied to the user equipment side, as performed by a UE of the user equipment side.

In a specific implementation, the transmission method provided in steps S401 to S402 described below may be executed by a chip having a data transmission function in the user equipment, or may be executed by a baseband chip in the user equipment.

Specifically, referring to fig. 8, the data transmission method according to this embodiment may include the following steps:

step S401, terminal capability information is obtained, wherein the terminal capability information is used for indicating XR (X-ray diffraction) capability supported by the UE and/or the HMD;

and step S402, reporting the terminal capability information.

Those skilled in the art understand that the steps S401 to S402 can be regarded as execution steps corresponding to the steps S101 to S103 described in the above embodiment shown in fig. 4, and the two steps are complementary in specific implementation principle and logic. Therefore, the explanation of the terms in the present embodiment may refer to the description related to the embodiment shown in fig. 4, and will not be repeated herein.

In one implementation, in step S401, the 5G UE may report the terminal capability information to the base station. Or, the 5G UE may directly report the terminal capability information to the SMF.

In a variation, in step S401, the application layer of the 5G UE may report the terminal capability information to the XR application server. Alternatively, the terminal capability information may be reported to the XR application server by the HMD to which the UE is connected.

In one implementation, step S401 may include the steps of: acquiring capability information of the HMD; and generating the terminal capability information according to the capability information of the HMD and the capability information of the UE.

For example, the UE may combine the capability information of the HMD processing data interacted with the HMD with the capability information of the UE itself processing data to generate capability information common to the UE and the HMD, i.e., the terminal capability information.

Further, the UE may obtain the capability information of the HMD directly from the HMD, or through other approaches. For example, the UE may obtain the capability information of the HMD from a network management center, a base station, other control network elements, or a manner predefined by a protocol.

Further, the act of acquiring capability information of the HMD may be performed upon initiation of the XR service, or may be performed after the HMD is powered on.

In a specific implementation, after step S402, the data transmission method according to this embodiment may further include the steps of: receiving data, wherein the data is transmitted according to transmission delay, the transmission delay is used for indicating the maximum time length from the time when network equipment receives the data to the time when the network equipment sends the data, and the transmission delay is determined according to terminal capability information.

Therefore, in this embodiment, the 5G UE actively reports the terminal capability information, so that the network side executes the solution shown in fig. 4 or fig. 6 to determine an appropriate transmission delay according to the terminal capability information, and further transmit data according to the transmission delay. Accordingly, the 5G UE can receive the data sent by the network within a reasonable transmission delay.

In one implementation, for a type 3 terminal, that is, when the HMD and the UE are connected in a split manner, the UE may also serve as a transmission node, and thus, a delay budget allocated to the UE also needs to be considered.

Correspondingly, after step S402, the transmission method according to this embodiment may further include the steps of: receiving data; receiving a latest moment or transmission delay reported by the HMD for transmitting the XR frame to the HMD, wherein the latest moment or transmission delay for transmitting the XR frame to the HMD is determined according to the capability information of the HMD and the display moment of the XR frame corresponding to the data in the HMD; transmitting the data with the latest time or transmission delay of the XR frame to the HMD as a constraint.

In particular, the display instant of an XR frame in the HMD may be known by signaling. The UE may obtain the display time of the XR frames in the HMD from a base station or may obtain the display time of the XR frames in the HMD from an XR application server through application layer interaction with the XR application server.

Further, based on the HMD's capability information and the display time of the XR frames in the HMD, the UE may determine a latest time to transmit data over the Wi-Fi interface. If the UE has not been able to transmit the data for the XR frame over the Wi-Fi interface at the latest time, the UE need not retransmit.

In one variation, the latest time to transmit the XR frame to the HMD may be determined by the HMD and reported to the UE.

Specifically, after step S402, the transmission method according to this embodiment may further include the steps of: receiving a latest moment reported by the HMD at which the XR frame is transmitted to the HMD; upon receiving the data, transmitting the data with the constraint of the latest time instant at which the XR frame was transmitted to the HMD.

Further, the HMD may acquire a display instant of the XR frame in the HMD from an XR application server or the UE.

In practical applications, the HMD may report to the UE the latest time at which the XR frames were transmitted to the HMD at any time after the XR service is initiated.

Therefore, at the UE side, by using the embodiment, the UE actively reports the capability of the UE and the HMD for processing data to the network, so that the network side determines the transmission delay budget.

Fig. 9 is a schematic structural diagram of a data transmission device according to a sixth embodiment of the present invention. Those skilled in the art will appreciate that the data transmission device 4 shown in fig. 9 may be used to implement the method solution described in the above embodiment shown in fig. 8.

Specifically, referring to fig. 9, the data transmission device 4 according to this embodiment may include: an obtaining module 41 is configured to obtain terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; and a reporting module 42, configured to report the terminal capability information.

For more details of the operation principle and the operation mode of the data transmission device 4, reference may be made to the related description in fig. 8, and details are not repeated here.

In a specific implementation, the data transmission device 4 may correspond to a Chip having a data transmission function in the user equipment, or correspond to a Chip having a data processing function, such as a System-On-a-Chip (SOC), a baseband Chip, or the like; or the chip module group comprises a chip with a data transmission function in the corresponding user equipment; or to a chip module having a chip with data processing function, or to a user equipment.

For example, for each device or product applied to or integrated into a chip, each module/unit included in the device or product may be implemented by hardware such as a circuit, or at least a part of the module/unit may be implemented by a software program running on a processor integrated within the chip, and the rest (if any) part of the module/unit may be implemented by hardware such as a circuit; for each device or product applied to or integrated with the chip module, each module/unit included in the device or product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be implemented by using a software program running on a processor integrated within the chip module, and the rest (if any) of the modules/units may be implemented by using hardware such as a circuit; for each device and product applied to or integrated in the terminal, each module/unit included in the device and product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules/units may be implemented by using hardware such as a circuit.

In a typical application scenario, referring to fig. 10, data generated by the xr application server 53 is transmitted via the network side 52 to the terminal 51 for display. Wherein, the terminal 51 includes an HMD511 and a UE512, and the UE512 executes the method described in fig. 8; the network side 52 includes a base station 521 and one or more nodes of a core network, such as the AMF522, the SMF523, and the PCRF524, where the one or more nodes of the network side 52, such as the SMF523, may perform the method in the embodiment shown in fig. 4, and the base station 521 may perform the method in the embodiment shown in fig. 6.

The transmission flow of data in the application scenario may include multiple stages. First, in phase 1, the terminal 51 may report its own terminal capability information. Then, in phase 2, the XR application server 53, the node on the network side 52, and the UE512 serve as data transmission nodes, which can determine XR service delay allocation according to the terminal capability information reported by the terminal 51, and perform data transmission according to the allocated delay budget.

The following is a detailed description of a specific implementation flow of each stage.

With continued reference to fig. 10, in stage 1, the ue512 may perform operation s801 to report terminal capability information of the terminal 51 to the base station 521. For example, the terminal capability information of the terminal 51 may include a combination type of the UE512 and the HMD 511.

For example, the UE512 may report the terminal capability information through a Radio Resource Control (RRC) message. For another example, the UE512 may also report through a Packet Data Convergence Protocol (PDCP) Control Protocol Data Unit (PDU), a Radio Link Control (RLC) PDU or a Media Access Control Element (MAC-CE), and may also report through a Non-Access Stratum (NAS) signaling.

When the terminal capability information is reported through the NAS signaling, since the base station 521 cannot directly read the NAS signaling, the reported terminal capability information is transparently transferred to the AMF522 through the base station 521, and then the AMF522 notifies the base station 521.

Further, operation s802 may be continued to report the terminal capability information to one or more core network nodes via the base station 521. For example, the base station 521 may report the terminal capability information of the terminal 51 to the AMF522, the AMF522 further reports the terminal capability information to the SMF523, and the SMF523 further reports the terminal capability information to the PCRF524.

It should be noted that the reporting sequence between the core network nodes is only an example, and in practical applications, the core network nodes that need to be reported and the reporting sequence between the nodes may be adjusted as needed.

In response to receiving the terminal capability information for terminal 51, each core network node may use this information to determine the XR traffic delay assignment for UE512 at stage 2.

PCRF524 may use this information to determine XR traffic charging for UE512. This is to consider that, in the three terminal types, when the same service is performed, the data volume transmitted by the terminal 51 of type 2 at the Uu port is larger than the data volume transmitted by the terminal 51 of type 1 or type 3 at the Uu port, so that the corresponding charging function module needs to be considered in the charging process.

Further, the core network node (e.g. PCRF 524) may perform operation s803 to report the terminal capability information of the terminal 51 to the XR application server 53. Accordingly, the XR application server may consider UE capabilities when determining XR traffic QoS for UE512 in phase 2.

It should be noted that the specific message format transmitted in each step in phase 1 may be the same or different. When each node transmits a message to the next node, the message format can be adjusted according to the message specification of the interface, but the transmission basic content is the same.

Thus, by executing the process described in stage 1, the UE512 may report the type of the data processed by the UE512 and the HMD511 and the required processing duration to the network 52, so that the network 52 determines the transmission delay budget.

With continued reference to fig. 10, at stage 2, the base station 521 may first complete clock synchronization with the UE512, HMD511, and XR application server 53.

Then, the XR application server 53 performs operation s804 to notify the core network node (e.g., SMF 523) of "display time of the XR frame in the HMD 511" through a session start procedure when the XR service is started. For example, the XR application server 53 may inform the SMF523 by operation s804 that the first XR frame of the XR service is displayed in the HMD511 at the time of 2021 year 3 month 5 day 14: and (4) dividing into 37 parts: and (3) 23 seconds: 345ms, after which an XR frame is displayed every 16 ms.

Further, SMF523 may perform operation s805 to notify base station 521 of the new QoS parameters for the XR service: uu transmits each XR frame at a time, which is "the time the XR frame is displayed in HMD 511".

Further, the base station 521 may perform operation s806 to determine the latest time instant for transmitting each XR frame by the Uu port according to the type of the terminal 51 and the processing time of the data. For example, if the base station 521 determines that the terminal 51 needs 15ms to process data according to the type of the terminal 51, it determines that the data packet included in the first XR frame needs to be processed at 14

days

3, 5 and 3 in 2021: and (4) dividing into 37 parts: and (3) 23 seconds: terminal 51 was sent 330ms ago, and terminal 51 needs to be sent one XR frame every 16ms thereafter.

Based on this, when the base station 521 receives the data packet corresponding to the XR frame, the latest time when the data packet is transmitted over the air interface (i.e., uu interface) can be determined regardless of whether the time when the data packet is received is jittered.

Thus, in stage 2, the base station 521 determines the latest time of the air interface for transmitting the XR data packet, and may determine a reasonable latest time of the XR data packet transmission on the premise that the base station 521 receives the downlink data and jitters.

In a variation, unlike the process of reporting the terminal capability information from bottom to top in the phase 1 shown in fig. 10, the reporting of the terminal capability information in the phase 1 may also be performed from top to bottom as shown in fig. 11.

Specifically, referring to fig. 11, the application layer of the ue512 may perform operation s901 to report the terminal capability information of the combination of itself and the HMD to the XR application server 53.

Further, operation s902 may be continued to notify one or more nodes of the network side 52 of the terminal capability information reported by the UE512 via the XR application server 53. For example, XR application server 53 may notify PCRF524 of terminal capability information, then notify SMF523 by PCRF524, and then notify AMF522 by SMF 523.

Further, the core network node (e.g. AMF 522) may perform operation s903 to notify the base station 521 of the terminal capability information reported by the UE512.

Alternatively, operation s901 may be replaced by operation s901', i.e. the HMD511 reports the terminal capability information of the terminal 51 to the XR application server 53.

Therefore, the UE512 may report the type of data processed by the UE512 and the HMD511 and the required processing duration to the XR application server 53, and then the XR application server 53 notifies the core network and the access network, so that the network side 52 determines the transmission delay budget.

In a variation, the action of the operation s806 in phase 2 shown in fig. 10 may be performed by a core network node (e.g., the SMF 523), that is, the operations s805 and s806 shown in fig. 10 may be replaced by the operations s805 'and s806' shown in fig. 12, so that the SMF523 determines the latest time instant for transmitting each XR frame at the Uu port and notifies the base station 521.

Specifically, referring to fig. 12, after acquiring "display time instant of XR frames in HMD 511" based on operation s804, SMF523 may perform operation s805' to determine the latest time instant at which Uu port transmits each XR frame according to the type of terminal 51 and the processing time of the data. For example, if SMF523 determines that terminal 51 requires 15ms to process XR packets based on the type of terminal 51, then it determines that the first XR frame contains packets that require 14 days 3/5/2021: and (4) dividing into 37 parts: and (3) 23 seconds: terminal 51 is sent 330ms before, and then an XR frame is sent to terminal 51 every 16 ms.

Further, SMF523 executes operation s806' to notify base station 521 of the new QoS parameters of the XR service: the Uu port transmits the latest instant of each XR frame.

In a variation, for a type 3 terminal 51, time is required to transmit data between HMD511 and UE512 since both are split connected. Accordingly, stage 2 may further perform subsequent actions to determine the latest transmission time instant of the data at the Wi-Fi transmission after performing operation s806.

In particular, with continued reference to fig. 10, the ue512 may perform operation s807 to obtain data processing capabilities of the HMD 511. For example, the acquired content may be "XR frames require processing time in HMD511 is xms". The sequence of this operation in the entire data transfer flow is not necessarily the operation s807 described in this embodiment, and this operation may be performed after the HMD511 is powered on, and there is no strict sequence relationship with other steps in this embodiment.

Further, UE512 may perform operation s808 to learn new XR service QoS parameters from base station 521 through signaling: the display time of the XR frame in HMD 511. For example, the first XR frame of the XR service is displayed in HMD511 at 14

days

3, 5 and 3 of 2021: and (4) dividing into 37 parts: and (3) 23 seconds: 345ms.

Correspondingly, in the present variation, the base station 521 acquires the new QoS parameter of the XR service by performing operation s 805: the time instant at which each XR frame is transmitted over Uu port is then signalled to the UE512 by performing operation s 808.

Further, the UE512 may perform operation s809 to determine a latest time instant for transmitting data over the Wi-Fi interface according to the processing capabilities of the HMD 511. For example, assume that the first XR frame of the XR service is displayed in HMD511 at 14

days

3, 5 and 3 of 2021: and (4) dividing into 37 parts: and (3) 23 seconds: 345ms and HMD511 requires 7ms of processing time, UE512 may determine that the latest time of transmission of the XR frame corresponding data over the Wi-Fi interface is 2021 year 3 month 5 day 14: and (4) dividing into 37 parts: and (3) 23 seconds: 338ms. If at this point UE512 has not been able to transmit data for the XR frame over the Wi-Fi interface, no retransmission is necessary.

From the above, for a type 3 terminal, UE512 may determine that XR data is transmitted too late at the latest time of Wi-Fi transmission of the XR data packet.

In a variation, the source of the display time of the XR frame acquired in operation s808 in HMD511 may also be the application layer. The application layer, such as UE512, obtains this information directly from XR application server 53.

In a variation, the above-described act of determining the latest moment in time for the Wi-Fi interface to transmit data for the type 3 terminal 51 may also be performed by the HMD 511. That is, operations s807 to s809 in fig. 10 may be replaced with operations s807 'to s809'.

Specifically, HMD511 may perform operation s807' to obtain this new XR service QoS parameters from XR application server 53: the display instant of the XR frame in HMD 511. For example, the information obtained may be "when the first XR frame of the XR service is displayed in the HMD511 at the time of 2021 year 3 month 5 day 14: and (4) dividing into 37 parts: and (3) 23 seconds: 345ms ".

Further, HMD511 may perform operation s808' to determine the latest time instant at which data is received over the Wi-Fi interface according to its own processing capabilities. For example, assuming that the HMD511 requires 7ms of processing time, the latest time of receiving the first frame of XR data over the Wi-Fi interface is determined to be 3 months, 5 months, and 14 days 2021: and (4) dividing into 37 parts: and (3) 23 seconds: 338ms, followed by an XR frame every 16 ms. That is, the latest time at which HMD511 receives the second frame of XR data over the Wi-Fi interface is 14/3/5/2021: and (4) dividing into 37 parts: and (3) 23 seconds: 354ms.

Further, the HMD511 performs operation s809' to notify the UE512 of the determined latest timing of receiving data through the Wi-Fi interface.

In one variation, the HMD511 may acquire the display time of the XR frame in the HMD511 from the UE when performing operation s 807'.

In a variation, the actions of operation s806 in phase 2 shown in fig. 10 may be performed by the XR application server 53, i.e., operations s804 to s806 shown in fig. 10 may be replaced with operations s1101 to s1102 shown in fig. 13, so that the XR application server 53 determines the latest time instant at which the XR frame is delivered to the UE512.

First, the base station 521 may complete clock synchronization with the UE512, HMD511, and XR application server 53. Then, in phase 1, the UE512 may perform operation s901 to report the terminal capability information of the terminal 51 to the XR application server 53. The terminal capability information includes the processing duration of XR frames in UE512 and HMD 511.

Then, referring to fig. 13, the XR application server 53 may perform operation s1101 to determine the latest time of delivery of the XR frames to the UE512 at the time of XR service initiation, based on the time of issue of the XR frames, the application layer end-to-end transmission delay, and the processing duration of the XR frames in the UE512 and HMD 511.

Further, operation s1102 may continue with the XR application server 53 informing the base station 521 via the core network node (e.g., SMF 523) of the latest XR frame arrival time of the UE512 "based on the session start procedure. For example, assume that the first XR frame of XR traffic is 14 at 3, 5, and 2021: and (4) dividing into 37 parts: and (3) 23 seconds: 305ms is sent from the XR application server 53 with an application layer end-to-end delay of 40ms, after which an XR frame is sent every 16 ms. Based on operation s901, the XR application server 53 determines that 15ms is required for the terminal 51 to process the data packet. The XR application server 53, when performing operation s1101, may determine: the first XR frame contains packets that need to be at 14/3/5/2021: and (4) dividing into 37 parts: and (3) 23 seconds: before 330ms to the terminal 51.

After the base station 521 learns the latest time through operation s1102, even if the data packet received from the gateway jitters, the base station 521 can dynamically determine the "maximum allowable delay" of the data packet transmitted over the air interface.

Thus, in this variation, the XR application server 53 determines the latest time when the base station 521 transmits the XR packet over the air interface and notifies the base station 521 to execute the XR packet. Thereby avoiding too late transmission of XR data on the premise that the base station 521 receives downlink data with jitter.

In a variation, the actions of the operation s806 in phase 2 shown in fig. 10 may be performed by a core network node (e.g., the SMF 523), that is, the operations s805 and s806 shown in fig. 10 may be replaced by the operations s1202 and s1203 shown in fig. 14, so that the SMF523 determines the latest time instant for transmitting each XR frame at Uu port and notifies the base station 521. Moreover, the difference from the above-described variation shown in fig. 12 is that operation s804 in fig. 12 may be further replaced with operation s1201 shown in fig. 14, that is, the SMF523 acquires content from the XR application server 53 differently.

First, the base station 521 may complete clock synchronization with the UE512, HMD511, and XR application server 53. Then, in phase 1, the SMF523 acquires the terminal capability information of the terminal 51 through operations s801 and s802, thereby determining the type of combination of the UE512 and the HMD511 and the length of time required for XR frame processing.

Then, in phase 2, the XR application server 53 performs operation s1201 to notify the SMF523 of "application layer end-to-end transmission delay at issue time of XR frame" when the XR service is started.

Further, SMF523 may perform operation s1202 to determine the latest time instant at which the XR frame is delivered to UE512 based on "the time instant at which the XR frame is emitted, the application layer end-to-end transmission delay" and "the type of UE512 and HMD511 combination and the time length required for XR frame processing".

SMF523 may then perform operation s1203 to notify base station 521 of the determined latest time instant.

For example, assume that the first XR frame of XR traffic is at 14/3/5/2021: and (4) dividing into 37 parts: and (3) 23 seconds: 305ms is sent from the XR application server 53 with an application layer end-to-end delay of 40ms, followed by one XR frame every 16 ms. SMF523 determines that terminal 51 needs 15ms to process the packet by performing operations s801 and s 802. Then SMF523 may determine when performing operation s 1202: the first XR frame contains packets that need to be at 14/3/5/2021: and (4) dividing into 37 parts: and (3) 23 seconds: 330ms ago to the terminal 51.

After the base station 521 knows the latest time, even if the data packet received from the gateway jitters, the base station 521 can dynamically determine the "maximum allowable delay" of the data packet transmitted over the air interface.

Thus, in this variation, SMF523 determines the latest time when the base station 521 transmits the XR data packet over the air interface and notifies the base station 521 to perform the operation. Therefore, under the premise that the base station 521 receives the downlink data and jitters, the XR data can be prevented from being transmitted too late.

In a common variation, the actions performed by SMF523 in phase 2 above may also be performed by AMF522.

In the application scenarios and the variation examples shown in fig. 10 to fig. 14, the peer end of the terminal 51 performing reporting of the terminal capability information in phase 1 may be one or more nodes of the core network, or may be the base station 521, or may be the XR application server 53.

When data of XR service with relaxed delay requirement is transmitted, the terminal 51 may report the terminal capability information to the base station 521. Accordingly, the base station 521 and the node of the core network may perform operations s805 and s806 in fig. 10. By adjusting the delay budget and calculating the latest moment by the base station 521, the XR data processing can be completed in the access layer, and the influence on the upper layer is small.

When data of XR service with strict delay requirement is transmitted, the terminal 51 may report the terminal capability information to a node (e.g., SMF 523) of the core network. Accordingly, the base station 521 and the node of the core network may perform operations s805 'and s806' of fig. 12. Since the core network plays a role in the whole transmission flow, the core network is more suitable for calculating the latest moment.

An embodiment of the present invention further provides a computer-readable storage medium, which is a non-volatile storage medium or a non-transitory storage medium, and a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the data transmission method provided in any of the above embodiments. Preferably, the storage medium may include a computer-readable storage medium such as a non-volatile (non-volatile) memory or a non-transitory (non-transient) memory. The storage medium may include ROM, RAM, magnetic or optical disks, etc.

The embodiment of the present invention further provides another data transmission apparatus, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the data transmission method provided in the embodiment corresponding to fig. 4 when executing the computer program. For example, the data transmission device may be a network device, such as an SMF in a network device. Also for example, the data transmission device may be an XR application server.

The embodiment of the present invention further provides another data transmission apparatus, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the data transmission method provided in the embodiment corresponding to fig. 6 when executing the computer program. For example, the data transmission device may be a network device, such as a base station in a network device.

The embodiment of the present invention further provides another data transmission apparatus, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the steps of the data transmission method provided in the embodiment corresponding to fig. 8 when executing the computer program. For example, the data transmission device may be a user equipment.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by instructing the relevant hardware through a program, which may be stored in a computer-readable storage medium, and the storage medium may include: ROM, RAM, magnetic or optical disks, and the like.

The technical scheme of the invention can be suitable for 5G (5 generation) communication systems, 4G and 3G communication systems, and various communication systems of subsequent evolution, such as 6G, 7G and the like.

The technical solution of the present invention is also applicable to different network architectures, including but not limited to relay network architecture, dual link architecture, and Vehicle-to-event architecture.

The 5G CN in this embodiment may also be referred to as a New Core (New Core), a 5G New Core, a Next Generation Core (NGC), or the like. The 5G-CN is set independently of an existing core network, such as an Evolved Packet Core (EPC).

A Base Station (BS) in the embodiment of the present application, which may also be referred to as a base station device, is a device deployed in a radio access network to provide a wireless communication function. For example, a device providing a base station function in a 2G network includes a Base Transceiver Station (BTS) and a Base Station Controller (BSC), a device providing a base station function in a 3G network includes a node B (NodeB) and a Radio Network Controller (RNC), a device providing a base station function in a 4G network includes an evolved node B (eNB), a device providing a base station function in a Wireless Local Area Network (WLAN) is an Access Point (AP), a device providing a base station function in a 5G New Radio (New Radio, NR) includes a node B (gNB) that continues to evolve, and a device providing a base station function in a future New communication system, and the like.

A terminal in this embodiment may refer to various forms of User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a Mobile Station (MS), a remote station, a remote terminal, a mobile device, a user terminal, a terminal device (terminal equipment), a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like, which are not limited in this embodiment of the present application.

In the embodiment of the application, a unidirectional communication link from an access network to a terminal is defined as a downlink, data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called as a downlink direction; the unidirectional communication link from the terminal to the access network is an uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is referred to as an uplink direction.

It should be understood that the term "and/or" herein is only one kind of association relationship describing the association object, and means that there may be three kinds of relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document indicates that the former and latter related objects are in an "or" relationship.

The "plurality" appearing in the embodiments of the present application means two or more.

The descriptions of the first, second, etc. appearing in the embodiments of the present application are only for the purpose of illustrating and differentiating the description objects, and do not represent any particular limitation to the number of devices in the embodiments of the present application, and cannot constitute any limitation to the embodiments of the present application.

The term "connection" in the embodiment of the present application refers to various connection manners such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in this embodiment of the present application. In the embodiments of the present application, the expression "network" and "system" refers to the same concept, and a communication system is a communication network.

It should be understood that, in the embodiment of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other general-purpose processors, digital Signal Processors (DSP), application Specific Integrated Circuits (ASIC), field Programmable Gate Arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).

The above-described embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. The procedures or functions described in accordance with the embodiments of the present application are produced in whole or in part when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus, and system may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately and physically included, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected by one skilled in the art without departing from the spirit and scope of the invention, as defined in the appended claims.

Claims

1. A method of data transmission, comprising:

acquiring terminal capability information, wherein the terminal capability information is used for indicating XR (X-ray diffraction) capabilities supported by the UE and/or the HMD;

determining a transmission delay according to the terminal capability information, wherein the transmission delay is used for indicating the maximum time length from the time when the network equipment receives the data to the time when the network equipment sends the data;

and sending the transmission delay.

2. The data transmission method of claim 1, wherein the terminal capability information comprises UE capability information and HMD capability information, wherein the UE capability information is indicative of XR capabilities supported by the UE and the HMD capability information is indicative of XR capabilities supported by the HMD.

3. The data transmission method according to claim 2, wherein the obtaining the terminal capability information includes:

and receiving the UE capability information reported by the UE and receiving the HMD capability information reported by the HMD.

4. The data transmission method according to claim 1, wherein the obtaining the terminal capability information includes:

acquiring the terminal capability information from a base station; or

And acquiring the terminal capability information from the XR application server.

5. The data transmission method according to claim 1, wherein the obtaining the terminal capability information includes:

and acquiring the terminal capability information from the SMF.

6. The data transmission method according to claim 1, further comprising:

reporting the terminal capability information to an XR application server; and/or the presence of a gas in the atmosphere,

and reporting the data transmission advance to an XR application server, wherein the data transmission advance is determined based on the terminal capability information.

7. The data transmission method according to claim 1, wherein the terminal capability information includes at least one of:

the type of UE combined with HMD;

the UE is combined with the HMD, and the needed XR service processing time is shortened;

the UE is combined with the HMD, and needed XR service processing capacity is achieved;

the UE, in combination with the HMD, requires XR traffic processing time after Uu port transmission.

8. The data transmission method according to claim 1, wherein the determining a transmission delay according to the terminal capability information includes:

acquiring the display time of the XR frame corresponding to the data in the HMD;

determining the latest time or the transmission delay of the XR frame to reach the UE according to the terminal capability information and the display time of the XR frame in the HMD.

9. The method of claim 8, wherein the obtaining of the display time of the XR frame corresponding to the data in the HMD comprises:

receiving a total transmission delay and a sending time of an Nth XR frame before the XR frame from an XR application server, wherein the total transmission delay is the maximum allowable delay from the time when the XR application server sends the data to the time when the data reaches an application layer of the UE, and N is a natural number;

and determining the display time of the XR frame corresponding to the data in the HMD according to the total transmission time delay and the sending time of the Nth XR frame before the XR frame.

10. The data transmission method according to claim 1, wherein the determining a transmission delay according to the terminal capability information includes:

receiving, from an XR application server, a latest time when an XR frame corresponding to the data arrives at the UE or the transmission delay, where the latest time when the XR frame arrives at the UE is determined according to the terminal capability information and a display time of the XR frame in the HMD.

11. The data transmission method according to claim 8, 9 or 10, further comprising:

and when the XR service is started, performing clock synchronization with the UE, the HMD, the base station and the XR application server.

12. A data transmission apparatus, comprising:

an obtaining module, configured to obtain terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD;

a determining module, configured to determine a transmission delay according to the terminal capability information, where the transmission delay is used to indicate a maximum duration between when a network device receives the data and when the network device sends the data;

and the sending module is used for sending the transmission delay.

13. A method of data transmission, comprising:

acquiring transmission delay, wherein the transmission delay is used for indicating the maximum time length from the time when network equipment receives the data to the time when the network equipment sends the data, the transmission delay is determined according to terminal capability information, and the terminal capability information is used for indicating XR (X-ray diffraction) capability supported by UE (user equipment) and/or HMD (HMD);

and transmitting the data according to the transmission delay.

14. The data transmission method according to claim 13, wherein the obtaining the transmission delay comprises:

and receiving the transmission delay from the SMF.

15. The data transmission method according to claim 13, wherein the obtaining the transmission delay comprises:

acquiring the terminal capability information and the display time of an XR frame corresponding to the data in the HMD;

determining a latest time instant when the XR frame arrives at the UE or the transmission delay according to the terminal capability information and the display time instant of the XR frame in the HMD.

16. The method of claim 15, wherein obtaining the display time of the XR frame corresponding to the data in the HMD comprises:

receiving a total transmission delay and a sending time of an Nth XR frame before the XR frame from an XR application server, wherein the total transmission delay is the transmission delay from the XR application server to UE, and N is a natural number;

17. The data transmission method according to claim 13, wherein the transmitting the data according to the transmission delay includes:

and after receiving the data, transmitting the data by taking the latest moment when the XR frame reaches the UE as a constraint.

18. The data transmission method according to claim 13, further comprising:

and when the XR service is started, performing clock synchronization with the UE, the HMD, the SMF and the XR application server.

19. The data transmission method of claim 13, wherein the terminal capability information comprises UE capability information and HMD capability information, wherein the UE capability information is indicative of XR capabilities supported by the UE and the HMD capability information is indicative of XR capabilities supported by the HMD.

20. The data transmission method according to claim 13, wherein the terminal capability information includes at least one of:

type of UE combined with HMD;

combining the UE with the HMD, and processing time of the needed XR service;

UE combined with HMD, required XR service handling capability;

the UE, in conjunction with the HMD, requires XR traffic processing time after Uu port transmission.

21. A data transmission apparatus, comprising:

an obtaining module, configured to obtain a transmission delay, where the transmission delay is used to indicate a maximum duration between when a network device receives the data and when the network device sends the data, and the transmission delay is determined according to terminal capability information, where the terminal capability information is used to indicate XR capabilities supported by the UE and/or the HMD; and the transmission module is used for transmitting the data according to the transmission delay.

22. A method of data transmission, comprising:

and reporting the terminal capability information.

23. The data transmission method of claim 22, further comprising:

receiving data, wherein the data is transmitted according to a transmission delay, the transmission delay is used for indicating the maximum time length from the time when network equipment receives the data to the time when the network equipment sends the data, and the transmission delay is determined according to terminal capability information.

24. The data transmission method according to claim 22, wherein the obtaining the terminal capability information includes:

acquiring capability information of the HMD;

and generating the terminal capability information according to the capability information of the HMD and the capability information of the UE.

25. The data transmission method of claim 22, further comprising:

receiving data;

determining a latest time or transmission delay for transmitting the XR frame to the HMD according to the HMD capability information and the display time of the XR frame in the HMD;

transmitting the data with the latest time or transmission delay of the XR frame to the HMD as a constraint.

26. The data transmission method of claim 22, further comprising:

receiving data;

receiving a latest moment or transmission delay reported by the HMD for transmitting the XR frame to the HMD, wherein the latest moment or transmission delay for transmitting the XR frame to the HMD is determined according to the capability information of the HMD and the display moment of the XR frame corresponding to the data in the HMD;

27. The data transmission method according to claim 22, wherein the reporting the terminal capability information comprises:

and reporting the terminal capability information to a base station, an XR application server or an SMF.

28. The data transmission method of claim 22, wherein the terminal capability information comprises UE capability information and HMD capability information, wherein the UE capability information is indicative of XR capabilities supported by the UE and the HMD capability information is indicative of XR capabilities supported by the HMD.

29. The data transmission method according to claim 22, wherein the terminal capability information comprises at least one of:

type of UE combined with HMD;

combining the UE with the HMD, and processing time of the needed XR service;

UE combined with HMD, required XR service handling capability;

30. The data transmission method of claim 22, further comprising:

XR service is started, clock synchronized with the base station, HMD, SMF, and XR application server.

31. A data transmission apparatus, comprising:

and the reporting module is used for reporting the terminal capability information.

32. A computer-readable storage medium, being a non-volatile storage medium or a non-transitory storage medium, having a computer program stored thereon, wherein the computer program, when executed by a processor, performs the steps of the method according to any one of claims 1 to 11 or 13 to 20 or 22 to 30.

33. A data transmission apparatus comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, wherein the processor, when executing the computer program, performs the steps of the method of any of claims 1 to 11 or any of claims 13 to 20 or any of claims 22 to 30.