Communication method, device and system
By introducing intelligent agents into the communication system, identifying and realizing user intentions, the problem of system design complexity in the prior art is solved, and more efficient intention translation and system operation are achieved.
Patent Information
- Application Number
- CN202311464430.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-03
- Publication Date
- 2025-05-06
AI Technical Summary
The enhanced evolution of the existing mobile network protocol system has led to the accumulation of complexity in system design and implementation, and there is unsustainability. The main reason is that the design complexity of the architecture system and signaling process depends on the number of business scenarios, business processes and network functions.
By introducing intelligent agents endogenous to the network, we can identify and understand user's intentions, and realize the mapping and orchestration of intentions to scenarios and service flows, thereby driving network functions and terminal devices to realize user intentions and reducing the complexity of internal process design.
It reduces the complexity of internal process design of the communication system, enables the terminal equipment to interact with the network through intentional interfaces, reduces the learning cost of terminal network use, and improves the efficiency of intentional translation and the overall working efficiency of the system.
Smart Images

Figure CN119946655A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communication technology, and more specifically, to a communication method, device and system. Background Art
[0002] The sixth generation (6G) system adds resources and capabilities in new dimensions of computing, intelligence, data, and perception based on enhanced connectivity. It is no longer a simple pipeline, but provides platform-based service capabilities, thus realizing the intelligent connection of all things.
[0003] However, the enhanced evolution based on the existing mobile network protocol system will cause the complexity of system design and implementation to accumulate continuously, which is unsustainable. The main reason is that the existing network architecture relies on the definition of standardized signaling processes. The complexity of the design of the architecture system and signaling processes depends on the number of business scenarios, the number of business processes in each scenario, and the number of network functions involved in each business process. As the types and number of objects participating in the interaction in the communication system increase, the traditional end-to-end signaling process customization method will cause problems such as many signaling types, complex logic, long version iteration cycle, and poor scalability. Summary of the invention
[0004] The embodiments of the present application provide a communication method and device to reduce the complexity of internal process design of a communication system.
[0005] In the first aspect, a communication method is provided, which can be executed by a first network element, or by a module (such as a chip or circuit) in the first network element, or by a logical node, logical module or software that can implement all or part of the functions of the first network element, and the present application does not limit this.
[0006] The method includes: receiving first information from a terminal device, the first information is used to describe an intention; obtaining capabilities and capability calling methods of at least one object, the capabilities of at least one object being related to the intention; determining an information interaction method between a first network element and at least one object based on the capabilities and capability calling methods of at least one object, the information interaction method being used to realize the intention; and calling the capabilities of at least one object based on the information interaction method.
[0007] Optionally, the first network element may be a network intelligent agent function (NIAF).
[0008] According to the technical solution provided by this application, only the calling method of each object capability needs to be defined within the network, and the scenarios and business processes are automatically generated by the first network element, thereby reducing the complexity of internal process design. In addition, the terminal device and NIAF interact through the intentional interface, and the first network element translates the intention into the business process within the network, thereby reducing the learning cost of the terminal using the network.
[0009] In combination with the first aspect, in certain implementations of the first aspect, obtaining the capability and capability calling method of at least one object includes: sending a first message to a second network element, the first message being used to request the capability and capability calling method of at least one object, the first message including an identifier of at least one object; receiving the capability and capability calling method of at least one object from the second network element.
[0010] Optionally, the second network element may be a registration function (RF).
[0011] According to the above technical solution, only the interaction between the first network element and the second network element is required to translate the intent description into an information interaction process that can realize the intent, thereby improving the efficiency of intent translation.
[0012] On the second aspect, a communication method is provided, which can be executed by a first network element, or by a module (such as a chip or circuit) in the first network element, or by a logical node, logical module or software that can implement all or part of the functions of the first network element, and the present application does not limit this.
[0013] The method includes: receiving first information from a terminal device, the first information is used to describe the intention; sending second information to a third network element, the second information is used to describe the intention; receiving third information from the third network element, the third information is used to indicate an information interaction method between the first network element and at least one object, the information interaction method is used to realize the intention, the information interaction method is determined according to the capability and capability calling method of at least one object; calling the capability of at least one object according to the information interaction method.
[0014] Optionally, the third network element may be an intent knowledge base (IKB).
[0015] According to the technical solution provided in the present application, the first network element requests the third network element to assist in identifying and translating the intent, so that the first network element can directly obtain the information interaction method returned by the third network element, thereby saving the computing power of the first network element, and using the saved computing power to execute other tasks of the first network element, thereby improving the overall working efficiency of the communication system.
[0016] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: updating a local intent knowledge base in the first network element according to the intent and the information interaction method, wherein the local intent knowledge base is used to determine the information interaction method corresponding to the intent.
[0017] According to the above technical solution, the first network element can continuously learn according to the data generated in the actual work process, so as to automatically adapt to the ability of new intents and / or new objects, and improve the business scenarios and accuracy that can be covered by intent translation without interface and process upgrades. In addition, after updating the local knowledge base, the first network element can directly translate the same or similar intents encountered in subsequent work without the help of a third network element, thereby improving the efficiency of intent translation.
[0018] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, calling the capability of at least one object according to the information interaction method includes: sending information of a sub-intent describing the intent to at least part of the at least one object.
[0019] According to the above technical solution, an intent with a complex implementation process can be decomposed into multiple sub-intentions with relatively simple implementation processes, and translated in parallel by multiple objects that can process the intent, thereby improving the overall intent translation efficiency of the communication system.
[0020] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, the method further includes: sending a result of realizing the intention to a terminal device.
[0021] According to the above technical solution, the terminal device can obtain the results of the implementation of the intention, thereby improving the user experience.
[0022] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, before receiving the first information from the terminal device, the method also includes: establishing a session with the terminal device through a fourth network element; receiving the first information from the terminal device, including: receiving the first information through the session.
[0023] Optionally, the fourth network element may be an intelligent session management function (ISMF).
[0024] According to the above technical solution, the terminal device can establish an intent-driven intelligent session with the first network element, so that the terminal device can interact with the network through an intention-based interface, reducing the learning cost of the terminal using the network.
[0025] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0026] According to the above technical solution, multiple types of schedulable objects are provided in the process of realizing intentions, so that more complex and diverse intentions can be realized, thereby enriching the task scenarios corresponding to the achievable intentions.
[0027] On the third aspect, a communication method is provided, which can be executed by a second network element, or by a module (such as a chip or circuit) in the second network element, or by a logical node, logical module or software that can implement all or part of the functions of the second network element, and the present application does not limit this.
[0028] The method comprises: receiving a message for requesting the capability and capability calling method of at least one object, the message comprising the identification of at least one object; and sending the capability and capability calling method of at least one object according to the identification of at least one object.
[0029] Optionally, the second network element may receive a message for requesting the capability and capability calling method of at least one object from the first network element, and correspondingly, the second network element sends the capability and capability calling method of at least one object to the first network element.
[0030] Optionally, the second network element may receive a message for requesting the capability and capability calling method of at least one object from the third network element, and correspondingly, the second network element sends the capability and capability calling method of at least one object to the third network element.
[0031] According to the technical solution provided in the present application, a unified channel for saving and querying the capability information of each callable object is provided for other first network elements and third network elements in the network, thereby avoiding the need to separately maintain the capability information of the object in multiple first network elements and second network elements, and saving the overall storage space of the system.
[0032] In combination with the third aspect, in certain implementations of the third aspect, before receiving a message for requesting the capabilities and capability calling methods of at least one object, the method also includes: receiving the identification, capabilities, and capability calling methods of at least one object; saving the capability template of at least one object, the capability template of each object in the at least one object including the identification, capabilities, and capability calling methods of the object.
[0033] According to the above technical solution, the second network element can provide a channel for object capability registration and specifically save and maintain the capability template of the object, thereby facilitating the first network element and the third network element to quickly and accurately query the required object capabilities and improve the efficiency and accuracy of the communication system translation intent.
[0034] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: querying a capability template of at least one object based on an identifier of at least one object to determine the capability and capability calling method of the at least one object.
[0035] According to the above technical solution, the second network element can query the capability template of the object based on the representation of the object, thereby improving the efficiency and accuracy of obtaining the required capabilities and capability calling methods.
[0036] In combination with the third aspect, in certain implementations of the third aspect, before receiving the identification, capability and capability calling method of at least one object, the method also includes: receiving a second message from a third network element, the second message being used to subscribe to the capability template of the object; after saving the capability template of at least one object, the method also includes: sending the capability template of at least one object to the third network element.
[0037] According to the above technical solution, the third network element can subscribe to the capability template from the second network element, so that the third network element can obtain the capability template of the latest registered object, so that the first network element or the third network element can learn the achievable intentions and build an intention knowledge base, thereby improving the effect of translating the intentions of the terminal device into specific business processes or task scheduling strategies.
[0038] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: receiving an identifier, capability, capability calling method of a terminal device and an identifier of a first network element from a fourth network element, wherein a session exists between the first network element and the terminal device; saving a capability template of the terminal device, wherein the capability template of the terminal device includes the identifier, capability, capability calling method of the terminal device and an identifier of the first network element; or saving the capability template of the terminal device and the identifier of the first network element, wherein the capability template of the terminal device includes the identifier, capability, capability calling method of the terminal device, and the capability template of the terminal device corresponds to the identifier of the first network element.
[0039] According to the above technical solution, the second network element can also save the association information between the terminal device and the first network element, so that the capabilities of the terminal device can also be called during the intention realization process, thereby expanding the application scenarios corresponding to the achievable intention to the business level.
[0040] In combination with the third aspect, in certain implementations of the third aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent agent, and a terminal device.
[0041] According to the above technical solution, multiple types of schedulable objects are provided in the process of realizing intentions, so that more complex and diverse intentions can be realized, thereby enriching the task scenarios corresponding to the achievable intentions.
[0042] In a fourth aspect, a communication method is provided, which can be executed by a third network element, or by a module (such as a chip or circuit) in the third network element, or by a logical node, logical module or software that can implement all or part of the functions of the third network element. The present application does not limit this.
[0043] The method includes: receiving second information from a first network element, the second information is used to describe an intention; obtaining capabilities and capability calling methods of at least one object, the capabilities of at least one object being related to the intention; determining an information interaction method between the first network element and at least one object based on the capabilities and capability calling methods of at least one object, the information interaction method being used to implement the intention; and sending third information to the first network element, the third information being used to indicate the information interaction method.
[0044] According to the technical solution provided in the present application, a new network element, a third network element, is introduced into the network to assist the first network element in identifying and translating intent, so that the first network element can directly obtain the information interaction method returned by the third network element, thereby saving the computing power of the first network element, and using the saved computing power to execute other tasks of the first network element, thereby improving the overall working efficiency of the communication system.
[0045] In combination with the fourth aspect, in certain implementations of the fourth aspect, obtaining the capabilities and capability calling methods of at least one object includes: sending a third message to a second network element, the third message being used to request the capabilities and capability calling methods of at least one object, the third message including an identifier of at least one object; receiving the capabilities and capability calling methods of at least one object from the second network element.
[0046] According to the above technical solution, the third network element can use the second network element to query the calling method of the object capability, thereby improving the efficiency and accuracy of obtaining the required capabilities and the capability calling method.
[0047] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method also includes: sending a second message to a second network element, the second message is used to subscribe to a capability template of an object, the capability template including an identifier of the object and the capabilities and capability calling method of the object; receiving capability templates of one or more objects from the second network element; and updating an intent knowledge base based on the capability templates of one or more objects, the intent knowledge base being used to determine an information interaction method corresponding to the intent.
[0048] According to the above technical solution, the third network element can subscribe to the capability template from the second network element, so that the third network element can obtain the capability template of the latest registered object, so that the third network element can learn the achievable intentions and build an intention knowledge base, thereby improving the effect of translating the intentions of the terminal device into specific business processes or task scheduling strategies.
[0049] In combination with the fourth aspect, in certain implementations of the fourth aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0050] According to the above technical solution, multiple types of schedulable objects are provided in the process of realizing intentions, so that more complex and diverse intentions can be realized, thereby enriching the task scenarios corresponding to the achievable intentions.
[0051] In the fifth aspect, a communication method is provided, which can be executed by a fourth network element, or by a module (such as a chip or circuit) in the fourth network element, or by a logical node, logical module or software that can implement all or part of the functions of the fourth network element. The present application does not limit this.
[0052] The method includes: receiving a fourth message from a terminal device, the fourth message is used to request to establish a session, the fourth message includes an identifier, capabilities and a capability calling method of the terminal device; according to the fourth message, establishing a session between the terminal device and a first network element, the first network element being used to realize the intention through information interaction with at least one object; and sending the identifier, capabilities, capability calling method of the terminal device and the identifier of the first network element to a second network element.
[0053] According to the technical solution provided in this application, the terminal device can establish an intent-driven endogenous intelligent session with the first network element, so that the terminal device can interact with the network through an intention-based interface, reducing the learning cost of the terminal using the network.
[0054] In combination with the fifth aspect, in certain implementations of the fifth aspect, the session is used to transmit intent and / or invoke capabilities of the terminal device.
[0055] According to the above technical solution, multimodal information interaction can be performed between the terminal device and the first network element through intelligent conversation, thereby enriching the achievable business scenarios and reducing the learning cost of the terminal device to use the network.
[0056] In combination with the fifth aspect, in certain implementations of the fifth aspect, before establishing a session between the terminal device and the first network element, the method also includes: selecting the first network element.
[0057] According to the above technical solution, the fourth network element can select a first network element that is most suitable for establishing an intelligent session with the terminal device when there are multiple available first network elements, thereby improving the intention interaction effect between the first network element and the terminal device.
[0058] In combination with the fifth aspect, in certain implementations of the fifth aspect, after establishing a session between the terminal device and the first network element, the method further includes: sending an address of the first network element to the terminal device.
[0059] According to the above technical solution, the terminal device can establish an intelligent session with the first network element and interact with information.
[0060] In combination with the fifth aspect, in certain implementations of the fifth aspect, before sending the address of the first network element to the terminal device, the method further includes: receiving the address of the first network element from the first network element.
[0061] According to the above technical solution, the efficiency of the fourth network element in establishing an intelligent session between the terminal device and the first network element can be improved.
[0062] In combination with the fifth aspect, in certain implementations of the fifth aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0063] According to the above technical solution, multiple types of schedulable objects are provided in the process of realizing intentions, so that more complex and diverse intentions can be realized, thereby enriching the task scenarios corresponding to the achievable intentions.
[0064] In a sixth aspect, a communication device is provided, which may be a first network element, or a module (such as a chip or circuit) in the first network element, or a logical node, a logical module or software that can realize all or part of the functions of the first network element. The device includes: a transceiver unit, which is used to receive first information from a terminal device, and the first information is used to describe an intention; a processing unit, which is also used to obtain the capability and capability calling method of at least one object, and the capability of at least one object is related to the intention; the processing unit is used to determine the information interaction method between the first network element and at least one object according to the capability and capability calling method of at least one object, and the information interaction method is used to realize the intention; the processing unit is also used to call the capability of at least one object according to the information interaction method.
[0065] Optionally, the first network element may be a NIAF.
[0066] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is specifically used to: send a first message to a second network element, the first message being used to request capabilities and capability calling methods of at least one object, the first message including an identifier of at least one object; and receive capabilities and capability calling methods of at least one object from the second network element.
[0067] In the seventh aspect, a communication device is provided, which may be a first network element, or a module (such as a chip or circuit) in the first network element, or a logical node, a logical module or software that can realize all or part of the functions of the first network element. The device includes: a transceiver unit, which is used to receive first information from a terminal device, and the first information is used to describe the intention; the transceiver unit is also used to send second information to a third network element, and the second information is used to describe the intention; the transceiver unit is also used to receive third information from the third network element, and the third information is used to indicate an information interaction method between the first network element and at least one object, and the information interaction method is used to realize the intention, and the information interaction method is determined according to the capability and capability calling method of at least one object; a processing unit is used to call the capability of at least one object according to the information interaction method.
[0068] In combination with the seventh aspect, in certain implementations of the seventh aspect, the processing unit is also used to: update a local intent knowledge base in the first network element based on the intent and the information interaction method, and the local intent knowledge base is used to determine the information interaction method corresponding to the intent.
[0069] In combination with the sixth aspect or the seventh aspect, in certain implementations of the sixth aspect or the seventh aspect, the processing unit is specifically used to: send information of a sub-intent describing an intent to at least part of the objects in at least one object.
[0070] In combination with the sixth aspect or the seventh aspect, in certain implementations of the sixth aspect or the seventh aspect, the transceiver unit is further used to: send the result of the implementation of the intention to the terminal device.
[0071] In combination with the sixth aspect or the seventh aspect, in certain implementations of the sixth aspect or the seventh aspect, before receiving the first information from the terminal device, the processing unit is also used to: establish a session with the terminal device through a fourth network element; the transceiver unit is specifically used to: receive the first information through the session.
[0072] In combination with the sixth aspect or the seventh aspect, in certain implementations of the sixth aspect or the seventh aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0073] In an eighth aspect, a communication device is provided, which may be a second network element, or a module (such as a chip or circuit) in the second network element, or a logical node, a logical module or software that can implement all or part of the functions of the second network element. The device includes: a transceiver unit, configured to receive a message for requesting the capability and capability calling method of at least one object, the message including an identifier of at least one object; and the transceiver unit, further configured to send the capability and capability calling method of at least one object according to the identifier of at least one object.
[0074] Optionally, the second network element may be RF.
[0075] In combination with the eighth aspect, in certain implementations of the eighth aspect, before receiving a message for requesting the capabilities and capability calling methods of at least one object, the transceiver unit is also used to: receive the identification, capabilities and capability calling methods of at least one object; the device also includes a processing unit, used to: save the capability template of at least one object, the capability template of each object in the at least one object includes the identification, capabilities and capability calling methods of the object.
[0076] In combination with the eighth aspect, in certain implementations of the eighth aspect, the processing unit is further used to: query the capability template of at least one object based on the identification of at least one object to determine the capability and capability calling method of the at least one object.
[0077] In combination with the eighth aspect, in certain implementations of the eighth aspect, before receiving the identification, capability and capability calling method of at least one object, the transceiver unit is also used to: receive a second message from a third network element, the second message being used to subscribe to the capability template of the object; after saving the capability template of at least one object, the transceiver unit is also used to: send the capability template of at least one object to the third network element.
[0078] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is also used to: receive the identifier, capability, capability calling method of the terminal device from the fourth network element, and the identifier of the first network element, and a session exists between the first network element and the terminal device; the processing unit is also used to: save the capability template of the terminal device, the capability template of the terminal device includes the identifier, capability, capability calling method of the terminal device, and the identifier of the first network element; or save the capability template of the terminal device and the identifier of the first network element, the capability template of the terminal device includes the identifier, capability, capability calling method of the terminal device, and the capability template of the terminal device corresponds to the identifier of the first network element.
[0079] In combination with the eighth aspect, in certain implementations of the eighth aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0080] In the ninth aspect, a communication device is provided, which may be a third network element, or a module (such as a chip or circuit) in the third network element, or a logical node, a logical module or software that can realize all or part of the functions of the third network element. The device includes: a transceiver unit, which is used to receive second information from the first network element, and the second information is used to describe the intention; a processing unit, which is also used to obtain the capability and capability calling method of at least one object, and the capability of at least one object is related to the intention; the processing unit is used to determine the information interaction method between the first network element and at least one object according to the capability and capability calling method of at least one object, and the information interaction method is used to realize the intention; the transceiver unit is also used to send third information to the first network element, and the third information is used to indicate the information interaction method.
[0081] Optionally, the third network element may be an IKB.
[0082] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver unit is specifically used to: send a third message to the second network element, the third message is used to request the capabilities and capability calling method of at least one object, the third message including the identifier of at least one object; receive the capabilities and capability calling method of at least one object from the second network element.
[0083] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver unit is also used to: send a second message to a second network element, the second message is used to subscribe to a capability template of an object, the capability template including an identifier of the object and the capabilities and capability calling method of the object; receive capability templates of one or more objects from the second network element; the processing unit is also used to: update an intent knowledge base based on the capability templates of one or more objects, the intent knowledge base being used to determine an information interaction method corresponding to the intent.
[0084] In combination with the ninth aspect, in certain implementations of the ninth aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0085] In the tenth aspect, a communication device is provided, which may be a fourth network element, or a module (such as a chip or circuit) in the fourth network element, or a logical node, a logical module or software that can realize all or part of the functions of the fourth network element. The device includes: a transceiver unit, which is used to receive a fourth message from a terminal device, the fourth message is used to request to establish a session, and the fourth message includes the identification, capabilities and capability calling method of the terminal device; a processing unit, which is used to establish a session between the terminal device and the first network element according to the fourth message, and the first network element is used to realize the intention through information interaction with at least one object; the transceiver unit is also used to send the identification, capabilities, capability calling method of the terminal device and the identification of the first network element to the second network element.
[0086] Optionally, the fourth network element may be an ISMF.
[0087] In combination with the tenth aspect, in certain implementations of the tenth aspect, the session is used to transmit intent and / or invoke capabilities of the terminal device.
[0088] In combination with the tenth aspect, in certain implementations of the tenth aspect, before establishing a session between the terminal device and the first network element, the processing unit is further used to: select the first network element.
[0089] In combination with the tenth aspect, in certain implementations of the tenth aspect, after establishing a session between the terminal device and the first network element, the transceiver unit is further used to: send an address of the first network element to the terminal device.
[0090] In combination with the tenth aspect, in certain implementations of the tenth aspect, before sending the address of the first network element to the terminal device, the transceiver unit is further used to: receive the address of the first network element from the first network element.
[0091] In combination with the tenth aspect, in certain implementations of the tenth aspect, at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent body, and a terminal device.
[0092] In the eleventh aspect, a communication device is provided, comprising a processor, wherein the processor is used to, by executing a computer program or instruction or through a logic circuit, enable the communication device to perform the method described in the first aspect and any possibility of the first aspect; or enable the communication device to perform the method described in the second aspect and any possibility of the second aspect; or enable the communication device to perform the method described in the third aspect and any possibility of the third aspect; or enable the communication device to perform the method described in the fourth aspect and any possibility of the fourth aspect; or enable the communication device to perform the method described in the fifth aspect and any possibility of the fifth aspect.
[0093] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.
[0094] In a possible implementation manner, the communication device further includes a communication interface, which is used to input and / or output signals.
[0095] In the twelfth aspect, a communication device is provided, comprising a logic circuit and an input-output interface, the input-output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect or any possibility of the first aspect; or, the logic circuit being used to execute the method described in the second aspect and any possibility of the second aspect; or, the logic circuit being used to execute the method described in the third aspect and any possibility of the third aspect; or, the logic circuit being used to execute the method described in the fourth aspect and any possibility of the fourth aspect; or, the logic circuit being used to execute the method described in the fifth aspect and any possibility of the fifth aspect.
[0096] In the thirteenth aspect, a communication system is provided, which includes the communication device described in the sixth aspect or any possibility of the sixth aspect, and / or the communication device described in the seventh aspect or any possibility of the seventh aspect.
[0097] In a possible implementation manner, the communication system also includes the communication device described in the eighth aspect or any possibility of the eighth aspect.
[0098] In a possible implementation manner, the communication system also includes the communication device described in the ninth aspect or any possibility of the ninth aspect.
[0099] In a possible implementation manner, the communication system also includes the communication device described in the tenth aspect or any possibility of the tenth aspect.
[0100] In the fourteenth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect or any possibility of the first aspect is executed; or, the method described in the second aspect and any possibility of the second aspect is executed; or, the method described in the third aspect and any possibility of the third aspect is executed; or, the method described in the fourth aspect and any possibility of the fourth aspect is executed; or, the method described in the fifth aspect and any possibility of the fifth aspect is executed.
[0101] In the fifteenth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect or any possibility of the first aspect to be executed; or, cause the method described in the second aspect and any possibility of the second aspect to be executed; or, cause the method described in the third aspect and any possibility of the third aspect to be executed; or, cause the method described in the fourth aspect and any possibility of the fourth aspect to be executed; or, cause the method described in the fifth aspect and any possibility of the fifth aspect to be executed. BRIEF DESCRIPTION OF THE DRAWINGS
[0102] Figure 1 It is a schematic diagram of the complexity of process design in traditional communication systems.
[0103] Figure 2 It is a schematic diagram of an application scenario of the communication method provided in an embodiment of the present application.
[0104] Figure 3 It is a schematic diagram of the complexity of process design in the communication system provided in the embodiment of the present application.
[0105] Figure 4 It is a schematic diagram of a communication system provided in an embodiment of the present application.
[0106] Figure 5 It is a schematic flowchart of a communication method provided in an embodiment of the present application.
[0107] Figure 6 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0108] Figure 7 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0109] Figure 8 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0110] Fig. 9 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0111] Fig.10 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0112] Fig.11 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0113] Fig.12 It is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0114] Fig.13 It is a schematic structural block diagram of a communication device provided in an embodiment of the present application.
[0115] Fig.14 It is a schematic structural block diagram of another communication device provided in an embodiment of the present application.
[0116] Fig.15 It is a schematic structural block diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0117] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system, sixth generation (6G) system or new radio (NR), as well as future communication systems.
[0118] As an example and not a limitation, in the embodiments of the present application, the terminal device in the embodiments of the present application may refer to user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device may also be a subscriber unit, a terminal device station, a terminal device agent, a terminal device device, or a terminal in V2X communication. The terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, a terminal in a 6G network, or a terminal in a future evolution network, etc., and the embodiments of the present application are not limited to this.
[0119] The terminal device in the embodiments of the present application may also be a mobile phone, a tablet computer, a computer with wireless transceiver function, a holographic projector, a video player, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a tactile terminal device, a vehicle-mounted terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in transportation safety, a wireless terminal in a smart city, and a wireless terminal in a smart home.
[0120] Among them, wearable devices can also be called wearable smart devices, which are a general term for the intelligent design of daily wearables and the development of wearable devices using wearable technology, such as head-mounted extended reality (XR) glasses, gloves, watches, clothing and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also realize powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that focus on a certain type of application functions and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0121] In addition, in the embodiments of the present application, the terminal device may also be a terminal device in an Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.
[0122] In addition, in this application, the terminal device may also include sensors such as smart printers, train detectors, gas stations, etc., and its main functions include collecting data (part of the terminal device), receiving control information and downlink data from the network device, and sending electromagnetic waves to transmit uplink data to the network device.
[0123] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a base transceiver station (BTS) in a global system of mobile communication (GSM) or code division multiple access (CDMA), or a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolutionary node base (eNB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G or 6G network and a future communication system, or a network device in a future evolved PLMN network, etc., may be an access point (AP) in a WLAN, or may be a gNB in a new radio (NR) system, and the embodiment of the present application is not limited. It can be understood that all or part of the functions of the network device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).
[0124] Among them, the functions and specific implementation methods of the terminal devices and network devices listed above are only exemplary descriptions, and the present application is not limited thereto.
[0125] In an embodiment of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call a program and execute a program.
[0126] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.
[0127] Based on the enhanced connectivity of the 5G system, the 6G system adds resources and capabilities in new dimensions such as computing, intelligence, data, and perception. It is no longer a simple pipeline, but provides platform-based service capabilities to achieve the intelligent connection of all things. However, the enhanced evolution based on the existing mobile network protocol system will cause the complexity of system design and implementation to accumulate continuously, which is unsustainable. The main reason is that the existing network architecture relies on the definition of standardized signaling processes. The complexity of the design of the architecture system and signaling processes depends on the number of business scenarios, the number of business processes in each scenario, and the number of network functions involved in each business process.
[0128] Figure 1 A schematic diagram showing the process design in a traditional communication system is shown in FIG. Figure 1 As shown, each NF in the system has different signaling interaction methods in each business process in each scenario. Therefore, the process design scale is: number of scenarios S × number of business flows P × number of network functions F, and the corresponding process design complexity is expressed as O(S·P·F). As the types and number of objects participating in the interaction in the communication system increase, the above traditional end-to-end signaling process customization method will cause problems such as many signaling types, complex logic, long version iteration cycle, and poor scalability. Therefore, how to reduce the complexity of the internal process design of the communication system has become a technical problem that needs to be solved urgently.
[0129] In view of this, the communication system provided in the embodiment of the present application identifies and understands the user's intentions through the network's endogenous intelligent agent, realizes the mapping and orchestration of intentions to scenarios and business flows, thereby driving network functions, intelligent entities, and multimodal terminal devices to ultimately achieve the user's intentions and realize the transformation from a process-driven network to an intent-driven network.
[0130] Figure 2 Schematic diagram of an application scenario that can be applied to the communication method of the embodiment of the present application. Figure 2 As shown, the system is an expressive communication system that is user-centric and drives multimodal information interaction between humans, machines, numbers, and spirits based on the intentions sent by users through terminal devices. It uses the inherent communication, perception, calculation, mathematics, and intelligence capabilities of intelligent agents to translate users' intentions into specific business flows, thereby directly calling or indirectly driving the capabilities of multiple objects to realize users' intentions.
[0131] The “person” mentioned in the above-mentioned communication scenario may refer to the user’s terminal device, for example Figure 2 The mobile phone shown in, or other terminal devices capable of sending user intentions, including but not limited to tablet computers, computers with wireless transceiver functions, smart watches, etc., are not specifically limited in this application.
[0132] The "machine" mentioned in the above-mentioned communication scenario can refer to a machine, that is, a type of terminal device with specific functions or capable of completing specific tasks, such as Figure 2 The XR device or drone shown in, or other terminal devices with specific functions or capable of completing specific tasks, including but not limited to vehicle-mounted terminal devices, wireless terminals in smart homes, terminal devices in Internet of Things systems, etc., are not specifically limited in this application.
[0133] The "number" mentioned in the above-mentioned communication scenario can refer to digital human or digital intelligent human. Digital human or digital intelligent human is a digital virtual image created based on computer graphics (CG) technology and artificial intelligence technology, with human appearance or behavior patterns, capable of intelligent voice interaction, visual recognition, emotional experience, etc. Figure 2 The Digital Homo sapiens clone shown in .
[0134] The “spirit” mentioned in the above-mentioned communication scenario may refer to a type of entity with autonomous or semi-autonomous intelligence. The above-mentioned entity may include physical devices, such as Figure 2 The service robot shown in the figure, or other terminal devices with autonomous or semi-autonomous intelligence, including but not limited to robots or robot dogs, etc.; the above entities may also include virtual entities, such as intelligent agents in the network, which can recognize and understand the intentions and semantics of physical communication objects and / or virtual communication objects, realize efficient interaction and transmission of intentions and semantics between communication objects, and assist in completing task processing.
[0135] In the embodiments of the present application, "object" refers to network devices and / or terminal devices in a communication system that have specific capabilities and participate in specific business processes in specific business scenarios, including but not limited to network functions (NF), management functions (MF), agents, call applications, third-party application functions (AF), and different types of terminal devices. Among them, NF is a type of network device that provides services to terminal devices or other network devices, such as Figure 2 As shown in FIG, the services provided by NF include but are not limited to at least one of the following: connection service, computing service, data service, or perception service. MF is a type of network device that provides management services to terminal devices or other network devices. The management services provided by MF can be Figure 2The cloud network facility management service may also be other control plane functions, such as MF for management and network orchestration (MANO), etc. AF is an application server that provides services to terminal devices or other network devices. The call application is used to provide call services to terminal devices, such as new calls in the Internet protocol (IP) multimedia system (IMS). An intelligent agent is an entity based on artificial intelligence (AI) technology, such as a digital person or digital intelligent person corresponding to the "number" in the aforementioned description, or a virtual entity included in the "spirit" in the aforementioned description. Different types of terminal devices include, but are not limited to, the terminal devices corresponding to the "human", "machine" and "spirit" in the aforementioned description.
[0136] It should be understood that the expression form of "capability" may be different depending on the type of object. For example, for NF or AF, the capability may be the service that NF or AF can provide externally; for terminal equipment or intelligent agent, the capability may be the task that the terminal equipment or intelligent agent can complete; or the capability may also be the internal processing of the object, such as the setting of MF parameters, etc. This application does not specifically limit the expression form of the object's capability.
[0137] For "capabilities" in different forms, there are also different forms of "capability calling methods". The "capability calling method" mentioned in the embodiments of this application can be any method that can use the services provided by the object or control the object to complete a task, including but not limited to the object's application programming interface (API), the object's control instructions, the object's parameter configuration rules, the object's intention or semantic interface, etc. The embodiments of this application do not specifically limit the form of the capability calling method.
[0138] The "intention" mentioned in the embodiments of the present application refers to the expected result of the target object. Intent includes but is not limited to the following information: intention expectation, intention object, intention target, intention context, etc. Intent expectation refers to the business scenario targeted by the intention, such as entrusting a digital human to act as an agent for the user to perform tasks, intelligently driving terminal devices, expanding the computing power of terminal devices, and forming a virtual network for a machine group; the intention object refers to the target object targeted by the intention, such as terminal devices, base stations, virtual private networks, call applications, computing services, third-party applications, etc.; the intention target refers to the target value that the performance indicator needs to achieve, such as throughput, latency, switching success rate, etc.; the intention context refers to the constraints on the intention expressed through relationships such as comparison, inclusion, and association, such as the duration of the intention, the priority of the intention, etc. The description form of the intention includes but is not limited to natural language, formatted intention expression model, etc., and this application does not make specific restrictions on this.
[0139] The "business flow" mentioned in the embodiments of the present application refers to the specific information exchange process between the intelligent agent and the object and / or multiple objects required to complete a specific business in a specific business scenario, that is, the specific implementation method of the intention. Depending on the type of information recipient and the degree of autonomous intelligence, the interactive information may include specific signaling, task scheduling strategies, and intentions.
[0140] Figure 3 A schematic diagram of a process design in a communication system provided in an embodiment of the present application is shown. Figure 3 As shown, an intelligent agent is introduced into the communication system provided in the embodiment of the present application. The intelligent agent and the terminal device have a unified intentional interface, and the information that can express the intention, such as semantics and data flow, is interacted with. The intelligent agent translates the intention into the corresponding scenario and business flow, so that the terminal device only needs to express the intention without knowing how to implement the scenario and business flow corresponding to each intention, thereby reducing the learning cost of the terminal device to use the network. On this basis, NF uses service interface so that the intelligent agent and each NF only need to define how the NF's capabilities are called. Since the NF's capability calling method is independent of the specific scenario or business flow, the process design scale is: the number of network functions F, and the corresponding process design complexity is expressed as O(F). Compared with the traditional communication system, the process design complexity is significantly reduced.
[0141] Combine the following Figure 4 The communication system 400 provided in the embodiment of the present application is specifically introduced. Figure 4As shown, system 400 includes network element 410, which can be a network intelligent agent function (NIAF). NIAF is an implementation of the intelligent agent mentioned above, which is used to receive and identify intentions from terminal devices (such as intelligent terminal devices) (or, intentions sent by terminal devices through access networks (AN)), and translate the intentions into specific information interaction methods, thereby directly calling or indirectly driving the capabilities of various objects to ultimately achieve the intentions sent by users through terminal devices. As mentioned above, these objects include but are not limited to other NFs or MFs, intelligent entities (such as digital humans), call applications (such as IMS new calls), third-party AFs, and different types of terminal devices.
[0142] The network element 410 can also map the intent to an information interaction method based on the local intent knowledge base. The network element 410 can also have an interaction interface, which can be used to receive intents, can also be used for interaction of other types of information, and can also be used to forward intents or sub-intents of intents to other devices. It should be understood that the above-mentioned composition and workflow of the network element 410 are only an example, and this application does not specifically limit the internal design of the network element 410.
[0143] Optionally, the communication system 400 may further include a network element 440, which may be an intelligent session management function (ISMF). Various types of terminal devices, including but not limited to mobile phones, XR glasses, IoT terminals, drones, robot dogs, robots, etc., may establish a session with the network element 410 through the network element 440. In an embodiment of the present application, the session established between the NIAF and the terminal device may be referred to as an intelligent session. The intelligent session is used to implement the intention interaction between the terminal device and the network element 410, and / or to implement the information interaction between the network element 410 and the terminal device required to achieve the intention, including but not limited to the semantic information sent by the terminal device to the network element 410 to express the intention, the intention sent by the network element 410 to the intelligent terminal device that can recognize and implement the intention, the specific signaling used by the network element 410 to control the terminal device, and the multimodal data (such as sensor data, image data, audio and video data, etc.) received or collected by the network element 410 from the terminal device. The terminal device can be addressed to network element 440 through other network elements (such as access and mobility management function (AMF) network element), or can be directly connected to network element 440, and this application does not make specific limitations on this.
[0144] Optionally, the communication system 400 may further include a network element 420 and / or a network element 430, wherein the network element 420 may be a registration function (RF) and the network element 430 may be an intent knowledge base (IKB). The network element 410 may rely on the network element 420 and the network element 430 to achieve accurate identification and translation of intents. The network element 420 is used to record the capability templates of various objects, that is, which callable capabilities each object provides and the calling method of the capabilities. In other words, the object registers the capability template with the network element 420. The capability template registered by the object with the network element 420 determines the type and scope of intent that the communication system 400 can achieve, and the intent that exceeds the capability template cannot be achieved. The network element 430 learns the intent that the communication system 400 can achieve by obtaining the capability template information, and maps it to the business process or task orchestration strategy that drives the capability object. When network element 410 receives a new intent, if it cannot process it, it can forward the intent to network element 430 for identification to obtain a translation result, and use the translation result as knowledge to update the local intent knowledge base, thereby accelerating the subsequent translation of the same or similar intent.
[0145] It should be understood that the above NIAF, RF, IKB and ISMF can be independent network elements in the communication system, or can be integrated into other network elements as functional modules. For example, RF, IKB and / or ISMF can be respectively used as functional modules inside the network element 410, so that the network element 410 has the NIAF function, and also has the functions of registering capability templates, learning intent knowledge and / or establishing intelligent sessions.
[0146] As mentioned above, depending on the type of information recipient and the degree of autonomous intelligence, the interactive information may include specific signaling, task scheduling strategies, and intents. In other words, the result of the intelligent agent translating the intent may include business processes and / or task scheduling strategies and / or sub-intents. For example, if the object involved in the intent is a non-intelligent terminal device, NF, AF or call application, etc., the intelligent agent can translate the intent into a specific business process. In this case, the intelligent agent can send specific signaling based on various protocols to the object, such as signaling interaction with NF based on service-based architecture (SBA), signaling interaction with IMS new calls based on session initialization protocol (SIP), and signaling interaction with AF based on hypertext transfer protocol (HTTP). For another example, if the object involved in the intent is a terminal device, NF, MF or AF with a certain degree of autonomous intelligence, which can autonomously determine the complete task execution process according to a specific task scheduling strategy, then the intelligent agent can translate the intent into a task scheduling strategy. In this case, the intelligent agent only sends the task scheduling strategy to the object without specifying specific signaling interactions, and the object determines the specific implementation process according to the task scheduling strategy to complete the task. For another example, if the object involved in the intent is a terminal device, digital intelligent person or other NIAF with higher-level intelligence, which has the ability to understand and implement the intent, then the intelligent agent can translate the intent into sub-intentions. In this case, the intelligent agent decomposes the intent into sub-intentions and assigns them to the object, which then performs further processing based on the sub-intentions to achieve the overall intent. It should be understood that in actual application scenarios, the result of the intelligent agent's intent translation may be a combination of the above-mentioned methods.
[0147] Combine the following Figures 5 to 12 The communication method provided by the above-mentioned communication system is specifically introduced in the embodiment of the present application. Figure 5 FIG. 5 is a schematic flow chart of a communication method 500 provided in an embodiment of the present application. Optionally, Figure 5 The method shown can be applied to Figure 4 A communication system 400 is shown.
[0148] In this embodiment, the network element and the terminal device are used as the execution subject of the interaction to illustrate the method, but the present application does not limit the execution subject of the interaction. Figure 5 The network element in the method may also be a chip, a chip system, or a processor that supports the method that can be implemented by the network element, or a logic module or software that can implement all or part of the network element functions; Figure 5The terminal device in the invention may also be a chip, a chip system or a processor that supports the method that can be implemented by the terminal device, or a logic module or software that can implement all or part of the functions of the terminal device.
[0149] It should be understood that the specific type of the terminal device is not limited in the embodiments of the present application. For example, the terminal device may be a UE or other types of terminal devices, and the present application does not make specific limitations on this.
[0150] like Figure 5 As shown, the method includes the following steps.
[0151] Step S510: The terminal device sends first information to the first network element. Correspondingly, the first network element receives the first information from the terminal device.
[0152] The first network element may be a NIAF, for example Figure 4 NIAF 410 shown in . Specifically, the first information is used to describe the intent, so the first information can also be called an intent description. The intent description can be a natural language description, such as text or voice of a natural language, or a formatted intent expression model, such as the intent expression model defined by the intent driven management service (intent driven management service, IDMS) of the management standard working group SA5 of the 3rd generation partnership project (3GPP).
[0153] The first information may be included in an intent request message sent by the terminal device to the first network element, and the intent request message is used to request the implementation of the intent described by the first information. Optionally, the intent request message may also include other information, such as a UE identity (ID), which is used to enable the first network element or other entities in the system to determine the identity of the terminal device sending the information.
[0154] Optionally, the intent request message may also carry attachments, including but not limited to pictures, text, voice, video, binary code files, application (APP) installation packages, etc., to expand or supplement the content described in the intent.
[0155] Optionally, the first network element and the terminal device may interact multiple times to confirm the specific intention of the terminal device. For example, the first network element may request the terminal device to supplement the detailed information of the intention description, or the first network element may send the identified intention to the terminal device to confirm whether the identification is correct. The above attachments may also be provided during multiple confirmation interactions of the intention.
[0156] After step S510, the first network element can obtain an information interaction method between the first network element and at least one object, and the information interaction method is used to implement the intention described by the above-mentioned first information. Optionally, the above-mentioned information interaction method can be determined by the first network element, or it can be obtained by the first network element from other network elements. Among them, the situation where the information interaction method is determined by the first network element can correspond to the following steps S520 and S530, and the situation where the information interaction method is obtained from other network elements can correspond to the following steps S540 to S570. That is, steps S520 to S570 described below can be selectively executed, for example, steps S520 and S530 can be executed, or steps S540 to S570 can also be executed. The two situations are described in detail below.
[0157] In some possible implementations, the information interaction method may be determined by the first network element, specifically corresponding to steps S520 and S530.
[0158] Step S520: The first network element obtains the capability and capability calling method of at least one object.
[0159] Specifically, the at least one object is an object related to realizing the above intention. For example, the first network element can determine which objects and capabilities in the communication system need to be scheduled to realize the intention based on the local intention knowledge base and the intention described in the first information. These objects determined to need to be scheduled are called objects. Among them, objects include but are not limited to NF, MF, AF, call application, intelligent agent, terminal device, etc.
[0160] The local intent knowledge base can be implemented in many ways, including but not limited to a mapping table between intent and object capabilities, a knowledge graph representing the relationship between intent and object capabilities, or a neural network model whose input is an intent description and whose output is the object capabilities. As an example, the first network element can save the capabilities of the object corresponding to each intent as a mapping table, and then determine the object required to implement the above intent based on the first information by looking up the table. For another example, the first network element can construct a knowledge graph based on different intents and the capabilities of different objects, and then use the knowledge graph to infer objects that have a relationship with the above intent based on the first information. For another example, the first network element can use known intents and the capabilities of the corresponding objects as training data to train a neural network model, so that the above intent is used as the input data of the neural network model based on the first information, and the object is determined based on the output data of the neural network model. It should be understood that the local intent knowledge base can also be implemented in other ways, and the embodiment of the present application does not specifically limit the way in which the first network element translates intent.
[0161] After determining at least one object, the first network element can query the capability and capability calling method corresponding to each object from the RF. Specifically, step S520 may include the following steps S521 and S522.
[0162] Step S521: The first network element sends a first message to the second network element. Correspondingly, the second network element receives the first message from the first network element.
[0163] The second network element may be a RF, for example Figure 4 RF 420 shown in . Specifically, the first message is used to request the capability and capability calling method of at least one object, and the capability of the at least one object is related to the intention described by the first information, so the first message can also be called a first capability query request message.
[0164] The first network element may send the above-mentioned first message to the second network element based on at least one determined object. The first message may include the identifier of the object, so that the second network element can query the capabilities of the object and the method for calling the capabilities. The first message may also include a UE ID. Specifically, the second network element may store a capability template for each object that has registered its capabilities with the second network element. The capability template includes at least the identifier of the object and the corresponding capabilities of each object and the method for calling each capability. Therefore, the second network element can query the capability template of at least one object based on the identifier of at least one object in the first message, thereby determining the capabilities of the at least one object and the corresponding calling method. Among them, the identifier of the above-mentioned object can be, for example, the name of the object or the ID of the object, etc., and this application does not make specific limitations on this.
[0165] Step S522: The second network element sends the capability and capability calling method of at least one object to the first network element. Correspondingly, the first network element receives the capability and capability calling method of at least one object from the second network element.
[0166] For example, the second network element may send a first capability query response message to the first network element in response to the first capability query request message. The first capability query response message may include the UE ID and the capability of each object in the at least one object and the corresponding capability calling method, thereby feeding back the query result to the first network element.
[0167] It should be understood that the above steps S521 and S522 are only examples of the case where NIAF and RF interact as two independent network elements, but the implementation of step S520 is not limited to this. For example, a function registration module may also be integrated in the first network element to store the capability template of the object locally. In this case, the capability and capability calling method of at least one object may be obtained by the first network element from a local query. For another example, the capability and capability calling method of at least one object may also be obtained by the first network element directly requesting at least one object. This application does not make specific limitations on this.
[0168] Step S530: The first network element determines an information interaction method.
[0169] For example, the first network element determines an information interaction method between the first network element and at least one object according to the capability and capability calling method of at least one object, where the information interaction method enables the capability of the at least one object to be called to achieve the above intention.
[0170] It should be understood that the information interaction method between the first network element and the at least one object may include: an information interaction method between the first network element and each object of at least part of the at least one object, and / or an information interaction method between at least two objects of the at least one object.
[0171] The above process only requires interaction between the first network element and the second network element to translate the intent description into an information interaction process that can realize the intent, thereby improving the efficiency of intent translation.
[0172] In other possible implementations, if the first network element cannot correctly translate the user's intent through the built-in local intent knowledge base, it can send an intent translation request message to the IKB, forward the intent description and corresponding attachments to the IKB, so that the IKB can perform intent recognition and translation, which specifically corresponds to steps S540, S550, S560 and S570.
[0173] Step S540: The first network element sends the second information to the third network element. Correspondingly, the third network element receives the second information from the first network element.
[0174] The third network element may be an IKB, for example Figure 4 IKB 430 shown in . Specifically, the second information is used to describe the intent described by the aforementioned first information. The description form of the second information may be the same as the first information, or may be different from the first information, such as converting a natural language description into an intent expression model, which is not specifically limited in this application. The second information may be included in an intent translation request message sent by the first network element to the third network element, and the intent translation request message is used to request the third network element to translate the intent described by the second information. Optionally, the intent request message may also include other information, such as UE ID, attachments corresponding to the intent description, etc.
[0175] Step S550: The third network element obtains the capability and capability calling method of at least one object.
[0176] For example, the third network element can determine at least one object related to realizing the intention described by the second information based on the second information. The specific implementation method can refer to the first network element determining the relevant description of the object based on the local intention knowledge base in S520, including but not limited to through a mapping table, a knowledge graph, a neural network model, etc., and this application does not make specific limitations on this.
[0177] After the third network element determines the at least one object, it may execute steps S551 and S552 to obtain the capability and capability calling method of the at least one object from the second network element, as follows.
[0178] Step S551: The third network element sends a third message to the second network element. Correspondingly, the second network element receives the third message from the third network element.
[0179] Specifically, the third message is used to request the capability and capability calling method of at least one object, and the capability of the at least one object is related to the intention described by the second information, so the third message can also be called a second capability query request message. The third message may include an identifier of the object, so that the second network element can query the capability of the object and the capability calling method, and the third message may also include a UE ID.
[0180] Step S552: The second network element sends the capability and capability calling method of at least one object to the third network element. Correspondingly, the third network element receives the capability and capability calling method of at least one object from the second network element.
[0181] For example, the second network element may send a second capability query response message to the third network element in response to the second capability query request message. The second capability query response message may include the capability of each object in the at least one object and the corresponding capability call method, thereby feeding back the query result to the first network element. Optionally, the second capability query response message includes the UE ID.
[0182] It should be understood that step S551 and step S552 are only one implementation method of step S550, and the third network element can also obtain the capability and capability calling method of at least one object in other ways, and this application does not make specific limitations on this.
[0183] Step S560: The third network element determines an information interaction method.
[0184] For example, the third network element determines an information interaction method between the first network element and at least one object according to the capability and capability calling method of at least one object, and the information interaction method enables the capability of the at least one object to be called to achieve the above intention.
[0185] Optionally, the specific process implemented by the third network element and the second network element in the above steps S550 and S560 may be similar to the process implemented by the first network element and the second network element in the above steps S520 and S530. Please refer to the description of the corresponding related content and will not be repeated here.
[0186] Step S570: The third network element sends the third information to the first network element. Correspondingly, the first network element receives the third information from the third network element.
[0187] Specifically, the third information is used to indicate the information interaction method determined by the third network element. The third information may be included in the intent translation response message sent by the third network element to the first network element in response to the intent translation request message, thereby feeding back the intent translation result to the first network element.
[0188] The above process enables the first network element to directly obtain the information interaction method returned by the third network element, thereby saving the computing power of the first network element, and using the saved computing power to execute other tasks of the first network element, thereby improving the overall working efficiency of the communication system.
[0189] In addition, the third network element can perform a more advanced intent translation relative to the local intent knowledge base of the first network element, that is, the third network element can perform a more comprehensive and accurate translation relative to the local intent knowledge base of the first network element, thereby improving the success rate of intent execution. "More advanced" may be due to the fact that the third network element adopts a more accurate translation method than the local intent knowledge base of the first network element. For example, the local intent knowledge base adopts a relatively simple mapping table method for the purpose of saving computing power, that is, the correspondence between some known intents and the capabilities of the object is saved as a mapping table for table lookup translation, while the third network element adopts a neural network model with a relatively complex algorithm, so the third network element can complete some translations that the local intent knowledge base cannot complete. The third network element and the local intent knowledge base can adopt the same translation method. In this case, "more advanced" may be due to the fact that the third network element has more and more comprehensive sample data for learning relative to the local intent knowledge base. For example, the third network element can use the capabilities of all registered objects in the RF as sample data for learning, while the local intent knowledge base may only use the intents and capabilities of the objects acquired in the actual business as learning samples for the purpose of saving storage space, so the third network element can complete some translations that the local intent knowledge base cannot complete. Or it may be other situations, such as a combination of the above two situations, which is not specifically limited in this application.
[0190] Optionally, the above steps S520 and S530 can be used in combination with steps S540 to S570 in part or in whole, and the order of each step can be exchanged. For example, after step S510, steps S540 to S570 can be performed first, but the intention translation response message sent by the third network element to the first network element may not include the specific method of information interaction, but only include the strategy of information interaction, such as which capabilities of which objects need to be called and the calling order of each object capability. In this case, after steps S540 to S570, the first network element can also perform steps S520 and S530, and query the second network element for the calling method of the object capability involved according to the information interaction strategy fed back by the third network element, so as to determine the specific method of information interaction. For another example, since the intention translation response message in the above example may not include the specific method of information interaction, the third network element may not obtain the object capability calling method. In this case, only steps S540, S570, S520 and S530 may be performed, and this application does not make specific limitations on this.
[0191] Optionally, when the first network element requests the third network element to assist in the intended translation, that is, when at least step S570 is executed, the method 500 may further include the following step S580.
[0192] S580: The first network element updates the local intent knowledge base.
[0193] For example, the first network element may update the local intent knowledge base in the first network element according to the intent described by the first information and the information interaction method included in the intent translation response message returned by the third network element. For example, the first network element may learn the intent of this time and at least one object determined by the third network element as a set of sample data. For example, if the local intent knowledge base adopts the implementation method of a mapping table, the first intent and at least one corresponding object may be added to the mapping table; if the local intent knowledge base adopts the implementation method of a knowledge graph, if there is no node corresponding to the first intent and / or at least one object in the graph, the corresponding node may be added to the graph, and the relationship between the nodes corresponding to the first intent and at least one object may be added; if the local intent knowledge base adopts the implementation method of a neural network model, the first intent and at least one corresponding object may be used as a set of new training data for training the neural network model, thereby updating the parameters of the model. The local intent knowledge base may also adopt other methods to learn sample data, and this application does not make specific limitations on this.
[0194] Through the above solution, NIAF can continuously learn based on the data generated during the actual work process, so as to automatically adapt to new intents and / or new objects, without the need to upgrade interfaces and processes, and improve the business scenarios and accuracy that intent translation can cover. In addition, after updating the local knowledge base, NIAF can directly translate the same or similar intents encountered in subsequent work without the help of IKB, thereby improving the efficiency of intent translation.
[0195] After obtaining the information interaction method between the first network element and at least one object through the above steps, the first network element can execute the following step S590.
[0196] Step S590: The first network element calls the capability of at least one object according to the information interaction method.
[0197] As described above, the information interaction between the first network element and at least one object includes: information interaction between the first network element and each object in at least part of the at least one object, and / or information interaction between at least two objects in at least one object. Therefore, in step S590, the first network element can directly schedule the object or indirectly drive the object. Direct scheduling refers to sending information directly to the object, thereby scheduling it to implement the corresponding capabilities; indirect driving refers to sending information to other objects, so that other objects then send information to the object to drive it to implement the corresponding capabilities.
[0198] As mentioned above, the first network element can translate the first intent into a business process and / or a task scheduling strategy and / or a sub-intent for processing. Therefore, the way in which the first network element calls the capability of at least one object includes but is not limited to: sending specific signaling to at least part of the at least one object, sending a task scheduling strategy to at least part of the at least one object, and / or sending a sub-intent to at least part of the at least one object. For example, the first network element can interact with the corresponding NF, AF, other terminal devices, or interact with digital people, other NIAFs for sub-intents, etc., and the present application does not make specific limitations on this. For example, the first network element can send fourth information to at least part of the at least one object, and the fourth information is used to describe the sub-intent of the intent, so that the intent with a complex implementation process can be decomposed into multiple sub-intents with relatively simple implementation processes, and multiple objects that can process the intent can translate in parallel, thereby improving the overall intent translation efficiency of the communication system.
[0199] It should be understood that in the embodiments of the present application, "the information interaction method is used to achieve the intention" means that the purpose of determining the information interaction method is to achieve the above intention, but it does not limit the ultimately determined information interaction method to be able to achieve the intention.
[0200] Through the above method 500, a new network element NIAF is introduced into the network, so that only the interface from NIAF to each functional entity needs to be defined inside the network, and the scenarios and business processes are automatically generated by NIAF, thereby reducing the complexity of internal process design. In addition, the terminal device and NIAF interact through the intentional interface, and NIAF translates the intention of the terminal device into the business process inside the network, thereby reducing the learning cost of the terminal using the network.
[0201] Optionally, for the above method 500, after step S590, NIAF may feed back the implementation result of the intent to the terminal device. For example, the first network element may send the fifth information to the terminal device, and the terminal device receives the fifth information from the first network element accordingly. The fifth information is used to indicate the implementation result of the intent described by the first information. The fifth information may be included in the intent response message sent by the first network element to the terminal device in response to the intent request message. The intent response message may include, for example, whether the intent is successfully implemented, the quantitative implementation effect (for example, the percentage of the expected value), the reason for the unsuccessful implementation part, etc. The intent response message may also include an attachment object for further supplementary explanation of the intent implementation result, including but not limited to text, pictures, videos, etc. Optionally, the above feedback step may be repeated. For example, the first network element may feed back the execution progress of the intent to the terminal device at any time during the intent implementation process in the form of event notifications, etc. This enables the terminal device to obtain feedback on the intent in a timely manner and improve the user experience.
[0202] Below through Figures 6 to 10 , the application of the above method 500 in different scenarios is introduced through five specific embodiments.
[0203] Example 1: The business scenario is that the user entrusts the digital human with the task of making and receiving phone calls through NIAF. The specific process is as follows: Figure 6 Method 600 is shown.
[0204] Optionally, before method 600 starts, the IMS call service sends an incoming call notification to the UE.
[0205] S601: UE sends an intent request message to NIAF.
[0206] For example, a user sends an intent request message to NIAF through the UE, and the content of the intent description in the intent request message can be "entrust a digital person to act as a proxy user to answer the phone." The intent description can also include a strategy for answering the call. For example, if it is a courier, prompt the courier to leave the courier at the door. If it is an educational institution that has been contacted before, write down the key information and notify the UE by text message, etc. If the above-mentioned policy information for answering the call is relatively large, it can also be provided as an attachment included in the intent request message in the form of text or the like. Optionally, the intent description can also include entrusting a digital person to act as a proxy user to make external calls. In this case, the time when the intent takes effect can be constrained by the intent context, such as making external calls according to the strategy at a specific time. This will not be described in detail in this embodiment.
[0207] S602: NIAF sends a capability query request message to RF.
[0208] For example, after receiving the intent request message, NIAF recognizes that the intent requires the digital human and the IMS call service to complete the task together, and therefore sends a capability query request message to RF to obtain the capabilities and capability calling methods of the digital human and the IMS call service. Optionally, if NIAF cannot recognize or translate the intent, the intent may also be sent to IKB for recognition and / or translation. For the specific process, reference may be made to the description of the relevant steps in the aforementioned method 500, which will not be repeated here.
[0209] S603: RF sends a capability query response message to NIAF.
[0210] For example, in response to a capability query request message, the RF queries the capability templates of objects whose object names are "digital human" and "IMS call service" in the capability templates of objects whose capabilities have been registered, thereby obtaining the respective capabilities of the digital human and the IMS call service and the corresponding calling methods for each capability, and returns the required capabilities and capability calling methods to the NIAF.
[0211] S604: NIAF determines the information exchange method.
[0212] For example, NIAF translates user intent into corresponding business processes based on the capabilities of digital humans and IMS call services, including sub-intention interactions between NIAF and digital humans and information interactions between NIAF and IMS call services.
[0213] S605: Sub-intention interaction between NIAF and digital human.
[0214] For example, S605a: NIAF sends a sub-intent request message to the digital human according to the business process, notifying the digital human of the response strategy for answering the phone; S605b: The digital human sends a sub-intent response message to NIAF, feeding back the recognition result of the sub-intent.
[0215] S606: Information interaction between NIAF and IMS call service.
[0216] For example, S606a: NIAF sends an IMS call forwarding request message to the IMS call service according to the business process to configure the IMS call service so that the IMS transfers specific incoming calls from the UE to the digital human; S606b: The IMS call service sends an IMS call forwarding response message to NIAF to feedback the configuration result of the IMS call service.
[0217] S607: NIAF sends an intent response message to the UE.
[0218] For example, the NIAF sends an intent response message to the UE to feedback the intent achievement result.
[0219] S608: Digital human and IMS call service make and receive calls according to the UE's intention.
[0220] For example, the IMS call service transfers a specific incoming call to a digital person, who answers the specific incoming call and responds on behalf of the user according to the response strategy expressed by the intent.
[0221] In the above embodiment, the UE only needs to send an intent to the NIAF, and the NIAF automatically translates the intent into a corresponding business process to implement the UE's intent, thereby simplifying the interface for interaction between the UE and the network, and eliminating the need to add new business process design and development.
[0222] Embodiment 2: The business scenario is that NIAF receives the intention of UE and drives multiple terminal devices to complete the task objectives to realize the intention, so that the terminal devices are intelligent enough to perceive the user's intention. The specific process is as follows: Figure 7 Method 700 is shown.
[0223] Optionally, terminal device 1 (e.g., smart electric car) and terminal device 2 (e.g., home control center) establish smart sessions with different NIAFs. For example, before method 700 starts, terminal device 1 located in city 1 may have established a smart session with NIAF 1, and terminal device 2 located in city 2 may have established a smart session with NIAF 2.
[0224] S701: UE sends an intent request message to NIAF 1.
[0225] For example, the user sends an intent request message to NIAF 1 through the UE. The intent description in the intent request message may be "drive back to city 2 at 2 pm, and hope that the temperature on the way and in the car and indoors is 26 degrees when arriving home".
[0226] S702: NIAF 1 recognition intent requires at least one terminal device to complete.
[0227] For example, after receiving the intent request message, NIAF 1 determines based on the local intent knowledge base that the intent requires terminal device 1 and terminal device 2 to complete the task together.
[0228] S703: Information exchange between NIAF 1 and RF.
[0229] For example, S703a: NIAF 1 sends a capability query request message to RF to obtain the capabilities of terminal device 1 and terminal device 2, the capability calling method, and the binding information between the terminal device and NIAF. It should be understood that the terminal device is different from other types of objects such as NF, AF or digital human. The terminal device needs to exchange information with other entities in the network through the NIAF that has established an intelligent session. Therefore, in order to be able to call the terminal device capabilities, it is also necessary to query which NIAF the terminal device has established an intelligent session with. S703b: RF sends a capability query response message to NIAF 1 and returns the query result to NIAF 1.
[0230] S704: NIAF 1 translates intent into business processes or task scheduling.
[0231] For example, NIAF 1 translates the user intent into the corresponding business process or task scheduling strategy based on the capabilities of terminal device 1 and terminal device 2. Among them, since NIAF 1 can determine that there is an intelligent session binding relationship between terminal device 2 and NIAF 2 based on the capability query result of terminal device 2, the translation result of NIAF 1 on the intent is divided into two parts, one part is the information interaction process of NIAF 1 to terminal device 1, and the other part is the sub-intention of controlling terminal device 2 transferred by NIAF 1 to NIAF 2, so as to request NIAF 2 to realize the final control and information interaction process of terminal device 2.
[0232] S705: NIAF 1 sends a sub-intent request message to NIAF 2.
[0233] For example, based on the intent description in the intent request message and the user's location information, NIAF1 can determine that the user arrives at home in city 2 at about 17:00. Therefore, the content of the intent description of the sub-intent can be "The user arrives home at about 17:00 and hopes that the indoor temperature will be controlled at 26 degrees."
[0234] S706: Information interaction between NIAF 1 and terminal device 1.
[0235] For example, NIAF 1 implements control and information interaction of terminal device 1 based on the intention translation result and the obtained capability information of terminal device 1. For example, NIAF 1 uses the air-conditioning control application programming interface (API) of terminal device 1 to control terminal device 1 to turn on the air-conditioning in the car and set the temperature to 26 degrees at 13:50 (that is, 10 minutes before the user's expected driving time expressed by the intention).
[0236] S707: Information exchange between NIAF 2 and RF.
[0237] For example, S707a: After NIAF 2 receives the sub-intent request message, it recognizes that the sub-intent needs to control the terminal device 2 to complete the task, so NIAF 2 sends a capability query request message to RF to obtain the capabilities and capability calling methods of the terminal device 2. S707b: RF sends a capability query response message to NIAF 2 and returns the query results to NIAF 2, such as whether the terminal device 2 has the temperature control capability and the remote API calling method.
[0238] S708: NIAF 2 translates the sub-intent into a business process or task scheduling.
[0239] For example, NIAF 2 translates the sub-intent into a corresponding business process or task scheduling strategy based on the capabilities of the terminal device 2.
[0240] S709: Information interaction between NIAF 2 and terminal device 2.
[0241] For example, NIAF 2 implements control and information interaction with terminal device 2 based on the sub-intention translation result and the obtained capability information of terminal device 2. For example, NIAF 2 calls the API of terminal device 2 to control the air conditioner at home to turn on the air conditioner in the car and set the temperature to 26 degrees at 16:45 (i.e., 15 minutes before the user's expected arrival time expressed by the sub-intention). Alternatively, NIAF 2 can also translate the sub-intention into a task scheduling strategy. For example, NIAF 2 only sends information to terminal device 2 to set the indoor temperature at 17 o'clock to 26 degrees. Terminal device 2 determines which smart devices in the home need to be scheduled and how to schedule them according to the above task scheduling strategy, which will not be described in detail in this embodiment.
[0242] S710: NIAF 2 sends a sub-intent response message to NIAF 1.
[0243] For example, NIAF 2 sends a sub-intent response message to NIAF 1, reporting that the sub-intent has been successfully executed.
[0244] S711: NIAF 1 sends an intent response message to the UE.
[0245] For example, NIAF 1 sends an intent response message to the UE, and feedback indicates that the intent has been scheduled.
[0246] It should be understood that the information exchange between NIAF 1 and terminal device 1, between NIAF 2 and terminal device 2, and between NIAF1 and NIAF 2 in the above process is sustainable, and the execution status of the intent or sub-intent can be fed back to the UE at any time in the form of event notifications, etc. For example, NIAF 1 and NIAF 2 can always monitor the execution status of the tasks of terminal device 1 and terminal device 2, such as the change of the current air-conditioning temperature value and whether the air-conditioning is faulty.
[0247] In the above embodiment, the UE expresses to the NIAF the intention that multiple terminal devices need to collaborate to complete the task, and the NIAF automatically translates the intention into the corresponding business process or task scheduling. According to the terminal device capability calling method provided in the registered capability template, multiple NIAFs drive multiple terminal devices to collaborate to realize the intention. Each NIAF interacts with the terminal device through an intentional interface, and multiple NIAFs collaborate to complete the task in the form of interactive sub-intentions, which simplifies the interface for interaction between NIAFs and does not require the design and development of new business processes.
[0248] Example 3: The business scenario is that NIAF receives the intention of UE and implements the establishment of a virtual network for a group of machine devices. The specific process is as follows Figure 8 Method 800 is shown.
[0249] Optionally, the “machine” or “machine device” mentioned in this embodiment is a type of terminal device, so before the method 800 starts, multiple machine devices have registered with the network and established intelligent sessions with the NIAF.
[0250] S801: UE sends an intent request message to NIAF.
[0251] For example, a user sends an intent request message to NIAF through a UE, and the intent description in the intent request message may be "to establish a virtual local area network (LAN) for specified machine members." Optionally, a list of specific machine members participating in the networking may be provided in text as an attachment included in the intent request message.
[0252] S802: NIAF identification intent requires control plane functions related to virtual networks (VN) to be completed.
[0253] S803: Information exchange between NIAF and RF.
[0254] For example, S803a: NIAF sends a first capability query request message to RF to obtain the capability template of each machine participating in the networking. S803b: RF sends a first capability query response message to NIAF, including but not limited to the capabilities of each machine, the capability calling method and the binding information with NIAF. S803c: NIAF sends a second capability query request message to RF to obtain the capability template of the NF related to the VN. S803d: RF sends a second capability query response message to NIAF, including but not limited to the capabilities of the VN-related control plane (VN control plane, VN-CP) and the capability calling method.
[0255] S804: NIAF translates intent into business processes or task scheduling.
[0256] S805: NIAF sends a VN establishment request message to VN-CP.
[0257] For example, NIAF sends a VN establishment request message to VN-CP based on the calling method for creating VN provided in the obtained VN-CP capability template. The VN establishment request message may include an ID list of machine members that need to be interconnected through VN.
[0258] S806: The VN-CP creates a VN, triggers the specified machine device to establish a session to the user plane function (UPF) network element and access the VN.
[0259] For example, VN-CP initiates the VN creation process, creates a VN member group including all machines on the user data management function (such as unified data management (UDM)), creates a virtual LAN (such as 5G LAN) exchange instance on UPF, and triggers all machines to establish sessions to UPF and access the created virtual LAN instance. All processes involved in this step can refer to existing standards, such as the standardized process defined by 3GPP 5G LAN, and this embodiment does not specifically limit this.
[0260] S807: VN-CP sends a VN establishment response message to NIAF.
[0261] For example, after the VN-CP creates the virtual LAN, it feeds back the result of the VN establishment through a VN establishment response message.
[0262] S808: NIAF sends an intent response message to the UE.
[0263] For example, NIAF sends an intent response message to the UE to feedback the intent execution result, such as successful creation of VNs for multiple target machines.
[0264] In the above embodiment, the UE expresses to NIAF the intention to form a virtual network for a group of machine devices, and NIAF automatically translates the intention into the corresponding business process to drive the control plane and / or user plane functions to create a virtual network for a specified group of machines, and enables the machines to access the virtual network to complete mutual communication. This enriches the types of objects that NIAF can drive, and does not require the design and development of new business processes.
[0265] Embodiment 4: The business scenario is that NIAF receives the intention of UE, drives the network to select and deploy task execution nodes, enables UE computing tasks to be offloaded to the network for execution, and realizes the effect of expanding UE computing capabilities. The specific process is as follows: Fig. 9 Method 900 is shown.
[0266] S901: UE sends an intent request message to NIAF.
[0267] For example, a user sends an intent request message to NIAF through UE, and the intent description in the intent request message may be "terminal computing task offloading". Optionally, the image package or download address of the code of the computing task to be offloaded may be provided as an attachment included in the intent request message.
[0268] S902: Information exchange between NIAF and RF.
[0269] For example, after receiving the intent request message, NIAF recognizes that the intent requires the computing network collaboration network function and the network function related to the computing service to complete the task together. Therefore, S902a: NIAF sends a capability query request message to RF to obtain the capability template of computing network collaboration and find the capability template of NF related to the computing service. S902b: RF sends a first capability query response message to NIAF, including but not limited to the capabilities of computing network collaboration and computing management and the capability calling method.
[0270] S903: NIAF translates intent into business processes or task scheduling.
[0271] For example, NIAF translates user intent into corresponding business flows or task scheduling based on the local intent knowledge base and the capability information of computing network collaboration and computing management. In this embodiment, the business flow mainly drives the computing network collaboration function to realize the offloading of terminal computing tasks.
[0272] S904: NIAF sends a computing offloading request message to the computing network collaboration.
[0273] For example, NIAF sends a computing offloading request message to the computing network collaboration function according to the business process. The computing offloading request message may also include the code image package or download address of the computing task that needs to be moved up. The computing network collaboration function calculates the offloading request message, and decomposes the computing offloading task into two steps: computing task installation and execution and session establishment. It should be understood that in some possible implementations, the computing network collaboration function can also be implemented by NIAF. In this case, NIAF no longer needs to send the above-mentioned computing offloading request message and needs to receive the computing offloading response message later, which will not be described in detail in this embodiment.
[0274] S905: The computing network collaboration sends a task installation request message to the computing management.
[0275] For example, the task installation request message may include the UE ID, the UE location, the code image package or the download address of the computing task, and the like.
[0276] S906: The computing manager selects a task execution node.
[0277] For example, the computing management task selects a task execution node that meets the task requirements based on information such as the UE location, computing task category, requirements for the software and hardware execution environment, and resource usage of the current computing node.
[0278] S907: Compute information interaction between management and task execution nodes.
[0279] For example, S907a: the computing management sends a task installation request message to the task execution node, and the task installation request message includes the code image package of the computing task to instruct the selected task execution node to download and install the code image and instantiate the computing task. S907b: the task execution node sends a task installation response message to the computing management, and feeds back the IP address and port number of the task execution node where the computing task is located or an accessible uniform resource locator (URL) to facilitate subsequent addressing and access between the UE and the offloaded computing task.
[0280] S908: The computing management sends a task installation response message to the computing network collaboration.
[0281] For example, the task installation response message may include the ID of the task execution node where the computing task is located, as well as the IP address and port number or an accessible URL.
[0282] S909: Information interaction between computing network collaboration and session management.
[0283] For example, S909a: The computing network collaboration sends a session establishment request message to the session management. The session establishment request message is used to request the session management function to execute S909b to trigger the establishment of a user plane session connection between the UE and the task execution node. The specific implementation method can refer to the existing communication standards, such as the session establishment process between the UE and the UPF defined by 3GPP. This application does not make specific restrictions on this. S909c: Sending a session establishment request message to the computing network collaboration is used to indicate the result of the session establishment.
[0284] S910: The computing network collaboration sends a computing offloading response message to NIAF, including but not limited to the IP address and port number of the task execution node where the computing task is located or the accessible URL.
[0285] S911: NIAF sends an intent response message to the UE, including but not limited to the IP address and port number of the task execution node where the computing task is located or accessible.
[0286] S912: The UE interacts with the computing tasks moved up by the task execution node to achieve UE computing power expansion.
[0287] In the above embodiment, the UE expresses the intention of terminal computing offloading to NIAF, and NIAF automatically translates the intention into the corresponding business process to drive the computing network collaboration function and computing management function to realize the operation of the terminal computing task on the best task execution node in the network, thereby improving the execution speed and accuracy of the computing task, saving the battery energy consumption of the UE, which is equivalent to the network expanding the computing capacity of the terminal UE. And the above process does not require the design and development of new business processes.
[0288] Example 5: An example of NIAF's autonomous learning intention. The specific business scenario is that NIAF learns and achieves the intention based on the newly registered capability template. The specific process is as follows: Fig.10 Method 1000 is shown.
[0289] S1001: UE sends an intent request message to NIAF.
[0290] For example, a user sends an intent request message to NIAF through UE, and the intent description in the intent request message may be "terminal computing task offloading". Optionally, the image package or download address of the code of the computing task to be offloaded may be provided as an attachment included in the intent request message.
[0291] S1002: NIAF and IKB are unable to translate intent.
[0292] For example, if NIAF cannot retrieve knowledge related to “terminal task offloading” based on the local intent knowledge base or IKB, and cannot deduce the business process to implement the intent based on the capability template of the object registered in RF, NIAF determines that the intent cannot be correctly translated at present.
[0293] S1003: NIAF sends an intent response message to the UE.
[0294] For example, the intent response message can be used to provide feedback to the UE that the above intent has not been achieved. The intent response message can also include the reason why the intent has not been achieved, such as "the registered network functions are missing network functions related to computing offloading."
[0295] S1004: The computing management sends an NF capability registration request message to the RF, which includes a capability template of the computing management.
[0296] S1005: The computing network collaboration sends an NF capability registration request message to the RF, which includes the capability template of the computing network collaboration.
[0297] For example, after step S1003 is completed, the subsequent computing management functions, computing network collaboration functions, and task execution nodes related to terminal computing task offloading are deployed to the operator network and the capabilities are registered with the RF.
[0298] S1006: The RF sends a capability information notification message to the IKB.
[0299] For example, the RF notifies the IKB of a new capability registration event, and the capability information notification message includes the capability template of the newly registered object.
[0300] S1007: The IKB learns and updates based on failed historical intents and newly registered capabilities.
[0301] For example, based on the historical records of previously unfulfilled intents and the newly registered capability templates, the IKB learns how to fulfill failed intents and updates the intent knowledge base for subsequent identification and translation of the same or similar intents. It should be understood that the method by which the IKB learns and updates intent knowledge is related to the implementation of the IKB, and this application does not specifically limit this. For details, please refer to the description related to the update of the local intent knowledge base of the NIAF in the method 500 above, which will not be repeated here.
[0302] S1008: The UE sends an intent request message to the NIAF.
[0303] For example, the user sends an intent request message to NIAF again through the UE, and the content of the intent description is still "terminal computing task offloading".
[0304] S1009: NIAF sends an intent translation request message to the IKB.
[0305] For example, since NIAF's local intent knowledge base has not been updated, NIAF itself is currently unable to correctly translate the above intent, so NIAF requests IKB to assist in identifying and translating the above intent.
[0306] S1010: The IKB sends an intent-to-translate response message to the NIAF.
[0307] For example, because IKB has previously learned how to handle intents related to terminal computing offloading for the newly added capability template, IKB is able to complete the translation of the above intent and feed back the translation results to NIAF.
[0308] S1011: NIAF updates local intent knowledge base.
[0309] For example, NIAF updates the local intent knowledge base based on translation results.
[0310] S1012: Implementing the intention of computing offload.
[0311] For example, NIAF can drive the computing network collaboration function, computing management function, and task execution node according to the business process in the translation result to complete the terminal computing upward movement. The specific implementation method can refer to the description of the relevant steps in Example 4, which will not be repeated here.
[0312] S1013: NIAF sends an intent response message to the UE, including but not limited to the IP address and port number of the task execution node where the computing task is located or accessible.
[0313] S1014: The UE interacts with the computing tasks moved up by the task execution node to achieve UE computing power expansion.
[0314] In the above-mentioned embodiment, NIAF and IKB can learn how to achieve intent based on the newly registered capability set and unfulfilled historical intents, and update NIAF's local intent library knowledge and IKB, thereby improving the success rate of intent recognition and translation, making NIAF more understanding as it is used, without the need to add new business process design and development.
[0315] Combination of the above Figures 5 to 10 The present invention provides a communication method for translating the intent sent by a terminal device into a business process or task scheduling. Fig.11 and Fig.12 Two other communication methods based on the communication system provided in the embodiment of the present application and related to the implementation of the above method 500 are introduced.
[0316] In some possible implementations, the terminal device can determine a suitable NIAF through ISMF and establish an intelligent session with the NIAF, so that the terminal device can subsequently interact with the NIAF. Fig.11 A schematic flow chart of a communication method 1100 provided in an embodiment of the present application is shown, which is used to enable a terminal device to establish an intelligent session with a NIAF via an ISMF. Optionally, Fig.11 The method shown can be applied to Figure 4 The communication system 400 shown. Optionally, Fig.12 The method shown can be performed in Figure 5 Before the method shown.
[0317] It should be understood that Fig.11 Before the method shown is executed, the terminal device may have completed the network registration process. For example, the terminal device initiates a registration request message to the access and mobility management function (AMF), which may include the UE ID (such as IMSI for 4G, SUPI / SUCI / GUTI for 5G, etc.) and security credentials required for the network registration process; the AMF interacts with the digital identity management function to complete the identity authentication of the terminal device; the AMF returns a registration response message to the terminal device, which may include a temporary ID assigned by the network to the terminal device, such as TMSI / GUTI, etc. The network registration process of the terminal device may also be implemented in other ways, for example, reference may be made to the network registration method of the terminal device in the existing 5G protocol, and this application does not make specific limitations on this.
[0318] like Fig.11 As shown, the method includes the following steps.
[0319] Step S1110: The terminal device sends a fourth message to the fourth network element. Correspondingly, the fourth network element receives the fourth message from the terminal device.
[0320] The fourth network element may be an ISMF, for example Figure 4 ISMF 440 shown in . Specifically, the fourth message is used to request the establishment of a session. In the embodiment of the present application, the session established between the NIAF and the terminal device may also be referred to as an intelligent session, so the fourth message may also be referred to as an intelligent session establishment request message. The fourth message may include the UE ID, as well as the identification, capability, and capability calling method of the terminal device. It should be understood that in some possible implementations, the UE ID may also be used as the identification of the terminal device, and the present application does not make specific limitations on this. Optionally, the fourth message may also include the location information of the terminal device, which is used to indicate the geographical location of the terminal device.
[0321] Optionally, the above method 1100 may include step S1120.
[0322] Step S1120: The fourth network element selects the first network element according to the fourth message.
[0323] The first network element is used to realize the intention through information interaction with at least one object. For example, the first network element is NIAF, such as Figure 4 Specifically, for example, when there are multiple available NIAFs, the ISMF can select a suitable NIAF from the multiple NIAFs for establishing a session with the terminal device according to the intelligent session establishment request information, and the selected NIAF is called the first network element.
[0324] For example, the ISMF may select the first network element according to the location information of the terminal device. For example, the first network element may be a NIAF that is closest to the geographical location of the terminal device among the multiple NIAFs mentioned above. This increases the rate of information interaction between the terminal device and the NIAF, and / or increases the signal strength of the interaction.
[0325] It should be understood that the above two methods of selecting NIAF are only examples, and ISMF can also select a suitable NIAF based on other criteria, which is not specifically limited in this application.
[0326] Step S1130: The fourth network element establishes a session between the first network element and the terminal device.
[0327] For example, ISMF can establish a connection from the terminal device to the RAN and then to the NIAF, which may include a connection between the terminal device and the RAN (e.g., a radio resource control (RRC) connection) and a connection from the RAN to the NIAF (e.g., a general packet radio service (GPRS) tunneling protocol for the user plane (GTP-U) tunnel connection at the user level). For the specific process, please refer to the session establishment process between the terminal device and the UPF in the 3GPP TS23502 protocol. The UPF in the above process can be replaced by the NIAF in the process of this application, and will not be described in detail in this embodiment. During the session establishment process, the NIAF or ISMF allocates the addresses (or communication identifiers) of the terminal device and the NIAF, such as the IP address of the terminal device, the IP address of the NIAF instance, etc., and may further include the port number corresponding to the NIAF instance.
[0328] Step S1140: The fourth network element sends the terminal device's identifier, capability, capability calling method and the first network element's identifier to the second network element. Correspondingly, the second network element receives the terminal device's identifier, capability, capability calling method and the first network element's identifier from the fourth network element.
[0329] The second network element may be a RF, for example Figure 4 RF 420 shown in . Specifically, if the terminal device is establishing a smart session for the first time, the terminal device's identifier, capability, capability calling method, and the identifier of the first network element may be included in a terminal capability registration request message, and the terminal capability registration request message is used to request to register the capability information of the terminal device to the second network element; otherwise, the terminal device's identifier, capability, capability calling method, and the identifier of the first network element may be included in a terminal capability update request, and the terminal capability update request is used to request the second network element to update the capability information of the terminal device. The identifier of the first network element may be, for example, the name of the NIAF or the ID of the NIAF, and this application does not specifically limit this.
[0330] Optionally, the above method 1100 may further include step S1150.
[0331] Step S1150: The second network element sends a terminal capability registration / update response message to the fourth network element. Correspondingly, the fourth network element receives the terminal capability registration / update response message from the second network element.
[0332] For example, the second network element saves the capability information of the terminal device in response to the terminal capability registration / update request message, and sends a terminal capability registration / update response message to indicate the capability registration result of the terminal device.
[0333] In some possible implementations, the capability template of the terminal device may include binding information between the terminal device and the NIAF, which is used to indicate the identifier of the first network element that establishes an intelligent session with the terminal device. In this case, the specific manner in which the second network element stores the capability information of the terminal device may be: the second network element stores the capability template of the terminal device, and the capability template of the terminal device includes the identifier, capability, capability calling method of the terminal device, and the identifier of the first network element.
[0334] In some other possible implementations, the binding information between the terminal device and the NIAF may not be included in the capability template, and the capability template of the terminal device and the identifier of the corresponding first network element are saved separately. In this case, the specific manner in which the second network element saves the capability information of the terminal device may be: saving the capability template of the terminal device and the identifier of the first network element, the capability template of the terminal device includes the identifier, capability, and capability calling method of the terminal device, and the capability template of the terminal device corresponds to the identifier of the first network element.
[0335] Optionally, the above method 1100 may further include step S1160.
[0336] Step S1160: The fourth network element sends the address of the first network element to the terminal device. Correspondingly, the terminal device receives the address of the first network element from the fourth network element.
[0337] For example, the address of the first network element may be included in the intelligent session establishment response message sent by the fourth network element to the terminal device in response to the intelligent session establishment request message, and the intelligent session establishment response message is used to feedback the establishment result of the intelligent session. The intelligent session establishment response message may also include an address assigned to the terminal device. Among them, the address of the first network element may be but is not limited to the IP address of the NIAF instance, and / or the port number of the NIAF instance, and the address of the terminal device may be but is not limited to the IP address of the terminal device, etc., or any other communication identifier that enables the terminal device to interact with the first network element. The present application does not specifically limit the form of the communication identifier.
[0338] Optionally, the address of the first network element may be received by the fourth network element before sending the intelligent session establishment response message. For example, the fourth network element may receive the address of the first network element in the above step S1130, that is, the address allocated by NIAF or ISMF to the terminal device and NIAF during the session establishment process; the fourth network element may receive the address of the first network element after the above step S1130, and the fourth network element may request the first network element or other network elements to obtain the address, which is not specifically limited in this application.
[0339] Enables intention and information interaction between the terminal device and the first network element, including but not limited to the terminal device sending intentions to the first network element, and / or the first network element implementing information interaction and control of the terminal device based on the capability template of the terminal device.
[0340] Through the above method 1100, ISMF enables the terminal device to establish an intent-driven endogenous intelligent session with NIAF, so that the terminal device can interact with the network through an intention-based interface, reducing the learning cost of the terminal using the network.
[0341] In some possible implementations, various objects that can be called by NIAF can register their capabilities with RF, and RF can send the newly registered capabilities to IKB in the form of subscription notifications for learning intent knowledge. Fig.12 A schematic flow chart of a communication method 1200 provided in an embodiment of the present application is shown, which is used for various objects to register their capabilities with the RF. Optionally, Fig.12 The method shown can be applied to Figure 4 The communication system 400 shown. Optionally, Fig.12The method shown can be performed in Figure 5 Before the method shown.
[0342] like Fig.12 As shown, the method includes the following steps. It should be understood that the following steps S1210 and S1240 are optional steps, and steps S1210 and S1240 are associated. That is, in the case where the optional step S1210 is executed before step S1220, then correspondingly, the optional step S1240 is executed after step S1230 is executed; or, neither step S1210 nor S1240 is executed, and only steps S1220 and S1230 are executed.
[0343] Step S1210: The third network element sends a second message to the second network element. Correspondingly, the second network element receives the second message from the third network element.
[0344] The second network element may be a RF, for example Figure 4 The third network element may be an IKB, for example Figure 4 430 shown in FIG. Specifically, the second message is used to subscribe to the capability template of the object, such as the capability template of the object that registers the capability with the second network element, so the second message can also be called a capability subscription message. After the third network element subscribes to the capability information from the second network element, when a new capability registration event occurs, the second network element will notify the third network element. Among them, the capability registration event may include but is not limited to: a new object registers a capability, a registered object registers a new capability, and / or a registered object updates a registered capability, etc.
[0345] Step S1220: The second network element receives the identifier, capability and capability calling method of one or more objects.
[0346] Specifically, the identifier, capability, and capability calling method of one or more objects may be included in the capability registration request message, and the capability registration request message is used to request capability registration to the second network element. Depending on the type of object, the capability registration request message may include but is not limited to an NF capability registration request message, an AF capability registration request message, a management and network orchestration (MANO) capability registration request message, a digital human capability registration request message, a terminal capability registration request message, etc.
[0347] The capability registration request message may include but is not limited to the following information: object category, such as NF, AF, call application, digital person, terminal device, etc.; object identifier, used to identify the object, and when the object is a virtual entity, it can also be used to identify the instance of the object. Exemplarily, the object identifier can be the name of the object; the address of the object, such as a fully qualified domain name (FQDN) or an IP address, used for object addressing; one or more capabilities of the object, where, when the object has multiple capabilities, the multiple capabilities can be expressed in the form of a capability list; capability calling method of each capability, such as an API name and an API calling method; if the object is a terminal device, it can also include binding information between the terminal device and the NIAF, which is used to indicate the NIAF that establishes an intelligent session with the terminal device, such as the identifier of the NIAF that establishes a session with the terminal device as described above. Optionally, the above information can be used as information in the capability template of the object.
[0348] Step S1230: The second network element saves capability templates of one or more objects.
[0349] Specifically, the second network element records the capability templates registered by various types of objects, which can be used for subsequent object capability queries. Among them, the capability template of the object includes at least the object's identification, capabilities, and capability call methods. Optionally, the capability template of the object may also include other information, such as the information that can be included in the capability registration request information exemplified in the above step S1220, including but not limited to the object category, object FQDN, object IP address, etc., and may also include any other information, which is not specifically limited in this application.
[0350] Step S1240: The second network element sends capability templates of one or more objects to the third network element. Correspondingly, the third network element receives capability templates of one or more objects from the second network element.
[0351] For example, the capability template of one or more objects may be included in a capability information notification message sent by the second network element to the third network element, and the capability information notification message is used to notify the third network element of the newly registered capability template to which it has subscribed. Among them, the capability template of the above-mentioned one or more objects refers to the capability template saved by the second object after the second network element receives the capability subscription message from the third network element. After the third network element receives the capability template of the above-mentioned one or more objects, it can learn the achievable intent based on the newly registered capability template and update the IKB based on the learning results. The specific update method can refer to the description of the relevant content of the update of the local intent knowledge base of NIAF in the aforementioned embodiment S580, which will not be repeated here.
[0352] Through the above method 1200, RF can realize the capability registration of various categories of objects so that NIAF or IKB can learn achievable intents and build an intent knowledge base, thereby improving the effect of translating the intent of the terminal device into specific business processes or task scheduling strategies.
[0353] Finally, the device embodiment of the embodiment of the present application is introduced.
[0354] In order to implement the functions in the method provided in the present application, the first network element, the second network element, the third network element, and the fourth network element may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
[0355] Fig.13 1 is a schematic block diagram of a communication device 1300 of an embodiment of the present application. The communication device 1300 includes a processor 1310 and a communication interface 1320, and the processor 1310 and the communication interface 1320 can be connected to each other through a bus 1330. The communication device 1300 can be at least one of the aforementioned first network element, second network element, third network element, or fourth network element.
[0356] Optionally, the communication device 1300 may further include a memory 1340. The memory 1340 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1340 is used to store relevant instructions and data.
[0357] The processor 1310 may be one or more central processing units (CPUs). When the processor 1310 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.
[0358] When the communication device 1300 is a first network element, illustratively, the communication device 1300 is used to perform the following operations: calling a capability of at least one object according to an information interaction method, etc.
[0359] When the communication device 1300 is a second network element, illustratively, the communication device 1300 is used to perform the following operations: receiving a message for requesting a capability and a capability calling method of at least one object, etc.
[0360] When the communication device 1300 is a third network element, illustratively, the communication device 1300 is used to perform the following operations: determine an information interaction method between the first network element and at least one object according to the capability and capability calling method of at least one object, etc.
[0361] When the communication device 1300 is the fourth network element, illustratively, the communication device 1300 is used to perform the following operations: establishing a session between the terminal device and the first network element, etc.
[0362] When the communication device 1300 is at least one of the first network element, the second network element, the third network element or the fourth network element, it will be responsible for executing the method or steps related to at least one of the first network element, the second network element, the third network element or the fourth network element in the above method embodiment.
[0363] The above description is only an exemplary description. For specific content, please refer to the content shown in the above method embodiment. Fig.13 The implementation of each operation in can also refer to Figures 5 to 12 The corresponding description of the method embodiment shown.
[0364] Fig.14 1 is a schematic block diagram of a communication device 1400 of an embodiment of the present application. The communication device 1400 may be at least one of the aforementioned first network element, second network element, third network element, or fourth network element, or may be a chip or module in the first network element, second network element, third network element, or fourth network element, for implementing the method involved in the above embodiment. The communication device 1400 includes a transceiver unit 1410 and a processing unit 1420. The transceiver unit 1410 and the processing unit 1420 are exemplarily introduced below.
[0365] The transceiver unit 1410 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting action of the communication device 1400, and the receiving unit is used to perform the receiving action of the communication device 1400. For ease of description, the embodiment of the present application combines the transmitting unit and the receiving unit into one transceiver unit. A unified description is given here, and no further description is given later.
[0366] When the communication device 1400 is a first network element, exemplarily, the transceiver unit 1410 is used to receive first information from a terminal device, and obtain capabilities and capability calling methods of at least one object, and the processing unit 1420 is used to determine an information interaction method between the first network element and at least one object based on the capabilities and capability calling methods of at least one object, and call the capabilities of at least one object based on the information interaction method; or the transceiver unit 1410 is used to receive first information from a terminal device, send second information to a third network element, and receive third information from the third network element, and the processing unit 1420 is used to call the capabilities of at least one object based on the information interaction method.
[0367] When the communication device 1400 is a second network element, exemplarily, the transceiver unit 1410 is used to receive a message for requesting the capability and capability calling method of at least one object, and send the capability and capability calling method of at least one object according to the identifier of the at least one object.
[0368] When the communication device 1400 is a third network element, exemplarily, the transceiver unit 1410 is used to receive second information from the first network element, and obtain the capability and capability calling method of at least one object, the processing unit 1420 is used to determine the information interaction method between the first network element and at least one object based on the capability and capability calling method of at least one object, and the transceiver unit 1410 is also used to send third information to the first network element.
[0369] When the communication device 1400 is a fourth network element, exemplarily, the transceiver unit 1410 is used to receive a fourth message from the terminal device, the processing unit 1420 is used to establish a session between the terminal device and the first network element according to the fourth message, and the transceiver unit 1410 is also used to send the terminal device's identification, capabilities, capability calling method and the identification of the first network element to the second network element.
[0370] When the communication device 1400 is at least one of the first network element, the second network element, the third network element or the fourth network element, it will be responsible for executing the method or steps related to at least one of the first network element, the second network element, the third network element or the fourth network element in the above method embodiment.
[0371] Optionally, the communication device 1400 further includes a storage unit 1430, and the storage unit 1430 is used to store a program or code for executing the aforementioned method.
[0372] Fig.13 and Fig.14 The device embodiment shown is used to implement Figures 5 to 12 The content described. Fig.13 and Fig.14The specific execution steps and methods of the device shown can refer to the contents described in the aforementioned method embodiment.
[0373] Fig.15 1 is a schematic block diagram of a communication device 1500 of an embodiment of the present application. The communication device 1500 is used to implement the functions of at least one of the aforementioned first network element, second network element, third network element or fourth network element. The communication device 1500 may be a chip in at least one of the aforementioned first network element, second network element, third network element or fourth network element.
[0374] The communication device 1500 includes: an input / output interface 1520 and a processor 1510. The input / output interface 1520 may be an input / output circuit. The processor 1510 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application. The input / output interface 1520 is used for inputting or outputting signals or data.
[0375] For example, when the communication device 1500 is a first network element, the input-output interface 1520 is used to receive first information from a terminal device, and obtain the capability and capability calling method of at least one object, and the processor 1510 is used to determine the information interaction method between the first network element and at least one object based on the capability and capability calling method of at least one object, and call the capability of at least one object according to the information interaction method; or the input-output interface 1520 is used to receive first information from a terminal device, send second information to a third network element, and receive third information from the third network element, and the processor 1510 is used to call the capability of at least one object according to the information interaction method.
[0376] For example, when the communication device 1500 is a second network element, the input / output interface 1520 is used to receive a message for requesting the capability and capability calling method of at least one object, and send the capability and capability calling method of at least one object according to the identifier of at least one object.
[0377] For example, when the communication device 1500 is a third network element, the input-output interface 1520 is used to receive the second information from the first network element, and obtain the capability and capability calling method of at least one object, the processor 1510 is used to determine the information interaction method between the first network element and at least one object based on the capability and capability calling method of at least one object, and the input-output interface 1520 is also used to send third information to the first network element.
[0378] For example, when the communication device 1500 is a fourth network element, the input-output interface 1520 is used to receive a fourth message from the terminal device, the processor 1510 is used to establish a session between the terminal device and the first network element according to the fourth message, and the input-output interface 1520 is also used to send the terminal device's identification, capabilities, capability calling methods and the identification of the first network element to the second network element.
[0379] In one possible implementation, the processor 1510 implements the functions implemented by at least one of the aforementioned first network element, second network element, third network element, or fourth network element by executing instructions stored in the memory.
[0380] Optionally, the communication device 1500 also includes a memory.
[0381] Optionally, the processor and memory are integrated together.
[0382] Optionally, the memory is outside the communication device 1500 .
[0383] In a possible implementation, the processor 1510 may be a logic circuit, and the processor 1510 inputs / outputs messages or signals through the input / output interface 1520. The logic circuit may be a signal processor, a chip, or other integrated circuit that can implement the method of the embodiment of the present application.
[0384] The above description of the communication device 1500 is only an exemplary description. The communication device 1500 can be used to execute the method described in the above embodiment. The specific content can be found in the description of the above method embodiment, which will not be repeated here.
[0385] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.
[0386] The present application also provides a chip, including: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in each of the above examples. Optionally, the chip also includes a memory, and the memory is used to store computer programs or codes.
[0387] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions involving at least one of the first network element, the second network element, the third network element or the fourth network element in any of the above-mentioned embodiments.
[0388] The present application provides a computer program product including instructions. When the computer program product is run on a computer, the method of the above embodiment is implemented.
[0389] The present application also provides a computer program. When the computer program is executed in a computer, the method of the above embodiment is implemented.
[0390] The present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.
[0391] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0392] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0393] In several embodiments provided in the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0394] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the technical solution of the embodiment of the present application.
[0395] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0396] If the function is implemented in the form of 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 the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of each method embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.
[0397] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A communication method, characterized in that: Applied to a first network element, the method includes: Receiving first information from a terminal device, where the first information is used to describe an intention; Acquire a capability and a capability calling method of at least one object, wherein the capability of the at least one object is related to the intent; Determining, according to the capability and capability calling method of the at least one object, an information interaction method between the first network element and the at least one object, wherein the information interaction method is used to realize the intention; The capability of the at least one object is invoked according to the information interaction method.
2. The method according to claim 1, characterized in that The method of obtaining the capability of at least one object and the capability calling method includes: Sending a first message to the second network element, where the first message is used to request a capability and a capability calling method of the at least one object, and the first message includes an identifier of the at least one object; Receive capabilities and a capability calling method of the at least one object from the second network element.
3. A communication method, characterized in that: Applied to a first network element, the method includes: Receiving first information from a terminal device, where the first information is used to describe an intention; Sending second information to a third network element, where the second information is used to describe the intention; receiving third information from the third network element, the third information being used to indicate an information interaction method between the first network element and at least one object, the information interaction method being used to implement the intention, the information interaction method being determined according to a capability and a capability calling method of the at least one object; The capability of the at least one object is invoked according to the information interaction method.
4. The method according to claim 3, characterized in that The method further comprises: According to the intention and the information interaction method, a local intention knowledge base in the first network element is updated, and the local intention knowledge base is used to determine the information interaction method corresponding to the intention.
5. The method according to any one of claims 1 to 4, characterized in that: The calling of the capability of the at least one object according to the information interaction method comprises: Information describing a sub-intent of the intent is sent to at least part of the at least one object.
6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Send the result of realizing the intention to the terminal device.
7. The method according to any one of claims 1 to 6, characterized in that: Before receiving the first information from the terminal device, the method further includes: Establishing a session with the terminal device through a fourth network element; The receiving first information from the terminal device includes: The first information is received through the session.
8. The method according to any one of claims 1 to 7, characterized in that The at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent agent, and a terminal device.
9. A communication method, characterized in that: Applied to the second network element, including: receiving a message for requesting a capability and a capability calling method of at least one object, wherein the message includes an identifier of the at least one object; According to the identifier of the at least one object, the capability and the capability calling method of the at least one object are sent.
10. The method according to claim 9, characterized in that Before receiving a message for requesting a capability and a capability calling method of at least one object, the method further includes: Receiving an identification, capabilities, and a capability invocation method of the at least one object; A capability template of the at least one object is saved, wherein the capability template of each object in the at least one object includes an identifier, a capability, and a capability calling method of the object.
11. The method according to claim 10, characterized in that The method further comprises: According to the identifier of the at least one object, a capability template of the at least one object is queried to determine the capability and capability calling method of the at least one object.
12. The method according to claim 10 or 11, characterized in that: Before receiving the identification, capability and capability calling method of the at least one object, the method further includes: receiving a second message from a third network element, where the second message is used to subscribe to a capability template of the object; After saving the capability template of the at least one object, the method further includes: Sending the capability template of the at least one object to the third network element.
13. The method according to any one of claims 9 to 12, characterized in that The method further comprises: Receiving an identifier, a capability, a capability calling method of a terminal device and an identifier of a first network element from a fourth network element, wherein a session exists between the first network element and the terminal device; Saving a capability template of the terminal device, where the capability template of the terminal device includes an identifier, a capability, a capability calling method of the terminal device, and an identifier of the first network element; or The capability template of the terminal device and the identifier of the first network element are saved, wherein the capability template of the terminal device includes the identifier, capability and capability calling method of the terminal device, and the capability template of the terminal device corresponds to the identifier of the first network element.
14. The method according to any one of claims 9 to 13, characterized in that The at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent agent, and a terminal device.
15. A communication method, characterized in that: Applied to the third network element, including: receiving second information from the first network element, where the second information is used to describe the intention; Acquire a capability and a capability calling method of at least one object, wherein the capability of the at least one object is related to the intent; Determining, according to the capability and capability calling method of the at least one object, an information interaction method between the first network element and the at least one object, wherein the information interaction method is used to realize the intention; Sending third information to the first network element, where the third information is used to indicate the information interaction method.
16. The method according to claim 15, characterized in that The method of obtaining the capability of at least one object and the capability calling method includes: Sending a third message to the second network element, where the third message is used to request the capability and capability calling method of the at least one object, and the third message includes an identifier of the at least one object; Receive capabilities and a capability calling method of the at least one object from the second network element.
17. The method according to claim 15 or 16, characterized in that The method further comprises: Sending a second message to the second network element, where the second message is used to subscribe to a capability template of the object, where the capability template includes an identifier of the object and capabilities and a capability calling method of the object; receiving a capability template of one or more objects from the second network element; An intent knowledge base is updated according to the capability template of the one or more objects, and the intent knowledge base is used to determine an information interaction method corresponding to the intent.
18. The method according to any one of claims 15 to 17, characterized in that The at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent agent, and a terminal device.
19. A communication method, characterized in that: Applied to the fourth network element, including: receiving a fourth message from a terminal device, the fourth message being used to request establishment of a session, the fourth message including an identifier, a capability, and a capability calling method of the terminal device; Establishing, according to the fourth message, a session between the terminal device and a first network element, the first network element being configured to realize an intention by interacting with at least one object; Send the identifier, capability, capability calling method of the terminal device and the identifier of the first network element to the second network element.
20. The method according to claim 19, characterized in that The session is used to transmit an intention and / or to invoke a capability of the terminal device.
21. The method according to claim 19 or 20, characterized in that Before establishing the session between the terminal device and the first network element, the method further includes: Select the first network element.
22. The method according to any one of claims 19 to 21, characterized in that After establishing the session between the terminal device and the first network element, the method further includes: Send the address of the first network element to the terminal device.
23. The method according to claim 22, characterized in that Before sending the address of the first network element to the terminal device, the method further includes: An address of the first network element is received from the first network element.
24. The method according to any one of claims 19 to 23, characterized in that The at least one object includes at least one of the following: a network function NF, a management function MF, an application function AF, a call application, an intelligent agent, and a terminal device.
25. A communication device, characterized in that: comprising means for performing the method of any one of claims 1 to 8; or comprising means for performing the method of any one of claims 9 to 14; or comprising means for performing the method of any one of claims 15 to 18; or Comprising means for performing the method of any one of claims 19 to 24.
26. A communication device, characterized in that: comprising a processor configured to, by executing a computer program or instructions, causing the communication device to perform the method according to any one of claims 1 to 8; or causing the communication device to perform the method according to any one of claims 9 to 14; or causing the communication device to perform the method according to any one of claims 15 to 18; or The communication device is caused to execute the method according to any one of claims 19 to 24.
27. The communication device according to claim 26, characterized in that The communication device further comprises a memory for storing the computer program or instructions.
28. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program or instruction. When the computer program or instruction is executed on a computer, causing the computer to execute the method according to any one of claims 1 to 8; or, causing the computer to execute the method according to any one of claims 9 to 14; or, causing the computer to execute the method according to any one of claims 15 to 18; or, The computer is caused to execute the method according to any one of claims 19 to 24.
29. A computer program product, characterized in that Contains instructions that, when executed on a computer, causing the computer to execute the method according to any one of claims 1 to 8; or, causing the computer to execute the method according to any one of claims 9 to 14; or, causing the computer to execute the method according to any one of claims 15 to 18; or, The computer is caused to execute the method according to any one of claims 19 to 24.
30. A communication system, characterized in that: include: A communication device for performing the method according to any one of claims 1 to 8; and A communication device for performing the method according to any one of claims 9 to 14.
31. The communication system according to claim 30, characterized in that The communication system further comprises: A communication device for performing the method of any one of claims 15 to 18; and / or A communication device for performing the method according to any one of claims 19 to 24.
Citation Information
Cited By
Navigation method, system and equipment based on multi-modal model, medium and product
CN121230736A
Communication method, apparatus and system
EP4794372A1