Communication method and device
By introducing the first information domain and the second information domain in the communication system, combined with the use of model identification, the problem of low management efficiency of AI/ML model in the prior art is solved, and the flexibility of the model control process and the management efficiency are improved. .
Patent Information
- Application Number
- PCT/CN2023/093094
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-14
AI Technical Summary
When existing communication systems manage a large number of AI/ML models, it is difficult to flexibly use model identification, resulting in inefficient management of model control processes.
By introducing a first information domain and a second information domain in the communication method, respectively, for representing a fixed model identifier and a variable model identifier, it is used in combination to achieve flexible management of model identifiers.
It improves the flexibility and management efficiency of the model control process, avoids the problem of coarse-grained management, and enhances the controllability of the communication system.
Smart Images

Figure CN2023093094_14112024_PF_FP_ABST
Abstract
Description
Communication method and device Technical Field
[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art
[0002] With the continuous development of artificial intelligence (AI) and machine learning (ML) technologies, the integration of communications technology with AI / ML is a trend in future communications. Due to the complexity and diversity of communication system scenarios, communication systems may introduce a large number of AI / ML models, necessitating consideration of how to manage these models.
[0003] Summary of the Invention
[0004] The embodiments of the present application provide a communication method and device that can use model identification more flexibly.
[0005] An embodiment of the present application provides a communication method, including:
[0006] The first device sends first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0007] An embodiment of the present application provides a communication method, including:
[0008] The second device receives first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0009] An embodiment of the present application provides a first device, including:
[0010] The first sending unit is configured to send first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0011] An embodiment of the present application provides a second device, including:
[0012] The first receiving unit is configured to receive first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0013] An embodiment of the present application provides a communication device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory, so that the communication device executes the above-mentioned communication method.
[0014] An embodiment of the present application provides a chip for implementing the above-mentioned communication method.
[0015] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.
[0016] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to execute the above-mentioned communication method.
[0017] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.
[0018] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.
[0019] In the embodiment of the present application, the model identifier can be used more flexibly through the first information field and / or the second information field. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.
[0021] FIG2 is a schematic flowchart of a communication method according to an embodiment of the present application.
[0022] FIG3 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0023] FIG4 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0024] FIG5 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0025] FIG6 is a schematic flowchart of a communication method according to an embodiment of the present application.
[0026] FIG7 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0027] FIG8 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0028] FIG9 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0029] FIG10 is a schematic block diagram of a first device according to an embodiment of the present application.
[0030] FIG11 is a schematic block diagram of a first device according to another embodiment of the present application.
[0031] FIG12 is a schematic block diagram of a second device according to an embodiment of the present application.
[0032] FIG13 is a schematic block diagram of a second device according to another embodiment of the present application.
[0033] FIG14 is a schematic block diagram of a communication device according to an embodiment of the present application.
[0034] FIG15 is a schematic block diagram of a chip according to an embodiment of the present application.
[0035] FIG16 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION
[0036] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0037] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0038] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0039] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.
[0040] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.
[0041] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0042] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0043] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).
[0044] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0045] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0046] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.
[0047] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.
[0048] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0049] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.
[0050] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.
[0051] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.
[0052] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.
[0053] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.
[0054] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.
[0055] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.
[0056] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.
[0057] To facilitate the management and control of cell-related operations, the communication system introduces related cell identifiers. At the same time, the cell identifier definitions vary for different usage scenarios, as follows:
[0058] A physical cell identity (PCI) has been introduced for physical cells. Combined with the cell's associated frequency identifier, a complete physical cell identity is formed. The PCI uniquely identifies a cell in a local area and can be reused in different geographic areas. The PCI can be used for measurement reporting, measurement configuration, and other scenarios.
[0059] A Cell Global Identity (CGI) is introduced for logical cells. The CGI consists of a Public Land Mobile Network (PLMN) identity (ID) and a cell identity. The CGI is a globally unique identifier that can be used in measurement reporting and other scenarios.
[0060] For a serving cell that is a secondary cell (SCell), a secondary cell index (SCell index) is introduced to facilitate terminal equipment to manage one or more cells configured on a network device, such as SCell activation and deactivation operations.
[0061] In order to facilitate the management of a large number of introduced AI / ML models, the communication system can introduce an identifier (ID) for the AI / ML model. In the embodiment of the present application, the AI / ML model identifier (ID) can be defined, and the AI / ML model identifier ID can also be used to perform AI operations.
[0062] FIG2 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 200 can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.
[0063] S210: The first device sends first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0064] In an embodiment of the present application, the first device may store model-related information, wherein the model-related information includes one or more of a model identifier, model algorithm data, and model description information, and some information needs to be synchronized with the second device to facilitate subsequent model management. For example, the first device may send first information to the second device. The model may be an artificial intelligence (AI) model and / or a machine learning (ML) model. The first model identifier may include an identifier of the AI model and / or the ML model.
[0065] In an embodiment of the present application, the first information may include only the first information field, or only the second information field, or may include the first information field and the second information field. For example, the first information field and the second information field are combined to obtain a first model identifier, the first information field is used to represent the fixed part in the model identifier, and the second information field is used to represent the non-fixed part in the model representation. The model identifier can be used more flexibly through the first information field and / or the second information field, which is conducive to the subsequent more flexible execution of the model control process based on the model identifier. For example, the model control process is executed using a fixed model identifier alone, a non-fixed model identifier alone, or a model identifier that combines the two.
[0066] In some scenarios, the first device may be a terminal device, and the second device may be a network device.
[0067] In some scenarios, the first device may be a network device, and the second device may be a terminal device.
[0068] In some scenarios, the first device may be a first terminal device, and the second device may be a second terminal device.
[0069] In some scenarios, the first device may be a first network device, and the second device may be a second network device.
[0070] In an embodiment of the present application, the network device may be an access network device or a core network device or an AI / ML model related information management device or an operation administration and maintenance (OAM) device.
[0071] Exemplarily, the access network device may be any of the following:
[0072] gNB, Centralized Unit (CU), Distributed Unit (DU), Centralized Unit-Control Plane (CU-CP), Centralized Unit-User Plane (CU-UP).
[0073] Exemplarily, the core network device may be any of the following:
[0074] Location Management Function (LMF) network element, Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), Unified Data Management (UDM), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), User Plane Function (UPF), Sensing Control Function (SF), Network Data Analytics Function (NWDAF) network element.
[0075] In one embodiment, the first information field includes at least one of a model identifier with an invariant meaning, a universal model identifier, and a globally unique model identifier. The first information field of the first model identifier may be predefined by the protocol or known. For example, the protocol predefines the value and meaning of the first information field. In any functional system using the protocol, the meaning corresponding to the value of the first information field may be fixed, determined, known, or globally applicable. For example, one or more information such as the model type, function, and name may be determined based on the value of the first information field predefined by the protocol.
[0076] In one embodiment, the second information field includes a variable-meaning model identifier and / or a custom model identifier. The meaning corresponding to the value of the second information field of the first model identifier may not be fixed. The same value may have the same or different meanings in different devices or systems. The specific meaning corresponding to each value of the second information field may be determined or defined by the information provider.
[0077] In an embodiment of the present application, each model may correspond to a fixed first information field and / or a non-fixed second information field. For example, the protocol pre-defined model identifier ID1 indicates a model for CSI compression feedback, model identifier ID2 indicates a model for beam management, and model identifier ID3 indicates a model for positioning. If the first information field of the first model identifier includes model identifier ID1, the receiver, sender, storage, or generator of the first model identifier may determine that the model corresponding to model identifier ID1 is used for the CSI compression feedback function.
[0078] In one embodiment, the first information field and / or the second information field has associated model description information.
[0079] In one embodiment, the model description information includes one or more of the following information:
[0080] Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of the input parameters associated with the model, preprocessing rules for input parameters associated with the model, information on the types of output parameters associated with the model, information on the format requirements of the output parameters associated with the model, preprocessing rules for output parameters associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization feature information of the model, version information of the model, accuracy level information of the model, compilation format information of the model data, storage format information of the model data, computational complexity information of the model, complexity information of the model, and size information of the model.
[0081] Information 1: Functional characteristics of model association
[0082] The functional characteristics associated with the model are used to indicate the functions associated with the corresponding model. For example, model 1 is used for the Channel State Information (CSI) compression feedback function, model 2 is used for the mobility enhancement function, model 3 is used for the beam prediction function, model 4 is used for the positioning function, etc.
[0083] Information 2: Model-related input parameter type information
[0084] The model-associated input parameter type information indicates the type of input parameters required by the corresponding model. For example, Model 3 is used for beam prediction, and the required input parameters include the index information of the actual measured beam and the signal measurement results of each beam obtained by actual measurement.
[0085] Information 3: Model-related input parameter format requirements
[0086] The input parameter format requirement information associated with the model is used to indicate the format of the input parameters required by the corresponding model. For example: Model 3 is used for the beam prediction function. Assuming that the network device can schedule resources in 8 beam directions, but only sends measurement reference signals in 4 of the beam directions, the terminal device can only obtain the measurement results of 4 beams in each measurement process. Scenario 1: The beam prediction model only predicts the signal measurement results of other beams that have not been measured at the current moment. If the beam prediction model used in Scenario 1 only needs to input the measurement results of 4 beams, the measurement results of the 4 beams obtained by the terminal device in each measurement can just be used as the input of the beam prediction model of Scenario 1 (the output can obtain the measurement results of the 8 beams associated with this measurement). That is: 4 true values, 4 predicted values, or the output is the predicted measurement results of 4 beams); Scenario 2: The beam prediction model is used to predict the measurement results of 8 beams in a period of time in the future. In this scenario, the input of the beam prediction model may be a set of measurement results of 4 beams obtained in the past N measurement processes, and the output of the beam prediction model is a set of measurement results of 8 beams in the future. For example, the input of the beam prediction model is a set of three groups of measurement results of 4 beams obtained at T-3, T-2, and T-1, and the output of the beam prediction model is a set of two groups of measurement results of 8 beams at time T and time T+1.
[0087] In summary, although beam prediction is performed using the same measurement results of four beams (the model input parameter types are the same), different application scenarios require different input data formats. Therefore, the input parameter format requirements associated with the AI / ML model are also one of the key information for describing a model.
[0088] Information 4: Model-associated input parameter preprocessing rules
[0089] The input parameter preprocessing rules associated with the model are used to indicate how to reprocess the input data set of the corresponding model. The operations involved in the reprocessing process may include at least one of data dimensionality reduction, data dimensionality increase, redundancy elimination, and redistribution.
[0090] Data dimensionality reduction: If the data dimension is higher than the dimension required by the model input, the data needs to be reduced in dimension through preprocessing rules before entering the model;
[0091] Data dimensionality increase: If the data dimension is lower than the dimension required by the model input, the data needs to be increased in dimension through preprocessing rules before entering the model;
[0092] Redundancy elimination: If the distribution or information content of multiple sets of data is similar, redundancy needs to be eliminated through preprocessing rules before entering the data into the model. This is because redundant data often does not bring more performance improvements but instead increases ineffective operations.
[0093] Redistribution: In some cases, it is difficult to obtain good model generalization by training data with similar feature information together. Redistributing data with different feature information is conducive to obtaining a model with better generalization.
[0094] For example, for scenario 1 in information 3, the terminal device can measure 4 of the 8 beams in cell A, but can only measure 5 of the 8 beams in cell B, and 3 of the 8 beams in cell C. If you want to use the same beam prediction model (only the measurement results of 4 beams are required as input) for beam prediction in cells A, B, and C, the measurement results of cell A can be used directly, but the measurement results obtained in cell B need to be reduced in data dimension, that is, 4 measurement results are selected from the measurement results of 5 available beams as the input parameters required by the model, and the measurement results obtained in cell C need to be increased in data dimension, that is, the measurement results of 3 available beams are changed to 4 to obtain the input parameters required by the model.
[0095] In another implementation, at least two of information 2, information 3, and information 4 may be defined in combination, and this application does not impose any restrictions on this.
[0096] Information 5: Model-related output parameter type information
[0097] The model-associated output parameter type information indicates the type of output parameter required by the corresponding model. For example, if model 3 is used for beam prediction, the corresponding output parameter types include the index information of the actual unmeasured beam and the predicted signal measurement results of each actual unmeasured beam.
[0098] Information 6: Model-related output parameter format requirements
[0099] The model-associated output parameter format requirement information is used to indicate the format of the output parameters required by the corresponding model. For example, if Model 3 is used for beam prediction, the output parameter can be the beam prediction result for one future moment, or the output parameter can be a set of beam prediction results for multiple future moments. For example, if the model input is a set of three sets of measurement results for four beams obtained at times T-3, T-2, and T-1, the model output can be the measurement results for eight beams at time T, or two sets of measurement results for eight beams at times T and T+1.
[0100] In summary, although the prediction of future beam measurement results is performed (the model output data type is the same), the required output data formats of Model 3 in different application scenarios are different. Therefore, the output parameter format requirements associated with the model are also one of the key information for describing a model.
[0101] Information 7: Model-associated output parameter preprocessing rules
[0102] The output parameter preprocessing rules associated with a model indicate how to reprocess the output data set of the corresponding model. This reprocessing may involve at least one of data dimensionality reduction, data dimensionality increase, redundant elimination, and redistribution. For specific processing methods, see the instructions in Information 4.
[0103] In another implementation, at least two of information 5, information 6, and information 7 may be defined in combination, and this application does not impose any limitation on this.
[0104] Information 8: Application scenario information associated with the model
[0105] The application scenario information associated with the model refers to different usage scenarios under the same functional characteristics. For example, for the model used for positioning, the application scenario can be further subdivided into a line of sight (LoS) scenario, a non-line of sight (NLoS) scenario, or a mixed scenario (including both LoS and NLoS). For another example, for the model used for mobility control, the application scenario can be further subdivided into a ground communication scenario, a non-ground communication scenario (including satellite communication, drone communication, hot air balloon communication and other sub-scenarios), and each scenario can be further divided into high-speed mobile scenarios, medium-speed mobile scenarios, low-speed mobile scenarios and other sub-scenarios, and can also be divided into high-frequency mobility scenarios, low-frequency mobility scenarios and other sub-scenarios. It is also possible to consider a combination of two scenarios, such as a ground communication high-frequency mobility scenario.
[0106] Optionally, information 8 may have a value indicating that the application scenario of the model is all scenarios (i.e., the model is applicable to any scenario corresponding to its associated functional characteristics). For example, for a model used for positioning, assuming that information 8 contains two bits, the value '00' can be used to indicate any scenario, '01' to indicate LoS scenario, '10' to indicate NLoS scenario, and '11' to indicate mixed scenario.
[0107] Information 9: Model-associated deployment location information
[0108] The deployment location information associated with the model includes any of the following meanings: deployed on core network equipment, deployed on application servers, deployed on OAM, deployed on access network equipment, deployed on terminal equipment, or no deployment location restriction.
[0109] Information 10: Capability requirements for using the model
[0110] The capability requirement information for using the model is used to indicate several capability requirements required for using the model. For example, the capability requirement information for using the model includes one or more of the following: the minimum floating-point computing capability required when the model is used, the minimum running memory required when the model is used, the memory size level occupied by the model algorithm data before compilation, the memory size level occupied by the model algorithm data after compilation, the minimum input data rate (or bit rate) required when the model is used, the maximum input data rate (or bit rate) required when the model is used, the minimum output data rate (or bit rate) required when the model is used, and the maximum output data rate (or bit rate) required when the model is used.
[0111] Information 11: Model-related performance monitoring indicator information
[0112] The performance monitoring indicator information associated with the model is used to indicate several indicators for monitoring the model. For example, the performance monitoring indicator information associated with the model may include one or more of the following: average energy consumption of a single inference process, average floating-point calculation amount of a single inference process, average latency of a single inference process, system throughput, system bit error rate, and average data packet transmission latency.
[0113] Information 12: Model-associated location information
[0114] The location information of the model is used to indicate the information related to the provider of the model data, specifically including: the country region information to which the model data belongs and / or the service provider information to which the model data belongs.
[0115] The service provider may be any of the following: OTT (Over The Top, providing application services to users through the Internet) manufacturer information, network operator information (for example, represented by a PLMN identifier), and public website information.
[0116] Information 13: Model-related valid usage scope information (e.g., applicable scenarios, configuration, site information, etc.)
[0117] The valid usage scope information associated with the model is used to indicate the conditions under which the model can be effectively used. For example, the valid usage scope information associated with the model includes one or more of the following: geographical area information allowing valid use, country information allowing valid use, PLMN information allowing valid use, Tracking Area Code (TAC) information allowing valid use, RANAC (RAN Area Code) information allowing valid use, cell information allowing valid use, and configuration information allowing valid use.
[0118] Information 14: Model generalization characteristics information.
[0119] Generalization characteristics reflect the breadth of applicable scenarios for a model. Generally speaking, the higher the generalization characteristics of a model, the more application scenarios it is applicable to. Model generalization characteristics information can include at least one type of model application scenario information (see Information 8 for definition), indicating that the corresponding associated model can be used in the aforementioned application scenarios.
[0120] Information 15: Model version information
[0121] As different parameters in the same application scenario change over time, the algorithm data of the corresponding model may need to be fine-tuned or updated. The updated model is associated with the same application scenario and functions as the original model, but the model algorithm data details differ slightly. Therefore, model algorithm version numbers can be used to distinguish them, facilitating the control and management of similar model algorithms.
[0122] Information 16: Model accuracy level information
[0123] Even for models with the same functionality and application scenario, different design complexities in the model algorithm will result in different inference accuracy. To distinguish between similar models in terms of inference accuracy, the model algorithm's accuracy level can be used to describe the inference accuracy of a given model.
[0124] Information 17: Compilation format information of model data
[0125] Model algorithms are essentially programs written in computer languages. Program file types differ depending on the language platform. Some languages are compatible with each other, while others are not. Therefore, the compilation format of model algorithm data is crucial for describing a model. This information allows model users to understand the required compilation environment. Otherwise, mistakenly using an incompatible language compilation environment will result in the inability to use the corresponding model algorithm.
[0126] Information 18: Storage format information of model data
[0127] This information is used to indicate the format in which the model data is stored, such as zip compression format.
[0128] Information 19: Model computational complexity information
[0129] This information is used to indicate the basic computing power required to use the model, for example, the number of floating-point numbers that need to be calculated per second.
[0130] Information 20: Model complexity information
[0131] This information is used to indicate the complexity of the model, for example: how many layers of neurons the model consists of.
[0132] Information 21: Model size information
[0133] This information is used to indicate the memory size occupied by the model data before or after compilation.
[0134] In an embodiment of the present application, the first information domain and the second information domain may include the same model description information. The specific values of the same model description information of the first information domain and the second information domain may be the same or different. For example, the accuracy of the positioning model associated with the first information domain is less than 10 meters, and the accuracy of the positioning model associated with the second information domain is less than 5 meters. In one embodiment, the association information between the first information domain and its corresponding model description information is predefined. The association relationship between the first information domain and the corresponding model description information can be given in a predefined manner in the protocol. Optionally, in a predefined manner, the model description information associated with the first information domain includes one or more of information 1 to information 21, and the value form of each item of information is a fixed value or a fixed configuration or a value range or a configuration range, and the value forms of different items of information may be the same or different.
[0135] For example, the function of the model corresponding to the model identifier ID2 contained in the first information domain is beam spatial domain prediction. The values of the various information contained in the model description information associated with ID2 are as follows: the functional characteristics associated with ID2 are beam spatial domain prediction; the input parameter types associated with ID2 are 4 beam identifiers and the reference signal measurement results corresponding to each beam identifier; the input parameter format associated with ID2 is required to be the latest acquired single beam measurement result; the input parameter preprocessing rule associated with ID2 is that when the number of beams actually measured is greater than 4, the 4 beams with the highest beam measurement results are selected as model input (and / or when the number of beams actually measured is less than 4, a regression algorithm is used to supplement 4 beams as model input); the output parameter types associated with ID2 are the inferred 8 beam identifiers and the reference signal inference results corresponding to each beam identifier. The output parameter format of the model association is required to be a single beam inference result inferred based on the most recently acquired single beam measurement result; the output parameter preprocessing rule associated with ID2 is to select K (K is a positive integer greater than or equal to 1) beam identifiers from multiple beam measurement results obtained by actual measurement and inference, and report the reference signal measurement / inference results corresponding to each selected beam identifier to the second device; the application scenario associated with ID2 is a wide beam scenario or a narrow beam scenario or a scenario applicable to both wide and narrow beams; the deployment location associated with ID2 is the terminal device side or the network device side; the ability to use the model corresponding to ID2 includes that the computing power of running the beam prediction model cannot be lower than the first threshold, the available memory cannot be lower than the second threshold, and the model training data collection capability is supported. The performance monitoring indicator associated with ID2 is the accuracy of the first M (M is a positive integer greater than or equal to 1) predicted beam measurement results; the place of origin associated with ID2 is the terminal device; the effective usage range information associated with ID2 includes the first configuration or the first geographical location area or the first cell list; the generalization feature of ID2 is that the expected inference accuracy can be achieved in cells deployed at any frequency point on Band A and Band B; the model accuracy level associated with ID2 is 2 (the accuracy range corresponding to each accuracy level is also predefined by the protocol); the model data compilation format associated with ID2 is ONNEX; the model computational complexity associated with ID2 is N (N is a positive number greater than or equal to 1) floating point numbers per second; the model complexity associated with ID2 is L1 to L2 neurons per layer and / or the model does not exceed L3 (L1, L2 and L3 are all positive integers greater than or equal to 1) layers of neurons; the model size associated with ID2 does not exceed W1MB or is W2MB to W3GB.
[0136] According to the above examples, it can be seen that some of the information included in the model description information associated with the first information domain is predefined in the form of fixed values or fixed configuration values, and some information is predefined in the form of a value range or a configuration range. In short, all information is given in a predefined manner.
[0137] In one embodiment, the association between the second information domain and its corresponding model description information is obtained through model testing or testing. The second information domain may include the actual values of the model description information obtained through testing or testing the actual model. The various information contained in the model description information associated with the second information domain may be an example of the various information requirements contained in the model description information associated with the first information domain. For example, if the model size requirement of model A is 100MB to 500MB (a predefined standard value range) based on a query in the first information domain (e.g., ID2), and the size of the model A obtained through actual training is 300MB, then the model A obtained through actual training meets the model description information requirements associated with the first information domain. Otherwise, if the size of the trained model A is 600MB, then although the model is also used for the corresponding function, the standard values of the first information domain cannot be used (in this example, ID2 cannot be used). The values of the various information in the model description information associated with the model obtained through actual training must all meet the predefined value requirements of the various information in the model description information associated with the first information domain. The reason for defining the second information domain is to maintain the flexibility of model implementation under the premise of predefined model requirements.
[0138] In one embodiment, the first information also includes model description information associated with the second information field. The model description information associated with the second information field includes one or more of the aforementioned information 1 to 21. For example, the first model identifier in the first information includes the first information field and the model description information associated with the second information field. For another example, the first model identifier in the first information includes the first information field and the second information field and the model description information associated with the second information field.
[0139] FIG3 is a schematic flow chart of a communication method according to another embodiment of the present application. The method 300 may include at least one feature of the embodiment of the method performed by the first device described above. The method 300 also includes:
[0140] S310: The first device receives second information, where the second information includes test information, and the test information includes one or more test case information.
[0141] In an embodiment of the present application, after the second device receives the first information from the first device, it can generate one or more corresponding test case information based on the first model identifier in the first information, and then send it to the first device through the second information. For example, if the value of the first model identifier represents the CSI model and related requirements, the second device can generate test case information that meets the relevant requirements of the CSI model. After the first device receives the test case information, it can perform model testing based on the test case information. For example, the first device receives test case information that meets the relevant requirements of the CSI model, uses the test case information to test the CSI model and obtain test results. Exemplarily, each test case information may include a set of model input parameter instance value information.
[0142] In one embodiment, as shown in FIG3 , the method further includes:
[0143] S320: The first device sends third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
[0144] In an embodiment of the present application, the test result may include one or more of model output parameter value information, model test success indication information, model test failure indication information, and model test failure reason indication information. The first device may send the test result to the second device via the third information.
[0145] In one embodiment, the method further comprises:
[0146] The first device receives fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
[0147] In some examples, the first message is used to request the second device to use the first information field and / or the second information field in the first model identifier to perform a model control process. After receiving the first message, if the second device refuses to use the information field in the first model identifier, it may send a fourth message including the refusal information to the first device.
[0148] In some examples, after receiving the third information, the second device learns that the model test failed or that the model test result does not meet the requirements of the corresponding model description information (for example, the model accuracy is worse than the model description information requirements), and can send fourth information including rejection information to the first device. In addition, even if the second device learns that the model test succeeded or that the model test result meets the requirements of the corresponding model description information based on the third information, it may still send fourth information including rejection information to the first device.
[0149] After receiving the rejection information from the second device, the first device may end the information interaction process.
[0150] In one embodiment, the fourth information also includes rejection reason information. For example, the rejection reason may include model test results not meeting requirements, the second device not supporting model deployment, the second device not supporting model management, model test failure, or rejection of the first model identifier. The rejection reason information in the fourth information may be a value corresponding to the rejection reason. For example, "model test results not meeting requirements" corresponds to 00, "model test failure" corresponds to 01, "rejection of the first model identifier" corresponds to 10, and other values may also be used.
[0151] In one embodiment, the method further includes: the first device receiving fifth information, the fifth information including acceptance request information and / or a third information field. After receiving the first information or the third information, if the second device determines to use the information field of the first model identifier, it may send the fifth information to the first device. If the fifth information includes acceptance request information, the first device may continue to perform subsequent operations, such as model control processes, based on the acceptance request information. If the fifth information includes the third information field, the first device may update the model identifier based on the third information field.
[0152] In one embodiment, the method further includes: the first device generates a second model identifier based on the third information field. In the embodiment of the present application, the meanings corresponding to the values of the third information field and the second information field may be the same or different. The first device may have saved the second information field before receiving the third information field, or may not have generated or saved the second information field. Based on whether the first device saved the second information field before receiving the third information field, and whether the meanings corresponding to the values of the third information field and the second information field are the same, the second model identifier can be generated in a corresponding manner.
[0153] In one embodiment, the second model identifier is generated in at least one of the following ways:
[0154] Combining the first information field and all or part of the sub-information fields of the third information field to obtain a second model identifier;
[0155] The first information field, the second information field, and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
[0156] In some examples, when the meaning of the third information field is the same as that of the second information field: if the first device has already saved the second information field before receiving the third information field, the received third information field can be used to replace the previously saved second information field, and the second model identifier is obtained by combining the first information field and the third information field; if the first device has not generated or saved the second information field before receiving the third information field, the received third information field can be saved, and the second model identifier is subsequently obtained by combining the first information field and the third information field.
[0157] In some examples, when the meaning of the third information field is different from the meaning of the second information field, a method for generating the second model identifier includes at least one of the following:
[0158] Method 1: If the first device has already stored the second information field before receiving the third information field, it can use all or part of the sub-information fields of the received third information field to replace the previously stored second information field, and the second model identifier is obtained by combining the first information field and all or part of the sub-information fields of the third information field.
[0159] Method 2: If the first device already has the second information field stored before receiving the third information field, it can use all or part of the sub-information fields of the received third information field as a supplement to the first model identifier. For example, the second model identifier can be obtained by combining the first information field, the second information field, and all or part of the sub-information fields of the third information field.
[0160] Method 3: If the first device has not generated or stored the second information field before receiving the third information field, it can store the received third information field and use all or part of the sub-information fields of the third information field as a supplement to the first model identifier. For example, the second model identifier can be generated by combining the first information field with all or part of the sub-information fields of the third information field.
[0161] The aforementioned partial sub-information field may include one or more sub-information fields included in the third information field.
[0162] In one embodiment, the second information field and / or the third information field includes one or more of the following sub-information field information:
[0163] Model-associated operator information, model-associated terminal device manufacturer information, model-associated model provider or manufacturer information, model-associated chip manufacturer information, model-associated network device manufacturer information, model version number information, and model-associated temporary identification information.
[0164] In an embodiment of the present application, the second information domain may be a meaning-variable model identifier and / or a custom model identifier. For example, the meaning-variable model identifier may include one or more of the above-mentioned sub-information domain information, or may include other information. The sub-information domain information included in the second information domain and the third information domain may be the same, partially the same, or different. For example, the second information domain includes operator information associated with the model and terminal device manufacturer information associated with the model, and the third information domain includes terminal device manufacturer information associated with the model and model provider or manufacturer information associated with the model.
[0165] FIG4 is a schematic flow chart of a communication method according to another embodiment of the present application. The method 400 may include at least one feature of the method embodiment performed by the first device described above. The method 400 also includes:
[0166] S410. The first device sends sixth information, where the sixth information is used for a model control process. The sixth information includes one or more of the following information: a first model identifier, a second information field, a second model identifier, and one or more sub-information fields of the third information field.
[0167] In an embodiment of the present application, a first device may send sixth information to a second device, and the sixth information may be used in a model control process of the second device. For example, if the sixth information includes a first model identifier, the model control process may be executed on the model corresponding to the first model identifier. If the sixth information includes a second information field, the model control process may be executed on the model corresponding to the second information field. If the sixth information includes a second model identifier, the model control process may be executed on the model corresponding to the second model identifier. If the sixth information includes a sub-information field of a third information field, the model control process may be executed on the model corresponding to the sub-information field of the third information field.
[0168] In one embodiment, as shown in FIG4 , the method further includes:
[0169] S420. The first device receives seventh information, where the seventh information is used in the model control process. The seventh information includes one or more of the following: a first model identifier, a second information field, a second model identifier, and one or more sub-information fields of the third information field. In this embodiment of the present application, the first device may receive the seventh information from the second device, where the seventh information may be used in the model control process of the first device. For examples, see the description of the sixth information.
[0170] In one embodiment, the model control process includes one or more of the following:
[0171] Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
[0172] In an embodiment of the present application, the sixth information and / or the seventh information may include information fields for indicating various model control processes. The sixth information and / or the seventh information itself may also represent a certain model control process. For example, a control bit in the sixth information is 0 to indicate model activation, and 1 to indicate model deactivation. For another example, the two control bits in the sixth information are 00 to indicate model selection, 01 to indicate model activation, 10 to indicate model deactivation, and 11 to indicate model switching. For another example, the function of the sixth information is model monitoring, and the function of the seventh information is model-related capability interaction. The meanings corresponding to the above values and the functions corresponding to the information are merely examples and not limitations, and can be flexibly set according to actual needs.
[0173] FIG5 is a schematic flow chart of a communication method according to another embodiment of the present application. The method 500 may include at least one feature of the method embodiment performed by the first device described above. The method 500 also includes:
[0174] S510: The first device receives eighth information, where the eighth information includes one or more first information fields.
[0175] In an embodiment of the present application, the second device can inform the first device through the eighth information which model description information associated with the models deployed by the first device needs to be synchronized with the second device. For example, the first device has models M1, M2, M3, and M4 deployed. If the eighth information includes a first information field for representing models M1 and M2, the first device needs to synchronize the model description information associated with models M1 and M2 with the second device.
[0176] In one embodiment, the eighth information is used to indicate to the first device that model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
[0177] In one embodiment, as shown in FIG5 , the method further includes:
[0178] S520: The first device sends ninth information, where the ninth information includes one or more first information fields.
[0179] In one embodiment, the ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
[0180] In an embodiment of the present application, the first device can inform the second device through the ninth information which models deployed by the first device and associated model description information can be synchronized with the second device. For example, the first device deploys models M1, M2, M3, and M4. If the ninth information includes the first information field associated with models M1, M2, M3, and M4, the first device can synchronize the model description information associated with models M1, M2, M3, and M4 with the second device.
[0181] In the embodiment of the present application, the order of the eighth information and the ninth information is not limited. The first device may receive the eighth information first, or may send the ninth information first. For example, the first device may first send the ninth information to the second device to inform the second device of the range of models that the first device supports synchronization; and then receive the eighth information from the second device to obtain the model that the second device actually needs to synchronize. For example, the first device may first send the ninth information including the first information field associated with models M1, M2, and M3 to the second device, and then receive the eighth information including the first information field associated with model M2 from the second device.
[0182] In an embodiment of the present application, the first device may determine the model type range of information interaction by interacting with the second device via the eighth information and / or the ninth information before or after receiving the first information.
[0183] In one embodiment, as shown in FIG5 , the method further includes:
[0184] S530: The first device sends tenth information, where the tenth information includes one or more first information fields.
[0185] In one embodiment, the tenth information is used to indicate a first information domain associated with a model that has been saved or deployed by the first device and / or a first information domain associated with a model that has not been saved or deployed by the first device.
[0186] In an embodiment of the present application, one or more models may be stored or deployed in the first device. For example, models M1, M2, M3, and M4 may be deployed in the first device. The first device may proactively report to the second device the first information domain associated with the models M1, M2, M3, and M4 deployed in the first device. For another example, models M5, M6, and M7 may not be stored in the first device. The first device may proactively report to the second device the first information domain associated with the models M5, M6, and M7 that are not stored in the first device.
[0187] In one embodiment, as shown in FIG5 , the method further includes:
[0188] S540: The first device receives eleventh information, where the eleventh information includes one or more first information fields.
[0189] In one embodiment, the eleventh information is used to query the model stored and / or deployed by the first device.
[0190] In an embodiment of the present application, the status of models stored and / or deployed by the first device can be reported based on a query request from the second device. For example, the query request received by the first device from the second device is the eleventh message for querying the status of models stored and / or deployed by the first device. After receiving the eleventh message, the first device can send the tenth message to the second device based on the eleventh message to inform the second device.
[0191] In the embodiments of the present application, any two or more of the eighth information, the ninth information, the tenth information, and the eleventh information may be used in conjunction with each other. For example, the first device first sends the tenth information to the second device, and then receives the ninth information and / or the eleventh information returned by the second device. For another example, the first device first receives the eleventh information sent by the second device, and then sends the eighth information and / or the tenth information to the second device. For another example, the first device first receives the eleventh information sent by the second device, then sends the tenth information to the second device, then sends the ninth information to the second device, and then receives the eighth information sent by the second device.
[0192] In an embodiment of the present application, the first device may exchange one or more of the eighth information, the ninth information, the tenth information, and the eleventh information with the second device. The first device may also exchange one or more of the eighth information, the ninth information, the tenth information, and the eleventh information with other devices other than the second device. For example, after receiving the ninth information from the third device, the first device may send the first information to the second device.
[0193] In one embodiment, as shown in FIG5 , the method further includes:
[0194] S550: The first device receives twelfth information, where the twelfth information includes capabilities related to the second device. In this embodiment of the present application, the first device may receive the twelfth information from the second device, thereby acquiring capabilities related to the second device. The capabilities related to the second device may be model-related capabilities.
[0195] In one embodiment, the capabilities related to the second device include one or more of the following:
[0196] Whether the model registration process is supported;
[0197] Whether the information synchronization process of model description information is supported;
[0198] Whether the model control process is supported;
[0199] Whether to support the model information query process.
[0200] For example, if the capability related to the second device included in the twelfth information is that the second device supports the model registration process, then other information such as the sixth information can be used to instruct the second device to perform the model registration process. If the capability related to the second device included in the twelfth information is that the second device does not support the model registration process, then the second device does not perform the model registration process. Examples of other capabilities of the second device are similar and are not given here for brevity.
[0201] In one embodiment, as shown in FIG5 , the method further includes:
[0202] S560: The first device sends thirteenth information, where the thirteenth information includes capabilities related to the first device. In an embodiment of the present application, the first device may send the thirteenth information to the second device, thereby informing the second device of the capabilities related to the first device. The capabilities related to the first device may be capabilities related to the model.
[0203] In one embodiment, the capabilities related to the first device include one or more of the following:
[0204] Whether the model registration process is supported;
[0205] Whether the information synchronization process of model description information is supported;
[0206] Whether the model control process is supported;
[0207] Whether to support the model information query process.
[0208] For example, if the capability related to the first device included in the thirteenth information is that the first device supports the model registration process, then other information such as the seventh information can be used to instruct the first device to perform the model registration process. If the capability related to the second device included in the thirteenth information is that the second device does not support the model registration process, then the first device does not perform the model registration process. Examples of other capabilities of the first device are similar and are not given here for brevity.
[0209] In the embodiment of the present application, the first device may exchange the twelfth information and / or the thirteenth information with the second device before or after sending the first information, or may exchange the twelfth information and / or the thirteenth information with the second device after sending the first information. Of course, the present application does not limit the order in which the twelfth information and / or the thirteenth information are sent with the other information in Figure 5. Figure 5 is only one example.
[0210] Any information involved in the embodiments of the present application, such as any information from the first information to the thirteenth information, can be carried by any of the following message types:
[0211] Long Term Evolution Positioning Protocol (LPP) message, Non-Access Stratum (NAS) message, Radio Resource Control (RRC) message, Media Access Control Control Element (MAC CE) message, Downlink Control Information (DCI) message, Uplink Control Information (UCI) message, Physical Uplink Control Channel (PUCCH) message, Physical Uplink Shared Channel (PUSCH) message, Inter-node message, Xn interface message, F1 interface message, E1 interface message, NG interface message, core network service architecture-based message or AI-specific message.
[0212] Any information involved in the embodiments of the present application, such as any information from the first information to the thirteenth information, can be carried by any of the following message types: unicast message, multicast message or broadcast message.
[0213] In some examples, unicast message (one-to-one): the source transmits the unicast message through a unicast channel. Only the terminal device or network device allocated with the corresponding unicast resource can attempt to receive the unicast message. The unicast message can also be called dedicated signaling.
[0214] In some examples, multicast messages (one-to-many): the source transmits the multicast message through the multicast channel. Terminal devices or network devices that are group members within the coverage area of the multicast signal can attempt to receive the multicast message. When a terminal device or network device joins a group, it obtains multicast channel-related resources.
[0215] In some examples, broadcast message (one-to-any): the source transmits the broadcast message through the broadcast channel, and any terminal device or network device within the coverage of the broadcast signal can attempt to receive the broadcast message.
[0216] FIG6 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 600 can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.
[0217] S610: A second device receives first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0218] In one embodiment, the first information field includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
[0219] In one embodiment, the second information field includes a meaning-variable model identifier and / or a custom model identifier.
[0220] In one embodiment, the first information field and / or the second information field has associated model description information.
[0221] In one embodiment, the model description information includes one or more of the following information:
[0222] Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of the input parameters associated with the model, preprocessing rules for input parameters associated with the model, information on the types of output parameters associated with the model, information on the format requirements of the output parameters associated with the model, preprocessing rules for output parameters associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization feature information of the model, version information of the model, accuracy level information of the model, compilation format information of the model data, storage format information of the model data, computational complexity information of the model, complexity information of the model, and size information of the model.
[0223] In one embodiment, the association information between the first information field and its corresponding model description information is predefined.
[0224] In one embodiment, the association information between the second information field and its corresponding model description information is obtained through model detection or testing.
[0225] In one embodiment, the first information further includes model description information associated with the second information field.
[0226] FIG7 is a schematic flow chart of a communication method according to another embodiment of the present application. The method 700 may include at least one feature of the embodiment of the method performed by the second device described above. The method 700 also includes:
[0227] S710: The second device sends second information, where the second information includes test information, and the test information includes one or more test case information.
[0228] In one embodiment, as shown in FIG7 , the method further includes:
[0229] S720: The second device receives third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
[0230] In one embodiment, the method further comprises:
[0231] The second device sends fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
[0232] In one embodiment, the fourth information further includes rejection reason information.
[0233] In one embodiment, the method further comprises:
[0234] The second device sends fifth information, where the fifth information includes acceptance request information and / or a third information field.
[0235] In one embodiment, the method further includes: generating a second model identifier based on the third information field.
[0236] In one embodiment, the second model identifier is generated in at least one of the following ways:
[0237] Combining the first information field and all or part of the sub-information fields of the third information field to obtain a second model identifier;
[0238] The first information field, the second information field, and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
[0239] In one embodiment, the second information field and / or the third information field includes one or more of the following sub-information field information:
[0240] Model-associated operator information, model-associated terminal device manufacturer information, model-associated model provider or manufacturer information, model-associated chip manufacturer information, model-associated network device manufacturer information, model version number information, and model-associated temporary identification information.
[0241] FIG8 is a schematic flow chart of a communication method according to another embodiment of the present application. The method 800 may include at least one feature of the embodiment of the method performed by the second device described above. The method 800 also includes:
[0242] S810. The second device receives sixth information, where the sixth information is used for a model control process. The sixth information includes one or more of the following information: a first model identifier, a second information field, the second model identifier, and one or more sub-information fields of the third information field.
[0243] In one embodiment, as shown in FIG8 , the method further includes:
[0244] S820. The second device sends seventh information, where the seventh information is used for the model control process. The seventh information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-information fields of the third information field.
[0245] In one embodiment, the model control process includes one or more of the following:
[0246] Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
[0247] FIG9 is a schematic flow chart of a communication method according to another embodiment of the present application. The method 900 may include at least one feature of the embodiment of the method performed by the second device described above. The method further includes:
[0248] S910: The second device sends eighth information, where the eighth information includes one or more first information fields.
[0249] In one embodiment, the eighth information is used to indicate to the first device that model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
[0250] In one embodiment, as shown in FIG9 , the method further includes:
[0251] S920: The second device receives ninth information, where the ninth information includes one or more first information fields.
[0252] In one embodiment, the ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
[0253] In one embodiment, as shown in FIG9 , the method further includes:
[0254] S930: The second device receives tenth information, where the tenth information includes one or more first information fields.
[0255] In one embodiment, the tenth information is used to indicate a first information domain associated with a model that has been saved or deployed by the first device and / or a first information domain associated with a model that has not been saved or deployed by the first device.
[0256] In one embodiment, as shown in FIG9 , the method further includes:
[0257] S940: The second device sends eleventh information, where the eleventh information includes one or more first information fields.
[0258] In one embodiment, the eleventh information is used to query the model stored and / or deployed by the first device.
[0259] In one embodiment, as shown in FIG9 , the method further includes:
[0260] S950: The second device sends twelfth information, where the twelfth information includes capabilities related to the second device.
[0261] In one embodiment, the capabilities related to the second device include one or more of the following:
[0262] Whether the model registration process is supported;
[0263] Whether the information synchronization process of model description information is supported;
[0264] Whether the model control process is supported;
[0265] Whether to support the model information query process.
[0266] In one embodiment, as shown in FIG9 , the method further includes:
[0267] S960: The second device receives thirteenth information, where the thirteenth information includes capabilities related to the first device.
[0268] In one embodiment, the capabilities related to the first device include one or more of the following:
[0269] Whether the model registration process is supported;
[0270] Whether the information synchronization process of model description information is supported;
[0271] Whether the model control process is supported;
[0272] Whether to support the model information query process.
[0273] In one embodiment, the second device is a terminal device or a network device.
[0274] For specific examples of the second device executing the communication methods 600, 700, 800, and 900 of this embodiment, reference can be made to the relevant descriptions about the second device in the above-mentioned communication methods 200, 300, 400, and 500, which will not be repeated here for the sake of brevity.
[0275] Figure 10 is a schematic block diagram of a first device 1000 according to an embodiment of the present application. The first device 1000 may include: a first sending unit 1001, configured to send first information, the first information including a first model identifier including a first information field and / or a second information field.
[0276] In one embodiment, the first information field includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
[0277] In one embodiment, the second information field includes a meaning-variable model identifier and / or a custom model identifier.
[0278] In one embodiment, the first information field and / or the second information field has associated model description information.
[0279] In one embodiment, the model description information includes one or more of the following information:
[0280] Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of the input parameters associated with the model, preprocessing rules for input parameters associated with the model, information on the types of output parameters associated with the model, information on the format requirements of the output parameters associated with the model, preprocessing rules for output parameters associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization feature information of the model, version information of the model, accuracy level information of the model, compilation format information of the model data, storage format information of the model data, computational complexity information of the model, complexity information of the model, and size information of the model.
[0281] In one embodiment, the association information between the first information field and its corresponding model description information is predefined.
[0282] In one embodiment, the association information between the second information field and its corresponding model description information is obtained through model detection or testing.
[0283] In one embodiment, the first information further includes model description information associated with the second information field.
[0284] In one embodiment, as shown in FIG11 , the first device 1100 further includes: a first receiving unit 1101 , configured for the first device to receive second information, where the second information includes test information, and the test information includes one or more test case information.
[0285] In one implementation, the first device further includes: a second sending unit 1102, configured to send third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
[0286] In one implementation, the first device further includes: a second receiving unit 1103, configured to receive fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
[0287] In one embodiment, the fourth information further includes rejection reason information.
[0288] In one implementation, the first device further includes: a third receiving unit 1104, configured to receive fifth information, where the fifth information includes acceptance request information and / or a third information field.
[0289] In one embodiment, the first device further includes: a processing unit 1105, configured to generate a second model identifier based on the third information field.
[0290] In one embodiment, the second model identifier is generated in at least one of the following ways:
[0291] Combining the first information field and all or part of the sub-information fields of the third information field to obtain a second model identifier;
[0292] The first information field, the second information field, and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
[0293] In one embodiment, the second information field and / or the third information field includes one or more of the following sub-information field information:
[0294] Model-associated operator information, model-associated terminal device manufacturer information, model-associated model provider or manufacturer information, model-associated chip manufacturer information, model-associated network device manufacturer information, model version number information, and model-associated temporary identification information.
[0295] In one embodiment, the first device also includes: a third sending unit 1106, used to send sixth information, the sixth information is used for the model control process, and the sixth information includes one or more of the following information: the first model identifier, the second information field, the second model identifier and one or more sub-information fields of the third information field.
[0296] In one embodiment, the first device also includes: a fourth receiving unit 1107, used to receive seventh information, the seventh information is used for the model control process, and the seventh information includes one or more of the following information: a first model identifier, a second information domain, a second model identifier, and one or more sub-information domains of the third information domain.
[0297] In one embodiment, the model control process includes one or more of the following:
[0298] Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
[0299] In one implementation, the first device further includes: a fifth receiving unit 1108, configured to receive eighth information, where the eighth information includes one or more first information fields.
[0300] In one embodiment, the eighth information is used to indicate to the first device that model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
[0301] In one implementation, the first device further includes: a fourth sending unit 1109, configured to send ninth information, where the ninth information includes one or more first information fields.
[0302] In one embodiment, the ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
[0303] In one implementation, the first device further includes: a fifth sending unit 1110, configured to send tenth information, where the tenth information includes one or more first information fields.
[0304] In one embodiment, the tenth information is used to indicate a first information domain associated with a model that has been saved or deployed by the first device and / or a first information domain associated with a model that has not been saved or deployed by the first device.
[0305] In one implementation, the first device further includes: a sixth receiving unit 1111, configured to receive eleventh information, where the eleventh information includes one or more of the first information fields.
[0306] In one embodiment, the eleventh information is used to query the model stored and / or deployed by the first device.
[0307] In one implementation, the first device further includes: a seventh receiving unit 1112, configured to receive twelfth information, where the twelfth information includes capabilities related to the second device.
[0308] In one embodiment, the capabilities related to the second device include one or more of the following:
[0309] Whether the model registration process is supported;
[0310] Whether the information synchronization process of model description information is supported;
[0311] Whether the model control process is supported;
[0312] Whether to support the model information query process.
[0313] In one implementation, the first device further includes: a sixth sending unit 1113, configured to send thirteenth information, where the thirteenth information includes capabilities related to the first device.
[0314] In one embodiment, the capabilities related to the first device include one or more of the following:
[0315] Whether the model registration process is supported;
[0316] Whether the information synchronization process of model description information is supported;
[0317] Whether the model control process is supported;
[0318] Whether to support the model information query process.
[0319] In one embodiment, the first device is a terminal device or a network device.
[0320] The first devices 1000 and 1100 of the embodiments of the present application can implement the corresponding functions of the first device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first devices 1000 and 1100 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first device of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).
[0321] Figure 12 is a schematic block diagram of a second device 1200 according to an embodiment of the present application. The second device 1200 may include: a first receiving unit 1201, configured to receive first information, the first information including a first model identifier including a first information field and / or a second information field.
[0322] In one embodiment, the first information field includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
[0323] In one embodiment, the second information field includes a meaning-variable model identifier and / or a custom model identifier.
[0324] In one embodiment, the first information field and / or the second information field has associated model description information.
[0325] In one embodiment, the model description information includes one or more of the following information:
[0326] Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of the input parameters associated with the model, preprocessing rules for input parameters associated with the model, information on the types of output parameters associated with the model, information on the format requirements of the output parameters associated with the model, preprocessing rules for output parameters associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization feature information of the model, version information of the model, accuracy level information of the model, compilation format information of the model data, storage format information of the model data, computational complexity information of the model, complexity information of the model, and size information of the model.
[0327] In one embodiment, the association information between the first information field and its corresponding model description information is predefined.
[0328] In one embodiment, the association information between the second information field and its corresponding model description information is obtained through model detection or testing.
[0329] In one embodiment, the first information further includes model description information associated with the second information field.
[0330] In one implementation, the second device 1300 further includes: a first sending unit 1301, configured to send second information, where the second information includes test information, and the test information includes one or more test case information.
[0331] In one embodiment, the second device further includes: a second receiving unit 1302, configured to receive third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
[0332] In one implementation, the second device further includes: a second sending unit 1303, configured to send fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
[0333] In one embodiment, the fourth information further includes rejection reason information.
[0334] In one implementation, the second device further includes: a third sending unit 1304, configured to send fifth information, where the fifth information includes acceptance request information and / or a third information field.
[0335] In one implementation, the second device further includes: a processing unit 1305, configured to generate a second model identifier based on the third information field.
[0336] In one embodiment, the second model identifier is generated in at least one of the following ways:
[0337] Combining the first information field and all or part of the sub-information fields of the third information field to obtain a second model identifier;
[0338] The first information field, the second information field, and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
[0339] In one embodiment, the second information domain and / or the third information domain includes one or more of the following sub-information domain information: model-associated operator information, model-associated terminal device manufacturer information, model-associated model provider or manufacturer information, model-associated chip manufacturer information, model-associated network device manufacturer information, model version number information, and model-associated temporary identification information.
[0340] In one embodiment, the second device also includes: a third receiving unit 1306, used to receive sixth information, the sixth information is used for the model control process, and the sixth information includes one or more of the following information: a first model identifier, a second information field, a second model identifier, and one or more sub-information fields of the third information field.
[0341] In one embodiment, the second device also includes: a fourth sending unit 1307, used to send seventh information, the seventh information is used for the model control process, and the seventh information includes one or more of the following information: a first model identifier, a second information field, a second model identifier, and one or more sub-information fields of the third information field.
[0342] In one embodiment, the model control process includes one or more of the following:
[0343] Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
[0344] In one embodiment, the second device further includes:
[0345] The fifth sending unit 1308 is configured to send eighth information, where the eighth information includes one or more first information fields.
[0346] In one embodiment, the eighth information is used to indicate to the first device that model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
[0347] In one embodiment, the second device further includes:
[0348] The fourth receiving unit 1309 is configured to receive ninth information, where the ninth information includes one or more first information fields.
[0349] In one embodiment, the ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
[0350] In one embodiment, the second device further includes:
[0351] The fifth receiving unit 1310 is configured to receive tenth information, where the tenth information includes one or more first information fields.
[0352] In one embodiment, the tenth information is used to indicate a first information domain associated with a model that has been saved or deployed by the first device and / or a first information domain associated with a model that has not been saved or deployed by the first device.
[0353] In one implementation, the second device further includes: a sixth sending unit 1311, configured to send eleventh information, where the eleventh information includes one or more of the first information fields.
[0354] In one embodiment, the eleventh information is used to query the model stored and / or deployed by the first device.
[0355] In one embodiment, the second device further includes:
[0356] The seventh sending unit 1312 is configured to send twelfth information, where the twelfth information includes capabilities related to the second device.
[0357] In one embodiment, the capabilities related to the second device include one or more of the following:
[0358] Whether the model registration process is supported;
[0359] Whether the information synchronization process of model description information is supported;
[0360] Whether the model control process is supported;
[0361] Whether to support the model information query process.
[0362] In one embodiment, the second device further includes:
[0363] The sixth receiving unit 1313 is configured to receive thirteenth information, where the thirteenth information includes capabilities related to the first device.
[0364] In one embodiment, the capabilities related to the first device include one or more of the following:
[0365] Whether the model registration process is supported;
[0366] Whether the information synchronization process of model description information is supported;
[0367] Whether the model control process is supported;
[0368] Whether to support the model information query process.
[0369] In one embodiment, the second device is a terminal device or a network device.
[0370] The second devices 1200 and 1300 of the embodiments of the present application can implement the corresponding functions of the second device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second device can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described by the various modules (sub-modules, units or components, etc.) in the second device of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).
[0371] The communication method of the embodiment of the present application may be a method for managing model identification, and this method may produce at least one of the following beneficial effects:
[0372] This approach combines the universality of a globally unique model identifier with the control flexibility of a variable model identifier, making the control process based on model identifiers more flexible. For example, you can use a globally unique model identifier alone, a variable model identifier alone, or a combination of the two.
[0373] This approach balances the universality of globally unique model identifiers with the control flexibility of variable model identifiers, allowing for the fine-grained management of different model implementation versions using the same globally unique model identifier. While retaining model implementation flexibility, it also manages the reliability of each model implementation version, avoiding the coarse-grained management issues associated with using only globally unique model identifiers and improving the controllability of the communication system.
[0374] The model description information of different model implementation versions using the same globally unique model identifier is aligned, making it easier for the model control end (for example, the second device) to control and manage the corresponding model based on the aligned model description information.
[0375] Figure 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application. The communication device 1400 includes a processor 1410, which can call and execute a computer program from a memory to enable the communication device 1400 to implement the method in the embodiment of the present application.
[0376] In one embodiment, the communication device 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to enable the communication device 1400 to implement the method in the embodiment of the present application.
[0377] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .
[0378] In one embodiment, the communication device 1400 may further include a transceiver 1430 , and the processor 1410 may control the transceiver 1430 to communicate with other devices. Specifically, the transceiver 1430 may send information or data to other devices, or receive information or data sent by other devices.
[0379] The transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include an antenna, and the number of antennas may be one or more.
[0380] In one embodiment, the communication device 1400 may be the first device of the embodiment of the present application, and the communication device 1400 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0381] In one embodiment, the communication device 1400 may be the second device of the embodiment of the present application, and the communication device 1400 may implement the corresponding processes implemented by the second device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0382] 15 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application. The chip 1500 includes a processor 1510, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.
[0383] In one embodiment, the chip 1500 may further include a memory 1520. The processor 1510 may call and execute a computer program from the memory 1520 to implement the method performed by the first device or the second device in the embodiment of the present application.
[0384] The memory 1520 may be a separate device independent of the processor 1510 , or may be integrated into the processor 1510 .
[0385] In one embodiment, the chip 1500 may further include an input interface 1530. The processor 1510 may control the input interface 1530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0386] In one embodiment, the chip 1500 may further include an output interface 1540. The processor 1510 may control the output interface 1540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0387] In one embodiment, the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.
[0388] In one embodiment, the chip can be applied to the second device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0389] The chips used in the first device and the second device may be the same chip or different chips.
[0390] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0391] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.
[0392] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).
[0393] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.
[0394] FIG16 is a schematic block diagram of a communication system 1600 according to an embodiment of the present application. The communication system 1600 includes a first device 1610 and a second device 1620 .
[0395] The first device 1610 is configured to send first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
[0396] The second device 1620 is configured to receive the first information.
[0397] The first device 1610 can be used to implement the corresponding functions implemented by the first device in the above method, and the second device 1620 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, they are not described here in detail.
[0398] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0399] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0400] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0401] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.
Claims
1. A communication method, comprising: The first device sends first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
2. The method according to claim 1, wherein: The first information domain includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
3. The method according to claim 1 or 2, wherein: The second information field includes a meaning-variable model identifier and / or a user-defined model identifier.
4. The method according to any one of claims 1 to 3, wherein: The first information field and / or the second information field has associated model description information.
5. The method according to claim 4, wherein: The model description information includes one or more of the following information: Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of input parameters associated with the model, input parameter preprocessing rules associated with the model, information on the types of output parameters associated with the model, information on the format requirements of output parameters associated with the model, output parameter preprocessing rules associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization characteristic information of the model, version information of the model, accuracy level information of the model, compilation format information of model data, storage format information of model data, computational complexity information of the model, complexity information of the model, and size information of the model.
6. The method according to any one of claims 1 to 5, wherein: The association information between the first information field and its corresponding model description information is predefined.
7. The method according to any one of claims 1 to 6, wherein: The association information between the second information field and its corresponding model description information is obtained through model detection or testing.
8. The method according to any one of claims 1 to 7, wherein: The first information also includes model description information associated with the second information field.
9. The method according to any one of claims 1 to 8, wherein: The method further comprises: The first device receives second information, where the second information includes test information, and the test information includes one or more test case information.
10. The method according to claim 9, wherein: The method further comprises: The first device sends third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
11. The method according to any one of claims 1 to 10, wherein: The method further comprises: The first device receives fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
12. The method according to claim 11, wherein: The fourth information also includes rejection reason information.
13. The method according to any one of claims 1 to 12, wherein: The method further comprises: The first device receives fifth information, where the fifth information includes acceptance request information and / or a third information field.
14. The method according to claim 13, wherein: The method further comprises: The first device generates a second model identifier based on the third information field.
15. The method according to claim 14, wherein: The manner in which the first device generates the second model identifier based on the third information field includes at least one of the following: Combining all or part of the sub-information fields of the first information field and the third information field to obtain a second model identifier; The first information field, the second information field and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
16. The method according to any one of claims 1 to 15, wherein: The second information field and / or the third information field includes one or more of the following sub-information field information: The operator information associated with the model, the terminal device manufacturer information associated with the model, the model provider or manufacturer information associated with the model, the chip manufacturer information associated with the model, the network equipment manufacturer information associated with the model, the version number information of the model, and the temporary identification information associated with the model.
17. The method according to any one of claims 1 to 16, wherein: The method further comprises: The first device sends sixth information, where the sixth information is used for a model control process, and the sixth information includes one or more of the following information: the first model identifier, the second information field, a second model identifier, and one or more sub-information fields of the third information field.
18. The method according to any one of claims 1 to 17, wherein: The method further comprises: The first device receives seventh information, the seventh information is used for the model control process, and the seventh information includes one of the following information One or more of: the first model identifier, the second information field, the second model identifier and one or more sub-information fields of the third information field.
19. The method according to claim 17 or 18, wherein: The model control process includes one or more of the following: Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
20. The method according to any one of claims 1 to 19, wherein: The method further comprises: The first device receives eighth information, where the eighth information includes one or more first information fields.
21. The method according to claim 20, wherein: The eighth information is used to indicate to the first device that the model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
22. The method according to any one of claims 1 to 21, wherein: The method further comprises: The first device sends ninth information, where the ninth information includes one or more first information fields.
23. The method according to claim 22, wherein: The ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
24. The method according to any one of claims 1 to 23, wherein: The method further comprises: The first device sends tenth information, where the tenth information includes one or more first information fields.
25. The method according to claim 24, wherein: The tenth information is used to indicate the first information domain associated with the model that has been saved or deployed by the first device and / or the first information domain associated with the model that has not been saved or deployed by the first device.
26. The method according to any one of claims 1 to 25, wherein: The method further comprises: The first device receives eleventh information, where the eleventh information includes one or more of the first information fields.
27. The method according to claim 26, wherein: The eleventh information is used to query the model status saved and / or deployed by the first device.
28. The method according to any one of claims 1 to 27, wherein: The method further comprises: The first device receives twelfth information, where the twelfth information includes capabilities related to the second device.
29. The method according to claim 28, wherein: The capabilities related to the second device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
30. The method according to any one of claims 1 to 29, wherein: The method further comprises: The first device sends thirteenth information, where the thirteenth information includes capabilities related to the first device.
31. The method according to claim 30, wherein: The capabilities related to the first device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
32. The method according to any one of claims 1 to 31, wherein: The first device is a terminal device or a network device.
33. A communication method, comprising: The second device receives first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
34. The method of claim 33, wherein: The first information domain includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
35. The method according to claim 33 or 34, wherein: The second information field includes a meaning-variable model identifier and / or a user-defined model identifier.
36. A method according to any one of claims 33 to 35, wherein: The first information field and / or the second information field has associated model description information.
37. The method of claim 36, wherein: The model description information includes one or more of the following information: Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of input parameters associated with the model, input parameter preprocessing rules associated with the model, information on the types of output parameters associated with the model, information on the format requirements of output parameters associated with the model, output parameter preprocessing rules associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization characteristic information of the model, version information of the model, accuracy level information of the model, compilation format information of model data, storage format information of model data, computational complexity information of the model, complexity information of the model, and size information of the model.
38. A method according to any one of claims 33 to 37, wherein: The association information between the first information field and its corresponding model description information is predefined.
39. The method according to any one of claims 33 to 38, wherein: The association information between the second information field and its corresponding model description information is obtained through model detection or testing.
40. The method according to any one of claims 33 to 39, wherein: The first information also includes model description information associated with the second information field.
41. A method according to any one of claims 33 to 40, wherein: The method further comprises: The second device sends second information, where the second information includes test information, and the test information includes one or more test case information.
42. The method of claim 41, wherein: The method further comprises: The second device receives third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
43. The method according to any one of claims 33 to 42, wherein: The method further comprises: The second device sends fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
44. The method of claim 43, wherein: The fourth information also includes rejection reason information.
45. The method according to any one of claims 33 to 44, wherein: The method further comprises: The second device sends fifth information, where the fifth information includes acceptance request information and / or a third information field.
46. The method of claim 45, wherein: The method further includes: the second device generating a second model identifier based on the third information domain.
47. The method of claim 46, wherein: The second model identifier is generated in at least one of the following ways: Combining all or part of the sub-information fields of the first information field and the third information field to obtain a second model identifier; The first information field, the second information field and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
48. A method according to any one of claims 33 to 47, wherein: The second information field and / or the third information field includes one or more of the following sub-information field information: The operator information associated with the model, the terminal device manufacturer information associated with the model, the model provider or manufacturer information associated with the model, the chip manufacturer information associated with the model, the network equipment manufacturer information associated with the model, the version number information of the model, and the temporary identification information associated with the model.
49. The method according to any one of claims 33 to 48, wherein: The method further comprises: The second device receives sixth information, where the sixth information is used for a model control process, and the sixth information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-information fields of the third information field.
50. The method according to any one of claims 33 to 49, wherein: The method further comprises: The second device sends seventh information, where the seventh information is used for a model control process, and the seventh information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-information fields of the third information field.
51. The method of claim 49 or 50, wherein: The model control process includes one or more of the following: Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
52. A method according to any one of claims 33 to 51, wherein: The method further comprises: The second device sends eighth information, where the eighth information includes one or more first information fields.
53. The method of claim 52, wherein: The eighth information is used to indicate to the first device that the model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
54. The method according to any one of claims 33 to 53, wherein: The method further comprises: The second device receives ninth information, where the ninth information includes one or more first information fields.
55. The method of claim 54, wherein: The ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
56. The method according to any one of claims 33 to 55, wherein: The method further comprises: The second device receives tenth information, where the tenth information includes one or more first information fields.
57. The method of claim 56, wherein: The tenth information is used to indicate the first information domain associated with the model that has been saved or deployed by the first device and / or the first information domain associated with the model that has not been saved or deployed by the first device.
58. The method according to any one of claims 33 to 57, wherein: The method further comprises: The second device sends eleventh information, where the eleventh information includes one or more of the first information fields.
59. The method of claim 58, wherein: The eleventh information is used to query the model status saved and / or deployed by the first device.
60. The method according to any one of claims 33 to 59, wherein: The method further comprises: The second device sends twelfth information, where the twelfth information includes capabilities related to the second device.
61. The method of claim 60, wherein: The capabilities related to the second device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
62. The method according to any one of claims 33 to 61, wherein: The method further comprises: The second device receives thirteenth information, where the thirteenth information includes capabilities related to the first device.
63. The method of claim 62, wherein: The capabilities related to the first device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
64. The method of any one of claims 33 to 63, wherein: The second device is a terminal device or a network device.
65. A first device, comprising: The first sending unit is used to send first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
66. The first device according to claim 65, wherein The first information domain includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
67. A first device according to claim 65 or 66, wherein The second information field includes a meaning-variable model identifier and / or a user-defined model identifier.
68. A first device according to any one of claims 65 to 67, wherein The first information field and / or the second information field has associated model description information.
69. The first device according to claim 68, wherein The model description information includes one or more of the following information: Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of input parameters associated with the model, input parameter preprocessing rules associated with the model, information on the types of output parameters associated with the model, information on the format requirements of output parameters associated with the model, output parameter preprocessing rules associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization characteristic information of the model, version information of the model, accuracy level information of the model, compilation format information of model data, storage format information of model data, computational complexity information of the model, complexity information of the model, and size information of the model.
70. A first device according to any one of claims 65 to 69, wherein: The association information between the first information field and its corresponding model description information is predefined.
71. A first device according to any one of claims 65 to 70, wherein The association information between the second information field and its corresponding model description information is obtained through model detection or testing.
72. A first device according to any one of claims 65 to 71, wherein The first information also includes model description information associated with the second information field.
73. A first device according to any one of claims 65 to 72, wherein: The first device also includes: The first receiving unit is used for the first device to receive second information, where the second information includes test information, and the test information includes one or more test case information.
74. The first device according to claim 73, wherein: The first device also includes: The second sending unit is used to send third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
75. A first device according to any one of claims 65 to 74, wherein The first device also includes: The second receiving unit is used to receive fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
76. The first device according to claim 75, wherein The fourth information also includes rejection reason information.
77. A first device according to any one of claims 65 to 76, wherein The first device also includes: The third receiving unit is used to receive fifth information, where the fifth information includes acceptance request information and / or a third information field.
78. The first device according to claim 77, wherein The first device also includes: A processing unit is used to generate a second model identifier based on the third information field.
79. The first device according to claim 78, wherein The manner in which the first device generates the second model identifier based on the third information field includes at least one of the following: Combining all or part of the sub-information fields of the first information field and the third information field to obtain a second model identifier; The first information field, the second information field and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
80. A first device according to any one of claims 65 to 79, wherein: The second information field and / or the third information field includes one or more of the following sub-information field information: The operator information associated with the model, the terminal device manufacturer information associated with the model, the model provider or manufacturer information associated with the model, the chip manufacturer information associated with the model, the network equipment manufacturer information associated with the model, the version number information of the model, and the temporary identification information associated with the model.
81. A first device according to any one of claims 65 to 80, wherein The first device also includes: The third sending unit is used to send sixth information, where the sixth information is used for the model control process, and the sixth information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-information fields of the third information field.
82. A first device according to any one of claims 65 to 81, wherein The first device also includes: The fourth receiving unit is used to receive seventh information, where the seventh information is used for the model control process, and the seventh information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-information fields of the third information field.
83. The first device according to claim 81 or 82, wherein The model control process includes one or more of the following: Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
84. A first device according to any one of claims 65 to 83, wherein The first device also includes: The fifth receiving unit is used to receive eighth information, where the eighth information includes one or more first information fields.
85. The first device according to claim 84, wherein The eighth information is used to indicate to the first device that the model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
86. A first device according to any one of claims 65 to 85, wherein The first device also includes: The fourth sending unit is used to send ninth information, where the ninth information includes one or more first information fields.
87. The first device according to claim 86, wherein The ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
88. A first device according to any one of claims 65 to 87, wherein The first device also includes: The fifth sending unit is used to send tenth information, where the tenth information includes one or more first information fields.
89. The first device according to claim 88, wherein The tenth information is used to indicate the first information domain associated with the model that has been saved or deployed by the first device and / or the first information domain associated with the model that has not been saved or deployed by the first device.
90. A first device according to any one of claims 65 to 89, wherein: The first device also includes: The sixth receiving unit is used to receive eleventh information, where the eleventh information includes one or more of the first information fields.
91. The first device according to claim 90, wherein The eleventh information is used to query the model status saved and / or deployed by the first device.
92. A first device according to any one of claims 65 to 91, wherein The first device also includes: The seventh receiving unit is used to receive twelfth information, where the twelfth information includes capabilities related to the second device.
93. The first device according to claim 92, wherein: The capabilities related to the second device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
94. A first device according to any one of claims 65 to 93, wherein The first device also includes: The sixth sending unit is used to send thirteenth information, where the thirteenth information includes capabilities related to the first device.
95. The first device of claim 94, wherein: The capabilities related to the first device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
96. A first device according to any one of claims 65 to 95, wherein: The first device is a terminal device or a network device.
97. A second device, comprising: The first receiving unit is used to receive first information, where the first information includes a first model identifier, and the first model identifier includes a first information field and / or a second information field.
98. The second device according to claim 97, wherein The first information domain includes at least one of a meaning-invariant model identifier, a universal model identifier, and a globally unique model identifier.
99. The second device according to claim 97 or 98, wherein: The second information field includes a meaning-variable model identifier and / or a user-defined model identifier.
100. The second device according to any one of claims 97 to 99, wherein: The first information field and / or the second information field has associated model description information.
101. The second device according to claim 100, wherein: The model description information includes one or more of the following information: Functional characteristics associated with the model, information on the types of input parameters associated with the model, information on the format requirements of input parameters associated with the model, input parameter preprocessing rules associated with the model, information on the types of output parameters associated with the model, information on the format requirements of output parameters associated with the model, output parameter preprocessing rules associated with the model, application scenario information associated with the model, deployment location information associated with the model, capability requirement information for using the model, performance monitoring indicator information associated with the model, location information associated with the model, effective usage scope information associated with the model, generalization characteristic information of the model, version information of the model, accuracy level information of the model, compilation format information of model data, storage format information of model data, computational complexity information of the model, complexity information of the model, and size information of the model.
102. The second device according to any one of claims 97 to 101, wherein: The association information between the first information field and its corresponding model description information is predefined.
103. The second device according to any one of claims 97 to 102, wherein: The association information between the second information field and its corresponding model description information is obtained through model detection or testing.
104. The second device according to any one of claims 97 to 103, wherein: The first information also includes model description information associated with the second information field.
105. The second device according to any one of claims 97 to 104, wherein: The second device also includes: The first sending unit is used to send second information, where the second information includes test information, and the test information includes one or more test case information.
106. The second device according to claim 105, wherein: The second device also includes: The second receiving unit is used to receive third information, where the third information includes test result information, and the test result information includes test results of one or more test cases.
107. The second device according to any one of claims 97 to 106, wherein: The second device also includes: The second sending unit is used to send fourth information, where the fourth information includes rejection information, and the rejection information is used to reject the request for the first information.
108. The second device according to claim 107, wherein: The fourth information also includes rejection reason information.
109. The second device according to any one of claims 97 to 108, wherein: The second device also includes: The third sending unit is used to send fifth information, where the fifth information includes acceptance request information and / or a third information field.
110. The second device according to claim 109, wherein: The second device further includes: a processing unit, configured to generate a second model identifier based on the third information field.
111. The second device according to claim 110, wherein: The second model identifier is generated in at least one of the following ways: Combining all or part of the sub-information fields of the first information field and the third information field to obtain a second model identifier; The first information field, the second information field and all or part of the sub-information fields of the third information field are combined to obtain a second model identifier.
112. The second device according to any one of claims 97 to 111, wherein The second information field and / or the third information field includes one or more of the following sub-information field information: The operator information associated with the model, the terminal device manufacturer information associated with the model, the model provider or manufacturer information associated with the model, the chip manufacturer information associated with the model, the network equipment manufacturer information associated with the model, the version number information of the model, and the temporary identification information associated with the model.
113. The second device according to any one of claims 97 to 112, wherein: The second device also includes: The third receiving unit is used to receive sixth information, where the sixth information is used for the model control process, and the sixth information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-information fields of the third information field.
114. The second device according to any one of claims 97 to 113, wherein: The second device also includes: The fourth sending unit is used to send seventh information, where the seventh information is used for the model control process, and the seventh information includes one or more of the following information: the first model identifier, the second information field, the second model identifier, and one or more sub-fields of the third information field. Information domain.
115. The second device according to claim 113 or 114, wherein: The model control process includes one or more of the following: Model selection, model activation, model deactivation, model switching, model deletion, model monitoring, model reasoning, model training, model update, model-related capability interaction, model registration, model transmission, model training data collection, model monitoring data collection, model reasoning data collection, model update data collection, model deployment.
116. The second device according to any one of claims 97 to 115, wherein: The second device also includes: The fifth sending unit is used to send eighth information, where the eighth information includes one or more first information fields.
117. The second device according to claim 116, wherein: The eighth information is used to indicate to the first device that the model description information associated with the target model deployed by the first device needs to be synchronized with the second device.
118. The second device according to any one of claims 97 to 117, wherein: The second device also includes: The fourth receiving unit is used to receive ninth information, where the ninth information includes one or more first information fields.
119. The second device according to claim 118, wherein The ninth information is used to indicate to the second device that the model description information associated with the target model deployed by the first device can be synchronized with the second device.
120. The second device according to any one of claims 97 to 119, wherein: The second device also includes: The fifth receiving unit is used to receive tenth information, where the tenth information includes one or more first information fields.
121. The second device according to claim 120, wherein: The tenth information is used to indicate the first information domain associated with the model that has been saved or deployed by the first device and / or the first information domain associated with the model that has not been saved or deployed by the first device.
122. The second device according to any one of claims 97 to 121, wherein: The second device also includes: The sixth sending unit is used to send eleventh information, where the eleventh information includes one or more of the first information fields.
123. The second device according to claim 122, wherein: The eleventh information is used to query the model status saved and / or deployed by the first device.
124. The second device according to any one of claims 97 to 123, wherein: The second device also includes: The seventh sending unit is used to send twelfth information, where the twelfth information includes capabilities related to the second device.
125. The second device according to claim 124, wherein The capabilities related to the second device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
126. The second device according to any one of claims 97 to 125, wherein The second device also includes: The sixth receiving unit is used to receive thirteenth information, where the thirteenth information includes capabilities related to the first device.
127. The second device according to claim 126, wherein The capabilities related to the first device include one or more of the following: Whether to support the model registration process; Whether to support the information synchronization process of model description information; Whether the model control process is supported; Whether to support the model information query process.
128. The second device according to any one of claims 97 to 127, wherein: The second device is a terminal device or a network device.
129. A communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the communication device executes the method as claimed in any one of claims 1 to 32 or any one of claims 33 to 64.
130. A chip, comprising: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 32 or any one of claims 33 to 64.
131. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform a method as claimed in any one of claims 1 to 32 or any one of claims 33 to 64.
132. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 32 or any one of claims 33 to 64.
133. A computer program causing a computer to perform the method of any one of claims 1 to 32 or any one of claims 33 to 64.
Citation Information
Patent Citations
Communication method and device
CN114143799A
Model request method, model request processing method and related equipment
CN116017493A
Chatbot server device, learning device, chatbot system, chatbot server device operation method, learning device operation method, program, and recording medium
JP6760676B1
Distributed learning method, server and application using identification card recognition model, and identification card recognition method using the same
US20220270355A1
Network model management method, session establishment or modification method, and apparatus
WO2021163895A1
