Communication method and device

Abstract

The invention relates to a communication method and equipment, and the communication method comprises the steps that first equipment sends a first message to second equipment, and the first message is used for requesting at least one of the following operations: application model data downloading or application model data adding; updating the application model data or modifying the application model data; uploading application model data; and deleting the application model data. According to the invention, the management of the model can be realized.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] With the continuous development of artificial intelligence (AI) and machine learning (ML) technologies, the combination of communication technology and AI / ML technology is one of the trends in future communications. Due to the complexity of communication system scenarios, different communication scenarios may require the use of different models for optimization processing. How to manage the models has become a technical problem that needs to be solved.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and device that can implement model management.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The first device sends a first message to the second device, where the first message is used to request at least one of the following operations:

[0007] Download or add application model data;

[0008] Application model data update or application model data modification;

[0009] Application model data upload;

[0010] Apply model data deletion.

[0011] This embodiment of the present application provides another communication method, including:

[0012] The second device receives a first message from the first device, where the first message is used to request at least one of the following operations:

[0013] Download or add application model data;

[0014] Application model data update or application model data modification;

[0015] Application model data upload;

[0016] Apply model data deletion.

[0017] An embodiment of the present application provides a first device, including:

[0018] The first sending module is configured to send a first message, where the first message is used to request at least one of the following operations:

[0019] Download or add application model data;

[0020] Application model data update or application model data modification;

[0021] Application model data upload;

[0022] Apply model data deletion.

[0023] An embodiment of the present application provides a second device, including:

[0024] The first receiving module is configured to receive a first message from a first device, where the first message is used to request at least one of the following operations:

[0025] Download or add application model data;

[0026] Application model data update or application model data modification;

[0027] Application model data upload;

[0028] Apply model data deletion.

[0029] An embodiment of the present application provides a device including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory so that the terminal device executes the above-mentioned communication method.

[0030] An embodiment of the present application provides a chip for implementing the above-mentioned communication method.

[0031] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.

[0032] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to execute the above-mentioned communication method.

[0033] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.

[0034] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.

[0035] In an embodiment of the present application, the management of the model can be achieved by sending a first message for requesting application model data-related operations to a second device through a first device. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0037] FIG2 is a schematic flowchart of a communication method 200 according to an embodiment of the present application.

[0038] FIG3 is a schematic diagram of the overall flow of model data transmission according to an embodiment of the present application.

[0039] FIG4 is a schematic flowchart of a communication method 400 according to an embodiment of the present application.

[0040] FIG5 is a schematic block diagram of a first device 500 according to an embodiment of the present application.

[0041] FIG6 is a schematic block diagram of a first device 600 according to an embodiment of the present application.

[0042] FIG7 is a schematic block diagram of a second device 700 according to an embodiment of the present application.

[0043] FIG8 is a schematic block diagram of a second device 800 according to an embodiment of the present application.

[0044] FIG9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application.

[0045] FIG10 is a schematic block diagram of a chip 1000 according to an embodiment of the present application.

[0046] FIG11 is a schematic block diagram of a communication system 1100 according to an embodiment of the present application. DETAILED DESCRIPTION

[0047] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0048] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0049] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0050] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0051] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0052] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (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 device, etc.

[0053] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0054] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0055] In an embodiment of the present application, the terminal device may 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 device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0056] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0057] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0058] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0059] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0060] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0061] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0062] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0063] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0064] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0065] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0066] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0067] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0068] In recent years, artificial intelligence research and related achievements have achieved remarkable results in many fields. Artificial intelligence has become a new approach for people to solve and address problems. Among these numerous research areas, neural network-based artificial intelligence research is an extremely important one. The basic structure of a simple neural network consists of an input layer, a hidden layer, and an output layer. The input layer receives data, the hidden layer processes the data, and the output layer produces the final result.

[0069] With the continuous development of neural network research, neural network deep learning algorithms have been proposed in recent years. This multi-hidden layer neural network structure has greatly improved the processing capabilities of the network and has been widely used in pattern recognition, signal processing, optimization combination, anomaly detection and other aspects.

[0070] Similarly, with the development of deep learning, convolutional neural networks have also been further studied. The basic structure of a convolutional neural network includes an input layer, multiple convolutional layers, multiple pooling layers, a fully connected layer, and an output layer. The introduction of convolutional and pooling layers effectively controls the rapid increase in network parameters, limits the number of parameters, exploits the characteristics of local structures, and improves the robustness of the algorithm.

[0071] With the continuous development of artificial intelligence (AI) and machine learning (ML) technologies, the combination of communication technology and AI / ML technology is one of the trends in future communications. Due to the complexity of communication system scenarios, such as paging, measurement, mobility and other application scenarios, different communication scenarios may require the use of different AI / ML models for optimization processing. The management of a large number of AI / ML models will become complicated, and how to manage AI / ML models has become a technical problem that needs to be solved. The embodiments of this application propose solutions for efficiently downloading, updating or deleting model data.

[0072] FIG2 is a schematic flow chart of a communication method 200 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0073] S210. The first device sends a first message to the second device, where the first message is used to request at least one of the following operations:

[0074] Download or add application model data;

[0075] Application model data update or application model data modification;

[0076] Application model data upload;

[0077] Apply model data deletion.

[0078] In an embodiment of the present application, the first device sends a first message to the second device for requesting relevant operations on application model data, thereby enabling management of the model.

[0079] In one implementation, the first device in the embodiment of the present application may include a terminal device.

[0080] In one implementation, the second device in the embodiment of the present application may include a network device or a terminal device.

[0081] Among them, the network equipment may include access network equipment, core network equipment or application model control equipment.

[0082] For example, the application model control device can be a special access network device or a special core network device. The application model control device can be mainly used to manage the application model, such as: executing model data transmission, registration management, model data storage, and model data addition, update, deletion, modification, upload, download and other operations.

[0083] In some implementations, the data module corresponding to the application model data proposed in the embodiments of the present application includes at least one of the following:

[0084] Model input data module, model output data module, model training data module, model inference data module, model storage data module, model calculation data module, model structure data module and model coordination control data module.

[0085] It should be noted that the data corresponding to an application model may be divided into several data submodules, each corresponding to a portion of the model's logical functionality. In one implementation, each data submodule is assigned a model data subblock identifier to facilitate model data management. For example, downloading and updating model data at the model data subblock granularity is more efficient than downloading the entire application model data.

[0086] In some implementations, the application model corresponding to the application model data proposed in the embodiments of the present application includes at least one of the following:

[0087] AI models, ML models, supercomputing models, neuron-like models, authentication models, encryption and decryption models, and self-optimization models.

[0088] For example, the application model itself can be understood as a special data block, and there is a potential for overall collaboration between the data in the data blocks. Depending on the function, the application model data can usually be divided into one or more model data sub-blocks. This data division mode facilitates the flexible and differentiated transmission of model data.

[0089] In some implementations, the first message may include at least one of the following:

[0090] Model identification information corresponding to at least one application model requested to be downloaded or added;

[0091] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be downloaded or added;

[0092] Model identification information corresponding to at least one application model requested to be updated or modified;

[0093] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be updated or modified;

[0094] Model identification information corresponding to at least one application model requested to be uploaded;

[0095] Model Quality of Service (QoS) requirement information corresponding to at least one application model requested to be uploaded;

[0096] Model data size indication information corresponding to at least one application model requested to be uploaded;

[0097] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0098] QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0099] Sub-block data size indication information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0100] Model identification information corresponding to at least one application model requested to be deleted;

[0101] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

[0102] By sending the first information to the network device or the second terminal device, the first terminal device can request the network device or the second terminal device to download, add, update, modify, upload, delete, and other operations on the application model or the model data sub-block in the application model, and provide the network device or the second terminal device with the relevant information required to perform the aforementioned operations.

[0103] Example 1:

[0104] FIG3 is a schematic diagram of the overall flow of model data transmission according to an embodiment of the present application. As shown in FIG3 , the contents of each step are as follows:

[0105] Step 1: A first device (such as a first terminal device) sends first capability indication information to a second device (such as a network device or a second terminal device), where the first capability indication information is used to indicate whether the first device has the capability to support application model-related operations.

[0106] Step 2-1: A first device (such as a first terminal device) receives second capability indication information from a second device (such as a network device or a second terminal device), where the second capability indication information indicates whether the second device has the capability to support application model-related operations.

[0107] Step 2-2: The first device (such as the first terminal device) receives switch indication information from the second device (such as the network device or the second terminal device), where the switch indication information is used to indicate whether the first device is allowed to enable the function of performing application model-related operations.

[0108] Among them, step 1 and step 2-1 are both optional steps. There may be a scenario with only step 1 but not step 2-1, a scenario with only step 2-1 but not step 1, or a scenario with both step 1 and step 2-1. In the latter scenario, the step 2-1 message may be a response message to the step 1 message, or it may be a message independent of step 1. If step 2-1 and step 1 are independent messages, then the logical order in which step 1 and step 2-1 are sent is not limited. At the same time, this application does not limit the order in which step 1 and step 2-1 are sent relative to other steps. Figure 3 is only an example, and this application does not limit the above description.

[0109] Furthermore, step 2-2 is also optional. If the first device does not receive the switch indication information from the second device, it may be assumed that the first device is allowed to enable the function of performing application model-related operations. Alternatively, if the first device does not receive the switch indication information from the second device, the first device may determine whether to enable the function of performing application model-related operations based on the message content in step 2-1. This embodiment of the application does not limit the order of step 2-2 and other steps.

[0110] Step 3a-1: The first device (eg, the first terminal device) sends a third message to the second device (eg, the network device or the second terminal device). The third message may be used to request application model data registration operations and / or to request model data format control information.

[0111] Step 3a-2: The first device (eg, the first terminal device) receives a fourth message from the second device (eg, the network device or the second terminal device).

[0112] Step 3a-1 and step 3a-2 are both optional steps and can be implemented in the following three ways:

[0113] Implementation method 1: In the scenario where only step 3a-1 is performed but step 3a-2 is not performed, the third message sent by the first terminal device does not require a response message from the network device or the second terminal device. For example, the model registration request content of the first terminal device will be accepted by the network device or the second terminal device by default, so the network device or the second terminal device does not need to respond to the model registration request of the first terminal device.

[0114] Implementation method 2: The scenario with only step 3a-2 but no step 3a-1. In this case, the first terminal device only passively receives the fourth message sent by the network device or the second terminal device. Under this implementation method, the first terminal device does not need to send a model registration request message. For example, the network device or the second terminal device sends the content of the fourth message as updated configuration information to the first terminal device. Then, the network device or the second terminal device initiating the fourth message does not depend on whether the first terminal device sends the third message, because the configuration information update operation can be triggered at any time based on the implementation.

[0115] Implementation method three: In the scenario where step 3a-1 and step 3a-2 exist at the same time, the fourth message of step 3a-2 is a response message to the third message of step 3a-1. For example, the first terminal device sends a third message requesting registration of model 1 and model 2, and the network device or the second terminal device replies to the first terminal device through the fourth message that only model 2 is approved for registration; or, the first terminal device sends a third message requesting registration of model 1 and model 2, and the network device or the second terminal device replies to the first terminal device through the fourth message that the third message is successfully received. This method implies that the content of the third message requesting registration is approved by the network device or the second terminal device.

[0116] The embodiments of the present application do not limit any of the above implementation methods.

[0117] Step 3b: The first terminal device determines the information required to send the first message through a preconfigured manner or a default manner; for example, determines the model data format control information corresponding to at least one application model.

[0118] Step 3b is optional. The logical relationship between step 3a (including step 3a-1 and / or step 3a-2) and step 3b may be as follows:

[0119] Implementation method 1: Step 3a and step 3b occur simultaneously, wherein step 3a is used to complete the application model data registration related operations, and step 3b is used to determine the model data format control information corresponding to at least one application model;

[0120] Implementation method two: Step 3a and step 3b occur simultaneously, wherein step 3a is used to complete the application model data registration related operations and obtain the model data format control information, or step 3a is only used to obtain the model data format control information, and step 3b is used to determine the model data format control information corresponding to at least one application model. Since both step 3a and step 3b can be used to obtain the model data format control information, if the model data format control information obtained by the above two steps for the same application model data is different, the conflict can be resolved by defining a priority. For example, the model data format control information obtained by step 3a always has a higher priority than the model data format control information obtained by step 3b. Of course, the protocol may also define in which scenarios the model data format control information obtained in step 3b covers the content obtained in step 3a, and in which scenarios the model data format control information obtained in step 3a covers the content obtained in step 3b. This application does not limit this;

[0121] Implementation method three: only step 3a is included, wherein step 3a is used to complete the application model data registration related operations and / or obtain the model data format control information;

[0122] Implementation method 4: only step 3b, wherein step 3b is used to obtain model data format control information.

[0123] Step 4: The first device (such as the first terminal device) sends a first message to the second device (such as the network device or the second terminal device). The first message can be used to request at least one of the operations of downloading, adding, updating, modifying, uploading, and deleting the application model data.

[0124] In some implementations, the first message may be a non-access stratum (NAS) message, an access stratum (AS) message, or an application model operation-specific control message.

[0125] Step 5: The first device (such as the first terminal device) receives a second message from the second device (such as the network device or the second terminal device). The second message can be used to indicate whether the operation requested by the first message is allowed.

[0126] In some implementations, the second message may be a non-access stratum (NAS) message, an access stratum (AS) message, or an application model operation-specific control message.

[0127] Step 5 is optional. In some implementations, the second message does not appear.

[0128] Step 6a-1: The first device (such as the first terminal device) receives an application model data transmission configuration message from the second device (such as the network device or the second terminal device). The application model data transmission configuration message is used to determine the resource configuration information required to transmit the corresponding application model data.

[0129] Step 6a-2: The first device (such as the first terminal device) receives or uploads the application model data according to the resource configuration information included in the application model data transmission configuration message.

[0130] Through step 6a-1 and step 6a-2, after receiving the application model data, the first device can reorganize the received application model data.

[0131] Step 6b: The first device (eg, the first terminal device) receives a control message containing application model data from the second device (eg, the network device or the second terminal device).

[0132] Through step 6b, after receiving the application model data, the first device can reorganize the application model data received through multiple control messages according to the content of the control message.

[0133] Steps 6a and 6b are optional. Generally speaking, step 6b and step 6a (including step 6a-1 and step 6a-2) do not need to occur at the same time. Either step 6b or step 6a can independently achieve the purpose of transmitting application model data. Of course, this application does not exclude the scenario where both steps 6a and 6b are defined at the same time. In this case, the second device decides whether to send the application model data through step 6a or step 6b.

[0134] It should be additionally noted that when step 6a and / or step 6b appear (are defined), step 4 may not appear. For example, the second device directly transmits the application model data to the first device through step 6a or step 6b. At this time, the first device does not need to send the first message requesting the transmission of the corresponding application model data.

[0135] In some implementations, after the first device reorganizes the received application model data, the method further includes:

[0136] Pass the reorganized application model data to the application model data management module; or,

[0137] The reorganized application model data is passed to the corresponding functional module according to the preset rules.

[0138] The application model data management module is used to uniformly manage all application model data within the first device.

[0139] The above preset rules can be any of the following:

[0140] According to the model identification information corresponding to the application model data, the reorganized application model data is passed to the corresponding functional module;

[0141] According to the routing indication information contained in the application model data, the reorganized application model data is passed to the corresponding functional module;

[0142] The reorganized application model data is transferred to the corresponding functional module according to the model identification information corresponding to the application model data and the routing indication information contained in the application model data.

[0143] The above-mentioned functional module can be at least one of the following: application layer, NAS layer, radio resource control (RRC, Radio Resource Control) layer, service data adaptation protocol (SDAP, Service Data Adaptation Protocol) layer, packet data convergence protocol (PDCP, Packet Data Convergence Protocol) layer, radio link control (RLC, Radio Link Control) layer, media access control (MAC, Media Access Control) layer, backhaul adaptation protocol (BAP, Backhaul Adaptation Protocol) layer or physical layer.

[0144] The following examples describe the messages in each of the above steps in detail.

[0145] Example 2:

[0146] In this example, the first message in step 4 in FIG. 3 may include at least one of the following information:

[0147] Information 1: Model identification information corresponding to at least one application model requested to be downloaded or added;

[0148] Information 2: sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be downloaded or added;

[0149] Information 3: Model identification information corresponding to at least one application model requested to be updated or modified;

[0150] Information 4: sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be updated or modified;

[0151] Information 5: Model identification information corresponding to at least one application model requested to be uploaded;

[0152] Information 6: Model QoS requirement information corresponding to at least one application model requested to be uploaded;

[0153] Information 7: Model data size indication information corresponding to at least one application model requested to be uploaded

[0154] Information 8: sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0155] Information 9: QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0156] Information 10: data size indication information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0157] Information 11: model identification information corresponding to at least one application model requested to be deleted;

[0158] Information 12: sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

[0159] In some implementations, the first message may include a NAS message, an AS message, or an application model operation-specific control message.

[0160] The AS message may be any one of the following types of messages: a radio resource control (RRC) message, a media access control (MAC) control element (CE) message, or an uplink control information (UCI) message.

[0161] Among them, the above-mentioned application model operation-specific control message can be a message specially defined for the application model, which is used to carry control information related to executing the application model operation.

[0162] There are at least two implementation methods for information 1 and information 2:

[0163] Method 1:

[0164] In this method, the corresponding functions of information 1 and information 2 can be realized through Table 1:

[0165]

[0166] Table 1

[0167] In Table 1, N is a positive integer. As shown in Table 1, the list type parameters associated with Information 1 and Information 2 include at least one list element, each of which contains a mandatory field and an optional field. The mandatory field carries the model identification information corresponding to the application model requested for download, and the optional field carries the model sub-block identification list corresponding to the model requested for download. The model sub-block identification list may contain sub-block identification information corresponding to at least one model data sub-block requested for download.

[0168] If only mandatory fields appear in a certain list element, it indicates that the first terminal device requests to completely download all the data of the corresponding application model; if mandatory fields and optional fields appear at the same time in a certain list element, it indicates that the first terminal device requests to download part of the data of the corresponding application model (i.e., not all the data of the corresponding application model), and indicates which data parts (data model sub-blocks) of the corresponding application model are desired to be downloaded through the optional fields. The implementation method of Table 1 can flexibly realize three functions, namely: only requesting all the data of at least one application model (a scenario in which no optional fields appear in the list elements), only requesting part of the data of at least one application model (a scenario in which all optional fields appear in the list elements), or simultaneously requesting all the data of at least one application model and requesting part of the data of at least one application model (a scenario in which the optional fields of some elements in the list elements do not appear, and the optional fields of the remaining elements in the list elements appear).

[0169] Method 2:

[0170] In this method, the corresponding functions of information 1 and information 2 can be realized through Table 2:

[0171]

[0172] Table 2

[0173] In Table 2, N is a positive integer. As shown in Table 2, Information 1 and Information 2 correspond to different parameters. The parameter corresponding to Information 1 is used to request the complete download of all data of at least one application model; while the list-type parameter corresponding to Information 2 includes at least one list element, each of which contains two sub-parameters: model identification information and a model sub-block identification list corresponding to the model requested for download (the model sub-block identification list may include sub-block identification information corresponding to at least one model data sub-block requested for download).

[0174] It should be noted that the first message may only contain information 1 or only contain information 2, and Tables 1 and 2 are examples of implementation methods based on the first message containing both information 1 and information 2. This application is not limited to any of the above definitions, that is, the first message can contain at least one of information 1 and information 2.

[0175] In the first message, information 3 is used to request an update or modification of all data of the corresponding application model, and information 4 is used to request an update or modification of a specified portion of data of the corresponding application model (the corresponding model data sub-block). The implementation of the corresponding functions of information 3 and information 4 is similar to the implementation of the corresponding functions of information 1 and information 2, that is, information 3 and information 4 can be implemented in two ways as shown in Tables 1 and 2 above. For specific implementation methods, please refer to the implementation methods of information 1 and information 2 in Tables 1 and 2 above, which will not be repeated here. In addition, the first message may also contain only information 3 or only information 4.

[0176] Implementation description of information 5 to information 10: Information 5 is used to request uploading of all data of the corresponding application model, and information 8 can be used to request uploading of a specified portion of data of the corresponding application model (the corresponding model data sub-block). The implementation methods of the corresponding functions of information 5 and information 8 are similar to the implementation methods of the corresponding functions of information 1 and information 2, that is, information 5 and information 8 can be implemented in the two ways shown in Tables 1 and 2 above. For specific implementation methods, please refer to the implementation methods of information 1 and information 2 in Tables 1 and 2 above, which will not be repeated here. In addition, the first message may also contain only information 5 or only information 8.

[0177] QoS requirement information can reflect the transmission requirement characteristics of data (such as transmission delay requirements, transmission throughput requirements, transmission bit error rate requirements, etc.). Information 6 is supplementary information to information 5, which can provide the network device or the second terminal device with the corresponding application model data transmission requirement information, so that the network device or the second terminal device can configure the corresponding resources to transmit the corresponding application model data. For example, the first terminal device requests to upload the data corresponding to application model 1, and at the same time informs the network device or the second terminal device that the QoS requirement corresponding to the application model 1 data is very high. Then, when the network device or the second terminal device configures the resources corresponding to the transmission of application model 1 data for the first terminal device, it can consider using a retransmission mechanism to ensure the transmission reliability of application model 1 data; conversely, the first terminal device requests to upload the data corresponding to application model 2, and at the same time informs the network device or the second terminal device that the QoS requirement corresponding to the application model 2 data is low. Then, when the network device or the second terminal device configures the resources corresponding to the transmission of application model 2 data for the first terminal device, it can consider not using a retransmission mechanism. Since the QoS requirement corresponding to application model 2 data is low, the model transmission requirement can also be met without using a retransmission mechanism.

[0178] Information 9 is supplementary information to information 8, and can provide the network device or the second terminal device with the transmission requirement information of the corresponding application model data sub-block, so that the network device or the second terminal device can configure the corresponding resources to transmit the corresponding application model data sub-block. For the data corresponding to an application model, the QoS requirements of each model data sub-block may be different. For example, the model structure module data may be higher than other module data, so the QoS requirement of the model structure module data may be very high. Then, the corresponding transmission resources can try to use a more reliable transmission method; for other module data, since the QoS requirement of the data is generally relatively low, it is also possible to consider a transmission method with appropriately reduced reliability (although the transmission reliability is reduced, the QoS requirement is still met). After all, a low-reliability transmission method generally has a higher transmission rate than a reliable transmission method (because it does not require frequent retransmission).

[0179] The configuration granularity of the QoS requirements in the above information 6 and information 9 is any one of the following configuration granularities:

[0180] Configure according to the granularity of application model identification, for example: all data corresponding to an application model share the same QoS requirement;

[0181] Configure according to the granularity of the application model sub-block identifier, for example: the data corresponding to an application model sub-block shares the same QoS requirement;

[0182] The configuration is performed according to the granularity of the application model sub-block identifier group, for example, the data corresponding to a group of application model sub-blocks share a common QoS requirement.

[0183] Information 7 is also supplementary to Information 5 and can be used to inform the network device or the second terminal device of the size of the model data to be uploaded. Informing the network device or the second terminal device of the size of the model data to be uploaded facilitates the network device or the second terminal device to reasonably allocate data transmission resources and also facilitates the final verification of the model data and verifies the security of the transmission.

[0184] Information 10 is also supplementary information to information 8 and can be used to inform the network device or the second terminal device of the size of the model data sub-block corresponding to the model data to be uploaded. The function of information 10 is similar to that of information 7 and will not be repeated here.

[0185] Description of the implementation of information 11 and information 12: Information 11 is used to request the deletion of all data of the corresponding application model, and information 12 is used to request the deletion of a specified portion of data of the corresponding application model (the corresponding model data sub-block). The implementation of the corresponding functions of information 11 and information 12 is similar to the implementation of the corresponding functions of information 1 and information 2, that is, information 11 and information 12 can be implemented in two ways as shown in Tables 1 and 2 above. For specific implementation methods, please refer to the implementation methods of information 1 and information 2 in Tables 1 and 2 above, which will not be repeated here. In addition, the first message may also contain only information 11 or only information 12.

[0186] It should be noted that the reason why information 1 to information 4 and information 11 and information 12 in the first message are not associated with corresponding QoS requirements and data size indication information is because the QoS requirement information and data size indication information are generally provided by the data sender. If the first terminal device serves as the data receiver, then the first terminal device does not need to provide such information to the data sender (network device or second terminal device).

[0187] Example 3:

[0188] In this example, the second message in step 5 in FIG. 3 may include at least one of the following information:

[0189] Model identification information corresponding to at least one application model allowed to be downloaded or added;

[0190] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be downloaded or added;

[0191] Model identification information corresponding to at least one application model that is allowed to be updated or modified;

[0192] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be updated or modified;

[0193] Model identification information corresponding to at least one application model allowed to be uploaded;

[0194] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be uploaded;

[0195] Model identification information corresponding to at least one application model that is allowed to be deleted;

[0196] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be deleted;

[0197] Model identification information corresponding to at least one application model that is not allowed to be downloaded or added;

[0198] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added;

[0199] Model identification information corresponding to at least one application model that is not allowed to be updated or modified;

[0200] Identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified;

[0201] Model identification information corresponding to at least one application model that is not allowed to be uploaded;

[0202] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be uploaded;

[0203] Model identification information corresponding to at least one application model that is not allowed to be deleted;

[0204] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model that is not allowed to be deleted.

[0205] In some implementations, the second message may include a NAS message, an AS message, or an application model operation-specific control message.

[0206] The AS message may be any one of the following types of messages: an RRC message, a MAC CE message, or a downlink control information (DCI) message.

[0207] Among them, the above-mentioned application model operation-specific control message can be a message specially defined for the application model, which is used to carry control information related to executing the application model operation.

[0208] The second message can be used as a response message to the first message, and the second message is an optional message. In one implementation, the second message does not appear. At this time, the network device or the second terminal device directly configures the model data transmission resource for the first terminal device through step 6a-1 of Figure 3. Since the model data transmission resource is associated with the corresponding model data that needs to be transmitted, the model data transmission resource itself can implicitly inform the first terminal device which model data is allowed to be transmitted and which model data is not allowed to be transmitted, thereby implicitly realizing the notification function of the above-mentioned second message; in another implementation, the second message appears and includes at least one of the above information. The purpose is also to inform the first terminal device which model data is allowed to be transmitted and which model data is not allowed to be transmitted. This method is an explicit notification method. In another implementation, the second message exists but is only used to notify the first terminal device whether the first message is successfully received. The default network device or the second terminal device needs to accept all requests contained in the first message sent by the first terminal device. This application does not limit the above implementation.

[0209] Example 4:

[0210] As shown in step 6a-1 in FIG. 3 , the first terminal device receives an application model data transmission configuration message sent by the network device or the second terminal device. The application model data transmission configuration message is used to determine resource configuration information required to transmit corresponding application model data.

[0211] For example, the resource configuration information required for transmitting the corresponding application model data may include configuration information of each communication sublayer of the data plane protocol stack, and the communication sublayer may include at least one of the following:

[0212] Model data adaptation layer, SDAP layer, PDCP layer, BAP layer, RLC layer, MAC layer and physical (PHY) layer.

[0213] Among them, the model data adaptation layer can be used to perform special processing on the model data, such as: segmenting, reorganizing, and retransmitting the model data.

[0214] In one implementation, the terminal device (such as the first terminal device in FIG3 ) forwards the first message content to the core network device or the application model control device through the access network device. After the core network device or the application model control device agrees to establish a model data transmission session for the terminal device, the core network device or the application model control device notifies the access network device to establish a model data transmission context for the terminal device. The access network device then configures the resource configuration information required for transmitting the corresponding application model data for the terminal device.

[0215] In another implementation, the terminal device (such as the first terminal device in FIG3 ) directly sends the first message content to the access network device, and the access network device establishes a model data transmission session for the terminal device and configures the resource configuration information required for transmitting the corresponding application model data for the terminal device through a reconfiguration process;

[0216] In another implementation method, the terminal device (such as the first terminal device in Figure 3) directly sends the first message content to the application model control device, and the application model control device establishes a model data transmission session for the terminal device, and configures the resource configuration information required for the transmission of the corresponding application model data for the terminal device through a reconfiguration process.

[0217] In addition, a hybrid of the above three implementation methods may be used, for example, different model data may use different request implementation methods.

[0218] Regardless of the above implementation method, the model data storage location can be any of the following:

[0219] All model data is stored in the core network equipment;

[0220] All model data is stored in the access network equipment;

[0221] All model data are stored in the application model control device;

[0222] Part of the model data is stored in the core network equipment, and the other part of the model data is stored in the access network equipment.

[0223] As shown in step 6a-2 of Figure 3 , the first terminal device receives application model data sent by the network device or the second terminal device based on the resource configuration information included in the application model data transmission configuration message. The first terminal device may then reassemble the received application model data. For example, the first terminal device reassembles the received application model data via the NAS layer, PDCP layer, SDAP layer, or a protocol layer dedicated to application model data reassembly.

[0224] Furthermore, after the first terminal device reorganizes the received application model data, the first terminal device further includes:

[0225] The reorganized application model data is passed to the application model data management module; or, the reorganized application model data is passed to the corresponding functional module according to preset rules.

[0226] In one embodiment, the preset rule may be any one of the following:

[0227] According to the model identification information corresponding to the application model data, the reorganized application model data is passed to the corresponding functional module;

[0228] According to the routing indication information contained in the application model data, the reorganized application model data is passed to the corresponding functional module;

[0229] The reorganized application model data is transferred to the corresponding functional module according to the model identification information corresponding to the application model data and the routing indication information contained in the application model data.

[0230] For example, the above functional module may be any one of the following: application layer, NAS layer, RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, BAP layer or physical layer.

[0231] Example 5:

[0232] As shown in step 6b of FIG. 3 , the first terminal device receives a control message including application model data sent by the network device or the second terminal device; the control message includes at least one of the following:

[0233] Apply model data;

[0234] Model identification information corresponding to the first application model to which the application model data belongs;

[0235] a serial number of the application model data in the first application model;

[0236] sub-block identification information corresponding to a first model data sub-block in a first application model to which the application model data belongs;

[0237] a serial number of the application model data in the first model data sub-block;

[0238] Control message indication information, where the control message indication information is used to indicate whether the current control message is the last segment of the control message;

[0239] The control message segment sequence number is used to indicate which segment the current control message belongs to.

[0240] Using the above approach, embodiments of the present application can divide an application model or a model digital sub-block within an application model into multiple segments, each of which is sent using a control message. In this way, a network device or a second terminal device can use multiple control messages to send multiple segments of the same application model or a model data sub-block within the same application model to a first terminal device, and the control messages can carry information such as the sequence number of the segment. This allows the first terminal device to combine the segments into an application model or a model digital sub-block after receiving the multiple control messages. That is, the first device can reassemble the application model data received via multiple control messages based on the content of the control messages.

[0241] For example, generally speaking, control messages can carry a smaller amount of data, while application models can carry a larger amount of data. For application model 1, the network device divides application model 1 into 100 pieces of data (i.e., 100 application model data sub-blocks) and uses 100 control messages to send these 100 pieces of application model data to the first terminal device. Each control message also includes model identification information corresponding to the application model to which the application model data belongs (i.e., application model 1), as well as the sequence number of the application model data in application model 1. Upon receiving these control messages, the first terminal device can reassemble the 100 application model data sub-blocks belonging to application model 1 based on the model identification information and sequence number carried in each control message to obtain application model 1. For another example, each control message also includes control message indication information indicating whether the current control message is the last segment of the control message, as well as a control message segment sequence number indicating the segment number of the control message to which the current control message belongs. Based on this information, the first terminal device receiving these control messages can reassemble the application model data belonging to the same application model in the control messages.

[0242] In some implementations, the first device reorganizes application model data received through multiple control messages according to control message content, including:

[0243] The first device reorganizes the received application model data through the NAS layer, the RRC layer, or a protocol layer dedicated to the reorganization of the application model data.

[0244] For example, the control message may include a NAS layer message, an RRC message, or a control message dedicated to application model data transmission.

[0245] The above-mentioned control message may include multiple application model data or may only include one type of application model data.

[0246] Furthermore, after reorganizing the received application model data, the first terminal device may further include: transmitting the reorganized application model data to the application model data management module; or transmitting the reorganized application model data to the corresponding functional module according to a preset rule. The preset rules and functional models can refer to the relevant content of Example 4 above and are not further described here.

[0247] Example 4 and Example 5 introduce two different methods of transmitting application model data. The embodiments of the present application can use the method introduced in Example 4 or Example 5 to transmit application model data, or can use a combination of the above two methods for transmission.

[0248] Example 6:

[0249] As shown in step 3a-1 in Figure 3, the first terminal device may further include sending a third message before sending the first message. The third message is used to request application model data registration related operations and / or to request application model data format control information.

[0250] The third message may include at least one of the following information:

[0251] Model identification information corresponding to at least one application model requested to be registered;

[0252] Requesting to update model identification information corresponding to at least one registered application model;

[0253] Model identification information corresponding to at least one application model requested to be registered;

[0254] Requests information indicating the application model data format control information.

[0255] In some implementations, the third message may include a NAS message, an AS message, or an application model operation-specific control message.

[0256] The above-mentioned AS message may be any one of the following types of messages: RRC message, MAC CE message or UCI message.

[0257] Among them, the above-mentioned application model operation-specific control message can be a message specially defined for the application model, which is used to carry control information related to executing the application model operation.

[0258] The third message is an optional message. If the third message does not exist, the first terminal device does not need to perform additional operations before sending the first message (i.e., it does not need to perform model registration operations and / or model data format control information acquisition request operations);

[0259] Defining the third message can facilitate the management of model data. Take the model data sending end as a network device and the model data receiving end as a terminal device as an example. From the perspective of the model data sending end, the transmission of model data also requires the use of network device resources. Before transmitting the model data, the third message process can be used to determine whether the terminal device is eligible to obtain these model data; the billing policy of the model data sending end is also one of the reasons for the introduction of the registration process. For example, when the network device receives the third message sent by the terminal device, it can determine whether the terminal device is eligible to download the corresponding application model data by checking the user contract information stored on the network device side. The result of the qualification review can be notified to the terminal device through the fourth message (described below); from the perspective of the model data requesting end (receiving end), the terminal device can determine whether the network device supports the download of the corresponding application model data through the third message process, because not every network device can support the download of all types of model data. For example, when the network device does not support the download of application model 1 data, even if the terminal device's own contract information allows the terminal device to download model 1 data, the network device will reject the model 1 data download registration request sent through the third message.

[0260] The above-mentioned application model data registration-related operations include at least one of application model data registration, application model data update registration, and application model data deregistration operations. If the terminal device wishes to register an application model that has not been previously registered, the third message may include model identification information corresponding to the at least one application model requested to be registered; if the terminal device wishes to change the previous application model registration result, the third message may include model identification information corresponding to the at least one application model requested to be updated; if the terminal device wishes to deregister (cancel registration) a previously registered application model, the third message may include model identification information corresponding to the at least one application model requested to be deregistered.

[0261] On the other hand, the application model data registration function corresponding to the third message not only solves the problem of whether the corresponding model data can be downloaded, but also solves the problem of the format in which the corresponding model data is downloaded. For example, the third message can also be used to request the application model data format control information. The content of the application model data format control information is described in detail later. Here we first introduce the method of obtaining the application model data format control information:

[0262] Method 1: Acquired through dedicated signaling interaction between the terminal device and the network device

[0263] In one implementation, the third message sent by the terminal device includes indication information for requesting to obtain application model data format control information. If the third message requests to register more than one application model, then these application models requested to register can share an indication information for obtaining application model data format control information, and the indication information can indicate that the terminal device requests to obtain application model data format control information corresponding to each application model requested to register. In another implementation, one or a group of application models requested to register are associated with an independent indication information for obtaining application model data format control information. This method is more flexible and can have finer granularity; because not every application model requested to register needs to obtain application model data format control information, if the terminal device has obtained this information for a certain application model on the same network device, then the terminal device can choose not to request to obtain the corresponding application model data format control information again. Regardless of the above definition of the indication information, after the network device successfully receives the registration request contained in the third message (which also includes indication information for requesting to obtain application model data format control information), it can provide the terminal device with the application model data format control information corresponding to the successfully registered application model through the fourth message.

[0264] In another implementation method, the third message sent by the terminal device does not include indication information for requesting to obtain application model data format control information. The protocol defaults that after the network device successfully receives the registration request contained in the third message, it needs to provide the terminal device with the application model data format control information corresponding to the successfully registered application model through the fourth message.

[0265] Method 2: Obtain through pre-configuration or default method

[0266] Taking the pre-configuration method as an example, for example, the first terminal device is preparing to download application model data 1 from the second terminal device. Before communicating with the second terminal device, the first terminal device has obtained the application model data format control information corresponding to the application model data 1 through the network device registration process. At this time, it can be considered that the application model data format control information corresponding to the application model data 1 is configured to the first terminal device by the network device through the pre-configuration process; for another example, the first terminal device belongs to a customized device of a certain network (such as a factory environment), then the corresponding application model data format control information can be configured to the first terminal device through the factory configuration method. This configuration method can also be considered as a type of pre-configuration method.

[0267] Taking the default method as an example, for example, the protocol directly stipulates that application model data 1 is divided into three data sub-blocks, and the sub-block identifiers are 00, 01 and 10 respectively; then, the first terminal device can obtain the corresponding application model data format control information through the default rules of the protocol.

[0268] In some embodiments, if both of the above methods are defined, it may be specified to use priority information. For example, the priority of the model data format control information obtained by the dedicated signaling interaction method (method 1) is always higher than the priority of the model data format control information obtained by method 2. In other words, when the network device or the second terminal device configures the model data format control information for the first terminal device through method 1, even if the model data format control information of the corresponding model is also obtained through method 2, the first terminal device still gives priority to the model data format control information obtained by method 1. For another example, the model data that the first terminal device is concerned about is only the model data format control information obtained through method 2 (the model data format control information of any model is not obtained through method 1 or although the model data format control information of some models is obtained by method 1, the model that the first terminal device is concerned about does not obtain the corresponding model data format control information through method 1), then according to the priority information, the first terminal device can use the model data format control information obtained through method 2.

[0269] Example 7:

[0270] In step 3a-2 of FIG. 3 , the first terminal device may further include receiving a fourth message before sending the first message. The fourth message includes at least one of the following information:

[0271] Information field 1: Model identification information corresponding to at least one successfully registered application model;

[0272] Information field 2: model data format control information corresponding to at least one successfully registered application model;

[0273] Information field 3: Operation condition control information related to at least one application model that has been successfully registered;

[0274] Information field 4: Model identification information corresponding to at least one application model that failed to register;

[0275] Information field 5: Failure reason information corresponding to at least one application model that failed to register;

[0276] Information field 6: Updates the model identification information corresponding to at least one successfully registered application model;

[0277] Information field 7: Updates the model data format control information corresponding to at least one successfully registered application model;

[0278] Information field 8: Updates the operation condition control information related to at least one application model that has been successfully registered;

[0279] Information field 9: Model identification information corresponding to at least one application model that failed to update registration;

[0280] Information field 10: update the failure reason information corresponding to at least one application model that failed to register;

[0281] Information field 11: model identification information corresponding to at least one successfully registered application model;

[0282] Information field 12: Model identification information corresponding to at least one application model that failed to be deregistered;

[0283] Information field 13: Failure reason information corresponding to at least one application model that failed to register.

[0284] In some implementations, the fourth message may include a NAS message, an AS message, or an application model operation-specific control message.

[0285] The above-mentioned AS message may be any one of the following types of messages: RRC message, MAC CE message or DCI message.

[0286] Among them, the above-mentioned application model operation-specific control message can be a message specially defined for the application model, which is used to carry control information related to executing the application model operation.

[0287] In some embodiments, the fourth message is a confirmation message of the successful receipt of the third message. That is, the fourth message may not carry any of the information in Information Fields 1 through 13, but may simply serve as a feedback message indicating the successful receipt of the third message. In this case, it is assumed that the network device or the second terminal device accepts all information in the third message sent by the first terminal device.

[0288] In some other implementations, there is no third message, but only a fourth message. In this case, the fourth message can be considered a configuration message actively triggered by the network device or the second terminal device, and the fourth message can include at least one of the information fields 1 to 13 above.

[0289] In some other implementations, the fourth message is a response message to the third message. In this case, the fourth message may include at least one of the information fields 1 to 13.

[0290] Next, the fourth message content corresponding to the second and third implementation modes described above is introduced in detail, focusing on information field 2, information field 3, information field 7 and information field 8.

[0291] Although information field 2 and information field 7 correspond to different functional parameters, they both contain model data format control information corresponding to the application model. The model data format control information includes at least one of the following information:

[0292] Subdomain information 1: model QoS requirement information corresponding to the application model;

[0293] Subdomain information 2: model data size indication information corresponding to the application model;

[0294] Subdomain information 3: model verification control information corresponding to the application model;

[0295] Subdomain information 4: model transmission security-related control information corresponding to the application model;

[0296] Subdomain information 5: model data block control information corresponding to the application model.

[0297] Among them, the QoS requirement information in subdomain information 1 can reflect the transmission requirement characteristics of the data, such as: transmission delay requirements, transmission throughput requirements, transmission bit error rate requirements, etc.; subdomain information 2 can reflect the corresponding model data size, which is convenient for operations such as model data resource management, data retransmission management, or data verification management; subdomain information 3 can be used to verify the corresponding model data, and the verification control information may include information such as the verification algorithm and the verification sequence; subdomain information 4 can be used to control the security of model data transmission, which may correspond to operations such as model data integrity protection and encryption and decryption protection; subdomain information 5 can be used to provide model data block control information. Since some model data will be divided into several parts, the model data block control information corresponding to the application model may include at least one of the following information:

[0298] The total number of model data blocks corresponding to an application model;

[0299] Identification information corresponding to each model data sub-block;

[0300] QoS requirement information corresponding to each model data sub-block;

[0301] Data size indication information corresponding to each model data sub-block;

[0302] Verification control information corresponding to each model data sub-block;

[0303] Each model data sub-block corresponds to model transmission security-related control information.

[0304] The meaning of each sub-domain in the model data block control information corresponding to the application model is similar to the meaning of the above-mentioned sub-domain information 1 to sub-domain information 4, and will not be repeated here.

[0305] Information Field 3 and Information Field 8 correspond to different functional parameters, but both contain information about application model-related operational condition control information. Even if an application model is successfully registered or successfully updated, this only indicates that the current network area supports the corresponding application model-related operations. Once the terminal device moves out of the current network area, the application model-related operations may become unavailable. With this information, whenever a terminal device is about to initiate an application model-related operation, it can compare the information provided by the current network with its stored application model-related operational condition control information. If the corresponding information meets the requirements or matches, the application model-related operation is executed; otherwise, the application model-related operation is not executed.

[0306] In some embodiments, the application model-related operation condition control information includes effective use area control information and / or effective use time control information associated with the application model-related operation.

[0307] Example 8:

[0308] In this example, capability interaction is performed between the first terminal device and the network device or the second terminal device.

[0309] For example, as shown in step 1 in FIG3 , the first terminal device also sends first capability indication information to the network device or the second terminal device, where the first capability indication information is used to indicate whether the first terminal device has the capability to support application model related operations.

[0310] For example, as shown in step 2-1 in Figure 3, the first terminal device also receives second capability indication information sent by the network device or the second terminal device, and the second capability indication information is used to inform the first terminal device whether the network device or the second terminal device has the ability to support application model related operations.

[0311] The first terminal device sending the first capability indication information and the first terminal device receiving the second capability indication information are both optional steps. Since the application model-related operations may include one or more operations, there are at least two ways to implement the first capability indication information or the second capability indication information:

[0312] Implementation 1: All application model related operations share a common capability indication information. In this implementation, these application model related operations are either supported at the same time or not supported at all.

[0313] Implementation method 2: One or a group of application model related operations corresponds to one capability indication information. In this method, some application model related operations are supported while other application model related operations are not supported.

[0314] In addition, in some embodiments, such as step 2-2 in Figure 3, if the first terminal device receives switch indication information from the network device or the second terminal device, the switch indication information is used to indicate whether the first terminal device is allowed to enable the function of performing application model related operations.

[0315] In some embodiments, the application model-related operations include at least one of the following operations:

[0316] Download or add application model data;

[0317] Application model data update or application model data modification;

[0318] Application model data upload;

[0319] Application model data deletion;

[0320] Application model data registration;

[0321] Apply model data update registration;

[0322] Apply model data to register;

[0323] Request to obtain application model data format control information.

[0324] In summary, it can be seen that the embodiments of the present application can realize the management and control of model data. Through the embodiments of the present application, on the one hand, the terminal device can realize the download, addition, update, modification, upload, deletion and other operations of one or more model data under the background of valid authorization (such as registration before use), thereby preventing illegal users from performing model data-related operations; on the other hand, the block processing of model data and the QoS demand management of data block granularity can more flexibly realize the effective transmission of model data. For example: when the terminal's own business is busy, apply to download part of the data blocks of the model data, and when the business is relatively idle, apply to download the remaining data blocks of the model data. Due to the block management of the model data, even if the time interval between the previous and subsequent downloads is very long, it will not affect the use of the model data after reorganization. Especially when the amount of model data is large, the advantages of this block download mode are more prominent, which is more flexible than downloading the model data in one go. At the same time, the QoS demand management of data block granularity can guide the data sender to appropriately select the transmission mode (for example: retransmission mode, partial retransmission mode or no retransmission mode) according to the importance of the model data sub-block, which is conducive to improving the efficiency of model data transmission.

[0325] FIG4 is a schematic flow chart of a communication method 400 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0326] S410. The second device receives a first message from the first device, where the first message is used to request at least one of the following operations:

[0327] Download or add application model data;

[0328] Application model data update or application model data modification;

[0329] Application model data upload;

[0330] Apply model data deletion.

[0331] In some embodiments, the first message includes at least one of the following:

[0332] Model identification information corresponding to at least one application model requested to be downloaded or added;

[0333] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be downloaded or added;

[0334] Model identification information corresponding to at least one application model requested to be updated or modified;

[0335] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be updated or modified;

[0336] Model identification information corresponding to at least one application model requested to be uploaded;

[0337] QoS requirement information corresponding to at least one application model requested to be uploaded;

[0338] Model data size indication information corresponding to at least one application model requested to be uploaded;

[0339] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0340] QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0341] Sub-block data size indication information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0342] Model identification information corresponding to at least one application model requested to be deleted;

[0343] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

[0344] In some implementations, the first message includes a NAS message, an AS message, or an application model operation-specific control message.

[0345] In some implementations, the method further includes: the second device sending a second message to the first device, where the second message includes at least one of the following:

[0346] Model identification information corresponding to at least one application model allowed to be downloaded or added;

[0347] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be downloaded or added;

[0348] Model identification information corresponding to at least one application model that is allowed to be updated or modified;

[0349] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be updated or modified;

[0350] Model identification information corresponding to at least one application model allowed to be uploaded;

[0351] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be uploaded;

[0352] Model identification information corresponding to at least one application model that is allowed to be deleted;

[0353] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be deleted;

[0354] Model identification information corresponding to at least one application model that is not allowed to be downloaded or added;

[0355] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added;

[0356] Model identification information corresponding to at least one application model that is not allowed to be updated or modified;

[0357] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified;

[0358] Model identification information corresponding to at least one application model that is not allowed to be uploaded;

[0359] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be uploaded;

[0360] Model identification information corresponding to at least one application model that is not allowed to be deleted;

[0361] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model that is not allowed to be deleted.

[0362] In some implementations, the second message includes a NAS message, an AS message, or an application model operation-specific control message.

[0363] In some implementations, it further includes: the second device sending an application model data transmission configuration message to the first device, where the application model data transmission configuration message is used to determine resource configuration information required to transmit the corresponding application model data.

[0364] In some implementations, the method further includes: the second device sending a control message including application model data to the first device; the control message including at least one of the following:

[0365] Apply model data;

[0366] Model identification information corresponding to the first application model to which the application model data belongs;

[0367] a serial number of the application model data in the first application model;

[0368] sub-block identification information corresponding to a first model data sub-block in a first application model to which the application model data belongs;

[0369] a serial number of the application model data in the first model data sub-block;

[0370] Control message indication information, where the control message indication information is used to indicate whether the current control message is the last segment of the control message;

[0371] The control message segment sequence number is used to indicate which segment the current control message belongs to.

[0372] In some implementations, the control message includes a NAS layer message, a radio resource control RRC message, or a control message dedicated to application model data transmission.

[0373] In some implementations, the method further includes: the second device receiving a third message from the first device, where the third message is used to request application model data registration related operations and / or to request model data format control information.

[0374] In some embodiments, the third message includes at least one of the following:

[0375] Model identification information corresponding to at least one application model requested to be registered;

[0376] Requesting to update model identification information corresponding to at least one registered application model;

[0377] Model identification information corresponding to at least one application model requested to be registered;

[0378] Instructions for requesting model data format control information.

[0379] In some implementations, the third message includes a NAS message, an AS message, or an application model operation-specific control message.

[0380] In some implementations, the method further includes: the second device sending a fourth message to the first device, where the fourth message includes at least one of the following:

[0381] Model identification information corresponding to at least one successfully registered application model;

[0382] Model data format control information corresponding to at least one successfully registered application model;

[0383] Related operation condition control information corresponding to at least one successfully registered application model;

[0384] Model identification information corresponding to at least one application model that failed to register;

[0385] Failure reason information corresponding to at least one application model that failed to register;

[0386] Update the model identification information corresponding to at least one successfully registered application model;

[0387] Update the model data format control information corresponding to at least one successfully registered application model;

[0388] Update the relevant operation condition control information corresponding to at least one successfully registered application model;

[0389] Update the model identification information corresponding to at least one application model that failed to register;

[0390] Update the failure reason information corresponding to at least one application model that failed to register;

[0391] Model identification information corresponding to at least one successfully registered application model;

[0392] Model identification information corresponding to at least one application model that failed to be registered;

[0393] Failure reason information corresponding to at least one application model that failed to register.

[0394] In some implementations, the fourth message includes a NAS message, an AS message, or an application model operation-specific control message.

[0395] In some embodiments, the model data format control information includes at least one of the following:

[0396] Model QoS requirement information corresponding to the application model;

[0397] Model data size indication information corresponding to the application model;

[0398] Model verification control information corresponding to the application model;

[0399] Model transmission security-related control information corresponding to the application model;

[0400] Model data block control information corresponding to the application model.

[0401] In some embodiments, the model data segmentation control information corresponding to the application model includes at least one of the following:

[0402] The number of model data sub-blocks corresponding to an application model;

[0403] Sub-block identification information corresponding to each model data sub-block;

[0404] QoS requirement information corresponding to each model data sub-block;

[0405] Data size indication information corresponding to each model data sub-block;

[0406] Verification control information corresponding to each model data sub-block;

[0407] Each model data sub-block corresponds to model transmission security-related control information.

[0408] In some embodiments, the further embodiment includes: the second device receiving first capability indication information from the first device, where the first capability indication information is used to indicate whether the first device has the capability to support application model related operations.

[0409] In some implementations, the further step includes: the second device sending second capability indication information to the first device, where the second capability indication information indicates whether the second device has the capability to support application model related operations.

[0410] In some embodiments, the further embodiment includes: the second device sending switch indication information to the first device, where the switch indication information is used to indicate whether the first device is allowed to enable a function of performing application model-related operations.

[0411] In some embodiments, applying the model-related operations includes at least one of the following:

[0412] Download or add application model data;

[0413] Application model data update or application model data modification;

[0414] Application model data upload;

[0415] Application model data deletion;

[0416] Application model data registration;

[0417] Apply model data update registration;

[0418] Apply model data to registration;

[0419] Request to obtain application model data format control information.

[0420] In some embodiments, the data module corresponding to the application model data includes at least one of the following:

[0421] Model input data module, model output data module, model training data module, model inference data module, model storage data module, model calculation data module, model structure data module and model coordination control data module.

[0422] In some embodiments, the application model corresponding to the application model data includes at least one of the following:

[0423] AI models, ML models, supercomputing models, neuron-like models, authentication models, encryption and decryption models, and self-optimization models.

[0424] In some embodiments, the first device includes a terminal device.

[0425] In some embodiments, the second device includes a network device or a terminal device.

[0426] In some implementations, the network device includes an access network device, a core network device, or an application model control device.

[0427] For a specific example of the second device executing the method 400 in this embodiment, reference may be made to the relevant description of the second device in the above method 200 , which will not be repeated here for the sake of brevity.

[0428] FIG5 is a schematic block diagram of a first device 500 according to an embodiment of the present application. The first device 500 may include:

[0429] The first sending module 510 is configured to send a first message, where the first message is used to request at least one of the following operations:

[0430] Download or add application model data;

[0431] Application model data update or application model data modification;

[0432] Application model data upload;

[0433] Apply model data deletion.

[0434] In some embodiments, the first message includes at least one of the following:

[0435] Model identification information corresponding to at least one application model requested to be downloaded or added;

[0436] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be downloaded or added;

[0437] Model identification information corresponding to at least one application model requested to be updated or modified;

[0438] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be updated or modified;

[0439] Model identification information corresponding to at least one application model requested to be uploaded;

[0440] Model quality of service (QoS) requirement information corresponding to at least one application model requested to be uploaded;

[0441] Model data size indication information corresponding to at least one application model requested to be uploaded;

[0442] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0443] QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0444] Sub-block data size indication information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0445] Model identification information corresponding to at least one application model requested to be deleted;

[0446] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

[0447] In some implementations, the first message includes a non-access stratum (NAS) message, an access stratum (AS) message, or an application model operation-specific control message.

[0448] FIG6 is a schematic block diagram of a first device 600 according to an embodiment of the present application. As shown in FIG6 , the first device further includes:

[0449] The second receiving module 620 is configured to receive a second message from the second device, where the second message includes at least one of the following:

[0450] Model identification information corresponding to at least one application model allowed to be downloaded or added;

[0451] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be downloaded or added;

[0452] Model identification information corresponding to at least one application model that is allowed to be updated or modified;

[0453] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be updated or modified;

[0454] Model identification information corresponding to at least one application model allowed to be uploaded;

[0455] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be uploaded;

[0456] Model identification information corresponding to at least one application model that is allowed to be deleted;

[0457] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be deleted;

[0458] Model identification information corresponding to at least one application model that is not allowed to be downloaded or added;

[0459] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added;

[0460] Model identification information corresponding to at least one application model that is not allowed to be updated or modified;

[0461] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified;

[0462] Model identification information corresponding to at least one application model that is not allowed to be uploaded;

[0463] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be uploaded;

[0464] Model identification information corresponding to at least one application model that is not allowed to be deleted;

[0465] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model that is not allowed to be deleted.

[0466] In some implementations, the second message includes a NAS message, an AS message, or an application model operation-specific control message.

[0467] As shown in FIG6 , in some embodiments, the first device further includes:

[0468] The third receiving module 630 is used to receive an application model data transmission configuration message from the second device, where the application model data transmission configuration message is used to determine resource configuration information required to transmit the corresponding application model data.

[0469] As shown in FIG6 , in some embodiments, the first device further includes:

[0470] The fourth receiving module 640 is configured to receive the application model data according to the resource configuration information included in the application model data transmission configuration message.

[0471] As shown in FIG6 , in some embodiments, the first device further includes:

[0472] The first reorganization module 650 is configured to reorganize the received application model data.

[0473] In some embodiments, the reassembly module 650 is configured to reassemble the received application model data through a NAS layer, a Packet Data Convergence Protocol (PDCP) layer, a Service Data Adaptation Protocol (SDAP) layer, or a protocol layer dedicated to application model data reassembly.

[0474] As shown in FIG6 , in some embodiments, the first device further includes:

[0475] The fifth receiving module 660 is configured to receive a control message including application model data from the second device; the control message including at least one of the following:

[0476] the application model data;

[0477] Model identification information corresponding to the first application model to which the application model data belongs;

[0478] The serial number of the application model data in the first application model;

[0479] sub-block identification information corresponding to a first model data sub-block in a first application model to which the application model data belongs;

[0480] a serial number of the application model data in the first model data sub-block;

[0481] Control message indication information, where the control message indication information is used to indicate whether the current control message is the last segment of the control message;

[0482] The control message segment sequence number is used to indicate which segment the current control message belongs to.

[0483] In some implementations, the control message includes a non-access stratum (NAS) message, a radio resource control (RRC) message, or a control message dedicated to application model data transmission.

[0484] As shown in FIG6 , in some embodiments, the first device further includes:

[0485] The first reassembly module 670 is configured to reassemble the application model data received via multiple control messages according to the control message content.

[0486] In some embodiments, the first reassembly module 670 is configured to reassemble the received application model data through a NAS layer, an RRC layer, or a protocol layer dedicated to application model data reassembly.

[0487] As shown in FIG6 , in some embodiments, the first device further includes:

[0488] The transfer module 680 is used to transfer the reorganized application model data to the application model data management module; or to transfer the reorganized application model data to the corresponding functional module according to a preset rule.

[0489] In some embodiments, the preset rule is any one of the following:

[0490] According to the model identification information corresponding to the application model data, the reorganized application model data is passed to the corresponding functional module;

[0491] According to the routing indication information contained in the application model data, the reorganized application model data is passed to the corresponding functional module;

[0492] The reorganized application model data is transferred to the corresponding functional module according to the model identification information corresponding to the application model data and the routing indication information contained in the application model data.

[0493] In some implementations, the functional module is any of the following: an application layer, a NAS layer, an RRC layer, a SDAP layer, a PDCP layer, an RLC layer, a MAC layer, a BAP layer, or a physical layer.

[0494] As shown in FIG6 , in some embodiments, the first device further includes:

[0495] The second sending module 690 is used to send a third message to the second device, where the third message is used to request application model data registration related operations and / or to request model data format control information.

[0496] In some embodiments, the third message includes at least one of the following:

[0497] Model identification information corresponding to at least one application model requested to be registered;

[0498] Requesting to update model identification information corresponding to at least one registered application model;

[0499] Model identification information corresponding to at least one application model requested to be registered;

[0500] Instructions for requesting model data format control information.

[0501] In some implementations, the third message includes a NAS message, an AS message, or an application model operation-specific control message.

[0502] As shown in FIG6 , in some embodiments, the first device further includes:

[0503] The sixth receiving module 691 is configured to receive a fourth message from the second device, where the fourth message includes at least one of the following:

[0504] Model identification information corresponding to at least one successfully registered application model;

[0505] Model data format control information corresponding to at least one successfully registered application model;

[0506] Related operation condition control information corresponding to at least one successfully registered application model;

[0507] Model identification information corresponding to at least one application model that failed to register;

[0508] Failure reason information corresponding to at least one application model that failed to register;

[0509] Update the model identification information corresponding to at least one successfully registered application model;

[0510] Update the model data format control information corresponding to at least one successfully registered application model;

[0511] Update the relevant operation condition control information corresponding to at least one successfully registered application model;

[0512] Update the model identification information corresponding to at least one application model that failed to register;

[0513] Update the failure reason information corresponding to at least one application model that failed to register;

[0514] Model identification information corresponding to at least one successfully registered application model;

[0515] Model identification information corresponding to at least one application model that failed to be registered;

[0516] Failure reason information corresponding to at least one application model that failed to register.

[0517] In some implementations, the fourth message includes a NAS message, an AS message, or an application model operation-specific control message.

[0518] As shown in FIG6 , in some embodiments, the first device further includes:

[0519] The determination module 692 is configured to determine the model data format control information corresponding to at least one application model through a preconfigured manner or a default manner.

[0520] In some embodiments, the model data format control information includes at least one of the following:

[0521] Model QoS requirement information corresponding to the application model;

[0522] Model data size indication information corresponding to the application model;

[0523] Model verification control information corresponding to the application model;

[0524] Model transmission security-related control information corresponding to the application model;

[0525] Model data block control information corresponding to the application model.

[0526] In some embodiments, the model data segmentation control information corresponding to the application model includes at least one of the following:

[0527] The number of model data sub-blocks corresponding to an application model;

[0528] Sub-block identification information corresponding to each model data sub-block;

[0529] QoS requirement information corresponding to each model data sub-block;

[0530] Data size indication information corresponding to each model data sub-block;

[0531] Verification control information corresponding to each model data sub-block;

[0532] Each model data sub-block corresponds to model transmission security-related control information.

[0533] As shown in FIG6 , in some embodiments, the first device further includes:

[0534] The third sending module 693 is used to send first capability indication information to the second device, where the first capability indication information is used to indicate whether the first device has the ability to support application model related operations.

[0535] As shown in FIG6 , in some embodiments, the first device further includes:

[0536] The seventh receiving module 694 is configured to receive second capability indication information from the second device, where the second capability indication information indicates whether the second device has the capability of supporting application model related operations.

[0537] As shown in FIG6 , in some embodiments, the first device further includes:

[0538] The eighth receiving module 695 is used to receive switch indication information from the second device, where the switch indication information is used to indicate whether the first device is allowed to enable a function of performing application model-related operations.

[0539] In some embodiments, applying the model-related operations includes at least one of the following:

[0540] Download or add application model data;

[0541] Application model data update or application model data modification;

[0542] Application model data upload;

[0543] Application model data deletion;

[0544] Application model data registration;

[0545] Apply model data update registration;

[0546] Apply model data to registration;

[0547] Request to obtain application model data format control information.

[0548] In some embodiments, the data module corresponding to the application model data includes at least one of the following:

[0549] Model input data module, model output data module, model training data module, model inference data module, model storage data module, model calculation data module, model structure data module and model coordination control data module.

[0550] In some embodiments, the application model corresponding to the application model data includes at least one of the following:

[0551] Artificial intelligence AI models, machine learning ML models, supercomputing models, neuron-like models, authentication models, encryption and decryption models, and self-optimization models.

[0552] In some embodiments, the first device includes a terminal device.

[0553] In some embodiments, the second device includes a network device or a terminal device.

[0554] In some implementations, the network device includes an access network device, a core network device, or an application model control device.

[0555] The first device 500 and the first device 600 of the embodiment of the present application can implement the corresponding functions of the terminal device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first device 500 and the first device 600 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first device 500 and the first device 600 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0556] FIG7 is a schematic block diagram of a second device 700 according to an embodiment of the present application. The second device 700 may include:

[0557] The first receiving module 710 is configured to receive a first message from a first device, where the first message is used to request at least one of the following operations:

[0558] Download or add application model data;

[0559] Application model data update or application model data modification;

[0560] Application model data upload;

[0561] Apply model data deletion.

[0562] In some embodiments, the first message includes at least one of the following:

[0563] Model identification information corresponding to at least one application model requested to be downloaded or added;

[0564] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be downloaded or added;

[0565] Model identification information corresponding to at least one application model requested to be updated or modified;

[0566] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be updated or modified;

[0567] Model identification information corresponding to at least one application model requested to be uploaded;

[0568] QoS requirement information corresponding to at least one application model requested to be uploaded;

[0569] Model data size indication information corresponding to at least one application model requested to be uploaded;

[0570] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0571] QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded;

[0572] Sub-block data size indication information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded;

[0573] Model identification information corresponding to at least one application model requested to be deleted;

[0574] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

[0575] In some implementations, the first message includes a NAS message, an AS message, or an application model operation-specific control message.

[0576] FIG8 is a schematic block diagram of a second device 800 according to an embodiment of the present application. As shown in FIG8 , the second device further includes:

[0577] The fourth sending module 820 is configured to send a second message to the first device, where the second message includes at least one of the following:

[0578] Model identification information corresponding to at least one application model allowed to be downloaded or added;

[0579] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be downloaded or added;

[0580] Model identification information corresponding to at least one application model that is allowed to be updated or modified;

[0581] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be updated or modified;

[0582] Model identification information corresponding to at least one application model allowed to be uploaded;

[0583] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be uploaded;

[0584] Model identification information corresponding to at least one application model that is allowed to be deleted;

[0585] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be deleted;

[0586] Model identification information corresponding to at least one application model that is not allowed to be downloaded or added;

[0587] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added;

[0588] Model identification information corresponding to at least one application model that is not allowed to be updated or modified;

[0589] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified;

[0590] Model identification information corresponding to at least one application model that is not allowed to be uploaded;

[0591] Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be uploaded;

[0592] Model identification information corresponding to at least one application model that is not allowed to be deleted;

[0593] The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model that is not allowed to be deleted.

[0594] In some implementations, the second message includes a NAS message, an AS message, or an application model operation-specific control message.

[0595] As shown in FIG8 , in some embodiments, the second device further includes:

[0596] The fifth sending module 830 is used to send an application model data transmission configuration message to the first device, where the application model data transmission configuration message is used to determine resource configuration information required to transmit the corresponding application model data.

[0597] As shown in FIG8 , in some embodiments, the second device further includes:

[0598] The sixth sending module 840 is configured to send a control message including application model data to the first device; the control message including at least one of the following:

[0599] Apply model data;

[0600] Model identification information corresponding to the first application model to which the application model data belongs;

[0601] a serial number of the application model data in the first application model;

[0602] sub-block identification information corresponding to a first model data sub-block in a first application model to which the application model data belongs;

[0603] a serial number of the application model data in the first model data sub-block;

[0604] Control message indication information, where the control message indication information is used to indicate whether the current control message is the last segment of the control message;

[0605] The control message segment sequence number is used to indicate which segment the current control message belongs to.

[0606] In some implementations, the control message includes a NAS layer message, a radio resource control RRC message, or a control message dedicated to application model data transmission.

[0607] As shown in FIG8 , in some embodiments, the second device further includes:

[0608] The ninth receiving module 850 is configured to receive a third message from the first device, where the third message is used to request application model data registration related operations and / or to request model data format control information.

[0609] In some embodiments, the third message includes at least one of the following:

[0610] Model identification information corresponding to at least one application model requested to be registered;

[0611] Requesting to update model identification information corresponding to at least one registered application model;

[0612] Model identification information corresponding to at least one application model requested to be registered;

[0613] Instructions for requesting model data format control information.

[0614] In some implementations, the third message includes a NAS message, an AS message, or an application model operation-specific control message.

[0615] As shown in FIG8 , in some embodiments, the second device further includes:

[0616] The seventh sending module 860 is configured to send a fourth message to the first device, where the fourth message includes at least one of the following:

[0617] Model identification information corresponding to at least one successfully registered application model;

[0618] Model data format control information corresponding to at least one successfully registered application model;

[0619] Related operation condition control information corresponding to at least one successfully registered application model;

[0620] Model identification information corresponding to at least one application model that failed to register;

[0621] Failure reason information corresponding to at least one application model that failed to register;

[0622] Update the model identification information corresponding to at least one successfully registered application model;

[0623] Update the model data format control information corresponding to at least one successfully registered application model;

[0624] Update the relevant operation condition control information corresponding to at least one successfully registered application model;

[0625] Update the model identification information corresponding to at least one application model that failed to register;

[0626] Update the failure reason information corresponding to at least one application model that failed to register;

[0627] Model identification information corresponding to at least one successfully registered application model;

[0628] Model identification information corresponding to at least one application model that failed to be registered;

[0629] Failure reason information corresponding to at least one application model that failed to register.

[0630] In some implementations, the fourth message includes a NAS message, an AS message, or an application model operation-specific control message.

[0631] In some embodiments, the model data format control information includes at least one of the following:

[0632] Model QoS requirement information corresponding to the application model;

[0633] Model data size indication information corresponding to the application model;

[0634] Model verification control information corresponding to the application model;

[0635] Model transmission security-related control information corresponding to the application model;

[0636] Model data block control information corresponding to the application model.

[0637] In some embodiments, the model data segmentation control information corresponding to the application model includes at least one of the following:

[0638] The number of model data sub-blocks corresponding to an application model;

[0639] Sub-block identification information corresponding to each model data sub-block;

[0640] QoS requirement information corresponding to each model data sub-block;

[0641] Data size indication information corresponding to each model data sub-block;

[0642] Verification control information corresponding to each model data sub-block;

[0643] Each model data sub-block corresponds to model transmission security-related control information.

[0644] As shown in FIG8 , in some embodiments, the second device further includes:

[0645] The tenth receiving module 870 is used to receive first capability indication information from the first device, where the first capability indication information is used to indicate whether the first device has the capability to support application model related operations.

[0646] As shown in FIG8 , in some embodiments, the second device further includes:

[0647] The eighth sending module 880 is used to send second capability indication information to the first device, where the second capability indication information indicates whether the second device has the ability to support application model related operations.

[0648] As shown in FIG8 , in some embodiments, the second device further includes:

[0649] The ninth sending module 890 is used to send switch indication information to the first device, where the switch indication information is used to indicate whether the first device is allowed to enable the function of performing application model related operations.

[0650] In some embodiments, applying the model-related operations includes at least one of the following:

[0651] Download or add application model data;

[0652] Application model data update or application model data modification;

[0653] Application model data upload;

[0654] Application model data deletion;

[0655] Application model data registration;

[0656] Apply model data update registration;

[0657] Apply model data to register;

[0658] Request to obtain application model data format control information.

[0659] In some embodiments, the data module corresponding to the application model data includes at least one of the following:

[0660] Model input data module, model output data module, model training data module, model inference data module, model storage data module, model calculation data module, model structure data module and model coordination control data module.

[0661] In some embodiments, the application model corresponding to the application model data includes at least one of the following:

[0662] AI models, ML models, supercomputing models, neuron-like models, authentication models, encryption and decryption models, and self-optimization models.

[0663] In some embodiments, the first device includes a terminal device.

[0664] In some embodiments, the second device includes a network device or a terminal device.

[0665] In some implementations, the network device includes an access network device, a core network device, or an application model control device.

[0666] The second device 700 and the second device 800 of the embodiment of the present application can implement the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second device 700 and the second device 800 can be found in the corresponding descriptions in the above-mentioned method embodiments, and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the second device 700 and the second device 800 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0667] Figure 9 is a schematic structural diagram of a communication device 900 according to an embodiment of the present application. The communication device 900 includes a processor 910, which can call and run a computer program from a memory to enable the communication device 900 to implement the method in the embodiment of the present application.

[0668] In one embodiment, the communication device 900 may further include a memory 920. The processor 910 may call and execute a computer program from the memory 920 to enable the communication device 900 to implement the method in the embodiment of the present application.

[0669] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0670] In one embodiment, the communication device 900 may further include a transceiver 930 , and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0671] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.

[0672] In one embodiment, the communication device 900 may be a network device of an embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0673] In one embodiment, the communication device 900 may be a terminal device of an embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the second device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0674] 10 is a schematic structural diagram of a chip 1000 according to an embodiment of the present application. The chip 1000 includes a processor 1010, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0675] In one embodiment, the chip 1000 may further include a memory 1020. The processor 1010 may call and execute a computer program from the memory 1020 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

[0676] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0677] In one embodiment, the chip 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0678] In one embodiment, the chip 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0679] In one embodiment, the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0680] In one embodiment, the chip can be applied to the second device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0681] The chips used in the first device and the second device may be the same chip or different chips.

[0682] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0683] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0684] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. 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).

[0685] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0686] FIG11 is a schematic block diagram of a communication system 1100 according to an embodiment of the present application. The communication system 1100 includes a first device 1110 and a second device 1120 .

[0687] The first device 1110 can be used to implement the corresponding functions implemented by the first device in the above method, and the second device 1220 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, they are not described here in detail.

[0688] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0689] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0690] 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.

[0691] 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 modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, comprising: A first device sends a first message to a second device, where the first message is used to request at least one of the following operations: Download or add application model data; Application model data update or application model data modification; Application model data upload; Apply model data deletion.

2. The method according to claim 1, wherein the first message comprises at least one of the following: Model identification information corresponding to at least one application model requested to be downloaded or added; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be downloaded or added; Model identification information corresponding to at least one application model requested to be updated or modified; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be updated or modified; Model identification information corresponding to at least one application model requested to be uploaded; Model quality of service (QoS) requirement information corresponding to at least one application model requested to be uploaded; Model data size indication information corresponding to at least one application model requested to be uploaded; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded; QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded; Sub-block data size indication information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded; Model identification information corresponding to at least one application model requested to be deleted; The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

3. The method according to claim 1 or 2, wherein: The first message includes a non-access stratum NAS message, an access stratum AS message, or an application model operation-specific control message.

4. The method according to any one of claims 1 to 3, further comprising: The first device receives a second message from the second device, where the second message includes at least one of the following: Model identification information corresponding to at least one application model allowed to be downloaded or added; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be downloaded or added; Model identification information corresponding to at least one application model that is allowed to be updated or modified; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be updated or modified; Model identification information corresponding to at least one application model allowed to be uploaded; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be uploaded; Model identification information corresponding to at least one application model that is allowed to be deleted; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be deleted; Model identification information corresponding to at least one application model that is not allowed to be downloaded or added; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added; Model identification information corresponding to at least one application model that is not allowed to be updated or modified; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified; Model identification information corresponding to at least one application model that is not allowed to be uploaded; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be uploaded; Model identification information corresponding to at least one application model that is not allowed to be deleted; The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model that is not allowed to be deleted.

5. The method according to any one of claims 1 to 4, wherein: The second message includes a NAS message, an AS message, or an application model operation-specific control message.

6. The method according to any one of claims 1 to 5, further comprising: The first device receives an application model data transmission configuration message from the second device, where the application model data transmission configuration message is used to determine resource configuration information required to transmit the corresponding application model data.

7. The method according to claim 6, further comprising: The first device receives the application model data according to the resource configuration information included in the application model data transmission configuration message.

8. The method according to claim 7, further comprising: The first device reorganizes the received application model data.

9. The method according to claim 8, wherein The first device reorganizes the received application model data, including: The first device reorganizes the received application model data through the NAS layer, the Packet Data Convergence Protocol PDCP layer, the Service Data Adaptation Protocol SDAP layer or a protocol layer dedicated to the reorganization of application model data.

10. The method according to any one of claims 1 to 9, further comprising: The first device receives a control message including application model data from the second device; the control message includes at least one of the following: Apply model data; Model identification information corresponding to the first application model to which the application model data belongs; a serial number of the application model data in the first application model; sub-block identification information corresponding to a first model data sub-block in a first application model to which the application model data belongs; a serial number of the application model data in the first model data sub-block; Control message indication information, where the control message indication information is used to indicate whether the current control message is the last segment of the control message; The control message segment sequence number is used to indicate which segment the current control message belongs to.

11. The method according to claim 10, wherein: The control message includes a non-access NAS layer message, a radio resource control RRC message or a control message dedicated to application model data transmission.

12. The method according to claim 10 or 11, further comprising: The first device reorganizes the application model data received through multiple control messages according to the control message content.

13. The method according to claim 12, wherein: The first device reorganizes the application model data received through multiple control messages according to the control message content, including: The first device reorganizes the received application model data through the NAS layer, the RRC layer or a protocol layer dedicated to the reorganization of application model data.

14. The method according to claim 9 or 13, after reorganizing the received application model data, further comprising: Passing the reorganized application model data to the application model data management module; or, The reorganized application model data is passed to the corresponding functional module according to the preset rules.

15. The method according to claim 14, wherein the preset rule is any one of the following: According to the model identification information corresponding to the application model data, the reorganized application model data is passed to the corresponding functional module; According to the routing indication information contained in the application model data, the reorganized application model data is passed to the corresponding functional module; The reorganized application model data is transferred to the corresponding functional module according to the model identification information corresponding to the application model data and the routing indication information contained in the application model data.

16. The method according to claim 14 or 15, wherein the functional module is any one of the following: application layer, NAS layer, RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, BAP layer or physical layer.

17. The method according to any one of claims 1 to 16, further comprising: The first device sends a third message to the second device, where the third message is used to request application model data registration related operations and / or to request model data format control information.

18. The method according to claim 17, wherein The third message includes at least one of the following: Model identification information corresponding to at least one application model requested to be registered; Requesting to update model identification information corresponding to at least one registered application model; Model identification information corresponding to at least one application model requested to be registered; Instructions for requesting model data format control information.

19. The method according to claim 17 or 18, wherein The third message includes a NAS message, an AS message, or an application model operation-specific control message.

20. The method according to any one of claims 1 to 19, further comprising: The first device receives a fourth message from the second device, where the fourth message includes at least one of the following: Model identification information corresponding to at least one successfully registered application model; Model data format control information corresponding to at least one successfully registered application model; Related operation condition control information corresponding to at least one successfully registered application model; Model identification information corresponding to at least one application model that failed to register; Failure reason information corresponding to at least one application model that failed to register; Update the model identification information corresponding to at least one successfully registered application model; Update the model data format control information corresponding to at least one successfully registered application model; Update the relevant operation condition control information corresponding to at least one successfully registered application model; Update the model identification information corresponding to at least one application model that failed to register; Update the failure reason information corresponding to at least one application model that failed to register; Model identification information corresponding to at least one successfully registered application model; Model identification information corresponding to at least one application model that failed to be registered; Failure reason information corresponding to at least one application model that failed to register.

21. The method according to claim 20, wherein The fourth message includes a NAS message, an AS message, or an application model operation-specific control message.

22. The method according to any one of claims 1 to 16, further comprising: The first device determines model data format control information corresponding to at least one application model through a preconfiguration method or a default method.

23. The method according to any one of claims 17 to 22, wherein: The model data format control information includes at least one of the following: Model QoS requirement information corresponding to the application model; Model data size indication information corresponding to the application model; Model verification control information corresponding to the application model; Model transmission security-related control information corresponding to the application model; Model data block control information corresponding to the application model.

24. The method according to claim 23, wherein The model data block control information corresponding to the application model includes at least one of the following: The number of model data sub-blocks corresponding to an application model; Sub-block identification 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; Verification control information corresponding to each model data sub-block; Each model data sub-block corresponds to model transmission security-related control information.

25. The method according to any one of claims 1 to 24, further comprising: The first device sends first capability indication information to the second device, where the first capability indication information is used to indicate whether the first device has the capability of supporting application model related operations.

26. The method according to any one of claims 1 to 25, further comprising: The first device receives second capability indication information from the second device, where the second capability indication information indicates whether the second device has the capability of supporting application model related operations.

27. The method according to any one of claims 1 to 26, further comprising: The first device receives switch indication information from the second device, where the switch indication information is used to indicate whether the first device is allowed to enable a function of performing application model-related operations.

28. The method according to any one of claims 25 to 27, wherein the application model-related operation comprises at least one of the following: Download or add application model data; Application model data update or application model data modification; Application model data upload; Application model data deletion; Application model data registration; Apply model data update registration; Apply model data to registration; Request to obtain application model data format control information.

29. The method according to any one of claims 1 to 28, wherein the data module corresponding to the application model data comprises at least one of the following: Model input data module, model output data module, model training data module, model inference data module, model storage data module, model calculation data module, model structure data module and model coordination control data module.

30. According to the method of any one of claims 1 to 29, the application model corresponding to the application model data comprises at least one of the following: Artificial intelligence AI models, machine learning ML models, supercomputing models, neuron-like models, authentication models, encryption and decryption models, and self-optimization models.

31. The method according to any one of claims 1-30, wherein the first device comprises a terminal device.

32. The method according to any one of claims 1-31, wherein the second device comprises a network device or a terminal device.

33. The method according to claim 32, wherein the network device comprises an access network device, a core network device or an application model control device.

34. A communication method comprising: The second device receives a first message from the first device, where the first message is used to request at least one of the following operations: Download or add application model data; Application model data update or application model data modification; Application model data upload; Apply model data deletion.

35. The method according to claim 34, wherein the first message comprises at least one of the following: Model identification information corresponding to at least one application model requested to be downloaded or added; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be downloaded or added; Model identification information corresponding to at least one application model requested to be updated or modified; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be updated or modified; Model identification information corresponding to at least one application model requested to be uploaded; QoS requirement information corresponding to at least one application model requested to be uploaded; Model data size indication information corresponding to at least one application model requested to be uploaded; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded; QoS requirement information corresponding to the model data sub-block corresponding to at least one application model requested to be uploaded; Sub-block data size indication information corresponding to a model data sub-block corresponding to at least one application model requested to be uploaded; Model identification information corresponding to at least one application model requested to be deleted; The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model requested to be deleted.

36. The method according to claim 34 or 35, wherein The first message includes a NAS message, an AS message, or an application model operation-specific control message.

37. The method according to any one of claims 34 to 36, further comprising: The second device sends a second message to the first device, where the second message includes at least one of the following: Model identification information corresponding to at least one application model allowed to be downloaded or added; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be downloaded or added; Model identification information corresponding to at least one application model that is allowed to be updated or modified; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be updated or modified; Model identification information corresponding to at least one application model allowed to be uploaded; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model allowed to be uploaded; Model identification information corresponding to at least one application model that is allowed to be deleted; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is allowed to be deleted; Model identification information corresponding to at least one application model that is not allowed to be downloaded or added; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be downloaded or added; Model identification information corresponding to at least one application model that is not allowed to be updated or modified; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be updated or modified; Model identification information corresponding to at least one application model that is not allowed to be uploaded; Sub-block identification information corresponding to a model data sub-block corresponding to at least one application model that is not allowed to be uploaded; Model identification information corresponding to at least one application model that is not allowed to be deleted; The sub-block identification information corresponding to the model data sub-block corresponding to at least one application model that is not allowed to be deleted.

38. The method according to any one of claims 34 to 37, wherein: The second message includes a NAS message, an AS message, or an application model operation-specific control message.

39. The method according to any one of claims 34 to 38, further comprising: The second device sends an application model data transmission configuration message to the first device, where the application model data transmission configuration message is used to determine resource configuration information required to transmit the corresponding application model data.

40. The method according to any one of claims 34 to 39, further comprising: The second device sends a control message including application model data to the first device; the control message includes at least one of the following: Apply model data; Model identification information corresponding to the first application model to which the application model data belongs; a serial number of the application model data in the first application model; sub-block identification information corresponding to a first model data sub-block in a first application model to which the application model data belongs; a serial number of the application model data in the first model data sub-block; Control message indication information, where the control message indication information is used to indicate whether the current control message is the last segment of the control message; The control message segment sequence number is used to indicate which segment the current control message belongs to.

41. The method according to claim 40, wherein The control message includes a NAS layer message, a radio resource control RRC message or a control message dedicated to application model data transmission.

42. The method according to any one of claims 34 to 41, further comprising: The second device receives a third message from the first device, where the third message is used to request an operation related to registration of application model data and / or to request acquisition of model data format control information.

43. The method according to claim 42, wherein The third message includes at least one of the following: Model identification information corresponding to at least one application model requested to be registered; Requesting to update model identification information corresponding to at least one registered application model; Model identification information corresponding to at least one application model requested to be registered; Instructions for requesting model data format control information.

44. The method according to claim 42 or 43, wherein The third message includes a NAS message, an AS message, or an application model operation-specific control message.

45. The method according to any one of claims 34 to 44, further comprising: The second device sends a fourth message to the first device, where the fourth message includes at least one of the following: Model identification information corresponding to at least one successfully registered application model; Model data format control information corresponding to at least one successfully registered application model; Related operation condition control information corresponding to at least one successfully registered application model; Model identification information corresponding to at least one application model that failed to register; Failure reason information corresponding to at least one application model that failed to register; Update the model identification information corresponding to at least one successfully registered application model; Update the model data format control information corresponding to at least one successfully registered application model; Update the relevant operation condition control information corresponding to at least one successfully registered application model; Update the model identification information corresponding to at least one application model that failed to register; Update the failure reason information corresponding to at least one application model that failed to register; Model identification information corresponding to at least one successfully registered application model; Model identification information corresponding to at least one application model that failed to be registered; Failure reason information corresponding to at least one application model that failed to register.

46. ​​The method of claim 45, wherein The fourth message includes a NAS message, an AS message, or an application model operation-specific control message.

47. The method according to any one of claims 42 to 46, wherein: The model data format control information includes at least one of the following: Model QoS requirement information corresponding to the application model; Model data size indication information corresponding to the application model; Model verification control information corresponding to the application model; Model transmission security-related control information corresponding to the application model; Model data block control information corresponding to the application model.

48. The method of claim 47, wherein The model data block control information corresponding to the application model includes at least one of the following: The number of model data sub-blocks corresponding to an application model; Sub-block identification 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; Verification control information corresponding to each model data sub-block; Each model data sub-block corresponds to model transmission security-related control information.

49. The method according to any one of claims 34 to 48, further comprising: The second device receives first capability indication information from the first device, where the first capability indication information is used to indicate whether the first device has the capability of supporting application model related operations.

50. The method according to any one of claims 34 to 49, further comprising: The second device sends second capability indication information to the first device, where the second capability indication information indicates whether the second device has the capability of supporting application model related operations.

51. The method according to any one of claims 34 to 50, further comprising: The second device sends switch indication information to the first device, where the switch indication information is used to indicate whether the first device is allowed to enable a function of performing application model-related operations.

52. The method according to any one of claims 49 to 51, wherein the application model-related operation comprises at least one of the following: Download or add application model data; Application model data update or application model data modification; Application model data upload; Application model data deletion; Application model data registration; Apply model data update registration; Apply model data to register; Request to obtain application model data format control information.

53. The method according to any one of claims 34 to 52, wherein the data module corresponding to the application model data comprises at least one of the following: Model input data module, model output data module, model training data module, model inference data module, model storage data module, model calculation data module, model structure data module and model coordination control data module.

54. The method according to any one of claims 34 to 53, wherein the application model corresponding to the application model data comprises at least one of the following: AI models, ML models, supercomputing models, neuron-like models, authentication models, encryption and decryption models, and self-optimization models.

55. The method according to any one of claims 34 to 54, wherein the first device comprises a terminal device.

56. The method according to any one of claims 34-55, wherein the second device comprises a network device or a terminal device.

57. The method according to claim 56, wherein the network device comprises an access network device, a core network device or an application model control device.

58. A first device comprising: The first sending module is configured to send a first message to the second device, where the first message is used to request at least one of the following operations: Download or add application model data; Application model data update or application model data modification; Application model data upload; Apply model data deletion.

59. A second device comprising: The first receiving module is configured to receive a first message from a first device, where the first message is used to request at least one of the following operations: Download or add application model data; Application model data update or application model data modification; Application model data upload; Apply model data deletion.

60. An apparatus comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so as to enable the device to perform the method according to any one of claims 1 to 33 or 34 to 57.

61. A chip comprising: A processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 33 or 34 to 57.

62. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 33 or 34 to 57.

63. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 33 or 34 to 57.

64. A computer program causing a computer to perform the method of any one of claims 1 to 33 or 34 to 57.

65. A communication system comprising: A first device, configured to perform the method according to any one of claims 1 to 33; A second device is configured to perform the method according to any one of claims 34 to 57.

Images