Model registration method and apparatus, and storage medium

Abstract

The present disclosure relates to the technical field of communications, and provides a model registration method and apparatus, and a storage medium. The method comprises: a first entity sends a first message to a second entity, wherein the first message is used for requesting to register a first model, the first message comprises an identifier of the first entity, an identifier of the first model, and model information of the first model, and the identifier of the first model is 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, wherein the second message comprises the identifier of the first model, an identifier of a second model, and indication information, the identifier of the second model is a network identifier allocated by the second entity to 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 on the basis of the registration decision related information, wherein the third message comprises the identifier of the second model and the registration decision. Thus, a network can provide services such as personalized model registration for a user, the network or a third party according to requirements, thereby providing a basis for AI-native services.

Description

Model registration method, device and storage medium

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on December 29, 2023, with application number 202311865428.8 and application name “A model registration method, device and storage medium”, the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present disclosure relates to the field of communication technology, and in particular to a model registration method, device, and storage medium. Background Art

[0003] The inherent intelligence of the 6th Generation Mobile Networks (6G) refers to the fact that 6G networks natively support artificial intelligence (AI), make AI capabilities a basic network service, and implement AI as a Service (AIaaS). This enables the network to self-learn and self-evolve, and can then provide AI training services, AI inference services, AI deployment and open services to users, networks or third parties.

[0004] Although the network architecture and network processes of the current mobile communication system can provide users with connection and data transmission services, they cannot provide intelligent endogenous services such as AI model registration and storage. Summary of the Invention

[0005] The present disclosure provides a model registration method, device and storage medium, which solve the technical problem that the communication system cannot provide intelligent endogenous services such as AI model registration and storage.

[0006] In a first aspect, an embodiment of the present disclosure provides a model registration method, applied to a first entity, the method comprising:

[0007] Sending 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, where the first model identifier is an identifier of the first model in the first entity;

[0008] receiving 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

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

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

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

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

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

[0014] In one embodiment, the method further comprises:

[0015] Sending 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, the model transmission mode, the model address, or the first model;

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

[0017] In one embodiment, the method further comprises:

[0018] Sending 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, the model transmission mode, the model address, or the first model;

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

[0020] In one embodiment, the method further comprises:

[0021] The first model is sent.

[0022] In one embodiment, the method further comprises:

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

[0024] A seventh message is received, which is sent by the second entity in response to the sixth message, where the seventh message is used to indicate a model update result.

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

[0026] The second entity is a unified data management UDM, a unified data warehouse 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;

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

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

[0029] In a second aspect, an embodiment of the present disclosure provides a model registration method, applied to a second entity, the method comprising:

[0030] receiving a first message sent by a first entity, where the first message is 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, where the first model identifier is an identifier of the first model in the first entity;

[0031] sending 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

[0032] A third message sent by the first entity is received, 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.

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

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

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

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

[0037] In one embodiment, the method further comprises:

[0038] receiving 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, the model transmission mode, the model address, or the first model;

[0039] In response to the fourth message, a fifth message is sent to the first entity, where the fifth message is used to instruct the model to store the result.

[0040] In one embodiment, the method further comprises:

[0041] The first model is received.

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

[0043] Verifying the first model to obtain a verification result;

[0044] The model information is updated according to the verification result.

[0045] In one embodiment, the method further comprises:

[0046] receiving a sixth message sent by the first entity, where the sixth message includes the second model identifier and further includes model update information and / or model supplementary information;

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

[0048] In a third aspect, an embodiment of the present disclosure provides a model registration method, applied to a third entity, the method comprising:

[0049] receiving 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, the model transmission mode, the model address, or the first model;

[0050] In response to the fourth message, a fifth message is sent to the first entity, where the fifth message is used to instruct the model to store the result.

[0051] In one embodiment, the method further comprises:

[0052] The first model is received.

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

[0054] Verifying the first model to obtain a verification result;

[0055] The model information is updated according to the verification result.

[0056] In a fourth aspect, an embodiment of the present disclosure provides a model registration device, applied to a first entity, the device comprising:

[0057] 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, the first message including 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;

[0058] a first receiving unit, configured to receive 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 allocated by the second entity to the first model, and the indication information indicating a registration decision or registration decision related information;

[0059] The second sending unit is 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.

[0060] In a fifth aspect, an embodiment of the present disclosure provides a model registration device, applied to a second entity, the device comprising:

[0061] 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 including 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;

[0062] 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, a second model identifier, and indication information, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

[0063] The second receiving unit is 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 includes the second model identifier and the registration decision.

[0064] In a sixth aspect, an embodiment of the present disclosure provides a model registration device, applied to a third entity, the device comprising:

[0065] a receiving unit, configured to receive a fourth message sent by the first entity, wherein 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, the model transmission mode, the model address, or the first model;

[0066] A sending unit is used 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.

[0067] In a seventh aspect, an embodiment of the present disclosure provides a model registration device, applied to a first entity, the device including a memory, a transceiver, and a processor:

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

[0069] Sending 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, where the first model identifier is an identifier of the first model in the first entity;

[0070] receiving 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

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

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

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

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

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

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

[0077] Sending 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, the model transmission mode, the model address, or the first model;

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

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

[0080] Sending 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, the model transmission mode, the model address, or the first model;

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

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

[0083] The first model is sent.

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

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

[0086] A seventh message is received, which is sent by the second entity in response to the sixth message, where the seventh message is used to indicate a model update result.

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

[0088] The second entity is a unified data management UDM, a unified data warehouse 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;

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

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

[0091] In an eighth aspect, an embodiment of the present disclosure provides a model registration device, applied to a second entity, the device including a memory, a transceiver, and a processor:

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

[0093] receiving a first message sent by a first entity, where the first message is 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, where the first model identifier is an identifier of the first model in the first entity;

[0094] sending 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

[0095] A third message sent by the first entity is received, 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.

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

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

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

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

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

[0101] receiving 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, the model transmission mode, the model address, or the first model;

[0102] In response to the fourth message, a fifth message is sent to the first entity, where the fifth message is used to instruct the model to store the result.

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

[0104] The first model is received.

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

[0106] Verifying the first model to obtain a verification result;

[0107] The model information is updated according to the verification result.

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

[0109] receiving a sixth message sent by the first entity, where the sixth message includes the second model identifier and further includes model update information and / or model supplementary information;

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

[0111] In a ninth aspect, an embodiment of the present disclosure provides a model registration device, applied to a third entity, the device including a memory, a transceiver, and a processor:

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

[0113] receiving 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, the model transmission mode, the model address, or the first model;

[0114] In response to the fourth message, a fifth message is sent to the first entity, where the fifth message is used to instruct the model to store the result.

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

[0116] The first model is received.

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

[0118] Verifying the first model to obtain a verification result;

[0119] The model information is updated according to the verification result.

[0120] In a tenth aspect, an embodiment of the present disclosure provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute any one of the methods of the first aspect.

[0121] In an eleventh aspect, an embodiment of the present disclosure provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute any one of the methods of the second aspect.

[0122] In the twelfth aspect, an embodiment of the present disclosure provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute any method of the third aspect.

[0123] The disclosed embodiments provide a model registration method, device, and storage medium, the method comprising: a first entity 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 a 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 a second model identifier and a registration decision. By adding a model registration function and a corresponding registration process to the network, the network can provide personalized model registration and other services to users, networks, or third parties on demand, providing a foundation for endogenous intelligence.

[0124] It should be understood that the contents described in the above summary of the invention are not intended to limit the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easier to understand through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0125] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the following is a brief introduction to the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0126] FIG1 is a schematic diagram of an architecture of a communication system in the related art;

[0127] FIG2 is a schematic diagram of an architecture of a communication system provided by an embodiment of the present disclosure;

[0128] FIG3 is another schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0129] FIG4 is a flowchart of a model registration method according to an embodiment of the present disclosure;

[0130] FIG5 is a flow chart of a model storage method provided by an embodiment of the present disclosure;

[0131] FIG6 is a flow chart of a model updating method provided by an embodiment of the present disclosure;

[0132] FIG7 is a second flowchart of the model registration method provided by an embodiment of the present disclosure;

[0133] FIG8 is a third flowchart of the model registration method provided by an embodiment of the present disclosure;

[0134] FIG9 is a fourth flowchart of the model registration method provided by an embodiment of the present disclosure;

[0135] FIG10 is a schematic structural diagram of a model registration device 1000 provided in an embodiment of the present disclosure;

[0136] FIG11 is a schematic structural diagram of a model registration device 1100 provided in an embodiment of the present disclosure;

[0137] FIG12 is a schematic structural diagram of a model registration device 1200 provided in an embodiment of the present disclosure;

[0138] FIG13 is a schematic structural diagram of a model registration device 1300 provided in an embodiment of the present disclosure;

[0139] FIG14 is a schematic structural diagram of a model registration device 1400 provided in an embodiment of the present disclosure;

[0140] FIG15 is a schematic structural diagram of a model registration device 1500 provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0141] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0142] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.

[0143] The terms "first," "second," and "third" that appear in the embodiments of this disclosure are used only to illustrate and distinguish the objects being described. They are not in any particular order, do not represent a specific limit on the number of objects in the embodiments of this disclosure, and do not constitute any limitation on the embodiments of this disclosure. 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. The use of terms such as "first" and "third" is only to distinguish between the different model identifiers, and does not indicate a difference in size, priority, or importance between the two model identifiers.

[0144] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0145] The embodiments of the present disclosure provide a model registration and device for providing personalized model registration and other services to users, networks or third parties on demand.

[0146] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0147] The terminal involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal may also be different. For example, in a 5G system, the terminal may be called User Equipment (UE). A wireless terminal may be a USB storage device, other personal computer memory devices, and a dongle. It may also communicate with one or more core networks (CN) via a radio access network (RAN). A wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal. For example, it may be a portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted mobile device that exchanges language and / or data with a radio access network. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablet computers, Machine-type Communication (MTC) terminals, etc. A wireless terminal may also be referred to as 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 points and routers / modems that meet the limitations of this definition, but are not limited in the embodiments of the present disclosure.

[0148] The access network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to the terminal. Depending on the application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present disclosure may be an evolutionary network device (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, etc., or a home evolved Node B (HeNB), a relay node, a femto, a pico base station, a network test device, etc., which is not limited in the embodiments of the present disclosure. In some network structures, network devices may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0149] Figure 1 is a schematic diagram of an architecture of a communication system in related art. As shown in Figure 1, the architecture includes a terminal, access network equipment, core network equipment, and a data network (DN) part.

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

[0151] The PCF entity is mainly used to guide the unified policy framework of network behavior and provide policy rule information to control plane entities (such as AMF, SMF, etc.).

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

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

[0154] The UPF entity is used to receive and forward user plane data. For example, the UPF entity can receive user plane data from a service server and send it to the terminal via the access network device. The UPF entity can also receive user plane data from the terminal via the access network device and forward it to the service server.

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

[0156] The UDM entity is mainly used for terminal contract data management, including the storage and management of terminal identification, terminal access authorization, etc.

[0157] The data network portion can be the data network that provides business services to users. Generally, the client is located at the terminal, and the server is located on 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.

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

[0159] Based on the technical problems in related technologies, the embodiments of the present disclosure provide a model registration method, which can construct a personalized model registration process through the interaction between multiple entities in the communication system, so that the communication system can provide personalized model registration, storage and other services to users, networks or third parties on demand.

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

[0161] The architecture of the communication system provided by the embodiments of the present disclosure may be as shown in Figure 2 or Figure 3, wherein the architecture shown in Figure 2 is a RAN service-oriented architecture, and the architecture shown in Figure 3 is a RAN non-service-oriented architecture. As shown in Figure 2 or Figure 3, the architecture includes a Requirement Analyzing 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.

[0162] The RAF entity is primarily used to determine service requirements.

[0163] For example, the RAF entity can determine service requirements by receiving user requests; the RAF entity can also perceive changes in scenario requirements and determine service requirements by analyzing perceived data; the RAF entity can also analyze current data / third-party data and historical data through AI algorithms to determine service requirements.

[0164] The NAF entity can be used to determine the execution operation list of the target service based on service requirements. The execution operation list is a series of execution operations, including connection establishment and assurance, task calculation, data processing, AI training / inference, etc.

[0165] 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 execution operation list of the target service.

[0166] Each NEF entity can be used to implement a category of functions, such as control plane network functions, user plane network functions, data plane network functions, and computing network functions. In other words, an NEF entity can perform a single network service operation, such as connection establishment and data computation, or it can perform collaborative operations to provide complex services, such as subnet establishment and AI joint training. In other words, the execution of a service can be performed by a single NEF entity or by multiple NEF entities in collaboration.

[0167] The third entity is mainly used to store the AI ​​model. The AI ​​model stored in the third entity is the AI ​​model registered in the second entity.

[0168] The third entity may also be referred to as an AI Model Storage Function (AIMSF) entity.

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

[0170] The fourth entity may also be referred to as an AI Model Registration Function (AIMRF) entity.

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

[0172] The fifth entity may also be referred to as an AI Model Authentication Function (AIMAF) entity.

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

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

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

[0176] When the above-mentioned entity is deployed on the access network equipment, it may mean that the above-mentioned entity is deployed on an existing functional entity such as a network function (NF) entity, an operation administration and maintenance (OAM) entity, or the above-mentioned entity may be deployed as a separate device in the access network.

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

[0178] The architecture of the communication system of the embodiment of the present disclosure includes not only the above-mentioned entities, but also other functional entities, such as a network resource registration and collection function (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 indicator parameters and save QoS indicator parameters generated by other network elements), a user AI model registration management network element (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 function (UDR) entity, a PCF entity, an AMF entity, an SMF entity, and a UPF entity. The embodiment of the present disclosure does not limit this.

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

[0180] Based on the above communication system architecture, the following details how multiple entities in the architecture interact to achieve on-demand provision of services such as model registration.

[0181] FIG4 is a flowchart of a model registration method according to an embodiment of the present disclosure. As shown in FIG4 , the method includes:

[0182] S401: A first entity sends a first message to a second entity. 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 first model information.

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

[0184] The first entity may be a first terminal, a first access network device, or a first core network device.

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

[0186] Exemplarily, the first functional entity may be an AIMRF entity, a UMRMF entity or a NAMRF entity.

[0187] 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, the first core network device, the second core network device and the third core network device are the same or different from each other.

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

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

[0190] The first message may also be referred to as a model registration request message.

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

[0192] The first model may also be a model obtained by optimizing the first entity.

[0193] For example, the first entity may first obtain the second model and model optimization data, and optimize and train the second model based on the model optimization data to obtain the first model. That is, the first model is obtained based on the training of the second model.

[0194] That is to say, the second model can also be called the basic model.

[0195] In a possible implementation, the first model in the embodiment of the present disclosure may be a personalized model.

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

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

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

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

[0200] Model modalities can include voice, text, image, multimodality, etc.

[0201] The model algorithm can indicate the algorithm type of the first model, which may include supervised learning, deep learning, reinforcement learning, etc. The model algorithm can also indicate the algorithm subtype of the first model, which may include a deep reinforcement learning network (Deep Q-Leaning Network, DQN) algorithm, a support vector machine (Support Vector Machine, SVM) algorithm, etc.

[0202] When the model's algorithm type is reinforcement learning, its algorithm subtype can be the DQN algorithm; when the model's algorithm type is supervised learning, its algorithm subtype can be the SVM algorithm.

[0203] Model accuracy may indicate the average accuracy of the first model inference.

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

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

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

[0207] The model application scenario may indicate the scenario in which the first model is applied, including wireless communication, medical treatment, education, transportation, etc.

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

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

[0210] Table 1 Model registration information

[0211] It should be noted that, in some embodiments, the model registration information may not include at least one of the third model identifier, the model application scenario, and the algorithm subtype, that is, the model registration information may not include the third model identifier, may not include the model application scenario, may not include the algorithm subtype, may not include the third model identifier and the model application scenario, may not include the third model identifier and the algorithm subtype, may not include the model application scenario and the algorithm subtype, or may not include the third model identifier, the model application scenario, and the algorithm subtype.

[0212] S402: The second entity sends a second message to the first entity in response to the first message.

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

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

[0215] The second entity may store a plurality of registration policies, each of which is applicable to a type of first entity.

[0216] Illustratively, the second entity may determine a target registration policy from a plurality of 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.

[0217] The second message may also be referred to as a model registration response message.

[0218] The second message may include the first model identifier, the second model identifier, and indication information.

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

[0220] The indication information may indicate a registration decision or information related to the registration decision.

[0221] The registration decision may be registration or non-registration or cancellation of registration.

[0222] The registration decision-related information may include a model query result, and the model query result may include an existing similar model or no similar model.

[0223] If the second entity decides whether to register, the indication information indicates the registration decision.

[0224] If the first entity decides whether to register, the indication information indicates registration decision related information. After receiving the indication information, the first entity may execute S403.

[0225] S403: The first entity sends a third message to the second entity based on the registration decision related information.

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

[0227] The third message may include the second model identification and the registration decision.

[0228] 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 structure is that there is an existing similar model, the registration decision in the third message may be cancellation of registration.

[0229] In the embodiment shown in Figure 4, the communication system constructs a personalized model registration process through the interaction between various entities, so that the communication system can intelligently provide personalized model registration services to users, networks or third parties based on personalized model registration requirements during the communication process.

[0230] The embodiment shown in FIG4 illustrates the personalized model registration process. The model storage process will be described in detail below in conjunction with FIG5 .

[0231] FIG5 is a flow chart of a model storage method provided by an embodiment of the present disclosure. As shown in FIG5 , the method includes:

[0232] S501: A first entity sends a fourth message to a second entity, where the fourth message is used to request storage of a first model.

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

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

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

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

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

[0238] If the fourth message carries the first model, the second entity can directly execute S502; if the fourth message does not carry the first model 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 fourth message does not carry the first model and the first model is not stored locally, the fourth message can carry the model address, 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.

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

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

[0241] Verification may mean first performing privacy and security verification on 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.

[0242] Among them, 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 the second entity receives 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 with the information of the received first model or inconsistent; 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.

[0243] Privacy and security verification may also be performed by the second entity or the third entity. The verification process is as described above and will not be repeated here.

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

[0245] Table 2 Updated model information

[0246] It should be noted that, in some embodiments, the updated model information may not include at least one of the third model identifier, the model application scenario, and the algorithm subtype.

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

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

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

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

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

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

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

[0254] In the embodiment shown in Figure 5, the first entity stores the first model in the second entity. In this case, the second entity has both model registration and model storage functions. If the second entity only has model registration, the first entity needs to store the first model in a third entity. The storage process can be seen in the embodiment shown in Figure 5 and will not be repeated here. In this case, the third entity has model storage function.

[0255] 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 to users, networks or third parties based on personalized model storage needs during the communication process.

[0256] Based on any of the above embodiments, the model updating process is described in detail below with reference to FIG6 .

[0257] FIG6 is a flow chart of a model updating method provided by an embodiment of the present disclosure. As shown in FIG6 , the method includes:

[0258] S601: A first entity sends a sixth message to a second entity.

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

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

[0261] The sixth message may include the second model identifier, model update information and / or model supplement information.

[0262] The model update information may refer to information after the first model is optimized.

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

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

[0265] The second entity can save model details, as shown in Table 3:

[0266] Table 3 Model details

[0267] It should be noted that, in some embodiments, the model detailed information may not include at least one of the third model identifier, model application scenario, algorithm subtype, model segmentation information, model compression information, compressed model full model ID, model parameter quantity, model performance, the framework version on which the first model depends, the dependent library, and model training information.

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

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

[0270] The seventh message may be used to indicate the model update result.

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

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

[0273] In the embodiment shown in FIG6 , 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.

[0274] The embodiment shown in FIG. 4 , the embodiment shown in FIG. 5 , the embodiment in which the first model is stored by a third entity, and the embodiment shown in FIG. 6 may be arbitrarily combined.

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

[0276] In embodiment 1, as shown in FIG7 , taking the first entity as a terminal and the second entity as a UDM as an example, the method includes:

[0277] 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 modality, a model algorithm, and a model accuracy.

[0278] In some embodiments, the first message may also include a model application scenario.

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

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

[0281] 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 and the model transmission mode.

[0282] In some embodiments, the fourth message may also carry a model address and / or the first model.

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

[0284] S704: Model transmission.

[0285] S705: Model verification.

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

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

[0288] 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 supplementary information.

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

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

[0291] Embodiment 2, as shown in FIG8 , taking the first entity as a terminal and the second entity as a first functional entity as an example, the method includes:

[0292] 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 modality, a model algorithm, and a model accuracy.

[0293] In some embodiments, the first message may also include a model application scenario.

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

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

[0296] 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 the second model identifier and the model transmission mode.

[0297] In some embodiments, the fourth message may also carry a model address and / or the first model.

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

[0299] S804: Model transmission.

[0300] S805: Model verification.

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

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

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

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

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

[0306] Embodiment 3, as shown in FIG9 , taking the first entity as a terminal and the second entity as a first functional entity as an example, the method includes:

[0307] 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 modality, a model algorithm, and a model accuracy.

[0308] In some embodiments, the first message may also include a model application scenario.

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

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

[0311] 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 and the model transmission mode.

[0312] In some embodiments, the fourth message may also carry a model address and / or the first model.

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

[0314] S904: Model transmission.

[0315] S905: Model verification.

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

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

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

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

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

[0321] On the basis of Example 2 and Example 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.

[0322] FIG10 is a schematic diagram of the structure of a model registration device 1000 provided in an embodiment of the present disclosure. As shown in FIG10 , the device 1000 includes: a memory 1010 , a transceiver 1020 , and a processor 1030 .

[0323] 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:

[0324] 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;

[0325] 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

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

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

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

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

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

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

[0332] Sending 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0333] A fifth message is received, which is sent by the second entity in response to the fourth message, where the fifth message is used to instruct the model to store the result.

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

[0335] Sending a fourth message to the 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0336] A fifth message is received, which is sent by the third entity in response to the fourth message, where the fifth message is used to instruct the model to store the result.

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

[0338] Send the first model.

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

[0340] Sending a sixth message to the second entity, where the sixth message includes the second model identifier and the model update information and / or model supplementary information;

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

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

[0343] The second entity is a unified data management (UDM), a unified data warehouse 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;

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

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

[0346] It should be noted here that the above-mentioned model registration device 1000 provided by the present disclosure can implement all the method steps implemented by the first entity in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be repeated here.

[0347] FIG11 is a schematic diagram of the structure of a model registration device 1100 provided in an embodiment of the present disclosure. As shown in FIG11 , the device 1100 includes: a memory 1110 , a transceiver 1120 , and a processor 1130 .

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

[0349] 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, where the first model identifier is an identifier of the first model in the first entity;

[0350] Sending 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

[0351] A third message sent by the first entity is received, 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.

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

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

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

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

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

[0357] receiving 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0358] In response to the fourth message, a fifth message is sent to the first entity, where the fifth message is used to instruct the model to store the result.

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

[0360] A first model is received.

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

[0362] Verify the first model and obtain verification results;

[0363] Update the model information based on the verification results.

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

[0365] receiving a sixth message sent by the first entity, where the sixth message includes the second model identifier and also includes model update information and / or model supplementary information;

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

[0367] It should be noted here that the above-mentioned model registration device 1100 provided by the present disclosure can implement all the method steps implemented by the second entity in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be repeated here.

[0368] FIG12 is a schematic diagram of the structure of a model registration device 1200 provided in an embodiment of the present disclosure. As shown in FIG12 , the device 1200 includes: a memory 1210 , a transceiver 1220 , and a processor 1230 .

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

[0370] receiving 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0371] In response to the fourth message, a fifth message is sent to the first entity, where the fifth message is used to instruct the model to store the result.

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

[0373] A first model is received.

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

[0375] Verify the first model and obtain verification results;

[0376] Update the model information based on the verification results.

[0377] It should be noted here that the above-mentioned model registration device 1200 provided by the present disclosure can implement all the method steps implemented by the third entity in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be repeated here.

[0378] Among them, in Figures 10 to 12, when the model registration device is a terminal, the device can also include a user interface. For different terminals, the user interface can also be an interface that can be connected to external and internal devices. The connected devices include but are not limited to a keypad, display, speaker, microphone, joystick, etc.

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

[0380] 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), and the processor may also adopt a multi-core architecture.

[0381] FIG13 is a schematic diagram of the structure of a model registration device 1300 provided in an embodiment of the present disclosure. As shown in FIG13 , the device 1300 includes:

[0382] A first sending unit 1310 is 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, where the first model identifier is an identifier of the first model in the first entity;

[0383] A first receiving unit 1320 is 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, where the second model identifier is a network identifier allocated by the second entity to the first model, and the indication information indicates a registration decision or registration decision related information;

[0384] The second sending unit 1330 is 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.

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

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

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

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

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

[0390] 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0391] The second receiving unit is 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.

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

[0393] a fourth sending unit, configured to send a fourth message to the 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0394] The third receiving unit is 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.

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

[0396] The fifth sending unit is configured to send the first model.

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

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

[0399] The fourth receiving unit is 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.

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

[0401] The second entity is a unified data management (UDM), a unified data warehouse 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;

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

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

[0404] It should be noted here that the above-mentioned model registration device 1300 provided by the present disclosure can implement all the method steps implemented by the first entity in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be repeated here.

[0405] FIG14 is a schematic diagram of the structure of a model registration device 1400 provided in an embodiment of the present disclosure. As shown in FIG14 , the device 1400 includes:

[0406] A first receiving unit 1410 is 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, where the first model identifier is an identifier of the first model in the first entity;

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

[0408] The second receiving unit 1430 is 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 includes the second model identifier and the registration decision.

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

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

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

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

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

[0414] a third 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0415] The second sending unit is 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.

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

[0417] The fourth receiving unit is configured to receive the first model.

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

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

[0420] The updating unit is used to update the model information according to the verification results.

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

[0422] 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 further includes model update information and / or model supplementary information;

[0423] The third sending unit is 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.

[0424] It should be noted here that the above-mentioned model registration device 1400 provided by the present disclosure can implement all the method steps implemented by the second entity in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be repeated here.

[0425] FIG15 is a schematic diagram of the structure of a model registration device 1500 provided in an embodiment of the present disclosure. As shown in FIG15 , the device 1500 includes:

[0426] The receiving unit 1510 is 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: a second model identifier, a model transmission mode, a model address, or the first model;

[0427] The sending unit 1520 is 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.

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

[0429] A first model is received.

[0430] In one embodiment, after receiving the first model, the apparatus 1500 further includes:

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

[0432] The updating unit is used to update the model information according to the verification results.

[0433] It should be noted here that the above-mentioned model registration device 1500 provided by the present disclosure can implement all the method steps implemented by the third entity in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be repeated here.

[0434] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0435] If the 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 the present disclosure is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of each method embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.

[0436] An embodiment of the present disclosure further provides a non-transitory readable storage medium, which stores a computer program. The computer program is used to enable a processor to execute all method steps of the first entity, or all method steps of the second entity, or all method steps of the third entity in the above method embodiment.

[0437] Non-transitory readable storage media can be any available media or data storage devices that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.

[0438] The embodiments of the present disclosure further provide a computer program product, including a computer program, which implements all or part of the steps of the above method embodiments when executed by a processor.

[0439] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on at least one computer-usable storage medium (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0440] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0441] These processor-executable instructions may 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, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0442] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0443] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. A model registration method, wherein, 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 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, 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, wherein The first model is a personalized model.

3. The method according to claim 1 or 2, wherein 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, wherein, 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-4, wherein, 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, wherein The method further includes: Sending the first model.

8. The method according to any one of claims 1-7, wherein, 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, wherein, 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 the 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, wherein 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, wherein, 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, wherein, 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, wherein, 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 supplement 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, wherein, When 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, wherein 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, wherein, When applied to a first entity, the device 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, wherein, 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, wherein, 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, wherein, 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; 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.

25. The device according to claim 24, wherein, The first model is a personalized model.

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

27. The apparatus according to claim 26, wherein 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 apparatus according to any one of claims 24 - 27, wherein, 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 apparatus according to any one of claims 24-27, wherein, 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, wherein, The processor is further configured to perform the following operations: Send the first model.

31. The apparatus according to any one of claims 24 - 30, wherein, 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, wherein, 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 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 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 for 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 apparatus according to claim 32, wherein, The first model is a personalized model.

34. The apparatus according to claim 32 or 33, wherein, The model information includes: model type, model modality, model algorithm, and model accuracy.

35. The apparatus according to claim 34, wherein, 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 apparatus according to any one of claims 32 - 35, wherein, 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 apparatus according to claim 36, wherein, The processor is further configured to perform the following operations: Receive the first model.

38. The device according to claim 36 or 37, wherein 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, wherein, 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, wherein, 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 apparatus according to claim 40, wherein, The processor is further configured to perform the following operations: Receive the first model.

42. The apparatus according to claim 40 or 41, wherein 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, wherein, 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