WO2024007926A1 - Xr对象渲染的方法、通信装置及系统 - Google Patents

Xr对象渲染的方法、通信装置及系统 Download PDF

Info

Publication number
WO2024007926A1
WO2024007926A1 PCT/CN2023/103528 CN2023103528W WO2024007926A1 WO 2024007926 A1 WO2024007926 A1 WO 2024007926A1 CN 2023103528 W CN2023103528 W CN 2023103528W WO 2024007926 A1 WO2024007926 A1 WO 2024007926A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
rendering
rendered
terminal device
call
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/CN2023/103528
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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
Priority claimed from CN202210952860.XA external-priority patent/CN117411944A/zh
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP23834694.4A priority Critical patent/EP4539436A4/en
Publication of WO2024007926A1 publication Critical patent/WO2024007926A1/zh
Priority to US19/009,412 priority patent/US20250139917A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
    • G06T19/00—Manipulating three-dimensional [3D] models or images for computer graphics
    • G06T19/006—Mixed reality
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
    • G06T15/00—Three-dimensional [3D] image rendering
    • G06T15/005—General purpose rendering architectures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
    • G06T19/00—Manipulating three-dimensional [3D] models or images for computer graphics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/131—Protocols for games, networked simulations or virtual reality
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
    • G06T2210/00—Indexing scheme for image generation or computer graphics
    • G06T2210/08—Bandwidth reduction
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
    • G06T2219/00—Indexing scheme for manipulating 3D models or images for computer graphics
    • G06T2219/024—Multi-user, collaborative environment

Definitions

  • the present application relates to the field of computer technology, and more specifically, to a method, communication device and system for XR object rendering.
  • Extended reality refers to the use of computers to combine reality and virtuality to create a virtual environment for human-computer interaction, providing the experiencer with a "sense of immersion” that seamlessly transitions between the virtual world and the real world.
  • XR calls Take XR calls as an example.
  • XR calls integrate XR technology into traditional real-time audio and video calls to provide a new audio and video call experience, including but not limited to: remote assistance, remote loss assessment, remote shopping, telemedicine, and remote immersion. Meetings etc.
  • the complex three-dimensional (3D) scenes and objects involved in XR call services place high demands on rendering computing power. Therefore, providing a rendering method to meet the requirements of 3D scenes and objects as much as possible is an issue worth considering.
  • Embodiments of the present application provide a method, communication device and system for XR object rendering, which can satisfy the requirements of 3D scenes and objects as much as possible by allocating rendering tasks.
  • the first aspect provides a method for rendering XR objects, which can be executed by a terminal device, or can also be executed by a component (such as a chip or circuit) of the terminal device, without limitation.
  • a component such as a chip or circuit
  • the following description takes execution by a terminal device as an example.
  • the method may include: the terminal device determines or accepts the rendering division of labor.
  • the rendering division of labor refers to: a part of the XR objects to be rendered in the XR call of the terminal device are rendered by the network-side rendering device, and the other part of the XR objects to be rendered are rendered by the terminal device; the terminal device Render the XR object to be rendered rendered by the terminal device during the XR call, and send the XR object to be rendered rendered by the network-side rendering device during the XR call to the network-side rendering device.
  • the terminal device can determine or accept the rendering division of XR objects to be rendered in the XR call, that is, determine which XR objects to be rendered are rendered by the terminal device, and which XR objects are rendered by the network-side rendering device.
  • rendering tasks can be dynamically allocated between the terminal device and the network-side rendering device, achieving effective collaboration between the terminal device and the network-side rendering device and on-demand allocation of rendering tasks.
  • the terminal device accepting rendering division of labor includes: the terminal device receives division of labor instruction information from the network side control device, and the division of labor instruction information indicates that a part of the XR call of the terminal device is to be rendered.
  • the XR object is rendered by the network-side rendering device, and/or another part of the XR object to be rendered in the XR call of the terminal device is rendered by the terminal device.
  • rendering negotiation can be carried out between network equipment and terminal equipment, that is, the network side control equipment can determine the rendering division of XR objects to be rendered in the XR call, that is, determine which XR objects to be rendered are to be rendered by the terminal device, and which The network-side rendering device is responsible for rendering XR objects.
  • the rendering tasks can be dynamically allocated between the terminal device and the network-side rendering device through the network-side control device, realizing the realization of the terminal device and network Effective collaboration between side rendering devices and on-demand distribution of rendering tasks.
  • the method further includes: the terminal device sending the processing capability information of the terminal device to the network side control device.
  • the terminal device can provide the processing capability information of the terminal device to the network side control device, so that the network side control device determines whether to split and render the XR object to be rendered in the XR call.
  • the network side control device can determine whether to split and render the XR objects to be rendered in the XR call based on the actual processing capabilities of the terminal device, in line with the processing capabilities of the terminal device. ability.
  • the terminal device sends a registration message or a session call message to the network side access device to trigger the network side access device to send processing capability information of the terminal device to the network side control device.
  • the registration message or the session call message contains the processing capability information of the terminal device.
  • the terminal device can send the processing capability information of the terminal device to the network side control device during the registration process or session call process.
  • the processing capability information of the terminal device includes the rendering available computing power of the terminal device, or the processing capability information of the terminal device includes the rendering available computing power of the terminal device and the terminal device. Supported rendering division of labor methods.
  • the rendering division of labor supported by the terminal device includes at least one of the following: division of labor by layer, division of labor by type.
  • the rendering available computing power of the terminal device is determined by the terminal device based on the configuration of its own computing resources, or the rendering available computing power of the terminal device is determined by the terminal device based on the configuration of the terminal device. Determined by the remaining computing resources or available computing resources.
  • the method further includes: the terminal device sends XR call processing requirement information to the network side control device.
  • the terminal device can provide the processing demand information of the XR call to the network side control device, so that the network side control device determines the rendering division of labor based on the processing demand information of the XR call. In this way, the rendering division determined by the network-side control device can meet the processing needs of XR calls.
  • the processing requirement information of the XR call includes at least one of the following: information of the XR object to be rendered in the XR call, video resolution of the XR call, and video frames of the XR call Rate.
  • the terminal device determines the rendering division of labor based on at least one of the following: processing capability information of the terminal device, processing capability information of the network-side rendering device, and processing requirement information of the XR call.
  • the method further includes: the terminal device receiving processing capability information of the network-side rendering device from the network-side control device.
  • the processing capability information of the network-side rendering device includes the available computing power for rendering of the network-side rendering device; or, the processing capability information of the network-side rendering device includes the network-side rendering device.
  • the available computing power for rendering of the network-side rendering device is determined based on the configuration of the computing resources of the network-side rendering device, or the available computing power for rendering of the network-side rendering device It is determined based on the remaining computing resources or available computing resources of the network-side rendering device.
  • the rendering division of labor includes at least one of the following: division of labor by layer, division of labor by type.
  • the method further includes: the terminal device sends division of labor confirmation request information to the network side control device, the division of labor confirmation request information is used to request acceptance of rendering division of labor, and the division of labor confirmation request information includes using Among the XR objects to be rendered in the XR call, the information of the XR objects to be rendered by the network-side rendering device is included.
  • the terminal device determines the XR objects to be rendered that need to be rendered by the network-side rendering device among the XR objects to be rendered in the Effective collaboration with network-side rendering devices and on-demand allocation of rendering tasks.
  • the method further includes: the terminal device receives a division of labor confirmation response message from the network side control device, and the division of labor confirmation response information indicates that the rendering division of labor is accepted.
  • the terminal device when the terminal device determines that the network-side rendering device will render the XR object to be rendered by the network-side rendering device according to the division of labor confirmation response information, it can send the XR object to be rendered by the network-side rendering device to the network-side rendering device for rendering.
  • the method further includes: the terminal device obtains network-side service indication information, and the network-side service indication information indicates that the network-side rendering device can provide a service for rendering XR objects (i.e. The ability to render XR objects within an XR call).
  • the method further includes: the terminal device sends a rendered XR object to the network-side rendering device, and the rendered XR object is a result to be rendered by the terminal device during the XR call. Render XR object for rendering.
  • the terminal device can send the rendered XR object, that is, the media data (such as video stream) corresponding to the rendered XR object to the network-side rendering device, so that the network-side rendering device can correspond to the rendered XR object of the terminal device.
  • the media data corresponding to the XR object rendered by the network-side rendering device are merged and processed to provide complete media data (such as a complete video stream) for the terminal device involved in the XR call.
  • the division of labor instruction information includes information about the XR object to be rendered rendered by the terminal device during the XR call, and the terminal device sends the network-side rendering during the XR call to the network-side rendering device.
  • the method Before rendering the XR object to be rendered by the device, the method also includes: the terminal device determines the rendering of the network-side rendering device in the XR call based on the information of the XR object to be rendered in the XR call and the XR object to be rendered by the terminal device in the XR call. The XR object to be rendered.
  • the terminal device can determine the XR objects to be rendered that the network-side rendering device needs to render based on the XR objects to be rendered in the XR call and the XR objects to be rendered that the terminal device itself needs to render, so as to send the network-side rendering device to the network-side rendering device.
  • the side rendering device is responsible for rendering related data of the XR object to be rendered.
  • the division of labor indication information includes information about the XR objects to be rendered that are rendered by the network-side rendering device during the XR call, and the terminal device is responsible for rendering the XR objects that are to be rendered by the terminal device during the XR call.
  • the method also includes: the terminal device determines the XR object to be rendered by the terminal device in the XR call based on the information of the XR object to be rendered in the XR call and the XR object to be rendered by the network-side rendering device in the XR call. Render XR objects.
  • the terminal device can determine the XR objects to be rendered that the terminal device needs to render based on the XR objects to be rendered in the XR call and the XR objects to be rendered that the network-side rendering device needs to render, so as to determine the XR objects to be rendered that the terminal device needs to render.
  • XR objects are rendered.
  • the division of labor indication information includes information about the XR objects to be rendered rendered by the terminal device during the XR call and information about the XR objects to be rendered rendered by the network-side rendering device during the XR call. information.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device It is an application server, and the network-side rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • a method for rendering XR objects is provided, which method can be executed by a network device, or can also be executed by a component of the network device (such as a chip or circuit), which is not limited.
  • a component of the network device such as a chip or circuit
  • the following description takes the execution by the network side control device as an example.
  • the method may include: the network side control device determines or accepts the rendering division of labor.
  • the rendering division of labor means that part of the objects to be rendered in the XR call of the terminal device are rendered by the network side rendering device, and another part of the XR objects to be rendered are rendered by the terminal device; the network side The control device triggers the XR object rendered by the terminal device during the XR call to be rendered by the terminal device, and the XR object to be rendered rendered by the network-side rendering device during the XR call is rendered by the network-side rendering device.
  • the network side control device triggers the XR object rendered by the terminal device during the XR call to be rendered by the terminal device, and the to-be-rendered XR object rendered by the network-side rendering device during the XR call
  • the object is rendered by the network-side rendering device, including: the network-side control device sends division of labor instruction information to the terminal device, and the division of labor instruction information indicates that part of the XR objects to be rendered in the XR call of the terminal device are rendered by the network-side rendering device, and/or the terminal Another part of the XR objects to be rendered in the device's XR call are rendered by the terminal device.
  • the method further includes: in response to determining that the processing capability of the terminal device cannot meet the processing requirements of the XR call, the network side control device determines that the terminal device and the network side rendering device render respectively. Some of the XR objects to be rendered in the XR call.
  • the network side control device determines (or judges) that the processing capability of the terminal device cannot meet the processing requirements of the XR call.
  • the network side control device determines the rendering division of labor based on at least one of the following: processing capability information of the terminal device, processing capability information of the network side rendering device, and processing requirements of the XR call information.
  • the method further includes: the network side control device receiving the processing requirement information of the XR call from the terminal device.
  • the processing requirement information of the XR call includes at least one of the following: information of the XR object to be rendered in the XR call, video resolution of the XR call, and video frame of the XR call Rate.
  • the method further includes: the network side control device receiving the processing capability information of the terminal device from the terminal device.
  • the processing capability information of the terminal device includes the rendering available computing power of the terminal device, or the processing capability information of the terminal device includes the rendering available computing power of the terminal device and the terminal device. Supported rendering division of labor methods.
  • the available computing power for rendering of the terminal device is determined based on the configuration of the terminal device's own computing resources, or the available computing power for rendering of the terminal device is based on the remaining computing power of the terminal device. Computing resources or available computing resources.
  • the method further includes: the network side control device receiving processing capability information of the network side rendering device from the network side rendering device.
  • the network side control device accepts rendering division of labor, including: the network side control device receives division of labor confirmation request information from the terminal device, and the division of labor confirmation request information is used to request acceptance of rendering division of labor.
  • the division of labor confirmation request information includes information used to determine the XR object to be rendered that is rendered by the network-side rendering device among the XR objects to be rendered in the XR call; the network-side control device accepts the rendering division of labor according to the division of labor confirmation request information.
  • the network side control device triggers the XR object rendered by the terminal device during the XR call to be rendered by the terminal device, and the to-be-rendered XR object rendered by the network-side rendering device during the XR call
  • the object is rendered by the network-side rendering device, including: the network-side control device sends a division of labor confirmation response message to the terminal device, and the division of labor confirmation response information indicates that the rendering division of labor is accepted.
  • the method further includes: the network side control device sending the processing capability information of the network side rendering device to the terminal device.
  • the processing capability information of the network-side rendering device includes the rendering available computing power of the network-side rendering device, or the processing capability information of the network-side rendering device includes the network-side rendering device.
  • the available computing power for rendering of the network-side rendering device is determined based on the configuration of the computing resources of the network-side rendering device, or the available computing power for rendering of the network-side rendering device It is determined based on the remaining computing resources or available computing resources of the network-side rendering device.
  • the rendering division of labor includes at least one of the following: division of labor by layer, division of labor by type.
  • the method further includes: the network side control device sends network side service indication information to the terminal device, and the network side service indication information indicates that the network side rendering device can provide XR objects. Rendering services.
  • the division of labor instruction information includes at least one of the following: information about the XR object to be rendered rendered by the terminal device during the XR call, information about the XR object rendered by the network-side rendering device during the XR call Information about the XR object to be rendered.
  • the method further includes: the network side control device sends a request message to the network side rendering device, the request message is used to request at least one of the following: address information of the network side rendering device , the rendering resource information of the network-side rendering device; among which, the address information of the network-side rendering device is used to connect the terminal device related to the XR call to the network-side rendering device through the network-side access device, and the rendering resource information is the network-side rendering device.
  • the request message includes the computing power required for the network-side rendering device to render the XR object to be rendered.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device is an application server, and the network side The rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • a method for rendering an XR object is provided, which method can be executed by a network device, or can also be executed by a component of the network device (such as a chip or a circuit), which is not limited.
  • a component of the network device such as a chip or a circuit
  • the following uses the network-side rendering device Take the preparation execution as an example to illustrate.
  • the method may include: the network side rendering device receives the second part of the XR object to be rendered from the terminal device; the network side rendering device renders the second part of the XR object to be rendered; the network side rendering device receives the rendered third XR object from the terminal device.
  • the first part of the XR objects to be rendered are the XR objects to be rendered that are rendered by the terminal device during the XR call
  • the second part of the XR objects to be rendered are the XR objects that are to be rendered by the network-side rendering device during the XR call.
  • the terminal device can render part of the XR object, and the network-side rendering device can render part of the XR object.
  • rendering tasks can be dynamically allocated between the terminal device and the network-side rendering device through the network-side control device, achieving effective collaboration between the terminal device and the network-side rendering device and on-demand allocation of rendering tasks.
  • the terminal device can send the rendered first part of the XR object to be rendered to the network-side rendering device, that is, the rendered media data (such as a video stream) corresponding to the first part of the XR object to be rendered, so that the network-side rendering device can process the rendered XR object.
  • the media data corresponding to the first part of the XR object to be rendered and the rendered media data corresponding to the second part of the XR object to be rendered are merged to provide complete media data (such as a video stream) for the terminal device involved in the XR session.
  • the method further includes: the network-side rendering device sends the combined media data to the terminal device corresponding to the XR call.
  • the network-side rendering device sends the processing capability information of the network-side rendering device to the network-side control device, and the processing capability information of the network-side rendering device is used to determine the division of labor indication information
  • the division of labor instruction information indicates that some of the XR objects to be rendered in the XR call of the terminal device are rendered by the network-side rendering device, and/or that another part of the XR objects to be rendered in the XR call of the terminal device are rendered by the terminal device.
  • the processing capability information of the network-side rendering device includes the rendering available computing power of the network-side rendering device, or the processing capability information of the network-side rendering device includes the network-side rendering device.
  • the available computing power for rendering of the network-side rendering device is determined based on the configuration of the computing resources of the network-side rendering device, or the available computing power for rendering of the network-side rendering device It is determined based on the remaining computing resources or available computing resources of the network-side rendering device when the XR session is established.
  • the method further includes: the network-side rendering device receives a request message from the network-side control device, where the request message is used to request at least one of the following: the address of the network-side rendering device Information, rendering resource information of the network-side rendering device; among which, the address information of the network-side rendering device is used to connect the terminal device related to the XR call to the network-side rendering device through the network-side access device, and the rendering resource information is the network-side rendering The device is used to render information on resources of the XR object to be rendered rendered by the network-side rendering device; the network-side rendering device sends a response to the request message to the network-side control device.
  • the request message includes the computing power required by the network-side rendering device to render the second part of the XR object to be rendered.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device is an application server, and the network side The rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • the fourth aspect provides a method for rendering XR objects.
  • the method can be executed by a network device, or it can also be executed by a component of the network device (such as a chip or a circuit), which is not limited.
  • a component of the network device such as a chip or a circuit
  • the following description takes the execution by the network side control device as an example.
  • the method may include: the network side control device sends a request message to the network side rendering device.
  • the request message is used to request the network side rendering device to render the XR object to be rendered rendered by the network side rendering device during the XR call of the terminal device.
  • the request message includes the returned XR object.
  • the computing power required for the XR object to be rendered by the network-side rendering device; the network-side control device receives the response of the request message from the network-side rendering device.
  • the response to the request message is used to notify the network-side control device: whether the network-side rendering device will Render the XR object to be rendered by the network-side rendering device during the XR call.
  • the response to the request message of the network-side rendering device includes the address information of the network-side rendering device.
  • the address information of the network-side rendering device is used to connect the terminal device related to the XR call to the network-side rendering through the network-side access device. equipment.
  • the network The address information of the network-side rendering device can implicitly notify the network-side control device: whether the network-side rendering device will render the XR object to be rendered by the network-side rendering device in the XR call.
  • the network side control device can send the computing power required for the XR object to be rendered rendered by the network side rendering device to the network side rendering device, and then the network side rendering device can use the computing power required for the XR object to be rendered based on the XR object to be rendered. Allocate resources appropriately.
  • the request message is used to request address information of the network-side rendering device.
  • the method before the network side control device sends the request message to the network side rendering device, the method further includes: the network side control device receives the network side rendering device from the network side rendering device. processing capability information.
  • the method further includes: the network side control device determines the XR object to be rendered by the network side rendering device during the XR call based on the processing capability information of the network side rendering device.
  • the processing capability information of the network-side rendering device includes the rendering available computing power of the network-side rendering device, or the processing capability information of the network-side rendering device includes the network-side rendering device.
  • the available computing power for rendering of the network-side rendering device is determined based on the configuration of the computing resources of the network-side rendering device, or the available computing power for rendering of the network-side rendering device It is determined based on the remaining computing resources or available computing resources of the network-side rendering device.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device is an application server, and the network side The rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • the fifth aspect provides a method for rendering XR objects.
  • the method can be executed by a network device, or it can also be executed by a component of the network device (such as a chip or a circuit), which is not limited.
  • a component of the network device such as a chip or a circuit
  • the following description takes execution by the network-side rendering device as an example.
  • the method may include: the network-side rendering device receives a request message from the network-side control device.
  • the request message is used to request the network-side rendering device to render the XR object to be rendered by the network-side rendering device during the XR call of the terminal device.
  • the request message includes The computing power required for the XR object to be rendered rendered by the network-side rendering device during the XR call; the network-side rendering device sends a response to the request message to the network-side control device, and the response to the request message is used to notify the network-side control device: network-side rendering Whether the device will render the XR object to be rendered by the network-side rendering device during the XR call.
  • the request message is used to request address information of the network-side rendering device.
  • the method further includes: the network-side rendering device determines the network-side rendering device to render the XR object in the call based on the computing power required by the network-side rendering device to render the XR object. The resources required by the network-side rendering device to render the XR object to be rendered.
  • the method before the network-side rendering device receives the request message from the network-side control device, the method further includes: the network-side rendering device sends the network-side rendering device to the network-side control device processing capability information.
  • the processing capability information of the network-side rendering device includes the rendering available computing power of the network-side rendering device, or the processing capability information of the network-side rendering device includes the network-side rendering device.
  • the available computing power for rendering of the network-side rendering device is determined based on the configuration of the computing resources of the network-side rendering device, or the available computing power for rendering of the network-side rendering device It is determined based on the remaining computing resources or available computing resources of the network-side rendering device.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device is an application server, and the network side The rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • the sixth aspect provides a method for rendering XR objects.
  • the method can be executed by a communication system (such as a communication system including a terminal device and a network device), or can also be performed by a component of the communication system (such as a chip or circuit). Execution without limitation. For convenience of description, the following description takes execution by a terminal device as an example.
  • the method may include: the network side control device determines or accepts the rendering division of labor.
  • the rendering division of labor refers to: a part of the XR objects to be rendered in the XR call of the terminal device are rendered by the network side rendering device, and the other part of the XR objects to be rendered are rendered by the terminal device;
  • Network side control The XR object rendered by the terminal device during the XR call triggered by the control device is rendered by the terminal device, and the XR object to be rendered rendered by the network-side rendering device during the XR call is rendered by the network-side rendering device.
  • the network side control device sends division of labor instruction information to the terminal device, and the division of labor instruction information instructs that some of the XR objects to be rendered in the XR call of the terminal device are rendered by the network side rendering device. , and/or, another part of the XR objects to be rendered in the XR call of the terminal device are rendered by the terminal device; the terminal device receives the division of labor instruction information, and renders the XR objects to be rendered in the XR call that are rendered by the terminal device according to the division of labor instruction information; The terminal device sends the XR object to be rendered rendered by the network-side rendering device during the XR call to the network-side rendering device.
  • the method further includes: the terminal device sending processing capability information of the terminal device to the network side control device.
  • the terminal device sends processing capability information of the terminal device to the network side control device, including: the terminal device sends a registration message or a session call message to the network side access device to trigger The network side access device sends the processing capability information of the terminal device to the network side control device, and the registration message or session call message contains the processing capability information of the terminal device.
  • the method further includes: the terminal device sends XR call processing requirement information to the network side control device.
  • the method further includes: the terminal device sends a rendered XR object to the network-side rendering device, and the rendered XR object is a result to be rendered by the terminal device during the XR call. Render XR object for rendering.
  • the terminal device determines the rendering division of labor and sends division of labor confirmation request information to the network side control device.
  • the division of labor confirmation request information is used to request acceptance of rendering division of labor, and the network side control device receives the A division of labor confirmation request is made, and the rendering division of labor is accepted based on the division of labor confirmation request.
  • the method further includes: the network side control device sends a division of labor confirmation response message to the terminal device, the division of labor confirmation response information indicates that the rendering division of labor is accepted, and the terminal device receives the division of labor confirmation response information and confirm the rendering division.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device is an application server, and the network side The rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • the seventh aspect provides a method for rendering XR objects.
  • the method can be executed by a communication system (such as a communication system including a terminal device and a network device), or can also be performed by a component of the communication system (such as a chip or circuit). Execution without limitation. For convenience of description, the following description takes execution by a terminal device as an example.
  • the method may include: the network side control device sends a request message to the network side rendering device.
  • the request message is used to request the network side rendering device to render the XR object to be rendered rendered by the network side rendering device during the XR call of the terminal device.
  • the request message includes the returned XR object.
  • the response to the request message is used to notify the network-side control device: whether the network-side rendering device will render The XR object to be rendered by the network-side rendering device during an XR call.
  • the method before the network side control device sends the request message to the network side rendering device, the method further includes: the network side rendering device sends the network side control device the Processing capability information of the network-side rendering device.
  • the network-side rendering device determines that the network-side rendering device renders the XR object according to the computing power required by the network-side rendering device to render the
  • the XR call contains the resources required for the XR object to be rendered rendered by the network-side rendering device.
  • the network side control device is an XR control plane network element, and the network side rendering device is an XR media plane network element; or, the network side control device is an application server, and the network side The rendering device is a media resource function network element; or the network-side control device is an Internet service signaling server, and the network-side rendering device is an Internet service media server.
  • An eighth aspect provides a communication device, which is used to perform any of the possible implementations of the above first to seventh aspects.
  • the device may include units and/or modules for performing the method in any possible implementation of the first to seventh aspects, such as a processing unit and/or a communication unit.
  • the device is a communication device (such as a terminal device, or a network device).
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip, chip system or circuit used in communication equipment (such as terminal equipment, such as network equipment).
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a ninth aspect provides a communication device, which includes at least one processor for executing computer programs or instructions stored in a memory to perform the method in any of the possible implementations of the first to seventh aspects.
  • the device further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a communication device (such as a terminal device, or a network device).
  • a communication device such as a terminal device, or a network device.
  • the device is a chip, chip system or circuit used in communication equipment (such as terminal equipment, such as network equipment).
  • a tenth aspect provides a processor for executing the methods provided in the above aspects.
  • a computer-readable storage medium stores a program code executed by a user device.
  • the program code includes a method for executing any of the possible implementations of the above-mentioned first to seventh aspects. method.
  • a computer program product containing instructions is provided.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method in any of the possible implementation modes of the above-mentioned first to seventh aspects.
  • a communication system including at least one of the aforementioned terminal device, network-side control device, and network-side rendering device.
  • Figure 1 is a schematic diagram of a communication system applicable to an embodiment of the present application.
  • Figure 2 is a schematic diagram of a communication system suitable for another embodiment of the present application.
  • Figure 3 is a schematic diagram of a communication system suitable for another embodiment of the present application.
  • Figure 4 is a schematic diagram of an XR object rendering method 400 provided by an embodiment of the present application.
  • Figure 5 is a schematic flow chart of an XR object rendering method 500 provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart of an XR object rendering method 600 provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of an XR object rendering method 700 provided by an embodiment of the present application.
  • Figure 8 is a schematic flow chart of an XR object rendering method 800 provided by an embodiment of the present application.
  • Figure 9 is a schematic diagram of an XR object rendering method 900 provided by an embodiment of the present application.
  • Figure 10 is a schematic flow chart of an XR object rendering method 1000 provided by an embodiment of the present application.
  • Figure 11 is a schematic flow chart of an XR object rendering method 1100 provided by an embodiment of the present application.
  • Figure 12 is a schematic flow chart of an XR object rendering method 1200 provided by an embodiment of the present application.
  • Figure 13 is a schematic flow chart of an XR object rendering method 1300 provided by an embodiment of the present application.
  • Figure 14 is a schematic diagram of a communication device 1400 provided by an embodiment of the present application.
  • Figure 15 is a schematic diagram of a communication device 1500 provided by an embodiment of the present application.
  • the technical solution provided by this application can be applied to various communication systems, such as the fifth generation (5th generation, 5G) or new wireless (new radio, NR) system, over the top (OTT) system (or system that provides various application services to users through the Internet), long term evolution (LTE) system, LTE frequency division dual (frequency division duplex, FDD) system, LTE time division duplex (TDD) system, etc.
  • LTE long term evolution
  • LTE frequency division dual frequency division duplex
  • TDD time division duplex
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • MTC machine type communication
  • IoT Internet of things
  • the terminal equipment in the embodiment of this application may also be called user equipment (UE), access terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.
  • UE user equipment
  • access terminal mobile device
  • user terminal terminal
  • terminal wireless communication equipment
  • user agent user device
  • terminals are: virtual reality (VR) devices, augmented reality (AR) devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile networks, PLMN), etc., the embodiments of the present application are not limited to this.
  • VR virtual reality
  • AR augmented reality
  • PLMN public land mobile networks
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the network device in the embodiment of the present application may be a device used to communicate with a terminal device.
  • the network device may be, for example, a device in a communication network used to provide services to terminal devices.
  • the communication network may include an operator's IP multimedia subsystem (IMS) network, a built communication network, or other communication networks, which is not limited.
  • IMS IP multimedia subsystem
  • the XR-M network element is an AR media function (AR-M) network element.
  • AR-M AR media function
  • XR-C network elements and XR-M network elements can be understood as network elements used to implement different functions and can be combined into network slices as needed.
  • XR-C network elements and XR-M network elements can be independent hardware devices, or they can be integrated into the same hardware device, or they can be network elements in the hardware device, or they can be software functions running on dedicated hardware. Or it is a virtualization function module instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform
  • XR-C network elements and XR-M network elements can be provided by IMS operators or by third parties without restrictions.
  • AS refers to the server that provides application layer services for terminal devices. As can be seen from the figure, AS is the AS in IMS.
  • Media resource function network element used to process media data (such as media data related to XR calls) (such as rendering XR objects), and can participate in rendering negotiations.
  • the media resource function network element may be a multimedia resource function (MRF) network element in the 3GPP standard specification, which includes a multimedia resource function controller (MRFC) and a multimedia resource processor (multimedia resource processor). function processor, MRFP).
  • MRF multimedia resource function
  • the OTT XR call server may include an OTT XR call service signaling server (or Internet XR call service signaling server), OTT XR call service media processing server (or Internet XR call service media processing server), OTT XR call service routing server.
  • the OTT XR call service signaling server is responsible for processing signaling or messages for the XR call service
  • the OTT XR call service media processing server is for example responsible for processing the media data for the XR call service
  • the OTT XR call service routing server is for example responsible for Route or forward signaling or messages related to XR call services.
  • the naming of the OTT XR call server does not limit the scope of protection of the embodiments of this application.
  • the OTT server in the subsequent embodiments of this application refers to the OTT XR call server, which will not be described again.
  • Network equipment and terminal equipment can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. In the embodiments of this application, the scenarios in which network devices and terminal devices are located are not limited.
  • XR refers to the combination of reality and virtuality through computers to create a virtual environment for human-computer interaction.
  • XR is the collective name for various technologies such as VR, AR, and mixed reality (MR).
  • MR mixed reality
  • the user can experience a "sense of immersion" that seamlessly transitions between the virtual world and the real world.
  • XR calls integrate XR technology into traditional real-time audio and video calls to provide a new audio and video call experience, including but not limited to: remote assistance, remote loss assessment, remote shopping, telemedicine, and remote immersion. Meetings etc.
  • XR objects refer to components (or objects in the XR scene) in the XR scene (such as the XR call scene), and mainly describe a certain type or component in the XR scene.
  • XR objects in the XR scene can include virtual conference rooms, virtual characters, virtual chairs, virtual tables, etc.
  • the media data corresponding to the rendered XR object may include a video image frame sequence (or simply a video frame sequence) for displaying the XR object, which may be transmitted to the opposite terminal device (or local device) in the form of a video stream through the network. terminal equipment).
  • the media data corresponding to the rendered XR object is displayed on the screen (such as the screen of the terminal device), it can have a 3D effect, that is, the user can see a three-dimensional picture through the size of the object presented on the screen and the distance and distance perception.
  • the data channel described in the embodiment of the present application can be, for example, an IMS data channel (IMS data channel), that is, a data channel in IMS, which can be used for data transmission based on the flow control transmission protocol (stream control transmission protocol).
  • control transmission protocol (SCTP) to transmit data; that is, a data channel is a logical channel or data connection that transmits data based on SCTP.
  • DC can be used to transmit signaling or data, such as rendering division of labor interaction information and/or XR objects.
  • computing power is used to measure the device's rendering processing capability for XR objects.
  • IMS-AGW Mainly responsible for providing media anchor points for access to the IMS network entrance.
  • P-CSCF network element Located in the visited network, it is the entry node for terminal equipment to access the IMS network. It is mainly responsible for the forwarding of session initialization protocol (session initialization protocol, SIP) signaling between the terminal equipment and the home network.
  • session initialization protocol session initialization protocol, SIP
  • I-CSCF network element It is located in the home network and is the unified entry point of the home network. It is mainly responsible for allocating or querying S-CSCF network elements that serve terminal equipment.
  • S-CSCF network element Located in the home network, it is the central node of the IMS network and is mainly responsible for the registration, authentication, session, routing and service triggering of terminal equipment.
  • DCS-C network element DC control plane network element, mainly responsible for providing DC management functions.
  • DCS-M network element DC media plane network element, mainly responsible for providing DC media processing functions.
  • FIG. 2 is a schematic diagram of a communication system suitable for another embodiment of the present application.
  • the communication system may include a UE and network elements in an IMS network.
  • the network elements in the IMS network may include, for example: AS, MRF network element, IMS-AGW, P-CSCF network element, I-CSCF network element, and S-CSCF network element.
  • AS Access Management Function
  • MRF Mobility Management Function
  • IMS-AGW IMS-AGW
  • P-CSCF network element I-CSCF network element
  • I-CSCF network element I-CSCF network element
  • S-CSCF network element S-CSCF network element
  • FIG 3 is a schematic diagram of a communication system suitable for another embodiment of the present application.
  • the communication system may include a UE and an OTT server.
  • a UE may include a UE and an OTT server.
  • OTT server may include a UE and an OTT server.
  • FIG. 1 to FIG. 3 are only simplified schematic diagrams for ease of understanding, and the present application is not limited thereto.
  • these communication systems may also include other UEs, or these communication systems may also include other UEs and communication networks to which other UEs belong.
  • the UE in Figure 1 is marked as UE#1, and other UEs are marked as UE#2.
  • UE#2 can communicate with the IMS network in Figure 1.
  • the communication system may also include UE#2 and the IMS network to which UE#2 belongs.
  • UE#2 may communicate with the IMS network to which UE#1 belongs through the IMS network to which UE#2 belongs.
  • the network elements in the IMS network to which UE#2 belongs can refer to the network elements in the IMS network to which UE#1 belongs, and there is no restriction on this.
  • network elements mentioned in the embodiments of this application can be understood as being used to implement different functions.
  • Network elements can be combined into network slices as needed.
  • These network elements can be independent hardware devices, or they can be integrated into the same hardware device, or they can be network elements in the hardware device, or they can be software functions running on dedicated hardware, or platforms (for example, cloud platforms ), this application does not limit the specific form of the above network elements.
  • the above nomenclature is only defined to facilitate the differentiation of different functions, and should not constitute any limitation on this application. This application does not rule out the possibility of using other naming in 6G networks and other networks in the future.
  • One rendering method is: rendering processing is performed by the terminal device.
  • rendering processing capabilities may not be able to meet the requirements of complex 3D scenes and objects, thus limiting the application and effects of XR services.
  • Another rendering method is: rendering processing by network devices.
  • this processing method requires the terminal device to send the relevant data of the XR object to be rendered to the network device. After the network device completes the rendering, it re-encodes the video and then sends it to the terminal device, which decodes and displays it. This method will bring a large delay and a large waste of resources to the network equipment.
  • Figure 4 is a schematic diagram of an XR object rendering method 400 provided by an embodiment of the present application.
  • Method 400 may include the following steps.
  • the terminal device accepts rendering division of labor.
  • Rendering division of labor refers to: a part of the XR objects to be rendered in the XR call of the terminal device are rendered by the network-side rendering device, and the other part of the XR objects to be rendered are rendered by the terminal device.
  • 410 may be: the terminal device receives the division of labor instruction information from the first network device, and the division of labor instruction information indicates that: a part of the XR objects to be rendered in the XR call of the terminal device are rendered by the second network device, and/or the terminal Another part of the XR objects to be rendered in the device's XR call are rendered by the terminal device.
  • the first network device represents the network side device that determines the rendering division, corresponding to the network side control device in the content of the invention
  • the second network device represents the network side device that performs rendering on some XR objects to be rendered in the XR call of the terminal device, Corresponding to the network-side rendering device in the summary of the invention, 410 and 420 below.
  • the rendering division of labor means the terminal device and the second network device respectively render some of the XR objects to be rendered in the XR call of the terminal device, that is, the XR objects to be rendered in the XR call of the terminal device are performed by the terminal device and the second network device. render.
  • the first network device may send division of labor instruction information to the terminal device to instruct the terminal device and the second network device to respectively render some of the XR objects to be rendered in the XR call of the terminal device.
  • the terminal device accepts the rendering division of labor according to the division of labor instruction information.
  • XR call can also be called XR communication (XR communication, or XR call service, or XR conversation). It can be understood that in the embodiment of the present application, XR calls are not limited to one-to-one communication (or end-to-end communication). XR calls can be one-to-many communications, many-to-one communications, or many-pair communications. Multiple communications without restrictions. For example, an XR call can be a conference call. The XR call of the terminal device refers to the XR call in which the terminal device participates.
  • the division of labor instruction information indicates: the terminal device renders the first part of the XR object to be rendered in the XR call of the terminal device and/or the second network device renders the second part of the XR object to be rendered in the XR call of the terminal device; or it can be replaced with :
  • the terminal device and the second network device respectively render some XR objects to be rendered in the XR call of the terminal device.
  • the division of labor instruction information indicates that the rendering operation of the XR object to be rendered in the XR call of the terminal device is shared by the terminal device and the second network device, and both are respectively responsible for the rendering operations of a part of the XR object to be rendered.
  • the division of labor indication information includes information about the second part of the XR object to be rendered that the second network device is responsible for rendering.
  • the method 400 also includes: the terminal device renders the XR object according to the XR Information about the XR object to be rendered and the second part of the XR object to be rendered during the call determines the first part of the XR object to be rendered. In this way, the terminal device can render the first part of the XR object to be rendered.
  • the first part of the information of the XR object to be rendered or the second part of the information of the XR object to be rendered included in the division of labor indication information may be the type of the XR object to be rendered (such as characters, buildings, plants, etc.); If the division of labor is based on layers, the first part of the information of the XR object to be rendered or the second part of the information of the XR object to be rendered included in the division of labor indication information may be the hierarchical information of the XR object to be rendered (such as foreground or background).
  • the division of labor indication information may also include the first part of the XR objects to be rendered that the terminal device is responsible for rendering, and the second part of the XR objects to be rendered that the second network device is responsible for rendering, so that the terminal device can directly determine based on the division of labor indication information that the terminal device is responsible for rendering
  • the first part of the XR object to be rendered, and the second part of the XR object to be rendered are sent to the second network device.
  • rendering negotiation can be performed between the network device and the terminal device. That is, the first network device can determine the rendering division of XR objects in the XR call, that is, determine which XR objects to be rendered are to be rendered by the terminal device and which ones.
  • the XR object to be rendered is rendered by the second network device.
  • the rendering task can be dynamically allocated between the terminal device and the second network device through the first network device, thus realizing the communication between the terminal device and the second network device. Effective collaboration among users and on-demand allocation of rendering tasks.
  • the terminal device sends processing capability information (that is, processing capability information) of the terminal device to the first network device.
  • the processing capability information of the terminal device may be used to determine the division of labor instruction information.
  • the first network device may determine the division of labor instruction information based on the processing capability information of the terminal device.
  • the terminal device sends processing capability information of the terminal device to the first network device during the registration process or the XR call establishment process.
  • the terminal device sends a registration message or a session call message to a third network device to trigger the third network device to send processing capability information of the terminal device to the first network device, and the registration message or session request message contains the processing capability information of the terminal device.
  • the session call message may be a session call request message or a session call response message.
  • the terminal device sends a registration message or a session call message to the third network device, and the registration message or session call message includes the processing capability information of the terminal device; after receiving the processing capability information of the terminal device, the third network device sends a message to the third network device.
  • the first network device sends the final processing capability information of the terminal device.
  • the third network device may be, for example, a network element in an IMS network, or may be an OTT server, etc., without limitation.
  • the third network device corresponds to the network-side access device in the content of the invention.
  • the processing capability may also be called XR media processing capability or XR object processing capability, and its naming does not limit the scope of protection of the embodiments of the present application.
  • the processing capability of the terminal device can be used to determine whether to perform split rendering on the XR objects to be rendered in the XR call.
  • Split rendering means that part of the XR objects to be rendered in the XR call are rendered by the terminal device, and part of the XR objects to be rendered are rendered by the second network device. render.
  • the processing capability of the terminal device includes the available computing power for rendering of the terminal device, or the processing capability of the terminal device includes the available computing power for rendering of the terminal device and the rendering division of labor method supported by the terminal device.
  • the available computing power for rendering of the terminal device indicates the available computing power or remaining computing power of the terminal device for rendering XR objects.
  • the available computing power for rendering of the terminal device is determined by the terminal device based on the configuration of its own computing resources (such as software and hardware resources).
  • the available computing power for rendering of the terminal device is determined by the terminal device based on the available or remaining computing power of the terminal device. Resources are determined. Among them, the available or remaining computing resources of the terminal device can be when the XR call is established or during the process of establishing the XR call (including the initial XR call establishment and the updated XR call establishment). Computing resources are determined.
  • the available computing power for rendering of the terminal device can be defined based on the remaining available power consumption limited by the graphics processing unit (GPU), or it can also be defined based on the remaining available computing power of the GPU. There is no limit. The specific combination method will be discussed later. 500 detailed description.
  • GPU graphics processing unit
  • division of labor by type refers to division of labor according to the type of XR objects to be rendered (such as people, buildings, plants, etc.), so that different entities (terminal devices or network devices) can render different types of XR objects to be rendered, for example, XR objects to be rendered such as people are rendered by terminal devices, and XR objects such as buildings and plants are rendered by network devices.
  • the embodiment of the present application does not limit the type classification method of XR objects to be rendered. It can also be understood that the embodiments of the present application are not limited to the above two division of labor methods, and other division of labor methods can also be adopted. For example, labor can also be divided according to motion states. XR objects that need to be moved and to be rendered are rendered by the terminal device, and stationary ones are to be rendered. XR objects are rendered by network devices.
  • the processing capabilities of the terminal device are exemplary rather than limiting.
  • the processing capability of the terminal device can be expressed in other forms.
  • the processing capability of the terminal device includes the available computing power for rendering of the terminal device and the rendering division methods that are prohibited (or not supported or allowed) by the terminal device.
  • the terminal device sending information about the processing capability of the terminal device to the first network device as an example, and this is not limiting.
  • the terminal device may also send information used to determine the processing capability of the terminal device to the first network device.
  • the processing requirements of XR calls are also called XR media processing requirements or XR object processing requirements. Their naming does not limit the scope of protection of the embodiments of this application. It can be used to determine whether to perform split rendering, and can also be used to determine the specific division of rendering labor.
  • the processing requirement information of the XR call includes at least one of the following: information about the XR object to be rendered in the XR call, XR call The video resolution and video frame rate of the XR call.
  • the information of the XR object to be rendered in the XR call that is, the original data of the XR object in the XR call service.
  • the XR objects to be rendered in an XR call include: raw data of virtual conference rooms, virtual characters, and virtual chairs.
  • the video resolution of the XR call refers to the length and width of the video screen of the XR call service, for example: 1920, 1080.
  • the video frame rate of the XR call refers to the number of video frames in the XR call service per unit time (such as 1 second), for example: 30 frames/second.
  • the following introduces the relevant scheme for the first network device to determine the rendering division of labor.
  • the first network device determines to split and render the XR object to be rendered in the XR call. It can be understood that due to split rendering, the processing capability of the terminal device can ensure that the terminal device renders some of the XR objects to be rendered in the XR call. Further optionally, if the processing capability of the terminal device meets the processing requirements of the XR call, the first network device may determine to split and render the XR objects to be rendered in the XR call, or may also determine that the terminal device performs split rendering on the XR call.
  • the XR objects to be rendered are rendered without restrictions. The embodiments of this application are mainly concerned with the situation of split rendering.
  • the processing capability information of the terminal device includes the rendering available computing power of the terminal device. If the rendering available computing power of the terminal device cannot meet the processing requirements of the XR call, the first network device determines the XR object to be rendered in the XR call. Perform split rendering.
  • the processing capability information of the terminal device includes the rendering available computing power of the terminal device and the rendering division method supported by the terminal device. If the rendering available computing power of the terminal device cannot meet the processing needs of the XR call, and the terminal device supports splitting, rendering, the first network device determines to split and render the XR object to be rendered in the XR call.
  • the first network device determines the rendering division of XR objects in the XR call based on at least one of the following: processing capability information of the terminal device, processing capability information of the second network device, and processing requirement information of the XR call.
  • the processing capability information of the second network device may refer to the processing capability information of the terminal device, which will not be described again here (it should be noted that the rendering available computing power of the second network device may be based on the computing power of the second network device).
  • the configuration of the resources is determined, or the rendering available computing power of the second network device is determined by the second network device based on the remaining computing resources or available computing resources of the second network device, or the rendering available computing power of the second network device can
  • the first network device is determined based on the configuration of the computing resources of the second network device, or the available computing power for rendering of the second network device is determined by the first network device based on the remaining computing resources or available computing resources of the second network device, This application does not limit this).
  • Example 1 The first network device determines the rendering division of labor for the XR object to be rendered in the XR call based on the processing capability information of the terminal device, that is, determines the division of labor instruction information.
  • the processing capability information of the terminal device includes the available computing power for rendering of the terminal device.
  • the first network device determines the first part of the XR objects to be rendered by the terminal device according to the available computing power for rendering of the terminal device.
  • the remaining XR objects to be rendered are determined by
  • the second network device is responsible for rendering.
  • Example 2 The first network device determines the rendering division of labor for the XR object in the XR call based on the processing capability information of the second network device, that is, the division of labor instruction information is determined.
  • the processing capability information of the second network device includes the available computing power for rendering of the second network device, and the first network device determines the first part of the XR objects to be rendered that the second network device is responsible for rendering based on the available computing power for rendering of the second network device. , the remaining XR objects to be rendered are rendered by the terminal device.
  • the processing capability information of the second network device includes the rendering division of labor mode supported by the second network device, and the first network device may determine the rendering division of labor according to the rendering division of labor mode supported by the second network device. If the rendering division of labor supported by the second network device is division of labor by type, then the rendering division of labor determined by the first network device may be: the terminal device renders a part of the XR objects to be rendered (such as virtual tables and chairs), and the second network device renders the remaining parts. XR objects to be rendered (such as virtual meeting rooms and people). In this case, it can be assumed that the rendering available computing power of the terminal device and the second network device is sufficient to render the XR objects to be rendered that they are responsible for.
  • Example 3 The first network device determines the rendering division of labor for the XR object in the XR call based on the processing requirement information of the XR call, that is, determines the division of labor instruction information.
  • the processing requirement information of the XR call includes: XR objects to be rendered in the XR call.
  • the first network device determines the rendering division of labor based on: Some XR objects to be rendered are rendered by the second network device. In this case, it can be assumed that the rendering available computing power of the terminal device and the second network device is sufficient to render the XR objects to be rendered that they are responsible for.
  • Example 4 The first network device determines the rendering division of labor for the XR object in the XR call based on the processing capability information of the terminal device and the processing capability information of the second network device, that is, determines the division of labor instruction information.
  • the processing capability information of the terminal device includes the rendering available computing power of the terminal device
  • the processing capability information of the second network device includes the rendering available computing power of the second network device
  • the first network device is based on the rendering available computing power of the terminal device and the third network device.
  • the available computing power for rendering of the two network devices determines the first part of the XR objects to be rendered that is responsible for rendering by the terminal device, and the second part of the XR objects to be rendered that is responsible for rendering by the second network device.
  • the rendering computing power available for the terminal device is sufficient for the terminal device to render the first part of the XR objects to be rendered
  • the rendering computing power available for the second network device is sufficient for the second network device to render the second part of the XR objects to be rendered.
  • Example 5 The first network device determines the rendering division of labor for the XR object in the XR call based on the processing capability information of the terminal device and the processing requirement information of the XR call, that is, the division of labor instruction information is determined.
  • the processing capability information of the terminal device includes the available computing power for rendering of the terminal device.
  • the first network device estimates the computing power required to render the XR object to be rendered in the XR call based on the processing demand information of the XR call, and based on the The computing power required for the XR object to be rendered and the available computing power for rendering of the terminal device determine the first part of the XR object to be rendered that is responsible for rendering by the terminal device, and the remaining XR objects to be rendered (i.e., the second part of the XR object to be rendered) are determined by the third The second network device is responsible for rendering.
  • Example 6 The first network device determines the rendering division of labor for the XR object in the XR call based on the processing capability information of the second network device and the processing requirement information of the XR call, that is, the division of labor instruction information is determined.
  • the processing capability information of the second network device includes the available computing power for rendering of the second network device.
  • the first network device estimates the computing power required to render the XR object to be rendered in the XR call based on the processing demand information of the XR call, and based on
  • the computing power required to render the XR object to be rendered in the XR call and the available computing power for rendering of the second network device are used to determine the second part of the XR object to be rendered that is responsible for rendering by the second network device, and the remaining XR objects to be rendered (i.e., the second part of the XR object to be rendered).
  • a portion of the XR objects to be rendered are rendered by the terminal device.
  • Example 7 The first network device determines the rendering division of labor for the XR object in the XR call based on the processing capability information of the terminal device, the processing capability information of the second network device, and the processing requirement information of the XR call, that is, the division of labor instruction information is determined.
  • the processing capability information of the second network device includes the available computing power for rendering of the second network device
  • the processing capability information of the terminal device includes the available computing power for rendering of the terminal device
  • the first network device estimates rendering based on the processing demand information of the XR call.
  • the computing power required to render the XR object in the XR call and based on the computing power required to render the XR object to be rendered in the XR call, the available computing power for rendering of the second network device, and the available computing power for rendering of the terminal device, determine The terminal device is responsible for rendering the first part of the XR object to be rendered
  • the second network device is responsible for rendering the second part of the XR object to be rendered.
  • the terminal device can render the XR object to be rendered in the XR call.
  • the first network device sends a request message to the second network device, and the request message is used to request at least one of the following: address information of the second network device, Rendering resource information of the second network device; the first network device receives a response to the request message from the second network device.
  • the request message is used to request the address information of the second network device
  • the response to the request message carries the address information of the second network device.
  • the first network device may send address information to the terminal device.
  • the response to the request message is used to notify the resource application result, that is, whether the second network device will render.
  • the request message is used to request the second network device to render the rendering resource information of the second part of the XR object to be rendered. If the response to the request message includes the address information of the second network device, it means that the second network device Agree to render. In another possible implementation, the request message is used to request the second network device to render the rendering resource information of the second part of the XR object to be rendered, and the response to the request message may include information directly indicating whether the second network device will render.
  • the request message includes the computing power required by the second network device to render the second part of the XR object to be rendered.
  • the computing power required by the second network device to render the second part of the XR object to be rendered is used by the second network device to allocate and render the second part of the XR object to be rendered.
  • the address information of the second network device is used to connect the terminal device related to the XR call to the second network device through the third network device.
  • the address information of the second network device includes the local connection address of the first resource endpoint and the local connection address of the second resource endpoint.
  • the connection address and the local connection address of the second resource endpoint are respectively used for the local terminal device (UE#1 in Figures 5 to 8) and the opposite terminal device (UE#2 in Figures 5 to 8).
  • the second network device is connected through the third network device.
  • the local terminal device is connected to the second network device through the third network device, and the opposite terminal device is connected to the second network device through the third network device.
  • the first network device sends a request message to the second network device.
  • the request message is used to request the address information of the second network device, which means that the request message is used to request the creation or allocation of endpoint resources.
  • the second network device may create or allocate a corresponding resource endpoint (also referred to as a media endpoint), and may also return information of the corresponding resource endpoint to the first network device.
  • the resource endpoints are the above-mentioned first resource endpoint and the second resource endpoint, and the resource endpoint information includes the local connection address of the first resource endpoint and the local connection address of the second resource endpoint.
  • the rendering resource information is information about the resources used by the second network device to render the XR object to be rendered by the second network device.
  • the first network device sends a request message to the second network device.
  • the request message is used to request the rendering resource information of the second network device, which means that the request message is used to request the second network device to reserve or allocate computing power. resources, correspondingly, the second network device can reserve or allocate corresponding computing resources.
  • FIG. 5 is a schematic flow chart of an XR object rendering method 500 provided by an embodiment of the present application.
  • This method 500 can be used to implement the solution of the above method 400.
  • this method 500 may include the following steps.
  • UE#1 sends the processing capability of UE#1 to the network device.
  • UE#1 reports its own processing capability, that is, UE#1's own processing capability information, to the network device, so that during the subsequent session establishment process, the network device can communicate between UE#1 and the network device based on the processing capability of UE#1. Conduct rendering negotiations.
  • the processing capability includes parameter A and parameter B.
  • parameter A represents the supported rendering division of labor method.
  • the rendering division methods supported by UE#1 include: division of labor by layer and division of labor by type.
  • Division of work by layer means that rendering can be performed in layers, for example, foreground and background are distinguished for rendering.
  • parameter B represents the available computing power for rendering, that is, the available computing power of the terminal device for rendering XR objects.
  • the value of parameter B can be a static value determined by the terminal device based on its own computing resource configuration (such as CPU model, number of memory modules, etc.), or it can be dynamically determined based on the idleness of the current terminal device's hardware resources when the session is established ( That is, the remaining computing resources or available computing resources of the terminal device are calculated and are not limited.
  • the remaining computing resources or available computing resources of the terminal device are calculated and are not limited.
  • Method 1 Defined by the remaining available power consumption limited by the GPU, and the value can be watts.
  • the overall power consumption of AR glasses is about 0.5 watts to 2 watts
  • the overall power consumption of VR all-in-one machines is about 3 watts to 7 watts.
  • UE#1 can determine the value of parameter B according to its own configuration.
  • Method 2 Defined by the remaining available computing power of the GPU, the value can be the number of floating point operations performed per second (floating point operations per second, TFLOPS).
  • the network device saves the processing capability of UE#1.
  • the method 500 also includes step 503 and step 504.
  • the network device sends the processing capability of the network device to UE#1.
  • UE#1 determines that the network device can render XR objects.
  • UE#1 can learn whether the network device can render XR objects, that is, whether it supports XR object rendering. Steps 503 and 504 are optional steps, that is, the network device does not need to provide the processing capabilities of the network device to UE#1, and UE#1 can default to the network device being able to render XR objects.
  • Scenario 1 UE#1 initiates an initial session call.
  • UE#1 sends a session call request to the network device.
  • processing capability of UE#1 reported by UE#1 in step 501 can also be sent in step 5111. That is, method 500 may not include 501, and in step 5111, the session call request includes the processing capabilities of UE#1.
  • the session call request includes processing requirements for the XR call.
  • UE#1 defaults to a network device that supports XR object rendering. Therefore, UE#1 carries XR call processing requirements in the session call request to request rendering negotiation with the network device.
  • UE#1 determines whether the network device supports XR object rendering based on the processing capability of the network device received in step 503. If UE#1 determines that the network device supports XR object rendering, UE#1 carries the processing requirements of the XR call in the session call request to request rendering negotiation with the network device. If UE#1 determines that the network device does not support media rendering, UE#1 does not carry the processing requirements for the XR call in the session call request. For the case where the network device does not support XR object rendering, as an example, UE#1 can perform the rendering process by itself. The embodiments of this application mainly introduce the situation in which network devices support XR object rendering.
  • the processing requirements for the XR call include one or more of parameter C, parameter D, and parameter E.
  • parameter C represents the XR object to be rendered, that is, the XR object to be rendered.
  • XR object to be rendered For example, use “0" to represent a virtual conference room, use “1” to represent a virtual character, use “2” to represent a virtual chair, and use “3" to represent a virtual table. If the value of parameter C is 0, 1, 2, it means that the XR objects to be rendered include: virtual conference room, virtual character, and virtual chair.
  • parameter D represents the video resolution, which can define the length and width of the video picture.
  • the value of parameter D is: 1920,1080, which indicates that the video resolution is: 1920,1080.
  • parameter E represents the video frame rate.
  • the value of parameter E is 30, which indicates that the video frame rate is 30 frames/second.
  • the network device determines the division of labor instruction information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the session call request in step 5111 includes the processing requirements for the XR call.
  • the network device generates the processing requirements for the XR call.
  • the network device generates processing requirements for the XR call based on the XR application business logic and session parameters. In this manner, the session call request in step 5111 does not need to carry the processing requirements of the XR call.
  • the network device determines the division of labor indication information based on the processing requirements of the XR call and the processing capability of UE#1. For example, the network device can determine whether the rendering computing power requirements of all XR objects to be rendered in this XR call exceed the available rendering computing power of UE#1 based on the processing requirements of the XR call and the processing capabilities of UE#1, that is, Whether the available computing power of UE#1 for rendering can meet the computing power requirements for the XR object to be rendered in this XR call.
  • the network device can determine to split the rendering of the XR object to be rendered in this XR call, that is, for the XR object to be rendered Object, the network device renders part of the XR object, and UE#1 renders part of the XR object.
  • some of the XR objects rendered by the network device may be XR objects whose rendering computing power required to render the XR object in this XR call exceeds the available rendering computing power of UE#1. It can be understood that due to split rendering, the available computing power for rendering of UE#1 is greater than or equal to the preset value, that is, UE#1 can render some XR objects.
  • the network device determines the division of labor indication information based on: the processing requirements of the XR call, the processing capability of UE#1, and the processing capability of the network device. For example, the network device can calculate the XR call rendering computing power requirements based on the processing requirements of the XR call, and determine whether it exceeds the processing capabilities of the terminal device (such as the available computing power for rendering), and determine Division of labor instruction information.
  • the network device can determine to split the rendering of the XR object to be rendered in this XR call, that is, for the XR object to be rendered Object, the network device renders part of the XR object, and UE#1 renders part of the XR object.
  • the network device can divide the rendering tasks according to its own available computing power for rendering and the available computing power for UE#1's rendering.
  • some of the XR objects rendered by the network device may be XR objects whose rendering computing power required to render the XR object in this XR call exceeds the available rendering computing power of UE#1. It's understandable, since it's Split rendering, so the available computing power for rendering of UE#1 is greater than or equal to the preset value, that is, UE#1 can render some XR objects.
  • the following describes how the network device determines whether the rendering computing power required for this XR call exceeds the available rendering computing power of UE#1.
  • the network device can estimate the power consumption or equivalent TFLOPS required to render the XR object to be rendered by matching the baseline data based on the video resolution or object volume, video frame rate, etc. of the XR object to be rendered, and then determine Whether the rendering computing power required for the XR object to be rendered in this XR call exceeds the available rendering computing power of UE#1.
  • benchmark testing can be done through a GPU testing tool to determine the power consumption or equivalent TFLOPS required to render the XR object to be rendered.
  • the model in the GPU test tool By testing different 3D Render the model in the GPU test tool to obtain the required power consumption or equivalent TFLOPS as benchmark data. Then, based on the XR object of the actual XR call, the corresponding power consumption or equivalent TFLOPS is calculated with reference to the video resolution and video frame rate corresponding to the same 3D model of the benchmark data, and then the power consumption or equivalent TFLOPS required to render the XR object to be rendered is obtained. Equivalent to TFLOPS.
  • the network device can determine to split the rendering of the XR object to be rendered in this XR call, that is, for the XR object to be rendered, XR object, network device renders part of XR object, UE#1 renders part of XR object.
  • Table 1 shows the power consumption and equivalent TFLOPS consumed by the rendering of several 3D models at different video resolutions or volumes and different video frame rates.
  • the network device can obtain the power consumption requirements for XR object rendering according to Table 1: the power consumption of the virtual conference room is 4 watts, the power consumption of the virtual chair is 1 watt, and the power consumption of the virtual table is 6 watts.
  • the network device calculates that the rendering power consumption requirement of the XR object to be rendered is 11 watts, which exceeds the processing capability of UE#1 (i.e. 4 watts). Therefore, for the XR object to be rendered, the network device renders part of the XR object, and UE#1 renders part of the XR object.
  • some of the XR objects rendered by the network device may be XR objects corresponding to which the rendering computing power required for the XR object to be rendered in this XR call exceeds the available computing power for rendering of UE#1.
  • the network device may determine that UE#1
  • the XR objects to be rendered that are responsible for rendering are: virtual conference room, and the XR objects to be rendered that are responsible for rendering by network equipment are: virtual chairs and virtual tables.
  • the network device sends division of labor instruction information to UE#1.
  • the network device sends division of labor instruction information to UE#1.
  • the network device sends a session call response to UE#1, and the session call response carries the rendering negotiation result of this XR call, that is, the division of labor indication information.
  • the division of labor instruction information includes parameter F and parameter G.
  • the parameter F represents the rendering division method of the XR call, that is, the split rendering method of the XR object to be rendered in the XR call.
  • the value definition of parameter F is the same as the value of parameter A in step 501. For example, assume that the value of parameter A in step 501 is 0, indicating that the supported rendering division of labor includes division of labor by layer, and the value of parameter A is 1, indicating that the supported rendering division of labor includes division of labor by type. Then in step 5113, if the value of parameter F is 0, it means that the rendering division of XR calls determined by the network device is by layer; if the value of parameter F is 1, it means that the rendering division of XR calls determined by the network device is The rendering division of labor is by type.
  • parameter G represents the XR object to be rendered that the network device is responsible for rendering. Based on this parameter G and all XR objects to be rendered, UE#1 can learn the XR objects to be rendered that it is responsible for rendering.
  • the value definition of parameter G is the same as the value of parameter C in step 5111. For example, assume that the value of parameter C in step 5111 is 0, 1, 2, 3, and its meaning is as follows: "0" represents a virtual conference room, "1" represents a virtual character, "2" represents a virtual chair, and "3" ” represents a virtual table. Taking the above example as an example, if the XR objects to be rendered that the network device is responsible for rendering are: virtual chairs and virtual tables, the value of parameter G can be 2 or 3.
  • UE#1 learns that UE#1 is responsible for rendering based on all XR objects to be rendered and the XR objects to be rendered that the network device is responsible for rendering. "Virtual Meeting Room”.
  • the division of labor instruction information includes parameters F and H, where parameter H represents the XR object to be rendered that UE#1 is responsible for rendering, that is, UE#1 is based on all XR objects to be rendered and the XR object to be rendered that UE#1 is responsible for rendering. , you can know the XR object to be rendered that the network device is responsible for rendering.
  • the division of labor instruction information includes parameter G and parameter H.
  • the division of labor instruction information includes parameter F, parameter G, and parameter H.
  • Scenario 2 UE#1 receives the initial session call.
  • the network device sends a session call request to UE#1.
  • the session call request is used to request the processing requirements of the XR call of UE#1.
  • UE#1 sends a session call response to the network device.
  • the session call response in step 5122 carries the processing requirements of the XR call of UE#1.
  • processing capability of UE#1 reported by UE#1 in step 501 can also be sent in step 5122. That is, method 500 may not include 501, and in step 5122, the session call response includes the processing capabilities of UE#1.
  • the network device determines the division of labor instruction information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the session call response in step 5122 includes the processing requirements of the XR call.
  • step 5112 For how the network device determines the implementation of the division of labor instruction information, refer to the relevant description in step 5112, which will not be described again here.
  • the network device sends division of labor instruction information to UE#1.
  • step 5113 Regarding the division of labor instruction information, refer to the relevant description in step 5113, which will not be described again here.
  • Scenario 3 UE#1 initiates a session update call.
  • UE#1 sends a session update call request to the network device.
  • the network device determines the division of labor instruction information based on the updated XR call processing requirements and the processing capability of UE#1.
  • the network device can determine a new processing requirement based on the updated XR call processing requirements and the processing capability of UE#1 division of labor instruction information.
  • the network device sends division of labor instruction information to UE#1.
  • Steps 5131 to 5133 are similar to steps 5111 to 5113 and will not be described again here.
  • Scenario 4 UE#1 receives a session update call.
  • UE#1 sends a session update call response to the network device.
  • the network device can determine a new processing requirement based on the updated XR call processing requirements and the processing capability of UE#1 division of labor instruction information.
  • the network device sends division of labor instruction information to UE#1.
  • Steps 5141 to 5144 are similar to steps 5121 to 5124, and will not be described again here.
  • UE#1 determines the XR object to be rendered that the network device is responsible for rendering based on the division of labor instruction information.
  • One possible implementation is that if the division of labor instruction information includes the parameter G, that is, the division of labor instruction information includes the XR object to be rendered that the network device is responsible for rendering, then UE#1 can directly determine the XR object that the network device is responsible for rendering based on the parameter G. Render XR objects.
  • UE#1 sends the XR object to be rendered that the network device is responsible for rendering to the network device.
  • UE#1 can send relevant data of the XR object that needs to be rendered by the network device to the network device. For example, if the network device is responsible for rendering "virtual chair” and “virtual table”, UE#1 can send the position coordinates of the "virtual table” and "virtual chair” in the video screen to the network device.
  • the network device renders the XR object to be rendered that the network device is responsible for rendering.
  • the network device If the network device is responsible for rendering the “virtual chair” and “virtual table”, and the network device receives the position coordinates of the "virtual table” and “virtual chair” in the video screen from UE#1, the network device can render the “virtual table” according to the “virtual table” " and “virtual chair” in the video screen to render the "virtual table” and "virtual chair”.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends the media data corresponding to the rendered XR object to the network device.
  • UE#1 After UE#1 completes rendering, it sends the media data of the rendered XR object (for example, the rendered "virtual conference room" in the above example) to the network device.
  • the media data of the rendered XR object for example, the rendered "virtual conference room” in the above example
  • the network device merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the network device to obtain merged media data.
  • the network device After the network device receives the media data corresponding to the rendered XR object of UE#1 (for example, the rendered "virtual conference room” in the above example), it can receive the media data corresponding to the rendered XR object of UE#1. Merge the media data corresponding to the XR objects rendered by the network device (for example, the rendered "virtual table” and "virtual chair” in the above example).
  • the network device can synthesize the XR object video stream rendered by the network side and the XR object video stream rendered by UE#1 in the renderer according to the video frames with the same timestamp.
  • the foreground, background, and occlusion, shadow and other relationships thereby outputting a complete video frame image frame by frame to form a video image sequence, which can be sent to the terminal device in the form of a video stream.
  • the following mainly takes sending in the form of a video stream as an example for illustrative explanation.
  • the network device sends the combined media data to UE#2.
  • the network device sends the combined video stream to UE#2.
  • UE#2 indicates the UE involved in the call service and is the opposite end UE of UE#1. For example, there is an XR call service between UE#1 and UE#2, and the network device sends the combined video stream to UE#2. In this way, UE#2 can display the rendered XR based on the received video image sequence. Object, allowing the user of UE#2 to see the XR object with 3D effect. It can be understood that the network device can directly send the combined video stream to UE#2, or can also send the combined video stream through other devices (such as the network device to which UE#2 belongs) without restriction. It can be understood that UE#1 can have XR calls (ie conferences) with multiple UEs, and the network device sends the combined video streams to the multiple UEs respectively.
  • the network device can also send the combined media data to UE#1, so that UE#1 can also display the rendered XR object, so that the user of UE#1 can see the XR object with a 3D effect.
  • the terminal device reports its own processing capabilities to the network device, and the network device can also notify the terminal device of its own processing capabilities, that is, the terminal device and the network device can exchange their respective processing capabilities.
  • the terminal device determines that the network device supports XR object rendering, it can carry the XR call processing requirements in the session call request and request rendering negotiation with the network device.
  • the network device can calculate the XR object rendering computing power requirements based on the processing requirements of the XR call, and determine whether the available computing power for rendering of the terminal device is exceeded. If the available computing power for rendering of the terminal device is exceeded, the network device's own processing capabilities can also be combined to determine the rendering division of labor for this session, and the rendering negotiation results will be notified to the terminal device.
  • the terminal device can determine which XR objects are rendered on the terminal device and which XR objects are rendered on the network device. For XR objects that require rendering by network devices, the terminal device can send data to be rendered by the network device to the network device. Finally, the network device can correspond to its own rendered XR object The media data corresponding to the XR object rendered by the terminal device is merged, and the merged media data is sent to the terminal device involved in this session.
  • the terminal device or network device can initiate a session update request, based on the updated XR call processing requirements Re-negotiate the rendering.
  • the division of labor is determined by the network device (such as steps 5112, 5123, etc.), and there is no restriction on this.
  • the division of labor can also be determined by the terminal device.
  • UE#1 may determine the division of labor indication information based on the processing requirements of the XR call and the processing capability information of UE#1 (for details, please refer to the description in step 5112), and then perform steps 521 to 527.
  • UE#1 may also send division of labor indication information to the network device.
  • UE#1 sends an XR object rendering request to the network device, and the network device returns an XR object rendering response.
  • the response contains indication information, which indicates that the network device will render the XR object for UE#1;
  • UE#1 confirms that the network
  • the XR object rendering response returned by the network device may also include the processing capability information of the network device (similar to the processing capability information of UE#1 in step 5112). In this way, UE#1 can perform the processing according to the processing capability information of the network device.
  • the processing capability information and other information determine how to divide the labor (for details, please refer to the description in step 5112), that is, determine which part of the XR objects to be rendered should be rendered by the network device, and then perform step 522.
  • the network device can decide to leave all the current remaining processing capabilities for the rendering of the XR object of UE#1, or it can decide to leave part of the current remaining processing capabilities for the rendering of the XR object of UE#1, that is, That is, the processing capability information returned by the network device through the XR object rendering response can represent all the current remaining processing capabilities of the network device, or can also represent a part of all the current remaining processing capabilities.
  • the network device leaves 5% of all current remaining processing capabilities for UE#1's rendering of the The processing capability allocates XR objects to be rendered to network devices, so as to prevent UE#1 from allocating too many rendering tasks of XR objects to network devices, or preventing network device resources from being monopolized by one UE.
  • the network device merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the network device as an example to illustrate.
  • UE#2 may perform the combining process.
  • UE#1 sends media data corresponding to the rendered XR object to UE#2
  • the network device sends media data corresponding to the rendered XR object to UE#2.
  • UE#2 performs merge processing.
  • other devices may also perform the merging process, which will not be described again.
  • Figure 6 is a schematic flow chart of an XR object rendering method 600 provided by an embodiment of the present application.
  • This method 600 can be used to implement the solution of the above method 400.
  • This method 600 can be used in the scenario of DC-based rendering negotiation, and the rendering negotiation can be performed after the DC is established, for example.
  • the first network device is an XR-C network element
  • the second network device is an XR-M network element
  • the IMS includes one or more network elements.
  • IMS stands for.
  • the method 600 shown in FIG. 6 may be used in the FIG. 1 architecture.
  • the method 600 may include the following steps.
  • UE#1 sends the processing capability of UE#1 to IMS.
  • UE#1 sends the processing capabilities of UE#1 to the IMS.
  • UE#1 sends a SIP registration (REGISTER) message to IMS, and the SIP REGISTER message carries the processing capabilities of UE#1.
  • the processing capabilities of UE#1 can be carried in the header field of SIP signaling (such as SIP REGISTER message).
  • processing capabilities of UE#1 are in the form:
  • split_rendering_method represents parameter A, which is the rendering division method supported by UE#1.
  • “rendering_capability” represents parameter B, which is the available rendering computing power of UE#1.
  • the value of “split_rendering_method” is 0 and 1, indicating that the supported rendering division methods include division of labor by layer and division of labor by type.
  • parameter A and parameter B refer to the previous relevant descriptions and will not repeat them here.
  • IMS sends the processing capabilities of UE#1 to the XR-C network element.
  • IMS After IMS successfully registers and authenticates UE#1, it forwards the processing capabilities of UE#1 to the XR-C network element. As an example, IMS sends an HTTP message to the XR-C network element, and the HTTP message carries the processing capability of UE#1.
  • the XR-C network element saves the processing capability of UE#1.
  • the method 500 also includes steps 604 to 606.
  • the XR-C network element sends the processing capabilities of the XR-M network element to the IMS.
  • One possible implementation method is that the XR-C network element sends an HTTP response message (such as a 200 message) to the IMS, and the HTTP response message includes the processing capability of the XR-M network element.
  • an HTTP response message such as a 200 message
  • IMS sends the processing capability of the XR-M network element to UE#1.
  • UE#1 determines that the XR-M network element can render the XR object.
  • Steps 604 to 606 are optional steps, that is, the XR-C network element does not need to provide the processing capability of the XR-M network element to UE#1, and UE#1 can default to the XR-M network element being able to render XR objects.
  • Audio and video media channel establishment and DC establishment are 607. Audio and video media channel establishment and DC establishment.
  • UE#1 When UE#1 initiates an XR call or receives an XR call, it can first establish an audio and video media channel with the IMS, and establish a DC between UE#1 and the IMS.
  • the DC between UE#1 and IMS can be used to transmit signaling or data between UE#1 and IMS, such as information related to rendering division of labor interaction and/or related data of XR objects, etc. It can be understood that the signaling for the interaction between UE#1 and IMS mentioned below can be transmitted through the DC.
  • the following describes the rendering negotiation process based on two scenarios.
  • Scenario 1 UE#1 initiates rendering negotiation.
  • UE#1 sends rendering negotiation request information to IMS.
  • processing capability of UE#1 reported by UE#1 in step 601 can also be sent in step 6111. That is, method 600 may not include step 601, and in step 6111, the rendering negotiation request information includes the processing capability of UE#1.
  • the rendering negotiation request information includes processing requirements for the XR call.
  • UE#1 defaults to the XR-M network element supporting XR object rendering. Therefore, UE#1 carries the processing requirements of the XR call in the rendering negotiation request information.
  • UE#1 determines whether the XR-M network element supports media rendering based on the processing capability of the XR-M network element received in step 605. If UE#1 determines that the XR-M network element supports XR object rendering, UE#1 carries the processing requirements of the XR call in the rendering negotiation request information. If UE#1 determines that the XR-M network element does not support XR object rendering, UE#1 does not carry the processing requirements for the XR call in the rendering negotiation request information. For the case where the XR-M network element does not support XR object rendering, as an example, UE#1 can perform the rendering process by itself. The embodiment of this application mainly introduces the situation in which XR-M network elements support XR object rendering.
  • the XR call processing requirements include parameter C, parameter D, and parameter E.
  • parameter C parameter C
  • parameter D parameter D
  • parameter E parameter E
  • processing requirements for an XR call would be of the form:
  • rendering_content represents parameter C, which is the XR object to be rendered.
  • video_resolution represents parameter D, which is the video resolution.
  • video_frame_rate represents parameter E, which is the video frame rate.
  • IMS sends an HTTP request message to the XR-C network element.
  • the HTTP request message in step 6112 also includes the processing requirements for the XR call.
  • the XR-C network element determines the division of labor indication information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the HTTP message in step 6112 includes the processing requirements of the XR call.
  • the XR-C network element generates the processing requirements for XR calls.
  • the XR-C network element generates XR call processing requirements based on XR application business logic and session parameters.
  • the XR-C network element determines the division of labor indication information, it can also comprehensively consider: the processing capabilities of the XR-M network element, the processing capabilities of UE#1, and the processing requirements of the XR call. Further optionally, the XR-M network element sends the processing capability of the XR-M network element to the XR-C network element. Regarding the implementation method of determining the division of labor instruction information, reference may be made to the relevant description in step 5112, which will not be described again here.
  • the XR-C network element sends division of labor instruction information to the IMS.
  • the XR-C network element sends an HTTP response message to the IMS.
  • the HTTP response message carries the rendering negotiation result of this XR call, that is, the division of labor indication information.
  • the division of labor instruction information includes at least one of the following: parameter F, parameter G, parameter H.
  • parameter F parameter F
  • parameter G parameter H
  • step 5113 the relevant descriptions in will not be repeated here.
  • the form of division of labor instruction information is as follows:
  • split_rendering_method represents parameter F, which is the rendering division method of the XR call.
  • the value definition of parameter F is the same as the value of parameter A in step 601.
  • network_rendering_content represents parameter G, that is, the XR object to be rendered that the XR-M network element is responsible for rendering.
  • the value definition of parameter G is the same as the value of parameter C in step 6111.
  • IMS sends labor division indication information to UE#1.
  • the IMS After receiving the division of labor instruction information sent by the XR-C network element, the IMS forwards the division of labor instruction information to UE#1.
  • One possible implementation manner is that the IMS sends a rendering negotiation response to UE#1, and the rendering negotiation response carries division of labor indication information.
  • the XR-C network element applies for resources from the XR-M network element.
  • the XR-C network element When the XR-C network element determines that it needs to render XR objects on the XR-M network element side according to the division of labor instruction information, it can apply for resources from the XR-M network element, that is, request the XR-M network element to render the objects that the XR-M network element is responsible for rendering. Render XR objects.
  • One possible implementation method is that the XR-C network element sends an HTTP request message to the XR-M network element. The HTTP request message is used to apply to the XR-M network element for resources related to rendering XR objects.
  • the XR-C network element's application for resources from XR-M includes: the XR-C network element requests the XR-M network element to create or allocate endpoint resources.
  • the XR-M network element creates or allocates the corresponding resource endpoint. (also called media endpoint), and returns the corresponding resource endpoint information (corresponding to the address information of the network-side rendering device in the content of the invention) to the XR-C network element.
  • the XR-M network element creates or allocates two resource endpoints, namely the first resource endpoint and the second resource endpoint.
  • the attributes of the first resource endpoint include the local connection address of the first resource endpoint.
  • the attributes of the second resource endpoint include the local connection address of the second resource endpoint, where the local connection address of the first resource endpoint and the local connection address of the second resource endpoint are respectively used to enable UE#1 to pass the IMS (UE The IMS accessed by #1) establishes a communication connection with the XR-M network element, and enables UE#2 to establish a communication connection with the XR-M network element through the IMS (IMS accessed by UE#2).
  • the XR-M network element returns the resource application result to the XR-C network element, including at least one of the following: result indication information and resource endpoint information.
  • the result indication information can be used to notify the XR-C network element whether the XR-M network element will render the XR object to be rendered that the XR-M network element is responsible for rendering.
  • the XR-C network element can request the UE #1 sends transmission instruction information to instruct UE#1 to send the XR object to be rendered that the XR-M network element is responsible for rendering to the XR-M network element.
  • the resource endpoint information includes the local connection address of the first resource endpoint and the local connection address of the second resource endpoint.
  • the XR-C network element can send the The call session control function (proxy-call session control function, P-CSCF) network element) sends the local connection address of the first resource endpoint to facilitate the IMS (such as the multimedia subsystem access gateway (IMS access gateway) controlled by the P-CSCF , IMS-AGW)) communicates with the XR-M network element through the local connection address of the first resource endpoint.
  • the call session control function proxy-call session control function, P-CSCF
  • IMS multimedia subsystem access gateway
  • IMS-AGW multimedia subsystem access gateway
  • UE#1 sends to the XR-M network element through IMS-AGW the to-be-rendered message that the XR-M network element is responsible for rendering.
  • XR objects For example, UE#1 has a connection with IMS-AGW, such as a first connection (the connection can also be understood as a channel).
  • IMS can establish IMS-AGW through the local connection address of the first resource endpoint sent by the XR-C network element.
  • a second connection with the XR-M network element and establishes a corresponding relationship between the first connection and the second connection.
  • IMS-AGW to receive the to-be-rendered message sent by UE#1 and is responsible for rendering by the XR-M network element.
  • the second connection can be determined, and the XR object to be rendered, which is responsible for rendering by the XR-M network element, can be forwarded to the XR-M network element through the second connection.
  • the resource endpoint information and labor division indication information may be carried in one signaling or message, or may be carried in different signaling or messages, without limitation.
  • the resource endpoint information returned by the XR-M network element to the P-CSCF sends the local connection address of the second resource endpoint, so that UE#2 communicates with the XR-M network element through the IMS.
  • UE#2 obtains the merged media from the XR-M network element through the IMS. data.
  • the XR-C network element may send the local value of the second resource endpoint to the P-CSCF in the accessed IMS.
  • the connection address is used to facilitate UE#2 to connect to the XR-M network element through the IMS-AGW controlled by the P-CSCF, so that UE#2 can obtain the combined media data from the XR-M network element through IMS-AGW.
  • step 6114 and step 6116 are not limited.
  • step 6114 is executed first, and then step 6116 is executed. That is, after the XR-C network element determines the division of labor indication information, it directly sends the division of labor indication information to UE#1 through IMS.
  • the local connection address and division of labor indication information can be carried in different signaling, that is, the XR-C network element first sends the division of labor indication information to UE#1 through IMS, and then receives the division of labor indication information from the XR-M network element After the local connection address is obtained, the local connection address is sent to the IMS.
  • step 6116 is executed first, and then step 6114 is executed. That is, after the XR-C network element determines the division of labor indication information, it can first apply for resources from the XR-M network element, and then send the division of labor indication information to UE#1 through IMS. In this case, after receiving the local connection address from the XR-M network element, the XR-C network element sends the division of labor instruction information and the local connection address to the IMS. As an example, the local connection address and labor division indication information can be carried in one signaling.
  • Scenario 2 UE#1 initiates re-rendering negotiation.
  • UE#1 sends re-rendering negotiation request information to IMS.
  • the terminal device may initiate a re-rendering negotiation.
  • UE#1 may send a re-rendering negotiation request message to the IMS to re-negotiate the rendering of the XR call.
  • IMS sends an HTTP message to the XR-C network element.
  • the XR-C network element determines the division of labor indication information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the XR-C network element can be based on the updated processing requirements of the XR call and the processing capability of UE#1. information to determine new division of labor instruction information.
  • the XR-C network element sends labor division instruction information to the IMS.
  • IMS sends labor division indication information to UE#1.
  • Steps 6121 to 6125 are similar to steps 6111 to 6115 and will not be described again here.
  • the XR-C network element applies to the XR-M network element to update rendering resources.
  • the XR-C network element determines that it needs to update the rendering on the XR-M network element side according to the division of labor instruction information, it can apply to the XR-M network element to update the rendering resources, that is, after requesting the XR-M network element to update the rendering division of labor, the XR-M network element
  • the XR object to be rendered that is responsible for rendering.
  • One possible implementation method is that the XR-C network element sends an HTTP message to the XR-M network element, and the HTTP message is used to apply for resource modification. For details, please refer to the description in step 6116, which will not be described again here.
  • the XR-M network element can re-create the endpoint resources or reuse the endpoint resources created or allocated in step 6116; the XR-M network element can reuse the computing resources reserved or allocated in step 6116.
  • the computing power resources may also be reallocated, and the reallocated computing power resources may be different from the computing power resources reserved or allocated in step 6116.
  • UE#1 determines the XR object to be rendered that the XR-M network element is responsible for rendering according to the division of labor instruction information.
  • Step 621 is similar to step 521 and will not be described again here.
  • UE#1 sends the XR object to be rendered that the XR-M network element is responsible for rendering to the XR-M network element.
  • UE#1 can send relevant data of XR objects that need to be rendered by the XR-M network element to the XR-M network element. For example, if the XR-M network element is responsible for rendering a "virtual character", UE#1 can send the action posture data needed to drive the virtual human to the XR-M network element.
  • UE#1 sends the XR object to be rendered that is responsible for rendering by the XR-M network element to IMS (such as DCS-M or IMS-AGW) through Application DC, and IMS will The rendered XR object to be rendered is forwarded to the XR-M network element.
  • IMS such as DCS-M or IMS-AGW
  • the XR-M network element renders the XR object to be rendered that the XR-M network element is responsible for rendering.
  • the XR-M network element can render the "virtual character" based on the data. To render.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends the media data corresponding to the rendered XR object to the XR-M network element.
  • UE#1 After UE#1 completes rendering, it sends the media data corresponding to the rendered XR object to the XR-M network element.
  • the XR-M network element merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the XR-M network element to obtain merged media data.
  • the XR-M network element sends the combined media data to UE#2.
  • Step 627 is similar to step 527 and will not be described again here.
  • step 625 the transmission between the XR-M network element and UE#1 in step 625 and the transmission between the XR-M network element and UE#2 in step 627 is similar to step 622, and will not be described again.
  • the XR-C network element can also combine the processing capabilities of the XR-M network element to decide the rendering division of labor for this session, and notify the terminal device of the rendering negotiation results.
  • the XR-C network element applies for media rendering resources from the XR-M network element.
  • the terminal device can determine which XR objects are rendered on the terminal device and which XR objects are rendered on the XR-M network element. For XR objects that require XR-M network element rendering, the terminal device can send the XR-M network element's data to be rendered to the XR-M network element.
  • the XR-M network element can merge the media data corresponding to the XR object rendered by itself and the media data corresponding to the XR object rendered by the terminal device, and send the merged media data to the terminal involved in this session. equipment.
  • the media rendering task may need to be re-divided due to some circumstances during the session, such as changes in the processing requirements of the Render negotiation.
  • the division of labor is determined by the XR-C network element (such as steps 6113, 6123, etc.), and there is no restriction on this.
  • the division of labor can also be determined by the terminal device.
  • UE#1 may determine the division of labor indication information based on the processing requirements of the XR call and the processing capability information of UE#1 (for details, please refer to the description in step 6113), and then perform steps 621 to 627.
  • UE#1 may also send division of labor indication information to the XR-C network element.
  • UE#1 sends an XR object rendering request to the XR-C network element, and the XR-C network element returns an XR object rendering response.
  • the response contains indication information, and the indication information indicates that the XR-C network element will be UE#1.
  • Render the XR object after UE#1 confirms that the XR-C network element will assist in rendering the XR object, it determines the XR object to be rendered that the XR-C network element is responsible for rendering, and then performs step 622.
  • the XR object rendering response returned by the XR-C network element may also include the processing capability information of the XR-C network element (similar to the processing capability information of UE#1 in step 6113). In this way, UE# 1. How to divide the work can be determined based on the processing capability information of the XR-C network element and other information (for details, please refer to the description in step 6113), that is, determine which part of the XR objects to be rendered should be rendered by the XR-C network element, and then perform step 622.
  • the XR-M network element can leave all the current remaining processing capabilities to the rendering of the XR object of UE#1, or can also leave part of the current remaining processing capabilities of the XR-M network element to the XR of UE#1 Object rendering, that is to say, the processing capability information returned by the XR-C network element through the XR object rendering response can represent all the current remaining processing capabilities of the XR-M network element, and can also represent all the current remaining processing capabilities of the XR-M network element. part of the ability.
  • the XR-M network element leaves 5% of all current remaining processing capabilities for the rendering of the XR object of UE#1, that is, the processing capability information returned by the XR-C network element represents this %5 processing capability, so that UE#1 allocates XR objects to be rendered to the XR-M network element based on the 5% processing capacity.
  • This can prevent UE#1 from assigning too many XR object rendering tasks to the XR-M network element, or avoid XR-M
  • the resources of the network element are exclusively occupied by one UE.
  • FIG. 7 is a schematic flow chart of an XR object rendering method 700 provided by an embodiment of the present application.
  • This method 700 can be used to implement the solution of the above method 400.
  • This method 700 can be used in a scenario where rendering negotiation is performed based on IMS SIP signaling.
  • the rendering negotiation can be completed during the call establishment process, for example.
  • the first network device is an AS
  • the second network device is an MRF network element.
  • the MRF network element may include, for example, MRFC and MRFP.
  • the IMS may include one or more network elements.
  • the architecture shown in Figure 2 which will be collectively referred to as “IMS core” below.
  • the method 700 shown in Figure 7 can be used with the Figure 2 architecture.
  • the method 700 may include the following steps.
  • UE#1 sends the processing capabilities of UE#1 to the IMS core network (IMS core).
  • IMS core IMS core network
  • Step 701 is similar to step 601 and will not be described again here.
  • IMS core sends the processing capabilities of UE#1 to the AS.
  • the IMS core After the IMS core successfully registers and authenticates UE#1, it forwards the processing capabilities of UE#1 to the AS. As an example, IMS core sends a SIP REGISTER message to the AS. The SIP REGISTER message carries the processing capabilities of UE#1.
  • the method 700 also includes steps 704 to 706.
  • the AS sends the processing capabilities of the MRF network element to the IMS core.
  • IMS core sends the processing capability of the MRF network element to UE#1.
  • UE#1 determines that the MRF network element can render the XR object.
  • Steps 704 to 706 are optional steps, that is, the AS does not need to provide the processing capability of the MRF network element to UE#1, and UE#1 can default to the MRF network element being able to render XR objects.
  • Scenario 1 UE#1 initiates XR call establishment.
  • UE#1 sends an invitation (INVITE) message to IMS core.
  • IMS core an invitation (INVITE) message
  • processing capability of UE#1 reported by UE#1 in step 701 can also be sent in step 7111. That is, method 700 may not include step 701, and in step 7111, the INVITE message includes the processing capabilities of UE#1.
  • the INVITE message includes processing requirements for the XR call.
  • UE#1 defaults to the MRF network element that supports XR object rendering. Therefore, UE#1 carries the processing requirements of the XR call in the INVITE message.
  • UE#1 determines whether the MRF network element supports media rendering based on the processing capability of the MRF network element received in step 705. If UE#1 determines that the MRF network element supports XR object rendering, UE#1 carries the processing requirements of the XR call in the INVITE message. If UE#1 determines that the MRF network element does not support XR object rendering, UE#1 does not carry the processing requirements for the XR call in the INVITE message. For the case where the MRF network element does not support XR object rendering, as an example, UE#1 can perform the rendering process by itself. The embodiment of this application mainly introduces how MRF network elements support XR object rendering.
  • the XR call processing requirements include parameter C, parameter D, and parameter E.
  • parameter C parameter C
  • parameter D parameter D
  • parameter E parameter E
  • processing requirements for an XR call would be of the form:
  • rendering_content represents parameter C, which is the XR object to be rendered.
  • video_resolution represents parameter D, which is the video resolution.
  • video_frame_rate represents parameter E, which is the video frame rate.
  • IMS core sends an INVITE message to AS.
  • the INVITE message in step 7111 includes the processing requirements for the XR call
  • the INVITE message in step 7112 also includes the processing requirements for the XR call.
  • the AS determines the division of labor instruction information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the INVITE message in step 7112 includes the processing requirements for the XR call.
  • the AS to generate processing requirements for XR calls.
  • the AS generates processing requirements for XR calls based on the XR application business logic and session parameters.
  • the AS may comprehensively consider: the processing capabilities of the MRF network element, the processing capabilities of UE#1, and the processing requirements of the XR call. Further optionally, the MRF network element sends the processing capability of the MRF network element to the AS. Regarding the implementation method of determining the division of labor instruction information, reference may be made to the relevant description in step 5112, which will not be described again here.
  • AS sends division of labor instruction information to IMS core.
  • One possible implementation method is that the AS sends an 18X For INVITE message or a 200 For INVITE message to the IMS core.
  • the 18X For INVITE message or the 200 For INVITE message carries the rendering negotiation result of this XR call, that is, the division of labor instruction information.
  • PRACK For INVITE message or acknowledgment response (ACKnowledgement, ACK) For INVITE message.
  • the PRACK For INVITE message or ACK For INVITE message carries the rendering negotiation result of this XR call, that is, the division of labor indication information.
  • the division of labor instruction information includes at least one of the following: parameter F, parameter G, parameter H.
  • parameter F parameter F
  • parameter G parameter H
  • step 5113 the relevant description in step 5113, which will not be described again here.
  • the form of division of labor instruction information is as follows:
  • step 6115 please refer to the relevant description in step 6115, which will not be described again here.
  • IMS core sends division of labor instruction information to UE#1.
  • IMS core After receiving the division of labor instruction information sent by the AS, IMS core forwards the division of labor instruction information to UE#1.
  • the IMS core sends an 18X For INVITE message or a 200 For INVITE message to UE#1, and the 18X For INVITE message or the 200 For INVITE message carries division of labor indication information.
  • the AS determines that it needs to render an XR object on the MRF network element side based on the division of labor instruction information, it can apply for resources from the MRF network element, that is, request the MRF network element to render the XR object to be rendered that the MRF network element is responsible for rendering.
  • One possible implementation method is that the AS sends an INVITE message to the MRF network element. The INVITE message is used to apply to the MRF network element for resources related to rendering XR objects.
  • the AS applying for resources from the MRF includes: the AS requests the MRF network element to create or allocate endpoint resources.
  • the MRF network element creates or allocates the corresponding resource endpoint (also called media endpoint), and assigns the corresponding resource endpoint to the MRF network element.
  • the information (corresponding to the address information of the network-side rendering device in the content of the invention) is returned to the AS.
  • the MRF network element creates or allocates two resource endpoints, namely the first resource endpoint and the second resource endpoint.
  • the attributes of the first resource endpoint include the local connection address of the first resource endpoint
  • the The attributes of the second resource endpoint include the local connection address of the second resource endpoint, where the local connection address of the first resource endpoint and the local connection address of the second resource endpoint are respectively used to enable UE#1 to pass the IMS core (UE#
  • the IMS core accessed by UE#2 establishes a communication connection with the MRF network element, and enables UE#2 to establish a communication connection with the MRF network element through the IMS core (IMS core accessed by UE#2).
  • the AS applying for resources from the MRF may also include: the AS requests the MRF network element to reserve or allocate computing power resources.
  • the MRF network element reserves or allocates the corresponding computing power resources, such as memory or CPU time slots. or GPU resources, etc.; optionally, the AS sends the information of the XR object to be rendered or the XR computing power requirement to the MRF network element.
  • the XR computing power requirement represents the computing power required for the XR object to be rendered by the MRF network element.
  • the MRF network element can reserve or allocate corresponding computing power resources based on the information of the XR object to be rendered or the XR computing power requirements.
  • the MRF network element returns the resource application result to the AS, including at least one of the following: result indication information and resource endpoint information.
  • the result indication information can be used to notify the AS whether the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering.
  • the AS can send transmission instruction information to UE#1 to instruct UE#1 Send the XR object to be rendered that the MRF network element is responsible for rendering to the MRF network element.
  • the resource endpoint information includes the local connection address of the first resource endpoint and the local connection address of the second resource endpoint.
  • the AS can send the first resource endpoint to the IMS core (for example, the P-CSCF network element in the IMS core).
  • the local connection address of the resource endpoint so that the IMS core (such as the IMS-AGW controlled by P-CSCF) communicates with the MRF network element through the local connection address of the first resource endpoint.
  • the IMS core such as the IMS-AGW controlled by P-CSCF
  • UE#1 communicates with the MRF network through the IMS-AGW.
  • the element sends the XR object to be rendered which is responsible for rendering by the MRF network element.
  • UE#1 has a connection with IMS-AGW, such as a third connection (the connection can also be understood as a channel).
  • IMS core can establish the connection between IMS-AGW and IMS-AGW through the local connection address of the first resource endpoint sent by the AS network element.
  • the fourth connection of the MRF network element and establishes the corresponding relationship between the third connection and the fourth connection. This corresponding relationship allows IMS-AGW to receive the XR object to be rendered sent by UE#1 and is responsible for rendering by the MRF network element.
  • the fourth connection is determined, and the XR object to be rendered that is responsible for rendering by the MRF network element is forwarded to the MRF network element through the fourth connection.
  • the resource endpoint information and labor division indication information may be carried in one signaling or message, or may be carried in different signaling or messages, without limitation.
  • the AS can also send the second resource endpoint to the IMS core (for example, the P-CSCF in the IMS core accessed by UE#2).
  • the local connection address of the resource endpoint so that UE#2 can communicate with the MRF network element through the IMS core. For example, UE#2 obtains the merged media data from the MRF network element through the IMS core.
  • the AS can send the local connection address of the second resource endpoint to the P-CSCF in the IMS core, so that UE#2 can connect to the MRF network element through the IMS-AGW controlled by the P-CSCF, so that UE#2 can pass IMS-AGW slave MRF network element Get the merged media data.
  • step 7114 and step 7116 is not limited.
  • step 7114 is executed first, and then step 7116 is executed. That is, after the AS determines the division of labor instruction information, it directly sends the division of labor instruction information to UE#1 through the IMS core.
  • the local connection address and labor division indication information can be carried in different signaling, that is, the AS first sends the division of labor indication information to UE#1 through the IMS core, and then receives the local connection address from the MRF network element. Then, send the local connection address to IMS core.
  • step 7116 is executed first, and then step 7114 is executed. That is, after the AS determines the division of labor indication information, it can first apply for resources from the MRF network element, and then send the division of labor indication information to UE#1 through the IMS core. In this case, after receiving the local connection address from the MRF network element, the AS sends the division of labor instruction information and the local connection address to the IMS core.
  • the local connection address and labor division indication information can be carried in one signaling.
  • Scenario 2 UE#1 receives XR call call establishment.
  • AS sends INVITE message to IMS core.
  • the INVITE message is used to request the processing requirements of the XR call of UE#1.
  • IMS core sends an INVITE message to UE#1.
  • the INVITE message in step 7121 is used to request the processing requirements of the XR call of UE#1
  • the INVITE message in step 7122 is used to request the processing requirements of the XR call of UE#1.
  • UE#1 sends a 200 For INVITE message to the IMS core.
  • the 200 For INVITE message in step 7123 carries the processing requirements of the XR call of UE#1.
  • processing capability of UE#1 reported by UE#1 in step 701 can also be sent in step 7123. That is, method 700 may not include 701, and in step 7123, the 200 For INVITE message includes the processing capabilities of UE#1.
  • the 200 For INVITE message in step 7123 can also be replaced by the 18X For INVITE message. There is no restriction on the specific type of the message.
  • IMS core sends 200 For INVITE message to AS.
  • the AS determines the division of labor instruction information based on the processing requirements of the XR call and the processing capability of UE#1.
  • Another possible implementation is for the AS to generate processing requirements for XR calls.
  • another possible implementation is to generate XR call processing requirements based on the XR application business logic and session parameters.
  • the AS may comprehensively consider: the processing capabilities of the MRF network element, the processing capabilities of UE#1, and the processing requirements of the XR call.
  • the AS may comprehensively consider: the processing capabilities of the MRF network element, the processing capabilities of UE#1, and the processing requirements of the XR call.
  • the implementation method of determining the division of labor instruction information reference may be made to the relevant description in step 5112, which will not be described again here.
  • AS sends division of labor instruction information to IMS core.
  • AS applies for resources from the MRF network element.
  • Steps 7126 to 7128 are similar to steps 7114 to 7116, and will not be described again here.
  • Scenario 3 UE#1 initiates XR call update.
  • UE#1 sends a REINVITE message to IMS core.
  • IMS core sends REINVITE message to AS.
  • the AS determines the division of labor instruction information based on the updated XR call processing requirements and the processing capability of UE#1.
  • step 7133 the AS determines the new division of labor based on the updated processing requirements of the XR call and the processing capability of UE#1. Instructions.
  • AS sends division of labor instruction information to IMS core.
  • IMS core sends division of labor instruction information to UE#1.
  • Steps 7131 to 7135 are similar to steps 7111 to 7115 and will not be described again here.
  • AS applies to the MRF network element to update rendering resources.
  • the AS determines that it needs to update the rendering on the MRF network element side based on the division of labor instruction information, it can apply to the MRF network element to update the rendering resources, that is, request the MRF network element to render the XR objects to be rendered that the MRF network element is responsible for rendering after the division of labor is updated.
  • One possible implementation method is that the AS sends a REINVITE message to the MRF network element, and the REINVITE message is used to apply for resource modification. For details, please refer to the description in step 7116, which will not be described again here.
  • the MRF network element can re-create the endpoint resources, or reuse the endpoint resources created or allocated in step 7116; the MRF network element can reuse the computing resources reserved or allocated in step 7116, or reuse them. Allocate computing power resources.
  • the reallocated computing power resources may be different from the computing power resources reserved or allocated in step 7116.
  • Scenario 4 UE#1 receives XR call update.
  • AS sends REINVITE message to IMS core.
  • IMS core sends a REINVITE message to UE#1.
  • UE#1 sends a 200 For REINVITE message to the IMS core.
  • IMS core sends 200 For REINVITE message to AS.
  • the AS determines the division of labor instruction information based on the updated XR call processing requirements and the processing capability of UE#1.
  • step 7145 the AS determines the new division of labor based on the updated processing requirements of the XR call and the processing capability of UE#1. Instructions.
  • AS sends division of labor instruction information to IMS core.
  • the AS sends an ACK For REINVITE message to the IMS core.
  • the ACK For REINVITE message includes labor division indication information.
  • IMS core sends division of labor instruction information to UE#1.
  • IMS core sends an ACK For REINVITE message to UE#1, and the ACK For REINVITE message includes division of labor indication information.
  • Steps 7141 to 7147 are similar to steps 7121 to 7127 and will not be described again here.
  • AS applies to the MRF network element to update rendering resources.
  • the AS determines that it needs to update the rendering on the MRF network element side based on the division of labor instruction information, it can apply to the MRF network element to update the rendering resources, that is, request the MRF network element to render the XR objects to be rendered that the MRF network element is responsible for rendering after the division of labor is updated.
  • One possible implementation method is that the AS sends a REINVITE message to the MRF network element, and the REINVITE message is used to apply for resource modification. For details, please refer to the description in step 7116, which will not be described again here.
  • the MRF network element can re-create the endpoint resources, or reuse the endpoint resources created or allocated in step 7128; the MRF network element can reuse the computing resources reserved or allocated in step 7128, or reuse them. Allocate computing power resources.
  • the reallocated computing power resources may be different from the computing power resources reserved or allocated in step 7128.
  • UE#1 determines the XR object to be rendered that the MRF network element is responsible for rendering based on the division of labor instruction information.
  • Step 721 is similar to step 521 and will not be described again here.
  • UE#1 sends the XR object to be rendered that the MRF network element is responsible for rendering to the MRF network element.
  • UE#1 can send the relevant data of the XR object that needs to be rendered by the MRF network element to the MRF network element. For example, if the MRF network element is responsible for rendering a "virtual human", UE#1 can send the action posture data needed to drive the virtual human to the MRF network element.
  • UE#1 sends the XR object to be rendered that the MRF network element is responsible for rendering to IMS-AGW through the third connection based on the rendering division of the XR object to be rendered in the According to the corresponding relationship, the XR object to be rendered, which is responsible for rendering by the MRF network element, is forwarded to the MRF network element through the fourth connection.
  • the MRF network element renders the XR object to be rendered that the MRF network element is responsible for rendering.
  • the MRF network element can render the "virtual character” based on the data.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends the media data corresponding to the rendered XR object to the MRF network element.
  • UE#1 After UE#1 completes rendering, it sends the media data corresponding to the rendered XR object to the MRF network element.
  • the MRF network element merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the MRF network element to obtain merged media data.
  • the MRF network element sends the combined media data to UE#2.
  • Step 727 is similar to step 527 and will not be described again here.
  • step 725 the transmission between the MRF network element and UE#1 in step 725 and the transmission between the MRF network element and UE#2 in step 727 is similar to step 722, and will not be described again.
  • the terminal device can report its own processing capabilities to the AS during the process of registering to the IMS, and the AS can also notify the terminal device of the processing capabilities of the MRF network element.
  • the terminal device determines that the MRF network element supports XR object rendering, it can carry the XR call processing requirements in the call request and request rendering negotiation.
  • AS can calculate the XR object rendering computing power requirements based on the processing requirements of the XR call, and determine whether the available computing power for rendering of the terminal device is exceeded. If the available computing power for rendering exceeds the terminal device, the AS can also combine the processing capabilities of the MRF network element to decide the rendering division of labor for this session, and notify the terminal device of the rendering negotiation results.
  • the AS applies for media rendering resources from the MRF network element.
  • the terminal device can determine which XR objects are rendered on the terminal device and which XR objects are rendered on the MRF network element.
  • the terminal device can send the data to be rendered by the MRF network element to the MRF network element.
  • the MRF network element can merge the media data corresponding to the XR object rendered by itself and the media data corresponding to the XR object rendered by the terminal device, and send the merged media data to the terminal device involved in this session.
  • the media rendering task may need to be re-divided due to some circumstances during the session, such as changes in the processing requirements of Conduct rendering negotiations.
  • the division of labor is determined by the AS (such as steps 7113, 7125, etc.), and there is no restriction on this.
  • the division of labor can also be determined by the terminal device.
  • UE#1 may determine the division of labor indication information based on the processing requirements of the XR call and the processing capability information of UE#1 (for details, please refer to the description in step 7113), and then perform steps 721 to 727.
  • UE#1 may also send division of labor indication information to the AS.
  • UE#1 sends an XR object rendering request to AS, and AS returns an XR object rendering response.
  • the response contains indication information, which indicates that AS will render the XR object for UE#1; UE#1 confirms that AS will assist in rendering.
  • the XR object is generated, the XR object to be rendered that is responsible for rendering by the AS is determined, and then step 722 is performed.
  • the XR object rendering response returned by the AS can also include the processing capability information of the AS (similar to the processing capability information of UE#1 in step 7113).
  • UE#1 can Wait for the information to determine how to divide the work (for details, please refer to the description in step 7113), that is, determine which part of the XR objects to be rendered belongs to AS rendering, and then perform step 722.
  • the MRF network element can reserve all the current remaining processing capabilities for the rendering of the XR object of UE#1, or it can reserve part of the current remaining processing capabilities of the MRF network element for the rendering of the XR object of UE#1.
  • the processing capability information returned by the AS through the XR object rendering response can represent all the current remaining processing capabilities of the MRF network element, or can also represent a part of the current remaining processing capabilities of the MRF network element.
  • the MRF network element leaves 5% of all current remaining processing capabilities for the rendering of the XR object of UE#1, that is, the processing capability information returned by the AS represents this %5 processing capability, so that UE#1 can use this 5% % of the processing power is allocated to the MRF network element to allocate XR objects to be rendered. This can prevent UE#1 from assigning too many XR object rendering tasks to the MRF network element, or prevent the resources of the MRF network element from being monopolized by one UE.
  • the MRF network element merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the MRF network element as an example for illustration.
  • UE#2 may perform the combining process.
  • UE#1 sends media data corresponding to the rendered XR object to UE#2
  • the MRF network element sends media data corresponding to the rendered XR object to UE#2.
  • UE#2 performs merge processing.
  • other devices may also perform the merging process, which will not be described again.
  • FIG 8 is a schematic flow chart of an XR object rendering method 800 provided by an embodiment of the present application.
  • This method 800 can be used to implement the solution of the above method 400.
  • the method 800 can be used in a scenario where rendering negotiation is completed based on HTTP/HTTPS messages.
  • the rendering negotiation can be completed during the call establishment process, for example.
  • it is assumed that the first network device and the second network device are OTT servers.
  • the method 800 shown in Figure 8 may be used in the Figure 3 architecture.
  • the method 800 may include the following steps.
  • UE#1 sends the processing capability of UE#1 to the OTT server.
  • UE#1 sends processing capabilities to the OTT server during the process of registering with the OTT server. For example, UE#1 sends an HTTP request message to the OTT server, and the HTTP request message carries the processing capability of UE#1.
  • the format of the processing capability information of UE#1 can be json format, as follows:
  • split_rendering_method "0,1"
  • the format of the processing capability information of UE#1 may be XML format, as follows:
  • split_rendering_method represents parameter A, which is the rendering division method supported by UE#1.
  • “rendering_capability” represents parameter B, which is the available rendering computing power of UE#1.
  • the value of "split_rendering_method” is 0 and 1, indicating that the supported rendering division methods include division of labor by layer and division of labor by type.
  • parameter A and parameter B refer to the previous relevant descriptions and will not repeat them here.
  • the OTT server saves the processing capability of UE#1.
  • the OTT server After the OTT server successfully registers and authenticates UE#1, it can save (or record) the processing capability of UE#1.
  • the method 800 also includes steps 803-804.
  • the OTT server sends the processing capability of the OTT server to UE#1.
  • the OTT server sends an HTTP response message to UE#1, where the HTTP response message includes the processing capabilities of the OTT server.
  • UE#1 determines that the OTT server can render XR objects.
  • Steps 803 to 804 are optional steps, that is, the OTT server does not need to provide the OTT server's processing capabilities to UE#1, and UE#1 can default to the OTT server being able to render XR objects.
  • Scenario 1 UE#1 initiates rendering negotiation.
  • UE#1 sends an HTTP request message to the OTT server.
  • processing capability of UE#1 reported by UE#1 in step 801 can also be sent in step 8111. That is, method 800 may not include step 801, and in step 8111, the HTTP request message includes the processing capabilities of UE#1.
  • the HTTP request message includes processing requirements for the XR call.
  • UE#1 defaults to the OTT server supporting XR object rendering. Therefore, UE#1 carries the processing requirements of the XR call in the HTTP request message.
  • UE#1 determines whether the OTT server supports media rendering based on the processing capability of the OTT server received in step 803. If UE#1 determines that the OTT server supports XR object rendering, UE#1 carries the processing requirements of the XR call in the HTTP request message. If UE#1 determines that the OTT server does not support XR object rendering, UE#1 does not carry the processing requirements for the XR call in the HTTP request message. For the case where the OTT server does not support XR object rendering, as an example, UE#1 can perform rendering processing by itself. The embodiment of this application mainly introduces the situation in which the OTT server supports XR object rendering.
  • the XR call processing requirements include parameter C, parameter D, and parameter E.
  • parameter C parameter C
  • parameter D parameter D
  • parameter E parameter E
  • the format of the XR call processing requirements can be json format, as follows:
  • the format of the processing requirements of the XR call may be in XML format, as follows:
  • rendering_content represents parameter C, the XR object to be rendered.
  • video_resolution represents parameter D, which is the video resolution.
  • video_frame_rate represents parameter E, which is the video frame rate.
  • the OTT server determines the division of labor instruction information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the HTTP request message in step 8111 includes the processing requirements for the XR call.
  • the OTT server generates the processing requirements for XR calls.
  • the OTT server generates processing requirements for XR calls based on XR application business logic and session parameters.
  • the OTT server may comprehensively consider: the processing capabilities of the OTT server, the processing capabilities of UE#1, and the processing requirements of the XR call.
  • the implementation method of determining the division of labor instruction information reference may be made to the relevant description in step 5112, which will not be described again here.
  • the OTT server sends labor division instruction information to UE#1.
  • the HTTP response message carries the rendering negotiation result of this XR call, that is, the division of labor indication information.
  • the division of labor instruction information includes at least one of the following: parameter F, parameter G, parameter H.
  • parameter F parameter F
  • parameter G parameter H
  • step 5113 the relevant description in step 5113, which will not be described again here.
  • the format of the division of labor instruction information can be in json format, as follows:
  • network_rendering_content "0,1,2" //Indicates the XR object to be rendered that the OTT server is responsible for rendering
  • the format of the division of labor instruction information may be in XML format, as follows:
  • split_rendering_method represents parameter F, which is the rendering division method.
  • the value definition of parameter F is the same as the value of parameter A in step 801.
  • network_rendering_content represents parameter G, which is the XR object to be rendered that the OTT server is responsible for rendering.
  • the value definition of parameter G is the same as the value of parameter C in step 8111.
  • Scenario 2 UE#1 receives rendering negotiation.
  • the OTT server sends an HTTP request message to UE#1.
  • the HTTP request message is used to request the processing requirements of the XR call of UE#1.
  • UE#1 sends an HTTP response message to the OTT server.
  • the HTTP response message in step 8122 carries the processing requirements of the XR call of UE#1.
  • processing capability of UE#1 reported by UE#1 in step 801 can also be sent in step 8122. That is, method 800 may not include step 801, and in step 8122, the HTTP response message includes the processing capabilities of UE#1.
  • the OTT server determines the division of labor instruction information based on the processing requirements of the XR call and the processing capability of UE#1.
  • the HTTP response message in step 8122 includes the processing requirements of the XR call.
  • Another possible implementation method is that the OTT server generates the processing requirements for XR calls.
  • another possible implementation is to generate XR call processing requirements based on the XR application business logic and session parameters.
  • the OTT server may comprehensively consider: the processing capabilities of the OTT server, the processing capabilities of UE#1, and the processing requirements of the XR call.
  • the implementation method of determining the division of labor instruction information reference may be made to the relevant description in step 5112, which will not be described again here.
  • the OTT server sends labor division instruction information to UE#1.
  • the OTT server sends an HTTP message to UE#1, and the HTTP message includes labor division indication information.
  • Step 8124 is similar to step 8113 and will not be described again here.
  • Scenario 3 UE#1 initiates media rendering renegotiation.
  • UE#1 sends a session update call request to the OTT server.
  • UE#1 sends an HTTP message to the OTT server, where the HTTP message includes a session update call request, or the HTTP message is used to request a session update call.
  • the OTT server determines the division of labor instruction information based on the updated XR call processing requirements and the processing capability of UE#1.
  • the OTT server determines a new Division of labor instruction information.
  • the OTT server sends labor division instruction information to UE#1.
  • Steps 8131 to 8133 are similar to steps 8111 to 8113 and will not be described again here.
  • Scenario 4 UE#1 receives media rendering renegotiation.
  • the OTT server sends a session update call request to UE#1.
  • UE#1 sends a session update call response to the OTT server.
  • the OTT server determines the division of labor instruction information based on the updated XR call processing requirements and the processing capability of UE#1.
  • the OTT server determines a new Division of labor instruction information.
  • the OTT server sends labor division instruction information to UE#1.
  • Steps 8141 to 8144 are similar to steps 8121 to 8124, and will not be described again here.
  • UE#1 determines the XR object to be rendered that the OTT server is responsible for rendering based on the division of labor instruction information.
  • Step 821 is similar to step 521 and will not be described again here.
  • UE#1 sends the XR object to be rendered that the OTT server is responsible for rendering to the OTT server.
  • the OTT server renders the XR object to be rendered that the OTT server is responsible for rendering.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends the media data corresponding to the rendered XR object to the OTT server.
  • UE#1 After UE#1 completes rendering, it sends the media data corresponding to the rendered XR object to the OTT server.
  • the OTT server merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the OTT server to obtain merged media data.
  • the OTT server sends the combined media data to UE#2.
  • Steps 822 to 827 are similar to steps 522 to 527 and will not be described again here.
  • the above method 800 is mainly illustrated by taking an OTT server as an example.
  • the OTT server may include a signaling server (also known as an OTT signaling server), a media processing server (also known as an OTT media server). , or OTT media processing server), routing server, different servers can perform different functions.
  • the first network device is a signaling server
  • the second network device is a media processing server.
  • the terminal device when the terminal device registers with the OTT server, the terminal device and the OTT server can exchange their respective processing capabilities.
  • the terminal device determines that the OTT server supports XR object rendering, it can carry the XR call processing requirements in the session call request and request rendering negotiation with the OTT server.
  • the OTT server can calculate the XR object rendering computing power requirements based on the processing requirements of the XR call, and determine whether the available computing power for rendering of the terminal device is exceeded. If the available computing power for rendering of the terminal device is exceeded, the OTT server's own processing capabilities can also be combined to determine the rendering division of labor for this session, and the rendering negotiation results will be notified to the terminal device.
  • the terminal device can determine which XR objects are rendered on the terminal device and which XR objects are rendered on the OTT server. For XR objects that require rendering by the OTT server, the terminal device can send the data to be rendered by the OTT server to the OTT server. Finally, the OTT server can merge the media data corresponding to the XR object rendered by itself and the media data corresponding to the XR object rendered by the terminal device, and send the merged media data to the terminal device involved in this session.
  • the terminal device or the OTT server can initiate a session update request, based on the updated processing requirements of the XR call Re-negotiate the rendering.
  • the division of labor is determined by the OTT server (such as steps 8112, 8123, etc.), and there is no restriction on this.
  • the division of labor can also be determined by the terminal device.
  • UE#1 may determine the division of labor indication information based on the processing requirements of the XR call and the processing capability information of UE#1 (for details, please refer to the description in step 8112), and then perform steps 821 to 827.
  • UE#1 may also send division of labor indication information to the OTT server.
  • UE#1 sends an XR object rendering request to the OTT server, and the OTT server returns an XR object rendering response.
  • the response contains indication information, which indicates that the OTT server will render the XR object for UE#1; UE#1 confirms the OTT After the server assists in rendering the XR object, it determines the XR object to be rendered that the OTT server is responsible for rendering, and then performs step 822.
  • the XR object rendering response returned by the OTT server may also include the processing capability information of the OTT server (similar to the processing capability information of UE#1 in step 8112).
  • UE#1 may The processing capability information and other information determine how to divide the labor (for details, please refer to the description in step 8112), that is, determine which part of the XR objects to be rendered should be rendered by the OTT server, and then perform step 822.
  • the OTT server can decide to leave all the current remaining processing power for the rendering of the XR object of UE#1, or it can decide to leave part of the current remaining processing power for the rendering of the XR object of UE#1, that is, That is, the processing capacity information returned by the OTT server through the XR object rendering response can represent all the current remaining processing capabilities of the OTT server, or can also represent a part of all the current remaining processing capabilities.
  • the OTT server leaves 5% of all current remaining processing capabilities for UE#1's rendering of the The processing capability allocates XR objects to be rendered to the OTT server. This can prevent UE#1 from allocating the rendering tasks of too many XR objects to the OTT server, or prevent the resources of the OTT server from being monopolized by one UE.
  • the OTT server merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the OTT server as an example to illustrate.
  • UE#2 may perform the combining process.
  • UE#1 sends media data corresponding to the rendered XR object to UE#2
  • the OTT server sends media data corresponding to the rendered XR object to UE#2.
  • UE#2 performs merge processing.
  • other devices may also perform the merging process, which will not be described again.
  • Figure 9 is a schematic diagram of an XR object rendering method 900 provided by an embodiment of the present application.
  • Method 900 may include the following steps.
  • the terminal device determines the rendering division of labor.
  • the rendering division of labor refers to: a part of the XR objects to be rendered in the XR call of the terminal device are rendered by the second network device, and the other part of the XR objects to be rendered are rendered by the terminal device.
  • the second network device represents a network-side device that renders some of the XR objects to be rendered in the XR call of the terminal device, corresponding to the network-side rendering device in the content of the invention.
  • the terminal device determines the rendering division of labor based on at least one of the following: processing capability information of the terminal device, processing capability information of the second network device, and processing requirement information of the XR call.
  • the processing capability information and the processing requirement information of the XR call (hereinafter referred to as the first processing requirement information of the XR call, corresponding to the processing requirement information of the XR call mentioned above) can be referred to the processing capability information and the processing of the XR call in method 400
  • the requirement information and the method for the terminal device to determine the rendering division of labor please refer to the method for the first network device to determine the rendering division of labor mentioned above, which will not be described again here.
  • the terminal device renders the XR object to be rendered rendered by the terminal device during the XR call, and sends the XR object to be rendered by the second network device during the XR call to the second network device.
  • the terminal device renders the first part of the XR object to be rendered, and sends the second part of the XR object to be rendered to the second network device.
  • the method 900 also includes: the terminal device sends the rendered first part of the XR object to be rendered to the second network device, and the second network device sends the rendered first part of the XR object to be rendered and the rendered second part of the XR object to be rendered.
  • XR object merging means that the second network device merges the rendered media data corresponding to the first part of the XR object to be rendered and the rendered media data corresponding to the second part of the XR object to be rendered.
  • XR object merging means that the second network device merges the rendered media data corresponding to the first part of the XR object to be rendered and the rendered media data corresponding to the second part of the XR object to be rendered.
  • method 900 further includes: the second network device sending the combined media data to the terminal device involved in the XR call.
  • the terminal device calculates the computing power required for rendering based on the XR objects that need to be rendered in the XR session, and determines the division of labor when it is judged that the computing power required exceeds the processing capability of the terminal device itself, and
  • the first network device may be requested to accept the rendering division through the division of labor confirmation request information.
  • rendering tasks can be dynamically allocated between the terminal device and the second network device through the terminal device, achieving effective collaboration between the terminal device and the second network device and on-demand allocation of rendering tasks.
  • the first network device sends the processing capability information of the second network device to the terminal device.
  • the first network device represents the network-side device that determines the rendering division, corresponding to the network-side control device in the content of the invention.
  • the processing capability information of the second network device may be part of the processing capability information of the second network device.
  • the partial processing capability information of the second network device may be determined by the second network device based on the configuration of its own computing resources, or the second network device may be determined based on the remaining computing resources or available computing resources of the second network device.
  • the proportion of the processing capability information sent by the first network device to the total processing capability information of the second network device can be flexibly determined based on the load of the second network device itself, and this application does not limit this.
  • the processing capability information sent by the network device represents 10% of the total processing capability, so that the terminal device allocates XR objects to be rendered to the network device based on this 10% processing capability, thereby preventing the terminal device from assigning too many rendering tasks of XR objects to network equipment, or to prevent network equipment resources from being monopolized by a terminal device.
  • the terminal device when the terminal device determines that the second network device can render the XR object to be rendered in the XR call, the terminal device sends a session call message to the third network device to trigger the third network device to send the message to the first network device.
  • the division of labor confirmation request information is used to request the first network device to accept the rendering division of labor, wherein the XR object to be rendered that is rendered by the second network device in the rendering division of labor is determined by the terminal device.
  • the division of labor confirmation request information includes the processing requirement information of the XR call (hereinafter referred to as the second processing requirement information of the XR call).
  • the first network device applies to the second network device for rendering resources according to the second processing requirement information of the XR call.
  • the terminal device defaults that the second network device can render the XR object to be rendered in the XR call; for another example, the terminal device obtains service indication information, and the service indication information indicates that the second network device can render the XR object to be rendered in the XR call. Render XR objects for rendering.
  • the first network device can determine whether the terminal device has signed a contract for the network rendering function based on the contract data of the terminal device. If the terminal device has signed a contract for the network rendering function, the first network device can send the network rendering function contracted by the terminal device (i.e., a service indication) to the terminal device. information), informing the terminal device that the second network device can render the XR object to be rendered in the XR call.
  • the third network device corresponds to the network-side access device in the content of the invention.
  • the third network device can be, for example, a network element in an IMS network, or it can also be an OTT server, etc., without limitation.
  • the second processing requirement information of the XR call includes: information used to determine the XR object to be rendered that is to be rendered by the second network device among the XR objects to be rendered in the XR call.
  • the second processing requirement information of the XR call includes the second part of the information of the XR object to be rendered, and the second part of the information of the XR object to be rendered may be the type of the XR object to be rendered (such as people, buildings, plants, etc.).
  • the second processing requirement information of the XR call includes the second part of the information of the XR object to be rendered.
  • the second part of the information of the XR object to be rendered may be the hierarchical information of the XR object to be rendered (such as foreground or background). ).
  • the second processing requirement information of the XR call also includes at least one of the following: video resolution of the XR call and video frame rate of the XR call.
  • the second processing requirement information of the XR call here is related to the terminal device determining in S910 that the XR call of the terminal device is to be rendered.
  • the rendering division of XR objects is different based on the first processing requirement information of the XR call.
  • the first processing requirement information of the XR call based on which the terminal device determines the rendering division of the XR object to be rendered in the XR call of the terminal device includes the information of the XR object to be rendered in the XR call, that is to say, the XR call Information about all XR objects to be rendered.
  • the second processing requirement information of the XR call here includes the information of the XR object to be rendered by the second network device among the XR objects to be rendered in the XR call. That is to say, the part of the XR call needs to be rendered by the second network device.
  • This application does not limit the information of the XR object to be rendered, or the information that allows the second network device to determine the XR object to be rendered by the second network device among the XR objects to be rendered in the XR call.
  • the first network device sends a request message to the second network device, and the request message is used to request at least one of the following: address information of the second network device, Rendering resource information of the second network device; the first network device receives a response to the request message from the second network device.
  • the request message is used to request at least one of the following: address information of the second network device, Rendering resource information of the second network device; the first network device receives a response to the request message from the second network device.
  • FIG 10 is a schematic flow chart of an XR object rendering method 1000 provided by an embodiment of the present application.
  • This method 1000 can be used to implement the solution of the above method 900.
  • this method 1000 may include the following steps.
  • the network device sends service indication information to UE#1.
  • the network device can obtain the subscription data of UE#1, and determine whether UE#1 has signed a contract or purchased a network rendering service based on the contract data. If the network device has signed a contract for the network rendering function, the network device can assist UE#1 in rendering the XR object, and then reports to UE# 1. Send service indication information to inform UE#1 that the network device can render XR objects, or to inform UE#1 that the network device can provide services for rendering XR objects.
  • the network device sends the processing capability of the network device to UE#1.
  • processing capability of the network device may be part of the total processing capability of the network device. How to determine the percentage of the total processing capability occupied by the specific part of the processing capability refers to the relevant description in method 900, which will not be described again.
  • the service indication information and the processing capability of the network device can be sent in one message or in two messages, and this application does not limit this. If sent in two messages, this application does not limit the order of steps 1001 and 1002.
  • UE#1 determines that the network device can render XR objects.
  • UE#1 saves the processing capability and/or service indication information of the network device. Based on the service indication information, it can be learned whether the network device can render XR objects, that is, whether it supports XR object rendering. Based on the processing capability of the network device, it can be known whether the network device has enough capability to assist UE#1 in completing the rendering of the XR object. Steps 1001/1002/1003 are optional steps, that is, the network device does not need to provide service indication information to UE#1, and UE#1 can default to UE#1 signing up for the network rendering function. Or the network device does not need to provide the processing capabilities of the network device to UE#1, and UE#1 can assume that the network device has sufficient capabilities to assist UE#1 in completing the rendering of the XR object.
  • Scenario 1 UE#1 initiates an initial session call.
  • UE#1 determines the rendering division of XR objects to be rendered in the XR call of UE#1, that is, some of the XR objects to be rendered in the XR call are rendered by the network device, and the other part of the XR objects to be rendered are rendered by UE#1.
  • UE#1 When UE#1 initiates the initial session call, based on the first processing requirement information of the XR call, it is determined that the processing capability of UE#1 cannot complete the rendering of the XR object in the XR call, so UE#1 determines that this XR call needs to be split. render.
  • UE#1 has signed up for the network rendering function by default, and the default network device has sufficient capabilities to assist UE#1 in rendering the XR object, and then UE#1 determines the rendering division of the XR object to be rendered in the XR call.
  • UE#1 determines that it has signed up for the network rendering function based on the service indication information in 1001, that is, the network device supports XR object rendering.
  • the network device has sufficient capabilities to assist UE#1 in completing the rendering of XR objects, and then determines Rendering division of XR objects to be rendered in XR calls. If UE#1 determines that the network device does not support XR object rendering, as an example, UE#1 can perform the rendering process by itself.
  • the embodiments of this application mainly introduce the situation in which network devices support XR object rendering.
  • UE#1 has signed up for the network rendering function by default, and UE#1 determines based on the processing capability of the network device in 1002 that the network device has sufficient capabilities to assist UE#1 in completing the rendering of the XR object, and then UE#1 Determine the rendering division of labor for the XR object to be rendered in the XR call.
  • UE#1 determines that it has signed up for the network rendering function based on the service indication information in 1001, and determines based on the processing capability of the network device in 1002 that the network device has sufficient capabilities to assist UE#1 in completing the rendering of the XR object ( That is, the available computing power required by the network device to complete the rendering of the XR object to be rendered does not exceed the processing capability of the network device), and then determine the rendering division of the XR object to be rendered for the XR call, that is, determine the rendering tasks that UE#1 and the network device each need to render XR objects.
  • UE#1 sends a session call request to the network device.
  • the session call request includes division of labor confirmation request information.
  • the division of labor confirmation request information is used to request the network device to accept rendering division of labor.
  • the division of labor confirmation request information includes the second processing requirement information of the XR call.
  • the second processing requirement information of the XR call includes information of the XR object to be rendered that needs to be rendered by the network device among the XR objects to be rendered in the XR call.
  • For other contents included in the second processing requirement information of the XR call (such as the video resolution and video frame rate of the XR call), refer to the relevant description in step 5111 and will not be described again.
  • the division of labor determination request information may indicate that all the XR objects to be rendered in the XR call need to be rendered by the network device, or that some of the XR objects to be rendered in the XR call need to be rendered by the network device. This application does not limit this.
  • the network device accepts the division of labor and allocates rendering resources.
  • the network device determines, based on the division of labor confirmation request information, the information of the XR object to be rendered that the terminal device wants the network device to assist in completing the rendering, and further determines whether it can assist in completing the rendering based on the processing capabilities of the network device. For example, if the network device determines that the rendering computing power required for the XR object to be rendered that the terminal device wants the network device to assist in completing the rendering exceeds the available computing power for rendering of the network device, it means that the network device cannot accept the division of rendering labor.
  • the network device determines that the rendering computing power required for the XR object to be rendered, which the terminal device wants the network device to assist in rendering, does not exceed the available computing power for rendering of the network device, it means that the network device can accept the division of labor.
  • the embodiments of this application mainly Introduce network devices that can accept the division of labor in rendering.
  • the network device must be able to accept the division of rendering labor. Further, render resources shall be reserved for XR objects to be rendered that require rendering by the network device.
  • the network device determines the computing power required for the XR object to be rendered based on the information of the XR object to be rendered that needs to be rendered by the network device, and reserves or allocates corresponding computing power resources based on the XR computing power requirements.
  • Computing resources such as memory or CPU time slots or GPU resources, etc.
  • the method for the network device to determine whether the rendering computing power required for the XR object to be rendered exceeds the available computing power for rendering of the network device can refer to the relevant description in 5112 and will not be described again.
  • the network device sends a division of labor confirmation response message to UE#1, and the division of labor confirmation response information instructs the network device to accept the rendering division of labor.
  • Scenario 2 UE#1 receives the initial session call.
  • the network device sends a session call request to UE#1.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • UE#1 When UE#1 receives the session call request, it determines based on the first processing requirement information of the XR call that the processing capability of UE#1 cannot complete the rendering of the XR object in the XR call. Therefore, UE#1 determines that this XR call needs to be split. render.
  • UE#1 sends a session call response to the network device, where the session call response includes division of labor confirmation request information.
  • step 1012 For details, please refer to the relevant description in step 1012, which will not be described again.
  • the network device accepts the rendering division of labor and allocates rendering resources.
  • the network device sends a division of labor confirmation response message to UE#1.
  • Steps 1024 to 1025 are similar to steps 1013 to 1014 and will not be described again here.
  • Scenario 3 UE#1 initiates a session update call.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • step 1011 assuming that the processing requirements of the XR call change, when UE#1 initiates a session update call, it will again determine whether the rendering of the XR object in the XR call can be completed based on the processing capabilities of UE#1, and step 1011 Similarly, please refer to the relevant description in step 1011 for details, which will not be described again.
  • UE#1 sends a session update call request to the network device.
  • the session update call request includes labor division confirmation request information.
  • the division of labor confirmation request information is used to request the network device to accept the updated rendering division of labor.
  • step 1012 For details, please refer to the relevant description in step 1012, which will not be described again.
  • the network device accepts the updated rendering division of labor and updates the rendering resources.
  • the network device re-determines the XR object to be rendered that needs to be rendered by the network device side according to the division of labor confirmation request information included in the session update call request, and updates the rendering resources according to the XR object that needs to be rendered by the network device side.
  • the network device can reuse the computing power resources reserved or allocated in step 1013, or can reallocate the computing power resources.
  • the reallocated computing power resources can be different from the computing power reserved or allocated in step 1013. resource.
  • the network device sends a division of labor confirmation response message to UE#1, and the division of labor confirmation response information instructs the network device to accept the updated rendering division of labor.
  • Steps 1033 to 1034 are similar to steps 1013 to 1014, and will not be described again here.
  • Scenario 4 UE#1 receives a session update call.
  • the network device sends a session update call request to UE#1.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • Step 1011 is similar. For details, please refer to the relevant description in step 1011 and will not be described again.
  • UE#1 sends a session update call response to the network device.
  • the session update call response includes labor division confirmation request information.
  • the division of labor confirmation request information is used to request the network device to accept the updated rendering division of labor.
  • step 1012 For details, please refer to the relevant description in step 1012, which will not be described again.
  • the network device accepts the updated rendering division of labor and updates the rendering resources.
  • the network device re-determines the XR object to be rendered that needs to be rendered by the network device side according to the division of labor confirmation request information included in the session update call response, and updates the rendering resources according to the XR object that needs to be rendered by the network device side.
  • the network device can reuse the computing power resources reserved or allocated in step 1024, or can reallocate the computing power resources.
  • the reallocated computing power resources can be different from the computing power reserved or allocated in step 1024. resource.
  • the network device sends a division of labor confirmation response message to UE#1, and the division of labor confirmation response information instructs the network device to accept the updated rendering division of labor.
  • Steps 1044 to 1045 are similar to steps 1013 to 1014 and will not be described again here.
  • UE#1 sends the XR object to be rendered that the network device is responsible for rendering to the network device.
  • UE#1 sends the XR object to be rendered that the network device is responsible for rendering to the network device based on the rendering division of the XR object to be rendered in the XR call.
  • the network device renders the XR object to be rendered that the network device is responsible for rendering.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends media data corresponding to the rendered XR object to the network device.
  • the network device merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the network device to obtain merged media data.
  • the network device sends the combined media data to UE#2.
  • Steps 1051 to 1056 are similar to steps 522 to 527 and will not be described again here.
  • the network device can notify the terminal device of its own processing capabilities and service indication information.
  • the terminal device determines the rendering division of labor after determining that the XR object rendering computing power requirement exceeds the available rendering computing power of the terminal device and confirms that the network device supports XR object rendering, sends division of labor confirmation request information to the network device, and requests to communicate with the network device. Render negotiation.
  • the network device can determine according to the division of labor confirmation request information that it will assist the terminal device in completing the rendering of the XR object and notify the terminal device.
  • the terminal device sends the data to be rendered by the network device to the network device.
  • the network device or other device can merge the media data corresponding to the XR object rendered by the network device and the media data corresponding to the XR object rendered by the terminal device, and send the merged media data to the parties involved in this session.
  • Terminal Equipment Terminal Equipment
  • the network device merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the network device as an example for illustrative explanation.
  • UE#2 that performs the merging process.
  • UE#1 sends media data corresponding to the rendered XR object to UE#2
  • the network device sends media data corresponding to the rendered XR object to UE#2.
  • UE#2 performs merge processing.
  • other devices may also perform the merging process, which will not be described again.
  • FIG 11 is a schematic flow chart of an XR object rendering method 1100 provided by an embodiment of the present application.
  • This method 1100 can be used to implement the solution of the above method 900.
  • This method 1100 can be used in the scenario of DC-based rendering negotiation, and the rendering negotiation can be performed after the DC is established, for example.
  • the first network device is an XR-C network element
  • the second network device is an XR-M network element
  • the IMS includes one or more network elements.
  • the architecture shown in Figure 1 which will be used uniformly below "IMS" stands for.
  • the method 1100 shown in Figure 11 may be used with the Figure 1 architecture.
  • the method 1100 may include the following steps.
  • UE#1 Before step 1101, UE#1 sends a SIP registration (REGISTER) message to IMS during the process of registering with IMS. After IMS successfully registers and authenticates UE#1, it sends an HTTP message to the XR-C network element.
  • SIP registration REGISTER
  • the XR-C network element sends service indication information to IMS.
  • the method for the XR-C network element to determine the service indication information is similar to step 1001 and will not be described again.
  • the XR-C network element sends an HTTP response message (such as a 200 message) to the IMS, and the HTTP response message includes service indication information.
  • IMS sends service indication information to UE#1.
  • the XR-C network element sends the processing capabilities of the XR-M network element to the IMS.
  • the processing capability of the XR-M network element is similar to the processing capability of the network device in step 1002, and will not be described again.
  • One possible implementation method is that the XR-C network element sends an HTTP response message (such as a 200 message) to the IMS, and the HTTP response message includes the processing capabilities of the XR-M network element.
  • an HTTP response message such as a 200 message
  • IMS sends the processing capabilities of the XR-M network element to UE#1.
  • the service indication information and the processing capability of the XR-M network element can be sent in one message or in two messages, and this application does not limit this. If sent in two messages, this application does not limit the order of steps 1101 and 1103, as well as the order of steps 1102 and 1104.
  • UE#1 determines that the XR-M network element can render XR objects.
  • UE#1 saves the processing capability and/or service indication information of the network device. Based on the service indication information, it can be learned whether the XR-M network element can render XR objects, that is, whether it supports XR object rendering. Based on the processing capability of the XR-M network element, it can be known whether the XR-M network element has enough capability to assist UE#1 in completing the rendering of the XR object. Steps 1101 to 1105 are optional steps, that is, the XR-C network element does not need to provide service indication information to UE#1, and UE#1 can default to UE#1 signing up for the network rendering function. Or it is not necessary to provide the processing capability of the XR-M network element to UE#1. UE#1 can assume that the XR-M network element has sufficient capabilities to assist UE#1 in rendering the XR object.
  • Audio and video media channel establishment and DC establishment are optional.
  • step 607 It is similar to step 607 and will not be described again.
  • service indication information sent in steps 1101 to 1104 and the processing capability of the XR-M network element can also be completed before UE#1 initiates the media rendering negotiation process, and this application does not limit this.
  • service indication information and the processing capabilities of the XR-M network element can be sent through the DC channel.
  • the following describes the rendering negotiation process based on two scenarios.
  • Scenario 1 UE#1 initiates rendering negotiation.
  • UE#1 determines the rendering division of XR objects to be rendered in the XR call of UE#1, that is, some of the XR objects to be rendered in the XR call are rendered by the XR-M network element, and the other part of the XR objects to be rendered are rendered by UE#1. .
  • UE#1 Based on the first processing requirement information of the XR call, UE#1 determines that the processing capability of UE#1 cannot complete the rendering of the XR object in the XR call, so UE#1 determines that split rendering is required for this XR call.
  • UE#1 has signed up for the network rendering function by default, and by default the XR-M network element has sufficient capabilities to assist UE#1 in rendering the XR object, and then UE#1 determines the rendering of the XR object to be rendered in the XR call. Division of labor.
  • UE#1 determines that UE#1 has signed up for the network rendering function based on the service indication information in 1102, that is, the XR-M network element supports XR object rendering, and by default the XR-M network element has sufficient capabilities to assist UE# 1.
  • Complete the rendering of the XR object and then determine the rendering division of the XR object to be rendered in the XR call. If UE#1 determines that the XR-M network element does not support XR object rendering, as an example, UE#1 can perform rendering processing by itself.
  • the embodiment of this application mainly introduces the situation in which XR-M network elements support XR object rendering.
  • UE#1 has signed up for the network rendering function by default, and UE#1 is based on the processing of the XR-M network element in 1104.
  • the processing capability determines that the XR-M network element has sufficient capabilities to assist UE#1 in completing the rendering of the XR object, and then UE#1 determines the rendering division of the XR object to be rendered in the XR call.
  • UE#1 determines that the XR-M network element supports XR object rendering based on the service indication information in 1102, and determines that the XR-M network element has sufficient capabilities based on the processing capability of the XR-M network element in 1104. Assist UE#1 to complete the rendering of the XR object (that is, the available computing power required by the XR-M network element to complete the rendering of the XR object to be rendered does not exceed the processing capability of the XR-M network element), and then determine the XR to be rendered for the XR call Object rendering division of labor.
  • UE#1 sends the division of labor confirmation request information to the IMS.
  • the division of labor confirmation request information is used to request the XR-C network element to accept the rendering division of labor.
  • UE#1 sends a media rendering negotiation request to the IMS.
  • the media rendering negotiation request includes labor division confirmation request information.
  • the division of labor confirmation request information includes the second processing requirement information of the XR call, and the second processing requirement information of the XR call. Includes information about the XR object to be rendered that needs to be rendered by the network device in the XR call.
  • the second processing requirement information of the XR call includes parameter C1, parameter C2, parameter D, and parameter E.
  • the second processing requirement information for an XR call is in the following form:
  • “network_rendering_content” represents parameter C1, which is the XR object to be rendered that needs to be rendered by the XR-M network element.
  • “video_resolution” indicates parameter D, which is the video resolution.
  • “video_frame_rate” represents parameter E, which is the video frame rate.
  • the XR-M network element When the XR-M network element renders some of the XR objects to be rendered, it is necessary to merge the media data corresponding to the XR objects rendered by UE#1 and the XR-M network element and then send them to UE#2. When rendering XR objects, the media data corresponding to all XR objects rendered by the XR-M network element can be directly sent to UE#2.
  • UE#2 may perform the combining process.
  • UE#1 sends media data corresponding to the rendered XR object to UE#2
  • the XR-M network element sends media data corresponding to the rendered XR object to UE#2.
  • UE#2 performs merge processing.
  • other devices may also perform the merging process, which will not be described again.
  • IMS sends an HTTP request message to the XR-C network element.
  • the HTTP request message also includes division of labor confirmation request information.
  • the XR-C network element applies for rendering resources from the XR-M network element.
  • the XR-C network element When the XR-C network element determines that it needs to render XR objects on the XR-M network element side based on the division of labor confirmation request information, it can apply for resources from the XR-M network element, that is, request the XR-M network element to render the XR-M network element responsible for rendering.
  • the XR object to be rendered One possible implementation method is that the XR-C network element sends an HTTP request message to the XR-M network element.
  • the HTTP request message is used to apply to the XR-M network element for rendering resources related to rendering XR objects.
  • the XR-C network element's application for rendering resources from XR-M includes: the XR-C network element requests the XR-M network element to create or allocate endpoint resources.
  • the XR-M network element creates or allocates a corresponding resource endpoint (also called a media endpoint), and returns the information of the corresponding resource endpoint (corresponding to the address information of the network-side rendering device in the content of the invention) to the XR-C network element.
  • the XR-M network element creates or allocates two resource endpoints, namely the first resource endpoint and the second resource endpoint.
  • the attributes of the first resource endpoint include the local connection address of the first resource endpoint.
  • the attributes of the second resource endpoint include the local connection address of the second resource endpoint, where the local connection address of the first resource endpoint and the local connection address of the second resource endpoint are respectively used to enable UE#1 to pass the IMS (UE The IMS accessed by #1) establishes a communication connection with the XR-M network element, and enables UE#2 to establish a communication connection with the XR-M network element through the IMS (IMS accessed by UE#2).
  • the XR-C network element's application for rendering resources from XR-M may also include: the XR-C network element requesting the XR-M network element to reserve or allocate computing power resources.
  • the XR-C network element sends the information of the XR object to be rendered or the XR computing power requirement to the XR-M network element.
  • the XR computing power requirement represents the XR object to be rendered that needs to be consumed by the XR-M network element.
  • the XR-M network element reserves or allocates corresponding computing power resources, such as memory or CPU time slots or GPU resources; in this way, the XR-M network element can be used to render the According to the object information or XR computing power requirements, reserve or allocate corresponding computing power resources.
  • the XR-M network element sends the application result to the XR-C network element.
  • the XR-M network element returns a resource application result to the XR-C network element, including at least one of the following: result indication information and resource endpoint information.
  • the result indication information can be used to notify the XR-C network element whether the XR-M network element will render the XR object to be rendered that the XR-M network element is responsible for rendering.
  • the XR-C network element can request the UE #1 sends transmission instruction information to instruct UE#1 to send the XR object to be rendered that the XR-M network element is responsible for rendering to the XR-M network element.
  • the resource endpoint information includes the local connection address of the first resource endpoint and the local connection address of the second resource endpoint.
  • the XR-C network element can send the -CSCF network element) sends the local connection address of the first resource endpoint, so that the IMS (such as the IMS-AGW controlled by P-CSCF) communicates with the XR-M network element through the local connection address of the first resource endpoint, such as UE #1 Send the XR object to be rendered by the XR-M network element to the XR-M network element through IMS-AGW.
  • the IMS such as the IMS-AGW controlled by P-CSCF
  • UE#1 has a connection with IMS-AGW, such as a first connection (the connection can also be understood as a channel).
  • IMS can establish IMS-AGW through the local connection address of the first resource endpoint sent by the XR-C network element.
  • a second connection with the XR-M network element and establishes a corresponding relationship between the first connection and the second connection. This corresponding relationship enables IMS-AGW to receive the to-be-rendered message sent by UE#1 and is responsible for rendering by the XR-M network element.
  • the second connection After receiving the XR object, the second connection can be determined, and the XR object to be rendered, which is responsible for rendering by the XR-M network element, can be forwarded to the XR-M network element through the second connection.
  • the P-CSCF sends the local connection address of the second resource endpoint, so that UE#2 communicates with the XR-M network element through the IMS. For example, UE#2 obtains the merged media from the XR-M network element through the IMS. data.
  • the XR-C network element can send the local connection address of the second resource endpoint to the P-CSCF in the IMS that UE#2 accesses, so that UE#2 can connect to the XR through the IMS-AGW controlled by the P-CSCF.
  • -M network element so that UE#2 can obtain the combined media data from the XR-M network element through IMS-AGW.
  • the application result returned by the XR-M network element to the XR-C network element indicates that the XR-M network element will render the XR object to be rendered that the XR-M network element is responsible for rendering, that is, the The M network element applied for rendering resources successfully, and further, the XR-C network element accepted the rendering division of labor.
  • the XR-C network element sends the division of labor confirmation response information and resource endpoint information to the IMS.
  • IMS sends the division of labor confirmation response message to UE#1.
  • the division of labor confirmation response information is used to instruct the XR-C network element to accept the rendering division of labor.
  • Scenario 2 UE#1 initiates re-rendering negotiation.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • UE#1 When the processing requirements of the XR call are updated during the XR call, UE#1 re-determines the rendering division of the XR object to be rendered. Otherwise, it is similar to step 1111 and will not be described again.
  • UE#1 sends the re-division of labor confirmation request information to the IMS.
  • the re-division of labor confirmation request information includes the updated second processing requirement information of the XR call.
  • the updated second processing requirement information of the XR call includes the information of the XR object to be rendered that needs to be rendered by the XR-M network element in the XR call.
  • the terminal device may initiate a re-rendering negotiation.
  • UE#1 can send a re-division of labor confirmation request message to the IMS in order to re-negotiate the rendering of the XR call.
  • IMS sends an HTTP message to the XR-C network element.
  • the HTTP message includes re-division of labor confirmation request information, which is used to request the XR-C network element to accept the updated rendering division of labor.
  • the XR-C network element applies to the XR-M network element to update rendering resources.
  • the XR-C network element When the XR-C network element determines that it needs to update the rendering on the XR-M network element side based on the re-division of labor confirmation request information, it can apply for update resources from the XR-M network element.
  • One possible implementation method is that the XR-C network element sends an HTTP message to the XR-M network element, and the HTTP message is used to apply for resource modification. It can be understood that in this step, the XR-M network element can re-create the endpoint resources or reuse the endpoint resources created or allocated in step 1114; the XR-M network element can reuse the computing resources reserved or allocated in step 1114.
  • the computing power resources may also be reallocated, and the reallocated computing power resources may be different from the computing power resources reserved or allocated in step 1114.
  • the XR-M network element sends the application result to the XR-C network element.
  • the XR-M network element returns the resource application result to the XR-C network element, including at least one of the following:
  • the result refers to Display information and resource endpoint information.
  • the result indication information can be used to notify the XR-C network element whether the XR-M network element will render the XR object to be rendered that the XR-M network element is responsible for rendering. If the XR-M network element re-creates the endpoint resource, the resource endpoint information includes the information of the re-created endpoint resource.
  • the XR-C network element sends a division of labor confirmation response message to the IMS.
  • the application result received by the XR-C network element indicates that the XR-M network element will render the XR object to be rendered that the XR-M network element is responsible for rendering, that is, the XR-C network element applies for rendering to the XR-M network element
  • the resource is successful.
  • the XR-C network element accepts the rendering division of labor and sends a division of labor confirmation response message to IMS.
  • the XR-M network element re-creates the endpoint resource in step 1125, the XR-C network element also needs to send the new resource endpoint information to the IMS.
  • IMS sends division of labor confirmation response information to UE#1.
  • UE#1 sends the XR object to be rendered that the XR-M network element is responsible for rendering to the XR-M network element.
  • One possible implementation method is that UE#1 sends the XR object to be rendered that the XR-M network element is responsible for rendering to the XR-M network element based on the rendering division of the XR object to be rendered in the XR call.
  • UE#1 sends the XR object to be rendered that the XR-M network element is responsible for rendering to IMS-AGW through the first connection based on the division of labor for the XR object to be rendered in the XR call.
  • IMS-AGW communicates with the second connection based on the first connection. According to the corresponding relationship of the connection, the XR object to be rendered that is responsible for rendering by the XR-M network element is forwarded to the XR-M network element through the second connection.
  • the XR-M network element renders the XR object to be rendered that the XR-M network element is responsible for rendering.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends the media data corresponding to the rendered XR object to the XR-M network element.
  • the XR-M network element merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the XR-M network element to obtain merged media data.
  • the XR-M network element sends the combined media data to UE#2.
  • Steps 1151 to 1156 are similar to steps 622 to 627, and will not be described again here.
  • the XR-C network element can notify the terminal device of the processing capabilities and service indication information of the XR-M network element.
  • the terminal device determines that the XR object rendering computing power requirement exceeds the terminal device's available rendering computing power and determines that the network device supports XR object rendering
  • the terminal device determines the rendering division of labor, and can transmit division of labor confirmation request information in the DC channel to request rendering negotiation.
  • the XR-C network element can determine based on the division of labor confirmation request information that the XR-M network element will assist the terminal device to complete the rendering of the XR object and inform the terminal device.
  • the terminal device sends the XR-M network element data to be rendered to the XR-M network element.
  • the XR-M network element or other device can merge the media data corresponding to the XR object rendered by the XR-M network element and the media data corresponding to the XR object rendered by the terminal device, and send the merged media data to UE#2 involved in this session.
  • the media rendering task may need to be re-divided due to some circumstances during the session, such as changes in the processing requirements of the Conduct rendering negotiations.
  • FIG 12 is a schematic flow chart of an XR object rendering method 1200 provided by an embodiment of the present application.
  • This method 1200 can be used to implement the solution of the above method 900.
  • the method 1200 can be used in a scenario where rendering negotiation is performed based on IMS SIP signaling.
  • the rendering negotiation can be completed during the call establishment process, for example.
  • the first network device is an AS
  • the second network device is an MRF network element.
  • the MRF network element may include, for example, MRFC and MRFP.
  • the IMS may include one or more network elements.
  • refer to the architecture shown in Figure 2 which will be collectively referred to as “IMS core” below.
  • the method 1200 shown in Figure 12 may be used in the Figure 2 architecture.
  • the method 1200 may include the following steps.
  • UE#1 Before step 1201, UE#1 sends a SIP REGISTER message to IMS during the registration process with IMS core. After IMS core successfully registers and authenticates UE#1, it sends SIP REGISTER to the AS network element.
  • AS sends service instruction information to IMS core.
  • step 1001 The method by which the AS determines the service indication information is similar to step 1001 and will not be described again.
  • IMS core sends service indication information to UE#1.
  • AS sends the processing capabilities of the MRF network element to the IMS core.
  • IMS core sends the processing capability of the MRF network element to UE#1.
  • the service indication information and the processing capability of the MRF network element can be sent in one message or in two messages. Send, this application does not impose restrictions on this. If sent in two messages, this application does not limit the order of steps 1201 and 1203, and the order of steps 1202 and 1204.
  • UE#1 determines that the MRF network element can render XR objects.
  • UE#1 saves the processing capability and/or service indication information of the network device. Based on the service indication information, it can be learned whether the MRF network element can render XR objects, that is, whether it supports XR object rendering. Based on the processing capability of the MRF network element, it can be known whether the MRF network element has enough capability to assist UE#1 in completing the rendering of the XR object. Steps 1201 to 1205 are optional steps, that is, the AS network element does not need to provide service indication information to UE#1, and UE#1 can default to UE#1 signing up for the network rendering function. Or it is not necessary to provide the processing capability of the MRF network element to UE#1. UE#1 can assume that the MRF network element has sufficient capabilities to assist UE#1 in rendering the XR object.
  • Scenario 1 UE#1 initiates XR call establishment.
  • UE#1 determines the rendering division of the XR objects to be rendered in the XR call of UE#1, that is, some of the XR objects to be rendered in the XR call are rendered by the MRF network element, and the other part of the XR objects to be rendered are rendered by UE#1.
  • UE#1 Based on the first processing requirement information of the XR call, UE#1 determines that the processing capability of UE#1 cannot complete the rendering of the XR object in the XR call, so UE#1 determines that split rendering is required for this XR call.
  • UE#1 has signed up for the network rendering function by default, and by default the MRF network element has sufficient capabilities to assist UE#1 in rendering the XR object, and then UE#1 determines the rendering division of the XR object to be rendered in the XR call.
  • UE#1 determines that UE#1 has signed up for the network rendering function based on the service indication information in 1202, that is, the MRF network element supports XR object rendering.
  • the MRF network element has sufficient capabilities to assist UE#1 in completing the XR object. rendering, and then determine the rendering division of the XR object to be rendered in the XR call. If UE#1 determines that the MRF network element does not support XR object rendering, as an example, UE#1 can perform rendering processing by itself.
  • the embodiment of this application mainly introduces how MRF network elements support XR object rendering.
  • UE#1 has signed up for the network rendering function by default, and UE#1 determines based on the processing capability of the MRF network element in 1204 that the MRF network element has sufficient capabilities to assist UE#1 in completing the rendering of the XR object, and then UE#1 #1 Determine the rendering division of the XR object to be rendered in the XR call.
  • UE#1 determines that the MRF network element supports XR object rendering based on the service indication information in 1202, and determines based on the processing capability of the MRF network element in 1204 that the MRF network element has sufficient capabilities to assist UE#1 in completing XR
  • the rendering of the object that is, the available computing power required by the MRF network element to complete the rendering of the XR object to be rendered does not exceed the processing capability of the MRF network element
  • UE#1 sends an INVITE message to the IMS core.
  • the INVITE message includes the division of labor confirmation request information.
  • the division of labor confirmation request information is used to request the AS network element to accept the rendering division of labor.
  • the division of labor confirmation request information includes the second processing requirement information of the XR call. The details are similar to step 1112 and will not be described again.
  • IMS core sends an INVITE message to AS.
  • the INVITE message in step 1212 includes division of labor confirmation request information
  • the INVITE message in step 1213 also includes division of labor confirmation request information.
  • the AS network element determines that it needs to render an XR object on the MRF network element side based on the division of labor confirmation request information, it can apply for resources from the MRF network element, that is, request the MRF network element to render the XR object to be rendered that the MRF network element is responsible for rendering.
  • One possible implementation method is that the AS network element sends an INVITE message to the MRF network element, and the INVITE message is used to apply to the MRF network element for rendering resources related to rendering XR objects.
  • the AS network element's application for rendering resources from the MRF includes: the AS network element requests the MRF network element to create or allocate endpoint resources.
  • the MRF network element creates or allocates a corresponding resource endpoint (also called a media endpoint), and returns the information of the corresponding resource endpoint (corresponding to the address information of the network-side rendering device in the content of the invention) to the AS network element.
  • the MRF network element creates or allocates two resource endpoints, namely the first resource endpoint and the second resource endpoint.
  • the attributes of the first resource endpoint include the local connection address of the first resource endpoint
  • the The attributes of the second resource endpoint include the local connection address of the second resource endpoint, where the local connection address of the first resource endpoint and the local connection address of the second resource endpoint are respectively used to enable UE#1 to pass the IMS core (UE#
  • the IMS core accessed by UE#2 establishes a communication connection with the MRF network element, and enables UE#2 to establish a communication connection with the MRF network element through the IMS core (IMS core accessed by UE#2).
  • the AS network element's application for rendering resources from the MRF may also include: the AS network element requesting the MRF network element to reserve or allocate computing power resources.
  • the MRF network element reserves or allocates corresponding computing resources, such as memory or CPU time slots or GPU resources.
  • the AS network element sends the information of the XR object to be rendered or the XR computing power requirement to the MRF network element.
  • the XR computing power requirement indicates that it belongs to the MRF.
  • the MRF network element can reserve or allocate corresponding computing power resources based on the information of the XR object to be rendered or the XR computing power requirements.
  • the MRF network element sends the application result to the AS.
  • the MRF network element returns the resource application result to the AS network element, including at least one of the following: result indication information and resource endpoint information.
  • the result indication information can be used to notify the AS network element whether the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering.
  • the AS network element can send transmission instruction information to UE#1 to Instruct UE#1 to send the XR object to be rendered that the MRF network element is responsible for rendering to the MRF network element.
  • the resource endpoint information includes the local connection address of the first resource endpoint and the local connection address of the second resource endpoint.
  • the AS network element can send a request to the IMS core (for example, the P-CSCF network element in the IMS core). ) sends the local connection address of the first resource endpoint, so that the IMS core (such as IMS-AGW controlled by P-CSCF) communicates with the MRF network element through the local connection address of the first resource endpoint, for example, UE#1 uses IMS-
  • the AGW sends the XR object to be rendered to the MRF network element, which is responsible for rendering by the MRF network element.
  • UE#1 has a connection with IMS-AGW, such as a third connection (the connection can also be understood as a channel).
  • IMS core can establish the connection between IMS-AGW and IMS-AGW through the local connection address of the first resource endpoint sent by the AS network element.
  • the fourth connection of the MRF network element and establishes the corresponding relationship between the third connection and the fourth connection. This corresponding relationship allows IMS-AGW to receive the XR object to be rendered sent by UE#1 and is responsible for rendering by the MRF network element.
  • the fourth connection is determined, and the XR object to be rendered that is responsible for rendering by the MRF network element is forwarded to the MRF network element through the fourth connection.
  • the AS network element can also send a request to the P-CSCF in the IMS core (such as the IMS core accessed by UE#2). ) Send the local connection address of the second resource endpoint so that UE#2 can communicate with the MRF network element through the IMS core. For example, UE#2 obtains the merged media data from the MRF network element through the IMS core.
  • the AS network element can send the local connection address of the second resource endpoint to the P-CSCF in the IMS core, so that UE#2 can connect to the MRF network element through the IMS-AGW controlled by the P-CSCF, so that UE#2
  • the combined media data can be obtained from the MRF network element through IMS-AGW.
  • the application result returned by the MRF network element to the AS network element indicates that the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering. That is, the AS network element successfully applied for rendering resources to the MRF network element. Further, the AS Network elements accept the rendering division of labor.
  • AS sends division of labor confirmation response information and resource endpoint information to IMS core.
  • the division of labor confirmation response information is used to instruct the AS network element to accept rendering division of labor.
  • IMS core sends a division of labor confirmation response message to UE#1.
  • Scenario 2 UE#1 receives XR call call establishment.
  • AS sends INVITE message to IMS core.
  • IMS core sends an INVITE message to UE#1.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • step 1211 Except for the scenario, it is similar to step 1211 and will not be described again.
  • UE#1 sends a 200 For INVITE message to the IMS core.
  • the 200 For INVITE message includes the division of labor confirmation request information.
  • the division of labor confirmation request information includes the second processing requirement information of the XR call. The details are similar to step 1112 and will not be described again.
  • the 200 For INVITE message in step 1224 can also be replaced by the 18X For INVITE message. There is no restriction on the specific type of the message.
  • IMS core sends a 200 For INVITE message to the AS.
  • the 200 For INVITE message includes the division of labor confirmation request information.
  • the 200 For INVITE message in step 1225 can also be replaced by the 18X For INVITE message. There is no restriction on the specific type of the message.
  • the AS applies for rendering resources from the MRF network element.
  • the MRF network element sends the application result to the AS.
  • AS sends division of labor confirmation response information and resource endpoint information to IMS core.
  • the application result received by the AS network element indicates that the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering. That is, the AS network element successfully applied for rendering resources to the MRF network element. Further, the AS network element accepted Rendering division of labor, sending division of labor confirmation response information and resource endpoint information to IMS core.
  • IMS core sends a division of labor confirmation response message to UE#1.
  • Steps 1226 to 1229 are similar to steps 1214 to 1217, and will not be described again here.
  • Scenario 3 UE#1 initiates XR call update.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1. When the processing requirements of the XR call are updated during the XR call, UE#1 re-determines the rendering division. Otherwise, it is similar to step 1211 and will not be described again.
  • UE#1 sends a REINVITE message to the IMS core.
  • the REINVITE message includes the division of labor confirmation request information to request the AS to accept the updated rendering division of labor.
  • IMS core sends a REINVITE message to AS.
  • the REINVITE message includes labor division confirmation request information to request AS to accept the updated rendering division of labor.
  • the division of labor confirmation request information in step 1232-step 1233 includes the updated second processing requirement information of the XR call.
  • the updated second processing requirement information of the XR call please refer to the relevant description in step 1112, which will not be described again.
  • the AS network element determines that it needs to update the rendering on the MRF network element side based on the division of labor confirmation request information, it can apply for update resources from the MRF network element.
  • One possible implementation method is that the AS network element sends a REINVITE message to the MRF network element, and the REINVITE message is used to apply for resource modification. It can be understood that in this step, the MRF network element can re-create the endpoint resources, or reuse the endpoint resources created or allocated in step 1214; the MRF network element can reuse the computing resources reserved or allocated in step 1214, or reuse them. Allocate computing power resources. The reallocated computing power resources may be different from the computing power resources reserved or allocated in step 1214.
  • the MRF network element sends the application result to the AS.
  • the MRF network element returns the resource application result to the AS network element, including at least one of the following: result indication information and resource endpoint information.
  • the result indication information can be used to notify the AS network element whether the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering. If the MRF network element re-creates the endpoint resource, the resource endpoint information includes the re-created resource endpoint information.
  • AS sends division of labor confirmation response information to IMS core.
  • the application result received by the AS network element indicates that the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering. That is, the AS network element successfully applied for rendering resources to the MRF network element. Further, the AS network element accepted Rendering division of labor, sending division of labor confirmation response information to IMS core. Optionally, if the MRF network element re-creates the endpoint resource, the AS also needs to send the new resource endpoint information to the IMS core.
  • IMS core sends a division of labor confirmation response message to UE#1.
  • Scenario 4 UE#1 receives XR call update.
  • AS sends REINVITE message to IMS core.
  • IMS core sends a REINVITE message to UE#1.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • UE#1 needs to re-determine the rendering division. Otherwise, it is similar to 1211 and will not be described again.
  • UE#1 sends a 200 For REINVITE message to the IMS core.
  • the 200 For REINVITE message includes the division of labor confirmation request information to request the AS to accept the updated rendering division of labor.
  • IMS core sends a 200 For REINVITE message to AS.
  • the 200 For REINVITE message includes the division of labor confirmation request information to request AS to accept the updated rendering division of labor.
  • Steps 1244 to 1245 are similar to steps 1224 to 1225 and will not be described again.
  • the AS network element determines that it needs to update the rendering on the MRF network element side based on the division of labor confirmation request information, it can apply for update resources from the MRF network element.
  • One possible implementation method is that the AS network element sends a REINVITE message to the MRF network element, and the REINVITE message is used to apply for resource modification.
  • the MRF network element can re-create the endpoint resources, or reuse the endpoint resources created or allocated in step 1226; the MRF network element can reuse the computing power resources reserved or allocated in step 1226, or reuse them. Allocate computing power resources.
  • the reallocated computing power resources may be different from the computing power resources reserved or allocated in step 1226.
  • the MRF network element sends the application result to the AS.
  • the MRF network element returns the resource application result to the AS network element, including at least one of the following: result indication information. information, resource endpoint information.
  • the result indication information can be used to notify the AS network element whether the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering. If the MRF network element re-creates the endpoint resource, the resource endpoint information includes the information of the re-created endpoint resource.
  • AS sends division of labor confirmation response information to IMS core.
  • the application result received by the AS network element indicates that the MRF network element will render the XR object to be rendered that the MRF network element is responsible for rendering. That is, the AS network element successfully applied for rendering resources to the MRF network element. Further, the AS network element accepted Rendering division of labor, sending division of labor confirmation response information to IMS core. Optionally, if the MRF network element re-creates the endpoint resource, the AS also needs to send the new resource endpoint information to the IMS core.
  • IMS core sends a division of labor confirmation response message to UE#1.
  • UE#1 sends the XR object to be rendered that the MRF network element is responsible for rendering to the MRF network element.
  • One possible implementation method is that UE#1 sends the XR object to be rendered that the MRF network element is responsible for rendering to the MRF network element based on the rendering division of the XR object to be rendered in the XR call.
  • UE#1 sends the XR object to be rendered that the MRF network element is responsible for rendering to IMS-AGW through the third connection based on the rendering division of the XR object to be rendered in the According to the corresponding relationship, the XR object to be rendered, which is responsible for rendering by the MRF network element, is forwarded to the MRF network element through the fourth connection.
  • the MRF network element renders the XR object to be rendered that the MRF network element is responsible for rendering.
  • UE#1 renders the XR object to be rendered that UE#1 is responsible for rendering.
  • UE#1 sends the media data corresponding to the rendered XR object to the MRF network element.
  • the MRF network element merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the MRF network element to obtain merged media data.
  • the MRF network element sends the combined media data to UE#2.
  • Steps 1251 to 1256 are similar to steps 722 to 727, and will not be described again here.
  • the AS can notify the terminal device of the processing capabilities and service indication information of the MRF network element.
  • the terminal device determines that the XR object rendering computing power requirement exceeds the available computing power for rendering of the terminal device and determines that the MRF network element supports XR object rendering
  • the terminal device can carry division of labor confirmation request information in the call request to request rendering negotiation.
  • the AS can determine based on the division of labor confirmation request information that the MRF network element will assist the terminal device in completing the rendering of the XR object and notify the terminal device.
  • the AS applies for media rendering resources from the MRF network element. Based on the rendering negotiation results, the terminal device can send the data to be rendered by the MRF network element to the MRF network element.
  • the MRF network element or other device can merge the media data corresponding to the XR object rendered by the MRF network element and the media data corresponding to the XR object rendered by the terminal device, and send the merged media data to all parties involved in this session. Involved UE#2.
  • the media rendering task may need to be re-divided due to some circumstances during the session, such as changes in the processing requirements of Conduct rendering negotiations.
  • the MRF network element merges the media data corresponding to the XR object rendered by UE#1 and the media data corresponding to the XR object rendered by the MRF network element as an example for illustration.
  • UE#2 may perform the combining process.
  • UE#1 sends media data corresponding to the rendered XR object to UE#2
  • the MRF network element sends media data corresponding to the rendered XR object to UE#2.
  • UE#2 performs merge processing.
  • other devices may also perform the merging process, which will not be described again.
  • FIG 13 is a schematic flow chart of an XR object rendering method 1300 provided by an embodiment of the present application.
  • This method 1300 can be used to implement the solution of the above method 900.
  • This method 1300 can be used in a scenario where rendering negotiation is completed based on HTTP/HTTPS messages.
  • the rendering negotiation can be completed during the call establishment process, for example.
  • it is assumed that the first network device and the second network device are OTT servers.
  • the method 1300 shown in Figure 13 may be used in the Figure 3 architecture.
  • the method 1300 may include the following steps.
  • UE#1 sends an HTTP request message to the OTT server to register.
  • the OTT server sends service indication information to UE#1.
  • the method by which the OTT server determines the service indication information is similar to the method by which the network device determines the service indication information in step 1001, and will not be described again.
  • the OTT server sends an HTTP response message to UE#1.
  • the HTTP response message includes service instructions. display information.
  • the OTT server sends the processing capability of the OTT server to UE#1.
  • the OTT server sends an HTTP response message to UE#1, where the HTTP response message includes the processing capabilities of the OTT server.
  • the service indication information and the processing capability of the OTT server can be sent in one message or in two messages, and this application does not limit this. If sent in two messages, this application does not limit the order of steps 1301 and 1302.
  • UE#1 determines that the OTT server can render the XR object.
  • UE#1 saves the processing capability and/or service indication information of the network device. Based on the service indication information, it can be learned whether the OTT server can render XR objects, that is, whether it supports XR object rendering. Based on the processing capability of the OTT server, it can be known whether the OTT server has enough capability to assist UE#1 in completing the rendering of the XR object. Steps 1301 to 1303 are optional steps, that is, the OTT server does not need to provide service indication information to UE#1, and UE#1 may default to UE#1 signing up for the network rendering function. Or the OTT server does not need to provide the OTT server's processing capabilities to UE#1, and UE#1 can assume that the OTT server has sufficient capabilities to assist UE#1 in rendering the XR object.
  • Scenario 1 UE#1 initiates rendering negotiation.
  • UE#1 determines the rendering division of XR objects to be rendered in the XR call, that is, part of the XR objects to be rendered in the XR call are rendered by the OTT server, and the other part of the XR objects to be rendered are rendered by UE#1.
  • UE#1 Based on the first processing requirement information of the XR call, UE#1 determines that the processing capability of UE#1 cannot complete the rendering of the XR object in the XR call, so UE#1 determines that split rendering is required for this XR call.
  • UE#1 has signed up for the network rendering function by default, and the default OTT server can assist in rendering the XR object, and then UE#1 determines the rendering division of the XR object to be rendered in the XR call.
  • UE#1 determines that it has signed up for the network rendering function based on the service indication information in 1301, that is, the OTT server supports XR object rendering.
  • the OTT server has sufficient capabilities to assist UE#1 in completing the rendering of XR objects, and then determines Rendering division of XR objects to be rendered in XR calls. If UE#1 determines that the OTT server does not support XR object rendering, as an example, UE#1 can perform rendering processing by itself.
  • the embodiment of this application mainly introduces the situation in which the OTT server supports XR object rendering.
  • UE#1 has signed up for the network rendering function by default, and UE#1 determines based on the processing capability of the OTT server in 1302 that the OTT server has sufficient capabilities to assist UE#1 in completing the rendering of the XR object, and then UE#1 Determine the rendering division of labor for the XR object to be rendered in the XR call.
  • UE#1 determines that the OTT server supports XR object rendering based on the service indication information in 1301, and determines based on the processing capability of the OTT server in 1302 that the OTT server has sufficient capabilities to assist UE#1 in completing the rendering of XR objects. (That is, the available computing power required by the OTT server to complete the rendering of the XR object to be rendered does not exceed the processing capability of the OTT server.) Then determine the rendering division of the XR object to be rendered for the XR call, that is, determine the rendering tasks that UE#1 and the OTT server each need to render. XR objects.
  • UE#1 sends an HTTP request message to the OTT server.
  • the HTTP request message includes the division of labor confirmation request information.
  • the division of labor confirmation request information is used to request the OTT server to accept the rendering division of labor.
  • the division of labor confirmation request information includes the second processing requirement information of the XR call.
  • the second processing requirement information of the XR call includes parameter C1, parameter C2, parameter D, and parameter E.
  • the details are similar to the division of labor confirmation request information in step 1112, and will not be described again.
  • the format of the second processing requirement information of the XR call can be json format, as follows:
  • the format of the second processing requirement information of the XR call may be XML format, as follows:
  • network_rendering_content represents parameter C1, which is the XR object to be rendered that needs to be rendered by the OTT server.
  • “rendering_type” indicates parameter C2, that is, whether the XR-M network element is required to render part of the XR objects to be rendered or whether the XR-M network element is required to render all the XR objects to be rendered.
  • “video_resolution” represents parameter D, which is the video resolution.
  • video_frame_rate represents parameter E, which is the video frame rate.
  • the OTT server accepts the division of labor and allocates rendering resources.
  • the method in which the OTT server allocates rendering resources based on the division of labor confirmation request information is similar to step 1013 and will not be described again.
  • the OTT server sends a division of labor confirmation response message to UE#1, and the division of labor confirmation response information instructs the OTT server to accept the rendering division of labor.
  • Scenario 2 UE#1 receives rendering negotiation.
  • the OTT server sends an HTTP request message to UE#1.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1, which is similar to step 1311 and will not be described again.
  • UE#1 sends an HTTP response message to the OTT server.
  • the HTTP response message includes division of labor confirmation request information.
  • Step 1323 is similar to step 1312 and will not be described again.
  • the OTT server accepts the rendering division of labor and allocates rendering resources.
  • the OTT server sends a division of labor confirmation response message to UE#1.
  • Scenario 3 UE#1 initiates media rendering renegotiation.
  • UE#1 determines the rendering division of the XR object to be rendered in the XR call of UE#1.
  • UE#1 determines the rendering division of XR objects to be rendered for UE#1's XR call based on the updated processing requirements of the XR call, the processing capabilities of UE#1, and the processing capabilities of the OTT server (optional). It is similar to step 1311 and will not be described again.
  • UE#1 sends a session update call request to the OTT server.
  • the session update call request includes labor division confirmation request information.
  • the division of labor confirmation request information is used to request the OTT server to accept the updated rendering division of labor.
  • UE#1 sends an HTTP message to the OTT server, where the HTTP message includes a session update call request, or the HTTP message is used to request a session update call.
  • Step 1332 is similar to step 1312 and will not be described again.
  • the OTT server accepts the updated rendering division and updates the rendering resources.
  • the OTT server re-determines the XR objects to be rendered that need to be rendered by the OTT server side according to the division of labor confirmation request information included in the session update call request, and updates the rendering resources according to the XR objects that need to be rendered by the OTT server side.
  • the OTT server can reuse the computing power resources reserved or allocated in step 1313, or can reallocate the computing power resources.
  • the reallocated computing power resources can be different from the computing power reserved or allocated in step 1313. resource.
  • the OTT server sends a division of labor confirmation response message to UE#1, and the division of labor confirmation response information instructs the OTT server to accept the updated rendering division of labor.
  • Scenario 4 UE#1 receives media rendering renegotiation.
  • the OTT server sends a session update call request to UE#1.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Graphics (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请提供了一种XR对象渲染的方法、通信装置及系统，该方法包括：终端设备确定或接受渲染分工，所述渲染分工是指所述终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，另一部分待渲染XR对象归所述终端设备渲染；所述终端设备渲染所述XR通话中归所述终端设备渲染的待渲染XR对象，并向所述网络侧渲染设备发送所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息。根据本申请提供的技术方案，实现终端设备和网络侧渲染设备之间的有效协同和渲染任务的按需分配。

Description

XR对象渲染的方法、通信装置及系统
本申请要求于2022年7月6日提交中国专利局、申请号为202210789069.1、申请名称为“XR对象渲染的方法、通信装置及系统”的中国专利申请的优先权，以及于2022年8月9日提交中国国家知识产权局、申请号为202210952860.X、申请名称为“XR对象渲染的方法、通信装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，并且更具体地，涉及一种XR对象渲染的方法、通信装置及系统。
背景技术
扩展现实(extended reality，XR)是指通过计算机将真实与虚拟相结合，打造一个人机交互的虚拟环境，为体验者带来虚拟世界与现实世界之间无缝转换的“沉浸感”。
以XR通话为例，XR通话将XR技术融入到传统实时音视频通话中，提供全新的音视频通话体验，例如包括但不限于：远程协助、远程定损、远程购物、远程医疗、远程沉浸式会议等。XR通话业务所涉及的复杂三维(three dimensional，3D)场景和物体对渲染算力的要求很高。因此，提供一种渲染方式以尽可能满足3D场景和物体的要求，是值得考虑的问题。
发明内容
本申请实施例提供一种XR对象渲染的方法、通信装置及系统，通过分配渲染任务，尽可能满足3D场景和物体的要求。
第一方面，提供了一种XR对象渲染的方法，该方法可以由终端设备执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由终端设备执行为例进行说明。
该方法可以包括：终端设备确定或接受渲染分工，渲染分工是指：终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，另一部分待渲染XR对象归终端设备渲染；终端设备渲染XR通话中归终端设备渲染的待渲染XR对象，并向网络侧渲染设备发送XR通话中归网络侧渲染设备渲染的待渲染XR对象。
基于上述技术方案，终端设备可确定或接受XR通话中待渲染XR对象的渲染分工，即确定哪些待渲染XR对象由终端设备负责渲染，哪些待渲染XR对象由网络侧渲染设备负责渲染，这样，针对XR通话中待渲染XR对象，可以在终端设备和网络侧渲染设备之间动态地分配渲染任务，实现终端设备和网络侧渲染设备之间的有效协同和渲染任务的按需分配。
结合第一方面，在第一方面的某些实现方式中，终端设备接受渲染分工包括：终端设备接收来自网络侧控制设备的分工指示信息，分工指示信息指示终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染。
基于上述技术方案，网络设备和终端设备之间可进行渲染协商，即网络侧控制设备可确定XR通话中待渲染XR对象的渲染分工，即确定哪些待渲染XR对象由终端设备负责渲染，哪些待渲染XR对象由网络侧渲染设备负责渲染，这样，针对XR通话中待渲染XR对象，可以通过网络侧控制设备，在终端设备和网络侧渲染设备之间动态地分配渲染任务，实现终端设备和网络侧渲染设备之间的有效协同和渲染任务的按需分配。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备向网络侧控制设备发送终端设备的处理能力信息。
基于上述技术方案，终端设备可以向网络侧控制设备提供终端设备的处理能力信息，以便网络侧控制设备确定是否要对XR通话中的待渲染XR对象进行拆分渲染。这样，网络侧控制设备可以根据终端设备实际的处理能力，确定是否对XR通话中的待渲染XR对象进行拆分渲染，符合终端设备的处理 能力。
结合第一方面，在第一方面的某些实现方式中，终端设备向网络侧接入设备发送注册消息或会话呼叫消息以触发网络侧接入设备向网络侧控制设备发送终端设备的处理能力信息，注册消息或会话呼叫消息包含终端设备的处理能力信息。
基于上述技术方案，终端设备可以在注册流程或会话呼叫流程中，向网络侧控制设备发送终端设备的处理能力信息。
结合第一方面，在第一方面的某些实现方式中，终端设备的处理能力信息包括终端设备的渲染可用算力，或者，终端设备的处理能力信息包括终端设备的渲染可用算力和终端设备支持的渲染分工方式。
结合第一方面，在第一方面的某些实现方式中，终端设备支持的渲染分工方式包括以下至少一项：按层分工、按类型分工。
结合第一方面，在第一方面的某些实现方式中，终端设备的渲染可用算力是终端设备基于自身计算资源的配置确定的，或者，终端设备的渲染可用算力是终端设备基于终端设备的剩余计算资源或可用计算资源确定的。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备向网络侧控制设备发送XR通话的处理需求信息。
基于上述技术方案，终端设备可以向网络侧控制设备提供XR通话的处理需求信息，以便网络侧控制设备基于XR通话的处理需求信息确定渲染分工。这样，可以使得网络侧控制设备确定的渲染分工满足XR通话的处理需求。
结合第一方面，在第一方面的某些实现方式中，XR通话的处理需求信息包括以下至少一项：XR通话的待渲染XR对象的信息、XR通话的视频分辨率、XR通话的视频帧率。
结合第一方面，在第一方面的某些实现方式中，终端设备根据以下至少一项确定渲染分工：终端设备的处理能力信息、网络侧渲染设备的处理能力信息、XR通话的处理需求信息。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备接收来自网络侧控制设备的网络侧渲染设备的处理能力信息。
结合第一方面，在第一方面的某些实现方式中，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力；或者，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力和网络侧渲染设备支持的渲染分工方式。
结合第一方面，在第一方面的某些实现方式中，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的计算资源的配置确定的，或者，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的剩余计算资源或可用计算资源确定的。
结合第一方面，在第一方面的某些实现方式中，渲染分工方式包括以下至少一项：按层分工、按类型分工。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备向网络侧控制设备发送分工确认请求信息，分工确认请求信息用于请求接受渲染分工，分工确认请求信息包括用于确定XR通话的待渲染XR对象中归网络侧渲染设备渲染的待渲染XR对象的信息。
基于上述技术方案，终端设备确定好XR通话中的待渲染XR对象中需要网络侧渲染设备渲染的待渲染XR对象后，可以通过分工确认请求信息和网络设备之间进行渲染协商，从而实现终端设备和网络侧渲染设备之间的有效协同和渲染任务的按需分配。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备接收来自网络侧控制设备的分工确认响应信息，分工确认响应信息指示渲染分工被接受。
基于上述技术方案，终端设备根据分工确认响应信息确定网络侧渲染设备将渲染归网络侧渲染设备渲染的待渲染XR对象时，可以将归网络侧渲染设备渲染的待渲染XR对象发送至网络侧渲染设备进行渲染。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备获取网络侧服务指示信息，网络侧服务指示信息指示网络侧渲染设备能够提供对XR对象进行渲染的服务(即渲染XR通话中的待渲染XR对象的能力)。
结合第一方面，在第一方面的某些实现方式中，方法还包括：终端设备向网络侧渲染设备发送渲染后XR对象，渲染后XR对象为终端设备对XR通话中归终端设备渲染的待渲染XR对象进行渲染所得。
基于上述技术方案，终端设备可以向网络侧渲染设备发送渲染后XR对象，也即渲染后的XR对象对应的媒体数据(如视频流)，以便网络侧渲染设备对终端设备渲染后的XR对象对应的媒体数据和网络侧渲染设备渲染后的XR对象对应的媒体数据进行合并处理，从而为XR通话涉及的终端设备提供完整的媒体数据(如完整的视频流)。
结合第一方面，在第一方面的某些实现方式中，分工指示信息包括XR通话中归终端设备渲染的待渲染XR对象的信息，终端设备向网络侧渲染设备发送XR通话中归网络侧渲染设备渲染的待渲染XR对象之前，方法还包括：终端设备根据XR通话中的待渲染XR对象和XR通话中归终端设备渲染的待渲染XR对象的信息，确定XR通话中归网络侧渲染设备渲染的待渲染XR对象。
基于上述技术方案，终端设备可以根据XR通话中的待渲染XR对象和终端设备自身需要渲染的待渲染XR对象，确定网络侧渲染设备需要渲染的待渲染XR对象，以便向网络侧渲染设备发送网络侧渲染设备负责渲染的待渲染XR对象的相关数据。
结合第一方面，在第一方面的某些实现方式中，分工指示信息包括XR通话中归网络侧渲染设备渲染的待渲染XR对象的信息，终端设备对渲染XR通话中归终端设备渲染的待渲染XR对象进行渲染之前，方法还包括：终端设备根据XR通话中的待渲染XR对象和XR通话中归网络侧渲染设备渲染的待渲染XR对象的信息，确定XR通话中归终端设备渲染的待渲染XR对象。
基于上述技术方案，终端设备可以根据XR通话中的待渲染XR对象和网络侧渲染设备需要渲染的待渲染XR对象，确定终端设备需要渲染的待渲染XR对象，以便对终端设备需要渲染的待渲染XR对象进行渲染。
结合第一方面，在第一方面的某些实现方式中，分工指示信息包括XR通话中归终端设备渲染的待渲染XR对象的信息和XR通话中归网络侧渲染设备渲染的待渲染XR对象的信息。
结合第一方面，在第一方面的某些实现方式中，所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
第二方面，提供了一种XR对象渲染的方法，该方法可以由网络设备执行，或者，也可以由网络设备的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由网络侧控制设备执行为例进行说明。
该方法可以包括：网络侧控制设备确定或接受渲染分工，渲染分工是指终端设备的XR通话中的一部分待渲染对象归网络侧渲染设备渲染，另一部分待渲染XR对象归终端设备渲染；网络侧控制设备触发XR通话中归终端设备渲染的XR对象被终端设备渲染，以及XR通话中归网络侧渲染设备渲染的待渲染XR对象被网络侧渲染设备渲染。
结合第二方面，在第二方面的某些实现方式中，网络侧控制设备触发XR通话中归终端设备渲染的XR对象被终端设备渲染，以及XR通话中归网络侧渲染设备渲染的待渲染XR对象被网络侧渲染设备渲染，包括：网络侧控制设备向终端设备发送分工指示信息，分工指示信息指示终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染。
结合第二方面，在第二方面的某些实现方式中，方法还包括：响应于确定终端设备的处理能力无法满足XR通话的处理需求，网络侧控制设备确定终端设备和网络侧渲染设备分别渲染XR通话中的部分待渲染XR对象。
可选地，网络侧控制设备确定(或者判断)终端设备的处理能力无法满足XR通话的处理需求。
结合第二方面，在第二方面的某些实现方式中，网络侧控制设备根据以下至少一项确定渲染分工：终端设备的处理能力信息、网络侧渲染设备的处理能力信息、XR通话的处理需求信息。
结合第二方面，在第二方面的某些实现方式中，方法还包括：网络侧控制设备接收来自终端设备的XR通话的处理需求信息。
结合第二方面，在第二方面的某些实现方式中，XR通话的处理需求信息包括以下至少一项：XR通话的待渲染XR对象的信息、XR通话的视频分辨率、XR通话的视频帧率。
结合第二方面，在第二方面的某些实现方式中，方法还包括：网络侧控制设备接收来自终端设备的该终端设备的处理能力信息。
结合第二方面，在第二方面的某些实现方式中，终端设备的处理能力信息包括终端设备的渲染可用算力，或者，终端设备的处理能力信息包括终端设备的渲染可用算力和终端设备支持的渲染分工方式。
结合第二方面，在第二方面的某些实现方式中，终端设备的渲染可用算力是基于终端设备自身计算资源的配置确定的，或者，终端设备的渲染可用算力是基于终端设备的剩余计算资源或可用计算资源确定的。
结合第二方面，在第二方面的某些实现方式中，方法还包括：网络侧控制设备接收来自网络侧渲染设备的网络侧渲染设备的处理能力信息。
结合第二方面，在第二方面的某些实现方式中，网络侧控制设备接受渲染分工，包括：网络侧控制设备接收来自终端设备的分工确认请求信息，分工确认请求信息用于请求接受渲染分工，分工确认请求信息包括用于确定XR通话的待渲染XR对象中归网络侧渲染设备渲染的待渲染XR对象的信息；网络侧控制设备根据分工确认请求信息接受渲染分工。
结合第二方面，在第二方面的某些实现方式中，网络侧控制设备触发XR通话中归终端设备渲染的XR对象被终端设备渲染，以及XR通话中归网络侧渲染设备渲染的待渲染XR对象被网络侧渲染设备渲染，包括：网络侧控制设备向终端设备发送分工确认响应信息，分工确认响应信息指示渲染分工被接受。
结合第二方面，在第二方面的某些实现方式中，方法还包括：网络侧控制设备向终端设备发送网络侧渲染设备的处理能力信息。
结合第二方面，在第二方面的某些实现方式中，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力，或者，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力和网络侧渲染设备支持的渲染分工方式。
结合第二方面，在第二方面的某些实现方式中，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的计算资源的配置确定的，或者，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的剩余计算资源或可用计算资源确定的。
结合第二方面，在第二方面的某些实现方式中，渲染分工方式包括以下至少一项：按层分工、按类型分工。
结合第二方面，在第二方面的某些实现方式中，方法还包括：网络侧控制设备向终端设备发送网络侧服务指示信息，网络侧服务指示信息指示网络侧渲染设备能够提供对XR对象进行渲染的服务。
结合第二方面，在第二方面的某些实现方式中，分工指示信息包括以下至少一项：XR通话中归终端设备渲染的待渲染XR对象的信息、XR通话中归网络侧渲染设备渲染的待渲染XR对象的信息。
结合第二方面，在第二方面的某些实现方式中，方法还包括：网络侧控制设备向网络侧渲染设备发送请求消息，请求消息用于请求以下至少一项：网络侧渲染设备的地址信息、网络侧渲染设备的渲染资源信息；其中，网络侧渲染设备的地址信息用于使与XR通话相关的终端设备通过网络侧接入设备连接到网络侧渲染设备，渲染资源信息为网络侧渲染设备用来渲染归所述网络侧渲染设备渲染的待渲染XR对象的资源的信息；网络侧控制设备接收来自网络侧渲染设备的请求消息的响应。
结合第二方面，在第二方面的某些实现方式中，请求消息中包括网络侧渲染设备待渲染的XR对象所需的算力。
结合第二方面，在第二方面的某些实现方式中，网络侧控制设备为XR控制面网元，网络侧渲染设备为XR媒体面网元；或者，网络侧控制设备为应用服务器，网络侧渲染设备为媒体资源功能网元；或者，网络侧控制设备为互联网业务信令服务器，网络侧渲染设备为互联网业务媒体服务器。
第二方面及各个可能的设计的有益效果可以参考第一方面相关的描述，在此不予赘述。
第三方面，提供了一种XR对象渲染的方法，该方法可以由网络设备执行，或者，也可以由网络设备的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由网络侧渲染设 备执行为例进行说明。
该方法可以包括：网络侧渲染设备接收来自终端设备的第二部分待渲染XR对象；网络侧渲染设备对第二部分待渲染XR对象进行渲染；网络侧渲染设备接收来自终端设备的渲染后的第一部分待渲染XR对象；网络侧渲染设备对渲染后的第一部分待渲染XR对象和渲染后的第二部分待渲染XR对象进行合并处理，得到合并后的媒体数据；其中，第一部分待渲染XR对象和第二部分待渲染XR对象分别为终端设备的XR通话中的部分待渲染XR对象。
其中，第一部分待渲染XR对象为XR通话中归终端设备渲染的待渲染XR对象，第二部分待渲染XR对象为XR通话中归网络侧渲染设备渲染的待渲染XR对象。
基于上述技术方案，对于XR通话的待渲染XR对象，可以由终端设备渲染部分XR对象，网络侧渲染设备渲染部分XR对象。这样，针对XR通话，可以通过网络侧控制设备，在终端设备和网络侧渲染设备之间动态地分配渲染任务，实现终端设备和网络侧渲染设备之间的有效协同和渲染任务的按需分配。进一步，终端设备可以向网络侧渲染设备发送渲染后的第一部分待渲染XR对象，也即渲染后的第一部分待渲染XR对象对应的媒体数据(如视频流)，以便网络侧渲染设备对渲染后的第一部分待渲染XR对象对应的媒体数据和渲染后的第二部分待渲染XR对象对应的媒体数据进行合并处理，从而为XR会话涉及的终端设备提供完整的媒体数据(如视频流)。
结合第三方面，在第三方面的某些实现方式中，方法还包括：网络侧渲染设备向XR通话对应的终端设备发送合并后的媒体数据。
结合第三方面，在第三方面的某些实现方式中，网络侧渲染设备向网络侧控制设备发送网络侧渲染设备的处理能力信息，网络侧渲染设备的处理能力信息用于确定分工指示信息，分工指示信息指示：终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染。
结合第三方面，在第三方面的某些实现方式中，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力，或者，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力和网络侧渲染设备支持的渲染分工方式。
结合第三方面，在第三方面的某些实现方式中，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的计算资源的配置确定的，或者，网络侧渲染设备的渲染可用算力是XR会话建立时基于网络侧渲染设备的剩余计算资源或可用计算资源确定的。
结合第三方面，在第三方面的某些实现方式中，方法还包括：网络侧渲染设备接收来自网络侧控制设备的请求消息，请求消息用于请求以下至少一项：网络侧渲染设备的地址信息、网络侧渲染设备的渲染资源信息；其中，网络侧渲染设备的地址信息用于使与XR通话相关的终端设备通过网络侧接入设备连接到网络侧渲染设备，渲染资源信息为网络侧渲染设备用来渲染归所述网络侧渲染设备渲染的待渲染XR对象的资源的信息；网络侧渲染设备向网络侧控制设备发送请求消息的响应。
结合第三方面，在第三方面的某些实现方式中，请求消息中包括网络侧渲染设备渲染第二部分待渲染XR对象所需的算力。
结合第三方面，在第三方面的某些实现方式中，网络侧控制设备为XR控制面网元，网络侧渲染设备为XR媒体面网元；或者，网络侧控制设备为应用服务器，网络侧渲染设备为媒体资源功能网元；或者，网络侧控制设备为互联网业务信令服务器，网络侧渲染设备为互联网业务媒体服务器。
第四方面，提供了一种XR对象渲染的方法，该方法可以由网络设备执行，或者，也可以由网络设备的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由网络侧控制设备执行为例进行说明。
该方法可以包括：网络侧控制设备向网络侧渲染设备发送请求消息，请求消息用于请求网络侧渲染设备渲染终端设备的XR通话中归网络侧渲染设备渲染的待渲染XR对象，请求消息包括归网络侧渲染设备渲染的待渲染XR对象所需的算力；网络侧控制设备接收来自网络侧渲染设备的请求消息的响应，请求消息的响应用于通知网络侧控制设备：网络侧渲染设备是否将渲染XR通话中归网络侧渲染设备渲染的待渲染XR对象。
可选地，网络侧渲染设备的请求消息的响应包括网络侧渲染设备的地址信息，网络侧渲染设备的地址信息用于使与XR通话相关的终端设备通过网络侧接入设备连接到网络侧渲染设备。此时，该网 络侧渲染设备的地址信息可隐含通知网络侧控制设备：网络侧渲染设备是否将渲染XR通话中归网络侧渲染设备渲染的待渲染XR对象。
基于上述技术方案，网络侧控制设备可以向网络侧渲染设备发送由网络侧渲染设备渲染的待渲染XR对象所需的算力，进而网络侧渲染设备可以基于该待渲染XR对象所需的算力合理的分配资源。
结合第四方面，在第四方面的某些实现方式中，请求消息用于请求网络侧渲染设备的地址信息。
结合第四方面，在第四方面的某些实现方式中，在网络侧控制设备向网络侧渲染设备发送请求消息之前，方法还包括：网络侧控制设备接收来自网络侧渲染设备的网络侧渲染设备的处理能力信息。
结合第四方面，在第四方面的某些实现方式中，方法还包括：网络侧控制设备根据网络侧渲染设备的处理能力信息，确定XR通话中归网络侧渲染设备渲染的待渲染XR对象。
结合第四方面，在第四方面的某些实现方式中，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力，或者，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力和网络侧渲染设备支持的渲染分工方式。
结合第四方面，在第四方面的某些实现方式中，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的计算资源的配置确定的，或者，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的剩余计算资源或可用计算资源确定的。
结合第四方面，在第四方面的某些实现方式中，网络侧控制设备为XR控制面网元，网络侧渲染设备为XR媒体面网元；或者，网络侧控制设备为应用服务器，网络侧渲染设备为媒体资源功能网元；或者，网络侧控制设备为互联网业务信令服务器，网络侧渲染设备为互联网业务媒体服务器。
第五方面，提供了一种XR对象渲染的方法，该方法可以由网络设备执行，或者，也可以由网络设备的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由网络侧渲染设备执行为例进行说明。
该方法可以包括：网络侧渲染设备接收来自网络侧控制设备的请求消息，请求消息用于请求网络侧渲染设备渲染终端设备的XR通话中归网络侧渲染设备渲染的待渲染XR对象，请求消息包括XR通话中归网络侧渲染设备渲染的待渲染XR对象所需的算力；网络侧渲染设备向网络侧控制设备发送请求消息的响应，请求消息的响应用于通知网络侧控制设备：网络侧渲染设备是否将渲染XR通话中归网络侧渲染设备渲染的待渲染XR对象。
结合第五方面，在第五方面的某些实现方式中，请求消息用于请求网络侧渲染设备的地址信息。
结合第五方面，在第五方面的某些实现方式中，方法还包括：网络侧渲染设备根据网络侧渲染设备待渲染的XR对象所需的算力，确定网络侧渲染设备渲染XR通话中归网络侧渲染设备渲染的待渲染XR对象所需的资源。
结合第五方面，在第五方面的某些实现方式中，在网络侧渲染设备接收来自网络侧控制设备的请求消息之前，方法还包括：网络侧渲染设备向网络侧控制设备发送网络侧渲染设备的处理能力信息。
结合第五方面，在第五方面的某些实现方式中，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力，或者，网络侧渲染设备的处理能力信息包括网络侧渲染设备的渲染可用算力和网络侧渲染设备支持的渲染分工方式。
结合第五方面，在第五方面的某些实现方式中，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的计算资源的配置确定的，或者，网络侧渲染设备的渲染可用算力是基于网络侧渲染设备的剩余计算资源或可用计算资源确定的。
结合第五方面，在第五方面的某些实现方式中，网络侧控制设备为XR控制面网元，网络侧渲染设备为XR媒体面网元；或者，网络侧控制设备为应用服务器，网络侧渲染设备为媒体资源功能网元；或者，网络侧控制设备为互联网业务信令服务器，网络侧渲染设备为互联网业务媒体服务器。
第五方面及各个可能的设计的有益效果可以参考第四方面相关的描述，在此不予赘述。
第六方面，提供了一种XR对象渲染的方法，该方法可以由通信系统(如包括终端设备和网络设备的通信系统)执行，或者，也可以由通信系统的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由终端设备执行为例进行说明。
该方法可以包括：网络侧控制设备确定或接受渲染分工，渲染分工是指：终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，另一部分待渲染XR对象归终端设备渲染；网络侧控 制设备触发XR通话中归终端设备渲染的XR对象被终端设备渲染，以及XR通话中归网络侧渲染设备渲染的待渲染XR对象被网络侧渲染设备渲染。
结合第六方面，在第六方面的某些实现方式中，网络侧控制设备向终端设备发送分工指示信息，分工指示信息指示终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染；终端设备接收该分工指示信息，并根据分工指示信息渲染XR通话中归终端设备渲染的待渲染XR对象；终端设备向网络侧渲染设备发送XR通话中归网络侧渲染设备渲染的待渲染XR对象。
结合第六方面，在第六方面的某些实现方式中，方法还包括：终端设备向网络侧控制设备发送终端设备的处理能力信息。
结合第六方面，在第六方面的某些实现方式中，终端设备向网络侧控制设备发送终端设备的处理能力信息，包括：终端设备向网络侧接入设备发送注册消息或会话呼叫消息以触发网络侧接入设备向网络侧控制设备发送终端设备的处理能力信息，注册消息或会话呼叫消息包含终端设备的处理能力信息。
结合第六方面，在第六方面的某些实现方式中，方法还包括：终端设备向网络侧控制设备发送XR通话的处理需求信息。
结合第六方面，在第六方面的某些实现方式中，方法还包括：终端设备向网络侧渲染设备发送渲染后XR对象，渲染后XR对象为终端设备对XR通话中归终端设备渲染的待渲染XR对象进行渲染所得。
结合第六方面，在第六方面的某些实现方式中，终端设备确定渲染分工，向网络侧控制设备发送分工确认请求信息，分工确认请求信息用于请求接受渲染分工，网络侧控制设备接收该分工确认请求，并根据该分工确认请求接受渲染分工。
结合第六方面，在第六方面的某些实现方式中，方法还包括：网络侧控制设备向终端设备发送分工确认响应信息，分工确认响应信息指示渲染分工被接受，终端设备接收该分工确认响应信息，并确认该渲染分工。
结合第六方面，在第六方面的某些实现方式中，网络侧控制设备为XR控制面网元，网络侧渲染设备为XR媒体面网元；或者，网络侧控制设备为应用服务器，网络侧渲染设备为媒体资源功能网元；或者，网络侧控制设备为互联网业务信令服务器，网络侧渲染设备为互联网业务媒体服务器。
第六方面可以参考第一方面或第二方面中的描述，在此不予赘述。
第七方面，提供了一种XR对象渲染的方法，该方法可以由通信系统(如包括终端设备和网络设备的通信系统)执行，或者，也可以由通信系统的组成部件(例如芯片或者电路)执行，对此不作限定。为了便于描述，下面以由终端设备执行为例进行说明。
该方法可以包括：网络侧控制设备向网络侧渲染设备发送请求消息，请求消息用于请求网络侧渲染设备渲染终端设备的XR通话中归网络侧渲染设备渲染的待渲染XR对象，请求消息包括归网络侧渲染设备渲染的待渲染XR对象所需的算力；网络侧渲染设备向网络侧控制设备发送请求消息的响应，请求消息的响应用于通知网络侧控制设备：网络侧渲染设备是否将渲染XR通话中归网络侧渲染设备渲染的待渲染XR对象。
结合第七方面，在第七方面的某些实现方式中，网络侧控制设备向网络侧渲染设备发送请求消息之前，方法还包括：所述网络侧渲染设备向所述网络侧控制设备发送所述网络侧渲染设备的处理能力信息。
结合第七方面，在第七方面的某些实现方式中，所述网络侧渲染设备根据所述网络侧渲染设备待渲染的XR对象所需的算力，确定所述网络侧渲染设备渲染所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象所需的资源。
结合第七方面，在第七方面的某些实现方式中，网络侧控制设备为XR控制面网元，网络侧渲染设备为XR媒体面网元；或者，网络侧控制设备为应用服务器，网络侧渲染设备为媒体资源功能网元；或者，网络侧控制设备为互联网业务信令服务器，网络侧渲染设备为互联网业务媒体服务器。
第七方面可以参考第四方面或第五方面中的描述，在此不予赘述。
第八方面，提供一种通信装置，该装置用于执行上述第一方面至第七方面任一种可能实现方式中 的方法。具体地，该装置可以包括用于执行第一方面至第七方面任一种可能实现方式中的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为通信设备(如终端设备，又如网络设备)。当该装置为通信设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于通信设备(如终端设备，又如网络设备)的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第九方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面至第七方面任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为通信设备(如终端设备，又如网络设备)。
在另一种实现方式中，该装置为用于通信设备(如终端设备，又如网络设备)的芯片、芯片系统或电路。
第十方面，提供一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第十一方面，提供一种计算机可读存储介质，该计算机可读介质存储用户设备执行的程序代码，该程序代码包括用于执行上述第一方面至第七方面任一种可能实现方式中的方法。
第十二方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第七方面任一种可能实现方式中的方法。
第十三方面，提供一种通信系统，包括前述的终端设备、网络侧控制设备、网络侧渲染设备中的至少一项。
附图说明
图1是适用于本申请一实施例的通信系统的示意图。
图2是适用于本申请另一实施例的通信系统的示意图。
图3是适用于本申请另一实施例的通信系统的示意图。
图4是本申请实施例提供的一种XR对象渲染的方法400的示意图。
图5是本申请实施例提供的一种XR对象渲染的方法500的示意性流程图。
图6是本申请实施例提供的一种XR对象渲染的方法600的示意性流程图。
图7是本申请实施例提供的一种XR对象渲染的方法700的示意性流程图。
图8是本申请实施例提供的一种XR对象渲染的方法800的示意性流程图。
图9是本申请实施例提供的一种XR对象渲染的方法900的示意图。
图10是本申请实施例提供的一种XR对象渲染的方法1000的示意性流程图。
图11是本申请实施例提供的一种XR对象渲染的方法1100的示意性流程图。
图12是本申请实施例提供的一种XR对象渲染的方法1200的示意性流程图。
图13是本申请实施例提供的一种XR对象渲染的方法1300的示意性流程图。
图14是本申请实施例提供的一种通信装置1400的示意图。
图15是本申请实施例提供的一种通信装置1500的示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线 (new radio，NR)系统、在网络上层(over the top，OTT)系统(或者说通过互联网向用户提供各种应用服务的系统)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
本申请实施例中的终端设备也可以称为用户设备(user equipment，UE)、接入终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
作为示例，一些终端的举例为：虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
本申请实施例中的网络设备可以是用于与终端设备通信的设备。作为示例，网络设备例如可以为用于为终端设备提供服务的通信网络中的设备。在本申请实施例中，通信网络可包括运营商IP多媒体子系统(IP multimedia subsystem，IMS)网络，也可包括搭建的通信网络，或者也可包括其他通信网络，对此不予限制。
作为示例，网络设备例如可以包括以下至少一项：扩展现实(extended reality，XR)控制面功能(XR control function，XR-C)网元、XR媒体面功能(XR media function，XR-M)网元、应用服务器(application server，AS)、媒体资源功能网元、OTT XR通话服务器。下面简单介绍一下各设备。
1、XR-C网元：XR业务的核心网控制面网元，可提供渲染协商功能。举例来说，XR-C网元可在终端设备和网络侧设备(如XR-M网元)之间就XR通话业务的渲染操作进行协调、确定渲染操作的分工等。
作为示例，XR-C网元为AR控制面功能(AR control function，AR-C)网元或AR应用服务器(AR application server，AR-AS)。
2、XR-M网元：XR业务的核心网媒体面网元，可用于提供XR对象渲染功能。
作为示例，XR-M网元为AR媒体面功能(AR media function，AR-M)网元。
可以理解，XR-C网元和XR-M网元，可以理解为用于实现不同功能的网元，可以按需组合成网络切片。XR-C网元和XR-M网元可以是各自独立的硬件设备，也可以集成于同一硬件设备中，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能模块，本申请对于上述网元的具体形态不作限定。还可以理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。
还可以理解，XR-C网元和XR-M网元可以由IMS运营商提供，也可以由第三方提供，不予限制。
3、AS：是指为终端设备提供应用层服务的服务器。从图中可看出，AS为IMS中的AS。
4、媒体资源功能网元：用于对媒体数据(如XR通话相关的媒体数据)进行处理(例如渲染XR对象)，可参与渲染协商。作为示例，媒体资源功能网元可以是3GPP标准规范中的多媒体资源功能(multimedia resource function，MRF)网元，其中包括多媒体资源控制器(multimedia resource function controller，MRFC)和多媒体资源处理器(multimedia resource function processor，MRFP)。
5、OTT服务器：是指用于提供运营商网络之上业务(即OTT业务，也称为互联网业务)的服务器，也称为互联网业务服务器。
6、OTT XR通话服务器：是指用于提供运营商网络之上XR通话业务(即OTT XR通话业务)的服务器，或者是指承载XR通话业务的OTT服务器，可提供渲染协商功能，例如，在终端设备和网络侧设备之间就XR通话业务的渲染操作进行协调、确定渲染操作的分工等。此外，OTT XR通话服务器还可用于实现OTT XR通话业务的信令处理和路由，以及XR通话业务的媒体处理。作为示例，OTT XR通话服务器可包括OTT XR通话业务信令服务器(或互联网XR通话业务信令服务器)、OTT XR通话业务媒体处理服务器(或互联网XR通话业务媒体处理服务器)、OTT XR通话业务路由服务器。示例性地，OTT XR通话业务信令服务器例如负责处理与XR通话业务的信令或消息，OTT XR通话业务媒体处理服务器例如负责处理与XR通话业务的媒体数据，OTT XR通话业务路由服务器例如负责路由或转发与XR通话业务有关的信令或消息。OTT XR通话服务器的命名不对本申请实施例的保护范围造成限定。
如无特别说明，本申请后续实施例中的OTT服务器均指OTT XR通话服务器，将不再赘述。
网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请实施例中对网络设备和终端设备所处的场景不做限定。
为便于理解本申请实施例，对本申请中涉及到的术语做简单说明。
1、XR：是指通过计算机将真实与虚拟相结合，打造一个人机交互的虚拟环境。XR是VR、AR、混合显示(mixed reality，MR)等多种技术的统称。通过将上述多种技术相融合，为体验者带来虚拟世界与现实世界之间无缝转换的“沉浸感”。以XR通话为例，XR通话将XR技术融入到传统实时音视频通话中，提供全新的音视频通话体验，例如包括但不限于：远程协助、远程定损、远程购物、远程医疗、远程沉浸式会议等。
2、XR对象，是指XR场景中(如XR通话场景中)的组件(或者说XR场景中的物体)，主要描述XR场景中的某一类或某个组成部分。例如，XR场景中的XR对象可以包括虚拟会议室、虚拟人物、虚拟椅子、虚拟桌子等。
3、渲染(render)：是指对XR对象的原始数据进行转换的过程，在该过程中，不可直接显示的XR对象的原始数据，被转换或者加工为可显示(通过显示器或XR眼镜)为具有三维(three dimensional，3D)效果的图像的媒体数据。为简洁和便于描述，本申请实施例中，将XR对象的原始数据简称为待渲染XR对象，将可显示为具有3D效果的图像的媒体数据，简称为渲染后XR对象。
示例性地，渲染后XR对象对应的媒体数据可包括用于显示XR对象的视频图像帧序列(或者简称为视频帧序列)，可以以视频流的形式通过网络传输到对端终端设备(或本端终端设备)。渲染后XR对象对应的媒体数据在屏幕上(如终端设备的屏幕上)显示以后，可具有3D效果，即用户可以通过屏幕中呈现的物体大小和远近距离感知看到立体的画面。
4、数据信道(data channel，DC)：本申请实施例所述的数据通道，例如可以是IMS数据通道(IMS data channel)，即IMS中的数据通道，可以用于基于流控制传输协议(stream control transmission protocol，SCTP)传输数据；也就是说，数据通道是一种基于SCTP传输数据的逻辑通道或数据连接。本申请实施例中DC可用于传输信令或数据，如渲染分工交互信息和/或XR对象。
5、算力：在本申请实施例中，用算力来衡量设备对XR对象的渲染处理能力。
上面对本申请中涉及到的术语做了简单说明，下文实施例中不再赘述。
首先结合图1至图3简单介绍适用于本申请的网络架构，如下。
图1是适用于本申请一实施例的通信系统的示意图。如图1所示，该通信系统可以包括UE、IMS网络中的网元、XR-C网元、XR-M网元。其中，IMS网络中的网元例如可以包括：数据信道控制面功能(data channel server control function，DCS-C)网元、AS、数据信道媒体面功能(data channel server media function，DCS-M)网元、IMS接入网关(IMS access gateway，IMS-AGW)、代理-呼叫会话控制功能(proxy-call session control function，P-CSCF)网元、查询-呼叫会话控制功能(interrogating-call session control function，I-CSCF)网元、服务-呼叫会话控制功能(serving-call session control function，S-CSCF)网元。下面简单介绍一下各个网元，未详细描述的可参考前面的说明。
1、IMS-AGW：主要负责提供接入IMS网络入口的媒体锚定点。
2、P-CSCF网元：位于拜访网络，是终端设备接入IMS网络的入口节点，主要负责终端设备与归属网络之间会话初始协议(session initialization protocol，SIP)信令的转发。
3、I-CSCF网元：位于归属网络，是归属网络的统一入口点，主要负责分配或者查询为终端设备服务的S-CSCF网元。
4、S-CSCF网元：位于归属网络，是IMS网络的中心节点，主要负责终端设备的注册、鉴权、会话、路由和业务触发。
5、DCS-C网元：DC控制面网元，主要负责提供DC管理功能。
6、DCS-M网元：DC媒体面网元，主要负责提供DC媒体处理功能。
图2是适用于本申请另一实施例的通信系统的示意图。如图2所示，该通信系统可以包括UE、IMS网络中的网元。其中，IMS网络中的网元例如可以包括：AS、MRF网元、IMS-AGW、P-CSCF网元、I-CSCF网元、S-CSCF网元。关于各网元的介绍可参考前面的说明。
图3是适用于本申请另一实施例的通信系统的示意图。如图3所示，该通信系统可以包括UE和OTT服务器。关于各网元的介绍可参考前面的说明。
可以理解，图1至图3仅为便于理解而示例的简化示意图，本申请并未限定于此。作为示例，这些通信系统分别还可以包括其他UE，或者，这些通信系统分别还可以包括其他UE以及其他UE所属的通信网络。以图1为例，为区分，将图1中的UE记为UE#1，其他UE记为UE#2，UE#2可与图1中的IMS网络通信。进一步可选地，该通信系统中还可以包括UE#2以及UE#2所属的IMS网络，UE#2可通过UE#2所属的IMS网络与UE#1所属的IMS网络通信。UE#2所属的IMS网络中的网元可参考UE#1所属的IMS网络中的网元，对此不予限制。
还可以理解，本申请实施例中提及的网元，如P-CSCF网元、I-CSCF网元、MRF网元、S-CSCF网元等功能网元，可以理解为用于实现不同功能的网元，可以按需组合成网络切片。这些网元可以是各自独立的硬件设备，也可以集成于同一硬件设备中，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能模块，本申请对于上述网元的具体形态不作限定。还可以理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在6G网络以及未来其它的网络中采用其他命名的可能。
随着XR技术的不断发展和应用，人们对XR视频的画质和分辨率的要求越来越高，XR所涉及的复杂三维(three dimensional，3D)场景和物体对渲染算力的要求很高。
一种渲染方式是：由终端设备进行渲染处理。但是，终端设备因软件/硬件资源、体积、重量、功耗和散热等因素限制，其渲染的处理能力可能无法满足复杂3D场景和物体的要求，从而限制了XR业务的应用和效果。
另一种渲染方式是：由网络设备进行渲染处理。但是，这种处理方式需要终端设备将待渲染XR对象的相关数据发送给网络设备，网络设备完成渲染后对视频进行重新编码，然后发送给终端设备，由终端设备进行解码和显示。这种方式会带来较大的时延，且会给网络设备带来较大的资源浪费。
本申请提出一种方式，网络设备和终端设备之间进行渲染协商，针对不同XR通话的处理需求在终端设备和网络设备之间动态地分配渲染任务，实现终端设备和网络设备之间的有效协同和渲染任务的按需分配。
可以理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
还可以理解，本申请中，指示信息所指示的信息，称为待指示信息。在具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
上面对本申请中涉及到的术语做了简单说明，下文实施例中不再赘述。
下文将结合附图详细说明本申请实施例提供的方法。
图4是本申请实施例提供的一种XR对象渲染的方法400的示意图。方法400可以包括如下步骤。
410，终端设备接受渲染分工，渲染分工是指：终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，另一部分待渲染XR对象归终端设备渲染。
示例性地，410可为：终端设备接收来自第一网络设备的分工指示信息，分工指示信息指示：终端设备的XR通话中的一部分待渲染XR对象归第二网络设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染。
其中，第一网络设备表示确定渲染分工的网络侧设备，对应发明内容中的网络侧控制设备，第二网络设备表示对终端设备的XR通话中的部分待渲染XR对象执行渲染的网络侧设备，对应发明内容、410和后文420中的网络侧渲染设备。其中，渲染分工表示：终端设备和第二网络设备分别渲染终端设备的XR通话中的部分待渲染XR对象，也即终端设备的XR通话中的待渲染XR对象由终端设备和第二网络设备进行渲染。第一网络设备确定XR通话中的待渲染XR对象的渲染分工后，可向终端设备发送分工指示信息，以指示终端设备和第二网络设备分别渲染终端设备的XR通话中的部分待渲染XR对象，终端设备根据分工指示信息接受该渲染分工。
第一网络设备和第二网络设备可以是逻辑功能设备，可以部署在同一个物理设备上，也可以部署在不同的物理设备上，对此不予限制。例如，第一网络设备为XR控制面网元(如记为XR-C网元)，第二网络设备为XR媒体面网元(如XR-M网元)；再例如，第一网络设备为AS，第二网络设备为媒体资源功能网元(如MRF网元)；再例如，第一网络设备为互联网业务信令服务器(如OTT信令服务器)，第二网络设备为互联网业务媒体服务器(如OTT媒体服务器)。后面结合图5至图8详细说明各种情况下的可能的流程。
XR通话(XR call)，也可称为XR通信(XR communication)，或者XR通话业务，或者XR会话)。可以理解，在本申请实施例中，XR通话并不限于一对一通信(或者说端对端通信)，XR通话可以是一对多通信，也可以是多对一通信，也可以是多对多通信，不予限制。例如，XR通话可以是会议通话。终端设备的XR通话，是指终端设备参与的XR通话，可以是终端设备发起的XR通话，也可以是其他终端设备向该终端设备发起的XR通话，还可以是网络侧设备(如网络侧聊天机器人)向终端设备发起的XR通话。
为便于说明，本申请实施例将终端设备负责渲染的待渲染XR对象(即归终端设备渲染的待渲染XR对象)记为第一部分待渲染XR对象，第二网络设备负责渲染的待渲染XR对象(即归第二网络设备渲染的待渲染XR对象)记为第二部分待渲染XR对象。分工指示信息指示：终端设备的XR通话中的一部分待渲染XR对象归第二网络设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染，也可以替换为：分工指示信息指示：终端设备渲染终端设备的XR通话中的第一部分待渲染XR对象和/或第二网络设备渲染终端设备的XR通话中的第二部分待渲染XR对象；或者也可替换为：终端设备和第二网络设备分别渲染终端设备的XR通话中的部分待渲染XR对象。换句话说，分工指示信息指示终端设备的XR通话中的待渲染XR对象的渲染操作是由终端设备和第二网络设备分担的，二者分别负责其中的一部分待渲染XR对象的渲染操作。
其中，第一部分待渲染XR对象和第二部分待渲染XR对象属于XR通话中的待渲染XR对象。第一部分待渲染XR对象和第二部分待渲染XR对象可以不同，如第一部分待渲染XR对象为XR通话中待渲染的部分XR对象，第二部分待渲染XR对象为XR通话中待渲染的其余部分XR对象。举例来说，XR通话中的待渲染XR对象包括：虚拟会议室、虚拟人物、虚拟椅子、虚拟桌子，作为示例，第一部分待渲染XR对象可以是：虚拟会议室、虚拟人物，第二部分待渲染XR对象可以是：虚拟椅子、虚拟桌子。
420，终端设备渲染XR通话中归终端设备渲染的待渲染XR对象，并向网络侧渲染设备发送XR通话中归网络侧渲染设备渲染的待渲染XR对象。
示例性地，420可为，终端设备根据分工指示信息渲染XR通话中归终端设备渲染的待渲染XR对象，并向第二网络设备发送XR通话中归第二网络设备渲染的待渲染XR对象。
也即终端设备对第一部分待渲染XR对象进行渲染，并向第二网络设备发送第二部分待渲染XR对象。终端设备向第二网络设备发送第二部分待渲染XR对象，可以理解为，终端设备向第二网络设 备发送第二部分待渲染XR对象对应的相关的数据。举例来说，若第二部分待渲染XR对象为：“虚拟椅子”和“虚拟桌子”，则终端设备可以将“虚拟桌子”和“虚拟椅子”的原始数据(如包括在视频画面中的位置坐标)发送给第二网络设备。
一种可能的情形，分工指示信息包括终端设备负责渲染的第一部分待渲染XR对象的信息，终端设备向第二网络设备发送第二部分待渲染XR对象之前，方法400还包括：终端设备根据XR通话中的待渲染XR对象和第一部分待渲染XR对象，确定第二部分待渲染XR对象。这样，终端设备可以向第二网络设备发送第二部分待渲染XR对象，也即第二部分待渲染XR对象相关的数据。举例来说，若第二部分待渲染XR对象为：“虚拟椅子”和“虚拟桌子”，则终端设备可以将“虚拟桌子”和“虚拟椅子”在视频画面中的位置坐标发送给第二网络设备。
另一种可能的情形，分工指示信息包括第二网络设备负责渲染的第二部分待渲染XR对象的信息，终端设备对第一部分待渲染XR对象进行渲染之前，方法400还包括：终端设备根据XR通话中的待渲染XR对象和第二部分待渲染XR对象的信息，确定第一部分待渲染XR对象。这样，终端设备可以对第一部分待渲染XR对象进行渲染。
可以理解，若是按类型分工，则分工指示信息包括的第一部分待渲染XR对象的信息或者第二部分待渲染XR对象的信息可以是待渲染XR对象的类型(如人物、建筑、植物等)；若是按层分工，则分工指示信息包括的第一部分待渲染XR对象的信息或者第二部分待渲染XR对象的信息可以是待渲染XR对象的层次信息(如前景或背景)。
还可以理解，上述两种情形为示例性说明，本申请实施例不限于此。例如，分工指示信息还可包括终端设备负责渲染的第一部分待渲染XR对象，以及第二网络设备负责渲染的第二部分待渲染XR对象，这样终端设备可以直接基于分工指示信息确定终端设备负责渲染的第一部分待渲染XR对象，以及向第二网络设备发送的第二部分待渲染XR对象。
可选地，方法400还包括：第二网络设备对渲染后的第一部分待渲染XR对象和渲染后的第二部分待渲染XR对象合并，也即第二网络设备对渲染后的第一部分待渲染XR对象对应的媒体数据和渲染后的第二部分待渲染XR对象对应的媒体数据合并。一种可能的实现方式，终端设备向第二网络设备发送渲染后XR对象对应的媒体数据，第二网络设备收到该渲染后XR对象对应的媒体数据后，将第二网络设备负责渲染的渲染后XR对象对应的媒体数据以及终端设备负责渲染的渲染后XR对象对应的媒体数据进行合并。其中，渲染后XR对象对应的媒体数据，例如可以形成渲染后XR对象对应的视频流。举例来说，第二网络设备可以将第二网络设备渲染后的XR对象视频帧和终端设备渲染后的XR对象视频帧按照相同时间戳的视频帧在渲染器中进行图像合成，合成时可以考虑前景背景、遮挡、阴影等关系，从而输出一帧帧完整的视频帧图像。
进一步可选地，方法400还包括：第二网络设备向XR通话涉及的终端设备发送合并后的媒体数据。例如，终端设备与其他终端设备之间进行XR通话呼叫业务，第二网络设备向其他终端设备发送合并后的视频流。可选地，第二网络设备还可向终端设备发送合并后的视频流。
可以理解，关于对渲染后的第一部分待渲染XR对象对应的媒体数据和渲染后的第二部分待渲染XR对象对应的媒体数据执行合并处理的设备，不予限制。
在本申请实施例中，网络设备和终端设备之间可进行渲染协商，也即第一网络设备可确定XR通话中XR对象的渲染分工，即确定哪些待渲染XR对象由终端设备负责渲染，哪些待渲染XR对象由第二网络设备负责渲染，这样，针对XR通话，可以通过第一网络设备，在终端设备和第二网络设备之间动态地分配渲染任务，实现终端设备和第二网络设备之间的有效协同和渲染任务的按需分配。
可选地，终端设备向第一网络设备发送终端设备的处理能力信息(也即处理能力的信息)。终端设备的处理能力信息可用于确定分工指示信息，如第一网络设备可基于终端设备的处理能力信息确定分工指示信息。一种可能的实现方式，终端设备在注册过程中或XR通话建立过程中，向第一网络设备发送终端设备的处理能力信息。例如，终端设备向第三网络设备发送注册消息或会话呼叫消息以触发第三网络设备向第一网络设备发送终端设备的处理能力信息，注册消息或会话请求消息包含终端设备的处理能力信息。其中，会话呼叫消息可以是会话呼叫请求消息，也可以是会话呼叫响应消息。具体来说，终端设备向第三网络设备发送注册消息或会话呼叫消息，该注册消息或会话呼叫消息中包括终端设备的处理能力信息；第三网络设备收到终端设备的处理能力信息后，向第一网络设备发送该终 端设备的处理能力信息。其中，第三网络设备例如可以为IMS网络中的网元，或者也可以是OTT服务器等，不予限制。其中，第三网络设备对应发明内容中的网络侧接入设备。处理能力，或者也可称为XR媒体处理能力，或者XR对象处理能力，其命名不对本申请实施例的保护范围造成限定。终端设备的处理能力可用于确定是否对XR通话中的待渲染XR对象进行拆分渲染，拆分渲染表示XR通话中部分待渲染XR对象由终端设备渲染，部分待渲染XR对象由第二网络设备渲染。
可选地，终端设备的处理能力包括终端设备的渲染可用算力(available computing power for rendering)，或者，终端设备的处理能力包括终端设备的渲染可用算力和终端设备支持的渲染分工方式。
1)终端设备的渲染可用算力，表示终端设备渲染XR对象的可用算力或剩余算力。作为示例，终端设备的渲染可用算力是终端设备基于自身计算资源(如软、硬件资源)的配置情况确定的，或者，终端设备的渲染可用算力是终端设备根据终端设备的可用或剩余计算资源确定的。其中，终端设备的可用或剩余计算资源，可以是XR通话建立时或者XR通话建立过程中(包括初始的XR通话建立，还包括更新后的XR通话建立)，终端设备根据终端设备的可用或剩余计算资源确定的。例如，终端设备的渲染可用算力，可以根据图形处理器(graphics processing unit，GPU)限定的剩余可用功耗定义，或者也可以根据GPU剩余可用算力定义，不予限制，具体的后面结合方法500详细说明。
2)终端设备支持的渲染分工方式(也叫渲染拆分方式、渲染分裂方式)：是指XR对象的渲染任务的分工维度，例如按层分工、按类型分工等。
其中，按层分工是指按待渲染XR对象所处的层面(如前景、背景)进行分工，使不同实体(终端设备或网络设备)渲染处于不同层面的待渲染XR对象，例如，前景待渲染XR对象归终端设备渲染，背景待渲染XR对象归网络设备渲染。
其中，按类型分工是指按待渲染XR对象的类型(如人物类、建筑类、植物类等)进行分工，使不同实体(终端设备或网络设备)渲染不同类型的待渲染XR对象，例如，人物类待渲染XR对象归终端设备渲染，建筑类和植物类待渲染XR对象归网络设备渲染。
可以理解，本申请实施例不限定对待渲染XR对象的类型划分方式。还可以理解，本申请实施例不限定以上两种分工方式，还可以采用其他的分工方式，例如，还可以按运动状态进行分工，需要运动的待渲染XR对象归终端设备渲染，静止的待渲染XR对象归网络设备渲染。
还可以理解，上述关于终端设备的处理能力的表示方式是示例性的，而不是限定。终端设备的处理能力可以通过其他形式表示，例如，终端设备的处理能力包括终端设备的渲染可用算力和终端设备禁止的(或者不支持的，或者不允许的)渲染分工方式。
还可以理解，上述以终端设备向第一网络设备发送终端设备的处理能力的信息为例进行了示例性说明，对此不予限制。例如，终端设备也可以向第一网络设备发送用来确定终端设备的处理能力的信息。
可选地，终端设备向第一网络设备发送XR通话的处理需求信息。进一步可选地，终端设备在确定第二网络设备能够对XR对象进行渲染的情况下，向第一网络设备发送XR通话的处理需求信息。例如，终端设备默认第二网络设备能够对XR对象进行渲染；再例如，终端设备获取服务指示信息，该服务指示信息指示第二网络设备能够对XR对象进行渲染，或者，能够提供对带渲染XR对象进行渲染的服务。其中，服务指示信息例如可以包含第二网络设备的处理能力信息，终端设备根据第二网络设备的处理能力信息确定第二网络设备能够对XR对象进行渲染。其中，终端设备获取服务指示信息，可以包括：终端设备接收来自第一网络设备的服务指示信息。
一种可能的实现方式，终端设备在XR通话建立过程中，向第一网络设备发送XR通话的处理需求信息。例如，终端设备向第三网络设备发送会话呼叫消息，该会话呼叫消息中包括XR通话的处理需求信息；第三网络设备收到XR通话的处理需求信息后，向第一网络设备发送XR通话的处理需求信息。其中，第三网络设备例如可以为IMS网络中的网元，或者也可以是OTT服务器等，不予限制。XR通话的处理需求信息和终端设备的处理能力信息可以携带于同一信令中，也可以携带于不同信令中，不予限制。
其中，XR通话的处理需求，或者称XR媒体处理需求或者称为XR对象处理需求，其命名不对本申请实施例的保护范围造成限定。可用于确定是否进行拆分渲染，还可用于确定具体的渲染分工。作为示例，XR通话的处理需求信息包括以下至少一项：XR通话中待渲染的XR对象的信息、XR通话 的视频分辨率、XR通话的视频帧率。
1)XR通话中待渲染的XR对象的信息，也即XR通话业务中XR对象的原始数据。举例来说，XR通话中待渲染的XR对象包括：虚拟会议室、虚拟人物、虚拟椅子的原始数据。
2)XR通话的视频分辨率，指XR通话业务的视频画面的长和宽，例如：1920,1080。
3)XR通话的视频帧率，指XR通话业务中单位时间内(如1秒)内视频帧的数量，例如：30帧/秒。
可以理解，上述为示例性说明，对此不予限制。
下面介绍第一网络设备确定渲染分工的相关方案。
可选地，若终端设备的处理能力无法满足XR通话的处理需求，则第一网络设备确定对XR通话中的待渲染XR对象进行拆分渲染。可以理解，由于是拆分渲染，故终端设备的处理能力能够保证终端设备对XR通话中的部分待渲染XR对象进行渲染。进一步地可选地，若终端设备的处理能力满足XR通话的处理需求，则第一网络设备可以确定对XR通话中的待渲染XR对象进行拆分渲染，或者也可以确定由终端设备对XR通话中的待渲染XR对象进行渲染，不予限制。本申请实施例主要关心拆分渲染的情况。
举例来说，终端设备的处理能力信息包括终端设备的渲染可用算力，若终端设备的渲染可用算力无法满足XR通话的处理需求，则第一网络设备确定对XR通话中的待渲染XR对象进行拆分渲染。再举例来说，终端设备的处理能力信息包括终端设备的渲染可用算力和终端设备支持的渲染分工方式，若终端设备的渲染可用算力无法满足XR通话的处理需求，且终端设备支持拆分渲染，则第一网络设备确定对XR通话中的待渲染XR对象进行拆分渲染。
可选地，第一网络设备根据以下至少一项，确定XR通话中XR对象的渲染分工：终端设备的处理能力信息、第二网络设备的处理能力信息、XR通话的处理需求信息。第二网络设备的处理能力信息可以参考终端设备的处理能力信息，此处不再赘述(需要说明的是，第二网络设备的渲染可用算力可以是第二网络设备基于第二网络设备的计算资源的配置确定的，或者，第二网络设备的渲染可用算力是第二网络设备基于第二网络设备的剩余计算资源或可用计算资源确定的，或者，第二网络设备的渲染可用算力可以是第一网络设备基于第二网络设备的计算资源的配置确定的，或者，第二网络设备的渲染可用算力是第一网络设备基于第二网络设备的剩余计算资源或可用计算资源确定的，本申请对此不做限制)。关于XR通话的处理需求信息的获取方式，不予限制。例如，终端设备向第一网络设备发送XR通话的处理需求信息；再例如，第一网络设备生成XR通话的处理需求信息。
示例1，第一网络设备根据终端设备的处理能力信息确定XR通话中待渲染XR对象的渲染分工，也即确定分工指示信息。
例如，终端设备的处理能力信息包括终端设备的渲染可用算力，第一网络设备根据终端设备的渲染可用算力确定由终端设备负责渲染的第一部分待渲染XR对象，剩余的待渲染XR对象由第二网络设备负责渲染。
再例如，终端设备的处理能力信息包括终端设备支持的渲染分工方式，第一网络设备可以根据终端设备支持的渲染分工方式确定渲染分工。如若终端设备支持的渲染分工方式为按层分工，那么第一网络设备确定的渲染分工可以是：终端设备渲染前景，第二网络设备渲染背景。在该情况下，可假设终端设备的渲染可用算力足够渲染前景，第二网络设备的渲染可用算力足够渲染背景。
示例2，第一网络设备根据第二网络设备的处理能力信息确定XR通话中XR对象的渲染分工，也即确定分工指示信息。
例如，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，第一网络设备根据第二网络设备的渲染可用算力确定由第二网络设备负责渲染的第一部分待渲染XR对象，剩余的待渲染XR对象由终端设备负责渲染。
再例如，第二网络设备的处理能力信息包括第二网络设备支持的渲染分工方式，第一网络设备可以根据第二网络设备支持的渲染分工方式确定渲染分工。如若第二网络设备支持的渲染分工方式为按类型分工，那么第一网络设备确定的渲染分工可以是：终端设备渲染一部分待渲染XR对象(如虚拟桌子和椅子)，第二网络设备渲染其余部分待渲染XR对象(如虚拟会议室和人物)。在该情况下，可假设终端设备和第二网络设备的渲染可用算力足够渲染各自负责的待渲染XR对象。
示例3，第一网络设备根据XR通话的处理需求信息确定XR通话中XR对象的渲染分工，也即确定分工指示信息。
例如，XR通话的处理需求信息包括：XR通话中的待渲染XR对象，第一网络设备根据：XR通话中的待渲染XR对象确定渲染分工，如部分待渲染XR对象由终端设备负责渲染，其余部分待渲染XR对象由第二网络设备负责渲染。在该情况下，可假设终端设备和第二网络设备的渲染可用算力足够渲染各自负责的待渲染XR对象。
示例4，第一网络设备根据终端设备的处理能力信息和第二网络设备的处理能力信息确定XR通话中XR对象的渲染分工，也即确定分工指示信息。
例如，终端设备的处理能力信息包括终端设备的渲染可用算力，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，第一网络设备根据终端设备的渲染可用算力和第二网络设备的渲染可用算力，确定由终端设备负责渲染的第一部分待渲染XR对象，以及由第二网络设备负责渲染的第二部分待渲染XR对象。其中，终端设备的渲染可用算力能够满足终端设备渲染第一部分待渲染XR对象，第二网络设备的渲染可用算力能够满足第二网络设备渲染第二部分待渲染XR对象。
示例5，第一网络设备根据终端设备的处理能力信息和XR通话的处理需求信息确定XR通话中XR对象的渲染分工，也即确定分工指示信息。
例如，终端设备的处理能力信息包括终端设备的渲染可用算力，第一网络设备根据XR通话的处理需求信息估计出渲染XR通话中待渲染XR对象所需的算力，并且根据渲染XR通话中待渲染XR对象所需的算力和终端设备的渲染可用算力，确定由终端设备负责渲染的第一部分待渲染XR对象，剩余的待渲染XR对象(即第二部分待渲染XR对象)由第二网络设备负责渲染。
示例6，第一网络设备根据第二网络设备的处理能力信息和XR通话的处理需求信息确定XR通话中XR对象的渲染分工，也即确定分工指示信息。
例如，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，第一网络设备根据XR通话的处理需求信息估计出渲染XR通话中待渲染XR对象所需的算力，并且根据渲染XR通话中待渲染XR对象所需的算力和第二网络设备的渲染可用算力，确定由第二网络设备负责渲染的第二部分待渲染XR对象，剩余的待渲染XR对象(即第一部分待渲染XR对象)由终端设备负责渲染。
示例7，第一网络设备根据终端设备的处理能力信息、第二网络设备的处理能力信息、XR通话的处理需求信息确定XR通话中XR对象的渲染分工，也即确定分工指示信息。
例如，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，终端设备的处理能力信息包括终端设备的渲染可用算力，第一网络设备根据XR通话的处理需求信息估计出渲染XR通话中待渲染XR对象所需的算力，并且根据渲染XR通话中待渲染XR对象所需的算力、第二网络设备的渲染可用算力、以及终端设备的渲染可用算力，确定由终端设备负责渲染的第一部分待渲染XR对象和由第二网络设备负责渲染的第二部分待渲染XR对象。
上述示例为示例性说明，本申请实施例并不限于此。
可以理解，在上述示例中，若终端设备和第二网络设备支持的渲染分工方式不同，作为示例，则可以由终端设备来渲染XR通话中的待渲染XR对象。
可选地，若第一网络设备和第二网络设备为不同设备，第一网络设备向第二网络设备发送请求消息，请求消息用于请求以下至少一项：第二网络设备的地址信息、第二网络设备的渲染资源信息；第一网络设备接收来自第二网络设备的请求消息的响应。例如，若请求消息用于请求第二网络设备的地址信息，则请求消息的响应中携带第二网络设备的地址信息。进一步，第一网络设备可向终端设备发送地址信息。再例如，若请求消息用于请求第二网络设备渲染第二部分待渲染XR对象的渲染资源信息，则请求消息的响应用于通知资源申请结果，即第二网络设备是否将进行渲染。一种可能的实现方式，请求消息用于请求第二网络设备渲染第二部分待渲染XR对象的渲染资源信息，若请求消息的响应包括第二网络设备的地址信息，则意味着第二网络设备同意进行渲染。另一种可能的实现方式，请求消息用于请求第二网络设备渲染第二部分待渲染XR对象的渲染资源信息，请求消息的响应可以包括直接指示第二网络设备是否将进行渲染的信息。
作为示例，请求消息中包括第二网络设备渲染第二部分待渲染XR对象所需的算力。第二网络设备渲染第二部分待渲染XR对象所需的算力，用于第二网络设备分配渲染第二部分待渲染XR对象所用 的资源。
其中，第二网络设备的地址信息用于使与XR通话相关的终端设备通过第三网络设备连接到第二网络设备。例如，假设终端设备与其他终端设备之间进行XR通话，第二网络设备的地址信息包括第一资源端点的本端连接地址和第二资源端点的本端连接地址，第一资源端点的本端连接地址和第二资源端点的本端连接地址分别用于本端终端设备(如图5至图8中的UE#1)和对端终端设备(如图5至图8中的UE#2)通过第三网络设备连接第二网络设备，例如，本端终端设备通过第三网络设备第二网络设备，对端终端设备通过第三网络设备连接到第二网络设备。示例性地，第一网络设备向第二网络设备发送请求消息，该请求消息用于请求第二网络设备的地址信息，即表示该请求消息用于请求创建或分配端点资源，相应地，第二网络设备可创建或分配相应的资源端点(也称为媒体端点)，并且还可向第一网络设备返回相应的资源端点的信息。其中，资源端点即为上述的第一资源端点和第二资源端点，资源端点的信息即包括第一资源端点的本端连接地址和第二资源端点的本端连接地址。
其中，渲染资源信息为第二网络设备用来渲染归所述第二网络设备渲染的待渲染XR对象的资源的信息。示例性地，第一网络设备向第二网络设备发送请求消息，该请求消息用于请求第二网络设备的渲染资源信息，即表示该请求消息用于请求第二网络设备预留或分配算力资源，相应地，第二网络设备可预留或分配相应的算力资源。
为便于理解，下面介绍适用于本申请实施例的可能的流程。可以理解，下文主要以在会话呼叫中进行渲染协商为例进行示例性说明，因此下文中的XR通话也可以替换为会话(或者称为XR会话)。
图5是本申请实施例提供的一种XR对象渲染的方法500的示意性流程图。该方法500可以用于实现上述方法400的方案。在该方法500中，假设第一网络设备和第二网络设备相同，即为图5中的网络设备；或者图5中的网络设备为第一网络设备和第二网络设备组成的系统，该方法500可以包括如下步骤。
501，UE#1向网络设备发送UE#1的处理能力。
UE#1向网络设备上报自己的处理能力，即UE#1自己的处理能力信息，以便在后续会话建立过程中，网络设备可以根据UE#1的处理能力，在UE#1和网络设备之间进行渲染协商。
可选地，处理能力包括参数A和参数B。
其中，参数A，表示支持的渲染分工方式。作为示例，UE#1支持的渲染分工方式包括：按层分工、按类型分工。按层分工，表示可以分层进行渲染，例如区分前景和背景进行渲染。
举例来说，用“0”表示按层分工，用“1”表示按类型分工，若参数A的取值为0，则表示支持的渲染分工方式为按层分工；若参数A的取值为1，则表示支持的渲染分工方式为按类型分工；若参数A的取值为0和1，则表示支持的渲染分工方式包括按层分工和按类型分工。
其中，参数B，表示渲染可用算力，也即终端设备渲染XR对象的可用算力。该参数B的取值可以是终端设备根据自身计算资源的配置(如CPU型号、内存条数量等)确定的静态取值，也可以动态地在会话建立时根据当前终端设备的硬件资源空闲程度(也即终端设备的剩余计算资源或可用计算资源)等计算得到，不予限制。下面介绍能够体现渲染可用算力的两种可能的方式。
方式1：以GPU限定的剩余可用功耗定义，取值可以为瓦。举例来说，AR眼镜整体功耗约为0.5瓦-2瓦，VR一体机整体功耗约为3瓦-7瓦。UE#1可以根据自身配置决定参数B的取值。
方式2：以GPU剩余可用算力定义，取值可以为每秒所执行的浮点运算次数(floating point operations per second，TFLOPS)。
可以理解，UE#1和网络设备之间进行渲染协商时，采用相同的算力表达方式，例如均采用上述方式1，或均采用上述方式2，以保证一致性。
上述参数为示例性说明，本申请实施例不限于此。例如，处理能力包括参数B和用于表示禁止的渲染分工方式的参数。
502，网络设备保存UE#1的处理能力。
可选地，方法500还包括步骤503和步骤504。
503，网络设备向UE#1发送网络设备的处理能力。
网络设备的处理能力，可以参考步骤501中UE#1的处理能力，此处不再赘述。
504，UE#1确定网络设备能够渲染XR对象。
UE#1基于网络设备的处理能力可获知网络设备是否能够渲染XR对象，也即是否支持XR对象渲染。步骤503和步骤504为可选步骤，也即网络设备可以不用向UE#1提供网络设备的处理能力，UE#1可默认网络设备能够渲染XR对象。
下面结合四种场景介绍渲染协商过程。
场景1：UE#1发起初始会话呼叫。
5111，UE#1向网络设备发送会话呼叫请求。
可以理解的是，步骤501中UE#1上报的UE#1的处理能力，也可以在步骤5111中发送。也即，方法500可以不包括501，且在步骤5111中，会话呼叫请求包括UE#1的处理能力。
可选地，会话呼叫请求中包括XR通话的处理需求。
一种可能的情形，UE#1默认网络设备支持XR对象渲染，因此，UE#1在会话呼叫请求中携带XR通话的处理需求，以请求和网络设备进行渲染协商。
另一种可能的情形，UE#1根据在步骤503中收到的网络设备的处理能力，确定网络设备是否支持XR对象渲染。若UE#1确定网络设备支持XR对象渲染，则UE#1在会话呼叫请求中携带XR通话的处理需求，以请求和网络设备进行渲染协商。若UE#1确定网络设备不支持媒体渲染，则UE#1在会话呼叫请求中不携带XR通话的处理需求。对于网络设备不支持XR对象渲染的情况，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍网络设备支持XR对象渲染的情况。
可选地，XR通话的处理需求包括参数C、参数D、参数E中的一项或多项。
其中，参数C，表示待渲染的XR对象，也即待渲染XR对象。举例来说，用“0”表示虚拟会议室，用“1”表示虚拟人物，用“2”表示虚拟椅子，用“3”表示虚拟桌子。若参数C的取值为0,1,2，则表示待渲染的XR对象包括：虚拟会议室、虚拟人物、虚拟椅子。
其中，参数D，表示视频分辨率，可定义视频画面的长和宽。举例来说，参数D的取值为：1920,1080，其表示视频分辨率为：1920,1080。
其中，参数E，表示视频帧率。举例来说，参数E的取值为30，其表示视频帧率为30帧/秒。
5112，网络设备根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤5111中的会话呼叫请求包括XR通话的处理需求。
另一种可能的实现方式，网络设备生成XR通话的处理需求。作为示例，网络设备根据XR应用业务逻辑和会话参数生成XR通话的处理需求。在该方式下，步骤5111中的会话呼叫请求可以不用携带XR通话的处理需求。
关于确定分工指示信息的方式：
一种可能的实现方式，网络设备根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。举例来说，网络设备可以根据XR通话的处理需求和UE#1的处理能力，确定本次XR通话待渲染的全部XR对象的渲染算力要求是否超出UE#1的渲染可用算力，也即UE#1的渲染可用算力能否满足本次XR通话待渲染XR对象所需的算力要求。若本次XR通话待渲染XR对象所需的渲染算力超出UE#1的渲染可用算力，则网络设备可以确定对本次XR通话待渲染XR对象进行拆分渲染，也即对于待渲染XR对象，网络设备渲染部分XR对象，UE#1渲染部分XR对象。作为示例，网络设备渲染的部分XR对象，可以是本次XR通话待渲染XR对象所需的渲染算力超出UE#1的渲染可用算力所对应的XR对象。可以理解，由于是拆分渲染，故UE#1的渲染可用算力大于或等于预设值，即UE#1能够对部分XR对象进行渲染。
另一种可能的实现方式，网络设备根据：XR通话的处理需求、UE#1的处理能力、以及网络设备的处理能力确定分工指示信息。举例来说，网络设备可以根据XR通话的处理需求计算得出XR通话渲染算力要求，并判断是否超出终端设备的处理能力(如渲染可用算力)，并结合网络设备自己的处理能力，确定分工指示信息。若本次XR通话待渲染XR对象所需的渲染算力超出UE#1的渲染可用算力，则网络设备可以确定对本次XR通话待渲染XR对象进行拆分渲染，也即对于待渲染XR对象，网络设备渲染部分XR对象，UE#1渲染部分XR对象。网络设备可以根据自身的渲染可用算力，以及UE#1的渲染可用算力，进行渲染任务的分工。作为示例，网络设备渲染的部分XR对象，可以是本次XR通话待渲染XR对象所需的渲染算力超出UE#1的渲染可用算力所对应的XR对象。可以理解，由于是 拆分渲染，故UE#1的渲染可用算力大于或等于预设值，即UE#1能够对部分XR对象进行渲染。
可以理解，上述两种实现方式为示例性说明，本申请实施例不限于此。例如，还可以参考方法400中的其它实现方式。
下面介绍网络设备判断本次XR通话所需的渲染算力是否超出UE#1的渲染可用算力的实现方式。
一种可能的实现方式，网络设备可以根据待渲染XR对象的视频分辨率或物体体积、视频帧率等，匹配基线数据估算出渲染待渲染XR对象所需的功耗或等效TFLOPS，进而判断本次XR通话待渲染XR对象所需的渲染算力是否超出UE#1的渲染可用算力。举例来说，可以通过GPU测试工具做基准测试以确定渲染待渲染XR对象所需的功耗或等效TFLOPS。首先，可以在测试过程中，采用统一的输入，例如包括但不限于：渲染着色器、光线、阴影等，并准备一系列不同视频分辨率和不同体积大小的多种3D模型，通过测试不同3D模型在GPU测试工具中的渲染，获取所需要的功耗或等效TFLOPS，作为基准数据。然后，根据实际XR通话的XR对象，参考基准数据的相同3D模型对应的视频分辨率和视频帧率计算对应的功耗或等效TFLOPS，进而得出渲染待渲染XR对象所需的功耗或等效TFLOPS。
若本次XR通话待渲染XR对象所需的渲染算力要求超出UE#1的渲染可用算力，则网络设备可以确定对本次XR通话待渲染XR对象进行拆分渲染，也即对于待渲染XR对象，网络设备渲染部分XR对象，UE#1渲染部分XR对象。下面结合表1给出一具体示例。表1示出了几种3D模型在不同视频分辨率或体积、不同视频帧率的渲染所消耗的功耗和等效TFLOPS。
表1
以表1为例，举例来说，假设UE#1的处理能力中参数B的取值为4瓦，XR通话的处理需求中参数C表示待渲染的XR对象包括虚拟会议室、虚拟椅子、以及虚拟桌子，参数D的视频分辨率为1920*1080，参数E的视频帧率为30。网络设备可以根据表1获得XR对象渲染的功耗要求：虚拟会议室的功耗为4瓦，虚拟椅子的功耗为1瓦，虚拟桌子的功耗为6瓦。因此，网络设备计算出待渲染XR对象的渲染功耗要求为11瓦，超出了UE#1的处理能力(即4瓦)。因此，对于待渲染XR对象，网络设备渲染部分XR对象，UE#1渲染部分XR对象。作为示例，网络设备渲染的部分XR对象，可以是本次XR通话待渲染XR对象所需的渲染算力超出UE#1的渲染可用算力所对应的XR对象，例如网络设备可以确定UE#1负责渲染的待渲染XR对象是：虚拟会议室，网络设备负责渲染的待渲染XR对象是：虚拟椅子和虚拟桌子。
5113，网络设备向UE#1发送分工指示信息。
也即网络设备向UE#1发送分工指示信息。举例来说，网络设备向UE#1发送会话呼叫响应，在该会话呼叫响应中携带本次XR通话的渲染协商结果，即分工指示信息。
作为示例，分工指示信息包括参数F和参数G。
其中，参数F，表示XR通话的渲染分工方式，也即XR通话中待渲染XR对象拆分渲染的方式。该参数F的取值定义同步骤501中参数A的取值。举例来说，假设步骤501中参数A的取值为0，表示支持的渲染分工方式包括按层分工，参数A的取值为1，表示支持的渲染分工方式包括按类型分工。那么在步骤5113中，若参数F的取值为0，则表示网络设备确定的XR通话的渲染分工方式为按层分工；若参数F的取值为1，则表示网络设备确定的XR通话的渲染分工方式为按类型分工。
其中，参数G，表示网络设备负责渲染的待渲染XR对象。UE#1基于该参数G以及待渲染的所有XR对象，可获知自己负责渲染的待渲染XR对象。该参数G的取值定义同步骤5111中参数C的取值。举例来说，假设步骤5111中参数C的取值为0,1,2,3，且含义如下：“0”表示虚拟会议室，“1”表示虚拟人物，“2”表示虚拟椅子，“3”表示虚拟桌子。以上述示例为例，若网络设备负责渲染的待渲染XR对象是：虚拟椅子和虚拟桌子，则参数G的取值可以为2,3。此外，若待渲染的所有XR对象包括：虚拟会议室、虚拟椅子、虚拟桌子，那么UE#1基于该待渲染的所有XR对象以及网络设备负责渲染的待渲染XR对象，获知UE#1负责渲染“虚拟会议室”。
可以理解，上述为示例性说明，本申请实施例不限于此。例如，分工指示信息包括参数F和H，其中，参数H表示UE#1负责渲染的待渲染XR对象，也即UE#1基于待渲染的所有XR对象以及UE#1负责渲染的待渲染XR对象，可获知网络设备负责渲染的待渲染XR对象。再例如，分工指示信息包括参数G和参数H。再例如，分工指示信息包括参数F、参数G和参数H。
场景2：UE#1接收初始会话呼叫。
5121，网络设备向UE#1发送会话呼叫请求。
可选地，会话呼叫请求用于请求UE#1的XR通话的处理需求。
5122，UE#1向网络设备发送会话呼叫响应。
若步骤5121中会话呼叫请求用于请求UE#1的XR通话的处理需求，则步骤5122中会话呼叫响应中携带UE#1的XR通话的处理需求。
可以理解的是，步骤501中UE#1上报的UE#1的处理能力，也可以在步骤5122中发送。也即，方法500可以不包括501，且在步骤5122中，会话呼叫响应包括UE#1的处理能力。
5123，网络设备根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤5122中的会话呼叫响应包括XR通话的处理需求。
另一种可能的实现方式，网络设备生成XR通话的处理需求。作为示例，网络设备根据XR应用业务逻辑和会话参数生成XR通话的处理需求。在该方式下，步骤5122中的会话呼叫响应可以不用携带XR通话的处理需求。
网络设备确定分工指示信息的实现方式，参考步骤5112中的相关描述，此处不再赘述。
5124，网络设备向UE#1发送分工指示信息。
举例来说，网络设备向UE#1发送会话呼叫响应确认消息，在该会话呼叫响应确认消息中携带本次XR通话的渲染协商结果，即分工指示信息。
关于分工指示信息，参考步骤5113中的相关描述，此处不再赘述。
场景3：UE#1发起会话更新呼叫。
5131，UE#1向网络设备发送会话更新呼叫请求。
5132，网络设备根据更新后的XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤5132中网络设备可以根据更新后的XR通话的处理需求和UE#1的处理能力，确定新的分工指示信息。
5133，网络设备向UE#1发送分工指示信息。
步骤5131-步骤5133与步骤5111-步骤5113类似，此处不再赘述。
场景4：UE#1接收会话更新呼叫。
5141，网络设备向UE#1发送会话更新呼叫请求。
5142，UE#1向网络设备发送会话更新呼叫响应。
5143，网络设备根据更新后的XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤5143中网络设备可以根据更新后的XR通话的处理需求和UE#1的处理能力，确定新的分工指示信息。
5144，网络设备向UE#1发送分工指示信息。
步骤5141-步骤5144与步骤5121-步骤5124类似，此处不再赘述。
上面结合四种场景进行了示例性说明，不管在上述哪种场景下，在确定分工指示信息后，可以包括如下步骤。
521，UE#1根据分工指示信息，确定网络设备负责渲染的待渲染XR对象。
一种可能的实现方式，若分工指示信息中包括参数G，也即分工指示信息中包括网络设备负责渲染的待渲染XR对象，则UE#1可直接基于该参数G确定网络设备负责渲染的待渲染XR对象。
另一种可能的实现方式，若分工指示信息中包括参数H，也即分工指示信息中包括UE#1负责渲染的待渲染XR对象，则UE#1可基于待渲染的所有XR对象以及UE#1负责渲染的待渲染XR对象，可获知网络设备负责渲染的待渲染XR对象。
522，UE#1向网络设备发送网络设备负责渲染的待渲染XR对象。
UE#1可以将需要网络设备渲染的XR对象的相关数据发送给网络设备。举例来说，若网络设备负责渲染“虚拟椅子”和“虚拟桌子”，则UE#1可以将“虚拟桌子”和“虚拟椅子”在视频画面中的位置坐标发送给网络设备。
523，网络设备渲染网络设备负责渲染的待渲染XR对象。
若网络设备负责渲染“虚拟椅子”和“虚拟桌子”，且网络设备收到来自UE#1的“虚拟桌子”和“虚拟椅子”在视频画面中的位置坐标，则网络设备可根据“虚拟桌子”和“虚拟椅子”在视频画面中的位置坐标对“虚拟桌子”和“虚拟椅子”进行渲染。
524，UE#1渲染UE#1负责渲染的待渲染XR对象。
525，UE#1向网络设备发送渲染后的XR对象对应的媒体数据。
UE#1完成渲染后，将渲染完成后的XR对象(例如，上述示例中的渲染后的“虚拟会议室”)媒体数据发给网络设备。
526，网络设备对UE#1渲染后的XR对象对应的媒体数据以及网络设备渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
网络设备将收到的UE#1渲染后的XR对象(例如，上述示例中的渲染后的“虚拟会议室”)对应的媒体数据后，可以将UE#1渲染后的XR对象对应的媒体数据和网络设备渲染后的XR对象(例如，上述示例中的渲染后的“虚拟桌子”和“虚拟椅子”)对应的媒体数据进行合并。
举例来说，网络设备可以将网络侧渲染后的XR对象视频流和UE#1渲染后的XR对象视频流按照相同时间戳的视频帧在渲染器中进行图像合成，合成时可以考虑前景背景、遮挡、阴影等关系，从而输出一帧帧完整的视频帧图像，形成视频图像序列，可以以视频流的形式发送给终端设备。下文主要以视频流的形式发送为例进行示例性说明。
527，网络设备向UE#2发送合并后的媒体数据。
如网络设备向UE#2发送合并后的视频流。
UE#2表示呼叫业务所涉及的UE，是UE#1的对端UE。举例来说，UE#1与UE#2之间进行XR通话呼叫业务，网络设备向UE#2发送合并后的视频流，这样，UE#2可以基于接收的视频图像序列显示出渲染后的XR对象，使UE#2的用户看到3D效果的XR对象。可以理解，网络设备可以直接向UE#2发送合并后的视频流，也可以通过其他设备(如UE#2所属的网络设备)发送合并后的视频流，不予限制。可以理解，UE#1可以与多个UE进行XR通话(即会议)，则网络设备分别向多个UE发送合并后的视频流。
可选地，网络设备也可以向UE#1发送合并后的媒体数据，这样UE#1也可显示渲染后的XR对象，使UE#1的用户看到3D效果的XR对象。
基于上述技术方案，终端设备向网络设备上报自身的处理能力，网络设备也可以将自身的处理能力通知给终端设备，也即终端设备和网络设备之间可交换各自的处理能力。终端设备确定网络设备支持XR对象渲染的情况下，可在会话呼叫请求中携带XR通话的处理需求，请求与网络设备之间进行渲染协商。网络设备可根据XR通话的处理需求计算得出XR对象渲染算力要求，并判断是否超出终端设备的渲染可用算力。若超出终端设备的渲染可用算力，则还可以结合网络设备自己的处理能力，决策本次会话的渲染分工，并将渲染协商结果通知给终端设备。终端设备基于渲染协商结果，可确定哪些XR对象在终端设备完成渲染，哪些XR对象在网络设备完成渲染。对于需要网络设备渲染的XR对象，终端设备可向网络设备发送网络设备待渲染的数据。最后，网络设备可对自己渲染后的XR对象对应 的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的终端设备。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由终端设备或网络设备发起会话更新请求，根据更新后的XR通话的处理需求重新进行渲染协商。
可以理解，图5所示方案中，如何分工是网络设备确定的(如步骤5112、5123等)，对此不予限制。一种可能的方案，如何分工也可以是终端设备确定的。
例如，UE#1可以根据XR通话的处理需求和UE#1的处理能力信息确定分工指示信息(具体可参考步骤5112中的描述)，进而再执行步骤521至步骤527。可选地，在执行步骤521之前，UE#1还可以向网络设备发送分工指示信息。
再例如，UE#1向网络设备发送XR对象渲染请求，网络设备返回XR对象渲染响应，该响应中包含指示信息，该指示信息指示网络设备将为UE#1渲染XR对象；UE#1确认网络设备将协助渲染XR对象后，再确定出归网络设备负责渲染的待渲染XR对象，进而再执行步骤522。该例子中，可选地，网络设备返回的XR对象渲染响应还可以包含网络设备的处理能力信息(与步骤5112中UE#1的处理能力信息类似)，如此，UE#1可以根据网络设备的处理能力信息等信息确定如何分工(具体可参考步骤5112中的描述)，即确定哪部分待渲染XR对象归网络设备渲染，再执行步骤522。可以理解，网络设备可以决策将当前所有剩余的处理能力都留给UE#1的XR对象的渲染，也可以决策将当前所有剩余的处理能力的一部分留给UE#1的XR对象的渲染，也就是说，网络设备通过XR对象渲染响应返回的处理能力信息可以表征网络设备当前所有剩余的处理能力，也可以表征当前所有剩余的处理能力的一部分。示例性地，网络设备将当前所有剩余的处理能力的5％留给UE#1的XR对象的渲染，即返回的处理能力信息表征这％5的处理能力，使UE#1根据这5％的处理能力给网络设备分配待渲染XR对象，如此可以避免UE#1将过多的XR对象的渲染任务分给网络设备，或者避免网络设备的资源被一个UE独占。
还可以理解，图5所示方案中，以网络设备对UE#1渲染后的XR对象对应的媒体数据以及网络设备渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，网络设备向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如，也可以是其他设备进行合并处理，不再赘述。
图6是本申请实施例提供的一种XR对象渲染的方法600的示意性流程图。该方法600可以用于实现上述方法400的方案。该方法600可用于基于DC的渲染协商的场景，渲染协商例如可在DC建立完成后进行。在该方法600中，第一网络设备为XR-C网元，第二网络设备为XR-M网元，IMS包含一个或多个网元，例如可以参考图1所示的架构，下面统一用“IMS”表示。作为示例，图6所示的方法600可用于图1架构。该方法600可以包括如下步骤。
601，UE#1向IMS发送UE#1的处理能力。
一种可能的实现方式，UE#1在向IMS注册的过程中，向IMS发送UE#1的处理能力。例如，UE#1向IMS发送SIP注册(REGISTER)消息，该SIP REGISTER消息中携带UE#1的处理能力。例如，可以在SIP信令(如SIP REGISTER消息)的头域中携带UE#1的处理能力。
作为示例，UE#1的处理能力的形式如下：
XR-Capability:split_rendering_method＝0,1；rendering_capability＝0/1/2
其中，“split_rendering_method”表示参数A，即UE#1支持的渲染分工方式。“rendering_capability”表示参数B，即UE#1的渲染可用算力。作为示例，“split_rendering_method”取值为0和1，表示支持的渲染分工方式包括按层分工和按类型分工。关于参数A和参数B，参考前面的相关描述，此处不再赘述。
602，IMS向XR-C网元发送UE#1的处理能力。
举例来说，IMS对UE#1注册鉴权成功后，将UE#1的处理能力转发给XR-C网元。作为示例，IMS向XR-C网元发送HTTP消息，该HTTP消息中携带UE#1的处理能力。
603，XR-C网元保存UE#1的处理能力。
可选地，方法500还包括步骤604-步骤606。
604，XR-C网元向IMS发送XR-M网元的处理能力。
一种可能的实现方式，XR-C网元向IMS发送HTTP响应消息(如200消息)，该HTTP响应消息中包括XR-M网元的处理能力。
605，IMS向UE#1发送XR-M网元的处理能力。
606，UE#1确定XR-M网元能够渲染XR对象。
UE#1基于XR-M网元的处理能力可获知XR-M网元是否能够渲染XR对象，也即是否支持XR对象渲染。步骤604-步骤606为可选步骤，也即XR-C网元可以不用向UE#1提供XR-M网元的处理能力，UE#1可默认XR-M网元能够渲染XR对象。
607，音视频媒体通道建立和DC建立。
UE#1在发起XR通话时或接收XR通话时，可先与IMS之间建立音视频媒体通道，并且建立UE#1与IMS之间的DC。UE#1与IMS之间的DC可用来传输UE#1与IMS之间的信令或数据，如渲染分工交互的相关信息和/或XR对象的相关数据等。可以理解，下文提及的UE#1与IMS之间交互的信令可通过该DC传输。
下面结合两种场景介绍渲染协商过程。
场景1：UE#1发起渲染协商。
6111，UE#1向IMS发送渲染协商请求信息。
可以理解的是，步骤601中UE#1上报的UE#1的处理能力，也可以在步骤6111中发送。也即，方法600可以不包括601，且在步骤6111中，渲染协商请求信息包括UE#1的处理能力。
可选地，渲染协商请求信息包括XR通话的处理需求。
一种可能的情形，UE#1默认XR-M网元支持XR对象渲染，因此，UE#1在渲染协商请求信息中携带XR通话的处理需求。
另一种可能的情形，UE#1根据在步骤605中收到的XR-M网元的处理能力，确定XR-M网元是否支持媒体渲染。若UE#1确定XR-M网元支持XR对象渲染，则UE#1在渲染协商请求信息中携带XR通话的处理需求。若UE#1确定XR-M网元不支持XR对象渲染，则UE#1在渲染协商请求信息中不携带XR通话的处理需求。对于XR-M网元不支持XR对象渲染的情况，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍XR-M网元支持XR对象渲染的情况。
可选地，XR通话的处理需求包括参数C、参数D、参数E。具体的，可以参考5111中的相关描述，此处不再赘述。
作为示例，XR通话的处理需求的形式如下：
XR-Session-Attribute:rendering_content＝0,1,2,3；video_resolution＝1920,1080；video_frame_rate＝30
其中，“rendering_content”表示参数C，即待渲染的XR对象。“video_resolution”表示参数D，即视频分辨率。“video_frame_rate”表示参数E，即视频帧率。
6112，IMS向XR-C网元发送HTTP请求消息。
可选地，若步骤6111中的渲染协商请求信息包括XR通话的处理需求，则步骤6112中的HTTP请求消息中也包括XR通话的处理需求。
6113，XR-C网元根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤6112中的HTTP消息包括XR通话的处理需求。
另一种可能的实现方式，XR-C网元生成XR通话的处理需求。作为示例，XR-C网元根据XR应用业务逻辑和会话参数生成XR通话的处理需求。
可选地，XR-C网元确定分工指示信息时，还可以综合考虑：XR-M网元的处理能力、UE#1的处理能力、以及XR通话的处理需求。进一步可选地，XR-M网元向XR-C网元发送XR-M网元的处理能力。关于确定分工指示信息的实现方式，可以参考步骤5112中的相关描述，此处不再赘述。
6114，XR-C网元向IMS发送分工指示信息。
一种可能的实现方式，XR-C网元向IMS发送HTTP响应消息，该HTTP响应消息中携带本次XR通话的渲染协商结果，即分工指示信息。
可选地，分工指示信息包括以下至少一项：参数F、参数G、参数H。具体的，可以参考步骤5113 中的相关描述，此处不再赘述。
作为示例，分工指示信息的形式如下：
XR-Session-Negotiation：split_rendering_method＝0/1；network_rendering_content＝0,1,2
其中，“split_rendering_method”表示参数F，即XR通话的渲染分工方式，该参数F的取值定义同步骤601中参数A的取值。其中，“network_rendering_content”表示参数G，即XR-M网元负责渲染的待渲染XR对象，该参数G的取值定义同步骤6111中参数C的取值。具体的，可以参考步骤5113中的相关描述，此处不再赘述。
6115，IMS向UE#1发送分工指示信息。
IMS收到XR-C网元发送的分工指示信息后，向UE#1转发该分工指示信息。
一种可能的实现方式，IMS向UE#1发送渲染协商响应，该渲染协商响应中携带分工指示信息。
6116，XR-C网元向XR-M网元申请资源。
XR-C网元根据分工指示信息，确定需要XR-M网元侧渲染XR对象时，可向XR-M网元申请资源，即请求XR-M网元渲染XR-M网元负责渲染的待渲染XR对象。一种可能的实现方式，XR-C网元向XR-M网元发送HTTP请求消息，该HTTP请求消息用于向XR-M网元申请与渲染XR对象有关的资源。
示例性地，XR-C网元向XR-M申请资源包括：XR-C网元向XR-M网元请求创建或分配端点资源，相应地，XR-M网元创建或分配相应的资源端点(也称为媒体端点)，并将相应的资源端点的信息(对应发明内容中的网络侧渲染设备的地址信息)返回给XR-C网元。例如，XR-M网元接收到上述HTTP请求后，创建或分配两个资源端点，分别为第一资源端点和第二资源端点，第一资源端点的属性包括第一资源端点的本端连接地址、第二资源端点的属性包括第二资源端点的本端连接地址，其中，第一资源端点的本端连接地址、第二资源端点的本端连接地址分别用于使UE#1通过IMS(UE#1接入的IMS)与XR-M网元建立通信连接和使UE#2通过IMS(UE#2接入的IMS)与XR-M网元建立通信连接。
示例性地，XR-C网元向XR-M申请资源还可以包括：XR-C网元向XR-M网元请求预留或分配算力资源，相应地，XR-M网元预留或分配相应的算力资源，例如，内存或者CPU时隙或GPU资源等；可选地，XR-C网元向XR-M网元发送待渲染XR对象的信息或XR算力要求，该XR算力要求表示归XR-M网元渲染的待渲染XR对象所需要消耗的算力，如此，XR-M网元可以根据待渲染XR对象的信息或XR算力要求，预留或者分配相应的算力资源。
可选地，XR-M网元向XR-C网元返回资源申请结果，包括以下至少一项：结果指示信息、资源端点的信息。其中，结果指示信息可用于通知XR-C网元，XR-M网元是否将对XR-M网元负责渲染的待渲染XR对象进行渲染。进一步，可选地，若资源申请结果用于通知XR-C网元：XR-M网元将对XR-M网元负责渲染的待渲染XR对象进行渲染，则XR-C网元可向UE#1发送传输指示信息，以指示UE#1向XR-M网元发送XR-M网元负责渲染的待渲染XR对象。示例性地，资源端点的信息包括第一资源端点的本端连接地址和第二资源端点的本端连接地址。
一种可能的情形，若XR-M网元向XR-C网元返回的资源端点的信息包含第一资源端点的本端连接地址，则XR-C网元可向IMS(例如IMS中的代理呼叫会话控制功能(proxy-call session control funtion，P-CSCF)网元)发送第一资源端点的本端连接地址，以便于IMS(例如P-CSCF控制的多媒体子系统接入网关(IMS access gateway，IMS-AGW))通过第一资源端点的本端连接地址与XR-M网元通信，例如UE#1通过IMS-AGW向XR-M网元发送由XR-M网元负责渲染的待渲染XR对象。示例地，UE#1与IMS-AGW已有连接，例如第一连接(连接还可以理解为通道)，IMS可以通过XR-C网元发送的第一资源端点的本端连接地址建立IMS-AGW与XR-M网元的第二连接，并且建立第一连接和第二连接的对应关系，该对应关系可以使得IMS-AGW接收到UE#1发送的由XR-M网元负责渲染的待渲染XR对象后，可以确定第二连接，并通过第二连接将由XR-M网元负责渲染的待渲染XR对象转发给XR-M网元。示例地，资源端点的信息和分工指示信息可以携带于一个信令或消息中，也可以携带于不同信令或消息中，不予限制。此外，若XR-M网元向XR-C网元返回的资源端点的信息包含第二资源端点的本端连接地址，XR-C网元还可向IMS(例如UE#2接入的IMS中的P-CSCF)发送第二资源端点的本端连接地址，以便于UE#2通过该IMS与XR-M网元通信，如UE#2通过该IMS从XR-M网元获取合并后的媒体数据。示例地，XR-C网元可向接入的IMS中的P-CSCF发送第二资源端点的本端 连接地址，以便于UE#2通过P-CSCF控制的IMS-AGW连接到XR-M网元，这样UE#2可以通过IMS-AGW从XR-M网元获取合并后的媒体数据。
可以理解，步骤6114和步骤6116的执行顺序不予限制。
例如，先执行步骤6114，再执行步骤6116。也即XR-C网元确定分工指示信息后，直接通过IMS向UE#1发送该分工指示信息。在该情况下，本端连接地址和分工指示信息可以携带于不同信令中，也即XR-C网元先通过IMS向UE#1发送分工指示信息，然后在收到来自XR-M网元的本端连接地址后，向IMS发送本端连接地址。
再例如，先执行步骤6116，再执行步骤6114。也即XR-C网元确定分工指示信息后，可以先向XR-M网元申请资源，然后再通过IMS向UE#1发送该分工指示信息。在该情况下，XR-C网元收到来自XR-M网元的本端连接地址后，向IMS发送分工指示信息和本端连接地址。作为示例，本端连接地址和分工指示信息可以携带于一个信令中。
场景2：UE#1发起重新渲染协商。
6121，UE#1向IMS发送重新渲染协商请求信息。
在某些情况下，例如，在XR通话过程中XR通话的处理需求更新的情况下，终端设备可能会发起重新渲染协商。在这些情况下，UE#1可以向IMS发送重新渲染协商请求信息，以便重新对XR通话进行渲染协商。
6122，IMS向XR-C网元发送HTTP消息。
6123，XR-C网元根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤6123中XR-C网元可以根据更新后的XR通话的处理需求和UE#1的处理能力信息，确定新的分工指示信息。
6124，XR-C网元向IMS发送分工指示信息。
6125，IMS向UE#1发送分工指示信息。
步骤6121-步骤6125与步骤6111-步骤6115类似，此处不再赘述。
6126，XR-C网元向XR-M网元申请更新渲染资源。
XR-C网元根据分工指示信息，确定需要XR-M网元侧更新渲染时，可向XR-M网元申请更新渲染资源，即请求XR-M网元渲染分工更新之后XR-M网元负责渲染的待渲染XR对象。一种可能的实现方式，XR-C网元向XR-M网元发送HTTP消息，该HTTP消息用于申请修改资源。具体的可参考步骤6116中的描述，此处不再赘述。可以理解的是，本步骤中XR-M网元可以重新创建端点资源，也可以重用步骤6116中创建或分配的端点资源；XR-M网元可以重用步骤6116中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤6116预留或分配的算力资源。
上面结合两种场景进行了示例性说明，不管在上述哪种场景下，在确定分工指示信息后，可以包括如下步骤。
621，UE#1根据分工指示信息，确定XR-M网元负责渲染的待渲染XR对象。
步骤621与步骤521类似，此处不再赘述。
622，UE#1向XR-M网元发送XR-M网元负责渲染的待渲染XR对象。
UE#1可以将需要XR-M网元渲染的XR对象的相关数据发送给XR-M网元。举例来说，若XR-M网元负责渲染“虚拟人物”，则UE#1可以将需要驱动虚拟人的动作姿态数据发送给XR-M网元。
一种可能的实现方式，UE#1通过Application DC将XR-M网元负责渲染的待渲染XR对象发送给IMS(如其中的DCS-M或IMS-AGW)，IMS将XR-M网元负责渲染的待渲染XR对象转发给XR-M网元。
623，XR-M网元渲染XR-M网元负责渲染的待渲染XR对象。
若XR-M网元负责渲染“虚拟人物”，且XR-M网元收到来自UE#1的需要驱动虚拟人的动作姿态数据，则XR-M网元可根据该数据对“虚拟人物”进行渲染。
624，UE#1渲染UE#1负责渲染的待渲染XR对象。
625，UE#1向XR-M网元发送渲染后的XR对象对应的媒体数据。
UE#1完成渲染后，将渲染完成后的XR对象对应的媒体数据发给XR-M网元。
626，XR-M网元对UE#1渲染后的XR对象对应的媒体数据以及XR-M网元渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
627，XR-M网元向UE#2发送合并后的媒体数据。
步骤627与步骤527类似，此处不再赘述。
可以理解，步骤625中XR-M网元和UE#1之间的传输和步骤627中XR-M网元和UE#2之间的传输的实现方式与步骤622类似，不再赘述。
基于上述技术方案，终端设备可在注册到IMS的过程中，向XR-C网元上报自身的处理能力，XR-C网元也可以将XR-M网元的处理能力通知给终端设备。终端设备确定XR-M网元支持XR对象渲染的情况下，可在DC建立请求中携带XR通话的处理需求，请求进行渲染协商。XR-C网元可根据XR通话的处理需求计算得出XR对象渲染算力要求，并判断是否超出终端设备的渲染可用算力。若超出终端设备的渲染可用算力，则XR-C网元还可以结合XR-M网元的处理能力，决策本次会话的渲染分工，并将渲染协商结果通知给终端设备，当需要XR-M网元参与媒体渲染时，XR-C网元向XR-M网元申请媒体渲染资源。终端设备基于渲染协商结果，可确定哪些XR对象在终端设备完成渲染，哪些XR对象在XR-M网元完成渲染。对于需要XR-M网元渲染的XR对象，终端设备可向XR-M网元发送XR-M网元待渲染的数据。最后，XR-M网元可对自己渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的终端设备。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由终端设备会重新发起渲染协商，根据更新后的XR通话的处理需求重新进行渲染协商。
可以理解，图6所示方案中，如何分工是XR-C网元确定的(如步骤6113、6123等)，对此不予限制。一种可能的方案，如何分工也可以是终端设备确定的。
例如，UE#1可以根据XR通话的处理需求和UE#1的处理能力信息确定分工指示信息(具体可参考步骤6113中的描述)，进而再执行步骤621至步骤627。可选地，在执行步骤621之前，UE#1还可以向XR-C网元发送分工指示信息。
再例如，UE#1向XR-C网元发送XR对象渲染请求，XR-C网元返回XR对象渲染响应，该响应中包含指示信息，该指示信息指示XR-C网元将为UE#1渲染XR对象；UE#1确认XR-C网元将协助渲染XR对象后，再确定出归XR-C网元负责渲染的待渲染XR对象，进而再执行步骤622。该例子中，可选地，XR-C网元返回的XR对象渲染响应还可以包含XR-C网元的处理能力信息(与步骤6113中UE#1的处理能力信息类似)，如此，UE#1可以根据XR-C网元的处理能力信息等信息确定如何分工(具体可参考步骤6113中的描述)，即确定哪部分待渲染XR对象归XR-C网元渲染，再执行步骤622。可以理解，XR-M网元可以将当前所有剩余的处理能力都留给UE#1的XR对象的渲染，也可以将XR-M网元当前所有剩余的处理能力的一部分留给UE#1的XR对象的渲染，也就是说，XR-C网元通过XR对象渲染响应返回的处理能力信息可以表征XR-M网元当前所有剩余的处理能力，也可以表征XR-M网元当前所有剩余的处理能力的一部分。示例性地，XR-M网元将当前所有剩余的处理能力的5％留给UE#1的XR对象的渲染，即XR-C网元返回的处理能力信息表征这％5的处理能力，使UE#1根据这5％的处理能力给XR-M网元分配待渲染XR对象，如此可以避免UE#1将过多的XR对象的渲染任务分给XR-M网元，或者避免XR-M网元的资源被一个UE独占。
还可以理解，图6所示方案中，以XR-M网元对UE#1渲染后的XR对象对应的媒体数据以及XR-M网元渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，XR-M网元向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如也可以是其他设备进行合并处理，不再赘述。
图7是本申请实施例提供的一种XR对象渲染的方法700的示意性流程图。该方法700可以用于实现上述方法400的方案。该方法700可用于基于IMS SIP信令进行渲染协商的场景，渲染协商例如可在呼叫建立过程中完成。在该方法700中，第一网络设备为AS，第二网络设备为MRF网元，MRF网元例如可以包括MRFC和MRFP，IMS包含一个或多个网元，例如可以参考图2所示的架构，下面统一用“IMS core”表示。作为示例，图7所示的方法700可用于图2架构。该方法700可以包括如下步骤。
701，UE#1向IMS核心网(IMS core)发送UE#1的处理能力。
步骤701与步骤601类似，此处不再赘述。
702，IMS core向AS发送UE#1的处理能力。
举例来说，IMS core对UE#1注册鉴权成功后，将UE#1的处理能力转发给AS。作为示例，IMS core向AS发送SIP REGISTER消息，该SIP REGISTER消息中携带UE#1的处理能力。
703，AS保存UE#1的处理能力。
可选地，方法700还包括步骤704-步骤706。
704，AS向IMS core发送MRF网元的处理能力。
705，IMS core向UE#1发送MRF网元的处理能力。
706，UE#1确定MRF网元能够渲染XR对象。
UE#1基于MRF网元的处理能力可获知MRF网元是否能够渲染XR对象，也即是否支持XR对象渲染。步骤704-步骤706为可选步骤，也即AS可以不用向UE#1提供MRF网元的处理能力，UE#1可默认MRF网元能够渲染XR对象。
下面结合四种场景介绍渲染协商过程。
场景1：UE#1发起XR通话呼叫建立。
7111，UE#1向IMS core发送邀请(INVITE)消息。
可以理解的是，步骤701中UE#1上报的UE#1的处理能力，也可以在步骤7111中发送。也即，方法700可以不包括701，且在步骤7111中，INVITE消息包括UE#1的处理能力。
可选地，INVITE消息包括XR通话的处理需求。
一种可能的情形，UE#1默认MRF网元支持XR对象渲染，因此，UE#1在INVITE消息中携带XR通话的处理需求。
另一种可能的情形，UE#1根据在步骤705中收到的MRF网元的处理能力，确定MRF网元是否支持媒体渲染。若UE#1确定MRF网元支持XR对象渲染，则UE#1在INVITE消息中携带XR通话的处理需求。若UE#1确定MRF网元不支持XR对象渲染，则UE#1在INVITE消息中不携带XR通话的处理需求。对于MRF网元不支持XR对象渲染的情况，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍MRF网元支持XR对象渲染的情况。
可选地，XR通话的处理需求包括参数C、参数D、参数E。具体的，可以参考5111中的相关描述，此处不再赘述。
作为示例，XR通话的处理需求的形式如下：
XR-Session-Attribute:rendering_content＝0,1,2,3；video_resolution＝1920,1080；video_frame_rate＝30
其中，“rendering_content”表示参数C，即待渲染的XR对象。“video_resolution”表示参数D，即视频分辨率。“video_frame_rate”表示参数E，即视频帧率。
7112，IMS core向AS发送INVITE消息。
可选地，若步骤7111中的INVITE消息包括XR通话的处理需求，则步骤7112中的INVITE消息中也包括XR通话的处理需求。
7113，AS根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤7112中的INVITE消息包括XR通话的处理需求。
另一种可能的实现方式，AS生成XR通话的处理需求。作为示例，AS根据XR应用业务逻辑和会话参数生成XR通话的处理需求。
可选地，AS确定分工指示信息时，可以综合考虑：MRF网元的处理能力、UE#1的处理能力、以及XR通话的处理需求。进一步可选地，MRF网元向AS发送MRF网元的处理能力。关于确定分工指示信息的实现方式，可以参考步骤5112中的相关描述，此处不再赘述。
7114，AS向IMS core发送分工指示信息。
一种可能的实现方式，AS向IMS core发送18X For INVITE消息或200 For INVITE消息，该18X For INVITE消息或200 For INVITE消息中携带本次XR通话的渲染协商结果，即分工指示信息。
另一种可能的实现方式，AS向IMS core发送临时确认响应(provisional response ACKnowledgement， PRACK)For INVITE消息或者确认响应(ACKnowledgement，ACK)For INVITE消息，该PRACK For INVITE消息或ACK For INVITE消息中携带本次XR通话的渲染协商结果，即分工指示信息。
可选地，分工指示信息包括以下至少一项：参数F、参数G、参数H。具体的，可以参考步骤5113中的相关描述，此处不再赘述。
作为示例，分工指示信息的形式如下：
XR-Session-Negotiation：split_rendering_method＝0/1；network_rendering_content＝0,1,2
具体的可以参考步骤6115中的相关描述，此处不再赘述。
7115，IMS core向UE#1发送分工指示信息。
IMS core收到AS发送的分工指示信息后，向UE#1转发该分工指示信息。
一种可能的实现方式，IMS core向UE#1发送18X For INVITE消息或200 For INVITE消息，该18X For INVITE消息或200 For INVITE消息中携带分工指示信息。
7116，AS向MRF网元申请资源。
AS根据分工指示信息，确定需要MRF网元侧渲染XR对象时，可向MRF网元申请资源，即请求MRF网元渲染MRF网元负责渲染的待渲染XR对象。一种可能的实现方式，AS向MRF网元发送INVITE消息，该INVITE消息用于向MRF网元申请与渲染XR对象有关的资源。
示例性地，AS向MRF申请资源包括：AS向MRF网元请求创建或分配端点资源，相应地，MRF网元创建或分配相应的资源端点(也称为媒体端点)，并将相应的资源端点的信息(对应发明内容中的网络侧渲染设备的地址信息)返回给AS。例如，MRF网元接收到上述INVITE消息后，创建或分配两个资源端点，分别为第一资源端点和第二资源端点，第一资源端点的属性包括第一资源端点的本端连接地址、第二资源端点的属性包括第二资源端点的本端连接地址，其中，第一资源端点的本端连接地址、第二资源端点的本端连接地址分别用于使UE#1通过IMS core(UE#1接入的IMS core)与MRF网元建立通信连接和使UE#2通过IMS core(UE#2接入的IMS core)与MRF网元建立通信连接。
示例性地，AS向MRF申请资源还可以包括：AS向MRF网元请求预留或分配算力资源，相应地，MRF网元预留或分配相应的算力资源，例如，内存或者CPU时隙或GPU资源等；可选地，AS向MRF网元发送待渲染XR对象的信息或XR算力要求，该XR算力要求表示归MRF网元渲染的待渲染XR对象所需要消耗的算力，如此，MRF网元可以根据待渲染XR对象的信息或XR算力要求，预留或者分配相应的算力资源。
可选地，MRF网元向AS返回资源申请结果，包括以下至少一项：结果指示信息、资源端点的信息。其中，结果指示信息可用于通知AS，MRF网元是否将对MRF网元负责渲染的待渲染XR对象进行渲染。进一步，可选地，若资源申请结果用于通知AS：MRF网元将对MRF网元负责渲染的待渲染XR对象进行渲染，则AS可向UE#1发送传输指示信息，以指示UE#1向MRF网元发送MRF网元负责渲染的待渲染XR对象。示例性地，资源端点的信息包括第一资源端点的本端连接地址和第二资源端点的本端连接地址。
一种可能的情形，若MRF网元向AS返回的资源端点的信息包含第一资源端点的本端连接地址，则AS可向IMS core(例如IMS core中的P-CSCF网元)发送第一资源端点的本端连接地址，以便于IMS core(例如P-CSCF控制的IMS-AGW)通过第一资源端点的本端连接地址与MRF网元通信，例如UE#1通过IMS-AGW向MRF网元发送由MRF网元负责渲染的待渲染XR对象。示例地，UE#1与IMS-AGW已有连接，例如第三连接(连接还可以理解为通道)，IMS core可以通过AS网元发送的第一资源端点的本端连接地址建立IMS-AGW与MRF网元的第四连接，并且建立第三连接和第四连接的对应关系，该对应关系可以使得IMS-AGW接收到UE#1发送的由MRF网元负责渲染的待渲染XR对象后，可以确定第四连接，并通过第四连接将由MRF网元负责渲染的待渲染XR对象转发给MRF网元。示例地，资源端点的信息和分工指示信息可以携带于一个信令或消息中，也可以携带于不同信令或消息中，不予限制。此外，若MRF网元向AS返回的资源端点的信息包含第二资源端点的本端连接地址，AS还可向IMS core(例如UE#2接入的IMS core中的P-CSCF)发送第二资源端点的本端连接地址，以便于UE#2通过该IMS core与MRF网元通信，如UE#2通过该IMS core从MRF网元获取合并后的媒体数据。示例地，AS可向IMS core中的P-CSCF发送第二资源端点的本端连接地址，以便于UE#2通过P-CSCF控制的IMS-AGW连接到MRF网元，这样UE#2可以通过IMS-AGW从MRF网元 获取合并后的媒体数据。
可以理解，步骤7114和步骤7116的执行顺序不予限制。
例如，先执行步骤7114，再执行步骤7116。也即AS确定分工指示信息后，直接通过IMS core向UE#1发送该分工指示信息。在该情况下，本端连接地址和分工指示信息可以携带于不同信令中，也即AS先通过IMS core向UE#1发送分工指示信息，然后在收到来自MRF网元的本端连接地址后，再向IMS core发送本端连接地址。
再例如，先执行步骤7116，再执行步骤7114。也即AS确定分工指示信息后，可以先向MRF网元申请资源，然后再通过IMS core向UE#1发送该分工指示信息。在该情况下，AS收到来自MRF网元的本端连接地址后，向IMS core发送分工指示信息和本端连接地址。作为示例，本端连接地址和分工指示信息可以携带于一个信令中。
场景2：UE#1接收XR通话呼叫建立。
7121，AS向IMS core发送INVITE消息。
可选地，INVITE消息用于请求UE#1的XR通话的处理需求。
7122，IMS core向UE#1发送INVITE消息。
若步骤7121中INVITE消息用于请求UE#1的XR通话的处理需求，则步骤7122中INVITE消息用于请求UE#1的XR通话的处理需求。
7123，UE#1向IMS core发送200 For INVITE消息。
若步骤7122中INVITE消息用于请求UE#1的XR通话的处理需求，则步骤7123中200 For INVITE消息中携带UE#1的XR通话的处理需求。
可以理解的是，步骤701中UE#1上报的UE#1的处理能力，也可以在步骤7123中发送。也即，方法700可以不包括701，且在步骤7123中，200 For INVITE消息包括UE#1的处理能力。
步骤7123中的200 For INVITE消息，也可以替换为18X For INVITE消息，关于消息的具体类型不予限制。
7124，IMS core向AS发送200 For INVITE消息。
步骤7124中的200 For INVITE消息，也可以替换为18X For INVITE消息，关于消息的具体类型不予限制。
7125，AS根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤7124中的200 For INVITE消息包括XR通话的处理需求。
另一种可能的实现方式，AS生成XR通话的处理需求。作为示例，另一种可能的实现方式，根据XR应用业务逻辑和会话参数生成XR通话的处理需求。
可选地，AS确定分工指示信息时，可以综合考虑：MRF网元的处理能力、UE#1的处理能力、以及XR通话的处理需求。关于确定分工指示信息的实现方式，可以参考步骤5112中的相关描述，此处不再赘述。
7126，AS向IMS core发送分工指示信息。
7127，IMS core向UE#1发送分工指示信息。
7128，AS向MRF网元申请资源。
步骤7126-步骤7128与步骤7114-步骤7116类似，此处不再赘述。
场景3：UE#1发起XR通话更新。
7131，UE#1向IMS core发送再邀请(REINVITE)消息。
7132，IMS core向AS发送REINVITE消息。
7133，AS根据更新后的XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤7133中AS根据更新后的XR通话的处理需求和UE#1的处理能力，确定新的分工指示信息。
7134，AS向IMS core发送分工指示信息。
7135，IMS core向UE#1发送分工指示信息。
步骤7131-步骤7135与步骤7111-步骤7115类似，此处不再赘述。
7136，AS向MRF网元申请更新渲染资源。
AS根据分工指示信息，确定需要MRF网元侧更新渲染时，可向MRF网元申请更新渲染资源，即请求MRF网元渲染分工更新之后MRF网元负责渲染的待渲染XR对象。一种可能的实现方式，AS向MRF网元发送REINVITE消息，该REINVITE消息用于申请修改资源。具体的可以参考步骤7116中的描述，此处不再赘述。可以理解的是，本步骤中MRF网元可以重新创建端点资源，也可以重用步骤7116中创建或分配的端点资源；MRF网元可以重用步骤7116中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤7116预留或分配的算力资源。
场景4：UE#1接收XR通话更新。
7141，AS向IMS core发送REINVITE消息。
7142，IMS core向UE#1发送REINVITE消息。
7143，UE#1向IMS core发送200 For REINVITE消息。
7144，IMS core向AS发送200 For REINVITE消息。
7145，AS根据更新后的XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤7145中AS根据更新后的XR通话的处理需求和UE#1的处理能力，确定新的分工指示信息。
7146，AS向IMS core发送分工指示信息。
一种可能的实现方式，AS向IMS core发送ACK For REINVITE消息，该ACK For REINVITE消息包括分工指示信息。
7147，IMS core向UE#1发送分工指示信息。
一种可能的实现方式，IMS core向UE#1发送ACK For REINVITE消息，该ACK For REINVITE消息包括分工指示信息。
步骤7141-步骤7147与步骤7121-步骤7127类似，此处不再赘述。
7148，AS向MRF网元申请更新渲染资源。
AS根据分工指示信息，确定需要MRF网元侧更新渲染时，可向MRF网元申请更新渲染资源，即请求MRF网元渲染分工更新之后MRF网元负责渲染的待渲染XR对象。一种可能的实现方式，AS向MRF网元发送REINVITE消息，该REINVITE消息用于申请修改资源。具体的可以参考步骤7116中的描述，此处不再赘述。可以理解的是，本步骤中MRF网元可以重新创建端点资源，也可以重用步骤7128中创建或分配的端点资源；MRF网元可以重用步骤7128中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤7128预留或分配的算力资源。
上面结合四种场景进行了示例性说明，不管在上述哪种场景下，在确定分工指示信息后，可以包括如下步骤。
721，UE#1根据分工指示信息，确定MRF网元负责渲染的待渲染XR对象。
步骤721与步骤521类似，此处不再赘述。
722，UE#1向MRF网元发送MRF网元负责渲染的待渲染XR对象。
UE#1可以将需要MRF网元渲染的XR对象的相关数据发送给MRF网元。举例来说，若MRF网元负责渲染“虚拟人物”，则UE#1可以将需要驱动虚拟人的动作姿态数据发送给MRF网元。
示例地，UE#1基于XR通话的待渲染XR对象的渲染分工，通过第三连接向IMS-AGW发送MRF网元负责渲染的待渲染XR对象，IMS-AGW基于第三连接与第四连接的对应关系，通过第四连接将由MRF网元负责渲染的待渲染XR对象转发给MRF网元。
723，MRF网元渲染MRF网元负责渲染的待渲染XR对象。
若MRF网元负责渲染“虚拟人物”，且MRF网元收到来自UE#1的需要驱动虚拟人的动作姿态数据，则MRF网元可根据该数据对“虚拟人物”进行渲染。
724，UE#1渲染UE#1负责渲染的待渲染XR对象。
725，UE#1向MRF网元发送渲染后的XR对象对应的媒体数据。
UE#1完成渲染后，将渲染完成后的XR对象对应的媒体数据发给MRF网元。
726，MRF网元对UE#1渲染后的XR对象对应的媒体数据以及MRF网元渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
727，MRF网元向UE#2发送合并后的媒体数据。
步骤727与步骤527类似，此处不再赘述。
可以理解，步骤725中MRF网元和UE#1之间的传输和步骤727中MRF网元和UE#2之间的传输的实现方式与步骤722类似，不再赘述。
基于上述技术方案，终端设备可在注册到IMS的过程中，向AS上报自身的处理能力，AS也可以将MRF网元的处理能力通知给终端设备。终端设备确定MRF网元支持XR对象渲染的情况下，可在呼叫请求中携带XR通话的处理需求，请求进行渲染协商。AS可根据XR通话的处理需求计算得出XR对象渲染算力要求，并判断是否超出终端设备的渲染可用算力。若超出终端设备的渲染可用算力，则AS还可以结合MRF网元的处理能力，决策本次会话的渲染分工，并将渲染协商结果通知给终端设备，当需要MRF网元参与媒体渲染时，AS向MRF网元申请媒体渲染资源。终端设备基于渲染协商结果，可确定哪些XR对象在终端设备完成渲染，哪些XR对象在MRF网元完成渲染。对于需要MRF网元渲染的XR对象，终端设备可向MRF网元发送MRF网元待渲染的数据。最后，MRF网元可对自己渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的终端设备。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由终端设备或AS发起会话更新请求，根据更新后的XR通话的处理需求重新进行渲染协商。
可以理解，图7所示方案中，如何分工是AS确定的(如步骤7113、7125等)，对此不予限制。一种可能的方案，如何分工也可以是终端设备确定的。
例如，UE#1可以根据XR通话的处理需求和UE#1的处理能力信息确定分工指示信息(具体可参考步骤7113中的描述)，进而再执行步骤721至步骤727。可选地，在执行步骤721之前，UE#1还可以向AS发送分工指示信息。
再例如，UE#1向AS发送XR对象渲染请求，AS返回XR对象渲染响应，该响应中包含指示信息，该指示信息指示AS将为UE#1渲染XR对象；UE#1确认AS将协助渲染XR对象后，再确定出归AS负责渲染的待渲染XR对象，进而再执行步骤722。该例子中，可选地，AS返回的XR对象渲染响应还可以包含AS的处理能力信息(与步骤7113中UE#1的处理能力信息类似)，如此，UE#1可以根据AS的处理能力信息等信息确定如何分工(具体可参考步骤7113中的描述)，即确定哪部分待渲染XR对象归AS渲染，再执行步骤722。可以理解，MRF网元可以将当前所有剩余的处理能力都留给UE#1的XR对象的渲染，也可以将MRF网元当前所有剩余的处理能力的一部分留给UE#1的XR对象的渲染，也就是说，AS通过XR对象渲染响应返回的处理能力信息可以表征MRF网元当前所有剩余的处理能力，也可以表征MRF网元当前所有剩余的处理能力的一部分。示例性地，MRF网元将当前所有剩余的处理能力的5％留给UE#1的XR对象的渲染，即AS返回的处理能力信息表征这％5的处理能力，使UE#1根据这5％的处理能力给MRF网元分配待渲染XR对象，如此可以避免UE#1将过多的XR对象的渲染任务分给MRF网元，或者避免MRF网元的资源被一个UE独占。
还可以理解，图7所示方案中，以MRF网元对UE#1渲染后的XR对象对应的媒体数据以及MRF网元渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，MRF网元向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如也可以是其他设备进行合并处理，不再赘述。
图8是本申请实施例提供的一种XR对象渲染的方法800的示意性流程图。该方法800可以用于实现上述方法400的方案。该方法800可用于基于HTTP/HTTPS消息完成渲染协商的场景，渲染协商例如可在呼叫建立过程中完成。在该方法800中，假设第一网络设备和第二网络设备为OTT服务器。作为示例，图8所示的方法800可用于图3架构。该方法800可以包括如下步骤。
801，UE#1向OTT服务器发送UE#1的处理能力。
一种可能的实现方式，UE#1在向OTT服务器注册的过程中，向OTT服务器发送处理能力。例如，UE#1向OTT服务器发送HTTP请求消息，该HTTP请求消息中携带UE#1的处理能力。
作为一示例，UE#1的处理能力信息的格式可以为json格式，如下：
Content-Type:application/json
{
“XR-Capability”:{
“split_rendering_method”:“0,1”,//表示支持的分工方式为按层分工和按类型分工
“rendering_capability”:“0/1/2”}//表示UE#1的渲染可用算力
}
作为另一示例，UE#1的处理能力信息的格式可以为XML格式，如下：
Content-Type:application/xml
<XR-Capability>
<split_rendering_method Value＝”0,1”><！--表示支持的分工方式为按层分工和按类型分工-->
<rendering_capability Value＝”0/1/2”><！--表示UE#1的渲染可用算力-->
</XR-Capability>
在上述任一示例中，“split_rendering_method”表示参数A，即UE#1支持的渲染分工方式。“rendering_capability”表示参数B，即UE#1的渲染可用算力。作为示例，“split_rendering_method”取值为0和1，表示支持的渲染分工方式包括按层分工和按类型分工。关于参数A和参数B，参考前面的相关描述，此处不再赘述。
802，OTT服务器保存UE#1的处理能力。
举例来说，OTT服务器对UE#1注册鉴权成功后，可保存(或者称记录)UE#1的处理能力。
可选地，方法800还包括步骤803-步骤804。
803，OTT服务器向UE#1发送OTT服务器的处理能力。
一种可能的实现方式，OTT服务器向UE#1发送HTTP响应消息，该HTTP响应消息包括OTT服务器的处理能力。
804，UE#1确定OTT服务器能够渲染XR对象。
UE#1基于OTT服务器的处理能力可获知OTT服务器是否能够渲染XR对象，也即是否支持XR对象渲染。步骤803-步骤804为可选步骤，也即OTT服务器可以不用向UE#1提供OTT服务器的处理能力，UE#1可默认OTT服务器能够渲染XR对象。
下面结合四种场景介绍渲染协商过程。
场景1：UE#1发起渲染协商。
8111，UE#1向OTT服务器发送HTTP请求消息。
可以理解的是，步骤801中UE#1上报的UE#1的处理能力，也可以在步骤8111中发送。也即，方法800可以不包括801，且在步骤8111中，HTTP请求消息包括UE#1的处理能力。
可选地，HTTP请求消息包括XR通话的处理需求。
一种可能的情形，UE#1默认OTT服务器支持XR对象渲染，因此，UE#1在HTTP请求消息中携带XR通话的处理需求。
另一种可能的情形，UE#1根据在步骤803中收到的OTT服务器的处理能力，确定OTT服务器是否支持媒体渲染。若UE#1确定OTT服务器支持XR对象渲染，则UE#1在HTTP请求消息中携带XR通话的处理需求。若UE#1确定OTT服务器不支持XR对象渲染，则UE#1在HTTP请求消息中不携带XR通话的处理需求。对于OTT服务器不支持XR对象渲染的情况，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍OTT服务器支持XR对象渲染的情况。
可选地，XR通话的处理需求包括参数C、参数D、参数E。具体的，可以参考5111中的相关描述，此处不再赘述。
作为一示例，XR通话的处理需求的格式可以为json格式，如下：
Content-Type:application/json
{
“XR-Session-Attribute”:{
“rendering_content”:“0,1,2,3”,//表示XR通话中的待渲染XR对象
“video_resolution”:“1920,1080”,//表示XR通话的视频分辨率
“video_frame_rate”:“30”}//表示XR通话的视频帧率
}
作为另一示例，XR通话的处理需求的格式可以为XML格式，如下：
Content-Type:application/xml
<XR-Session-Attribute>
<rendering_content Value＝“0,1,2,3”/><！--表示XR通话中的待渲染XR对象-->
<video_resolution Value＝“1920,1080”/><！--表示XR通话的视频分辨率-->
<video_frame_rate Value＝“30”/><！--表示XR通话的视频帧率-->
</XR-Session-Attribute>
在上述任一示例中，“rendering_content”表示参数C，即待渲染的XR对象。“video_resolution”表示参数D，即视频分辨率。“video_frame_rate”表示参数E，即视频帧率。
8112，OTT服务器根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤8111中的HTTP请求消息包括XR通话的处理需求。
另一种可能的实现方式，OTT服务器生成XR通话的处理需求。作为示例，OTT服务器根据XR应用业务逻辑和会话参数生成XR通话的处理需求。
可选地，OTT服务器确定分工指示信息时，可以综合考虑：OTT服务器的处理能力、UE#1的处理能力、以及XR通话的处理需求。关于确定分工指示信息的实现方式，可以参考步骤5112中的相关描述，此处不再赘述。
8113，OTT服务器向UE#1发送分工指示信息。
一种可能的实现方式，OTT服务器向UE#1发送HTTP响应消息，该HTTP响应消息中携带本次XR通话的渲染协商结果，即分工指示信息。
可选地，分工指示信息包括以下至少一项：参数F、参数G、参数H。具体的，可以参考步骤5113中的相关描述，此处不再赘述。
作为一示例，分工指示信息的格式可以为json格式，如下：
Content-Type:application/json
{
“XR-Session-Negotiation”:{
“split_rendering_method”:“0/1”,//表示渲染分工方式
“network_rendering_content”:“0,1,2”//表示OTT服务器负责渲染的待渲染XR对象
}
}
作为另一示例，分工指示信息的格式可以为XML格式，如下：
Content-Type:application/xml
<XR-Session-Negotiation>
<split_rendering_method Value＝”0/1”/><！--表示渲染分工方式-->
<network_rendering_content Value＝”0,1,2”/><！--表示OTT服务器负责渲染的待渲染XR对象-->
</XR-Session-Attribute>
在上述任一示例中，“split_rendering_method”表示参数F，即渲染分工方式，该参数F的取值定义同步骤801中参数A的取值。“network_rendering_content”表示参数G，即OTT服务器负责渲染的待渲染XR对象，该参数G的取值定义同步骤8111中参数C的取值。
场景2：UE#1接收渲染协商。
8121，OTT服务器向UE#1发送HTTP请求消息。
可选地，HTTP请求消息用于请求UE#1的XR通话的处理需求。
8122，UE#1向OTT服务器发送HTTP响应消息。
若步骤8121中HTTP请求消息用于请求UE#1的XR通话的处理需求，则步骤8122中HTTP响应消息中携带UE#1的XR通话的处理需求。
可以理解的是，步骤801中UE#1上报的UE#1的处理能力，也可以在步骤8122中发送。也即，方法800可以不包括801，且在步骤8122中，HTTP响应消息包括UE#1的处理能力。
8123，OTT服务器根据XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
关于XR通话的处理需求的获取方式：
一种可能的实现方式，步骤8122中的HTTP响应消息包括XR通话的处理需求。
另一种可能的实现方式，OTT服务器生成XR通话的处理需求。作为示例，另一种可能的实现方式，根据XR应用业务逻辑和会话参数生成XR通话的处理需求。
可选地，OTT服务器确定分工指示信息时，可以综合考虑：OTT服务器的处理能力、UE#1的处理能力、以及XR通话的处理需求。关于确定分工指示信息的实现方式，可以参考步骤5112中的相关描述，此处不再赘述。
8124，OTT服务器向UE#1发送分工指示信息。
一种可能的实现方式，OTT服务器向UE#1发送HTTP消息，该HTTP消息中包括分工指示信息。
步骤8124与步骤8113类似，此处不再赘述。
场景3：UE#1发起媒体渲染重协商。
8131，UE#1向OTT服务器发送会话更新呼叫请求。
一种可能的实现方式，UE#1向OTT服务器发送HTTP消息，该HTTP消息包括会话更新呼叫请求，或者该HTTP消息用于请求会话更新呼叫。
8132，OTT服务器根据更新后的XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤8132中OTT服务器根据更新后的XR通话的处理需求和UE#1的处理能力，确定新的分工指示信息。
8133，OTT服务器向UE#1发送分工指示信息。
步骤8131-步骤8133与步骤8111-步骤8113类似，此处不再赘述。
场景4：UE#1接收媒体渲染重协商。
8141，OTT服务器向UE#1发送会话更新呼叫请求。
8142，UE#1向OTT服务器发送会话更新呼叫响应。
8143，OTT服务器根据更新后的XR通话的处理需求和UE#1的处理能力，确定分工指示信息。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，所以在步骤8143中OTT服务器根据更新后的XR通话的处理需求和UE#1的处理能力，确定新的分工指示信息。
8144，OTT服务器向UE#1发送分工指示信息。
步骤8141-步骤8144与步骤8121-步骤8124类似，此处不再赘述。
上面结合四种场景进行了示例性说明，不管在上述哪种场景下，在确定分工指示信息后，可以包括如下步骤。
821，UE#1根据分工指示信息，确定OTT服务器负责渲染的待渲染XR对象。
步骤821与步骤521类似，此处不再赘述。
822，UE#1向OTT服务器发送OTT服务器负责渲染的待渲染XR对象。
823，OTT服务器渲染OTT服务器负责渲染的待渲染XR对象。
824，UE#1渲染UE#1负责渲染的待渲染XR对象。
825，UE#1向OTT服务器发送渲染后的XR对象对应的媒体数据。
UE#1完成渲染后，将渲染完成后的XR对象对应的媒体数据发给OTT服务器。
826，OTT服务器对UE#1渲染后的XR对象对应的媒体数据以及OTT服务器渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
827，OTT服务器向UE#2发送合并后的媒体数据。
步骤822-步骤827与步骤522-步骤527类似，此处不再赘述。
可以理解，上述方法800主要以OTT服务器为例进行了示例性说明，如前所述，OTT服务器可包括信令服务器(或者称为OTT信令服务器)、媒体处理服务器(或者称为OTT媒体服务器，或者OTT媒体处理服务器)、路由服务器，不同的服务器可执行不同功能。作为示例，第一网络设备为信令服务器，第二网络设备为媒体处理服务器，具体的可参考方法600或700的描述，此处不再赘述。
基于上述技术方案，终端设备注册到OTT服务器时，终端设备和OTT服务器之间可交换各自的处理能力。终端设备确定OTT服务器支持XR对象渲染的情况下，可在会话呼叫请求中携带XR通话的处理需求，请求与OTT服务器之间进行渲染协商。OTT服务器可根据XR通话的处理需求计算得出XR对象渲染算力要求，并判断是否超出终端设备的渲染可用算力。若超出终端设备的渲染可用算力，则还可以结合OTT服务器自己的处理能力，决策本次会话的渲染分工，并将渲染协商结果通知给终端设备。终端设备基于渲染协商结果，可确定哪些XR对象在终端设备完成渲染，哪些XR对象在OTT服务器完成渲染。对于需要OTT服务器渲染的XR对象，终端设备可向OTT服务器发送OTT服务器待渲染的数据。最后，OTT服务器可对自己渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的终端设备。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由终端设备或OTT服务器发起会话更新请求，根据更新后的XR通话的处理需求重新进行渲染协商。
可以理解，图8所示方案中，如何分工是OTT服务器确定的(如步骤8112、8123等)，对此不予限制。一种可能的方案，如何分工也可以是终端设备确定的。
例如，UE#1可以根据XR通话的处理需求和UE#1的处理能力信息确定分工指示信息(具体可参考步骤8112中的描述)，进而再执行步骤821至步骤827。可选地，在执行步骤821之前，UE#1还可以向OTT服务器发送分工指示信息。
再例如，UE#1向OTT服务器发送XR对象渲染请求，OTT服务器返回XR对象渲染响应，该响应中包含指示信息，该指示信息指示OTT服务器将为UE#1渲染XR对象；UE#1确认OTT服务器将协助渲染XR对象后，再确定出归OTT服务器负责渲染的待渲染XR对象，进而再执行步骤822。该例子中，可选地，OTT服务器返回的XR对象渲染响应还可以包含OTT服务器的处理能力信息(与步骤8112中UE#1的处理能力信息类似)，如此，UE#1可以根据OTT服务器的处理能力信息等信息确定如何分工(具体可参考步骤8112中的描述)，即确定哪部分待渲染XR对象归OTT服务器渲染，再执行步骤822。可以理解，OTT服务器可以决策将当前所有剩余的处理能力都留给UE#1的XR对象的渲染，也可以决策将当前所有剩余的处理能力的一部分留给UE#1的XR对象的渲染，也就是说，OTT服务器通过XR对象渲染响应返回的处理能力信息可以表征OTT服务器当前所有剩余的处理能力，也可以表征当前所有剩余的处理能力的一部分。示例性地，OTT服务器将当前所有剩余的处理能力的5％留给UE#1的XR对象的渲染，即返回的处理能力信息表征这％5的处理能力，使UE#1根据这5％的处理能力给OTT服务器分配待渲染XR对象，如此可以避免UE#1将过多的XR对象的渲染任务分给OTT服务器，或者避免OTT服务器的资源被一个UE独占。
还可以理解，图8所示方案中，以OTT服务器对UE#1渲染后的XR对象对应的媒体数据以及OTT服务器渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，OTT服务器向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如也可以是其他设备进行合并处理，不再赘述。
图9是本申请实施例提供的一种XR对象渲染的方法900的示意图。方法900可以包括如下步骤。
910，终端设备确定渲染分工，渲染分工是指：终端设备的XR通话中的一部分待渲染XR对象归第二网络设备渲染，另一部分待渲染XR对象归终端设备渲染。
其中，第二网络设备表示对终端设备的XR通话中的部分待渲染XR对象执行渲染的网络侧设备，对应发明内容中的网络侧渲染设备。
一种可能的实施方式，终端设备根据以下至少一项确定渲染分工：终端设备的处理能力信息、第二网络设备的处理能力信息、XR通话的处理需求信息。
具体地，处理能力信息和XR通话的处理需求信息(后文记为XR通话的第一处理需求信息，对应前文的XR通话的处理需求信息)可参考方法400中处理能力信息和XR通话的处理需求信息的描述，终端设备确定渲染分工的方法可参考上文中第一网络设备确定渲染分工的方法，在此不再赘述。
920，终端设备渲染XR通话中归终端设备渲染的待渲染XR对象，并向第二网络设备发送XR通话中归第二网络设备渲染的待渲染XR对象。
若终端设备负责渲染的待渲染XR对象记为第一部分待渲染XR对象，第二网络设备负责渲染的待渲染XR对象记为第二部分待渲染XR对象。即终端设备对第一部分待渲染XR对象进行渲染，并向第二网络设备发送第二部分待渲染XR对象。
可选地，方法900还包括：终端设备向第二网络设备发送渲染后的第一部分待渲染XR对象，第二网络设备对渲染后的第一部分待渲染XR对象和渲染后的第二部分待渲染XR对象合并，也即第二网络设备对渲染后的第一部分待渲染XR对象对应的媒体数据和渲染后的第二部分待渲染XR对象对应的媒体数据合并。可能的实现方式可参考方法400中的相关描述，在此不再赘述。
进一步可选地，方法900还包括：第二网络设备向XR通话涉及的终端设备发送合并后的媒体数据。
可以理解，关于对渲染后的第一部分待渲染XR对象对应的媒体数据和渲染后的第二部分待渲染XR对象对应的媒体数据执行合并处理的设备，不予限制，可参考方法400中的相关描述，在此不再赘述。
在本申请实施例中，终端设备根据XR会话需要渲染的XR对象计算渲染所需要消耗的算力，并判断所需要消耗的算力超过终端设备自身的处理能力的情况下可以确定渲染分工，并可以通过分工确认请求信息请求第一网络设备接受渲染分工。这样，针对XR通话，可以通过终端设备，在终端设备和第二网络设备之间动态地分配渲染任务，实现终端设备和第二网络设备之间的有效协同和渲染任务的按需分配。
可选地，第一网络设备向终端设备发送第二网络设备的处理能力信息。
其中，第一网络设备表示确定渲染分工的网络侧设备，对应发明内容中的网络侧控制设备。
一种可能的实现方式，第二网络设备的处理能力信息可以是第二网络设备的部分处理能力信息。
示例地，第二网络设备的部分处理能力信息可以是第二网络设备基于自身计算资源的配置确定的，或者是所述第二网络设备基于第二网络设备的剩余计算资源或可用计算资源确定。
具体地，第一网络设备发送的处理能力信息所占第二网络设备的全部处理能力信息的比例可通过第二网络设备自身的负载灵活确定，本申请对此不做限制。例如，网络设备发送的处理能力信息表征全部处理能力的10％，使终端设备根据这10％的处理能力给网络设备分配待渲染XR对象，避免终端设备将过多的XR对象的渲染任务分给网络设备，或者避免网络设备的资源被一个终端设备独占。
可选地，终端设备在确定第二网络设备能够对该XR通话中的待渲染XR对象进行渲染的情况下，向第三网络设备发送会话呼叫消息以触发第三网络设备向第一网络设备发送分工确认请求信息，用于请求第一网络设备接受渲染分工，其中，渲染分工中归第二网络设备渲染的待渲染XR对象由终端设备确定。分工确认请求信息包括XR通话的处理需求信息(后文记为XR通话的第二处理需求信息)。第一网络设备根据XR通话的第二处理需求信息向第二网络设备申请渲染资源。例如，终端设备默认第二网络设备能够对该XR通话中的待渲染XR对象进行渲染；再例如，终端设备获取服务指示信息，该服务指示信息指示第二网络设备能够对该XR通话中的待渲染XR对象进行渲染。其中，第一网络设备可以基于终端设备的签约数据判断终端设备是否签约了网络渲染功能，如签约了网络渲染功能，第一网络设备可以向终端设备发送终端设备签约的网络渲染功能(即服务指示信息)，告知终端设备第二网络设备能够对该XR通话中的待渲染XR对象进行渲染。
其中，第三网络设备对应发明内容中的网络侧接入设备，第三网络设备例如可以为IMS网络中的网元，或者也可以是OTT服务器等，不予限制。
一种可能的实施方式，XR通话的第二处理需求信息包括：用于确定XR通话的待渲染XR对象中归第二网络设备渲染的待渲染XR对象的信息。
示例地，若是按类型分工，XR通话的第二处理需求信息包括第二部分待渲染XR对象的信息，第二部分待渲染XR对象的信息可以是待渲染XR对象的类型(如人物、建筑、植物等)。
示例地，若是按层分工，XR通话的第二处理需求信息包括第二部分待渲染XR对象的信息，第二部分待渲染XR对象的信息可以是待渲染XR对象的层次信息(如前景或背景)。
可选地，XR通话的第二处理需求信息还包括以下至少一项：XR通话的视频分辨率、XR通话的视频帧率。
应注意，此处XR通话的第二处理需求信息与S910中终端设备确定终端设备的XR通话中待渲染 XR对象的渲染分工时依据的XR通话的第一处理需求信息有区别。区别如下：S910中终端设备确定终端设备的XR通话中待渲染XR对象的渲染分工时依据的XR通话的第一处理需求信息包括的是XR通话的待渲染XR对象的信息，也就是说XR通话的全部待渲染XR对象的信息。而此处XR通话的第二处理需求信息包括的是XR通话的待渲染XR对象中归第二网络设备渲染的待渲染XR对象的信息，也就是说XR通话的部分需要第二网络设备渲染的待渲染XR对象的信息，或者是能够让第二网络设备确定在XR通话的待渲染XR对象中归第二网络设备渲染的待渲染XR对象的信息，本申请对此不做限制。
可选地，若第一网络设备和第二网络设备为不同设备，第一网络设备向第二网络设备发送请求消息，请求消息用于请求以下至少一项：第二网络设备的地址信息、第二网络设备的渲染资源信息；第一网络设备接收来自第二网络设备的请求消息的响应。详细内容可参见方法400中的相关介绍，在此不再赘述。
可以理解，方法900中涉及的部分流程和内容与方法400类似，因此类似处涉及的详细内容可参见方法400中的相关介绍，方法900中不再赘述。
图10是本申请实施例提供的一种XR对象渲染的方法1000的示意性流程图。该方法1000可以用于实现上述方法900的方案。在该方法1000中，假设第一网络设备和第二网络设备相同，即为图10中的网络设备；或者图10中的网络设备为第一网络设备和第二网络设备组成的系统，该方法1000可以包括如下步骤。
1001，网络设备向UE#1发送服务指示信息。
网络设备可获取UE#1的签约数据，根据签约数据判断UE#1是否签约或购买了网络渲染服务，如果签约了网络渲染功能，则网络设备能够协助UE#1渲染XR对象，则向UE#1发送服务指示信息以告知UE#1网络设备能够对XR对象进行渲染，或者告知UE#1网络设备能够提供对XR对象进行渲染的服务。
网络签约功能的参数示例：Network_Function:rendering。
1002，网络设备向UE#1发送网络设备的处理能力。
网络设备的处理能力，可以参考步骤501中UE#1的处理能力，此处不再赘述。
需要注意的是此处网络设备的处理能力可以是网络设备的全部处理能力中的部分处理能力，具体部分处理能力占用全部处理能力的百分比如何确定参考方法900中相关描述，不再赘述。
可以理解，服务指示信息和网络设备的处理能力可以在一个消息中发送，也可以在两个消息中发送，本申请对此不做限制。如果在两个消息中发送，本申请对步骤1001和1002的先后顺序不做限定。
1003，UE#1确定网络设备能够渲染XR对象。
示例地，UE#1保存网络设备的处理能力和/或服务指示信息，基于服务指示信息可获知网络设备是否能够渲染XR对象，也即是否支持XR对象渲染。基于网络设备的处理能力可以获知网络设备是否有足够能力协助UE#1完成XR对象的渲染。步骤1001/1002/1003为可选步骤，也即网络设备可以不用向UE#1提供服务指示信息，UE#1可默认UE#1签约了网络渲染功能。或者网络设备可以不用向UE#1提供网络设备的处理能力，UE#1可默认网络设备有足够能力协助UE#1完成XR对象的渲染。
下面结合四种场景介绍渲染协商过程。
场景1：UE#1发起初始会话呼叫。
1011，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工，即XR通话中的一部分待渲染XR对象归网络设备渲染，另一部分待渲染XR对象归UE#1渲染。
UE#1在发起初始会话呼叫时，基于XR通话的第一处理需求信息确定通过UE#1的处理能力不能完成XR通话中XR对象的渲染，因此UE#1确定本次XR通话需要进行拆分渲染。
一种可能的情形，UE#1默认签约了网络渲染功能，并且默认网络设备有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
另一种可能的情形，UE#1基于1001中的服务指示信息确定签约了网络渲染功能，即网络设备支持XR对象渲染，默认网络设备有足够能力协助UE#1完成XR对象的渲染，继而确定XR通话的待渲染XR对象的渲染分工。若UE#1确定网络设备不支持XR对象渲染，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍网络设备支持XR对象渲染的情况。
又一种可能的情形，UE#1默认签约了网络渲染功能，并且UE#1基于1002中的网络设备的处理能力确定网络设备有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
还一种可能的情形，UE#1基于1001中的服务指示信息确定签约了网络渲染功能，并且基于1002中的网络设备的处理能力确定网络设备有足够能力协助UE#1完成XR对象的渲染(即网络设备完成待渲染XR对象的渲染所需要的可用算力没有超出网络设备的处理能力)，继而确定XR通话的待渲染XR对象的渲染分工，即确定UE#1和网络设备各自需要渲染的XR对象。
1012，UE#1向网络设备发送会话呼叫请求，会话呼叫请求中包括分工确认请求信息，分工确认请求信息用于请求网络设备接受渲染分工。
一种可能的实现方式，分工确认请求信息包括XR通话的第二处理需求信息。XR通话的第二处理需求信息包括XR通话的待渲染XR对象中需要网络设备渲染的待渲染XR对象的信息。XR通话的第二处理需求信息包括的其他内容(例如XR通话的视频分辨率、视频帧率)参考步骤5111中相关描述，不再赘述。
示例地，分工确定请求信息可以指示XR通话的全部待渲染XR对象需要网络设备渲染，或XR通话的部分待渲染XR对象需要网络设备渲染，本申请对此不做限制。
1013，网络设备接受渲染分工，分配渲染资源。
一种可能的实现方式，网络设备基于分工确认请求信息确定终端设备想要网络设备协助完成渲染的待渲染XR对象的信息，进一步基于网络设备的处理能力确定是否可以协助完成渲染。例如，网络设备判断终端设备想要网络设备协助完成渲染的待渲染XR对象所需的渲染算力超出网络设备的渲染可用算力，则表示网络设备不能接受渲染分工。再例如，网络设备判断终端设备想要网络设备协助完成渲染的待渲染XR对象所需的渲染算力没有超出网络设备的渲染可用算力，则表示网络设备能接受渲染分工，本申请实施例主要介绍网络设备能接受渲染分工。
网络设备确定能接受渲染分工，进一步，为需要网络设备渲染的待渲染XR对象预留渲染资源。
示例地，网络设备根据需要网络设备渲染的待渲染XR对象的信息确定该待渲染XR对象所需要消耗的算力，基于XR算力要求预留或者分配相应的算力资源。算力资源例如，内存或者CPU时隙或GPU资源等。
网络设备判断待渲染XR对象所需的渲染算力是否超出网络设备的渲染可用算力的方法可以参考5112中的相关描述，不再赘述。
1014，网络设备向UE#1发送分工确认响应信息，分工确认响应信息指示网络设备接受渲染分工。
场景2：UE#1接收初始会话呼叫。
1021，网络设备向UE#1发送会话呼叫请求。
1022，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
UE#1在接收会话呼叫请求时，基于XR通话的第一处理需求信息确定通过UE#1的处理能力不能完成XR通话中XR对象的渲染，因此UE#1确定本次XR通话需要进行拆分渲染。
UE#1确定渲染分工的具体内容参见步骤1011中相关描述，不再赘述。
1023，UE#1向网络设备发送会话呼叫响应，会话呼叫响应包括分工确认请求信息。
具体参见步骤1012中相关描述，不再赘述。
1024，网络设备接受渲染分工，分配渲染资源。
1025，网络设备向UE#1发送分工确认响应信息。
步骤1024-步骤1025与步骤1013-步骤1014类似，此处不再赘述。
场景3：UE#1发起会话更新呼叫。
1031，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
在本申请实施例中，假设XR通话的处理需求发生变化，则UE#1在发起会话更新呼叫时，重新通过UE#1的处理能力确定是否能完成XR通话中XR对象的渲染，与步骤1011类似，具体参见步骤1011中相关描述，不再赘述。
1032，UE#1向网络设备发送会话更新呼叫请求，会话更新呼叫请求包括分工确认请求信息，分工确认请求信息用于请求网络设备接受更新后的渲染分工。
具体参见步骤1012中相关描述，不再赘述。
1033，网络设备接受更新后的渲染分工，更新渲染资源。
示例地，网络设备根据会话更新呼叫请求中包括的分工确认请求信息，重新确定需要网络设备侧渲染的待渲染XR对象，根据需要网络设备侧渲染的待渲染XR对象更新渲染资源。可以理解的是本步骤中网络设备可以重用步骤1013中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1013中预留或分配的算力资源。
1034，网络设备向UE#1发送分工确认响应信息，分工确认响应信息指示网络设备接受更新后的渲染分工。
步骤1033-步骤1034与步骤1013-步骤1014类似，此处不再赘述。
场景4：UE#1接收会话更新呼叫。
1041，网络设备向UE#1发送会话更新呼叫请求。
1042，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
在本申请实施例中，假设XR通话的处理需求发生变化，则UE#1在接收到会话更新呼叫请求时，重新通过UE#1的处理能力确定是否能完成XR通话中XR对象的渲染，与步骤1011类似，具体参见步骤1011中相关描述，不再赘述。
1043，UE#1向网络设备发送会话更新呼叫响应，会话更新呼叫响应包括分工确认请求信息，分工确认请求信息用于请求网络设备接受更新后的渲染分工。
具体参见步骤1012中相关描述，不再赘述。
1044，网络设备接受更新后的渲染分工，更新渲染资源。
示例地，网络设备根据会话更新呼叫响应中包括的分工确认请求信息，重新确定需要网络设备侧渲染的待渲染XR对象，根据需要网络设备侧渲染的待渲染XR对象更新渲染资源。可以理解的是本步骤中网络设备可以重用步骤1024中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1024中预留或分配的算力资源。
1045，网络设备向UE#1发送分工确认响应信息，分工确认响应信息指示网络设备接受更新后的渲染分工。
步骤1044-步骤1045与步骤1013-步骤1014类似，此处不再赘述。
上面结合四种场景进行了示例性说明，不管在上述哪种场景下，在UE#1接收到分工确认响应信息后，可以包括如下步骤。
1051，UE#1向网络设备发送网络设备负责渲染的待渲染XR对象。
示例地，UE#1基于XR通话的待渲染XR对象的渲染分工向网络设备发送网络设备负责渲染的待渲染XR对象。
1052，网络设备渲染网络设备负责渲染的待渲染XR对象。
1053，UE#1渲染UE#1负责渲染的待渲染XR对象。
1054，UE#1向网络设备发送渲染后的XR对象对应的媒体数据。
1055，网络设备对UE#1渲染后的XR对象对应的媒体数据以及网络设备渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
1056，网络设备向UE#2发送合并后的媒体数据。
步骤1051-步骤1056与步骤522-步骤527类似，此处不再赘述。
基于上述技术方案，网络设备可以将自身的处理能力以及服务指示信息通知给终端设备。终端设备在确定XR对象渲染算力要求超出终端设备的渲染可用算力，并且确定网络设备支持XR对象渲染的情况下确定渲染分工，向网络设备发送分工确认请求信息，请求与网络设备之间进行渲染协商。网络设备可根据分工确认请求信息确定将协助终端设备完成XR对象的渲染并告知终端设备，终端设备向网络设备发送网络设备待渲染的数据。最后，网络设备或其他设备可对网络设备渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的终端设备。
可以理解，图10所示方案中，以网络设备对UE#1渲染后的XR对象对应的媒体数据以及网络设备渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以 是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，网络设备向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如，也可以是其他设备进行合并处理，不再赘述。
图11是本申请实施例提供的一种XR对象渲染的方法1100的示意性流程图。该方法1100可以用于实现上述方法900的方案。该方法1100可用于基于DC的渲染协商的场景，渲染协商例如可在DC建立完成后进行。在该方法1100中，第一网络设备为XR-C网元，第二网络设备为XR-M网元，IMS包含一个或多个网元，例如可以参考图1所示的架构，下面统一用“IMS”表示。作为示例，图11所示的方法1100可用于图1架构。该方法1100可以包括如下步骤。
步骤1101之前，UE#1在向IMS注册的过程中，向IMS发送SIP注册(REGISTER)消息，IMS对UE#1注册鉴权成功后，向XR-C网元发送HTTP消息。
1101，XR-C网元向IMS发送服务指示信息。
XR-C网元确定服务指示信息的方法与步骤1001类似，不再赘述。
一种可能的实现方式，XR-C网元向IMS发送HTTP响应消息(如200消息)，该HTTP响应消息中包括服务指示信息。
1102，IMS向UE#1发送服务指示信息。
1103，XR-C网元向IMS发送XR-M网元的处理能力。
XR-M网元的处理能力与步骤1002中的网络设备的处理能力类似，不再赘述。
一种可能的实现方式，XR-C网元向IMS发送HTTP响应消息(如200消息)，该HTTP响应消息中包括XR-M网元的处理能力。
1104，IMS向UE#1发送XR-M网元的处理能力。
可以理解，服务指示信息和XR-M网元的处理能力可以在一个消息中发送，也可以在两个消息中发送，本申请对此不做限制。如果在两个消息中发送，本申请对步骤1101和1103的先后顺序，以及步骤1102和1104的先后顺序不做限定。
1105，UE#1确定XR-M网元能够渲染XR对象。
示例地，UE#1保存网络设备的处理能力和/或服务指示信息，基于服务指示信息可获知XR-M网元是否能够渲染XR对象，也即是否支持XR对象渲染。基于XR-M网元的处理能力可以获知XR-M网元是否有足够能力协助UE#1完成XR对象的渲染。步骤1101-步骤1105为可选步骤，也即XR-C网元可以不用向UE#1提供服务指示信息，UE#1可默认UE#1签约了网络渲染功能。或者可以不用向UE#1提供XR-M网元的处理能力，UE#1可默认XR-M网元有足够能力协助UE#1完成XR对象的渲染。
1106，音视频媒体通道建立和DC建立。
与步骤607类似，不再赘述。
可以理解，步骤1101至1104中发送的服务指示信息以及XR-M网元的处理能力也可以在UE#1发起媒体渲染协商流程之前完成，本申请对此不做限制。例如服务指示信息以及XR-M网元的处理能力可以在DC通道完成发送。
下面结合两种场景介绍渲染协商过程。
场景1：UE#1发起渲染协商。
1111，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工，即XR通话中的一部分待渲染XR对象归XR-M网元渲染，另一部分待渲染XR对象归UE#1渲染。
UE#1基于XR通话的第一处理需求信息确定通过UE#1的处理能力不能完成XR通话中XR对象的渲染，因此UE#1确定本次XR通话需要进行拆分渲染。
一种可能的情形，UE#1默认签约了网络渲染功能，并且默认XR-M网元有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
另一种可能的情形，UE#1基于1102中的服务指示信息确定UE#1签约了网络渲染功能，即XR-M网元支持XR对象渲染，默认XR-M网元有足够能力协助UE#1完成XR对象的渲染，继而确定XR通话的待渲染XR对象的渲染分工。若UE#1确定XR-M网元不支持XR对象渲染，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍XR-M网元支持XR对象渲染的情况。
又一种可能的情形，UE#1默认签约了网络渲染功能，并且UE#1基于1104中的XR-M网元的处 理能力确定XR-M网元有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
还一种可能的情形，UE#1基于1102中的服务指示信息确定XR-M网元支持XR对象渲染，并且基于1104中的XR-M网元的处理能力确定XR-M网元有足够能力协助UE#1完成XR对象的渲染(即XR-M网元完成待渲染XR对象的渲染所需要的可用算力没有超出XR-M网元的处理能力)，继而确定确定XR通话的待渲染XR对象的渲染分工。
1112，UE#1向IMS发送分工确认请求信息，分工确认请求信息用于请求XR-C网元接受渲染分工。
一种可能的实现方式，UE#1向IMS发送媒体渲染协商请求，媒体渲染协商请求包括分工确认请求信息，分工确认请求信息包括XR通话的第二处理需求信息，XR通话的第二处理需求信息包括XR通话的待渲染XR对象中需要网络设备渲染的待渲染XR对象的信息。例如XR通话的第二处理需求信息包括参数C1、参数C2、参数D、参数E。具体的，可以参考1012以及5111中的相关描述，此处不再赘述。
作为示例，XR通话的第二处理需求信息的形式如下：
XR-Session-Attribute:
network_rendering_content＝0,1,2,3；rendering_type＝0/1；video_resolution＝1920,1080；video_frame_rate＝30
其中，“network_rendering_content”表示参数C1，即需要XR-M网元渲染的待渲染的XR对象。rendering_type表示参数C2，即需要XR-M网元渲染部分待渲染的XR对象还是需要XR-M网元渲染全部待渲染的XR对象。例如rendering_type＝0表示需要XR-M网元渲染部分待渲染的XR对象，rendering_type＝1表示需要XR-M网元渲染全部待渲染的XR对象“video_resolution”表示参数D，即视频分辨率。“video_frame_rate”表示参数E，即视频帧率。
XR-M网元渲染部分待渲染的XR对象时需要将UE#1和XR-M网元渲染后的XR对象对应的媒体数据合并后再发给UE#2，XR-M网元渲染全部待渲染的XR对象时，可直接将XR-M网元渲染后的全部XR对象对应的媒体数据直接发送给UE#2。
可以理解，上述以XR-M网元对UE#1渲染后的XR对象对应的媒体数据以及XR-M网元渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，XR-M网元向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如也可以是其他设备进行合并处理，不再赘述。
1113，IMS向XR-C网元发送HTTP请求消息，HTTP请求消息中也包括分工确认请求信息。
1114，XR-C网元向XR-M网元申请渲染资源。
XR-C网元根据分工确认请求信息，确定需要XR-M网元侧渲染XR对象时，可向XR-M网元申请资源，即请求XR-M网元渲染XR-M网元负责渲染的待渲染XR对象。一种可能的实现方式，XR-C网元向XR-M网元发送HTTP请求消息，该HTTP请求消息用于向XR-M网元申请与渲染XR对象有关的渲染资源。
示例性地，XR-C网元向XR-M申请渲染资源包括：XR-C网元向XR-M网元请求创建或分配端点资源。相应地，XR-M网元创建或分配相应的资源端点(也称为媒体端点)，并将相应的资源端点的信息(对应发明内容中的网络侧渲染设备的地址信息)返回给XR-C网元。例如，XR-M网元接收到上述HTTP请求后，创建或分配两个资源端点，分别为第一资源端点和第二资源端点，第一资源端点的属性包括第一资源端点的本端连接地址、第二资源端点的属性包括第二资源端点的本端连接地址，其中，第一资源端点的本端连接地址、第二资源端点的本端连接地址分别用于使UE#1通过IMS(UE#1接入的IMS)与XR-M网元建立通信连接和使UE#2通过IMS(UE#2接入的IMS)与XR-M网元建立通信连接。
示例性地，XR-C网元向XR-M申请渲染资源还可以包括：XR-C网元向XR-M网元请求预留或分配算力资源。可选地，XR-C网元向XR-M网元发送待渲染XR对象的信息或XR算力要求，该XR算力要求表示归XR-M网元渲染的待渲染XR对象所需要消耗的算力，相应地，XR-M网元预留或分配相应的算力资源，例如，内存或者CPU时隙或GPU资源等；如此，XR-M网元可以根据待渲染XR对 象的信息或XR算力要求，预留或者分配相应的算力资源。
1115，XR-M网元向XR-C网元发送申请结果。
一种可能的实施方式，XR-M网元向XR-C网元返回资源申请结果，包括以下至少一项：结果指示信息、资源端点的信息。其中，结果指示信息可用于通知XR-C网元，XR-M网元是否将对XR-M网元负责渲染的待渲染XR对象进行渲染。进一步，可选地，若资源申请结果用于通知XR-C网元：XR-M网元将对XR-M网元负责渲染的待渲染XR对象进行渲染，则XR-C网元可向UE#1发送传输指示信息，以指示UE#1向XR-M网元发送XR-M网元负责渲染的待渲染XR对象。示例性地，资源端点的信息包括第一资源端点的本端连接地址和第二资源端点的本端连接地址。
一种可能的情形，若XR-M网元向XR-C网元返回的资源端点的信息包含第一资源端点的本端连接地址，则XR-C网元可向IMS(例如IMS中的P-CSCF网元)发送第一资源端点的本端连接地址，以便于IMS(例如P-CSCF控制的IMS-AGW)通过第一资源端点的本端连接地址与XR-M网元通信，例如UE#1通过IMS-AGW向XR-M网元发送由XR-M网元负责渲染的待渲染XR对象。示例地，UE#1与IMS-AGW已有连接，例如第一连接(连接还可以理解为通道)，IMS可以通过XR-C网元发送的第一资源端点的本端连接地址建立IMS-AGW与XR-M网元的第二连接，并且建立第一连接和第二连接的对应关系，该对应关系可以使得IMS-AGW接收到UE#1发送的由XR-M网元负责渲染的待渲染XR对象后，可以确定第二连接，并通过第二连接将由XR-M网元负责渲染的待渲染XR对象转发给XR-M网元。此外，若XR-M网元向XR-C网元返回的资源端点的信息包含第二资源端点的本端连接地址，XR-C网元还可向IMS(例如UE#2接入的IMS中的P-CSCF)发送第二资源端点的本端连接地址，以便于UE#2通过该IMS与XR-M网元通信，如UE#2通过该IMS从XR-M网元获取合并后的媒体数据。示例地，XR-C网元可向UE#2接入的IMS中的P-CSCF发送第二资源端点的本端连接地址，以便于UE#2通过P-CSCF控制的IMS-AGW连接到XR-M网元，这样UE#2可以通过IMS-AGW从XR-M网元获取合并后的媒体数据。
可以理解，XR-M网元向XR-C网元返回的申请结果表示XR-M网元将对XR-M网元负责渲染的待渲染XR对象进行渲染，即XR-C网元向XR-M网元申请渲染资源成功，进一步地，XR-C网元接受渲染分工。
1116，XR-C网元向IMS发送分工确认响应信息与资源端点的信息。
1117，IMS向UE#1发送分工确认响应信息，分工确认响应信息用于指示XR-C网元接受渲染分工。
场景2：UE#1发起重新渲染协商。
1121，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
在XR通话过程中XR通话的处理需求更新的情况下，UE#1重新确定待渲染XR对象的渲染分工，除此之外，与步骤1111类似，不再赘述。
1122，UE#1向IMS发送重新分工确认请求信息，重新分工确认请求信息包括更新后的XR通话的第二处理需求信息。更新后的XR通话的第二处理需求信息包括XR通话的待渲染XR对象中需要XR-M网元渲染的待渲染XR对象的信息。
在某些情况下，例如，在XR通话过程中XR通话的处理需求更新的情况下，终端设备可能会发起重新渲染协商。在这些情况下，UE#1可以向IMS发送重新分工确认请求信息，以便重新对XR通话进行渲染协商。
1123，IMS向XR-C网元发送HTTP消息，HTTP消息包括重新分工确认请求信息，用于请求XR-C网元接受更新后的渲染分工。
1124，XR-C网元向XR-M网元申请更新渲染资源。
XR-C网元根据重新分工确认请求信息，确定需要XR-M网元侧更新渲染时，可向XR-M网元申请更新资源。一种可能的实现方式，XR-C网元向XR-M网元发送HTTP消息，该HTTP消息用于申请修改资源。可以理解的是，本步骤中XR-M网元可以重新创建端点资源，也可以重用步骤1114中创建或分配的端点资源；XR-M网元可以重用步骤1114中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1114预留或分配的算力资源。
1125，XR-M网元向XR-C网元发送申请结果。
一种可能的实现方式，XR-M网元向XR-C网元返回资源申请结果，包括以下至少一项：结果指 示信息、资源端点的信息。其中，结果指示信息可用于通知XR-C网元，XR-M网元是否将对XR-M网元负责渲染的待渲染XR对象进行渲染。若XR-M网元重新创建了端点资源，则资源端点的信息包括重新创建的端点资源的信息。
1126，XR-C网元向IMS发送分工确认响应信息。
示例地，XR-C网元接收到的申请结果表示XR-M网元将对XR-M网元负责渲染的待渲染XR对象进行渲染，即XR-C网元向XR-M网元申请渲染资源成功，进一步地，XR-C网元接受渲染分工，向IMS发送分工确认响应信息。可选地，若步骤1125中XR-M网元重新创建了端点资源，XR-C网元还需要向IMS发送新的资源端点的信息。
1127，IMS向UE#1发送分工确认响应信息。
上面结合两种场景进行了示例性说明，不管在上述哪种场景下，在UE#1接收到分工确认响应信息后，可以包括如下步骤。
1151，UE#1向XR-M网元发送XR-M网元负责渲染的待渲染XR对象。
一种可能的实现方式，UE#1基于XR通话的待渲染XR对象的渲染分工向XR-M网元发送XR-M网元负责渲染的待渲染XR对象。
示例地，UE#1基于XR通话的待渲染XR对象的渲染分工，通过第一连接向IMS-AGW发送XR-M网元负责渲染的待渲染XR对象，IMS-AGW基于第一连接与第二连接的对应关系，通过第二连接将由XR-M网元负责渲染的待渲染XR对象转发给XR-M网元。
1152，XR-M网元渲染XR-M网元负责渲染的待渲染XR对象。
1153，UE#1渲染UE#1负责渲染的待渲染XR对象。
1154，UE#1向XR-M网元发送渲染后的XR对象对应的媒体数据。
1155，XR-M网元对UE#1渲染后的XR对象对应的媒体数据以及XR-M网元渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
1156，XR-M网元向UE#2发送合并后的媒体数据。
步骤1151-步骤1156与步骤622-步骤627类似，此处不再赘述。
基于上述技术方案，XR-C网元可以将XR-M网元的处理能力和服务指示信息通知给终端设备。终端设备在确定XR对象渲染算力要求超出终端设备的渲染可用算力，并且确定网络设备支持XR对象渲染的情况下确定渲染分工，可在DC通道中传输分工确认请求信息，请求进行渲染协商。XR-C网元可根据分工确认请求信息确定XR-M网元将协助终端设备完成XR对象的渲染并告知终端设备，终端设备向XR-M网元发送XR-M网元待渲染的数据。最后，XR-M网元或其他设备可对XR-M网元渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的UE#2。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由UE#1会重新发起渲染协商，根据更新后的XR通话的处理需求重新进行渲染协商。
图12是本申请实施例提供的一种XR对象渲染的方法1200的示意性流程图。该方法1200可以用于实现上述方法900的方案。该方法1200可用于基于IMS SIP信令进行渲染协商的场景，渲染协商例如可在呼叫建立过程中完成。在该方法1200中，第一网络设备为AS，第二网络设备为MRF网元，MRF网元例如可以包括MRFC和MRFP，IMS包含一个或多个网元，例如可以参考图2所示的架构，下面统一用“IMS core”表示。作为示例，图12所示的方法1200可用于图2架构。该方法1200可以包括如下步骤。
步骤1201之前，UE#1在向IMS core注册的过程中，向IMS发送SIP REGISTER消息，IMS core对UE#1注册鉴权成功后，向AS网元发送SIP REGISTER。
1201，AS向IMS core发送服务指示信息。
AS确定服务指示信息的方法与步骤1001类似，不再赘述。
1202，IMS core向UE#1发送服务指示信息。
1203，AS向IMS core发送MRF网元的处理能力。
1204，IMS core向UE#1发送MRF网元的处理能力。
可以理解，服务指示信息和MRF网元的处理能力可以在一个消息中发送，也可以在两个消息中发 送，本申请对此不做限制。如果在两个消息中发送，本申请对步骤1201和1203的先后顺序，以及步骤1202和1204的先后顺序不做限定。
1205，UE#1确定MRF网元能够渲染XR对象。
示例地，UE#1保存网络设备的处理能力和/或服务指示信息，基于服务指示信息可获知MRF网元是否能够渲染XR对象，也即是否支持XR对象渲染。基于MRF网元的处理能力可以获知MRF网元是否有足够能力协助UE#1完成XR对象的渲染。步骤1201-步骤1205为可选步骤，也即AS网元可以不用向UE#1提供服务指示信息，UE#1可默认UE#1签约了网络渲染功能。或者可以不用向UE#1提供MRF网元的处理能力，UE#1可默认MRF网元有足够能力协助UE#1完成XR对象的渲染。
下面结合四种场景介绍渲染协商过程。
场景1：UE#1发起XR通话呼叫建立。
1211，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工，即XR通话中的一部分待渲染XR对象归MRF网元渲染，另一部分待渲染XR对象归UE#1渲染。
UE#1基于XR通话的第一处理需求信息确定通过UE#1的处理能力不能完成XR通话中XR对象的渲染，因此UE#1确定本次XR通话需要进行拆分渲染。
一种可能的情形，UE#1默认签约了网络渲染功能，并且默认MRF网元有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
另一种可能的情形，UE#1基于1202中的服务指示信息确定UE#1签约了网络渲染功能，即MRF网元支持XR对象渲染，默认MRF网元有足够能力协助UE#1完成XR对象的渲染，继而确定XR通话的待渲染XR对象的渲染分工。若UE#1确定MRF网元不支持XR对象渲染，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍MRF网元支持XR对象渲染的情况。
又一种可能的情形，UE#1默认签约了网络渲染功能，并且UE#1基于1204中的MRF网元的处理能力确定MRF网元有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
还一种可能的情形，UE#1基于1202中的服务指示信息确定MRF网元支持XR对象渲染，并且基于1204中的MRF网元的处理能力确定MRF网元有足够能力协助UE#1完成XR对象的渲染(即MRF网元完成待渲染XR对象的渲染所需要的可用算力没有超出MRF网元的处理能力)，继而确定XR通话的待渲染XR对象的渲染分工。1212，UE#1向IMS core发送INVITE消息，INVITE消息包括分工确认请求信息，分工确认请求信息用于请求AS网元接受渲染分工。
分工确认请求信息包括XR通话的第二处理需求信息，具体与步骤1112类似，不再赘述。
1213，IMS core向AS发送INVITE消息。
可选地，若步骤1212中的INVITE消息包括分工确认请求信息，则步骤1213中的INVITE消息中也包括分工确认请求信息。
1214，AS向MRF网元申请渲染资源。
AS网元根据分工确认请求信息，确定需要MRF网元侧渲染XR对象时，可向MRF网元申请资源，即请求MRF网元渲染MRF网元负责渲染的待渲染XR对象。一种可能的实现方式，AS网元向MRF网元发送INVITE消息，该INVITE消息用于向MRF网元申请与渲染XR对象有关的渲染资源。
示例性地，AS网元向MRF申请渲染资源包括：AS网元向MRF网元请求创建或分配端点资源。相应地，MRF网元创建或分配相应的资源端点(也称为媒体端点)，并将相应的资源端点的信息(对应发明内容中的网络侧渲染设备的地址信息)返回给AS网元。例如，MRF网元接收到上述INVITE消息后，创建或分配两个资源端点，分别为第一资源端点和第二资源端点，第一资源端点的属性包括第一资源端点的本端连接地址、第二资源端点的属性包括第二资源端点的本端连接地址，其中，第一资源端点的本端连接地址、第二资源端点的本端连接地址分别用于使UE#1通过IMS core(UE#1接入的IMS core)与MRF网元建立通信连接和使UE#2通过IMS core(UE#2接入的IMS core)与MRF网元建立通信连接。
示例性地，AS网元向MRF申请渲染资源还可以包括：AS网元向MRF网元请求预留或分配算力资源。相应地，MRF网元预留或分配相应的算力资源，例如，内存或者CPU时隙或GPU资源等。可选地，AS网元向MRF网元发送待渲染XR对象的信息或XR算力要求，该XR算力要求表示归MRF 网元渲染的待渲染XR对象所需要消耗的算力，如此，MRF网元可以根据待渲染XR对象的信息或XR算力要求，预留或者分配相应的算力资源。
1215，MRF网元向AS发送申请结果。
一种可能的实施方式，MRF网元向AS网元返回资源申请结果，包括以下至少一项：结果指示信息、资源端点的信息。其中，结果指示信息可用于通知AS网元，MRF网元是否将对MRF网元负责渲染的待渲染XR对象进行渲染。进一步，可选地，若资源申请结果用于通知AS网元：MRF网元将对MRF网元负责渲染的待渲染XR对象进行渲染，则AS网元可向UE#1发送传输指示信息，以指示UE#1向MRF网元发送MRF网元负责渲染的待渲染XR对象。示例性地，资源端点的信息包括第一资源端点的本端连接地址和第二资源端点的本端连接地址。
一种可能的情形，若MRF网元向AS网元返回的资源端点的信息包含第一资源端点的本端连接地址，则AS网元可向IMS core(例如IMS core中的P-CSCF网元)发送第一资源端点的本端连接地址，以便于IMS core(例如P-CSCF控制的IMS-AGW)通过第一资源端点的本端连接地址与MRF网元通信，例如UE#1通过IMS-AGW向MRF网元发送由MRF网元负责渲染的待渲染XR对象。示例地，UE#1与IMS-AGW已有连接，例如第三连接(连接还可以理解为通道)，IMS core可以通过AS网元发送的第一资源端点的本端连接地址建立IMS-AGW与MRF网元的第四连接，并且建立第三连接和第四连接的对应关系，该对应关系可以使得IMS-AGW接收到UE#1发送的由MRF网元负责渲染的待渲染XR对象后，可以确定第四连接，并通过第四连接将由MRF网元负责渲染的待渲染XR对象转发给MRF网元。此外，若MRF网元向AS网元返回的资源端点的信息包含第二资源端点的本端连接地址，AS网元还可向IMS core(例如UE#2接入的IMS core中的P-CSCF)发送第二资源端点的本端连接地址，以便于UE#2通过该IMS core与MRF网元通信，如UE#2通过该IMS core从MRF网元获取合并后的媒体数据。示例地，AS网元可向IMS core中的P-CSCF发送第二资源端点的本端连接地址，以便于UE#2通过P-CSCF控制的IMS-AGW连接到MRF网元，这样UE#2可以通过IMS-AGW从MRF网元获取合并后的媒体数据。
可以理解，MRF网元向AS网元返回的申请结果表示MRF网元将对MRF网元负责渲染的待渲染XR对象进行渲染，即AS网元向MRF网元申请渲染资源成功，进一步地，AS网元接受渲染分工。
1216，AS向IMS core发送分工确认响应信息与资源端点的信息，分工确认响应信息用于指示AS网元接受渲染分工。
1217，IMS core向UE#1发送分工确认响应信息。
场景2：UE#1接收XR通话呼叫建立。
1221，AS向IMS core发送INVITE消息。
1222，IMS core向UE#1发送INVITE消息。
1223，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工.
除场景之外，与步骤1211类似，不再赘述。
1224，UE#1向IMS core发送200 For INVITE消息，200 For INVITE消息包括分工确认请求信息。
分工确认请求信息包括XR通话的第二处理需求信息，具体与步骤1112类似，不再赘述。
步骤1224中的200 For INVITE消息，也可以替换为18X For INVITE消息，关于消息的具体类型不予限制。
1225，IMS core向AS发送200 For INVITE消息，200 For INVITE消息包括分工确认请求信息。
步骤1225中的200 For INVITE消息，也可以替换为18X For INVITE消息，关于消息的具体类型不予限制。
1226，AS向MRF网元申请渲染资源。
1227，MRF网元向AS发送申请结果。
1228，AS向IMS core发送分工确认响应信息与资源端点的信息。
示例地，AS网元接收到的申请结果表示MRF网元将对MRF网元负责渲染的待渲染XR对象进行渲染，即AS网元向MRF网元申请渲染资源成功，进一步地，AS网元接受渲染分工，向IMS core发送分工确认响应信息与资源端点的信息。
1229，IMS core向UE#1发送分工确认响应信息。
步骤1226-步骤1229与步骤1214-步骤1217类似，此处不再赘述。
场景3：UE#1发起XR通话更新。
1231，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。在XR通话过程中XR通话的处理需求更新的情况下，UE#1重新确定渲染分工，除此之外，与步骤1211类似，不再赘述。
1232，UE#1向IMS core发送REINVITE消息，REINVITE消息包括分工确认请求信息，用以请求AS接受更新后的渲染分工。
1233，IMS core向AS发送REINVITE消息，REINVITE消息包括分工确认请求信息，用以请求AS接受更新后的渲染分工。
步骤1232-步骤1233中的分工确认请求信息包括更新后的XR通话的第二处理需求信息，更新后的XR通话的第二处理需求信息的具体内容可参见步骤1112中相关描述，不再赘述。
1234，AS向MRF网元申请更新渲染资源。
AS网元根据分工确认请求信息，确定需要MRF网元侧更新渲染时，可向MRF网元申请更新资源。一种可能的实现方式，AS网元向MRF网元发送REINVITE消息，该REINVITE消息用于申请修改资源。可以理解的是，本步骤中MRF网元可以重新创建端点资源，也可以重用步骤1214中创建或分配的端点资源；MRF网元可以重用步骤1214中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1214预留或分配的算力资源。
1235，MRF网元向AS发送申请结果。
一种可能的实现方式，MRF网元向AS网元返回资源申请结果，包括以下至少一项：结果指示信息、资源端点的信息。其中，结果指示信息可用于通知AS网元，MRF网元是否将对MRF网元负责渲染的待渲染XR对象进行渲染。若MRF网元重新创建了端点资源，则资源端点的信息包括重新创建的资源端点的信息。
1236，AS向IMS core发送分工确认响应信息。
示例地，AS网元接收到的申请结果表示MRF网元将对MRF网元负责渲染的待渲染XR对象进行渲染，即AS网元向MRF网元申请渲染资源成功，进一步地，AS网元接受渲染分工，向IMS core发送分工确认响应信息。可选地，若MRF网元重新创建了端点资源，AS还需要向IMS core发送新的资源端点的信息。
1237，IMS core向UE#1发送分工确认响应信息。
场景4：UE#1接收XR通话更新。
1241，AS向IMS core发送REINVITE消息。
1242，IMS core向UE#1发送REINVITE消息。
1243，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
XR通话的处理需求更新的情况下，导致渲染任务需要重新分工，则UE#1需要重新确定渲染分工，除此之外，与1211类似，不再赘述。
1244，UE#1向IMS core发送200 For REINVITE消息，200 For REINVITE消息包括分工确认请求信息，用以请求AS接受更新后的渲染分工。
1245，IMS core向AS发送200 For REINVITE消息，200 For REINVITE消息包括分工确认请求信息，用以请求AS接受更新后的渲染分工。
步骤1244-步骤1245与步骤1224-步骤1225类似，不再赘述。
1246，AS向MRF网元申请更新渲染资源。
AS网元根据分工确认请求信息，确定需要MRF网元侧更新渲染时，可向MRF网元申请更新资源。一种可能的实现方式，AS网元向MRF网元发送REINVITE消息，该REINVITE消息用于申请修改资源。具体的可以参考步骤1214中的描述，此处不再赘述。可以理解的是，本步骤中MRF网元可以重新创建端点资源，也可以重用步骤1226中创建或分配的端点资源；MRF网元可以重用步骤1226中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1226预留或分配的算力资源。
1247，MRF网元向AS发送申请结果。
一种可能的实现方式，MRF网元向AS网元返回资源申请结果，包括以下至少一项：结果指示信 息、资源端点的信息。其中，结果指示信息可用于通知AS网元，MRF网元是否将对MRF网元负责渲染的待渲染XR对象进行渲染。若MRF网元重新创建了端点资源，则资源端点的信息包括重新创建的端点资源的信息。
1248，AS向IMS core发送分工确认响应信息。
示例地，AS网元接收到的申请结果表示MRF网元将对MRF网元负责渲染的待渲染XR对象进行渲染，即AS网元向MRF网元申请渲染资源成功，进一步地，AS网元接受渲染分工，向IMS core发送分工确认响应信息。可选地，若MRF网元重新创建了端点资源，AS还需要向IMS core发送新的资源端点的信息。
1249，IMS core向UE#1发送分工确认响应信息。
上面结合四种场景进行了示例性说明，不管在上述哪种场景下，在UE1接收到分工确认响应信息后，可以包括如下步骤。
1251，UE#1向MRF网元发送MRF网元负责渲染的待渲染XR对象。
一种可能的实现方式，UE#1基于XR通话的待渲染XR对象的渲染分工向MRF网元发送MRF网元负责渲染的待渲染XR对象。
示例地，UE#1基于XR通话的待渲染XR对象的渲染分工，通过第三连接向IMS-AGW发送MRF网元负责渲染的待渲染XR对象，IMS-AGW基于第三连接与第四连接的对应关系，通过第四连接将由MRF网元负责渲染的待渲染XR对象转发给MRF网元。
1252，MRF网元渲染MRF网元负责渲染的待渲染XR对象。
1253，UE#1渲染UE#1负责渲染的待渲染XR对象。
1254，UE#1向MRF网元发送渲染后的XR对象对应的媒体数据。
1255，MRF网元对UE#1渲染后的XR对象对应的媒体数据以及MRF网元渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
1256，MRF网元向UE#2发送合并后的媒体数据。
步骤1251-步骤1256与步骤722-步骤727类似，此处不再赘述。
基于上述技术方案，AS可以将MRF网元的处理能力和服务指示信息通知给终端设备。终端设备在确定XR对象渲染算力要求超出终端设备的渲染可用算力，并且确定MRF网元支持XR对象渲染的情况下确定渲染分工，可在呼叫请求中携带分工确认请求信息，请求进行渲染协商。AS可根据分工确认请求信息确定MRF网元将协助终端设备完成XR对象的渲染并告知终端设备，AS向MRF网元申请媒体渲染资源。终端设备基于渲染协商结果，可向MRF网元发送MRF网元待渲染的数据。最后，MRF网元或者其他设备可对MRF网元渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的UE#2。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由终端设备或AS发起会话更新请求，根据更新后的XR通话的处理需求重新进行渲染协商。
可以理解，图12所示方案中，以MRF网元对UE#1渲染后的XR对象对应的媒体数据以及MRF网元渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，MRF网元向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如也可以是其他设备进行合并处理，不再赘述。
图13是本申请实施例提供的一种XR对象渲染的方法1300的示意性流程图。该方法1300可以用于实现上述方法900的方案。该方法1300可用于基于HTTP/HTTPS消息完成渲染协商的场景，渲染协商例如可在呼叫建立过程中完成。在该方法1300中，假设第一网络设备和第二网络设备为OTT服务器。作为示例，图13所示的方法1300可用于图3架构。该方法1300可以包括如下步骤。
可选地，1301之前，UE#1向OTT服务器发送HTTP请求消息进行注册。
1301，OTT服务器向UE#1发送服务指示信息。
OTT服务器确定服务指示信息的方法与步骤1001中网络设备确定服务指示信息的方法类似，不再赘述。
一种可能的实现方式，OTT服务器向UE#1发送HTTP响应消息，该HTTP响应消息包括服务指 示信息。
1302，OTT服务器向UE#1发送OTT服务器的处理能力。
一种可能的实现方式，OTT服务器向UE#1发送HTTP响应消息，该HTTP响应消息包括OTT服务器的处理能力。
可以理解，服务指示信息和OTT服务器的处理能力可以在一个消息中发送，也可以在两个消息中发送，本申请对此不做限制。如果在两个消息中发送，本申请对步骤1301和1302的先后顺序不做限定。
1303，UE#1确定OTT服务器能够渲染XR对象。
示例地，UE#1保存网络设备的处理能力和/或服务指示信息，基于服务指示信息可获知OTT服务器是否能够渲染XR对象，也即是否支持XR对象渲染。基于OTT服务器的处理能力可以获知OTT服务器是否有足够能力协助UE#1完成XR对象的渲染。步骤1301-步骤1303为可选步骤，也即OTT服务器可以不用向UE#1提供服务指示信息，UE#1可默认UE#1签约了网络渲染功能。或者OTT服务器可以不用向UE#1提供OTT服务器的处理能力，UE#1可默认OTT服务器有足够能力协助UE#1完成XR对象的渲染。
下面结合四种场景介绍渲染协商过程。
场景1：UE#1发起渲染协商。
1311，UE#1确定XR通话的待渲染XR对象的渲染分工，即XR通话中的一部分待渲染XR对象归OTT服务器渲染，另一部分待渲染XR对象归UE#1渲染。
UE#1基于XR通话的第一处理需求信息确定通过UE#1的处理能力不能完成XR通话中XR对象的渲染，因此UE#1确定本次XR通话需要进行拆分渲染。
一种可能的情形，UE#1默认签约了网络渲染功能，并且默认OTT服务器可以协助完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
另一种可能的情形，UE#1基于1301中的服务指示信息确定签约了网络渲染功能，即OTT服务器支持XR对象渲染，默认OTT服务器有足够能力协助UE#1完成XR对象的渲染，继而确定XR通话的待渲染XR对象的渲染分工。若UE#1确定OTT服务器不支持XR对象渲染，作为示例，UE#1可以自己进行渲染处理。本申请实施例主要介绍OTT服务器支持XR对象渲染的情况。
又一种可能的情形，UE#1默认签约了网络渲染功能，并且UE#1基于1302中的OTT服务器的处理能力确定OTT服务器有足够能力协助UE#1完成XR对象的渲染，继而UE#1确定XR通话的待渲染XR对象的渲染分工。
还一种可能的情形，UE#1基于1301中的服务指示信息确定OTT服务器支持XR对象渲染，并且基于1302中的OTT服务器的处理能力确定OTT服务器有足够能力协助UE#1完成XR对象的渲染(即OTT服务器完成待渲染XR对象的渲染所需要的可用算力没有超出OTT服务器的处理能力)继而确定XR通话的待渲染XR对象的渲染分工，即确定UE#1和OTT服务器各自需要渲染的XR对象。
1312，UE#1向OTT服务器发送HTTP请求消息，HTTP请求消息包括分工确认请求信息，分工确认请求信息用于请求OTT服务器接受渲染分工。
分工确认请求信息包括XR通话的第二处理需求信息，可选地，XR通话的第二处理需求信息包括参数C1、参数C2、参数D、参数E。具体与步骤1112中的分工确认请求信息类似，不再赘述。
作为一示例，XR通话的第二处理需求信息的格式可以为json格式，如下：
Content-Type:application/json
{
“XR-Session-Attribute”:{
“network_rendering_content”:“0,1,2,3”,//表示XR通话中需要OTT服务器渲染的待渲染XR对象
“rendering_type”:”0/1”,//表示XR通话中的部分/全部待渲染XR对象需要OTT服务器渲染
“video_resolution”:“1920,1080”,//表示XR通话的视频分辨率
“video_frame_rate”:“30”}//表示XR通话的视频帧率
}
作为另一示例，XR通话的第二处理需求信息的格式可以为XML格式，如下：
Content-Type:application/xml
<XR-Session-Attribute>
<network_rendering_content Value＝“0,1,2,3”/><！--表示XR通话中需要OTT服务器渲染的待渲染XR对象-->
<rendering_type Value＝“0/1”/><！--XR通话中的部分/全部待渲染XR对象需要OTT服务器渲染-->
<video_resolution Value＝“1920,1080”/><！--表示XR通话的视频分辨率-->
<video_frame_rate Value＝“30”/><！--表示XR通话的视频帧率-->
</XR-Session-Attribute>
在上述任一示例中，“network_rendering_content”表示参数C1，即需要OTT服务器渲染的待渲染的XR对象。“rendering_type”表示参数C2，即需要XR-M网元渲染部分待渲染的XR对象还是需要XR-M网元渲染全部待渲染的XR对象。“video_resolution”表示参数D，即视频分辨率。“video_frame_rate”表示参数E，即视频帧率。
1313，OTT服务器接受渲染分工，分配渲染资源。
OTT服务器基于分工确认请求信息分配渲染资源的方法与步骤1013类似，不再赘述。
1314，OTT服务器向UE#1发送分工确认响应信息，分工确认响应信息指示OTT服务器接受渲染分工。
场景2：UE#1接收渲染协商。
1321，OTT服务器向UE#1发送HTTP请求消息。
1322，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工，与步骤1311类似，不再赘述。
1323，UE#1向OTT服务器发送HTTP响应消息，HTTP响应消息包括分工确认请求信息。
步骤1323与1312类似，不再赘述。
1324，OTT服务器接受渲染分工，分配渲染资源。
OTT服务器基于分工确认分配渲染资源的方法与步骤1013类似，不再赘述。
1325，OTT服务器向UE#1发送分工确认响应信息。
场景3：UE#1发起媒体渲染重协商。
1331，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
UE#1根据更新后的XR通话的处理需求、UE#1的处理能力和OTT服务器的处理能力(可选)，确定UE#1的XR通话的待渲染XR对象的渲染分工。与步骤1311类似，不再赘述。
1332，UE#1向OTT服务器发送会话更新呼叫请求，会话更新呼叫请求包括分工确认请求信息，分工确认请求信息用于请求OTT服务器接受更新后的渲染分工。
一种可能的实现方式，UE#1向OTT服务器发送HTTP消息，该HTTP消息包括会话更新呼叫请求，或者该HTTP消息用于请求会话更新呼叫。
步骤1332与步骤1312类似，不再赘述。
1333，OTT服务器接受更新后的渲染分工，更新渲染资源。
示例地，OTT服务器根据会话更新呼叫请求中包括的分工确认请求信息，重新确定需要OTT服务器侧渲染的待渲染XR对象，根据需要OTT服务器侧渲染的待渲染XR对象更新渲染资源。可以理解的是本步骤中OTT服务器可以重用步骤1313中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1313中预留或分配的算力资源。
1334，OTT服务器向UE#1发送分工确认响应信息，分工确认响应信息指示OTT服务器接受更新后的渲染分工。
场景4：UE#1接收媒体渲染重协商。
1341，OTT服务器向UE#1发送会话更新呼叫请求。
1342，UE#1确定UE#1的XR通话的待渲染XR对象的渲染分工。
在本申请实施例中，假设XR通话的处理需求发生变化，导致渲染任务需要重新分工，UE#1根据更新后的XR通话的处理需求、UE#1的处理能力和OTT服务器的处理能力(可选)，重新确定XR通话的待渲染XR对象的渲染分工。与步骤1311类似，不再赘述。
1343，UE#1向OTT服务器发送会话更新呼叫响应，会话更新呼叫响应包括分工确认请求信息， 分工确认请求信息用于请求OTT服务器接受更新后的渲染分工。
步骤1343与步骤1312类似，不再赘述。
1344，OTT服务器接受更新后的渲染分工，更新渲染资源。
示例地，OTT服务器根据会话更新呼叫响应中包括的分工确认请求信息，重新确定需要OTT服务器侧渲染的待渲染XR对象，根据需要OTT服务器侧渲染的待渲染XR对象更新渲染资源。可以理解的是本步骤中OTT服务器可以重用步骤1324中预留或分配的算力资源，也可以重新分配算力资源，重新分配的算力资源可以不同于步骤1324中预留或分配的算力资源。
1345，OTT服务器向UE#1发送分工确认响应信息，分工确认响应信息指示OTT服务器接受更新后的渲染分工。
上面结合四种场景进行了示例性说明，不管在上述哪种场景下，在UE#1接收到分工确认响应信息后，可以包括如下步骤。
1351，UE#1向OTT服务器发送OTT服务器负责渲染的待渲染XR对象。
示例地，UE#1基于XR通话的待渲染XR对象的渲染分工向OTT服务器发送OTT服务器负责渲染的待渲染XR对象。
1352，OTT服务器渲染OTT服务器负责渲染的待渲染XR对象。
1353，UE#1渲染UE#1负责渲染的待渲染XR对象。
1354，UE#1向OTT服务器发送渲染后的XR对象对应的媒体数据。
UE#1完成渲染后，将渲染完成后的XR对象对应的媒体数据发给OTT服务器。
1355，OTT服务器对UE#1渲染后的XR对象对应的媒体数据以及OTT服务器渲染后的XR对象对应的媒体数据进行合并处理，得到合并后的媒体数据。
1356，OTT服务器向UE#2发送合并后的媒体数据。
步骤1351-步骤1356与步骤522-步骤527类似，此处不再赘述。
可以理解，上述方法1300主要以OTT服务器为例进行了示例性说明，如前所述，OTT服务器可包括信令服务器(或者称为OTT信令服务器)、媒体处理服务器(或者称为OTT媒体服务器，或者OTT媒体处理服务器)、路由服务器，不同的服务器可执行不同功能。作为示例，第一网络设备为信令服务器，第二网络设备为媒体处理服务器，具体的可参考方法1100或1200的描述，此处不再赘述。
基于上述技术方案，终端设备注册到OTT服务器时，OTT服务器可以将OTT服务器的处理能力和服务指示信息通知给终端设备。终端设备在确定XR对象渲染算力要求超出终端设备的渲染可用算力，并且确定OTT服务器支持XR对象渲染的情况下确定渲染分工，可在呼叫请求中携带分工确认请求信息，请求进行渲染协商。OTT服务器可根据分工确认请求信息确定OTT服务器将协助终端设备完成XR对象的渲染并告知终端设备，OTT服务器预留媒体渲染资源。终端设备基于渲染协商结果，可向OTT服务器发送OTT服务器待渲染的数据。最后，OTT服务器或其他设备可对OTT服务器渲染后的XR对象对应的媒体数据和终端设备渲染后的XR对象对应的媒体数据进行合并，并将合并后的媒体数据发给本次会话所涉及的UE#2。此外，如果在会话过程中由于一些情况，比如XR通话的处理需求发生变化，导致媒体渲染任务可能需要重新分工，则可由终端设备或OTT服务器发起会话更新请求，根据更新后的XR通话的处理需求重新进行渲染协商。
可以理解，图13所示方案中，以OTT服务器对UE#1渲染后的XR对象对应的媒体数据以及OTT服务器渲染后的XR对象对应的媒体数据进行合并处理为例进行示例性说明，对此不予限制。例如也可以是UE#2进行合并处理。如UE#1向UE#2发送渲染后的XR对象对应的媒体数据，OTT服务器向UE#2发送渲染后的XR对象对应的媒体数据。UE#2进行合并处理。再例如也可以是其他设备进行合并处理，不再赘述。
可以理解，本申请实施例中的图5至图8/图10至图13中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图5至图8/图10至图13的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
还可以理解，上述图5至图8/图10至图13中各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑 确定，而不应对本申请实施例的实施过程构成任何限定。例如，在上述图5至图8所示的流程中，网络设备渲染待渲染XR对象和终端设备渲染待渲染XR对象之间的顺序不限定。以步骤523和步骤524为例，步骤523和步骤524可以同时进行；或者也可以先执行步骤523，再执行步骤524；或者也可以先执行步骤524，再执行步骤523。
还可以理解，在上述一些实施例中，主要以现有的网络架构中的网元为例进行了示例性说明，应理解，对于网元的具体形式本申请实施例不作限定。例如，在未来可以实现同样功能的网元都适用于本申请实施例。
还可以理解，在上述一些实施例中，多次提到XR通话，XR通话例如可以为AR通话(AR communication)。
还可以理解，在上述一些实施例中，渲染后XR对象和渲染后的XR对象有时交替使用，其表示相同的含义。类似地，待渲染XR对象和待渲染的XR对象有时交替使用，其表示相同的含义。
还可以理解，在上述一些实施例中，多次提及发送XR通话的处理需求，其可以包括发送XR通话的处理需求的信息(也即直接发送XR通话的处理需求的信息)，也可以包括发送用于确定XR通话的处理需求的信息(也即发送一些信息，该信息可用于确定XR通话的处理需求)。
还可以理解，在上述一些实施例中，发送媒体数据，也可以替换为发送视频流。
还可以理解，在上述一些实施例中，发送处理能力和发送处理能力信息有时交替使用，其均表示发送处理能力的信息。发送处理能力信息(或者发送处理能力)，其可以包括发送处理能力信息(也即直接发送处理能力信息)，也可以包括发送用于确定处理能力的信息(也即发送一些信息，该信息可用于确定处理能力信息)。
还可以理解，在本申请的各实施例中涉及到一些消息名称，其命名不对本申请实施例的保护范围造成限定。例如，REINVITE消息和200 For REINVITE消息均为示例性说明，200 For REINVITE消息可理解为REINVITE消息的响应消息。再例如，HTTP请求消息和HTTP响应消息是为区分做的命名，其均属于HTTP消息。可以理解，以A向B发送消息为例，只要可以用于A和B之间的消息都适用于本申请实施例。
还可以理解，在上述一些实施例中，多次提及发送消息。以A向B发送消息为例，A向B发送消息，可以包括A直接向B发送消息，也可以包括A通过其他设备或网元向B发送消息，对此不予限制。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，上述各个方法实施例中，由设备实现的方法和操作，也可以由可由设备的组成部件(例如芯片或者电路)来实现，不作限定。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例。
图14是本申请实施例提供的一种通信装置1400的示意图。该装置1400包括收发单元1410和处理单元1420。收发单元1410可以用于实现相应的通信功能。收发单元1410还可以称为通信接口或通信单元。处理单元1420可以用于进行处理操作，如确定渲染方式等。
可选地，该装置1400还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1420可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中网络设备或终端设备的动作。
在第一种设计中，该装置1400可以是前述实施例中的终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)，也可以是终端设备的组成部件(如芯片)。该装置1400可实现对应于上文方法实施例中的终端设备执行的步骤或者流程。其中，收发单元1410可用于执行上文方法实施例中终端设备的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1410可用于执行步骤410中接收来自第一网络设备的分工指示信息的操作、步骤420中向第二网络设备发送第二部分待渲染XR对象的操作，还可以用于执行图5至图8中UE的发送和/或接收数据或消息的操作。处理单元1420可用于执行上文方法实施例中终端设备的处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)。例如，处理单元1420可用于执行图4中的步骤420中渲染XR 通话中归终端设备渲染的待渲染XR对象的操作。再例如，处理单元1420可用于执行图5至图8中UE的处理操作。例如，处理单元1420可用于执行图9中的步骤910中确定渲染分工的操作、步骤920中渲染XR通话中归终端设备渲染的待渲染XR对象的操作。再例如，处理单元1420可用于执行图10至图13中UE的处理操作。收发单元1410可用于执行步骤920中向第二网络设备发送归第二网络设备渲染的待渲染对象的操作，还可以用于执行图10至图13中UE的发送和/或接收数据或消息的操作。
一种可能的实现方式，处理单元1420，用于确定或接受渲染分工，渲染分工是指：终端设备的XR通话中的一部分待渲染XR对象归第二网络设备渲染，另一部分待渲染XR对象归终端设备渲染；处理单元1420，还用于渲染XR通话中归终端设备渲染的待渲染XR对象得到渲染后XR对象；收发单元1410，用于向第二网络设备发送XR通话中归第二网络设备渲染的待渲染XR对象。
可选地，收发单元1410，用于接收来自第一网络设备的分工指示信息，分工指示信息指示终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染。
可选地，收发单元1410，还用于向第一网络设备发送终端设备的处理能力信息。
可选地，收发单元1410，具体用于向第三网络设备发送注册消息或会话呼叫消息以触发第三网络设备向第一网络设备发送终端设备的处理能力信息，注册消息或会话呼叫消息包含终端设备的处理能力信息。
可选地，终端设备的处理能力信息包括终端设备的渲染可用算力，或者，终端设备的处理能力信息包括终端设备的渲染可用算力和终端设备支持的渲染分工方式。
可选地，终端设备支持的渲染分工方式包括以下至少一项：按层分工、按类型分工。
可选地，终端设备的渲染可用算力是终端设备基于自身计算资源的配置确定的，或者，终端设备的渲染可用算力是终端设备基于终端设备的剩余计算资源或可用计算资源确定的。
可选地，收发单元1410，还用于向第一网络设备发送XR通话的处理需求信息。
可选地，XR通话的处理需求信息包括以下至少一项：XR通话的待渲染XR对象的信息、XR通话的视频分辨率、XR通话的视频帧率。
可选地，处理单元1420用于根据以下至少一项确定渲染分工：终端设备的处理能力信息、第二网络设备的处理能力信息、XR通话的处理需求信息。
可选地，收发单元1410，还用于接收来自第一网络设备的第二网络设备的处理能力信息。
可选地，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力；或者，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力和第二网络设备支持的渲染分工方式。
可选地，第二网络设备的渲染可用算力是基于第二网络设备的计算资源的配置确定的，或者，第二网络设备的渲染可用算力是基于第二网络设备的剩余计算资源或可用计算资源确定的。
可选地，渲染分工方式包括以下至少一项：按层分工、按类型分工。
可选地，收发单元1410，还用于向第三网络设备发送分工确认请求信息，分工确认请求信息用于请求接受渲染分工，分工确认请求信息包括用于确定XR通话的待渲染XR对象中归第二网络设备渲染的待渲染XR对象的信息。
可选地，收发单元1410，还用于接收来自第一网络设备的分工确认响应信息，分工确认响应信息指示渲染分工被接受。可选地，收发单元1410，还用于获取网络侧服务指示信息，网络侧服务指示信息用于指示第二网络设备能够提供对XR对象进行渲染的服务(即渲染XR通话中的待渲染XR对象的能力)。
可选地，收发单元1410，还用于向第二网络设备发送渲染后XR对象。
可选地，分工指示信息包括XR通话中归终端设备渲染的待渲染XR对象，处理单元1420，还用于根据XR通话中的待渲染XR对象和XR通话中归终端设备渲染的待渲染XR对象，确定XR通话中归第二网络设备渲染的待渲染XR对象。
可选地，分工指示信息包括XR通话中归第二网络设备渲染的待渲染XR对象，处理单元1420，还用于根据XR通话中的待渲染XR对象和XR通话中归第二网络设备渲染的待渲染XR对象，确定XR通话中归终端设备渲染的待渲染XR对象。
可选地，第一网络设备为XR控制面网元，第二网络设备为XR媒体面网元；或者，第一网络设备 为应用服务器，第二网络设备为媒体资源功能网元(如MRF网元)；或者，第一网络设备为互联网业务信令服务器，第二网络设备为互联网业务媒体服务器。
在第二种设计中，该装置1400可以是前述实施例中的第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)，也可以是第一网络设备的组成部件(如芯片)。该装置1400可实现对应于上文方法实施例中的第一网络设备执行的步骤或者流程。其中，收发单元1410可用于执行上文方法实施例中第一网络设备的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1410可用于执行步骤410中向终端设备发送分工指示信息的操作，还可以用于执行图5/10中的网络设备发送和/或接收数据或消息的操作，还可以用于执行图6/11中的XR-C网元发送和/或接收数据或消息的操作，还可以用于执行图7/12中的AS发送和/或接收数据或消息的操作，还可以用于执行图8/13中的OTT服务器发送和/或接收数据或消息的操作。处理单元1420可用于执行上文方法实施例中第一网络设备的数据和/或信息处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1420可用于执行图4涉及的内容中的第一网络设备的数据和/或信息处理相关的操作，还可以用于执行图5/10中的网络设备的数据和/或信息处理相关的操作，还可以用于执行图6/11中的XR-C网元的数据和/或信息处理相关的操作，还可以用于执行图7/12中的AS的数据和/或信息处理相关的操作，还可以用于执行图8/13中的OTT服务器的数据和/或信息处理相关的操作。
一种可能的实现方式，处理单元1420，用于确定或接受渲染分工，渲染分工是指终端设备的XR通话中的一部分待渲染对象归网络侧渲染设备渲染，另一部分待渲染XR对象归终端设备渲染；收发单元1410，用于触发XR通话中归终端设备渲染的XR对象被终端设备渲染，以及XR通话中归第二网络设备渲染的待渲染XR对象被第二网络设备渲染。
可选地，收发单元1410，用于向终端设备发送分工指示信息，分工指示信息指示：终端设备的XR通话中的一部分待渲染XR对象归第二网络设备渲染，和/或，终端设备的XR通话中的另一部分待渲染XR对象归终端设备渲染。
可选地，处理单元1420，用于响应于确定终端设备的处理能力无法满足XR通话的处理需求，确定终端设备和第二网络设备分别渲染XR通话中的部分待渲染XR对象。
可选地，处理单元1420，具体用于根据以下至少一项确定渲染分工：终端设备的处理能力信息、第二网络设备的处理能力信息、XR通话的处理需求信息。
可选地，收发单元1410，还用于接收来自终端设备的XR通话的处理需求信息。
可选地，XR通话的处理需求信息包括以下至少一项：XR通话的待渲染XR对象的信息、XR通话的视频分辨率、XR通话的视频帧率。
可选地，收发单元1410，还用于接收来自终端设备的终端设备的处理能力信息。
可选地，终端设备的处理能力信息包括终端设备的渲染可用算力，或者，终端设备的处理能力信息包括终端设备的渲染可用算力和终端设备支持的渲染分工方式。
可选地，终端设备的渲染可用算力是基于终端设备自身计算资源的配置确定的，或者，终端设备的渲染可用算力是基于终端设备的剩余计算资源或可用计算资源确定的。
可选地，收发单元1410，还用于接收来自第二网络设备的第二网络设备的处理能力信息。
可选地，收发单元1410，还用于接收来自终端设备的分工确认请求信息，分工确认请求信息用于请求接受渲染分工，分工确认请求信息包括用于确定XR通话的待渲染XR对象中归第二网络设备渲染的待渲染XR对象的信息；处理单元1420，具体用于根据分工确认请求信息接受渲染分工。
可选地，收发单元1410，还用于向终端设备发送分工确认响应信息，分工确认响应信息指示渲染分工被接受。
可选地，收发单元1410，还用于向终端设备发送第二网络设备的处理能力信息。
可选地，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，或者，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力和第二网络设备支持的渲染分工方式。
可选地，第二网络设备的渲染可用算力是基于第二网络设备的计算资源的配置确定的，或者，第二网络设备的渲染可用算力是基于第二网络设备的剩余计算资源或可用计算资源确定的。
可选地，渲染分工方式包括以下至少一项：按层分工、按类型分工。
可选地，收发单元1410，还用于向终端设备发送网络侧服务指示信息，网络侧服务指示信息用于指示第二网络设备能够提供对XR对象进行渲染的服务。
可选地，收发单元1410，还用于向第二网络设备发送请求消息，请求消息用于请求以下至少一项：第二网络设备的地址信息、第二网络设备的渲染资源信息；其中，第二网络设备的地址信息用于使与XR通话相关的终端设备通过网络侧接入设备连接到第二网络设备，渲染资源信息为第二网络设备用来渲染归所述第二网络设备渲染的待渲染XR对象的资源的信息；接收来自第二网络设备的请求消息的响应。
可选地，请求消息中包括第二网络设备待渲染的XR对象所需的算力。
可选地，第一网络设备为XR控制面网元，第二网络设备为XR媒体面网元；或者，第一网络设备为应用服务器，第二网络设备为媒体资源功能网元；或者，第一网络设备为互联网业务信令服务器，第二网络设备为互联网业务媒体服务器。
另一种可能的实现方式，收发单元1410，用于向第二网络设备发送请求消息，请求消息用于请求第二网络设备渲染终端设备的XR通话中归第二网络设备渲染的待渲染XR对象，请求消息包括归第二网络设备渲染的待渲染XR对象所需的算力；收发单元1410，还用于接收来自第二网络设备的请求消息的响应，请求消息的响应用于通知第一网络设备：第二网络设备是否将渲染XR通话中归第二网络设备渲染的待渲染XR对象。
可选地，收发单元1410，还用于接收来自第二网络设备的第二网络设备的处理能力信息。
可选地，处理单元1420，用于根据第二网络设备的处理能力信息，确定XR通话中归第二网络设备渲染的待渲染XR对象。
可选地，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，或者，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力和第二网络设备支持的渲染分工方式。
可选地，第二网络设备的渲染可用算力是基于第二网络设备的计算资源的配置确定的，或者，第二网络设备的渲染可用算力是基于第二网络设备的剩余计算资源或可用计算资源确定的。
可选地，第一网络设备为XR控制面网元，第二网络设备为XR媒体面网元；或者，第一网络设备为应用服务器，第二网络设备为媒体资源功能网元；或者，第一网络设备为互联网业务信令服务器，第二网络设备为互联网业务媒体服务器。
在第三种设计中，该装置1400可以是前述实施例中的第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)，也可以是第二网络设备的组成部件(如芯片)。该装置1400可实现对应于上文方法实施例中的第二网络设备执行的步骤或者流程。其中，收发单元1410可用于执行上文方法实施例中第二网络设备的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1410可用于执行图4中的步骤420或图9中的步骤920中接收第二部分待渲染XR对象的操作，还可以用于执行图5/10中的网络设备发送和/或接收数据或消息的操作，还可以用于执行图6/11中的XR-M网元发送和/或接收数据或消息的操作，还可以用于执行图7/12中的MRF网元发送和/或接收数据或消息的操作，还可以用于执行图8/13中的OTT服务器发送和/或接收数据或消息的操作。处理单元1420可用于执行上文方法实施例中第二网络设备的数据和/或信息处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1420可用于执行图4/9中的第二网络设备或网络侧渲染设备的数据和/或信息处理相关的操作，还可以用于执行图5/10中的网络设备的数据和/或信息处理相关的操作，还可以用于执行图6/11中的XR-M网元的数据和/或信息处理相关的操作，还可以用于执行图7/12中的MRF网元的数据和/或信息处理相关的操作，还可以用于执行图8/13中的OTT服务器的数据和/或信息处理相关的操作。
一种可能的实现方式，收发单元1410，用于接收来自第一网络设备的请求消息，请求消息用于请求第二网络设备渲染终端设备的XR通话中归第二网络设备渲染的待渲染XR对象，请求消息包括终端设备的XR通话中归第二网络设备渲染的待渲染XR对象所需的算力；收发单元1410，还用于向第一网络设备发送请求消息的响应，请求消息的响应用于通知第一网络设备：第二网络设备是否将渲染XR通话中归第二网络设备渲染的待渲染XR对象。
可选地，处理单元1420，用于根据第二网络设备待渲染的XR对象所需的算力，确定第二网络设 备渲染XR通话中归第二网络设备渲染的待渲染XR对象所需的资源。
可选地，收发单元1410，还用于向第一网络设备发送第二网络设备的处理能力信息。
可选地，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力，或者，第二网络设备的处理能力信息包括第二网络设备的渲染可用算力和第二网络设备支持的渲染分工方式。
可选地，第二网络设备的渲染可用算力是基于第二网络设备的计算资源的配置确定的，或者，第二网络设备的渲染可用算力是基于第二网络设备的剩余计算资源或可用计算资源确定的。
可选地，第一网络设备为XR控制面网元，第二网络设备为XR媒体面网元；或者，第一网络设备为应用服务器，第二网络设备为媒体资源功能元；或者，第一网络设备为互联网业务信令服务器，第二网络设备为互联网业务媒体服务器。
可以理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
还可以理解，这里的装置1400以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置1400可以具体为上述实施例中的终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)，可以用于执行上述各方法实施例中与终端设备对应的各个流程和/或步骤，例如，图4中的步骤410-420，图5至图8中UE执行的步骤，图9中的步骤910-920，图10至图13中UE执行的步骤。或者，装置1400可以具体为上述实施例中的第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)，可以用于执行上述各方法实施例中与第一网络设备对应的各个流程和/或步骤，例如，步骤410，图5/10中网络设备执行的步骤，图6/11中XR-C网元执行的步骤，图7/12中AS执行的步骤，图8/13中OTT服务器执行的步骤。或者，装置1400可以具体为上述实施例中的第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)，可以用于执行上述各方法实施例中与第二网络设备对应的各个流程和/或步骤，例如，图4中的步骤420，图9中的步骤920,图5/10中网络设备执行的步骤，图6/11中XR-M网元执行的步骤，图7/12中MRF网元执行的步骤，图8/13中OTT服务器执行的步骤。为避免重复，在此不再赘述。
上述各个方案的装置1400具有实现上述方法中终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)所执行的相应步骤的功能；或者，上述各个方案的装置1400具有实现上述方法中第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)所执行的相应步骤的功能；或者，上述各个方案的装置1400具有实现上述方法中第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元1410还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
可以理解的是，图14中的装置可以是前述实施例中的设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图15是本申请实施例提供另一种通信装置1500的示意图。该装置1500包括处理器1510，处理器1510用于执行存储器1520存储的计算机程序或指令，或读取存储器1520存储的数据，以执行上文各方法实施例中的方法。可选地，处理器1510为一个或多个。
可选地，如图15所示，该装置1500还包括存储器1520，存储器1520用于存储计算机程序或指令和/或数据。该存储器1520可以与处理器1510集成在一起，或者也可以分离设置。可选地，存储器1520 为一个或多个。
可选地，如图15所示，该装置1500还包括收发器1530，收发器1530用于信号的接收和/或发送。例如，处理器1510用于控制收发器1530进行信号的接收和/或发送。
作为一种方案，该装置1500用于实现上文各个方法实施例中由终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)执行的操作。
作为另一种方案，该装置1500用于实现上文各个方法实施例中由第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)执行的操作。
作为另一种方案，该装置1500用于实现上文各个方法实施例中由第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)执行的操作。
可以理解，本申请实施例中提及的处理器可以是中央处理单元(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)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)执行的方法的计算机指令。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)执行的方法的计算机指令。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)执行的方法的计算机指令。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)执行的方法。
本申请实施例还提供一种通信系统，包括前述的终端设备(如图4/9中的终端设备，图5至图8/图10至图13中的UE)、第一网络设备(如图4涉及的内容中的第一网络设备，图5/10中的网络设 备，图6/11中的XR-C网元，图7/12中的AS，图8/13中的OTT服务器)、第二网络设备(如图4/9中的第二网络设备或网络侧渲染设备，图5/10中的网络设备，图6/11中的XR-M网元，图7/12中的MRF网元，图8/13中的OTT服务器)中的至少一项。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (79)

  1. 一种扩展现实XR对象渲染的方法，其特征在于，包括：
    终端设备确定或接受渲染分工，所述渲染分工是指所述终端设备的XR通话中的一部分待渲染XR对象归网络侧渲染设备渲染，另一部分待渲染XR对象归所述终端设备渲染；
    所述终端设备渲染所述XR通话中归所述终端设备渲染的待渲染XR对象，并向所述网络侧渲染设备发送所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备接受渲染分工，包括：
    所述终端设备接收来自网络侧控制设备的分工指示信息，所述分工指示信息指示所述终端设备的XR通话中的一部分待渲染XR对象归所述网络侧渲染设备渲染，和/或，所述终端设备的XR通话中的另一部分待渲染XR对象归所述终端设备渲染。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧控制设备发送所述终端设备的处理能力信息，所述终端设备的处理能力信息用于确定所述分工指示信息。
  4. 根据权利要求3所述的方法，其特征在于，所述终端设备向所述网络侧控制设备发送所述终端设备的处理能力信息，包括：
    所述终端设备向网络侧接入设备发送注册消息或会话呼叫消息以触发所述网络侧接入设备向所述网络侧控制设备发送所述终端设备的处理能力信息，所述注册消息或所述会话呼叫消息包含所述终端设备的处理能力信息。
  5. 根据权利要求2至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧控制设备发送所述XR通话的处理需求信息。
  6. 根据权利要求5所述的方法，其特征在于，所述XR通话的处理需求信息包括以下至少一项：所述XR通话的待渲染XR对象的信息、所述XR通话的视频分辨率、所述XR通话的视频帧率。
  7. 根据权利要求2至6中任一项所述的方法，其特征在于：
    所述分工指示信息包括所述XR通话中归所述终端设备渲染的待渲染XR对象的信息，所述方法还包括：所述终端设备根据所述XR通话中的待渲染XR对象和所述XR通话中归所述终端设备渲染的待渲染XR对象的信息，确定所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象；或者，
    所述分工指示信息包括所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息，所述方法还包括：所述终端设备根据所述XR通话中的待渲染XR对象和所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息，确定所述XR通话中归所述终端设备渲染的待渲染XR对象；或者，
    所述分工指示信息包括所述XR通话中归所述终端设备渲染的待渲染XR对象的信息和所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息。
  8. 根据权利要求1所述的方法，其特征在于，所述终端设备确定渲染分工，包括：
    所述终端设备基于以下至少一项确定所述渲染分工：
    所述终端设备的处理能力信息、所述网络侧渲染设备的处理能力信息、所述XR通话的处理需求信息。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收来自网络侧控制设备的所述网络侧渲染设备的处理能力信息。
  10. 根据权利要求3至9中任一项所述的方法，其特征在于，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力，或者，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力和所述终端设备支持的渲染分工方式。
  11. 根据权利要求8至10中任一项所述的方法，其特征在于：
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力；或者，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力和所述网络侧渲染设备支持的渲染分工方式。
  12. 根据权利要求10或11所述的方法，其特征在于，所述渲染分工方式包括以下至少一项：按层分工、按类型分工。
  13. 根据权利要求8至12中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧控制设备发送分工确认请求信息，所述分工确认请求信息用于请求接受所述渲染分工，所述分工确认请求信息包括用于确定所述XR通话的待渲染XR对象中归所述网络侧渲染设备渲染的待渲染XR对象的信息。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收来自所述网络侧控制设备的分工确认响应信息，所述分工确认响应信息指示所述渲染分工被接受。
  15. 根据权利要求1至14中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备获取网络侧服务指示信息，所述网络侧服务指示信息指示所述网络侧渲染设备能够提供对XR对象进行渲染的服务。
  16. 根据权利要求1至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧渲染设备发送渲染后XR对象，所述渲染后XR对象为所述终端设备对所述XR通话中归所述终端设备渲染的待渲染XR对象进行渲染所得。
  17. 根据权利要求1至16中任一项所述的方法，其特征在于：
    所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，
    所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，
    所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
  18. 一种扩展现实XR对象渲染的方法，其特征在于，包括：
    网络侧控制设备确定或接受渲染分工，所述渲染分工是指终端设备的XR通话中的一部分待渲染对象归网络侧渲染设备渲染，另一部分待渲染XR对象归所述终端设备渲染；
    所述网络侧控制设备触发所述XR通话中归所述终端设备渲染的XR对象被所述终端设备渲染，以及所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象被所述网络侧渲染设备渲染。
  19. 根据权利要求18所述的方法，其特征在于，所述网络侧控制设备确定渲染分工，包括：
    所述网络侧控制设备根据以下至少一项确定所述渲染分工：
    所述终端设备的处理能力信息、所述网络侧渲染设备的处理能力信息、所述XR通话的处理需求信息。
  20. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备接收来自所述终端设备的所述XR通话的处理需求信息。
  21. 根据权利要求19或20所述的方法，其特征在于，所述XR通话的处理需求信息包括以下至少一项：所述XR通话的待渲染XR对象的信息、所述XR通话的视频分辨率、所述XR通话的视频帧率。
  22. 根据权利要求19所述的方法，其特征在于，所述网络侧控制设备触发所述XR通话中归所述终端设备渲染的XR对象被所述终端设备渲染，以及所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象被所述网络侧渲染设备渲染，包括：
    所述网络侧控制设备向所述终端设备发送分工指示信息，所述分工指示信息指示：所述终端设备的XR通话中的一部分待渲染XR对象归所述网络侧渲染设备渲染，和/或，所述终端设备的XR通话中的另一部分待渲染XR对象归所述终端设备渲染。
  23. 根据权利要求18至22中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备接收来自所述终端设备的所述终端设备的处理能力信息。
  24. 根据权利要求19至23中任一项所述的方法，其特征在于，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力，或者，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力和所述终端设备支持的渲染分工方式。
  25. 根据权利要求18至24中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述网络侧渲染设备的处理能力信息。
  26. 根据权利要求22至25中任一项所述的方法，其特征在于，所述分工指示信息包括以下至少一 项：所述XR通话中归所述终端设备渲染的待渲染XR对象的信息、所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息。
  27. 根据权利要求18所述的方法，其特征在于，所述网络侧控制设备接受渲染分工，包括：
    所述网络侧控制设备接收来自所述终端设备的分工确认请求信息，所述分工确认请求信息用于请求接受所述渲染分工，所述分工确认请求信息包括用于确定所述XR通话的待渲染XR对象中归所述网络侧渲染设备渲染的待渲染XR对象的信息；
    所述网络侧控制设备根据所述分工确认请求信息接受所述渲染分工。
  28. 根据权利要求27所述的方法，其特征在于，所述网络侧控制设备触发所述XR通话中归所述终端设备渲染的XR对象被所述终端设备渲染，以及所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象被所述网络侧渲染设备渲染，包括：
    所述网络侧控制设备向所述终端设备发送分工确认响应信息，所述分工确认响应信息指示所述渲染分工被接受。
  29. 根据权利要求27或28所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述终端设备发送所述网络侧渲染设备的处理能力信息。
  30. 根据权利要求19至26和29中任一项所述的方法，其特征在于，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力，或者，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力和所述网络侧渲染设备支持的渲染分工方式。
  31. 根据权利要求24或30所述的方法，其特征在于，所述渲染分工方式包括以下至少一项：按层分工、按类型分工。
  32. 根据权利要求18至31中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述终端设备发送网络侧服务指示信息，所述网络侧服务指示信息指示所述网络侧渲染设备能够提供对XR对象进行渲染的服务。
  33. 根据权利要求18至32中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述网络侧渲染设备发送请求消息，所述请求消息用于请求以下至少一项：所述网络侧渲染设备的地址信息、所述网络侧渲染设备的渲染资源信息；其中，所述网络侧渲染设备的地址信息用于使与所述XR通话相关的终端设备通过网络侧接入设备连接到所述网络侧渲染设备，所述渲染资源信息为所述网络侧渲染设备用来渲染归所述网络侧渲染设备渲染的待渲染XR对象的资源的信息；
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述请求消息的响应。
  34. 根据权利要求33所述的方法，其特征在于，所述请求消息中包括所述网络侧渲染设备待渲染的XR对象所需的算力。
  35. 根据权利要求18至34中任一项所述的方法，其特征在于：
    所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，
    所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，
    所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
  36. 一种扩展现实XR对象渲染的方法，其特征在于，包括：
    网络侧控制设备向网络侧渲染设备发送请求消息，所述请求消息用于请求所述网络侧渲染设备渲染终端设备的XR通话中归所述网络侧渲染设备渲染的待渲染XR对象，所述请求消息包括归所述网络侧渲染设备渲染的待渲染XR对象所需的算力；
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述请求消息的响应，所述请求消息的响应用于通知所述网络侧控制设备：所述网络侧渲染设备是否将渲染所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象。
  37. 根据权利要求36所述的方法，其特征在于，在所述网络侧控制设备向网络侧渲染设备发送请求消息之前，所述方法还包括：
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述网络侧渲染设备的处理能力信息。
  38. 根据权利要求37所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备根据所述网络侧渲染设备的处理能力信息，确定所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象。
  39. 根据权利要求37或38所述的方法，其特征在于，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力，或者，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力和所述网络侧渲染设备支持的渲染分工方式。
  40. 根据权利要求36至39中任一项所述的方法，其特征在于：
    所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，
    所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，
    所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
  41. 一种扩展现实XR对象渲染的方法，其特征在于，包括：
    网络侧渲染设备接收来自网络侧控制设备的请求消息，所述请求消息用于请求所述网络侧渲染设备渲染终端设备的XR通话中归所述网络侧渲染设备渲染的待渲染XR对象，所述请求消息包括归所述网络侧渲染设备渲染的待渲染XR对象所需的算力；
    所述网络侧渲染设备向所述网络侧控制设备发送所述请求消息的响应，所述请求消息的响应用于通知所述网络侧控制设备：所述网络侧渲染设备是否将渲染所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象。
  42. 根据权利要求41所述的方法，其特征在于，所述方法还包括：
    所述网络侧渲染设备根据所述网络侧渲染设备待渲染的XR对象所需的算力，确定所述网络侧渲染设备渲染所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象所需的资源。
  43. 根据权利要求41或42所述的方法，其特征在于，在所述网络侧渲染设备接收来自网络侧控制设备的请求消息之前，所述方法还包括：
    所述网络侧渲染设备向所述网络侧控制设备发送所述网络侧渲染设备的处理能力信息。
  44. 根据权利要求43所述的方法，其特征在于，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力，或者，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力和所述网络侧渲染设备支持的渲染分工方式。
  45. 根据权利要求41至44中任一项所述的方法，其特征在于：
    所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，
    所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，
    所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
  46. 一种扩展现实XR对象渲染的方法，其特征在于，包括：
    网络侧控制设备确定或接受渲染分工，所述渲染分工是指终端设备的XR通话中的一部分待渲染对象归网络侧渲染设备渲染，另一部分待渲染XR对象归所述终端设备渲染；
    所述终端设备确定或接受所述渲染分工；
    所述网络侧控制设备触发所述XR通话中归所述终端设备渲染的XR对象被所述终端设备渲染，以及所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象被所述网络侧渲染设备渲染；
    所述终端设备渲染所述XR通话中归所述终端设备渲染的待渲染XR对象，并向所述网络侧渲染设备发送所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息。
  47. 根据权利要求46所述的方法，其特征在于，所述网络侧控制设备确定渲染分工，所述终端设备接受所述渲染分工，包括：
    所述网络侧控制设备根据以下至少一项确定所述渲染分工：
    所述终端设备的处理能力信息、所述网络侧渲染设备的处理能力信息、所述XR通话的处理需求信息；
    所述网络侧控制设备向所述终端设备发送分工指示信息，所述分工指示信息指示所述终端设备的XR通话中的一部分待渲染XR对象归所述网络侧渲染设备渲染，和/或，所述终端设备的XR通话中的另一部分待渲染XR对象归所述终端设备渲染
    所述终端设备接收来自网络侧控制设备的分工指示信息。
  48. 根据权利要求47所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧控制设备发送所述终端设备的处理能力信息，所述终端设备的处理能力信息用于确定所述分工指示信息；
    所述网络侧控制设备接收来自所述终端设备的所述终端设备的处理能力信息。
  49. 根据权利要求47或48所述的方法，其特征在于，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力，或者，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力和所述终端设备支持的渲染分工方式。
  50. 根据权利要求48或49所述的方法，其特征在于，所述终端设备向所述网络侧控制设备发送所述终端设备的处理能力信息，包括：
    所述终端设备向网络侧接入设备发送注册消息或会话呼叫消息以触发所述网络侧接入设备向所述网络侧控制设备发送所述终端设备的处理能力信息，所述注册消息或所述会话呼叫消息包含所述终端设备的处理能力信息。
  51. 根据权利要求47至50中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述网络侧渲染设备的处理能力信息。
  52. 根据权利要求47至51中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧控制设备发送所述XR通话的处理需求信息；
    所述网络侧控制设备接收来自所述终端设备的所述XR通话的处理需求信息。
  53. 根据权利要求52所述的方法，其特征在于，所述XR通话的处理需求信息包括以下至少一项：所述XR通话的待渲染XR对象的信息、所述XR通话的视频分辨率、所述XR通话的视频帧率。
  54. 根据权利要求47至53中任一项所述的方法，其特征在于：
    所述分工指示信息包括所述XR通话中归所述终端设备渲染的待渲染XR对象的信息，所述方法还包括：所述终端设备根据所述XR通话中的待渲染XR对象和所述XR通话中归所述终端设备渲染的待渲染XR对象的信息，确定所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象；或者，
    所述分工指示信息包括所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息，所述方法还包括：所述终端设备根据所述XR通话中的待渲染XR对象和所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息，确定所述XR通话中归所述终端设备渲染的待渲染XR对象；或者，
    所述分工指示信息包括所述XR通话中归所述终端设备渲染的待渲染XR对象的信息和所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象的信息。
  55. 根据权利要求46所述的方法，其特征在于，所述终端设备确定渲染分工，所述网络侧控制设备接受所述渲染分工，包括：
    所述终端设备基于以下至少一项确定所述渲染分工：
    所述终端设备的处理能力信息、所述网络侧渲染设备的处理能力信息、所述XR通话的处理需求信息。
  56. 根据权利要求55所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述终端设备发送所述网络侧渲染设备的处理能力信息；
    所述终端设备接收来自网络侧控制设备的所述网络侧渲染设备的处理能力信息。
  57. 根据权利要求55或56所述的方法，其特征在于，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力，或者，
    所述终端设备的处理能力信息包括所述终端设备的渲染可用算力和所述终端设备支持的渲染分工方式。
  58. 根据权利要求55至57中任一项所述的方法，其特征在于：
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力；或者，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力和所述网络侧渲染设备支持的渲染分工方式。
  59. 根据权利要求57或58所述的方法，其特征在于，所述渲染分工方式包括以下至少一项：按层 分工、按类型分工。
  60. 根据权利要求55至59中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧控制设备发送分工确认请求信息，所述分工确认请求信息用于请求接受所述渲染分工，所述分工确认请求信息包括用于确定所述XR通话的待渲染XR对象中归所述网络侧渲染设备渲染的待渲染XR对象的信息；
    所述网络侧控制设备接收来自所述终端设备的所述分工确认请求信息。
  61. 根据权利要求60所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述终端设备发送分工确认响应信息，所述分工确认响应信息指示所述渲染分工被接受；
    所述终端设备接收来自所述网络侧控制设备的所述分工确认响应信息。
  62. 根据权利要求46至61中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述终端设备发送网络侧服务指示信息，所述网络侧服务指示信息指示所述网络侧渲染设备能够提供对XR对象进行渲染的服务；
    所述终端设备获取所述网络侧服务指示信息。
  63. 根据权利要求46至62中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络侧渲染设备发送渲染后XR对象，所述渲染后XR对象为所述终端设备对所述XR通话中归所述终端设备渲染的待渲染XR对象进行渲染所得。
  64. 根据权利要求46至63中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备向所述网络侧渲染设备发送请求消息，所述请求消息用于请求以下至少一项：所述网络侧渲染设备的地址信息、所述网络侧渲染设备的渲染资源信息；其中，所述网络侧渲染设备的地址信息用于使与所述XR通话相关的终端设备通过网络侧接入设备连接到所述网络侧渲染设备，所述渲染资源信息为所述网络侧渲染设备用来渲染归所述网络侧渲染设备渲染的待渲染XR对象的资源的信息；
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述请求消息的响应。
  65. 根据权利要求64所述的方法，其特征在于，所述请求消息中包括所述网络侧渲染设备待渲染的XR对象所需的算力。
  66. 根据权利要求45至65中任一项所述的方法，其特征在于：
    所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，
    所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，
    所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
  67. 一种扩展现实XR对象渲染的方法，其特征在于，包括：
    网络侧控制设备向网络侧渲染设备发送请求消息，所述请求消息用于请求所述网络侧渲染设备渲染终端设备的XR通话中归所述网络侧渲染设备渲染的待渲染XR对象，所述请求消息包括归所述网络侧渲染设备渲染的待渲染XR对象所需的算力；
    所述网络侧渲染设备接收来自网络侧控制设备的请求消息；
    所述网络侧渲染设备向所述网络侧控制设备发送所述请求消息的响应，所述请求消息的响应用于通知所述网络侧控制设备：所述网络侧渲染设备是否将渲染所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象；
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述请求消息的响应。
  68. 根据权利要求67所述的方法，其特征在于，所述方法还包括：
    所述网络侧渲染设备根据所述网络侧渲染设备待渲染的XR对象所需的算力，确定所述网络侧渲染设备渲染所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象所需的资源。
  69. 根据权利要求67或68所述的方法，其特征在于，在所述网络侧控制设备向网络侧渲染设备发送请求消息之前，所述方法还包括：
    所述网络侧渲染设备向所述网络侧控制设备发送所述网络侧渲染设备的处理能力信息；
    所述网络侧控制设备接收来自所述网络侧渲染设备的所述网络侧渲染设备的处理能力信息。
  70. 根据权利要求68或69所述的方法，其特征在于，所述方法还包括：
    所述网络侧控制设备根据所述网络侧渲染设备的处理能力信息，确定所述XR通话中归所述网络侧渲染设备渲染的待渲染XR对象。
  71. 根据权利要求68至70中任一项所述的方法，其特征在于，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力，或者，
    所述网络侧渲染设备的处理能力信息包括所述网络侧渲染设备的渲染可用算力和所述网络侧渲染设备支持的渲染分工方式。
  72. 根据权利要求67至71中任一项所述的方法，其特征在于：
    所述网络侧控制设备为XR控制面网元，所述网络侧渲染设备为XR媒体面网元；或者，
    所述网络侧控制设备为应用服务器，所述网络侧渲染设备为媒体资源功能网元；或者，
    所述网络侧控制设备为互联网业务信令服务器，所述网络侧渲染设备为互联网业务媒体服务器。
  73. 一种通信装置，其特征在于，包括执行如权利要求1至17中任一项所述方法的单元或模块，或包括执行如权利要求18至35中任一项所述方法的单元或模块，或包括执行如权利要求36至40中任一项所述方法的单元或模块，或包括执行如权利要求41至45中任一项所述方法的单元或模块。
  74. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行以下任一项：
    如权利要求1至17中任一项所述的方法，如权利要求18至35中任一项所述的方法，如权利要求36至40中任一项所述的方法，或者如权利要求41至45中任一项所述的方法。
  75. 一种通信系统，其特征在于，包括终端设备和网络设备，
    其中，所述终端设备用于执行如权利要求1至17中任一项所述的方法，所述网络设备用于执行如权利要求18至35中任一项所述的方法。
  76. 一种通信系统，其特征在于，包括网络侧控制设备和网络侧渲染设备，
    其中，所述网络侧控制设备用于执行如权利要求36至40中任一项所述的方法，所述网络侧渲染设备用于执行如权利要求41至45中任一项所述的方法。
  77. 一种计算机可读存储介质，其特征在于，包括计算机程序，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至17中任一项所述的方法；或者，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求18至35中任一项所述的方法；或者
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求36至40中任一项所述的方法；或者，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求41至45中任一项所述的方法。
  78. 一种计算机程序产品，其特征在于，所述计算机程序产品中包括计算机程序代码，其特征在于：
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求1至17中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求18至35中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求36至40中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求41至45中任一项所述的方法。
  79. 一种通信装置，其特征在于，所述通信装置用于执行如权利要求1至45中任一项所述的方法。
PCT/CN2023/103528 2022-07-06 2023-06-29 Xr对象渲染的方法、通信装置及系统 Ceased WO2024007926A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP23834694.4A EP4539436A4 (en) 2022-07-06 2023-06-29 XR OBJECT RENDERING METHOD, AND COMMUNICATION APPARATUS AND SYSTEM
US19/009,412 US20250139917A1 (en) 2022-07-06 2025-01-03 Xr object rendering method and communication apparatus and system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210789069 2022-07-06
CN202210789069.1 2022-07-06
CN202210952860.XA CN117411944A (zh) 2022-07-06 2022-08-09 Xr对象渲染的方法、通信装置及系统
CN202210952860.X 2022-08-09

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/009,412 Continuation US20250139917A1 (en) 2022-07-06 2025-01-03 Xr object rendering method and communication apparatus and system

Publications (1)

Publication Number Publication Date
WO2024007926A1 true WO2024007926A1 (zh) 2024-01-11

Family

ID=89454229

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103528 Ceased WO2024007926A1 (zh) 2022-07-06 2023-06-29 Xr对象渲染的方法、通信装置及系统

Country Status (3)

Country Link
US (1) US20250139917A1 (zh)
EP (1) EP4539436A4 (zh)
WO (1) WO2024007926A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025198899A1 (en) * 2024-03-19 2025-09-25 Qualcomm Incorporated Distributing communication and computing of split rendering of media data
WO2025212721A1 (en) * 2024-04-03 2025-10-09 Tencent America LLC A novel method for device type and media codec capabilities exchange in 5g real-time communication sessions

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12526681B2 (en) * 2022-10-19 2026-01-13 Qualcomm Incorporated Signaling for extended reality (XR) rendering offloading
US20250063079A1 (en) * 2023-08-15 2025-02-20 Nokia Technologies Oy Seamless split rendering session relocation between split rendering servers supporting extended reality applications in mobile communication networks

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105096373A (zh) * 2015-06-30 2015-11-25 华为技术有限公司 一种媒体内容渲染的方法、用户设备及系统
CN106534667A (zh) * 2016-10-31 2017-03-22 努比亚技术有限公司 分布式协同渲染方法及终端
US20220028172A1 (en) * 2020-07-23 2022-01-27 Samsung Electronics Co., Ltd. Method and apparatus for transmitting 3d xr media data
CN114501062A (zh) * 2022-01-27 2022-05-13 腾讯科技（深圳）有限公司 视频渲染协同方法、装置、设备及存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111371849A (zh) * 2019-02-22 2020-07-03 华为技术有限公司 数据处理的方法和电子设备
US11302055B2 (en) * 2019-04-01 2022-04-12 Apple Inc. Distributed processing in computer generated reality system
US20230403596A1 (en) * 2020-10-26 2023-12-14 Nokia Technologies Oy Apparatus, method, and computer program for providing service level for extended reality application

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105096373A (zh) * 2015-06-30 2015-11-25 华为技术有限公司 一种媒体内容渲染的方法、用户设备及系统
CN106534667A (zh) * 2016-10-31 2017-03-22 努比亚技术有限公司 分布式协同渲染方法及终端
US20220028172A1 (en) * 2020-07-23 2022-01-27 Samsung Electronics Co., Ltd. Method and apparatus for transmitting 3d xr media data
CN114501062A (zh) * 2022-01-27 2022-05-13 腾讯科技（深圳）有限公司 视频渲染协同方法、装置、设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4539436A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025198899A1 (en) * 2024-03-19 2025-09-25 Qualcomm Incorporated Distributing communication and computing of split rendering of media data
WO2025212721A1 (en) * 2024-04-03 2025-10-09 Tencent America LLC A novel method for device type and media codec capabilities exchange in 5g real-time communication sessions

Also Published As

Publication number Publication date
EP4539436A1 (en) 2025-04-16
EP4539436A4 (en) 2025-10-01
US20250139917A1 (en) 2025-05-01

Similar Documents

Publication Publication Date Title
WO2024007926A1 (zh) Xr对象渲染的方法、通信装置及系统
JP6325105B2 (ja) 複数のソースから単一のシンクへのワイヤレスメディア共有
CN111147893B (zh) 一种视频自适应方法、相关设备以及存储介质
CN103650458B (zh) 媒体流的传输方法、装置与系统
US20060083244A1 (en) Method for sessions including multiple resources
CN106295107A (zh) 一种实现医学影像同步会诊的方法及系统
CN111711784B (zh) 会议控制方法、装置、可读介质及电子设备
EP4366274A1 (en) Communication method and apparatus, and communication system
WO2015078220A1 (zh) 媒体复用协商的方法和装置
US9264662B2 (en) Chat preauthorization
CN117411944A (zh) Xr对象渲染的方法、通信装置及系统
CN115362672A (zh) 使用网络边缘的体三维会话服务的方法和装置
CN106357654A (zh) 远程过程调用方法、装置及通信系统
WO2016114967A1 (en) Systems and methods for adaptive context-aware control of multimedia communication sessions
CN112532578B (zh) 通信系统
CN115297093B (zh) 边缘设备数据访问方法、相关装置及计算机程序产品
CN117082631A (zh) 数据处理方法、装置、终端、网络侧设备及介质
WO2022143291A1 (zh) 一种业务的配置方法及装置
KR20170071251A (ko) 회의 서비스를 제공하는 다중 접속 제어 장치
CN114302505B (zh) 会话连接方法及网络功能实体设备
WO2023213274A1 (zh) 数据处理方法、装置、终端、网络侧设备及介质
WO2026056258A1 (zh) 数据渲染方法、媒体处理网元、终端设备及存储介质
CN118433341A (zh) 视频会议方法、装置及通信系统
WO2025189819A1 (zh) 通信方法及装置
WO2025148729A1 (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: 23834694

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023834694

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 11202409009S

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 2023834694

Country of ref document: EP

Effective date: 20250109

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2023834694

Country of ref document: EP