Communication method, communication device, communication system, and readable storage medium

Abstract

The present application relates to the technical field of communications, and in particular to a communication method, a communication device, a communication system, and a readable storage medium. The method comprises: in the call process of a first user and a second user, a first network element recognizing a communication intention of the first user on the basis of the communication content sent by the first user to the second user; sending to a second network element information for describing the communication intention, so that the second network element generates intention service information on the basis of the information used for describing the communication intention, and returns the intention service information to the first network element; and the first network element providing an intention service for the second user and / or the first user on the basis of the intention service information. According to the embodiments of the present application, an intention service based on a user communication intention can be provided for users in the call process of the users, thereby improving the communication efficiency.

Description

Communication methods, communication devices, communication systems, and readable storage media

[0001] This application claims priority to Chinese Patent Application No. 202410024198.0, filed on January 5, 2024, with the China National Intellectual Property Administration, entitled “Communication Method, Communication Device, Communication System and Readable Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method, communication device, communication system and readable storage medium. Background Technology

[0003] The International Telecommunication Union-Radiocommunication Sector (ITU-R) has proposed six major scenarios for International Mobile Telecommunications (IMT) 2030. These include two main areas: firstly, connectivity enhancement scenarios for 5G, such as immersive communication, ultra-reliable low-latency communication, and massive data transmission; and secondly, new scenarios including ubiquitous connectivity, artificial intelligence (AI) and communication integration, and sensing and communication integration. It can be understood that the development path before 5G focused on the evolution of communication and connectivity, emphasizing the "Internet of Everything"; while future communication technologies, such as 6G, add resources and capabilities in computing, intelligence, data, and sensing to the enhanced connectivity, aiming for the "Intelligent Internet of Everything." In short, future communication technologies, such as 6G networks, are networks that integrate communication (or connectivity), computing, intelligence, data, and sensing, enabling the intelligent Internet of Everything.

[0004] The "everything" in "Internet of Everything" can be understood as: people (natural persons), machines, data (intelligent humans), and spirits (intelligent robots) connected to future networks (such as 6G networks). The "intelligent connection" in "Internet of Everything" can be understood as: centered on the user (such as a person or enterprise), driving information interaction between people, machines, data, and spirits based on user intent, and ultimately achieving the user's communication intent or purpose by utilizing the inherent capabilities of communication, perception, computation, data, and intelligence.

[0005] Currently, networks can only provide users with deterministic services, such as intelligent customer service, fun calls, simultaneous interpretation, content sharing, and screen sharing in 5G new calls. These are all services provided based on deterministic business (or predefined functions). However, how to provide users with intent services based on their communication intentions (which are uncertain) during a call remains to be explored. Summary of the Invention

[0006] This application provides a communication method, communication device, communication system, and readable storage medium, which can provide users with intent services based on the user's communication intent, thereby improving communication efficiency.

[0007] The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.

[0008] In this application, "intent service" can be understood as a service related to intent. A service can be understood as an action or process that provides assistance to a user, meets their needs, or completes a task.

[0009] In a first aspect, this application provides a communication method, the method comprising: a first network element identifying the communication intent of a first user using the first terminal based on communication content sent from a first terminal to a second terminal; the first network element sending information describing the communication intent to the second network element; the first network element receiving first intent service information corresponding to the communication intent from the second network element, and providing a first intent service to the second terminal and / or the first terminal based on the first intent service information.

[0010] For example, the first network element identifies the communication intent of the first user using the first terminal based on the communication content sent from the first terminal to the second terminal. This includes: the first network element identifying the communication intent of the first user using the first terminal based on the communication content sent from the first terminal to the second terminal and from the second terminal to the first terminal. In other words, when the first network element identifies the communication intent of the first user, it can do so based on the communication content exchanged between the first terminal and the second terminal, or it can do so based solely on the communication content sent from the first terminal to the second terminal.

[0011] For example, the first network element may be a network intelligent agent function (NIAF), and the second network element may be an intent service function (ISF). For an explanation of NIAF and ISF, please refer to the embodiments below, which will not be described in detail here.

[0012] This application identifies the user's communication intent within the communication content during a call by the network side, generates intent service information corresponding to this intent, and then provides the user with the appropriate intent service based on this intent service information. This allows for the provision of intent services based on the user's communication intent (which is uncertain), thereby improving communication efficiency.

[0013] In conjunction with the first aspect, in one possible implementation, the information used to describe the communication intent includes one or more of the following: the category of the communication intent, the topic of the communication intent, the keywords of the communication intent, or the semantics of the communication intent. In other words, after the first network element identifies the communication intent of the first user, the first network element can process the identified communication intent to obtain information describing the communication intent. For example, the semantics of the communication intent can be text-based semantics, or semantics processed by vectorization techniques such as embedding, i.e., a semantic vector.

[0014] In conjunction with the first aspect, in one possible implementation, before the first network element sends information describing the communication intent to the second network element, the method further includes: the first network element sending a first query message to a third network element, the first query message being used to query a second network element that supports the communication intent; the first network element receiving a first response message from the third network element, the first response message including information about the second network element. The information about the second network element may include, but is not limited to, one or more of the following: the access address of the second network element (such as the application programming interface (API), uniform resource locator (URL), or media access control (MAC) address of the second network element), the identifier of the second network element, or the name of the second network element. It can be understood that the information about the second network element can be used to identify this second network element.

[0015] For example, the third network element can be an intentservice registration function (ISRF). For an explanation of ISRF, please refer to the embodiments below, which will not be described in detail here.

[0016] For example, the first query message includes the semantic vector of the communication intent. The similarity between the registration information vector of the second network element and the semantic vector of the communication intent is greater than a threshold. Alternatively, the second network element is one of the top K similarity vectors, sorted from largest to smallest. These similarities include the similarity between the semantic vector of the communication intent and the registration information vectors of multiple network elements stored in the third network element, where K is a positive integer. In other words, the third network element can store vectorized network element registration information as a vector database (during network element registration, its original registration information is vectorized, and the processed registration information vector is associated with and stored with the original registration information). After receiving the first query message, it can calculate the similarity between the semantic vector of the communication intent and the registration information vectors of the network elements it stores, thereby returning information of the second network element with high similarity (e.g., top K, or similarity greater than a certain threshold).

[0017] It is understandable that, because the user's communication intent is uncertain, the first network element of this application, after recognizing the user's communication intent, may not be able to determine which network element in the network can provide the intent service corresponding to that communication intent. Therefore, this application queries the network element that manages intent services (i.e., the third network element) in the network for a second network element that can support the communication intent, so that the second network element can generate corresponding intent service information based on the information used to describe the communication intent, thereby providing the user with the corresponding intent service.

[0018] In conjunction with the first aspect, in one possible implementation, the first network element provides a first intent service to the second terminal and / or the first terminal, including: the first network element sending the aforementioned first intent service information to the second terminal and / or the first terminal. Alternatively, the first network element sends second intent service information to the second terminal and / or the first terminal, which may be the result of processing the aforementioned first intent service information based on the capabilities of the second terminal and / or the first terminal. For example, the second intent service information is intent service information whose display format of the first intent service information has been processed to match the information display capabilities of the second terminal and / or the first terminal.

[0019] It can be understood that the first network element providing the first intent service to the second terminal includes: the first network element sending the aforementioned first intent service information or second intent service information to the second terminal, wherein the second intent service information is the result of processing the aforementioned first intent service information based on the capabilities of the second terminal. The first network element providing the first intent service to the first terminal includes: the first network element sending the aforementioned first intent service information or second intent service information to the first terminal, wherein the second intent service information is the result of processing the aforementioned first intent service information based on the capabilities of the first terminal. The first network element providing the first intent service to both the second terminal and the first terminal includes: the first network element sending the aforementioned first intent service information to both the second terminal and the first terminal, or the first network element sending the second intent service information to the second terminal and sending fourth intent service information to the first terminal. Wherein, the second intent service information is the result of processing the aforementioned first intent service information based on the capabilities of the second terminal, and the fourth intent service information is the result of processing the aforementioned first intent service information based on the capabilities of the first terminal.

[0020] This application provides intent services adapted to the capabilities of different terminals, which can achieve better display effects on the terminal.

[0021] In conjunction with the first aspect, in one possible implementation, before the first network element provides the first intent service to the second terminal and / or the first terminal, the method further includes: the first network element sending its address to the second terminal and / or the first terminal; the first network element receiving a first message from the second terminal and / or the first terminal, the first message being used to obtain the aforementioned first intent service. When the first network element provides the first intent service to the second terminal and / or the first terminal, the first network element can provide the first intent service to the second terminal and / or the first terminal based on the first message.

[0022] The first network element of this application actively informs the terminal of its own address so that the terminal can obtain the intended service from the first network element.

[0023] In conjunction with the first aspect, in one possible implementation, before the first network element provides the first intent service to the second terminal and / or the first terminal, the method further includes: the first network element establishing a communication connection with the second terminal and / or the first terminal. When the first network element provides the first intent service to the second terminal and / or the first terminal, the first network element provides the first intent service to the second terminal and / or the first terminal through the communication connection.

[0024] For example, the first network element establishes a communication connection with the second terminal and / or the first terminal, including: the first network element sending a media session request (such as a Session Initialization Protocol (SIP) Invitation (SIP INVITE) message to the second terminal and / or the first terminal, and negotiating the establishment of a media streaming session (such as a Real-Time Transport Protocol (RTP) session) through the media session request; the first network element receiving a media session response from the second terminal and / or the first terminal to establish this media streaming session. The first network element can then provide a first intent service to the second terminal and / or the first terminal through this media streaming session (such as the RTP session). This application provides intent services by establishing a new communication connection (or media streaming session), which has minimal impact on existing call content.

[0025] In conjunction with the first aspect, in one possible implementation, after the first network element provides the first intent service to the second terminal and / or the first terminal, the method further includes: the first network element receiving operation information from the first terminal and / or the second terminal, the operation information including operation events of the first user and / or the second user using the second terminal regarding the first intent service; the first network element sending the operation information to the second network element; the first network element receiving third intent service information from the second network element, the third intent service information being intent service information updated based on the operation events based on the first intent service information; and based on this third intent service information, the first network element providing the second intent service to the second terminal and / or the first terminal.

[0026] For example, the first network element provides a second intent service to the second terminal and / or the first terminal, including: the first network element triggers the first terminal and / or the second terminal to execute the task corresponding to the aforementioned third intent service information. For instance, the first network element sends an instruction to the first terminal and / or the second terminal, instructing them to execute the task corresponding to the third intent service information.

[0027] In conjunction with the first aspect, in one possible implementation, before the first network element receives the third intent service information from the second network element, the method further includes: the first network element sending one or more of the following to the second network element: the digital identity authorization information of the first user, or the digital identity authorization information of the second user; the digital identity authorization information of the first user or the digital identity authorization information of the second user is used to generate the third intent service information in conjunction with the above-mentioned operation events.

[0028] In conjunction with the first aspect, in one possible implementation, before the first network element receives the first intent service information corresponding to the communication intent from the second network element, the method further includes: the first network element sending one or more of the following to the second network element: the digital human information of the first user, the digital human information of the second user, the personalized information of the first user, and the personalized information of the second user. Wherein, the digital human information of the first user, the digital human information of the second user, the personalized information of the first user, or the personalized information of the second user are used to generate the first intent service information by combining the aforementioned information describing the communication intent.

[0029] In conjunction with the first aspect, in one possible implementation, before the first network element identifies the communication intent of the first user using the first terminal based on the communication content sent from the first terminal to the second terminal, the method further includes: the first network element receiving communication content from a user plane network element, the communication content being transmitted through a session between the first terminal and the second terminal, the user plane network element serving the session.

[0030] For example, before the first network element receives communication content from the user plane network element, the method further includes: the first network element receiving a second message from the first terminal, the second message including information for indicating the aforementioned session, the second message being used to instruct the first network element to insert into the session; the first network element sending a first request message to a fourth network element, the first request message being used to request the establishment of a connection between the first network element and the user plane network element serving the session, the first request message including the address of the first network element. It can be understood that when the first network element subsequently provides intent services to the second terminal and / or the first terminal, it can do so through this connection.

[0031] For example, after receiving the second message, the first network element can query the network for the fourth network element corresponding to the session and send a first request message to the fourth network element. In another possible implementation, the second message may also include the identifier of the first terminal. In this case, after receiving the second message, the first network element can query the network for the fourth network element corresponding to the first terminal and then send a first request message to the fourth network element.

[0032] For example, the fourth network element can be an intelligent session management function (ISMF). For an explanation of ISMF, please refer to the following embodiments, which will not be detailed here.

[0033] For example, the second message further includes indication information, which indicates that the transmission direction of the communication content is from the first terminal to the second terminal; the first request message also includes this second indication information. The second indication information can be used by the user plane network element to filter the communication content sent to the first network element.

[0034] In conjunction with the first aspect, in one possible implementation, before the first network element identifies the communication intent of the first user using the first terminal based on the communication content sent from the first terminal to the second terminal, the method further includes: the first network element receiving communication content from a media network element, which is sent from the first terminal to the second terminal via the media network element and the first network element. For example, the communication content being sent from the first terminal to the second terminal via the media network element and the first network element includes: the communication content being sent from the first terminal to the second terminal via a session, where the session is a session between the first terminal, the media network element, the first network element, and the second terminal.

[0035] For example, before the first network element receives communication content from the media network element, the method further includes: the first network element receiving a session invitation message or a session re-invitation message from the first terminal, wherein the session invitation message is used to establish a session between the first terminal and the second terminal via the media network element and the first network element, and the session re-invitation message is used to modify the session between the first terminal and the second terminal so that the first network element can insert into the session; the first network element forwards a session invitation response or a session re-invitation response returned by the second terminal to the first terminal, wherein the session invitation response or the session re-invitation response is used to agree to the session invitation message or the session re-invitation message.

[0036] For example, before the first network element receives communication content from the media network element, the method further includes: the first network element receiving a third message from a first terminal, the third message including information indicating a session between the first terminal and a second terminal, the third message indicating that the first network element transmits intent service information with the media network element serving the session through the session; the first network element sending a fourth message to the media network element, the fourth message including the information indicating the session, the fourth message requesting the transmission of intent service information through the session; and the first network element receiving a fifth message from the media network element, the fifth message indicating agreement to transmit intent service information through the session. For example, the fourth message may be a session re-INVITE message, which includes newly added media lines (m lines), which can be used to negotiate with the media network element to transmit intent service information through the session. The fifth message may be a session re-INVITE response, which can be used to agree to transmit intent service information through the session.

[0037] Secondly, this application provides a communication method, the method comprising: a first terminal sending communication content to a second terminal, the communication content including a communication intent of a first user using the first terminal; the first terminal receiving first intent service information corresponding to the communication intent, and calling an application associated with the first intent service information to output the first intent service information.

[0038] For example, the path for the first terminal to send communication content to the second terminal is as follows: the first terminal first sends the communication content to the base station 1 connected to the first terminal, the base station 1 then sends the communication content to the user plane function 1 to which the first terminal belongs, the user plane function 1 sends the communication content to the user plane function 2 to which the first network element and the second terminal belong respectively, the user plane function 2 sends it to the base station 2 connected to the second terminal, and the base station 2 sends it to the second terminal.

[0039] In conjunction with the second aspect, in one possible implementation, the display format of the aforementioned first intent service information matches the information display capability of the first terminal.

[0040] In conjunction with the second aspect, in one possible implementation, before the first terminal receives the first intent service information corresponding to the aforementioned communication intent, the method further includes: the first terminal receiving the address of the first network element; the first terminal sending a first message to the first network element, the first message being used to obtain the first intent service information.

[0041] In conjunction with the second aspect, in one possible implementation, before the first terminal receives the first intent service information corresponding to the aforementioned communication intent, the method further includes: the first terminal establishing a communication connection with the first network element. The first terminal receiving the first intent service information corresponding to the communication intent includes: the first terminal receiving the first intent service information corresponding to the communication intent through the communication connection. The method by which the first terminal establishes a communication connection with the first network element is described in the relevant section of the first aspect and will not be repeated here.

[0042] In conjunction with the second aspect, in one possible implementation, after the first terminal calls the first application associated with the aforementioned first intent service information to output the first intent service information, the method further includes: the first terminal generating operation information in response to an operation event of the first user regarding the first intent service information; the first terminal sending the operation information to the first network element or the second network element; and the first terminal receiving second intent service information, which is the intent service information updated based on the operation event.

[0043] For example, after the first terminal receives the second intent service information, the method further includes: the first terminal, based on the second intent service information, calling an application associated with the second intent service information to execute the task corresponding to the second intent service information.

[0044] In conjunction with the second aspect, in one possible implementation, the aforementioned communication content is transmitted via a session between the first terminal and the second terminal. Before the first terminal receives the first intent service information corresponding to the communication intent, the method further includes: the first terminal sending a second message to the first network element, the second message including information for indicating the session, the second message being used to instruct the first network element to insert into the session.

[0045] For example, the first terminal receives first intent service information corresponding to the communication intent, including: the first terminal receives a user plane message from the user plane network element serving the session, and the payload of the user plane message carries the first intent service information.

[0046] For example, the second message also includes indication information, which indicates that the transmission direction of the communication content is from the first terminal to the second terminal.

[0047] In conjunction with the second aspect, in one possible implementation, the aforementioned communication content is transmitted via a session between the first terminal and the second terminal. Before the first terminal receives the first intent service information corresponding to the communication intent, the method further includes: the first terminal sending a third message to the first network element, the third message including information for indicating the session, the third message being used to instruct the first network element to transmit the first intent service information with the media network element serving the session through the session.

[0048] For example, the first terminal receives a media plane message from a media network element serving the session, and the payload of the media plane message carries the first intent service information.

[0049] Thirdly, this application provides a communication device for performing the method in the first aspect or any possible implementation thereof. The communication device includes units for performing the method in the first aspect or any possible implementation thereof.

[0050] Fourthly, this application provides a communication device for performing the method in the second aspect or any possible implementation thereof. The communication device includes units for performing the method in the second aspect or any possible implementation thereof.

[0051] In the third or fourth aspect, the aforementioned communication device may include a transceiver unit and a processing unit. Further details regarding the transceiver unit and processing unit can be found in the device embodiments shown below. The beneficial effects of the third and fourth aspects described above can be referenced in the relevant descriptions of the first and second aspects, and will not be repeated here.

[0052] Fifthly, this application provides a communication device including a processor for executing the methods shown in any possible implementation of the first aspect, the second aspect, or any of the above-described aspects. Alternatively, the processor is configured to execute a program stored in a memory, wherein when the program is executed, the methods shown in any possible implementation of the first aspect, the second aspect, or any of the above-described aspects are executed.

[0053] In conjunction with the fifth aspect, in one possible implementation, the memory is located outside the aforementioned communication device.

[0054] In conjunction with the fifth aspect, in one possible implementation, the memory is located within the aforementioned communication device.

[0055] In this application, the processor and memory can also be integrated into a single device, that is, the processor and memory can be integrated together.

[0056] In conjunction with the fifth aspect, in one possible implementation, the communication device further includes a transceiver for sending or receiving information.

[0057] Sixthly, this application provides a communication device that may include a processor and an interface circuit connected together. The interface circuit is used for exchanging (or sending / receiving or inputting / outputting) information or data, and the processor is used to execute program instructions that cause the communication device to perform the methods described in the first aspect, the second aspect, or any possible implementation thereof. The interface circuit may be a communication interface or a transceiver. The transceiver may be a radio frequency module in the communication device, or a combination of a radio frequency module and an antenna, or an input / output interface of a chip or circuit.

[0058] In a seventh aspect, this application provides a readable storage medium storing program instructions that, when run on a computer, cause the computer to perform the method described in the first aspect, or the second aspect, or any possible implementation thereof.

[0059] Eighthly, this application provides a program product containing program instructions that, when run, cause the method described in any possible implementation of the first aspect, or the second aspect, or any of the aspects to be executed.

[0060] Ninthly, this application provides an apparatus, which can be implemented as a chip or as a device, including a processor. The processor is used to read and execute a program stored in a memory to execute one or more of the first and second aspects described above, or one or more of the communication methods provided in any possible implementation of any of the aspects. Optionally, the apparatus further includes a memory connected to the processor via a circuit. Further optionally, the apparatus includes a communication interface to which the processor is connected. The communication interface is used to receive information to be processed, the processor obtains the information from the communication interface, processes the information, and outputs the processing result through the communication interface. The communication interface can be an input / output interface.

[0061] In one possible implementation, the processor and memory can be physically independent units, or the memory can be integrated with the processor.

[0062] In a tenth aspect, this application provides a communication system, which includes a first network element and a second network element; optionally, the communication system further includes a first terminal and / or a second terminal. The first network element can be used to perform the method described in the first aspect or any possible implementation thereof. The second network element can be used to receive information from the first network element and / or send information to the first network element. The first terminal can be used to perform the method described in the second aspect or any possible implementation thereof.

[0063] The technical effects achieved in the above aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, which will not be repeated here. Attached Figure Description

[0064] Figure 1 is a conceptual schematic diagram of a communication method provided in an embodiment of this application;

[0065] Figure 2 is a simplified schematic diagram of the communication system provided in an embodiment of this application;

[0066] Figure 3 is a schematic diagram of a possible application scenario provided by an embodiment of this application;

[0067] Figure 4 is a simplified flowchart of the communication method provided in an embodiment of this application;

[0068] Figure 5 is a schematic flowchart of the first communication method provided in an embodiment of this application;

[0069] Figure 6 is a schematic flowchart of a second communication method provided in an embodiment of this application;

[0070] Figure 7 is a schematic diagram of a third communication method provided in an embodiment of this application;

[0071] Figure 8 is a schematic flowchart of the fourth communication method provided in the embodiments of this application;

[0072] Figure 9 is a schematic diagram of the fifth type of communication method provided in the embodiments of this application;

[0073] Figure 10 is a sixth flowchart illustrating the communication method provided in an embodiment of this application;

[0074] Figure 11 is a schematic diagram of the structure of the RTP message header extension provided in an embodiment of this application;

[0075] Figure 12 is a seventh flowchart illustrating the communication method provided in an embodiment of this application;

[0076] Figure 13 is a schematic diagram of the eighth communication method provided in the embodiments of this application;

[0077] Figure 14 is a structural schematic diagram of a communication device provided in an embodiment of this application;

[0078] Figure 15 is another structural schematic diagram of the communication device provided in an embodiment of this application;

[0079] Figure 16 is another structural schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0080] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0081] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: 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.

[0082] In the description of this application, the terms "first," "second," etc., are used only to distinguish different objects and do not limit the quantity or order of execution, nor do they imply that they are necessarily different. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0083] In this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0084] It should be understood that in this application, "when," "if," and "if" all refer to the device making a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment when it is implemented, nor do they imply any other limitations.

[0085] In this application, "simultaneously" can be understood as at the same point in time, within a period of time, or within the same cycle. In some scenarios, "simultaneously" can also be understood as "in parallel". The specific meaning can be understood in combination with the context.

[0086] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.

[0087] In addition, the terms “system” and “network” are often used interchangeably in this article.

[0088] It is understood that in the various embodiments of this application, expressions such as "B corresponding to A" and "B corresponding to / associated with A" all indicate that there is a correspondence between A and B, and B can be determined based on A. It should also be understood that determining / generating B based on A does not mean that B is determined / generated solely based on A; B can also be determined / generated based on A and / or other information.

[0089] The "Internet of Everything" in this application can be understood as a kind of "meaning-oriented communication." "Meaning-oriented communication" can also be understood as task-oriented or intent-driven communication. For example, centered on the user (such as a person or enterprise), multimodal information interaction between humans, machines, data, and intelligence is driven based on the user's intent or purpose, utilizing the inherent capabilities of communication, sensing, computing, data, and intelligence to ultimately achieve the user's communication intent or purpose; this is "meaning-oriented communication." See Figure 1, which is a conceptual schematic diagram of meaning-oriented communication provided in an embodiment of this application. As shown in Figure 1, devices such as mobile phones, extended reality (XR) glasses, drones, and service robots connected to the network can interact with intelligent agents (which can be network elements) in the network through multimodal interaction of intent / semantics / data. The intelligent agent utilizes the network's connectivity services, computing services, data services, sensing services, call services, cloud network infrastructure, etc., to achieve the user's communication intent or purpose.

[0090] It is understandable that in the field of artificial intelligence, "multimodal" usually refers to perceptual information, such as images, text, and speech. Multimodal input can help artificial intelligence understand the external world more accurately. In this application, "multimodal information" can be understood as information (or data) of multiple modalities or types, including but not limited to: text, images, videos, and speech.

[0091] One possible implementation involves using a messaging app to recognize user gestures in text or video messages and matching them against predefined rules. This can generate corresponding animation effects within the chat session, enhancing the fun of communication and strengthening the expression of user emotions and feelings. For example, recognizing keywords in user chat text (such as "Happy Birthday") can generate corresponding full-screen animations (such as a "cake" emoji rain). Similarly, recognizing specific gestures in video chat (such as "heart," "peace sign," or "thumbs up") can generate corresponding screen animation effects (such as "heart," "fireworks," or "like"). However, this approach only allows for simple recognition based on specific keywords or gestures and simple effect matching based on predefined rules; it does not support intelligent recognition and semantic understanding of the user's communication intent. Furthermore, this approach relies on a specific application platform for both parties, making it impossible to achieve cross-network, cross-platform services.

[0092] Therefore, this application provides a communication method, communication device, communication system, and readable storage medium that, during a user's call, identifies and understands the user's communication intent through the network side and provides the user with corresponding intent service information in the user's communication session, thereby providing the user with intent services that are independent of a specific application platform, realize the whole network and cross-platform, and improve communication efficiency.

[0093] To better understand this application, the communication system and possible application scenarios provided in this application are first introduced below. It should be understood that the system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0094] The communication system provided in this application can be an enhancement of an existing communication system, or it can be obtained by adding some network functions (NFs) to an existing communication system, or it can be a new communication system. This application does not impose any limitations. It is understood that the network function (NF) in this application can be simply referred to as a network element, and the two can be used interchangeably.

[0095] In one possible implementation, refer to Figure 2, which is a simplified schematic diagram of the communication system provided in an embodiment of this application. As shown in Figure 2, the communication system includes, but is not limited to, one or more of the following: network intelligent agent function (NIAF), intelligent session management function (ISMF), intent service registration function (ISRF), intent service function (ISF), (intelligent) terminal, or user data management function (UDMF). Exemplarily, the communication system also includes one or more of the following: application function (AF), or other network elements (e.g., computing service functions, data service functions, sensing service functions, cloud infrastructure control, etc.).

[0096] In one possible implementation, the Network Intelligent Agent Function (NIAF) can be used to receive communication content from user terminals and / or identify the communication intent within it. For example, the NIAF can also be used to query and / or invoke relevant Intent Service Functions (ISFs) to obtain intent service information. For example, the NIAF can also send intent service information to one or more (intelligent) terminals associated with the user. For example, the NIAF can also interact with other network elements (such as digital human management, subscription authorization management, multi-terminal management, etc.) to provide more input parameters for the Intent Service Functions (ISFs). For example, the NIAF can also process the obtained intent service information to adapt it to the user's terminal capabilities / terminal type, etc.

[0097] For example, NIAF can be divided into one or more of the following parts: user plane (e.g., multimodal interaction module), control plane (e.g., session management module), intelligence plane (e.g., intent processing module), or data plane (e.g., user information module). The user plane (e.g., multimodal interaction module) can be used to receive multimodal interaction information from user sessions and / or preprocess that multimodal interaction information. For example, the user plane (e.g., multimodal interaction module) can also output intent service information to the user session in a multimodal manner. The control plane (e.g., session management module) can be used to manage sessions related to intent communication (or expressive communication). For example, the control plane (e.g., session management module) can add / remove NIAF from user sessions, and / or add intent service information transmission channels to user sessions. The intelligence plane (e.g., intent processing module) can be used to identify the user's communication intent. For example, the intelligence plane (e.g., intent processing module) can be used to parse the communication content in the user session and intelligently identify the communication intent based on AI capabilities, and / or can be used to parse intent requests sent by the user terminal to obtain the user's communication intent. The data plane (such as the user information module) can be used to obtain information related to the user. For example, the data plane (such as the user information module) can obtain user-related contract / location information, multi-terminal information, digital human information, or network context status information, etc.

[0098] It is understood that the above-described module division of NIAF is merely an example, or in other words, the internal processing module of NIAF is only an example, and the embodiments of this application do not limit the internal design of NIAF.

[0099] In one possible implementation, NIAF can be deployed as an independent network element (NF) (in the core network) or it can be deployed in conjunction with other network elements. For example, NIAF can be part of the user plane function (UPF).

[0100] In one possible implementation, the Intelligent Session Management Function (ISMF) can be used to establish (intelligent) sessions between various (intelligent) terminals and the Network Intelligent Agent Function (NIAF). For example, the ISMF can be deployed as a standalone network element (NF) (in the core network), or it can be a newly defined independent network element; it can also be deployed in conjunction with other network elements, for example, the ISMF can be an enhancement of existing network elements (such as the policy control function (PCF), access and mobility management function (AMF), and / or session management function (SMF)).

[0101] In one possible implementation, the Intent Service Function (ISF) can be understood as a service provided to achieve a specific communication intent (or user intent). The ISF can be used to generate intent service information. For example, the input to the ISF may include the communication intent identified by the NIAF, and / or user-related information (e.g., user subscription / location information, multi-terminal information, digital human information, or network context state information, etc.), and the output of the ISF may include intent service information. For example, the intent service information can be multimodal, such as text, voice, video, image, and / or haptic feedback.

[0102] In one possible implementation, the Intent Service Registration Function (ISRF) can be used to record registered ISFs in the network. For example, the ISRF can also be queried by the NIAF and return the corresponding ISF information. For instance, ISF information includes, but is not limited to, one or more of the following: the ISF's intent service capabilities, connection method (or access method), invocation parameters (or input parameters), or output format. For example, the ISF's connection / access method can include, but is not limited to, the protocol used to access the ISF (e.g., Hypertext Transfer Protocol (HTTP)) or a method of the protocol (e.g., the HTTP GET method). The ISF's output format can be understood as the format of the ISF's output parameters, including, but not limited to, the modality of the output parameters, such as text / voice / video; the display format, such as 2D / 3D / VR / AR; the resolution; and / or the type of intent service information.

[0103] In one possible implementation, the terminal can be connected to a network and used to transmit intent-related data. For example, the terminal can also use an Intent Service Function (ISF) to receive and display intent service information. The terminal in this application embodiment can include various smart terminals, such as mobile phones, XR glasses, IoT terminals, drones, robot dogs, robots, etc. In mobile communication networks, the terminal is also often referred to as user equipment (UE). In other words, "terminal" and "UE" can be used interchangeably in this application. However, this application is not limited to mobile communication networks and can also be applied to other future or existing communication networks, such as wireless local area networks (WLANs) or wireless personal area networks (WPANs).

[0104] In one possible implementation, the User Data Management Function (UDMF) can be used to manage user-related data, including but not limited to one or more of the following: the user's digital human information (such as the digital human's related identifiers, appearance, identity role, or business permissions), user-related multi-terminal information (such as the terminal type, capabilities, or location), the user's number (such as the subscriber identification module (SIM) number), service subscription information, personal preferences, or other personalized information. This data can be accessed by the NIAF to provide the ISF with input parameter information related to intent services; and / or, for the NIAF to process the intent service information output by the ISF. For example, digital human information, multi-terminal information, user preferences, and service authorization information can be managed by separate sub-modules. As shown in Figure 2, the UDMF includes one or more of the following (sub)modules: digital human management (e.g., for managing the user's digital human information), multi-terminal management (e.g., for managing user-related multi-terminal information), user preference management (e.g., for managing the user's personal preferences and / or other personalized information), or subscription authorization management (e.g., for managing the user's service authorization). Of course, these sub-modules can also be deployed independently as network elements. It is understood that the internal processing module of the UDMF shown in Figure 2 is merely an example, and the embodiments of this application do not limit the internal design of the UDMF.

[0105] In one possible implementation, the application function (AF) can be a third-party application server that participates in the user session.

[0106] It is understood that the names of the various network elements and / or (sub)modules shown in Figure 2 are merely examples, and this application does not limit the names of the various network elements and / or (sub)modules shown in Figure 2. Furthermore, the embodiments of this application do not limit the specific technologies and specific equipment forms adopted by the various network elements and / or (sub)modules shown in Figure 2.

[0107] Referring to Figure 3, which is a schematic diagram of a possible application scenario provided by an embodiment of this application, as shown in Figure 3, during communication, User 1 sends an invitation to User 2. The Network Intelligent Agent Function (NIAF) can use AI capabilities to analyze User 1's communication content, identify User 1's communication intent, and query and call relevant intent service functions (such as travel, movies, shopping, ordering food, etc.) from the system (e.g., ISRF) based on this communication intent. Furthermore, NIAF can obtain intent service information related to the user's communication intent (such as tourist destination images / videos generated through artificial intelligence generated content (AIGC), clothing styles matching the user's digital avatar, and movie posters matching the preferences of both users). This intent service information can be interactive (e.g., User 1 and User 2 can select and / or confirm movie posters, showtimes, seats, etc., presented on the terminals). Intent service information can help users effectively convey their intent and achieve consensus. NIAF can also drive the user's multiple terminals to perform corresponding intelligent tasks (such as setting itineraries, event reminders, etc.) based on the results of intent consensus.

[0108] In this application, the user's "communication intent" can be understood as a "goal / purpose" that the user expects to achieve. This "goal" may include the desire to perform a certain task (which can be broken down into multiple sub-tasks / actions), or the desired state / result (for example, in human-machine communication, the machine may be instructed to reach a certain state, such as a drone maintaining a certain altitude for cruising, or establishing a low-latency, highly reliable private network). The "intent service information" related to the "user's communication intent" can be understood as relevant information that assists / supports the user in expressing / transmitting / achieving the desired "goal / purpose".

[0109] The technical solution provided in this application is described in detail below.

[0110] To facilitate a clear description of the technical solutions of this application, multiple embodiments are used for illustration, as detailed in the following descriptions of the various embodiments. In this application, unless otherwise specified, the same or similar parts between different embodiments or implementations can be referenced interchangeably. In the various embodiments of this application, and in the various implementation methods / methods / implementations within those embodiments, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within those embodiments are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within those embodiments can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments described below do not constitute a limitation on the scope of protection of this application. It is understood that the order of the embodiments below does not represent their importance.

[0111] It should be understood that in this application, the indication includes direct indication (also known as explicit indication) and implicit indication. Direct indication information A refers to information A being included; implicit indication information A refers to information A being indicated through the correspondence between information A and information B, and through direct indication information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0112] It should be understood that in this application, information C is used to determine information D, which includes both determining information D based solely on information C and determining it based on information C and other information. Furthermore, the use of information C to determine information D can also include indirect determination, such as when information D is determined based on information E, and information E is determined based on information C.

[0113] Furthermore, in the embodiments of this application, "network element A sends information A to network element B" can be understood as network element B being the destination of information A or an intermediate network element in the transmission path between the destination and network element B, which may include sending information directly or indirectly to network element B. "Network element B receives information A from network element A" can be understood as network element A being the source of information A or an intermediate network element in the transmission path between the source and network element A, which may include receiving information directly or indirectly from network element A. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way and will not be elaborated further here.

[0114] In one possible implementation, the first network element of this application can be NIAF, the second network element can be ISF, the third network element can be ISRF, and the fourth network element can be ISMF. The media network element (MF) in this application can be used for media forwarding and processing of user communication content (which can be represented by some media format), such as optimizing, enhancing, compressing, and transcoding media carrying communication content (e.g., audio, video, text, images, etc.). For example, the media network element can be a unified media function (UMF). It is understood that the descriptions of various network elements in this application are merely examples, and any network element that can implement the technical solution of this application is within the protection scope of this application.

[0115] The overall process of the technical solution in this application will be briefly introduced below.

[0116] In one possible implementation, this application introduces a Network Intelligent Agent (NIAF) function into the network. Leveraging the network's inherent AI capabilities and Intent Service Functions (ISF) provided by terminals or external applications, it identifies the user's intended communication intent / purpose during communication and displays intent service information related to the user's communication intent in a multimodal / multi-terminal manner. This intent service information is added to the user's communication session and returned to the user, thereby helping both parties better understand each other's communication intent. Furthermore, bidirectional interaction can be performed based on this intent service information to reach an intent consensus result, which can then drive the execution of intelligent tasks related to the intent consensus result.

[0117] For example, referring to Figure 4, which is a simplified flowchart of the communication method provided in an embodiment of this application. As shown in Figure 4, the communication method may include, but is not limited to, steps S1 to S4. In one possible implementation, before step S1, the communication method shown in Figure 4 may further include step S0. In one possible implementation, after step S4, the communication method shown in Figure 4 may further include steps S5 and / or S6.

[0118] S0, Register Intent Service Function (ISF).

[0119] In one possible implementation, an Intent Service Function (ISF) can be registered with an Intent Service Registration Function (ISRF) so that other network elements can discover / query the ISF through the ISRF and / or use the services provided by the ISF. This application does not limit the registration process between the ISF and the ISRF. For example, different Intent Service Functions can provide different services; of course, multiple Intent Service Functions may provide the same service, and this application does not impose any restrictions.

[0120] For example, the registration information of an intent service function (or the information registered by the intent service function (ISF) to the intent service registration function (ISRF)) may include one or more of the following: the category of the intent service function (e.g., shopping, travel, transportation, education, dining, etc.); keywords used to match and search for the intent service function; the semantics used to search for the intent service function; the service capabilities of the intent service function (e.g., a description of what intents or tasks the intent service function can handle, which can be a description based on natural language or a machine-readable formal language, such as Extensible Markup Language (XML), JSON (JavaScript Object Notation), or YAML (YAML Ain't a Markup Language)); and the application programming interface (API) or uniform resource locator (URL) of the intent service function. The locator (URL), the output format of the intent service function (e.g., image, video, 360-degree panoramic information, etc.), the calling parameters (or input parameters) of the intent service function, the multimodal interaction capabilities of the intent service function (e.g., text, voice, image, touch, etc.), or the multimedia parameters of the intent service function (e.g., encoding / decoding, bandwidth, latency, etc.).

[0121] S1, Activate Intent Assistance to insert Network Intelligent Agent Function (NIAF) into the user session.

[0122] In one possible implementation, the intent assistance function is activated on the user side (e.g., the user's terminal) or the network side (e.g., the user plane function (UPF) or media function (MF)). The network side can add the Network Intelligent Agent Function (NIAF) to the user session and establish a multimedia session channel for transmitting intent service information. "Inserting NIAF into the user session" can be understood as: when the UPF or MF receives a session message from the terminal, it can forward that session message to the NIAF.

[0123] S2 identifies the user's communication intent.

[0124] In one possible implementation, the Network Intelligent Agent Function (NIAF) can identify a user's communication intent based on one or more session messages (or communication content). For example, the NIAF can use AI Agent functionality to identify one or more session messages (or communication content) based on text, speech, semantic recognition, and large AI models to determine the user's communication intent.

[0125] As we can understand, a large AI model, also known as a foundation model, is a computer model that, through learning and training on massive amounts of data, can understand human language and semantics and extract useful information from them. A large AI model can be composed of multiple sub-models and can be divided into two types: neural network models and non-neural network models.

[0126] S3, query and invoke intent service functions.

[0127] In one possible implementation, the Network Intelligent Agent Function (NIAF) can query and invoke intent service functions. For example, based on the identified user's communication intent, NIAF can query registered and / or system-native intent services (such as AIGC) to find an intent service function matching the communication intent, and then invoke that intent service function. The intent service function can generate relevant intent service information based on the communication intent and return that information to NIAF.

[0128] S4 sends the intent service information generated by the intent service function to the user, thereby providing the user with the corresponding intent service.

[0129] In one possible implementation, the Network Intelligent Agent Function (NIAF) can send the intent service information returned by the Intent Service Function (ISF) to one or more terminals associated with the user. For example, NIAF can select the optimal multimodal presentation format to send the intent service information to the user based on the capabilities of the one or more terminals associated with the user. For instance, for VR glasses, the intent service information can be presented in a 360° panoramic mode, while for mobile phones or tablets, it can be presented in a planar mode. The presentation method may include customizing and / or filtering the content of the intent service information based on the user's digital human information (identity / digital avatar / preferences, etc.).

[0130] In this application, descriptions such as "user-related terminal" or "user-corresponding terminal" can refer to a terminal associated with / bound to a user's identifier (e.g., mobile phone number, personal account, or ID card number).

[0131] S5 allows users to engage in multimodal information interaction based on intent service information.

[0132] In one possible implementation, if the intent service information is interactive, users can perform actions such as marking, selecting, sorting, ordering, or confirming on the terminal based on the content of the intent service information. The terminal can send the user's operation information regarding the intent service information to the Network Intelligent Agent Function (NIAF). NIAF can then synchronize the user's operation process (such as mouse movements, finger touch points, or eye focus) and / or results to other users in real time via multimedia streaming. During this process, NIAF can utilize the user's digital human information (such as digital identity) for security authentication and / or authorization.

[0133] S6 triggers multiple terminals to execute related tasks based on intent service information.

[0134] In one possible implementation, the Network Intelligent Agent (NIAF) function can drive multiple user-related terminals to perform corresponding intelligent tasks based on the user's confirmation in the intent service information through the AI ​​Agent function. For example, NIAF can send instructions to user-related terminals to set mobile phone calendar reminders, set the destination / route of a smart car, trigger VR headsets (i.e., head-mounted displays, HMDs) to download and install software, or command drones or robots to go to a designated destination, collect and transmit images and videos, etc.

[0135] In this embodiment, the NIAF is inserted into the user session on the network side or the user side. The NIAF on the network side identifies the communication intent in the user's communication content and calls the relevant intent service function to generate intent service information related to the communication intent and return it to the user. This helps both parties in the communication to better understand the intent they want to convey to each other. Since the NIAF and ISF can be deployed in the core network, the transmission of communication intent across the entire network and across platforms can be realized, helping users to quickly reach a consensus on intent and thus improve communication efficiency.

[0136] The communication method provided in this application is described in detail below.

[0137] Referring to Figure 5, which is a schematic flowchart of the first communication method provided in this application embodiment, the method mainly describes how NIAF generates intent service information adapted to different terminal capabilities by calling the AIGC capability of ISF and feeding it back to the user, thereby providing intent services to the user. As shown in Figure 5, this communication method includes, but is not limited to, the following steps:

[0138] S101, Terminal A and Terminal B communicate.

[0139] In one possible implementation, user 1 and user 2 can establish a multimedia communication session (referred to as a multimedia call) through their respective personal terminals (i.e., terminal A and terminal B), such as voice calls, video calls, or text chats. Before or during a multimedia call, an intent-assisted function can be activated to enable the network-side NIAF to receive session messages forwarded by other network elements (such as UPF). The specific implementation of activating the intent-assisted function can be found in the description of the embodiments below, and will not be elaborated here. It is understood that "activating the intent-assisted function" in this application can be interpreted as "inserting the NIAF into the user session (such as terminal A and terminal B establishing a multimedia call)," thereby enabling the network-side NIAF to receive user session messages or user communication content forwarded by other network elements (such as UPF).

[0140] In one possible implementation, in response to user 1's action (such as making a voice or video call), terminal A can send a session establishment request to the network. This request may include the identifiers of both parties (i.e., terminal A and terminal B), the multimedia type, and call parameters (such as text, audio / video codec parameters, etc.). The network can allocate available resources based on terminal A's request and respond with a session establishment response. The network then establishes a multimedia call connection between terminal A and terminal B based on terminal A's request. After receiving the session establishment response, terminal A can establish a communication connection with the network. Once the session is established, terminal A can send a service activation request to the network. This request includes the service type (such as intent-assisted functions) and related parameters. Based on terminal A's request, the network configures the corresponding service functions, adds NIAF to the user session, and responds with a service activation response. After service activation, users 1 and 2 can interact with multimedia data (including communication content) through terminals A and B. NIAF can obtain this multimedia data (including communication content) to identify the user's communication intent and provide corresponding intent service information based on the user's communication intent.

[0141] In one possible implementation, terminal A can carry communication content input by user 1 (e.g., information of various types / modalities such as text, audio, video, and images) in a session message and send it to terminal B. Terminal B can also carry communication content input by user 2 in a session message and send it to terminal A. The session message sent from terminal A to terminal B can be forwarded through the base station connected to terminal A to the user plane function (denoted as UPF-A, hereinafter referred to as UPF-A). UPF-A can forward the session message to the user plane function (denoted as UPF-B, hereinafter referred to as UPF-B). If the intent assist function is activated, UPF-A can also forward the session message to NIAF, or UPF-A can extract the communication content from the session message and send the communication content to NIAF. After receiving the session message forwarded by UPF-A, UPF-B sends the session message to terminal B. Similarly, a session message sent from terminal B to terminal A can be forwarded to UPF-B via the base station connected to terminal B. UPF-B then forwards the session message to UPF-A and / or NIAF. UPF-A then sends the received session message to terminal A. Depending on the network deployment, UPF-A and UPF-B may be the same entity. It can be understood that the session message can also be processed and forwarded by the Application Function (AF) between UPF-A and UPF-B. For example, when UPF-B forwards a session message to UPF-A, it may need to be processed and forwarded by the AF before reaching UPF-A.

[0142] It is understandable that if the intent assist function is activated during a multimedia call, UPF-A and / or UPF-B can forward historical session messages or historical communication content exchanged between terminal A and terminal B during the multimedia call before the activation of the intent assist function to NIAF, so that NIAF can better identify the user's communication intent.

[0143] In one possible implementation, the communication content of user 1 may include user 1's communication intent, such as inviting user 2 to travel to a certain place, or purchasing clothing, jewelry, game items, etc. for user 2. In another possible implementation, terminal A may carry the user's communication intent in the session message in an unstructured data form (such as through natural language or text), or in a specific structured data form (such as a predefined intent message format). The user's communication intent may be identified by terminal A through the user's communication content, or it may be explicitly expressed by the user. It is understood that if terminal A carries the user's communication intent in the session message, then after receiving the session message, NIAF does not need to identify the user's communication intent again, but can directly query the ISRF for the ISF that supports the communication intent. In other words, if terminal A carries the user's communication intent in the session message, the communication method of this embodiment may skip step S102 and jump to step S103.

[0144] S102, NIAF identifies the user's communication intent based on the received communication content.

[0145] In one possible implementation, during a multimedia call between terminal A and terminal B, the NIAF can perform intent recognition on the communication content in one or more received session messages, or perform intent recognition on the received communication content, to obtain the communication intent of user 1. These one or more session messages may include session messages (i.e., the context content of the user's dialogue) exchanged between terminal A and terminal B during the multimedia call over a period of time.

[0146] For example, NIAF can use technologies such as text, speech, semantic recognition, or large AI models to identify the communication intent contained in the communication content. NIAF can also call on AI algorithm engines, external resources or services (such as web search, semantic knowledge bases, etc.) to further identify the communication content, thereby enhancing the accuracy of intent recognition.

[0147] For example, after obtaining the communication intent of User 1, NIAF can engage in two-way communication with User 1 to make a more accurate judgment on User 1's communication intent. For instance, NIAF can use intelligent question answering or utilize the Prompt mechanism in the AI ​​large model to communicate with User 1 to confirm whether the intent recognition result is accurate. NIAF can use the communication intent confirmed by User 1 as the final intent recognition result. In other words, NIAF can perform subsequent operations based on the communication intent confirmed by User 1, such as querying the ISF that supports the communication intent in step S104 below.

[0148] The following examples illustrate the communication intent identified by NIAF in various scenarios. It can be understood that the communication content in the following scenarios can be carried in multiple session messages. It can also be understood that the communication content in the following scenarios can be a portion of the communication content exchanged between terminal A and terminal B during a multimedia call.

[0149] Scene 1: Tourism and Vacation Scene

[0150] User 1: "Let's go on our honeymoon to Erhai Lake together."

[0151] User 2: "What's the scenery like at Erhai Lake? Is it suitable for taking wedding photos?"

[0152] User 1: "There are popular photo spots like A, B, and C. The scenery is beautiful and they are perfect for taking wedding photos. I'll have Intent Assistant send them to you."

[0153] Based on the above communication content, NIAF identified that User 1's communication intent was to send wedding photo renderings of scenic spots a, b, and c to User 2.

[0154] Scenario 2: Shopping Scenarios

[0155] User 1: "I saw a really pretty A-line dress online. How about I give it to you as a birthday present?"

[0156] User 2: "I've recently gained weight and got a new hairstyle, so I'm afraid it won't suit me."

[0157] User 1: "No problem, I'll have the Intent Assistant send you the try-on effect. You'll need to authorize your digital human avatar."

[0158] Based on the above communication content, NIAF identified that User 1's communication intent was to send User 2 the effect of trying on style a clothing.

[0159] Scenario 3: Education / Communication Scenarios

[0160] User 1: "What is Schrödinger's cat?"

[0161] User 2: "It is a thought experiment in quantum mechanics about the collapse of superposition states."

[0162] User 1: "I still don't understand. Could you explain it again?"

[0163] User 2: "I can't explain it clearly. Let me have the Intent Assistant explain it to you in a more vivid way."

[0164] Based on the above communication content, NIAF identified that User 2's communication intention was to explain the "Schrödinger's cat" thought experiment to User 1 in a vivid way.

[0165] Scenario 4: Real-view navigation scenario

[0166] User 1: "Hello, could you please tell me the exact location of your interview location A? I can't find it."

[0167] User 2: "Please wait a moment, I'll have the intent assistant help you with the real-view navigation."

[0168] Based on the above communication content, NIAF identified that user 2's communication intent was to help user 1 find destination a through real-view navigation.

[0169] Scenario 5: NIAF will send the identified communication intent to the user for confirmation, or ask the user questions about the uncertain parts of the communication intent and obtain the user's answer.

[0170] For example, in the aforementioned scenario 2, after recognizing the communication intent of user 1, NIAF can also send a message to terminal A, which carries the following content: Do you want to "send the effect of trying on xx style of clothing on user B"?

[0171] User 1 replies "Yes" via terminal A. NIAF can then perform subsequent operations based on User 1's confirmed communication intent.

[0172] For example, in the aforementioned scenario 1, after recognizing user 1's communication intent, NIAF can also send a message to terminal A, which carries the following content: Would you like a "Chinese" style or a "Western" style wedding photo effect?

[0173] User 1 replies via terminal A: "Western style". NIAF can then update User 1's communication intent to: "Send Western-style wedding photo renderings of locations a, b, and c to User 2". NIAF can then perform subsequent operations based on this updated communication intent.

[0174] S103, NIAF sends query message 1 to ISRF. Query message 1 is used to query the ISF that supports the above communication intent.

[0175] S104, the ISRF sends Query Response 1 to the NIAF. Query Response 1 includes information from the ISF that supports the aforementioned communication intent.

[0176] In one possible implementation, after determining the user's communication intent, the NIAF can send a query message 1 to the ISRF. This query message 1 can include information describing the communication intent and can be used to query an ISF that supports the communication intent. For example, the information describing the communication intent includes, but is not limited to, one or more of the following: the category of the communication intent, the topic of the communication intent, the keywords of the communication intent, or the semantics of the communication intent. The semantics of the communication intent can be semantics directly based on text description or semantics processed through vectorization embedding techniques. For example, the communication intent identified in scenario 1 above could be categorized as "tourism," with themes such as "honeymoon, wedding photos," and keywords such as "scenic spot a, scenic spot b, scenic spot c." The communication intent identified in scenario 2 above could be categorized as "shopping," with themes such as "trying on clothes," and keywords such as "style a." The communication intent identified in scenario 3 above could be categorized as "education," with themes such as "Schrödinger's cat," and keywords such as "quantum mechanics." The communication intent identified in scenario 4 above could be categorized as "transportation," with themes such as "real-time navigation," and keywords such as "location a." In Scenario 1, the semantics of the communication intent can be the text "Send wedding photo renderings of scenic spots a, b, and c to user 2", or text with the same or similar semantics (such as an English translation), or a string of numerical vectors (such as [-0.4685, 0.4572, 0.5159, -0.2618, -0.6871, ...]) after the text has been processed by a machine semantic vectorization algorithm, representing the vector mapping of the text in a high-dimensional semantic space.

[0177] After receiving query message 1, the ISRF can search among registered ISFs for ISFs that support the communication intent. For example, the ISRF can search among registered ISFs for ISFs that match the communication intent (e.g., searching among registered ISFs for ISFs whose service capabilities can handle the communication intent), or ISFs that match the category, topic, keywords, and / or semantics of the communication intent, or a combination of several query methods. When using semantic matching, query matching can be based on vectorized semantic associations. In this case, the ISRF itself can act as a vector database storing vectorized ISF registration information (during ISF registration, its original registration information is vectorized, and the processed registration information vector is associated with and stored with the original registration information). It can also calculate the similarity between the semantic vector of the communication intent and the ISF registration information vector within the ISRF, thereby returning one or more ISFs with high similarity (e.g., top K, or similarity greater than a certain threshold). If the ISRF finds an ISF among the registered ISFs that supports the communication intent (e.g., an ISF that matches the category, topic, keywords, or semantics of the communication intent), the ISRF can send query response 1 to the NIAF. Query response 1 can include information about one or more ISFs that support the communication intent. For example, for scenarios 1 and 2 above, travel ISFs and shopping ISFs can be queried respectively. Both (i.e., travel ISFs and shopping ISFs) can provide AIGC functionality, enabling the generation of corresponding intent service information based on the user's communication intent. For instance, if the ISRF finds multiple ISFs that support the communication intent, the ISRF can return the information of these multiple ISFs to the NIAF, or it can select (which can be arbitrary or based on the ISRF's internal strategy (e.g., load balancing)) a ​​subset of ISFs (this embodiment does not limit the selection) and include the information of these subset ISFs in query response 1 to return to the NIAF. Alternatively, the ISRF can return the information of the first ISF found that supports the communication intent to the NIAF. The ISF information in query response 1 may include, but is not limited to, one or more of the following: the ISF's access address (such as the ISF's API, URL, or MAC address), the ISF's identifier, or the ISF's name. It is understood that this ISF information can be used to identify the ISF.

[0178] If the ISRF finds no registered ISF that supports the communication intent (e.g., no registered ISF matches the category of the communication intent), the ISRF can send a query failure message to the NIAF. This message can include the reason for the failure (e.g., "Unable to find an ISF that supports the communication intent"). Upon receiving this message, the NIAF can send a query message to other ISRFs to find an ISF that supports the communication intent. Alternatively, the NIAF can notify the user's relevant terminal (e.g., terminal A) that the intent service corresponding to the communication intent is not supported.

[0179] In one possible implementation, the query message 1 may further include the type or capability of terminal A and / or terminal B. The ISRF can filter ISFs from the queried ISFs supporting the communication intent, selecting those whose output format matches the type / capability of terminal A and / or terminal B, and return the information of the filtered ISFs to the NIAF via query response 1. For example, the type or capability of terminal A and terminal B can be understood as the information display methods supported by terminal A and terminal B. For example, terminal A is a mobile phone, supporting two-dimensional planar display. For example, terminal B is a VR headset, supporting 360-degree panoramic and three-dimensional stereoscopic display. For example, the output format of the ISF may include, but is not limited to: planar images, three-dimensional images, two-dimensional (2D) video, three-dimensional (3D) video, or 360-degree panoramic information, etc.

[0180] In one possible implementation, NIAF can access a local database to query the capabilities / types of terminal A and terminal B. Alternatively, NIAF can query the UDMF for the capabilities / types of terminal A and terminal B. Or, NIAF can first query the local database for the capabilities / types of terminal A and terminal B; if the local database does not store the capabilities / types of terminal A and terminal B, it can then query the UDMF for them. For example, NIAF can send query message 2 to the UDMF, which may include the identifiers of terminal A and terminal B (such as IDs or MAC addresses). This query message 2 can be used to query the capabilities / types of terminal A and terminal B. After receiving query message 2, the UDMF can query the capabilities / types of terminal A and terminal B locally and can return query response 2 to NIAF, which includes the queried capabilities / types of terminal A and terminal B. For example, query response 2 may also include one or more of the following: the current load of terminal A, the operating mode of terminal A, the current load of terminal B, or the operating mode of terminal B. It is understandable that, depending on the network subscription affiliation, querying the capabilities / types of terminal A and terminal B may require negotiation between the respective NIAFs to which terminal A and terminal B belong. For example, when the NIAF to which terminal A belongs (denoted as NIAF-A) needs to obtain the capabilities / types of terminal B, it can send an intent request to the NIAF to which terminal B belongs (denoted as NIAF-B). This intent request can include the identifier of terminal B and can be used to obtain the capabilities / types of terminal B. This intent request can be sent using natural language text, a large model-based prompt, or a service-based interface. NIAF-B can then obtain the capabilities / types of terminal B from the UDMF (denoted as UDMF-B) in terminal B's home network and return it to NIAF-A. Message routing between NIAF-A and NIAF-B can be based on pre-configured network settings or forwarded based on the addresses and domain names of NIAF-A and NIAF-B.

[0181] In one possible implementation, the query response 1 may further include one or more of the following: ISF invocation parameters (or input parameters), ISF output format, ISF service capabilities, ISF subscription and / or permission information, ISF capability or status information, ISF access method, or ISF network resource requirements. The ISF invocation parameters (or input parameters) may include necessary parameters required for the ISF to generate intent service information, such as communication intent, or information describing that communication intent. For example, the ISF invocation parameters (or input parameters) may also include one or more of the following: the user's digital human information, the user's personalized information, or the user's geographic location information (such as latitude and longitude, or Global Positioning System (GPS) location). The ISF subscription and / or permission information may include the ISF's subscription information with user 1 and user 2, the permission information of user 1 and user 2 within the ISF, the level-related condition information of user 1 and user 2, and the ISF's service fee information. ISF capability information may include the degree of matching / relevance with the aforementioned communication intent (expressed as a percentage, rating, or grade, etc.). ISF status information may include the current load of the ISF. ISF network resource requirements may include the ISF's computing power, bandwidth, or latency, etc. ISF access methods may include the protocol used to access the ISF (such as the HTTP protocol), and / or a certain method of the protocol (such as the HTTP GET method).

[0182] In one possible implementation, if the query response 1 includes ISF call parameters, after receiving the query response 1, the NIAF can obtain the value corresponding to the call parameters based on the ISF call parameters. Here, "value" does not necessarily refer to an index value, but rather to the content of the call parameters. For example, if the ISF call parameters include digital person information, the NIAF can query the UDMF for the digital person information of user 1 and / or user 2. For instance, the NIAF can send query message 3 to the UDMF, which may include the identification information of user 1 and / or user 2 (such as the International Mobile Subscriber Identity (IMSI)). This query message 3 can be used to query the user's digital person information. After receiving query message 3, the UDMF can query the digital person information of user 1 and / or user 2 locally and can return query response 3 to the NIAF, which may include the digital person information of user 1 and / or user 2. It is understandable that, depending on the network contract ownership, querying digital human information may require negotiation between the NIAF to which terminal A and terminal B belong, respectively. For details, please refer to the previous section on querying the capabilities / types of terminal A and terminal B, which will not be repeated here.

[0183] The digital human information may include, but is not limited to, one or more of the following: digital human identifier, digital human image, or digital identity authorization information. For example, in scenario 1 above, NIAF obtains the digital human images of user 1 and user 2 respectively through UDMF (which can be used to generate wedding photo renderings). In scenario 2 above, NIAF obtains the digital human image of user 2 through UDMF (which can be used to generate try-on renderings).

[0184] It is understandable that if the digital human information includes digital identity authorization information, then the process by which NIAF obtains the user's digital human information also includes an authorization interaction process with the user. This authorization interaction process can be conducted by NIAF or UDMF interacting with the user to obtain the user's digital identity authorization. For example, taking the authorization interaction process with user 1 as an example, NIAF or UDMF can send a digital identity authorization request to terminal A, which can be used to request authorization from user 1. After receiving the digital identity authorization request, terminal A can output and display the digital identity authorization request. User 1 can operate on terminal A to confirm whether to authorize. If user 1 confirms the authorization, terminal A can generate a digital identity authorization (e.g., an authorization token) and return it to NIAF or UDMF. The authorization interaction process for user 2 is the same as that for user 1, and will not be described in detail here.

[0185] For example, the ISF's call parameters include the terminal's location information (such as latitude and longitude, or GPS location). NIAF can obtain the location information from terminal A and / or terminal B. For instance, taking NIAF obtaining the location information of terminal A as an example, NIAF can send a location acquisition request to terminal A. After receiving the location acquisition request, terminal A can perform positioning (such as enabling GPS) to obtain its own geographical location and can return its geographical location information to NIAF. NIAF can also directly obtain the location information of terminal A through the location service function in terminal A's home network. The way NIAF obtains the location information of terminal B is the same as the way it obtains the location information of terminal A, and will not be described in detail here. For example, in scenario 4 above, NIAF obtains the location information of terminal A (which can be used for augmented reality navigation).

[0186] In another possible implementation, after obtaining the aforementioned communication intent (as described in step S103 above), the NIAF can send the communication intent to the AI ​​big data model. The AI ​​big data model then analyzes and obtains the calling parameters (or input parameters) required to generate the intent service information, and transmits them to the NIAF. For example, in scenario 1 above, after analyzing user 1's communication intent, the AI ​​big data model can determine that the calling parameters include the digital human images of user 1 and user 2. As another example, in scenario 2 above, after analyzing user 1's communication intent, the AI ​​big data model can determine that the calling parameters include user 2's digital human image. And as yet another example, in scenario 4 above, after analyzing user 2's communication intent, the AI ​​big data model can determine that the calling parameters include user 1's location information. Then, the NIAF can obtain the value corresponding to the calling parameters, as described above, and will not be repeated here.

[0187] In one possible implementation, the ISF can also be deployed internally within NIAF as a built-in function. In this case, after NIAF determines the user's communication intent, it does not need to externally query for ISFs that support that intent; NIAF can directly determine the ISF that supports it. NIAF can also obtain the calling parameters of the ISF that supports the communication intent and, based on the calling parameters of the ISF, obtain the corresponding values ​​of those calling parameters. See the previous description for details, which will not be repeated here.

[0188] S105, NIAF sends information describing the aforementioned communication intent to the queried ISF.

[0189] S106, the ISF sends intent service information corresponding to the above communication intent to the NIAF.

[0190] In one possible implementation, NIAF invokes the queried ISF, providing necessary invocation parameters (such as information describing the aforementioned communication intent, a digital human image, or the terminal's location information) to generate intent service information. For example, NIAF can send message A to the queried ISF, which may include information describing the aforementioned communication intent. Message A can then be used to invoke the ISF to generate intent service information corresponding to that communication intent.

[0191] In one possible implementation, before invoking the queried ISF, NIAF can further access other external services or resources (such as web search, websites, semantic knowledge bases, etc.) to obtain more information about the invocation parameters (such as semantics similar to the invocation parameters of the ISF, or multimedia materials associated with the invocation parameters of the ISF). For example, for scenario 3 above, if the invocation parameters of the ISF include the keyword "Schrödinger's cat" indicating the communication intent, then the similar semantics of the invocation parameter "Schrödinger's cat" could be "quantum superposition thought experiment"; the associated multimedia materials could be "photographs of Schrödinger", "pictures of cats", or "theoretical formulas of Schrödinger", etc.

[0192] In one possible implementation, if the query response 1 includes information from multiple ISFs, the NIAF can select one ISF from these ISFs and send message A to that ISF. Message A may include information describing the communication intent. Message A can be used to invoke the ISF to generate intent service information associated with the communication intent. For example, the NIAF can select one ISF based on its output format, subscription and / or permission information, capability or status information, or network resource requirements. For instance, the NIAF can select the ISF whose capability information matches the communication intent most closely, or whose output format matches the terminal capability most closely, or whose output format matches the NIAF's own secondary processing capability most closely, or whose current load is the lowest, or whose call parameter requirements are met most readily, or whose service cost is the lowest, or select an ISF based on other strategies / conditions.

[0193] In one possible implementation, after receiving message A, the ISF can generate intent service information associated with the communication intent based on message A, and can send message B to the NIAF, which includes the intent service information associated with the communication intent. For example, message A may include other calling parameters in addition to information describing the communication intent. For instance, in scenario 1, message A may also include the digital avatars of user 1 and user 2; in scenario 2, message A may also include the digital avatar of user 2; and in scenario 4, message A may also include the location information of user 1. It can be understood that the ISF can provide AIGC capabilities, enabling it to generate corresponding intent service information based on the input communication intent. For example, in scenario 1, the tourism ISF can generate virtual wedding photos or short videos (i.e., intent service information) of user 1 and user 2 at scenic spots a, b, and c in Erhai Lake based on user 1's communication intent and the digital avatars of user 1 and user 2. In scenario 2, the shopping ISF can generate the effect of trying on clothing A on user 2's digital avatar based on user 1's communication intent, user 2's digital avatar, and the clothing style A recommended by user 1 (i.e., intent service information).

[0194] To better understand the process of ISF generating intent service information, the following section breaks down the process into tasks / actions based on specific scenarios.

[0195] Scenario 1: User 1's communication intent is to send wedding photo renderings of scenic spots a, b, and c to User 2.

[0196] Task breakdown

[0197] Subtask 1 / Action 1: Search for / obtain scenic images of attractions a, b, and c, such as images related to wedding photos.

[0198] Subtask 2 / Action 2: Obtain the digital human images of User 1 and User 2.

[0199] Subtask 3 / Action 3: Generate wedding photo renderings of User 1 and User 2 in locations a, b, and c.

[0200] Subtask 4 / Action 4: Send wedding photo renderings to user 2.

[0201] In Scenario 1, the ISF can first search for / retrieve scenic images of attractions a, b, and c, such as images related to wedding photos. If message A contains the digital images of users 1 and 2, the ISF can obtain these images from message A. If message A does not contain the digital images of users 1 and 2, the ISF can retrieve them from the NIAF or UDMF. For example, the ISF can send a parameter retrieval message to the NIAF to retrieve the digital images of users 1 and 2. After receiving this message, the NIAF can query the UDMF for the digital images of users 1 and 2; the specific query method is described above and will not be repeated here. After retrieving the digital images of users 1 and 2, the NIAF sends them to the ISF. Alternatively, the ISF can also query the UDMF for the digital images of users 1 and 2, using the same method as the NIAF query, which will not be repeated here. After obtaining the digital images of User 1 and User 2, ISF can use AIGC technology to generate wedding photo renderings of the digital images of User 1 and User 2 at locations a, b, and c, i.e., intent service information. ISF can send this intent service information, "wedding photo renderings of User 1 and User 2's digital images at locations a, b, and c," to NIAF via message B. NIAF then sends this intent service information (such as wedding photo renderings) to User 2.

[0202] Scenario 2: User 1's communication intent is to send User 2 the effect of trying on style A clothing.

[0203] Task breakdown

[0204] Subtask 1 / Action 1: Search for / obtain the digital model of garment style A.

[0205] Subtask 2 / Action 2: Obtain the digital human image of User 2.

[0206] Subtask 3 / Action 3: Synthesize a digital human figure wearing clothes 'a'.

[0207] Subtask 4 / Action 4: Send the synthesized digital human image to user 2.

[0208] In Scenario 2, the ISF can first search for / obtain a digital model of clothing style 'a'. If message A contains a digital image of user 2, the ISF can obtain the digital image of user 2 from message A. If message A does not contain a digital image of user 2, the ISF can obtain the digital image of user 2 from NIAF or UDMF; the specific acquisition method is described above and will not be repeated here. The ISF can then use AIGC technology to generate / synthesize a digital image of user 2 wearing clothing 'a', i.e., intent service information. The ISF can send this intent service information, "digital image of user 2 wearing clothing 'a'", to NIAF via message B. NIAF then sends this intent service information (such as the digital image of user 2 wearing clothing 'a') to user 2.

[0209] Scenario 3: User 2's communication intention is to explain the "Schrödinger's cat" thought experiment to User 1 in a visual way.

[0210] Subtask 1 / Action 1: Obtain information related to "Schrödinger's cat", including various visual materials such as images and videos.

[0211] Subtask 2 / Action 2: Send relevant information to user 1.

[0212] Subtask 3 / Action 3: Receive questions from user 1 and answer them.

[0213] Repeatedly execute subtasks 1-3 until user 1 indicates understanding or ends / deactivates the intent accessibility feature.

[0214] In scenario 3, the ISF first obtains information related to "Schrödinger's cat" and sends this information (i.e., intent service information) to terminal A where user 1 is located. User 1 can ask questions through terminal A, and the ISF receives the question message from terminal A and answers the relevant questions from user 1. The above process is repeated until user 1 understands the "Schrödinger's cat" thought experiment or ends / deactivates the intent assistance function.

[0215] Scenario 4: User 2's communication intent is to help User 1 find destination a through augmented reality navigation.

[0216] Subtask 1 / Action 1: Get the location p of user 1.

[0217] Subtask 2 / Action 2: Obtain real-world photos of the area surrounding location p.

[0218] Subtask 3 / Action 3: Overlay navigation route instructions onto real-world photos.

[0219] Subtask 4 / Action 4: Send a real-view photo with navigation route overlaid to User 1.

[0220] Repeat subtasks 1-4 until user 1 reaches destination a, or end / deactivate intent accessibility.

[0221] In Scenario 4, if message A contains the location information of terminal A (user 1), the ISF can obtain user 1's location information from message A. If message A does not contain the location information of terminal A (user 1), the ISF can obtain user 1's location information from the NIAF or terminal A. For example, the ISF can send a parameter retrieval message to the NIAF to obtain user 1's location information. After receiving the parameter retrieval message, the NIAF can obtain user 1's location information from terminal A. The specific acquisition method is described above and will not be repeated here. After obtaining the location information of terminal A, the NIAF sends the location information of terminal A to the ISF. The location information of terminal A is user 1's location information. Of course, the ISF can also obtain user 1's location information from terminal A. The acquisition method is the same as that of the NIAF, and will not be repeated here. The ISF then obtains real-world photos of the area surrounding user 1's location information, overlays navigation route instructions on the real-world photos, and sends the real-world photos overlaid with navigation routes (i.e., intent service information) to the NIAF via message B. The NIAF sends the intent service information (such as a real-world photo overlaid with the navigation route) to user 1. This process is repeated until user 1 reaches destination a, or the intent assistance function is terminated / deactivated.

[0222] In one possible implementation, message A may further include the capabilities / types of terminal A and terminal B. In other words, NIAF can request intent service information suitable for different terminal capabilities from ISF. After ISF generates intent service information, if the display / presentation format of the intent service information is incompatible with the capabilities / type of terminal A, it can adjust the display / presentation format to adapt it to the capabilities / type of terminal A, thus obtaining intent service information a. Similarly, if the display / presentation format of the intent service information is incompatible with the capabilities / type of terminal B, it can adjust the display / presentation format to adapt it to the capabilities / type of terminal B, thus obtaining intent service information b. The content of intent service information, intent service information a, and intent service information b is the same, but their display or presentation formats may be the same or different. ISF can return intent service information a and intent service information b to NIAF in message B.

[0223] It is understood that if the above query message 1 includes the capabilities / types of terminal A and / or terminal B, then message A may not include the capabilities / types of terminal A and terminal B.

[0224] In one possible implementation, message A may also include one or more of the following: the current load of terminal A, the operating mode of terminal A, the current load of terminal B, or the operating mode of terminal B. Then, after generating intent service information, the ISF can adapt and convert the intent service information based on the terminal's current load / operating mode. For example, assuming the intent service information generated by the ISF is displayed as a 3D image, and terminal A's information display capabilities include both 2D and 3D images, if terminal A's current load is high or its operating mode is 2D, the ISF can convert the intent service information (e.g., a 3D image) into a 2D image; if terminal A's current load is low or its operating mode is 3D, the ISF can maintain the same display / presentation format of the intent service information.

[0225] S107, NIAF provides intent services to terminal A.

[0226] S108, NIAF provides intent services to terminal B.

[0227] In one possible implementation, the execution order of steps S107 and S108 is not limited. For example, step S107 can be executed before step S108, after step S108, or simultaneously / in parallel with step S108.

[0228] In one possible implementation, after obtaining the intent service information associated with the aforementioned communication intent, NIAF can provide intent services to terminal A and terminal B respectively, for example, by sending intent service information to terminal A and terminal B respectively. It is understood that NIAF may also provide intent services only to terminal A or terminal B, and this embodiment of the application does not impose any limitations.

[0229] In one possible implementation, after obtaining the intent service information, NIAF can adapt and convert the intent service information for the terminal capabilities of User 1 and User 2. For example, if the display format of the intent service information is incompatible with the capabilities of Terminal A, NIAF can convert the display format of the intent service information to a format compatible with the capabilities of Terminal A and send the converted intent service information to Terminal A. Similarly, if the display format of the intent service information is incompatible with the capabilities of Terminal B, NIAF can convert the display format of the intent service information to a format compatible with the capabilities of Terminal B and send the converted intent service information to Terminal B. For instance, if the intent service information returned by ISF is a 2D planar image / video, only compatible with the capabilities of Terminal A (e.g., a mobile phone) and not compatible with the capabilities of Terminal B (e.g., a VR headset), NIAF can convert the intent service information into panoramic 360-degree 3D multimedia information to adapt to the capabilities of Terminal B (e.g., a VR headset) for immersive viewing using a VR headset. Conversely, if the intent service information returned by the ISF is panoramic 3D multimedia information, only compatible with the capabilities of terminal B (such as a VR headset) and not with the capabilities of terminal A (such as a mobile phone), the NIAF can convert this intent service information into a 2D planar image / video to suit the capabilities of terminal A (such as a mobile phone) for viewing on a mobile phone. The NIAF can also adapt and convert the intent service information based on the terminal load or operating mode of users 1 and 2. For example, assuming the intent service information returned by the ISF to the NIAF is displayed as a 3D image, and terminal A's information display capabilities include both 2D and 3D images, if terminal A's current load is high or its operating mode is 2D, the NIAF can convert the intent service information (e.g., a 3D image) into a 2D image before sending it to terminal A; if terminal A's current load is low or its operating mode is 3D, the NIAF can send the intent service information to terminal A without changing its display / presentation format.

[0230] In one possible implementation, the NIAF can send the aforementioned intent service information to the UPF, which then forwards it to terminal A and / or terminal B via the packet. For example, the NIAF can send intent service information with a display format adapted to the capabilities of terminal A to UPF-A. Upon receiving this intent service information, UPF-A can insert it into the user plane message sent to terminal A via the packet. Similarly, the NIAF can send intent service information with a display format adapted to the capabilities of terminal B to UPF-A. Upon receiving this intent service information, UPF-A can insert it into the user plane message sent to terminal B via the packet. Alternatively, UPF-A can forward the intent service information to UPF-B, which then inserts it into the user plane message sent to terminal B via the packet. It is understood that this implementation may require extending the payload format of the user plane message to simultaneously include the original user session information and the associated intent service information. In other words, the intent service information can be located in the payload portion of the user plane message.

[0231] In another possible implementation, before steps S107 and S108, such as during the establishment of a multimedia communication session, or after the NIAF obtains the intent service information but before steps S107 and S108, the NIAF can establish a specific media channel with terminal A and / or terminal B. For ease of description, this specific media channel will be referred to as the intent service media channel below. The NIAF can transmit intent service information to terminal A and / or terminal B through this intent service media channel. For example, the NIAF and terminal A and / or terminal B can establish a channel for transmitting intent service information through two methods: pull and push.

[0232] Pull Method: Terminal A and Terminal B can send a request to a specific address of NIAF or ISF (i.e., the address used to obtain intent service information) to obtain intent service information. The following example uses the NIAF address. This address can be sent to Terminal A and Terminal B in advance by NIAF. The sending method can be as a separate message or carried within existing messages (such as SMS, RCS messages (i.e., rich communication service) or 5G messages), and this application embodiment does not impose any restrictions. The address can be in the form of a uniform resource locator (URL). The address sent by NIAF to Terminal A and Terminal B can be the same or different (for example, to adapt to different terminal capabilities, the display format of intent service information is different, and its storage location is also different). For example, the address sent by NIAF to Terminal A is http: / / niaf.example.com / intent_assistant_info / ue_a, and the address sent by NIAF to Terminal B is moq: / / niaf.example.com / intent_assistant_info / ue_b. After receiving an address (such as the NIAF address) for retrieving intent service information, terminal A can send message C to NIAF with that address as the destination address. Message C is used to retrieve intent service information. Upon receiving message C, NIAF sends the intent service information to terminal A in the response message of message C. Similarly, after receiving an address (such as the NIAF address) for retrieving intent service information, terminal B can send message D to NIAF with that address as the destination address. Message D is used to retrieve intent service information. Upon receiving message D, NIAF sends the intent service information to terminal B in the response message of message D. For example, messages C and D can be HTTP GET messages or MoQ SUBSCRIBE REQUEST messages on Quick UDP internet connections (QUIC). In this case, the channel for transmitting intent service information is a media channel consisting of request and response messages between terminals A and B and NIAF (or ISF).

[0233] Push Method: NIAF (or ISF) can send intent service information to terminal A and / or terminal B via push messaging. For example, it can send intent service information to terminal A and / or terminal B via SMS, RCS (Rich Communication Service) messages, or 5G messages. Alternatively, NIAF (or ISF) can send a new multimedia session request (such as a Session Initialization Protocol (SIP) Invitation (SIP INVITE) message) to terminal A and / or terminal B, and negotiate the establishment of a multimedia streaming session (such as a Real-Time Transport Protocol (RTP) session) through this request. After receiving the multimedia session request, terminal A and / or terminal B can send a multimedia session response to NIAF to establish a multimedia streaming session. Then, NIAF can send intent service information to terminal A and / or terminal B through the established multimedia streaming session. In this case, the channel for transmitting intent service information is the media channel formed by the messages pushed by NIAF (or ISF) to terminal A and / or terminal B, or the newly established multimedia session.

[0234] It is understandable that the intent service information sent by NIAF to terminal A can be adapted to the capabilities of terminal A. Similarly, the intent service information sent by NIAF to terminal B can be adapted to the capabilities of terminal B.

[0235] In one possible implementation, after receiving the intent service information, terminals A and B can display it. There are various display methods, such as displaying it as a separate multimedia object (e.g., a separate window, an AR-overlaid virtual object, etc.), or displaying it within the virtual environment / background of the call. Thus, users 1 and 2 can quickly understand each other's intent based on the visualized intent service information and reach a consensus on travel plans or shopping plans.

[0236] In this embodiment, the NIAF, in conjunction with the context of the user's communication session during a call, identifies the user's communication intent and invokes the corresponding ISF. The ISF dynamically generates intent service information based on AIGC technology and sends this intent service information to the user to provide intent services during the call. Because NIAF and ISF can be deployed in the core network, intent services can be implemented across the entire network and across platforms, improving communication efficiency. Furthermore, this embodiment adapts the intent service information to the terminal capabilities to achieve optimal display effects.

[0237] Referring to Figure 6, which is a second flowchart illustrating the communication method provided in this application embodiment, this method mainly describes how NIAF generates interactive intent service information and sends it to the user by invoking the AIGC capability of ISF, thereby providing more flexible intent services. As shown in Figure 6, this communication method includes, but is not limited to, the following steps:

[0238] S201, Terminal A and Terminal B communicate.

[0239] In one possible implementation, the implementation of step S201 in the embodiment of this application can be referred to the implementation of step S101 in the embodiment shown in FIG5 above, which will not be repeated here.

[0240] S202, NIAF identifies the user's communication intent based on the received communication content.

[0241] In one possible implementation, the implementation of step S202 in the embodiment of this application can refer to the implementation of step S102 in the embodiment shown in FIG5 above, which will not be repeated here.

[0242] One possible implementation differs from the embodiment shown in Figure 5 above in that the user's communication intent in this embodiment may involve the selection of both communicating parties. For example, if user 1 invites user 2 to watch a movie together, both parties need to negotiate the movie type, name, theater location, showtime, seats, etc. If it is a dinner party scenario, both parties need to negotiate the type of food, restaurant location, dining time, dishes, etc.

[0243] The following examples illustrate the user's communication intent in various scenarios. It is understood that the communication content in the following scenarios can be carried in multiple session messages. It is also understood that the communication content in the following scenarios can be a portion of the communication content exchanged between terminal A and terminal B during a multimedia call.

[0244] Scene 6: Watching a movie

[0245] User 1: "Let's go see a movie together this weekend?"

[0246] User 2: "What movies are showing recently?"

[0247] User 1: "There are several blockbuster movies, including your favorite genre. I'll have Intent Assistant send them to you."

[0248] Based on the above communication content, NIAF identified that User 1's communication intent was to send information about movies that would be showing this weekend and that would match User 2's preferences to User 2 (and User 1).

[0249] Scene 7: Dinner party

[0250] User 1: "I have a reunion dinner with my old classmates tomorrow night. Do you have any suggestions?"

[0251] User 2: "Several nice restaurants have opened in X shopping mall."

[0252] User 1: "Do you have any private rooms? I estimate there will be 8 to 10 people coming."

[0253] User 2: "No problem, I'll have the intent assistant select a few suitable ones and send them to you to take a look."

[0254] Based on the above communication content, NIAF identified that User 2's communication intent was to send information about a newly opened, highly rated restaurant in the X shopping mall with private rooms for 8 to 10 people to User 1 (and User 2).

[0255] It is understandable that NIAF can identify a user's communication intent based on the communication content in the session message, but it may not be able to determine whether the user's communication intent involves the selection of both communicating parties. NIAF can determine whether the user's communication intent involves the selection of both communicating parties, or whether the intent service information is interactive, based on the output format of the ISF subsequently queried. See the description below for details, which will not be elaborated here.

[0256] S203, NIAF sends Query Message 1 to ISRF. Query Message 1 is used to query the ISF that supports the above communication intent.

[0257] S204, the ISRF sends Query Response 1 to the NIAF. Query Response 1 includes information from the ISF that supports the aforementioned communication intent.

[0258] In one possible implementation, the implementation of steps S203 and S204 in the embodiments of this application can refer to the implementation of steps S103 and S104 in the embodiment shown in FIG5 above, which will not be repeated here.

[0259] It is understood that the differences from the embodiment shown in Figure 5 above include: for scenarios 6 and 7, NIAF queries and obtains the movie ISF and restaurant ISF respectively, and does not need to obtain the digital human images of user 1 and / or user 2. For example, for scenarios 6 and 7, the ISF call parameters include the personalized information of user 1 and / or user 2 (e.g., interests and preferences regarding movie and restaurant types). NIAF can query the personalized information of user 1 and / or user 2 from UDMF, and the query method is the same as NIAF querying the user's digital human information from UDMF, which will not be repeated here.

[0260] In one possible implementation, the query response 1 may further include the ISF output format. This output format may include, in addition to one or more of the following: the modality of the output parameters (e.g., text / voice / video), display format (e.g., 2D / 3D / VR / AR), or resolution; it may also include the type of the output intent service information (e.g., interactive or non-interactive). Upon receiving the query response 1, the NIAF can determine, based on the ISF output format, whether the communication intent involves a choice between the communicating parties, in order to facilitate subsequent processing of the intent service information. It is understood that if the ISF output format indicates that the intent service information output by the ISF is interactive, it means that the user's communication intent involves a choice between the communicating parties, and the NIAF can subsequently convert the intent service information returned by the ISF into an interactive form before sending it to the user's terminal. If the ISF output format indicates that the intent service information output by the ISF is non-interactive, it means that the user's communication intent does not involve a choice between the communicating parties.

[0261] In this embodiment of the application, the intent service information is interactive or has interactivity, which can be understood as: the user can operate on the presented intent service information through the terminal, such as: marking, selecting, sorting, ordering, or confirming.

[0262] S205, NIAF sends information describing the aforementioned communication intent to the queried ISF.

[0263] S206, the ISF sends Intent Service Information 1, which corresponds to the above communication intent, to the NIAF.

[0264] In one possible implementation, steps S205 and S206 of the embodiments of this application can be implemented with reference to steps S105 and S106 of the embodiment shown in FIG5 above, and will not be repeated here. It can be understood that the intent service information 1 in the embodiments of this application can be interactive.

[0265] In one possible implementation, the aforementioned intent service information 1 can be adapted (sorted or filtered, etc.) to the user's personalized information. For example, in scenario 6 above, NAIF can provide the movie ISF with information about the movie types that user 2 likes or dislikes, meaning that message A contains user 2's personalized information; the movie ISF can then prioritize the movie types that user 2 likes in the generated intent service information, or filter out the movie types that user 2 dislikes, to obtain intent service information 1. Similarly, in scenario 7 above, the catering ISF can also sort or filter restaurants and dishes in the generated intent service information based on user 1's preferences for dishes or catering types, to obtain intent service information 1. Alternatively, if message A does not contain the user's personalized information, then after receiving the intent service information 1 returned by the ISF, NAIF can process the intent service information 1 based on the user's personalized information (such as sorting or filtering) to obtain the processed intent service information 1.

[0266] S207, NIAF provides the first intent service to terminal A.

[0267] S208, NIAF provides the first intent service to terminal B.

[0268] In one possible implementation, the implementation of steps S207 and S208 in the embodiments of this application can refer to the implementation of steps S107 and S108 in the embodiment shown in FIG5 above, which will not be repeated here.

[0269] In one possible implementation, NIAF can provide a first intent service to terminal A and terminal B respectively, for example, by sending intent service information to terminal A and terminal B respectively. The method by which NIAF sends intent service information to terminal A and terminal B is described in the relevant description of the embodiment shown in Figure 5 above, and will not be repeated here. The intent service information sent by NIAF to terminal A and terminal B is interactive and can also be adapted (sorted or filtered, etc.) to the user's personalized information. Specifically, the intent service information sent by NIAF to terminal A and terminal B can be returned by ISF (i.e., intent service information 1), or it can be intent service information 1 returned by ISF processed by NIAF. It can also be understood that the display format of the intent service information sent by NIAF to terminal A can be adapted to the capabilities of terminal A, and the display format of the intent service information sent by NIAF to terminal B can be adapted to the capabilities of terminal B.

[0270] S209, Terminal A sends Operation Message 1 to NIAF. Operation Message 1 includes the operation event of User 1 for the first intent service.

[0271] S210, Terminal B sends Operation Message 2 to NIAF. Operation Message 2 includes the operation event of User 2 for the first intent service.

[0272] In one possible implementation, after receiving the intent service information, terminals A and B can output and display it. For example, terminals A and B can determine whether the intent service information is interactive based on the format of the intent service information returned by NIAF. For instance, if the intent service information received by terminals A and B is a video stream, it means that the intent service information is not interactive, or in other words, the user cannot operate on the intent service information. If the intent service information received by terminals A and B is a webpage, it means that the intent service information is interactive, or in other words, the user can operate on the intent service information.

[0273] In one possible implementation, User 1 can perform operations such as marking, selecting, sorting, ordering, or confirming the intent service information presented on Terminal A. Similarly, User 2 can perform operations such as marking, selecting, sorting, ordering, or confirming the intent service information presented on Terminal B. For example, in scenario 6 above, the intent service information may include a series of movie posters (including covers and synopses), and User 1 and User 2 can each select their favorite movie from these posters. For example, in scenario 7 above, the intent service information may include restaurant information (including restaurant names and menus), and User 1 and User 2 can each select their favorite restaurant and dish from the restaurant information. Terminal A responds to User 1's operation by generating operation information 1, which includes User 1's operation events related to the intent service information, such as the selected movie or the selected restaurant and dish. Terminal B responds to User 2's operation by generating operation information 2, which includes User 2's operation events related to the intent service information, such as the selected movie or the selected restaurant and dish. Terminal A can send operation information 1 to NIAF, and terminal B can send operation information 2 to NIAF.

[0274] In one possible implementation, if terminal A and NIAF establish an intent service media channel, terminal A can send operation information 1 to NIAF through this channel. Similarly, if terminal B and NIAF establish an intent service media channel, terminal B can also send operation information 2 to NIAF through this channel. If neither terminal A nor terminal B has established an intent service media channel with NIAF, terminal A can include operation information 1 in a user plane message sent to terminal B and send it to its own UPF-A; similarly, terminal B can include operation information 2 in a user plane message sent to terminal A and send it to its own UPF-B. Since the intent assistance function is activated, UPF-A, upon receiving a user plane message from terminal A, will forward it to NIAF, and UPF-B, upon receiving a user plane message from terminal B, will also forward it to NIAF. NIAF can obtain operation information 1 by parsing the user plane message from terminal A and operation information 2 by parsing the user plane message from terminal B. Understandably, this implementation might require extending the payload format of user plane messages to include both the original user session information and the operational information. In other words, the operational information could be located in the payload portion of the user plane message.

[0275] In one possible implementation, the execution order of steps S209 and S210 is not limited. For example, step S209 can be executed before step S210, after step S210, or simultaneously / in parallel with step S210.

[0276] S211, NIAF sends message E to ISF, which includes one or more of the following: Operation Information 1, Operation Information 2, or Operation Information 3. Operation Information 3 is determined based on Operation Information 1 and Operation Information 2.

[0277] S212, ISF updates the content of Intent Service Information 1 based on message E to obtain Intent Service Information 2.

[0278] S213, ISF sends Intent Service Information 2 to NIAF.

[0279] In one possible implementation, after obtaining the aforementioned operation information 1 and operation information 2, NIAF can send message E to ISF. Message E may include one or more of the following: operation information 1, operation information 2, or operation information 3. Operation information 3 may be the result of comprehensive processing of operation information 1 and operation information 2 (e.g., taking their intersection or union). In other words, NIAF can merge and summarize the choices of user 1 and user 2 (i.e., operation information 1 and operation information 2) before sending them to ISF. For example, in scenario 6 above, operation information 1 includes three movies (x, y, z) selected by user 1, and operation information 2 includes two movies (w, x) selected by user 2. NIAF can take the intersection of operation information 1 and operation information 2 to obtain operation information 3 (containing movie x); or NIAF can take the union of operation information 1 and operation information 2 to obtain operation information 3 (containing four movies: w, x, y, z). Of course, NIAF can also send user 1's choice (i.e., operation information 1) and user 2's choice (i.e., operation information 2) to ISF without merging and summarizing them.

[0280] In one possible implementation, after receiving message E, the ISF can update the content of intention service information 1 based on message E to obtain intention service information 2. The ISF can then send intention service information 2 to the NIAF. It can be understood that if message E includes operation information 1 and operation information 2, but not operation information 3, the ISF returns two pieces of intention service information 2 to the NIAF: one updated based on operation information 1, and the other updated based on operation information 2. The NIAF can coordinate and merge the two received intention service information 2 (e.g., taking the intersection or union) to obtain intention service information 3. The NIAF can then send intention service information 3 to terminals A and B. If message E includes operation information 3, the ISF returns one piece of intention service information 2 to the NIAF, and this intention service information 2 is updated based on operation information 3 (which is the information after comprehensive processing of operation information 1 and operation information 2 (e.g., taking the intersection or union)). The NIAF can then feed back this intention service information 2 to terminals A and B.

[0281] For example, ISF can filter, sort, or sort the content of intent service information 1 based on operation information to obtain intent service information 2. For instance, in scenario 6 above, operation information 1 includes three movies x, y, and z selected by user 1. ISF can filter out the three movies x, y, and z from intent service information 1 and obtain more information about the three movies x, y, and z (such as popular reviews, ratings, theaters, showtimes, seating charts, etc.) to generate intent service information 2.

[0282] In one possible implementation, the intent service information 2 / intent service information 3 fed back by NIAF to terminal A and terminal B can also be interactive. Therefore, in this embodiment, steps S209 to S213 can be repeated until an intent service result is obtained or the intent service function is deactivated. It is understood that user operations on intent service information (such as booking tickets or ordering food) may require user authorization. After receiving the user's operation information, NIAF can obtain the digital identity authorization (such as a token) of user 1 and / or user 2 from relevant network elements such as UDMF. The method of obtaining this authorization is the same as the method by which NIAF queries digital human information from UDMF, and will not be elaborated here. In step S212, NIAF can also provide the digital identity authorization (such as a token) of user 1 and / or user 2 to ISF, such as carrying the digital identity authorization of user 1 and / or user 2 in message E, to complete the corresponding intent service operation (such as booking tickets, ordering food, or making a reservation), and obtain updated intent service information, which includes intent service results (such as booking results, ordering results, or reservation results). For ease of description, it is assumed that intent service information 2 contains intent service results.

[0283] S214, NIAF provides a second intent service to terminal A and / or terminal B.

[0284] In one possible implementation, the NIAF provides a second intent service to terminal A and / or terminal B. This can be achieved by the NIAF triggering terminal A and / or terminal B to execute the task corresponding to the intent service information 2. For example, after obtaining intent service information 2, the NIAF determines that it contains an intent service result (such as a ticket booking result, a food ordering result, or a reservation result). If the intent service result is successful (such as a successful ticket booking, successful food ordering, or successful reservation), the NIAF can trigger multiple terminals belonging to user 1 and user 2 in the network (which may be other terminals not participating in the multimedia call) to execute tasks related to the intent service result. For example, the NIAF can query the UDMF for terminal information belonging to user 1 and user 2 (such as the terminal's address, identifier, or type / capability). For instance, the NIAF can send a query message 4 to the UDMF, which may include the identification information of user 1 and user 2 (such as IMSI or identity identifier). This query message 4 can be used to query the user's terminal information. After receiving query message 4, UDMF can locally query the terminal information bound to the identification information of User 1 and User 2 (there may be multiple terminals bound to one user), and can return query response 4 to NIAF, which may include the terminal information of User 1 and User 2. Then, NIAF can send instructions to the multiple terminals found to drive each terminal to perform tasks related to the result of the intent service. For example, NIAF can send a schedule reminder instruction (such as the start time of a successfully booked movie ticket, or the arrival time of a successfully booked restaurant) to User 1 and / or User 2's smartwatches to set schedule reminders on their smartwatches. As another example, NIAF can send a route planning instruction (including the starting location and destination, where the destination could be the location of a successfully booked movie theater, or the location of a successfully booked restaurant, etc.) to User 1 and / or User 2's smart cars to set corresponding route planning, etc. For example, NIAF can send instructions to the terminal through control plane signaling, or it can be carried in user plane messages in the user plane. This application embodiment does not impose any restrictions.

[0285] In this embodiment, the NIAF, in conjunction with the context of the user's communication session, identifies the user's communication intent and invokes the corresponding ISF. The ISF dynamically generates interactive intent service information based on AIGC technology and sends this interactive intent service information to the user, allowing the user to operate on the intent service information. The NIAF can obtain the user's digital identity authorization based on the user's operation, enabling the user to obtain intent service results (such as booking tickets, ordering food, etc.). The NIAF can then trigger multi-terminal execution tasks related to the user based on the intent service results. Because the NIAF and ISF can be deployed in the core network, this embodiment can provide users with full-network, cross-platform intent services during their calls, improving communication efficiency.

[0286] Referring to Figure 7, which is a third flowchart illustrating the communication method provided in this application embodiment, this method mainly describes activating intent assistance functions through application layer messages during a call. In one possible implementation, this application embodiment can be combined with the embodiments shown in Figure 5 or Figure 6 above, or it can be implemented independently; this application is not limited to this.

[0287] As shown in Figure 7, this communication method includes, but is not limited to, the following steps:

[0288] S301, Terminal A sends a function activation message to NIAF, which instructs NIAF to insert a session.

[0289] In one possible implementation, prior to step S301, terminal A and terminal B have already established an end-to-end multimedia communication session. User 1 can activate or deactivate the intent assistive function through terminal A, specifically by means including but not limited to voice commands, gesture commands, or clicking specific function buttons on terminal A. In response to user 1's activation of the intent assistive function, terminal A generates a function activation message and can send this message to the NIAF. This function activation message can be used to activate the intent assistive function, or in other words, it instructs the NIAF to insert into the session. In this embodiment, "activating the intent assistive function" can be understood as "inserting the NIAF into the session," and the two are equivalent. Alternatively, in response to user 1's deactivation of the intent assistive function, terminal A generates a function deactivation message and can send this message to the NIAF. This function deactivation message can be used to deactivate the intent assistive function, or in other words, it instructs the NIAF to exit the session. In this embodiment, "deactivating the intent assistive function" can be understood as "exiting the NIAF from the session," and the two are equivalent. It is understandable that deactivating intent assistive functions can occur even when intent assistive functions are already activated. It is also understandable that terminal A sending function activation and function deactivation messages to the NIAF can be forwarded through the user plane function (UPF-A) to which terminal A belongs. For example, the function activation or deactivation message sent by terminal A first reaches the base station connected to terminal A, the base station then forwards it to the UPF-A to which terminal A belongs, and the UPF-A forwards it to the NIAF.

[0290] In one possible implementation, the aforementioned function activation or deactivation message may include session information. This session information can be used to indicate a communication session established between terminal A and terminal B. For example, the session information may include one or more of the following: one or more session characteristic parameters (e.g., an Internet Protocol (IP) 5-tuple: source IP address, destination IP address, source port, destination port, and protocol type), or one or more session identifiers. The one or more sessions may include the aforementioned multimedia communication session established between terminal A and terminal B.

[0291] In one possible implementation, the aforementioned function activation or deactivation message may further include one or more of the following: indication information 1, or indication information 2. Indication information 1 can be used to indicate the activation / deactivation of the intent-assisted function, or in other words, indication information 1 can be used to indicate the NIAF to insert or exit a session. Indication information 2 can be used to indicate the session direction of activating / deactivating the intent-assisted function, or in other words, indication information 2 can be used to indicate the transmission direction of the communication content for intent recognition by the NIAF, such as uplink, downlink, or bidirectional. For example, uplink can refer to the direction of terminal A sending a message to terminal B, downlink can refer to the direction of terminal B sending a message to terminal A, and bidirectional can refer to the direction of terminal A sending a message to terminal B, and the direction of terminal B sending a message to terminal A. It is understood that if the function activation / deactivation message does not contain indication information 1, the function of the message can be indicated by the message name of the function activation / deactivation message.

[0292] In one possible implementation, the aforementioned activation / deactivation message can be an application-layer message, such as an HTTP message or a Media over QUIC (MoQ) message over a User Datagram Protocol (UDP) network connection. For example, an HTTP message extension could define specific HTTP URL parameters indicating that the message is used to activate / deactivate the intent assistive function. For instance, an `activate_intent` parameter could be added to the target URL of an HTTP GET message. When `activate_intent` is set to `true`, it indicates activation of the intent assistive function or NIAF insertion into the session; when `activate_intent` is set to `false`, it indicates deactivation / deactivation of the intent assistive function or NIAF exit from the session. Simultaneously, a `sessionId` parameter could be added to the target URL of the HTTP GET message, assigned the value of the session characteristic parameter (such as an IP 5-tuple) for which the intent assistive function (or NIAF insertion or exit) needs to be activated / deactivated; alternatively, the value could be a session identifier (such as a session name, session ID, etc.). You can also add a `dir` (direction) parameter to the target URL of the HTTPGET message to indicate the session direction for activating / deactivating the intent accessibility feature (or NIAF insertion or exit) (e.g., up for uplink, downlink, and bi-directional, denoted by "bi"). An example, a possible message format (excerpt), is as follows:

[0293] GET http: / / niaf.example.com? activate_intent=true&sessionId=<5-tuple>&dir=bi.

[0294] Alternatively, specific well-known URLs can be used to simplify parameters in HTTP GET messages. For example, the `activate_intent` parameter can be replaced by an address prefixed with `intent_service`, or the `intent_service` prefix in the HTTP GET message can be used to indicate that the message is for activating intent-based accessibility features or instructing NIAF to insert a session. An example, excerpt of a possible message format, is as follows:

[0295] GET http: / / intent_service.example.com? sessionId=<5-tuple>&dir=bi.

[0296] For example, MoQ message extensions include adding parameters to the SUBSCRIBE REQUEST message to indicate whether intent assistance is activated or deactivated. For instance, a new session name "intent_assistant" is added to the SUBSCRIBE REQUEST message to quickly identify the purpose of the session identified by this name; this session can be used to subsequently transmit intent assistance information. Simultaneously, the SUBSCRIBE REQUEST message adds the parameter keys activate_intent and associatedTrackIds. When activate_intent is set to true, intent assistance is activated; when it is set to false, intent assistance is deactivated or disabled. associatedTrackIds represents the user session identifier for activating / deactivating intent assistance, and its values ​​include the uplink session identifier (in this embodiment, a session message from terminal A to terminal B) and / or the downlink session identifier (in this embodiment, a session message from terminal B to terminal A). Of course, associatedTrackIds can also be used to represent session characteristic parameters (such as the IP 5-tuple). For example, a possible message format is as follows:

[0297] S302, NIAF sends a request message to ISMF. This request message requests the establishment of a connection between NIAF and UPF-A, which serves the aforementioned session. The request message includes the address of NIAF.

[0298] S303, ISMF sends a configuration policy to UPF-A. This configuration policy includes session connection information used to establish a connection between UPF-A and NIAF. This connection can be used to transmit session messages.

[0299] In one possible implementation, after receiving the aforementioned function activation message, the NIAF can send a request message to the ISMF. This request message can be used to request the establishment of a connection between the NIAF and the UPF-A serving the session indicated by the aforementioned session information. For example, the request message may include the aforementioned session information. For example, the request message may also include the aforementioned indication information 2.

[0300] After receiving the request message, the ISMF can complete the necessary authorization verification process. For example, the ISMF can query the UDMF to see if user 1, corresponding to terminal A, has subscribed to Intent Assistance. If user 1 has subscribed to Intent Assistance, the ISMF can send a configuration policy to the UPF-A to which terminal A belongs. If user 1 has not subscribed to Intent Assistance, the ISMF can reject the request message. The configuration policy may include session connection information, which can be used to establish a session channel between the UPF-A and the NIAF. This session channel can be used to transmit session messages. For example, the session connection information may include one or more of the following: the NIAF's address, the NIAF's port, or the protocol used by the session channel (e.g., Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or QUIC, etc.). For example, the configuration policy may also include one or more of the following: the aforementioned session information, or the aforementioned indication information 2. It is understandable that if the session direction indicated by instruction information 2 is uplink, then after UPF-A establishes a session channel with NIAF, UPF can forward only session messages sent from terminal A to terminal B to NIAF (i.e., uplink session). If the session direction indicated by instruction information 2 is downlink, then after UPF-A establishes a session channel with NIAF, UPF can forward only session messages sent from terminal B to terminal A to NIAF (i.e., downlink session). If the session direction indicated by instruction information 2 is bidirectional, then after UPF-A establishes a session channel with NIAF, UPF can forward both session messages sent from terminal A to terminal B (i.e., uplink session) and session messages sent from terminal B to terminal A (i.e., downlink session) to NIAF.

[0301] In another possible implementation, after receiving the aforementioned function deactivation message, NIAF can send a session termination message to UPF-A. This session termination message can be used to disconnect the session channel between NIAF and UPF-A. This session channel can be used to transmit session messages. "Disconnecting the session channel between NIAF and UPF-A" can be understood as: NIAF no longer receives session messages forwarded by UPF-A, or UPF-A no longer forwards session messages to NIAF. Upon receiving the session termination message, UPF-A can disconnect from NIAF. For example, the session termination message may include session information associated with the intent-assisted function, or in other words, the session termination message carries the session information included in the function deactivation message. Accordingly, the session termination message can be used to disconnect one or more session channels between NIAF and UPF-A, and these session channels correspond to the session information in the session termination message. In other words, NIAF can disconnect some session channels from UPF-A using the session termination message, while other session channels remain open. In other words, NIAF may stop receiving some session messages forwarded by UPF-A (these session messages belong to the session identified by this session information), but may receive session messages from other sessions forwarded by UPF-A; or UPF-A may stop forwarding session messages belonging to the session identified by this session information to NIAF.

[0302] S304, UPF-A sends a session connection request to NIAF. This session connection request is used to request the establishment of a session channel. This session channel can be used to transmit session messages.

[0303] S305, NIAF sends a session connection response to UPF-A. This session connection response is used to respond to the aforementioned session connection request.

[0304] In one possible implementation, after receiving the aforementioned configuration policy, UPF-A can send a session connection request to NIAF. This request can be used to establish a session channel between UPF-A and NIAF. Upon receiving the session connection request, NIAF can send a session connection response to UPF-A, which can be used to agree to the session connection request. The established session channel between UPF-A and NIAF can then be used to forward user session messages to NIAF.

[0305] It is understood that the embodiments of this application are described using the example of terminal A sending a message to activate / deactivate the intent accessibility function. In actual applications, terminal B may also send the message to activate / deactivate the intent accessibility function, and the implementation method is similar to that of the embodiments of this application, which will not be described in detail here.

[0306] In one possible implementation, after step S305, UPF-A can send one or more session messages to NIAF, which may belong to a single session. NIAF can identify the user's communication intent based on the communication content in these one or more session messages. For example, if the above configuration policy includes the aforementioned session information, the one or more session messages sent by UPF-A to NIAF may belong to a session determined by that session information. For example, the session messages sent by UPF-A to NIAF may be real-time interactions between terminal A and terminal B. Of course, UPF-A can also send historical session messages or communication content to NIAF so that NIAF can better understand the context of the user session and identify the user's communication intent. It is understood that, depending on the application scenario and / or the configuration policy issued by ISMF (such as including session direction), UPF-A may only forward session messages or communication content sent by terminal A to terminal B (i.e., uplink session), or only forward session messages or communication content sent by terminal B to terminal A (i.e., downlink session), or forward both.

[0307] In one possible implementation, since the user's session messages may also be processed and forwarded by the application function (AF) between UPF-A and UPF-B, UPF-A in this embodiment can also be replaced by AF, which will not be elaborated here.

[0308] In this embodiment of the application, the NIAF is instructed to insert a session by extending the application layer message. After receiving the application layer message instructing the NIAF to insert a session, the NIAF requests to join the session from the ISMF. The ISMF sends session connection information to the UPF. The UPF establishes a session channel with the NIAF based on the session connection information, so that the NIAF can obtain the user's communication content from the UPF, support the NIAF's intent recognition, and lay the foundation for expressive communication.

[0309] Referring to Figure 8, which is a schematic flowchart of the fourth communication method provided in this application embodiment, this method mainly describes activating intent assistance functions through control plane messages before or during a call. In one possible implementation, this application embodiment can be implemented in conjunction with the embodiments shown in Figure 5 or Figure 6 above, or it can be implemented alone; this application is not limited to this.

[0310] As shown in Figure 8, this communication method includes, but is not limited to, the following steps:

[0311] S401, Terminal A sends a session modification request or session establishment request to the ISMF. The session modification request or session establishment request includes indication information 1, which is used to indicate the activation of the intent assistance function.

[0312] In one possible implementation, user 1 can activate or deactivate the intent-assisted function via terminal A. Specific methods include, but are not limited to, using voice commands, gesture commands, or clicking specific function buttons on terminal A. In response to user 1's activation of the intent-assisted function, terminal A can generate indication information 1. It is understood that if terminal A and terminal B have already established an end-to-end multimedia communication session before step S401, terminal A can send a session modification request to the ISMF. This session modification request includes indication information 1, which can be used to indicate the activation or deactivation of the intent-assisted function. If terminal A and terminal B have not yet established an end-to-end multimedia communication session before step S401, terminal A can send a session establishment request to the ISMF. This session establishment request includes indication information 1, which can be used to indicate the activation of the intent-assisted function. This session establishment request can be used to establish a multimedia communication session from terminal A to terminal B via NIAF.

[0313] In one possible implementation, the session modification request may further include indication information 2, which can be used to indicate the session direction for activating or deactivating the intent assistive function. The session establishment request may also include indication information 2, which can be used to indicate the session direction for activating the intent assistive function.

[0314] In one possible implementation, taking a 5G system as an example, the aforementioned session modification request can be a Protocol Data Unit (PDU) Session Modification Request, and the aforementioned session establishment request can be a PDU Session Establishment Request. Both the PDU Session Modification Request and the PDU Session Establishment Request can be carried by non-access stratum (NAS) signaling. Therefore, parameters indicating the activation of intent-assisted functions can be extended in the NAS signaling. For example, a new information element (IE) "Activate_Intent" can be extended into the PDU Session Modification Request or the PDU Session Establishment Request. When Activate_Intent is set to true, it indicates that the intent-assisted function is activated; when Activate_Intent is set to false, it indicates that the intent-assisted function is deactivated or disabled. It can be understood that Activate_Intent is set to true in the PDU Session Establishment Request. You can also extend the new information element "Intent_Direction" in the PDU session modification request or PDU session establishment request, and assign it a value of uplink, downlink, or bidirectional to indicate the session direction for activating / deactivating the intent accessibility function.

[0315] S402, ISMF sends Session Connection Information 1 to UPF-A. This Session Connection Information 1 is used to establish a session channel between UPF-A and NIAF. This session channel can be used to transmit session messages.

[0316] In one possible implementation, after receiving the aforementioned session modification request or session establishment request, if the indication information 1 indicates activation of the intent assistance function, the ISMF can send session connection information 1 to the UPF-A to which terminal A belongs after completing the necessary authorization verification process. If the ISMF receives a session modification request, the session connection information 1 can be used to modify the current session to establish a session channel between UPF-A and NIAF. If the ISMF receives a session establishment request, the session connection information 1 can be used to establish a session channel between UPF-A and NIAF. The session connection information 1 may include one or more of the following: the address of NIAF, the port of NIAF, or the protocol used by the session channel.

[0317] In one possible implementation, the ISMF can also send session connection information 2 to the NIAF. This session connection information 2 may include one or more of the following: the address of the UPF-A, the port of the UPF-A, or the protocol used by the session channel. Through session connection information 2, the ISMF can inform the NIAF in advance that the UPF-A is network-authorized and enable the NIAF to prepare the relevant session resources in advance.

[0318] In one possible implementation, if the indication information 1 in the aforementioned session modification request indicates deactivation of the intent assistance function, the ISMF can send a deactivation message to the UPF-A. This deactivation message can be used to indicate disconnection of the session channel between the UPF-A and the NIAF. This session channel can be used to transmit session messages. For example, the deactivation message may include the session identifier from the session modification request; then, upon receiving the deactivation message, the UPF-A may no longer forward the session messages corresponding to that session identifier to the NIAF. Alternatively, upon receiving the deactivation message, the UPF can send a session termination message to the NIAF. This session termination message can be used to disconnect the session channel between the UPF-A and the NIAF. For example, upon receiving the session termination message, the NIAF may disconnect from the UPF-A. For example, upon receiving the session termination message, the NIAF may not disconnect from the UPF-A, but instead will no longer perform intent recognition on the session messages corresponding to that session identifier.

[0319] S403, UPF-A sends a session connection request to NIAF. This session connection request is used to request the establishment of a session channel. This session channel can be used to transmit session messages.

[0320] S404, NIAF sends a session connection response to UPF-A, which is used to respond to the aforementioned session connection request.

[0321] In one possible implementation, the implementation of steps S403 and S404 in this embodiment can be referred to the implementation of steps S304 and S305 in the embodiment shown in FIG7 above, and will not be repeated here. It can be understood that this embodiment uses the example of terminal A sending a session modification request / session establishment request to activate / deactivate the intent assistive function. In practical applications, terminal B can also send a session modification request / session establishment request to activate / deactivate the intent assistive function, and its implementation is similar to that in this embodiment, and will not be repeated here.

[0322] In one possible implementation, after step S404, the NIAF can send a session modification response or a session establishment response to terminal A. The session modification response can be used to indicate successful session modification. The session establishment response can be used to indicate successful session establishment. For example, the session modification response can be a PDU session modification response, and the session establishment response can be a PDU session establishment response. It is understood that the purpose of "activating intent assistive functions" in this embodiment can be to insert the NIAF into an existing session or to establish a session via the NIAF.

[0323] This application uses control plane messages to activate / deactivate intent-assisted functions and manage sessions, simplifying the information carried in the messages. For example, it eliminates the need to carry session information (such as session characteristic parameters or session identifiers) in the messages, thereby reducing overhead.

[0324] Referring to Figure 9, which is a fifth flowchart illustrating the communication method provided in this application embodiment, this method mainly describes adding NIAF to the session via the network side before or during a call. In one possible implementation, this application embodiment can be combined with the embodiments shown in Figures 5 or 6 above, or it can be implemented independently; this application is not limited to this.

[0325] As shown in Figure 9, this communication method includes, but is not limited to, the following steps:

[0326] S501, configure a first policy for activating intent assistive functions for UPF-A, and / or configure a second policy for deactivating intent assistive functions for UPF-A.

[0327] In one possible implementation, when the ISMF finds that User 1's subscription data includes intent assistance features from the UDMF, the ISMF can send a first policy to the UPF-A to activate the intent assistance features. When the ISMF finds that User 1's subscription data does not include intent assistance features from the UDMF, the ISMF can send a second policy to the UPF-A to deactivate the intent assistance features, or it can choose not to send the first policy.

[0328] In another possible implementation, a first strategy for activating intent assistive functions can be pre-configured / pre-defined in UPF-A, and / or a second strategy for deactivating intent assistive functions can be pre-configured / pre-defined.

[0329] For example, the first strategy described above could be to activate the intent assistance function when a user's session message is detected to meet certain conditions (e.g., user type, user identifier, session type, etc.). The second strategy described above could be to deactivate the intent assistance function when a user's session message is detected to meet certain conditions (e.g., user type, user identifier, session type, etc.). For example, when the session message received by the UPF-A belongs to a calling service, a called service, or a two-way service, the intent assistance function is activated / deactivated. Another example is when the session message received by the UPF-A comes from a voice call, a video call, or a digital human call, the intent assistance function is activated / deactivated. Yet another example is when the session message received by the UPF-A is a real-time call, a non-real-time message, or an offline response, the intent assistance function is activated / deactivated. Yet another example is when the session message received by the UPF-A comes from a specific user identifier, a specific terminal type, is located at a specific time, or is located in a specific location area, the intent assistance function is activated / deactivated.

[0330] S502, UPF-A determines to activate the intent assist function based on the received session message and the first strategy described above. Alternatively, it determines to deactivate the intent assist function based on the received session message and the second strategy described above.

[0331] S503, UPF-A sends a function activation message to ISMF, which instructs NIAF to insert the session corresponding to the session message.

[0332] In one possible implementation, UPF-A receives a session message from terminal A. If the session message satisfies the first strategy described above, UPF-A determines to activate the intent assistance function. UPF-A can send a function activation message to ISMF, which can be used to instruct NIAF to insert into the session corresponding to the session message or to activate the intent assistance function. The function activation message can include one or more of the following: indication information 1 or indication information 2. Indication information 1 can be used to instruct NIAF to insert into the session corresponding to the session message or to activate the intent assistance function. Indication information 2 can be used to indicate the session direction for activating the intent assistance function, or in other words, to indicate the transmission direction of the communication content for intent identification by NIAF, such as uplink, downlink, or bidirectional.

[0333] For example, taking a 5G system as an example, the aforementioned function activation message can be a Packet Forwarding Control Protocol (PFCP) Node Report Request message. For instance, the PFCP Node Report Request message can be extended by adding a new information element "Activate_Intent". When activate_intent is set to true, it indicates activation of the intent assist function or NIAF session insertion; correspondingly, when activate_intent is set to false, it indicates deactivation or disabling of the intent assist function. A new information element "Intent_Direction" can also be added to the PFCP Node Report Request message, set to uplink, downlink, or bidirectional, indicating the session direction for activating the intent assist function.

[0334] In another possible implementation, if the session message satisfies the second strategy described above, then UPF-A determines to deactivate the intent assistance function. UPF-A can send a session end message to NIAF, which can be used to disconnect the session channel between NIAF and UPF-A. This session channel can be used by UPF-A to forward the user's session messages to NIAF. For example, the session end message may include one or more of the following: indication information 1, or indication information 2. Indication information 1 can be used to indicate the deactivation of the intent assistance function, and indication information 2 can be used to indicate the session direction for deactivating the intent assistance function. After receiving the session end message, NIAF can disconnect from UPF-A. For example, if the session end message includes indication information 2, then after receiving the session end message, NIAF may not disconnect from UPF-A, but instead will no longer perform intent identification on session messages belonging to this session direction in the current session.

[0335] S504, ISMF sends Session Connection Information 1 to UPF-A. This Session Connection Information 1 is used to establish a session channel between UPF-A and NIAF. This session channel can be used to transmit session messages or communication content.

[0336] In one possible implementation, after receiving the aforementioned function activation message, the ISMF can perform necessary permission or policy checks (e.g., checking whether User 1 has subscribed to Intent Assistance). If the permission or policy check passes (e.g., User 1 has subscribed to Intent Assistance), the ISMF can send Session Connection Information 1 to the UPF-A. This Session Connection Information 1 includes one or more of the following: the NIAF's address, the NIAF's port, or the protocol used by the session channel. This Session Connection Information 1 can be used to establish a session channel between the UPF-A and the NIAF. This session channel can be used to transmit user session messages or communication content to the NIAF.

[0337] In one possible implementation, after the permission or policy check is passed (e.g., user 1 has subscribed to Intent Accessibility), ISMF can also send session connection information 2 to NIAF. This session connection information 2 may include one or more of the following: the address of UPF-A, the port of UPF-A, or the protocol used by the session channel. Through session connection information 2, ISMF can inform NIAF in advance that this UPF-A is network-authorized and allow NIAF to prepare the relevant session resources in advance.

[0338] In one possible implementation, after the permission or policy check is passed (e.g., user 1 has subscribed to the intent assistive function), the ISMF can first send a session modification request or a session establishment request to terminal A. This session modification request or session establishment request can be used to request activation of the intent assistive function to obtain user 1's authorization confirmation (i.e., agreement to enable / activate the intent assistive function). It is understood that the session modification request includes the identification information of the session to be modified. For example, the session modification request can be a PDU session modification request, and the session establishment request can be a PDU session establishment request. For a description of the PDU session modification request and PDU session establishment request, please refer to the relevant description of step S401 in the embodiment shown in Figure 8 above, which will not be repeated here. After receiving the session modification request or session establishment request, user 1 can operate terminal A to agree to enable / activate the intent assistive function. Terminal A can send user 1's confirmation result to the ISMF through a session modification response or a session establishment response. The session modification response or session establishment response can include user 1's confirmation result, such as user 1 agreeing to activate the intent assistive function. After receiving a session modification response or session establishment response from terminal A, ISMF can send session connection information 1 to UPF-A. For details regarding session connection information 1, please refer to the description of step S402 in the embodiment shown in Figure 8 above; it will not be repeated here.

[0339] S505, UPF-A sends a session connection request to NIAF. This session connection request is used to request the establishment of a session channel. This session channel can be used to transmit session messages or communication content.

[0340] S506, NIAF sends a session connection response to UPF-A. This session connection response is used to respond to the session connection request mentioned above.

[0341] In one possible implementation, the implementation of steps S505 and S506 in this embodiment can be found in the implementation of steps S304 and S305 in the embodiment shown in FIG7 above, and will not be repeated here. It is understood that this embodiment uses UPF-A to activate / deactivate the intent assistive function as an example. In practical applications, UPF-B can also be used to activate / deactivate the intent assistive function message, and its implementation is similar to that of this embodiment (simply replace UPF-A with UPF-B), and will not be repeated here.

[0342] In this embodiment, the network side determines whether to activate the intent assist function based on the received session message and the configured relevant policy. If the intent assist function is activated, the NIAF is inserted into the session through the control plane message, which can simplify the information carried in the message. For example, it is not necessary to carry session information (such as session characteristic parameters or session identifier) ​​in the message, thereby reducing overhead.

[0343] Referring to Figure 10, which is a sixth flowchart illustrating the communication method provided in this application embodiment, this method mainly describes activating intent assistance functions through user plane messages during a call. In one possible implementation, this application embodiment can be combined with the embodiments shown in Figures 5 or 6 above, or it can be implemented independently; this application is not limited to this.

[0344] Referring to Figure 10, the communication method includes, but is not limited to, the following steps:

[0345] S601, Terminal A sends a user plane message to UPF-A, which is used to activate the intent assistance function.

[0346] In one possible implementation, before step S601, such as during the establishment of a multimedia communication session between terminal A and terminal B, taking the use of a Session Description Protocol (SDP) to establish the multimedia communication session as an example, terminal A sends an Invite message (such as an SDP offer) to its home UPF-A to initiate a request to establish a session. This Invite message (such as an SDP offer) can be used to establish a multimedia channel between UPF-A and terminal A. This multimedia channel can be used not only to transmit user session messages but also to transmit subsequent intent service information. Similarly, terminal B can also send an Invite message (such as an SDP offer) to its home UPF-B to initiate a request to establish a session. This Invite message (such as an SDP offer) can be used to establish a multimedia channel between UPF-B and terminal B. This multimedia channel can be used not only to transmit user session messages but also to transmit subsequent intent service information. In other words, the multimedia channel pre-negotiated between terminal A / terminal B and UPF-A / UPF-B in this INVITE message supports the transmission intent service information.

[0347] For example, a new media attribute line (line 'a') can be extended in the INVITE message using the Session Description Protocol (SDP) to support Real-Time Transport Protocol (RTP) header extensions (extmap). This allows subsequent user plane messages to include the corresponding RTP header extension fields to indicate whether the intent accessibility feature is activated or deactivated. For example: a = extmap:99urn:xxx:params:rtp-hdrext:intent-active. This media attribute line (line 'a') can be used to indicate that the established multimedia channel supports the transmission intent service information.

[0348] After receiving an INVITE message (such as an SDP offer), UPF-A / UPF-B can know that the multimedia channel that terminal A / terminal B wants to establish supports the transmission of intent service information (or, supports terminal A / terminal B sending user plane messages carrying RTP header extension fields), and can send a response message (such as an SDP answer) to terminal A. This response message (such as an SDP answer) can be used to respond to the aforementioned INVITE message (such as an SDP offer). If the response message (such as an SDP answer) indicates success, it means that the multimedia channel between UPF-A and terminal A has been successfully established, or the multimedia channel between UPF-B and terminal B has been successfully established. It can be understood that when this application embodiment is implemented in conjunction with the embodiments shown in Figures 5 or 6 above, the process of NIAF sending intent service information to terminal A and terminal B may include: NIAF can first send the intent service information to UPF-A and UPF-B, then UPF-A sends it to terminal A through the multimedia channel established here, and UPF-B sends it to terminal B through the multimedia channel established here.

[0349] In one possible implementation, after the multimedia channel is successfully established, user 1 can activate or deactivate the intent-assisted function via terminal A. In response to user 1's activation or deactivation of the intent-assisted function, terminal A generates a user plane message and can send this user plane message to UPF-A. This user plane message can be used to activate or deactivate the intent-assisted function. For example, the user plane message may include parameter information for activating or deactivating the intent-assisted function. For instance, this parameter information may be a Real-Time Transport Protocol (RTP) header extension.

[0350] For example, referring to Figure 11, which is a schematic diagram of the structure of the RTP message header extension provided in an embodiment of this application. As shown in Figure 11, new identifiers (IDs) and data can be added to the RTP message header extension. The ID represents intent-active, and the data has a value of true to indicate that the intent assistance function is activated, and a value of false to indicate that the intent assistance function is deactivated / disactivated.

[0351] In one possible implementation, after receiving the aforementioned user plane message, UPF-A can parse the user plane message and determine whether it contains parameter information (such as RTP header extension) for activating / deactivating intent-assisted functions. If the user plane message contains parameter information for activating intent-assisted functions (such as the data value corresponding to the intent-active ID in the RTP header extension being true), then steps S602 to S605 below are executed.

[0352] If the user plane message contains parameters for deactivating intent-active features (such as the data value being false for the intent-active ID in the RTP header extension), the UPF can send a session termination message to the NIAF. This session termination message can be used to disconnect the session channel between the NIAF and the UPF-A. This session channel can then be used by the UPF-A to forward the user's session messages to the NIAF. Upon receiving the session termination message, the NIAF can disconnect from the UPF-A.

[0353] S602, UPF-A sends a function activation message to ISMF, which instructs NIAF to insert the session corresponding to the user plane message.

[0354] In one possible implementation, the implementation of step S602 in the embodiment of this application can refer to the implementation of step S503 in the embodiment shown in FIG9 above, which will not be repeated here.

[0355] S603, ISMF sends session connection information to UPF-A. This session connection information is used to establish a session channel between UPF-A and NIAF. This session channel can be used to transmit session messages and / or communication content.

[0356] In one possible implementation, after receiving the aforementioned function activation message, the ISMF can perform necessary permission or policy checks (e.g., checking whether User 1 has subscribed to Intent Assistance). If the permission or policy check passes (e.g., User 1 has subscribed to Intent Assistance), the ISMF can send session connection information to the UPF-A. This session connection information includes one or more of the following: the NIAF's address, the NIAF's port, or the protocol used by the session channel. This session connection information can be used to establish a session channel between the UPF-A and the NIAF. This session channel can be used to forward the user's session messages to the NIAF.

[0357] S604, UPF-A sends a session connection request to NIAF. This session connection request is used to request the establishment of a session channel. This session channel can be used to transmit session messages and / or communication content.

[0358] S605, NIAF sends a session connection response to UPF-A. This session connection response is used to respond to the session connection request mentioned above.

[0359] In one possible implementation, the implementation of steps S604 and S605 in this embodiment can be referred to the implementation of steps S304 and S305 in the embodiment shown in FIG7 above, and will not be repeated here. This embodiment uses the example of terminal A sending a user plane message to activate / deactivate intent assistive function. In practical applications, terminal B can also send a user plane message to activate / deactivate intent assistive function, and its implementation is similar to that in this embodiment, and will not be repeated here. It can be understood that the purpose of "activating intent assistive function" in this embodiment may be to insert NIAF into an existing session.

[0360] This application extends user plane messages to activate / deactivate intent assistance functions, which can simplify the complexity of session management and support NIAF intent recognition, laying the foundation for expressive communication.

[0361] Referring to Figure 12, which is a seventh flowchart illustrating the communication method provided in this application embodiment, this method mainly describes the session management process based on an IP media system (IMS). The IMS may include a call session control function (CSCF), a media function (MF), and a NIAF, and optionally, an ISF. For example, the NIAF and / or ISF respectively serve as an application server (AS) within the IMS. In this method, CSCF-A represents the CSCF to which terminal A belongs, and CSCF-B represents the CSCF to which terminal B belongs. In one possible implementation, this application embodiment can be combined with the embodiments shown in Figures 5 or 6 above, or it can be implemented independently; this application is not limited to this.

[0362] As shown in Figure 12, this communication method includes, but is not limited to, the following steps:

[0363] S701, Terminal A sends a session invitation message or a session re-invitation message to CSCF-A. The session invitation message or the session re-invitation message includes a first parameter, which is used to indicate whether to activate or deactivate the intent accessibility function.

[0364] In one possible implementation, user 1 can activate or deactivate the intent-assisted function through terminal A. Terminal A, in response to user 1's activation / deactivation of the intent-assisted function, can generate a first parameter. It is understood that if terminal A and terminal B have already established an end-to-end multimedia communication session before step S701, terminal A can send a session re-invitation message (such as SIP re-INVITE, used to modify an existing user session) to its own CSCF (denoted as CSCF-A). This session re-invitation message (such as SIP re-INVITE) may include the first parameter. This first parameter can be used to indicate the activation or deactivation of the intent-assisted function. If terminal A and terminal B have not yet established an end-to-end multimedia communication session before step S701, terminal A can send a session invitation message (such as SIP INVITE, used to initiate a new session) to CSCF-A. This session invitation message (such as SIP INVITE) includes the first parameter. This first parameter can be used to indicate the activation of the intent-assisted function. It can also be understood that terminal A and terminal B can establish a multimedia communication session via IMS, and the media content of this multimedia communication session can be forwarded through the MF-A and MF-B networks to which terminal A and terminal B belong. Depending on the network deployment, MF-A and MF-B may be the same entity.

[0365] In one possible implementation, the aforementioned session invitation message or the aforementioned session re-invitation message may further include a second parameter, which can be used to indicate the session direction for activating / deactivating the intent assistive function.

[0366] For example, a feature-tag named Intent_Activate (the first parameter mentioned above) can be added to session invitation messages (such as SIP INVITE) or session re-invite messages (such as SIP re-INVITE). When the feature-tag is true, the intent assist feature is activated; when the feature-tag is false, the intent assist feature is deactivated. Another feature-tag named Intent_Direction (the second parameter mentioned above) can also be added to session invitation messages (such as SIP INVITE) or session re-invite messages (such as SIP re-INVITE). Its value can be uplink, downlink, or bidirectional, used to indicate the session direction for activating / deactivating the intent assist feature.

[0367] S702, CSCF-A sends the session invitation message or the session re-invitation message to NIAF.

[0368] In one possible implementation, after receiving the aforementioned session invitation message (such as SIP INVITE) or session re-invitation message (such as SIP re-INVITE), CSCF-A can parse the first parameter (such as feature-tag) to determine whether to activate the intent assistance function. If CSCF-A determines to activate the intent assistance function (e.g., the feature-tag value is true), then CSCF-A can forward the session invitation message or the session re-invitation message to NIAF. It can be understood that CSCF-A has already obtained the NIAF's routing address before forwarding the session invitation message or session re-invitation message to NIAF. For example, CSCF-A can obtain the NIAF's routing address through a SIP REGISTER message or through pre-configuration. After receiving the session invitation message or the session re-invitation message, NIAF can further forward the session invitation message or the session re-invitation message to the CSCF to which terminal B belongs (denoted as CSCF-B), CSCF-B then forwards it to the MF to which terminal B belongs (denoted as MF-B), and MF-B then forwards it to terminal B, so that terminal B knows that the intent assistance function has been activated.

[0369] In one possible implementation, after receiving the aforementioned session invitation message (such as SIP INVITE) or session re-invitation message (such as SIP re-INVITE), CSCF-A can send a session invitation response or a session re-invitation response to terminal A. The session invitation response can be used to indicate agreement to establish a multimedia communication session. The session re-invitation response can be used to indicate agreement to modify an existing multimedia communication session.

[0370] In one possible implementation, if the first parameter indicates that the intent assistance function is deactivated, CSCF-A can still forward the session invitation message or the session re-invitation message to NIAF, but CSCF-A will no longer forward the session message corresponding to the session invitation message or the session re-invitation message to NIAF. NIAF can also send the session invitation message or the session re-invitation message to terminal B through CSCF-B and MF-B, so that terminal B is aware that the intent assistance function has been deactivated.

[0371] S703, CSCF-A sends this session message to NIAF. This session message belongs to the session corresponding to the aforementioned session invitation message or the aforementioned session re-invitation message.

[0372] In one possible implementation, if the first parameter indicates activation of the intent assistance function, then the session messages between terminal A and terminal B will be forwarded through MF-A, MF-B, CSCF-A, CSCF-B, and NIAF. Therefore, after receiving the session message from terminal A, CSCF-A can send the session message to NIAF. This session message includes communication content, allowing NIAF to identify the user's communication intent based on the communication content in the session message. This session message can belong to the session corresponding to the aforementioned session invitation message or the aforementioned session re-invitation message.

[0373] It is understood that the embodiments of this application use the activation / deactivation of intent assistance function by terminal A as an example for illustration. In practical applications, the activation / deactivation of intent assistance function can also be done by terminal B, and the implementation method is similar to that of the embodiments of this application, which will not be repeated here. It is also understood that when the embodiments of this application are implemented in combination with the embodiments shown in Figure 5 or Figure 6 above, NIAF can also send intent service information to terminal A and / or terminal B along with the data. For example, NIAF can first send the obtained intent service information to MF-A and / or MF-B, and MF-A can insert the intent service information along with the data in the media plane message sent to terminal A, and / or MF-B can insert the intent service information along with the data in the media plane message sent to terminal B. In this implementation method, it may be necessary to extend the payload format of the media plane message to simultaneously include the original user session information and the related intent service information. In other words, the intent service information can be located in the payload part of the media plane message.

[0374] This application embodiment indicates the activation of intent assistance function by carrying parameters in the session invitation message or session re-invitation message, and adds NIAF to IMS so that NIAF can obtain the user's session content, support NIAF intent recognition, and lay the foundation for expressive communication.

[0375] Referring to Figure 13, which is an eighth flowchart illustrating the communication method provided in this application embodiment, this method mainly describes the session management process of bypassing NIAF into a user session based on an IP Multimedia System (IMS). The IMS may include a CSCF, MF, and NIAF, and optionally also an ISF. For example, NIAF and / or ISF respectively serve as an application server (AS) within the IMS. In this method, CSCF-A represents the CSCF to which terminal A belongs, and CSCF-B represents the CSCF to which terminal B belongs. In one possible implementation, this application embodiment can be implemented in conjunction with the embodiments shown in Figures 5 or 6 above, or it can be implemented independently; this application is not limited to this.

[0376] As shown in Figure 13, the communication method includes, but is not limited to, the following steps:

[0377] S801, Terminal A sends a session indication message to NIAF. This session indication message includes information indicating a session between Terminal A and Terminal B, and is used to instruct NIAF to insert into the session. Alternatively, this session indication message instructs NIAF to transmit intent service information with the media network element serving the session through the session.

[0378] In one possible implementation, prior to step S801, terminal A and terminal B have already established a multimedia communication session via IMS. After establishing the multimedia communication session, in response to user 1's activation of the intent assistance function, terminal A can generate a session indication message (e.g., SIP REFER) and send it to the NIAF. This session indication message may include identification information (e.g., Call-ID or Session-ID parameters) for one or more (existing) sessions. For example, the session indication message may also include an indication to activate the intent assistance function. This session indication message can be used to instruct the NIAF to insert into these one or more sessions. Alternatively, the session indication message can be used to instruct the NIAF to transmit intent service information through the session to the media network element (e.g., MF-A) serving the session.

[0379] It is understandable that the aforementioned session indication message can be forwarded through CSCF-A. In other words, the session indication message sent by terminal A first reaches CSCF-A, and after receiving the session indication message, CSCF-A can forward the session indication message to NIAF.

[0380] In step S802, NIAF sends a session re-invitation message to MF-A. This session re-invitation message includes information indicating the session between terminal A and terminal B, and is used to request joining the session. Alternatively, this session re-invitation message is used to request the transmission of intent service information through the session.

[0381] In one possible implementation, after receiving the aforementioned session indication message, the NIAF can send a session re-invitation message (such as a SIP re-INVITE) to the MF-A to which terminal A belongs. This session re-invitation message may include identification information for one or more of the aforementioned sessions (e.g., Call-ID or Session-ID parameters). This session re-invitation message can be used to request joining these one or more sessions. Alternatively, it can be used to request the transmission of intent service information through these one or more sessions.

[0382] S803, MF-A sends a session re-invitation response to NIAF. This session re-invitation response indicates agreement to transmit intent service information through the aforementioned session.

[0383] In one possible implementation, after receiving the aforementioned session re-invitation message, MF-A can negotiate with NIAF to establish a bidirectional multimedia channel based on the SDP media parameters in the message. For ease of distinction, this channel is referred to as the first multimedia channel. This first multimedia channel can transmit both user session messages and communication content, as well as intent service information. For example, MF-A sends a session re-invitation response to NIAF to indicate agreement to transmit intent service information through the aforementioned session. Subsequently, MF-A can forward session messages or communication content from one or more of the aforementioned sessions to NIAF, enabling NIAF to identify the user's communication intent based on the user's communication content.

[0384] In one possible implementation, after receiving the aforementioned session re-invitation message, MF-A can send a channel establishment message to terminal A. This channel establishment message can be used to request the establishment of a multimedia channel between MF-A and terminal A, which, for ease of distinction, is referred to as the second multimedia channel. Upon receiving this channel establishment message, terminal A can reply to MF-A with a channel establishment response, agreeing to establish the second multimedia channel between MF-A and terminal A. This second multimedia channel can be used to transmit intent service information. It can be understood that prior to this, a channel already exists between MF-A and terminal A for transmitting user data (i.e., communication content). The second multimedia channel established here can be dedicated to transmitting intent service information.

[0385] In one possible implementation, after receiving the aforementioned session indication message, NIAF can also send a session re-invitation message to the MF-B to which terminal B belongs. This session re-invitation message may include identification information (e.g., Call-ID or Session-ID parameters) of one or more of the aforementioned sessions. This session re-invitation message can be used to request joining these one or more sessions. After receiving the session re-invitation message, MF-B can also negotiate with NIAF to establish a bidirectional multimedia channel based on the SDP media parameters in the session re-invitation message. After receiving the session re-invitation message, MF-B can also send a channel establishment message to terminal B. This channel establishment message can be used to request the establishment of a multimedia channel between MF-B and terminal B; the specific establishment method is described above and will not be repeated here. After receiving the channel establishment message, terminal B can reply to MF-B with a channel establishment response, indicating its agreement to establish a multimedia channel between MF-B and terminal B.

[0386] It is understandable that when MF-B and MF-A are the same entity, or when terminal B does not need to obtain intent service information, NIAF does not need to send a session re-invitation message to MF-B.

[0387] This application embodiment adopts an out-of-session negotiation method to bypass and mount NIAF into the user's session, so that NIAF can obtain the user's session content, support NIAF's intent recognition, and lay the foundation for expressive communication.

[0388] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.

[0389] This application embodiment divides various network elements of this application into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The communication device of this application embodiment will be described in detail below with reference to Figures 14 to 16.

[0390] Referring to Figure 14, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device may include a transceiver unit 10 and a processing unit 20.

[0391] In some embodiments of this application, the communication device may be the NIAF shown above, or a chip or circuit disposed in the NIAF. That is, the communication device may be used to perform the steps or functions performed by the NIAF in the method embodiments described above.

[0392] The processing unit 20 is configured to identify the communication intent of a first user using the first terminal based on the communication content sent from the first terminal to the second terminal; the transceiver unit 10 is configured to send information describing the communication intent to the second network element; the transceiver unit 10 is also configured to receive first intent service information corresponding to the communication intent from the second network element; the processing unit 20 is also configured to provide a first intent service to the second terminal and / or the first terminal based on the first intent service information.

[0393] For example, the information described above for describing the communication intent includes one or more of the following: the category of the communication intent, the topic of the communication intent, the keywords of the communication intent, or the semantics of the communication intent.

[0394] For example, the transceiver unit 10 is further configured to: send a first query message to a third network element, the first query message being used to query a second network element that supports the communication intent; and receive a first response message from the third network element, the first response message including information about the second network element.

[0395] For example, the first query message includes the semantic vector of the communication intent. The similarity between the registration information vector of the second network element and the semantic vector of the communication intent is greater than a threshold. Alternatively, the second network element is a plurality of network elements corresponding to the top K similarity values ​​sorted from largest to smallest, where the plurality of similarity values ​​include the similarity between the semantic vector of the communication intent and the registration information vectors of the plurality of network elements stored in the third network element, and K is a positive integer.

[0396] For example, the processing unit 20 is specifically used to control the transceiver unit 10 to send the first intent service information to the second terminal and / or the first terminal; or, to send the second intent service information to the second terminal and / or the first terminal, wherein the second intent service information is the result of processing the first intent service information based on the capabilities of the second terminal and / or the first terminal.

[0397] For example, the second intent service information is the result of processing the first intent service information based on the capabilities of the second terminal and / or the first terminal, including: the second intent service information is intent service information whose display format of the first intent service information is processed to match the information display capabilities of the second terminal and / or the first terminal.

[0398] For example, the transceiver unit 10 is further configured to: send the address of the first network element to the second terminal and / or the first terminal; and receive a first message from the second terminal and / or the first terminal, the first message being used to obtain the first intent service. The processing unit 20 is specifically configured to provide the first intent service to the second terminal and / or the first terminal according to the first message.

[0399] For example, processing unit 20 is further configured to establish a communication connection with the second terminal and / or the first terminal. Specifically, processing unit 20 is further configured to provide the first intent service to the second terminal and / or the first terminal through the communication connection.

[0400] For example, the transceiver unit 10 is further configured to receive operation information from the first terminal and / or the second terminal, the operation information including operation events of the first user and / or the second user using the second terminal for the first intent service; the transceiver unit 10 is further configured to send the operation information to the second network element; the transceiver unit 10 is further configured to receive third intent service information from the second network element, the third intent service information being intent service information updated based on the first intent service information based on the operation events; the processing unit 20 is further configured to provide a second intent service to the second terminal and / or the first terminal based on the third intent service information.

[0401] For example, the processing unit 20 is specifically used to trigger the first terminal and / or the second terminal to execute the task corresponding to the third intent service information.

[0402] For example, the transceiver unit 10 is further configured to send one or more of the following to the second network element: the digital identity authorization information of the first user, or the digital identity authorization information of the second user; the digital identity authorization information of the first user or the digital identity authorization information of the second user is used to generate the third intent service information in conjunction with the operation event.

[0403] For example, the transceiver unit 10 is further configured to send one or more of the following to the second network element: the digital human information of the first user, the digital human information of the second user, the personalized information of the first user, and the personalized information of the second user. Wherein, the digital human information of the first user, the digital human information of the second user, the personalized information of the first user, or the personalized information of the second user are used in conjunction with the information describing the communication intent to generate the first intent service information.

[0404] For example, the transceiver unit 10 is further configured to receive the communication content from a user plane network element, the communication content being transmitted through a session between a first terminal and a second terminal, the user plane network element serving the session.

[0405] For example, the transceiver unit 10 is further configured to: receive a second message from a first terminal, the second message including information for indicating the session, the second message being used to instruct a first network element to insert into the session; and send a first request message to a fourth network element, the first request message being used to request the establishment of a connection between the first network element and a user plane network element serving the session, the first request message including the address of the first network element.

[0406] For example, the second message also includes indication information, which indicates that the transmission direction of the communication content is from the first terminal to the second terminal; the first request message also includes the second indication information.

[0407] For example, the transceiver unit 10 is further configured to: receive communication content from a media network element, the communication content being sent from the first terminal to the second terminal via the media network element and the first network element.

[0408] For example, the communication content is sent from the first terminal to the second terminal through the media network element and the first network element, including: the communication content is sent from the first terminal to the second terminal through a session, the session being a session between the first terminal, the media network element, the first network element, and the second terminal.

[0409] For example, the transceiver unit 10 is further configured to: receive a third message from a first terminal, the third message including information for indicating a session between the first terminal and a second terminal, the third message being used to instruct a first network element to transmit intent service information with a media network element serving the session through the session; send a fourth message to the media network element, the fourth message including the information for indicating the session, the fourth message being used to request the transmission of intent service information through the session; and receive a fifth message from the media network element, the fifth message being used to indicate agreement to transmit intent service information through the session.

[0410] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments, which will not be detailed here. In addition, the technical effects of the embodiments of this application are the same as those in the foregoing method embodiments, and will not be repeated here for the sake of brevity.

[0411] Reusing Figure 14, in some other embodiments of this application, the communication device may be the terminal A shown above, or a chip or circuit disposed in terminal A. That is, the communication device may be used to perform the steps or functions performed by terminal A in the method embodiments described above.

[0412] The transceiver unit 10 is used to send communication content to the second terminal, the communication content including the communication intent of the first user using terminal A; the transceiver unit 10 is also used to receive first intent service information corresponding to the communication intent; the processing unit 20 is used to call the application associated with the first intent service information to output the first intent service information.

[0413] For example, the display format of the first intent service information is matched with the information display capabilities of terminal A.

[0414] For example, the transceiver unit 10 is further configured to receive the address of the first network element; the transceiver unit 10 is further configured to send a first message to the first network element, the first message being used to obtain information related to the first intent service.

[0415] For example, the processing unit 20 is further configured to establish a communication connection with the first network element; the transceiver unit 10 is specifically configured to receive first intent service information corresponding to the communication intent through the communication connection.

[0416] For example, the processing unit 20 is further configured to generate operation information in response to the operation event of the first user on the first intent service information; the transceiver unit 10 is further configured to send the operation information to the first network element or the second network element; the transceiver unit 10 is further configured to receive second intent service information, which is the intent service information updated based on the operation event of the first intent service information.

[0417] For example, the processing unit 20 is also specifically used to invoke an application associated with the second intent service information to execute the task corresponding to the second intent service information based on the second intent service information.

[0418] For example, the communication content is transmitted through a session between terminal A and the second terminal. The transceiver unit 10 is also configured to send a second message to the first network element, the second message including information for indicating the session, the second message being used to instruct the first network element to insert into the session.

[0419] For example, the transceiver unit 10 is specifically used to receive a user plane message from a user plane network element serving the session, wherein the payload of the user plane message carries the first intent service information.

[0420] For example, the second message also includes indication information, which indicates that the transmission direction of the communication content is from terminal A to the second terminal.

[0421] For example, the communication content is transmitted through a session between terminal A and the second terminal. The transceiver unit 10 is further configured to send a third message to the first network element, the third message including information for indicating the session, the third message being used to instruct the first network element to transmit the first intent service information to the media network element serving the session through the session.

[0422] For example, the transceiver unit 10 is specifically used to receive a media plane message from the media network element serving the session, wherein the payload of the media plane message carries the first intent service information.

[0423] It is understood that the specific descriptions of the transceiver unit and processing unit shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver unit and processing unit, please refer to the above method embodiments, which will not be detailed here. In addition, the technical effects of the embodiments of this application are the same as those in the foregoing method embodiments, and will not be repeated here for the sake of brevity.

[0424] The communication device according to embodiments of this application has been described above. The following describes possible product forms of the communication device. It should be understood that any product possessing the functions of the communication device described in FIG. 7 falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the communication device according to the embodiments of this application to this extent.

[0425] In one possible implementation, in the communication device shown in FIG14, the processing unit 20 may be one or more processors, and the transceiver unit 10 may be a transceiver, or the transceiver unit 10 may also be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, and the receiving unit may be a receiver. The transmitting unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver may be coupled, etc., and the connection method of the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0426] Referring to Figure 15, which is another structural schematic diagram of the communication device provided in an embodiment of this application, the communication device provided in this application can be used to implement the methods described in any of the above method embodiments, as can be seen from the descriptions in the above method embodiments. The communication device can be any of the aforementioned functional entities, or chips or circuits therein. For example, the communication device includes one or more processors 1001 and transceivers 1002. The communication device may further include a memory 1003. In one implementation, the communication device also includes an input / output device (not shown in the figure).

[0427] The processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0428] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0429] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0430] The processor 1001, transceiver 1002, and memory 1003 can be connected via a communication bus.

[0431] The processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or for transmitting or relaying signals.

[0432] The processor 1001 may store instructions, which may be computer programs. These computer programs, running on the processor 1001, cause the communication device to perform the methods described in the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

[0433] In one implementation, the communication device may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0434] It is understood that the communication device shown in the embodiments of this application may have more components than those in Figure 15, and the embodiments of this application do not limit this. The methods executed by the processor and transceiver shown above are merely examples, and the specific steps executed by the processor and transceiver can be referred to the description of the method embodiments above.

[0435] In another possible implementation, in the communication device shown in FIG14, the processing unit 20 can be one or more logic circuits, and the transceiver unit 10 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver unit 10 can also be a sending unit and a receiving unit. The sending unit can be an output interface, and the receiving unit can be an input interface. The sending unit and the receiving unit are integrated into one unit, such as an input / output interface. Referring to FIG16, FIG16 is another structural schematic diagram of the communication device provided in the embodiments of this application. As shown in FIG16, the communication device shown in FIG16 includes a logic circuit 901 and an interface 902. That is, the above-mentioned processing unit 20 can be implemented by the logic circuit 901, and the transceiver unit 10 can be implemented by the interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input / output interface, a pin, etc. For example, FIG16 shows the above-mentioned communication device as a chip, which includes a logic circuit 901 and an interface 902.

[0436] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. This logic circuit and interface can be used to implement the methods described in any of the above method embodiments; please refer to the descriptions in the above method embodiments.

[0437] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.

[0438] For specific implementations of the embodiment shown in Figure 16, please refer to the above embodiments, which will not be described in detail here.

[0439] This application also provides a communication system, which includes a NIAF, an ISF, terminal A, and terminal B; optionally, it also includes an ISRF. The NIAF, ISF, terminal A, and terminal B can be used to execute the methods in any of the foregoing method embodiments.

[0440] In addition, this application also provides a computer program for implementing the operations and / or processes performed by any network element in any of the above-described method embodiments in the methods provided in this application.

[0441] This application also provides a computer program for implementing the operations and / or processes performed by a terminal in the method provided in this application.

[0442] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform operations and / or processes performed by any network element in any of the above-described method embodiments in the methods provided in this application.

[0443] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by a terminal in the method provided in this application.

[0444] This application also provides a computer program product, which includes computer code or a computer program, which, when run on a computer, causes the operations and / or processes performed by any network element in any of the above-described method embodiments to be executed in the methods provided in this application.

[0445] This application also provides a computer program product, which includes computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by a terminal in the method provided in this application to be executed.

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

[0447] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0448] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0449] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0450] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first network element identifies the communication intent of the first user using the first communication device based on the communication content sent from the first communication device to the second communication device. The first network element sends information describing the communication intent to the second network element; The first network element receives first intent service information corresponding to the communication intent from the second network element; Based on the first intent service information, the first network element provides the first intent service to the second communication device and / or the first communication device.

2. The method according to claim 1, characterized in that, The information used to describe the communication intent includes one or more of the following: the category of the communication intent, the topic of the communication intent, the keywords of the communication intent, or the semantics of the communication intent.

3. The method according to claim 1 or 2, characterized in that, Before the first network element sends information describing the communication intent to the second network element, the method further includes: The first network element sends a first query message to the third network element, the first query message being used to query a second network element that supports the communication intent; The first network element receives a first response message from the third network element, the first response message including information from the second network element.

4. The method according to claim 3, characterized in that, The first query message includes a semantic vector of the communication intent; The similarity between the registration information vector of the second network element and the semantic vector of the communication intent is greater than a threshold; Alternatively, the second network element is a network element corresponding to the top K similarity values ​​sorted from largest to smallest. The multiple similarities include the similarity between the semantic vector of the communication intent and the registration information vectors of the multiple network elements stored in the third network element, where K is a positive integer.

5. The method according to any one of claims 1 to 4, characterized in that, The first network element provides a first intent service to the second communication device and / or the first communication device, including: The first network element sends the first intent service information to the second communication device and / or the first communication device; or... The first network element sends second intent service information to the second communication device and / or the first communication device. The second intent service information is the result of processing the first intent service information based on the capabilities of the second communication device and / or the first communication device.

6. The method according to claim 5, characterized in that, The second intent service information is the result of processing the first intent service information based on the capabilities of the second communication device and / or the first communication device, including: The second intent service information is intent service information whose display format is processed to match the information display capabilities of the second communication device and / or the first communication device.

7. The method according to any one of claims 1 to 6, characterized in that, Before the first network element provides the first intent service to the second communication device and / or the first communication device, the method further includes: The first network element sends its address to the second communication device and / or the first communication device. The first network element receives a first message from the second communication device and / or the first communication device, the first message being used to obtain the first intent service; The first network element provides a first intent service to the second communication device and / or the first communication device, including: the first network element provides a first intent service to the second communication device and / or the first communication device according to a first message.

8. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The first network element establishes a communication connection with the second communication device and / or the first communication device; The first network element provides a first intent service to the second communication device and / or the first communication device, including: The first network element provides the first intent service to the second communication device and / or the first communication device through the communication connection.

9. The method according to any one of claims 1 to 8, characterized in that, After the first network element provides the first intent service to the second communication device and / or the first communication device, the method further includes: The first network element receives operation information from the first communication device and / or the second communication device, the operation information including operation events of the first user and / or the second user using the second communication device for the first intention service; The first network element sends the operation information to the second network element; The first network element receives third intent service information from the second network element, wherein the third intent service information is intent service information updated based on the operation event; Based on the third intent service information, the first network element provides the second intent service to the second communication device and / or the first communication device.

10. The method according to claim 9, characterized in that, The first network element provides a second intent service to the second communication device and / or the first communication device, including: The first network element triggers the first communication device and / or the second communication device to execute the task corresponding to the third intent service information.

11. The method according to claim 10, characterized in that, Before the first network element receives the third intent service information from the second network element, the method further includes: The first network element sends one or more of the following to the second network element: the digital identity authorization information of the first user, or the digital identity authorization information of the second user; the digital identity authorization information of the first user or the digital identity authorization information of the second user is used to generate the third intent service information in conjunction with the operation event.

12. The method according to any one of claims 1 to 11, characterized in that, Before the first network element receives the first intent service information corresponding to the communication intent from the second network element, the method further includes: The first network element sends one or more of the following to the second network element: the digital human information of the first user, the digital human information of the second user, the personalized information of the first user, and the personalized information of the second user; Wherein, the digital human information of the first user, the digital human information of the second user, the personalized information of the first user, or the personalized information of the second user are used in combination with the information used to describe the communication intent to generate the first intent service information.

13. The method according to any one of claims 1 to 12, characterized in that, Before the first network element identifies the communication intent of the first user using the first communication device based on the communication content sent from the first communication device to the second communication device, the method further includes: The first network element receives the communication content from the user plane network element, and the communication content is transmitted through a session between the first communication device and the second communication device, with the user plane network element serving the session.

14. The method according to claim 13, characterized in that, Before the first network element receives the communication content from the user plane network element, the method further includes: The first network element receives a second message from the first communication device, the second message including information for indicating the session, the second message being used to instruct the first network element to insert into the session; The first network element sends a first request message to the fourth network element (ISMF). The first request message is used to request the establishment of a connection between the first network element and the user plane network element serving the session. The first request message includes the address of the first network element.

15. The method according to claim 14, characterized in that, The second message also includes indication information, which indicates that the transmission direction of the communication content is from the first communication device to the second communication device; the first request message also includes the second indication information.

16. The method according to any one of claims 1 to 12, characterized in that, Before the first network element identifies the communication intent of the first user using the first communication device based on the communication content sent from the first communication device to the second communication device, the method further includes: The first network element receives communication content from the media network element, the communication content being sent by the first communication device to the second communication device through the media network element and the first network element.

17. The method according to claim 16, characterized in that, The communication content is sent from the first communication device to the second communication device via the media network element and the first network element, including: The communication content is sent from the first communication device to the second communication device through a session, and the session is a session between the first communication device, the media network element, the first network element, and the second communication device.

18. The method according to claim 16 or 17, characterized in that, Before the first network element receives communication content from the media network element, the method further includes: The first network element receives a third message from the first communication device, the third message including information for indicating a session between the first communication device and the second communication device, the third message being used to instruct the first network element to transmit intent service information to a media network element serving the session through the session; The first network element sends a fourth message to the media network element, the fourth message including the information used to indicate the session, the fourth message being used to request the transmission of intent service information through the session; The first network element receives a fifth message from the media network element, the fifth message indicating agreement to transmit intent service information through the session.

19. A communication method, characterized in that, include: The first communication device sends communication content to the second communication device, the communication content including the communication intent of the first user using the first communication device; The first communication device receives first intent service information corresponding to the communication intent, and calls the application associated with the first intent service information to output the first intent service information.

20. The method according to claim 19, characterized in that, The display format of the first intent service information matches the information display capability of the first communication device.

21. The method according to claim 19 or 20, characterized in that, Before the first communication device receives the first intent service information corresponding to the communication intent, the method further includes: The first communication device receives the address of the first network element; The first communication device sends a first message to the first network element, the first message being used to obtain information related to the first intent service.

22. The method according to claim 19 or 20, characterized in that, Before the first communication device receives the first intent service information corresponding to the communication intent, the method further includes: The first communication device establishes a communication connection with the first network element; The first communication device receives first intent service information corresponding to the communication intent, including: the first communication device receives first intent service information corresponding to the communication intent through the communication connection.

23. The method according to any one of claims 19 to 22, characterized in that, After the first communication device invokes the first application associated with the first intent service information to output the first intent service information, the method further includes: The first communication device generates operation information in response to the first user's operation event regarding the first intent service information; The first communication device sends the operation information to the first network element or the second network element; The first communication device receives second intent service information, which is intent service information updated based on the operation event.

24. The method according to claim 23, characterized in that, After the first communication device receives the second intent service information, the method further includes: The first communication device invokes the application associated with the second intent service information to execute the task corresponding to the second intent service information based on the second intent service information.

25. The method according to claim 19 or 20, characterized in that, The communication content is transmitted through a session between the first communication device and the second communication device; Before the first communication device receives the first intent service information corresponding to the communication intent, the method further includes: The first communication device sends a second message to the first network element. The second message includes information for indicating the session and is used to instruct the first network element to insert into the session.

26. The method according to claim 25, characterized in that, The first communication device receives first intent service information corresponding to the communication intent, including: The first communication device receives a user plane message from a user plane network element serving the session, and the payload of the user plane message carries the first intent service information.

27. The method according to claim 25 or 26, characterized in that, The second message also includes indication information, which indicates that the transmission direction of the communication content is from the first communication device to the second communication device.

28. The method according to claim 19 or 20, characterized in that, The communication content is transmitted through a session between the first communication device and the second communication device; Before the first communication device receives the first intent service information corresponding to the communication intent, the method further includes: The first communication device sends a third message to the first network element. The third message includes information for instructing the first network element to transmit the first intent service information to the media network element serving the session through the session.

29. The method according to claim 28, characterized in that, The first communication device receives first intent service information corresponding to the communication intent, including: The first communication device receives a media plane message from a media network element serving the session, and the payload of the media plane message carries the first intent service information.

30. The method according to any one of claims 1 to 29, characterized in that, The first communication device is a terminal or a chip.

31. A communication device, characterized in that, Includes units or modules for performing the method according to any one of claims 1 to 30.

32. 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 and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 30 through logic circuits or executing code instructions.

33. A readable storage medium, characterized in that, The device is used to store a program, which is executed by one or more processors, such that a device including the one or more processors performs the method as described in any one of claims 1 to 30.

34. A computer program product, characterized in that, The computer program product includes computer code or a computer program, and when the computer code or computer program is run on a computer, the method as described in any one of claims 1 to 30 is performed.

35. [Correction 27.02.2025 based on Rule 91] A communication system, characterized in that, It includes a first network element and a second network element, wherein the first network element is used to perform the method as described in any one of claims 1 to 18, and the second network element is used to receive information from the first network element and / or send information to the first network element.

36. [Correction 27.02.2025 according to Rule 91] The method according to claim 35, characterized in that, The communication system further includes a communication means for performing the method as described in any one of claims 19 to 30.

37. [Corrected according to Rule 91, February 27, 2025] A communication method, characterized in that, include: The first network element identifies the communication intent of the first user using the first communication device based on the communication content sent from the first communication device to the second communication device. The first network element sends information describing the communication intent to the second network element; The second network element receives the information describing the communication intent from the first network element, and sends first intent service information corresponding to the communication intent to the first network element; The first network element receives the first intent service information from the second network element, and provides the first intent service to the second communication device and / or the first communication device based on the first intent service information.

38. [Correction 27.02.2025 according to Rule 91] The method according to claim 37, characterized in that, The method further includes: The first communication device sends communication content to the second communication device, the communication content including the communication intention of the first user using the first communication device.

39. [Correction 27.02.2025 according to Rule 91] The method according to claim 38, characterized in that, The method further includes: The first communication device receives first intent service information corresponding to the communication intent, and calls the application associated with the first intent service information to output the first intent service information.

Images