Information transmission method, lightweight processing method and related communication device

Abstract

The present application provides a method for information transmission, a method for lightweight processing, and a related communication device, which are applicable to the field of communications. The method determines policy information based on uplink channel state information. The lightweight method and lightweight policy configuration determined by the policy information meet the uplink transmission capability, thereby reducing the loss of model accuracy and improving transmission efficiency. The method includes: a network device receives a first notification message sent by a terminal device, the first notification message is used to indicate that the terminal device has completed training of a target model, the first notification message includes a model name corresponding to the target model, and then determines policy information based on the uplink channel state information of the terminal device, the policy information is used for the terminal device to determine the lightweight method and lightweight policy configuration, and further, the network device sends a lightweight indication message to the terminal device, the lightweight indication message includes the model name corresponding to the target model and policy information.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a method for information transmission, a method for lightweight processing, and related communication devices. Background Art

[0002] Federated learning is an encrypted, distributed machine learning technology that fully leverages the data and computing power of participating parties, enabling multiple parties to collaboratively build universal, robust machine learning models without sharing data. Amidst increasingly stringent data regulations, federated learning can address key issues such as data ownership, data privacy, data access rights, and access to heterogeneous data. In wireless scenarios, federated learning can be used to train models to ensure data security or reduce information transmission.

[0003] Currently, to reduce communication overhead, after completing local model training, the user equipment (UE) selects a lightweight method and lightweight policy configuration from among its supported lightweight methods based on certain criteria to perform lightweight processing on the local model before uploading the model parameter information. The selected lightweight method can be directly applied without restoring the lightweight model parameter information.

[0004] However, when the uplink transmission rate is high, if the UE adopts a lightweight method and lightweight strategy configuration with a higher compression rate, the model accuracy will suffer a lot of loss, resulting in a decrease in accuracy after aggregation. Secondly, when the uplink transmission rate is low, if the UE adopts a lightweight method and lightweight strategy configuration with a lower compression rate, the amount of model parameter information transmitted is too large, which may lead to a waste of transmission resources and reduce transmission efficiency. Summary of the Invention

[0005] The embodiments of the present application provide a method for information transmission, a method for lightweight processing, and related communication devices, which are used to reduce the loss of model accuracy and improve transmission efficiency.

[0006] In the first aspect, the present application provides a method for information transmission. The method can be executed by a network device, or it can be executed by a chip configured in the network device, and the present application does not limit this. The method includes: the network device receives a first notification message sent by a terminal device, the first notification message is used to indicate that the terminal device has completed the training of the target model, the first notification message includes the model name corresponding to the target model, and then the network device determines the policy information based on the uplink channel state information of the terminal device, the policy information is used for the terminal device to determine the lightweight method and lightweight policy configuration, and finally the network device sends a lightweight indication message to the terminal device, the lightweight indication message includes the model name corresponding to the target model and the policy information, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

[0007] In this embodiment, since the policy information is determined based on the uplink channel state information, the lightweight method and lightweight policy configuration determined by the terminal device through the policy information are in line with the uplink transmission capability of the terminal device, thereby reducing the loss of model accuracy and meeting the transmission delay requirements, thereby reducing the waste of transmission resources and improving transmission efficiency.

[0008] In an optional embodiment of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy. Therefore, the method further includes: the network device receiving a second notification message sent by the terminal device, the second notification message including a model name corresponding to the target model, the second notification message being used to indicate that the terminal device cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy, and the compression rate condition policy.

[0009] In this embodiment, since the policy information is any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy, the second notification message indicates that the terminal device cannot perform lightweight processing under the conditions of satisfying various condition policies. Therefore, the network device can determine that the target model has failed to be lightweighted through the second notification message. Therefore, when the network device aggregates the model parameter information uploaded by the terminal device through the aggregation algorithm and updates each model parameter, it will not aggregate the model parameter information of the target model, thereby ensuring that the updated model parameters are the model parameters after the lightweight processing is completed, thereby improving the reliability and accuracy of the model parameter update.

[0010] In an optional embodiment of the present application, the policy information is a lightweight method and a lightweight policy configuration. Therefore, the method further includes: the network device receives a third notification message sent by the terminal device, the third notification message including a model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration.

[0011] In this embodiment, since the policy information is the lightweight method and lightweight policy configuration determined by the network device, the third notification message indicates that the terminal device cannot execute the lightweight method and lightweight policy configuration based on its own lightweight capability, that is, it cannot perform lightweight processing. Therefore, the network device can determine through the third notification message that the target model has failed to be lightweighted. Therefore, when the network device aggregates the model parameter information uploaded by the terminal device through the aggregation algorithm and updates each model parameter, it will not aggregate the model parameter information of the target model, thereby ensuring that the updated model parameters are the model parameters after the lightweight processing is completed, thereby improving the reliability and accuracy of the model parameter update.

[0012] In an optional embodiment of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy. Therefore, the method further includes: the network device receiving a model upload message sent by the terminal device, the model upload message carrying a lightweight method and a lightweight policy configuration.

[0013] In this embodiment, the network device can determine the lightweight method and lightweight policy configuration used by the terminal device based on the model upload message, so the network device can restore the model parameter information after lightweight processing, which is conducive to ensuring the compression rate and the accuracy of the lightweight model.

[0014] In an optional implementation of the present application, the first notification message further includes model parameters of the target model. Therefore, the network device determines the policy information according to the model parameters of the target model and the uplink channel state information of the terminal device.

[0015] In this embodiment, since the first notification message also includes the model parameters of the target model, the policy information determined by the model parameters and the uplink channel state information can not only meet the uplink transmission capability of the terminal device, but also determine the policy information of the model parameters that are more in line with the target model, thereby improving the accuracy and reliability of the lightweight method and lightweight policy configuration determined according to the policy information.

[0016] In an optional implementation of the present application, the policy information is a lightweight method and a lightweight policy configuration, or the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

[0017] In this embodiment, the policy information improves the efficiency of the solution by directly indicating the lightweight method and lightweight policy configuration. It can also indicate the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy, and the compression rate condition policy, so that the terminal device can flexibly determine the lightweight method and lightweight policy configuration according to the actual situation based on various condition policies, thereby improving the flexibility of the solution. Secondly, the network device is the control end of the entire federated training process. The network device specifies the lightweight method and lightweight policy configuration that the terminal device should adopt, which helps to simplify the aggregation process of model parameters.

[0018] In an optional embodiment of the present application, the policy information includes a lightweight object (compressionObject), wherein the lightweight object is used to indicate the target type of the model parameters of the target model. Specifically, the lightweight object refers to the parameter file type that needs to be lightweight processed, and the parameter file type can be a gradient file, a residual file, or a weight file.

[0019] In this embodiment, since the lightweight object included in the policy information is used to indicate the target type of the model parameters of the target model, the determined policy information can not only meet the uplink transmission capability of the terminal device, but also determine the parameter file type for lightweight processing to achieve alignment of the parameter file types between the terminal device and the network device, thereby further improving the accuracy of the policy information.

[0020] In an optional embodiment of the present application, the method further includes: the network device receives a device registration message sent by the terminal device, the device registration message carries lightweight capability information (compressionCapacity) of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0021] In this embodiment, through the lightweight capability information in the device registration message, the network device can know at least one policy information that the terminal device can meet, thereby achieving alignment of lightweight capabilities between the terminal device and the network device, that is, the policy information determined by the network device is all satisfyable by the terminal device, reducing the possibility of lightweight failure of the terminal device, thereby improving the feasibility of this solution.

[0022] In an optional embodiment of the present application, the method also includes: the network device sends a lightweight capability query message to the terminal device, the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device, and then receives a capability query confirmation message sent by the terminal device, the capability query confirmation message carries the lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0023] In this embodiment, the network device queries the terminal device for lightweight capability information, so that the network device can obtain the lightweight capability information, and thus learn at least one policy information that the terminal device can satisfy, thereby achieving alignment of lightweight capabilities between the terminal device and the network device, that is, the policy information determined by the network device is all satisfyable by the terminal device, reducing the possibility of lightweight failure of the terminal device, thereby improving the feasibility of this solution.

[0024] In an optional implementation manner of the present application, the lightweight capability query message includes a model name corresponding to the target model.

[0025] In this embodiment, the network device uses the model name corresponding to the target model so that the terminal device determines the lightweight capability information of the target model that the network device needs to determine through the model name corresponding to the target model, so that the lightweight capability information sent can meet the requirements of the target model.

[0026] In an optional implementation manner of the present application, the lightweight indication message further includes a lightweight object, where the lightweight object is used to indicate a target type of a model parameter of the target model.

[0027] In this embodiment, since the lightweight object indicated by the lightweight indication message is used to indicate the target type of the model parameters of the target model, the determined policy information can not only meet the uplink transmission capability of the terminal device, but also determine the parameter file type for lightweight processing to achieve alignment of the parameter file types between the terminal device and the network device, thereby further improving the accuracy of the policy information.

[0028] On the second aspect, the present application provides a method for lightweight processing. The method can be executed by a terminal device, or it can be executed by a chip configured in the terminal device, and the present application does not limit this. The method includes: the terminal device sends a first notification message to the network device, and the first notification message is used to indicate that the terminal device has completed the training of the target model. The first notification message includes the model name corresponding to the target model, and then receives a lightweight indication message sent by the network device, and the lightweight indication message includes the model name corresponding to the target model and policy information. The policy information is determined based on the uplink channel state information of the terminal device, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model. Furthermore, the terminal device determines the lightweight method and lightweight policy configuration based on the policy information, and finally performs lightweight processing on the model parameters of the target model according to the determined lightweight method and lightweight policy configuration.

[0029] In this embodiment, since the policy information is determined based on the uplink channel state information, the lightweight method and lightweight policy configuration determined by the terminal device through the policy information are in line with the uplink transmission capability of the terminal device. Therefore, the model parameters of the target model are lightweight processed through the lightweight method and lightweight policy configuration that are in line with the uplink transmission capability, thereby reducing the loss of model accuracy. Moreover, since it is in line with the uplink transmission capability of the terminal device itself, the lightweight processing performed also meets the transmission delay requirements.

[0030] In an optional embodiment of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy. Therefore, the method further includes: the terminal device sending a second notification message to the network device, the second notification message including a model name corresponding to the target model, the second notification message being used to indicate that the terminal device cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy, and the compression rate condition policy.

[0031] In this embodiment, after the terminal device fails to perform lightweight processing on the target model, it informs the network device that it cannot perform lightweight processing while meeting various conditional strategies. Therefore, when the network device updates each model parameter, it will not aggregate the model parameter information of the target model, thereby ensuring that the updated model parameters are model parameters after lightweight processing, thereby improving the reliability and accuracy of the model parameter update.

[0032] In an optional embodiment of the present application, the policy information is a lightweight method and a lightweight policy configuration. Therefore, the method further includes: the terminal device sends a third notification message to the network device, the third notification message including the model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration.

[0033] In this embodiment, after the terminal device fails to perform lightweight processing on the target model, it informs the network device that it cannot execute the lightweight method and lightweight policy configuration based on its own lightweight capabilities, that is, it cannot perform lightweight processing. Therefore, when the network device updates each model parameter, it will not aggregate the model parameter information of the target model, thereby ensuring that the updated model parameters are model parameters after lightweight processing, thereby improving the reliability and accuracy of the model parameter update.

[0034] In an optional embodiment of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy. Therefore, the method further includes: the terminal device sending a model upload message to the network device, the model upload message carrying the lightweight method and the lightweight policy configuration.

[0035] In this embodiment, the terminal device uploads a message through the model, which enables the network device to determine the lightweight method and lightweight policy configuration used by the terminal device. Therefore, the terminal device can flexibly determine the lightweight method and lightweight policy configuration according to its own needs, and the network device can also restore the model parameter information after lightweight processing. This not only improves the flexibility of the lightweight method and lightweight policy configuration, but also helps to ensure the compression rate and the accuracy of the lightweight model.

[0036] In an optional implementation manner of the present application, the first notification message includes model parameters of the target model.

[0037] In this embodiment, since the first notification message also includes the model parameters of the target model, the policy information determined by the model parameters and the uplink channel state information can not only meet the uplink transmission capability of the terminal device, but also determine the policy information of the model parameters that are more in line with the target model, thereby improving the accuracy and reliability of the lightweight method and lightweight policy configuration determined according to the policy information, thereby reducing the loss of accuracy when the terminal device performs lightweight processing on the target model.

[0038] In an optional implementation of the present application, the policy information is a lightweight method and a lightweight policy configuration, or the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

[0039] In this embodiment, the policy information improves the efficiency of this solution by directly indicating the lightweight method and lightweight policy configuration. It can also indicate the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy, so that the terminal device can flexibly determine the lightweight method and lightweight policy configuration according to various condition policies according to actual conditions, thereby improving the flexibility of this solution.

[0040] In an optional implementation manner of the present application, the policy information includes a lightweight object, where the lightweight object is used to indicate a target type of a model parameter of the target model.

[0041] In this embodiment, since the lightweight object included in the policy information is used to indicate the target type of the model parameters of the target model, the determined policy information can not only meet the uplink transmission capabilities of the terminal device, but also determine the parameter file type for lightweight processing, further improving the accuracy of the policy information. It can not only improve the accuracy and reliability of the lightweight method and lightweight policy configuration determined based on the policy information, thereby reducing the loss of accuracy when the terminal device performs lightweight processing on the target model. Secondly, it can also achieve alignment of parameter file types between the terminal device and the network device. Therefore, during lightweight processing, the required parameter file type is directly determined from multiple parameter file types, thereby improving the efficiency of lightweight processing.

[0042] In an optional implementation of the present application, the terminal device determines the lightweight method, lightweight policy configuration and lightweight object based on the policy information, and then the terminal device performs lightweight processing on the model parameters of the target model that meets the target type based on the lightweight method and lightweight policy configuration.

[0043] In this embodiment, since the determined policy information not only meets the uplink transmission capabilities of the terminal device, but also determines policy information that better meets the model parameters of the target model, the accuracy and reliability of the lightweight method and lightweight policy configuration determined based on the policy information are improved, thereby reducing the loss of accuracy when the terminal device performs lightweight processing on the target model. Furthermore, the parameter file type determined for lightweight processing can further improve the accuracy of the policy information and achieve alignment of the parameter file types between the terminal device and the network device. Therefore, during lightweight processing, the required parameter file type is directly determined from multiple parameter file types, thereby improving the efficiency of lightweight processing.

[0044] In an optional implementation of the present application, the method further includes: the terminal device sends a device registration message to the network device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0045] In this embodiment, the lightweight capability information in the device registration message allows the network device to know at least one policy information that the terminal device can meet, thereby achieving alignment of lightweight capabilities between the terminal device and the network device. Therefore, the policy information determined by the network device received by the terminal device is meetable by the terminal device, reducing the possibility of lightweight failure of the terminal device, thereby improving the feasibility of this solution.

[0046] In an optional embodiment of the present application, the method also includes: the terminal device receives a lightweight capability query message sent by the network device, the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device, the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device, and then the terminal device determines the at least one policy information satisfied according to the lightweight capability query message, and finally sends a capability query confirmation message to the network device, wherein the capability query confirmation message carries the lightweight capability information of the terminal device.

[0047] In this embodiment, the network device queries the terminal device for lightweight capability information, the terminal device determines at least one policy information that it can satisfy, and sends a capability query confirmation message to the network device, so that the network device can know at least one policy information that the terminal device can satisfy, thereby achieving alignment of lightweight capabilities between the terminal device and the network device. Therefore, the policy information determined by the network device received by the terminal device is satisfyable by the terminal device, reducing the possibility of lightweight failure of the terminal device, thereby improving the feasibility of this solution.

[0048] In an optional implementation manner of the present application, the lightweight capability query message includes a model name corresponding to the target model.

[0049] In this embodiment, the terminal device determines the lightweight capability information of the target model that the network device needs to determine through the model name corresponding to the target model, so that the lightweight capability information sent can meet the requirements of the target model.

[0050] In an optional implementation manner of the present application, the lightweight indication message further includes a lightweight object, where the lightweight object is used to indicate a target type of a model parameter of the target model.

[0051] In this embodiment, since the lightweight object indicated by the lightweight indication message is used to indicate the target type of the model parameters of the target model, the determined policy information can not only meet the uplink transmission capability of the terminal device, but also determine the parameter file type for lightweight processing to achieve alignment of the parameter file types between the terminal device and the network device, thereby further improving the accuracy of the policy information.

[0052] In a third aspect, a communication device is provided. The communication device has the ability to implement some or all of the functions of the network device described in the first aspect and any possible implementation of the first aspect. For example, the device may have the functions of some or all of the embodiments of the network device in this application, or it may have the functions of implementing any embodiment of this application alone. The functions may be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0053] In one possible design, the communication device may include a processing module and a transceiver module. The processing module is configured to support the communication device in performing the corresponding functions of the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the processing module and the communication module and stores program instructions and data necessary for the communication device.

[0054] In one embodiment, the communication device includes:

[0055] A transceiver module, configured to receive a first notification message sent by a terminal device, wherein the first notification message is used to indicate that the terminal device has completed training of the target model, and the first notification message includes a model name corresponding to the target model;

[0056] A processing module, configured to determine policy information based on uplink channel state information of a terminal device, wherein the policy information is used by the terminal device to determine a lightweight communication device and a lightweight policy configuration;

[0057] The transceiver module is also used to send a lightweight indication message to the terminal device, wherein the lightweight indication message includes the model name and policy information corresponding to the target model, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

[0058] As an example, the processing module may be a processor or a processing unit, the transceiver module may be a transceiver, a communication interface or a communication unit, and the storage module may be a memory or a storage unit.

[0059] In another embodiment, the communication device may include:

[0060] A processor, configured to receive a first notification message sent by a terminal device, wherein the first notification message is used to indicate that the terminal device has completed training of a target model, and the first notification message includes a model name corresponding to the target model;

[0061] A transceiver configured to determine policy information based on uplink channel state information of a terminal device, wherein the policy information is used by the terminal device to determine a lightweight communication device and a lightweight policy configuration;

[0062] The transceiver is also used to send a lightweight indication message to the terminal device, wherein the lightweight indication message includes the model name and policy information corresponding to the target model, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

[0063] In an optional implementation manner of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy;

[0064] The transceiver module is also used to receive a second notification message sent by the terminal device, wherein the second notification message includes the model name corresponding to the target model, and the second notification message is used to indicate that the terminal device cannot meet any one of the file size condition strategy, the uplink transmission rate condition strategy, the transmission time condition strategy and the compression rate condition strategy.

[0065] In an optional implementation of the present application, the policy information is a lightweight method and a lightweight policy configuration;

[0066] The transceiver module is also used to receive a third notification message sent by the terminal device, wherein the third notification message includes the model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and lightweight policy configuration.

[0067] In an optional implementation manner of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy;

[0068] The transceiver module is also used to receive the model upload message sent by the terminal device, wherein the model upload message carries the lightweight communication device and the lightweight strategy configuration.

[0069] In an optional implementation manner of the present application, the first notification message includes model parameter information of the target model;

[0070] The processing module is specifically used for the network device to determine the strategy information according to the model parameter information of the target model and the uplink channel state information of the terminal device.

[0071] In an optional embodiment of the present application, the policy information is a lightweight communication device and a lightweight policy configuration;

[0072] or,

[0073] The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

[0074] In an optional implementation manner of the present application, the policy information includes a lightweight object, wherein the lightweight object is used to indicate a target type of model parameter information of the target model.

[0075] In an optional embodiment of the present application, the transceiver module is further used to receive a device registration message sent by the terminal device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0076] In an optional embodiment of the present application, the transceiver module is further configured to send a lightweight capability query message from the network device to the terminal device, wherein the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device;

[0077] The transceiver module is further used to receive a capability query confirmation message sent by the terminal device, wherein the capability query confirmation message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0078] In an optional implementation manner of the present application, the lightweight capability query message includes a model name corresponding to the target model.

[0079] In an optional implementation manner of the present application, the lightweight indication message further includes a lightweight object, wherein the lightweight object is used to indicate a target type of model parameter information of the target model.

[0080] During implementation, the processor can be used to perform, for example, but not limited to, baseband-related processing, and the transceiver can be used to perform, for example, but not limited to, radio frequency transceiver. The above-mentioned devices can be respectively arranged on independent chips, or at least partially or completely arranged on the same chip. For example, the processor can be further divided into an analog baseband processor and a digital baseband processor. Among them, the analog baseband processor can be integrated with the transceiver on the same chip, and the digital baseband processor can be arranged on an independent chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (such as but not limited to a graphics processor, a multimedia processor, etc.) on the same chip. Such a chip can be called a system on chip. Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the implementation form of the above-mentioned devices.

[0081] In a fourth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and configured to execute instructions in the memory to implement the method of any possible implementation of the first aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface, the communication interface being configured to input and / or output information, the information comprising at least one of instructions and data.

[0082] In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver or an input / output interface.

[0083] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0084] In another implementation, the communication device is a chip or chip system configured in a network device. When the communication device is a chip or chip system configured in a network device, the communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits. The processor can also be embodied as a processing circuit or a logic circuit.

[0085] In a fifth aspect, a communication device is provided. The communication device has the ability to implement some or all of the functions of the terminal device described in the second aspect and any possible implementation of the second aspect. For example, the functions of the device may have the functions of some or all of the embodiments of the terminal device in this application, or may have the functions of implementing any embodiment of this application alone. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0086] In one possible design, the communication device may include a processing module and a transceiver module. The processing module is configured to support the communication device in performing the corresponding functions of the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the processing module and the communication module and stores program instructions and data necessary for the communication device.

[0087] In one embodiment, the communication device includes:

[0088] A transceiver module, configured for the terminal device to send a first notification message to the network device, wherein the first notification message is used to indicate that the terminal device has completed training of the target model, and the first notification message includes a model name corresponding to the target model;

[0089] The transceiver module is further configured to receive a lightweight indication message sent by a network device, wherein the lightweight indication message includes a model name and policy information corresponding to a target model, the policy information being determined based on uplink channel state information of the terminal device, and the lightweight indication message being used to instruct the terminal device to perform lightweight processing on model parameter information of the target model;

[0090] A processing module, configured to determine a lightweight communication device and a lightweight policy configuration according to the policy information;

[0091] The processing module is further configured to perform lightweight processing on the model parameter information of the target model according to the lightweight communication device and the lightweight strategy configuration.

[0092] The relevant contents of this implementation method can be found in the relevant contents of the second aspect mentioned above, and will not be described in detail here.

[0093] As an example, the processing module may be a processor or a processing unit, the transceiver module may be a transceiver, a communication interface or a communication unit, and the storage module may be a memory or a storage unit.

[0094] In another embodiment, the communication device may include:

[0095] A transceiver, configured for a terminal device to send a first notification message to a network device, wherein the first notification message is used to indicate that the terminal device has completed training of a target model, and the first notification message includes a model name corresponding to the target model;

[0096] The transceiver is further configured to receive a lightweight indication message sent by a network device, wherein the lightweight indication message includes a model name and policy information corresponding to a target model, the policy information being determined based on uplink channel state information of the terminal device, and the lightweight indication message being used to instruct the terminal device to perform lightweight processing on model parameter information of the target model;

[0097] a processor, configured to determine a lightweight communication device and a lightweight policy configuration based on the policy information;

[0098] The processor is further configured to perform lightweight processing on the model parameter information of the target model according to the lightweight communication device and the lightweight strategy configuration.

[0099] In an optional implementation manner of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy;

[0100] The transceiver module is also used to send a second notification message to the network device, wherein the second notification message includes the model name corresponding to the target model, and the second notification message is used to indicate that the terminal device cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy.

[0101] In an optional implementation of the present application, the policy information is a lightweight method and a lightweight policy configuration;

[0102] The transceiver module is also used to send a third notification message to the network device, wherein the third notification message includes the model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and lightweight policy configuration.

[0103] In an optional implementation manner of the present application, the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy;

[0104] The transceiver module is also used to send a model upload message to the network device, wherein the model upload message carries a lightweight communication device and a lightweight strategy configuration.

[0105] The first notification message includes model parameter information of the target model.

[0106] In an optional embodiment of the present application, the policy information is a lightweight communication device and a lightweight policy configuration;

[0107] or,

[0108] The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

[0109] In an optional implementation manner of the present application, the policy information includes a lightweight object, wherein the lightweight object is used to indicate a target type of model parameter information of the target model.

[0110] In an optional embodiment of the present application, the processing module is specifically configured to determine a lightweight communication device, a lightweight policy configuration, and a lightweight object based on the policy information;

[0111] The processing module is specifically configured to perform lightweight processing on model parameter information of a target model that meets the target type according to the lightweight communication device and the lightweight strategy configuration.

[0112] In an optional implementation of the present application, the transceiver module is further used to send a device registration message to the network device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0113] In an optional embodiment of the present application, the transceiver module is further configured to receive a lightweight capability query message sent by the network device, wherein the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device;

[0114] The processing module is further configured to determine at least one policy information satisfied according to the lightweight capability query message;

[0115] The transceiver module is further configured to send a capability query confirmation message to the network device, wherein the capability query confirmation message carries the lightweight capability information of the terminal device.

[0116] In an optional implementation manner of the present application, the lightweight capability query message includes a model name corresponding to the target model.

[0117] In an optional implementation manner of the present application, the lightweight indication message further includes a lightweight object, wherein the lightweight object is used to indicate a target type of model parameter information of the target model.

[0118] During implementation, the processor can be used to perform, for example, but not limited to, baseband-related processing, and the transceiver can be used to perform, for example, but not limited to, radio frequency transceiver. The above-mentioned devices can be respectively arranged on independent chips, or at least partially or completely arranged on the same chip. For example, the processor can be further divided into an analog baseband processor and a digital baseband processor. Among them, the analog baseband processor can be integrated with the transceiver on the same chip, and the digital baseband processor can be arranged on an independent chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (such as but not limited to a graphics processor, a multimedia processor, etc.) on the same chip. Such a chip can be called a system on chip. Whether each device is independently arranged on different chips or integrated on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the implementation form of the above-mentioned devices.

[0119] In a sixth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and configured to execute instructions in the memory to implement the method of any possible implementation of the second aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface, the communication interface being configured to input and / or output information, the information comprising at least one of instructions and data.

[0120] In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input / output interface.

[0121] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0122] In another implementation, the communication device is a chip or chip system configured in a terminal device. When the communication device is a chip or chip system configured in a terminal device, the communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits. The processor can also be embodied as a processing circuit or a logic circuit.

[0123] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method of any possible implementation of the first and second aspects.

[0124] In a specific implementation, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter. The input circuit and the output circuit may be the same circuit, which functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0125] In an eighth aspect, a communication device is provided, comprising a communication interface and a processor. The communication interface is coupled to the processor. The communication interface is configured to input and / or output information. The information includes at least one of instructions and data. The processor is configured to execute a computer program to cause the communication device to perform the method of any possible implementation of the first and second aspects.

[0126] Optionally, there are one or more processors and one or more memories.

[0127] In a ninth aspect, a communication device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter, so that the device executes the method of any possible implementation of the first and second aspects.

[0128] Optionally, there are one or more processors and one or more memories.

[0129] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0130] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0131] It should be understood that the relevant information exchange process, such as sending indication information, can be the process of outputting the indication information from the processor, and receiving indication information can be the process of inputting the received indication information into the processor. Specifically, the information output by the processor can be output to the transmitter, and the input information received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0132] The communication device in the above-mentioned eighth and ninth aspects can be a chip, and the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor, or can be located outside the processor and exist independently.

[0133] In the tenth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute the method in any possible implementation of the first and second aspects above.

[0134] In the eleventh aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute the method in any possible implementation of the first and second aspects above.

[0135] In the twelfth aspect, a communication system is provided, comprising the aforementioned terminal device and network device.

[0136] In the thirteenth aspect, the present application provides a chip system, which includes a processor and an interface, wherein the interface is used to obtain a program or instruction, and the processor is used to call the program or instruction to implement or support the network device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method.

[0137] In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the network device. The chip system can be composed of a chip or include a chip and other discrete devices.

[0138] On the fourteenth aspect, the present application provides a chip system, which includes a processor and an interface, wherein the interface is used to obtain a program or instruction, and the processor is used to call the program or instruction to implement or support the terminal device to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method.

[0139] In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the terminal device. The chip system can be composed of a chip or include a chip and other discrete devices.

[0140] It should be noted that the beneficial effects brought about by the implementation methods of the third to fourteenth aspects of this application can be understood by referring to the implementation methods of the first and second aspects, and therefore are not repeated.

[0141] Through the technical solution provided by the present application, the terminal device sends a first notification message including the model name corresponding to the target model to the network device. The first notification message is used to indicate that the terminal device has completed the training of the target model. Therefore, the network device knows through the first notification message that the terminal device has completed the training of the target model, and then determines the policy information according to the uplink channel state information of the terminal device, and sends a lightweight indication message including the model name corresponding to the target model and the policy information to the terminal device. Thus, the terminal device determines the lightweight method and lightweight policy configuration according to the policy information, and performs lightweight processing on the model parameter information of the target model according to the lightweight method and lightweight policy configuration. Since the policy information is determined according to the uplink channel state information, the lightweight method and lightweight policy configuration determined by the terminal device through the policy information are in line with the uplink transmission capability of the terminal device, so that the loss of model accuracy can be reduced and the transmission delay requirements can be met, thereby reducing the waste of transmission resources and improving transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0142] Figure 1 A schematic diagram of the system framework in the embodiment of the present application;

[0143] Figure 2 This is a schematic diagram of the application of horizontal federated learning in the UE-RAN system in an embodiment of the present application;

[0144] Figure 3 This is a schematic diagram of model pruning in an embodiment of the present application;

[0145] Figure 4 A schematic diagram of the model quantification in the embodiment of the present application;

[0146] Figure 5 A schematic diagram of an embodiment of a method for information transmission in an embodiment of the present application;

[0147] Figure 6 A schematic diagram of an embodiment of a lightweight processing method in an embodiment of the present application;

[0148] Figure 7 A schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application;

[0149] Figure 8 A schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application;

[0150] Figure 9A schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application;

[0151] Figure 10 A schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application;

[0152] Figure 11 This is a schematic diagram of an embodiment of a communication device in an embodiment of the present application;

[0153] Figure 12 This is a schematic diagram of another embodiment of a communication device in an embodiment of the present application;

[0154] Figure 13 is a schematic block diagram of a communication device in an embodiment of the present application;

[0155] Figure 14 is a schematic diagram of the structure of the terminal device provided in an embodiment of the present application;

[0156] Figure 15 It is a structural diagram of the network device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0157] The technical solution in this application will be described below with reference to the accompanying drawings.

[0158] 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) system, universal mobile telecommunication system (UMTS). With the continuous development of communication systems, the technical solutions of the present application can be applied to fifth generation (5G) system or new radio (NR), and can also be applied to future networks, such as 6G system or even future system; or can also be used for device to device (D2D) system, machine to machine (M2M) system, etc.

[0159] It should be understood that the network device in the communication system can be any device with wireless transceiver function or a chip that can be set in the device, and the device includes but is not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (for example, Home evolved NodeB, or Home Node B, HNB), Base Band Unit (BBU), Access Point (AP) in Wireless Fidelity (WIFI) system, Wireless Relay Node, Wireless Backhaul Node, Transmission Point (TP) It can also be a device used in 5G, 6G or even future systems, such as a gNB in ​​an NR system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), a distributed unit (DU), a picocell, a femtocell, or a road side unit (RSU) in a vehicle to everything (V2X) or intelligent driving scenario.

[0160] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include a radio unit (RU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU implements the functions of the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) layer, while the DU implements the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer (PHY). Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling or PDCP layer signaling, can also be considered to be sent by the DU, or by both the DU and the RU. It is understood that a network device can be a CU node, a DU node, or a device that includes both a CU node and a DU node. In addition, the CU may be classified as a network device in a radio access network (RAN), or may be classified as a network device in a core network CN, which is not limited here.

[0161] In the embodiments disclosed in the present application, the communication device used to implement the function of the network device can be a network device; it can also be a communication device that can support the network device to implement the function, such as a chip system, and the communication device can be installed in the network device.

[0162] It should also be understood that the terminal device in the communication system can also be referred to as UE, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user communication device. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a wireless terminal in the aforementioned V2X vehicle network or an RSU of wireless terminal type, etc. The embodiment of the present application does not limit the application scenario.

[0163] In addition, in order to facilitate understanding of the embodiments of the present application, the following explanations are made.

[0164] First, for ease of description, in this application, when numbering, consecutive numbers may be used starting from 0. For example, the 0th symbol in a time slot may refer to the first symbol in that time slot. Of course, this is not a limitation in the specific implementation. For example, consecutive numbering may also start from 1. For example, the 1st symbol in a time slot may also refer to the first symbol in that time slot. Due to different starting values ​​for numbering, the same symbol will have different numbers in the time slot.

[0165] It should be understood that the above descriptions are all made for the purpose of describing the technical solutions provided by the embodiments of the present application, and are not intended to limit the scope of the present application.

[0166] Second, in the embodiments shown below, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", etc., and there is no order of precedence or size between the technical features described by the "first", "second", and "third".

[0167] Third, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple, respectively.

[0168] Fourth, in the embodiments shown below, some scenarios are illustrated using the NR network scenario in a wireless communication network as an example. It should be noted that the solutions in the embodiments disclosed in this application can also be applied to other wireless communication networks, and the corresponding names can also be replaced by the names of corresponding functions in other wireless communication networks.

[0169] Fifth, the embodiments disclosed herein will present various aspects, embodiments, or features of the present invention centered around systems comprising multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the accompanying figures. Furthermore, combinations of these solutions may also be used.

[0170] Sixth, in the embodiments disclosed in this application, "of", "relevant" and "corresponding" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0171] In order to better understand the information transmission method, lightweight processing method and related communication device disclosed in the embodiments of the present application, first, the system architecture of the communication system used in the embodiments of the present invention is described. Figure 1 , Figure 1 A schematic diagram of the system framework in the embodiment of the present application is shown in FIG. Figure 1 In the UE-RAN system shown in Figure (A), horizontal federated learning is performed between multiple UEs, the UE is a participant in the horizontal federated learning process, and the RAN is the coordinator in the horizontal federated learning process. Furthermore, the method disclosed in the embodiment of the present application is also applicable to other system architectures, for example, Figure 1In the RAN-network management scenario shown in Figure (B), horizontal federated learning is performed between multiple RANs. RANs are participants in the horizontal federated learning process, and the Element Management System (EMS) and / or Network Management System (NMS) are coordinators in the horizontal federated learning process. Figure 1 Figure C shows a system under the enabler of Network Automation (eNA) architecture. Horizontal federated learning is performed between multiple local Network Data Analytics Functions (localNWDAFs). The local NWDAFs are participants in the horizontal federated learning process, and the central Network Data Analytics Function (centralNWDAF) is the coordinator of the horizontal federated learning process.

[0172] Secondly, some terms or concepts involved in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0173] 1. Federated Learning

[0174] Federated learning is an encrypted, distributed machine learning technology that fully leverages the data and computing power of participating parties, enabling multiple parties to collaboratively build universal, robust machine learning models without sharing data. Amidst increasingly stringent data regulations, federated learning can address key issues such as data ownership, data privacy, data access rights, and access to heterogeneous data. In wireless scenarios, federated learning can be used to train models to ensure data security or reduce information transmission.

[0175] Horizontal Federated Learning

[0176] Horizontal federated learning is a key branch of federated learning. Horizontal federation includes a coordinator and several participants. Participants are responsible for using local data for model training, and the coordinator is responsible for aggregating the models of each participant. For easier understanding, please refer to Figure 2 , Figure 2This is a schematic diagram of the application of horizontal federated learning in the UE-RAN system in an embodiment of the present application. As shown in the figure, in horizontal federated learning, the coordinator (RAN) sends the model to multiple participants (multiple user devices), and the multiple participants use their own data sets to train the model. After the multiple participants complete the training of the model, they send the trained model parameter information to the coordinator, whereupon the coordinator aggregates the model parameter information received from the participants (for example, using a federated averaging algorithm for aggregation) and then updates the model. The above process will be repeated until the model converges, the maximum number of times is reached, or the maximum training time is reached.

[0177] 3. AI model lightweight technology

[0178] The essence of AI model lightweighting technology is to reduce storage space or reduce computational complexity at the expense of a certain degree of model accuracy loss. Currently, the more common and mature model lightweighting technologies include model pruning and model quantization.

[0179] For a better understanding of model pruning, see Figure 3 , Figure 3 This is a schematic diagram of model pruning in an embodiment of the present application. As shown in the figure, the main principle of model pruning is to compress the network storage space by removing redundant connections in the neural network. The redundant connections here mainly refer to connections with smaller weights in the neural network. In the model pruning method, it is necessary to configure the pruning strategy, such as the pruning ratio and pruning method of each layer of the neural network. The model processed by the model pruning method can be directly applied to model retraining or model inference. Specifically, the pruning methods in the embodiments of the present application include but are not limited to weight pruning, neuron pruning, channel pruning and kernel pruning.

[0180] To understand model quantization, see Figure 4 , Figure 4 This is a schematic diagram of model quantization in an embodiment of the present application. As shown in the figure, the main principle of model quantization is to compress the original network by reducing the number of bits required to represent the weights of the neural network. Normally, the parameter information of the deep learning model is 32-bit floating point type, and the model quantization method can quantize the 32-bit floating point weights to 16-bit, 8-bit, 4-bit, 2-bit, or even 1-bit, thereby greatly compressing the storage space occupied by the network. In the model quantization method, it is necessary to configure the quantization strategy, which includes but is not limited to the number of quantization bits, quantization mode, quantization step size, and zero value offset, etc. The model processed by the model quantization method needs to undergo a certain degree of recovery before it can be applied to model retraining or model inference. Specifically, the quantization methods in the embodiments of the present application include but are not limited to uniform quantization and non-uniform quantization.

[0181] 4. Lightweight Methods

[0182] Lightweight methods represent the types of methods that can be used to lightweight AI models. They can be divided into general lightweight methods and customized lightweight methods. In the embodiments of this application, lightweight processing indicates the storage space size of compressed model parameter information. General lightweight methods refer to common and mature technologies in the industry, including but not limited to model pruning, model quantization, or a combination of pruning and quantization. Customized lightweight methods refer to model compression methods customized for specific models.

[0183] 5. Lightweight Strategy Configuration

[0184] Each lightweight method corresponds to a parameter configuration template. When using a lightweight method, you need to fill in the template parameters for that method. The filled-in content is the lightweight strategy configuration. For example, for a model pruning lightweight method, the parameter configuration template may include the pruning ratio and pruning method for each neural network layer.

[0185] 6. Compression Ratio

[0186] The compression ratio indicates the ratio of the model parameter information file size after lightweight processing to the model parameter information file size before lightweight processing.

[0187] Therefore, in order to reduce communication overhead, after completing local model training, the UE can select a lightweight method and lightweight policy configuration from the lightweight methods it supports according to certain criteria to perform lightweight processing on the local model, and then upload the model parameter information. The selected lightweight method is a method that can be directly applied without restoring the lightweight model parameter information. However, when the uplink transmission rate is high, if the UE adopts a lightweight method and lightweight policy configuration with a higher compression ratio, the model accuracy will suffer a lot of loss, resulting in a decrease in accuracy after aggregation. Secondly, when the uplink transmission rate is low, if the UE adopts a lightweight method and lightweight policy configuration with a lower compression ratio, the amount of model parameter information transmitted is too large, which may lead to a waste of transmission resources and reduced transmission efficiency.

[0188] In order to solve the above problems, the embodiments of the present application provide a method for information transmission and a method for lightweight processing, which are used to reduce the loss of model accuracy and meet the transmission delay requirements, thereby reducing the waste of transmission resources and improving transmission efficiency.

[0189] The following describes in detail the information transmission method used in the embodiment of the present application with the network device as the execution subject. Figure 5 , Figure 5This is a schematic diagram of an embodiment of a method for information transmission in an embodiment of the present application. The method for information transmission includes the following steps.

[0190] S101. A network device receives a first notification message sent by a terminal device, wherein the first notification message is used to indicate that the terminal device has completed training of a target model, and the first notification message includes a model name corresponding to the target model.

[0191] In this embodiment, the network device can select the terminal device that needs to participate in the training of the target model through an internal algorithm, and then send a model training message to the terminal device that is training the target model. The model training message includes the model name of the target model and the model file of the target model, so that the terminal device can use local data to train the target model. When the terminal device has completed the training of the target model, it can send a first notification message to the network device, and include the model name (modelName) corresponding to the target model in the first notification message, so that the network device determines that the terminal device has completed the training of the target model based on the first notification information. For example, the terminal device is training model A, model B and model C. When the terminal device has completed the training of model A, it can determine model A as the target model and send a first notification message carrying the model name "Model A" to the network device. After the network device receives the first notification message, it can determine that the terminal device has completed the training of model A.

[0192] Optionally, the first notification message may also include model parameter information (modelParameterInfo) of the target model. Specifically, in this embodiment, modelParameterInfo is parameter file information (parameterInfo), and parameterInfo refers to the parameter file information corresponding to the parameter file type that has been agreed upon in advance by the terminal device and the network device. Among them, the parameter file type can be a gradient file, a residual file, or a weight file. Secondly, parameterInfo can be the size of the parameter file, the sparsity of the parameter file, or information that helps the network device determine the lightweight method and lightweight policy configuration, which is not specifically limited here. Therefore, when the first notification message can also include model parameter information, that is, the terminal device can feedback information of other types of parameter files in addition to the agreed types to the network device, which helps the network device to formulate lightweight indication information that is more suitable for the target model, and further ensure the accuracy of the model after lightweighting. Secondly, whether to include model parameter information requires the terminal device to decide for itself based on the characteristics of the model parameter information. For example, when the parameter file type agreed in advance is a weight file, if the terminal device determines that the residual file is more sparse and the model accuracy loss after lightweight processing may be smaller, the terminal device can feed back the information of the residual file to the network device by feeding back the model parameter information, thereby reducing the model accuracy loss after lightweight processing.

[0193] Optional, model parameter information is in list form, each item in the list is<parameterType,parameterInfo> , where parameterType indicates the parameter file type and parameterInfo indicates the parameter file information.

[0194] S102. The network device determines policy information according to the uplink channel state information of the terminal device, wherein the policy information is used by the terminal device to determine a lightweight method and lightweight policy configuration.

[0195] In this embodiment, the network device obtains uplink channel state information of the terminal device through measurement, allocates uplink transmission resources to the terminal device, and then determines policy information based on the uplink channel state information. This policy information is used by the terminal device to determine a lightweight method and lightweight policy configuration. Specifically, the lightweight method includes model pruning and / or model quantization.

[0196] Optionally, the policy information can be any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression ratio condition policy, or the policy information can be a lightweight method and a lightweight policy configuration. The file size condition policy is the parameter file size requirement corresponding to the parameter file, specifically the maximum parameter file size that can be achieved by the selected lightweight method and the lightweight policy configuration. Secondly, the uplink transmission rate condition policy is the rate requirement corresponding to the uplink transmission rate, specifically the maximum uplink transmission rate that can be achieved by the selected lightweight method and the lightweight policy configuration. Secondly, the transmission time condition policy is the time requirement corresponding to the transmission time, specifically the maximum transmission time that can be achieved by the selected lightweight method and the lightweight policy configuration. Thirdly, the compression ratio condition policy is the compression ratio requirement corresponding to the compression ratio, specifically the maximum compression ratio that can be achieved by the selected lightweight method and the lightweight policy configuration. For example, the maximum transmission time in the time requirement is 2 seconds, i.e., the transmission time configured by the lightweight method and the lightweight policy cannot exceed 2 seconds. Alternatively, the parameter file size requirement is a maximum parameter file size of 10MB (MByte). This means that the size of the parameter file transferred using the lightweight method and lightweight policy configuration cannot exceed 10MB. It should be understood that the preceding examples are only for understanding this solution. Specific conditional policies need to be flexibly determined based on actual circumstances and are not specifically limited here.

[0197] Optionally, the policy information may further include a lightweight object, which is used to indicate the target type of the model parameters of the target model. In this embodiment, the lightweight object may be a gradient file, a residual file, or a weight file. Specifically, if in step S101, the first notification message includes the model parameter information of the target model, and the model parameter information only includes the parameter file information corresponding to the default parameter file type, then the policy information does not need to include a lightweight object, that is, the network device and the terminal device both determine the default parameter file type for lightweight processing. If in step S101, the first notification message includes the model parameter information of the target model, and the model parameter information includes a variety of parameter file types and parameter file information, the network device and the terminal device need to determine the parameter file type for lightweight processing through the policy information, so the policy information also needs to include a lightweight object.

[0198] Specifically, when the first notification message also includes model parameter information of the target model, the network device can determine the policy information based on the uplink channel state information of the terminal device and the model parameter information of the target model. Since the policy information can be the size of the parameter file, the sparsity of the parameter file, or information that helps the network device determine the lightweight method and lightweight policy configuration, further determining the policy information based on the parameter file information can improve the accuracy of the determined policy information.

[0199] S103. The network device sends a lightweight indication message to the terminal device, wherein the lightweight indication message includes a model name and policy information corresponding to the target model, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

[0200] In this embodiment, the network device sends a lightweight indication message to the terminal device, where the lightweight indication message includes the model name and policy information corresponding to the target model, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

[0201] Specifically, when the policy information is a lightweight method and a lightweight policy configuration, the lightweight method can be represented in either bitmap or plaintext form. Therefore, when the lightweight method is transmitted via a bitmap, each bit represents a method. If the bit is 1, it indicates that the method is adopted; if the bit is 0, it indicates that the method is not adopted. For example, a bitmap of 00000010 indicates the adoption of the second lightweight method. Secondly, the lightweight policy configuration is the specific configuration for the specified lightweight method. As can be seen from the description of the aforementioned terms or concepts, each lightweight method has a fixed parameter template, and the policy configuration provides an instance of the parameter template. Since the network device is the controller of the entire federated training process, specifying the lightweight method and lightweight policy configuration that the terminal device should adopt helps simplify the model parameter aggregation process. For example, the network device can specify the same type of lightweight method or the same type of lightweight object for different terminal devices to facilitate model parameter aggregation.

[0202] Secondly, when the policy information is any one of the file size condition policy, uplink transmission rate condition policy, transmission time condition policy and compression rate condition policy, the terminal device needs to determine a lightweight method and lightweight policy configuration that meet at least one of the aforementioned condition policies. In this case, since the lightweight method and lightweight policy configuration are determined by the terminal device based on the policy information, if the determined lightweight method and lightweight policy configuration can meet the lightweight capability of the terminal device, the terminal device can implement them. Secondly, there may also be a situation where the lightweight method and lightweight policy configuration supported by the terminal device do not meet the condition policy. At this time, lightweighting fails, and the terminal device will send a second notification message to the network device. The second notification message includes the model name corresponding to the target model. The second notification message is used to indicate that the lightweight method and lightweight policy configuration supported by the terminal device cannot meet any one of the file size condition policy, uplink transmission rate condition policy, transmission time condition policy and compression rate condition policy, that is, the terminal device fails to perform lightweight processing on the target model. Furthermore, if the policy information is a lightweight method and a lightweight policy configuration, that is, the lightweight method and the lightweight policy configuration are determined by the network device, then the lightweight method and the lightweight policy configuration may not meet the lightweight capabilities of the terminal device. Therefore, when the lightweight capabilities of the terminal device are not met, the terminal device will send a third notification message to the network device. The third notification message includes the model name corresponding to the target model. The third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration, that is, the terminal device fails to perform lightweight processing on the target model. Whether the network device receives the second notification message or the third notification message needs to be determined based on whether the terminal device successfully performs lightweight processing on the target model.

[0203] The following describes in detail the lightweight processing method used in the embodiment of the present application with the terminal device as the execution subject. Figure 6 , Figure 6 This is a schematic diagram of an embodiment of a lightweight processing method in an embodiment of the present application. The information transmission method includes the following steps.

[0204] S201. The terminal device sends a first notification message to the network device, wherein the first notification message is used to indicate that the terminal device has completed training of the target model, and the first notification message includes a model name corresponding to the target model.

[0205] In this embodiment, the network device selects the terminal devices that need to participate in training the target model through an internal algorithm, and then sends a model training message to the terminal devices training the target model. The model training message includes the model name of the target model and the model file of the target model, so that the terminal devices can use local data to train the target model. When the terminal device has completed training the target model, it can send a first notification message to the network device, and the first notification message includes the model name corresponding to the target model, so that the network device determines that the terminal device has completed training the target model based on the first notification information.

[0206] Optionally, the first notification message may also include model parameter information of the target model. Specifically, the model parameter information is parameter file information, and the parameter file information refers to the parameter file information corresponding to the parameter file type that has been agreed upon in advance between the terminal device and the network device. Among them, the parameter file type can be a gradient file, a residual file, or a weight file. Secondly, the parameter file information can be the size of the parameter file, the sparsity of the parameter file, or information that helps the network device determine the lightweight method and lightweight policy configuration, which is not specifically limited here.

[0207] Therefore, when the first notification message can also include model parameter information, the terminal device can feedback information of other types of parameter files in addition to the agreed types to the network device, which helps the network device to formulate lightweight indication information that is more suitable for the target model, and further ensure the accuracy of the model after lightweighting. Secondly, whether to include model parameter information is determined by the terminal device based on the characteristics of the model parameter information. For example, when the parameter file type agreed in advance is a weight file, if the terminal device determines that the sparsity of the residual file is higher, the loss of model accuracy after lightweight processing may be smaller, then the terminal device can feedback the information of the residual file to the network device by feeding back the model parameter information, thereby reducing the loss of model accuracy after lightweight processing.

[0208] Optional, model parameter information is in list form, each item in the list is<parameterType,parameterInfo> , where parameterType indicates the parameter file type and parameterInfo indicates the parameter file information.

[0209] S202. The terminal device receives a lightweight indication message sent by the network device, wherein the lightweight indication message includes a model name and policy information corresponding to the target model. The policy information is determined based on the uplink channel state information of the terminal device. The lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

[0210] In this embodiment, since the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model, the terminal device can start the lightweight processing process after receiving the lightweight indication message. When the first notification message only includes the model name corresponding to the target model, the network device obtains the uplink channel state information of the terminal device by measurement in a similar manner as described in step S102, and allocates uplink transmission resources to the terminal device, and then after the uplink channel state information determines the policy information, the network device sends a lightweight indication message to the terminal device, and the lightweight indication message includes the model name corresponding to the target model and the policy information. Secondly, when the first notification message also includes model parameter information, the network device can determine the policy information based on the uplink channel state information of the terminal device and the model parameter information of the target model. Since the policy information can be the size of the parameter file, the sparsity of the parameter file, or information that helps the network device determine the lightweight method and lightweight policy configuration, further determining the policy information based on the parameter file information can improve the accuracy of the determined policy information.

[0211] Optionally, the policy information may be any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy, or the policy information may be a lightweight method and a lightweight policy configuration. The lightweight method includes model pruning and / or model quantization. When the policy information is a lightweight method and a lightweight policy configuration, the representation of the lightweight method may be in bitmap form or in plain text form. The specific representation of the lightweight method and the lightweight policy configuration are similar to those in the aforementioned embodiment and will not be repeated here.

[0212] Optionally, the policy information may further include a lightweight object, where the lightweight object is used to indicate a target type of a model parameter of the target model. In this embodiment, the lightweight object may be a gradient file, a residual file, or a weight file.

[0213] Secondly, when the policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy, the terminal device is required to determine a lightweight method and a lightweight policy configuration that satisfies at least one of the aforementioned condition policies. The information included in the specific policy information is not limited here. Specifically, if in step S201, the first notification message includes the model parameter information of the target model, and the model parameter information only includes the parameter file information corresponding to the default parameter file type, then the policy information does not need to include a lightweight object, that is, the network device and the terminal device both determine the default parameter file type for lightweight processing. If in step S201, the first notification message includes the model parameter information of the target model, and the model parameter information includes a variety of parameter file types and parameter file information, the network device and the terminal device need to determine the parameter file type for lightweight processing through the policy information, so the policy information also needs to include a lightweight object.

[0214] S203: The terminal device determines a lightweight method and lightweight policy configuration according to the policy information.

[0215] In this embodiment, when the policy information is a lightweight method and a lightweight policy configuration determined by the network device, the terminal device can directly determine the lightweight method and the lightweight policy configuration based on the policy information. Secondly, when the policy information is any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy, and the compression rate condition policy, then the terminal device needs to determine the lightweight method and lightweight policy configuration that meet the aforementioned at least one condition policy from at least one lightweight method and lightweight policy configuration (i.e., lightweight capability) that it can meet. If the lightweight capability of the terminal device cannot meet the aforementioned at least one condition policy, it is determined from the lightweight method and lightweight policy configuration supported by the terminal device, which is not limited here.

[0216] Specifically, when the policy information is any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy, and the compression rate condition policy, the terminal device can determine the lightweight method and lightweight policy configuration according to the model parameter characteristics. If the number of selectable lightweight methods and lightweight policy configurations that can meet the condition policy is greater than 1, then the specific selection is determined by the terminal device's own policy. Specifically, the lightweight method and lightweight policy configuration with the smallest precision loss among multiple lightweight methods and lightweight policy configurations that meet the condition policy can be selected based on the principle of minimum precision loss. The first lightweight method and lightweight policy configuration that meets the condition policy found by the terminal device can also be selected. One can even be randomly selected from all lightweight methods and lightweight policy configurations that meet the condition policy. For example, when the model residual file is very sparse, the terminal device tends to use the model pruning method to process the residual file. Therefore, in this case, the specific method for determining the lightweight method and lightweight policy configuration needs to be flexibly determined according to the actual situation and is not limited here.

[0217] S204: The terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight strategy configuration.

[0218] In this embodiment, the terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight policy configuration determined in step S204.

[0219] It should be understood that when the policy information is any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy, if the lightweight method and the lightweight policy configuration are determined by the terminal device according to the policy information, in this case, since the lightweight method and the lightweight policy configuration are determined by the terminal device according to the policy information, then if the determined lightweight method and lightweight policy configuration can meet the lightweight capability of the terminal device, the terminal device can implement them. Secondly, there may also be a situation where the lightweight method and lightweight policy configuration supported by the terminal device do not meet the condition policy. At this time, the lightweight fails, and the terminal device will send a second notification message to the network device. The second notification message includes the model name corresponding to the target model. The second notification message is used to indicate that the lightweight method and lightweight policy configuration supported by the terminal device cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy, that is, the terminal device fails to perform lightweight processing on the target model.

[0220] If the lightweight method and lightweight policy configuration are determined by the terminal device, and if the lightweight method and lightweight policy configuration determined by the terminal device can meet the lightweight capability of the terminal device, the terminal device can implement them. Secondly, in this case, there may also be a situation where the lightweight method and lightweight policy configuration supported by the terminal device do not meet the conditional policy. At this time, lightweighting fails, and the terminal device will send a second notification message to the network device. The second notification message includes the model name corresponding to the target model. The second notification message is used to indicate that the lightweight method and lightweight policy configuration supported by the terminal device cannot meet any one of the file size conditional policy, uplink transmission rate conditional policy, transmission time conditional policy and compression rate conditional policy, that is, the terminal device fails to perform lightweight processing on the target model.

[0221] Furthermore, if the policy information is a lightweight method and a lightweight policy configuration, that is, the lightweight method and the lightweight policy configuration are determined by the network device, then the lightweight method and the lightweight policy configuration may not meet the lightweight capabilities of the terminal device. Therefore, when the lightweight capabilities of the terminal device are not met, the terminal device will send a third notification message to the network device. The third notification message includes the model name corresponding to the target model. The third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration, that is, the terminal device fails to perform lightweight processing on the target model. Whether the terminal device sends the second notification message or the third notification message needs to be determined based on whether the terminal device successfully performs lightweight processing on the target model.

[0222] Optionally, if the policy information includes a lightweight object, the terminal device performs lightweight processing on the specified lightweight object; if the policy information does not include a lightweight object, the terminal device performs lightweight processing on a default parameter file.

[0223] Through the above embodiments, the method for network device information transmission and the method for terminal device lightweight processing are introduced. The following is an example of a network device allowing two terminal devices to perform lightweight processing on a target model through information transmission.

[0224] As can be seen from the aforementioned embodiments, the first notification message may include a model name corresponding to the target model, or a model name corresponding to the target model and model parameters of the target model, and the policy information may be any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy, or the policy information may be a lightweight method and a lightweight policy configuration. The following describes situations where the policy information is different information.

[0225] 1. The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

[0226] See also Figure 7 , Figure 7 This is a schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application. The lightweight processing method specifically includes the following steps.

[0227] S301. A network device receives device registration messages sent by two terminal devices.

[0228] In this embodiment, two terminal devices (terminal device A and terminal device B) both send a device registration message to the network device. The device registration message includes the device information of the terminal device. When the network device training task is triggered, the network device can determine the target model to be trained and execute step S302.

[0229] S302: The network device determines the terminal devices that participate in model training.

[0230] In this embodiment, when a network device training task is triggered, the network device selects the terminal devices that need to participate in model training of the target model to be trained through an internal algorithm. In this embodiment, terminal device A and terminal device B both need to participate in model training as an example.

[0231] S303. The network device sends a model training message to two terminal devices.

[0232] In this embodiment, the network device sends a model training message to the terminal device A and the terminal device B. The model training message includes the model name of the target model and the model file of the target model.

[0233] S304: The terminal device uses local data to perform model training on the target model to be trained.

[0234] In this embodiment, after terminal device A and terminal device B receive the model training message, terminal device A uses the local data corresponding to terminal device A to perform model training on the target model to be trained, and terminal device B uses the local data corresponding to terminal device B to perform model training on the target model to be trained.

[0235] S305: The terminal device completes model training of the target model to be trained, obtains the target model, and sends a first notification message to the network device.

[0236] In this embodiment, terminal device A and terminal device B both complete model training of the target model to be trained, obtain the target model, and send a first notification message to the network device. The specific first notification message is similar to the previous embodiment and will not be repeated here.

[0237] S306: The network device obtains uplink channel status information of the two terminal devices.

[0238] In this embodiment, after the network device receives the first notification message sent by the two terminal devices in step S305, it triggers an uplink channel measurement process for terminal device A and terminal device B, thereby obtaining uplink channel state information of terminal device A and terminal device B. Furthermore, the network device also allocates corresponding uplink transmission resources to terminal device A and terminal device B respectively based on the obtained uplink channel state information.

[0239] S307: The network device determines policy information according to the uplink channel status information of the two terminal devices.

[0240] In this embodiment, since the first notification message may include the model name corresponding to the target model, or the model name corresponding to the target model and the model parameters of the target model. Therefore, when the first notification message includes the model name corresponding to the target model, the network device needs to determine the policy information based on the uplink channel state information obtained in step S306. When the first notification message includes the model name corresponding to the target model and the model parameters of the target model, the network device needs to determine the policy information based on the uplink channel state information and the model parameters of the target model obtained in step S306. The specific method of determining the policy information is similar to that of the aforementioned embodiment and will not be repeated here. Secondly, in this embodiment, the policy information is any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy.

[0241] S308. The network device sends a lightweight indication message to the two terminal devices.

[0242] In this embodiment, the network device sends a lightweight indication message to the terminal device A and the terminal device B. The lightweight indication message includes the model name and policy information corresponding to the target model. The specific method is similar to step S103 and will not be repeated here.

[0243] S309: The terminal device determines a lightweight method and a lightweight policy configuration.

[0244] In this embodiment, since terminal device A and terminal device B can receive the lightweight instruction message sent by the network device in step S308, and the lightweight instruction message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model, the terminal device can determine the lightweight method and lightweight policy configuration based on the policy information carried in the lightweight instruction message. The specific method is similar to step S203 and will not be repeated here.

[0245] S310: The terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight strategy configuration.

[0246] In this embodiment, since the policy information in this embodiment is any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy, the terminal device determines the lightweight method and lightweight policy configuration based on the policy information. The lightweight method and lightweight policy configuration meet the lightweight capability of the terminal device and also meet any one of the aforementioned condition policies. The terminal device can implement the determined lightweight method and lightweight policy configuration. Therefore, the terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight policy configuration, and the terminal device will execute step S311. Secondly, in a possible implementation method, if the lightweight method and lightweight policy configuration supported by the terminal device do not meet the condition policy, the lightweight method fails and the terminal device will execute step S312.

[0247] For example, in this embodiment, the lightweight process of terminal device A fails, while terminal device B completes the lightweight process. Therefore, terminal device A will execute step S312, while terminal device B will execute step S311.

[0248] S311. The terminal device sends a model upload message to the network device.

[0249] In this embodiment, after terminal device B executes step S310, terminal device B sends a model upload message to the network device. The model upload message includes the model name of the target model, the parameter file obtained by lightweight processing of the model parameters of the target model, the training data length of the target model, the lightweight method, and the lightweight strategy configuration.

[0250] Optionally, the model upload message may also include a lightweight object. If the lightweight object selected by the terminal device is not the default parameter file type agreed upon in advance between the terminal device and the network device, the model upload message needs to specify the lightweight object so that the network device can obtain specific information about the lightweight processing.

[0251] S312. The terminal device sends a second notification message to the network device.

[0252] In this embodiment, since the terminal device A fails to perform lightweight processing in a possible implementation method, the terminal device A needs to send a second notification message to the network device. The second notification message includes the model name corresponding to the target model. The second notification message is used to indicate that the lightweight method supported by the terminal device A and the lightweight policy configuration cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy, that is, the terminal device A fails to perform lightweight processing on the target model.

[0253] It should be understood that there is no time sequence limitation between step S311 and step S312, that is, step S311 and step S312 can be performed simultaneously or in a certain order, which should not be understood as a limitation of the embodiment.

[0254] S313: The network device updates the model parameters of the target model.

[0255] In this embodiment, when the network device receives a model upload message sent by all terminal devices that perform model training on the target model to be trained, or receives a second notification message, or reaches the maximum time limit, the network device aggregates the parameter file obtained by lightweight processing of the model parameters of the target model fed back by each terminal device that sends the model upload message through an aggregation algorithm, and updates the model parameters of the target model.

[0256] For example, since terminal device A fails to perform lightweighting, the network device can learn through the second notification message sent by terminal device A that the lightweighting method and lightweighting policy configuration supported by terminal device A cannot meet any of the file size condition policy, uplink transmission rate condition policy, transmission time condition policy and compression rate condition policy, that is, terminal device A fails to perform lightweight processing on the target model, and terminal device B will send a model upload message, so the network device can aggregate the parameter file in the model upload message sent by terminal device B and update the model parameters of the target model.

[0257] Furthermore, the network device needs to determine whether the conditions for stopping training are met at this time. If not, step 302 is executed to continue the process of training to aggregation. If so, the process ends.

[0258] 2. Strategy information includes lightweight methods and lightweight strategy configuration.

[0259] See also Figure 8 , Figure 8 This is a schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application. The lightweight processing method specifically includes the following steps.

[0260] S401: A network device receives device registration messages sent by two terminal devices.

[0261] In this embodiment, the manner in which the network device receives the device registration messages sent by the two terminal devices is similar to step S301 and will not be described in detail here.

[0262] S402: The network device determines the terminal devices that participate in model training.

[0263] In this embodiment, the manner in which the network device determines the terminal devices participating in model training is similar to step S302 and will not be repeated here.

[0264] S403. The network device sends a model training message to two terminal devices.

[0265] In this embodiment, the manner in which the network device sends the model training message to the two terminal devices is similar to step S303 and will not be repeated here.

[0266] S404: The terminal device uses local data to perform model training on the target model to be trained.

[0267] In this embodiment, the terminal device uses local data to perform model training on the target model to be trained in a manner similar to step S304, which will not be repeated here.

[0268] S405: The terminal device completes model training of the target model to be trained, obtains the target model, and sends a first notification message to the network device.

[0269] In this embodiment, the terminal device completes the model training of the target model to be trained, obtains the target model, and sends the first notification message to the network device in a manner similar to step S305, which will not be repeated here.

[0270] S406: The network device obtains uplink channel status information of two terminal devices.

[0271] In this embodiment, the manner in which the network device obtains the uplink channel state information of the two terminal devices is similar to step S306 and will not be described again here.

[0272] S407: The network device determines policy information according to the uplink channel status information of the two terminal devices.

[0273] In this embodiment, the network device determines the policy information based on the uplink channel state information of the two terminal devices in a manner similar to step S307, which will not be repeated here. However, in this embodiment, the policy information is a lightweight method and a lightweight policy configuration.

[0274] S408. The network device sends a lightweight indication message to the two terminal devices.

[0275] In this embodiment, the manner in which the network device sends the lightweight indication message to the two terminal devices is similar to step S308 and will not be repeated here.

[0276] S409: The terminal device determines a lightweight method and a lightweight policy configuration.

[0277] In this embodiment, since terminal device A and terminal device B can receive the lightweight indication message sent by the network device in step S408, and the policy information in the lightweight indication message is the lightweight method and lightweight policy configuration, the terminal devices can directly obtain the lightweight method and lightweight policy configuration. The specific method is similar to step S203 and will not be repeated here.

[0278] S410: The terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight strategy configuration.

[0279] In this embodiment, since the policy information in this embodiment is a lightweight method and a lightweight policy configuration, and since the lightweight method and the lightweight policy configuration are determined by the network device, the lightweight method and the lightweight policy configuration may not meet the lightweight capability of the terminal device. Therefore, if the lightweight capability of the terminal device is not met, the model parameters of the target model cannot be lightweight processed. Therefore, the terminal device needs to execute step S411. If the lightweight capability is met, the terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and the lightweight policy configuration, and executes step S412.

[0280] For example, in this embodiment, the lightweight process of terminal device A fails, while terminal device B completes the lightweight process. Therefore, terminal device A executes step S411, while terminal device B executes step S412.

[0281] S411. The terminal device sends a third notification message to the network device.

[0282] In this embodiment, terminal device A sends a third notification message to the network device, which includes the model name corresponding to the target model. The third notification message is used to indicate that the terminal device cannot execute the lightweight method and lightweight policy configuration, that is, terminal device A fails to perform lightweight processing on the target model.

[0283] S412: The terminal device sends a model upload message to the network device.

[0284] In this embodiment, the manner in which the terminal device sends the model upload message to the network device is similar to step S311 and will not be repeated here.

[0285] It should be understood that there is no time sequence limitation between step S411 and step S412, that is, step S411 and step S412 can be performed simultaneously or in a certain order, which should not be understood as a limitation of the embodiment.

[0286] S413: The network device updates the model parameters of the target model.

[0287] In this embodiment, when the network device receives a model upload message sent by all terminal devices that perform model training on the target model to be trained, or receives a third notification message, or reaches the maximum time limit, the network device aggregates the parameter file obtained by lightweight processing of the model parameters of the target model fed back by each terminal device that sends the model upload message through an aggregation algorithm, and updates the model parameters of the target model.

[0288] For example, since terminal device A fails to perform lightweighting, the network device can learn from the third notification message sent by terminal device A that terminal device A cannot execute the lightweighting method and lightweight policy configuration, that is, terminal device A fails to perform lightweight processing on the target model, and terminal device B sends a model upload message, so the network device can aggregate the parameter file in the model upload message sent by terminal device B and update the model parameters of the target model.

[0289] Furthermore, the network device needs to determine whether the conditions for stopping training are met at this time. If not, step 402 is executed to continue the process of training to aggregation. If so, the process ends.

[0290] As can be seen from the above embodiments, when the policy information is a lightweight method and lightweight policy configuration determined by a network device, there may be a problem where the lightweight capability of the terminal device cannot execute the lightweight method and lightweight policy configuration. Therefore, when the network device determines the policy information, if it has obtained the lightweight capability of the terminal device, and the lightweight capability is the quantization method and lightweight policy configuration that the terminal device can satisfy, then the quantization method and lightweight policy configuration determined by the network device will satisfy the lightweight capability of the terminal device, thereby avoiding the possibility of lightweight failure of the terminal device. The following describes the ways in which the network device obtains the lightweight capability of the terminal device through different messages.

[0291] 1. The device registration message carries lightweight capability information of the terminal device. The lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0292] See also Figure 9 , Figure 9 This is a schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application. The lightweight processing method specifically includes the following steps.

[0293] S501. A network device receives device registration messages sent by two terminal devices, wherein the device registration messages carry lightweight capability information of the terminal devices, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal devices.

[0294] In this embodiment, two terminal devices (terminal device A and terminal device B) each send a device registration message to the network device. This device registration message includes the terminal device's device information and carries the terminal device's lightweight capability information. The lightweight capability information indicates at least one policy information satisfied by the terminal device. Then, when a network device training task is triggered, the network device determines the target model to be trained and executes step S502.

[0295] Specifically, lightweight capabilities refer to lightweight methods defined in the standard and supported by terminal devices. Lightweight capabilities can be transmitted in plain text or bitmap form. The specific transmission method is similar to lightweight objects and will not be repeated here.

[0296] S502: The network device determines the terminal devices that participate in model training.

[0297] In this embodiment, the manner in which the network device determines the terminal devices participating in model training is similar to step S302 and will not be repeated here.

[0298] S503. The network device sends a model training message to two terminal devices.

[0299] In this embodiment, the manner in which the network device sends the model training message to the two terminal devices is similar to step S303 and will not be repeated here.

[0300] S504: The terminal device uses local data to perform model training on the target model to be trained.

[0301] In this embodiment, the terminal device uses local data to perform model training on the target model to be trained in a manner similar to step S304, which will not be repeated here.

[0302] S505: The terminal device completes model training of the target model to be trained, obtains the target model, and sends a first notification message to the network device.

[0303] In this embodiment, the terminal device completes the model training of the target model to be trained, obtains the target model, and sends the first notification message to the network device in a manner similar to step S305, which will not be repeated here.

[0304] S506: The network device obtains uplink channel status information of two terminal devices.

[0305] In this embodiment, the manner in which the network device obtains the uplink channel state information of the two terminal devices is similar to step S306 and will not be described again here.

[0306] S507: The network device determines policy information according to the uplink channel status information of the two terminal devices.

[0307] In this embodiment, since the first notification message may include the model name corresponding to the target model, or the model name corresponding to the target model and the model parameters of the target model. Therefore, when the first notification message includes the model name corresponding to the target model, the network device needs to determine the policy information based on the uplink channel state information obtained in step S506, and the determined policy information must satisfy the lightweight capability information of the terminal device obtained in step S501. When the first notification message includes the model name corresponding to the target model and the model parameters of the target model, the network device needs to determine the policy information based on the uplink channel state information and the model parameters of the target model obtained in step S506, and the determined policy information must satisfy the lightweight capability information of the terminal device obtained in step S501.

[0308] It should be understood that the specific method of determining the policy information is similar to the above embodiment, as long as the determined policy information meets the lightweight capability information of the terminal device, which will not be repeated here. In this embodiment, the policy information is a lightweight method and a lightweight policy configuration.

[0309] S508. The network device sends a lightweight indication message to the two terminal devices.

[0310] In this embodiment, the manner in which the network device sends the lightweight indication message to the two terminal devices is similar to step S308 and will not be repeated here.

[0311] S509: The terminal device determines a lightweight method and lightweight policy configuration.

[0312] In this embodiment, the manner in which the terminal device determines the lightweight method and configures the lightweight policy is similar to step S203 and will not be repeated here.

[0313] S510: The terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight strategy configuration.

[0314] In this embodiment, since the policy information (lightweight method and lightweight policy configuration) determined by the network device in step 507 satisfies the lightweight capability information of the terminal device, the terminal device will not be unable to perform lightweight processing. Therefore, the specific manner in which the terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight policy configuration is similar to step S204 and will not be repeated here. Furthermore, in this embodiment, if the terminal device cannot execute the lightweight method and lightweight policy configuration, or the lightweight method and lightweight policy configuration supported by the terminal device cannot meet any of the file size condition policy, uplink transmission rate condition policy, transmission time condition policy and compression rate condition policy, when the lightweight processing fails, refer to Figure 7 as well as Figure 8 The corresponding introduction will not be repeated here.

[0315] S511. The terminal device sends a model upload message to the network device.

[0316] In this embodiment, the manner in which the terminal device sends the model upload message to the network device is similar to step S311 and will not be repeated here.

[0317] S512: The network device updates the model parameters of the target model.

[0318] In this embodiment, the network device updates the model parameters of the target model in a manner similar to step S312, which will not be described in detail here.

[0319] 2. The network device receives a capability query confirmation message sent by the terminal device, wherein the capability query confirmation message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0320] See also Figure 10 , Figure 10 This is a schematic diagram of another embodiment of the lightweight processing method in the embodiment of the present application. The lightweight processing method specifically includes the following steps.

[0321] S601: A network device receives device registration messages sent by two terminal devices.

[0322] In this embodiment, the network device receives the device registration messages sent by the two terminal devices in a similar manner to step S301, which will not be described in detail here.

[0323] S602: The network device sends a lightweight capability query message to the terminal device, where the lightweight capability query message is used by the terminal device to determine lightweight capability information of the terminal device.

[0324] In this embodiment, the network device sends a lightweight capability query message to the terminal device, so that the terminal device determines its own lightweight capability information through the lightweight capability query message.

[0325] Specifically, lightweight capabilities refer to lightweight methods defined in the standard and supported by terminal devices. Lightweight capabilities can be transmitted in plain text or bitmap form. The specific transmission method is similar to lightweight objects and will not be repeated here.

[0326] S603: The network device receives a capability query confirmation message sent by the terminal device, wherein the capability query confirmation message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

[0327] In this embodiment, after the terminal device determines its lightweight capability information, it sends a capability query confirmation message to the network device. This capability query confirmation message carries the terminal device's lightweight capability information, which indicates at least one policy information that the terminal device satisfies. Thus, the network device obtains the terminal device's lightweight capability information. Then, when a training task is triggered on the network device, the network device can determine the target model to be trained.

[0328] S604: The network device determines the terminal devices that participate in model training.

[0329] In this embodiment, the manner in which the network device determines the terminal devices participating in model training is similar to step S302 and will not be repeated here.

[0330] S605. The network device sends a model training message to two terminal devices.

[0331] In this embodiment, the manner in which the network device sends the model training message to the two terminal devices is similar to step S303 and will not be repeated here.

[0332] S606: The terminal device uses local data to perform model training on the target model to be trained.

[0333] In this embodiment, the terminal device uses local data to perform model training on the target model to be trained in a manner similar to step S304, which will not be repeated here.

[0334] S607: The terminal device completes model training of the target model to be trained, obtains the target model, and sends a first notification message to the network device.

[0335] In this embodiment, the terminal device completes the model training of the target model to be trained, obtains the target model, and sends the first notification message to the network device in a manner similar to step S305, which will not be repeated here.

[0336] S608: The network device obtains uplink channel status information of the two terminal devices.

[0337] In this embodiment, the manner in which the network device obtains the uplink channel state information of the two terminal devices is similar to step S306 and will not be described again here.

[0338] S609: The network device determines policy information according to the uplink channel status information of the two terminal devices.

[0339] In this embodiment, the manner in which the network device determines the policy information according to the uplink channel state information of the two terminal devices is similar to step S507 and will not be described in detail here.

[0340] S610. The network device sends a lightweight indication message to two terminal devices.

[0341] In this embodiment, the manner in which the network device sends the lightweight indication message to the two terminal devices is similar to step S308 and will not be repeated here.

[0342] S611. The terminal device determines a lightweight method and lightweight policy configuration.

[0343] In this embodiment, the manner in which the terminal device determines the lightweight method and configures the lightweight policy is similar to step S203 and will not be repeated here.

[0344] S612: The terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight strategy configuration.

[0345] In this embodiment, the terminal device performs lightweight processing on the model parameters of the target model according to the lightweight method and lightweight policy configuration in a manner similar to step S510, which will not be repeated here.

[0346] S613: The terminal device sends a model upload message to the network device.

[0347] In this embodiment, the manner in which the terminal device sends the model upload message to the network device is similar to step S311 and will not be repeated here.

[0348] S614: The network device updates the model parameters of the target model.

[0349] In this embodiment, the network device updates the model parameters of the target model in a manner similar to step S312, which will not be described in detail here.

[0350] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of method. It is understandable that, in order to realize the above functions, the communication device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the modules and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0351] The embodiment of the present application can divide the functional modules of the communication device based on the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0352] The communication device in this application is described in detail below. Figure 11 , Figure 11 This is a schematic diagram of an embodiment of a communication device in an embodiment of the present application. As shown in the figure, the communication device 700 includes a transceiver module 701 and a processing module 702.

[0353] Optionally, the communication device 700 may correspond to the network device in the above method embodiment, for example, it may be a network device, or a component configured in the network device (such as a circuit, a chip or a chip system, etc.).

[0354] It should be understood that the communication device 700 may correspond to the embodiment of the present application. Figure 5 The method in, or, Figure 7 The method in, or, Figure 8 The method in, or, Figure 9 The method in, or, Figure 10 In the method, the communication device 700 may include a device for performing Figure 5 The method in, or, Figure 7 The method in, or, Figure 8 The method in, or, Figure 9 The method in, or, Figure 10 Furthermore, the units in the communication device 700 and the above-mentioned other operations and / or functions are respectively for implementing Figure 5 The method in, or, Figure 7The method in, or, Figure 8 The method in, or, Figure 9 The method in, or, Figure 10 The corresponding process of the method in .

[0355] Wherein, when the communication device 700 is used to perform Figure 5 When the method is used, the transceiver module 701 can be used to execute Figure 5 In step S101 and step S103 of the method, the processing module 702 can be used to perform Figure 5 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0356] When the communication device 700 is used to perform Figure 7 When the method is used, the transceiver module 701 can be used to execute Figure 7 In the method of step S301, step S305 and step S311 or step S312, the processing module 702 can be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0357] When the communication device 700 is used to perform Figure 8 When the method is used, the transceiver module 701 can be used to execute Figure 7 In the method of step S401, step S405, step S411 and step S412, the processing module 702 can be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0358] When the communication device 700 is used to perform Figure 9 When the method is used, the transceiver module 701 can be used to perform Figure 7 In the method of step S501, step S505 and step S511, the processing module 702 can be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0359] When the communication device 700 is used to perform Figure 10 When the method is used, the transceiver module 701 can be used to perform Figure 7 In the method of step S601, step S602, step S603, step S605, step S607 and step S613, the processing module 702 can be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0360] It should also be understood that when the communication device 700 is a network device, the transceiver module 701 in the communication device 700 can be implemented by a transceiver, for example, corresponding to Figure 13 The transceiver 920 in the communication device 900 shown in FIG or the remote radio unit (RRU) 4100 in the network device 4000 shown in FIG, the processing module 702 in the communication device 700 may be implemented by at least one processor, for example, corresponding to Figure 13 The processor 910 or the processor 910 in the communication device 900 shown in FIG. Figure 15 The processing unit 4200 or processor 4202 in the network device 4000 is shown.

[0361] It should also be understood that when the communication device 700 is a chip or chip system configured in a network device, the transceiver module 701 in the communication device 700 can be implemented through an input / output interface, circuit, etc., and the processing module 702 in the communication device 700 can be implemented through a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0362] Second, see Figure 12 , Figure 12 This is a schematic diagram of another embodiment of a communication device in an embodiment of the present application. As shown in the figure, the communication device 800 includes a transceiver module 801 and a processing module 802.

[0363] Optionally, the communication device 800 may correspond to the terminal device in the above method embodiment, for example, it may be a terminal device, or a component configured in the terminal device (such as a circuit, a chip or a chip system, etc.).

[0364] It should be understood that the communication device 800 may correspond to the embodiment of the present application. Figure 6 The method in, or, Figure 7 The method in, or, Figure 8 The method in, or, Figure 9 The method in, or, Figure 10 In the method, the communication device 800 may include a method for performing Figure 6 The method in, or, Figure 7 The method in, or, Figure 8 The method in, or, Figure 9 The method in, or, Figure 10 Furthermore, the units in the communication device 800 and the above-mentioned other operations and / or functions are respectively for realizing Figure 6 The method in, or, Figure 7 The method in, or, Figure 8 The method in, or, Figure 9 The method in, or, Figure 10 The corresponding process of the method in .

[0365] Wherein, when the communication device 800 is used to perform Figure 6 When the method is used, the transceiver module 801 can be used to perform Figure 6 In step S201 of the method and without going to S202, the processing module 802 can be used to perform Figure 4 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0366] When the communication device 800 is used to perform Figure 7 When the method is used, the transceiver module 801 can be used to perform Figure 7 In the method of step S301, step S303, step S305, step S306, step S308 and step S311 or step 312, the processing module 802 can be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0367] When the communication device 800 is used to perform Figure 8 When the method is used, the transceiver module 801 can be used to perform Figure 8 In the method of step S401, step S403, step S405, step S406, step S408, step S411 and step S412, the processing module 802 can be used to perform Figure 8 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0368] When the communication device 800 is used to perform Figure 9 When the method is used, the transceiver module 801 can be used to perform Figure 9In the method of step S501, step S503, step S505, step S506, step S508 and step S511, the processing module 802 can be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0369] When the communication device 800 is used to perform Figure 10 When the method is used, the transceiver module 801 can be used to perform Figure 10 In the method of step S601, step S602, step S603, step S605, step S607, step S608, step S610, and step S613, the processing module 802 may be used to perform Figure 7 It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0370] It should also be understood that when the communication device 800 is a terminal device, the transceiver module 801 in the communication device 800 can be implemented by a transceiver, for example, corresponding to Figure 13 The transceiver 920 or the communication device 900 shown in FIG. Figure 14 The transceiver 3020 in the terminal device 3000 shown in FIG, the processing module 802 in the communication device 800 may be implemented by at least one processor, for example, corresponding to Figure 13 The processor 910 or the processor 910 in the communication device 900 shown in FIG. Figure 14 The processor 3010 in the terminal device 3000 is shown.

[0371] It should also be understood that when the communication device 800 is a chip or chip system configured in a terminal device, the transceiver module 801 in the communication device 800 can be implemented through an input / output interface, circuit, etc., and the processing module 802 in the communication device 800 can be implemented through a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0372] Figure 13 FIG. 9 is a schematic block diagram of a communication device 900 in an embodiment of the present application. Figure 13 As shown, the communication device 900 includes a processor 910, a transceiver 920, and a memory 930. The processor 910, the transceiver 920, and the memory 930 communicate with each other via an internal connection path. The memory 930 is used to store instructions, and the processor 910 is used to execute the instructions stored in the memory 930 to control the transceiver 920 to send and / or receive signals.

[0373] It should be understood that the communication device 900 can correspond to the terminal device in the above-mentioned method embodiment, and can be used to execute the various steps and / or processes performed by the network device or terminal device in the above-mentioned method embodiment. Optionally, the memory 930 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. The memory 930 can be a separate device or integrated into the processor 910. The processor 910 can be used to execute the instructions stored in the memory 930, and when the processor 910 executes the instructions stored in the memory, the processor 910 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the network device or terminal device.

[0374] Optionally, the communication device 900 is the terminal device in the above embodiment.

[0375] Optionally, the communication device 900 is the network device in the above embodiment.

[0376] The transceiver 920 may include a transmitter and a receiver. The transceiver 920 may further include an antenna, which may be one or more. The processor 910, memory 930, and transceiver 920 may be integrated on different chips. For example, the processor 910 and memory 930 may be integrated in a baseband chip, and the transceiver 920 may be integrated in a radio frequency chip. The processor 910, memory 930, and transceiver 920 may also be integrated on the same chip. This application does not limit this.

[0377] Optionally, the communication device 900 is a component configured in a terminal device, such as a circuit, a chip, a chip system, etc.

[0378] Optionally, the communication device 900 is a component configured in a network device, such as a circuit, a chip, a chip system, etc.

[0379] The transceiver 920 may also be a communication interface, such as an input / output interface, a circuit, etc. The transceiver 920 , the processor 910 , and the memory 920 may all be integrated into the same chip, such as a baseband chip.

[0380] Figure 14 3000 is a schematic diagram of the structure of the terminal device 3000 provided in the embodiment of the present application. The terminal device 3000 can be applied to Figure 1In the system shown, the functions of the terminal device in the above-described method embodiment are performed. As shown in the figure, the terminal device 3000 includes a processor 3010 and a transceiver 3020. Optionally, the terminal device 3000 also includes a memory 3030. The processor 3010, the transceiver 3020, and the memory 3030 can communicate with each other via an internal connection path to transmit control and / or data signals. The memory 3030 is used to store a computer program, and the processor 3010 is used to call and execute the computer program from the memory 3030 to control the transceiver 3020 to transmit and receive signals. Optionally, the terminal device 3000 may also include an antenna 3040 for transmitting uplink data or uplink control signaling output by the transceiver 3020 via wireless signals.

[0381] The processor 3010 and the memory 3030 can be combined into a communication device, and the processor 3010 is used to execute the program code stored in the memory 3030 to implement the above functions. In specific implementation, the memory 3030 can also be integrated into the processor 3010, or independent of the processor 3010. The processor 3010 can be combined with the memory 3030 to form a communication device. Figure 12 Processing module 802 or Figure 13 Corresponding to the processor 910 in .

[0382] The transceiver 3020 can be used with Figure 12 The transceiver module 801 or Figure 13 The transceiver 3020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.

[0383] It should be understood that Figure 14 The terminal device 3000 shown can realize Figure 6 , Figure 7 , Figure 8 , Figure 9 as well as Figure 10 The illustrated method embodiments involve various processes of the terminal device. The operations and / or functions of the various modules in the terminal device 3000 are respectively for implementing the corresponding processes in the aforementioned method embodiments. For details, please refer to the description of the aforementioned method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.

[0384] The processor 3010 can be used to execute the actions implemented within the terminal device described in the previous method embodiments, while the transceiver 3020 can be used to execute the actions of the terminal device sending to or receiving from the network device described in the previous method embodiments. For details, please refer to the description of the previous method embodiments and will not be repeated here.

[0385] Optionally, the terminal device 3000 may further include a power supply 3050 for providing power to various devices or circuits in the terminal device.

[0386] In addition, in order to make the functions of the terminal device more complete, the terminal device 3000 may also include one or more of an input unit 3060, a display unit 3070, an audio circuit 3080, a camera 3090 and a sensor 3100, and the audio circuit may also include a speaker 3082, a microphone 3084, etc.

[0387] Figure 15 This is a schematic diagram of the structure of the network device provided in the embodiment of the present application, for example, a schematic diagram of the structure of a base station. The base station 4000 can be applied to Figure 1 In the system shown, the functions of the network device in the above method embodiment are performed. As shown in the figure, the base station 4000 may include one or more radio frequency units, such as RRU4100 and one or more baseband units (BBU) (also known as distributed units (DU)) 4200. The RRU 4100 may be called a transceiver unit and may be connected to the base station 4000. Figure 11 The transceiver module 701 or Figure 13 . Optionally, the RRU 4100 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., and may include at least one antenna 4101 and a radio frequency unit 4102. Optionally, the RRU 4100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit). The RRU 4100 part is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals, for example, for sending indication information to terminal devices. The BBU 4200 part is mainly used for baseband processing, controlling the base station, etc. The RRU 4100 and the BBU 4200 may be physically arranged together or physically separated, that is, a distributed base station.

[0388] The BBU 4200 is the control center of the base station, which can also be called a processing unit. Figure 11 Processing module 702 or Figure 13 The processor 910 in the embodiment corresponds to the baseband processor 910, which is mainly used to perform baseband processing functions such as channel coding, multiplexing, modulation, spread spectrum, etc. For example, the BBU (processing unit) can be used to control the base station to execute the operation process of the network device in the above method embodiment, such as generating the above indication information.

[0389] In one example, the BBU 4200 may be composed of one or more single boards, and the multiple single boards may jointly support a wireless access network of a single access standard (such as an LTE network), or may separately support wireless access networks of different access standards (such as an LTE network, a 5G network, or other networks). The BBU 4200 also includes a memory 4201 and a processor 4202. The memory 4201 is used to store necessary instructions and data. The processor 4202 is used to control the base station to perform necessary actions, such as controlling the base station to execute the operation process of the network device in the above method embodiment. The memory 4201 and the processor 4202 can serve one or more single boards. That is, a memory and a processor can be set separately on each single board. Alternatively, multiple single boards may share the same memory and processor. In addition, necessary circuits may also be set on each single board.

[0390] It should be understood that Figure 15 The base station 4000 shown is capable of Figure 5 , Figure 7 , Figure 8 , Figure 9 as well as Figure 10 The illustrated method embodiments involve various processes of network devices. The operations and / or functions of the various modules in base station 4000 are respectively for implementing the corresponding processes in the aforementioned method embodiments. For details, please refer to the description of the aforementioned method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.

[0391] The BBU 4200 can be used to perform the actions implemented within the network device described in the previous method embodiments, while the RRU 4100 can be used to perform the actions described in the previous method embodiments, where the network device sends or receives data to or from a terminal device. For details, please refer to the description in the previous method embodiments and will not be repeated here.

[0392] It should be understood that Figure 15 The base station 4000 shown is only one possible form of network equipment and should not constitute any limitation to this application. The method provided in this application is applicable to network equipment in other forms. For example, it may include an AAU, and may also include a CU and / or DU, or include a BBU and an adaptive radio unit (ARU), or a BBU; it may also be customer premises equipment (CPE), or it may be in other forms. This application does not limit the specific form of the network equipment.

[0393] The CU and / or DU can be used to perform the actions implemented within the network device described in the previous method embodiments, while the AAU can be used to perform the actions described in the previous method embodiments where the network device sends or receives information to or from the terminal device. For details, please refer to the description in the previous method embodiments and will not be repeated here.

[0394] The present application also provides a communication device, comprising at least one processor, wherein the at least one processor is configured to execute a computer program stored in a memory, so that the communication device executes the method executed by the terminal device or network device in any of the above method embodiments.

[0395] It should be understood that the above-mentioned communication device may be one or more chips. For example, the communication device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0396] An embodiment of the present application further provides a communication device, comprising a processor and a communication interface. The communication interface is coupled to the processor. The communication interface is configured to input and / or output information. The information includes at least one of instructions and data. The processor is configured to execute a computer program to cause the communication device to perform the method performed by the terminal device or network device in any of the above method embodiments.

[0397] The present application also provides a communication device including a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program from the memory, so that the communication device executes the method executed by the terminal device or network device in any of the above method embodiments.

[0398] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0399] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0400] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0401] According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: a computer program code, which, when executed on a computer, causes the computer to execute Figures 5 to 10 The method executed by the terminal device or the method executed by the network device in the illustrated embodiment.

[0402] According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores a program code, and when the program code is run on a computer, the computer executes Figures 5 to 10 The method executed by the terminal device or the method executed by the network device in the illustrated embodiment.

[0403] According to the method provided in the embodiment of the present application, the present application also provides a system, which includes one or more terminal devices and one or more network devices as mentioned above.

[0404] The network devices in the above-mentioned various apparatus embodiments completely correspond to the network devices or terminal devices in the terminal devices and method embodiments, and the corresponding steps are performed by the corresponding modules or units. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be referred to the corresponding method embodiments. Among them, there can be one or more processors.

[0405] In the above embodiments, a terminal device can be used as an example of a receiving device, and a network device can be used as an example of a sending device. However, this does not constitute any limitation on the present application. For example, both the sending device and the receiving device can be terminal devices. The present application does not limit the specific types of the sending device and the receiving device.

[0406] As used in this specification, the terms "component," "module," "system," and the like are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0407] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0408] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0409] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0410] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0411] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0412] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0413] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for information transmission, characterized in that: include: The network device receives a first notification message sent by the terminal device, wherein the first notification message is used to indicate that the terminal device has completed training of the target model, and the first notification message includes a model name corresponding to the target model; The network device determines policy information based on the uplink channel state information of the terminal device, wherein the policy information is used by the terminal device to determine a lightweight method and a lightweight policy configuration, and the lightweight method and lightweight policy configuration determined by the terminal device through the policy information are consistent with the uplink transmission capability of the terminal device; The network device sends a lightweight indication message to the terminal device, wherein the lightweight indication message includes the model name corresponding to the target model and the policy information, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

2. The method according to claim 1, characterized in that The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The method further comprises: The network device receives a second notification message sent by the terminal device, wherein the second notification message includes the model name corresponding to the target model, and the second notification message is used to indicate that the terminal device cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy.

3. The method according to claim 1, characterized in that The strategy information includes the lightweight method and the lightweight strategy configuration; The method further comprises: The network device receives a third notification message sent by the terminal device, wherein the third notification message includes a model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration.

4. The method according to claim 1, wherein The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The method further comprises: The network device receives a model upload message sent by the terminal device, wherein the model upload message carries the lightweight method and the lightweight policy configuration.

5. The method according to claim 1, wherein The first notification message includes model parameter information of the target model; The network device determines the policy information according to the uplink channel state information of the terminal device, including: The network device determines the policy information according to the model parameter information of the target model and the uplink channel state information of the terminal device.

6. The method according to claim 5, characterized in that The strategy information includes the lightweight method and the lightweight strategy configuration; or, The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

7. The method according to claim 6, characterized in that The policy information includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

8. The method according to claim 1, characterized in that The method further comprises: The network device receives a device registration message sent by the terminal device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

9. The method according to claim 1, characterized in that The method further comprises: The network device sends a lightweight capability query message to the terminal device, wherein the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device; The network device receives a capability query confirmation message sent by the terminal device, wherein the capability query confirmation message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

10. The method according to claim 9, characterized in that The lightweight capability query message includes a model name corresponding to the target model.

11. The method according to any one of claims 1 to 10, characterized in that The lightweight indication message further includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

12. A lightweight processing method, characterized in that: include: The terminal device sends a first notification message to the network device, wherein the first notification message is used to indicate that the terminal device has completed training of the target model, and the first notification message includes a model name corresponding to the target model; The terminal device receives a lightweight indication message sent by the network device, wherein the lightweight indication message includes a model name and policy information corresponding to the target model, the policy information is determined according to the uplink channel state information of the terminal device, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model; The terminal device determines a lightweight method and a lightweight policy configuration according to the policy information, wherein the lightweight method and the lightweight policy configuration determined by the terminal device through the policy information comply with the uplink transmission capability of the terminal device; The terminal device performs lightweight processing on the model parameter information of the target model according to the lightweight method and the lightweight strategy configuration.

13. The method according to claim 12, characterized in that The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The method further comprises: The terminal device sends a second notification message to the network device, wherein the second notification message includes the model name corresponding to the target model, and the second notification message is used to indicate that the terminal device cannot meet any one of the file size condition policy, the uplink transmission rate condition policy, the transmission time condition policy and the compression rate condition policy.

14. The method according to claim 12, characterized in that The strategy information includes the lightweight method and the lightweight strategy configuration; The method further comprises: The terminal device sends a third notification message to the network device, wherein the third notification message includes a model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration.

15. The method according to claim 12, characterized in that The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The method further comprises: The terminal device sends a model upload message to the network device, wherein the model upload message carries the lightweight method and the lightweight policy configuration.

16. The method according to claim 12, characterized in that The first notification message includes model parameter information of the target model.

17. The method according to claim 16, characterized in that The strategy information includes the lightweight method and the lightweight strategy configuration; or, The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

18. The method according to claim 16, characterized in that The policy information includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

19. The method according to claim 18, characterized in that The terminal device determines a lightweight method and a lightweight policy configuration according to the policy information, including: The terminal device determines the lightweight method, the lightweight policy configuration, and the lightweight object according to the policy information; The terminal device performs lightweight processing on the model parameter information of the target model according to the lightweight method and the lightweight strategy configuration, including: The terminal device performs lightweight processing on the model parameter information of the target model that meets the target type according to the lightweight method and the lightweight policy configuration.

20. The method according to claim 12, wherein The method further comprises: The terminal device sends a device registration message to the network device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

21. The method according to claim 12, wherein The method further comprises: The terminal device receives a lightweight capability query message sent by the network device, wherein the lightweight capability query message is used by the terminal device to determine lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device; The terminal device determines, according to the lightweight capability query message, the at least one policy information that is satisfied; The terminal device sends a capability query confirmation message to the network device, wherein the capability query confirmation message carries lightweight capability information of the terminal device.

22. The method according to claim 21, characterized in that The lightweight capability query message includes a model name corresponding to the target model.

23. The method according to any one of claims 12 to 22, characterized in that The lightweight indication message further includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

24. A communication device, characterized in that: The communication device is a network device, including: A transceiver module, configured to receive a first notification message sent by a terminal device, wherein the first notification message is used to indicate that the terminal device has completed training of a target model, and the first notification message includes a model name corresponding to the target model; a processing module, configured to determine policy information based on the uplink channel state information of the terminal device, wherein the policy information is used by the terminal device to determine a lightweight method and a lightweight policy configuration, and the lightweight method and lightweight policy configuration determined by the terminal device through the policy information are consistent with the uplink transmission capability of the terminal device; The transceiver module is also used to send a lightweight indication message to the terminal device, wherein the lightweight indication message includes the model name corresponding to the target model and the policy information, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model.

25. The communication device according to claim 24, characterized in that The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The transceiver module is also used to receive a second notification message sent by the terminal device, wherein the second notification message includes the model name corresponding to the target model, and the second notification message is used to indicate that the terminal device cannot meet any one of the file size condition strategy, the uplink transmission rate condition strategy, the transmission time condition strategy and the compression rate condition strategy.

26. The communication device according to claim 24, characterized in that The strategy information includes the lightweight method and the lightweight strategy configuration; The transceiver module is also used to receive a third notification message sent by the terminal device, wherein the third notification message includes the model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration.

27. The communication device according to claim 24, wherein: The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The transceiver module is further configured to receive a model upload message sent by the terminal device, wherein the model upload message carries the lightweight method and the lightweight strategy configuration.

28. The communication device according to claim 24, wherein: The first notification message includes model parameter information of the target model; The processing module is specifically configured to determine the strategy information based on the model parameter information of the target model and the uplink channel state information of the terminal device.

29. The communication device according to claim 28, characterized in that The strategy information includes the lightweight method and the lightweight strategy configuration; or, The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

30. The communication device according to claim 29, wherein: The policy information includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

31. The communication device according to claim 24, wherein: The transceiver module is further used to receive a device registration message sent by the terminal device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

32. The communication device according to claim 24, wherein: The transceiver module is further configured to send a lightweight capability query message to the terminal device, wherein the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device; The transceiver module is further used to receive a capability query confirmation message sent by the terminal device, wherein the capability query confirmation message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

33. The communication device according to claim 32, wherein: The lightweight capability query message includes a model name corresponding to the target model.

34. The communication device according to any one of claims 24 to 33, characterized in that The lightweight indication message further includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

35. A communication device, characterized in that: The communication device is a terminal device, including: A transceiver module, configured to send a first notification message to a network device, wherein the first notification message is used to indicate that the terminal device has completed training of a target model, and the first notification message includes a model name corresponding to the target model; The transceiver module is further configured to receive a lightweight indication message sent by the network device, wherein the lightweight indication message includes a model name corresponding to the target model and policy information, where the policy information is determined based on the uplink channel state information of the terminal device; a processing module, configured to determine a lightweight method and a lightweight policy configuration according to the policy information, wherein the lightweight method and the lightweight policy configuration determined by the terminal device through the policy information comply with the uplink transmission capability of the terminal device; The processing module is further configured to perform lightweight processing on the model parameter information of the target model according to the lightweight method and the lightweight strategy configuration.

36. The communication device according to claim 35, characterized in that The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The transceiver module is also used to send a second notification message to the network device, wherein the second notification message includes the model name corresponding to the target model, and the second notification message is used to indicate that the terminal device cannot meet any one of the file size condition strategy, the uplink transmission rate condition strategy, the transmission time condition strategy and the compression rate condition strategy.

37. The communication device according to claim 35, wherein: The strategy information includes the lightweight method and the lightweight strategy configuration; The transceiver module is also used to send a third notification message to the network device, wherein the third notification message includes the model name corresponding to the target model, and the third notification message is used to indicate that the terminal device cannot execute the lightweight method and the lightweight policy configuration.

38. The communication device according to claim 35, wherein: The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy; The transceiver module is further configured to send a model upload message to the network device, wherein the model upload message carries the lightweight method and the lightweight policy configuration.

39. The communication device according to claim 35, wherein: The first notification message includes model parameter information of the target model.

40. The communication device according to claim 39, wherein: The strategy information includes the lightweight method and the lightweight strategy configuration; or, The policy information is any one of a file size condition policy, an uplink transmission rate condition policy, a transmission time condition policy, and a compression rate condition policy.

41. The communication device according to claim 39, wherein: The policy information includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

42. The communication device according to claim 41, wherein: The processing module is specifically configured to determine the lightweight method, the lightweight strategy configuration, and the lightweight object according to the strategy information; The processing module is specifically configured to perform lightweight processing on the model parameter information of the target model that meets the target type according to the lightweight method and the lightweight strategy configuration.

43. The communication device according to claim 35, wherein: The transceiver module is further used to send a device registration message to the network device, wherein the device registration message carries lightweight capability information of the terminal device, and the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device.

44. The communication device according to claim 35, wherein: The transceiver module is further configured to receive a lightweight capability query message sent by the network device, wherein the lightweight capability query message is used by the terminal device to determine the lightweight capability information of the terminal device, the lightweight capability information is used to indicate at least one policy information satisfied by the terminal device, and the lightweight indication message is used to instruct the terminal device to perform lightweight processing on the model parameter information of the target model; The processing module is further configured to determine the at least one policy information satisfied according to the lightweight capability query message; The transceiver module is further configured to send a capability query confirmation message to the network device, wherein the capability query confirmation message carries the lightweight capability information of the terminal device.

45. The communication device according to claim 44, characterized in that The lightweight capability query message includes a model name corresponding to the target model.

46. ​​The communication device according to any one of claims 35 to 45, characterized in that The lightweight indication message further includes a lightweight object, wherein the lightweight object is used to indicate a target type of the model parameter information of the target model.

47. A network device, characterized in that: include: Processor, memory, input and output interfaces; The processor is coupled to the memory and the input / output interface; The processor executes the method according to any one of claims 1 to 11 by running the code in the memory.

48. A terminal device, characterized in that: include: Processor, memory, input and output interfaces; The processor is coupled to the memory and the input / output interface; The processor executes the method according to any one of claims 12 to 23 by running the code in the memory.

49. A chip, characterized in that The chip includes at least one processor, which is communicatively connected to at least one memory, and the at least one memory stores instructions; the instructions are executed by the at least one processor to execute the method described in any one of claims 1 to 11, or to execute the method described in any one of claims 12 to 23.

50. A computer-readable storage medium storing instructions, which, when the instructions are executed on a computer, enable the computer to execute the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 23.

51. A communication system comprising a network device and a terminal device, wherein the network device executes the method according to any one of claims 1 to 11, and the terminal device executes the method according to any one of claims 12 to 23.

Images