Semantic communication method and related device

Abstract

The embodiment of the invention provides a semantic communication method and a related device, and the method comprises the steps: sending semantic conversion mode information to an intermediate device, the semantic conversion mode information being used for indicating a semantic conversion model and / or a semantic conversion knowledge base used by the intermediate device, the intermediate equipment is used for forwarding the coded data of the sending end to the receiving end; sending the semantic conversion mode information to the sending end; and sending the semantic conversion mode information to the receiving end. Therefore, under the condition that the semantic knowledge base or the semantic model between the sending end and the receiving end is not matched, the semantic communication quality between the sending end and the receiving end is improved through semantic conversion in the intermediate equipment.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a semantic communication method and related devices. Background Art

[0002] With the evolution of communication technologies, a new capability has been proposed in the Sixth Generation (6G) network architecture: semantic communication. Semantic communication is a new architecture that can incorporate the needs and information meanings of users into the communication process, and can significantly improve the transmission efficiency by exploring semantic information. In recent years, with the continuous development of artificial intelligence technologies and the huge progress in algorithms, computing power, and data, it has been able to accurately and efficiently extract semantic information such as images, texts, or voices, making semantic communication possible at the engineering level. Compared with traditional communication methods driven by data fidelity, semantic communication is a communication method that extracts information at the semantic level from the information source to achieve the purpose of "preserving meaning", which can greatly reduce the required transmission channel bandwidth.

[0003] The current semantic communication structure is as follows: After the source data is semantically extracted locally at the sending end, semantic encoding is performed in combination with the encoding knowledge base (also called the encoded semantic encoding knowledge base) and the encoding model at the sending end. After receiving the encoded data, the receiving end performs semantic decoding and semantic recovery to obtain the source data in combination with the local decoding knowledge base (also called the decoded semantic encoding knowledge base) and the decoding model.

[0004] However, currently, due to possible mismatches between the encoding knowledge base and / or encoding model at the sending end and the decoding knowledge base and / or decoding model at the receiving end, there is a problem of low semantic recovery accuracy. Summary of the Invention

[0005] In a first aspect, an embodiment of this application proposes a semantic communication method, which is applied to a core network device. The method includes: sending semantic conversion mode information to an intermediate device, where the semantic conversion mode information is used to indicate the semantic conversion model and / or semantic conversion knowledge base used by the intermediate device, and the intermediate device is used to forward the encoded data of the sending end to the receiving end; sending the semantic conversion mode information to the sending end; and sending the semantic conversion mode information to the receiving end.

[0006] In the embodiments of the present application, the core network device sends semantic conversion mode information to the intermediate device, the sending end, and the receiving end, so that the semantic conversion model and the semantic conversion knowledge base used by the intermediate device match the semantic encoding model and the semantic encoding knowledge base of the sending end, and the semantic conversion model and the semantic conversion knowledge base used by the intermediate device match the semantic decoding model and the semantic decoding knowledge base of the receiving end. In the case where the semantic knowledge base or the semantic model between the sending end and the receiving end does not match, the semantic communication quality between the sending end and the receiving end is improved through the semantic conversion of the intermediate device.

[0007] In combination with the first aspect, in a possible implementation manner of the first aspect, semantic conversion capability information of the sending end is received, where the semantic conversion capability information is used to indicate a semantic encoding model and / or a semantic encoding knowledge base supported by the sending end; according to the semantic conversion capability information of the sending end, the semantic conversion mode information is determined, where the semantic conversion model matches the semantic encoding model supported by the sending end, and the semantic conversion knowledge base matches the semantic encoding knowledge base supported by the sending end. The sending end reports the semantic conversion capability information to the core network device, and the core network device determines the semantic conversion mode information according to the capability information, ensuring that the semantic encoding model and / or the semantic encoding knowledge base indicated by the semantic conversion mode information match the semantic encoding model and / or the semantic encoding knowledge base supported by the sending end, and improving the semantic communication quality between the sending end and the receiving end.

[0008] In combination with the first aspect, in a possible implementation manner of the first aspect, the method further includes: determining the semantic conversion mode information according to the quality of service requirements for semantic communication between the sending end and the receiving end, where the quality of service requirements for semantic communication include any one or more of the following: semantic decoding accuracy rate, semantic similarity, semantic clarity, guaranteed bit rate, packet transmission delay budget, or packet error rate. Determining the semantic conversion mode information according to the quality of service requirements for semantic communication improves the implementation flexibility of the solution.

[0009] In combination with the first aspect, in a possible implementation manner of the first aspect, the semantic conversion model includes: a semantic conversion encoding model and a semantic conversion decoding model, and the semantic conversion knowledge base includes: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base. Optionally, the semantic conversion model may also include performing semantic encoding functions and semantic decoding functions, improving the implementation flexibility of the solution.

[0010] In combination with the first aspect, in a possible implementation manner of the first aspect, the semantic conversion mode information includes any one or more of the following information: information about the semantic conversion model, information about the semantic conversion knowledge base, information about the semantic conversion encoding model, information about the semantic conversion encoding knowledge base, information about the semantic conversion decoding model, or information about the semantic conversion decoding knowledge base. This information includes, but is not limited to: identification information, index, or complete model information or complete knowledge base information.

[0011] In combination with the first aspect, in a possible implementation manner of the first aspect, the semantic conversion capability information includes any one or more of the following: type information of the semantic encoding model, size of the semantic encoding model, identification information of the semantic encoding model, type information of the semantic encoding knowledge base, size of the semantic encoding knowledge base, or identification information of the semantic encoding knowledge base. The sending end can report to the core network device relevant information about the semantic encoding model supported by the sending end and / or relevant information about the semantic encoding knowledge base supported by the sending end. So that the core network device can determine the corresponding semantic conversion capability information according to this semantic conversion capability information.

[0012] In a second aspect, an embodiment of the present application proposes a semantic communication method, which is applied to an intermediate device. The method includes: receiving semantic conversion mode information sent by a core network device, where the semantic conversion mode information is used to indicate a semantic conversion model and / or a semantic conversion knowledge base used by the intermediate device; determining the semantic conversion model and / or the semantic conversion knowledge base according to the semantic conversion mode information; receiving first encoded data sent by a sending end, where the first encoded data is data encoded by the sending end using a semantic encoding model and / or a semantic encoding knowledge base; processing the first encoded data using the semantic conversion model and the semantic conversion knowledge base to obtain second encoded data; and sending the second encoded data to a receiving end.

[0013] In an embodiment of the present application, the intermediate device determines a semantic conversion model and / or a semantic conversion knowledge base for performing semantic conversion according to the semantic conversion mode information sent by the core network device, ensuring that the receiving end can successfully decode the second encoded data sent to the receiving end. The semantic communication quality between the sending end and the receiving end is improved.

[0014] In combination with the second aspect, in a possible implementation manner of the second aspect, the semantic conversion model includes: a semantic conversion encoding model and a semantic conversion decoding model, and the semantic conversion knowledge base includes: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base. Optionally, the semantic conversion model can also include performing semantic encoding and semantic decoding functions, which improves the implementation flexibility of the solution.

[0015] In combination with the second aspect, in a possible implementation manner of the second aspect, the semantic conversion mode information includes any one or more of the following information: information of the semantic conversion model, information of the semantic conversion knowledge base, information of the semantic conversion encoding model, information of the semantic conversion encoding knowledge base, information of the semantic conversion decoding model, or information of the semantic conversion decoding knowledge base. This information includes, but is not limited to, identification information, index, or complete model information or complete knowledge base information.

[0016] In combination with the second aspect, in a possible implementation manner of the second aspect, processing the first encoded data by using the semantic conversion model and the semantic conversion knowledge base to obtain the second encoded data includes: decoding the first encoded data by using the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data; encoding the intermediate data by using the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate the second encoded data. Specifically, the intermediate device performs semantic conversion processing on the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to obtain the second encoded data. Specifically, the semantic conversion processing includes: first, performing semantic decoding and semantic restoration on the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate intermediate data, and then performing semantic extraction and semantic encoding on the intermediate data according to the semantic conversion model and the semantic conversion knowledge base to obtain the second encoded data.

[0017] In combination with the second aspect, in a possible implementation manner of the second aspect, the intermediate device includes a first intermediate device and a second intermediate device, where the first intermediate device provides services for the sending end, and the second intermediate device provides services for the receiving end. Processing the first encoded data by using the semantic conversion model and the semantic conversion knowledge base to obtain the second encoded data includes: the first intermediate device decoding the first encoded data by using the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data; the first intermediate device sending the intermediate data to the second intermediate device; the second intermediate device encoding the intermediate data by using the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate the second encoded data; sending the second encoded data to the receiving end includes: the second intermediate device sending the second encoded data to the receiving end.

[0018] The first intermediate device performs semantic decoding and semantic restoration on the first encoded data according to the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data. Then, the first intermediate device sends the intermediate data to the second intermediate device, and the second intermediate device performs semantic extraction and semantic encoding on the intermediate data according to the semantic conversion encoding model and the semantic conversion encoding knowledge base to obtain the second encoded data.

[0019] In a third aspect, an embodiment of the present application provides a semantic communication method, which is applied to a sending end, and the method includes:

[0020] Receiving semantic conversion mode information sent by a core network device, where the semantic conversion mode information is used to indicate a semantic conversion model and / or a semantic conversion knowledge base used by an intermediate device, and the intermediate device is used to forward the encoded data of the sending end to a receiving end;

[0021] Determining a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information, where the semantic encoding model matches the semantic conversion model, and the semantic encoding knowledge base matches the semantic conversion knowledge base;

[0022] Using the semantic encoding knowledge base and the semantic encoding knowledge base to perform encoding processing on source data to generate first encoded data;

[0023] Sending the first encoded data to the intermediate device.

[0024] In an embodiment of the present application, the sending end determines a semantic encoding model and / or a semantic encoding knowledge base that matches the semantic conversion model and / or the semantic conversion knowledge base for semantic conversion by the intermediate device according to the semantic conversion mode information sent by the core network device. Then, the sending end performs encoding processing on the source data according to the semantic encoding model and the semantic encoding knowledge base to generate the first encoded data. Ensure that the receiving end can successfully decode the second encoded data generated by the intermediate device based on the first encoded data. The semantic communication quality between the sending end and the receiving end is improved.

[0025] In combination with the third aspect, in a possible implementation manner of the third aspect, the method further includes: sending semantic conversion capability information to the core network device, where the semantic conversion capability information is used to indicate the semantic encoding model and / or the semantic encoding knowledge base supported by the sending end. The sending end can report relevant information on the semantic encoding model supported by the sending end and / or relevant information on the semantic encoding knowledge base supported by the sending end to the core network device. So that the core network device can determine the corresponding semantic conversion capability information according to the semantic conversion capability information.

[0026] In combination with the third aspect, in a possible implementation manner of the third aspect, the semantic conversion capability information includes any one or more of the following: the type information of the semantic encoding model, the size of the semantic encoding model, the identification information of the semantic encoding model, the type information of the semantic encoding knowledge base, the size of the semantic encoding knowledge base, or the identification information of the semantic encoding knowledge base.

[0027] Fourth aspect, an embodiment of the present application proposes a semantic communication method, which is applied to a receiving end, and the method includes:

[0028] Receiving semantic conversion mode information sent by a core network device, where the semantic conversion mode information is used to indicate a semantic conversion model and / or a semantic conversion knowledge base used by an intermediate device, and the intermediate device is used to forward encoded data of a sending end to the receiving end;

[0029] Determining a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information, where the semantic decoding model matches the semantic conversion model, and the semantic decoding knowledge base matches the semantic conversion knowledge base;

[0030] Receiving second encoded data sent by the intermediate device;

[0031] Using the semantic decoding knowledge base and the semantic decoding knowledge base to perform decoding processing on the second encoded data to generate target data.

[0032] In an embodiment of the present application, the receiving end determines a semantic decoding model and / or a semantic decoding knowledge base that matches the semantic conversion model and / or the semantic conversion knowledge base for performing semantic conversion by the intermediate device according to the semantic conversion mode information sent by the core network device. Then, the receiving end performs decoding processing on the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data. Since the semantic decoding model and / or the semantic decoding knowledge base used by the receiving end are indicated by the intermediate device, it can be ensured that the receiving end successfully decodes the second encoded data. The semantic communication quality between the sending end and the receiving end is improved.

[0033] In combination with the fourth aspect, in a possible implementation manner of the fourth aspect, the semantic conversion mode information includes any one or more of the following information: the information of the semantic conversion model, the information of the semantic conversion knowledge base, the information of the semantic conversion encoding model, the information of the semantic conversion encoding knowledge base, the information of the semantic conversion decoding model, or the information of the semantic conversion decoding knowledge base.

[0034] Fifth aspect, an embodiment of the present application proposes a communication device, which is applied to a core network device, and the communication device includes:

[0035] A transceiver module, configured to send semantic conversion mode information to an intermediate device, where the semantic conversion mode information is used to indicate a semantic conversion model and / or a semantic conversion knowledge base used by the intermediate device, and the intermediate device is configured to forward encoded data of a sending end to a receiving end;

[0036] The transceiver module is further configured to send the semantic conversion mode information to the sending end;

[0037] The transceiver module is further configured to send the semantic conversion mode information to the receiving end.

[0038] In a possible implementation,

[0039] The transceiver module is further configured to receive semantic conversion capability information of the sending end, where the semantic conversion capability information is used to indicate a semantic encoding model and / or a semantic encoding knowledge base supported by the sending end;

[0040] A processing module, configured to determine the semantic conversion mode information according to the semantic conversion capability information of the sending end, where the semantic conversion model matches the semantic encoding model supported by the sending end, and the semantic conversion knowledge base matches the semantic encoding knowledge base supported by the sending end.

[0041] In a possible implementation,

[0042] The processing module is further configured to determine the semantic conversion mode information according to quality of service requirements for semantic communication between the sending end and the receiving end, where the quality of service requirements for the semantic communication include any one or more of the following: semantic decoding accuracy rate, semantic similarity, semantic clarity, guaranteed bit rate, packet transmission delay budget, or packet error rate.

[0043] In a possible implementation, the semantic conversion model includes: a semantic conversion encoding model and a semantic conversion decoding model, and the semantic conversion knowledge base includes: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base.

[0044] In a possible implementation, the semantic conversion mode information includes any one or more of the following information: information about the semantic conversion model, information about the semantic conversion knowledge base, information about the semantic conversion encoding model, information about the semantic conversion encoding knowledge base, information about the semantic conversion decoding model, or information about the semantic conversion decoding knowledge base.

[0045] In a possible implementation, the semantic conversion capability information includes any one or more of the following: the type information of the semantic encoding model, the size of the semantic encoding model, the identification information of the semantic encoding model, the type information of the semantic encoding knowledge base, the size of the semantic encoding knowledge base, or the identification information of the semantic encoding knowledge base.

[0046] In a sixth aspect, an embodiment of the present application provides a communication device, which is applied to an intermediate device. The communication device includes:

[0047] The transceiver module is further configured to receive semantic conversion mode information sent by a core network device, where the semantic conversion mode information is used to indicate a semantic conversion model and / or a semantic conversion knowledge base used by the intermediate device;

[0048] The processing module is further configured to determine the semantic conversion model and / or the semantic conversion knowledge base according to the semantic conversion mode information;

[0049] The transceiver module is further configured to receive first encoded data sent by a sending end, where the first encoded data is data encoded by the sending end using a semantic encoding model and / or a semantic encoding knowledge base;

[0050] The processing module is further configured to process the first encoded data using the semantic conversion model and the semantic conversion knowledge base to obtain second encoded data;

[0051] The transceiver module is further configured to send the second encoded data to a receiving end.

[0052] In a possible implementation, the semantic conversion model includes: a semantic conversion encoding model and a semantic conversion decoding model, and the semantic conversion knowledge base includes: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base.

[0053] In a possible implementation, the semantic conversion mode information includes any one or more of the following information: the information of the semantic conversion model, the information of the semantic conversion knowledge base, the information of the semantic conversion encoding model, the information of the semantic conversion encoding knowledge base, the information of the semantic conversion decoding model, or the information of the semantic conversion decoding knowledge base.

[0054] In a possible implementation,

[0055] The processing module is further configured to perform decoding processing on the first encoded data using the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data;

[0056] The processing module is further configured to perform encoding processing on the intermediate data by using the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate the second encoded data.

[0057] In a possible implementation manner, the intermediate device includes a first intermediate device and a second intermediate device, where the first intermediate device provides services for the sending end, and the second intermediate device provides services for the receiving end.

[0058] The processing module is further configured to perform decoding processing on the first encoded data by using the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data.

[0059] The transceiver module is further configured to send the intermediate data to the second intermediate device.

[0060] The processing module is further configured to perform encoding processing on the intermediate data by using the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate the second encoded data.

[0061] The transceiver module is further configured to send the second encoded data to the receiving end.

[0062] In a seventh aspect, an embodiment of the present application provides a semantic communication method. The communication device is applied to a sending end, and the communication device includes:

[0063] The transceiver module is further configured to receive semantic conversion mode information sent by a core network device. The semantic conversion mode information is used to indicate a semantic conversion model and / or a semantic conversion knowledge base used by an intermediate device, and the intermediate device is used to forward the encoded data of the sending end to a receiving end.

[0064] The processing module is further configured to determine a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information, where the semantic encoding model matches the semantic conversion model, and the semantic encoding knowledge base matches the semantic conversion knowledge base.

[0065] The processing module is further configured to perform encoding processing on source data by using the semantic encoding knowledge base and the semantic encoding knowledge base to generate first encoded data.

[0066] The transceiver module is further configured to send the first encoded data to the intermediate device.

[0067] In a possible implementation manner,

[0068] The transceiver module is further configured to send semantic conversion capability information to the core network device. The semantic conversion capability information is used to indicate a semantic encoding model and / or a semantic encoding knowledge base supported by the sending end.

[0069] In a possible implementation, the semantic conversion capability information includes any one or more of the following: the type information of the semantic encoding model, the size of the semantic encoding model, the identification information of the semantic encoding model, the type information of the semantic encoding knowledge base, the size of the semantic encoding knowledge base, or the identification information of the semantic encoding knowledge base.

[0070] In an eighth aspect, an embodiment of the present application provides a semantic communication method. The communication device is applied to the receiving end, and the communication device includes:

[0071] The transceiver module is further configured to receive the semantic conversion mode information sent by the core network device. The semantic conversion mode information is used to indicate the semantic conversion model and / or the semantic conversion knowledge base used by the intermediate device. The intermediate device is used to forward the encoded data of the sending end to the receiving end;

[0072] The processing module is further configured to determine a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information, where the semantic decoding model matches the semantic conversion model, and the semantic decoding knowledge base matches the semantic conversion knowledge base;

[0073] The transceiver module is further configured to receive the second encoded data sent by the intermediate device;

[0074] The processing module is further configured to use the semantic decoding knowledge base and the semantic decoding knowledge base to perform decoding processing on the second encoded data to generate target data.

[0075] In a possible implementation, the semantic conversion mode information includes any one or more of the following information:

[0076] The information of the semantic conversion model, the information of the semantic conversion knowledge base, the information of the semantic conversion encoding model, the information of the semantic conversion encoding knowledge base, the information of the semantic conversion decoding model, or the information of the semantic conversion decoding knowledge base.

[0077] The ninth aspect of the present application provides a communication device, which can implement the method in the above-mentioned first aspect or any possible implementation manner of the first aspect. The device includes corresponding units or modules for executing the above method. The units or modules included in the device can be implemented by software and / or hardware. For example, the device can be a core network device, or the device can be a component in the core network device (such as a processor, a chip, or a chip system, etc.), or the device can also be a logical module or software that can implement all or part of the core network device. Among them, the communication device includes a transceiver module and a processing module. For example, the communication device is a server with a core network device.

[0078] The tenth aspect of the present application provides a communication device, which can implement the method in the above-mentioned second aspect or any possible implementation manner of the second aspect. The device includes corresponding units or modules for executing the above method. The units or modules included in the device can be implemented by software and / or hardware. For example, the device can be an intermediate device, or the device can be a component in the intermediate device (such as a processor, a chip, or a chip system, etc.), or the device can also be a logical module or software that can implement all or part of the intermediate device. Among them, the communication device includes a transceiver module and a processing module.

[0079] The eleventh aspect of the present application provides a communication device, which can implement the method in the above-mentioned third aspect or any possible implementation manner of the third aspect. The device includes corresponding units or modules for executing the above method. The units or modules included in the device can be implemented by software and / or hardware. For example, the device can be a sending end, or the device can be a component in the sending end (such as a processor, a chip, or a chip system, etc.), or the device can also be a logical module or software that can implement all or part of the sending end. Among them, the communication device includes a transceiver module and a processing module.

[0080] The twelfth aspect of the present application provides a communication device, which can implement the method in the above-mentioned fourth aspect or any possible implementation manner of the fourth aspect. The device includes corresponding units or modules for executing the above method. The units or modules included in the device can be implemented by software and / or hardware. For example, the device can be a receiving end, or the device can be a component in the receiving end (such as a processor, a chip, or a chip system, etc.), or the device can also be a logical module or software that can implement all or part of the receiving end. Among them, the communication device includes a transceiver module and a processing module.

[0081] The thirteenth aspect of the embodiments of the present application provides a communication device, including at least one processor, and the at least one processor is coupled to a memory; the memory is used to store programs or instructions; the at least one processor is used to execute the programs or instructions, so that the device implements the method of any one of the possible implementation manners in the foregoing first aspect to fourth aspect.

[0082] The fourteenth aspect of the embodiments of the present application provides a communication device, including a communication interface for inputting and / or outputting signaling or data; a processor for executing a computer-executable program, so that the device implements the method of any one of the possible implementation manners in the foregoing first aspect to fourth aspect.

[0083] The fifteenth aspect of the embodiments of the present application provides a communication device, including at least one logic circuit and an input / output interface; the input / output interface is used to input or output information; the logic circuit is used to execute the method of any one of the possible implementation manners in the foregoing first aspect to fourth aspect.

[0084] The sixteenth aspect of the embodiments of the present application provides a computer program product (or computer program), when the computer program product is executed by the processor, the processor executes the methods in the foregoing first aspect to fourth aspect and any possible implementation manner.

[0085] The seventeenth aspect of the embodiments of the present application provides a chip system, the chip system includes at least one processor, and is used to support the communication device to implement the methods in the foregoing first aspect to fourth aspect and any possible implementation manner.

[0086] In a possible design, the chip system may further include a memory for storing necessary program instructions and data of the communication device. The chip system may be composed of chips, or may include chips and other discrete devices. Optionally, the chip system further includes an interface circuit, and the interface circuit provides program instructions and / or data for the at least one processor.

[0087] The eighteenth aspect of the embodiments of the present application provides a communication system, the communication system includes the communication device in the foregoing fifth aspect, the communication device in the sixth aspect, the communication device in the seventh aspect, and / or the communication device in the eighth aspect.

[0088] Among them, the technical effects brought by any one of the design manners in the fifth aspect to the eighteenth aspect can refer to the technical effects brought by different implementation manners in the foregoing first aspect to the fourth aspect, and will not be elaborated here. Description of the Drawings

[0089] Figure 1 It is a schematic diagram of a communication system in the embodiments of the present application;

[0090] Figure 2 It is a schematic diagram of semantic communication;

[0091] Figure 3 It is a schematic diagram of a scenario of semantic communication;

[0092] Figure 4 It is a schematic diagram of the communication scenario involved in the embodiments of the present application;

[0093] Figure 5 It is a schematic diagram of the embodiment process of a semantic communication method proposed in the embodiments of the present application;

[0094] Figure 6 It is a schematic diagram of a network protocol stack architecture in the embodiments of the present application;

[0095] Figure 7 It is a schematic diagram of the embodiment process of a semantic communication method proposed in the embodiments of the present application;

[0096] Figure 8 It is a schematic diagram of the embodiment process of a semantic communication method proposed in the embodiments of the present application;

[0097] Figure 9 It is a schematic diagram of the embodiment process of a semantic communication method proposed in the embodiments of the present application;

[0098] Figure 10 It is a schematic diagram of the embodiment process of a semantic communication method proposed in the embodiments of the present application;

[0099] Figure 11 It is a schematic diagram of a communication device provided by the present application;

[0100] Figure 12 It is another schematic diagram of a communication device provided by the present application;

[0101] Figure 13 It is another schematic diagram of a communication device provided by the present application;

[0102] Figure 14 It is another schematic diagram of a communication device provided by the present application. Detailed implementation manners

[0103] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Terms such as "first" and "second" and their corresponding term numbers in the specification and claims of the present application and the above-mentioned accompanying drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, which is only a way of distinguishing objects with the same attributes when describing the embodiments of the present application. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion, so that a process, method, system, product or device including a series of units does not have to be limited to those units, but may include other units not clearly listed or inherent to these processes, methods, products or devices.

[0104] In the description of the present application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; the "and / or" in the present application is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the present application, "at least one item" means one or more items, and "multiple items" means two or more items. "At least one of the following (items)" or its similar expressions refer to any combination of these items, including any combination of single (item) or plural (items). For example, at least one of a, b, or c may mean: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, c may be single or multiple.

[0105] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th generation (5G) system, New Generation (NR) communication system or future 6th generation communication system, etc.

[0106] The part operated by an operator in various communication systems can be referred to as the operator network. The operator network can also be called a public land mobile network (PLMN) network, which is a network established and operated by the government or an operator approved by the government for the purpose of providing land mobile communication services to the public. It is mainly a public network where mobile network operators (MNOs) provide mobile broadband access services to users. The operator network or PLMN network described in the embodiments of this application can be a network that meets the standards of the 3rd Generation Partnership Project (3GPP), simply referred to as a 3GPP network. Usually, the 3GPP network is operated by an operator, including but not limited to the 5th-generation (5G) mobile communication network, the 4th-generation (4G) mobile communication network, or the 3rd-generation (3G) mobile communication technology network. It also includes the future 6th-generation (6G) mobile communication network.

[0107] Please refer to Figure 1 , Figure 1 which is a schematic diagram of a communication system in the embodiments of this application. As Figure 1 shown, the communication system includes an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a radio access network (RAN), a policy control function (PCF), a terminal device, a user plane function (UPF), a network exposure function (NEF), an application function (AF), and a data network (DN), etc.

[0108] The following briefly introduces Figure 1 each network function (or network element) shown in

[0109] Terminal device: It can be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.

[0110] The terminal device can be a device that provides voice / data to users. For example, it can be a handheld device with wireless connection function, in-vehicle device, etc. Currently, some examples of terminals are: mobile phone, tablet computer, laptop computer, palmtop computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing devices connected to a wireless modem, wearable device, terminal device in a 5G network or terminal device in a future evolved public land mobile communication network, etc. The embodiments of the present application are not limited thereto.

[0111] By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. A wearable device, also known as a wearable intelligent device, is a general term for devices developed by applying wearable technologies to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothing or accessories. A wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0112] 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. The 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 technologies, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection.

[0113] It should be noted that the terminal device and the access network device may communicate with each other using a certain air interface technology (such as NR or LTE technology, etc.). The terminal device and the terminal device may also communicate with each other using a certain air interface technology (such as NR or LTE technology, etc.).

[0114] In the embodiments of the present application, the terminal device may be replaced by a device for realizing the functions of the terminal device, or may also be a device capable of supporting the terminal device to realize such functions, such as a chip system or a chip. This device may be installed in the terminal device. In addition, the chip system may be composed of chips, or may include chips and other discrete devices.

[0115] An access network device (also known as a wireless access network) can be a device with wireless transceiver functions. The access network device can be a device that provides wireless communication function services, usually located on the network side, including but not limited to: the next-generation base station (gNodeB, gNB) in the fifth-generation communication system, the next-generation base station in the sixth-generation (mobile communication system), the base station in the future mobile communication system, or the access node in the WiFi system, the evolved node B (eNB) in the LTE system, the radio network controller (RNC), the node B (NB), the base station controller (BSC), the home base station (e.g., home evolved NodeB, or home Node B, HNB), the wireless access point, the base band unit (BBU), the transmission reception point (TRP), the transmitting point (TP), the base transceiver station (BTS), etc. In one network structure, the access network device can include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a RAN device with a control plane CU node, a user plane CU node, and a DU node. The access network device serves a cell, and the user equipment communicates with the base station through the transmission resources used by the cell (e.g., frequency domain resources, or in other words, spectrum resources). The cell can be the cell corresponding to the base station (e.g., the base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. Here, the small cell can include: the metro cell, the micro cell, the pico cell, the femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services. The access network device can be a macro base station, a micro base station or an indoor station, and can also be a relay node or a donor node, a device that provides wireless communication services for user equipment in the V2X communication system, a wireless controller in the cloud radio access network (CRAN) scenario, a relay station, a vehicle-mounted device, a wearable device, and network devices in future evolved networks, etc.The access network device may also be wireless access equipment such as Integrated Access and Backhaul (IAB), Network-controlled Repeater (NCR), etc.

[0116] The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.

[0117] Unified data management network element (also called unified data management network element, unified data management network element entity, data management equipment, unified data management network element equipment) is a kind of core network equipment, mainly used to process terminal equipment identification, access authentication, registration and mobility management, etc. Unified data management is a control plane device.

[0118] Policy control function (also known as policy control network element, policy control functional network element, policy control equipment, policy control functional network element entity, etc.): mainly responsible for policy control functional network element such as billing for sessions and service flow levels, service quality bandwidth guarantee and mobility management, terminal device policy decision-making, etc.

[0119] Session management function (also called session management function network element): mainly performs session management, execution of control policies issued by PCF, selection of UPF, allocation of Internet Protocol addresses for terminal devices, etc.

[0120] The access and mobility management function (also known as access and mobility management function entity, access and mobility management equipment, access and mobility management function network element, access management equipment, mobility management equipment) is a type of core network equipment, mainly used for mobility management and access management, etc. It can be used to implement other functions of the mobility management entity (MME) except session management, such as lawful interception, or access authorization (or authentication), user equipment registration, mobility management, tracking area update process, reachability detection, selection of session management function network element, mobile state transition management and other functions.

[0121] User plane function (also known as user plane equipment, user plane function network element, user plane function network element, user plane function entity): mainly includes the following functions: data packet routing and transmission, packet detection, service usage reporting, QoS processing, uplink packet detection, downlink data packet storage and other user plane related functions.

[0122] The Application Function (AF) is similar to an application server, which interacts with other 5G core network control planes (NFs) and provides service offerings. The AF can exist for different application services and can be owned by an operator or a trusted third party. For example, the main function of this network element is to inform the PCF of the latest service requirements of a third-party enterprise for a certain application. The PCF will generate corresponding Quality of Service (QoS) rules according to the requirements to ensure that the services provided by the network meet the requirements put forward by the third party.

[0123] It should be noted that the application server in the embodiments of this application includes the Application Function (AF) and / or the Application Server (AS), or other devices (or functions or network elements, etc.) that can support or provide application services (or service offerings). The embodiments of this application do not limit this. For example, the application server can be a Mobile Edge Computing (MEC) node or a base station.

[0124] Network Exposure Function. The NEF can also be referred to as a network exposure device, a network exposure function entity, a network exposure function network element, a network capability exposure function entity, a network capability exposure function device, a network capability exposure function network element, or a network capability exposure device, etc. The NEF is mainly used to support the exposure of capabilities and events, such as securely exposing the services and capabilities provided by 3GPP network functions to the outside.

[0125] It should be understood that the RAN, SMF, PCF, or AF in the embodiments of this application can also be referred to as a communication device or a communication equipment, which can be a general device or a dedicated device. This application does not make specific limitations on this.

[0126] It should also be understood that the above names are only used to distinguish different functions and do not mean that these devices are separate physical devices. This application does not limit the specific forms of the above devices. For example, they can be integrated in the same physical device or can be different physical devices respectively. In actual deployment, network functions (or simply referred to as functions), network elements, or devices can be co-located. For example, the Access and Mobility Management Function network element can be co-located with the Session Management Function network element; the Session Management Function network element can be co-located with the User Plane Function network element. When two functions are co-located, the interaction between the two functions provided by the embodiments of this application becomes an internal operation of the co-located function or can be omitted.

[0127] It can be understood that the above functions can be either network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or virtualized functions instantiated on a platform (such as a cloud platform).

[0128] It should be noted that Figure 1 the naming of each device (such as AF, SMF, PCF, AMF, etc.) is just a name, and the name does not limit the functions of the device itself. In the 5G network and other future networks, the above-mentioned devices can also have other names, and this application does not make specific limitations on this. For example, in the 6G network, some or all of the above-mentioned network elements may use the terms in 5G, or may have other names, etc. This is uniformly explained here and will not be repeated below.

[0129] It should be noted that the examples mentioned in this application do not represent the best; the first, second, etc. mentioned in this application are only used to distinguish different information, messages or other objects, and do not represent an order relationship; in addition, the embodiments in this application can refer to and learn from each other, and the same or similar steps or terms will not be repeated one by one.

[0130] In the embodiments of this application, the direction from the terminal device to the application server (or the user plane function network element) is called the uplink direction. Correspondingly, the direction from the application server (or the user plane function network element) to the terminal device is called the downlink direction.

[0131] The following introduces the technical concepts related to the embodiments of this application:

[0132] 1. Semantic communication.

[0133] Compared with the traditional communication method driven by data fidelity, semantic communication is a communication method that extracts information at the semantic level from the information source to achieve "meaning preservation", which can greatly reduce the required transmission channel bandwidth. For ease of understanding, please refer to Figure 2 , Figure 2It is a schematic diagram of semantic communication. On the sending end side, first, the sending end sends the original source information generated by the source into the semantic extraction module, and the semantic extraction module generates a semantic representation sequence based on the original source information. Second, the semantic representation sequence is sent into the semantic source encoder, and the semantic source encoder performs compression coding on the semantic feature sequence. Second, the compressed semantic feature sequence is sent into the channel encoder, and the channel encoder performs channel coding processing on the semantic feature sequence; finally, the sending end transmits the semantic feature sequence that has undergone channel coding processing to the transmission channel. On the receiving end side, first, the received data (i.e., the semantic feature sequence that has undergone channel coding processing) is subjected to channel decoding (decoding can also be replaced by decoding), and then semantic decoding is performed to obtain the semantic representation sequence. Then, the semantic representation sequence is sent into the semantic recovery and reconstruction module, and finally the source data is obtained. In semantic communication, the task completion quality or semantic accuracy rate is usually used for performance evaluation. Compared with traditional communication, the sending and receiving ends of semantic communication also need to be equipped with a knowledge base, and the knowledge base includes original data samples and corresponding semantic label information. The semantic encoding and decoding module needs to use a knowledge base including a large amount of data, and trains a deep learning network on the knowledge base to fit the features of semantics, so as to efficiently extract and reconstruct semantic information.

[0134] Exemplarily, a possible scenario of semantic communication is as Figure 3 shown Figure 3 It is a schematic diagram of a semantic communication scenario. The semantic communication function is deployed on the UE and the network side, and this function supports operations such as semantic extraction, semantic encoding, semantic decoding, and semantic recovery based on a knowledge base (also known as a semantic knowledge base).

[0135] Semantic communication requires the knowledge bases of the sending end and the receiving end to match each other in order to achieve a high accuracy rate of semantic recovery. For different types of applications (such as text, pictures, or audio and video, etc.), different application scenarios (industrial manufacturing or personal entertainment, etc.), or different preferences of the sending end and the receiving end, the knowledge bases required for semantic communication between the sending and receiving ends are also different. Limited by the size of the knowledge base, obtaining the knowledge bases of each other between the sending and receiving ends requires a large communication overhead. In addition, obtaining the knowledge bases of each other between the sending and receiving ends often involves privacy issues. Due to the possible mismatch between the encoding knowledge base and / or encoding model of the sending end and the decoding knowledge base and / or decoding model of the receiving end, there is a problem of low semantic recovery accuracy rate.

[0136] Based on this, an embodiment of this application proposes a semantic communication method. The core network device sends semantic conversion mode information to the intermediate device. The semantic conversion mode information is used to indicate the semantic conversion model and / or semantic conversion knowledge base used by the intermediate device. The intermediate device is used to forward the encoded data of the sending end to the receiving end; the core network device sends semantic conversion mode information to the sending end; the core network device sends semantic conversion mode information to the receiving end. The core network device sends semantic conversion mode information to the intermediate device, the sending end, and the receiving end, so that the semantic conversion model and semantic conversion knowledge base used by the intermediate device match the semantic encoding model and semantic encoding knowledge base of the sending end, and the semantic conversion model and semantic conversion knowledge base used by the intermediate device match the semantic decoding model and semantic decoding knowledge base of the receiving end. When the semantic knowledge base or semantic model between the sending end and the receiving end does not match, the semantic recovery accuracy is improved through the semantic conversion of the intermediate device, and the semantic communication quality between the sending end and the receiving end is improved.

[0137] Next, the embodiments of this application will be introduced with reference to the accompanying drawings. First, the communication scenarios involved in the embodiments of this application will be introduced. Please refer to Figure 4 , Figure 4 which is a schematic diagram of the communication scenario involved in the embodiments of this application. The communication scenarios involved in the embodiments of this application include: 1. Peer-to-peer (P2P) mode communication scenario, that is, semantic communication between UEs. The sending-end UE and the receiving-end UE can transmit data through the Radio Access Network (RAN), Core Network (CN), and Data Network (DN); 2. Client-server (C-S) mode communication scenario, that is, semantic communication between the UE and the application server (or cloud server). The UE and the cloud server can be used as the receiving end or the sending end of each other, and data transmission is carried out through RAN and CN transmission.

[0138] The intermediate device in the embodiments of this application includes: a user plane device or an access network device. In other words, the device that performs semantic conversion processing can be a terminal device and a user plane device, or a terminal device and an access network device. For ease of understanding, please refer to Figure 6 , Figure 6This is a schematic diagram of a network protocol stack architecture in an embodiment of this application. In the embodiment of this application, the protocol layer that performs semantic conversion processing is called the semantic transformation layer (STL). Adding a protocol layer for semantic conversion processing on the core network side can be integrating the STL into the existing protocol layers of the core network, adding an independent STL on the basis of the existing protocol layers of the core network, or adding an independent semantic transformation function (STF) on the existing core network side, and this STF function executes the STL layer protocol. In one example, the STL layer can be integrated into the protocol data unit (PDU) protocol function of the UPF. In another example, the STL layer is added below the PDU layer of the UPF. Uu is the interface between the UE and the base station in the 3GPP system, and TN L2&L1 are the layer 2 (L2) and layer 1 (L1) protocols of the transport network (TN).

[0139] Adding a protocol layer for semantic conversion processing on the access network side can be integrating the STL into the existing protocol layers of the access network, adding an independent STL on the basis of the existing protocol layers of the access network, or adding an independent semantic transformation function (STF) on the existing access network side, and this STF function executes the STL layer protocol. In one example, the STF layer can be integrated into the service data adaptation protocol (SDAP) protocol function of the base station (gNB), or the STL layer is added above the SDAP layer.

[0140] In a possible implementation, the semantic conversion protocol layer (or the semantic conversion function) has the ability to perform semantic encoding and decoding across semantic knowledge bases, and the semantic conversion protocol layer (or the semantic conversion function) can perform semantic conversion on the information at the sending end. The semantic conversion protocol layer (or the semantic conversion function) on the sending end side performs semantic conversion on the information that has undergone semantic extraction and semantic encoding on the sending end side to obtain encoded information. This encoded information is information that matches the semantic decoding model and the semantic decoding knowledge base of the semantic conversion protocol layer (or the semantic conversion function) on the receiving end side, and the receiving end side can perform semantic decoding and semantic restoration on this encoded information. The semantic conversion protocol layer (or the semantic conversion function) can obtain the semantic encoding model and the semantic encoding knowledge base on the sending end side, and can also obtain the semantic decoding model and the semantic decoding knowledge base on the receiving end side. The semantic conversion protocol layer (or the semantic conversion function) on the sending end side can be deployed on the terminal device that executes the sending end function, or can be deployed on the intermediate device that provides services for the sending end, such as an access network device or a user plane device.

[0141] In another possible implementation, the semantic conversion protocol layer (or the semantic conversion function) on the sending end side is used to obtain the semantic encoding model and the semantic encoding knowledge base, and the semantic conversion protocol layer (or the semantic conversion function) on the receiving end side is used to obtain the semantic decoding model and the semantic decoding knowledge base.

[0142] Please refer to Figure 5 , Figure 5 which is a schematic flowchart of the implementation process of a semantic communication method proposed in an embodiment of this application. A semantic communication method proposed in an embodiment of this application includes:

[0143] S1. The sending end sends semantic conversion capability information to the core network device.

[0144] In step S1, the sending end sends semantic conversion capability information to the core network device, and this semantic conversion capability information is used to indicate the semantic encoding model and / or the semantic encoding knowledge base supported by the sending end. Exemplarily, the semantic conversion capability information includes any one or more of the following: the type information of the semantic encoding model, the size of the semantic encoding model, the identification information of the semantic encoding model, the type information of the semantic encoding knowledge base, the size of the semantic encoding knowledge base, or the identification information of the semantic encoding knowledge base.

[0145] Specifically, the type information of the semantic encoding knowledge base indicates the type of the semantic encoding knowledge base. The types of the semantic encoding knowledge base include, but are not limited to: a semantic encoding knowledge base for image-type data, a semantic encoding knowledge base for voice-type data, a semantic encoding knowledge base for video-type data, or a semantic encoding knowledge base for text-type data. The type information of the semantic encoding model indicates the type of the semantic encoding model. The types of the semantic encoding model include, but are not limited to: a semantic encoding model for image-type data, a semantic encoding model for voice-type data, a semantic encoding model for video-type data, or a semantic encoding model for text-type data.

[0146] The size of the semantic encoding model can be the number of parameters of the semantic encoding model or the storage space size occupied by the semantic encoding model. For example, the semantic encoding model includes 10 million parameters, or the semantic encoding model occupies 1 gigabyte (Gbytes) of storage space.

[0147] The identification information of the semantic encoding model includes, but is not limited to: an identifier (indicator, ID) or an index. Exemplarily, index 0 indicates that the semantic encoding model is "Autoencoder", and index 1 indicates that the semantic encoding model is "transformer".

[0148] The identification information of the semantic encoding knowledge base includes, but is not limited to: an identifier (indicator, ID) or an index. Exemplarily, index 3 indicates that the semantic encoding knowledge base includes the "MINIST" dataset, and index 4 indicates that the semantic encoding knowledge base includes the "CIFAR-10" dataset.

[0149] Optionally, the sender carries the semantic conversion capability information in the PDU session establishment or modification request sent to the core network device.

[0150] Exemplarily, the sender can be a terminal device or an application server. For ease of description, the terminal device on the sender side is referred to as the source terminal device.

[0151] S2. The core network device determines the semantic conversion mode information according to the semantic conversion capability information.

[0152] In step S2, the core network device determines the semantic conversion mode information according to the semantic conversion capability information reported by the sender. The semantic conversion mode information is used to indicate the semantic conversion model and / or the semantic conversion knowledge base used by the intermediate device, and the intermediate device is used to forward the encoded data of the sender to the receiver.

[0153] The semantic conversion mode information includes any one or more of the following: identification information (or index) of the semantic conversion model and identification information (or index) of the semantic conversion knowledge base.

[0154] Optionally, the semantic conversion mode information includes any one or more of the following: identification information (or index) of the semantic conversion coding model, identification information (or index) of the semantic conversion coding knowledge base, identification information (or index) of the semantic conversion decoding model corresponding to the semantic conversion coding model, and identification information (or index) of the semantic conversion decoding knowledge base.

[0155] Optionally, the semantic conversion mode information sent by the core network device to different devices may be different. For example, the semantic conversion mode information sent by the core network device to the sending end may be the identification information (or index) of the semantic coding model and / or the identification information (or index) of the semantic coding knowledge base; the semantic conversion mode information sent by the core network device to the intermediate device may be the identification information (or index) of the semantic conversion model and / or the identification information (or index) of the semantic conversion knowledge base. Or, the semantic conversion mode information sent by the core network device to the intermediate device may be the identification information (or index) of the semantic conversion coding model, the identification information (or index) of the semantic conversion coding knowledge base, the identification information (or index) of the semantic conversion decoding model, and / or the identification information (or index) of the semantic conversion decoding knowledge base; the semantic conversion mode information sent by the core network device to the receiving end may be the identification information (or index) of the semantic decoding model and / or the identification information (or index) of the semantic decoding knowledge base.

[0156] In a possible implementation, the core network device determines the semantic coding model and / or the semantic coding knowledge base supported by the sending end according to the semantic conversion capability information. Then, the core network device determines the semantic conversion model and / or the semantic conversion knowledge base that matches the semantic coding model and / or the semantic coding knowledge base. Exemplarily, the core network device may be an access and mobility management network element.

[0157] In another possible implementation, the core network device obtains the Quality of Service (QoS) requirements for semantic communication between the sender and the receiver. Then, it determines the semantic conversion mode information according to the QoS requirements for the semantic communication. The QoS requirements for the semantic communication include any one or more of the following: semantic decoding accuracy, semantic similarity, semantic clarity, guaranteed bit rate, packet transmission delay budget, or packet error rate. Exemplarily, the core network device configures one or more semantic conversion modes, and each semantic conversion mode includes the QoS for semantic communication that can be achieved by adopting the semantic conversion mode. After the core network device selects a certain semantic conversion mode, it sends the semantic conversion mode information corresponding to the semantic conversion mode to the sender, the receiver, and / or the intermediate device, so as to meet the QoS requirements for the semantic communication.

[0158] In another example, the core network device may include a session management network element. The session management network element can obtain the QoS requirements for semantic communication locally, and the session management network element can negotiate with the policy control function to obtain the QoS requirements for the semantic communication. Optionally, the QoS requirements for the semantic communication are carried in the PDU session establishment or modification request sent by the sender to the core network device.

[0159] Further, the core network device determines the semantic decoding model and / or the semantic decoding knowledge base used by the receiver according to the semantic conversion mode information, and the semantic decoding model and / or the semantic decoding knowledge base used by the receiver match the semantic conversion model and / or the semantic conversion knowledge base.

[0160] S3. The core network device sends the semantic conversion mode information to the intermediate device.

[0161] After step S2, step S3 is executed.

[0162] In step S3, the core network device sends the semantic conversion mode information to the intermediate device, and the semantic conversion mode information includes: information about the semantic conversion model, and / or, information about the semantic conversion knowledge base. Exemplarily, the information about the semantic conversion model may be the indication information of the semantic conversion model, and the information about the semantic conversion knowledge base may be the indication information of the semantic conversion knowledge base.

[0163] Since the semantic conversion model may include: a semantic conversion encoding model and a semantic conversion decoding model, and the semantic conversion knowledge base may include: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base. Therefore, the semantic conversion mode information includes any one or more of the following information: information about the semantic conversion model, information about the semantic conversion knowledge base, information about the semantic conversion encoding model, information about the semantic conversion encoding knowledge base, information about the semantic conversion decoding model, or information about the semantic conversion decoding knowledge base. Regarding the semantic conversion mode information, reference may also be made to the semantic conversion mode information described in the foregoing step S2, which will not be elaborated here.

[0164] Exemplarily, this intermediate device may be an intermediate device on the sending end side, or it may also be an intermediate device on the receiving end side. This intermediate device may further include a first intermediate device on the sending end side and a second intermediate device on the receiving end side. The intermediate device includes but is not limited to: an access network device, or a user plane device.

[0165] In one example, after receiving the semantic conversion mode information, the intermediate device processes the semantic conversion mode information by the STL layer of the intermediate device.

[0166] Exemplarily, the receiving end includes but is not limited to: a terminal device or an application server. For ease of description, the terminal device on the receiving end side is referred to as the target terminal device.

[0167] Exemplarily, the core network device includes a core network device that provides services for both the sending end and the receiving end, or may also include a source core network device that provides services for the sending end and a target core network device that provides services for the receiving end.

[0168] S4. The core network device sends the semantic conversion mode information to the sending end.

[0169] In step S4, the core network device sends the semantic conversion mode information to the sending end.

[0170] In one possible implementation, the semantic conversion mode information includes: information about the semantic conversion model, and / or, information about the semantic conversion knowledge base.

[0171] In another possible implementation, the semantic conversion mode information includes: information about the semantic encoding model, and / or, information about the semantic encoding knowledge base.

[0172] Exemplarily, the core network device sends the semantic conversion mode information to the access network device, and the access network device sends the semantic conversion mode information to the sending end. The semantic conversion mode information is carried in the Downlink control information (DCI), MAC Control Element (MAC CE), Packet Data Convergence Protocol (PDCP) control PDU, or Radio Resource Control (RRC) message.

[0173] In another example, the core network device sends a PDU session establishment response or a PDU session modification response to the sending end, and the semantic conversion mode information is carried in the PDU session establishment response or the PDU session modification response.

[0174] In one possible implementation, after step S2, step S4 is executed.

[0175] In another possible implementation, when the intermediate device includes an access network device, step S4 is executed after step S3.

[0176] S5. The core network device sends the semantic conversion mode information to the receiving end.

[0177] After step S2, step S5 is executed.

[0178] In step S5, the core network device sends the semantic conversion mode information to the receiving end.

[0179] In one possible implementation, the semantic conversion mode information includes: information on the semantic conversion model, and / or, information on the semantic conversion knowledge base. The receiving end determines the semantic decoding model corresponding to the semantic conversion model from the semantic decoding models supported by the receiving end according to the information on the semantic conversion model included in the semantic conversion mode information. Alternatively, the receiving end determines the semantic decoding knowledge base corresponding to the semantic conversion knowledge base from the semantic decoding knowledge bases supported by the receiving end according to the information on the semantic conversion knowledge base included in the semantic conversion mode information.

[0180] In another possible implementation, the semantic conversion mode information includes: information on the semantic decoding model, and / or, information on the semantic decoding knowledge base.

[0181] Exemplarily, the core network device sends the semantic conversion mode information to the access network device, and the access network device sends the semantic conversion mode information to the receiving end. The semantic conversion mode information is carried in the Downlink control information (DCI), MAC Control Element (MAC CE), Packet Data Convergence Protocol (PDCP) control PDU, or Radio Resource Control (RRC) message.

[0182] In another example, the core network device sends a PDU session establishment response or a PDU session modification response to the receiving end, and the semantic conversion mode information is carried in the PDU session establishment response or the PDU session modification response.

[0183] It should be noted that the semantic encoding model configured by the core network device for the sending end and the semantic decoding model configured by the core network device for the receiving end need to be adapted to each other. The meaning of being adapted to each other is that the semantic encoding model and the semantic decoding model can meet certain quality guarantees for semantic communication or accuracy guarantees for semantic recovery.

[0184] S6. The sending end determines the semantic encoding model and / or the semantic encoding knowledge base according to the semantic conversion mode information.

[0185] In step S6, when the semantic conversion mode information includes: information on the semantic conversion model, and / or, information on the semantic conversion knowledge base. The sending end determines the semantic encoding model corresponding to the semantic conversion model from the semantic encoding models supported by the sending end according to the information on the semantic conversion model included in the semantic conversion mode information. Or, the sending end determines the semantic encoding knowledge base corresponding to the semantic conversion knowledge base from the semantic encoding knowledge bases supported by the sending end according to the information on the semantic conversion knowledge base included in the semantic conversion mode information.

[0186] When the semantic conversion mode information includes: information on the semantic encoding model, and / or, information on the semantic encoding knowledge base. The sending end directly determines the semantic encoding model and / or the semantic encoding knowledge base according to the semantic conversion mode information.

[0187] In a possible implementation manner, the semantic encoding model is locally configured at the sending end, and the sending end determines the semantic encoding knowledge base according to the semantic conversion mode information.

[0188] In another possible implementation manner, the semantic encoding knowledge base is locally configured at the sending end, and the sending end determines the semantic encoding model according to the semantic conversion mode information.

[0189] In another possible implementation, the sender determines a semantic encoding model and a semantic encoding knowledge base according to the semantic conversion mode information.

[0190] In one example, the STL layer of the sender determines a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information.

[0191] S7. The sender encodes the source data according to the semantic encoding model and the semantic encoding knowledge base to generate first encoded data.

[0192] Step S7 is executed after step S6.

[0193] In step S7, the sender performs semantic extraction, semantic encoding, and / or source-channel joint encoding on the source data according to the semantic encoding model and the semantic encoding knowledge base to generate first encoded data.

[0194] In one example, the STL layer of the sender encodes the source data according to the semantic encoding model and the semantic encoding knowledge base to generate first encoded data.

[0195] S8. The sender sends the first encoded data to the intermediate device.

[0196] S9. The intermediate device determines a semantic conversion model and / or a semantic conversion knowledge base according to the semantic conversion mode information.

[0197] After step S3, step S9 is executed.

[0198] In step S9, in one possible implementation, the semantic conversion model is locally configured on the intermediate device, and the intermediate device determines the semantic conversion knowledge base according to the semantic conversion mode information.

[0199] In another possible implementation, the semantic conversion knowledge base is locally configured on the intermediate device, and the intermediate device determines the semantic conversion model according to the semantic conversion mode information.

[0200] In another possible implementation, the intermediate device determines a semantic conversion model and a semantic conversion knowledge base according to the semantic conversion mode information.

[0201] Further, when the semantic conversion model includes a semantic conversion encoding model and a semantic conversion decoding model, the intermediate device can also determine the semantic conversion encoding model and the semantic conversion decoding model according to the semantic conversion mode information. When the semantic conversion knowledge base includes a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base, the intermediate device can also determine the semantic conversion encoding knowledge base and the semantic conversion decoding knowledge base according to the semantic conversion mode information.

[0202] In one example, the STL layer of the intermediate device determines a semantic conversion model and / or a semantic conversion knowledge base according to the semantic conversion mode information.

[0203] S10. The intermediate device processes the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate second encoded data.

[0204] In step S10, a possible implementation is that the intermediate device performs semantic conversion processing on the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to obtain second encoded data. Specifically, the semantic conversion processing includes: first, performing semantic decoding and semantic restoration on the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate intermediate data, and then performing semantic extraction and semantic encoding on the intermediate data according to the semantic conversion model and the semantic conversion knowledge base to obtain second encoded data.

[0205] In another possible implementation, the intermediate device performs semantic decoding and semantic restoration on the first encoded data according to the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data. Then, the intermediate device performs semantic extraction and semantic encoding on the intermediate data according to the semantic conversion encoding model and the semantic conversion encoding knowledge base to obtain second encoded data.

[0206] In one example, the STL layer of the intermediate device processes the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate second encoded data.

[0207] S11. The intermediate device sends the second encoded data to the receiving end.

[0208] S12. The receiving end determines a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information.

[0209] After step S5, step S12 is executed.

[0210] In step S12, when the semantic conversion mode information includes: information of the semantic conversion model, and / or, information of the semantic conversion knowledge base. The receiving end determines the semantic decoding model corresponding to the semantic conversion model from the semantic decoding models supported by the receiving end according to the information of the semantic conversion model included in the semantic conversion mode information. Or, the receiving end determines the semantic decoding knowledge base corresponding to the semantic conversion knowledge base from the semantic decoding knowledge bases supported by the receiving end according to the information of the semantic conversion knowledge base included in the semantic conversion mode information.

[0211] When the semantic conversion mode information includes: information of the semantic decoding model, and / or, information of the semantic decoding knowledge base. The receiving end directly determines the semantic decoding model and / or the semantic decoding knowledge base according to the semantic conversion mode information.

[0212] In a possible implementation, the receiving end locally configures a semantic decoding model, and the receiving end determines a semantic decoding knowledge base according to the semantic conversion mode information.

[0213] In another possible implementation, the receiving end locally configures a semantic decoding knowledge base, and the receiving end determines a semantic decoding model according to the semantic conversion mode information.

[0214] In another possible implementation, the receiving end determines a semantic decoding model and a semantic decoding knowledge base according to the semantic conversion mode information.

[0215] In one example, the STL layer of the receiving end determines a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information.

[0216] S13. The receiving end decodes the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0217] In step S13, the receiving end performs semantic decoding, semantic recovery, and / or source-channel joint decoding processing on the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0218] In one example, the STL layer of the receiving end decodes the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0219] It should be noted that in this embodiment, the application process of the semantic communication method is introduced by taking the PDU session establishment or modification process as an example. In addition to the PDU session establishment or modification process, the semantic communication method proposed in the embodiments of the present application can also be applied to other service processes, and the embodiments of the present application do not limit this. For example, the embodiments of the present application do not limit the messages carried by the semantic conversion ability information or the semantic conversion mode information.

[0220] In the embodiments of the present application, the core network device sends semantic conversion mode information to the intermediate device, the sending end, and the receiving end, so that the semantic conversion model and the semantic conversion knowledge base used by the intermediate device match the semantic encoding model and the semantic encoding knowledge base of the sending end, and the semantic conversion model and the semantic conversion knowledge base used by the intermediate device match the semantic decoding model and the semantic decoding knowledge base of the receiving end. In the case where the semantic knowledge base or the semantic model does not match between the sending end and the receiving end, the semantic recovery accuracy is improved through semantic conversion in the intermediate device, and the semantic communication quality between the sending end and the receiving end is improved.

[0221] Combined with the foregoing embodiments, an application scenario proposed in the embodiments of the present application will be introduced next. The sending end is a source terminal device, the receiving end is a target terminal device, and the intermediate device is an access network device or a user plane device. This application scenario is asFigure 7 As shown. Please refer to Figure 7 , Figure 7 which is a schematic flowchart of an embodiment of a semantic communication method proposed in an embodiment of this application. A semantic communication method proposed in an embodiment of this application includes:

[0222] D1. The source terminal device sends semantic conversion capability information to the core network device.

[0223] Step D1 is similar to the foregoing step S1 and will not be elaborated here.

[0224] D2. The core network device determines semantic conversion mode information according to the semantic conversion capability information.

[0225] Step D2 is similar to the foregoing step S2 and will not be elaborated here.

[0226] D3. The core network device sends the semantic conversion mode information to the access network device or the user plane device.

[0227] Step D3 is similar to the foregoing step S3 and will not be elaborated here.

[0228] D4. The core network device sends the semantic conversion mode information to the source terminal device.

[0229] Step D4 is similar to the foregoing step S4 and will not be elaborated here.

[0230] D5. The core network device sends the semantic conversion mode information to the target terminal device.

[0231] Step D5 is similar to the foregoing step S5 and will not be elaborated here.

[0232] D6. The source terminal device determines a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information.

[0233] Step D6 is similar to the foregoing step S6 and will not be elaborated here.

[0234] D7. The source terminal device encodes the source data according to the semantic encoding model and the semantic encoding knowledge base to generate first encoded data.

[0235] Step D7 is similar to the foregoing step S7 and will not be elaborated here.

[0236] D8. The source terminal device sends the first encoded data to the access network device or the user plane device.

[0237] Step D8 is similar to the foregoing step S8 and will not be elaborated here.

[0238] D9. The access network device or the user plane device determines a semantic conversion model and / or a semantic conversion knowledge base according to the semantic conversion mode information.

[0239] Step D9 is similar to the foregoing step S9 and will not be elaborated here.

[0240] D10. The access network device or the user plane device processes the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate second encoded data.

[0241] Step D10 is similar to the foregoing step S10 and will not be elaborated here.

[0242] D11. The access network device or the user plane device sends the second encoded data to the target terminal device.

[0243] Step D11 is similar to the foregoing step S11 and will not be elaborated here.

[0244] D12. The target terminal device determines a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information.

[0245] Step D12 is similar to the foregoing step S12 and will not be elaborated here.

[0246] D13. The target terminal device decodes the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0247] Step D13 is similar to the foregoing step S13 and will not be elaborated here.

[0248] Combined with the foregoing embodiments, an application scenario proposed by the embodiments of the present application will be introduced next. The sending end is the source terminal device, the receiving end is the target terminal device, and the intermediate devices include a first intermediate device providing services for the sending end and a second intermediate device providing services for the receiving end. Among them, the first intermediate device includes a source access network device or a source user plane device, and the second intermediate device includes a target access network device or a target user plane device. The core network device includes a source core network device providing services for the sending end or the first intermediate device, and a target core network device providing services for the receiving end or the second intermediate device. It can be understood that the source core network device and the target core network device may be the same device or two independent devices. This application scenario is as Figure 8 shown. Please refer to Figure 8 , Figure 8 , which is a schematic flowchart of the implementation process of a semantic communication method proposed by the embodiments of the present application. A semantic communication method proposed by the embodiments of the present application includes:

[0249] F1. The source terminal device sends semantic conversion capability information to the source core network device.

[0250] Step F1 is similar to the foregoing step S1 and will not be elaborated here.

[0251] Optionally, the target terminal device may also send semantic conversion capability information to the target core network device.

[0252] F2. The source core network device and the target core network device determine semantic conversion mode information based on the semantic conversion capability information.

[0253] In step F2, first, a set of semantic conversion mode information that can be supported by both the source terminal device and the target terminal device is pre-configured between the source core network device and the target core network device. The set of semantic conversion mode information includes: indexes or identification information of one or more semantic mode information, and each semantic mode information corresponds to a set of association relationships, and the association relationships include: semantic conversion encoding model, semantic conversion encoding knowledge base, semantic conversion decoding model, and semantic conversion decoding knowledge base. For example, the semantic mode information includes indexes or identification information of the semantic conversion encoding model, indexes or identification information of the semantic conversion encoding knowledge base, indexes or identification information of the semantic conversion decoding model, and indexes or identification information of the semantic conversion decoding knowledge base.

[0254] Exemplarily, the semantic mode information of the source core network device includes: information of the semantic conversion encoding model and information of the semantic conversion encoding knowledge base. The semantic mode information of the source core network device may also include: information of the semantic encoding model and information of the semantic encoding knowledge base. The semantic mode information of the target core network device includes: information of the semantic conversion decoding model and information of the semantic conversion decoding knowledge base. The semantic mode information of the target core network device may also include: information of the semantic decoding model and information of the semantic decoding knowledge base.

[0255] Secondly, the source core network device determines, according to the semantic conversion capability information of the source terminal device, the semantic conversion mode information that matches the semantic conversion capability information of the source terminal device from the set of semantic conversion mode information, and notifies the semantic conversion mode information to the target core network device.

[0256] Optionally, the source core network device may also notify multiple candidate semantic conversion mode information to the target core network device. The multiple candidate semantic conversion mode information sent by the source core network device to the target core network device includes any one or more of the following: information of the semantic conversion encoding model, information of the semantic conversion encoding knowledge base, information of the semantic encoding model, information of the semantic encoding knowledge base, information of the semantic conversion decoding model, information of the semantic conversion decoding knowledge base, information of the semantic decoding model, or information of the semantic decoding knowledge base.

[0257] The target core network device queries the local semantic conversion mode information set according to the received semantic conversion mode information, determines the semantic conversion mode information that matches the semantic conversion capability information of the target terminal device, and replies with a confirmation message to the source core network device. This confirmation message indicates that the target core network device agrees to use the semantic conversion decoding model and / or semantic conversion decoding knowledge base indicated by this semantic conversion mode information. Optionally, if the source core network device sends multiple candidate semantic conversion mode information to the target core network device, the target core network device determines the semantic conversion mode information to be used from the multiple candidate semantic conversion mode information, and then the confirmation message sent by the target core network device to the source core network device includes the semantic conversion mode information determined by the target core network device to be used.

[0258] In another possible implementation, if the source core network device and the target core network device are the same core network device, step F2 may not be executed, and the core network device sends the semantic conversion mode information to the first intermediate device, the source terminal device, the second intermediate device, and the target terminal device respectively.

[0259] F3. The source core network device sends the semantic conversion mode information to the first intermediate device.

[0260] Step F3 is similar to the foregoing step S3 and will not be elaborated here.

[0261] In step F3, in one possible implementation, the semantic conversion mode information sent by the source core network device to the first intermediate device includes the indication information (or index) of the semantic conversion decoding model, and / or the indication information (or index) of the semantic conversion decoding knowledge base.

[0262] F4. The source core network device sends the semantic conversion mode information to the source terminal device.

[0263] Step F4 is similar to the foregoing step S4 and will not be elaborated here.

[0264] F5. The target core network device sends the semantic conversion mode information to the second intermediate device.

[0265] Step F5 is similar to the foregoing step S3 and will not be elaborated here.

[0266] In step F5, in one possible implementation, the semantic conversion mode information sent by the target core network device to the second intermediate device includes the indication information (or index) of the semantic conversion encoding model, and / or the indication information (or index) of the semantic conversion encoding knowledge base.

[0267] F6. The target core network device sends the semantic conversion mode information to the target terminal device.

[0268] Step F6 is similar to the foregoing step S5 and will not be elaborated here.

[0269] F7. The source terminal device determines a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information.

[0270] Step F7 is similar to the foregoing step S6 and will not be elaborated here.

[0271] F8. The source terminal device encodes the source data according to the semantic encoding model and the semantic encoding knowledge base to generate first encoded data.

[0272] Step F8 is similar to the foregoing step S7 and will not be elaborated here.

[0273] F9. The source terminal device sends the first encoded data to the first intermediate device.

[0274] F10. The first intermediate device determines a semantic conversion decoding model and / or a semantic conversion decoding knowledge base according to the semantic conversion mode information.

[0275] Step F10 is similar to the foregoing step S9 and will not be elaborated here.

[0276] F11. The first intermediate device decodes the first encoded data according to the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data.

[0277] In step F11, the first intermediate device performs semantic decoding and semantic restoration on the first encoded data according to the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data.

[0278] F12. The first intermediate device sends the intermediate data to the second intermediate device.

[0279] F13. The second intermediate device determines a semantic conversion encoding model and / or a semantic conversion encoding knowledge base according to the semantic conversion mode information.

[0280] F14. The second intermediate device encodes the intermediate data according to the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate second encoded data.

[0281] In step F14, the intermediate device performs semantic extraction and semantic encoding on the intermediate data according to the semantic conversion encoding model and the semantic conversion encoding knowledge base to obtain second encoded data.

[0282] F15. The second intermediate device sends the second encoded data to the target terminal device.

[0283] F16. The target terminal device determines a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information.

[0284] F17. The target terminal device decodes the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0285] Steps F16 - F17 are similar to the aforementioned steps S12 - S13, and will not be elaborated here.

[0286] Combined with the foregoing embodiments, the following introduces an application scenario proposed by the embodiments of the present application. The sending end is a terminal device, the receiving end is an application server, and the intermediate device includes an access network device or a user plane device. The intermediate device performs semantic conversion of data in the uplink direction, which refers to the direction from the terminal device to the application server. This application scenario is as Figure 9 shown. Please refer to Figure 9 , Figure 9 which is a schematic flowchart of the implementation process of a semantic communication method proposed by the embodiments of the present application. A semantic communication method proposed by the embodiments of the present application includes:

[0287] G1. The terminal device sends semantic conversion capability information to the core network device.

[0288] G2. The core network device determines semantic conversion mode information according to the semantic conversion capability information.

[0289] In step G2, the core network device determines the uplink semantic conversion mode information from the terminal device to the application server according to the semantic conversion capability information reported by the terminal device. The uplink semantic conversion mode information includes: information on the semantic encoding model for uplink semantic conversion, information on the semantic encoding knowledge base for uplink semantic conversion, information on the semantic decoding model for uplink semantic conversion, information on the semantic decoding knowledge base for uplink semantic conversion, information on the semantic conversion decoding model for uplink semantic conversion, information on the semantic conversion decoding knowledge base for uplink semantic conversion, information on the semantic conversion encoding model for uplink semantic conversion, and / or information on the semantic conversion encoding knowledge base for uplink semantic conversion.

[0290] G3. The core network device sends the semantic conversion mode information to the access network device or the user plane device.

[0291] G4. The core network device sends the semantic conversion mode information to the terminal device.

[0292] Exemplarily, the uplink semantic conversion mode information sent by the core network device to the terminal device includes: the information on the semantic decoding model for uplink semantic conversion, and / or the information on the semantic decoding knowledge base for uplink semantic conversion.

[0293] G5. The core network device sends the semantic conversion mode information to the application server.

[0294] Exemplarily, the uplink semantic conversion mode information sent by the core network device to the application server includes: information on the semantic encoding model for uplink semantic conversion, and / or information on the semantic encoding knowledge base for uplink semantic conversion.

[0295] G6. The terminal device determines a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information.

[0296] G7. The terminal device encodes the source data according to the semantic encoding model and the semantic encoding knowledge base to generate first encoded data.

[0297] G8. The terminal device sends the first encoded data to the access network device or the user plane device.

[0298] G9. The access network device or the user plane device determines a semantic conversion model and / or a semantic conversion knowledge base according to the semantic conversion mode information.

[0299] G10. The access network device or the user plane device processes the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate second encoded data.

[0300] G11. The access network device or the user plane device sends the second encoded data to the application server.

[0301] G12. The application server determines a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information.

[0302] G13. The application server decodes the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0303] Steps G1 - G13 are similar to the aforementioned steps S1 - S13, and will not be elaborated here.

[0304] Combined with the foregoing embodiments, the following introduces an application scenario proposed by the embodiments of the present application. The sending end is the application server, the receiving end is the terminal device, and the intermediate device includes the access network device or the user plane device. The intermediate device performs semantic conversion of the data in the downlink direction, and this downlink direction refers to the direction from the application server to the terminal device. This application scenario is as Figure 10 shown. Please refer to Figure 10 , Figure 10 which is a schematic flowchart of the implementation process of a semantic communication method proposed by the embodiments of the present application. A semantic communication method proposed by the embodiments of the present application includes:

[0305] H1. The application server sends semantic conversion capability information to the core network device.

[0306] H2. The core network device determines the semantic conversion mode information according to the semantic conversion capability information.

[0307] In step H2, the core network device determines the downlink semantic conversion mode information from the application server to the terminal device according to the semantic conversion capability information reported by the application server. The downlink semantic conversion mode information includes: information on the semantic encoding model for downlink semantic conversion, information on the semantic encoding knowledge base for downlink semantic conversion, information on the semantic decoding model for downlink semantic conversion, information on the semantic decoding knowledge base for downlink semantic conversion, the semantic conversion decoding model for downlink semantic conversion, the semantic conversion decoding knowledge base for downlink semantic conversion, the semantic conversion encoding model for downlink semantic conversion, and / or the semantic conversion encoding knowledge base for downlink semantic conversion.

[0308] H3. The core network device sends the semantic conversion mode information to the access network device or the user plane device.

[0309] H4. The core network device sends the semantic conversion mode information to the application server.

[0310] Exemplarily, the downlink semantic conversion mode information sent by the core network device to the application server includes: the information on the semantic decoding model for downlink semantic conversion, and / or the information on the semantic decoding knowledge base for downlink semantic conversion.

[0311] H5. The core network device sends the semantic conversion mode information to the terminal device.

[0312] Exemplarily, the downlink semantic conversion mode information sent by the core network device to the terminal device includes: the information on the semantic encoding model for downlink semantic conversion, and / or the information on the semantic encoding knowledge base for downlink semantic conversion.

[0313] H6. The application server determines the semantic encoding model and / or the semantic encoding knowledge base according to the semantic conversion mode information.

[0314] H7. The application server encodes the source data according to the semantic encoding model and the semantic encoding knowledge base to generate the first encoded data.

[0315] H8. The application server sends the first encoded data to the access network device or the user plane device.

[0316] H9. The access network device or the user plane device determines the semantic conversion model and / or the semantic conversion knowledge base according to the semantic conversion mode information.

[0317] H10. The access network device or the user plane device processes the first encoded data according to the semantic conversion model and the semantic conversion knowledge base to generate the second encoded data.

[0318] H11. The access network device or the user plane device sends the second encoded data to the terminal device.

[0319] H12. The terminal device determines a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information.

[0320] H13. The terminal device decodes the second encoded data according to the semantic decoding model and the semantic decoding knowledge base to generate target data.

[0321] Steps H1 - H13 are similar to the foregoing steps S1 - S13 and will not be elaborated here.

[0322] It should be noted that Figure 9 the illustrated embodiments and Figure 10 the illustrated embodiments can be combined. In other words, the core network device determines the semantic conversion mode information for uplink semantic conversion according to the semantic conversion capability information reported by the terminal device; the core network device determines the semantic conversion mode information for downlink semantic conversion according to the semantic conversion capability information reported by the application server. Then, the intermediate device performs semantic conversion in the uplink direction according to the semantic conversion mode information for uplink semantic conversion, and performs semantic conversion in the downlink direction according to the semantic conversion mode information for downlink semantic conversion.

[0323] The above describes the present application from the perspective of the method. The following will further describe other embodiments provided by the present application.

[0324] Please refer to Figure 11 , which is a schematic diagram of an implementation of the communication device provided by the present application. The communication device 1100 includes a processing module 1101 and a transceiver module 1102. The communication device 1100 can implement the functions of the communication device (including the sending end, the intermediate device, the core network device, and / or the receiving end, etc.) in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the communication device 1100 can be the sending end, the intermediate device, the core network device, and / or the receiving end, or can also be an integrated circuit or component inside the sending end, the intermediate device, the core network device, and / or the receiving end, such as a chip, or can also be an integrated circuit or component integrating the inside of the sending end, the intermediate device, the core network device, and / or the receiving end.

[0325] Please refer to Figure 12 , which is another schematic structural diagram of the communication device 1200 provided by the present application. The communication device 1200 at least includes an input / output interface 1202. Among them, the communication device 1200 can be a chip or an integrated circuit.

[0326] Optionally, the communication device further includes a logic circuit 1201.

[0327] Among them, Figure 11 the transceiver module 1102 shown can be a communication interface, and this communication interface can be Figure 12 the input / output interface 1202 in [reference], and this input / output interface 1202 can include an input interface and an output interface. Alternatively, this communication interface can also be a transceiver circuit, and this transceiver circuit can include an input interface circuit and an output interface circuit.

[0328] Optionally, when the communication device 1200 is the sending end, intermediate device, core network device, and / or receiving end in the foregoing embodiments, the input / output interface 1202 is used to input and output information; the logic circuit 1201 is used to execute the methods executed by the sending end, intermediate device, core network device, and / or receiving end in the foregoing embodiments.

[0329] Among them, the logic circuit 1201 and the input / output interface 1202 can also execute other steps executed by the communication device in any embodiment and achieve the corresponding beneficial effects, which will not be elaborated here.

[0330] In a possible implementation manner, Figure 11 the processing module 1101 shown can be Figure 12 the logic circuit 1201 in [reference].

[0331] Optionally, the logic circuit 1201 can be a processing device, and the functions of the processing device can be implemented partially or entirely by software. Among them, the functions of the processing device can be implemented partially or entirely by software.

[0332] Optionally, the processing device can include a memory and a processor. Among them, the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to execute the corresponding processing and / or steps in any method embodiment.

[0333] Optionally, the processing device can only include a processor. The memory for storing the computer program is located outside the processing device, and the processor is connected to the memory through a circuit / wire to read and execute the computer program stored in the memory. Among them, the memory and the processor can be integrated together, or they can also be physically independent of each other.

[0334] Optionally, the processing device may be one or more chips or one or more integrated circuits. For example, the processing device may be one or more field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), system on chips (SoCs), central processor units (CPUs), network processors (NPs), digital signal processing circuits (DSPs), microcontroller units (MCUs), programmable logic devices (PLDs), or other integrated chips, or any combination of the above chips or processors, etc.

[0335] Please refer to Figure 13 , for the communication device 1300 involved in the above embodiments provided by the embodiments of the present application. The communication device 1300 may specifically be the communication device acting as a sending end, an intermediate device, a core network device, and / or a receiving end in the above embodiments.

[0336] Among them, a possible schematic logical structure diagram of the communication device 1300. The communication device 1300 may include but is not limited to at least one processor 1301 and a communication port 1302.

[0337] Further optionally, the device may further include at least one of a memory 1303 and a bus 1304. In the embodiments of the present application, the at least one processor 1301 is used to control and process the actions of the communication device 1300.

[0338] In addition, the processor 1301 may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of the present application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on. Those skilled in the art can clearly understand that for the sake of convenience and brevity of description, the specific working processes of the systems, devices, and units described above may refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0339] It should be noted that Figure 13The communication device 1300 shown can be specifically used to implement the steps implemented by the sending end, intermediate device, core network device, and / or receiving end in the foregoing method embodiments, and achieve the corresponding technical effects of the sending end, intermediate device, core network device, and / or receiving end. Figure 13 For the specific implementation manners of the communication device shown, reference can be made to the descriptions in the foregoing method embodiments, and details are not described herein one by one.

[0340] Please refer to Figure 14 , which is a schematic structural diagram of the communication device 1400 involved in the foregoing embodiments provided in the embodiments of the present application. The communication device 1400 can specifically be the communication device acting as the sending end, intermediate device, core network device, and / or receiving end in the foregoing embodiments. Among them, the structure of the communication device can refer to Figure 14 the structure shown.

[0341] The communication device 1400 includes at least one processor 1401 and at least one network interface 1404. Further optionally, the communication device further includes at least one memory 1402, at least one transceiver 1403, and one or more antennas 1405. The processor 1401, the memory 1402, the transceiver 1403, and the network interface 1404 are connected, for example, connected by a bus. In the embodiments of the present application, this connection can include various interfaces, transmission lines, or buses, etc., and this embodiment does not limit this. The antenna 1405 is connected to the transceiver 1403. The network interface 1404 is used to enable the communication device to communicate with other communication devices through a communication link. For example, the network interface 1404 can include a network interface between the communication device and the core network device, such as an S1 interface, and the network interface can include a network interface between the communication device and other communication devices (such as other radio access networks or core network devices), such as an X2 or Xn interface.

[0342] The processor 1401 is mainly used to process communication protocols and communication data, and control the entire communication device, execute software programs, and process the data of the software programs, for example, to support the communication device to perform the actions described in the embodiments. The communication device can include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data, and the central processing unit is mainly used to control the entire terminal device, execute software programs, and process the data of the software programs. Figure 14The processor 1401 therein may integrate the functions of a baseband processor and a central processor. Those skilled in the art can understand that the baseband processor and the central processor may also be separate processors, interconnected through technologies such as a bus. Those skilled in the art can understand that the terminal device may include multiple baseband processors to adapt to different network standards, and the terminal device may include multiple central processors to enhance its processing capabilities. Each component of the terminal device may be connected through various buses. The baseband processor may also be referred to as a baseband processing circuit or a baseband processing chip. The central processor may also be referred to as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data may be built into the processor or stored in the memory in the form of a software program, and the processor executes the software program to implement the baseband processing function.

[0343] The memory is mainly used to store software programs and data. The memory 1402 may exist independently and be connected to the processor 1401. Optionally, the memory 1402 may be integrated with the processor 1401, for example, integrated within a single chip. Among them, the memory 1402 can store the program code for implementing the technical solution of the embodiments of the present application and be controlled by the processor 1401 for execution. Various types of computer program codes being executed can also be regarded as the driver programs of the processor 1401.

[0344] Figure 14 Only one memory and one processor are shown. In an actual terminal device, there may be multiple processors and multiple memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element. The embodiments of the present application do not make any limitations in this regard.

[0345] The transceiver 1403 can be used to support the reception or transmission of radio frequency signals between the communication device and the terminal. The transceiver 1403 can be connected to the antenna 1405. The transceiver 1403 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1405 can receive radio frequency signals. The receiver Rx of the transceiver 1403 is used to receive the radio frequency signals from the antenna, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 1401 so that the processor 1401 can further process the digital baseband signals or digital intermediate frequency signals, such as demodulation processing and decoding processing. In addition, the transmitter Tx in the transceiver 1403 is also used to receive the modulated digital baseband signals or digital intermediate frequency signals from the processor 1401, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 1405. Specifically, the receiver Rx can selectively perform one-stage or multi-stage down-conversion processing and analog-to-digital conversion processing on the radio frequency signals to obtain digital baseband signals or digital intermediate frequency signals, and the order of the down-conversion processing and the analog-to-digital conversion processing can be adjusted. The transmitter Tx can selectively perform one-stage or multi-stage up-conversion processing and digital-to-analog conversion processing on the modulated digital baseband signals or digital intermediate frequency signals to obtain radio frequency signals, and the order of the up-conversion processing and the digital-to-analog conversion processing can be adjusted. The digital baseband signals and the digital intermediate frequency signals can be collectively referred to as digital signals.

[0346] The transceiver 1403 can also be referred to as a transceiver module, a transceiver, a transceiver device, etc. Optionally, the devices used to implement the receiving function in the transceiver module can be regarded as the receiving unit, and the devices used to implement the sending function in the transceiver module can be regarded as the sending unit. That is, the transceiver module includes a receiving unit and a sending unit. The receiving unit can also be referred to as a receiver, an input port, a receiving circuit, etc., and the sending unit can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0347] It should be noted that Figure 14 The illustrated communication device 1400 can specifically be used to implement the steps implemented by the sending end, the intermediate device, the core network device, and / or the receiving end in the foregoing method embodiments, and achieve the corresponding technical effects of the sending end, the intermediate device, the core network device, and / or the receiving end. Figure 14 For the specific implementation manners of the illustrated communication device 1400, reference can be made to the descriptions in the foregoing method embodiments, and details are not described herein one by one.

[0348] The embodiment of the present application further provides a computer-readable storage medium storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor executes the method in the possible implementation manners of the sending end, the intermediate device, the core network device, and / or the receiving end in the foregoing embodiments.

[0349] The embodiments of the present application further provide a computer program product (or computer program) for storing one or more computers. When the computer program product is executed by the processor, the processor executes the methods of the possible implementation manners of the foregoing sending end, intermediate device, core network device, and / or receiving end.

[0350] The embodiments of the present application further provide a chip system. The chip system includes at least one processor, which is used to support a communication device to implement the functions involved in the possible implementation manners of the foregoing communication device. Optionally, the chip system further includes an interface circuit, and the interface circuit provides program instructions and / or data for the at least one processor. In a possible design, the chip system may further include a memory, which is used to store the necessary program instructions and data of the communication device. The chip system may be composed of chips, or may include chips and other discrete devices. Among them, the communication device may specifically be the sending end, intermediate device, core network device, and / or receiving end in the foregoing method embodiments.

[0351] The embodiments of the present application further provide a communication system, which includes the sending end, intermediate device, core network device, and / or receiving end in any of the foregoing embodiments.

[0352] In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other may be through some interfaces. The indirect coupling or communication connection of the device or unit may be in an electrical, mechanical, or other form.

[0353] The unit described as a separated component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0354] In addition, each functional unit in various embodiments of the present application may be integrated into a processing module, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that makes a contribution, or all or part of the technical solution, may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a radio access network, etc.) to execute all or part of the steps of the method in various embodiments of the present application. The foregoing storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc that can store program codes.

Claims

1. A semantic communication method, characterized in that, The method is applied to a core network device, and the method includes: Sending semantic conversion mode information to an intermediate device, where the semantic conversion mode information is used to indicate the semantic conversion model and / or semantic conversion knowledge base used by the intermediate device, and the intermediate device is used to forward the encoded data of a sending end to a receiving end; Sending the semantic conversion mode information to the sending end; Sending the semantic conversion mode information to the receiving end.

2. The method according to claim 1, characterized in that, The method further includes: Receiving semantic conversion capability information of the sending end, where the semantic conversion capability information is used to indicate the semantic encoding model and / or semantic encoding knowledge base supported by the sending end; Determining the semantic conversion mode information according to the semantic conversion capability information of the sending end, where the semantic conversion model matches the semantic encoding model supported by the sending end, and the semantic conversion knowledge base matches the semantic encoding knowledge base supported by the sending end.

3. The method according to claim 1, characterized in that, The method further includes: Determining the semantic conversion mode information according to the quality of service requirements of semantic communication between the sending end and the receiving end, where the quality of service requirements of the semantic communication include any one or more of the following: Semantic decoding accuracy, semantic similarity, semantic clarity, guaranteed bit rate, packet transmission delay budget, or packet error rate.

4. The method according to any one of claims 1-3, characterized in that, The semantic conversion model includes: a semantic conversion encoding model and a semantic conversion decoding model, The semantic conversion knowledge base includes: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base.

5. The method according to claim 4, characterized in that, The semantic conversion mode information includes any one or more of the following information: Information about the semantic conversion model, information about the semantic conversion knowledge base, information about the semantic conversion encoding model, information about the semantic conversion encoding knowledge base, information about the semantic conversion decoding model, or information about the semantic conversion decoding knowledge base.

6. The method according to any one of claims 2-5, characterized in that, The semantic conversion capability information includes any one or more of the following: Type information of the semantic encoding model, size of the semantic encoding model, identification information of the semantic encoding model, type information of the semantic encoding knowledge base, size of the semantic encoding knowledge base, or identification information of the semantic encoding knowledge base.

7. A semantic communication method, characterized in that, The method is applied to an intermediate device, and the method includes: Receiving semantic conversion mode information sent by a core network device, where the semantic conversion mode information is used to indicate the semantic conversion model and / or semantic conversion knowledge base used by the intermediate device; Determining the semantic conversion model and / or the semantic conversion knowledge base according to the semantic conversion mode information; Receiving first encoded data sent by a sending end, where the first encoded data is data encoded by the sending end using a semantic encoding model and / or a semantic encoding knowledge base; Processing the first encoded data using the semantic conversion model and the semantic conversion knowledge base to obtain second encoded data; Sending the second encoded data to a receiving end.

8. The method according to claim 7, characterized in that, The semantic conversion model includes: a semantic conversion encoding model and a semantic conversion decoding model, The semantic conversion knowledge base includes: a semantic conversion encoding knowledge base and a semantic conversion decoding knowledge base.

9. The method according to claim 8, characterized in that, The semantic conversion mode information includes any one or more of the following information: Information of the semantic conversion model, information of the semantic conversion knowledge base, information of the semantic conversion encoding model, information of the semantic conversion encoding knowledge base, information of the semantic conversion decoding model, or information of the semantic conversion decoding knowledge base.

10. The method according to claim 8 or 9, characterized in that, Processing the first encoded data by using the semantic conversion model and the semantic conversion knowledge base to obtain the second encoded data, including: Performing decoding processing on the first encoded data by using the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data; Performing encoding processing on the intermediate data by using the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate the second encoded data.

11. The method according to claim 8 or 9, characterized in that, The intermediate device includes a first intermediate device and a second intermediate device. Among them, the first intermediate device provides services for the sending end, and the second intermediate device provides services for the receiving end. Processing the first encoded data by using the semantic conversion model and the semantic conversion knowledge base to obtain the second encoded data, including: The first intermediate device performs decoding processing on the first encoded data by using the semantic conversion decoding model and the semantic conversion decoding knowledge base to generate intermediate data; The first intermediate device sends the intermediate data to the second intermediate device; The second intermediate device performs encoding processing on the intermediate data by using the semantic conversion encoding model and the semantic conversion encoding knowledge base to generate the second encoded data; Sending the second encoded data to the receiving end, including: The second intermediate device sends the second encoded data to the receiving end.

12. A semantic communication method, characterized in that, The method is applied to the sending end, and the method includes: Receiving semantic conversion mode information sent by the core network device, where the semantic conversion mode information is used to indicate the semantic conversion model and / or semantic conversion knowledge base used by the intermediate device, and the intermediate device is used to forward the encoded data of the sending end to the receiving end; Determining a semantic encoding model and / or a semantic encoding knowledge base according to the semantic conversion mode information, where the semantic encoding model matches the semantic conversion model, and the semantic encoding knowledge base matches the semantic conversion knowledge base; Performing encoding processing on the source data by using the semantic encoding knowledge base and the semantic encoding knowledge base to generate the first encoded data; Sending the first encoded data to the intermediate device.

13. The method according to claim 12, characterized in that, The method further includes: Sending semantic conversion capability information to the core network device, where the semantic conversion capability information is used to indicate the semantic encoding model and / or semantic encoding knowledge base supported by the sending end.

14. The method according to claim 13, characterized in that, The semantic conversion capability information includes any one or more of the following: Type information of the semantic encoding model, size of the semantic encoding model, identification information of the semantic encoding model, type information of the semantic encoding knowledge base, size of the semantic encoding knowledge base, or identification information of the semantic encoding knowledge base.

15. A semantic communication method, characterized in that, The method is applied to the receiving end, and the method includes: Receive the semantic conversion mode information sent by the core network device, where the semantic conversion mode information is used to indicate the semantic conversion model and / or semantic conversion knowledge base used by the intermediate device, and the intermediate device is used to forward the encoded data of the sending end to the receiving end; Determine a semantic decoding model and / or a semantic decoding knowledge base according to the semantic conversion mode information, where the semantic decoding model matches the semantic conversion model, and the semantic decoding knowledge base matches the semantic conversion knowledge base; Receive the second encoded data sent by the intermediate device; Use the semantic decoding knowledge base and the semantic decoding knowledge base to perform decoding processing on the second encoded data to generate target data.

16. The method according to claim 15, characterized in that, The semantic conversion mode information includes any one or more of the following information: Information about the semantic conversion model, information about the semantic conversion knowledge base, information about the semantic conversion encoding model, information about the semantic conversion encoding knowledge base, information about the semantic conversion decoding model, or information about the semantic conversion decoding knowledge base.

17. A communication device, characterized in that, Includes a communication interface and a processor: The communication interface is used for inputting and / or outputting signaling or data; The processor is used to execute computer-executable programs, so that the method described in any one of claims 1-6 is executed, or the method described in any one of claims 7-11 is executed, or the method described in any one of claims 12-14 is executed, or the method described in any one of claims 15-16 is executed.

18. A communication device, characterized in that, Includes a processor and a memory, The memory is used to store computer programs or instructions; The processor is used to execute the computer program or instructions in the memory, so that the method described in any one of claims 1-6 is executed, or the method described in any one of claims 7-11 is executed, or the method described in any one of claims 12-14 is executed, or the method described in any one of claims 15-16 is executed.

19. A computer-readable storage medium, comprising instructions, characterized in that, When the instruction is executed by the processor, the method described in any one of claims 1-6, or claims 7-11, or claims 12-14, or claims 15-16 is implemented.

20. A computer program product, comprising a program, characterized in that, When the program is executed by the processor, the method described in any one of claims 1-6, or claims 7-11, or claims 12-14, or claims 15-16 is implemented.

21. A chip system, characterized in that, The chip system includes at least one processor. When the program instructions are executed in the at least one processor, the method described in any one of claims 1-6, or claims 7-11, or claims 12-14, or claims 15-16 is implemented.

22. A communication system, characterized in that, Includes a communication device for executing the method described in any one of claims 1-6, a communication device for executing the method described in any one of claims 7-11, a communication device for executing the method described in any one of claims 12-14, and a communication device for executing the method described in any one of claims 15-16.

Images