A method and apparatus for communication

Abstract

A communication method and device are used to guarantee the security when an entity renders a digital human to request a digital human model from a BAR network element in a digital human related call. In the present application, the method comprises: a first terminal sends a capability negotiation request, the capability negotiation request carries an identifier of a first digital human, and the capability negotiation request is used for negotiating the rendering of the first digital human. The first terminal receives a capability negotiation response, the capability negotiation response includes information of a first entity, the first entity is an entity used for downloading a first digital human model, and the first digital human model is used for rendering the first digital human. The first terminal generates a token according to the information of the first entity, and the token is used to authorize the first entity to download the first digital human model.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more particularly to a communication method and apparatus. Background Technology

[0002] A digital human is a virtual character with a digital appearance, displayed through display devices such as mobile phones, televisions, augmented reality (AR) glasses, or virtual reality (VR) glasses. For example, Figure 1 This diagram illustrates a scenario of a digital human-related call. A first terminal acts as a data acquisition unit, collecting user information from user 'a' and providing it to a rendering entity. The rendering entity generates video frames based on user 'a's information and the digital human model corresponding to the first terminal. These video frames include the digital human corresponding to user 'a'. The video frames are then displayed on a second terminal, allowing user 'b' on the second terminal to see the digital human corresponding to user 'a'. The rendering entity can be the first terminal, the second terminal, or a network device (e.g., a media function (MF) network element). The user information can specifically include action information, language information, facial expression information, and text information.

[0003] Ensuring the safety of digital human models is a matter of concern. Summary of the Invention

[0004] This application provides a communication method and apparatus for ensuring the security of digital human models.

[0005] In a first aspect, this application provides a communication method, which can be executed by a first communication device, which may be a first terminal or a part of the first terminal (e.g., a chip in the first terminal).

[0006] When the first communication device is a first terminal, for example, the first communication device can send information to a data channel application server (DCAS), or the first communication device can receive information from the DCAS. When the first communication device is a module in the first terminal, the first communication device can send information to other modules in the first terminal (such as a radio frequency module or antenna), for example, the information is sent by the first terminal to the DCAS; or, the first communication device can receive information from other modules (such as a radio frequency module or antenna), for example, the information is sent by the DCAS to the first terminal.

[0007] For ease of description, the following explanation will use the example of the first communication device being the first terminal.

[0008] The method is applied to a scenario in which the first terminal and the second terminal perform a digital human related call, and the method comprises:

[0009] The first terminal sends a capability negotiation request, and the capability negotiation request carries an identifier of the first digital human. The capability negotiation request is used for negotiating rendering of the first digital human. The first terminal receives a capability negotiation response, and the capability negotiation response includes information of a first entity. The first entity is an entity used for downloading a first digital human model. The first digital human model is used for rendering of the first digital human. The first terminal generates a token based on the information of the first entity. The token is used for authorizing the first entity to download the first digital human model. The first terminal sends the token.

[0010] The information of the first entity may be, for example, an identifier of the first entity and / or a type of the first entity.

[0011] In the above technical solution, the first terminal issues a token based on the information of the first entity (i.e., the entity used for downloading the first digital human model). Compared with the first terminal generating a token based on coarse-grained information (such as information of all possible entities that may use the token, for example, including terminal types, MF entity types, and DC AS types), the first terminal generates a token based on fine-grained information (i.e., the information of the first entity). The token is used for the first entity to download the first digital human model, and cannot be used for other entities to download the first digital human model, thereby avoiding the rights to download the digital human model from being abused and improving security. Thus, when the first entity requests the first digital human model from a base digital human repository (BAR) network element based on the token, the BAR network element can verify the identity of the first entity based on the token. For example, the BAR network element provides the first digital human model to the first entity when it is determined that the first entity passes the identity verification, and the BAR network element does not provide the first digital human model to the first entity when it is determined that the first entity does not pass the identity verification. In this way, the first terminal issues the token, thereby improving security in the process of requesting the digital human model.

[0012] In the capability negotiation process, the first terminal obtains the information of the first entity, which helps to save the number of signaling interactions.

[0013] In a possible implementation manner, the token includes the information of the first entity and the identifier of the first digital human.

[0014] In the above technical solution, the first terminal carries the information of the first entity and the identifier of the first digital human in the token. In other words, the first entity is authorized to download the first digital human model corresponding to the identifier of the first digital human. Correspondingly, the BAR network element can perform verification based on the token, which helps to improve security in the process of requesting the digital human model.

[0015] In a possible implementation, the first terminal establishes a first application data channel (ADC) with the DC AS. Illustratively, the capability negotiation request is sent by the first terminal to the DC AS through the first ADC, for example, the first terminal sends the capability negotiation request to a MF network element, and the MF network element forwards the capability negotiation request to the DC AS. Illustratively, the capability negotiation response is sent by the DC AS to the first terminal through the first ADC, in other words, the capability negotiation response is information from the DC AS received by the first terminal through the first ADC, for example, the DC AS sends the capability negotiation response to the MF network element, and the MF network element forwards the capability negotiation response to the first terminal.

[0016] In a possible implementation, the capability negotiation response further includes information of an entity for storing the first digital human model, and the token includes information of the entity for storing the first digital human model. In a possible implementation, the entity for storing the first digital human model is a first BAR network element, and illustratively, the information of the first BAR network element is an identifier of the first BAR network element.

[0017] In the above technical solution, the first terminal carries information of an entity for storing the first digital human model (for example, an identifier of the first BAR network element) in the token, and when a second BAR network element receives a request of the first entity for downloading the first digital human model, the second BAR network element can determine whether the information of the entity for storing the first digital human model in the token is information of the second BAR network element, and further determine whether to provide the first digital human model to the first entity. Illustratively, when the second BAR network element determines that the information of the entity for storing the first digital human model included in the token is the same as the information of the second BAR network element (that is, the first BAR and the second BAR are the same BAR), the second BAR network element provides the first digital human model to the first entity; and when the second BAR network element determines that the information of the entity for storing the first digital human model included in the token is different from the information of the second BAR network element (that is, the first BAR and the second BAR are different BARs), the second BAR network element does not provide the first digital human model to the first entity. In this way, the security of the digital human model in the BAR network element is further ensured. Further, compared with the first terminal generating a token based on coarse-grained information (such as information of all possible entities for providing the digital human model), the first terminal generates a token based on fine-grained information (for example, information of the first BAR network element), and the token is used by the first entity to request the first digital human model from the first BAR, but cannot be used by the first entity to request the first digital human model from other entities, in other words, the token indicates that the first BAR can provide the first digital human model, but other entities cannot provide the first digital human model, and the authorization of the digital human model is more accurate, the right to provide the digital human model is avoided from being abused, and the security is further ensured.

[0018] In a possible implementation, the token is carried in the re-invite message. For example, the first terminal sends a re-invite message, and the re-invite message includes the token. For example, the re-invite message is used to establish a second ADC between the first terminal and the DC AS, and the second ADC is used to transmit service data, for example, data between the first terminal and the second terminal (such as data for rendering by a rendering entity (for example, user information), a digital person after rendering, etc.). In the above technical solution, the first terminal carries the token in the re-invite message, without adding other messages, which helps to save the number of signaling interactions.

[0019] In a possible implementation, the first entity is one of the DC AS, the MF network element, the first terminal, and the second terminal related to the call. For example, the first entity is a rendering entity, for example, one of the MF network element, the first terminal, and the second terminal. For another example, the first entity is a proxy entity, which can be used to proxy the rendering entity to request the first digital person model from the BAR network element, for example, the DC AS.

[0020] In a possible implementation, the capability negotiation request carries the negotiation parameter of the first terminal; the negotiation parameter of the first terminal includes the rendering capability of the first terminal and / or the candidate entity recommended by the first terminal; and the candidate entity includes one or more of the MF network element, the first terminal, and the second terminal related to the call. For example, the negotiation parameter of the first terminal can be used to determine the information of the first entity.

[0021] The above technical solution helps to improve the flexibility of determining the information of the first entity.

[0022] In a second aspect, a method for communication is provided, which can be performed by a second communication device. The second communication device can be a DC AS, or a part of the DC AS (for example, a chip in the DC AS).

[0023] When the second communication device is the DC AS, the second communication device can send information to the first terminal, or the second communication device can receive information from the first terminal. When the second communication device is a module in the DC AS, the second communication device can send information to other modules (such as a radio frequency module or an antenna) in the DC AS, for example, the information is sent by the DC AS to the first terminal; or the second communication device can receive information from other modules (such as a radio frequency module or an antenna), for example, the information is sent by the first terminal to the DC AS.

[0024] For convenience of description, the second communication device is taken as the DC AS for example.

[0025] The method is applied to a scenario in which the first terminal and the second terminal perform a digital human related call, and the method comprises:

[0026] The DC AS receives a capability negotiation request, the capability negotiation request carrying an identifier of the first digital human, the capability negotiation request being used for negotiating rendering of the first digital human; the DC AS sends a capability negotiation response, the capability negotiation response including information of a first entity, the first entity being an entity used for downloading a first digital human model, the first digital human model being used for rendering of the first digital human; the information of the first entity is used for generating a token, the token being used for authorizing the first entity to download the first digital human model. For example, the information of the first entity is used for the first terminal to generate the token.

[0027] In a possible implementation, the capability negotiation response further includes information of an entity used for storing the first digital human model. For example, the information of the entity used for storing the first digital human model is an identifier of the first BAR network element.

[0028] In a possible implementation, the capability negotiation request carries negotiation parameters of the first terminal; the negotiation parameters of the first terminal include rendering capability of the first terminal and / or a candidate entity recommended by the first terminal; the candidate entity includes one or more of the MF network element, the first terminal and the second terminal related to the call. After receiving the capability negotiation request, the DC AS further determines the information of the first entity according to the negotiation parameters of the first terminal.

[0029] For example, when the DC AS determines the information of the first entity according to the negotiation parameters of the first terminal, the DC AS can specifically obtain negotiation parameters of the MF network element and negotiation parameters of the second terminal from the MF network element; and the DC AS determines the information of the first entity according to the negotiation parameters of the first terminal, the negotiation parameters of the MF network element and the negotiation parameters of the second terminal. For example, the negotiation parameters of the MF network element include rendering capability of the MF network element and / or a candidate entity recommended by the MF network element; and the negotiation parameters of the second terminal include rendering capability of the second terminal and / or a candidate entity recommended by the second terminal.

[0030] In a possible implementation, the first entity is one of the DC AS, the MF network element, the first terminal and the second terminal related to the call.

[0031] In a possible implementation, when the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal all do not meet the preset rendering requirement, the DC AS further sends a first request to a network repository function (NRF) network element, the first request including the preset rendering requirement, and the first request being used to request a first entity meeting the preset rendering requirement; further, the DC AS receives a first response from the NRF, the first response including information of the first entity.

[0032] In the technical solution, when the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal all do not meet the preset rendering requirement, the DC AS further requests information of the first entity from the NRF network element, thereby ensuring normal progress of the rendering process.

[0033] For example, the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal all do not meet the preset rendering requirement, which can be that the rendering capability of the first terminal, the rendering capability of the MF network element and the rendering capability of the second terminal all do not meet the preset rendering requirement.

[0034] In a possible implementation, the rendering capability of the first terminal includes one or more of the following:

[0035] (1) Whether the first terminal supports rendering, that is, whether the first terminal has the capability of being a rendering entity.

[0036] (2) The rendering data requirement of the first terminal, wherein the rendering data requirement of the first terminal includes a data type required by the first terminal when rendering the first digital human and / or a minimum number of sensors corresponding to the data type required when rendering the first digital human.

[0037] (3) The remaining computing resource of the first terminal, wherein the remaining computing resource of the first terminal includes one or more of the following: a current available resource of a central processing unit (CPU) of the first terminal, a current available power consumption of a graphics processing unit (GPU) of the first terminal, a current available computing power of the GPU or a current available memory resource.

[0038] (4) A score of the remaining computing resource of the first terminal, wherein the score can be obtained by the first terminal scoring the remaining computing resource of the first terminal according to a preset scoring system.

[0039] In a possible implementation, the first terminal establishes a first ADC with the DC AS. Illustratively, the capability negotiation request is sent by the first terminal to the DC AS through the first ADC, in other words, the capability negotiation request is information from the first terminal received by the DC AS through the first ADC. For example, the first terminal sends the capability negotiation request to a MF network element, and the MF network element forwards the capability negotiation request to the DC AS. Illustratively, the capability negotiation response is sent by the DC AS to the first terminal through the first ADC, for example, the DC AS sends the capability negotiation response to the MF network element, and the MF network element forwards the capability negotiation response to the first terminal.

[0040] In a third aspect, the present application provides a method of communication, which can be executed by a third communication device, which can be a second BAR network element, or a part of the second BAR network element (for example, a chip in the second BAR network element).

[0041] For the convenience of description, the third communication device is taken as the second BAR network element for example.

[0042] The method is applied to a scenario in which the first terminal and the second terminal perform a digital human related call, and the method comprises the following steps.

[0043] The second BAR network element receives a token from a second entity, the token being used to authorize a first entity to download a first digital human model, the token being generated by the first terminal according to information of the first entity, the first digital human model being used for rendering of the first digital human. The second BAR network element sends the first digital human model to the second entity when it is determined that the information of the second entity is the same as the information of the first entity in the token; and the second BAR network element does not send the first digital human model to the second entity when it is determined that the information of the second entity is not the same as the information of the first entity in the token.

[0044] In a possible implementation, the token comprises the information of the first entity and an identifier of the first digital human.

[0045] In a possible implementation, the token further comprises information of an entity for storing the digital human model (for example, an identifier of the second BAR network element). The second BAR network element can further determine whether the information of the entity for storing the digital human model in the token is information of the second BAR network element. Further, when the second BAR network element determines that the information of the entity for storing the digital human model in the token is information of the second BAR network element, and the information of the second entity is the same as the information of the first entity in the token, the first digital human model is sent to the second entity.

[0046] In a fourth aspect, the present application provides a method of communication, which can be executed by a fourth communication device, which can be a NRF network element, or a part of the NRF network element (for example, a chip in the NRF network element).

[0047] For the convenience of description, the fourth communication device is taken as an example of the NRF network element for illustration.

[0048] The method is applied to a scenario in which the first terminal and the second terminal perform a digital human related call, and the method comprises:

[0049] The NRF network element receives a first request, the first request comprising preset rendering requirements, the first request being used to request a first entity satisfying the preset rendering requirements, the first request being sent by the DC AS when it is determined that the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal all do not satisfy the preset rendering requirements; and the NRF network element sends a first response, the first response comprising information of the first entity.

[0050] In a fifth aspect, an embodiment of the present application provides a communication device.

[0051] The device has the function of implementing the first communication device in the first aspect or any possible implementation manner of the first aspect. The communication device can also have the function of implementing the second communication device in the second aspect or any possible implementation manner of the second aspect. The communication device can also have the function of implementing the third communication device in the third aspect or any possible implementation manner of the third aspect. The communication device can also have the function of implementing the fourth communication device in the fourth aspect or any possible implementation manner of the fourth aspect.

[0052] The functions of the communication device described above can be implemented by hardware, or by hardware executing corresponding software, and the hardware or software includes one or more modules or units or means corresponding to the functions.

[0053] In a possible implementation manner, the structure of the device comprises a processing module and a transceiver module.

[0054] The processing module is configured to support the device to perform the corresponding functions of the first communication device in the first aspect or any possible implementation manner of the first aspect, or the corresponding functions of the second communication device in the second aspect or any possible implementation manner of the second aspect, or the corresponding functions of the third communication device in the third aspect or any possible implementation manner of the third aspect, or the corresponding functions of the fourth communication device in the fourth aspect or any possible implementation manner of the fourth aspect.

[0055] The transceiver module is configured to support communication between the apparatus and other communication devices, for example, when the apparatus is a first communication device, the transceiver module can send a capability negotiation request. The apparatus can further include a storage module coupled to the processing module, which stores necessary program instructions and data of the apparatus. As an example, the processing module can be a processor, the communication module can be a transceiver, and the storage module can be a memory, which can be integrated with the processor or can be separately arranged from the processor.

[0056] In another possible implementation, the apparatus includes a processor and can further include a memory. The processor is coupled to the memory and is configured to execute computer program instructions stored in the memory to cause the apparatus to perform the method in the first aspect or any possible implementation of the first aspect, or perform the method in the second aspect or any possible implementation of the second aspect, or perform the method in the third aspect or any possible implementation of the third aspect, or perform the method in the fourth aspect or any possible implementation of the fourth aspect. Optionally, the apparatus further includes a communication interface, and the processor is coupled to the communication interface. When the apparatus is a device, the communication interface can be a transceiver or an input / output interface; when the apparatus is a chip included in the device, the communication interface can be an input / output interface of the chip. Optionally, the transceiver can be a transceiver circuit, and the input / output interface can be an input / output circuit.

[0057] In a sixth aspect, an embodiment of the present application provides a chip system, including: a processor and a memory, the processor being coupled to the memory, and the memory being configured to store program or instructions, when the program or instructions are executed by the processor, causing the chip system to perform the method in the first aspect or any possible implementation of the first aspect, or perform the method in the second aspect or any possible implementation of the second aspect, or perform the method in the third aspect or any possible implementation of the third aspect, or perform the method in the fourth aspect or any possible implementation of the fourth aspect.

[0058] Optionally, the chip system further includes an interface circuit configured to interact code instructions with the processor.

[0059] Optionally, the processor in the chip system can be one or more processors, which can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor, which is configured to read software code stored in the memory.

[0060] Optionally, the memory in the chip system can also be one or more. The memory can be integrated with the processor, or can be separately arranged from the processor. For example, the memory can be a non-transient processor, such as a read only memory (ROM), which can be integrated on the same chip as the processor, or can be separately arranged on different chips.

[0061] In a seventh aspect, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program or instructions, when the computer program or instructions are executed by a communication device, the communication device performs the method in the first aspect or any possible implementation manner of the first aspect, or performs the method in the second aspect or any possible implementation manner of the second aspect, or performs the method in the third aspect or any possible implementation manner of the third aspect, or performs the method in the fourth aspect or any possible implementation manner of the fourth aspect.

[0062] In an eighth aspect, a computer program product is provided, and the computer program product includes a computer program or instructions, when the computer program or instructions are executed by a communication device, the communication device performs the method in the first aspect or any possible implementation manner of the first aspect, or performs the method in the second aspect or any possible implementation manner of the second aspect, or performs the method in the third aspect or any possible implementation manner of the third aspect, or performs the method in the fourth aspect or any possible implementation manner of the fourth aspect.

[0063] In a ninth aspect, an embodiment of the present application provides a communication system, and the communication system includes one or more of a first communication device, a second communication device, a third communication device or a fourth communication device, wherein the first communication device performs the method in the first aspect or any possible implementation manner of the first aspect, the second communication device performs the method in the second aspect or any possible implementation manner of the second aspect, the third communication device performs the method in the third aspect or any possible implementation manner of the third aspect, and the fourth communication device performs the method in the fourth aspect or any possible implementation manner of the fourth aspect.

[0064] The technical effects achieved by any one of the second aspect to the ninth aspect can refer to the description of the beneficial effects of the first aspect, which will not be repeated here. The technical solutions in the first aspect to the ninth aspect can be mutually referred to. BRIEF DESCRIPTION OF DRAWINGS

[0065] Figure 1 A schematic diagram of a digital human related communication scenario;

[0066] Figure 2A A network architecture diagram provided for the present application;

[0067] Figure 2B Another network architecture diagram provided for the present application;

[0068] Figure 2C Still another network architecture diagram provided for the present application;

[0069] Figure 3 A flow diagram of a first communication method provided for the present application;

[0070] Figure 4 A flow diagram of a second communication method provided for the present application;

[0071] Figure 5 A flow diagram of a third communication method provided for the present application;

[0072] Figure 6 A flow diagram of a fourth communication method provided for the present application;

[0073] Figure 7 A flow diagram of a fifth communication method provided for the present application;

[0074] Figure 8 A flow diagram of a sixth communication method provided for the present application;

[0075] Figure 9 A flow diagram of a seventh communication method provided for the present application;

[0076] Figure 10 A structure diagram of a communication device provided for the present application;

[0077] Figure 11 Another structure diagram of a communication device provided for the present application. DETAILED DESCRIPTION

[0078] The following first explains the related technical features involved in the embodiments of the present application. It should be noted that these explanations are to make the embodiments of the present application easier to understand, and should not be regarded as limiting the scope of protection required by the present application.

[0079] The communication method provided in the present application can be applied to various communication systems, for example, a 5th generation (5G) communication system (or referred to as a new radio (NR) system), a 4th generation (4G) communication system (or referred to as a long term evolution (LTE) system), an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, and the like. The technical solutions provided in the present application can also be applied to future communication systems.

[0080] The network architecture to which the communication method provided in the present application is applicable will be introduced below.

[0081] Referring to Figure 2A A network architecture diagram is exemplarily provided in the present application. Figure 2A The network architecture shown includes a first terminal, a communication network, and a second terminal. The first terminal and the second terminal can communicate through the communication network. Exemplarily, the first terminal and the second terminal can communicate through the communication network for avatar-related communication.

[0082] An avatar (also referred to as an animated avatar) refers to a virtual image or an avatar on the network. Avatar technology is to map the facial expressions, actions, and voices of a user in real time to an avatar representation (also referred to as an avatar model, a base avatar, etc.), and generate an avatar, so that the avatar can imitate and respond to the real-time behavior of the user.

[0083] The communication service, also referred to as a call, refers to a service such as a voice call, a video call, or data interaction between a terminal as an originating party or a terminating party and other one or more terminals through a communication network. The call can cover the entire process from call setup (e.g., dialing) to call end, or part of the process from call setup to call end. The call can be a one-to-one call or a one-to-many (e.g., a conference) call. The embodiments of the present application take a one-to-one call as an example, but the related solutions can be applied to a one-to-many call.

[0084] The communication network can be an Internet Protocol (IP) Multimedia Subsystem (IMS) network, where the IMS network is an open system based on IP and providing various multimedia services to users. Furthermore, the communication network may include one or more network devices.

[0085] For example, see Figure 2B As shown, the communication network may include call session control function (CSCF) network elements, IMS access media gateway (AGW), home subscriber server (HSS) network elements, IMS application server (AS) network elements, MF network elements, etc.

[0086] Figure 2C The communication network shown is in Figure 2B Based on the illustrated communication network, additional network elements related to data channels (DC) are added, such as the data channel signaling function (DCSF) network element, the data channel application repository (DCAR) network element, and DC AS. Optionally, Figure 2C The illustrated communication system also includes network exposure function (NEF) network elements, NRF network elements, and BAR network elements.

[0087] This is for Figures 2A-2C A brief introduction to each network element shown (or referred to as a functional network element, functional entity, node, device, etc.):

[0088] 1、Terminal: A terminal can be referred to as a user equipment (UE), terminal device, terminal apparatus, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc., which is a device that has a wireless or wired communication ability. For example, a terminal can be connected with a wireless access device through an air interface, or the terminal can be connected with a wired access device through a wired interface. In terms of product form, a terminal can include a handheld device with a communication function, a vehicle-mounted device, a wearable device, or a computing device, etc. Exemplarily, a terminal can be a mobile phone, a pad, a computer (such as a notebook computer, a palm computer, etc.) with a wireless communication function, a mobile internet device (MID), a virtual reality (VR) terminal, an augmented reality (AR) terminal, a smart watch, a smart bracelet, smart glasses, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a SIP phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with a wireless communication function, another processing device connected to a wireless modem, a terminal in an internet of things (IoT) system, a desktop computer, or a terminal defined in a 3rd generation partnership project (3GPP) standard specification, etc., without limitation.

[0089] 2、CSCF network element, which is a functional entity inside IMS and is the core of the whole IMS. It is mainly responsible for processing signaling control in the process of multimedia call session. It manages user authentication of IMS, quality of service (QoS) of IMS bearer plane, control of session initiation protocol (SIP) session in cooperation with other network elements, and service negotiation and resource allocation, etc. Among them, the CSCF network element can communicate with the terminal, and the CSCF network element can communicate with the gateway device. For example, the CSCF network element can select the gateway device for communication with the terminal, and the CSCF network element can allocate routing information, such as IP address or port, for the terminal and the gateway device.

[0090] As an example but not limitation, the CSCF network element is divided into proxy CSCF network element (P-CSCF network element), interrogating CSCF network element (I-CSCF network element), serving CSCF network element (S-CSCF network element), etc. according to functions. Among them, the P-CSCF network element is the entry node of the user accessing the IMS network, and is mainly responsible for forwarding SIP signaling between the IMS user and the home network. The I-CSCF network element is the unified entry point of the IMS user's home network, and is responsible for allocating or querying the S-CSCF network element serving the user. The S-CSCF network element is the unified entry point of the IMS user's home network, and is responsible for allocating or querying the S-CSCF network element serving the user.

[0091] It can be understood that the above-mentioned P-CSCF network element, S-CSCF network element and I-CSCF network element can be independently configured in different entities, or can be integrated in the same entity, and the present application does not make any limitation.

[0092] 3、IMS AGW: IMS AGW can provide IMS network access gateway and media gateway functions.

[0093] 4、DCSF network element: used to provide data channel signaling control function.

[0094] 5、DCAR network element: used to store the warehouse of data channel application (DC App).

[0095] 6、HSS network element: the HSS network element in IMS is a database for storing user information, and the user saves user data. As an example but not limitation, the user data can include information of the data channel service used by the user and the operator.

[0096] 7、IMS AS: IMS AS is an application layer device in the IMS system, which is located at the uppermost layer, and provides basic services and supplementary services, such as multimedia conference, fusion communication, short message gateway, standard operator, and the like. The IMS network is an open system based on IP bearing and providing various multimedia services to users. The IMS AS interacts with the CSCF network element, and then triggers and executes various network services. In addition, the terminal communicates with the IMS AS, and the IMS AS can establish a data channel for the terminal.

[0097] For example, the IMS AS can be a multimedia telephone application server (MMTEL AS) or a telephone application server (TAS).

[0098] 8、DC AS: also known as extended reality application server (XRAS). The DC AS is used to provide data channel service logic. It can be understood that the DC AS can be deployed in the IMS network, in which case the DC AS can be directly connected to other network elements in the IMS network through an interface (such as a service interface); or the DC AS can also be deployed outside the IMS network, in which case the DC AS can be connected to other network elements in the IMS network through the NEF network element (or the IMS border network management).

[0099] For example, the DC AS can download an avatar ID list from the BAR network element and send it to the terminal. For example, the DC AS can also download an avatar model from the BAR network element based on the avatar ID.

[0100] 9、NEF network element: the NEF network element is used to safely open various services of the 5GC network to third parties.

[0101] 10、MF network element: also known as a media server, which is used to provide media resource management functions, including media resource management of media channels and media resource management of data channels. Further, the MF network element can drive a rendered animation avatar based on an avatar model and user information (such as action information, language information, expression information, text information, and the like). For example, the MF network element can also download an avatar model from the BAR network element based on the avatar ID.

[0102] 11. BAR network element: used to save digital human model, and the identification of digital human (which can be expressed as Avatar ID). Further, one terminal corresponds to one or more digital human models, and each digital human model is identified by an Avatar ID. The BAR network element also saves the identification list of digital human of each terminal (which can be expressed as Avatar ID list).

[0103] 12. NRF network element: used to register, manage and detect the state of network function (NF) network element. Each NF must be registered through the NRF network element when starting to be able to provide services.

[0104] The network architecture applied to the embodiments of the present application is only an example, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiments of the present application. That is, the network architecture and business scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems. The network elements or devices listed in the above network architecture are only exemplary, and the network architecture applicable to the present application can also include other network elements or devices, which are not limited by the present application. The naming of the above-mentioned network elements or devices is only defined for the convenience of distinguishing different functions, and should not constitute any limitation on the present application. Other naming can also be used in other network architectures.

[0105] Further, the digital human call is similar to the video call, both of which provide visual and interactive communication and provide real-time images of the communication user about his / her mood, attention and other social information. Unlike the video call, the digital human call presents the virtual animated digital human (digital human image) processed by the terminal or network device (such as MF network element) to the opposite user, rather than the real image in the video call.

[0106] In one possible flow of digital human call, after the first terminal initiates the digital human call to the second terminal, the MF network element downloads the digital human model from the BAR network element, and obtains the user information from the first terminal. The MF network element renders the digital human according to the digital human model and the user information, and then combines the scene to render the digital human. The MF network element sends the digital human combined with the scene to the second terminal.

[0107] Further, the digital human model is a 2D or 3D model or figure (simple understanding is a digital human template) of the first terminal generated online or offline, which can be stored in the BAR network element (or, digital asset repository (DAR), digital asset container (DAC), DCAR network element). The BAR network element can be provided by the network, a third-party entity outside the network, or a local storage device of the terminal.

[0108] The user information comes from the sensing devices of the first terminal, such as a camera and a special motion capture device, which can capture the action information of the user's head (face), body, legs, hands, etc. using the first terminal, and a microphone can capture the language information of the user using the first terminal. The first terminal sends the processed (for generating a digital human) user information to the MF network element.

[0109] It should be noted that the digital human can also be generated by the first terminal or the second terminal, at which time the first terminal or the second terminal needs to download the digital human model from the BAR network element and generate the digital human. If the digital human is generated by the first terminal, the first terminal generates the digital human based on the downloaded digital human model and the user information collected by the sensor, and sends it to the second terminal after combining the scene; if the digital human is generated by the second terminal, the second terminal can generate the digital human based on the downloaded digital human model and the user information from the first terminal, and then display the digital human after combining the scene.

[0110] In this application, rendering and driving are considered as the same operation, that is, a certain entity needs to generate a digital human based on the digital human model and the user information and combine the environmental information, the English name is animate, and the rendering is used to describe in the following.

[0111] The present application provides a method of communication for ensuring the security in the rendering process.

[0112] The method is applied to the scenario of the first terminal and the second terminal conducting a digital human related call. Exemplarily, the first terminal initiates a digital human related call to the second terminal as a calling party, and the second terminal receives the digital human related call as a called party.

[0113] Figure 3A flowchart of a communication method is exemplarily provided in the present application, which can be performed by a first communication device and a second communication device, wherein the first communication device can be a first terminal or a part (e.g. a chip) of the first terminal; the second communication device can be a DC AS or a part (e.g. a chip) of the DC AS. For the convenience of description, the first communication device is exemplarily taken as a first terminal and the second communication device is exemplarily taken as a DC AS. Further, the method focuses on how the first terminal obtains information of a first entity and generates a token according to the information of the first entity.

[0114] The network device involved in the method includes a DC AS and a MF network element related to a call.

[0115] Exemplarily, the DC AS related to the call refers to a DC AS used to provide data channel service logic for the call, for example, when the first terminal and the second terminal are deployed in the same IMS network, the DC AS related to the call can be a DC AS inside the IMS network; when the first terminal and the second terminal are deployed in different IMS networks, the DC AS related to the call can be a DC AS inside the same IMS network as the first terminal. The MF network element related to the call refers to a MF network element used to provide media resource management function for the call.

[0116] The first terminal and the DC AS establish a first ADC, which is used for rendering negotiation. The first terminal and the MF network element establish end-to-end protection, and the MF network element and the DC AS establish end-to-end protection. When the first terminal sends a message to the DC AS through the first ADC, the first terminal can send the message to the MF network element, and the MF network element forwards the message to the DC AS, for example, the MF network element does not analyze the message, and the message is transparently transmitted in the MF network element. When the DC AS sends a message to the first terminal through the first ADC, the DC AS can send the message to the MF network element, and the MF network element forwards the message to the first terminal, for example, the MF network element does not analyze the message, and the message is transparently transmitted in the MF network element.

[0117] In step 301, the first terminal sends a capability negotiation request to the DC AS.

[0118] Correspondingly, the DC AS receives the capability negotiation request from the first terminal.

[0119] The capability negotiation request can also be referred to as a negotiation request, a rendering negotiation request, a driving negotiation request, an animation negotiation request, and the like.

[0120] The capability negotiation request is used for negotiation of rendering of the digital person. Exemplarily, the capability negotiation request is used for negotiation of a rendering data type, a rendering entity, and the like used in the rendering of the digital person. The rendering entity refers to an entity used for generating the digital person according to user information and a digital person model, and the rendering entity can be the first terminal, the second terminal, or an MF network element related to digital person communication between the first terminal and the second terminal. The rendering data type is, for example, text, language, action, and the like. For the convenience of description, the digital person rendered this time is referred to as a first digital person, and the model used for generating the first digital person is referred to as a first digital person model, that is, the first digital person model is used for rendering of the first digital person.

[0121] The capability negotiation request carries an identifier (avatar id) of the first digital person. Exemplarily, the identifier of the first digital person is used for retrieving the first digital person model, and the identifier of the first digital person can also be referred to as an identifier of the first digital person model or an identifier of the model. Exemplarily, the capability negotiation request can also carry negotiation parameters of the first terminal. Exemplarily, the negotiation parameters of the first terminal include a rendering capability of the first terminal and / or a candidate entity preferred (English representation: prefer, and the present application can also replace “preferred” with “not preferred”) by the first terminal, wherein the candidate entity includes one or more of the MF network element, the first terminal, and the second terminal.

[0122] The rendering capability of the first terminal includes one or more of the following:

[0123] (1) Whether the first terminal supports rendering, that is, whether the first terminal has the capability of being a rendering entity. For example, the rendering capability of the first terminal includes 1 bit of indication information, when the 1 bit is 1, it represents that the first terminal supports rendering; when the 1 bit is 0, it represents that the first terminal does not support rendering. Of course, there can be other indication manners, which will not be exemplified herein.

[0124] (2) the rendering data requirement of the first terminal, wherein the rendering data requirement of the first terminal includes a data type required by the first terminal when generating the first digital human (i.e., when rendering the first digital human) and / or a minimum number of sensors corresponding to the data type required by the first terminal when generating the first digital human (i.e., when rendering the first digital human). For example, the rendering data requirement of the first terminal includes an action type, and the minimum number of sensors corresponding to the action type is 3, i.e., the data type required by the first terminal when rendering the first digital human is the action type, and the data of this type is required to be collected by at least 3 sensors.

[0125] (3) the remaining computing resources of the first terminal, wherein the remaining computing resources of the first terminal include one or more of the current available resources of the CPU of the first terminal, the current available power consumption of the GPU, the current available computing power of the GPU, or the current available memory resources.

[0126] (4) the score of the remaining computing resources of the first terminal. The score can be obtained by the first terminal scoring the remaining computing resources of the first terminal according to a preset scoring system. For example, the preset scoring system is unified by the first terminal, the second terminal, and the MF network element.

[0127] For example, the negotiation parameter of the first terminal includes "support rendering, and the recommended entity is the first terminal", which means that the first terminal supports rendering and recommends itself as the rendering entity. For another example, the negotiation parameter of the first terminal includes "do not support rendering, and the recommended entity is the MF network element", which means that the first terminal does not support rendering and recommends the MF network element as the rendering entity.

[0128] For example, the first ADC is established between the first terminal and the DC AS, and the first terminal sends a capability negotiation request to the DC AS. Specifically, the first terminal sends a capability negotiation request to the MF network element, and the MF network element forwards the capability negotiation request to the DC AS, e.g., the MF network element does not analyze the capability negotiation request, and the capability negotiation request is transparently transmitted in the MF network element.

[0129] Step 302: The DC AS sends a capability negotiation response to the first terminal.

[0130] Correspondingly, the first terminal receives the capability negotiation response from the DC AS.

[0131] The capability negotiation response includes the information of the first entity, which can be the type of the first entity and / or the identity (ID) of the first entity.

[0132] The capability negotiation response can be referred to as a negotiation response, a rendering negotiation response, a driving negotiation response, an animation negotiation response, and the like. The information of the first entity can be referred to as information of a subject, information of an authorized entity, a rendering negotiation parameter, a rendering negotiation result, and the like.

[0133] The first entity is an entity for downloading the first digital human model. The first entity can be one of a DC AS, a MF network element, a first terminal, and a second terminal related to a current call of the first terminal and the second terminal.

[0134] It can be understood that the first entity can be a rendering entity or a proxy entity of the rendering entity. When the first entity is the rendering entity, the first entity can be the first terminal, the second terminal, or the MF network element, and the rendering entity can request to download the first digital human model. When the first entity is the proxy entity of the rendering entity, the first entity can be the DC AS, and further, the rendering entity can be the first terminal, the second terminal, or the MF network element, and the DC AS can proxy the rendering entity to request to download the first digital human model.

[0135] In addition, the capability negotiation response further includes information of an entity for storing the first digital human model. The entity for storing the first digital human model can be a first BAR network element, and the information of the first BAR network element can be an identifier of the first BAR network element.

[0136] The first ADC is established between the first terminal and the DC AS, and the first terminal can send a message to the DC AS through the first ADC. When the DC AS sends the capability negotiation response to the first terminal, the DC AS can send the capability negotiation response to the MF network element, and the MF network element forwards the capability negotiation response to the first terminal, for example, the MF network element does not analyze the capability negotiation response, and the capability negotiation response is transparently transmitted in the MF network element.

[0137] Optionally, before step 302, one or more of the following steps A, B, and C are further included.

[0138] Step A, the DC AS determines the information of the first entity in response to the capability negotiation request.

[0139] That is, the DC AS receiving the capability negotiation request is the trigger condition for the DC AS determining the information of the first entity. When determining the information of the first entity, the DC AS can determine the information of the first entity in combination with the parameters in the capability negotiation request, or can determine the information of the first entity without combination with the parameters in the capability negotiation request. The following sub-implementation modes 1 to 3 are explained.

[0140] Implementation mode 1, the DC AS determines the information of the first entity according to the first configuration information. In this implementation mode, the DC AS does not determine the information of the first entity in combination with the parameters in the capability negotiation request.

[0141] For example, the first configuration information includes one of the following configurations:

[0142] Configuration 1, selecting the MF network element as the rendering entity. That is, when the first configuration information of the DC AS is the configuration 1, the DC AS can determine the MF network element as the rendering entity. In addition, the "MF network element" in the configuration 1 can also be replaced by "first terminal" or "second terminal".

[0143] Configuration 2, priority sorting of multiple entities in the DC AS, the MF network element, the first terminal and the second terminal.

[0144] For example, the priority sorting included in the configuration 2 is in turn the MF network element, the first terminal and the second terminal. When the first configuration information of the DC AS is the configuration 2, the DC AS can determine whether the MF network element can be the rendering entity according to the priority sorting, and further, if the DC AS determines that the MF network element can be the rendering entity, the DC AS determines the MF network element as the rendering entity; if the DC AS determines that the MF network element cannot be the rendering entity, the DC AS continues to determine whether the first terminal can be the rendering entity, until the rendering entity is determined.

[0145] Among them, the DC AS includes a preset rendering requirement, for example, the minimum requirement for rendering a digital person. When the DC AS determines whether the MF network element can be the rendering entity, the DC AS can specifically determine whether the rendering capability of the MF network element can meet the preset rendering requirement, and if the DC AS determines that the rendering capability of the MF network element meets the preset rendering requirement, the DC AS determines that the MF network element can be the rendering entity; if the DC AS determines that the rendering capability of the MF network element does not meet the preset rendering requirement, the DC AS determines that the MF network element cannot be the rendering entity. The DC AS determines whether the first terminal or the second terminal can be the rendering entity in a similar manner to the MF network element. The rendering capability of the MF network element, the first terminal and the second terminal is described in the following implementation mode 2.

[0146] In a possible implementation, the DC AS determines the information of the first entity according to the negotiation parameter of the first terminal in the capability negotiation request.

[0147] In one possible example, the DC AS further obtains the negotiation parameter of the MF network element and the negotiation parameter of the second terminal, and then determines the information of the first entity according to the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal.

[0148] The negotiation parameter of the MF network element includes the rendering capability of the MF network element and / or the candidate entity recommended by the MF network element. The negotiation parameter of the second terminal includes the rendering capability of the second terminal and / or the candidate entity recommended by the second terminal. The negotiation parameter of the MF network element or the negotiation parameter of the second terminal can refer to the description of the negotiation parameter of the first terminal in step 301. The candidate entity recommended by the MF network element or the candidate entity recommended by the second terminal can refer to the description of the candidate entity recommended by the first terminal in step 301.

[0149] For example, the DC AS obtains the negotiation parameter of the MF network element and the negotiation parameter of the second terminal from the MF network element.

[0150] For example, the DC AS sends a first obtaining request to the MF network element, where the first obtaining request is used to request the negotiation parameter of the MF network element and the negotiation parameter of the second terminal. The first obtaining request includes the identifier of the MF network element and the identifier of the second terminal. Correspondingly, the MF network element sends a first obtaining response to the DC AS, where the first obtaining response includes the negotiation parameter of the MF network element and the negotiation parameter of the second terminal. For example, when the MF network element receives the first obtaining request, the MF network element sends a second obtaining request to the second terminal according to the first obtaining request, where the second obtaining request is used to request the negotiation parameter of the second terminal, and the second obtaining request includes the identifier of the second terminal. Correspondingly, the second terminal sends a second obtaining response to the MF network element, where the second obtaining response includes the negotiation parameter of the second terminal, and the MF network element sends the first obtaining response to the DC AS according to the second obtaining response.

[0151] For another example, the DC AS sends an obtaining request to the MF network element, where the obtaining request is used to request the negotiation parameter of the second terminal, and the obtaining request includes the identifier of the second terminal. Correspondingly, the MF network element forwards the obtaining request to the second terminal, the second terminal sends an obtaining response to the MF network element, and the obtaining response includes the negotiation parameter of the second terminal. The MF network element carries the negotiation parameter of the MF network element in the obtaining response when forwarding the obtaining response.

[0152] Further, the DC AS pre-configures the negotiation parameter of the MF network element in the DC AS. The DC AS obtains the negotiation parameter of the second terminal from the MF network element. For example, the DC AS sends a request for obtaining to the MF network element, the request for obtaining is used to request the negotiation parameter of the second terminal, and the request for obtaining includes the identity of the second terminal. Correspondingly, the MF network element forwards the request for obtaining to the second terminal. Then, the second terminal sends a response for obtaining to the MF network element, and the MF network element forwards the response for obtaining to the DC AS, and the response for obtaining includes the negotiation parameter of the second terminal.

[0153] The request for obtaining can also be referred to as an animation capability request, and the response for obtaining can also be referred to as an animation capability response.

[0154] When the DC AS determines the information of the first entity according to the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal, the following examples can be included at least:

[0155] Example 1: The negotiation parameter of each entity carries the rendering capability of the entity, but does not carry the candidate entity recommended by the entity. Then, the DC AS can select the entity with stronger rendering capability as the first entity according to the rendering capability of each entity.

[0156] For example, the DC AS selects the entity (for example, the MF network element) with stronger rendering capability as the first entity according to the rendering capability of the first terminal, the rendering capability of the second terminal and the rendering capability of the MF network element.

[0157] Further, the rendering capability of the entity can not be carried in the negotiation parameter of the entity, and at this time, the DC AS can consider that the entity does not support rendering. Then, the DC AS selects the entity with stronger rendering capability as the first entity from the entities supporting rendering. For example, the negotiation parameter of the first terminal does not carry the rendering capability of the first terminal, the negotiation parameter of the second terminal carries the rendering capability of the second terminal, and the negotiation parameter of the MF network element carries the rendering capability of the MF network element. The DC AS can default that the first terminal does not support rendering, and then selects the entity (for example, the MF network element) with stronger rendering capability as the first entity according to the rendering capability of the second terminal and the rendering capability of the MF network element.

[0158] In Example 2, the negotiation parameter of each entity carries the candidate entity recommended by the entity, but does not carry the rendering capability of the entity. For example, the DC AS determines the first entity according to the candidate entity recommended by the first terminal, for example, the DC AS selects the candidate entity recommended by the first terminal as the first entity. Alternatively, the DC AS determines which entity has the most votes, and then selects the entity as the first entity, for example, the first terminal recommends the MF network element and the first terminal as the first entity, the second terminal recommends the MF network element and the second terminal as the first entity, and the MF network element recommends the MF network element as the first entity, and then the DC AS determines that the MF network element has the most votes, and selects the MF network element as the first entity.

[0159] In Example 3, the negotiation parameter of each entity carries the candidate entity recommended by the entity, and the rendering capability of the entity, and the DC AS selects the recommended entity supporting rendering.

[0160] In combination with the example of the negotiation parameter of the first terminal, the negotiation parameter of the MF network element, and the negotiation parameter of the second terminal provided in Table 1, the first entity determined by the DC AS is explained.

[0161] For example, when the negotiation parameter of the first terminal includes "supporting rendering, and the recommended entity is the first terminal", the negotiation parameter of the second terminal includes "supporting rendering, and the recommended entity is the second terminal", and the negotiation parameter of the MF network element includes "supporting rendering, and the recommended entity is the MF network element", the DC AS can select any one of the MF network element, the first terminal, and the second terminal as the first entity. That is, when each entity supports rendering and recommends itself as the first entity, the DC AS can select any one of the MF network element, the first terminal, and the second terminal as the first entity.

[0162] For another example, when the negotiation parameter of the first terminal includes "supporting rendering, and the recommended entity is the first terminal or the MF network element", the negotiation parameter of the second terminal includes "supporting rendering, and the recommended entity is the second terminal or the MF network element", and the negotiation parameter of the MF network element includes "supporting rendering, and the recommended entity is the MF network element", the DC AS can select any one of the MF network element, the first terminal, and the second terminal as the first entity. That is, when each terminal supports rendering and recommends an entity other than the opposite terminal as the first entity, the DC AS can select any one of the MF network element, the first terminal, and the second terminal as the first entity. Other examples can also be referred to Table 1, and will not be listed one by one.

[0163] Table 1

[0164]

[0165]

[0166] It should be noted that in the negotiation parameter of the first terminal, the "candidate entity recommended by the first terminal" can also be replaced by "candidate entity not recommended by the first terminal", for example, the negotiation parameter of the first terminal includes "not recommended second terminal"; or can also be replaced by "whether the first terminal recommends the second terminal and / or the MF network element", for example, the negotiation parameter of the first terminal includes "recommend the second terminal and the MF network element as the first entity", for another example, the negotiation parameter of the first terminal includes "recommend the MF network element as the first entity, and do not recommend the second terminal as the first entity". The negotiation parameter of the MF network element or the negotiation parameter of the second terminal is similar to the negotiation parameter of the first terminal, and will not be repeated.

[0167] In addition, the DC AS can also obtain one or more of the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal, and then determine the information of the first entity according to the negotiation parameter obtained by the DC AS. For example, the DC AS obtains the negotiation parameter of the first terminal from the capability negotiation request, and obtains the negotiation parameter of the MF network element from the acquisition response, and then the DC AS determines the information of the first entity according to the negotiation parameter of the first terminal and the negotiation parameter of the MF network element. For specific implementation, please refer to the above examples 1 to 3.

[0168] In this implementation mode 2, the first entity can be a rendering entity.

[0169] Of course, the above are all exemplary descriptions, and the present application can also have other implementation modes, which will not be repeated one by one.

[0170] Implementation mode 3, the DC AS requests the information of the first entity from the NRF network element.

[0171] In one possible example, the DC AS includes a preset rendering requirement, which can be considered as the minimum requirement for rendering the digital person, for example, the required data type for rendering, and the minimum number of sensors corresponding to the required data type for rendering.

[0172] In one possible example, when the DC AS determines that none of the rendering capabilities in the negotiation parameter obtained by it meets the preset rendering requirement, the DC AS sends a first request to the NRF network element, the first request includes the preset rendering requirement, and the first request is used to request the information of the first entity that meets the preset rendering requirement. Correspondingly, the NRF network element receives the first request, determines the information of the first entity according to the preset rendering requirement in the first request, sends a first response to the DC AS, and the first response includes the information of the first entity. The DC AS receives the first response from the NRF network element.

[0173] Exemplarily, the DC AS obtains the negotiation parameter of the first terminal, the negotiation parameter of the MF network element and the negotiation parameter of the second terminal, and determines that the rendering capability in the negotiation parameter of the first terminal, the rendering capability in the negotiation parameter of the MF network element and the rendering capability in the negotiation parameter of the second terminal all do not meet the preset rendering requirement, and requests the information of the first entity from the NRF network element.

[0174] Exemplarily, the DC AS obtains the negotiation parameter of the first terminal and the negotiation parameter of the MF network element, and determines that the rendering capability in the negotiation parameter of the first terminal and the rendering capability in the negotiation parameter of the MF network element all do not meet the preset rendering requirement, and requests the information of the first entity from the NRF network element.

[0175] For the NRF network element, the NRF network element can determine a new MF network element from the network according to the preset rendering requirement, take the new MF network element as the first entity, and then send the information of the first entity to the DC AS. Exemplarily, the first terminal also needs to establish a second ADC with the DC AS based on the new MF network element (instead of establishing a second ADC with the DC AS based on the original MF). Exemplarily, the first request can be a MF network element modification request message, and the first response can be a MF network element modification response message. For convenience of description, the original MF network element is recorded as a first MF network element, and the new MF network element is recorded as a second MF network element, the first MF network element and the second MF network element are different, that is, the MF network element used for information transmission in the first ADC is the first MF network element, and the MF network element used for information transmission in the second ADC is the second MF network element.

[0176] Alternatively, the NRF network element can determine an entity (also referred to as a compute node function (CNF) network element) from the network for rendering according to the preset rendering requirement, take the CNF network element as the first entity, and then send information of the first entity to the DC AS. Further, the CNF network element carries information of the first entity in the capability negotiation response, and the first terminal can also generate a token based on the information of the CNF network element, so that the CNF network element requests the first digital human model from the BAR network element according to the token, and the CNF network element generates the first digital human according to the first digital human model. In addition, in this case, the NRF network element can also determine a CNF network element from the network according to the preset rendering requirement, and then send information of the CNF network element to the DC AS. The DC AS sends the information of the CNF network element to the first MF network element, and takes the first MF network element as the first entity. Further, the first MF network element carries information of the first MF network element in the capability negotiation response, and the first terminal can generate a token based on the information of the first MF network element. The first MF network element requests the first digital human model according to the token, sends the requested first digital human model to the CNF network element, and the CNF network element generates the first digital human according to the first digital human model. The CNF network element sends the first digital human to the first MF network element.

[0177] In addition, in another implementation, when determining a new MF network element or CNF network element, the NRF network element does not need to consider the preset rendering requirement, but the DC AS determines whether the new MF network element or CNF network element meets the preset rendering requirement. For example, the NRF network element returns the information (such as the identifier and rendering capability) of the determined network element to the DC AS through the first response. The DC AS determines whether the rendering capability of the network element meets the preset rendering requirement according to the preset rendering requirement. If yes, the network element is determined as the first entity. Otherwise, the DC AS sends the first request to the NRF network element again until the DC AS requests an entity with rendering capability meeting the preset rendering requirement from the NRF network element. In this scenario, the first request can not carry the preset rendering requirement. Alternatively, when the NRF network element determines that there is no network element meeting the preset rendering requirement in the network according to the preset rendering requirement, the NRF network element can return a failure indication to the DC AS, which indicates that there is no network element meeting the preset rendering requirement in the current network.

[0178] In addition, the DC AS can also not need to determine whether the rendering capability in the negotiation parameter obtained by the DC AS meets the preset rendering requirement before sending the first request to the NRF network element. For example, the DC AS sends the first request to the NRF network element in response to the capability negotiation request. For example, the first request includes the preset rendering requirement. The NRF network element sends the first response to the DC AS, and the first response includes information of the first entity.

[0179] Step B, the DC AS determines the information of the first BAR network element in response to the capability negotiation request.

[0180] That is, the DC AS receiving the capability negotiation request serves as a trigger condition for the DC AS determining the information of the first BAR network element.

[0181] When determining the information of the first BAR network element, the DC AS can specifically determine the information of the first BAR network element according to the identifier of the first digital human in the capability negotiation request and the second configuration information. The information of the first BAR network element can specifically be an identifier of the first BAR network element.

[0182] For example, the BAR network element 1 stores digital human models 1 to 10, the BAR network element 2 stores digital human models 11 to 20, and the second configuration information includes a list 1 corresponding to the BAR network element 1 and a list 2 corresponding to the BAR network element 2. The list 1 includes identifiers of the respective digital humans corresponding to the digital human models 1 to 10, and the list 2 includes identifiers of the respective digital humans corresponding to the digital human models 11 to 20. Further, the DC AS can determine the identifier of the BAR network element (i.e., the first BAR network element) storing the first digital human model according to the identifier of the first digital human and the list of identifiers of the respective digital humans corresponding to the digital human models stored in each BAR network element. In the above example, the first digital human is digital human 5, and the first BAR network element is the BAR network element 1.

[0183] The information of the first BAR network element can also be referred to as information of a service provider (English: audience) or information of a serving entity. For example, when the capability negotiation response includes the information of the first entity and the information of the first BAR network element, both the information of the first entity and the information of the first BAR network element can be considered as rendering negotiation parameters or rendering negotiation results.

[0184] Step C, the DC AS determines whether the first terminal has the right to use the first digital human model in response to the capability negotiation request.

[0185] That is, the DC AS receiving the capability negotiation request serves as a trigger condition for the DC AS determining whether the first terminal has the right to use the first digital human model.

[0186] For example, the DC AS stores a list of the digital person identifiers corresponding to each terminal that has the use permission. The DC AS can determine the list of the digital person identifiers corresponding to the first terminal according to the identifier of the first terminal, and then determine whether the identifier of the first digital person is in the list of the digital person identifiers corresponding to the first terminal. If yes, it is determined that the first terminal has the permission to use the first digital person model; otherwise, it is determined that the first terminal does not have the permission to use the first digital person model.

[0187] For example, the DC AS includes the list of the digital person identifiers corresponding to terminal 1 to terminal 3 respectively. The list of the digital person identifiers corresponding to terminal 1 includes the identifiers of digital person 1 to digital person 3, the list of the digital person identifiers corresponding to terminal 2 includes the identifiers of digital person 2 to digital person 3, and the list of the digital person identifiers corresponding to terminal 3 includes the identifiers of digital person 1 to digital person 4. Further, the first terminal is terminal 1, and the first digital person is digital person 1. The DC AS can determine that the list of the digital person identifiers corresponding to terminal 1 includes the identifier of the first digital person (i.e., the identifier of digital person 1) according to the identifier of the first terminal (i.e., terminal 1), and determine that the first terminal has the permission to use the first digital person model. For another example, the first terminal is terminal 1, and the first digital person is digital person 4. The DC AS determines that the list of the digital person identifiers corresponding to terminal 1 does not include the identifier of the first digital person (i.e., the identifier of digital person 4), and determines that the first terminal does not have the permission to use the first digital person model.

[0188] In this way, it is avoided that the first terminal sends the identifier of the digital person of another terminal, and thus the entity renders the digital person of the other terminal or the digital person model of the other terminal is leaked.

[0189] Further, the DC AS determines whether the first terminal has the permission to use the first digital person model after receiving the capability negotiation request. The DC AS can discover early that the first terminal does not have the permission to use the first digital person model, avoid returning the information of the first entity and / or the information of the first BAR network element to the first terminal and subsequent rendering process, and help save message transmission resources.

[0190] In addition, in step C, after determining that the first terminal has the permission to use the first digital person model, the DC AS can additionally store the mapping relationship between the identifier of the first terminal and the identifier of the first digital person. The identifier of the first digital person does not need to be carried in the token sent by the first terminal subsequently.

[0191] Further, if the DC AS selects the MF network element or the second terminal as the first entity, the DC AS can also send the rendering data requirement (e.g., the data type required by the first entity when generating the first digital human) of the first entity as a parameter in the capability negotiation response to the first terminal. Correspondingly, when collecting user information, the first terminal can specifically collect corresponding user information according to the data type required by the first entity, so as to help reduce the workload of the first terminal; or the first terminal collects all types of user information, and then sends corresponding user information according to the data type required by the first entity, so as to help reduce the data amount of network transmission messages.

[0192] In another example, if the second terminal is the rendering entity, and the user information and the token are forwarded by the MF network element, the first terminal can also add the data type required by the second terminal for rendering in the token, so that the MF network element can receive all types of user information collected by the first terminal, and based on the data type required by the second terminal for rendering in the token, the MF network element can delete all types of user information to obtain the data type required by the second terminal, and send the data type required by the second terminal to the second terminal, so as to help reduce the data amount of transmission messages.

[0193] Step 303, the first terminal generates a token according to the information of the first entity.

[0194] The token is used to authorize the first entity to download the first digital human model. For example, the token includes the information of the first entity. For example, the token can also carry the identifier of the first digital human.

[0195] When the DC AS also determines the information of the entity for storing the first digital human model (e.g., the information of the first BAR network element), the token can also include the information of the entity for storing the first digital human model. Correspondingly, the token is used to authorize the first entity to download the first digital human model from the information of the entity for storing the first digital human model.

[0196] The following exemplary provides two forms of tokens:

[0197] Form 1: The token includes an authorized avatar field, an issuer field, a subject field, an audience field, and an expiration time field. The avatar field includes the identifier of the first digital human, the issuer field includes the identifier of the first terminal, the subject field includes the identifier of the first entity, the audience field includes the identifier of the first BAR network element, and the expiration time field includes t1.

[0198] The token includes the identity of the first digital human, the identity of the first terminal, the identity of the first entity, the identity of the first BAR network element, and t1. That is, the positions of each information in the token are pre-set, and then the first terminal fills the identity of the first digital human, the identity of the first terminal, the identity of the first entity, the identity of the first BAR network element, and t1 into the corresponding positions of the token respectively.

[0199] In step 304, the first terminal sends the token.

[0200] When the first terminal sends the token, specifically, the first terminal can send a re-invite message including the token, and the re-invite message is used to establish a second ADC.

[0201] It can be understood that steps 301 to 303 belong to a rendering capability negotiation process. Before the rendering capability negotiation process, the first terminal and the DC AS have established a first ADC, and the first ADC is used for rendering capability negotiation. After the rendering capability negotiation process, the first terminal and the DC AS also need to establish a second ADC, and the second ADC is used to transmit service data, for example, data between the first terminal and the second terminal (such as data used for rendering by the rendering entity (for example, user information), a digital human after rendering, etc.).

[0202] For example, after the rendering capability negotiation process, the first ADC is removed.

[0203] It is worth noting that if the first entity is a second MF network element (implementation mode 3 of step A), after the rendering capability negotiation process, the first terminal needs to establish a second ADC with the DC AS based on the second MF network element.

[0204] Based on the first entity being an MF network element, a DC AS, a second terminal, or a first terminal, the way in which the first entity obtains the token is explained as follows:

[0205] When the first entity is an MF network element, the first terminal can first send a re-invite message to the IMS AS, and then the IMS AS sends a media resource reserving message to the MF network element, and the media resource reserving message includes the token.

[0206] It should be noted that after receiving the media resource reserving message, the MF network element can also perform the following check 1 and / or check 2:

[0207] Check 1: The MF network element checks whether the digital human identity in the token is consistent with the digital human identity previously checked by the DC AS;

[0208] Check 2, the MF network element checks whether the digital human identifier in the media resource reservation message is consistent with the digital human identifier checked by the DC AS previously.

[0209] For convenience of description, check 1 and check 2 are taken as examples for illustration. Herein, the digital human identifier in the token or the digital human identifier in the media resource reservation message is collectively referred to as the digital human identifier to be checked.

[0210] Exemplarily, the MF network element can perform check 1 and / or check 2 based on the following manners:

[0211] Manner (1), the MF network element sends a digital human identifier check result request to the DC AS, the digital human identifier check result request carrying the identifier of the digital human to be checked and the identifier of the first terminal, and the DC AS returns a digital human identifier check result, the digital human identifier check result being used to indicate whether the identifier of the digital human to be checked is checked successfully.

[0212] Manner (2), the MF network element sends a digital human identifier list request to the DC AS / DCSF network element, the digital human identifier list request carrying the identifier of the first terminal, and the DC AS / DCSF network element returns a digital human identifier list corresponding to the first terminal to the MF network element. Subsequently, the MF network element determines whether the identifier of the digital human to be checked is in the digital human identifier list corresponding to the first terminal.

[0213] It can be understood that when the MF network element determines that check 1 and / or check 2 is failed, the MF network element can no longer perform the subsequent rendering process.

[0214] When the first entity is the DC AS, the first terminal can first send a re-invite message to the IMS AS, and the IMS AS sends a media resource reservation to the MF network element, the media resource reservation including the token. The MF network element forwards the token to the DC AS after obtaining the token. Exemplarily, the MF network element can also perform check 1 and / or check 2 after receiving the media resource reservation message. It can be understood that when the MF network element determines that check 1 and / or check 2 is failed, the MF network element can no longer forward the token to the DC AS.

[0215] When the first entity is the second terminal, the first terminal can first send a re-invite message to the IMS AS, and the IMS AS sends a re-invite message to the second terminal. Exemplarily, the communication between the terminal and the IMS AS is forwarded via a P / S-CSCF network element, that is, the first terminal can first send a re-invite message to the P / S-CSCF network element, and the P / S-CSCF network element sends a re-invite message to the IMS AS; the IMS AS sends a re-invite message to the P / S-CSCF network element, and the P / S-CSCF network element sends a re-invite message to the second terminal.

[0216] When the first entity is the first terminal, the first terminal can save the token without sending (i.e., step 304 is an optional step).

[0217] For example, steps 301 to 303 belong to the steps in the rendering capability negotiation process, and in the scenario of the first terminal and the second terminal conducting a digital human related call, the first terminal can negotiate the rendering capability with the network through the first ADC, which can be specifically negotiating who to render in the digital human rendering process, and what data type to use for rendering. For example, step 304 belongs to the establishment process of the second ADC, and after the first terminal and the network negotiate the rendering capability, the first terminal can further request to establish the second ADC, which is used for data transmission in the rendering process, and the first terminal can send the token based on the re-invitation message for establishing the second ADC.

[0218] In Figure 3 In the related process, the first entity obtains the token. Subsequently, the first entity can request the first digital human model based on the token, which can be specifically seen from Figure 4 The flowchart of the second communication method is exemplarily provided. The method can be executed by the first entity and the first BAR network element.

[0219] Step 401: The first entity sends a token to the first BAR network element. Correspondingly, the first BAR network element receives the token from the first entity.

[0220] For example, the first entity sends an avatar representation download request to the first BAR network element, and the token is included in the avatar representation download request. The avatar representation download request can also include the identity of the first digital human and the identity of the first terminal.

[0221] Based on whether the first entity is a proxy entity or a rendering entity, the following exemplary cases are described:

[0222] Case 1: The first entity is a proxy entity, i.e., the first entity is a DC AS, and the DC AS sends an avatar representation download request to the first BAR network element on behalf of a rendering entity, which can be the first terminal, the second terminal or the MF network element. The avatar representation download request also carries a client credentials assertion (CCA) corresponding to the rendering entity, and the specific verification method is described in step 402.

[0223] Case 2: The first entity is a rendering entity:

[0224] Case 2.1, the first entity is the first terminal, the first terminal sends a digital human model download request to the MF network element; the MF network element sends the digital human model download request to the DC AS; the DC AS sends the digital human model download request to the first BAR network element.

[0225] Exemplarily, after receiving the digital human model download request, the MF network element can also perform the above-mentioned check 1 and / or check 2. It can be understood that when the MF network element determines that check 1 and / or check 2 is not passed, the MF network element can no longer forward the digital human model download request to the DC AS.

[0226] Case 2.2, the first entity is the second terminal, the second terminal sends a digital human model download request to the MF network element; the MF network element sends the digital human model download request to the DC AS; the DC AS sends the digital human model download request to the first BAR network element.

[0227] Exemplarily, after receiving the digital human model download request, the MF network element can also perform the above-mentioned check 1 and / or check 2. It can be understood that when the MF network element determines that check 1 and / or check 2 is not passed, the MF network element can no longer forward the digital human model download request to the DC AS.

[0228] Case 2.3, the first entity is the MF network element, the MF network element sends a digital human model download request to the DC AS; the DC AS sends the digital human model download request to the first BAR network element.

[0229] Step 402, the first BAR network element determines that the check is passed according to the token.

[0230] In one possible example, the token includes information of the first entity. The first BAR network element can determine that the entity sending the token is the entity authorized to download the first digital human model according to the information of the first entity included in the token, and then determine that the check is passed.

[0231] In combination with whether the first entity is a proxy entity or a rendering entity, the following exemplary cases are explained as follows:

[0232] Case 1, the first entity is a proxy entity, that is, the first entity is the DC AS. The first BAR network element confirms the identity of the DC AS when the first BAR network element establishes a transport layer security (TLS) channel with the DC AS; further, the first BAR network element determines that the information of the first entity in the token is the information of the DC AS, and then determines that the check is passed.

[0233] Case 2, the first entity is a rendering entity:

[0234] Case 2.1, the first entity is the first terminal, the first BAR network element checks the signature of the token based on the public key of the first terminal, and determines that the token passes the verification (equivalent to determining that the issuer in the token is the first terminal), and further determines that the issuer and the subject in the token are consistent, and thus determines that the verification passes.

[0235] Case 2.2, when the first entity is the MF network element, and the MF network element and the first BAR network element perform end-to-end communication, the first BAR network element confirms the identity of the MF network element when establishing a TLS channel with the MF network element. Further, after the first BAR network element determines that the information of the first entity in the token is the information of the MF network element, it determines that the verification passes.

[0236] When the first entity is the MF network element, and the MF network element communicates with the first BAR network element through the DC AS proxy, the first BAR network element confirms the identity of the DC AS when establishing a TLS channel with the DC AS, and then obtains the CCA from the digital human model download request, wherein the CCA includes the information of the MF network element. After the first BAR network element determines that the subject in the token is the information of the MF network element in the CCA, it determines that the verification passes.

[0237] Case 2.3, the first entity is the second terminal, and the second terminal and the first BAR network element perform end-to-end communication, the first BAR network element confirms the identity of the second terminal by establishing TLS with the second terminal. Further, after the first BAR network element determines that the information of the first entity in the token is the information of the second terminal, it determines that the verification passes.

[0238] When the first entity is the second terminal, and the second terminal communicates with the first BAR network element through the DC AS proxy, the first BAR network element confirms the identity of the DC AS by establishing a TLS channel with the DC AS, and then obtains the CCA from the digital human model download request, wherein the CCA includes the information of the second terminal. After the first BAR network element determines that the subject in the token is the information of the second terminal in the CCA, it determines that the verification passes.

[0239] In addition, the token can also include the information of the first BAR network element. The first BAR network element can also determine that it is the network element authorized by the token to provide the first digital human model according to the information of the first BAR network element included in the token. That is, when the first BAR network element determines that the entity sending the token is the entity authorized by the token to download the first digital human model according to the information of the first entity included in the token, and determines that it is the network element authorized by the token to provide the first digital human model according to the information of the first BAR network element included in the token, it determines that the verification passes.

[0240] Step 403, the first BAR network element sends the first digital human model to the first entity.

[0241] For example, the first BAR network element sends the first digital human model to the first entity after determining that the check passes according to the token. For example, the first BAR network element sends a digital human model response to the first entity, and the digital human model response includes the first digital human model. In addition, when the first BAR network element determines that the check fails according to the token, the first BAR network element sends a check failure response to the first entity.

[0242] At step 404, when the first entity is a rendering entity, the first entity generates a digital human according to the first digital human model; when the first entity is a proxy entity of the rendering entity, the first entity sends the first digital human model to the rendering entity, and the rendering entity generates a digital human according to the first digital human model.

[0243] It should be noted that, Figure 4 The related embodiments are described by taking the first entity (that is, the entity authorized by the first terminal to download the first digital human model) as an example. In this embodiment, it is also described that the second entity sends a token to the first BAR network element. Accordingly, the first BAR network element can determine whether the second entity is an entity authorized by the token (that is, the first entity). If the first BAR network element determines that the second entity is an entity authorized by the token, it is determined that the check passes. If the first BAR network element determines that the second entity is not an entity authorized by the token, it is determined that the check fails.

[0244] Figure 4 The related embodiments are described by taking the first BAR network element (that is, the entity providing the first digital human model) as an example. In this embodiment, it is also described that the second entity sends a token to the second BAR network element. The second BAR network element not only needs to determine whether the second entity is an entity authorized by the token, but also needs to determine whether it is a BAR network element indicated by the token (that is, whether the second BAR network element is the first BAR network element). Further, if the second BAR network element determines that the second entity is an entity authorized by the token and it is a BAR network element indicated by the token, it is determined that the check passes, and the first digital human model is provided to the second entity. Otherwise, it is determined that the check fails, and the first digital human model is not provided to the second entity.

[0245] It can be understood that, Figure 4 The related embodiments can be executed by a third communication device, which can be the second BAR network element or part (such as a chip) of the second BAR network element.

[0246] In combination with the above Figure 3 And Figure 4 The description in the related embodiments, such as Figure 5A third communication method is exemplarily provided in the present application, and a flowchart of the third communication method is shown in FIG. 5. The third communication method is that a DC AS determines information of a first entity according to first configuration information, where the first entity is an MF network element, and further, the MF network element requests a first digital human model from a first BAR network element, and generates a first digital human based on the first digital human model.

[0247] At step 501, a first ADC is established between the first terminal and the DC AS. The first ADC is used for rendering negotiation. Exemplarily, before step 501, a bootstrap data channel (BDC) is further established between the first terminal and the DC AS.

[0248] At step 502, the first terminal sends a capability negotiation request to the DC AS. Correspondingly, the DC AS receives the capability negotiation request from the first terminal. Exemplarily, the capability negotiation request includes an identifier of the first digital human and negotiation parameters of the first terminal. The specific implementation of step 502 can be referred to the description in step 301.

[0249] At step 503, the DC AS determines that the first terminal has the permission to use the first digital human model. The specific implementation of step 503 can be referred to the description in step C.

[0250] At step 504, the DC AS determines information of the first entity according to first configuration information, and determines information of the first BAR network element according to second configuration information. The first configuration information and the second configuration information can be collectively referred to as configuration information. The information of the first entity is the information of the MF network element, for example, an identifier of the MF network element. The information of the first BAR network element is, for example, an identifier of the first BAR network element. The specific implementation of step 504 can be referred to the description in steps A and B.

[0251] At step 505, the DC AS determines a capability negotiation result. Exemplarily, the DC AS determines a rendering data type used by the MF network element in the rendering process of the first digital human according to rendering data requirements of the MF network element, and the capability negotiation result includes the rendering data type.

[0252] At step 506, the DC AS sends a capability negotiation response to the first terminal. Correspondingly, the first terminal receives the capability negotiation response from the DC AS. The capability negotiation response includes the capability negotiation result, the information of the MF network element, and the information of the first BAR network element. The specific implementation of step 506 can be referred to the description in step 302.

[0253] Step 507, the first terminal sends a re-invite message to the IMS AS. Correspondingly, the IMS AS receives the re-invite message from the first terminal. The re-invite message includes the token and the identification of the first digital human. Exemplarily, the subject field in the token is the information of the MF network element, the issuer field is the identification of the first terminal, and the audience field is the information of the first BAR network element. The specific implementation of step 507 can be referred to the description in 304. Exemplarily, before step 507, the first terminal can also generate the token according to the information of the MF network element and the information of the first BAR network element, and the specific implementation can be referred to the description in 303.

[0254] Step 508, the IMS AS sends a media resource reservation message to the MF network element. Correspondingly, the MF network element receives the media resource reservation message from the IMS AS. The media resource reservation message includes the token and the identification of the first digital human. The specific implementation of step 508 can be referred to the description in 304.

[0255] Step 509, the MF network element sends a digital human model download request to the first BAR network element. Correspondingly, the first BAR network element receives the digital human model download request from the MF network element. The digital human model download request includes the identification of the first terminal, the token, and the identification of the first digital human. The specific implementation of step 509 can be referred to the description in 401.

[0256] Step 510, the first BAR network element sends a digital human model response to the MF network element. Correspondingly, the MF network element receives the digital human model response from the first BAR network element. The digital human model response includes the first digital human model. The specific implementation of step 510 can be referred to the description in 403. Exemplarily, before step 510, the first BAR network element can also determine that the verification is passed after determining that the subject field in the token is the information of the MF network element and the audience field is the information of the first BAR network element, and the specific implementation can be referred to the description in 402.

[0257] Step 511, the MF network element generates the first digital human according to the first digital human model.

[0258] Figure 5 In related embodiments, steps 502 to 506 belong to the rendering capability negotiation process, steps 507 and 508 belong to the second ADC establishment process, and steps 509 to 511 are the digital human rendering process. It can be understood that, Figure 5 Only steps related to the present application are exemplarily shown, and other steps can also be included in the rendering capability negotiation process, the ADC establishment process, and the digital human rendering process, which are not listed herein.

[0259] In combination with the above Figure 3 andFigure 4 The description in the related embodiments, such as Figure 6 A fourth communication method is exemplarily provided in the present application, and a flowchart of the fourth communication method is shown in FIG. 6. The fourth communication method is specifically a method for determining information of a first entity according to first configuration information by a DCAS. Further, the first entity is a first terminal, the first terminal requests a first digital human model from a first BAR network element, and a first digital human is generated based on the first digital human model.

[0260] In step 601, a first ADC is established between the first terminal and the DCAS. The first ADC is used for rendering negotiation. Exemplarily, before step 601, a BDC is further established between the first terminal and the DCAS.

[0261] In step 602, the first terminal sends a capability negotiation request to the DCAS. Correspondingly, the DCAS receives the capability negotiation request from the first terminal. Exemplarily, the capability negotiation request includes an identifier of the first digital human and negotiation parameters of the first terminal. The specific implementation of step 602 can be referred to the description in step 301.

[0262] In step 603, the DCAS determines that the first terminal has the permission to use the first digital human model. The specific implementation of step 603 can be referred to the description in step C.

[0263] In step 604, the DCAS determines information of the first entity according to first configuration information, and determines information of the first BAR network element according to second configuration information. The first configuration information and the second configuration information can be collectively referred to as configuration information. The information of the first entity is the information of the first terminal, for example, an identifier of the first terminal. The information of the first BAR network element is, for example, an identifier of the first BAR network element. The specific implementation of step 604 can be referred to the description in steps A and B.

[0264] In step 605, the DCAS determines a capability negotiation result. Exemplarily, the DCAS determines a type of rendering data used by the first terminal in the rendering process of the first digital human according to rendering data requirements of the first terminal, and the capability negotiation result includes the type of rendering data.

[0265] In step 606, the DCAS sends a capability negotiation response to the first terminal. Correspondingly, the first terminal receives the capability negotiation response from the DCAS. The capability negotiation response includes the capability negotiation result, the information of the first terminal, and the information of the first BAR network element. The specific implementation of step 606 can be referred to the description in step 302.

[0266] Step 607, the first terminal sends a digital human model download request to the first BAR network element. Correspondingly, the first BAR network element receives the digital human model download request from the first terminal. The digital human model download request includes the identifier of the first terminal, the token, and the identifier of the first digital human. Exemplarily, the subject field in the token is the information of the first terminal, the issuer field is the identifier of the first terminal, and the audience includes the information of the first BAR network element. The specific implementation of step 607 can be referred to the description in 304. Exemplarily, before step 607, the first terminal can also generate the token according to the information of the first terminal and the information of the first BAR network element, and the specific implementation can be referred to the description in 303.

[0267] Step 608, the first BAR network element sends a digital human model response to the first terminal. Correspondingly, the first BAR network element receives the digital human model response from the first BAR network element. The digital human model response includes the first digital human model. The specific implementation of step 608 can be referred to the description in 403. Exemplarily, before step 608, the first BAR network element can also determine that the verification is passed after determining that the subject field in the token is the information of the first terminal and the audience field is the information of the first BAR network element, and the specific implementation can be referred to the description in 402.

[0268] Step 609, the first terminal generates the first digital human according to the first digital human model.

[0269] The steps 602 to 606 belong to the rendering capability negotiation process, and the steps 607 to 609 belong to the digital human rendering process. It can be understood that, Figure 6 Only steps related to the present application are exemplarily shown, and other steps can also be included in the rendering capability negotiation process and the digital human rendering process. Before the digital human rendering process, the first terminal will also send a re-invitation message to the IMS AS to request to establish a second ADC, which is not listed in the present application.

[0270] As Figure 7 A flowchart of a fifth communication method exemplarily provided by the present application is shown, and in the communication method, the DC AS determines the information of the first entity according to the first configuration information. Further, the first entity is the second terminal, and the second terminal also requests the first digital human model from the first BAR network element and generates the first digital human based on the first digital human model.

[0271] Step 701, a first ADC is established between the first terminal and the DC AS. Exemplarily, before step 701, a BDC is also established between the first terminal and the DC AS.

[0272] Step 702, the first terminal sends a capability negotiation request to the DC AS. Correspondingly, the DC AS receives the capability negotiation request from the first terminal. Exemplarily, the capability negotiation request includes the identifier of the first digital human and the negotiation parameter of the first terminal. The specific implementation of step 702 can be referred to the description in step 301.

[0273] Step 703, the DC AS determines that the first terminal has the permission to use the first digital human model. The specific implementation of step 703 can be referred to the description in step C.

[0274] Step 704, the DC AS determines the information of the first entity according to the first configuration information, and determines the information of the first BAR network element according to the second configuration information. The first configuration information and the second configuration information can be collectively referred to as configuration information. The information of the first entity is the information of the second terminal, for example, the identifier of the second terminal. The information of the first BAR network element is, for example, the identifier of the first BAR network element. The specific implementation of step 704 can be referred to the description in steps A and B.

[0275] Step 705, the DC AS determines the capability negotiation result. Exemplarily, the DC AS determines the rendering data type used by the second terminal in the rendering process of the first digital human according to the rendering data requirement of the second terminal, and the capability negotiation result includes the rendering data type.

[0276] Step 706, the DC AS sends a capability negotiation response to the first terminal. Correspondingly, the first terminal receives the capability negotiation response from the DC AS. The capability negotiation response includes the capability negotiation result, the information of the second terminal, and the information of the first BAR network element. The specific implementation of step 706 can be referred to the description in step 302.

[0277] Step 707, the first terminal sends a re-invite message to the IMS AS. Correspondingly, the IMS AS receives the re-invite message from the first terminal. The re-invite message includes the token and the identifier of the first digital human. Exemplarily, the subject field in the token is the information of the second terminal, the issuer field is the identifier of the first terminal, and the audience includes the information of the first BAR network element. The specific implementation of step 707 can be referred to the description in step 304. Exemplarily, before step 707, the first terminal can also generate the token according to the information of the second terminal and the information of the first BAR network element, and the specific implementation can be referred to the description in step 303.

[0278] Step 708, the IMS AS sends a re-invite message to the P / S-CSCF network element. Correspondingly, the P / S-CSCF network element receives the re-invite message from the IMS AS.

[0279] Step 709, the P / S-CSCF network element sends a re-invite message to the second terminal. Correspondingly, the second terminal receives the re-invite message from the P / S-CSCF network element.

[0280] Step 710, the second terminal sends a digital human model download request to the first BAR network element. Correspondingly, the first BAR network element receives the digital human model download request from the second terminal. The digital human model download request includes the identifier of the first terminal, the token, and the identifier of the first digital human. The specific implementation of step 710 can be referred to the description in 401.

[0281] Step 711, the first BAR network element sends a digital human model response to the second terminal. Correspondingly, the second terminal receives the digital human model response from the first BAR network element. The digital human model response includes the first digital human model. The specific implementation of step 711 can be referred to the description in 403. For example, before step 711, the first BAR network element can determine that the subject field in the token is the information of the second terminal and the audience field is the information of the first BAR network element, and then determine that the verification is passed. The specific implementation can be referred to the description in 402.

[0282] Step 712, the second terminal generates the first digital human according to the first digital human model.

[0283] The steps 702 to 706 belong to the rendering capability negotiation process, the steps 707 to 709 belong to the second ADC establishment process, and the steps 710 to 712 belong to the digital human rendering process. It can be understood that, Figure 7 Only the steps related to the present application are exemplarily shown, and other steps can be included in the rendering capability negotiation process, the ADC establishment process, and the digital human rendering process, which are not listed in the present application.

[0284] For example, Figure 8 A flowchart of a sixth communication method is exemplarily provided in the present application. In the communication method, the DCAS determines the information of the first entity according to the negotiation parameter of the first terminal, the negotiation parameter of the second terminal, and the negotiation parameter of the MF network element. Further, the first entity is the MF network element, and the MF network element further requests the first digital human model from the first BAR network element and generates the first digital human based on the first digital human model.

[0285] Step 801, a first ADC is established between the first terminal and the DCAS. The first ADC is used for rendering negotiation. For example, before step 801, a BDC is further established between the first terminal and the DCAS.

[0286] At step 802, the first terminal sends a capability negotiation request to the DC AS. Correspondingly, the DC AS receives the capability negotiation request from the first terminal. Exemplarily, the capability negotiation request includes the identifier of the first digital human and the negotiation parameter of the first terminal. The implementation of step 802 can refer to the description in step 301.

[0287] At step 803, the DC AS determines that the first terminal has the permission to use the first digital human model. The implementation of step 803 can refer to the description in step C.

[0288] At step 804, the DC AS sends a rendering capability request to the MF network element. Correspondingly, the MF network element receives the rendering capability request from the DC AS. The rendering capability request includes the identifier of the second terminal, and the rendering capability request is used to request the negotiation parameter of the second terminal, which includes the rendering capability of the second terminal and the candidate entity recommended by the second terminal. The implementation of step 804 can refer to the description in step A.

[0289] At step 805, the MF network element sends a rendering capability request to the second terminal. Correspondingly, the second terminal receives the rendering capability request from the MF network element. The implementation of step 805 can refer to the description in step A.

[0290] At step 806, the second terminal sends a rendering capability response to the MF network element. Correspondingly, the MF network element receives the rendering capability response from the second terminal. The rendering capability response of the second terminal includes the negotiation parameter of the second terminal. The implementation of step 806 can refer to the description in step A.

[0291] At step 807, the MF network element sends a rendering capability response to the DC AS. Correspondingly, the DC AS receives the rendering capability response from the MF network element. The rendering capability response of the MF network element includes the negotiation parameter of the second terminal and the negotiation parameter of the MF network element, which includes the rendering capability of the MF network element and the candidate entity recommended by the MF network element. The implementation of step 807 can refer to the description in step A.

[0292] At step 808, the DC AS determines the information of the first entity (i.e., the information of the MF network element) according to the negotiation parameter of the first terminal, the negotiation parameter of the second terminal and the negotiation parameter of the MF network element, and determines the information of the first BAR network element according to the second configuration information. The implementation of step 808 can refer to the description in steps A and B.

[0293] At step 809, the DC AS determines the capability negotiation result. For example, the DC AS determines, according to the rendering data requirement of the MF network element, a rendering data type used by the MF network element in the rendering process of the first digital human, and the capability negotiation result includes the rendering data type.

[0294] At step 810, the DC AS sends the capability negotiation response to the first terminal. Correspondingly, the first terminal receives the capability negotiation response from the DC AS. The capability negotiation response includes the capability negotiation result, the information of the MF network element, and the information of the first BAR network element. The specific implementation of step 810 can be referred to the description in step 302.

[0295] After step 810, steps 507 to 511 can also be included. Steps 802 to 810 belong to the rendering capability negotiation process. It can be understood that, Figure 8 Only steps related to the present application are exemplarily shown, and other steps can also be included in the rendering capability negotiation process, the ADC establishment process, and the digital human rendering process, which are not listed herein.

[0296] In addition, after step 810, Figure 8 In related embodiments, if the first entity is the first terminal, after step 810, steps 607 to 609 can also be included. If the first entity is the second terminal, after step 810, steps 707 to 712 can also be included. Details are not described herein.

[0297] As Figure 9 A flowchart of a seventh communication method exemplarily provided by the present application is shown, in which the DC AS determines, according to the negotiation parameter of the first terminal, the negotiation parameter of the second terminal, and the negotiation parameter of the MF network element, that the information of the first entity is not determined, and the DC AS requests the information of the first entity from the NRF network element. Further, the first entity is a new MF network element (i.e., a second MF network element), and the second MF network element also requests the first digital human model from the first BAR network element, and generates the first digital human based on the first digital human model.

[0298] Figure 9 In related embodiments, the difference from the above-mentioned embodiments is that, after step 807, the DC AS determines that the rendering capabilities of the first terminal, the second terminal, and the first MF network element all do not meet the preset rendering requirement. The following describes from after step 807: Figure 8 At step 901, the DC AS determines that the rendering capabilities of the first terminal, the second terminal, and the first MF network element all do not meet the preset rendering requirement. The DC AS determines the information of the first BAR network element according to the second configuration information. The specific implementation of step 901 can be referred to the description in steps A and B.

[0299] At step 901, the DC AS determines that the rendering capabilities of the first terminal, the second terminal, and the first MF network element all do not meet the preset rendering requirement. The DC AS determines the information of the first BAR network element according to the second configuration information. The specific implementation of step 901 can be referred to the description in steps A and B.

[0300] At step 902, the DC AS sends a first request to the NRF network element, and correspondingly, the NRF network element receives the first request from the DC AS. The first request includes the preset rendering requirement. The first request is used to request the information of the first entity satisfying the preset rendering requirement from the NRF network element. The specific implementation of step 902 can be referred to the description in step A.

[0301] At step 903, the NRF network element sends a first response to the DC AS, and correspondingly, the DC AS receives the first response from the NRF network element. The first response includes the information of the first entity (i.e., the information of the second MF network element). In one specific example, the NRF network element determines the information of the second MF network element according to the preset rendering requirement, and sends the first response to the DC AS. The specific implementation of step 903 can be referred to the description in step A.

[0302] At step 904, the DC AS sends the information of the second MF network element to the IMS AS, and the information of the second MF network element is used for the DC AS to update the MF network element, so that the first terminal establishes a second ADC based on the second MF network element and the DC AS. In an example, the DC AS can also send the information of the second MF network element to the DCSF network element, and the information of the second MF network element is used for the DCSF network element to update the MF network element, so that the first terminal establishes a second ADC based on the second MF network element and the DC AS. The specific implementation of step 904 can be referred to the description in step A.

[0303] After step 904, steps 507 to 511 can also be included, with the difference that the first MF in them is replaced by the second MF. Among them, steps 901 to 904 belong to the rendering capability negotiation process. It can be understood that, Figure 9 Only steps related to the present application are exemplarily shown, and other steps can also be included in the rendering capability negotiation process, the ADC establishment process and the digital person rendering process, which are not listed in the present application.

[0304] It should be further noted that the above embodiments are all described by taking the DC AS as an example to determine the information of the first entity, and in other possible examples, the information of the first entity can also be determined by the MF network element, the first terminal, the second terminal, or other network elements. For example, in the case where the MF network element determines the information of the first entity, when the capability negotiation request of the first terminal is sent to the MF network element, the MF network element can determine the information of the first entity. For example, in the case where the first terminal determines the information of the first entity, the first terminal can determine the information of the first entity before capability negotiation. For example, in the case where the second terminal determines the information of the first entity, the DC AS can request the second terminal for the information of the first entity after receiving the capability negotiation request, and accordingly, the second terminal can return the information of the first entity to the DC AS or directly send the information of the first entity to the first terminal. For example, in the case where other network elements determine the information of the first entity, the DC AS can forward the capability negotiation request to the other network elements after receiving the capability negotiation request, and the other network elements determine the information of the first entity, and then the other network elements forward the information of the first entity to the first terminal through the DC AS, or the other network elements directly send the information of the first entity to the first terminal.

[0305] The step numbers of each flowchart described in the above embodiments are only an example of the execution flow, and do not constitute a limitation on the execution sequence of the steps. The steps shown in each flowchart are not all the steps that must be executed, and some steps can be deleted based on the actual needs, or other possible steps can be added based on the actual needs.

[0306] The above focuses on the differences between the embodiments, and other contents except the differences can be mutually referred between the embodiments. In addition, the same embodiment can also be mutually referred between different implementation manners or different examples.

[0307] Based on the above content and the same concept, Figure 10 and Figure 11 The structure schematic diagram of the possible communication apparatus provided in the present application. These communication apparatuses can be used to realize the functions of the first terminal or the DC AS in the above method embodiments, and thus can also realize the beneficial effects possessed by the above method embodiments. In the present application, the communication apparatus can be, for example, Figures 2A-2C the first terminal (or a module (for example, a chip) in the first terminal) in any one of the figures, or can also be Figure 2C the DC AS (or a module (for example, a chip) in the DC AS) in the figure.

[0308] For example, Figure 10As shown, the communication apparatus 1000 includes a processing module 1001 and a transceiver module 1002.

[0309] When the communication apparatus 1000 is used to implement the function of the first terminal of any one of the illustrated method embodiments: Figures 3-9

[0310] The transceiver module 1002 is configured to send a capability negotiation request, the capability negotiation request carrying the identity of the digital human, the capability negotiation request being used to negotiate the rendering of the digital human; and receive a capability negotiation response, the capability negotiation response including information of a first entity, the first entity being an entity used to download a digital human model, the digital human model being used for the rendering of the digital human;

[0311] The processing module 1001 is configured to generate a token according to the information of the first entity, the token being used to authorize the first entity to download the digital human model.

[0312] The transceiver module 1002 is further configured to send the token.

[0313] In a possible implementation, the token includes the information of the first entity and the identity of the digital human.

[0314] In a possible implementation, the token is carried in a re-invite message.

[0315] In a possible implementation, the capability negotiation response further includes information of an entity used to store the digital human model, and the token includes the information of the entity used to store the digital human model.

[0316] In a possible implementation, the first entity is one of a DC AS, an MF network element, the first terminal and the second terminal related to the call.

[0317] In a possible implementation, the capability negotiation request carries negotiation parameters of the first terminal; the negotiation parameters of the first terminal include rendering capability of the first terminal and / or a candidate entity recommended by the first terminal; the candidate entity includes one or more of the MF network element, the first terminal and the second terminal related to the call.

[0318] In a possible implementation, the capability negotiation request is sent by the transceiver module 1002 to the DC AS through a first ADC, the first ADC being a channel between the transceiver module 1002 and the DC AS.

[0319] When the communication apparatus 1000 is used to implement the function of the DC AS of any one of the illustrated method embodiments: Figures 3-9

[0320] ​​The transceiver module 1002 is configured to receive a capability negotiation request, the capability negotiation request carrying an identifier of the digital human, and the capability negotiation request being used for negotiating rendering of the digital human.

[0321] The processing module 1001 is configured to determine information of a first entity.

[0322] The transceiver module 1002 is further configured to send a capability negotiation response, the capability negotiation response including the information of the first entity, the first entity being an entity used for downloading a digital human model, and the digital human model being used for rendering of the digital human.

[0323] The information of the first entity is used by the first terminal to generate a token, and the token is used to authorize the first entity to download the digital human model.

[0324] In a possible implementation, the capability negotiation response further includes information of an entity used for storing the digital human model.

[0325] In a possible implementation, the capability negotiation request carries negotiation parameters of the first terminal, the negotiation parameters of the first terminal including rendering capability of the first terminal and / or a candidate entity recommended by the first terminal, and the candidate entity including one or more of an MF network element related to the call, the first terminal, and the second terminal.

[0326] In a possible implementation, when determining the information of the first entity according to the negotiation parameters of the first terminal, the processing module 1001 is specifically configured to obtain, from the MF network element, negotiation parameters of the MF network element and negotiation parameters of the second terminal, and determine the information of the first entity according to the negotiation parameters of the first terminal, the negotiation parameters of the MF network element, and the negotiation parameters of the second terminal.

[0327] In a possible implementation, the first entity is one of a DC AS, the MF network element, the first terminal, and the second terminal related to the call.

[0328] In a possible implementation, when the processing module 1001 determines that none of the negotiation parameters of the first terminal, the negotiation parameters of the MF network element, and the negotiation parameters of the second terminal meets the preset rendering requirement, the transceiver module 1002 is further configured to send, to an NRF network element, a first request including the preset rendering requirement, the first request being used for requesting the first entity meeting the preset rendering requirement, and receive a first response from the NRF network element, the first response including the information of the first entity.

[0329] In a possible implementation, the capability negotiation request is sent by the first terminal to the transceiver module 1002 through a first ADC; wherein the first ADC is a channel between the first terminal and the transceiver module 1002. In other words, the capability negotiation request is information from the first terminal received by the transceiver module 1002 through the first ADC.

[0330] As shown in Figure 11 The apparatus 1100 provided by the embodiments of the present application is shown in Figure 11 The apparatus shown can be Figure 10 A hardware circuit implementation of the apparatus is shown in the figure. The apparatus can be applied to the flowcharts shown in the foregoing, to perform the functions of the first terminal or the DCAS in the method embodiments described above. For the convenience of description, Figure 11 Only the main components of the apparatus are shown.

[0331] Figure 11 The apparatus 1100 shown includes a communication interface 1110, a processor 1120 and a memory 1130, wherein the memory 1130 is used to store program instructions and / or data. The processor 1120 can operate in cooperation with the memory 1130. The processor 1120 can execute the program instructions stored in the memory 1130. When the instructions or programs stored in the memory 1130 are executed, the processor 1120 is used to perform the operations performed by the processing module 1001 in the embodiments described above, and the communication interface 1110 is used to perform the operations performed by the transceiver module 1002 in the embodiments described above.

[0332] The memory 1130 and the processor 1120 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between the apparatuses, units or modules, which can be electrical, mechanical or other forms, for information interaction between the apparatuses, units or modules. At least one of the memories 1130 can be included in the processor 1120.

[0333] In the embodiments of the present application, the communication interface can be a transceiver, a circuit, a bus, a module or other types of communication interfaces. In the embodiments of the present application, when the communication interface is a transceiver, the transceiver can include a separate receiver, a separate transmitter; or a transceiver integrated with transceiving functions, or a communication interface.

[0334] The apparatus 1100 can further include a communication line 1140. The communication interface 1110, the processor 1120, and the memory 1130 can be connected to each other through the communication line 1140. The communication line 1140 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication line 1140 can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, Figure 11 Only one thick line is used to represent the buses in the figure, but it does not mean that there is only one bus or only one type of bus.

[0335] Based on the above and the same idea, the present application further provides a computer readable storage medium, which stores a computer program or instructions, when the computer program or instructions are executed by a communication device, the method executed by the first terminal in the above method embodiment is implemented, or the method executed by the DCAS in the above method embodiment is implemented.

[0336] Based on the above and the same idea, the present application further provides a computer program product, which includes a computer program or instructions, when the computer program or instructions are executed by a communication device, the method executed by the first terminal in the above method embodiment is implemented, or the method executed by the DCAS in the above method embodiment is implemented.

[0337] Based on the above and the same idea, the present application further provides a communication system, which includes: a first communication device and / or a second communication device; the first communication device implements the method executed by the first terminal in the above method embodiment, and the second communication device implements the method executed by the DCAS in the above method embodiment.

[0338] In the embodiments of the present application, the number of nouns, unless otherwise specified, represents "a singular noun or a plural noun", that is, "one or more". "At least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. For example, A / B means A or B. "At least one of the following" or the like means any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c means a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0339] In embodiments of the present application, "sending" and "receiving" refer to the direction of signal transmission. For example, "sending information to XX" can be understood as that the destination of the information is XX. "Receiving information from YY" can be understood as that the source of the information is YY. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be between devices, such as between the MF network element and the terminal, or within a device, such as between components, modules, chips, software modules or hardware modules within the device through a bus, wire or interface.

[0340] In embodiments of the present application, "when", "if" and "whether" refer to the objective situation that the device will make corresponding processing, and are not limited in time, and do not require the device to have a judgment action when implemented. Without special instructions, "if" and "whether" can be replaced, and "when" and "in the case of" can be replaced. "When" and "if" / "whether" can be replaced.

[0341] In embodiments of the present application, the words "exemplary" or "for example" are used to mean serving as an example or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of "exemplary" or "for example" is intended to present concepts in a concrete manner.

[0342] In embodiments of the present application, the ordinal numbers "first", "second", etc. are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of the multiple objects. For example, the first indication information and the second indication information refer to two different indication information, and do not mean that the priority or importance of the two indication information is different.

[0343] It can be understood that the various numbers involved in the embodiments of the present application are only for convenient differentiation, and do not limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined by its function and inherent logic.

Claims

1. A communication method applied to a scenario where a first terminal and a second terminal are conducting digital human-related calls, characterized in that, include: The first communication device sends a capability negotiation request, which carries the identifier of the digital human and is used to negotiate the rendering of the digital human. The first communication device receives a capability negotiation response, which includes information about a first entity, the first entity being an entity used to download a digital human model, the digital human model being used for rendering the digital human; The first communication device generates a token based on the information of the first entity, and the token is used to authorize the first entity to download the digital human model; The first communication device sends the token; The first communication device is the first terminal, or a part of the first terminal.

2. The method as described in claim 1, characterized in that, The token includes information about the first entity and the identifier of the digital human.

3. The method as described in claim 1 or 2, characterized in that, The token is carried in the re-invitation message.

4. The method according to any one of claims 1-3, characterized in that, The capability negotiation response also includes information about the entity used to store the digital human model, and the token includes the information about the entity used to store the digital human model.

5. The method according to any one of claims 1-4, characterized in that, The first entity is one of the data channel application server, media function network element, first terminal, and second terminal associated with the call.

6. The method according to any one of claims 1-5, characterized in that, The capability negotiation request carries the negotiation parameters of the first terminal; the negotiation parameters of the first terminal include the rendering capabilities of the first terminal and / or the candidate entities recommended by the first terminal. The candidate entities include one or more of the media function network elements associated with the call, the first terminal, and the second terminal.

7. The method according to any one of claims 1-6, characterized in that, The capability negotiation request is sent by the first communication device to the data channel application server through the application data channel; The application data channel is the channel between the first communication device and the data channel application server.

8. A communication method applied to a scenario where a first terminal and a second terminal are conducting a digital human-related call, characterized in that, include: The second communication device receives a capability negotiation request, which carries the identifier of the digital human and is used to negotiate the rendering of the digital human. The second communication device sends a capability negotiation response, which includes information about a first entity, which is an entity used to download a digital human model, and the digital human model is used for rendering the digital human. The information of the first entity is used to generate a token, which is used to authorize the first entity to download the digital human model. The second communication device is a data channel application server or a part of the data channel application server associated with the call.

9. The method as described in claim 8, characterized in that, The capability negotiation response also includes information about the entity used to store the digital human model.

10. The method as described in claim 8 or 9, characterized in that, The capability negotiation request carries the negotiation parameters of the first terminal; the negotiation parameters of the first terminal include the rendering capabilities of the first terminal and / or the candidate entities recommended by the first terminal. The candidate entities include one or more of the media function network elements associated with the call, the first terminal, and the second terminal; Following the second communication device's capability negotiation request, the following is also included: The second communication device determines the information of the first entity based on the negotiation parameters of the first terminal.

11. The method as described in claim 10, characterized in that, The second communication device determines the information of the first entity based on the negotiation parameters of the first terminal, including: The second communication device obtains the negotiation parameters of the media function network element and the negotiation parameters of the second terminal; The second communication device determines the information of the first entity based on the negotiation parameters of the first terminal, the negotiation parameters of the media function network element, and the negotiation parameters of the second terminal.

12. The method according to any one of claims 8-11, characterized in that, The first entity is one of the data channel application server, media function network element, first terminal, and second terminal associated with the call.

13. The method as described in claim 11, characterized in that, Also includes: When the second communication device determines that the negotiation parameters of the first terminal, the negotiation parameters of the media function network element, and the negotiation parameters of the second terminal all fail to meet the preset rendering requirements, it sends a first request to the network storage function network element. The first request includes the preset rendering requirements and is used to request a first entity that meets the preset rendering requirements. The second communication device receives a first response from the network storage function element, the first response including information about the first entity.

14. The method according to any one of claims 8-13, characterized in that, The capability negotiation request is information received by the second communication device from the first terminal through the application data channel; The application data channel is the channel between the first terminal and the second communication device.

15. A communication device, characterized in that, It includes a module for performing the method as described in any one of claims 1 to 7, or includes a module for performing the method as described in any one of claims 8 to 14.

16. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor implements the method as described in any one of claims 1 to 7 through logic circuits or executable code instructions, or the processor implements the method as described in any one of claims 8 to 14 through logic circuits or executable code instructions.

17. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 7, or implement the method as described in any one of claims 8 to 14.

18. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 7, or implement the method as described in any one of claims 8 to 14.

19. A communication system, characterized in that, include: First communication device and second communication device; The first communication device is used to implement the method as described in any one of claims 1 to 7; The second communication device is used to implement the method as described in any one of claims 8 to 14.

Images