WO2022228322A1 - 数据传输方法及装置、计算机可读存储介质 - Google Patents

数据传输方法及装置、计算机可读存储介质 Download PDF

Info

Publication number
WO2022228322A1
WO2022228322A1 PCT/CN2022/088676 CN2022088676W WO2022228322A1 WO 2022228322 A1 WO2022228322 A1 WO 2022228322A1 CN 2022088676 W CN2022088676 W CN 2022088676W WO 2022228322 A1 WO2022228322 A1 WO 2022228322A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability information
hmd
data
terminal capability
transmission delay
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/088676
Other languages
English (en)
French (fr)
Inventor
韩立锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Publication of WO2022228322A1 publication Critical patent/WO2022228322A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2111/00—Details relating to CAD techniques
    • G06F2111/18—Details relating to CAD techniques using virtual or augmented reality

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a data transmission method and device, and a computer-readable storage medium.
  • Extended Reality (XR) technology is the collective name of Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR) technology, which can combine the physical environment with The fusion of virtual environments, or the provision of a completely immersive virtual experience environment, has broad application prospects in the era of the fifth-generation mobile communication technology (The Fifth-Generation mobile communications, referred to as 5G).
  • 5G The Fifth-Generation mobile communications
  • XR services Services transmitted based on XR technology can be called XR services.
  • QoS Quality of Service
  • UE User Equipment
  • the technical problem solved by the present invention is how to accurately determine the QoS of the XR service so as to enhance the transmission of the XR service.
  • an embodiment of the present invention provides a data transmission method, including: acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; according to the terminal capability information , determine the transmission delay, where the transmission delay is used to indicate the maximum duration between the network device receiving the data and sending the data; the transmission delay is sent.
  • the terminal capability information includes 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.
  • the acquiring the terminal capability information includes: receiving the UE capability information reported by the UE, and receiving the HMD capability information reported by the HMD.
  • the acquiring the terminal capability information includes: acquiring the terminal capability information from a base station; or acquiring the terminal capability information from an XR application server.
  • the acquiring the terminal capability information includes: acquiring the terminal capability information from the SMF.
  • the data transmission method further includes: reporting the terminal capability information to the XR application server; and/or reporting the data sending advance to the XR application server, where the data sending advance is based on the terminal capability information definite.
  • the terminal capability information includes at least one of the following: the type of the combination of the UE and the HMD; the required XR service processing time for the combination of the UE and the HMD; the required XR service processing capability for the combination of the UE and the HMD; HMD combination, XR service processing time required after Uu port transmission.
  • the determining the transmission delay according to the terminal capability information includes: acquiring the display time of the XR frame corresponding to the data in the HMD; The display time in the HMD is used to determine the latest time when the XR frame arrives at the UE or the transmission delay.
  • the acquiring the display time of the XR frame corresponding to the data in the HMD includes: receiving the total transmission delay from the XR application server and the sending time of the Nth XR frame before the XR frame, wherein , the total transmission delay is the maximum allowable delay from the time when the XR application server sends the data to the time when the data reaches the application layer of the UE, N is a natural number; according to the total transmission delay and the XR The transmission moment of the Nth XR frame before the frame determines the display moment of the XR frame corresponding to the data in the HMD.
  • the determining the transmission delay according to the terminal capability information includes: receiving the latest time at which the XR frame corresponding to the data arrives at the UE or the transmission delay from the XR application server, wherein the The latest time at which the XR frame arrives at the UE is determined according to the terminal capability information and the display time of the XR frame in the HMD.
  • the data transmission method further includes: when the XR service is started, performing clock synchronization with the UE, the HMD, the base station and the XR application server.
  • an embodiment of the present invention further provides a data transmission apparatus, including: an acquisition module configured to acquire terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; a determining module, configured to determine the transmission delay according to the terminal capability information, wherein the transmission delay is used to indicate the maximum time period between the network device receiving the data and sending the data; the sending module is configured to send the transmission delay.
  • an embodiment of the present invention further provides a data transmission method, including: obtaining a transmission delay, wherein the transmission delay is used to indicate the maximum time between receiving the data and sending the data by a network device.
  • the transmission delay is determined according to the terminal capability information, and the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; the data is transmitted according to the transmission delay.
  • the acquiring the transmission delay includes: receiving the transmission delay from the SMF.
  • the acquiring the transmission delay includes: acquiring the terminal capability information and the display time of the XR frame corresponding to the data in the HMD; according to the terminal capability information and the XR frame in the HMD The display time in the HMD is used to determine the latest time when the XR frame arrives at the UE or the transmission delay.
  • the acquiring the display time of the XR frame corresponding to the data in the HMD includes: receiving the total transmission delay from the XR application server and the sending time of the Nth XR frame before the XR frame, wherein , the total transmission delay is the transmission delay between the XR application server and the UE, and N is a natural number; according to the total transmission delay and the transmission time of the Nth XR frame before the XR frame, determine the corresponding data The display moment of the XR frame in the HMD.
  • the transmitting the data according to the transmission delay includes: after receiving the data, transmitting the data with the latest time when the XR frame arrives at the UE as a constraint.
  • the data transmission method further includes: when the XR service is started, performing clock synchronization with the UE, the HMD, the SMF and the XR application server.
  • the terminal capability information includes 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.
  • the terminal capability information includes at least one of the following: the type of the combination of the UE and the HMD; the required XR service processing time for the combination of the UE and the HMD; the required XR service processing capability for the combination of the UE and the HMD; HMD combination, XR service processing time required after Uu port transmission.
  • an embodiment of the present invention further provides a data transmission apparatus, including: an acquisition module, configured to acquire a transmission delay, wherein the transmission delay is used to instruct a network device to receive the data to send the data.
  • the maximum duration between data, and the transmission delay is determined according to the terminal capability information, and the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; the transmission module is used to transmit the data according to the transmission delay. stated data.
  • an embodiment of the present invention further provides a data transmission method, including: 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.
  • the data transmission method further includes: receiving data, wherein the data is transmitted according to a transmission delay, and the transmission delay is used to indicate the time between the network device receiving the data and sending the data and the transmission delay is determined according to the terminal capability information.
  • the acquiring terminal capability information includes: acquiring capability information of the HMD; and generating the terminal capability information according to the capability information of the HMD and the capability information of the UE.
  • the data transmission method further includes: receiving data; acquiring the display time of the XR frame corresponding to the data in the HMD; according to the capability information of the HMD and the XR frame in the HMD. Display time, determine the latest time or transmission delay for transmitting the XR frame to the HMD; transmit the data with the latest time or transmission delay for transmitting the XR frame to the HMD as a constraint.
  • the data transmission method further includes: receiving data; receiving the latest time or transmission delay for transmitting the XR frame to the HMD reported by the HMD, wherein the transmitting the XR frame to the HMD
  • the latest time or transmission delay of the XR frame is determined according to the capability information of the HMD and the display time of the XR frame corresponding to the data in the HMD; the latest time for transmitting the XR frame to the HMD
  • the time or transmission delay is the constraint, and the data is transmitted.
  • the reporting of the terminal capability information includes: reporting the terminal capability information to the base station, the XR application server or the SMF.
  • the terminal capability information includes 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.
  • the terminal capability information includes at least one of the following: the type of the combination of the UE and the HMD; the required XR service processing time for the combination of the UE and the HMD; the required XR service processing capability for the combination of the UE and the HMD; HMD combination, XR service processing time required after Uu port transmission.
  • the data transmission method further includes: when the XR service is started, performing clock synchronization with the base station, the HMD, the SMF, and the XR application server.
  • an embodiment of the present invention further provides a data transmission apparatus, including: an acquisition module configured to acquire terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD;
  • the reporting module is used to report terminal capability information.
  • embodiments of the present invention further provide a computer-readable storage medium, where the computer-readable storage medium is a non-volatile storage medium or a non-transitory storage medium, and a computer program is stored thereon. The steps of the above-described methods are performed when the computer program is executed by the processor.
  • an embodiment of the present invention further provides a data transmission device, including a memory and a processor, the memory stores a computer program that can run on the processor, and the processor runs the computer When the program executes the steps of the above method.
  • an embodiment of the present invention provides a data transmission method, including: acquiring terminal capability information, where the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; The terminal capability information determines the transmission delay, where the transmission delay is used to indicate the maximum time period between the network device receiving the data and sending the data; the transmission delay is sent.
  • the QoS of the XR service can be accurately determined according to the XR service processing capability of the terminal, especially the distribution of the transmission delay in each transmission node can be reasonably determined, thereby enhancing the transmission of the XR service data.
  • the QoS of the XR service is determined according to the acquired terminal capability information. Further, accurate QoS can help to reasonably allocate the delay budget, so as to reasonably determine the allocation of the total transmission delay in each transmission node.
  • an embodiment of the present invention further provides a data transmission method, including: acquiring a transmission delay, where the transmission delay is used to instruct a network device to receive the data to send the data.
  • the maximum duration between data, and the transmission delay is determined according to the terminal capability information, the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; the data is transmitted according to the transmission delay. Therefore, for the transmission node, regardless of whether jitter occurs when the transmission node receives the data, the latest time of data transmission on the air interface can be determined based on the received transmission delay, so as to avoid data transmission too late.
  • an embodiment of the present invention further provides a data transmission method, including: acquiring terminal capability information, where 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.
  • the UE actively reports the terminal capability information to the network, so that the network side can determine the transmission delay budget.
  • FIG. 1 is a schematic diagram of a first data transmission in the prior art
  • Fig. 2 is the second data transmission schematic diagram in the prior art
  • Fig. 3 is three kinds of combination types of UE and HMD involved in XR service in the prior art
  • FIG. 5 is a schematic structural diagram of a data transmission device according to the second embodiment of the present invention.
  • FIG. 6 is a flowchart of a data transmission method according to a third embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a data transmission device according to a fourth embodiment of the present invention.
  • FIG. 8 is a flowchart of a data transmission method according to a fifth embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a data transmission apparatus according to a sixth embodiment of the present invention.
  • FIG. 10 is a schematic diagram of signaling interaction in a typical application scenario of an embodiment of the present invention.
  • Fig. 11 is a schematic diagram of signaling interaction of a variation of stage 1 in the application scenario shown in Fig. 10;
  • Fig. 12 is the signaling interaction schematic diagram of the first variation of stage 2 in the application scenario shown in Fig. 10;
  • Fig. 13 is a schematic diagram of signaling interaction of the second variation of stage 2 in the application scenario shown in Fig. 10;
  • FIG. 14 is a schematic diagram of signaling interaction of the third variant of Phase 2 in the application scenario shown in FIG. 10 .
  • the existing network does not know the capability of the terminal to process XR service data in advance, so it cannot determine the allocation of the transmission delay budget of the XR service in each transmission node, and cannot accurately determine the QoS.
  • the video data (also called XR service data) transmitted by the XR service is generated from the XR Application Server (XR Application Server, referred to as XR APP Server), it enters the first network through the Internet Protocol (Internet Protocol, referred to as IP) network.
  • IP Internet Protocol
  • 3GPP 3rd Generation Partnership Project
  • Figure 1 shows the transmission process of XR service data when the network does not use an edge cloud (edge cloud).
  • the IP network after receiving the XR service data sent by the XR application server, the IP network directly transmits it to the UE via the User Plane Function (UPF) and the base station (eg gNB).
  • Fig. 2 shows the transmission process of XR service data when the network adopts edge cloud.
  • the IP network receives the XR service data sent by the XR application server and sends it to the UPF.
  • the edge cloud does some application layer processing (such as rendering, compositing, etc.)
  • the XR service data is then transmitted to the UE through the base station.
  • the 3GPP protocol defines many optional functions, such as whether to support 1024 Quadrature Amplitude Modulation (QAM), whether to support multiple connections, etc.
  • the base station can configure appropriate radio parameters for the UE according to the capabilities of the UE.
  • terminal refers to the combination result of the UE and the Head Mounted Display (HMD), where the UE is the receiving end of the XR service data, usually a 5G terminal, such as a 5G mobile phone (5G phone) , HMD is the presentation end of XR service data, such as AR glasses.
  • HMD Head Mounted Display
  • this type of terminal is an HMD, that is, the UE and the HMD are grouped together.
  • a type 1 terminal integrates all functions on the terminal side, including rendering, compositing, decoding, etc., and finally presents video and audio to the user. That is to say, after the terminal of type 1 receives the XR service data transmitted by the network via the User to Network interface Universal (Uu) interface (referred to as Uu port), it completes all function processing locally on the terminal side XR frames (ie, video frames for XR services) are presented. Since all functions are performed at the terminal, the Type 1 terminal is bulky and uncomfortable to wear.
  • Uu User to Network interface Universal
  • the UE and the HMD are also grouped together.
  • the terminal of type 2 has relatively simple functions, that is, only decoding.
  • other XR business data processing is done by the edge cloud, such as rendering, compositing, etc. That is to say, the XR service data transmitted by the network is processed by the edge cloud, and then transmitted to the type 2 terminal through the Uu port.
  • the type 2 terminal carries fewer functions, so it is thinner and more comfortable to use.
  • the UE and the HMD are physically separated, and data is transmitted between them through Wi-Fi.
  • most of the data processing functions can be placed on the UE side, such as rendering and compositing, while the HMD is only responsible for decoding. That is to say, after the 5G mobile phone receives the XR service data transmitted by the network via the Uu port, after the 5G mobile phone completes some functional processing locally, it is transmitted to the HMD via Wi-Fi, and the HMD completes the remaining part of the functional processing locally.
  • the frame is presented to the user.
  • the HMD in the Type 3 terminal is as thin and light as the Type 2 terminal and is comfortable to use.
  • the position of the time window reserved for the Uu port to transmit data may be different due to the different types of terminals.
  • the total downlink delay budget of a video frame ie, the end-to-end transmission delay of the application layer
  • ms milliseconds
  • the UPF For a type 1 terminal, it takes 10ms for the HMD to complete rendering, compositing, and decoding, and 10ms for Uu port transmission. Therefore, the UPF must transmit the data of the video frame to the base station 10ms in advance.
  • the UPF For type 2 terminals, it takes 5ms for HMD to complete decoding, and 10ms for Uu port transmission. Therefore, the UPF must transmit the data of the video frame to the base station 15ms in advance.
  • the UPF For a type 3 terminal, it takes 5ms for HMD to complete decoding, 1ms for Wi-Fi transmission, and 3ms for UE to complete rendering and compositing. Therefore, the UPF must transmit the data of the video frame to the base station 16ms in advance.
  • the network does not know the combination type of the UE and the HMD in advance, it cannot determine the allocation of service delay in each transmission node, and cannot accurately determine the QoS.
  • the base station will request the UE capability information from the Access and Mobility Management Function (AMF) in the core network. If the UE establishes a connection with the network for the first time and the AMF does not store the UE capability information, the base station will request the UE for this information. After the UE reports its own capability information, the base station configures the UE accordingly with radio parameters matching its capability. Subsequently, the base station uploads the capability information of the UE to the AMF for storage. After that, even if the UE is disconnected from the base station, its capability information still remains in the AMF. After the next time the UE establishes a connection with the base station, the base station only needs to obtain the UE capability information from the AMF, and there is no need for the UE to report.
  • AMF Access and Mobility Management Function
  • the base station when the service is established, the base station obtains the QoS information of the service, which includes a delay budget parameter, which means "the maximum allowable delay of each data packet transmitted on the air interface".
  • a delay budget parameter which means "the maximum allowable delay of each data packet transmitted on the air interface”.
  • the base station starts timing from the moment the UPF receives the data packet, and if the data packet has not been sent out after the "maximum allowable delay", the transmission is abandoned. That is to say, the base station takes the time when the data packet arrives at itself as the starting time of the "maximum allowable delay".
  • the existing protocol stipulates that the capability information reported by the UE only involves the access layer capability of the UE, and does not involve the XR processing capability of the UE, so the problem of delay budget allocation of the XR service cannot be solved.
  • the XR service has a large amount of data and dense data packets. Therefore, before the data packet arrives at the base station, it may experience queuing congestion in the IP network or in the UPF, causing jitter when the data packet arrives at the base station.
  • the base station cannot perceive the jittered data packets arriving at itself, and thus cannot achieve the flexible "maximum allowable delay”.
  • the required processing time is also different due to the different processing of the data packet. If the processing time required by the UE cannot be determined before the "maximum transmission delay" is determined, the "maximum transmission delay" of the data packet cannot be accurately determined.
  • an embodiment of the present invention provides a data transmission method, including: acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; according to the terminal capability information , determine the transmission delay, where the transmission delay is used to indicate the maximum duration between the network device receiving the data and sending the data; the transmission delay is sent.
  • the QoS of the XR service can be accurately determined according to the XR service processing capability of the terminal, especially the distribution of the transmission delay in each transmission node can be reasonably determined, thereby enhancing the transmission of the XR service data.
  • the QoS of the XR service is determined according to the acquired terminal capability information. Further, accurate QoS can help to reasonably allocate the delay budget, so as to reasonably determine the allocation of the total transmission delay in each transmission node.
  • FIG. 4 is a flowchart of a data transmission method according to the first embodiment of the present invention.
  • This embodiment can be applied to an XR scenario, and the data transmitted using this embodiment is XR service data.
  • the XR video generated by the XR application server is transmitted to the terminal via the network and presented, and the data corresponds to one or more XR frames in the XR video.
  • the network device may include a node in the core network, such as an AMF or a session management function (Session Management Function, SMF for short) in the core network.
  • AMF Access Management Function
  • SMF Session Management Function
  • One or more nodes in the core network can be understood as transmission nodes that need to pass through in the process of data transmission from the XR application server to the terminal.
  • the delay budget of these transmission nodes can be reasonably allocated according to the XR data processing capability of the terminal on the premise of satisfying the total transmission delay, so as to avoid data transmission to the terminal too late.
  • the total transmission delay is the maximum allowable delay from when the XR application server sends the XR service data until the XR service data reaches the application layer of the UE, and N is a natural number.
  • the total transmission delay may also be referred to as the application layer end-to-end transmission delay, which is related to service characteristics, and can be determined when the XR service is started and notified to the core network by the XR application server.
  • the core network reasonably allocates the delay budget of each transmission node based on the total transmission delay to ensure that the data can reach the UE within the end-to-end transmission delay of the application layer.
  • the transmission methods provided in the following steps S101 to S103 may be executed by a chip with a data transmission function in the network device, or may be executed by a baseband chip in the network device.
  • the data transmission method described in this embodiment may include the following steps:
  • Step S101 acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD;
  • Step S102 determining a transmission delay according to the terminal capability information, where the transmission delay is used to indicate the maximum duration between the network device receiving the data and sending the data;
  • Step S103 sending the transmission delay.
  • the terminal capability information includes 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.
  • the terminal capability information may include the type of the combination of the UE and the HMD, such as the three types shown in FIG. 3 above, and other extension types that may be defined in the future. Such as replacing the Wi-Fi connection in the type 3 terminal with a wired connection, etc.
  • the network side can determine the XR service processing time required for the combination of the UE and the HMD according to the type reported by the UE.
  • the terminal capability information may include the XR service processing time required by the combination of the UE and the HMD. That is, the UE can directly report the XR service processing time required for combining itself with the HMD.
  • the XR service processing time required for the combination of the UE and the HMD may 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 part of the function processing, and may also include the time required for data transmission between the UE and the HMD.
  • the UE and the HMD need to complete, reference may be made to the relevant description in FIG. 3 above, which will not be repeated here.
  • the required XR service processing time may be the average time, the maximum time, or the variance.
  • the terminal capability information may include the XR service processing capability required by the combination of the UE and the HMD. For example, a maximum of X bytes (Byte) of data can be processed per second, or a maximum of Y video frames (ie, XR frames) can be processed per second.
  • the terminal capability information may include the required XR service processing time after the UE is combined with the HMD after Uu port transmission.
  • the processing time after Uu port transmission is the length of time required for rendering, compositing, and decoding.
  • the processing time after Uu port transmission is the time length required for decoding.
  • the processing time after Uu port transmission is the sum of the time lengths required for rendering, compositing, Wi-Fi transmission, and decoding.
  • the network side may pre-store the terminal capability information reported by the UEs that have been connected in the history.
  • the 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.
  • the preset database can be stored in the AMF.
  • the UE reports the terminal capability information when initially accessing the network, and the network stores the terminal capability information in the preset database of the AMF.
  • the UE accesses the network again, it does not need to report its terminal capability information again, and the network side directly obtains the terminal capability information reported by the UE from the AMF.
  • the preset database may be the association relationship between the unique identifier of the UE and the terminal capability information.
  • step S101 a preset database is searched according to the unique identifier of the UE that is currently accessing the network and needs to perform the XR service, so as to obtain the associated terminal capability information.
  • the same UE is connected to different HMDs, or different transmission methods (such as Wi-Fi transmission or wired connection), may generate different terminal capability information.
  • the same UE in the preset database may be associated with multiple terminal capability information, respectively corresponding to scenarios of connecting to different HMDs or connecting to HMDs in different ways.
  • step S101 the corresponding terminal capability information is searched in a preset database according to the unique identifier of the UE that is currently accessing the network and needs to perform the XR service, and the unique identifier of the HMD that the UE is currently connected to.
  • step S101 when step S101 is performed, the corresponding terminal capability information is searched in a preset database according to the unique identifier of the UE that is currently accessing the network and needs to perform the XR service, and the specific connection method between the UE and the HMD.
  • the step S101 may include the step of: receiving the terminal capability information reported by the UE.
  • the UE For example, for a UE initially accessing the network, since the terminal capability information of the UE has not been stored in the AMF, the UE needs to report the terminal capability information to the network.
  • the terminal capability information may not be stored in the AMF, and the UE actively reports the terminal capability information every time it accesses the network.
  • the HMD can independently report its own capability information to the network side.
  • the SMF may receive the UE capability information reported by the UE and receive the HMD capability information reported by the HMD.
  • 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 a base station. That is, the UE reports the terminal capability information to the base station, and the base station reports it to one or more nodes of the core network step by step, and finally reports to the XR application server.
  • This example is a bottom-up escalation process.
  • the base station may report the terminal capability information reported by the UE to the AMF, the SMF, and the Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF for short).
  • Policy and Charging Rules Function Policy and Charging Rules Function
  • the network side may receive the terminal capability information reported by the UE from an XR application server. That is to say, the UE reports the terminal capability information to the XR application server, and the XR application server transfers it to the core network and the base station step by step.
  • This example is a top-down escalation process.
  • 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.
  • the base station may not know the terminal capability information of the terminal.
  • the core network node determines the QoS of the XR service, and the base station only needs to execute according to the QoS.
  • the SMF may further perform the step of: reporting the terminal capability information to the XR application server. So that the actual processing capability of the terminal is considered when the XR application server determines the QoS of the XR service of the terminal.
  • the XR application server can know the time required for the terminal to process the video frame, so as to determine an appropriate data transmission advance.
  • the data sending advance means that the XR application server needs to send the data packet of the XR frame x milliseconds (ms) before the display time of the XR frame in the HMD.
  • the data transmission advance may be the time required for the terminal side to process the XR frame.
  • the data sending advance may be that the XR application server is required to send the frame data xms before the display time when the HMD displays the XR frame.
  • the XR application server may not know the terminal capability information of the terminal. This is because the functions performed by the UE and the HMD are the same regardless of the type of terminal. For a specific function, whether it is processed on the UE side or on the HMD side, it can be insensitive to the XR application server.
  • the SMF may calculate the data transmission advance and report it to the XR application server.
  • the AMF or the SMF can calculate the data transmission advance and notify the XR application server of the required XR service processing time.
  • the core network node may determine the time margin left to the XR application server according to the XR service processing capability reported by the terminal. Specifically, the time length in the terminal capability information obtained in step S101 at this time may be the time required for rendering, synthesizing, and decoding.
  • the core network node can determine the time margin left for the XR application server in combination with the processing capability of the edge cloud and the XR service processing capability reported by the terminal. Specifically, the time length in the terminal capability information obtained in step S101 at this time may be the time required for decoding.
  • the core network node may determine the time margin left to the XR application server in combination with the XR service processing capability reported by the terminal. Specifically, the time length in the terminal capability information obtained in step S101 at this time may be the time required for decoding.
  • the step S102 may include the steps of: acquiring the 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 , and determine the latest time or the transmission delay at which the XR frame arrives at the UE.
  • the display moment of the XR frame in the HMD may be notified to the core network node by the XR application server through a session start (session start) process.
  • the SMF determines the time required for the terminal to process the data packet according to the acquired terminal capability information, and in combination with the display time of the XR frame in the HMD, it can be calculated when the XR frame needs to arrive at the terminal at the latest, that is, the The latest time at which the XR frame arrives at the UE.
  • the latest time may be understood as the latest time of Uu interface transmission.
  • the latest time when the XR frame arrives at the UE can be calculated.
  • the display moment of the XR frame in the HMD may be calculated by the network side by itself.
  • the network side may receive the total transmission delay and the sending time of the Nth XR frame before the XR frame from the XR application server. Then, the display time of the XR frame corresponding to the data in the HMD is determined according to the total transmission delay and the transmission time of the Nth XR frame before the XR frame.
  • the data may correspond to one or more XR frames, wherein the display moment of each XR frame in the HMD is determined according to the total transmission delay and the transmission moment of the Nth XR frame before the XR frame.
  • the information obtained from the XR application server may also include the XR frame interval, so as to calculate the transmission time and display time of each frame.
  • the QoS of the XR service can be accurately determined according to the XR service processing capability of the terminal, and especially the allocation of the transmission delay among the transmission nodes can be reasonably determined, thereby enhancing the XR. Transmission of business data.
  • the QoS of the XR service is determined according to the acquired terminal capability information. Further, accurate QoS can help to reasonably allocate the delay budget, so as to reasonably determine the allocation of the total transmission delay in each transmission node.
  • the data transmission method shown in FIG. 4 may be performed by an XR application server.
  • the XR application server may perform steps S101 to S103 shown in FIG. 4 to determine the transmission delay according to the acquired terminal capability information, and send the transmission delay to the SMF.
  • the terminal capability information can be directly obtained from the UE and the HMD.
  • the step S101 may include the step of: acquiring the terminal capability information from the SMF.
  • the display moment of the XR frame in the HMD may be calculated by the XR application server and notified to the network side.
  • the latest time at which the XR frame corresponding to the data arrives at the UE or the transmission delay may be determined by the XR application server and notified to the SMF.
  • the terminal capability information of the terminal may be reported to the XR application server directly or through the network side. Therefore, when the XR service starts, the XR application server can determine the latest time when the XR frame arrives at the UE or the XR frame according to the sending time of the XR frame, the total transmission delay, and the processing time of the XR frame in the UE and the HMD. The transmission delay is notified to the base station through the core network.
  • the network side may receive the latest time when the XR frame corresponding to the data arrives at the UE from the XR application server, and notify the base station.
  • FIG. 5 is a schematic structural diagram of a data transmission device according to the second embodiment of the present invention.
  • the data transmission apparatus 2 in this embodiment can be used to implement the method and technical solution described in the embodiment shown in FIG. 4 above.
  • the data transmission apparatus 2 in this embodiment may include: an acquisition module 21, configured to acquire terminal capability information, where the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD;
  • the determining module 22 is configured to determine the transmission delay according to the terminal capability information, wherein the transmission delay is used to indicate the maximum duration between the network equipment receiving the data and sending the data;
  • the sending module 23 is configured to use to send the transmission delay.
  • the above-mentioned data transmission apparatus 2 may correspond to a chip with a data transmission function in a network device, or a chip with a data processing function, such as a system-on-a-chip (System-On-a-Chip, SOC for short), A baseband chip, etc.; or a chip module including a chip with a data transmission function in a network device; or a chip module with a data processing function chip, or a network device.
  • a chip with a data transmission function in a network device or a chip with a data processing function, such as a system-on-a-chip (System-On-a-Chip, SOC for short), A baseband chip, etc.
  • a chip module including a chip with a data transmission function in a network device or a chip module with a data processing function chip, or a network device.
  • each module/unit included in each device and product described in the above embodiments it may be a software module/unit, a hardware module/unit, or a part of a software module/unit, a part of which is a software module/unit. is a hardware module/unit.
  • each module/unit included therein may be implemented by hardware such as circuits, or at least some of the modules/units may be implemented by a software program.
  • Running on the processor integrated inside the chip the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the chip module, the modules/units contained therein can be They are all implemented by hardware such as circuits, and different modules/units can be located in the same component of the chip module (such as chips, circuit modules, etc.) or in different components, or at least some of the modules/units can be implemented by software programs.
  • the software program runs on the processor integrated inside the chip module, and the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the terminal, each module contained in it
  • the units/units may all be implemented in hardware such as circuits, and different modules/units may be located in the same component (eg, chip, circuit module, etc.) or in different components in the terminal, or at least some of the modules/units may be implemented by software programs Realization, the software program runs on the processor integrated inside the terminal, and the remaining (if any) part of the modules/units can be implemented in hardware such as circuits.
  • FIG. 6 is a flowchart of a data transmission method according to the third embodiment of the present invention.
  • the embodiment of FIG. 6 may be applied to the network side, eg, performed by a network device on the network side.
  • the network equipment may include a base station.
  • the SMF in the above-mentioned embodiment shown in FIG. 4 is executed to send the transmission delay to the base station, and the base station executes this implementation to transmit the XR service data to the UE.
  • the transmission method provided by the following steps S201 to S202 may be executed by a chip with a data transmission function in the network device, or may be executed by a baseband chip in the network device.
  • the data transmission method described in this embodiment may include the following steps:
  • Step S201 obtaining a transmission delay, where the transmission delay is used to indicate the maximum time period between the network device receiving the data and sending the data, and the transmission delay is determined according to the terminal capability information, and the terminal Capability information is used to indicate the XR capabilities supported by the UE and/or HMD;
  • Step S202 the data is transmitted according to the transmission delay.
  • steps S201 to S202 can be regarded as execution steps corresponding to the steps S101 to S103 in the above-mentioned embodiment shown in FIG. 4 , and the two are complementary in specific implementation principles and logic. . Therefore, for the explanation of the terms involved in this embodiment, reference may be made to the related description of the embodiment shown in FIG. 4 , which will not be repeated here.
  • step S201 may include: receiving the transmission delay from the SMF.
  • step S201 may include: acquiring the terminal capability information and the display time of the XR frame corresponding to the data in the HMD; according to the terminal capability information and the XR frame in the HMD The display time in , determine the latest time or the transmission delay at which the XR frame arrives at the UE.
  • the base station can determine the time required for the terminal to process data packets according to the terminal capability information reported by the UE, and then calculate the latest time when the XR frame arrives at the UE according to the display time of the XR frame notified by the SMF in the HMD.
  • the base station may acquire the terminal capability information from the UE.
  • the base station may acquire the terminal capability information from the core network.
  • the base station may receive the total transmission delay and the transmission time of the Nth XR frame before the XR frame from the XR application server. Then, the display time of the XR frame corresponding to the data in the HMD is determined according to the total transmission delay and the transmission time of the Nth XR frame before the XR frame.
  • 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.
  • the base station transmits the data with the latest time when the XR frame corresponding to the data arrives at the UE as a constraint.
  • the base station will not transmit the data.
  • the base station After the base station receives the data, regardless of whether jitter occurs at the time of receiving the data, it can determine the latest time of data transmission on the air interface based on this embodiment, and then reasonably determine the subsequent execution logic. Further, after the base station knows the latest time when the XR frame arrives at the UE, even if the data received from the gateway is jittered, the base station can dynamically determine the "maximum allowable delay" for data transmission over the air interface.
  • FIG. 7 is a schematic structural diagram of a data transmission apparatus according to a fourth embodiment of the present invention.
  • the data transmission apparatus 3 in this embodiment can be used to implement the method and technical solution described in the embodiment shown in FIG. 6 above.
  • the data transmission apparatus 3 in this embodiment may include: an acquisition module 31, configured to acquire a transmission delay, wherein the transmission delay is used to instruct a network device to receive the data to send the data the maximum duration between data, and the transmission delay is determined according to the terminal capability information, the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; the transmission module 32 is configured to transmit according to the transmission delay the data.
  • the above-mentioned data transmission device 3 may correspond to a chip with a data transmission function in a network device, or a chip with a data processing function, such as a system-on-a-chip (System-On-a-Chip, SOC for short), A baseband chip, etc.; or a chip module including a chip with a data transmission function in a network device; or a chip module with a data processing function chip, or a network device.
  • a chip with a data transmission function in a network device or a chip with a data processing function, such as a system-on-a-chip (System-On-a-Chip, SOC for short), A baseband chip, etc.
  • a chip module including a chip with a data transmission function in a network device or a chip module with a data processing function chip, or a network device.
  • each module/unit included in each device and product described in the above embodiments it may be a software module/unit, a hardware module/unit, or a part of a software module/unit, a part of which is a software module/unit. is a hardware module/unit.
  • each module/unit included therein may be implemented by hardware such as circuits, or at least some of the modules/units may be implemented by a software program.
  • Running on the processor integrated inside the chip the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the chip module, the modules/units contained therein can be They are all implemented by hardware such as circuits, and different modules/units can be located in the same component of the chip module (such as chips, circuit modules, etc.) or in different components, or at least some of the modules/units can be implemented by software programs.
  • the software program runs on the processor integrated inside the chip module, and the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the terminal, each module contained in it
  • the units/units may all be implemented in hardware such as circuits, and different modules/units may be located in the same component (eg, chip, circuit module, etc.) or in different components in the terminal, or at least some of the modules/units may be implemented by software programs Realization, the software program runs on the processor integrated inside the terminal, and the remaining (if any) part of the modules/units can be implemented in hardware such as circuits.
  • FIG. 8 is a flowchart of a data transmission method according to a fifth embodiment of the present invention.
  • the embodiment of FIG. 8 may be applied to the user equipment side, eg, performed by the UE on the user equipment side.
  • the transmission method provided by the following steps S401 to S402 may be executed by a chip with a data transmission function in the user equipment, or may be executed by a baseband chip in the user equipment.
  • the data transmission method described in this embodiment may include the following steps:
  • Step S401 acquiring terminal capability information, wherein the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD;
  • Step S402 reporting terminal capability information.
  • steps S401 to S402 can be regarded as execution steps corresponding to the steps S101 to S103 in the above-mentioned embodiment shown in FIG. 4 , and the two are complementary in specific implementation principles and logic. . Therefore, for the explanation of the terms involved in this embodiment, reference may be made to the related description of the embodiment shown in FIG. 4 , which will not be repeated here.
  • the 5G UE may report the terminal capability information to the base station.
  • the 5G UE may directly report the terminal capability information to the SMF.
  • the application layer of the 5G UE may report the terminal capability information to the XR application server.
  • the terminal capability information may be reported to the XR application server by the HMD connected to the UE.
  • step S401 may include the steps of: acquiring capability information of the HMD; and generating the terminal capability information according to the capability information of the HMD and the capability information of the UE.
  • the UE may combine the capability information of the HMD to process data obtained by interacting with the HMD with the capability information of the UE itself to process data to generate capability information common to the UE and the HMD, that is, the terminal capability information.
  • the UE can directly obtain the capability information of the HMD from the HMD, or obtain the capability information of the HMD through other means.
  • the UE may acquire the capability information of the HMD from the network management center, the base station, other control network elements, or a manner predetermined by the protocol.
  • the action of acquiring the capability information of the HMD can be executed when the XR service is started, or can be executed after the HMD is powered on.
  • the data transmission method in this embodiment may further include the step of: receiving data, wherein the data is transmitted according to a transmission delay, and the transmission delay is used to indicate the network The maximum duration between the device receiving the data and sending the data, and the transmission delay is determined according to the terminal capability information.
  • the 5G UE actively reports the terminal capability information, so that the network side executes the solution of the embodiment shown in FIG. 4 or FIG. 6 to determine the appropriate transmission delay according to the terminal capability information, and then transmits the transmission according to the transmission delay. data.
  • the 5G UE can receive the data sent by the network within a reasonable transmission delay.
  • the UE can also act as a transmission node, so the delay budget allocated to the UE also needs to be considered.
  • the transmission method in this embodiment may further include the steps of: receiving data; receiving the latest time or transmission delay for transmitting the XR frame to the HMD reported by the HMD, wherein the The latest time or transmission delay for transmitting the XR frame to the HMD is determined according to the capability information of the HMD and the display time of the XR frame corresponding to the data in the HMD; The latest time or transmission delay for transmitting the XR frame is a constraint, and the data is transmitted.
  • the display moment of the XR frame in the HMD can be obtained through signaling.
  • the UE may obtain the display time of the XR frame in the HMD from the base station, or may obtain the display time of the XR frame in the HMD from the XR application server through the interaction between the application layer and the XR application server.
  • the UE can determine the latest time to transmit data through the Wi-Fi interface. If the UE fails to transmit the data of the XR frame through the Wi-Fi interface at the latest time, the UE does not need to transmit any more.
  • the latest time for transmitting the XR frame to the HMD may be determined by the HMD and then reported to the UE.
  • the transmission method in this embodiment may further include the steps of: receiving the latest time for transmitting the XR frame to the HMD reported by the HMD;
  • the latest time for transmitting the XR frame to the HMD is a constraint, and the data is transmitted.
  • the HMD may obtain the display moment of the XR frame in the HMD from the XR application server or the UE.
  • the HMD may report the latest time of transmitting the XR frame to the HMD to the UE at any time after the XR service is started.
  • the UE actively reports the data processing capabilities of the UE and the HMD to the network, so that the network side can determine the transmission delay budget.
  • FIG. 9 is a schematic structural diagram of a data transmission apparatus according to a sixth embodiment of the present invention. Those skilled in the art understand that the data transmission device 4 shown in FIG. 9 can be used to implement the method and technical solution described in the embodiment shown in FIG. 8 above.
  • the data transmission apparatus 4 in this embodiment may include: an acquisition module 41 configured to acquire terminal capability information, where the terminal capability information is used to indicate the XR capability supported by the UE and/or the HMD; reporting Module 42, configured to report terminal capability information.
  • the above-mentioned data transmission device 4 may correspond to a chip with a data transmission function in the user equipment, or to a chip with a data processing function, such as a system-on-a-chip (System-On-a-Chip, SOC for short), A baseband chip, etc.; or a chip module including a chip with a data transmission function in the user equipment; or a chip module with a data processing function chip, or a user equipment.
  • a chip with a data transmission function in the user equipment or to a chip with a data processing function, such as a system-on-a-chip (System-On-a-Chip, SOC for short), A baseband chip, etc.
  • a chip module including a chip with a data transmission function in the user equipment or a chip module with a data processing function chip, or a user equipment.
  • each module/unit included in each device and product described in the above embodiments it may be a software module/unit, a hardware module/unit, or a part of a software module/unit, a part of which is a software module/unit. is a hardware module/unit.
  • each module/unit included therein may be implemented by hardware such as circuits, or at least some of the modules/units may be implemented by a software program.
  • Running on the processor integrated inside the chip the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the chip module, the modules/units contained therein can be They are all implemented by hardware such as circuits, and different modules/units can be located in the same component of the chip module (such as chips, circuit modules, etc.) or in different components, or at least some of the modules/units can be implemented by software programs.
  • the software program runs on the processor integrated inside the chip module, and the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the terminal, each module contained in it
  • the units/units may all be implemented in hardware such as circuits, and different modules/units may be located in the same component (eg, chip, circuit module, etc.) or in different components in the terminal, or at least some of the modules/units may be implemented by software programs Realization, the software program runs on the processor integrated inside the terminal, and the remaining (if any) part of the modules/units can be implemented in hardware such as circuits.
  • the data generated by the XR application server 53 is transmitted to the terminal 51 via the network side 52 for display.
  • the terminal 51 includes an HMD511 and a UE512, and the UE512 executes the method described in FIG. 8;
  • the network side 52 includes a base station 521 and one or more nodes of the core network, such as AMF522, SMF523 and PCRF524, and one or more nodes of the network side 52
  • the SMF 523 may execute the method of the embodiment shown in FIG. 4 above
  • the base station 521 may execute the method of the embodiment shown in FIG. 6 above.
  • the data transmission process in this application scenario may include multiple stages. First, in phase 1, the terminal 51 may report its own terminal capability information. Then, in phase 2, the XR application server 53, the nodes on the network side 52, and the UE 512, as data transmission nodes, can determine the XR service delay allocation according to the terminal capability information reported by the terminal 51, and perform data transfer according to the allocated delay budget. transmission.
  • the UE 512 may perform operation s801 to report the terminal capability information of the terminal 51 to the base station 521 .
  • the terminal capability information of the terminal 51 may include the combination type of the UE 512 and the HMD 511 .
  • the UE 512 may report the terminal capability information through a radio resource control (Radio Resource Control, RRC for short) message.
  • RRC Radio Resource Control
  • the UE512 can also control a Protocol Data Unit (Protocol Data Unit, PDU for short), a Radio Link Control (Radio Link Control, RLC for short) PDU or a Media Access Control through a Packet Data Convergence Protocol (PDCP for short) Layer control element (Media Access Control-Control Element, referred to as MAC-CE) reporting, can also be reported through non-access stratum (Non-Access Stratum, referred to as NAS) signaling.
  • PDU Protocol Data Unit
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • MAC-CE Media Access Control-Control Element
  • NAS non-access stratum
  • the reported terminal capability information is transparently transmitted to the AMF 522 via the base station 521, and then the AMF 522 notifies the base station 521.
  • operation s802 may be continued to report the terminal capability information to one or more core network nodes via the base station 521 .
  • the base station 521 may report the terminal capability information of the terminal 51 to the AMF522, the AMF522 further reports the terminal capability information to the SMF523, and the SMF523 further reports the terminal capability information to the PCRF524.
  • reporting sequence among the core network nodes is only an example. In practical applications, the core network nodes that need to be reported and the reporting sequence among the nodes can be adjusted as required.
  • each core network node may use the information in phase 2 to determine the XR service delay allocation for the UE 512.
  • PCRF 524 can use this information to determine XR service charging for UE 512. This is considering that among the three terminal types, the amount of data transmitted by the terminal 51 of type 2 on the Uu port is larger than the amount of data transmitted by the terminal 51 of type 1 or type 3 on the Uu port when performing the same service, so the corresponding charging Functional modules require special consideration in the billing process.
  • the core network node (eg PCRF 524 ) may perform operation s803 to report the terminal capability information of the terminal 51 to the XR application server 53 .
  • the XR application server may consider the UE capability when determining the QoS of the XR service of the UE 512 in Phase 2.
  • each step in Phase 1 may be the same or different.
  • the message format can be adjusted according to the message specification of the interface, but the basic content of the transmission is the same.
  • the UE 512 can report to the network side 52 the type of data processed by the UE 512 and the HMD 511 and the required processing time, so that the network side 52 can determine the transmission delay budget.
  • the base station 521 may first complete clock synchronization with the UE 512 , the HMD 511 and the XR application server 53 .
  • the XR application server 53 performs operation s804 to notify the core network node (such as the SMF 523 ) "the display time of the XR frame in the HMD 511" through the session start (session start) process.
  • the specific content notified by the XR application server 53 to the SMF 523 through operation s804 may be that the display time of the first XR frame of the XR service in the HMD 511 is March 5, 2021 14:37:23:345ms, An XR frame is then displayed every 16ms.
  • the SMF 523 may perform operation s805 to notify the base station 521 of the new QoS parameters of the XR service: the moment when the Uu port transmits each XR frame, that is, the "display moment of the XR frame in the HMD 511".
  • the base station 521 may perform operation s806 to determine the latest time at which the Uu interface transmits each XR frame according to the type of the terminal 51 and the processing time of the data. For example, the base station 521 determines that it takes 15ms for the terminal 51 to process data according to the type of the terminal 51, and determines that the data packet contained in the first XR frame needs to be delivered before 14:37:23:330ms on March 5, 2021 The terminal 51 needs to send an XR frame to the terminal 51 every 16 ms thereafter.
  • the base station 521 when receiving the data packet corresponding to the XR frame, the base station 521 can determine the latest time when the data packet is transmitted on the air interface (ie, the Uu interface) regardless of whether the time of receiving the data packet is jittered.
  • the base station 521 determines the latest time for transmitting XR data packets over the air interface, and can determine a reasonable latest time for transmitting XR data packets on the premise that the base station 521 receives downlink data jitter.
  • the reporting of terminal capability information in phase 1 may also be performed top-to-bottom as shown in FIG. 11 .
  • the application layer of the UE 512 may perform operation s901 to report the terminal capability information combined with the HMD to the XR application server 53 .
  • operation s902 may be continued to notify one or more nodes of the network side 52 via the XR application server 53 of the terminal capability information reported by the UE 512 .
  • the XR application server 53 may notify the PCRF 524 of the terminal capability information, and then the PCRF 524 notifies the SMF 523 of the terminal capability information, and then the SMF 523 notifies the AMF 522 of the terminal capability information.
  • the core network node (eg, AMF 522 ) may perform operation s903 to notify the base station 521 of the terminal capability information reported by the UE 512 .
  • operation s901 may be replaced with operation s901', that is, the HMD 511 reports the terminal capability information of the terminal 51 to the XR application server 53.
  • the UE512 can report to the XR application server 53 the type of data processed by the UE512 and the HMD 511 and the required processing time, and then the XR application server 53 notifies the core network and the access network for the network side 52 to determine the transmission delay budget.
  • operation s806 in phase 2 shown in FIG. 10 may be performed by a core network node (eg, SMF 523 ), that is, operations s805 and s806 shown in FIG. 10 may be replaced by the operations shown in FIG. 12 s805 ′ and operation s806 ′, so that the SMF 523 determines the latest time for the Uu port to transmit each XR frame and notifies the base station 521 .
  • a core network node eg, SMF 523
  • operations s805 and s806 shown in FIG. 10 may be replaced by the operations shown in FIG. 12 s805 ′ and operation s806 ′, so that the SMF 523 determines the latest time for the Uu port to transmit each XR frame and notifies the base station 521 .
  • the SMF523 may perform operation s805' to determine the Uu port to transmit each XR according to the type of the terminal 51 and the processing time of the data The latest moment of the frame. For example, if the SMF523 determines that it takes 15ms for the terminal 51 to process the XR data packet according to the type of the terminal 51, it is determined that the data packet contained in the first XR frame needs to be sent before 14:37:23:330ms on March 5, 2021 After reaching the terminal 51, an XR frame needs to be sent to the terminal 51 every 16 ms.
  • the SMF 523 performs operation s806' to notify the base station 521 of the new QoS parameters of this XR service: the latest time for the Uu port to transmit each XR frame.
  • the UE 512 may perform operation s807 to acquire the data processing capability of the HMD 511 .
  • the acquired content may be "the processing time required for the XR frame in the HMD511 is xms".
  • the sequence of this action in the overall data transmission process is not necessarily the operation s807 described in this specific implementation. This action can also be performed after the HMD 511 is powered on, and there is no strict sequence relationship with other steps in this specific implementation.
  • the UE 512 may perform operation s808 to acquire the new XR service QoS parameter from the base station 521 through signaling: the display time of the XR frame in the HMD 511 .
  • the display time of the first XR frame of the XR service in the HMD511 is March 5, 2021 14:37:23:345ms.
  • the base station 521 obtains the new QoS parameters of this XR service by executing operation s805: the time when the Uu interface transmits each XR frame, and then notifies the UE 512 by executing operation s808.
  • the UE 512 may perform operation s809 to determine the latest time to transmit data through the Wi-Fi interface according to the processing capability of the HMD 511 . For example, assuming that the display time of the first XR frame of the XR service in the HMD511 is 14:37:23:345ms on March 5, 2021, and the processing time required by the HMD511 is 7ms, the UE512 can determine that the The latest time for the Wi-Fi interface to transmit the data corresponding to the XR frame is March 5, 2021 14:37:23:338ms. If the UE 512 has not been able to transmit the data of the XR frame through the Wi-Fi interface at this moment, no further transmission is required.
  • the UE 512 can determine the latest time to transmit the XR data packet on Wi-Fi, so as to avoid transmitting the XR data too late.
  • the source of the display moment of the XR frame obtained in operation s808 in the HMD 511 may also be the application layer.
  • the application layer of the UE 512 directly obtains this information from the XR application server 53 .
  • the above-mentioned action of determining the latest time for the Wi-Fi interface to transmit data for the terminal 51 of type 3 may also be performed by the HMD 511 . That is, operations s807 to s809 in FIG. 10 may be replaced with operations s807' to s809'.
  • the HMD 511 may perform operation s807' to obtain a new QoS parameter of the XR service from the XR application server 53: the display time of the XR frame in the HMD 511.
  • the acquired information may be "the display time of the first XR frame of the XR service in the HMD 511 is March 5, 2021 14:37:23:345ms".
  • the HMD511 may perform operation s808' to determine the latest time to receive data through the Wi-Fi interface according to its own processing capability. For example, assuming that the processing time required by HMD511 is 7ms, the latest time to receive the first frame of XR data through the Wi-Fi interface is 14:37:23:338ms on March 5, 2021, and then every An XR frame is transmitted every 16ms. That is, the latest time for the HMD511 to receive the second frame of XR data through the Wi-Fi interface is March 5, 2021 14:37:23:354ms.
  • the HMD 511 performs operation s809' to notify the UE 512 of the determined latest time to receive data through the Wi-Fi interface.
  • the display time of the XR frame in the HMD 511 may be obtained from the UE.
  • operation s806 in stage 2 shown in FIG. 10 may be performed by the XR application server 53, that is, operations s804 to s806 shown in FIG. 10 may be replaced with operations s1101 to s1101 shown in FIG. 13 . s1102, so that the XR application server 53 determines the latest time at which the XR frame is delivered to the UE 512.
  • the base station 521 can complete clock synchronization with the UE 512 , the HMD 511 and the XR application server 53 . Then in Phase 1, the UE 512 may perform operation s901 to report the terminal capability information of the terminal 51 to the XR application server 53 .
  • the terminal capability information includes the processing duration of the XR frame in the UE512 and the HMD511.
  • the XR application server 53 may perform operation s1101 to determine the XR frame according to the sending time of the XR frame, the end-to-end transmission delay of the application layer, and the processing time of the XR frame in the UE 512 and the HMD 511 when the XR service is started. The latest time when the frame is delivered to the UE 512 .
  • operation s1102 may be continued, and the XR application server 53 notifies the base station 521 of "the latest time when the XR frame is delivered to the UE 512" through the core network node (eg, the SMF 523) based on the session start process. 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, the end-to-end delay of the application layer is 40ms, and it is sent every 16ms thereafter An XR frame. Based on operation s901, the XR application server 53 determines that it takes 15 ms for the terminal 51 to process the data packet. Then, when the operation s1101 is performed, the XR application server 53 can determine that the data packet included in the first XR frame needs to be delivered to the terminal 51 before 14:37:23:330ms on March 5, 2021.
  • the core network node eg. the SMF 523
  • the base station 521 After the base station 521 obtains the latest time through operation s1102, even if the data packet received from the gateway is jittered, the base station 521 can dynamically determine the "maximum allowable delay" of the data packet transmission on the air interface.
  • the XR application server 53 determines the latest time for the base station 521 to transmit the XR data packet over the air interface and notifies the base station 521 to execute it. Therefore, on the premise that the base station 521 receives downlink data jitters, it is avoided to transmit XR data too late.
  • operation s806 in phase 2 shown in FIG. 10 may be performed by a core network node (eg, SMF 523 ), that is, operations s805 and s806 shown in FIG. 10 may be replaced by operations shown in FIG. 14 s1202 and operation s1203, so that the SMF 523 determines the latest time for the Uu port to transmit each XR frame and notifies the base station 521.
  • operation s804 in FIG. 12 can be further replaced with operation s1201 shown in FIG. 14 , that is, the content acquired by the SMF 523 from the XR application server 53 is different.
  • the base station 521 can complete clock synchronization with the UE 512 , the HMD 511 and the XR application server 53 . Then in stage 1, the SMF523 obtains the terminal capability information of the terminal 51 through operations s801 and s802, thereby determining the type of the combination of the UE512 and the HMD511 and the time length required for XR frame processing.
  • the XR application server 53 performs operation s1201 to notify the SMF 523 of "the end-to-end transmission delay of the application layer at the time of sending the XR frame" when the XR service is started.
  • the SMF523 may perform operation s1202 to determine that the XR frame is delivered to the UE512 according to "the sending time of the XR frame, the end-to-end transmission delay of the application layer” and “the combination type of the UE512 and the HMD511 and the time length required for the processing of the XR frame" the latest time.
  • the SMF 523 may perform operation s1203 to notify the base station 521 of the determined latest time.
  • the end-to-end delay of the application layer is 40ms, and it is sent every 16ms thereafter An XR frame.
  • the SMF 523 determines that it takes 15ms for the terminal 51 to process the data packet by performing operations s801 and s802. Then, when the SMF523 performs operation s1202, it can be determined that the data packet contained in the first XR frame needs to be delivered to the terminal 51 before 14:37:23:330ms on March 5, 2021.
  • the base station 521 After the base station 521 knows the latest time, even if the data packets received from the gateway are jittered, the base station 521 can dynamically determine the "maximum allowable delay" for the data packets to be transmitted on the air interface.
  • the SMF 523 determines the latest time at which the base station 521 transmits the XR data packet over the air interface and notifies the base station 521 to execute. Therefore, under the premise that the base station 521 receives downlink data jitters, it is possible to avoid transmitting XR data too late.
  • the actions performed by the SMF 523 in the above Phase 2 may also be performed by the AMF 522 .
  • the opposite end that the terminal 51 performs reporting of the terminal capability information in phase 1 may be one or more nodes of the core network, or may be the base station 521 , or It can be the XR application server 53 .
  • the terminal 51 may report the terminal capability information to the base station 521 .
  • the base station 521 and the nodes of the core network may perform operations s805 and s806 in FIG. 10 .
  • the terminal 51 may report the terminal capability information to the node of the core network (eg, the SMF 523 ).
  • the base station 521 and the nodes of the core network may perform operations s805' and s806' in FIG. 12 . Because the core network plays a linking role in the entire transmission process, it is more appropriate for the core network to calculate the latest time.
  • An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium is a non-volatile storage medium or a non-transitory storage medium, on which a computer program is stored, and the computer program is executed by a processor
  • the storage medium may include a computer-readable storage medium such as a non-volatile memory or a non-transitory memory.
  • the storage medium may include ROM, RAM, magnetic or optical disks, and the like.
  • An embodiment of the present invention further provides another data transmission device, including a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor executes the above-mentioned computer program when the processor runs the computer program.
  • FIG. 4 corresponds to the steps of the data transmission method provided by the embodiment.
  • the data transmission apparatus may be a network device, such as SMF in the network device.
  • the data transmission device may be an XR application server.
  • An embodiment of the present invention further provides another data transmission device, including a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor executes the above-mentioned computer program when the processor runs the computer program.
  • FIG. 6 corresponds to the steps of the data transmission method provided by the embodiment.
  • the data transmission apparatus may be a network device, such as a base station in the network device.
  • An embodiment of the present invention further provides another data transmission device, including a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor executes the above-mentioned computer program when the processor runs the computer program.
  • FIG. 8 corresponds to the steps of the data transmission method provided by the embodiment.
  • the data transmission apparatus may be user equipment.
  • the technical solution of the present invention can be applied to 5G (5 generation) communication systems, 4G and 3G communication systems, and various communication systems that will evolve later, such as 6G and 7G.
  • the technical solution of the present invention is also applicable to different network architectures, including but not limited to relay network architectures, dual-link architectures, and Vehicle-to-Everything (vehicle-to-anything communication) architectures.
  • the 5G CN described in the embodiments of this application may also be referred to as a new core network (new core), or 5G New Core, or a next generation core network (next generation core, NGC), or the like.
  • 5G-CN is set up independently of an existing core network, such as an evolved packet core (EPC).
  • EPC evolved packet core
  • a base station (base station, BS) in the embodiments of the present application which may also be referred to as base station equipment, is a device deployed in a wireless access network to provide a wireless communication function.
  • the devices that provide base station functions in 2G networks include base transceiver stations (BTS) and base station controllers (BSCs).
  • the devices that provide base station functions in 3G networks include Node B (NodeB) and wireless
  • the network controller radio network controller, RNC
  • the equipment that provides the base station function in the 4G network includes the evolved NodeB (evolved NodeB, eNB), in the wireless local area network (wireless local area network, WLAN), the device that provides the base station function
  • the equipment is an access point (AP)
  • the equipment that provides base station functions in 5G New Radio (NR) includes the continuously evolving Node B (gNB), and the equipment that provides base station functions in new communication systems in the future Wait.
  • the terminal in the embodiments of this application may refer to various forms of user equipment (user equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station (mobile station, MS), remote station, remote terminal, Mobile equipment, user terminal, terminal equipment, wireless communication equipment, user agent or user equipment.
  • user equipment user equipment
  • MS mobile station
  • remote station remote terminal
  • Mobile equipment user terminal
  • terminal equipment wireless communication equipment
  • user agent user equipment
  • the terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or future evolved Public Land Mobile Networks (PLMN)
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • a terminal device, etc. is not limited in this embodiment of the present application.
  • the embodiment of the present application defines the unidirectional communication link from the access network to the terminal as the downlink, the data transmitted on the downlink is the downlink data, and the transmission direction of the downlink data is called the downlink direction;
  • the unidirectional communication link is the uplink, the data transmitted on the uplink is the uplink data, and the transmission direction of the uplink data is called the uplink direction.
  • connection in the embodiments of the present application refers to various connection modes such as direct connection or indirect connection, so as to realize communication between devices, which is not limited in the embodiments of the present application.
  • Network and “system” appearing in the embodiments of this application express the same concept, and a communication system is a communication network.
  • the processor may be a central processing unit (central processing unit, CPU for short), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP for short) , application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory Fetch memory
  • direct memory bus random access memory direct rambus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs. 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 the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed method, apparatus and system may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included individually, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.
  • the above-mentioned integrated units implemented in the form of software functional units can be stored in a computer-readable storage medium.
  • the above-mentioned software functional unit is stored in a storage medium, and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute some steps of the methods described in the various embodiments of the present invention.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM for short), Random Access Memory (RAM for short), magnetic disk or CD, etc. that can store program codes medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种数据传输方法及装置、计算机可读存储介质，所述方法包括：获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；发送所述传输时延。通过本发明方案能够根据终端的XR业务处理能力精准确定XR业务的QoS，尤其合理确定传输时延在各传输节点的分配，从而增强XR业务数据的传输。

Description

数据传输方法及装置、计算机可读存储介质
本申请要求2021年4月27日提交中国专利局、申请号为202110462046.5、发明名称为“数据传输方法及装置、计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体地涉及一种数据传输方法及装置、计算机可读存储介质。
背景技术
扩展现实(Extended Reality，简称XR)技术即虚拟现实(Virtual Reality，简称VR)、增强现实(Augmented Reality，简称AR)与混合现实(Mixed Reality，简称MR)技术的合称，能够将物理环境与虚拟环境融合在一起，或提供完全身临其境般的虚拟体验环境，在第五代移动通信技术(The Fifth–Generation mobile communications，简称5G)时代具有广阔的应用前景。
基于XR技术传输的业务可以称为XR业务，现有的网络在针对XR业务配置服务质量(Quality of Service，简称QoS)时，仅考虑用户设备(User Equipment，简称UE)的接入层能力，因而容易导致针对XR业务配置的QoS不准确。不准确的QoS会增加数据的传输时延，影响数据传输及时性，进而影响用户体验。
发明内容
本发明解决的技术问题是如何准确确定XR业务的QoS，以增强XR业务的传输。
为解决上述技术问题，本发明实施例提供一种数据传输方法，包 括：获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；发送所述传输时延。
可选的，所述终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
可选的，所述获取终端能力信息，包括：接收UE上报的所述UE能力信息，以及接收HMD上报的所述HMD能力信息。
可选的，所述获取终端能力信息，包括：从基站获取所述终端能力信息；或者，从XR应用服务器获取所述终端能力信息。
可选的，所述获取终端能力信息，包括：从SMF获取所述终端能力信息。
可选的，所述数据传输方法还包括：向XR应用服务器上报所述终端能力信息；和/或，向XR应用服务器上报数据发送提前量，所述数据发送提前量是基于所述终端能力信息确定的。
可选的，所述终端能力信息包括以下至少一项：UE与HMD结合的类型；UE与HMD结合，所需的XR业务处理时间；UE与HMD结合，所需的XR业务处理能力；UE与HMD结合，在Uu口传输之后所需的XR业务处理时间。
可选的，所述根据所述终端能力信息，确定传输时延，包括：获取所述数据对应的XR帧在所述HMD中的显示时刻；根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻，确定所述XR帧到达所述UE的最晚时刻或所述传输时延。
可选的，所述获取所述数据对应的XR帧在所述HMD中的显示时刻，包括：从XR应用服务器接收总传输时延以及所述XR帧之前第N个XR帧的发送时刻，其中，所述总传输时延为自XR应用服 务器发出所述数据起，到所述数据到达所述UE的应用层的最大容许时延，N为自然数；根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻确定所述数据对应的XR帧在所述HMD中的显示时刻。
可选的，所述根据所述终端能力信息，确定传输时延，包括：从XR应用服务器接收所述数据对应的XR帧到达所述UE的最晚时刻或者所述传输时延，其中，所述XR帧到达所述UE的最晚时刻是根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻确定的。
可选的，所述数据传输方法还包括：XR业务启动时，与所述UE、HMD、基站以及XR应用服务器进行时钟同步。
为解决上述技术问题，本发明实施例还提供一种数据传输装置，包括：获取模块，用于获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；确定模块，用于根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；发送模块，用于发送所述传输时延。
为解决上述技术问题，本发明实施例还提供一种数据传输方法，包括：获取传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD支持的XR能力；根据所述传输时延传输所述数据。
可选的，所述获取传输时延，包括：自SMF接收所述传输时延。
可选的，所述获取传输时延，包括：获取所述终端能力信息，以及所述数据对应的XR帧在所述HMD中的显示时刻；根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻，确定所述XR帧到达所述UE的最晚时刻或所述传输时延。
可选的，所述获取所述数据对应的XR帧在所述HMD中的显示时刻，包括：从XR应用服务器接收总传输时延以及所述XR帧之前第N个XR帧的发送时刻，其中，所述总传输时延为XR应用服务器到UE之间的传输时延，N为自然数；根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻确定所述数据对应的XR帧在所述HMD中的显示时刻。
可选的，所述根据所述传输时延传输所述数据，包括：在接收到所述数据后，以所述XR帧到达所述UE的最晚时刻为约束，传输所述数据。
可选的，所述数据传输方法还包括：XR业务启动时，与所述UE、HMD、SMF以及XR应用服务器进行时钟同步。
可选的，所述终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
可选的，所述终端能力信息包括以下至少一项：UE与HMD结合的类型；UE与HMD结合，所需的XR业务处理时间；UE与HMD结合，所需的XR业务处理能力；UE与HMD结合，在Uu口传输之后所需的XR业务处理时间。
为解决上述技术问题，本发明实施例还提供一种数据传输装置，包括：获取模块，用于获取传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD支持的XR能力；传输模块，用于根据所述传输时延传输所述数据。
为解决上述技术问题，本发明实施例还提供一种数据传输方法，包括：获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；上报终端能力信息。
可选的，所述数据传输方法还包括：接收数据，其中，所述数据是根据传输时延进行传输的，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定。
可选的，所述获取终端能力信息，包括：获取所述HMD的能力信息；根据所述HMD的能力信息以及所述UE的能力信息，生成所述终端能力信息。
可选的，所述数据传输方法还包括：接收数据；获取所述数据对应的XR帧在所述HMD中的显示时刻；根据所述HMD的能力信息以及所述XR帧在所述HMD中的显示时刻，确定向所述HMD传输所述XR帧的最晚时刻或传输时延；以所述向所述HMD传输所述XR帧的最晚时刻或传输时延为约束，传输所述数据。
可选的，所述数据传输方法还包括：接收数据；接收所述HMD上报的向所述HMD传输所述XR帧的最晚时刻或传输时延，其中，所述向所述HMD传输所述XR帧的最晚时刻或传输时延根据所述HMD的能力信息以及所述数据对应的XR帧在所述HMD中的显示时刻确定；以所述向所述HMD传输所述XR帧的最晚时刻或传输时延为约束，传输所述数据。
可选的，所述上报终端能力信息包括：向基站、XR应用服务器或SMF上报所述终端能力信息。
可选的，所述终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
可选的，所述终端能力信息包括以下至少一项：UE与HMD结合的类型；UE与HMD结合，所需的XR业务处理时间；UE与HMD结合，所需的XR业务处理能力；UE与HMD结合，在Uu口传输之后所需的XR业务处理时间。
可选的，所述数据传输方法还包括：XR业务启动时，与基站、HMD、SMF以及XR应用服务器进行时钟同步。
为解决上述技术问题，本发明实施例还提供一种数据传输装置，包括：获取模块，用于获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；上报模块，用于上报终端能力信息。
为解决上述技术问题，本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述方法的步骤。
为解决上述技术问题，本发明实施例还提供一种数据传输装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述方法的步骤。
与现有技术相比，本发明实施例的技术方案具有以下有益效果：
在网络侧，如网络中的SMF侧，本发明实施例提供一种数据传输方法，包括：获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；发送所述传输时延。
采用本实施方案，能够根据终端的XR业务处理能力精准确定XR业务的QoS，尤其合理确定传输时延在各传输节点的分配，从而增强XR业务数据的传输。具体而言，根据获取的终端能力信息确定XR业务的QoS。进一步，准确的QoS能够利于合理分配时延预算，从而合理确定总传输时延在各个传输节点的分配情况。
在网络侧，如网络中的基站侧，本发明实施例还提供一种数据传输方法，包括：获取传输时延，其中，所述传输时延用于指示网络设 备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD支持的XR能力；根据所述传输时延传输所述数据。由此，对于传输节点而言，无论传输节点接收到数据的时刻是否发生的抖动，均可以基于接收到的传输时延确定数据在空口传输的最晚时刻，避免过晚传输数据。
在UE侧，本发明实施例还提供一种数据传输方法，包括：获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；上报终端能力信息。采用本实施方案，UE主动向网络上报终端能力信息，以便网络侧确定传输时延预算。
附图说明
图1是现有技术中第一种数据传输原理图；
图2是现有技术中第二种数据传输原理图；
图3是现有技术中XR业务涉及的UE和HMD的三种结合类型；
图4是本发明第一实施例一种数据传输方法的流程图；
图5是本发明第二实施例一种数据传输装置的结构示意图；
图6是本发明第三实施例一种数据传输方法的流程图；
图7是本发明第四实施例一种数据传输装置的结构示意图；
图8是本发明第五实施例一种数据传输方法的流程图；
图9是本发明第六实施例一种数据传输装置的结构示意图；
图10是本发明实施例一个典型应用场景的信令交互示意图；
图11是图10所示应用场景中阶段1的一个变化例的信令交互示意图；
图12是图10所示应用场景中阶段2的第一个变化例的信令交互 示意图；
图13是图10所示应用场景中阶段2的第二个变化例的信令交互示意图；
图14是图10所示应用场景中阶段2的第三个变化例的信令交互示意图。
具体实施方式
如背景技术所言，现有网络预先不知道终端处理XR业务数据的能力，也就无法确定XR业务的传输时延预算在各个传输节点的分配情况，无法准确确定QoS。
具体而言，XR业务所传输的视频数据(也称XR业务数据)从XR应用服务器(XR Application Server，简称XR APP Server)生成后，经过网络互连协议(Internet Protocol，简称IP)网络进入第三代合作伙伴计划(3rd Generation Partnership Project，简称3GPP)网络，经过核心网路由器、基站最终传至终端，由终端向用户进行显示。在整个传输过程中XR业务数据经过的网元如图1或图2所示。图1示出的是网络没有采用边缘云(edge cloud)时XR业务数据的传输流程。具体而言，IP网络接收到XR应用服务器发出的XR业务数据后，直接经用户面功能(User Plane Function，简称UPF)、基站(如gNB)传到UE。图2示出的是网络采用边缘云时XR业务数据的传输流程。具体而言，IP网络接收到XR应用服务器发出的XR业务数据后发送至UPF，XR业务数据经UPF后由边缘云做一些应用层的处理(如渲染、合成等)，经过边缘云处理后的XR业务数据再经过基站传到UE。
另一方面，现有网络传输业务数据流程中，由于UE的功能参数各不相同，3GPP协议定义了很多可选功能，如是否支持1024正交振幅调制(Quadrature Amplitude Modulation，简称QAM)、是否支持多连接等。相应的，UE接入网络后，基站可以根据UE能力为UE配置合适的无线参数。
目前3GPP确定XR涉及的终端有三种类型，其涉及的功能分布如图3所示。在本实施方案中，“终端”是指UE与头戴显示器(Head Mounted Display，简称HMD)的结合结果，其中UE为XR业务数据的接收端，通常为5G终端，如5G手机(5G phone)，HMD为XR业务数据的呈现端，如AR眼镜(AR glass)。
参考图3，对于类型1的终端，该类终端即是一个HMD，也即UE和HMD是集合在一起的。类型1的终端一体化地完成终端侧的所有功能，包括渲染、合成、解码等，以及最终向用户呈现视频和音频。也就是说，类型1的终端接收到网络经由用户网络界面通用(User to Network interface Universal，简称Uu)接口(简称Uu口)传输的XR业务数据后，在终端侧本地完成所有功能处理后在本地呈现XR帧(即XR业务的视频帧)。由于所有功能均在终端完成，所以类型1的终端比较笨重，佩戴不舒适。
继续参考图3，对于类型2的终端，也是UE与HMD集合在一起的。但与类型1的终端不同的是，类型2的终端完成的功能比较简单，即只有解码。而其它的XR业务数据处理则由边缘云完成，如渲染、合成等。也就是说，网络传输的XR业务数据经由边缘云完成部分功能处理后，再经由Uu口传输至类型2的终端，类型2的终端在本地完成剩余部分功能处理后在本地呈现视频帧。与类型1的终端相比，类型2的终端所承载的功能更少，所以更加轻薄，使用更加舒适。
继续参考图3，对于类型3的终端，UE和HMD在物理上分开，二者之间通过Wi-Fi传输数据。这样可以把大部分的数据处理功能放在UE侧，如渲染与合成，而HMD只负责解码。也就是说，5G手机接收到网络经由Uu口传输的XR业务数据后，在5G手机本地完成部分功能处理后，经由Wi-Fi传输给HMD，HMD在本地完成剩余部分功能处理后将该帧视频帧呈现给用户。这样，类型3的终端中的HMD与类型2的终端同样轻薄，使用舒适。
由图3可见，网络向终端传输XR业务数据时，留给Uu口传输 数据的时间窗的位置可能因终端类型的不同而有所区别。假设一个视频帧的全部下行时延预算(即应用层端到端传输时延)为30毫秒(ms)，对于不同类型的终端，网络进行时延分配的结果各不相同。
对于类型1的终端，HMD完成渲染、合成、解码等处理需要10ms，Uu口传输需要10ms。所以UPF必须提前10ms将视频帧的数据传至基站。
对于类型2的终端，HMD完成解码需要5ms，Uu口传输需要10ms。所以UPF必须提前15ms将视频帧的数据传至基站。
对于类型3的终端，HMD完成解码需要5ms，Wi-Fi传输需要1ms，UE完成渲染、合成需要3ms。所以UPF必须提前16ms将视频帧的数据传至基站。
如果网络预先不知道UE和HMD结合的类型，就无法确定业务时延在各个传输节点的分配，无法准确确定QoS。
根据现有协议的规定，UE与基站建立连接后，基站会向核心网中的接入和移动性管理功能(Access and Mobility Management Function，简称AMF)请求UE能力信息。如果UE是初次与网络建立连接，AMF没有存储UE能力信息，则基站会向UE请求该信息。UE上报自身能力信息后，基站据此为UE配置与其能力匹配的无线参数。随后，基站将UE的能力信息上传至AMF保存。此后，UE即使与基站断开连接，但是其能力信息仍然保留在AMF中。下一次UE与基站建立连接后，基站只需从AMF获取UE能力信息，无需再让UE上报。
现有技术中，业务建立时，基站获知业务的QoS信息，其中包含时延预算参数，其含义为“每个数据包在空口传输的最大可容许时延”。业务传输过程中，基站从UPF收到数据包的时刻开始计时，如果经过“最大可容许时延”还没有将该数据包传出，则放弃传输。也就是说，基站是以数据包到达自己的时刻作为“最大容许时延”的起始时 刻。
但是，现有协议规定UE上报的能力信息只涉及UE的接入层能力，不涉及UE的XR处理能力，所以不能解决XR业务的时延预算分配问题。
而XR业务的数据量较大，数据包比较密集。所以，数据包到达基站前，可能在IP网络内部或在UPF内部经历了排队拥塞，造成数据包到达基站的时刻产生抖动。
如果要实现“XR应用服务器到HMD”的确定时延，即固定的应用层端到端传输时延。对于基站来说，当接收了到达时刻有抖动的数据包时，每个数据包在空口的“最大容许时延”实际上是不同的。例如，对于到达基站迟到的数据包，其在空口的“最大容许时延”变小。又例如，对于到达基站较早的数据包，其在空口的“最大容许时延”则比较大。
但是，按现有的QoS架构，基站无法感知到达自己时发生抖动的数据包，也就无法实现弹性的“最大容许时延”。
另外，对于不同类型的终端，收到数据包后，在HMD显示之前，由于对数据包所做的处理不同，所需的处理时间也是不同的。如果确定“最大传输时延”之前不能确定UE所需的处理时间长度，也无法准确确定数据包的“最大传输时延”。
为解决上述技术问题，本发明实施例提供一种数据传输方法，包括：获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；发送所述传输时延。
采用本实施方案，能够根据终端的XR业务处理能力精准确定XR业务的QoS，尤其合理确定传输时延在各传输节点的分配，从而增强XR业务数据的传输。具体而言，根据获取的终端能力信息确定 XR业务的QoS。进一步，准确的QoS能够利于合理分配时延预算，从而合理确定总传输时延在各个传输节点的分配情况。
为使本发明的上述目的、特征和有益效果能够更为明显易懂，下面结合附图对本发明的具体实施例做详细的说明。
图4是本发明第一实施例一种数据传输方法的流程图。
本实施方案可以应用于XR场景，采用本实施方案传输的数据即为XR业务数据。在XR场景中，XR应用服务器生成的XR视频经由网络传输至终端并呈现，所述数据对应所述XR视频中的一个或多个XR帧。
本实施方案可以应用于网络侧，如由网络侧的网络设备执行。所述网络设备可以包括核心网中的节点，如核心网中的AMF或会话管理功能(Session Management Function，简称SMF)。
所述核心网中的一个或多个节点可以理解为数据从XR应用服务器传输到终端过程中需要经过的传输节点。
采用本实施方案能够在满足总传输时延的前提下，根据终端的XR数据处理能力合理分配这些传输节点的时延预算，避免数据过晚传输到终端。其中，总传输时延为自XR应用服务器发出所述XR业务数据起，到所述XR业务数据到达所述UE的应用层的最大容许时延，N为自然数。所述总传输时延也可称为应用层端到端传输时延，与业务特性有关，可以在XR业务启动时即确定并由XR应用服务器通知给核心网。核心网基于该总传输时延合理分配各传输节点的时延预算，以确保数据能够在应用层端到端传输时延内到达UE。
在具体实施中，下述步骤S101～步骤S103所提供的传输方法可以由网络设备中的具有数据传输功能的芯片执行，也可以由网络设备中的基带芯片执行。
具体地，参考图4，本实施例所述数据传输方法可以包括如下步骤：
步骤S101，获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
步骤S102，根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；
步骤S103，发送所述传输时延。
在一个具体实施中，终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
具体而言，终端能力信息可以包括UE与HMD结合的类型，如上述图3示出的三种类型，以及未来可能定义的其他扩展类型。如用有线连接代替类型3的终端中的Wi-Fi连接等。相应的，网络侧可以根据UE上报的类型来确定UE和HMD结合所需的XR业务处理时间。
进一步，终端能力信息可以包括UE与HMD结合，所需的XR业务处理时间。也即，UE可以直接上报自身与HMD结合所需的XR业务处理时间。例如，UE与HMD结合所需的XR业务处理时间可以为UE完成部分功能处理所需时间与HMD完成剩余部分功能处理所需时间之和，还可以包括UE与HMD之间传输数据所需时间。其中，UE和HMD各自需要完成的功能可以参考上述图3中的相关描述，在此不予赘述。
上述UE与HMD结合，所需的XR业务处理时间可以为平均时间、最大时间或者方差等。
进一步，终端能力信息可以包括UE与HMD结合，所需的XR业务处理能力。如每秒最多可处理X字节(Byte)的数据，又如每秒最多可处理Y个视频帧(即XR帧)。
进一步，终端能力信息可以包括UE与HMD结合，在Uu口传 输之后所需的XR业务处理时间。对于类型1的终端，Uu口传输之后的处理时间即为渲染、合成、解码所需的时间长度。对于类型2的终端，Uu口传输之后的处理时间即为解码所需的时间长度。对于类型3的终端，Uu口传输之后的处理时间即为渲染、合成、Wi-Fi传输以及解码所需的时间长度之和。
在一个具体实施中，网络侧可以预先存储有历史上连接过的UE上报的终端能力信息，相应的，所述步骤S101可以包括步骤：查找预设数据库，以获取所述UE关联的终端能力信息，其中，所述预设数据库记录有UE与终端能力信息的关联关系。
具体地，预设数据库可以存储于AMF。例如，UE在初始接入网络时上报终端能力信息，网络将该终端能力信息存储于AMF的预设数据库中。UE再次接入网络时无需再次上报其终端能力信息，网络侧直接从AMF中获取该UE上报的终端能力信息。
进一步，预设数据库中存储的可以是UE的唯一标识与终端能力信息的关联关系。在执行步骤S101时，根据当前接入网络且需要进行XR业务的UE的唯一标识查找预设数据库，以获取关联的终端能力信息。
在一个变化例中，以诸如类型3的终端这类分体式连接的UE和HMD为例，同一UE和不同的HMD连接，或者UE和HMD之间采用不同的传输方式(如Wi-Fi传输或有线连接)，可能生成不同的终端能力信息。
相应的，预设数据库中同一UE可以关联多个终端能力信息，分别对应连接不同HMD或采用不同方式连接HMD的场景。
在执行步骤S101时，根据当前接入网络且需要进行XR业务的UE的唯一标识，以及该UE当前连接的HMD的唯一标识，在预设数据库中查找对应的终端能力信息。
或者，在执行步骤S101时，根据当前接入网络且需要进行XR 业务的UE的唯一标识，以及UE与HMD的具体连接方式，在预设数据库中查找对应的终端能力信息。
在一个变化例中，所述步骤S101可以包括步骤：接收所述UE上报的所述终端能力信息。
例如，对于初始接入网络的UE，由于AMF中尚未存储该UE的终端能力信息，因而UE需要向网络上报终端能力信息。
又例如，终端能力信息可以不存储于AMF中，UE每次接入网络时均主动上报终端能力信息。
进一步，HMD可以独自向网络侧上报自身能力信息。相应的，在步骤S101中，SMF可以接收UE上报的所述UE能力信息，以及接收HMD上报的所述HMD能力信息。
进一步，网络侧接收所述UE上报的所述终端能力信息的具体流程可以包括：从基站接收所述UE上报的所述终端能力信息。也就是说，UE向基站上报终端能力信息，由基站逐级上报至核心网的一个或多个节点，最终上报至XR应用服务器。该示例为从下至上的上报流程。
例如，基站可以分别向AMF、SMF以及策略与计费规则功能单元(Policy and Charging Rules Function，简称PCRF)上报UE上报的终端能力信息。
或者，网络侧可以从XR应用服务器接收所述UE上报的所述终端能力信息。也就是说，UE将终端能力信息上报至XR应用服务器，由XR应用服务器逐级传递至核心网和基站。该示例为从上至下的上报流程。
例如，PCRF、SMF以及AMF等5G核心网节点可以从XR应用服务器侧获知终端能力信息，然后通知给基站。或者，基站也可以不知道终端的终端能力信息。相应的，建立XR业务时，由核心网节点确定XR业务的QoS，基站只需按QoS执行即可。
在一个具体实施中，在步骤S101之后，SMF还可以执行步骤：向XR应用服务器上报所述终端能力信息。以便XR应用服务器确定终端的XR业务的QoS时考虑终端的实际处理能力。
例如，根据终端能力信息，XR应用服务器可以获知终端处理视频帧所需时长，从而确定合适的数据发送提前量。其中，数据发送提前量是指，XR应用服务器需要在XR帧在HMD中的显示时刻之前x毫秒(ms)发出该XR帧的数据包。
进一步，数据发送提前量可以为，终端侧处理XR帧所需时长。或者，数据发送提前量可以为，要求XR应用服务器在HMD显示XR帧的显示时刻之前xms发出该帧数据。
或者，XR应用服务器也可以不知道终端的终端能力信息。这是因为无论哪一种类型的终端，UE与HMD完成的功能是相同的。对于某一项特定功能，无论放在UE侧处理，还是放在HMD侧处理，对XR应用服务器来说可以是无感的。
在一个变化例中，响应于步骤S101获取到终端能力信息，可以由SMF计算数据发送提前量后上报给XR应用服务器。
例如，根据终端能力信息中UE和HMD结合，所需的XR业务处理时间，AMF或者SMF可以计算得到数据发送提前量并通知给XR应用服务器。
对于类型1的终端，核心网节点(如AMF)可以根据终端上报的XR业务处理能力确定留给XR应用服务器的时间余量。具体而言，此时步骤S101获取的终端能力信息中的时间长度可以为渲染、合成以及解码所需时间。
对于类型2的终端，核心网节点可以结合边缘云的处理能力以及终端上报的XR业务处理能力确定留给XR应用服务器的时间余量。具体而言，此时步骤S101获取的终端能力信息中的时间长度可以为解码所需时间。
对于类型3的终端，核心网节点可以结合终端上报的XR业务处理能力确定留给XR应用服务器的时间余量。具体而言，此时步骤S101获取的终端能力信息中的时间长度可以为解码所需时间。
在一个具体实施中，所述步骤S102可以包括步骤：获取所述数据对应的XR帧在所述HMD中的显示时刻；根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻，确定所述XR帧到达所述UE的最晚时刻或所述传输时延。
具体地，XR帧在所述HMD中的显示时刻可以由XR应用服务器通过会话启动(session start)流程通知给核心网节点。
进一步，SMF根据获取的终端能力信息确定终端处理数据包所需时间，结合XR帧在所述HMD中的显示时刻，即可推算出该XR帧最晚需要在何时到达终端，也即所述XR帧到达所述UE的最晚时刻。所述最晚时刻可以理解为Uu口传输的最晚时刻。
进一步，根据传输时延和接收到所述XR帧的时刻，可以推算得到XR帧到达UE的最晚时刻。
在一个具体实施中，所述XR帧在所述HMD中的显示时刻可以是网络侧自行计算得到的。
具体而言，网络侧可以从XR应用服务器接收所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻。然后，根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻，确定所述数据对应的XR帧在所述HMD中的显示时刻。
其中，所述数据可以对应一个或多个XR帧，其中每一XR帧在HMD中的显示时刻根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻确定。
进一步，从XR应用服务器处获得的信息还可以包括XR帧间隔，以便推算每一帧的发送时刻和显示时刻。
由上，在网络侧，如网络中的SMF侧，采用本实施方案，能够根据终端的XR业务处理能力精准确定XR业务的QoS，尤其合理确定传输时延在各传输节点的分配，从而增强XR业务数据的传输。具体而言，根据获取的终端能力信息确定XR业务的QoS。进一步，准确的QoS能够利于合理分配时延预算，从而合理确定总传输时延在各个传输节点的分配情况。
在图4所示实施例的一个变化例中，图4所示数据传输方法可以由XR应用服务器执行。具体而言，XR应用服务器可以执行图4所示步骤S101至步骤S103，以根据获取的终端能力信息确定传输时延，并将传输时延发送至SMF。
进一步，终端能力信息可以直接获取自UE和HMD。或者，所述步骤S101可以包括步骤：从SMF获取所述终端能力信息。
进一步，XR帧在所述HMD中的显示时刻可以是由XR应用服务器计算得到后通知给网络侧的。相应的，所述数据对应的XR帧到达所述UE的最晚时刻或者所述传输时延可以由XR应用服务器确定后通知给SMF。
具体而言，终端的终端能力信息可以直接或通过网络侧上报至XR应用服务器。因此，XR应用服务器可以在XR业务启动时，根据XR帧的发出时刻、总传输时延，以及XR帧在UE和HMD中的处理时长，确定XR帧到达所述UE的最晚时刻或者所述传输时延并通过核心网通知基站。
相应的，网络侧可以从XR应用服务器接收所述数据对应的XR帧到达所述UE的最晚时刻，并通知基站。
图5是本发明第二实施例一种数据的输装置的结构示意图。本领域技术人员理解，本实施例所述数据传输装置2可以用于实施上述图4所述实施例中所述的方法技术方案。
具体地，参考图5，本实施例所述数据传输装置2可以包括：获 取模块21，用于获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；确定模块22，用于根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；发送模块23，用于发送所述传输时延。
关于所述数据传输装置2的工作原理、工作方式的更多内容，可以参照上述图4中的相关描述，这里不再赘述。
在具体实施中，上述的数据传输装置2可以对应于网络设备中具有数据传输功能的芯片，或者对应于具有数据处理功能的芯片，例如片上系统(System-On-a-Chip，简称SOC)、基带芯片等；或者对应于网络设备中包括具有数据传输功能芯片的芯片模组；或者对应于具有数据处理功能芯片的芯片模组，或者对应于网络设备。
在具体实施中，关于上述实施例中描述的各个装置、产品包含的各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。
例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可 以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
图6是本发明第三实施例一种数据传输方法的流程图。图6的实施方案可以应用于网络侧，如由网络侧的网络设备执行。所述网络设备可以包括基站。执行上述图4所示实施例的SMF发送传输时延至基站，基站执行本实施方案以将XR业务数据传输至UE。
在具体实施中，下述步骤S201～步骤S202所提供的传输方法可以由网络设备中的具有数据传输功能的芯片执行，也可以由网络设备中的基带芯片执行。
具体地，参考图6，本实施例所述数据传输方法可以包括如下步骤：
步骤S201，获取传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
步骤S202，根据所述传输时延传输所述数据。
本领域技术人员理解，所述步骤S201至步骤S202可以视为与上述图4所示实施例所述步骤S101至步骤S103相呼应的执行步骤，两者在具体的实现原理和逻辑上是相辅相成的。因而，本实施例中涉及名词的解释可以参考图4所示实施例的相关描述，这里不再赘述。
在一个具体实施中，步骤S201可以包括：自SMF接收所述传输时延。
在一个变化例中，步骤S201可以包括：获取所述终端能力信息，以及所述数据对应的XR帧在所述HMD中的显示时刻；根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻，确定所述XR帧到达所述UE的最晚时刻或所述传输时延。
例如，基站可以根据UE上报的终端能力信息确定终端处理数据包所需时间，进而根据SMF通知的XR帧在所述HMD中的显示时刻，推算出XR帧到达所述UE的最晚时刻。
进一步，基站可以从UE处获取所述终端能力信息。或者，基站可以从核心网处获取所述终端能力信息。
进一步，基站可以从XR应用服务器接收总传输时延以及所述XR帧之前第N个XR帧的发送时刻。然后，根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻确定所述数据对应的XR帧在所述HMD中的显示时刻。
在一个具体实施中，步骤S202可以包括：在接收到所述数据后，以所述XR帧到达所述UE的最晚时刻为约束，传输所述数据。
具体而言，作为传输节点，基站在接收到所述数据后，以所述数据对应的XR帧到达所述UE的最晚时刻为约束传输所述数据。
例如，如果在所述数据对应的所述XR帧到达所述UE的最晚时刻之后才接收到所述数据，则基站不再传输该数据。
由此，基站收到数据后，无论收到数据的时刻是否发生抖动，均可基于本实施方案确定数据在空口传输的最晚时刻进而合理确定后续执行逻辑。进一步，基站获知XR帧到达所述UE的最晚时刻后，从网关收到的数据即使发生抖动，基站也能动态确定数据在空口传输的“最大容许时延”。
图7是本发明第四实施例一种数据传输装置的结构示意图。本领域技术人员理解，本实施例所述数据传输装置3可以用于实施上述图6所述实施例中所述的方法技术方案。
具体地，参考图7，本实施例所述数据传输装置3可以包括：获取模块31，用于获取传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD 支持的XR能力；传输模块32，用于根据所述传输时延传输所述数据。
关于所述数据传输装置3的工作原理、工作方式的更多内容，可以参照上述图7中的相关描述，这里不再赘述。
在具体实施中，上述的数据传输装置3可以对应于网络设备中具有数据传输功能的芯片，或者对应于具有数据处理功能的芯片，例如片上系统(System-On-a-Chip，简称SOC)、基带芯片等；或者对应于网络设备中包括具有数据传输功能芯片的芯片模组；或者对应于具有数据处理功能芯片的芯片模组，或者对应于网络设备。
在具体实施中，关于上述实施例中描述的各个装置、产品包含的各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。
例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
图8是本发明第五实施例一种数据传输方法的流程图。图8的实施方案可以应用于用户设备侧，如由用户设备侧的UE执行。
在具体实施中，下述步骤S401～S402所提供的传输方法可以由用户设备中的具有数据传输功能的芯片执行，也可以由用户设备中的基带芯片执行。
具体地，参考图8，本实施例所述数据传输方法可以包括如下步骤：
步骤S401，获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
步骤S402，上报终端能力信息。
本领域技术人员理解，所述步骤S401至步骤S402可以视为与上述图4所示实施例所述步骤S101至步骤S103相呼应的执行步骤，两者在具体的实现原理和逻辑上是相辅相成的。因而，本实施例中涉及名词的解释可以参考图4所示实施例的相关描述，这里不再赘述。
在一个具体实施中，在步骤S401中，5G UE可以向基站上报所述终端能力信息。或者，5G UE可以直接向SMF上报所述终端能力信息。
在一个变化例中，在步骤S401中，5G UE的应用层可以向XR应用服务器上报所述终端能力信息。或者，可以由UE所连接的HMD向XR应用服务器上报所述终端能力信息。
在一个具体实施中，步骤S401可以包括步骤：获取所述HMD的能力信息；根据所述HMD的能力信息以及所述UE的能力信息，生成所述终端能力信息。
例如，UE可以将与HMD交互得到的HMD处理数据的能力信息与UE自身处理数据的能力信息相结合，以生成UE和HMD共同的能力信息，即所述终端能力信息。
进一步，UE可以从HMD处直接获得HMD的能力信息，或者通过其他途径获取HMD的能力信息。例如，UE可以从网管中心、 基站、其他控制网元或者协议预先规定的方式，获取HMD的能力信息。
进一步，获取HMD的能力信息的动作可以在XR业务启动时即执行，也可以在HMD通电后就执行。
在一个具体实施中，在步骤S402之后，本实施方案所述数据传输方法还可以包括步骤：接收数据，其中，所述数据是根据传输时延进行传输的，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定。
由此，本实施方案中，5G UE主动上报终端能力信息，使得网络侧执行上述图4或图6所示实施例的方案根据终端能力信息确定合适的传输时延，进而根据该传输时延传输数据。相应的，5G UE能够在合理的传输时延内接收到网络发送的数据。
在一个具体实施中，对于类型3的终端，也即所述HMD与所述UE为分体式连接时，UE也可以作为传输节点，因而也需要考虑分配给UE的时延预算。
相应的，在步骤S402之后，本实施例所述传输方法还可以包括步骤：接收数据；接收所述HMD上报的向所述HMD传输所述XR帧的最晚时刻或传输时延，其中，所述向所述HMD传输所述XR帧的最晚时刻或传输时延根据所述HMD的能力信息以及所述数据对应的XR帧在所述HMD中的显示时刻确定；以所述向所述HMD传输所述XR帧的最晚时刻或传输时延为约束，传输所述数据。
具体而言，XR帧在所述HMD中的显示时刻可以通过信令获知。UE可以从基站处获得XR帧在所述HMD中的显示时刻，或者，可以通过应用层与XR应用服务器的交互从XR应用服务器处获取XR帧在所述HMD中的显示时刻。
进一步，根据HMD的能力信息以及XR帧在所述HMD中的显示时刻，UE可以确定通过Wi-Fi接口传输数据的最晚时刻。如果在 该最晚时刻UE还未能通过Wi-Fi接口传输该XR帧的数据，则UE无需再传输。
在一个变化例中，向所述HMD传输所述XR帧的最晚时刻可以由HMD确定后上报给UE。
具体而言，在步骤S402之后，本实施例所述传输方法还可以包括步骤：接收所述HMD上报的向所述HMD传输所述XR帧的最晚时刻；在接收到所述数据时，以所述向所述HMD传输所述XR帧的最晚时刻为约束，传输所述数据。
进一步，HMD可以从XR应用服务器或者UE处获取XR帧在所述HMD中的显示时刻。
在实际应用中，HMD可以在XR业务启动后的任意时刻向UE上报向所述HMD传输所述XR帧的最晚时刻。
由上，在UE侧，采用本实施方案，UE主动向网络上报UE和HMD处理数据的能力，以便网络侧确定传输时延预算。
图9是本发明第六实施例一种数据传输装置的结构示意图。本领域技术人员理解，图9所述数据传输装置4可以用于实施上述图8所述实施例中所述的方法技术方案。
具体地，参考图9，本实施例所述数据传输装置4可以包括：获取模块41用于获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；上报模块42，用于上报终端能力信息。
关于所述数据传输装置4的工作原理、工作方式的更多内容，可以参照上述图8中的相关描述，这里不再赘述。
在具体实施中，上述的数据传输装置4可以对应于用户设备中具有数据传输功能的芯片，或者对应于具有数据处理功能的芯片，例如片上系统(System-On-a-Chip，简称SOC)、基带芯片等；或者对应 于用户设备中包括具有数据传输功能芯片的芯片模组；或者对应于具有数据处理功能芯片的芯片模组，或者对应于用户设备。
在具体实施中，关于上述实施例中描述的各个装置、产品包含的各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。
例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
在一个典型的应用场景中，参考图10，XR应用服务器53产生的数据经由网络侧52传输至终端51进行显示。其中，终端51包括HMD511和UE512，UE512执行上述图8所述方法；网络侧52包括基站521和核心网的一个或多个节点，如AMF522、SMF523和PCRF524，网络侧52的一个或多个节点如SMF523可以执行上述图4所述实施例的方法，基站521可以执行上述图6所示实施例的方法。
本应用场景中数据的传输流程可以包括多个阶段。首先，在阶段1，终端51可以上报自身的终端能力信息。然后，在阶段2，XR应 用服务器53、网络侧52的节点以及UE512作为数据的传输节点，可以根据终端51上报的终端能力信息确定XR业务时延分配，并按分配的时延预算进行数据的传输。
接下来针对各阶段的具体实现流程进行详细阐述。
继续参考图10，在阶段1，UE512可以执行操作s801，以向基站521上报终端51的终端能力信息。例如，终端51的终端能力信息可以包括UE512与HMD511的结合类型。
例如，UE512可以通过无线资源控制(Radio Resource Control，简称RRC)消息上报所述终端能力信息。又例如，UE512也可以通过分组数据汇聚协议(Packet Data Convergence Protocol，简称PDCP)控制协议数据单元(Protocol Data Unit，简称PDU)、无线链路控制(Radio Link Control，简称RLC)PDU或者媒体访问控制层控制单元(Media Access Control-Control Element，简称MAC-CE)上报，还可以通过非接入层(Non-Access Stratum，简称NAS)信令上报。
通过NAS信令上报终端能力信息时，由于基站521不能直接读取NAS信令，所以上报的终端能力信息经由基站521透传至AMF522，再由AMF522通知基站521。
进一步，可以继续执行操作s802，以经由基站521向一个或多个核心网节点上报所述终端能力信息。例如，基站521可以向AMF522上报终端51的终端能力信息，AMF522将该终端能力信息进一步上报至SMF523，SMF523将该终端能力信息进一步上报至PCRF524。
需要指出的是，上述各核心网节点之间的上报顺序仅是一个示例，在实际应用中，可以根据需要调节需要上报的核心网节点，以及各节点之间的上报顺序。
响应于接收到终端51的终端能力信息，各个核心网节点在阶段2可以使用该信息确定UE512的XR业务时延分配。
PCRF524可以利用该信息确定UE512的XR业务计费。这是考 虑到三种终端类型中，进行同样业务时类型2的终端51在Uu口传输的数据量比类型1或类型3的终端51在Uu口传输的数据量更大，因此相应的计费功能模块在计费过程中需要进行特别考虑。
进一步，核心网节点(如PCRF524)可以执行操作s803，以向XR应用服务器53上报终端51的终端能力信息。相应的，XR应用服务器在阶段2中确定UE512的XR业务QoS时，可以考虑UE能力。
值得注意的是，阶段1中各个步骤所传输的具体消息格式可以相同，也可以不同。每一个节点向下一节点传输消息时，可以根据接口的消息规范对消息格式进行调整，但传输的基本内容相同。
由上，通过执行阶段1所述流程，UE512可以向网络侧52上报UE512和HMD511处理数据的类型以及所需处理时长，供网络侧52确定传输时延预算。
继续参考图10，在阶段2，基站521首先可以与UE512、HMD511和XR应用服务器53完成时钟同步。
然后，XR应用服务器53在XR业务启动时，执行操作s804，以通过会话开始(session start)流程通知核心网节点(如SMF523)“XR帧在HMD511中的显示时刻”。例如，XR应用服务器53通过操作s804通知给SMF523的具体内容可以为，XR业务的第一个XR帧在HMD511中的显示时刻为2021年3月5日14时：37分：23秒：345ms，其后每隔16ms显示一个XR帧。
进一步，SMF523可以执行操作s805，以通知基站521本次XR业务的QoS新参数：Uu口传输每个XR帧的时刻，也即“XR帧在HMD511中的显示时刻”。
进一步，基站521可以执行操作s806，以根据终端51的类型及数据的处理时间，确定Uu口传输每个XR帧的最晚时刻。例如，基站521根据终端51的类型确定终端51处理数据需要15ms，则确定 第一个XR帧所包含的数据包需要在2021年3月5日14时：37分：23秒：330ms之前送达终端51，之后每隔16ms需要将一个XR帧送达终端51。
基于此，基站521接收到XR帧所对应的数据包时，无论收到数据包的时刻是否发生抖动，均可以确定数据包在空口(即Uu口)传输的最晚时刻。
由上，在阶段2，由基站521确定空口传输XR数据包的最晚时刻，可以在基站521接收下行数据发生抖动的前提下，确定合理的XR数据包传输最晚时刻。
在一个变化例中，与上述图10所示阶段1由下至上的终端能力信息上报流程不同，阶段1中终端能力信息的上报也可以是如图11所示由上至下地进行的。
具体地，参考图11，UE512的应用层可以执行操作s901，以向XR应用服务器53上报自身和HMD结合的终端能力信息。
进一步，可以继续执行操作s902，以经由XR应用服务器53向网络侧52的一个或多个节点通知UE512上报的终端能力信息。例如，XR应用服务器53可以将终端能力信息通知给PCRF524，然后由PCRF524将终端能力信息通知给SMF523，然后由SMF523通知给AMF522。
进一步，核心网节点(如AMF522)可以执行操作s903，以向基站521通知UE512上报的终端能力信息。
或者，操作s901可以替换为操作s901’，也即，由HMD511向XR应用服务器53上报终端51的终端能力信息。
由上，UE512可以向XR应用服务器53上报UE512和HMD511处理数据的类型以及所需处理时长，再由XR应用服务器53通知核心网及接入网，供网络侧52确定传输时延预算。
在一个变化例中，图10所示阶段2中操作s806的动作可以由核心网节点(如SMF523)执行，也即，图10示出的操作s805和操作s806可以替换为图12示出的操作s805’和操作s806’，从而由SMF523确定Uu口传输每个XR帧的最晚时刻并通知基站521。
具体地，参考图12，在基于操作s804获取“XR帧在HMD511中的显示时刻”后，SMF523可以执行操作s805’，以根据终端51的类型及数据的处理时间，确定Uu口传输每个XR帧的最晚时刻。例如，SMF523根据终端51的类型确定终端51处理XR数据包需要15ms，则确定第一个XR帧所包含的数据包需要在2021年3月5日14时:37分:23秒:330ms之前送达终端51，之后每隔16ms需要将一个XR帧送达终端51。
进一步，SMF523执行操作s806’，以通知基站521本次XR业务的QoS新参数：所述Uu口传输每个XR帧的最晚时刻。
在一个变化例中，对于类型3的终端51，由于HMD511和UE512是分体式连接的，两者之间需要时间传输数据。因此，阶段2在执行操作s806后，还可以进一步执行后续动作以确定数据在Wi-Fi传输的最晚传输时刻。
具体地，继续参考图10，UE512可以执行操作s807，以获取HMD511的数据处理能力。例如，获取的内容可以为“XR帧在HMD511中需要的处理时间是xms”。该动作在整体数据传输流程中的顺序不一定是本具体实施所述的操作s807，该动作也可以在HMD511通电之后就进行，与本具体实施中其它步骤之间不存在严格的顺序关系。
进一步，UE512可以执行操作s808，以通过信令从基站521处获知XR业务QoS新参数：XR帧在HMD511中的显示时刻。例如，XR业务的第一个XR帧在HMD511中的显示时刻为2021年3月5日14时:37分:23秒:345ms。
相应的，在本变化例中，基站521通过执行操作s805获取本次XR业务的QoS新参数：Uu口传输每个XR帧的时刻，然后通过执行操作s808通知给UE512。
进一步，UE512可以执行操作s809，以根据HMD511的处理能力确定通过Wi-Fi接口传输数据的最晚时刻。例如，假设XR业务的第一个XR帧在HMD511中的显示时刻为2021年3月5日14时：37分：23秒：345ms，而HMD511需要的处理时间长度为7ms，则UE512可以确定通过Wi-Fi接口传输该XR帧对应数据的最晚时刻为2021年3月5日14时:37分:23秒:338ms。如果在这一时刻UE512还未能通过Wi-Fi接口传输XR帧的数据，则无需再传输。
由上，对于类型3的终端，UE512可以确定在Wi-Fi传输XR数据包的最晚时刻，避免过晚传输XR数据。
在一个变化例中，操作s808所获取的XR帧在HMD511中的显示时刻的来源也可以是应用层。如UE512的应用层直接从XR应用服务器53处获取该信息。
在一个变化例中，上述针对类型3的终端51确定Wi-Fi接口传输数据的最晚时刻的动作，也可以由HMD511执行。也就是说，图10中操作s807至操作s809可以替代为操作s807’至操作s809’。
具体而言，HMD511可以执行操作s807’，以从XR应用服务器53获取本次XR业务QoS新参数：XR帧在HMD511中的显示时刻。例如，获取的信息可以为“XR业务的第一个XR帧在HMD511中的显示时刻为2021年3月5日14时：37分：23秒：345ms”。
进一步，HMD511可以执行操作s808’，以根据自身的处理能力确定通过Wi-Fi接口接收数据的最晚时刻。例如，假设HMD511需要的处理时间长度为7ms，则确定通过Wi-Fi接口接收XR数据第一个帧的最晚时刻为2021年3月5日14时：37分：23秒：338ms，之后每隔16ms传输一个XR帧。也即，HMD511通过Wi-Fi接口接收XR 数据第二个帧的最晚时刻为2021年3月5日14时：37分：23秒：354ms。
进一步，HMD511执行操作s809’，以将确定的通过Wi-Fi接口接收数据的最晚时刻通知给UE512。
在一个变化例中，HMD511执行操作s807’时可以从UE处获取XR帧在HMD511中的显示时刻。
在一个变化例中，图10所示阶段2中操作s806的动作可以由XR应用服务器53执行，也即，图10示出的操作s804至操作s806可以替换为图13示出的操作s1101至操作s1102，从而由XR应用服务器53确定XR帧送达UE512的最晚时刻。
首先，基站521可以与UE512、HMD511和XR应用服务器53完成时钟同步。然后在阶段1中，UE512可以执行操作s901，以向XR应用服务器53上报终端51的终端能力信息。所述终端能力信息包括XR帧在UE512和HMD511中的处理时长。
然后，参考图13，XR应用服务器53可以执行操作s1101，以在XR业务启动时根据XR帧的发出时刻、应用层端到端传输时延以及XR帧在UE512和HMD511中的处理时长，确定XR帧的最晚送达UE512的时刻。
进一步，可以继续执行操作s1102，XR应用服务器53基于会话开始流程，通过核心网节点(如SMF523)通知基站521“XR帧最晚送达UE512的时刻”。例如，假设XR业务的第一个XR帧于2021年3月5日14时：37分：23秒：305ms从XR应用服务器53发出，应用层端到端时延为40ms，其后每16ms发送一个XR帧。基于操作s901，XR应用服务器53确定终端51处理数据包需要15ms。则执行操作s1101时XR应用服务器53可以确定：第一个XR帧所包含的数据包需要在2021年3月5日14时：37分：23秒：330ms之前送达终端51。
基站521通过操作s1102获知该最晚时刻后，从网关收到的数据包即使发生抖动，基站521也能动态确定数据包在空口传输的“最大容许时延”。
由此，本变化例由XR应用服务器53确定基站521在空口传输XR数据包的最晚时刻并通知基站521执行。从而在基站521接收下行数据发生抖动的前提下避免过晚传输XR数据。
在一个变化例中，图10所示阶段2中操作s806的动作可以由核心网节点(如SMF523)执行，也即，图10示出的操作s805和操作s806可以替换为图14示出的操作s1202和操作s1203，从而由SMF523确定Uu口传输每个XR帧的最晚时刻并通知基站521。并且，与上述图12所示变化例的区别在于，图12中操作s804可以进一步替换为图14所示操作s1201，也即SMF523从XR应用服务器53获取的内容不同。
首先，基站521可以与UE512、HMD511和XR应用服务器53完成时钟同步。然后在阶段1中，SMF523通过操作s801和操作s802获取终端51的终端能力信息，从而确定UE512和HMD511结合的类型及XR帧处理所需时间长度。
然后，在阶段2中，XR应用服务器53执行操作s1201，以在XR业务启动时向SMF523通知“XR帧的发出时刻应用层端到端传输时延”。
进一步，SMF523可以执行操作s1202，以根据“XR帧的发出时刻，应用层端到端传输时延”以及“UE512和HMD511结合的类型及XR帧处理所需时间长度”，确定XR帧送达UE512的最晚时刻。
然后，SMF523可以执行操作s1203，以将确定的最晚时刻通知基站521。
例如，假设XR业务的第一个XR帧于2021年3月5日14时：37分：23秒：305ms从XR应用服务器53发出，应用层端到端时延 为40ms，其后每16ms发出一个XR帧。SMF523通过执行操作s801和操作s802确定终端51处理数据包需要15ms。则SMF523执行操作s1202时可以确定：第一个XR帧所包含的数据包需要在2021年3月5日14时：37分：23秒：330ms之前送达终端51。
基站521获知该最晚时刻后，从网关收到的数据包即使发生抖动，基站521也能动态确定数据包在空口传输的“最大容许时延”。
由上，在本变化例中，由SMF523确定基站521在空口传输XR数据包的最晚时刻并通知基站521执行。从而可以在基站521接收下行数据发生抖动的前提下，避免过晚传输XR数据。
在一个共同变化例中，上述阶段2中由SMF523执行的动作，也可以由AMF522执行。
在上述图10至图14示出的应用场景及其变化例中，终端51在阶段1中执行上报终端能力信息的对端可以为核心网的一个或多个节点，也可以为基站521，还可以为XR应用服务器53。
当传输的是对时延要求较宽松的XR业务的数据时，终端51可以向基站521上报终端能力信息。相应的，基站521和核心网的节点可以执行图10中操作s805和操作s806。通过基站521自己调节时延预算、计算最晚时刻，能够在接入层完成XR数据的处理，对上层影响小。
当传输的是对时延要求较严格的XR业务的数据时，终端51可以向核心网的节点(如SMF523)上报终端能力信息。相应的，基站521和核心网的节点可以执行图12中操作s805’和操作s806’。因为核心网在整个传输流程中起到承上启下的作用，因而由核心网计算最晚时刻更为合适。
本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述任一实施例提供的 数据的传输方法的步骤。优选地，所述存储介质可以包括诸如非挥发性(non-volatile)存储器或者非瞬态(non-transitory)存储器等计算机可读存储介质。所述存储介质可以包括ROM、RAM、磁盘或光盘等。
本发明实施例还提供了另一种数据传输装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述图4对应实施例所提供的数据传输方法的步骤。例如，所述数据传输装置可以为网络设备，如网络设备中的SMF。又例如，所述数据传输装置可以为XR应用服务器。
本发明实施例还提供了另一种数据传输装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述图6对应实施例所提供的数据传输方法的步骤。例如，所述数据传输装置可以为网络设备，如网络设备中的基站。
本发明实施例还提供了另一种数据传输装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述图8对应实施例所提供的数据传输方法的步骤。例如，所述数据传输装置可以为用户设备。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指示相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：ROM、RAM、磁盘或光盘等。
本方明技术方案可适用于5G(5 generation)通信系统，还可适用于4G、3G通信系统，还可适用于后续演进的各种通信系统，例如6G、7G等。
本方明技术方案也适用于不同的网络架构，包括但不限于中继网络架构、双链接架构，Vehicle-to-Everything(车辆到任何物体的通信) 架构。
本申请实施例中所述的5G CN也可以称为新型核心网(new core)、或者5G New Core、或者下一代核心网(next generation core，NGC)等。5G-CN独立于现有的核心网，例如演进型分组核心网(evolved packet core，EPC)而设置。
本申请实施例中的基站(base station，BS)，也可称为基站设备，是一种部署在无线接入网用以提供无线通信功能的装置。例如在2G网络中提供基站功能的设备包括基地无线收发站(base transceiver station,BTS)和基站控制器(base station controller，BSC)，3G网络中提供基站功能的设备包括节点B(NodeB)和无线网络控制器(radio network controller，RNC)，在4G网络中提供基站功能的设备包括演进的节点B(evolved NodeB，eNB)，在无线局域网络(wireless local area networks，WLAN)中，提供基站功能的设备为接入点(access point，AP)，5G新无线(New Radio，NR)中的提供基站功能的设备包括继续演进的节点B(gNB),以及未来新的通信系统中提供基站功能的设备等。
本申请实施例中的终端可以指各种形式的用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、远方站、远程终端、移动设备、用户终端、终端设备(terminal equipment)、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例定义接入网到终端的单向通信链路为下行链路，在 下行链路上传输的数据为下行数据，下行数据的传输方向称为下行方向；而终端到接入网的单向通信链路为上行链路，在上行链路上传输的数据为上行数据，上行数据的传输方向称为上行方向。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，表示前后关联对象是一种“或”的关系。
本申请实施例中出现的“多个”是指两个或两个以上。
本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。
本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。本申请实施例中出现的“网络”与“系统”表达的是同一概念，通信系统即为通信网络。
应理解，本申请实施例中，所述处理器可以为中央处理单元(central processing unit，简称CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，简称DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically  EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在本申请所提供的几个实施例中，应该理解到，所揭露的方法、装置和系统，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
虽然本发明披露如上，但本发明并非限定于此。任何本领域技术人员，在不脱离本发明的精神和范围内，均可作各种更动与修改，因此本发明的保护范围应当以权利要求所限定的范围为准。

Claims (33)

  1. 一种数据传输方法，其特征在于，包括：
    获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
    根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；
    发送所述传输时延。
  2. 根据权利要求1所述的数据传输方法，其特征在于，所述终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
  3. 根据权利要求2所述的数据传输方法，其特征在于，所述获取终端能力信息，包括：
    接收UE上报的所述UE能力信息，以及接收HMD上报的所述HMD能力信息。
  4. 根据权利要求1所述的数据传输方法，其特征在于，所述获取终端能力信息，包括：
    从基站获取所述终端能力信息；或者
    从XR应用服务器获取所述终端能力信息。
  5. 根据权利要求1所述的数据传输方法，其特征在于，所述获取终端能力信息，包括：
    从SMF获取所述终端能力信息。
  6. 根据权利要求1所述的数据传输方法，其特征在于，还包括：
    向XR应用服务器上报所述终端能力信息；和/或，
    向XR应用服务器上报数据发送提前量，所述数据发送提前量是基于所述终端能力信息确定的。
  7. 根据权利要求1所述的数据传输方法，其特征在于，所述终端能力信息包括以下至少一项：
    UE与HMD结合的类型；
    UE与HMD结合，所需的XR业务处理时间；
    UE与HMD结合，所需的XR业务处理能力；
    UE与HMD结合，在Uu口传输之后所需的XR业务处理时间。
  8. 根据权利要求1所述的数据传输方法，其特征在于，所述根据所述终端能力信息，确定传输时延，包括：
    获取所述数据对应的XR帧在所述HMD中的显示时刻；
    根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻，确定所述XR帧到达所述UE的最晚时刻或所述传输时延。
  9. 根据权利要求8所述的数据传输方法，其特征在于，所述获取所述数据对应的XR帧在所述HMD中的显示时刻，包括：
    从XR应用服务器接收总传输时延以及所述XR帧之前第N个XR帧的发送时刻，其中，所述总传输时延为自XR应用服务器发出所述数据起，到所述数据到达所述UE的应用层的最大容许时延，N为自然数；
    根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻确定所述数据对应的XR帧在所述HMD中的显示时刻。
  10. 根据权利要求1所述的数据传输方法，其特征在于，所述根据所述终端能力信息，确定传输时延，包括：
    从XR应用服务器接收所述数据对应的XR帧到达所述UE的最晚时刻或者所述传输时延，其中，所述XR帧到达所述UE的最晚时 刻是根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻确定的。
  11. 根据权利要求8或9或10所述的数据传输方法，其特征在于，还包括：
    XR业务启动时，与所述UE、HMD、基站以及XR应用服务器进行时钟同步。
  12. 一种数据传输装置，其特征在于，包括：
    获取模块，用于获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
    确定模块，用于根据所述终端能力信息，确定传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长；
    发送模块，用于发送所述传输时延。
  13. 一种数据传输方法，其特征在于，包括：
    获取传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
    根据所述传输时延传输所述数据。
  14. 根据权利要求13所述的数据传输方法，其特征在于，所述获取传输时延，包括：
    自SMF接收所述传输时延。
  15. 根据权利要求13所述的数据传输方法，其特征在于，所述获取传输时延，包括：
    获取所述终端能力信息，以及所述数据对应的XR帧在所述HMD 中的显示时刻；
    根据所述终端能力信息以及所述XR帧在所述HMD中的显示时刻，确定所述XR帧到达所述UE的最晚时刻或所述传输时延。
  16. 根据权利要求15所述的数据传输方法，其特征在于，所述获取所述数据对应的XR帧在所述HMD中的显示时刻，包括：
    从XR应用服务器接收总传输时延以及所述XR帧之前第N个XR帧的发送时刻，其中，所述总传输时延为XR应用服务器到UE之间的传输时延，N为自然数；
    根据所述总传输时延以及所述XR帧之前第N个XR帧的发送时刻确定所述数据对应的XR帧在所述HMD中的显示时刻。
  17. 根据权利要求13所述的数据传输方法，其特征在于，所述根据所述传输时延传输所述数据，包括：
    在接收到所述数据后，以所述XR帧到达所述UE的最晚时刻为约束，传输所述数据。
  18. 根据权利要求13所述的数据传输方法，其特征在于，还包括：
    XR业务启动时，与所述UE、HMD、SMF以及XR应用服务器进行时钟同步。
  19. 根据权利要求13所述的数据传输方法，其特征在于，所述终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
  20. 根据权利要求13所述的数据传输方法，其特征在于，所述终端能力信息包括以下至少一项：
    UE与HMD结合的类型；
    UE与HMD结合，所需的XR业务处理时间；
    UE与HMD结合，所需的XR业务处理能力；
    UE与HMD结合，在Uu口传输之后所需的XR业务处理时间。
  21. 一种数据传输装置，其特征在于，包括：
    获取模块，用于获取传输时延，其中，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
    传输模块，用于根据所述传输时延传输所述数据。
  22. 一种数据传输方法，其特征在于，包括：
    获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
    上报终端能力信息。
  23. 根据权利要求22所述的数据传输方法，其特征在于，还包括：
    接收数据，其中，所述数据是根据传输时延进行传输的，所述传输时延用于指示网络设备接收所述数据到发送所述数据之间的最大时长，且所述传输时延根据终端能力信息确定。
  24. 根据权利要求22所述的数据传输方法，其特征在于，所述获取终端能力信息，包括：
    获取所述HMD的能力信息；
    根据所述HMD的能力信息以及所述UE的能力信息，生成所述终端能力信息。
  25. 根据权利要求22所述的数据传输方法，其特征在于，还包括：
    接收数据；
    获取所述数据对应的XR帧在所述HMD中的显示时刻；
    根据所述HMD的能力信息以及所述XR帧在所述HMD中的显示时刻，确定向所述HMD传输所述XR帧的最晚时刻或传输时延；
    以所述向所述HMD传输所述XR帧的最晚时刻或传输时延为约束，传输所述数据。
  26. 根据权利要求22所述的数据传输方法，其特征在于，还包括：
    接收数据；
    接收所述HMD上报的向所述HMD传输所述XR帧的最晚时刻或传输时延，其中，所述向所述HMD传输所述XR帧的最晚时刻或传输时延根据所述HMD的能力信息以及所述数据对应的XR帧在所述HMD中的显示时刻确定；
    以所述向所述HMD传输所述XR帧的最晚时刻或传输时延为约束，传输所述数据。
  27. 根据权利要求22所述的数据传输方法，其特征在于，所述上报终端能力信息包括：
    向基站、XR应用服务器或SMF上报所述终端能力信息。
  28. 根据权利要求22所述的数据传输方法，其特征在于，所述终端能力信息包括UE能力信息和HMD能力信息，其中，所述UE能力信息用于指示UE支持的XR能力，所述HMD能力信息用于指示HMD支持的XR能力。
  29. 根据权利要求22所述的数据传输方法，其特征在于，所述终端能力信息包括以下至少一项：
    UE与HMD结合的类型；
    UE与HMD结合，所需的XR业务处理时间；
    UE与HMD结合，所需的XR业务处理能力；
    UE与HMD结合，在Uu口传输之后所需的XR业务处理时间。
  30. 根据权利要求22所述的数据传输方法，其特征在于，还包括：
    XR业务启动时，与基站、HMD、SMF以及XR应用服务器进行时钟同步。
  31. 一种数据传输装置，其特征在于，包括：
    获取模块，用于获取终端能力信息，其中，所述终端能力信息用于指示UE和/或HMD支持的XR能力；
    上报模块，用于上报终端能力信息。
  32. 一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器运行时执行权利要求1至11中任一项或13至20中任一项或22至30中任一项所述方法的步骤。
  33. 一种数据传输装置，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，其特征在于，所述处理器运行所述计算机程序时执行权利要求1至11中任一项或13至20中任一项或22至30中任一项所述方法的步骤。
PCT/CN2022/088676 2021-04-27 2022-04-24 数据传输方法及装置、计算机可读存储介质 Ceased WO2022228322A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110462046.5A CN115250504B (zh) 2021-04-27 2021-04-27 数据传输方法及装置、计算机可读存储介质
CN202110462046.5 2021-04-27

Publications (1)

Publication Number Publication Date
WO2022228322A1 true WO2022228322A1 (zh) 2022-11-03

Family

ID=83696549

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/088676 Ceased WO2022228322A1 (zh) 2021-04-27 2022-04-24 数据传输方法及装置、计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN115250504B (zh)
WO (1) WO2022228322A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024229827A1 (zh) * 2023-05-11 2024-11-14 北京小米移动软件有限公司 信息指示方法、装置、通信设备及存储介质
WO2025112919A1 (zh) * 2023-11-29 2025-06-05 华为技术有限公司 基于服务质量的数据传输方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118283800B (zh) * 2022-12-29 2026-01-20 荣耀终端股份有限公司 时延信息管理方法及相关装置
CN119071300A (zh) * 2023-06-01 2024-12-03 大唐移动通信设备有限公司 云xr服务器的选择方法、设备、装置和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106101575A (zh) * 2016-06-28 2016-11-09 广东欧珀移动通信有限公司 一种增强现实照片的生成方法、装置及移动终端
CN108990112A (zh) * 2017-05-31 2018-12-11 华为技术有限公司 通信网络中的任务处理方法和通信装置
CN110770785A (zh) * 2017-06-29 2020-02-07 皇家Kpn公司 用于在vr中显示的屏幕共享
CN111064981A (zh) * 2018-10-16 2020-04-24 北京凌宇智控科技有限公司 一种视频串流的系统及方法
US20220028172A1 (en) * 2020-07-23 2022-01-27 Samsung Electronics Co., Ltd. Method and apparatus for transmitting 3d xr media data

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109314674B (zh) * 2016-04-20 2022-09-09 瑞典爱立信有限公司 取决于传输类型和ue处理能力延迟传输
CN107889097B (zh) * 2016-09-30 2022-01-28 中兴通讯股份有限公司 上行调度的处理方法、装置及系统
CN108401291B (zh) * 2017-02-06 2023-05-09 华为技术有限公司 数据传输的方法和装置
US10623725B2 (en) * 2018-01-03 2020-04-14 Votanic Ltd. 3D glasses incorporating real-time tracking
CN110958681B (zh) * 2018-09-27 2023-09-05 中兴通讯股份有限公司 业务传输方法及装置
US10904905B2 (en) * 2018-09-28 2021-01-26 Qualcomm Incorporated Variable packet delay budgets for wireless communications
CN111200848B (zh) * 2018-11-19 2022-03-25 华为技术有限公司 一种通信方法及装置
CN111698787B (zh) * 2019-03-14 2023-03-31 华为技术有限公司 调度规则确定方法及其装置
CN111865515B (zh) * 2019-04-25 2022-04-05 华为技术有限公司 通信方法和通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106101575A (zh) * 2016-06-28 2016-11-09 广东欧珀移动通信有限公司 一种增强现实照片的生成方法、装置及移动终端
CN108990112A (zh) * 2017-05-31 2018-12-11 华为技术有限公司 通信网络中的任务处理方法和通信装置
CN110770785A (zh) * 2017-06-29 2020-02-07 皇家Kpn公司 用于在vr中显示的屏幕共享
CN111064981A (zh) * 2018-10-16 2020-04-24 北京凌宇智控科技有限公司 一种视频串流的系统及方法
US20220028172A1 (en) * 2020-07-23 2022-01-27 Samsung Electronics Co., Ltd. Method and apparatus for transmitting 3d xr media data

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANNONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; QoE parameters and metrics relevant to the Virtual Reality user experience (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 26.929; V0.8.0, vol. SA WG4, no. V0.8.0, 26 April 2019 (2019-04-26), pages 1 - 36, XP051723700 *
QUALCOMM INCORPORATED, XIAOMI, TENCENT, SAMSUNG: "Updates to TR", 3GPP DRAFT; S4-200217, vol. SA WG4, 23 January 2020 (2020-01-23), Wroclaw, Poland, pages 1 - 20, XP051845128 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024229827A1 (zh) * 2023-05-11 2024-11-14 北京小米移动软件有限公司 信息指示方法、装置、通信设备及存储介质
WO2025112919A1 (zh) * 2023-11-29 2025-06-05 华为技术有限公司 基于服务质量的数据传输方法及装置

Also Published As

Publication number Publication date
CN115250504A (zh) 2022-10-28
CN115250504B (zh) 2026-01-30

Similar Documents

Publication Publication Date Title
JP7544782B2 (ja) サービス品質監視方法およびシステムならびにデバイス
WO2022228322A1 (zh) 数据传输方法及装置、计算机可读存储介质
WO2020259456A1 (zh) 数据包传输的方法和通信装置
WO2022068620A1 (zh) 一种数据传输方法以及装置
WO2023103919A1 (zh) 数据传输方法和数据传输装置
US20210112437A1 (en) User Plane QOS Bearer Control Method for 5G Fixed Access
EP4576869A1 (en) Data transmission method in communication system, and communication apparatus
WO2016029737A1 (zh) 一种数据传输方法及基站
WO2020147768A1 (zh) 处理数据的方法和处理数据的装置
WO2021249218A1 (zh) 数据传输方法和装置
WO2021008515A1 (zh) 网络切片架构下的数据传输的方法和装置
WO2020199034A1 (zh) 用于中继通信的方法和装置
WO2023185402A1 (zh) 通信方法及装置
WO2021062809A1 (zh) 一种时刻信息的通知方法和装置
WO2022152129A1 (zh) 上行数据发送增强流程的触发方法、装置及终端
JP2026504590A (ja) バッファ状態を報告する方法及び通信機器
CN120238907A (zh) 基于非3GPP接入的QoS处理方法、装置、可读介质及设备
WO2024065524A1 (zh) 分组数据汇聚协议实体建立、分组数据汇聚协议实体建立指示装置以及方法
WO2023217009A1 (zh) 数据传输方法、装置及通信设备
WO2022257910A1 (zh) QoS的控制方法及装置
CN115696554A (zh) 业务同步方法、装置及存储介质
WO2022193127A1 (zh) 业务调度方法、装置及系统
US20260032512A1 (en) Packet discarding method and communication apparatus
RU2785330C2 (ru) Устройство, система и способ мониторинга качества обслуживания
WO2024098267A1 (zh) 数据传输装置、数据发送装置以及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22794793

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22794793

Country of ref document: EP

Kind code of ref document: A1