Communication method and device

Abstract

This application relates to a communication method and a device. The communication method includes: transmitting, by a first device, a first message to a second device, where the first message is used to request at least one of the following operations: downloading application model data or adding application model data; updating application model data or modifying application model data; uploading application model data; or deleting application model data.

What is claimed is: 
     
         1 . A first device, comprising a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to invoke the computer program stored in the memory and run the computer program, to cause the first device to execute a method of:
 transmitting a first message to a second device, wherein the first message is used to request at least one of following operations:   downloading application model data or adding application model data;   updating application model data or modifying application model data;   uploading application model data; or   deleting application model data.   
     
     
         2 . The first device according to  claim 1 , wherein the first message comprises at least one of following:
 model identifier information corresponding to at least one application model that is requested to be downloaded or added;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be downloaded or added;   model identifier information corresponding to at least one application model that is requested to be updated or modified;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be updated or modified;   model identifier information corresponding to at least one application model that is requested to be uploaded;   model quality of service QoS requirement information corresponding to at least one application model that is requested to be uploaded;   model data size indication information corresponding to at least one application model that is requested to be uploaded;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be uploaded;   QoS requirement information of a model data sub-block corresponding to at least one application model that is requested to be uploaded;   sub-block data size indication information of a model data sub-block corresponding to at least one application model that is requested to be uploaded;   model identifier information corresponding to at least one application model that is requested to be deleted; or   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be deleted.   
     
     
         3 . The first device according to  claim 1 , wherein the first device is further configured to:
 receive a second message from the second device, wherein the second message comprises at least one of following:   model identifier information corresponding to at least one application model that is allowed to be downloaded or added;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be downloaded or added;   model identifier information corresponding to at least one application model that is allowed to be updated or modified;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be updated or modified;   model identifier information corresponding to at least one application model that is allowed to be uploaded;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be uploaded;   model identifier information corresponding to at least one application model that is allowed to be deleted;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be deleted;   model identifier information corresponding to at least one application model that is not allowed to be downloaded or added;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added;   model identifier information corresponding to at least one application model that is not allowed to be updated or modified;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified;   model identifier information corresponding to at least one application model that is not allowed to be uploaded;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be uploaded;   model identifier information corresponding to at least one application model that is not allowed to be deleted; or   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be deleted.   
     
     
         4 . The first device according to  claim 1 , wherein the first device is further configured to:
 receive an application model data transmission configuration message from the second device, wherein the application model data transmission configuration message is used to determine resource configuration information for transmitting the corresponding application model data; and   receive the application model data based on the resource configuration information comprised in the application model data transmission configuration message.   
     
     
         5 . The first device according to  claim 4 , wherein the first device is further configured to:
 reassemble the received application model data;   wherein for reassembling the received application model data, the first device is further configured to:   reassemble the received application model data through a NAS, a packet data convergence protocol PDCP layer, a service data adaptation protocol SDAP layer, or a protocol layer dedicated to reassembly of the application model data.   
     
     
         6 . The first device according to  claim 1 , wherein the first device is further configured to:
 reassemble based on content of the control message, the application model data that is received via a plurality of control messages;   wherein for reassembling, based on content of the control message, the application model data that is received via a plurality of control messages, the first device is further configured to:   reassemble the received application model data through a NAS, an RRC layer, or a protocol layer dedicated to reassembly of the application model data.   
     
     
         7 . The first device according to  claim 5 , wherein after the reassembling the received application model data, the first device is further configured to:
 transfer reassembled application model data to an application model data management module; or   transfer reassembled application model data to a corresponding function module according to a preset rule;   wherein the preset rule comprises any one of following:   the reassembled application model data is transferred to the corresponding function module based on model identifier information corresponding to the application model data;   the reassembled application model data is transferred to the corresponding function module based on route indication information comprised in the application model data; or   the reassembled application model data is transferred to the corresponding function module based on model identifier information corresponding to the application model data and route indication information comprised in the application model data;   wherein the function module comprises any one of following: an application layer, the NAS, an RRC layer, the SDAP layer, the PDCP layer, an RLC layer, a MAC layer, a BAP layer, or a physical layer.   
     
     
         8 . The first device according to  claim 1 , wherein the first device is further configured to:
 determine, in a pre-configuration manner or a default manner, model data format control information corresponding to at least one application model.   
     
     
         9 . The first device according to  claim 1 , wherein the first device comprises a terminal device, or the second device comprises a network device or a terminal device. 
     
     
         10 . A second device, comprising a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to invoke the computer program stored in the memory and run the computer program, to cause the second device to execute a method of:
 receiving a first message from a first device, wherein the first message is used to request at least one of following operations:   downloading application model data or adding application model data;   updating application model data or modifying application model data;   uploading application model data; or   deleting application model data.   
     
     
         11 . The second device according to  claim 10 , wherein the second device is further configured to:
 transmit the first device, a control message comprising the application model data, wherein the control message comprises at least one of following:   the application model data;   model identifier information corresponding to a first application model to which the application model data belongs;   a sequence number of the application model data in the first application model;   sub-block identifier information corresponding to a first model data sub-block in a first application model to which the application model data belongs;   a sequence number of the application model data in the first model data sub-block;   control message indication information, wherein the control message indication information is used to indicate whether a current control message is a last segment of a control message; or   a control message segment sequence number, wherein the control message segment sequence number is used to indicate a segment sequence number of a current control message in a control message.   
     
     
         12 . The second device according to  claim 10 , wherein the second device is further configured to:
 receive a third message from the first device, wherein the third message is used to request performing an operation related to registration of the application model data, and/or used to request obtaining model data format control information;   wherein the third message comprises at least one of following:   model identifier information corresponding to at least one application model that is requested to be registered;   model identifier information corresponding to at least one application model whose registration is requested to be updated;   model identifier information corresponding to at least one application model that is requested to be de-registered; or   indication information that requests obtaining the model data format control information.   
     
     
         13 . The second device according to  claim 10 , wherein the second device is further configured to: transmit a fourth message to the first device, wherein the fourth message comprises at least one of following:
 model identifier information corresponding to at least one application model that has been registered successfully;   model data format control information corresponding to at least one application model that has been registered successfully;   operation condition control information corresponding to at least one application model that has been registered successfully;   model identifier information corresponding to at least one application model that fails to be registered;   failure cause information corresponding to at least one application model that fails to be registered;   model identifier information corresponding to at least one application model whose registration has been updated successfully;   model data format control information corresponding to at least one application model whose registration has been updated successfully;   operation condition control information corresponding to at least one application model whose registration has been updated successfully;   model identifier information corresponding to at least one application model whose registration fails to be updated;   failure cause information corresponding to at least one application model whose registration fails to be updated;   model identifier information corresponding to at least one application model that has been de-registered successfully;   model identifier information corresponding to at least one application model that fails to be de-registered; or   failure cause information corresponding to at least one application model that fails to be de-registered.   
     
     
         14 . The second device according to  claim 12 , wherein the model data format control information comprises at least one of following:
 model QoS requirement information corresponding to an application model;   model data size indication information corresponding to an application model;   model check control information corresponding to an application model;   model transmission security-related control information corresponding to an application model; or   model data block control information corresponding to an application model;   wherein the model data block control information corresponding to an application model comprises at least one of following:   a quantity of model data sub-blocks corresponding to one application model;   sub-block identifier information corresponding to each model data sub-block;   QoS requirement information corresponding to each model data sub-block;   data size indication information corresponding to each model data sub-block;   check control information corresponding to each model data sub-block; or   model transmission security-related control information corresponding to each model data sub-block.   
     
     
         15 . The second device according to  claim 10 , wherein the second device is further configured to:
 receive first capability indication information from the first device, wherein the first capability indication information is used to indicate whether the first device is capable of supporting an application model-related operation.   
     
     
         16 . The second device according to  claim 10 , wherein the second device is further configured to:
 transmit on/off indication information to the first device, wherein the on/off indication information is used to indicate whether the first device is allowed to perform an application model-related operation.   
     
     
         17 . The second device according to  claim 15 , wherein the application model-related operation comprises at least one of following:
 downloading the application model data or adding the application model data;   updating the application model data or modifying the application model data;   uploading the application model data;   deleting the application model data;   registering the application model data;   updating registration of the application model data;   de-registering the application model data; or   requesting obtaining format control information of the application model data.   
     
     
         18 . A communication method, comprising:
 transmitting, by a first device, a first message to a second device, wherein the first message is used to request at least one of following operations:   downloading application model data or adding application model data;   updating application model data or modifying application model data;   uploading application model data; or   deleting application model data.   
     
     
         19 . The method according to  claim 18 , wherein the first message comprises at least one of following:
 model identifier information corresponding to at least one application model that is requested to be downloaded or added;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be downloaded or added;   model identifier information corresponding to at least one application model that is requested to be updated or modified;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be updated or modified;   model identifier information corresponding to at least one application model that is requested to be uploaded;   model quality of service QoS requirement information corresponding to at least one application model that is requested to be uploaded;   model data size indication information corresponding to at least one application model that is requested to be uploaded;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be uploaded;   QoS requirement information of a model data sub-block corresponding to at least one application model that is requested to be uploaded;   sub-block data size indication information of a model data sub-block corresponding to at least one application model that is requested to be uploaded;   model identifier information corresponding to at least one application model that is requested to be deleted; or   sub-block identifier information of a model data sub-block corresponding to at least one application model that is requested to be deleted.   
     
     
         20 . The method according to  claim 18 , further comprising:
 receiving, by the first device, a second message from the second device, wherein the second message comprises at least one of following:   model identifier information corresponding to at least one application model that is allowed to be downloaded or added;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be downloaded or added;   model identifier information corresponding to at least one application model that is allowed to be updated or modified;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be updated or modified;   model identifier information corresponding to at least one application model that is allowed to be uploaded;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be uploaded;   model identifier information corresponding to at least one application model that is allowed to be deleted;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is allowed to be deleted;   model identifier information corresponding to at least one application model that is not allowed to be downloaded or added;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added;   model identifier information corresponding to at least one application model that is not allowed to be updated or modified;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified;   model identifier information corresponding to at least one application model that is not allowed to be uploaded;   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be uploaded;   model identifier information corresponding to at least one application model that is not allowed to be deleted; or   sub-block identifier information of a model data sub-block corresponding to at least one application model that is not allowed to be deleted.