Model management method and device and communication system

Abstract

The embodiment of the invention provides a model management method and device and a communication system. The model management device is applied to terminal equipment, and comprises a first receiving unit which is configured to receive information which is sent by network equipment and is related to configuration and / or scene; and the management unit is configured to manage the model used by the terminal equipment according to the configuration and / or the scene.

Description

Model management method, device and communication system Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] Massive multiple-input multiple-output (MIMO) technology is one of the key technologies for 5G mobile communications. MIMO can provide higher channel capacity, but achieving these benefits depends on obtaining accurate channel state information.

[0003] In MIMO technology, terminal devices measure spatial channels and provide channel state information (CSI) back to the network. Based on this CSI, the network selects an appropriate precoding matrix for downlink transmission to the terminal, minimizing the probability of bit errors in the terminal's reception.

[0004] The channel state information generation and feedback process can be summarized as follows. The network device sends a channel state information reference signal (CSI-RS) to each terminal device. The terminal device estimates the channel using the received CSI-RS and obtains an estimate of the spatial channel matrix. The terminal device further uses the estimated spatial channel to obtain CSI. In new radio (NR) technology, CSI feedback is implicit. That is, the terminal device feeds back CSI in the form of recommended transmission parameters to the network device. These transmission parameters include channel state indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), synchronization signal block resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), and physical layer RSRP (L1-RSRP). The base station can directly use the parameters recommended by the terminal device for downlink transmission, or it can choose not to use the recommended parameters.

[0005] In frequency division duplex (FDD) systems, for the downlink, when network devices use downlink channel information for precoding, terminal devices are required to feed back downlink channel state information to the network devices via the uplink. However, because downlink channel information is proportional to the number of antennas on the network devices, in massive MIMO scenarios, the large number of network device antennas results in a very large amount of downlink channel state information feedback. The Third Generation Partnership Project (3GPP) has designed enhanced codebooks (for example, the etype II codebook) for downlink feedback, reducing the amount of channel state information feedback through frequency domain compression. However, given the precious uplink resources, there is still a need to further reduce the amount of uplink feedback.

[0006] With the advancement of artificial intelligence / machine learning (AI / ML) technologies, applying them to the physical layer of wireless communications to address the challenges of traditional methods has become a key technology trend. The application of AI / ML models to wireless communication systems, particularly air interface transmission, is a new technology for 5G-Advanced and 6G.

[0007] Figure 1 is a schematic diagram of AI / ML-based CSI feedback. As shown in Figure 1, in operation 101, the terminal device uses a CSI generation module based on an AI / ML model to compress the downlink CSI to obtain compressed CSI. The network device receives this compressed CSI over the air interface. In operation 102, the network device uses a CSI reconstruction model based on the AI / ML model to decompress the received CSI to obtain recovered CSI. Because compressed channel state information is transmitted over the air interface, the amount of uplink channel feedback can be significantly reduced when channel coefficients are well correlated.

[0008] AI / ML model technology is also being applied to beam management or positioning. For example, in beam management, AI / ML models can be used to predict the optimal spatial beam pair based on a small number of beam measurements, reducing system load and latency.

[0009] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0010] Summary of the Invention

[0011] The inventors of this application discovered that since AI / ML models are trained for at least one scenario and / or at least one configuration, the trained AI / ML models may not be applicable to all scenarios and / or configurations. Therefore, it is necessary to manage the AI / ML models, for example, lifecycle management. However, in the prior art, there is little discussion on the lifecycle management of AI / ML models.

[0012] In response to at least the above-mentioned problems or other similar problems, embodiments of the present application provide a method, device, and communication system for model management, which manage the model based on information related to the configuration and / or scenario, thereby maintaining the model in a state adapted to the configuration and / or scenario, thereby improving the reliability of the model.

[0013] According to one aspect of an embodiment of the present application, there is provided a model management apparatus, applied to a terminal device, the apparatus comprising:

[0014] a first receiving unit configured to receive information related to configuration and / or scenario sent by a network device; and

[0015] A management unit is configured to manage the model used by the terminal device according to the configuration and / or scenario.

[0016] According to another aspect of an embodiment of the present application, a model management apparatus is provided, which is applied to a network device, and includes:

[0017] A first sending unit configured to send information related to configuration and / or scenario to a terminal device; and

[0018] The second receiving unit is configured to receive information related to management of the model used by the terminal device by the terminal device according to the configuration and / or scenario.

[0019] One of the beneficial effects of the embodiments of the present application is that the model is managed based on information related to the configuration and / or scenario, thereby maintaining the model in a state adapted to the configuration and / or scenario, thereby improving the reliability of the model.

[0020] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0021] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0022] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0024] Figure 1 is a schematic diagram of CSI feedback based on AI / ML;

[0025] FIG2 is a schematic diagram of the communication system of the present application;

[0026] FIG3 is a schematic diagram of a model management method according to an embodiment of the first aspect of the present application;

[0027] FIG4 is a schematic diagram of an example of managing models used by terminal devices;

[0028] FIG5 is a schematic diagram of a terminal device and a network device communicating when a model is adapted to a configuration and / or scenario;

[0029] FIG6 is a schematic diagram of communication between a terminal device and a network device when the terminal device is able to obtain a model adapted to a configuration and / or scenario;

[0030] 7 is a schematic diagram of communication between a terminal device and a network device when the terminal device is able to obtain a model adapted to a configuration and / or scenario;

[0031] FIG8 is a schematic diagram of a model management method according to an embodiment of the second aspect;

[0032] FIG9 is a schematic diagram of an apparatus for model management according to an embodiment of the third aspect;

[0033] FIG10 is a schematic diagram of a model management apparatus according to an embodiment of the fourth aspect;

[0034] FIG11 is a schematic diagram of a terminal device according to an embodiment of the fifth aspect;

[0035] Figure 12 is a schematic diagram of a network device of an embodiment of the fifth aspect. DETAILED DESCRIPTION

[0036] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0037] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0038] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0039] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0040] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0041] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. Network devices may include, but are not limited to, the following devices: an integrated access and backhaul node (IAB-node), a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and the like.

[0042] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0043] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0044] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0045] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0046] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as mentioned above.

[0047] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" are interchangeable to avoid confusion.

[0048] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" are interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH)" are interchangeable.

[0049] In addition, sending or receiving PUSCH can be understood as sending or receiving uplink data carried by PUSCH, sending or receiving PUCCH can be understood as sending or receiving uplink information carried by PUCCH, and sending or receiving PRACH can be understood as sending or receiving preamble carried by PRACH; uplink signals can include uplink data signals and / or uplink control signals, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or uplink channels. Sending uplink transmission on uplink resources can be understood as sending the uplink transmission using the uplink resources. Similarly, downlink data / signals / channels / information can be understood accordingly.

[0050] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0051] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0052] Figure 2 is a schematic diagram of the communication system of the present application, which schematically illustrates a situation taking a terminal device and a network device as an example. As shown in Figure 2, the communication system 100 may include a network device 201 and a terminal device 202 (for simplicity, Figure 2 only illustrates one terminal device as an example).

[0053] In the embodiment of the present application, existing services or future services can be carried out between the network device 201 and the terminal device 202. For example, these services include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0054] Among them, the terminal device 202 can send data to the network device 201, for example, using an authorized or unauthorized transmission mode. The network device 201 can receive data sent by one or more terminal devices 202 and feedback information to the terminal device 202, such as confirmation ACK / non-confirmation NACK information. The terminal device 202 can confirm the end of the transmission process, or can continue new data transmission, or can retransmit the data based on the feedback information.

[0055] In the following description of this application, the artificial intelligence (AI) model may also be referred to as an artificial intelligence / machine learning (AI / ML) model, that is, the AI ​​model and AI / ML model recorded in this application have the same meaning.

[0056] Embodiments of the first aspect

[0057] An embodiment of the first aspect provides a model management method, which is applied to a terminal device, for example, the terminal device 202 in FIG. 2 .

[0058] FIG3 is a schematic diagram of a model management method according to an embodiment of the first aspect of the present application. As shown in FIG3 , the method includes:

[0059] Operation 301: Receive information related to configuration and / or scenario sent by a network device; and

[0060] Operation 302: Manage the model used by the terminal device according to the configuration and / or scenario.

[0061] Through the embodiments of the first aspect, the model is managed based on information related to the configuration and / or scenario, thereby maintaining the model in a state adapted to the configuration and / or scenario, thereby improving the reliability of the model. For example, even if the configuration and / or scenario changes, the model can still be managed to adapt to the changed configuration and / or scenario.

[0062] In at least one embodiment, the model in operation 302 is used to generate channel state information (CSI), and / or for beam management, and / or positioning. The model may be an artificial intelligence (AI) model. The model can be applicable to at least one configuration and / or at least one scenario. For example, the model is trained based on at least one configuration and / or at least one scenario.

[0063] In at least one embodiment, the terminal device may have at least one model, for example, the terminal device may store at least one model. In addition, the terminal device may also obtain at least one model from another device, for example, the terminal device may obtain at least one model from a network device based on a model transfer mechanism, or the terminal device may download the model from a public server or a server with intellectual property rights.

[0064] In at least one embodiment, the configuration in operations 301 and 302 may be a configuration specified in the communication protocol or a configuration not specified in the communication protocol, such as an antenna configuration of a network device.

[0065] In a specific example, the antenna configuration is used to configure at least one of the following parameters of an antenna of the network device:

[0066] The number of antenna panels contained in one column of the antenna array;

[0067] The number of antenna panels contained in a row of the antenna array;

[0068] The distance between adjacent antenna panels in the horizontal direction;

[0069] The distance between adjacent antenna panels in the vertical direction;

[0070] The antenna array is a uniform antenna array or a non-uniform antenna array;

[0071] In an antenna panel, the number of antenna units included in a column, and / or the number of antenna units included in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna (for example, the tilt angle of the antenna is 0°, or ±45°), etc.

[0072] In at least one embodiment, the number of antenna configurations is one or more than one.

[0073] In one example, when the number of antenna configurations is more than one, the more than one antenna configurations may have corresponding antenna configuration identification numbers (IDs).

[0074] For example, the antenna configuration ID can be a primary ID or a secondary ID. For the secondary ID, an example is as follows:

[0075] The secondary ID of an antenna configuration can be represented by an array (a1, a2), where a1 represents the sub-ID of the antenna configuration item, including the "number of antenna panels in a column of the antenna array" and so on. For example, if there are 12 possible antenna configurations, a1 can take values ​​from 1, 2, 3, ..., 12. a2 represents the sub-ID of each possible value within the antenna configuration. For example, if there are 6 possible values ​​for "number of antenna panels in a column of the antenna array," a2 can take values ​​from 1, 2, 3, ..., 6. In this case, (a1, a2) has a total of 72 possible values, including (1, 1), ..., (12, 6). For this example, if it were a primary ID, the 72 possible antenna configuration primary IDs would be 1, 2, ..., 72. The order of the antenna configuration primary IDs can be predefined.

[0076] In another example, antenna configuration parameters and their corresponding values ​​are predefined, for example, in a standard communication protocol document. For example, a high-level parameter name can be defined for each antenna configuration item in the standard document. The parameter names and their corresponding values ​​can be defined in the standard document, as shown in Table 1. Table 1 provides an example definition of antenna configuration parameter names and their corresponding values.

[0077] Table 1:

[0078]

[0079]

[0080] In the subsequent description of this application, the antenna configuration identification number (ID) is used as an example for description.

[0081] As shown in FIG3 , the method further includes:

[0082] Operation 303: Receive inquiry information sent by the network device, where the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is applicable to the configuration and / or scenario.

[0083] In operation 303, the query information may include the configuration and / or scenario-related information in operation 301, so that operation 303 and operation 301 may be combined into the same operation; or, the query information does not include the configuration and / or scenario-related information in operation 301, so that operation 303 and operation 301 are two separate operations.

[0084] In operations 301 and 303, information related to configuration and / or scenario and / or the query information may be received via a downlink channel, such as a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH).

[0085] In at least one embodiment, corresponding to operation 301, the network device may send information related to the configuration and / or scenario to the terminal device when the scenario and / or configuration changes. For example, the terminal device may still be communicating with the same network device, but the antenna configuration of the network device may have changed, such as at least one antenna panel being disabled. Furthermore, the present application is not limited thereto, and the network device may also send information related to the configuration and / or scenario to the terminal device in other situations (e.g., at startup).

[0086] In at least one embodiment, the management of the model used by the terminal device in operation 302 includes: model generalization, and / or model switching, and / or model updating, and / or switching of model types (for example, switching from an AI model to a non-AI model, or switching from a non-AI model to an AI model), etc.

[0087] In the case of model updates, the terminal device can record the model's version identification number (ID). In addition, when the model has an ID, the version ID under this model ID can still be recorded, such as version 3 of AI model 2.

[0088] In some implementations, a terminal device can report model management results, or identification information (ID) corresponding to the model management results, namely, a model management result ID, to a network device. This model management result ID can include several types of model management, such as: within the model's generalization capabilities, i.e., AI / ML model adaptation to the configuration and / or scenario; model switching; and model updates. Each type of model management has a corresponding processing method. For example, for model updates, processing methods include model fine-tuning and model training. Based on the above, the model management result ID can be designed as a primary, secondary, or tertiary ID, etc., but is not limited to these. For a secondary ID, a secondary ID can be defined as (a, b), where a represents the model management type and b represents the processing method for each model management type. For a tertiary ID, a secondary ID can be defined as (a, b, c), where a represents the model management type, b represents the processing method for each model management type, and c represents the model version number for model updates. A specific example is provided below, as shown in Table 2. Here we assume that the terminal device has and can access a total of 6 AI / ML models.

[0089] Table 2:

[0090]

[0091]

[0092]

[0093] As can be seen from Table 2, the advantage of the first-level ID is that it may save the number of bits required to describe this ID. The advantage of the second-level ID is that it can clearly indicate the type of model management. The third-level ID can record the model version number. In some embodiments, the third-level ID can be introduced based on the second-level ID only for model updates, while the second-level ID is still used for AI model adaptation and / or scene and model switching.

[0094] Fig. 4 is a diagram illustrating an example of managing a model used by a terminal device, for implementing operation 302. In this example, the antenna configuration of the network device is changed, for example, at least one antenna panel is disabled.

[0095] As shown in Figure 4, the models used by terminal devices are managed, including:

[0096] Operation 401: Verify whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario;

[0097] Operation 402: reporting to the network device that the model used by the terminal device is applicable to the configuration and / or scenario as a result of model management, or reporting to the network device identification information (ID) corresponding to the result of the model management.

[0098] In operation 401, one verification method may be to check the specification of the AI / ML model used to see whether the changed antenna configuration is included in the specification of the AI / ML model used, for example, the specification of the AI / ML model used states that it can be applied to a situation where certain antenna panels are disabled.

[0099] Another verification method can be based on AI / ML model monitoring. For example, the terminal device requests the network device to adapt to the changed antenna configuration data via an uplink channel. This data can be pre-agreed upon by both parties and is known to both parties. After receiving the request from the terminal device, the network device sends the data to the terminal device via a downlink channel. The terminal device receives the data, decodes it, and calculates the block error rate (BLER). If the BLER is not greater than a pre-agreed value, the AI / ML model being used by the terminal device is adapted to the changed antenna configuration; otherwise, it is not adapted.

[0100] In operation 402, the terminal device may report to the network device through an uplink channel (PUCCH or PUSCH), and the report content is that the AI / ML model being used by the terminal device can adapt to the antenna configuration configured by the network device (for example, the changed antenna configuration), for example: the generalization capability of the AI / ML model being used by the terminal device includes the antenna configuration configured by the network device, that is, the AI / ML model can be applied to a variety of configurations and / or scenarios. For the case of reporting using the primary ID of the model management result ID, in the example of Table 2, the reporting ID is 1, which can be described using the bit sequence "0000". For the case of reporting using the secondary ID of the model management result ID, in the example of Table 2, the reporting ID is (1,1), which can be described using the bit sequence "00 000".

[0101] FIG5 is a schematic diagram of a terminal device and a network device communicating when a model is adapted to a configuration and / or scenario. FIG5 corresponds to operation 402 .

[0102] As shown in Figure 5:

[0103] Operation 501: The network device sends information related to the configuration and / or scenario, and query information, where the query information inquires whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario.

[0104] Operation 502: After verification, the terminal device reports to the network device that the model used by the terminal device is applicable to the configuration and / or scenario.

[0105] As shown in FIG4 , managing the model used by the terminal device may also include:

[0106] Operation 403: Report to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and that the terminal device has and / or can obtain a model applicable to the configuration and / or scenario.

[0107] As shown in FIG4 , managing the model used by the terminal device may also include:

[0108] Operation 404: switching the model; and

[0109] Operation 405: After switching the model, report to the network device: a message indicating successful model switching, and / or information about the switched model, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the end time of the report, and / or the time interval between the time when the switching takes effect and the start time of the report.

[0110] In operation 405 , information of the switched model corresponds to the configuration and / or scenario.

[0111] In at least one embodiment, the model switching in operation 404 can be performed spontaneously by the terminal device or based on the instruction of the network device. For example, as shown in FIG4 , managing the model used by the terminal device also includes:

[0112] Operation 406: Receive a switching command sent by the network device, where the switching command instructs the terminal device to switch the model.

[0113] Through operation 406 , the terminal device may perform model switching upon receiving a switching command from the network device.

[0114] As shown in FIG4 , managing the model used by the terminal device may also include:

[0115] Operation 407: Report the switching of the model to the network device as a result of model management, or report identification information (ID) corresponding to the result of the model management to the network device.

[0116] In a specific example, the above operations 403 to 407 are described as follows:

[0117] The terminal device reports to the network device through the uplink channel (PUCCH or PUSCH), and the report content includes that the AI / ML model currently being used by the terminal device cannot adapt to the changed antenna configuration configured by the network device. The terminal device repeats the above verification process for the AI / ML model it owns or can obtain to test whether the AI / ML model it owns or can obtain is adapted to the changed antenna configuration. The obtainable AI / ML model may be an AI / ML model sent to the terminal device by the network device, or it may be an AI / ML model downloaded by the terminal device through a public server or a server with intellectual property rights. The terminal device reports to the network device through the uplink channel (PUCCH or PUSCH), and the report content includes that the terminal device has or can obtain the AI / ML model that is applicable to the changed antenna configuration of the network device. The network device sends signaling through the downlink channel to notify the terminal device to switch the AI / ML model (switch). After receiving the signaling, the terminal device switches to the appropriate AI / ML model and reports to the network device via the uplink channel. The report includes the successful AI / ML model switch by the terminal device and information about the switched AI / ML model, such as the model ID. In the case where the network device has an AI / ML model monitoring function, after receiving the report from the terminal device, the network device processes the KPI monitored by the AI / ML model. For example, if the KPI monitored by the AI / ML model is BLER, the network device resets the error counter to 0 and then performs AI / ML model monitoring.

[0118] Figure 6 is a schematic diagram of a terminal device and a network device communicating when the terminal device is able to obtain a model adapted to a configuration and / or scenario. Operation 602 of Figure 6 corresponds to operations 403 to 407.

[0119] As shown in Figure 6:

[0120] Operation 601: The network device sends information related to the configuration and / or scenario, and query information, where the query information inquires whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario.

[0121] Operation 602: After verification, the terminal device reports to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and that the terminal device has and / or can obtain a model applicable to the configuration and / or scenario; after model switching, the terminal device reports to the network device that the model switching is performed, a message of successful model switching, and / or information about the switched model, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the end time of this report, and / or the time interval between the time when the switching takes effect and the start time of this report.

[0122] As shown in FIG4 , managing the model used by the terminal device may also include:

[0123] Operation 408: Report to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

[0124] As shown in FIG4 , managing the model used by the terminal device may also include:

[0125] Operation 409: Update the model based on the data received from the network device and / or the downloaded data; and

[0126] Operation 410: After the model is updated, report a message indicating that the model has been updated successfully and information about the updated model to the network device.

[0127] In operation 409, the terminal device receives data from the network device via signaling, or the terminal device receives data from the network device in the form of data packets. Signaling includes radio resource control (RRC), media access control layer control element (MAC CE) signaling, or downlink control information (DCI). Furthermore, before operation 409, the terminal device may first send a message requesting data to the network device, and then, in operation 409, the terminal device may receive data from the network device.

[0128] In operation 409 , the terminal device may also download data from a public server or a server with intellectual property (IP).

[0129] The received data and / or downloaded data includes: original data and / or data obtained by quantizing the original data. For example, the data may be a vector of a spatial channel matrix, or data based on quantization of a vector of a spatial channel matrix, wherein the quantization method includes a single-precision floating point number, a double-precision floating point number, an integer, any codebook specified by the Third Generation Partnership Project (3GPP), or a combination of any 3GPP codebook structure and a set of customized non-3GPP parameters.

[0130] In operation 409, updating the model includes fine-tuning or training the used model. In addition, after the model is updated, the terminal device can record the version number of the updated model, for example, the version number of the updated AI model.

[0131] In operation 410 , the information of the updated model includes identification information (ID) of the updated model and / or model version information.

[0132] As shown in FIG4 , managing the model used by the terminal device also includes:

[0133] Operation 411: Switch the type of model to be used to perform corresponding processing.

[0134] Operation 411 may also be referred to as model fallback. In operation 411, the type of model used is switched, including: switching from an artificial intelligence model to a non-artificial intelligence model, or switching from a non-artificial intelligence model to an artificial intelligence model. For example, if the time required to update a model (e.g., an AI model) is greater than a threshold, the terminal device may switch the AI ​​model being used to a non-AI model, thereby continuing the corresponding processing and avoiding suspension of the service for too long. The corresponding processing includes: generating channel state information, and / or beam management, and / or positioning.

[0135] For example, in operation 411, the terminal device may choose to fall back from using the AI ​​model for CSI feedback to using the traditional codebook method for CSI feedback, and the terminal device reports the fallback to the AI ​​model, the time when the fallback occurs, and the type and recommended parameters of the traditional 3GPP-specified codebook to which it falls back to to the network device through the uplink channel. The codebook types include Rel-15 single-panel type 1 (type 1) codebook, Rel-15 multi-panel type 1 codebook, Rel-15 type 2 codebook, Rel-15 type 2 port selection codebook, Rel-16 type 2 codebook, Rel-16 type 2 port selection codebook, Rel-17 type 2 codebook, etc.

[0136] As shown in FIG4 , managing the model used by the terminal device also includes:

[0137] Operation 412, before switching the type of model used (for example, before operation 411), report to the network device: the type of model used by the terminal device for corresponding processing, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the end time of this report, and / or the time interval between the time when the switch takes effect and the start time of this report, and / or the type and / or parameters of the model used after the switch.

[0138] Through operation 412 , the network device can prepare to cooperate with the model fallback of the terminal device.

[0139] As shown in FIG4 , managing the model used by the terminal device also includes:

[0140] Operation 413: After the model is updated, the model in use is switched to the updated model, and the network device is reported: the terminal device switches the model in use to the updated model, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the end time of the report, and / or the time interval between the time when the switch takes effect and the start time of the report.

[0141] Through operation 413, the model rolled back in operation 411 can be switched to an updated model, for example, from a non-AI model to an updated AI model. Furthermore, through the reporting of the terminal device, the network device can be prepared to cooperate with the model switching of the terminal device.

[0142] Figure 7 is a schematic diagram of a terminal device and a network device communicating when the terminal device is able to obtain a model adapted to a configuration and / or scenario. The operations in Figure 7 correspond to operations 408 to 413.

[0143] As shown in Figure 7:

[0144] Operation 701: The network device sends information related to the configuration and / or scenario, and query information, where the query information inquires whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario.

[0145] Operation 702: After verification, the terminal device reports to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device does not have and cannot obtain a model applicable to the configuration and / or scenario; the terminal device reports to the network device that the terminal device updates the model and switches the working mode of the currently used AI model to a working mode using a non-AI model, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the end time of the report, and / or the time interval between the time when the switching takes effect and the start time of the report, and / or the type and / or parameters of the model used after the switch;

[0146] Operation 703: The network device notifies the terminal device that it has switched the terminal device to a non-AI model working mode.

[0147] Operation 704: After completing the model update, the terminal device reports to the network device: information about the updated model; and the terminal device reports to the network device: the switching from a non-AI model operating mode to an AI model operating mode, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the end time of the reporting, and / or the time interval between the time when the switching takes effect and the start time of the reporting.

[0148] Operation 705: The network device informs the terminal device that it has learned that the terminal device has switched to a working mode using the updated AI model.

[0149] In the above embodiments, the signaling sent through the downlink channel may be RRC signaling, MAC CE signaling, or DCI signaling. The signaling sent through the uplink channel may be RRC signaling, MAC CE signaling, or UCI signaling.

[0150] In the present application, high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, a master information block (MIB), system information, or a dedicated RRC message; or a radio resource control information element (RRC IE). High-layer signaling may also be, for example, media access control (MAC) signaling; or a media access control control element (MAC CE). However, the present application is not limited thereto.

[0151] In embodiments of the present application, one or more AI / ML models may be configured and run in a network device and / or a terminal device. The AI / ML models may be used for various signal processing functions in wireless communications, such as CSI estimation and reporting, beam management and beam prediction, positioning, etc.; the present application is not limited thereto.

[0152] The following describes an embodiment of managing the model used by the terminal device based on the scenario.

[0153] In at least some embodiments, a terminal device moves from a cell covered by a current network device to a cell covered by another network device, where the antenna configuration of the another network device is different from the antenna configuration of the network device (i.e., the current network device). The scenario of the cell covered by the another network device is different from the scenario of the cell where the terminal device was previously located.

[0154] In the case of a terminal device moving into a cell covered by another network device, the terminal device queries the network device via an uplink channel regarding the network device's (i.e., the other network device's) scenario and configuration. The terminal device may also report information about the AI / ML model it is currently using to the network device. This information may be a predefined model ID. The network device notifies the terminal device of the network device's scenario and configuration via a downlink channel and queries the terminal device to determine whether its currently used AI / ML model is compatible with the scenario and configuration provided by the network device, or whether the terminal device possesses and / or is able to obtain an AI / ML model that is compatible with the scenario and configuration provided by the network device. The terminal device verifies whether its currently used AI / ML model is compatible with the scenario and configuration provided by the network device, or whether the terminal device possesses and / or is able to obtain an AI / ML model that is compatible with the scenario and configuration provided by the network device. The verification method may be the same as described previously. The terminal device may also use the previously described methods and / or processes for model management, including maintaining the model unchanged (i.e., within the model's generalization capabilities), switching models, or updating models. During a model update, the AI / ML model may be reverted to existing standard methods based on non-AI / ML methods for CSI generation and feedback, beam management, and / or positioning. The terminal device completes the corresponding model management actions and reports the model management results to the network device. The reporting method can be similar to the methods and / or processes described above.

[0155] Embodiments of the second aspect

[0156] At least for the same problem as the embodiment of the first aspect, the embodiment of the second aspect of the present application provides a model management method applied to network equipment, corresponding to the embodiment of the first aspect.

[0157] FIG8 is a schematic diagram of a model management method according to an embodiment of the second aspect, the method comprising:

[0158] Operation 801: Sending information related to configuration and / or scenario to a terminal device; and

[0159] Operation 802: Receive information related to management of a model used by the terminal device by the terminal device according to the configuration and / or scenario.

[0160] In operation 802, the model is used to generate channel state information (CSI), and / or beam management, and / or positioning. For example, the model is an artificial intelligence model, the terminal device has and / or can obtain at least one such model, and the model is applicable to at least one configuration and / or at least one scenario.

[0161] In at least one embodiment, the configuration includes an antenna configuration of the network device.

[0162] The antenna configuration is used to configure at least one of the following parameters of the antenna of the network device:

[0163] The number of antenna panels contained in one column of the antenna array;

[0164] The number of antenna panels contained in a row of the antenna array;

[0165] The distance between adjacent antenna panels in the horizontal direction;

[0166] The distance between adjacent antenna panels in the vertical direction;

[0167] The antenna array is a uniform antenna array or a non-uniform antenna array;

[0168] In an antenna panel, the number of antenna units contained in a column, and / or the number of antenna units contained in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna.

[0169] In at least one embodiment, the number of the antenna configurations is one or more than one. The more than one antenna configurations have corresponding antenna configuration identification numbers (IDs), or the parameters of the antenna configurations and their corresponding values ​​are predefined.

[0170] In at least one embodiment, as shown in FIG8 , the method further includes:

[0171] Operation 803: Send inquiry information to the terminal device, where the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is applicable to the configuration and / or scenario.

[0172] The query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

[0173] In at least one embodiment, the information related to the management of the model used by the terminal device includes: a result of model management, or identification information (ID) corresponding to the result of the model management. The result of the model management includes: the model used by the terminal device is suitable for the configuration and / or scenario.

[0174] In at least another embodiment, the terminal device manages information related to the model used, including:

[0175] The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is capable of acquiring a model applicable to the configuration and / or scenario.

[0176] In addition, the information related to the management of the model used by the terminal device also includes:

[0177] The message of successful model switching, and / or information of the model after switching, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the time when the network device receives the information related to the management of the model used by the terminal device.

[0178] In addition, the information related to the management of the model used by the terminal device also includes:

[0179] The result of model management, or identification information (ID) corresponding to the result of model management. The information of the switched model corresponds to the configuration and / or scenario.

[0180] The result of the model management includes: switching the model.

[0181] In addition, the network device may send a switching command to the terminal device, where the switching command instructs the terminal device to switch the model.

[0182] In at least one further embodiment, the terminal device manages information related to the model used, including: the model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

[0183] The information related to the management of the model used by the terminal device also includes:

[0184] A message indicating that the model has been successfully updated and information about the updated model.

[0185] Wherein, updating the model includes: fine-tuning or training the used model. The information of the updated model includes: identification information (ID) and / or model version information of the updated model.

[0186] The information related to the management of the model used by the terminal device also includes:

[0187] The result of model management, or identification information (ID) corresponding to the result of model management.

[0188] The result of the model management includes: updating the model.

[0189] In addition, the network device sends data for updating the model to the terminal device via signaling or in the form of data packets. The signaling includes: radio resource control (RRC), media access control layer control element (MAC CE) signaling or downlink control information (DCI).

[0190] The data includes original data and / or data obtained by quantifying the original data.

[0191] In addition, the network device may also switch the type of model used by the network device to perform corresponding processing.

[0192] Switching the type of model to be used includes switching from an artificial intelligence model to a non-artificial intelligence model, or vice versa. Corresponding processing includes generating channel state information, and / or beam management, and / or positioning.

[0193] In addition, the information related to the management of the model used by the terminal device also includes:

[0194] The type of model used by the terminal device for switching to perform corresponding processing, and / or the moment when the switching of the terminal device takes effect, and / or the time interval between the moment when the switching of the terminal device takes effect and the moment when the network device receives the information related to the management of the model used by the terminal device, and / or the type and / or parameters of the model used after the switching of the terminal device.

[0195] In addition, the information related to the management of the model used by the terminal device also includes:

[0196] The terminal device switches the model used to the updated model, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the time when the network device receives the information related to the management of the model used by the terminal device.

[0197] In addition, the network device may also switch the model in use to a model corresponding to the updated model.

[0198] Embodiments of the third aspect

[0199] The embodiment of the third aspect of the present application provides a model management apparatus, which is applied to a terminal device and corresponds to the method of the embodiment of the first aspect.

[0200] FIG9 is a schematic diagram of a model management apparatus according to an embodiment of the third aspect. As shown in FIG9 , the apparatus 900 includes:

[0201] A first receiving unit 901 is configured to receive information related to configuration and / or scenario sent by a network device; and

[0202] The management unit 902 is configured to manage the model used by the terminal device according to the configuration and / or scenario.

[0203] In at least one embodiment, the model is used to generate channel state information (CSI), and / or beam management, and / or positioning.

[0204] In at least one embodiment, the model is an artificial intelligence model. The terminal device has and / or is capable of acquiring at least one such model. The model is applicable to at least one configuration and / or at least one scenario.

[0205] In at least one embodiment, the configuration includes an antenna configuration of the network device.

[0206] In at least one embodiment, the antenna configuration is used to configure at least one of the following parameters of the antenna of the network device:

[0207] The number of antenna panels contained in one column of the antenna array;

[0208] The number of antenna panels contained in a row of the antenna array;

[0209] The distance between adjacent antenna panels in the horizontal direction;

[0210] The distance between adjacent antenna panels in the vertical direction;

[0211] The antenna array is a uniform antenna array or a non-uniform antenna array;

[0212] In an antenna panel, the number of antenna units contained in a column, and / or the number of antenna units contained in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna.

[0213] In at least one embodiment, the number of the antenna configurations is one or more than one, the more than one antenna configurations have corresponding antenna configuration identification numbers (IDs), or the parameters of the antenna configurations and their corresponding values ​​are predefined.

[0214] In at least one embodiment, the first receiving unit is further configured to:

[0215] Receive inquiry information sent by the network device, where the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is applicable to the configuration and / or scenario.

[0216] In at least one embodiment, the query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

[0217] In at least one embodiment, managing the model used by the terminal device includes:

[0218] Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and

[0219] The model used by the terminal device is reported to the network device as a result of model management, that the model is applicable to the configuration and / or scenario, or identification information (ID) corresponding to the result of the model management is reported to the network device.

[0220] In at least one embodiment, managing the model used by the terminal device includes:

[0221] Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and

[0222] Reporting to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is able to obtain a model applicable to the configuration and / or scenario.

[0223] In at least one embodiment, managing the model used by the terminal device further includes:

[0224] Switching the model; and

[0225] After switching the model, reporting to the network device:

[0226] Message of successful model switching, and / or information of the model after switching, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the end time of this report, and / or the time interval between the time when the switching takes effect and the start time of this report.

[0227] In at least one embodiment, managing the model used by the terminal device further includes:

[0228] The switching of the model is reported to the network device as a result of model management, or identification information (ID) corresponding to the result of the model management is reported to the network device.

[0229] In at least one embodiment, managing the model used by the terminal device further includes:

[0230] A switching command sent by the network device is received, where the switching command instructs the terminal device to switch the model.

[0231] In at least one embodiment, the information of the switched model corresponds to the configuration and / or scenario.

[0232] In at least one embodiment, managing the model used by the terminal device includes:

[0233] Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and

[0234] The model used by the terminal device to report to the network device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

[0235] In at least one embodiment, managing the model used by the terminal device further includes:

[0236] updating the model based on data received from the network device and / or data downloaded; and

[0237] After the model is updated, a message indicating that the model has been updated successfully and information about the updated model are reported to the network device.

[0238] In at least one embodiment, managing the model used by the terminal device further includes:

[0239] The updated model is reported to the network device as a result of model management, or identification information (ID) corresponding to the result of the model management is reported to the network device.

[0240] In at least one embodiment, the terminal device receives the data from the network device via signaling, or the terminal device receives the data from the network device in the form of data packets; or

[0241] The terminal device downloads the data from a public server or a server with intellectual property (IP).

[0242] In at least one embodiment, the signaling includes: radio resource control (RRC), medium access control layer control element (MAC CE) signaling or downlink control information (DCI).

[0243] In at least one embodiment, updating the model includes fine-tuning or training the model used.

[0244] In at least one embodiment, the information of the updated model includes: identification information (ID) and / or model version information of the updated model.

[0245] In at least one embodiment, the received data and / or the downloaded data include original data and / or data obtained by quantizing the original data.

[0246] In at least one embodiment, managing the model used by the terminal device further includes:

[0247] Switches the type of model used to process accordingly.

[0248] In at least one embodiment, switching the type of model used includes:

[0249] Switch from an AI model to a non-AI model, or vice versa.

[0250] In at least one embodiment, the corresponding processing includes:

[0251] Generate channel state information, and / or beam management, and / or positioning.

[0252] In at least one embodiment, managing the model used by the terminal device further includes:

[0253] Before switching the type of model used, report to the network device: the type of model used by the terminal device for corresponding processing, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the end time of this report, and / or the time interval between the time when the switch takes effect and the start time of this report, and / or the type and / or parameters of the model used after the switch.

[0254] In at least one embodiment, managing the model used by the terminal device further includes:

[0255] After the model is updated, the used model is switched to the updated model, and the following information is reported to the network device:

[0256] The terminal device switches the model used to the updated model, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the end time of this report, and / or the time interval between the time when the switch takes effect and the start time of this report.

[0257] Embodiments of the fourth aspect

[0258] The embodiment of the fourth aspect of the present application provides a model management device, which is applied to a network device and corresponds to the method of the embodiment of the second aspect.

[0259] FIG10 is a schematic diagram of a device for model management according to an embodiment of the fourth aspect. As shown in FIG10 , the device 1000 includes:

[0260] A first sending unit 1001 is configured to send information related to configuration and / or scenario to a terminal device; and

[0261] The second receiving unit 1002 is configured to receive information related to management of the model used by the terminal device by the terminal device according to the configuration and / or scenario.

[0262] In at least one embodiment, the model is used to generate channel state information (CSI), and / or beam management, and / or positioning.

[0263] In at least one embodiment, the model is an artificial intelligence model. The terminal device has and / or is capable of acquiring at least one such model, and the model is applicable to at least one configuration and / or at least one scenario.

[0264] In at least one embodiment, the configuration includes an antenna configuration of the network device.

[0265] In at least one embodiment, the antenna configuration is used to configure at least one of the following parameters of the antenna of the network device:

[0266] The number of antenna panels contained in one column of the antenna array;

[0267] The number of antenna panels contained in a row of the antenna array;

[0268] The distance between adjacent antenna panels in the horizontal direction;

[0269] The distance between adjacent antenna panels in the vertical direction;

[0270] The antenna array is a uniform antenna array or a non-uniform antenna array;

[0271] In an antenna panel, the number of antenna elements included in a column, and / or the number of antenna elements included in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna.

[0272] In at least one embodiment, the number of the antenna configurations is one or more than one, the more than one antenna configurations have corresponding antenna configuration identification numbers (IDs), or the parameters of the antenna configurations and their corresponding values ​​are predefined.

[0273] In at least one embodiment, the first sending unit is further configured to:

[0274] Sending inquiry information to the terminal device, wherein the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is suitable for the configuration and / or scenario.

[0275] In at least one embodiment, the query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

[0276] In at least one embodiment, the terminal device manages information related to the model used, including:

[0277] The result of model management, or identification information (ID) corresponding to the result of the model management, wherein the result of the model management includes: the model used by the terminal device is applicable to the configuration and / or scenario.

[0278] In at least one embodiment, the terminal device manages information related to the model used, including:

[0279] The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is capable of acquiring a model applicable to the configuration and / or scenario.

[0280] In at least one embodiment, the information related to the management of the model used by the terminal device further includes:

[0281] The message of successful model switching, and / or information of the model after switching, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the time when the network device receives the information related to the management of the model used by the terminal device.

[0282] In at least one embodiment, the information related to the management of the model used by the terminal device further includes:

[0283] The result of model management, or identification information (ID) corresponding to the result of model management, wherein the result of model management includes: switching the model.

[0284] In at least one embodiment, the first sending unit is further configured to:

[0285] A switching command is sent to the terminal device, where the switching command instructs the terminal device to switch the model.

[0286] In at least one embodiment, the information of the switched model corresponds to the configuration and / or scenario.

[0287] In at least one embodiment, the terminal device manages information related to the model used, including:

[0288] The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

[0289] In at least one embodiment, the information related to the management of the model used by the terminal device further includes:

[0290] A message indicating that the model has been successfully updated and information about the updated model.

[0291] In at least one embodiment, the information related to the management of the model used by the terminal device further includes:

[0292] The result of model management, or identification information (ID) corresponding to the result of model management, wherein the result of model management includes: updating the model.

[0293] In at least one embodiment, the first sending unit is further configured to:

[0294] The data for updating the model is sent to the terminal device via signaling or in the form of data packets.

[0295] In at least one embodiment, the signaling includes: radio resource control (RRC), medium access control layer control element (MAC CE) signaling or downlink control information (DCI).

[0296] In at least one embodiment, updating the model includes fine-tuning or training the model used.

[0297] In at least one embodiment, the information of the updated model includes: identification information (ID) and / or model version information of the updated model.

[0298] In at least one embodiment, the data includes original data and / or data obtained by quantifying the original data.

[0299] In at least one embodiment, the apparatus further comprises:

[0300] The switching unit 1003 is configured to switch the type of model used by the network device to perform corresponding processing.

[0301] In at least one embodiment, switching the type of model used includes:

[0302] Switch from an AI model to a non-AI model, or vice versa.

[0303] In at least one embodiment, the corresponding processing includes:

[0304] Generate channel state information, and / or beam management, and / or positioning.

[0305] In at least one embodiment, the information related to the management of the model used by the terminal device further includes:

[0306] The type of model used by the terminal device for switching to perform corresponding processing, and / or the moment when the switching of the terminal device takes effect, and / or the time interval between the moment when the switching of the terminal device takes effect and the moment when the network device receives the information related to the management of the model used by the terminal device, and / or the type and / or parameters of the model used after the switching of the terminal device.

[0307] In at least one embodiment, the information related to the management of the model used by the terminal device further includes:

[0308] The terminal device switches the model used to the updated model, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the time when the network device receives the information related to the management of the model used by the terminal device.

[0309] In at least one embodiment, the switching unit 1003 is further configured to switch the model used by the network device to a model corresponding to the updated model.

[0310] Embodiments of the fifth aspect

[0311] An embodiment of the fifth aspect of the present application provides a communication system, which may include a network device and a terminal device.

[0312] Figure 11 is a schematic diagram of a terminal device in a communication system according to an embodiment of the fifth aspect. As shown in Figure 11 , the terminal device 1100 (e.g., corresponding to the terminal device 202 in Figure 2 ) may include a processor 1110 and a memory 1120; the memory 1120 stores data and programs and is coupled to the processor 1110. It should be noted that this figure is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0313] For example, the processor 1110 may be configured to execute a program to implement the method in the embodiment of the first aspect.

[0314] As shown in Figure 11 , the terminal device 1100 may further include: a communication module 1130, an input unit 1140, a display 1150, and a power supply 1160. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1100 does not necessarily include all of the components shown in Figure 11 , and these components are not essential. Furthermore, the terminal device 1100 may also include components not shown in Figure 11 , for which reference may be made to the prior art.

[0315] FIG12 is a schematic diagram of a network device according to an embodiment of the fifth aspect. As shown in FIG12 , network device 1200 (e.g., corresponding to network device 201 in FIG2 ) may include a processor 1210 (e.g., a central processing unit (CPU)) and a memory 1220; the memory 1220 is coupled to the processor 1210. The memory 1220 may store various data and may also store an information processing program 1230, which is executed under the control of the processor 1210.

[0316] For example, the processor 1210 may be configured to execute a program to implement the method as described in the embodiment of the second aspect.

[0317] In addition, as shown in FIG12 , network device 1200 may further include: a transceiver 1240 and an antenna 1250, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1200 does not necessarily include all the components shown in FIG12 ; in addition, network device 1200 may also include components not shown in FIG12 , and reference may be made to the prior art for details.

[0318] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0319] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0320] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.

[0321] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.

[0322] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0323] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0324] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0325] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0326] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0327] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0328] Terminal-side method:

[0329] 1. A model management method, applied to a terminal device, comprising:

[0330] receiving configuration and / or scenario-related information sent by a network device; and

[0331] The model used by the terminal device is managed according to the configuration and / or scenario.

[0332] 1a. The method as described in Note 1, wherein:

[0333] The model is used to generate channel state information (CSI), and / or beam management, and / or positioning.

[0334] 1b. The method as described in Note 1, wherein:

[0335] The model is an artificial intelligence model,

[0336] The terminal device has and / or is capable of acquiring at least one of the models,

[0337] The model can be applicable to at least one configuration and / or at least one scenario.

[0338] 2. The method as described in Note 1, wherein:

[0339] The configuration includes an antenna configuration of the network device.

[0340] 3. The method as described in Note 2, wherein:

[0341] The antenna configuration is used to configure at least one of the following parameters of the antenna of the network device:

[0342] The number of antenna panels contained in one column of the antenna array;

[0343] The number of antenna panels contained in a row of the antenna array;

[0344] The distance between adjacent antenna panels in the horizontal direction;

[0345] The distance between adjacent antenna panels in the vertical direction;

[0346] The antenna array is a uniform antenna array or a non-uniform antenna array;

[0347] In an antenna panel, the number of antenna units contained in a column, and / or the number of antenna units contained in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna.

[0348] 4. The method as described in Note 2, wherein:

[0349] The number of the antenna configurations is one or more than one,

[0350] More than one antenna configuration has a corresponding antenna configuration identification number (ID), or the parameters of the antenna configuration and their corresponding values ​​are predefined.

[0351] 5. The method as described in Note 1, wherein:

[0352] The method further comprises:

[0353] Receive inquiry information sent by the network device, where the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is applicable to the configuration and / or scenario.

[0354] 5a. The method as described in Note 5, wherein:

[0355] The query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

[0356] 6. The method as described in Note 5, wherein:

[0357] Managing the model used by the terminal device, including:

[0358] Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and

[0359] The model used by the terminal device is reported to the network device as a result of model management, that the model is applicable to the configuration and / or scenario, or identification information (ID) corresponding to the result of the model management is reported to the network device.

[0360] 7. The method as described in Note 5, wherein:

[0361] Managing the model used by the terminal device, including:

[0362] Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and

[0363] Reporting to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is able to obtain a model applicable to the configuration and / or scenario.

[0364] 8. The method as described in Supplementary Note 7, wherein:

[0365] Managing the model used by the terminal device also includes:

[0366] Switching the model; and

[0367] After switching the model, reporting to the network device:

[0368] Message of successful model switching, and / or information of the model after switching, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the end time of this report, and / or the time interval between the time when the switching takes effect and the start time of this report.

[0369] 8a. The method as described in Note 8, wherein

[0370] Managing the model used by the terminal device also includes:

[0371] The switching of the model is reported to the network device as a result of model management, or identification information (ID) corresponding to the result of the model management is reported to the network device.

[0372] 8b. The method as described in Supplement 8, wherein:

[0373] Managing the model used by the terminal device also includes:

[0374] A switching command sent by the network device is received, where the switching command instructs the terminal device to switch the model.

[0375] 9. The method as described in Supplementary Note 8, wherein:

[0376] The information of the switched model corresponds to the configuration and / or scenario.

[0377] 10. The method as described in Note 5, wherein:

[0378] Managing the model used by the terminal device, including:

[0379] Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and

[0380] The model used by the terminal device to report to the network device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

[0381] 11. The method as described in Supplementary Note 10, wherein:

[0382] Managing the model used by the terminal device also includes:

[0383] updating the model based on data received from the network device and / or data downloaded; and

[0384] After the model is updated, a message indicating that the model has been updated successfully and information about the updated model are reported to the network device.

[0385] 11a. The method as described in Note 11, wherein:

[0386] Managing the model used by the terminal device also includes:

[0387] The updated model is reported to the network device as a result of model management, or identification information (ID) corresponding to the result of the model management is reported to the network device.

[0388] 11b. The method as described in Note 11, wherein:

[0389] The terminal device receives the data from the network device through signaling, or the terminal device receives the data from the network device in the form of data packets; or

[0390] The terminal device downloads the data from a public server or a server with intellectual property (IP).

[0391] 11b1. The method as described in Note 11b, wherein

[0392] The signaling includes: radio resource control (RRC), media access control layer control element (MAC CE) signaling or downlink control information (DCI).

[0393] 11c. The method as described in Note 11, wherein:

[0394] Updating the model includes fine-tuning or training the model in use.

[0395] 11d. The method as described in Note 11, wherein:

[0396] The information of the updated model includes: identification information (ID) and / or model version information of the updated model.

[0397] 12. The method as described in Note 11, wherein:

[0398] The received data and / or the downloaded data include original data and / or data obtained by quantizing the original data.

[0399] 13. The method as described in Note 11, wherein:

[0400] Managing the model used by the terminal device also includes:

[0401] Switches the type of model used to process accordingly.

[0402] 13a. The method of claim 13, wherein switching the type of model used comprises:

[0403] Switch from an AI model to a non-AI model, or vice versa.

[0404] 13b. The method as described in Note 13, wherein:

[0405] The corresponding processing includes:

[0406] Generate channel state information, and / or beam management, and / or positioning.

[0407] 14. The method as described in Note 13, wherein:

[0408] Managing the model used by the terminal device also includes:

[0409] Before switching the type of model used, report to the network device:

[0410] The terminal device switches the type of model used to perform corresponding processing, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the end time of this report, and / or the time interval between the time when the switch takes effect and the start time of this report, and / or the type and / or parameters of the model used after the switch.

[0411] 15. The method as described in Note 13, wherein:

[0412] Managing the model used by the terminal device also includes:

[0413] After the model is updated, the used model is switched to the updated model, and the following information is reported to the network device:

[0414] The terminal device switches the model used to the updated model, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the end time of this report, and / or the time interval between the time when the switch takes effect and the start time of this report.

[0415] 16. A method for antenna configuration, comprising:

[0416] Define a parameter name corresponding to at least one antenna configuration parameter.

[0417] Method on the network device side:

[0418] 1. A model management method, applied to a network device, comprising:

[0419] Sending configuration and / or scenario-related information to the terminal device; and

[0420] Receive information related to management of a model used by the terminal device by the terminal device according to the configuration and / or scenario.

[0421] 1a. The method as described in Note 1, wherein:

[0422] The model is used to generate channel state information (CSI), and / or beam management, and / or positioning.

[0423] 1b. The method as described in Note 1, wherein:

[0424] The model is an artificial intelligence model,

[0425] The terminal device has and / or is capable of acquiring at least one of the models,

[0426] The model can be applicable to at least one configuration and / or at least one scenario.

[0427] 2. The method as described in Note 1, wherein:

[0428] The configuration includes an antenna configuration of the network device.

[0429] 3. The method as described in Note 2, wherein:

[0430] The antenna configuration is used to configure at least one of the following parameters of the antenna of the network device:

[0431] The number of antenna panels contained in one column of the antenna array;

[0432] The number of antenna panels contained in a row of the antenna array;

[0433] The distance between adjacent antenna panels in the horizontal direction;

[0434] The distance between adjacent antenna panels in the vertical direction;

[0435] The antenna array is a uniform antenna array or a non-uniform antenna array;

[0436] In an antenna panel, the number of antenna units contained in a column, and / or the number of antenna units contained in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna.

[0437] 4. The method as described in Note 2, wherein:

[0438] The number of the antenna configurations is one or more than one,

[0439] More than one antenna configuration has a corresponding antenna configuration identification number (ID), or the parameters of the antenna configuration and their corresponding values ​​are predefined.

[0440] 5. The method as described in Note 1, wherein:

[0441] The method further comprises:

[0442] Sending inquiry information to the terminal device, wherein the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is suitable for the configuration and / or scenario.

[0443] 5a. The method as described in Note 5, wherein:

[0444] The query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

[0445] 6. The method as described in Note 5, wherein:

[0446] The terminal device manages information related to the model used, including:

[0447] The result of model management, or identification information (ID) corresponding to the result of model management,

[0448] The result of the model management includes: the model used by the terminal device is suitable for the configuration and / or scenario.

[0449] 7. The method as described in Note 5, wherein:

[0450] The terminal device manages information related to the model used, including:

[0451] The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is capable of acquiring a model applicable to the configuration and / or scenario.

[0452] 8. The method as described in Supplementary Note 7, wherein:

[0453] The terminal device manages the information related to the model used, and further includes:

[0454] The message of successful model switching, and / or information of the model after switching, and / or the time when the switching takes effect, and / or the time interval between the time when the switching takes effect and the time when the network device receives the information related to the management of the model used by the terminal device.

[0455] 8a. The method as described in Note 8, wherein

[0456] The terminal device manages the information related to the model used, and further includes:

[0457] The result of model management, or identification information (ID) corresponding to the result of model management,

[0458] The result of the model management includes: switching the model.

[0459] 8b. The method as described in Supplement 8, wherein:

[0460] The method further comprises:

[0461] A switching command is sent to the terminal device, where the switching command instructs the terminal device to switch the model.

[0462] 9. The method as described in Supplementary Note 8, wherein:

[0463] The information of the switched model corresponds to the configuration and / or scenario.

[0464] 10. The method as described in Note 5, wherein:

[0465] The terminal device manages information related to the model used, including:

[0466] The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

[0467] 11. The method as described in Supplementary Note 10, wherein:

[0468] The terminal device manages the information related to the model used, and further includes:

[0469] A message indicating that the model has been successfully updated and information about the updated model.

[0470] 11a. The method as described in Note 11, wherein:

[0471] The terminal device manages the information related to the model used, and further includes:

[0472] The result of model management, or identification information (ID) corresponding to the result of model management,

[0473] The result of the model management includes: updating the model.

[0474] 11b. The method as described in Note 11, wherein:

[0475] The method further comprises:

[0476] The network device sends data for updating the model to the terminal device through signaling or in the form of data packets.

[0477] 11b1. The method as described in Note 11b, wherein

[0478] The signaling includes: radio resource control (RRC), media access control layer control element (MAC CE) signaling or downlink control information (DCI).

[0479] 11c. The method as described in Note 11, wherein:

[0480] Updating the model includes fine-tuning or training the model in use.

[0481] 11d. The method as described in Note 11, wherein:

[0482] The information of the updated model includes: identification information (ID) and / or model version information of the updated model.

[0483] 12. The method as described in Note 11b, wherein:

[0484] The data includes original data and / or data obtained by quantifying the original data.

[0485] 13. The method as described in Note 11, wherein:

[0486] The method further comprises:

[0487] Toggles the type of model used by the network device to process accordingly.

[0488] 13a. The method of claim 13, wherein switching the type of model used comprises:

[0489] Switch from an AI model to a non-AI model, or vice versa.

[0490] 13b. The method as described in Note 13, wherein:

[0491] The corresponding processing includes:

[0492] Generate channel state information, and / or beam management, and / or positioning.

[0493] 14. The method as described in Note 13, wherein:

[0494] The terminal device manages the information related to the model used, and further includes:

[0495] The type of model used by the terminal device for switching to perform corresponding processing, and / or the moment when the switching of the terminal device takes effect, and / or the time interval between the moment when the switching of the terminal device takes effect and the moment when the network device receives the information related to the management of the model used by the terminal device, and / or the type and / or parameters of the model used after the switching of the terminal device.

[0496] 15. The method as described in Note 13, wherein:

[0497] The terminal device manages the information related to the model used, and further includes:

[0498] The terminal device switches the model used to the updated model, and / or the time when the switch takes effect, and / or the time interval between the time when the switch takes effect and the time when the network device receives the information related to the management of the model used by the terminal device.

[0499] 16. The method as described in Note 15, wherein:

[0500] The method further comprises:

[0501] The network device switches the model used to a model corresponding to the updated model.

Claims

1. A model management device, applied to a terminal device, comprising: a first receiving unit configured to receive information related to configuration and / or scenario sent by a network device; as well as A management unit is configured to manage the model used by the terminal device according to the configuration and / or scenario.

2. The device according to claim 1, wherein The model is used to generate channel state information (CSI), and / or beam management, and / or positioning.

3. The device according to claim 1, wherein The model is an artificial intelligence model, The terminal device has and / or is capable of acquiring at least one of the models, The model can be applicable to at least one configuration and / or at least one scenario.

4. The device according to claim 1, wherein The configuration includes an antenna configuration of the network device.

5. The device according to claim 4, wherein The antenna configuration is used to configure at least one of the following parameters of the antenna of the network device: The number of antenna panels contained in one column of the antenna array; The number of antenna panels contained in a row of the antenna array; The distance between adjacent antenna panels in the horizontal direction; The distance between adjacent antenna panels in the vertical direction; The antenna array is a uniform antenna array or a non-uniform antenna array; In an antenna panel, the number of antenna units contained in a column, and / or the number of antenna units contained in a row, and / or the distance between adjacent antennas in the horizontal direction, and / or the distance between adjacent antennas in the vertical direction, and / or whether the antennas in the antenna panel are single-polarized or dual-polarized, and / or the tilt angle of the dual-polarized antenna.

6. The device according to claim 4, wherein The number of the antenna configurations is one or more than one, More than one antenna configuration has a corresponding antenna configuration identification number (ID), or the parameters of the antenna configuration and their corresponding values ​​are predefined.

7. The device according to claim 1, wherein The first receiving unit is further configured to: Receive inquiry information sent by the network device, where the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is applicable to the configuration and / or scenario.

8. The device according to claim 7, wherein The query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

9. The device according to claim 7, wherein Managing the model used by the terminal device, including: Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and The model used by the terminal device is reported to the network device as a result of model management, that the model is applicable to the configuration and / or scenario, or identification information (ID) corresponding to the result of the model management is reported to the network device.

10. The device according to claim 7, wherein Managing the model used by the terminal device, including: Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and Reporting to the network device that the model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is able to obtain a model applicable to the configuration and / or scenario.

11. The device according to claim 7, wherein Managing the model used by the terminal device, including: Verifying whether the model used by and / or owned by and / or accessible to the terminal device is applicable to the configuration and / or scenario; and The model used by the terminal device to report to the network device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

12. A model management device, applied to a network device, comprising: A first sending unit, configured to send information related to the configuration and / or scenario to the terminal device; as well as The second receiving unit is configured to receive information related to management of the model used by the terminal device by the terminal device according to the configuration and / or scenario.

13. The device of claim 12, wherein: The model is used to generate channel state information (CSI), and / or beam management, and / or positioning.

14. The apparatus of claim 12, wherein: The model is an artificial intelligence model, The terminal device has and / or is capable of acquiring at least one of the models, The model can be applicable to at least one configuration and / or at least one scenario.

15. The apparatus of claim 12, wherein: The configuration includes an antenna configuration of the network device.

16. The apparatus of claim 12, wherein: The first sending unit is further configured to: Sending inquiry information to the terminal device, wherein the inquiry information is used to inquire whether the model used and / or owned and / or obtainable by the terminal device is suitable for the configuration and / or scenario.

17. The apparatus of claim 16, wherein: The query information includes the information related to the configuration and / or scenario, or the query information does not include the information related to the configuration and / or scenario.

18. The apparatus of claim 16, wherein: The terminal device manages information related to the model used, including: The result of model management, or identification information (ID) corresponding to the result of model management, The result of the model management includes: the model used by the terminal device is suitable for the configuration and / or scenario.

19. The apparatus of claim 16, wherein: The terminal device manages information related to the model used, including: The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device has and / or is capable of acquiring a model applicable to the configuration and / or scenario.

20. The apparatus of claim 16, wherein: The terminal device manages information related to the model used, including: The model used by the terminal device is not applicable to the configuration and / or scenario, and the terminal device does not have and / or cannot obtain a model applicable to the configuration and / or scenario.

Images