Data transmission method and apparatus, computer-readable storage medium

Abstract

A data transmission method and apparatus, and a computer-readable storage medium, are disclosed. The method includes: acquiring terminal capability information, wherein the terminal capability information is used to indicate XR capabilities supported by the UE and / or HMD; determining a transmission delay based on the terminal capability information, wherein the transmission delay is used to indicate the maximum duration between when a network device receives the data and when it sends the data; and transmitting the transmission delay. This invention enables accurate determination of the QoS of XR services based on the terminal's XR service processing capabilities, and particularly, rationally determines the allocation of transmission delay across transmission nodes, thereby enhancing the transmission of XR service data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a data transmission method and device, and a computer readable storage medium. BACKGROUND

[0002] Extended Reality (XR) technology, which is a combination of Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR) technologies, can fuse physical and virtual environments together or provide a completely immersive virtual experience environment, and has broad application prospects in the era of the Fifth-Generation mobile communications (5G).

[0003] The service based on XR technology transmission can be referred to as XR service. When the existing network configures Quality of Service (QoS) for the XR service, only the access layer capability of User Equipment (UE) is considered, so that the QoS configured for the XR service is inaccurate. The inaccurate QoS increases the transmission delay of data, affects the timeliness of data transmission, and further affects the user experience. SUMMARY

[0004] The technical problem solved by the present application is how to accurately determine the QoS of the XR service to enhance the transmission of the XR service.

[0005] To solve the above technical problem, the present application provides a data transmission method, comprising: acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and / or HMD; determining a transmission delay according to the terminal capability information, wherein the transmission delay is used to indicate the maximum time length between the reception of the data by the network device and the sending of the data; and sending the transmission delay.

[0006] Optionally, the terminal capability information comprises UE capability information and HMD capability information, wherein the UE capability information is used to indicate the XR capability supported by the UE, and the HMD capability information is used to indicate the XR capability supported by the HMD.

[0007] Optionally, the acquiring of the terminal capability information comprises: receiving the UE capability information reported by the UE, and receiving the HMD capability information reported by the HMD.

[0008] Optionally, the terminal capability information is acquired from a base station or an XR application server.

[0009] Optionally, the terminal capability information is acquired from an SMF.

[0010] Optionally, the data transmission method further comprises: reporting the terminal capability information to an XR application server; and / or reporting a data sending advance to the XR application server, the data sending advance being determined based on the terminal capability information.

[0011] Optionally, the terminal capability information comprises at least one of the following: a type of a UE combined with a HMD; an XR service processing time required by the UE combined with the HMD; an XR service processing capability required by the UE combined with the HMD; an XR service processing time required by the UE combined with the HMD after Uu port transmission.

[0012] Optionally, the transmission delay is determined based on the terminal capability information, comprising: acquiring a display time of an XR frame corresponding to the data in the HMD; and determining a latest time of the XR frame reaching the UE or the transmission delay based on the terminal capability information and the display time of the XR frame in the HMD.

[0013] Optionally, the display time of the XR frame corresponding to the data in the HMD is acquired, comprising: 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 a maximum allowable delay from the XR application server sending the data to the data reaching 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 based on the total transmission delay and the sending time of the Nth XR frame before the XR frame.

[0014] Optionally, the transmission delay is determined based on the terminal capability information, comprising: receiving the latest time of the XR frame reaching the UE or the transmission delay from an XR application server, wherein the latest time of the XR frame reaching the UE is determined based on the terminal capability information and the display time of the XR frame in the HMD.

[0015] Optionally, the data transmission method further comprises: performing clock synchronization with the UE, the HMD, a base station and the XR application server when an XR service is started.

[0016] To solve the above technical problems, the embodiment of the present application further provides a data transmission device, comprising: an acquisition module, configured to acquire terminal capability information, wherein the terminal capability information is used to indicate XR capability supported by a UE and / or a HMD; a determination module, configured to determine a transmission delay according to the terminal capability information, wherein the transmission delay is used to indicate a maximum time length between receiving the data by a network device and sending the data; and a sending module, configured to send the transmission delay.

[0017] To solve the above technical problems, the embodiment of the present application further provides a data transmission method, comprising: acquiring a transmission delay, wherein the transmission delay is used to indicate a maximum time length between receiving the data by a network device and sending the data, and the transmission delay is determined according to terminal capability information, and the terminal capability information is used to indicate XR capability supported by a UE and / or a HMD; and transmitting the data according to the transmission delay.

[0018] Optionally, the acquiring the transmission delay comprises receiving the transmission delay from an SMF.

[0019] Optionally, the acquiring the transmission delay comprises: acquiring the terminal capability information and a display time of an XR frame corresponding to the data in the HMD; and determining a latest time when the XR frame reaches the UE or the transmission delay according to the terminal capability information and the display time of the XR frame in the HMD.

[0020] Optionally, the acquiring 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 a transmission delay between the XR application server and 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 delay and the sending time of the Nth XR frame before the XR frame.

[0021] Optionally, the transmitting the data according to the transmission delay comprises: after receiving the data, transmitting the data with the latest time when the XR frame reaches the UE as a constraint.

[0022] Optionally, the data transmission method further comprises: when XR service starts, performing clock synchronization with the UE, the HMD, the SMF and the XR application server.

[0023] Optionally, the terminal capability information comprises UE capability information and HMD capability information, wherein the UE capability information is used to indicate XR capability supported by the UE, and the HMD capability information is used to indicate XR capability supported by the HMD.

[0024] Optionally, the terminal capability information comprises at least one of the following: a type of the UE combined with the HMD; an XR service processing time required by the UE combined with the HMD; an XR service processing capability required by the UE combined with the HMD; an XR service processing time required by the UE combined with the HMD after Uu port transmission.

[0025] To solve the above technical problems, the embodiment of the present application further provides a data transmission device, comprising: an acquisition module, configured to acquire a transmission time delay, wherein the transmission time delay is used to indicate a maximum time length between receiving the data by a network device and sending the data, and the transmission time delay is determined according to terminal capability information, and the terminal capability information is used to indicate an XR capability supported by a UE and / or an HMD; and a transmission module, configured to transmit the data according to the transmission time delay.

[0026] To solve the above technical problems, the embodiment of the present application further provides a data transmission method, comprising: acquiring terminal capability information, wherein the terminal capability information is used to indicate an XR capability supported by a UE and / or an HMD; and reporting the terminal capability information.

[0027] Optionally, the data transmission method further comprises: receiving data, wherein the data is transmitted according to a transmission time delay, the transmission time delay is used to indicate a maximum time length between receiving the data by a network device and sending the data, and the transmission time delay is determined according to terminal capability information.

[0028] Optionally, the acquiring terminal capability information comprises: acquiring capability information of the HMD; and generating the terminal capability information according to the capability information of the HMD and capability information of the UE.

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

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

[0031] Optionally, the reporting the terminal capability information comprises: reporting the terminal capability information to a base station, an XR application server, or an SMF.

[0032] Optionally, the terminal capability information comprises UE capability information and HMD capability information, wherein the UE capability information is used to indicate XR capability supported by the UE, and the HMD capability information is used to indicate XR capability supported by the HMD.

[0033] Optionally, the terminal capability information comprises at least one of the following: a type of combination of the UE and the HMD; an XR service processing time required by the combination of the UE and the HMD; an XR service processing capability required by the combination of the UE and the HMD; an XR service processing time required by the combination of the UE and the HMD after Uu port transmission.

[0034] Optionally, the data transmission method further comprises: performing clock synchronization with a base station, an HMD, an SMF, and an XR application server when an XR service is started.

[0035] To solve the above technical problems, an embodiment of the present application further provides a data transmission device, comprising: an acquisition module, configured to acquire terminal capability information, wherein the terminal capability information is used to indicate XR capability supported by a UE and / or an HMD; and a reporting module, configured to report the terminal capability information.

[0036] To solve the above technical problems, an embodiment of the present application 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, wherein the computer program is run on a processor to execute the steps of the above method.

[0037] To solve the above technical problems, an embodiment of the present application further provides a data transmission device, comprising a memory and a processor, wherein the memory has a computer program stored thereon, the computer program is run on the processor, and the processor executes the steps of the above method when running the computer program.

[0038] Compared with the prior art, the technical scheme of the embodiment of the present application has the following beneficial effects:

[0039] On the network side, such as the SMF side in the network, an embodiment of the present application provides a data transmission method, comprising: acquiring terminal capability information, wherein the terminal capability information is used to indicate XR capability supported by a UE and / or an HMD; determining a transmission delay according to the terminal capability information, wherein the transmission delay is used to indicate a maximum time length between receiving the data by a network device and sending the data; and sending the transmission delay.

[0040] With the embodiment, the QoS of the XR service can be accurately determined according to the XR service processing capability of the terminal, and in particular, the allocation of the transmission delay at each transmission node can be reasonably determined, thereby enhancing the transmission of the XR service data. Specifically, the QoS of the XR service is determined according to the acquired terminal capability information. Further, the accurate QoS can facilitate the reasonable allocation of the delay budget, thereby reasonably determining the allocation of the total transmission delay at each transmission node.

[0041] At the network side, such as the base station side in the network, the embodiment of the application further provides a data transmission method, comprising: acquiring a transmission delay, wherein the transmission delay is used to indicate the maximum time length between the reception of the data by the network device and the sending of the data, and the transmission delay is determined according to terminal capability information, the terminal capability information being used to indicate the XR capability supported by the UE and / or the HMD; and transmitting the data according to the transmission delay. Thus, for the transmission node, no matter whether the time when the transmission node receives the data occurs jitter, the latest time of the air interface transmission of the data can be determined based on the received transmission delay, thereby avoiding the transmission of the data too late.

[0042] At the UE side, the embodiment of the application further provides a data transmission method, comprising: acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and / or the HMD; and reporting the terminal capability information. With the embodiment, the UE actively reports the terminal capability information to the network, so that the network side determines the transmission delay budget. BRIEF DESCRIPTION OF DRAWINGS

[0043] Figure 1 is a first data transmission principle diagram in the prior art;

[0044] Figure 2 is a second data transmission principle diagram in the prior art;

[0045] Figure 3 is three combination types of the UE and the HMD involved in the XR service in the prior art;

[0046] Figure 4 is a flow chart of a data transmission method according to the first embodiment of the application;

[0047] Figure 5 is a structural schematic diagram of a data transmission device according to the second embodiment of the application;

[0048] Figure 6 is a flow chart of a data transmission method according to the third embodiment of the application;

[0049] Figure 7 is a structural schematic diagram of a data transmission device according to the fourth embodiment of the application;

[0050] Figure 8is a flow chart of a data transmission method of a fifth embodiment of the present application;

[0051] Figure 9 is a structural schematic diagram of a data transmission device of a sixth embodiment of the present application;

[0052] Figure 10 is a signaling interaction schematic diagram of a typical application scenario of an embodiment of the present application;

[0053] Figure 11 is Figure 10 is a signaling interaction schematic diagram of a variation of stage 1 in the application scenario shown;

[0054] Figure 12 is Figure 10 is a signaling interaction schematic diagram of a first variation of stage 2 in the application scenario shown;

[0055] Figure 13 is Figure 10 is a signaling interaction schematic diagram of a second variation of stage 2 in the application scenario shown;

[0056] Figure 14 is Figure 10 is a signaling interaction schematic diagram of a third variation of stage 2 in the application scenario shown. DETAILED DESCRIPTION

[0057] As described in the background, the existing network does not know the terminal's ability to process XR service data in advance, so it cannot determine the allocation of the XR service transmission delay budget at each transmission node, and cannot accurately determine the QoS.

[0058] Specifically, after the video data (also referred to as XR service data) transmitted by the XR service is generated from the XR application server (XR APP Server for short), it enters the 3rd Generation Partnership Project (3GPP for short) network through the Internet Protocol (IP for short) network, passes through the core network router and the base station, and finally reaches the terminal, and is displayed to the user by the terminal. In the entire transmission process, the XR service data passes through network elements such as Figure 1 or Figure 2 as shown. Figure 1 What is shown is the transmission process of XR service data when the network does not use edge cloud. Specifically, after the IP network receives the XR service data sent by the XR application server, it is directly transmitted to the UE through the User Plane Function (UPF for short) and the base station (such as gNB). Figure 2The transmission process of XR service data when the network adopts edge cloud is shown. Specifically, the IP network receives the XR service data sent by the XR application server and sends it to the UPF. The XR service data is processed by the edge cloud at the application layer (such as rendering, synthesis, etc.) after passing through the UPF. The XR service data processed by the edge cloud is transmitted to the UE through the base station.

[0059] On the other hand, in the existing network transmission service data process, because the functional parameters of UEs are different, the 3GPP protocol defines many optional functions, such as whether to support 1024 quadrature amplitude modulation (QAM) and whether to support multi-connection. Correspondingly, after the UE accesses the network, the base station can configure appropriate wireless parameters for the UE according to the UE capability.

[0060] Currently, 3GPP determines that there are three types of terminals involved in XR, and the functions involved are distributed as shown in Figure 3 In the present embodiment, the "terminal" refers to the combination of a UE and a head-mounted display (HMD), wherein the UE is the receiving end of the XR service data, and is usually a 5G terminal such as a 5G phone, and the HMD is the presentation end of the XR service data, such as an AR glass.

[0061] Referring to Figure 3 For a type 1 terminal, the terminal is a HMD, that is, the UE and the HMD are integrated. The type 1 terminal integrally completes all functions on the terminal side, including rendering, synthesis, decoding, etc., and finally presents video and audio to the user. That is, after the type 1 terminal receives the XR service data transmitted by the network via the user network interface universal (Uu) interface (Uu port), it locally completes all function processing on the terminal side and presents the XR frame (i.e., the video frame of the XR service) locally. Since all functions are completed on the terminal, the type 1 terminal is relatively bulky and uncomfortable to wear.

[0062] Referring to Figure 3For type 2 terminals, the UE is also combined with the HMD. However, unlike type 1 terminals, type 2 terminals have relatively simple functions, that is, only decoding. Other XR service data processing, such as rendering and synthesis, is completed by the edge cloud. That is, the XR service data transmitted by the network is processed by the edge cloud, and then transmitted to the type 2 terminal via the Uu interface. The type 2 terminal completes the remaining function processing locally and presents the video frame locally. Compared with type 1 terminals, type 2 terminals carry fewer functions, so they are thinner and more comfortable to use.

[0063] With continued reference to Figure 3 For type 3 terminals, the UE and the HMD are physically separated, and data is transmitted between them via Wi-Fi. In this way, most of the data processing functions can be placed on the UE side, such as rendering and synthesis, and the HMD is only responsible for decoding. That is, after the 5G mobile phone receives the XR service data transmitted by the network via the Uu interface, it completes part of the function processing locally, and then transmits it to the HMD via Wi-Fi. The HMD completes the remaining function processing locally and presents the video frame to the user. In this way, the HMD in the type 3 terminal is also thin and comfortable to use, like the type 2 terminal.

[0064] By Figure 3 As can be seen, when the network transmits XR service data to the terminal, the position of the time window left for the Uu interface to transmit data may differ depending on the type of terminal. Assuming that the total downlink delay budget (i.e., the application layer end-to-end transmission delay) of a video frame is 30 milliseconds (ms), the network allocates different delays for different types of terminals.

[0065] For type 1 terminals, the HMD takes 10 ms to complete rendering, synthesis, decoding, and other processing, and the Uu interface takes 10 ms to transmit. Therefore, the UPF must transmit the data of the video frame to the base station 10 ms in advance.

[0066] For type 2 terminals, the HMD takes 5 ms to complete decoding, and the Uu interface takes 10 ms to transmit. Therefore, the UPF must transmit the data of the video frame to the base station 15 ms in advance.

[0067] For type 3 terminals, the HMD takes 5 ms to complete decoding, Wi-Fi transmission takes 1 ms, and the UE takes 3 ms to complete rendering and synthesis. Therefore, the UPF must transmit the data of the video frame to the base station 16 ms in advance.

[0068] If the network does not know in advance the type of combination of the UE and the HMD, it cannot determine the allocation of service delays at each transmission node, and cannot accurately determine the QoS.

[0069] According to existing protocols, after a UE establishes a connection with a base station, the base station requests UE capability information from the Access and Mobility Management Function (AMF) in the core network. If the UE is establishing a connection with the network for the first time and the AMF does not store UE capability information, the base station will request this information from the UE. After the UE reports its own capability information, the base station configures radio parameters matching its capabilities accordingly. Subsequently, the base station uploads the UE's capability information to the AMF for storage. Even if the UE disconnects from the base station thereafter, its capability information remains in the AMF. The next time the UE establishes a connection with the base station, the base station only needs to obtain the UE's capability information from the AMF, without requiring the UE to report it again.

[0070] In existing technologies, when a service is established, the base station obtains the service's QoS information, which includes a latency budget parameter, meaning "the maximum permissible latency for each data packet to be transmitted over the air interface." During service transmission, the base station starts timing from the moment it receives the data packet from the UPF. If the data packet has not been transmitted after the "maximum permissible latency," transmission is abandoned. In other words, the base station uses the moment the data packet arrives at it as the starting moment of the "maximum permissible latency."

[0071] However, existing protocols stipulate that the capability information reported by the UE only involves the UE's access layer capabilities and does not involve the UE's XR processing capabilities, so it cannot solve the problem of latency budget allocation for XR services.

[0072] XR services involve large amounts of data with dense packet density. Therefore, before reaching the base station, packets may experience queuing congestion within the IP network or the UPF, causing jitter in the arrival time of the packets.

[0073] To achieve deterministic latency from the XR application server to the HMD, i.e., a fixed end-to-end transmission latency at the application layer, the "maximum permissible latency" at the air interface differs for each data packet received by the base station when its arrival time varies. For example, a data packet arriving late at the base station has a smaller "maximum permissible latency" at the air interface, while a data packet arriving early has a larger "maximum permissible latency" at the air interface.

[0074] However, under the existing QoS architecture, base stations cannot detect data packets that jitter when they arrive at them, and therefore cannot achieve a flexible "maximum allowable latency".

[0075] Furthermore, for different types of terminals, the processing time required after receiving a data packet and before it is displayed on the HMD varies due to the different processing performed on the data packet. If the processing time 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 either.

[0076] To address the aforementioned technical problems, embodiments of the present invention provide a data transmission method, comprising: acquiring terminal capability information, wherein the terminal capability information is used to indicate XR capabilities supported by the UE and / or HMD; determining a transmission delay based on the terminal capability information, wherein the transmission delay is used to indicate the maximum duration between when a network device receives the data and when it sends the data; and sending the transmission delay.

[0077] This implementation scheme enables precise determination of the QoS of XR services based on the terminal's XR service processing capabilities, particularly in the rational allocation of transmission latency across transmission nodes, thereby enhancing XR service data transmission. Specifically, the QoS of XR services is determined based on the acquired terminal capability information. Furthermore, accurate QoS facilitates the rational allocation of latency budget, thus enabling a reasonable determination of the total transmission latency distribution across transmission nodes.

[0078] To make the above-mentioned objectives, features and beneficial effects of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0079] Figure 4 This is a flowchart of a data transmission method according to the first embodiment of the present invention.

[0080] This implementation scheme can be applied to XR scenarios, and the data transmitted using this implementation scheme is XR service data. In an XR scenario, the XR video generated by the XR application server is transmitted to the terminal via the network and displayed, and the data corresponds to one or more XR frames in the XR video.

[0081] This implementation scheme can be applied to the network side, such as by network devices on the network side. The network devices may include nodes in the core network, such as the AMF or Session Management Function (SMF) in the core network.

[0082] One or more nodes in the core network can be understood as transmission nodes that data needs to pass through during the process of transmitting data from the XR application server to the terminal.

[0083] This implementation scheme, while meeting the total transmission delay requirement, rationally allocates the delay budget of these transmission nodes based on the terminal's XR data processing capabilities, thus preventing data from being transmitted to the terminal too late. The total transmission delay is the maximum permissible delay at the application layer from when the XR application server sends the XR service data to when the XR service data arrives at the UE, where N is a natural number. This total transmission delay, also known as the application layer end-to-end transmission delay, is related to service characteristics and can be determined when the XR service is initiated and notified to the core network by the XR application server. The core network rationally allocates the delay budget of each transmission node based on this total transmission delay to ensure that data arrives at the UE within the application layer end-to-end transmission delay.

[0084] In specific implementation, the transmission method provided in steps S101 to S103 below can be executed by a chip with data transmission function in the network device, or by a baseband chip in the network device.

[0085] Specifically, refer to Figure 4 The data transmission method described in this embodiment may include the following steps:

[0086] Step S101: Obtain terminal capability information, wherein the terminal capability information is used to indicate the XR capabilities supported by the UE and / or HMD;

[0087] Step S102: Determine the transmission delay based on the terminal capability information, wherein the transmission delay is used to indicate the maximum duration between when the network device receives the data and when it sends the data;

[0088] Step S103: Send the transmission delay.

[0089] In one specific implementation, the terminal capability information includes UE capability information and HMD capability information, wherein the UE capability information is used to indicate the XR capabilities supported by the UE, and the HMD capability information is used to indicate the XR capabilities supported by the HMD.

[0090] Specifically, terminal capability information may include the type of UE-HMD combination, as described above. Figure 3 The three types shown are for reference only, and other extended types may be defined in the future. For example, replacing Wi-Fi connections in Type 3 terminals with wired connections. Accordingly, the network side can determine the XR service processing time required for the combination of the UE and HMD based on the type reported by the UE.

[0091] Furthermore, the terminal capability information can include the XR service processing time required for the UE to combine with the HMD. That is, the UE can directly report the XR service processing time required for its combination with the HMD. For example, the XR service processing time required for the UE to combine with the HMD can be the sum of the time required for the UE to complete part of the function processing and the time required for the HMD to complete the remaining function processing, and can also include the time required for data transmission between the UE and the HMD. The functions that the UE and HMD need to perform can be referred to the above. Figure 3 The relevant descriptions in the text will not be repeated here.

[0092] The required XR service processing time when the UE is combined with the HMD can be the average time, the maximum time, or the variance.

[0093] Furthermore, terminal capability information can include the XR service processing capabilities required when the UE is combined with the HMD. For example, it can process up to X bytes of data per second, or up to Y video frames (i.e., XR frames) per second.

[0094] Furthermore, the terminal capability information can include the XR service processing time required after the UE and HMD are combined and transmitted via the Uu interface. For Type 1 terminals, the processing time after Uu interface transmission is the time required for rendering, compositing, and decoding. For Type 2 terminals, the processing time after Uu interface transmission is the time required for decoding. For Type 3 terminals, the processing time after Uu interface transmission is the sum of the time required for rendering, compositing, Wi-Fi transmission, and decoding.

[0095] In one specific implementation, the network side may pre-store terminal capability information reported by UEs that have connected in the past. Accordingly, step S101 may include the step of: 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.

[0096] Specifically, the preset database can be stored in the AMF. For example, when a UE initially accesses the network, it reports terminal capability information, and the network stores this terminal capability information in the preset database of the AMF. When the UE accesses the network again, it does not need to report its terminal capability information again; the network side directly obtains the terminal capability information reported by the UE from the AMF.

[0097] Furthermore, the preset database may store the association between the UE's unique identifier and terminal capability information. When executing step S101, the preset database is searched based on the unique identifier of the UE currently accessing the network and requiring XR services to obtain the associated terminal capability information.

[0098] In one variation, taking a split-connection UE and HMD such as a type 3 terminal as an example, different terminal capability information may be generated if the same UE is connected to different HMDs, or if different transmission methods (such as Wi-Fi transmission or wired connection) are used between the UE and HMD.

[0099] Correspondingly, the same UE can be associated with multiple terminal capability information in the preset database, corresponding to scenarios of connecting to different HMDs or using different methods to connect to HMDs.

[0100] When performing step S101, the corresponding terminal capability information is searched in the preset database based on the unique identifier of the UE that is currently accessing the network and needs to perform XR services, and the unique identifier of the HMD that the UE is currently connected to.

[0101] Alternatively, when performing step S101, the corresponding terminal capability information can be searched in a preset database based on the unique identifier of the UE currently accessing the network and requiring XR services, as well as the specific connection method between the UE and the HMD.

[0102] In one variation, step S101 may include the step of receiving the terminal capability information reported by the UE.

[0103] For example, for a UE that is initially accessing the network, since the AMF has not yet stored the UE's terminal capability information, the UE needs to report the terminal capability information to the network.

[0104] For example, terminal capability information may not be stored in the AMF; the UE will actively report the terminal capability information each time it accesses the network.

[0105] Furthermore, the HMD can independently report its own capability information to the network side. Accordingly, in step S101, the SMF can receive the UE capability information reported by the UE, and also receive the HMD capability information reported by the HMD.

[0106] Furthermore, the specific process for the network side to receive the terminal capability information reported by the UE may include: receiving the terminal capability information reported by the UE from the base station. That is, the UE reports the terminal capability information to the base station, which then reports it level by level to one or more nodes in the core network, and finally to the XR application server. This example illustrates a bottom-up reporting process.

[0107] For example, the base station can report the terminal capability information reported by the UE to the AMF, SMF, and Policy and Charging Rules Function (PCRF) respectively.

[0108] Alternatively, the network side can receive the terminal capability information reported by the UE from the XR application server. In other words, the UE reports the terminal capability information to the XR application server, which then relays it level by level to the core network and base stations. This example illustrates a top-down reporting process.

[0109] For example, 5G core network nodes such as PCRF, SMF, and AMF can obtain terminal capability information from the XR application server and then notify the base station. Alternatively, the base station may not need to know the terminal's capability information. Accordingly, when establishing an XR service, the core network nodes determine the QoS of the XR service, and the base station only needs to execute according to the QoS.

[0110] In one specific implementation, after step S101, the SMF may further perform the step of reporting the terminal capability information to the XR application server. This allows the XR application server to consider the terminal's actual processing capabilities when determining the QoS of the terminal's XR services.

[0111] For example, based on terminal capability information, the XR application server can determine the time required for the terminal to process video frames, thereby determining an appropriate data transmission lead time. Here, the data transmission lead time refers to the amount of time (x milliseconds) the XR application server needs to send the data packet for the XR frame before its display time in the HMD.

[0112] Furthermore, the data transmission lead time can be the time required for the terminal to process the XR frame. Alternatively, the data transmission lead time can be xms before the XR application server sends the frame data when the HMD displays the XR frame.

[0113] Alternatively, the XR application server may not be aware of the terminal's capabilities. This is because, regardless of the terminal type, the functions performed by the UE and HMD are the same. For a specific function, whether it is processed on the UE side or the HMD side, it can be invisible to the XR application server.

[0114] In one variation, in response to obtaining terminal capability information in step S101, the SMF can calculate the data transmission lead and report it to the XR application server.

[0115] For example, based on the combination of UE and HMD in the terminal capability information, the required XR service processing time can be calculated by the AMF or SMF, and the data transmission advance can be notified to the XR application server.

[0116] For Type 1 terminals, the core network node (such as AMF) can determine the time margin allocated to the XR application server based on the XR service processing capabilities reported by the terminal. Specifically, the time length in the terminal capability information obtained in step S101 can be the time required for rendering, compositing, and decoding.

[0117] For Type 2 terminals, the core network node can determine the time margin allocated to the XR application server by combining the processing capabilities of the edge cloud and the XR service processing capabilities reported by the terminal. Specifically, the time length in the terminal capability information obtained in step S101 can be the time required for decoding.

[0118] For type 3 terminals, the core network node can determine the time margin allocated to the XR application server based on the XR service processing capabilities reported by the terminal. Specifically, the time length in the terminal capability information obtained in step S101 can be the time required for decoding.

[0119] In one specific implementation, step S102 may include the steps of: obtaining the display time of the XR frame corresponding to the data in the HMD; and determining the latest time when the XR frame arrives at the UE or the transmission delay based on the terminal capability information and the display time of the XR frame in the HMD.

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

[0121] Furthermore, the SMF determines the time required for the terminal to process data packets based on the acquired terminal capability information. Combined with the display time of the XR frame in the HMD, it can calculate the latest time the XR frame needs to arrive at the terminal, i.e., the latest time the XR frame arrives at the UE. This latest time can be understood as the latest time for Uu interface transmission.

[0122] Furthermore, based on the transmission delay and the time when the XR frame is received, the latest time when the XR frame arrives at the UE can be calculated.

[0123] In one specific implementation, the display time of the XR frame in the HMD can be calculated by the network side itself.

[0124] Specifically, the network side can receive the total transmission delay and the transmission time of the Nth XR frame preceding the XR frame from the XR application server. Then, based on the total transmission delay and the transmission time of the Nth XR frame preceding the XR frame, the display time of the XR frame corresponding to the data in the HMD is determined.

[0125] The data may correspond to one or more XR frames, and the display time of each XR frame in the HMD is determined based on the total transmission delay and the transmission time of the Nth XR frame preceding the XR frame.

[0126] Furthermore, the information obtained from the XR application server may also include the XR frame interval, in order to calculate the transmission and display time of each frame.

[0127] Therefore, on the network side, such as the SMF side within the network, this implementation scheme can accurately determine the QoS of XR services based on the terminal's XR service processing capabilities, especially by rationally determining the distribution of transmission latency across transmission nodes, thereby enhancing the transmission of XR service data. Specifically, the QoS of XR services is determined based on the acquired terminal capability information. Furthermore, accurate QoS facilitates the rational allocation of latency budget, thus rationally determining the distribution of total transmission latency across transmission nodes.

[0128] exist Figure 4 In a variation of the illustrated embodiment, Figure 4 The data transmission method shown can be executed by an XR application server. Specifically, the XR application server can execute... Figure 4 Steps S101 to S103 are shown to determine the transmission delay based on the acquired terminal capability information and send the transmission delay to the SMF.

[0129] Furthermore, the terminal capability information can be directly obtained from the UE and HMD. Alternatively, step S101 may include the step of obtaining the terminal capability information from the SMF.

[0130] Furthermore, the display time of the XR frame in the HMD can be calculated by the XR application server and then notified to the network side. Correspondingly, the latest arrival time of the XR frame corresponding to the data at the UE or the transmission delay can be determined by the XR application server and then notified to the SMF.

[0131] Specifically, the terminal's capability information can be reported directly to the XR application server or through the network side. Therefore, when the XR service is started, the XR application server can determine the latest time the XR frame arrives at the UE or the transmission delay based on the XR frame's transmission time, total transmission delay, and the processing time of the XR frame in the UE and HMD, and notify the base station through the core network.

[0132] Correspondingly, the network side can 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.

[0133] Figure 5This is a schematic diagram of a data transmission device according to a second embodiment of the present invention. Those skilled in the art will understand that the data transmission device 2 described in this embodiment can be used to implement the above-described... Figure 4 The method described in the embodiments is a technical solution.

[0134] Specifically, refer to Figure 5 The data transmission device 2 described in this embodiment may include: an acquisition module 21, used to acquire terminal capability information, wherein the terminal capability information is used to indicate the XR capabilities supported by the UE and / or HMD; a determination module 22, used to determine the transmission delay based on the terminal capability information, wherein the transmission delay is used to indicate the maximum duration between the network device receiving the data and sending the data; and a sending module 23, used to send the transmission delay.

[0135] For more information on the working principle and operation mode of the data transmission device 2, please refer to the above. Figure 4 The relevant descriptions in the text will not be repeated here.

[0136] In specific implementations, the aforementioned data transmission device 2 may correspond to a chip with data transmission function in a network device, or to a chip with data processing function, such as a system-on-a-chip (SOC), a baseband chip, etc.; or to a chip module in a network device that includes a chip with data transmission function; or to a chip module with a chip with data processing function; or to a network device.

[0137] In specific implementation, the modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both.

[0138] For example, for various devices and products applied to or integrated into a chip, each module / unit can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, each module / unit can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0139] Figure 6 This is a flowchart of a data transmission method according to the third embodiment of the present invention. Figure 6 The implementation scheme can be applied to the network side, such as being executed by network devices on the network side. The network devices may include base stations. The above implementation... Figure 4 The SMF transmission delay in the illustrated embodiment extends to the base station, which executes this implementation scheme to transmit XR service data to the UE.

[0140] In specific implementation, the transmission method provided in steps S201 to S202 below can be executed by a chip with data transmission function in the network device, or by a baseband chip in the network device.

[0141] Specifically, refer to Figure 6 The data transmission method described in this embodiment may include the following steps:

[0142] Step S201, obtain transmission delay, wherein the transmission delay is used to indicate the maximum duration between the network device receiving the data and sending the data, and the transmission delay is determined according to terminal capability information, wherein the terminal capability information is used to indicate the XR capabilities supported by the UE and / or HMD;

[0143] Step S202: Transmit the data according to the transmission delay.

[0144] Those skilled in the art will understand that steps S201 to S202 can be considered as the above. Figure 4 The execution steps S101 to S103 in the illustrated embodiment correspond to each other, and they are complementary in their specific implementation principles and logic. Therefore, the explanation of the terms involved in this embodiment can be found by referring to... Figure 4 The relevant descriptions of the embodiments shown will not be repeated here.

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

[0146] 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; and determining the latest time when the XR frame arrives at the UE or the transmission delay based on the terminal capability information and the display time of the XR frame in the HMD.

[0147] For example, the base station can determine the time required for the terminal to process data packets based on the terminal capability information reported by the UE, and then calculate the latest time when the XR frame arrives at the UE based on the display time of the XR frame notified by the SMF in the HMD.

[0148] Furthermore, the base station can obtain the terminal capability information from the UE. Alternatively, the base station can obtain the terminal capability information from the core network.

[0149] Furthermore, the base station can receive the total transmission delay and the transmission time of the Nth XR frame preceding the XR frame from the XR application server. Then, based on the total transmission delay and the transmission time of the Nth XR frame preceding the XR frame, the display time of the XR frame corresponding to the data in the HMD is determined.

[0150] In one specific implementation, step S202 may include: after receiving the data, transmitting the data with the latest time when the XR frame arrives at the UE as a constraint.

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

[0152] For example, if the data is received after the latest time the XR frame corresponding to the data arrives at the UE, the base station will no longer transmit the data.

[0153] Therefore, after receiving data, regardless of whether jitter occurs at the time of data reception, the base station can determine the latest time of data transmission over the air interface based on this implementation scheme, and thus reasonably determine the subsequent execution logic. Furthermore, after the base station learns the latest time that the XR frame arrives at the UE, even if jitter occurs in the data received from the gateway, the base station can dynamically determine the "maximum permissible delay" of data transmission over the air interface.

[0154] Figure 7 This is a schematic diagram of a data transmission device according to the fourth embodiment of the present invention. Those skilled in the art will understand that the data transmission device 3 described in this embodiment can be used to implement the above-described... Figure 6 The method described in the embodiments is a technical solution.

[0155] Specifically, refer to Figure 7 The data transmission device 3 described in this embodiment may include: an acquisition module 31, used to acquire a transmission delay, wherein the transmission delay is used to indicate the maximum duration between when the network device receives the data and when it sends the data, and the transmission delay is determined according to terminal capability information, the terminal capability information being used to indicate the XR capabilities supported by the UE and / or HMD; and a transmission module 32, used to transmit the data according to the transmission delay.

[0156] For more information on the working principle and operation mode of the data transmission device 3, please refer to the above. Figure 7 The relevant descriptions in the text will not be repeated here.

[0157] In specific implementation, the aforementioned data transmission device 3 may correspond to a chip with data transmission function in a network device, or to a chip with data processing function, such as a system-on-a-chip (SOC), a baseband chip, etc.; or to a chip module in a network device that includes a chip with data transmission function; or to a chip module with a chip with data processing function; or to a network device.

[0158] In specific implementation, the modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both.

[0159] For example, for various devices and products applied to or integrated into a chip, each module / unit can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, each module / unit can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0160] Figure 8 This is a flowchart of a data transmission method according to the fifth embodiment of the present invention. Figure 8 The implementation scheme can be applied to the user equipment side, such as by the UE on the user equipment side.

[0161] In specific implementation, the transmission method provided by the following steps S401 to S402 can be executed by a chip with data transmission function in the user equipment, or by a baseband chip in the user equipment.

[0162] Specifically, refer to Figure 8 The data transmission method described in this embodiment may include the following steps:

[0163] Step S401: Obtain terminal capability information, wherein the terminal capability information is used to indicate the XR capabilities supported by the UE and / or HMD;

[0164] Step S402: Report terminal capability information.

[0165] Those skilled in the art will understand that steps S401 to S402 can be considered as the above. Figure 4 The execution steps S101 to S103 in the illustrated embodiment correspond to each other, and they are complementary in their specific implementation principles and logic. Therefore, the explanation of the terms involved in this embodiment can be found by referring to... Figure 4 The relevant descriptions of the embodiments shown will not be repeated here.

[0166] In one specific implementation, in step S401, the 5G UE can report the terminal capability information to the base station. Alternatively, the 5G UE can directly report the terminal capability information to the SMF.

[0167] In one variation, in step S401, the application layer of the 5G UE can report the terminal capability information to the XR application server. Alternatively, the HMD to which the UE is connected can report the terminal capability information to the XR application server.

[0168] In one specific implementation, step S401 may include the steps of: obtaining the capability information of the HMD; and generating the terminal capability information based on the capability information of the HMD and the capability information of the UE.

[0169] For example, the UE can combine the HMD processing data capability information obtained from interacting with the HMD with the UE's own data processing capability information to generate common capability information for both the UE and the HMD, namely the terminal capability information.

[0170] Furthermore, the UE can obtain HMD capability information directly from the HMD, or through other means. For example, the UE can obtain HMD capability information from the network management center, base station, other control network elements, or through methods pre-defined by the protocol.

[0171] Furthermore, the action of obtaining HMD capability information can be performed when the XR service is started, or it can be performed after the HMD is powered on.

[0172] In one specific implementation, after step S402, the data transmission method of this embodiment may further include the step of receiving data, wherein the data is transmitted according to a transmission delay, the transmission delay being used to indicate the maximum duration between the network device receiving the data and sending the data, and the transmission delay being determined according to terminal capability information.

[0173] Therefore, in this implementation scheme, the 5G UE actively reports terminal capability information, enabling the network side to perform the aforementioned actions. Figure 4 or Figure 6 The embodiment shown determines an appropriate transmission delay based on terminal capability information, and then transmits data according to that delay. Accordingly, the 5G UE can receive data sent by the network within a reasonable transmission delay.

[0174] In one specific implementation, for a type 3 terminal, that is, when the HMD and the UE are connected separately, the UE can also act as a transmission node, and therefore the latency budget allocated to the UE also needs to be considered.

[0175] Accordingly, after step S402, the transmission method described in this embodiment may further include the steps of: receiving data; receiving the latest time or transmission delay of transmitting the XR frame to the HMD reported by the HMD, wherein the latest time or transmission delay of transmitting the XR frame to the HMD is determined based on the capability information of the HMD and the display time of the XR frame corresponding to the data in the HMD; and transmitting the data with the latest time or transmission delay of transmitting the XR frame to the HMD as a constraint.

[0176] Specifically, the display time of the XR frame in the HMD can be obtained through signaling. The UE can obtain the display time of the XR frame in the HMD from the base station, or it can obtain the display time of the XR frame in the HMD from the XR application server through interaction between the application layer and the XR application server.

[0177] Furthermore, based on the HMD's capability information and the display time of the XR frame in the HMD, the UE can determine the latest possible time to transmit data via the Wi-Fi interface. If the UE fails to transmit the XR frame data via the Wi-Fi interface by the latest possible time, then the UE does not need to transmit it further.

[0178] In one variation, the latest time for transmitting the XR frame to the HMD can be determined by the HMD and reported to the UE.

[0179] Specifically, after step S402, the transmission method described in this embodiment may further include the steps of: receiving the latest time reported by the HMD for transmitting the XR frame to the HMD; and transmitting the data when the data is received, with the latest time for transmitting the XR frame to the HMD as a constraint.

[0180] Furthermore, the HMD can obtain the display time of the XR frame in the HMD from the XR application server or the UE.

[0181] In practical applications, the HMD can report to the UE the latest time to transmit the XR frame to the HMD at any time after the XR service is started.

[0182] Therefore, on the UE side, by adopting this implementation scheme, the UE actively reports the UE and HMD's data processing capabilities to the network so that the network side can determine the transmission delay budget.

[0183] Figure 9 This is a schematic diagram of a data transmission device according to the sixth embodiment of the present invention. Those skilled in the art will understand that... Figure 9 The data transmission device 4 can be used to implement the above. Figure 8 The method described in the embodiments is a technical solution.

[0184] Specifically, refer to Figure 9 The data transmission device 4 described in this embodiment may include: an acquisition module 41 for acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capabilities supported by the UE and / or HMD; and a reporting module 42 for reporting the terminal capability information.

[0185] For more information on the working principle and operation mode of the data transmission device 4, please refer to the above. Figure 8 The relevant descriptions in the text will not be repeated here.

[0186] In specific implementation, the aforementioned data transmission device 4 may correspond to a chip with data transmission function in a user equipment, or to a chip with data processing function, such as a system-on-a-chip (SOC), a baseband chip, etc.; or to a chip module in a user equipment that includes a chip with data transmission function; or to a chip module with a chip with data processing function; or to a user equipment.

[0187] In specific implementation, the modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both.

[0188] For example, for various devices and products applied to or integrated into a chip, each module / unit can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, each module / unit can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0189] In a typical application scenario, refer toFigure 10 The data generated by the XR application server 53 is transmitted to the terminal 51 for display via the network side 52. The terminal 51 includes an HMD 511 and a UE 512, with the UE 512 performing the above-described... Figure 8 The method described above; the network side 52 includes a base station 521 and one or more nodes of the core network, such as AMF522, SMF523, and PCRF524. One or more nodes of the network side 52, such as SMF523, can perform the above-described method. Figure 4 The method described in the embodiment can be executed by base station 521. Figure 6 The method of the illustrated embodiment.

[0190] In this application scenario, the data transmission process can include multiple stages. First, in stage 1, terminal 51 can report its own terminal capability information. Then, in stage 2, XR application server 53, network-side nodes 52, and UE 512, as data transmission nodes, can determine the XR service latency allocation based on the terminal capability information reported by terminal 51, and transmit data according to the allocated latency budget.

[0191] The following section will elaborate on the specific implementation process of each stage.

[0192] Continue to refer to Figure 10 In phase 1, UE512 can perform operation s801 to report terminal capability information of terminal51 to base station 521. For example, the terminal capability information of terminal51 may include the combination type of UE512 and HMD511.

[0193] For example, UE512 can report the terminal capability information via Radio Resource Control (RRC) messages. Alternatively, UE512 can also report via Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU), Radio Link Control (RLC) PDU, or Media Access Control-Control Element (MAC-CE), and can also report via Non-Access Stratum (NAS) signaling.

[0194] When reporting terminal capability information via NAS signaling, since base station 521 cannot directly read NAS signaling, the reported terminal capability information is transmitted through base station 521 to AMF522, and then AMF522 notifies base station 521.

[0195] Furthermore, operation s802 can be performed to report the terminal capability information to one or more core network nodes via base station 521. For example, base station 521 can report the terminal capability information of terminal 51 to AMF522, AMF522 can further report the terminal capability information to SMF523, and SMF523 can further report the terminal capability information to PCRF524.

[0196] It should be noted that the above reporting order among the core network nodes is only an example. In practical applications, the core network nodes that need to report, as well as the reporting order among the nodes, can be adjusted as needed.

[0197] In response to receiving terminal capability information from terminal 51, each core network node can use this information to determine the XR service latency allocation for UE512 during phase 2.

[0198] PCRF524 can use this information to determine the XR service billing for UE512. This is because, among the three terminal types, when performing the same service, the amount of data transmitted by terminal 51 of type 2 on the Uu interface is greater than that of terminal 51 of type 1 or type 3 on the Uu interface. Therefore, the corresponding billing function module needs to take special consideration during the billing process.

[0199] Furthermore, core network nodes (such as PCRF524) can execute operation s803 to report the terminal capability information of terminal 51 to XR application server 53. Accordingly, when determining the XR service QoS of UE512 in phase 2, the XR application server can consider the UE's capabilities.

[0200] It is worth noting that the specific message formats transmitted in each step of Phase 1 can be the same or different. When each node transmits a message to the next node, it can adjust the message format according to the interface's message specification, but the basic content transmitted remains the same.

[0201] As described above, by executing the process described in Phase 1, UE512 can report to the network side 52 the type of data processed by UE512 and HMD511 and the required processing time, so that the network side 52 can determine the transmission delay budget.

[0202] Continue to refer to Figure 10 In phase 2, base station 521 can first complete clock synchronization with UE512, HMD511 and XR application server 53.

[0203] Then, when the XR service starts, the XR application server 53 executes operation s804 to notify the core network node (such as SMF523) of the "display time of the XR frame in HMD511" through the session start procedure. For example, the specific content that the XR application server 53 notifies the SMF523 through operation s804 can be that the display time of the first XR frame of the XR service in HMD511 is 14:37:23:345ms on March 5, 2021, and then an XR frame is displayed every 16ms thereafter.

[0204] Furthermore, the SMF523 can perform operation s805 to notify the base station 521 of the new QoS parameters for this XR service: the time when each XR frame is transmitted via the Uu interface, which is also the "time when the XR frame is displayed in the HMD511".

[0205] Furthermore, base station 521 can execute operation s806 to determine the latest time for transmitting each XR frame via the Uu interface based on the type of terminal 51 and the data processing time. For example, if base station 521 determines that terminal 51 needs 15ms to process data based on the type of terminal 51, then it determines that the data packet contained in the first XR frame needs to be delivered to terminal 51 before 14:37:23:330ms on March 5, 2021, and thereafter, an XR frame needs to be delivered to terminal 51 every 16ms.

[0206] Based on this, when base station 521 receives the data packet corresponding to the XR frame, it can determine the latest time of data packet transmission on the air interface (i.e., Uu interface) regardless of whether jitter occurs at the time of receiving the data packet.

[0207] Therefore, in stage 2, the latest time for air interface transmission of XR data packets is determined by base station 521. Under the premise that jitter occurs when base station 521 receives downlink data, a reasonable latest time for XR data packet transmission can be determined.

[0208] In one variation, as described above Figure 10 The terminal capability information reporting process in Stage 1 differs from the bottom-up process shown. In Stage 1, the reporting of terminal capability information can also be as follows: Figure 11 The process is shown from top to bottom.

[0209] Specifically, refer to Figure 11 The application layer of UE512 can perform operation s901 to report its own terminal capability information combined with HMD to the XR application server 53.

[0210] Furthermore, operation s902 can be performed to notify one or more nodes on the network side 52 of the terminal capability information reported by UE512 via XR application server 53. For example, XR application server 53 can notify PCRF524 of the terminal capability information, which PCRF524 then notifies SMF523, which in turn notifies AMF522.

[0211] Furthermore, core network nodes (such as AMF522) can perform operation s903 to notify base station 521 of the terminal capability information reported by UE512.

[0212] Alternatively, operation s901 can be replaced by operation s901', that is, HMD511 reports the terminal capability information of terminal 51 to XR application server 53.

[0213] Therefore, UE512 can report the type of data processed by UE512 and HMD511 and the required processing time to XR application server 53, and then XR application server 53 notifies the core network and access network so that network side 52 can determine the transmission delay budget.

[0214] In one variation example, Figure 10 The actions performed on the s806 in Phase 2 shown can be executed by core network nodes (such as SMF523), that is, Figure 10 Operations s805 and s806 shown can be replaced with Figure 12 The operations s805' and s806' shown enable the SMF523 to determine the latest time for Uu interface transmission of each XR frame and notify the base station 521.

[0215] Specifically, refer to Figure 12 After obtaining the "display time of the XR frame in HMD511" based on operation s804, SMF523 can execute operation s805' to determine the latest time for Uu interface transmission of each XR frame according to the type of terminal 51 and the data processing time. For example, if SMF523 determines that terminal 51 needs 15ms to process XR data packets based on the type of terminal 51, then it determines that the data packets contained in the first XR frame need to be delivered to terminal 51 before 14:37:23:330ms on March 5, 2021, and then an XR frame needs to be delivered to terminal 51 every 16ms thereafter.

[0216] Furthermore, SMF523 performs operation s806' to notify base station 521 of the new QoS parameters for this XR service: the latest time when the Uu interface transmits each XR frame.

[0217] In a variation example, for type 3 terminal 51, since HMD511 and UE512 are connected separately, time is required for data transmission between them. Therefore, after performing operation s806, phase 2 can further perform subsequent actions to determine the latest transmission time of data in Wi-Fi transmission.

[0218] Specifically, please refer to Figure 10 UE512 can execute operation s807 to obtain the data processing capabilities of HMD511. For example, the obtained content could be "the processing time required for an XR frame in HMD511 is xms". The order of this action in the overall data transmission process is not necessarily the order of operation s807 described in this specific embodiment. This action can also be performed after HMD511 is powered on, and there is no strict sequential relationship between it and other steps in this specific embodiment.

[0219] Furthermore, UE512 can execute operation s808 to obtain new QoS parameters for the XR service from base station 521 via signaling: the display time of the XR frame in HMD511. For example, the display time of the first XR frame of the XR service in HMD511 is 14:37:23:345ms on March 5, 2021.

[0220] Accordingly, in this variation example, base station 521 obtains the new QoS parameters for this XR service by performing operation s805: the time of transmission of each XR frame via the Uu interface, and then notifies UE 512 by performing operation s808.

[0221] Furthermore, UE512 can execute operation s809 to determine the latest time to transmit data via the Wi-Fi interface based on the processing capability of HMD511. For example, assuming the first XR frame of the XR service is displayed in HMD511 at 14:37:23:345ms on March 5, 2021, and HMD511 requires 7ms of processing time, then UE512 can determine that the latest time to transmit the corresponding data of this XR frame via the Wi-Fi interface is 14:37:23:338ms on March 5, 2021. If UE512 has not yet transmitted the XR frame data via the Wi-Fi interface by this time, then no further transmission is necessary.

[0222] Therefore, for type 3 terminals, UE512 can determine the latest time for Wi-Fi transmission of XR data packets, thus avoiding the transmission of XR data too late.

[0223] In a variation, the source of the display time of the XR frame acquired by operation s808 in HMD511 can also be the application layer. For example, the application layer of UE512 directly obtains this information from the XR application server 53.

[0224] In a variation, the action of determining the latest time for Wi-Fi interface data transmission for type 3 terminal 51 described above can also be performed by HMD 511. That is, Figure 10 Operations s807 to s809 can be replaced by operations s807' to s809'.

[0225] Specifically, HMD511 can perform operation s807' to obtain new QoS parameters for the current XR service from XR application server 53: the display time of the XR frame in HMD511. For example, the obtained information could be "the display time of the first XR frame of the XR service in HMD511 is 14:37:23:345ms on March 5, 2021".

[0226] Furthermore, the HMD511 can execute operation s808' to determine the latest time to receive data via the Wi-Fi interface based on its processing capabilities. For example, assuming the HMD511 requires 7ms of processing time, the latest time to receive the first frame of XR data via the Wi-Fi interface is determined to be March 5, 2021, 14:37:23:338ms, and then an XR frame is transmitted every 16ms thereafter. That is, the latest time for the HMD511 to receive the second frame of XR data via the Wi-Fi interface is March 5, 2021, 14:37:23:354ms.

[0227] Furthermore, HMD511 performs operation s809' to notify UE512 of the latest time determined for receiving data via the Wi-Fi interface.

[0228] In one variation, when the HMD511 performs operation s807', it can obtain the display time of the XR frame in the HMD511 from the UE.

[0229] In one variation example, Figure 10 The actions performed on s806 in stage 2 shown can be executed by the XR application server 53, that is, Figure 10 Operations s804 to s806 shown can be replaced with Figure 13 Operations s1101 to s1102 are shown, thereby allowing the XR application server 53 to determine the latest time when the XR frame is delivered to the UE 512.

[0230] First, base station 521 can synchronize its clock with UE 512, HMD 511, and XR application server 53. Then, in phase 1, UE 512 can execute operation s901 to report terminal capability information of terminal 51 to XR application server 53. The terminal capability information includes the processing time of XR frames in UE 512 and HMD 511.

[0231] Then, refer to Figure 13 The XR application server 53 can perform operation s1101 to determine the latest time when the XR frame is delivered to UE512 based on the XR frame's transmission time, the application layer end-to-end transmission delay, and the XR frame's processing time in UE512 and HMD511 when the XR service is started.

[0232] Furthermore, operation s1102 can be executed. Based on the session initiation procedure, XR application server 53 notifies base station 521 of the latest delivery time of the XR frame to UE 512 via a core network node (such as SMF 523). For example, assuming the first XR frame of the XR service is sent from XR application server 53 at 14:37:23:305ms on March 5, 2021, with an application layer end-to-end latency of 40ms, and an XR frame is sent every 16ms thereafter. Based on operation s901, XR application server 53 determines that terminal 51 needs 15ms to process the data packet. Then, when executing operation s1101, XR application server 53 can determine that the data packet contained in the first XR frame needs to be delivered to terminal 51 before 14:37:23:330ms on March 5, 2021.

[0233] After the base station 521 learns the latest time by operating s1102, even if the data packets received from the gateway are jittered, the base station 521 can dynamically determine the "maximum allowable delay" of the data packets in the air interface transmission.

[0234] Therefore, in this variation, the XR application server 53 determines the latest time for the base station 521 to transmit XR data packets over the air interface and notifies the base station 521 to execute it. This avoids transmitting XR data too late, even if jitter occurs when the base station 521 receives downlink data.

[0235] In one variation example, Figure 10 The actions performed on the s806 in Phase 2 shown can be executed by core network nodes (such as SMF523), that is, Figure 10 Operations s805 and s806 shown can be replaced with Figure 14 The operations s1202 and s1203 shown enable the SMF523 to determine the latest time for transmitting each XR frame via the Uu interface and notify the base station 521. Furthermore, in conjunction with the above... Figure 12 The difference in the variations shown is that, Figure 12 The S804 can be further replaced by... Figure 14 The operation s1201 shown is different from the content that SMF523 obtains from XR application server 53.

[0236] First, base station 521 can synchronize its clock with UE 512, HMD 511, and XR application server 53. Then, in phase 1, SMF 523 obtains terminal capability information of terminal 51 through operations s801 and s802, thereby determining the type of combination between UE 512 and HMD 511 and the time required for XR frame processing.

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

[0238] Furthermore, SMF523 can perform operation s1202 to determine the latest time when the XR frame is delivered to UE512 based on "the time when the XR frame is sent, the end-to-end transmission delay of the application layer" and "the type of combination of UE512 and HMD511 and the length of time required for XR frame processing".

[0239] Then, SMF523 can perform operation s1203 to notify base station 521 of the determined latest time.

[0240] For example, suppose the first XR frame of the XR service is sent from the XR application server 53 at 14:37:23:305ms on March 5, 2021, with an application layer end-to-end latency of 40ms, and an XR frame is sent every 16ms thereafter. SMF523 determines through operations s801 and s802 that terminal 51 needs 15ms to process the data packet. Therefore, when SMF523 executes operation s1202, it can determine that the data packet contained in the first XR frame needs to be delivered to terminal 51 before 14:37:23:330ms on March 5, 2021.

[0241] After learning of the latest time, even if the data packets received from the gateway experience jitter, the base station 521 can dynamically determine the "maximum allowable delay" for data packets to be transmitted over the air interface.

[0242] Therefore, in this variation, the SMF523 determines the latest time for base station 521 to transmit XR data packets over the air interface and notifies base station 521 to execute it. This avoids transmitting XR data too late, even if jitter occurs when base station 521 receives downlink data.

[0243] In a common variation example, the actions performed by SMF523 in stage 2 above can also be performed by AMF522.

[0244] In the above Figures 10 to 14In the application scenarios and variations shown, the peer of terminal 51 that reports terminal capability information in stage 1 can be one or more nodes of the core network, base station 521, or XR application server 53.

[0245] When transmitting data for XR services with less stringent latency requirements, terminal 51 can report terminal capability information to base station 521. Correspondingly, base station 521 and core network nodes can execute... Figure 10 The system operates on S805 and S806. By adjusting the delay budget and calculating the latest time by the base station 521, XR data processing can be completed at the access layer with minimal impact on the upper layers.

[0246] When transmitting XR service data with strict latency requirements, terminal 51 can report terminal capability information to nodes in the core network (such as SMF523). Correspondingly, base station 521 and nodes in the core network can perform... Figure 12 Operations s805' and s806' are used in the middle. Because the core network plays a crucial role in the entire transmission process, it is more appropriate for the core network to calculate the latest time.

[0247] This invention also provides a computer-readable storage medium, which is a non-volatile or non-transitory storage medium storing a computer program. When 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 non-volatile or non-transitory memory. The storage medium may include ROM, RAM, a magnetic disk, or an optical disk, etc.

[0248] This invention also provides another data transmission device, including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor runs the computer program, it performs the above-described... Figure 4 The steps of the data transmission method provided in the corresponding embodiment are described. For example, the data transmission device can be a network device, such as an SMF in a network device. Another example is that the data transmission device can be an XR application server.

[0249] This invention also provides another data transmission device, including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor runs the computer program, it performs the above-described... Figure 6 The steps of the data transmission method provided in the corresponding embodiment. For example, the data transmission device can be a network device, such as a base station in a network device.

[0250] This invention also provides another data transmission device, including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor runs the computer program, it performs the above-described... Figure 8 The steps of the data transmission method provided in the corresponding embodiment. For example, the data transmission device can be a user equipment.

[0251] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include ROM, RAM, disk, or optical disk, etc.

[0252] The technical solution of this invention is applicable to 5G (5-generation) communication systems, as well as 4G and 3G communication systems, and can also be applied to various communication systems that evolve in the future, such as 6G and 7G.

[0253] This technical solution is also applicable to different network architectures, including but not limited to relay network architecture, dual-link architecture, and Vehicle-to-Everything (V2X) architecture.

[0254] The 5G CN described in this application embodiment can also be referred to as a new core network, 5G NewCore, or next-generation core network (NGC), etc. The 5G-CN is set up independently of existing core networks, such as evolved packet cores (EPC).

[0255] The base station (BS) in this application embodiment, also referred to as base station equipment, is a device deployed in a wireless access network to provide wireless communication functions. For example, in a 2G network, equipment providing base station functions includes a base transceiver station (BTS) and a base station controller (BSC); in a 3G network, equipment providing base station functions includes a Node B (NodeB) and a radio network controller (RNC); in a 4G network, equipment providing base station functions includes an evolved Node B (eNB); in wireless local area networks (WLANs), equipment providing base station functions is an access point (AP); in 5G New Radio (NR), equipment providing base station functions includes a continuing evolved Node B (gNB); and other equipment providing base station functions in future new communication systems, etc.

[0256] In this application, the term "terminal" can refer to various forms of user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent, or user device. Terminal equipment can also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device, or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal equipment in future 5G networks, or terminal equipment in future evolved Public Land Mobile Networks (PLMNs), etc. This application does not limit the scope of these examples.

[0257] In this application embodiment, the one-way communication link from the access network to the terminal is defined as the downlink, the data transmitted on the downlink is called downlink data, and the transmission direction of the downlink data is called the downlink direction; while the one-way communication link from the terminal to the access network is defined as the uplink, the data transmitted on the uplink is called uplink data, and the transmission direction of the uplink data is called the uplink direction.

[0258] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article indicates that the preceding and following related objects have an "or" relationship.

[0259] In the embodiments of this application, "multiple" refers to two or more.

[0260] The descriptions of "first," "second," etc., appearing in the embodiments of this application are for illustrative purposes and to distinguish the objects being described. They have no order and do not indicate any special limitation on the number of devices in the embodiments of this application, nor do they constitute any limitation on the embodiments of this application.

[0261] In this application's embodiments, "connection" refers to various connection methods, such as direct or indirect connection, to achieve communication between devices. This application's embodiments do not impose any limitations on this. In this application's embodiments, "network" and "system" express the same concept; a communication system is a communication network.

[0262] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0263] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. 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 synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0264] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0265] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0266] In the several embodiments provided in this application, it should be understood that the disclosed methods, apparatuses, and systems can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0267] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or in a combination of hardware and software functional units.

[0268] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0269] While the present invention has been disclosed above, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of the invention; therefore, the scope of protection of the present invention should be determined by the scope defined in the claims.

Claims

1. A data transmission method, characterized by, Applied to a core network node side, comprising: In response to the data being an XR service with strict delay requirement, obtaining terminal capability information, wherein the terminal capability information is used to indicate XR capability supported by the UE and the HMD; According to the terminal capability information, determining a transmission delay or a latest time of an XR frame corresponding to the data reaching the UE, wherein the transmission delay is used to indicate a maximum time length between receiving the data by a network device and sending the data. Sending the transmission delay or the latest time of the XR frame reaching the UE.

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 used to indicate XR capability supported by the UE, and the HMD capability information is used to indicate XR capability supported by the HMD.

3. The data transmission method of claim 2, wherein, The obtaining of the terminal capability information comprises: Receiving the UE capability information reported by the UE, and receiving the HMD capability information reported by the HMD.

4. The data transmission method of claim 1, wherein, The obtaining of the terminal capability information comprises: Obtaining the terminal capability information from a base station; or Obtaining the terminal capability information from an XR application server.

5. The data transmission method of claim 1, wherein, The obtaining of the terminal capability information comprises: Obtaining the terminal capability information from an SMF.

6. The data transmission method of claim 1, wherein, Further comprising: Reporting the terminal capability information to an XR application server; And / or, Reporting a data sending advance amount to an XR application server, wherein the data sending advance amount is determined based on the terminal capability information.

7. The data transmission method of claim 1, wherein, The terminal capability information comprises at least one of the following: A type of combination of the UE and the HMD; An XR service processing time required by the combination of the UE and the HMD; An XR service processing capability required by the combination of the UE and the HMD; An XR service processing time required by the combination of the UE and the HMD after Uu port transmission.

8. The data transmission method of claim 1, wherein, The determining of the transmission delay or the latest time of the XR frame corresponding to the data reaching the UE according to the terminal capability information comprises: Obtaining a display time of the XR frame corresponding to the data in the HMD; According to the terminal capability information and the display time of the XR frame in the HMD, determining the latest time of the XR frame reaching the UE or the transmission delay.

9. The data transmission 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 a maximum allowable delay from sending the data by the XR application server to the data reaching an application layer of the UE, and N is a natural number; According to the total transmission delay and the sending time of the Nth XR frame before the XR frame, determining the display time of the XR frame corresponding to the data in the HMD.

10. The data transmission method of claim 1, wherein, The determining of the transmission delay or the latest time of the XR frame corresponding to the data reaching the UE according to the terminal capability information comprises: Receiving the latest time of the XR frame reaching the UE or the transmission delay from an XR application server, wherein the latest time of the XR frame reaching the UE is determined according to the terminal capability information and the display time of the XR frame in the HMD.

11. The data transmission method according to claim 8 or 9 or 10, characterized in that, Further comprising: When an XR service is started, clock synchronization is performed with the UE, HMD, base station, and XR application server.

12. A data transmission apparatus, characterized by comprising: Applied to a core network node side, comprising: An acquisition module, configured to acquire terminal capability information in response to data of an XR service with strict delay requirement being transmitted, wherein the terminal capability information is used to indicate XR capability supported by the UE and the HMD; A determination module, configured to determine a latest time when an XR frame corresponding to the data arrives at the UE according to the terminal capability information, wherein the transmission delay is used to indicate a maximum time length between reception of the data by the network device and transmission of the data. A sending module, configured to send the transmission delay or the latest time when the XR frame arrives at the UE.

13. A data transmission method, characterized by, Applied to a network device side, comprising: Acquire a transmission delay or a latest time when an XR frame corresponding to the data arrives at the UE, wherein the transmission delay is used to indicate a maximum time length between reception of the data by the network device and transmission of the data, and the transmission delay or the latest time when the XR frame arrives at the UE is determined according to terminal capability information, wherein the terminal capability information is used to indicate XR capability supported by the UE and the HMD; Transmit the data according to the transmission delay or the latest time when the XR frame arrives at the UE. In response to data of an XR service with relaxed delay requirement being transmitted, the acquisition of the transmission delay or the latest time when the XR frame arrives at the UE comprises: acquisition of the terminal capability information and display time of the XR frame corresponding to the data in the HMD; and determination of the latest time when the XR frame arrives at the UE or the transmission delay according to the terminal capability information and the display time of the XR frame in the HMD. In response to data of an XR service with strict delay requirement being transmitted, the acquisition of the transmission delay or the latest time when the XR frame arrives at the UE comprises: reception of the transmission delay or the latest time when the XR frame arrives at the UE from the SMF.

14. The data transmission method of claim 13, wherein, The acquisition of the display time of the XR frame corresponding to the data in the HMD comprises: Receiving a total transmission delay and transmission time of an Nth XR frame before the XR frame from the XR application server, wherein the total transmission delay is a transmission delay between the XR application server and the UE, and N is a natural number; Determining the display time of the XR frame corresponding to the data in the HMD according to the total transmission delay and the transmission time of the Nth XR frame before the XR frame.

15. The data transmission method of claim 13, wherein, The transmission of the data according to the transmission delay or the latest time when the XR frame arrives at the UE comprises: After the data is received, the data is transmitted with the latest time when the XR frame arrives at the UE as a constraint.

16. The data transmission method of claim 13, wherein, Further comprising: When an XR service is started, clock synchronization is performed with the UE, HMD, SMF, and XR application server.

17. 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 used to indicate XR capability supported by the UE, and the HMD capability information is used to indicate XR capability supported by the HMD.

18. The data transmission method of claim 13, wherein, The terminal capability information includes at least one of the following: A type of the UE combined with the HMD; An XR service processing time required by the UE combined with the HMD; An XR service processing capability required by the UE combined with the HMD; An XR service processing time required by the UE combined with the HMD after Uu port transmission.

19. A data transmission apparatus, characterized by comprising: Applied to a network device side, including: An acquisition module, configured to acquire a transmission delay or a latest time of an XR frame corresponding to the data reaching a UE, wherein the transmission delay is used to indicate a maximum time length between receiving the data by the network device and sending the data, and the transmission delay or the latest time of the XR frame reaching the UE is determined according to terminal capability information, and the terminal capability information is used to indicate an XR capability supported by the UE and the HMD; A transmission module, configured to transmit the data according to the transmission delay or the latest time of the XR frame reaching the UE. In response to the data being of an XR service with a relaxed requirement on a time delay, the acquisition module performs the following steps: acquiring the terminal capability information and a display time of the XR frame corresponding to the data in the HMD; and determining the transmission delay or the latest time of the XR frame reaching the UE according to the terminal capability information and the display time of the XR frame in the HMD. In response to the data being of an XR service with a strict requirement on a time delay, the acquisition module performs the following step: receiving the transmission delay or the latest time of the XR frame reaching the UE from an SMF.

20. A data transmission method, characterized by, Applied to a user equipment side, including: Acquiring terminal capability information, wherein the terminal capability information is used to indicate an XR capability supported by the UE and the HMD; Reporting the terminal capability information; Receiving data, wherein the data is transmitted according to a transmission delay or a latest time of an XR frame corresponding to the data reaching the UE, the transmission delay is used to indicate a maximum time length between receiving the data by a network device and sending the data, and the transmission delay or the latest time of the XR frame reaching the UE is determined according to terminal capability information; In response to the data being of an XR service with a relaxed requirement on a time delay, an action of determining the transmission delay or the latest time of the XR frame reaching the UE according to the terminal capability information is performed by a base station. In response to the data being of an XR service with a strict requirement on a time delay, an action of determining the transmission delay or the latest time of the XR frame reaching the UE according to the terminal capability information is performed by an SMF.

21. The data transmission method of claim 20, wherein, The acquiring of the terminal capability information includes: Acquiring capability information of the HMD; Generating the terminal capability information according to the capability information of the HMD and capability information of the UE.

22. The data transmission method of claim 20, wherein, Further including: Acquiring a display time of the XR frame corresponding to the data in the HMD; Determining a latest time of transmitting the XR frame to the HMD or a transmission delay according to the capability information of the HMD and the display time of the XR frame in the HMD; Transmitting the data with the latest time of transmitting the XR frame to the HMD or the transmission delay as a constraint.

23. The data transmission method of claim 20, wherein, Further including: receive a latest time or a transmission delay of transmitting the XR frame to the HMD reported by the HMD, wherein the latest time or the transmission delay of transmitting the XR frame to the HMD is determined according to the capability information of the HMD and a display time of the XR frame corresponding to the data in the HMD; transmit the data with the latest time or the transmission delay of transmitting the XR frame to the HMD as a constraint.

24. The data transmission method of claim 20, wherein, The reported terminal capability information includes: report the terminal capability information to a base station, an XR application server or an SMF.

25. The data transmission method of claim 20, wherein, The terminal capability information includes UE capability information and HMD capability information, wherein the UE capability information is used to indicate XR capability supported by the UE, and the HMD capability information is used to indicate XR capability supported by the HMD.

26. The data transmission method of claim 20, wherein, The terminal capability information includes at least one of the following: a type of combination of the UE and the HMD; XR service processing time required by the UE in combination with the HMD; XR service processing capability required by the UE in combination with the HMD; XR service processing time required by the UE after Uu port transmission in combination with the HMD.

27. The data transmission method of claim 20, wherein, Further comprising: clock synchronization with a base station, an HMD, an SMF and an XR application server when an XR service is started.

28. A data transmission device, characterized by Applied to a user equipment side, comprising: an acquisition module configured to acquire terminal capability information, wherein the terminal capability information is used to indicate XR capability supported by the UE and the HMD; a reporting module configured to report the terminal capability information. The data transmission device further performs the step of receiving data, wherein the data is transmitted according to a transmission delay or a latest time of arrival of an XR frame corresponding to the data at the UE, the transmission delay is used to indicate a maximum time length between receiving the data by a network device and sending the data, and the transmission delay or the latest time of arrival of the XR frame at the UE is determined according to terminal capability information; wherein, in response to the data being of an XR service with relaxed delay requirement, the action of determining the transmission delay or the latest time of arrival of the XR frame at the UE according to the terminal capability information is performed by a base station; in response to the data being of an XR service with strict delay requirement, the action of determining the transmission delay or the latest time of arrival of the XR frame at the UE according to the terminal capability information is performed by an SMF.

29. A computer-readable storage medium, which is a non-volatile storage medium or a non-transitory storage medium, on which a computer program is stored, characterized in that, The computer program, when executed by a processor, performs the steps of the method of any one of claims 1 to 11 or any one of claims 13 to 18 or any one of claims 20 to 27.

30. A data transmission apparatus comprising a memory and a processor, said memory having stored thereon a computer program executable on said processor, characterized in that, The processor, when executing the computer program, performs the steps of the method of any one of claims 1 to 11 or any one of claims 13 to 18 or any one of claims 20 to 27.

Images