Model registration method and device and storage medium

Abstract

The invention provides a model registration method and device and a storage medium, and relates to the technical field of communication. The method comprises: a first entity sends a first message to a second entity, the first message being used for requesting registration of a first model, the first message comprising an identifier of the first entity, a first model identifier and model information of the first model, the first model identifier being an identifier of the first model in the first entity; a second message sent by the second entity in response to the first message is received, the second message comprises a first model identifier, a second model identifier and indication information, the second model identifier is a network identifier allocated by the second entity for the first model, and the indication information indicates a registration decision or registration decision related information; and sending a third message to the second entity based on the registration decision related information, the third message including the second model identification and the registration decision. Therefore, the network can provide services such as personalized model registration for the user, the network or the third party as required, and a basis is provided for intelligent endogenesis.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method, apparatus, and storage medium for model registration. Background Art

[0002] The intelligent endogeny of the 6th Generation Mobile Networks (6G) can refer to that the 6G network natively supports Artificial Intelligence (AI), takes the AI capability as the basic service of the network, realizes AI as a Service (AIaaS), enables the network to self-learn and self-evolve, and then can provide AI training services, AI inference services, AI deployment and open services, etc. for users, the network, or third parties.

[0003] However, the network architecture and network processes of existing mobile communication systems can only provide connection and data transmission services for users, and cannot provide intelligent endogeny services such as AI model registration and storage. Summary of the Invention

[0004] This application provides a method, apparatus, and storage medium for model registration, which solves the technical problem that the communication system cannot provide intelligent endogeny services such as AI model registration and storage.

[0005] In a first aspect, an embodiment of this application provides a method for model registration, which is applied to a first entity. The method includes:

[0006] Sending a first message to a second entity, where the first message is used to request the registration of a first model, and the first message includes the identifier of the first entity, the first model identifier, and the model information of the first model, and the first model identifier is the identifier of the first model in the first entity;

[0007] Receiving a second message sent by the second entity in response to the first message, where the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is the network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0008] Based on the registration decision-related information, sending a third message to the second entity, where the third message includes the second model identifier and the registration decision.

[0009] In one implementation, the first model is a personalized model.

[0010] In one implementation, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0011] In one embodiment, the model information further includes a third model identifier and / or a model application scenario;

[0012] Wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

[0013] In one embodiment, the method further includes:

[0014] Sending a fourth message to the second entity, the fourth message being used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0015] Receiving a fifth message sent by the second entity in response to the fourth message, the fifth message being used to indicate a model storage result.

[0016] In one embodiment, the method further includes:

[0017] Sending a fourth message to a third entity, the fourth message being used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0018] Receiving a fifth message sent by the third entity in response to the fourth message, the fifth message being used to indicate a model storage result.

[0019] In one embodiment, the method further includes:

[0020] Sending the first model.

[0021] In one embodiment, the method further includes:

[0022] Sending a sixth message to the second entity, the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0023] Receiving a seventh message sent by the second entity in response to the sixth message, the seventh message being used to indicate a model update result.

[0024] In one embodiment, the first entity is a first terminal, a first access network device, or a first core network device;

[0025] The second entity is a Unified Data Management (UDM), a Unified Data Repository (UDR), or a first functional entity, and the first functional entity is deployed on a second terminal, a second access network device, or a second core network device;

[0026] The third entity is deployed in a third terminal, a third access network device, or a third core network device;

[0027] The first terminal, the second terminal, and the third terminal are the same or different from each other, the first access network device, the second access network device, and the third access network device are the same or different from each other, and the first core network device, the second core network device, and the third core network device are the same or different from each other.

[0028] In a second aspect, an embodiment of the present application provides a model registration method, which is applied to a second entity. The method includes:

[0029] Receiving a first message sent by a first entity, the first message is used to request to register a first model. The first message includes the identifier of the first entity, a first model identifier, and model information of the first model. The first model identifier is the identifier of the first model in the first entity;

[0030] Responding to the first message by sending a second message to the first entity. The second message includes the first model identifier, a second model identifier, and indication information. The second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0031] Receiving a third message sent by the first entity. The third message is a message determined based on the registration decision-related information. The third message includes the second model identifier and a registration decision.

[0032] In an implementation manner, the first model is a personalized model.

[0033] In an implementation manner, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0034] In an implementation manner, the model information further includes a third model identifier and / or a model application scenario;

[0035] Wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

[0036] In an implementation manner, the method further includes:

[0037] Receiving a fourth message sent by the first entity. The fourth message is used to request to store the first model. The fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0038] Send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate the model storage result.

[0039] In one embodiment, the method further includes:

[0040] Receive the first model.

[0041] In one embodiment, after receiving the first model, the method further includes:

[0042] Verify the first model to obtain a verification result;

[0043] Update the model information according to the verification result.

[0044] In one embodiment, the method further includes:

[0045] Receive a sixth message sent by the first entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0046] Send a seventh message to the first entity in response to the sixth message, where the seventh message is used to indicate the model update result.

[0047] In a third aspect, an embodiment of the present application provides a model registration method, which is applied to a third entity, and the method includes:

[0048] Receive a fourth message sent by the first entity, where the fourth message is used to request to store a first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model;

[0049] Send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate the model storage result.

[0050] In one embodiment, the method further includes:

[0051] Receive the first model.

[0052] In one embodiment, after receiving the first model, the method further includes:

[0053] Verify the first model to obtain a verification result;

[0054] Update the model information according to the verification result.

[0055] In a fourth aspect, an embodiment of the present application provides a model registration device, which is applied to a first entity, and the device includes:

[0056] A first sending unit, configured to send a first message to a second entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is an identifier of the first model in the first entity;

[0057] A first receiving unit, configured to receive a second message sent by the second entity in response to the first message, where the second message includes the first model identifier, a second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0058] A second sending unit, configured to send a third message to the second entity based on the registration decision-related information, where the third message includes the second model identifier and a registration decision.

[0059] In one implementation, the first model is a personalized model.

[0060] In one implementation, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0061] In one implementation, the model information further includes a third model identifier and / or a model application scenario;

[0062] where the third model identifier is an identifier of a second model, and the first model is trained based on the second model.

[0063] In one implementation, the apparatus further includes:

[0064] A third sending unit, configured to send a fourth message to the second entity, where the fourth message is used to request storage of the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0065] A second receiving unit, configured to receive a fifth message sent by the second entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0066] In one implementation, the apparatus further includes:

[0067] A fourth sending unit, configured to send a fourth message to a third entity, where the fourth message is used to request storage of the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0068] A third receiving unit, configured to receive a fifth message sent by the third entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0069] In an implementation, the apparatus further includes:

[0070] A fifth sending unit, configured to send the first model.

[0071] In an implementation, the apparatus further includes:

[0072] A sixth sending unit, configured to send a sixth message to the second entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0073] A fourth receiving unit, configured to receive a seventh message sent by the second entity in response to the sixth message, where the seventh message is used to indicate a model update result.

[0074] In an implementation, the first entity is a first terminal, a first access network device, or a first core network device;

[0075] The second entity is a unified data management UDM, a unified data repository function UDR, or a first functional entity, and the first functional entity is deployed in a second terminal, a second access network device, or a second core network device;

[0076] The third entity is deployed in a third terminal, a third access network device, or a third core network device;

[0077] The first terminal, the second terminal, and the third terminal are the same or different from each other, the first access network device, the second access network device, and the third access network device are the same or different from each other, and the first core network device, the second core network device, and the third core network device are the same or different from each other.

[0078] In a fifth aspect, an embodiment of the present application provides a model registration apparatus, which is applied to a second entity, and the apparatus includes:

[0079] A first receiving unit, configured to receive a first message sent by a first entity, where the first message is used to request registration of a first model, the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is an identifier of the first model in the first entity;

[0080] A first sending unit, configured to send a second message to the first entity in response to the first message, where the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0081] A second receiving unit, configured to receive a third message sent by the first entity, where the third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and the registration decision.

[0082] In one implementation, the first model is a personalized model.

[0083] In one implementation, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0084] In one implementation, the model information further includes a third model identifier and / or a model application scenario;

[0085] Wherein, the third model identifier is an identifier of the second model, and the first model is trained based on the second model.

[0086] In one implementation, the apparatus further includes:

[0087] A third receiving unit, configured to receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0088] A second sending unit, configured to send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0089] In one implementation, the apparatus further includes:

[0090] A fourth receiving unit, configured to receive the first model.

[0091] In one implementation, after receiving the first model, the apparatus further includes:

[0092] A verification unit, configured to verify the first model to obtain a verification result;

[0093] An update unit, configured to update the model information according to the verification result.

[0094] In one implementation, the apparatus further includes:

[0095] A fifth receiving unit, configured to receive a sixth message sent by the first entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0096] A third sending unit, configured to send a seventh message to the first entity in response to the sixth message, where the seventh message is used to indicate a model update result.

[0097] In a sixth aspect, an embodiment of the present application provides a model registration device, which is applied to a third entity. The device includes:

[0098] A receiving unit, configured to receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model;

[0099] A sending unit, configured to send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0100] In an implementation manner, the receiving unit is further configured to:

[0101] Receive the first model.

[0102] In an implementation manner, after receiving the first model, the device further includes:

[0103] A verification unit, configured to verify the first model to obtain a verification result;

[0104] An update unit, configured to update the model information according to the verification result.

[0105] In a seventh aspect, an embodiment of the present application provides a model registration device, which is applied to a first entity. The device includes a memory, a transceiver, and a processor:

[0106] The memory is configured to store a computer program; the transceiver is configured to send and receive data under the control of the processor; the processor is configured to read the computer program in the memory and perform the following operations:

[0107] Send a first message to a second entity, where the first message is used to request registering a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is an identifier of the first model in the first entity;

[0108] Receive a second message sent by the second entity in response to the first message, where the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is the network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0109] Based on the registration decision-related information, send a third message to the second entity, where the third message includes the second model identifier and the registration decision.

[0110] In one implementation, the first model is a personalized model.

[0111] In one implementation, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0112] In one implementation, the model information further includes a third model identifier and / or a model application scenario;

[0113] Wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

[0114] In one implementation, the processor is further configured to perform the following operations:

[0115] Send a fourth message to the second entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model;

[0116] Receive a fifth message sent by the second entity in response to the fourth message, where the fifth message is used to indicate the model storage result.

[0117] In one implementation, the processor is further configured to perform the following operations:

[0118] Send a fourth message to a third entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model;

[0119] Receive a fifth message sent by the third entity in response to the fourth message, where the fifth message is used to indicate the model storage result.

[0120] In one implementation, the processor is further configured to perform the following operations:

[0121] Send the first model.

[0122] In one implementation, the processor is further configured to perform the following operations:

[0123] Send a sixth message to the second entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0124] Receive a seventh message sent by the second entity in response to the sixth message, where the seventh message is used to indicate the model update result.

[0125] In one implementation, the first entity is a first terminal, a first access network device, or a first core network device;

[0126] The second entity is a Unified Data Management (UDM), a Unified Data Repository (UDR), or a first functional entity, and the first functional entity is deployed in a second terminal, a second access network device, or a second core network device;

[0127] The third entity is deployed in a third terminal, a third access network device, or a third core network device;

[0128] The first terminal, the second terminal, and the third terminal are the same or different from each other, the first access network device, the second access network device, and the third access network device are the same or different from each other, and the first core network device, the second core network device, and the third core network device are the same or different from each other.

[0129] In an eighth aspect, an embodiment of the present application provides a model registration device, which is applied to a second entity. The device includes a memory, a transceiver, and a processor:

[0130] The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0131] Receive a first message sent by a first entity, where the first message is used to request registration of a first model, and the first message includes the identifier of the first entity, the first model identifier, and the model information of the first model. The first model identifier is the identifier of the first model in the first entity;

[0132] In response to the first message, send a second message to the first entity, where the second message includes the first model identifier, a second model identifier, and indication information. The second model identifier is the network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0133] Receive a third message sent by the first entity, where the third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and a registration decision.

[0134] In one embodiment, the first model is a personalized model.

[0135] In one embodiment, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0136] In one embodiment, the model information further includes a third model identifier and / or a model application scenario;

[0137] Wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

[0138] In one embodiment, the processor is further configured to perform the following operations:

[0139] Receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, model transmission method, model address, or the first model;

[0140] In response to the fourth message, send a fifth message to the first entity, where the fifth message is used to indicate the model storage result.

[0141] In one embodiment, the processor is further configured to perform the following operations:

[0142] Receive the first model.

[0143] In one embodiment, after receiving the first model, the processor is further configured to perform the following operations:

[0144] Verify the first model to obtain a verification result;

[0145] Update the model information according to the verification result.

[0146] In one embodiment, the processor is further configured to perform the following operations:

[0147] Receive a sixth message sent by the first entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0148] In response to the sixth message, send a seventh message to the first entity, where the seventh message is used to indicate the model update result.

[0149] In a ninth aspect, an embodiment of the present application provides a model registration device, which is applied to a third entity. The device includes a memory, a transceiver, and a processor:

[0150] The memory is used to store computer programs; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0151] Receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model;

[0152] In response to the fourth message, send a fifth message to the first entity, where the fifth message is used to indicate the model storage result.

[0153] In one implementation, the processor is further used to perform the following operations:

[0154] Receive the first model.

[0155] In one implementation, after receiving the first model, the processor is further used to perform the following operations:

[0156] Verify the first model to obtain a verification result;

[0157] Update the model information according to the verification result.

[0158] In a tenth aspect, an embodiment of the present application provides a non-transitory readable storage medium, where the non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method according to any item in the first aspect.

[0159] In an eleventh aspect, an embodiment of the present application provides a non-transitory readable storage medium, where the non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method according to any item in the second aspect.

[0160] In a twelfth aspect, an embodiment of the present application provides a non-transitory readable storage medium, where the non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute the method according to any item in the third aspect.

[0161] An embodiment of the present application provides a model registration method, apparatus, and storage medium. The method includes: a first entity sending a first message to a second entity, the first message being used to request the registration of a first model, the first message including the identifier of the first entity, the first model identifier, and the model information of the first model, and the first model identifier being the identifier of the first model in the first entity; receiving a second message sent by the second entity in response to the first message, the second message including the first model identifier, the second model identifier, and indication information, the second model identifier being the network identifier assigned by the second entity to the first model, and the indication information indicating a registration decision or registration decision-related information; and based on the registration decision-related information, sending a third message to the second entity, the third message including the second model identifier and the registration decision. By adding a model registration function and a corresponding registration process in the network, the network can provide services such as personalized model registration for users, the network, or third parties as needed, providing a basis for intelligent in-situ

[0162] It should be understood that the content described in the above-mentioned summary of the invention does not aim to limit the key or important features of the embodiments of the present invention, nor is it used to limit the scope of the present invention. Other features of the present invention will become easily understandable through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0163] In order to more clearly illustrate the technical solutions in the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0164] Figure 1 It is a schematic diagram of an architecture of a communication system in the related art;

[0165] Figure 2 It is a schematic diagram of an architecture of a communication system provided by an embodiment of the present application;

[0166] Figure 3 It is another schematic diagram of an architecture of a communication system provided by an embodiment of the present application;

[0167] Figure 4 It is the flow of the model registration method provided by an embodiment of the present application Figure 1 ;

[0168] Figure 5 It is a flowchart of a model storage method provided by an embodiment of the present application;

[0169] Figure 6 It is a flowchart of a model update method provided by an embodiment of the present application;

[0170] Figure 7The flowchart of the model registration method provided by the embodiments of this application Figure 2 ;

[0171] Figure 8 The flowchart of the model registration method provided by the embodiments of this application Figure 3 ;

[0172] Figure 9 The flowchart of the model registration method provided by the embodiments of this application Figure 4 ;

[0173] Figure 10 The schematic structural diagram of the model registration device 1000 provided by the embodiments of this application;

[0174] Figure 11 The schematic structural diagram of the model registration device 1100 provided by the embodiments of this application;

[0175] Figure 12 The schematic structural diagram of the model registration device 1200 provided by the embodiments of this application;

[0176] Figure 13 The schematic structural diagram of the model registration device 1300 provided by the embodiments of this application;

[0177] Figure 14 The schematic structural diagram of the model registration device 1400 provided by the embodiments of this application;

[0178] Figure 15 The schematic structural diagram of the model registration device 1500 provided by the embodiments of this application. Detailed implementation manners

[0179] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0180] In the embodiments of this application, the term "a plurality of" refers to two or more, and other quantifiers are similar.

[0181] In the embodiments of this application, descriptions such as "first", "second", and "third" are only used for illustration and to distinguish description objects, without an order, and do not represent a special limitation on the number of objects in the embodiments of this application, and cannot constitute any limitation to the embodiments of this application. For example, the first model identifier is the identifier of the first model in the first entity, and the third model identifier is the identifier of the second model. Using descriptions such as "first" and "third" is only to distinguish different model identifiers, rather than indicating differences in the size, priority, or importance of these two model identifiers.

[0182] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0183] The embodiments of the present application provide a model registration method and apparatus for providing services such as personalized model registration for users, networks, or third parties as needed.

[0184] Among them, the method and the apparatus are based on the same inventive concept. Since the principles of solving problems by the method and the apparatus are similar, the implementation of the apparatus and the method can be referred to each other, and the repeated parts will not be described again.

[0185] The terminal involved in the embodiments of the present application can be a device that provides voice and / or data connectivity to users, such as a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal may also be different. For example, in a 5G system, the terminal can be called a User Equipment (UE). The wireless terminal can be a USB storage device, other personal computer memory devices, and dongles. It can also communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). The wireless terminal can be a mobile terminal, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal. For example, it can be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges voice and / or data with the wireless access network. For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, Machine-type Communication (MTC) terminals, etc. The wireless terminal can also be called a system, subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, and wireless access routers and routers / modems that meet the limitations of this definition, which are not limited in the embodiments of the present application.

[0186] The access network device involved in the embodiments of the present application may be a base station, which may include multiple cells that provide services to terminals. Depending on the specific application scenarios, the base station may also be referred to as an access point, or may be a device in the access network that communicates with wireless terminals through one or more sectors over the air interface, or other names. The network device can be used to mutually replace the received air frames and Internet Protocol (IP) packets, and act as a router between the wireless terminal and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the management of the attributes of the air interface. For example, the network device involved in the embodiments of the present application may be an evolved network device (eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), etc., or may also be a Home evolved Node B (HeNB), a relay node, a femto, a pico, a network test device, etc., which are not limited in the embodiments of the present application. In some network architectures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0187] Figure 1 It is a schematic diagram of an architecture of a communication system in the related art. As Figure 1 shown, the architecture includes a terminal, an access network device, a core network device, and a Data Network (DN) part.

[0188] Among them, the core network device can also be referred to as a core network element or a core network functional entity. As an example, the core network functional entity can include any one of the following: Policy Control Function (PCF) entity, Network Slice Selection Function (NSSF) entity, Unified Data Management (UDM) entity, Network Repository Function (NRF) entity, Session Management Function (SMF) entity, Access and Mobility Management Function (AMF) entity, and User Plane Function (UPF) entity. As an example, the functions of the above functional entities are as follows:

[0189] The PCF entity is mainly used for the unified policy framework that guides network behavior and provides policy rule information for control plane entities (such as AMF, SMF, etc.).

[0190] The AMF entity is mainly used for functions such as access control, mobility management, registration, and deregistration.

[0191] The SMF entity is mainly used for user plane network element selection, user plane network element redirection, IP address allocation for the terminal, as well as the establishment, modification, and release of sessions and Quality of Service (QoS) control.

[0192] The UPF entity is mainly used for receiving and forwarding user plane data. For example, the UPF entity can receive user plane data from the service server and send the user plane data to the terminal through the access network device. The UPF entity can also receive user plane data from the terminal through the access network device and forward it to the service server.

[0193] The NSSF entity is mainly used for network slice selection.

[0194] The UDM entity is mainly used for the subscription data management of the terminal, including the storage and management of the terminal identifier, access authorization of the terminal, etc.

[0195] The data network part can be a data network that provides business services for users. Generally, the client is located at the terminal and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators.

[0196] The network architecture of the current 5G mobile communication system can be as Figure 1 shown. Similar to previous generations of mobile communication systems, it is designed with connection and data transmission as the center and can only provide users with connection and data transmission services, but cannot provide intelligent endogenous services such as model registration services and model storage services.

[0197] Based on the technical problems in the existing technology, the embodiments of the present application provide a model registration method, which can construct a personalized model registration process through the interaction between multiple entities in the communication system, enabling the communication system to provide personalized model registration, storage and other services for users, networks or third parties as needed.

[0198] In the embodiments of the present application, providing a personalized model registration service through the communication system may refer to completing the personalized model registration process through the interaction between multiple entities in the communication system; the personalized model registration service may refer to the entire personalized model registration process.

[0199] The architecture of the communication system provided by the embodiments of the present application can be as Figure 2 or Figure 3 shown. Among them, Figure 2 the architecture shown is the architecture after the RAN is service-oriented, Figure 3 and the architecture shown is the architecture where the RAN is not service-oriented. As Figure 2 or Figure 3 shown, this architecture includes a Require Analysing Function (RAF) entity, a Network Adaptability Function (NAF) entity, a Network Collaboration Function (NCF) entity, at least one Network Execution Function (NEF) entity, a third entity, a fourth entity and a fifth entity.

[0200] The RAF entity is mainly used to determine service requirements.

[0201] Exemplarily, the RAF entity can determine service requirements by receiving a user's request; the RAF entity can also sense changes in scenario requirements and determine service requirements by analyzing the sensed data; the RAF entity can also analyze current data / third-party data and historical data through AI algorithms to determine service requirements.

[0202] The NAF entity can be used to determine a list of execution operations for the target service according to the service requirements. The execution operation list is a series of execution operations, and the execution operations include connection establishment and guarantee, task calculation, data processing, AI training / inference, etc.

[0203] The NCF entity can be used to coordinate the execution progress, functions, and / or resources of at least one NEF entity; it can also be used to determine the list of execution operations for the target service.

[0204] Each NEF entity can be used to implement a type of function, such as a control plane network function, a user plane network function, a data plane network function, a computing network function, etc. That is, the NEF entity can execute a single network service operation, such as connection establishment, data calculation, etc.; it can also execute collaborative operations to complete the provision of complex services, such as subnet establishment, AI joint training, etc. In other words, the execution operations of a service can be executed by a single NEF entity or by multiple NEF entities in collaboration.

[0205] The third entity is mainly used to store the AI model, and the AI model stored in the third entity is the AI model that has been registered in the second entity.

[0206] The third entity can also be called the AI Model Storage Function (AIMSF) entity.

[0207] The fourth entity is mainly used for the registration of various AI models.

[0208] The fourth entity can also be called the AI Model Registration Function (AIMRF) entity.

[0209] The fifth entity is mainly used to verify the security, privacy protection, and performance of the AI model.

[0210] The fifth entity can also be called the AI Model Authentication Function (AIMAF) entity.

[0211] The third entity can be deployed on the third terminal, the third access network device, or the third core network device; the fourth entity can be deployed on the fourth terminal, the fourth access network device, or the fourth core network device; the fifth entity can be deployed on the fifth access network device or the fifth core network device; the third terminal and the fourth terminal can be the same or different from each other, the third access network device, the fourth access network device, and the fifth access network device can be the same or different from each other, and the third core network device, the fourth core network device, and the fifth core network device can be the same or different from each other.

[0212] When the third entity is deployed on the third terminal, it can be deployed on the third terminal through software, through hardware, or through a combination of software and hardware.

[0213] When the fourth entity is deployed on the fourth terminal, it can be deployed on the fourth terminal through software, or through hardware, or through a combination of software and hardware.

[0214] When the above-mentioned entity is deployed on an access network device, it may mean that the above-mentioned entity is deployed on existing functional entities such as a Network Function (NF) entity or an Operation Administration and Maintenance (OAM) entity, or the above-mentioned entity can be deployed as a separate device in the access network.

[0215] When the above-mentioned entity is deployed on a core network device, it may mean that the above-mentioned entity is deployed on existing functional entities such as an NF entity or an OAM entity, or the above-mentioned entity can be deployed as a separate device in the core network.

[0216] The architecture of the communication system according to the embodiments of the present application not only includes the above-mentioned entities, but may also include other functional entities, such as a Network-resource Registration and CollectionFunction (NRCF) entity (which can be used to register network resources and receive updates on the status of network function resources), a Network Service Policy Function (NSPF) entity (which can be used to generate QoS metric parameters and save QoS metric parameters generated by other network elements), a User AI Model RegistrationManagement Function (UMRMF) entity (which can be used to register and save UE personalized models), a Network AI Model Registration Function (NAMRF) entity (which can be used to register network personalized models), a UDM entity, a Unified Data Repository (UDR) entity, a PCF entity, an AMF entity, an SMF entity, and a UPF entity. The embodiments of the present application do not limit this.

[0217] It should be noted that the names of the above entities are only examples, and the embodiments of the present application do not limit the specific names of each entity. As long as the functions implemented are the same or similar, they can be considered the same entity.

[0218] Based on the above communication system architecture, how multiple entities in the architecture interact to achieve the on-demand supply of services such as model registration will be described in detail below.

[0219] Figure 4 Flow of the model registration method provided by the embodiment of this application Figure 1 As shown in Figure 4 the figure, the method includes:

[0220] S401. The first entity sends a first message to the second entity. The first message is used to request the registration of the first model. The first message includes the identifier of the first entity, the first model identifier, and the first model information.

[0221] In other words, the second entity receives the first message sent by the first entity.

[0222] The first entity may be the first terminal, the first access network device, or the first core network device.

[0223] The second entity may be the UDM or the UDR or the first functional entity. The first functional entity may be deployed in the second terminal, the second access network device, or the second core network device.

[0224] Exemplarily, the first functional entity may be the AIMRF entity, the UMRMF entity, or the NAMRF entity.

[0225] The first terminal, the second terminal, and the third terminal may be the same or different from each other. The first access network device, the second access network device, and the third access network device may be the same or different from each other. The first core network device, the second core network device, the second core network device, and the third core network device may be the same or different from each other.

[0226] When the first entity is the first access network device, it may be the OAM deployed in the access network or the NF deployed in the access network.

[0227] When the first entity is the first core network device, it may be the OAM deployed in the core network or the NF deployed in the core network.

[0228] The first message may also be referred to as the model registration request message.

[0229] The first model may be obtained by the first entity from other network elements. For example, the other network elements may be the network elements for training and optimizing the model.

[0230] The first model may also be the model optimized by the first entity.

[0231] Exemplarily, the first entity may first obtain the second model and the model optimization data, and perform optimization training on the second model based on the model optimization data to obtain the first model. That is, the first model is obtained by training based on the second model.

[0232] That is to say, the second model may also be referred to as the base model.

[0233] In a possible implementation, the first model in the embodiments of the present application may be a personalized model.

[0234] Exemplarily, the first model may be a personalized AI model.

[0235] The first model identifier may be the identifier of the first model in the first entity, and may also be referred to as the local model identifier.

[0236] In a possible implementation, the model information may include: model type, model modality, model algorithm, and model accuracy.

[0237] The model type may indicate that the first model is a basic algorithm model or an industry-specific model, etc.

[0238] The model modality may include voice, text, image, multi-modal, etc.

[0239] The model algorithm may indicate the algorithm type of the first model. The algorithm type may include supervised learning, deep learning, reinforcement learning, etc.; the model algorithm may also be used to indicate a specific model algorithm. The specific model algorithm may include algorithms such as Deep Q-Leaning Network (DQN) algorithm and Support Vector Machine (SVM) algorithm.

[0240] When the model algorithm type is reinforcement learning, the specific model algorithm may be the DQN algorithm; when the model algorithm type is supervised learning, the specific model algorithm may be the SVM algorithm.

[0241] The model accuracy may indicate the average accuracy rate of the first model's inference.

[0242] In a possible implementation, the model information may further include a third model identifier and / or a model application scenario.

[0243] The third model identifier may be the identifier of the second model.

[0244] Exemplarily, the third model identifier may be the unique identifier of the second model in the network.

[0245] The model application scenario may indicate the scenario where the first model is applied, including wireless communication, medical, education, transportation, etc.

[0246] The model application scenario may also indicate the model application field. The model application field may indicate the field of the first model in the corresponding scenario. For example, in the wireless communication scenario, the model application field may include resource scheduling, mobility management, etc. In the transportation scenario, the model application field may include image recognition, route navigation, etc.

[0247] Exemplarily, the information carried in the first message can be collectively referred to as model registration information. Exemplarily, the model registration information can be as shown in Table 1:

[0248] Table 1 Model Registration Information

[0249] Parameter Name Parameter Meaning Identifier of the First Entity First Model Identifier Identifier of the First Model in the First Entity Third Model Identifier [Optional] Unique Identifier of the Second Model in the Network Model Type Indicates that the first model is a basic algorithm model, an industry-specific model, etc. Model Application Scenario [Optional] Indicates the scenario to which the first model applies - Model Application Field Indicates the field of the first model in the corresponding scenario Model Modality Voice, text, image, multi-modal, etc. Model Algorithm Indicates the algorithm type and specific model algorithm of the first model [Optional] Model Accuracy Indicates the average accuracy rate of the first model's inference

[0250] S402. In response to the first message, the second entity sends a second message to the first entity.

[0251] In other words, the first entity receives the second message sent by the second entity in response to the first message.

[0252] The second entity can determine whether the first entity can register according to the UE subscription information and / or the registration policy, and then send a second message to the first entity.

[0253] Multiple registration policies can be stored in the second entity, and each registration policy is applicable to a type of first entity.

[0254] Exemplarily, the second entity can determine the target registration policy from multiple registration policies according to the type of the first entity, and then determine whether the first entity can register based on the target registration policy.

[0255] The second message can also be referred to as a model registration response message.

[0256] The second message can include a first model identifier, a second model identifier, and indication information.

[0257] The second model identifier is the network identifier assigned by the second entity to the first model, that is, the second model identifier is the unique identifier of the first model in the network.

[0258] The indication information can indicate a registration decision or information related to the registration decision.

[0259] The registration decision can be registration, non-registration, or deregistration.

[0260] The information related to the registration decision can include a model query result, and the model query result can include an existing similar model or no similar model.

[0261] If it is the second entity that decides whether to register, the indication information indicates the registration decision.

[0262] If it is the first entity that decides whether to register, the indication information indicates the information related to the registration decision. After receiving the indication information, the first entity can execute S403.

[0263] S403. Based on the information related to the registration decision, the first entity sends a third message to the second entity.

[0264] In other words, the second entity receives the third message sent by the first entity.

[0265] The third message may include a second model identifier and a registration decision.

[0266] When the registration decision-related information includes a model query result, if the model query result is that there is no similar model, the registration decision in the third message may be registration; if the model query result is that there is an existing similar model, the registration decision in the third message may be deregistration.

[0267] In Figure 4 In the illustrated embodiment, the communication system constructs a personalized model registration process through the interaction between entities, enabling the communication system to provide personalized model registration services for users, networks, or third parties intelligently based on personalized model registration requirements during communication.

[0268] Figure 4 The illustrated embodiment illustrates the personalized model registration process. Next, the model storage process will be described in detail in conjunction with Figure 5 The model storage process will be described in detail.

[0269] Figure 5 FIG. is a flowchart of a model storage method provided by an embodiment of the present application. As Figure 5 shown, the method includes:

[0270] S501. The first entity sends a fourth message to the second entity, and the fourth message is used to request to store the first model.

[0271] In other words, the second entity receives the fourth message sent by the first entity.

[0272] The fourth message may be referred to as a model storage request message.

[0273] The fourth message may include at least one of the following: a second model identifier, a model transmission method, a model address, or the first model.

[0274] The model transmission method may be determined based on the size of the first model.

[0275] The model address may be the storage address of the first model.

[0276] If the first model is carried in the fourth message, the second entity can directly execute S502; if the first model is not carried in the fourth message and the first model is stored locally, the first entity can send the first model to the second entity, and the second entity executes S502 after receiving the first model; if the first model is not carried in the fourth message and the first model is not stored locally, the model address can be carried in the fourth message, and the second entity can interact with the network element storing the model based on the model address to obtain the first model, and the second entity executes S502 after receiving the first model.

[0277] After receiving the first model, the second entity stores the first model.

[0278] In a possible implementation, after receiving the first model, the second entity can also verify the first model to obtain a verification result, and update the model information according to the verification result.

[0279] Verification may mean first verifying the privacy and security of the first model. If the verification passes, the reported model information is verified based on the received first model. If the reported model information is inconsistent with the information of the received first model, the inconsistent model information is updated based on the information of the received first model.

[0280] Among them, the privacy and security verification can be performed by the fifth entity. That is, the second entity can send the received first model to the fifth entity; the fifth entity verifies the privacy and security of the first model to obtain a first verification result, and the first verification result can be verification passed or verification failed; the fifth entity sends the first verification result to the second entity; after receiving the first verification result, if the first verification result is verification passed, the second entity verifies the reported model information based on the received first model to obtain a second verification result, and the second verification result can be that the reported model information is consistent or inconsistent with the information of the received first model; when the second verification result is that the reported model information is inconsistent with the information of the received first model, the inconsistent model information is updated based on the information of the received first model; when the reported model information is consistent with the information of the received first model, there is no need to update the model information.

[0281] The privacy and security verification can also be performed by the second entity or the third entity. The verification process is as described above and will not be elaborated here.

[0282] The updated model information can be as shown in Table 2:

[0283] Table 2 Updated Model Information

[0284] Parameter Name Parameter Meaning Identifier of the First Entity Model Application Scenario [Optional] Indicates the scenario to which the first model applies - Model Application Field Indicates the field of the first model in the corresponding scenario Model Parameter List - First Model Identifier Identifier of the First Model in the First Entity - Third Model Identifier [Optional] Unique Identifier of the Second Model in the Network - Model Algorithm Indicates the algorithm type and specific model algorithm of the first model [Optional] - Model Accuracy Indicates the average accuracy rate of the first model's inference

[0285] In the embodiment of the present application, the second entity has a model registration function and a model storage function.

[0286] S502: The second entity sends a fifth message to the first entity in response to the fourth message.

[0287] In other words, the first entity receives the fifth message sent by the second entity in response to the fourth message.

[0288] The fifth message may be referred to as a model storage response message.

[0289] The fifth message may be used to instruct the model to store the result.

[0290] The model storage result may be model storage completion.

[0291] The fifth message may include the second model identifier and the model storage result.

[0292] exist Figure 5 In the embodiment shown, the first entity stores the first model in the second entity. In this case, the second entity has both the model registration function and the model storage function. If the second entity only has the model registration function, the first entity needs to store the first model in the third entity. The storage process can be found in Figure 5 The illustrated embodiment will not be described in detail here, wherein the third entity has a model storage function.

[0293] The communication system builds a personalized model storage process through the interaction between various entities, so that the communication system can intelligently provide personalized model storage services for users, networks or third parties based on personalized model storage needs during the communication process.

[0294] Based on any of the above embodiments, Figure 6 Describe the model update process in detail.

[0295] Figure 6 A flow chart of a model updating method provided in an embodiment of the present application. Figure 6 As shown, the method includes:

[0296] S601. The first entity sends a sixth message to the second entity.

[0297] In other words, the second entity receives the sixth message sent by the first entity.

[0298] The sixth message may be used to request updating and supplementing model information.

[0299] The sixth message may include the second model identifier, model update information and / or model supplement information. The model update information may refer to information after the first model is optimized.

[0300] Model supplementary information is information that needs to be supplemented based on the model information.

[0301] The combination of model supplementary information and model information is model detailed information.

[0302] The second entity can save model detailed information, which is shown in Table 3:

[0303] Table 3 Model details

[0304]

[0305]

[0306] S602: The second entity sends a seventh message to the first entity in response to the sixth message.

[0307] In other words, the first entity receives the seventh message sent by the second entity in response to the sixth message. The seventh message can be used to indicate the model update result.

[0308] The model update result may include model update completion.

[0309] The seventh message may include the second model identifier and the model update result.

[0310] exist Figure 6 In the illustrated embodiment, the communication system constructs a personalized model update process through the interaction between various entities, so that the communication system can intelligently provide personalized model update services to users, networks or third parties based on personalized model update requirements during the communication process.

[0311] Above Figure 4 The embodiment shown, Figure 5 The embodiment shown, the embodiment in which the first model is stored by a third entity, and Figure 6 The shown embodiments can be combined arbitrarily.

[0312] Based on the above-mentioned multiple embodiments, several combined embodiments obtained by combining the above-mentioned multiple embodiments are shown below.

[0313] Embodiment 1, as Figure 7 As shown, taking the first entity as a terminal and the second entity as a UDM as an example, the method includes:

[0314] S701. The terminal sends a first message to the UDM. The first message is used to request registration of a first model. The first message includes a terminal identifier, a second model identifier, a third model identifier, a model type, a model application scenario [optional], a model modality, a model algorithm, and a model accuracy.

[0315] S702: The UDM sends a second message to the terminal in response to the first message, where the second message includes the first model identifier, the second model identifier, and a registration decision.

[0316] It should be noted that the execution process from S701 to S702 can refer to the execution process from S401 to S402, which will not be repeated here.

[0317] S703. The terminal sends a fourth message to the UDM. The fourth message is used to request to store the first model. The fourth message includes the second model identifier, the model transmission mode, the model address [optional] and the first model [optional].

[0318] If the fourth message does not carry the first model, execute S704; if the fourth message carries the first model, execute S705.

[0319] S704: Model transmission.

[0320] S705: Model verification.

[0321] S706. The UDM sends a fifth message to the terminal in response to the fourth message, where the fifth message includes the second model identifier and the model storage result.

[0322] It should be noted that the execution process of S703 to S706 can refer to the execution process of S501 to S502, and will not be repeated here.

[0323] S707: The terminal sends a sixth message to the UDM, where the sixth message includes the second model identifier, model update information and / or model supplement information.

[0324] S708. The UDM sends a seventh message to the terminal in response to the sixth message, where the seventh message includes a second model identifier and a model update result.

[0325] In the first embodiment, the UDM has a model registration function, a model storage function, and a model update function.

[0326] Embodiment 2, as Figure 8 As shown, taking the first entity as a terminal and the second entity as a first functional entity as an example, the method includes:

[0327] S801. The terminal sends a first message to the first functional entity. The first message is used to request registration of a first model. The first message includes a terminal identifier, a second model identifier, a third model identifier, a model type, a model application scenario [optional], a model modality, a model algorithm, and a model accuracy.

[0328] S802: The first functional entity sends a second message to the terminal in response to the first message, where the second message includes the first model identifier, the second model identifier, and a registration decision.

[0329] It should be noted that the execution process from S801 to S802 can refer to the execution process from S401 to S402, and will not be repeated here.

[0330] S803. The terminal sends a fourth message to the first functional entity. The fourth message is used to request to store the first model. The fourth message includes a second model identifier, a model transmission mode, a model address [optional] and a first model [optional].

[0331] If the fourth message does not carry the first model, execute S804; if the fourth message carries the first model, execute S805.

[0332] S804: Model transmission.

[0333] S805: Model verification.

[0334] S806. The first functional entity sends a fifth message to the terminal in response to the fourth message, where the fifth message includes the second model identifier and the model storage result.

[0335] It should be noted that the execution process of S803 to S806 can refer to the execution process of S501 to S502, and will not be repeated here.

[0336] S807. The terminal sends a sixth message to the first functional entity, where the sixth message includes the second model identifier, model update information and / or model supplementary information.

[0337] S808. The first functional entity sends a seventh message to the terminal in response to the sixth message, where the seventh message includes a second model identifier and a model update result.

[0338] In embodiment 2, the first functional entity has a model registration function, a model storage function and a model update function. In embodiment 2, the first functional entity may be an AIMRF entity or a UMRMF entity.

[0339] Embodiment 3, as Figure 9 As shown, taking the first entity as a terminal and the second entity as a first functional entity as an example, the method includes:

[0340] S901. The terminal sends a first message to the first functional entity. The first message is used to request registration of a first model. The first message includes a terminal identifier, a second model identifier, a third model identifier, a model type, a model application scenario [optional], a model modality, a model algorithm, and a model accuracy.

[0341] S902: The first functional entity sends a second message to the terminal in response to the first message, where the second message includes the first model identifier, the second model identifier, and a registration decision.

[0342] It should be noted that the execution process from S901 to S902 can refer to the execution process from S401 to S402, which will not be repeated here.

[0343] S903. The terminal sends a fourth message to the third entity. The fourth message is used to request to store the first model. The fourth message includes the second model identifier, the model transmission mode, the model address [optional] and the first model [optional].

[0344] If the fourth message does not carry the first model, execute S904; if the fourth message carries the first model, execute S905.

[0345] S904: Model transmission.

[0346] S905: Model verification.

[0347] S906: The third entity sends a fifth message to the terminal in response to the fourth message, where the fifth message includes the second model identifier and the model storage result.

[0348] It should be noted that the execution process of S903 to S906 can refer to the execution process of S501 to S502, and will not be repeated here.

[0349] S907. The terminal sends a sixth message to the first functional entity, where the sixth message includes the second model identifier, model update information and / or model supplementary information.

[0350] S908. The first functional entity sends a seventh message to the terminal in response to the sixth message, where the seventh message includes a second model identifier and a model update result.

[0351] In embodiment 3, the first functional entity has a model registration function and a model update function. In embodiment 3, the first functional entity may be an AIMRF entity or a NAMRF entity.

[0352] On the basis of Embodiment 2 and Embodiment 3, the first entity may be replaced by NF / OAM to execute the above process, and it is only necessary to change the terminal identifier to the NF identifier.

[0353] Figure 10 Schematic diagram of the structure of the model registration device 1000 provided in the embodiment of the present application. Figure 10 As shown, the device 1000 includes: a memory 1010 , a transceiver 1020 , and a processor 1030 .

[0354] The memory 1010 is used to store computer programs; the transceiver 1020 is used to send and receive data under the control of the processor 1030; the processor 1030 is used to read the computer program stored in the memory 1010 and perform the following operations:

[0355] Sending a first message to the second entity, where the first message is used to request registration of the first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, where the first model identifier is an identifier of the first model in the first entity;

[0356] receiving a second message sent by the second entity in response to the first message, the second message including the first model identifier, the second model identifier and indication information, the second model identifier being a network identifier allocated by the second entity to the first model, and the indication information indicating a registration decision or registration decision related information;

[0357] Based on the registration decision related information, a third message is sent to the second entity, where the third message includes the second model identifier and the registration decision.

[0358] In one embodiment, the first model is a personalized model.

[0359] In one implementation, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0360] In one embodiment, the model information further includes a third model identifier and / or a model application scenario;

[0361] The third model identifier is the identifier of the second model, and the first model is obtained by training based on the second model.

[0362] In one implementation, the processor 1030 is further configured to perform the following operations:

[0363] Sending a fourth message to the second entity, where the fourth message is used to request to store the first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission mode, a model address, or the first model;

[0364] A fifth message sent by the second entity in response to the fourth message is received, where the fifth message is used to indicate a model storage result.

[0365] In one implementation, the processor 1030 is further configured to perform the following operations:

[0366] Sending a fourth message to the third entity, where the fourth message is used to request to store the first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission mode, a model address, or the first model;

[0367] A fifth message sent by the third entity in response to the fourth message is received, where the fifth message is used to indicate a model storage result.

[0368] In one implementation, the processor 1030 is further configured to perform the following operations:

[0369] Send the first model.

[0370] In one implementation, the processor 1030 is further configured to perform the following operations:

[0371] Send a sixth message to a second entity, where the sixth message includes a second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0372] Receive a seventh message sent by the second entity in response to the sixth message, where the seventh message is used to indicate the model update result.

[0373] In one implementation, the first entity is a first terminal, a first access network device, or a first core network device;

[0374] The second entity is a Unified Data Management (UDM), a Unified Data Repository (UDR), or a first functional entity, and the first functional entity is deployed on a second terminal, a second access network device, or a second core network device;

[0375] The third entity is deployed on a third terminal, a third access network device, or a third core network device;

[0376] The first terminal, the second terminal, and the third terminal may be the same or different from each other, the first access network device, the second access network device, and the third access network device may be the same or different from each other, and the first core network device, the second core network device, and the third core network device may be the same or different from each other.

[0377] It should be noted here that the above-mentioned model registration device 1000 provided in this application can implement all the method steps implemented by the first entity in the above method embodiments, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0378] Figure 11 This is a schematic structural diagram of a model registration device 1100 provided in an embodiment of this application. As Figure 11 shown, the device 1100 includes: a memory 1110, a transceiver 1120, and a processor 1130.

[0379] The memory 1110 is used to store computer programs; the transceiver 1120 is used to transmit and receive data under the control of the processor 1130; the processor 1130 is used to read the computer programs stored in the memory 1110 and perform the following operations:

[0380] Receive a first message sent by a first entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is the identifier of the first model in the first entity;

[0381] Send a second message to the first entity in response to the first message. The second message includes a first model identifier, a second model identifier, and indication information. The second model identifier is the network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information.

[0382] Receive a third message sent by the first entity. The third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and the registration decision.

[0383] In one implementation, the first model is a personalized model.

[0384] In one implementation, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0385] In one implementation, the model information further includes a third model identifier and / or a model application scenario;

[0386] Wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

[0387] In one implementation, the processor 1130 is further configured to perform the following operations:

[0388] Receive a fourth message sent by the first entity. The fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model;

[0389] Send a fifth message to the first entity in response to the fourth message. The fifth message is used to indicate the model storage result.

[0390] In one implementation, the processor 1130 is further configured to perform the following operations:

[0391] Receive the first model.

[0392] In one implementation, after receiving the first model, the processor 1130 is further configured to perform the following operations:

[0393] Verify the first model to obtain a verification result;

[0394] Update the model information according to the verification result.

[0395] In one implementation, the processor 1130 is further configured to perform the following operations:

[0396] Receive a sixth message sent by the first entity. The sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplementary information;

[0397] Send a seventh message to the first entity in response to the sixth message, where the seventh message is used to indicate the model update result.

[0398] It should be noted here that the above-mentioned model registration device 1100 provided in this application can implement all the method steps implemented by the second entity in the above method embodiment, and can achieve the same technical effect. Therefore, the same parts and beneficial effects as those in the method embodiment will not be specifically described herein.

[0399] Figure 12 This is a schematic structural diagram of the model registration device 1200 provided in an embodiment of this application. As Figure 12 shown, the device 1200 includes: a memory 1210, a transceiver 1220, and a processor 1230.

[0400] The memory 1210 is used to store computer programs; the transceiver 1220 is used to transmit and receive data under the control of the processor 1230; the processor 1230 is used to read the computer programs stored in the memory 1210 and perform the following operations:

[0401] Receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission method, a model address, or the first model;

[0402] Send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate the model storage result.

[0403] In one implementation, the processor 1230 is further used to perform the following operations:

[0404] Receive the first model.

[0405] In one implementation, after receiving the first model, the processor 1230 is further used to perform the following operations:

[0406] Verify the first model to obtain a verification result;

[0407] Update the model information according to the verification result.

[0408] It should be noted here that the above-mentioned model registration device 1200 provided in this application can implement all the method steps implemented by the third entity in the above method embodiment, and can achieve the same technical effect. Therefore, the same parts and beneficial effects as those in the method embodiment will not be specifically described herein.

[0409] Among them, in Figures 10 to 12In the case where the model registration device is a terminal, the device may further include a user interface. For different terminals, the user interface may also be an interface capable of externally or internally connecting to required devices. The connected devices include, but are not limited to, a keypad, a display, a speaker, a microphone, a joystick, etc.

[0410] The bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1030 or processor 1130 or processor 1230 and memories represented by memory 1010 or memory 11110 or memory 1210. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and thus will not be further described herein. The bus interface provides an interface. The transceiver may be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which includes transmission media such as wireless channels, wired channels, optical cables, etc. The processor is responsible for managing the bus architecture and general processing, and the memory may store data used by the processor when performing operations.

[0411] Optionally, the processor may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD). The processor may also adopt a multi-core architecture.

[0412] Figure 13 It is a schematic structural diagram of the model registration device 1300 provided by an embodiment of the present application. As Figure 13 shown, the device 1300 includes:

[0413] A first sending unit 1310, configured to send a first message to a second entity, where the first message is used to request registration of a first model, and the first message includes an identifier of a first entity, a first model identifier, and model information of the first model, and the first model identifier is the identifier of the first model in the first entity;

[0414] A first receiving unit 1320, configured to receive a second message sent by the second entity in response to the first message, where the second message includes a first model identifier, a second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0415] A second sending unit 1330, configured to send a third message to a second entity based on registration decision related information, where the third message includes a second model identifier and a registration decision.

[0416] In one embodiment, the first model is a personalized model.

[0417] In one embodiment, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0418] In one embodiment, the model information further includes a third model identifier and / or a model application scenario;

[0419] Wherein, the third model identifier is an identifier of the second model, and the first model is trained based on the second model.

[0420] In one embodiment, the apparatus 1300 further includes:

[0421] A third sending unit, configured to send a fourth message to a second entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission method, a model address, or the first model;

[0422] A second receiving unit, configured to receive a fifth message sent by the second entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0423] In one embodiment, the apparatus 1300 further includes:

[0424] A fourth sending unit, configured to send a fourth message to a third entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission method, a model address, or the first model;

[0425] A third receiving unit, configured to receive a fifth message sent by the third entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0426] In one embodiment, the apparatus 1300 further includes:

[0427] A fifth sending unit, configured to send the first model.

[0428] In one embodiment, the apparatus 1300 further includes:

[0429] A sixth sending unit, configured to send a sixth message to a second entity, where the sixth message includes a second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0430] A fourth receiving unit, configured to receive a seventh message sent by the second entity in response to the sixth message, where the seventh message is used to indicate a model update result.

[0431] In one embodiment, the first entity is a first terminal, a first access network device, or a first core network device;

[0432] The second entity is a Unified Data Management (UDM), a Unified Data Repository Function (UDR), or a first functional entity, and the first functional entity is deployed in a second terminal, a second access network device, or a second core network device;

[0433] The third entity is deployed in a third terminal, a third access network device, or a third core network device;

[0434] The first terminal, the second terminal, and the third terminal are the same or different from each other, the first access network device, the second access network device, and the third access network device are the same or different from each other, and the first core network device, the second core network device, and the third core network device are the same or different from each other.

[0435] It should be noted here that the above-mentioned model registration device 1300 provided in this application can implement all the method steps implemented by the first entity in the above method embodiments, and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0436] Figure 14 FIG. is a schematic structural diagram of a model registration device 1400 provided in an embodiment of this application. As Figure 14 shown, the device 1400 includes:

[0437] A first receiving unit 1410, configured to receive a first message sent by the first entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is the identifier of the first model in the first entity;

[0438] A first sending unit 1420, configured to send a second message to the first entity in response to the first message, where the second message includes the first model identifier, a second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information;

[0439] A second receiving unit 1430, configured to receive a third message sent by the first entity, where the third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and the registration decision.

[0440] In one embodiment, the first model is a personalized model.

[0441] In one embodiment, the model information includes: model type, model modality, model algorithm, and model accuracy.

[0442] In one embodiment, the model information further includes a third model identifier and / or a model application scenario;

[0443] Wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

[0444] In one embodiment, the apparatus 1400 further includes:

[0445] A third receiving unit, configured to receive a fourth message sent by a first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission method, a model address, or the first model;

[0446] A second sending unit, configured to send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0447] In one embodiment, the apparatus 1400 further includes:

[0448] A fourth receiving unit, configured to receive the first model.

[0449] In one embodiment, after receiving the first model, the apparatus 1400 further includes:

[0450] A verification unit, configured to verify the first model to obtain a verification result;

[0451] An update unit, configured to update the model information according to the verification result.

[0452] In one embodiment, the apparatus 1400 further includes:

[0453] A fifth receiving unit, configured to receive a sixth message sent by the first entity, where the sixth message includes a second model identifier, and the sixth message further includes model update information and / or model supplement information;

[0454] A third sending unit, configured to send a seventh message to the first entity in response to the sixth message, where the seventh message is used to indicate a model update result.

[0455] It should be noted here that the above-mentioned model registration apparatus 1400 provided in this application can implement all the method steps implemented by the second entity in the above method embodiments, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0456] Figure 15 It is a schematic structural diagram of a model registration apparatus 1500 provided in an embodiment of this application. As Figure 15 shown, the apparatus 1500 includes:

[0457] A receiving unit 1510, configured to receive a fourth message sent by a first entity, where the fourth message is used to request storing a first model, and the fourth message includes at least one of the following: a second model identifier, a model transmission method, a model address, or the first model;

[0458] A sending unit 1520, configured to send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

[0459] In one implementation, the receiving unit 1510 is further configured to:

[0460] Receive the first model.

[0461] In one implementation, after receiving the first model, the apparatus 1500 further includes:

[0462] A verification unit, configured to verify the first model to obtain a verification result;

[0463] An update unit, configured to update model information according to the verification result.

[0464] It should be noted here that the above-mentioned model registration apparatus 1500 provided in this application can implement all the method steps implemented by the third entity in the above method embodiment, and can achieve the same technical effect. The same parts and beneficial effects as those in the method embodiment will not be specifically described in this embodiment.

[0465] It should be noted that the division of units in the embodiments of this application is illustrative only, and is only a logical function division. In actual implementation, there may be other division methods. In addition, in each embodiment of this application, each functional unit may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0466] When an integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of each method embodiment of this application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs.

[0467] An embodiment of this application also provides a non-transitory readable storage medium. The non-transitory readable storage medium stores a computer program, and the computer program is used to cause a processor to execute all the method steps of the first entity, or all the method steps of the second entity, or all the method steps of the third entity in the above method embodiments.

[0468] The non-transitory readable storage medium can be any available medium or data storage device that a computer can access, including but not limited to magnetic memories (such as floppy disks, hard disks, magnetic tapes, magneto-optical discs (MO), etc.), optical memories (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor memories (such as ROM, EPROM, EEPROM, non-volatile memories (NAND FLASH), solid state drives (SSD)).

[0469] An embodiment of this application also provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements all or part of the steps of the above method embodiments.

[0470] Those skilled in the art should understand that the embodiments of this application can be provided as a method, a system, or a computer program product. Therefore, this application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application can adopt the form of a computer program product implemented on at least one computer-usable storage medium (including but not limited to disk memories and optical memories, etc.) that contains computer-usable program codes.

[0471] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices produce means for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0472] These processor-executable instructions can also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the processor-readable memory produce a manufacture including instruction means for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0473] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operational steps are performed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more of the flows Figure 1 one or more of the flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0474] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these changes and modifications.

Claims

1. A model registration method, characterized in that, Applied to a first entity, the method includes: Sending a first message to a second entity, the first message being used to request registration of a first model, the first message including an identifier of the first entity, a first model identifier, and model information of the first model, the first model identifier being an identifier of the first model in the first entity; Receiving a second message sent by the second entity in response to the first message, the second message including the first model identifier, a second model identifier, and indication information, the second model identifier being a network identifier assigned by the second entity to the first model, the indication information indicating a registration decision or registration decision-related information; Based on the registration decision-related information, sending a third message to the second entity, the third message including the second model identifier and the registration decision.

2. The method according to claim 1, characterized in that, The first model is a personalized model.

3. The method according to claim 1 or 2, characterized in that, The model information includes: model type, model modality, model algorithm, and model accuracy.

4. The method according to claim 3, wherein The model information further includes a third model identifier and / or a model application scenario; Wherein, the third model identifier is an identifier of a second model, and the first model is trained based on the second model.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Sending a fourth message to the second entity, the fourth message being used to request storage of the first model, the fourth message including at least one of the following: the second model identifier, a model transmission method, a model address, or the first model; Receiving a fifth message sent by the second entity in response to the fourth message, the fifth message being used to indicate a model storage result.

6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Sending a fourth message to a third entity, the fourth message being used to request storage of the first model, the fourth message including at least one of the following: the second model identifier, a model transmission method, a model address, or the first model; Receiving a fifth message sent by the third entity in response to the fourth message, the fifth message being used to indicate a model storage result.

7. The method according to claim 5 or 6, characterized in that, The method further includes: Sending the first model.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Sending a sixth message to the second entity, the sixth message including the second model identifier, the sixth message further including model update information and / or model supplement information; Receiving a seventh message sent by the second entity in response to the sixth message, the seventh message being used to indicate a model update result.

9. The method according to claim 8, wherein The first entity is a first terminal, a first access network device, or a first core network device; The second entity is a Unified Data Management (UDM), a Unified Data Repository (UDR), or a first functional entity, the first functional entity being deployed in a second terminal, a second access network device, or a second core network device; The third entity is deployed in a third terminal, a third access network device, or a third core network device; The first terminal, the second terminal, and the third terminal are the same or different from each other, the first access network device, the second access network device, and the third access network device are the same or different from each other, and the first core network device, the second core network device, and the third core network device are the same or different from each other.

10. A model registration method, characterized in that, Applied to a second entity, the method includes: Receive a first message sent by a first entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is the identifier of the first model in the first entity; In response to the first message, send a second message to the first entity, where the second message includes the first model identifier, a second model identifier, and indication information, and the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information; Receive a third message sent by the first entity, where the third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and a registration decision.

11. The method according to claim 10, wherein, The first model is a personalized model.

12. The method according to claim 10 or 11, characterized in that, The model information includes: model type, model modality, model algorithm, and model accuracy.

13. The method according to claim 12, wherein The model information further includes a third model identifier and / or a model application scenario; Wherein, the third model identifier is an identifier of a second model, and the first model is trained based on the second model.

14. The method according to any one of claims 10-13, characterized in that, The method further includes: Receive a fourth message sent by the first entity, where the fourth message is used to request storage of the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model; In response to the fourth message, send a fifth message to the first entity, where the fifth message is used to indicate a model storage result.

15. The method according to claim 14, wherein The method further includes: Receive the first model.

16. The method according to claim 14 or 15, characterized in that After receiving the first model, the method further includes: Verify the first model to obtain a verification result; Update the model information according to the verification result.

17. The method according to any one of claims 10-16, characterized in that, The method further includes: Receive a sixth message sent by the first entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplementary information; In response to the sixth message, send a seventh message to the first entity, where the seventh message is used to indicate a model update result.

18. A model registration method, characterized in that, Applied to a third entity, the method includes: Receive a fourth message sent by the first entity, where the fourth message is used to request storage of a first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model; In response to the fourth message, send a fifth message to the first entity, where the fifth message is used to indicate a model storage result.

19. The method according to claim 18, wherein The method further includes: Receive the first model.

20. The method according to claim 18 or 19, characterized in that, After receiving the first model, the method further includes: Verify the first model to obtain a verification result; Update the model information according to the verification result.

21. A model registration device, characterized in that, Applied to a first entity, the apparatus includes: A first sending unit, configured to send a first message to a second entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is the identifier of the first model in the first entity; A receiving unit, configured to receive a second message sent by the second entity in response to the first message, where the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information; A second sending unit, configured to send a third message to the second entity based on the registration decision-related information, where the third message includes the second model identifier and the registration decision.

22. A model registration device, characterized in that, Applied to a second entity, the apparatus includes: A first receiving unit, configured to receive a first message sent by a first entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is an identifier of the first model in the first entity; A sending unit, configured to send a second message to the first entity in response to the first message, where the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information; A second receiving unit, configured to receive a third message sent by the first entity, where the third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and the registration decision.

23. A model registration device, characterized in that, Applied to a third entity, the apparatus includes: A receiving unit, configured to receive a fourth message sent by the first entity, where the fourth message is used to request storage of the first model, and the fourth message includes at least one of the following: the second model identifier, a model transmission method, a model address, or the first model; A sending unit, configured to send a fifth message to the first entity in response to the fourth message, where the fifth message is used to indicate a model storage result.

24. A model registration device, characterized in that, Applied to a first entity, the apparatus includes a memory, a transceiver, and a processor: The memory is configured to store a computer program; the transceiver is configured to send and receive data under the control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: Send a first message to a second entity, where the first message is used to request registration of a first model, and the first message includes an identifier of the first entity, a first model identifier, and model information of the first model, and the first model identifier is an identifier of the first model in the first entity; Receive a second message sent by the second entity in response to the first message, where the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is a network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information; Based on the registration decision-related information, send a third message to the second entity, where the third message includes the second model identifier and the registration decision.

25. The device according to claim 24, characterized in that, The first model is a personalized model.

26. The device according to claim 24 or 25, characterized in that, The model information includes: model type, model modality, model algorithm, and model accuracy.

27. The device according to claim 26, characterized in that, The model information further includes a third model identifier and / or a model application scenario; wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

28. The device according to any one of claims 24-27, characterized in that, The processor is further configured to perform the following operations: Send a fourth message to the second entity, the fourth message being used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, model transmission method, model address, or the first model; Receive a fifth message sent by the second entity in response to the fourth message, the fifth message being used to indicate the model storage result.

29. The device according to any one of claims 24-27, characterized in that, The processor is further configured to perform the following operations: Send a fourth message to a third entity, the fourth message being used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, model transmission method, model address, or the first model; Receive a fifth message sent by the third entity in response to the fourth message, the fifth message being used to indicate the model storage result.

30. The method according to claim 28 or 29, characterized in that, The processor is further configured to perform the following operations: Send the first model.

31. The device according to any one of claims 24-30, characterized in that, The processor is further configured to perform the following operations: Send a sixth message to the second entity, the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information; Receive a seventh message sent by the second entity in response to the sixth message, the seventh message being used to indicate the model update result.

32. A model registration device, characterized in that, Applied to a second entity, the device includes a memory, a transceiver, and a processor: The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Receive a first message sent by a first entity, the first message being used to request registering a first model, and the first message includes the identifier of the first entity, the first model identifier, and the model information of the first model, and the first model identifier is the identifier of the first model in the first entity; Send a second message to the first entity in response to the first message, the second message includes the first model identifier, the second model identifier, and indication information, the second model identifier is the network identifier assigned by the second entity to the first model, and the indication information indicates a registration decision or registration decision-related information; Receive a third message sent by the first entity, the third message is a message determined based on the registration decision-related information, and the third message includes the second model identifier and the registration decision.

33. The device according to claim 32, characterized in that, The first model is a personalized model.

34. The device according to claim 32 or 33, characterized in that, The model information includes: model type, model modality, model algorithm, and model accuracy.

35. The device according to claim 34, characterized in that, The model information further includes a third model identifier and / or a model application scenario; wherein, the third model identifier is the identifier of the second model, and the first model is trained based on the second model.

36. The device according to any one of claims 32-35, characterized in that, The processor is further configured to perform the following operations: Receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model; In response to the fourth message, send a fifth message to the first entity, where the fifth message is used to indicate the model storage result.

37. The device according to claim 36, characterized in that, The processor is further configured to perform the following operations: Receive the first model.

38. The device according to claim 36 or 37, characterized in that After receiving the first model, the processor is further configured to perform the following operations: Verify the first model to obtain a verification result; Update the model information according to the verification result.

39. The device according to any one of claims 32 - 38, characterized in that, The processor is further configured to perform the following operations: Receive a sixth message sent by the first entity, where the sixth message includes the second model identifier, and the sixth message further includes model update information and / or model supplement information; In response to the sixth message, send a seventh message to the first entity, where the seventh message is used to indicate the model update result.

40. A model registration device, characterized in that, Applied to a third entity, the device includes a memory, a transceiver, and a processor: The memory is used to store a computer program; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Receive a fourth message sent by the first entity, where the fourth message is used to request storing the first model, and the fourth message includes at least one of the following: the second model identifier, the model transmission method, the model address, or the first model; In response to the fourth message, send a fifth message to the first entity, where the fifth message is used to indicate the model storage result.

41. The device according to claim 40, characterized in that, The processor is further configured to perform the following operations: Receive the first model.

42. The device according to claim 40 or 41, characterized in that, After receiving the first model, the processor is further configured to perform the following operations: Verify the first model to obtain a verification result; Update the model information according to the verification result.

43. A non-transitory readable storage medium, characterized in that, The non-transitory readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the method according to any one of claims 1-8, or the method according to any one of claims 10-17, or the method according to any one of claims 18-20.

Images