Wireless communication methods, terminal devices, access network devices and core network devices

Abstract

Provided are wireless communication methods, terminal devices, access network devices, and core network devices. A method comprises: a terminal device sends first information to a network device, the first information comprising a first identifier, and the first identifier being associated with model deployment information of the terminal device. In the embodiments of the present application, introducing the identifier associated with the model deployment information can simplify the indication of the model deployment information of the terminal device.

Description

Wireless communication method, terminal equipment, access network equipment and core network equipment Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, access network equipment, and core network equipment. Background Art

[0002] As technology evolves, terminal devices will deploy one or more models. The question of how to indicate the model deployment information of terminal devices to network devices is a problem that needs to be solved.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a wireless communication method, a terminal device, an access network device, and a core network device. The following describes in detail various aspects of the embodiments of the present application.

[0005] In a first aspect, a wireless communication method is provided, comprising: a terminal device sends first information to a network device, wherein the first information includes a first identifier, and the first identifier is associated with model deployment information of the terminal device.

[0006] In a second aspect, a wireless communication method is provided, including: a first core network device receives first information sent by a terminal device, the first information includes a first identifier, and the first identifier is associated with model deployment information of the terminal device.

[0007] According to a third aspect, a wireless communication method is provided, including: a first access network device receives third information sent by a first core network device, the third information includes a fourth identifier, the information contained in the fourth identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0008] In a fourth aspect, a wireless communication method is provided, including: a first access network device receives first information sent by a terminal device, the first information includes a first identifier, and the first identifier is associated with model deployment information of the terminal device.

[0009] In the fifth aspect, a wireless communication method is provided, including: a first core network device receives sixth information sent by a first access network device, the sixth information includes a seventh identifier, the information contained in the seventh identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0010] In a sixth aspect, a terminal device is provided, comprising: a communication module for sending first information to a network device, wherein the first information comprises a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0011] In the seventh aspect, a core network device is provided, which is a first core network device. The first core network device includes: a communication module for receiving first information sent by a terminal device, the first information includes a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0012] In the eighth aspect, an access network device is provided, which is a first access network device, and the first access network device includes: a communication module for receiving third information sent by a first core network device, the third information includes a fourth identifier, the information contained in the fourth identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0013] In the ninth aspect, an access network device is provided, which is a first access network device, and the first access network device includes: a communication module for receiving first information sent by a terminal device, the first information includes a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0014] In the tenth aspect, a core network device is provided, which is a first core network device, and the first core network device includes: a communication module for receiving sixth information sent by a first access network device, the sixth information includes a seventh identifier, and the information contained in the seventh identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0015] In the eleventh aspect, a terminal device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes the method described in the first aspect.

[0016] In the twelfth aspect, a core network device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the core network device executes the method as described in any one of the second and fifth aspects.

[0017] In the thirteenth aspect, an access network device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the access network device executes the method as described in any one of the third and fourth aspects.

[0018] In a fourteenth aspect, a device is provided, comprising a processor for calling a program from a memory so that the device executes a method as described in any one of the first to fifth aspects.

[0019] In the fifteenth aspect, a chip is provided, characterized in that it includes a processor for calling a program from a memory so that a device equipped with the chip executes a method as described in any one of the first to fifth aspects.

[0020] In the sixteenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in any one of the first to fifth aspects.

[0021] In the seventeenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in any one of the first to fifth aspects.

[0022] In aspect 18, a computer program is provided, which enables a computer to execute the method as described in any one of aspects 1 to 5.

[0023] The embodiment of the present application introduces an identifier associated with model deployment information, which can simplify the indication of model deployment information of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0025] FIG2 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0026] FIG3 is a flow chart of a possible implementation of FIG2 .

[0027] FIG4 is a flow chart of another possible implementation of FIG2 .

[0028] FIG5 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.

[0029] FIG6 is a schematic diagram of the structure of a core network device provided in one embodiment of the present application.

[0030] FIG7 is a schematic diagram of the structure of an access network device provided in one embodiment of the present application.

[0031] FIG8 is a schematic structural diagram of an access network device provided in another embodiment of the present application.

[0032] FIG9 is a schematic structural diagram of a core network device provided in another embodiment of the present application.

[0033] FIG10 is a schematic structural diagram of a device that can be used in an embodiment of the present application. DETAILED DESCRIPTION

[0034] The technical solution in this application will be described below with reference to the accompanying drawings.

[0035] Communication system architecture

[0036] FIG1 is a diagram illustrating an exemplary system architecture of a wireless communication system 100 to which embodiments of the present application may be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0037] FIG1 exemplarily shows a network device and a terminal device. Optionally, the wireless communication system 100 may include one or more network devices 110 and / or one or more terminal devices 120. For a network device 110, the one or more terminal devices 120 may all be located within the network coverage of the network device 110, or all be located outside the network coverage of the network device 110, or some may be located within the coverage of the network device 110 and others outside the network coverage of the network device 110. This is not limited in the embodiments of the present application.

[0038] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0039] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0040] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0041] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0042] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0043] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0044] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0045] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0046] Definition of terminal equipment capability information in communication systems

[0047] Communication systems (such as 5G) have many functions, some of which are mandatory functions of terminal devices, but most of them are optional functions of terminal devices. Terminal devices generally indicate which optional functions they support through the capability information reporting process. Different functions can be indicated through different capability information fields. The coding position and specific capability meaning of all capability information fields contained in the terminal device capability information are predefined by the protocol. In other words, if the terminal device needs to indicate a new device capability (for example, the terminal device supports a new optional function), this device capability needs to be defined through the protocol pre-defined process through coding rules (that is, defining the coding position and specific capability meaning of the capability information field). Otherwise, the network device cannot understand the newly defined capabilities of the terminal device.

[0048] The number and / or types of models (such as artificial intelligence (AI) models) deployed on terminal devices may change dynamically (e.g., due to updates to terminal device software and / or hardware). If terminal devices notify network devices of changes to their model deployment information through capability information reporting, this requires pre-definition through a protocol before updated capability information can be reported. On the one hand, defining new terminal device capabilities requires a standardization process. If different companies disagree, it may be impossible to introduce new terminal device model capabilities required by certain terminal device or chip manufacturers, resulting in the development of these terminal devices or chips being constrained by the standards discussion process (i.e., without a standard in place, there can be no product upgrades, which is not in the manufacturer's commercial interests). On the other hand, the model deployment and update processes of terminal device or chip manufacturers may simply be individual commercial activities. Forcing all terminal device or chip manufacturers to update their capabilities through a standardization process is neither in line with commercial competition nor conducive to protecting the independent innovation of individual manufacturers.

[0049] From another perspective, if the above-mentioned terminal device model deployment information update is completely carried out through implementation, it will bring huge challenges to the model deployment information update of network equipment or operators, because network equipment or operators need to obtain the model deployment update status of each terminal device manufacturer or chip manufacturer that has joined the network through implementation, and even the model deployment update status of each terminal device (subsequent information updates must also be considered). In a sense, it is difficult for network equipment or operators to meet the above requirements and they have no motivation to meet the above requirements, because a large amount of offline information interaction requires additional manpower and material resources, which is obviously not a method that network equipment manufacturers or operators are willing to bear. Therefore, a simple implementation solution cannot solve the above-mentioned information interaction problem well.

[0050] Based on the above analysis, the standard requires a model deployment information indication or update method that takes into account both terminal equipment manufacturers (and / or chip manufacturers) and network manufacturers (and / or operators). This application aims to overcome the shortcomings of the above solutions.

[0051] Example 1:

[0052] Figure 2 is a flow chart of a wireless communication method provided in Example 1 of the present application. The method in Figure 2 can be executed by a terminal device and a network device.

[0053] The network devices mentioned in Figure 2 can be access network devices or core network devices. For example, if the network device is an access network device, the access network device can be any of the following: a base station (e.g., a gNB), a centralized unit (CU), a distributed unit (DU), a centralized unit-control plane (CU-CP), or a centralized unit-user plane (CU-UP). Taking the network device as a core network device as an example, the core network device is any one of the following: location management function (LMF) network element, network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), user plane function (UPF), sensing function (SF), network data analytics function (NWDAF), and AI function management entity.

[0054] Referring to Figure 2, in step S210, a terminal device sends first information to a network device. In response, the network device receives the first information sent by the terminal device. The first information includes a first identifier. The first identifier is associated with the model deployment information of the terminal device. In other words, the first identifier is used to determine the model deployment status of the terminal device.

[0055] It should be noted that the models mentioned in each embodiment of the present application may refer to AI models and / or machine learning (ML) models.

[0056] The model deployment information of a terminal device can be used to indicate the model deployment status of the terminal device. For example, the model deployment information of a terminal device can indicate one or more models that have been deployed on the terminal device. Alternatively, the model deployment information of a terminal device can indicate the model information actually available to the terminal device.

[0057] In some implementations, the first identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0058] In some implementations, the first identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0059] According to the embodiments of the present application, on the one hand, from the perspective of terminal device manufacturers or chip manufacturers, the update of model deployment information supported by terminal devices does not depend on the enhancement of standard protocols. The first information only provides one or more logical identifiers. The model deployment information associated with each logical identifier is not fixed. The terminal device or model provider can dynamically change the model deployment information content associated with a logical identifier at any time through an inter-manufacturer agreement. This method indirectly provides the model deployment information of the terminal device (the network device can determine the associated model deployment information based on the logical identifier provided by the terminal device), so that the network device can perform corresponding management operations for specific terminal devices, such as: model activation, model deactivation, model switching and other operations, and also provides the possibility for the business level to dynamically update the model deployment information content associated with a logical identifier, so as to facilitate product developers to provide non-standard product upgrades and respond to users' product experience improvement needs in a timely manner.

[0060] On the other hand, from the perspective of network equipment manufacturers or operators, the solution provided in the embodiments of the present application avoids the cost burden brought to network equipment manufacturers or operators by obtaining the model deployment information supported by terminal devices in a completely implementation-based manner, because obtaining the model deployment information supported by terminal devices in a completely implementation-based manner means that network equipment manufacturers or operators need to invest a lot of manpower and material resources to obtain and maintain the above information offline, and even need to obtain and maintain model deployment information according to the granularity of terminal devices. Compared with the logical identifier mapping method, the cost of the completely implementation-based method is higher. Therefore, the model deployment information provision method based on logical identifiers not only indirectly provides the model deployment information of the terminal device to the network equipment manufacturers or operators (the network device can determine the associated model deployment information based on the logical identifier provided by the terminal device), so that the network device can perform corresponding model management operations for specific terminal devices, but also saves network operating costs compared to obtaining model deployment information based on implementation.

[0061] As mentioned above, the network device in Figure 2 can be a core network device or an access network device. The following describes in detail possible implementations of Example 1, taking the network device as a core network device and an access network device as examples, respectively, in conjunction with Example 2 and Example 3.

[0062] Example 2: The terminal device sends the first information to the first core network device

[0063] As shown in Figure 3, in Example 2, step S210 in Example 1 may include or be replaced by step S310, i.e., the terminal device sends the first information to the first core network device, and accordingly, the first core network device receives the first information sent by the terminal device. For a description of the first information, see Example 1 and Examples 5 to 9 below.

[0064] In some implementations, after receiving the first information, the first core network device stores the first information in the context information of the terminal device.

[0065] The first information is stored in the core network device, and the terminal device does not need to report the first model related information to the core network device or the access network device every time it enters the connected state, thereby saving the terminal device information reporting overhead.

[0066] In some implementations, the first core network device sends the second information to the second core network device, and correspondingly, the second core network device receives the second information sent by the first core network device. The second information includes a third identifier.

[0067] The third identifier is associated with the model deployment information of the terminal device. In other words, the third identifier is used to determine the model deployment status of the terminal device.

[0068] In some implementations, the third identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0069] In some implementations, the third identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0070] In some implementations, the information included in the third identifier is a subset of the information included in the first identifier. In other words, the third identifier may include some or all of the information in the first identifier.

[0071] When the core network device serving the terminal device changes (for example, due to the mobility of the terminal device), in order to avoid the terminal device reporting the first information to the new core network device again, the old core network device can transmit the second information to the new core network device, thereby reducing the terminal device information reporting overhead. For example, when the old core network device knows that the new core network device only supports a partial model set, the third identifier can include part of the information in the first identifier.

[0072] In some implementations, the first core network device sends the third information to the first access network device, and correspondingly, the first access network device receives the third information sent by the first core network device. The third information includes one or more of the following: a fourth identifier, a model identifier, and model description information.

[0073] In some implementations, the fourth identifier is associated with the model deployment information of the terminal device. In other words, the fourth identifier is used to indicate the model deployment status of the terminal device.

[0074] In some implementations, the fourth identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0075] In some implementations, the fourth identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0076] In some implementations, the information included in the fourth identifier may be a subset of the information included in the first identifier. That is, the fourth identifier may include some or all of the information in the first identifier. For example, when the first core network device knows that the first access network device only supports a partial set of models, the fourth identifier may include some of the information in the first identifier.

[0077] In some implementations, the model identifier in the third information may be used to identify one or more models in the model deployment information.

[0078] In some implementations, the model identifier in the third information may be used to identify one or more models in a model set supported by the terminal device.

[0079] In some implementations, the model description information in the third information may be used to describe one or more models in the model deployment information or in the model set. A detailed description of the model description information is provided in Example 4 below and will not be described in detail here.

[0080] In some implementations, the first access network device locally maintains a mapping relationship between the fourth identifier, the model identifier, and the model description information. In this case, the third information only needs to include the fourth identifier.

[0081] In some implementations, the first access network device does not locally maintain the mapping relationship between the fourth identifier, the model identifier, and the model description information. In this case, the third information needs to include the fourth identifier, the model identifier, and the model description information, or only include the model identifier and model description information associated with the fourth identifier.

[0082] After the first access network device obtains the third information from the first core network device, the first access network device can perform model control operations at the terminal device granularity, such as model activation, model deactivation, and model switching.

[0083] In some implementations, after the first access network device receives the third information, it may send fourth information to the second access network device. Correspondingly, the second access network device receives the fourth information sent by the first access network device. The fourth information may include one or more of the fifth identifier, the model identifier, and the model description information.

[0084] In some implementations, the fifth identifier is associated with the model deployment information of the terminal device. In other words, the fifth identifier is used to indicate the model deployment status of the terminal device.

[0085] In some implementations, the fifth identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0086] In some implementations, the fifth identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0087] In some implementations, the information included in the fifth identifier may be a subset of the information included in the fourth identifier. That is, the fifth identifier may include some or all of the information in the fourth identifier. For example, when the first access network device knows that the second access network device only supports a partial set of models, the fifth identifier may include some of the information in the fourth identifier.

[0088] In some implementations, the model identifier in the fourth information may be used to identify one or more models in the model deployment information.

[0089] In some implementations, the model identifier in the fourth information may be used to identify one or more models in a model set supported by the terminal device.

[0090] In some implementations, the model description information in the fourth information may be used to describe one or more models in the model deployment information or in the model set. A detailed description of the model description information is provided in Example 4 below and is not described in detail here.

[0091] In some implementations, the second access network device locally maintains a mapping relationship between the fifth identifier, the model identifier, and the model description information. In this case, the fourth information only needs to include the fifth identifier.

[0092] In some implementations, the second access network device does not locally maintain the mapping relationship between the fifth identifier, the model identifier, and the model description information. In this case, the fourth information needs to include the fifth identifier, the model identifier, and the model description information, or only include the model identifier and model description information associated with the fifth identifier.

[0093] After the new access network device (corresponding to the above-mentioned second access network device) obtains the fourth information from the old access network device (corresponding to the above-mentioned first access network device), the new access network device can perform terminal device-granular model control operations, such as: model activation, model deactivation, and model switching, thereby avoiding the terminal device from re-reporting the first information after changing the service cell due to mobility reasons, and ensuring the continuity of the model control information (such as AI control information) in the access network device information interaction process.

[0094] Example 3: The terminal device sends the first information to the first access network device

[0095] As shown in Figure 4, in Example 3, step S210 in Example 1 may include or be replaced by step S410, i.e., the terminal device sends the first information to the first access network device, and accordingly, the first access network device receives the first information sent by the terminal device. For a description of the first information, see Example 1 and Examples 5 to 9 below.

[0096] Compared with Example 2, Example 3 sends the first information to the access network device, which can shorten the transmission delay of the first information. On the other hand, the model deployment information related to the terminal device is directly sent to the access network device, and the information is used more promptly.

[0097] In some implementations, the first access network device stores the first information in the context information of the terminal device. In some implementations, after receiving the first information, the first access network device may send fifth information to the second access network device. Accordingly, the second access network device receives the fifth information sent by the first access network device. The fifth information includes one or more of the following: a sixth identifier, a model identifier, and model description information.

[0098] In some implementations, the sixth identifier is associated with the model deployment information of the terminal device. In other words, the sixth identifier is used to indicate the model deployment status of the terminal device.

[0099] In some implementations, the sixth identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0100] In some implementations, the sixth identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0101] In some implementations, the information included in the sixth identifier may be a subset of the information included in the first identifier. That is, the sixth identifier may include some or all of the information in the first identifier. For example, when the first access network device knows that the second access network device only supports a partial set of models, the sixth identifier may include some of the information in the first identifier.

[0102] In some implementations, the model identifier in the fifth information may be used to identify one or more models in the model deployment information.

[0103] In some implementations, the model identifier in the fifth information may be used to identify one or more models in a model set supported by the terminal device.

[0104] In some implementations, the model description information in the fifth information may be used to describe one or more models in the model deployment information or in the model set. A detailed description of the model description information is provided in Example 4 below and will not be described in detail here.

[0105] In some implementations, the second access network device locally maintains a mapping relationship between the sixth identifier, the model identifier, and the model description information. In this case, the fifth information only needs to include the sixth identifier.

[0106] In some implementations, the second access network device does not locally maintain the mapping relationship between the sixth identifier, the model identifier, and the model description information. In this case, the fifth information needs to include the sixth identifier, the model identifier, and the model description information, or only include the model identifier and model description information associated with the sixth identifier.

[0107] After the new access network device (corresponding to the second access network device mentioned above) obtains the fifth information from the old access network device (corresponding to the first access network device mentioned above), the new access network device can perform terminal device-granular model control operations, such as: model activation, model deactivation, and model switching, thereby avoiding the terminal device from re-reporting the first information after changing the service cell due to mobility reasons, and ensuring the continuity of the model control information (such as AI control information) in the access network device information interaction process.

[0108] In some implementations, after receiving the first information, the first access network device can send the sixth information to the first core network device. Accordingly, the first core network device receives the sixth information sent by the first access network device, and the sixth information includes one or more of the following: a seventh identifier, a model identifier, and a model description information.

[0109] In some implementations, the seventh identifier is associated with the model deployment information of the terminal device. In other words, the seventh identifier is used to indicate the model deployment status of the terminal device.

[0110] In some implementations, the seventh identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0111] In some implementations, the seventh identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0112] In some implementations, the information included in the seventh identifier may be a subset of the information included in the first identifier. That is, the seventh identifier may include some or all of the information in the first identifier. For example, when the first access network device knows that the first core network device only supports a partial set of models, the seventh identifier may include some of the information in the first identifier.

[0113] In some implementations, the model identifier in the sixth information may be used to identify one or more models in the model deployment information.

[0114] In some implementations, the model identifier in the sixth information may be used to identify one or more models in a model set supported by the terminal device.

[0115] In some implementations, the model description information in the sixth information may be used to describe one or more models in the model deployment information or in the model set. A detailed description of the model description information is provided in Example 4 below and will not be described in detail here.

[0116] In some implementations, the sixth information only needs to include the seventh identifier.

[0117] In some implementations, the sixth information needs to include the seventh identifier, the model identifier, and the model description information, or include the model identifier and the model description information associated with the seventh identifier.

[0118] The transmission of the sixth information can avoid the need for the terminal device to report the first information again each time it enters the connected state, because the terminal device will send the sixth information to the core network device for storage before leaving the connected state each time. When it enters the connected state again subsequently, the core network device will provide all or part of the saved sixth information to the new access network device for use.

[0119] In some implementations, a third access network device (the same as or different from the first access network device) receives the seventh information sent by the first core network device, and in response, the first core network device sends the seventh information to the third access network device. The seventh information includes one or more of the following: an eighth identifier, a model identifier, and model description information.

[0120] In some implementations, the eighth identifier is associated with the model deployment information of the terminal device. In other words, the eighth identifier is used to indicate the model deployment status of the terminal device.

[0121] In some implementations, the eighth identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0122] In some implementations, the eighth identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0123] In some implementations, the information included in the eighth identifier may be a subset of the information included in the seventh identifier. That is, the eighth identifier may include some or all of the information in the seventh identifier. For example, when the first core network device knows that the third access network device only supports a partial model set, the eighth identifier may include some of the information in the seventh identifier.

[0124] In some implementations, the model identifier in the seventh information may be used to identify one or more models in the model deployment information.

[0125] In some implementations, the model identifier in the seventh information may be used to identify one or more models in a model set supported by the terminal device.

[0126] In some implementations, the model description information in the seventh information may be used to describe one or more models in the model deployment information or in the model set. A detailed description of the model description information is provided in Example 4 below and will not be described in detail here.

[0127] In some implementations, the seventh information only needs to include the eighth identifier.

[0128] In some implementations, the seventh information needs to include the eighth identifier, the model identifier, and the model description information, or include the model identifier and the model description information associated with the eighth identifier.

[0129] In some implementations, the first core network device sends the eighth information to the second core network device, and correspondingly, the second core network device receives the eighth information sent by the first core network device. The eighth information includes one or more of the following: a ninth identifier, a model identifier, and model description information.

[0130] In some implementations, the ninth identifier is associated with the model deployment information of the terminal device. In other words, the ninth identifier is used to indicate the model deployment status of the terminal device.

[0131] In some implementations, the ninth identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0132] In some implementations, the ninth identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0133] In some implementations, the information included in the ninth identifier may be a subset of the information included in the seventh identifier. That is, the ninth identifier may include some or all of the information in the seventh identifier. For example, when the first core network device knows that the second core network device only supports a partial set of models, the ninth identifier may include some of the information in the seventh identifier.

[0134] In some implementations, the model identifier in the eighth information may be used to identify one or more models in the model deployment information.

[0135] In some implementations, the model identifier in the eighth information may be used to identify one or more models in a model set supported by the terminal device.

[0136] In some implementations, the model description information in the eighth information may be used to describe one or more models in the model deployment information or in the model set. A detailed description of the model description information is provided in Example 4 below and will not be described in detail here.

[0137] In some implementations, the eighth information only needs to include the ninth identifier.

[0138] In some implementations, the eighth information needs to include the ninth identifier, the model identifier, and the model description information, or include the model identifier and the model description information associated with the ninth identifier.

[0139] When the core network device serving the terminal device changes, the above process maintains the continuity of model deployment information maintenance between different core networks, avoids the terminal device from reporting the first information again, and saves air interface information reporting overhead.

[0140] Example 4: Model Description Information (Applicable to Any of Examples 1 to 3)

[0141] In some implementations, the model description information includes one or more of the following information: information indicating the function of the model; information indicating the type of the input parameters of the model; information indicating the format of the input parameters of the model; information indicating the preprocessing rules of the input parameters of the model; information indicating the type of the output parameters of the model; information indicating the format requirements of the output parameters of the model; information indicating the preprocessing rules of the output parameters of the model; information indicating the application scenario of the model; information indicating the deployment location of the model; information indicating the capability requirements for using the model; information indicating the performance monitoring indicators of the model; information indicating the location of the model; information indicating the effective use scope of the model; information indicating the generalization characteristics of the model; information indicating the version of the model; information indicating the accuracy of the model; information indicating the compilation format of the model data; information indicating the storage format of the model data; information indicating the computational complexity of the model; information indicating the model complexity of the model; information indicating the size of the model.

[0142] The following provides detailed examples of the information that may be included in the model description information.

[0143] Information 1: Information indicating the function of the model

[0144] Information 1 may be used to indicate the function or functional characteristics associated with the corresponding model. For example, model 1 is used for channel state information (CSI) compression feedback function, model 2 is used for mobility enhancement function, model 3 is used for beam prediction function, model 4 is used for positioning function, etc.

[0145] Information 2: Information indicating the type of input parameters of the model

[0146] Information 2 can be used to indicate the types of input parameters required by the corresponding model. For example, Model 3 is used for beam prediction, and the required input parameters include the index information of the actual measured beam and the signal measurement results of each beam obtained by actual measurement.

[0147] Information 3: Information indicating the format of the model's input parameters

[0148] Information 3 can be used to indicate the format of the input parameters required by the corresponding model. For example, if Model 3 is used for beam prediction, and the network device can schedule resources in eight beam directions but only sends measurement reference signals in four of them, the terminal device can only obtain measurement results for four beams in each measurement process.

[0149] Scenario 1: The beam prediction model only predicts the signal measurement results of other beams that have not been measured at the current moment. If the beam prediction model used in Scenario 1 only needs to input the measurement results of 4 beams, then the measurement results of 4 beams obtained by the terminal device in each measurement can be used as the input of the beam prediction model in Scenario 1 (the output can obtain the measurement results of the 8 beams associated with this measurement, that is: 4 true values, 4 predicted values, or the output is the measurement results of the predicted 4 beams).

[0150] Scenario 2: The beam prediction model is used to predict the measurement results of 8 beams in the future. In this scenario, the input of the beam prediction model may be the set of measurement results of 4 beams obtained in the past N measurement processes, and the output of the beam prediction model is the set of measurement results of 8 beams in the future. For example, the input of the beam prediction model is the set of three sets of measurement results of 4 beams obtained at time T-3, T-2, and T-1, and the output of the beam prediction model is the set of two sets of measurement results of 8 beams at time T and time T+1.

[0151] In summary, although beam prediction is performed using the same measurement results for the four beams (the model input parameter types are the same), different application scenarios require different input data formats. Therefore, the input parameter format requirements associated with the model are also one of the key information in describing the model.

[0152] Information 4: Information indicating the preprocessing rules of the model's input parameters

[0153] Information 4 may be used to indicate how to reprocess the input data set of the corresponding model. The operations involved in the reprocessing process may include at least one of data dimensionality reduction, data dimensionality increase, redundancy elimination, and redistribution.

[0154] Data dimensionality reduction: If the data dimension is higher than the dimension required by the model input, the data needs to be reduced in dimension through preprocessing rules before entering the model;

[0155] Data dimensionality increase: If the data dimension is lower than the dimension required by the model input, the data needs to be increased in dimension through preprocessing rules before entering the model;

[0156] Redundancy elimination: If the distribution or information content of multiple sets of data is similar, redundancy needs to be eliminated through preprocessing rules before entering the data into the model. This is because redundant data often does not bring more performance improvements but instead increases ineffective operations.

[0157] Redistribution: In some cases, it is difficult to obtain good model generalization by training data with similar feature information together. Redistributing data with different feature information is conducive to obtaining a model with better generalization.

[0158] For example, for scenario 1 in information 3, the terminal device can measure 4 of the 8 beams in cell A, but can only measure 5 of the 8 beams in cell B, and 3 of the 8 beams in cell C. If you want to use the same beam prediction model (only the measurement results of 4 beams are required as input) for beam prediction in cells A, B, and C, the measurement results of cell A can be used directly, but the measurement results obtained in cell B need to be reduced in data dimension, that is, 4 measurement results are selected from the measurement results of 5 available beams as the input parameters required by the model, and the measurement results obtained in cell C need to be increased in data dimension, that is, the measurement results of 3 available beams are changed to 4 to obtain the input parameters required by the model.

[0159] In another implementation, at least two of information 2, information 3, and information 4 may be defined in combination, and this application does not impose any restrictions on this.

[0160] Information 5: Information indicating the type of output parameters of the model

[0161] Information 5 can be used to indicate the type of output parameters required by the corresponding model. For example, if model 3 is used for beam prediction, the corresponding output parameter types include index information of the actual unmeasured beam and predicted signal measurement results of each actual unmeasured beam.

[0162] Information 6: Information indicating the format requirements of the model's output parameters

[0163] Information 6 can be used to indicate the format of the output parameters required by the corresponding model. For example, if model 3 is used for beam prediction, the output parameter can be the beam prediction result for one future moment, or the output parameter can be a set of beam prediction results for multiple future moments. For example, if the model input is a set of three sets of measurement results for four beams obtained at times T-3, T-2, and T-1, the model output can be the measurement results for eight beams at time T, or two sets of measurement results for eight beams at times T and T+1.

[0164] In summary, although the prediction of future beam measurement results is performed (the model output data type is the same), the required output data formats of Model 3 in different application scenarios are different. Therefore, the output parameter format requirements associated with the model are also one of the key information to describe the model.

[0165] Information 7: Information indicating the preprocessing rules of the model's output parameters

[0166] Information 7 may be used to indicate how to reprocess the output data set of the corresponding model. The reprocessing process may involve at least one of data dimensionality reduction, data dimensionality increase, redundant elimination, and redistribution. For specific processing methods, please refer to the relevant instructions in Information 4.

[0167] In another implementation, at least two of information 5, information 6, and information 7 may be defined in combination, and this application does not impose any limitation on this.

[0168] Information 8: Information indicating the application scenario of the model

[0169] Information 8 may refer to different usage scenarios under the same functional characteristics. For example, for the model used for positioning, the application scenario can be further subdivided into line of sight (LoS) scenario (or direct path scenario), non-line of sight (NLoS) scenario (or non-direct path scenario) or mixed scenario (including both LoS and NLoS). For another example, for the model used for mobility control, the application scenario can be further subdivided into ground communication scenario and non-ground communication scenario (including satellite communication, drone communication, hot air balloon communication and other sub-scenarios). Each scenario can be further divided into high-speed mobility scenario, medium-speed mobility scenario, low-speed mobility scenario and other sub-scenarios, and can also be divided into high-frequency mobility scenario, low-frequency mobility scenario and other sub-scenarios. It is also possible to consider the combination of two scenarios, such as ground communication high-frequency mobility scenario.

[0170] Optionally, information 8 may have a value indicating that the application scenario of the model is all scenarios (i.e., the model is applicable to any scenario corresponding to its associated functional characteristics). For example, for a model used for positioning, assuming that information 8 contains two bits, the value '00' can be used to indicate any scenario, '01' to indicate LoS scenario, '10' to indicate NLoS scenario, and '11' to indicate mixed scenario.

[0171] Information 9: Information indicating the deployment location of the model

[0172] Information 9 may include any one of the following meanings: deployed on core network equipment, deployed on application servers, deployed in operation administration and maintenance (OAM), deployed on access network equipment, deployed on terminal equipment, or no deployment location restriction.

[0173] Information 10: Information indicating capability requirements for using the model

[0174] Information 10 may be used to indicate several capability requirements required for using the model. For example, the capability requirement information for using the model may include one or more of the following: the minimum floating-point computing capability required for model use, the minimum running memory required for model use, the memory size level occupied by the model algorithm data before compilation, the memory size level occupied by the model algorithm data after compilation, the minimum input data rate (or bit rate) required for model use, the maximum input data rate (or bit rate) required for model use, the minimum output data rate (or bit rate) required for model use, and the maximum output data rate (or bit rate) required for model use.

[0175] Information 11: Information indicating the performance monitoring indicators of the model

[0176] Information 11 may be used to indicate several indicators for monitoring the model. For example, the performance monitoring indicator information associated with the model may include one or more of the following: average energy consumption of a single inference process, average floating-point calculation amount of a single inference process, average latency of a single inference process, system throughput, system bit error rate, average data packet transmission latency, and model inference accuracy.

[0177] Information 12: Information indicating the location of the model

[0178] The information 12 may be used to indicate information related to the provider of the model data. For example, the information 12 may include information about the country or region to which the model data belongs and / or information about the service provider to which the model data belongs.

[0179] The service provider may be any of the following: OTT (Over The Top, providing application services to users through the Internet) manufacturer information, network operator information (for example, represented by a public land mobile network (PLMN) identifier), and public website information.

[0180] Information 13: Information indicating the valid usage range of the model

[0181] Information 13 may include, for example, one or more of the applicable scenarios, configuration, and site information of the model. Information 13 may be used to indicate the conditions under which the model is effectively used. For example, the effective use scope information associated with the model includes one or more of the following: geographic area information allowing effective use, country information allowing effective use, PLMN information allowing effective use, tracking area code (TAC) information allowing effective use, access network area code (RANAC) information allowing effective use, cell information allowing effective use, and configuration information allowing effective use.

[0182] Information 14: Information indicating the generalization properties of the model

[0183] Generalization characteristics reflect the breadth of applicable scenarios for a model. Generally speaking, the higher the generalization characteristics of a model, the more application scenarios it is applicable to. Model generalization characteristics information can include at least one type of model application scenario information (see Information 8 for definition), indicating that the corresponding associated model can be used in the aforementioned application scenarios.

[0184] Information 15: Information indicating the version of the model

[0185] As different parameters in the same application scenario change over time, the algorithm data of the corresponding model may need to be fine-tuned or updated. The updated model is associated with the same application scenario and functions as the original model, but the model algorithm data details differ slightly. Therefore, model algorithm version numbers can be used to distinguish them, facilitating the control and management of similar model algorithms.

[0186] Information 16: Information indicating the accuracy of the model (such as indicating the accuracy level of the model)

[0187] Even for models with the same functionality and application scenario, different design complexities in the model algorithm will result in different inference accuracy. To distinguish between similar models in terms of inference accuracy, the model algorithm's accuracy level can be used to describe the inference accuracy of a given model.

[0188] Information 17: Information indicating the compilation format of model data

[0189] Model algorithms are essentially programs written in computer languages. Program file types differ depending on the language platform. Some languages ​​are compatible with each other, while others are not. Therefore, the compilation format of model algorithm data is crucial for describing a model. This information allows model users to understand the required compilation environment. Otherwise, mistakenly using an incompatible language compilation environment will result in the inability to use the corresponding model algorithm.

[0190] Information 18: Information indicating the storage format of model data

[0191] The information 18 may be used to indicate the format in which the model data is stored, such as zip compression format.

[0192] Information 19: Information indicating the computational complexity of the model

[0193] Information 19 may be used to indicate the basic computing power required to use the model, for example, the number of floating-point numbers required to be calculated per second.

[0194] Information 20: Information indicating the model complexity of the model

[0195] The information 20 may be used to indicate the complexity of the model, for example, how many layers of neurons the model consists of.

[0196] Information 21: Information indicating the size of the model

[0197] Information 21 may be used to indicate the memory size occupied by the model data before or after compilation.

[0198] Example 5: Version Identification Associated with Hardware Configuration of Terminal Device (Applicable to Any of Examples 1 to 3)

[0199] A complete terminal device consists of software configuration (e.g., software installed on the terminal device that matches the chip) and hardware configuration (e.g., the chip installed on the terminal device). The hardware configuration of a terminal device is rarely updated after leaving the factory, while some software configurations may be updated periodically as needed. Models deployed on terminal devices rely on the terminal device's software and hardware resources to function properly.

[0200] In some implementations, the model deployment information of a terminal device may be associated only with the hardware configuration version supported by the terminal device. That is, once the version identifier associated with the hardware configuration supported by the terminal device is known, the model deployment information of the terminal device can be known. In this implementation, since the hardware configuration supported by the terminal device generally does not change, the model deployment information supported by the terminal device generally does not change. Table 1 below shows one possible implementation.

[0201] Table 1: Correlation between model deployment information and version identifiers associated with hardware configuration

[0202] In Table 1, parameter n1 is a positive integer greater than or equal to 1. The version identifier associated with the hardware configuration of each terminal device is associated with a model deployment information supported by the terminal device (i.e., a predefined association relationship). The model deployment information supported by each terminal device represents the model information that has been deployed by the terminal device under the corresponding hardware configuration conditions. For example: the models supported by the terminal device under the hardware condition of configuration chip X include model A and model B; the models supported under the hardware condition of configuration chip Y include model A, model B, and model C; the models supported under the hardware condition of configuration chip Z include model A, model B, model C, and model D.

[0203] From the perspective of terminal devices, there's no need to directly report the specific mapping between the version identifier associated with the hardware configuration and model deployment information (i.e., the mapping shown in Table 1). Instead, they only need to report the version identifier associated with the hardware configuration they currently support. This reduces the cost of reporting model-related information for terminal devices. Hardware developers (such as terminal manufacturers or chip manufacturers) can align the mapping relationships in Table 1 with network equipment operators (communications carriers or network equipment manufacturers) through inter-vendor agreements. Since terminal device hardware configurations typically remain unchanged after leaving the factory, the model information supported by the terminal devices also remains unchanged. While this reduces some model deployment flexibility, terminal device operation is simplified, as there's no need to consider the additional operations required to update model deployment information. From the perspective of network equipment operators, because the mapping relationships in Table 1 can be obtained through inter-vendor agreements, the standard requires minimal information (i.e., only the version identifier associated with the hardware configuration sent by the terminal device). Network devices can obtain the model deployment information for a terminal device based on the received version identifier associated with the hardware configuration, simplifying standardization discussions. On the other hand, the mapping information in Table 1 maintained through inter-manufacturer agreements is not updated frequently, which greatly reduces the human and material costs associated with inter-manufacturer agreement maintenance and updates. This is because the version identifier associated with the terminal device's hardware configuration is not updated very frequently (usually updated on a quarterly basis, for example: mobile phone chip iterations take at least several months). Although network equipment manages terminal device models at the terminal device granularity, the information in Table 1 maintained by the network equipment is maintained at the hardware configuration version granularity, because the hardware configuration versions supported by the same terminal device are generally the same. As a result, the amount of information corresponding to Table 1 that the network equipment operator needs to maintain will not be large, and only one hardware configuration version needs to be updated.

[0204] Example 6: Version Identification Associated with Software Configuration of Terminal Device (Applicable to Any of Examples 1 to 3)

[0205] The model deployment information of the terminal device (i.e., the model information actually available to the terminal device) can be associated only with the software configuration supported by the terminal device. That is, once the version identifier associated with the software configuration supported by the terminal device is known, the model deployment information supported by the corresponding software configuration version can be known. In this implementation, since the software configuration supported by the terminal device does not change frequently, the model deployment information supported by the terminal device will not change frequently either. Table 2 is an example of this implementation:

[0206] Table 2: Relationship between model deployment information and version identifiers associated with software configuration

[0207] In Table 2, parameter n2 is a positive integer greater than or equal to 1. The version identifier associated with each software configuration supported by the terminal device is associated with a model deployment information supported by the terminal device (i.e., a predefined association relationship). The model deployment information supported by each terminal device represents the model information that has been deployed by the terminal device under the corresponding software configuration conditions. For example, the models supported by the terminal device under software configuration S1 include model A and model B, the models supported under software configuration S2 include model A, model B, and model C, and the models supported under software configuration S3 include model A, model B, model C, and model D.

[0208] From the perspective of the terminal device, there is no need to directly report the specific mapping relationship between the version identifier associated with the software configuration and the model deployment information (i.e., the mapping relationship shown in Table 2). It is only necessary to report the version identifier associated with the software configuration currently supported by itself, which saves the overhead of reporting relevant information of the terminal device, because the software development manufacturer (such as the terminal manufacturer) will align the mapping relationship contained in Table 2 with the network equipment operator (communication operator or network equipment manufacturer) through an inter-manufacturer agreement. On the other hand, since the terminal device software configuration can be changed, it means that the model information supported by the terminal device can also be changed, which increases the flexibility of the terminal device model deployment, that is: the self-deployed model can be updated through the software configuration version update, and the terminal device only needs to send the updated software configuration version identifier to the network device to allow the network device to obtain the latest deployed model information of the terminal device, and the additional standardization workload brought by the model update process is very small. From the perspective of network equipment operators, the standard receives very little information (i.e., only the software configuration version identification information sent by the terminal device is received), because the mapping relationship in Table 2 has been obtained through inter-manufacturer agreement. The network equipment can obtain the model deployment information of the terminal device based on the version identification associated with the received software configuration, which simplifies the workload of standardization discussions. On the other hand, the mapping information in Table 2 maintained through inter-manufacturer agreement can also be updated, providing a way to update the model information of the terminal device through software. This can achieve terminal device performance upgrades without the user replacing the terminal device, thereby improving the user's product experience. Although the network equipment manages the model of the terminal device at the terminal device granularity, the Table 2 information maintained by the network equipment is at the software configuration version granularity, because the same terminal device does not support too many software configuration versions. In this way, the amount of information corresponding to Table 2 that the network equipment operator needs to maintain will not be large, and only one software configuration version needs to be updated.

[0209] Example 7: Second Identification (Applicable to Any of Examples 1 to 3)

[0210] The second identifier is associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device. In other words, the model deployment information of the terminal device (i.e., the model information actually available to the terminal device) can be associated with a combination of the hardware configuration and software configuration supported by the terminal device. That is, if one of the hardware configuration and the software configuration changes, the model deployment information supported by the terminal device may be different. This implementation has two branches, and examples are given in Table 3 and Table 4 respectively:

[0211] Table 3: Example 1 of the association between model deployment information, hardware configuration version, and software configuration version

[0212] In Table 3, parameter n3 is a positive integer greater than or equal to 1, and a second identifier corresponds to a set of hardware configuration versions and software configuration versions supported by a terminal device. The second identifier may include one or more information fields (or multiple fields). In one implementation, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device. For example, a second identifier occupies 32 bits and is divided into two information fields, wherein the first information field occupies 16 bits, indicating the hardware configuration version supported by the terminal device, and the second information field occupies 16 bits, indicating the software configuration version supported by the terminal device. In another implementation, a second identifier may contain only one information field, that is: the second identifier as a whole information represents the hardware configuration version and software configuration version supported by the terminal device. For example, the models supported by the terminal device under chip configuration X and software configuration S1 include model A and model B, the models supported under chip configuration X and software configuration S2 include model A, model B and model C, the models supported under chip configuration Y and software configuration S1 include model A, model B, model C and model D, and the models supported under chip configuration Z and software configuration S1 include model A, model C and model D.

[0213] Table 4: Example 2 of the association between model deployment information, hardware configuration version, and software configuration version

[0214] In Table 4, the number of hardware configuration versions is 2. Parameters n4 and n5 are positive integers greater than or equal to 1. A hardware configuration-associated version identifier corresponds to a set of hardware configuration versions supported by a terminal device. A software configuration-associated version identifier corresponds to a set of software configuration versions supported by a terminal device. The model deployment information supported by a set of terminal devices is associated with a combination of a hardware configuration-associated version identifier and a software configuration-associated version identifier. That is, the hardware configuration and software configuration supported by the terminal device must be determined simultaneously to uniquely determine the model deployment information supported by the terminal device. For example, the models supported by the terminal device under chip configuration X and software configuration S1 include Model A and Model B. Under chip configuration X and software configuration S2, the models supported include Model A, Model B, and Model C. Under chip configuration Y and software configuration S1, the models supported include Model A, Model B, Model C, and Model D. Under chip configuration Z and software configuration S1, the models supported include Model A, Model C, and Model D.

[0215] From the perspective of terminal devices, there is no need to directly report the mapping relationship shown in Table 3 or Table 4. It is only necessary to report the second identifier currently supported by itself (or the version identifier associated with the hardware configuration and the version identifier associated with the software configuration), which saves the overhead of reporting relevant information of the terminal device, because the software and hardware developers will align the mapping relationship contained in Table 3 or Table 4 with the network equipment operator (communication operator or network equipment manufacturer) through inter-manufacturer agreement. On the other hand, while providing differentiated models for different hardware configurations, it supports the use of software configuration to update model deployment information, taking into account the characteristics of terminal device hardware configuration and software configuration updates, providing differentiated products for different user groups (from a hardware perspective), and providing software configuration update services for the same hardware device (from a software perspective), thereby improving the experience of different user groups; From the perspective of network equipment operators, the standard receives less information because the mapping relationship in Table 3 or Table 4 has been obtained through inter-manufacturer agreement. The network equipment can obtain the model deployment information of the terminal device based on the received second identifier (or the version identifier associated with the hardware configuration and the version identifier associated with the software configuration), which simplifies the workload of standardization discussions. On the other hand, the mapping information in Table 3 or Table 4 maintained through inter-manufacturer agreement will not be updated frequently, which to a certain extent reduces the manpower and material costs brought about by the maintenance and update of the inter-manufacturer agreement. At the same time, the mapping information in Table 3 or Table 4 maintained through inter-manufacturer agreement can also be updated, providing a way to update the terminal device model information through software, which can achieve terminal device performance upgrades without the user replacing the terminal device, which not only improves the user product experience but also reflects the differentiated service advantages of the network equipment operator. Although the model management of terminal devices by network devices is performed at the granularity of terminal devices, the information in Table 3 or Table 4 maintained by the network devices is performed at the granularity of hardware configuration version and software configuration version. This is because the hardware configuration versions supported by the same terminal device are usually the same, and the software configuration versions supported by the same terminal device will not be too many. In this way, the amount of information corresponding to Table 3 or Table 4 that the network device operator needs to maintain will not be large, and only one hardware configuration version and one software configuration version need to be updated once.

[0216] Example 8: Model set identification supported by the terminal device

[0217] The model set identifier supported by the terminal device is a logical identifier. A model set identifier is associated with one or more models. The terminal device reports the model set identifier supported by itself to the network device. Since the network device locally maintains the association relationship between the model set identifier and the model (i.e., the association relationship shown in Table 5 below), the network device can confirm the model set supported by the terminal device based on the model set identifier. Table 5 is an example of this implementation method:

[0218] Table 5: Association between model deployment information and model collection identifier

[0219] In Table 5, parameter n6 is a positive integer greater than or equal to 1. Each model set identifier supported by a terminal device is associated with a type of model deployment information supported by the terminal device (i.e., a predefined association). Each type of model deployment information supported by the terminal device represents the model information deployed by the terminal device under the corresponding model set identifier. For example, model set identifier 1 indicates that the terminal device has deployed models A and B, model set identifier 2 indicates that the terminal device has deployed models A, B, and C, and model set identifier 3 indicates that the terminal device has deployed models A, B, C, and D. The information in Table 5 will be communicated to the network device operator through an inter-vendor agreement.

[0220] In some implementations, the identifier associated with the set of models supported by the terminal device can be defined or transmitted according to one or more of the following granularities: version identifier granularity associated with the hardware configuration of the terminal device, version identifier granularity associated with the software configuration of the terminal device, second identifier granularity, terminal device granularity, protocol layer granularity, frequency point (component carrier) granularity, band granularity (or bandwidth granularity), band combination granularity (or bandwidth combination granularity) and channel model granularity.

[0221] Defining or transmitting model set identifiers at different granularities can bring the following beneficial effects: on the one hand, it allows the model update processes between different functional modules of the terminal device (for example: hardware functional modules, software functional modules, protocol layer functional modules) to be untied, thereby accurately implementing the update of model deployment information of specific functional modules, avoiding the situation where a single functional module updates the model deployment information and causes other unrelated functional modules to passively perform update operations; on the other hand, models generally have optimal working scenarios (for example: at a specific frequency, a specific bandwidth, and a specific bandwidth combination). Defining a model set with scenario granularity can also untie the model update processes between different scenarios, thereby accurately implementing the update of model deployment information supported in a specific scenario, thereby avoiding the situation where updating the model deployment information in a single scenario causes other unrelated scenarios to passively perform update operations.

[0222] The meaning of the granularity of the version identifier associated with the hardware configuration (the meaning is introduced in Example 5 above): it refers to the association of the version identifier of a hardware configuration with one or more model set identifiers. The actual meaning is that the terminal device can support one or more sets of models under a hardware configuration, and each set of models contains one or more models.

[0223] The meaning of the granularity of the version identifier associated with the software configuration (the meaning is introduced in Example 6 above): it refers to the association of the version identifier of a software configuration with one or more model set identifiers. The actual meaning is that the terminal device can support one or more sets of models under a software configuration, and each set of models contains one or more models.

[0224] The meaning of the granularity of the second identifier (the meaning is described in Example 7 above): refers to a second identifier associated with one or more model set identifiers. The actual meaning is that the terminal device can support one or more sets of models under a hardware configuration and a software configuration, and each set of models contains one or more models.

[0225] The meaning of terminal device granularity: refers to a terminal device associated with one or more model set identifiers. The actual meaning is that the terminal device supports one or more sets of models, and each set of models contains one or more models.

[0226] The meaning of protocol layer granularity: The protocol layer can be divided in any of the following ways:

[0227] Application layer, non-access stratum (NAS) and access stratum (AS);

[0228] NAS layer, non-NAS layer;

[0229] AS layer, non-AS layer;

[0230] Application layer, non-application layer;

[0231] Application layer, NAS layer, service data adaptation protocol (SDAP) layer, radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, backhaul adaptation protocol (BAP) layer, radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer.

[0232] The meaning of protocol layer granularity is explained using the example of dividing the protocol layer into the application layer, NAS layer, and AS layer. This means that the application layer, NAS layer, and AS layer are each associated with one or more model set identifiers (different protocol layers are associated with different model sets). This actually means that the application layer, NAS layer, and AS layer of the terminal device each support one or more sets of models, each set containing one or more models. The meaning of protocol layer granularity for other protocol layer divisions is similar and is not further explained here.

[0233] The meaning of frequency granularity: refers to the association of one or a group of frequencies with one or more model set identifiers. The actual meaning is that the terminal device supports one or more sets of models under one or a group of frequencies, and each set of models contains one or more models.

[0234] The meaning of frequency band granularity: refers to one or a group of frequency bands associated with one or more model set identifiers. The actual meaning is that the terminal device supports one or more sets of models under one or a group of frequency band conditions, and each set of models contains one or more models.

[0235] The meaning of frequency band combination granularity: refers to one or a group of frequency band combinations associated with one or more model set identifiers. The actual meaning is that the terminal device supports one or more sets of models under one or a group of frequency band combinations, and each set of models contains one or more models.

[0236] The meaning of channel model granularity: refers to a channel model associated with one or more model set identifiers. The actual meaning is that the terminal device supports one or more sets of models under a channel model, and each set of models contains one or more models.

[0237] In some implementations, the channel models mentioned above can be divided according to base station deployment scenarios, or according to signal direct paths or indirect paths.

[0238] In some implementations, the base station deployment scenarios mentioned above may be used to indicate one or more of the following scenarios:

[0239] indoor hotspot (InH);

[0240] indoor factory (InF);

[0241] Urban macro (UMa);

[0242] Urban micro (UMi);

[0243] Rural macro (RMa).

[0244] In some implementations, the above-mentioned different granularities can be used individually (see the above description) or in combination. Take the definition or transmission of the model set identifier according to the second identifier granularity, frequency band granularity, and frequency band combination granularity as an example for explanation: it means that one second identifier, one frequency band, and one frequency band combination are associated with one or more model set identifiers, which actually means that the terminal device supports one or more sets of models under one software and hardware configuration, one bandwidth, and one bandwidth combination condition, and each set of models contains one or more models.

[0245] As another example, the model set identifier is defined or transmitted at the frequency point granularity and the frequency band granularity;

[0246] For another example, the model set identifier is defined or transmitted according to the frequency point granularity, the frequency band granularity, and the frequency band combination granularity;

[0247] For another example, the model set identifier is defined or transmitted according to the second identifier granularity and the channel model granularity.

[0248] For another example, the model set identifier is defined or transmitted according to the second identifier granularity, the frequency point granularity, the frequency band granularity, and the frequency band combination granularity;

[0249] For another example, the model set identifier is defined or transmitted according to the second identifier granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

[0250] Example 9: Combination of Information Contained in the First Information (Applicable to Examples 1 to 3)

[0251] As mentioned above, the first information may include one or more of a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier (associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device); and an identifier associated with the set of models supported by the terminal device. In some implementations, the first information may include only one of the above identifiers, or may include multiple of the above identifiers simultaneously.

[0252] For example, the first information may only include a version identifier associated with the hardware configuration (the meaning of which is described in the above embodiment 5).

[0253] For another example, the first information may only include a version identifier associated with the software configuration (the meaning of which is described in the above embodiment 6).

[0254] For another example, the first information may include only the second identifier (the meaning of which is described in Example 7 above), or include the hardware configuration version identifier and the software configuration version identifier.

[0255] For another example, the first information may only include the model set identifier (the meaning of which is described in the above embodiment 8).

[0256] For another example, the first information includes a version identifier associated with the hardware configuration and a model set identifier.

[0257] For another example, the first information includes a version identifier associated with the software configuration and a model set identifier.

[0258] For another example, the first information includes the second identifier and the model set identifier, or includes a version identifier associated with the hardware configuration, a version identifier associated with the software configuration, and the model set identifier.

[0259] Optionally, if the first information only includes a model set identifier, the model set identifier can be defined or transmitted according to one or more of the following granularities: terminal device granularity, protocol layer granularity, frequency point granularity, frequency band granularity, frequency band combination granularity, and channel model granularity.

[0260] Optionally, if the first information includes a version identifier and a model set identifier associated with the hardware configuration, the above-mentioned model set identifier can be defined or transmitted according to one or more of the following granularities: hardware configuration version identifier granularity, terminal device granularity, protocol layer granularity, frequency point granularity, frequency band granularity, frequency band combination granularity, and channel model granularity.

[0261] Optionally, if the first information includes a version identifier and a model set identifier associated with the software configuration, the above-mentioned model set identifier can be defined or transmitted according to one or more of the following granularities: software configuration version identifier granularity, terminal device granularity, protocol layer granularity, frequency point granularity, frequency band granularity, frequency band combination granularity, and channel model granularity.

[0262] Optionally, if the first information includes a second identifier and a model set identifier, or includes a version identifier associated with the hardware configuration, a version identifier associated with the software configuration, and a model set identifier, then the above-mentioned model set identifier can be defined or transmitted according to one or more of the following granularities: hardware configuration version identifier granularity, software configuration version identifier granularity, first identifier granularity, terminal device granularity, protocol layer granularity, frequency point granularity, frequency band granularity, frequency band combination granularity, and channel model granularity.

[0263] Example 10: Transmission and / or carrying method of any information in Examples 1 to 3

[0264] Optionally, any information involved in the embodiments of the present application is carried by any one of the following message types: NR positioning protocol A (NR positioning protocol A, NRPPa) message, long term evolution positioning protocol (long term evolution positioning protocol, LPP) message, NAS message, RRC message, media access control control element (media access control control element, MAC CE) message, downlink control information (downlink control information, DCI) message, uplink control information (uplink control information, UCI) message, physical uplink control channel (physical uplink control channel, PUCCH) message, physical uplink shared channel (physical uplink shared channel, PUSCH) message, inter-node message, Xn interface message, F1 interface message, E1 interface message, NG interface message, core network service architecture-based message or AI dedicated message.

[0265] Optionally, any information involved in Examples 1 to 3 is carried by any one of the following message types: a unicast message, a multicast message, or a broadcast message.

[0266] Unicast message (one-to-one): The source transmits unicast messages through a unicast channel. Only terminal devices or network devices that have been allocated the corresponding unicast resources can attempt to receive the unicast message. Unicast messages can also be called dedicated signaling.

[0267] Multicast message (one-to-many): The source transmits the multicast message through the multicast channel. Terminal devices or network devices that are members of the group and within the coverage area of ​​the multicast signal can attempt to receive the multicast message. When a terminal device or network device joins a group, it obtains multicast channel-related resources.

[0268] Broadcast message (one-to-any): The source transmits the broadcast message through the broadcast channel. Any terminal device or network device within the coverage of the broadcast signal can attempt to receive the broadcast message.

[0269] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 4 . The device embodiment of the present application is described in detail below in conjunction with Figures 5 to 10 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0270] FIG5 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. The terminal device 500 shown in FIG5 may include a communication module 510. The communication module 510 is configured to send first information to a network device, the first information including a first identifier associated with the model deployment information of the terminal device.

[0271] In some implementations, the first identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0272] In some implementations, the first identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0273] In some implementations, the second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

[0274] In some implementations, the identifier associated with the set of models supported by the terminal device is defined or transmitted according to one or more of the following granularities: the version identifier granularity associated with the hardware configuration of the terminal device, the version identifier granularity associated with the software configuration of the terminal device, the second identifier granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity, and the channel model granularity.

[0275] In some implementations, the network device is an access network device or a core network device.

[0276] Figure 6 is a schematic diagram of the structure of a core network device provided in one embodiment of the present application. The core network device 600 shown in Figure 6 may be a first core network device. The core network device 600 includes a communication module 610. The communication module 610 is configured to receive first information sent by a terminal device, the first information including a first identifier associated with the model deployment information of the terminal device.

[0277] In some implementations, the first identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0278] In some implementations, the first identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0279] In some implementations, the second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

[0280] In some implementations, the identifier associated with the set of models supported by the terminal device is defined or transmitted according to one or more of the following granularities: the version identifier granularity associated with the hardware configuration of the terminal device, the version identifier granularity associated with the software configuration of the terminal device, the second identifier granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity, and the channel model granularity.

[0281] In some implementations, the communication module 610 is further configured to: store the first information in the context information of the terminal device.

[0282] In some implementations, the communication module 610 is further used to: send second information to the second core network device, where the second information includes a third identifier, and the information included in the third identifier is a subset of the information included in the first identifier.

[0283] In some implementations, the core network device 600 is also used to: send third information to the first access network device, and the third information includes one or more of the following: a fourth identifier, the information contained in the fourth identifier is a subset of the information contained in the first identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set.

[0284] In some implementations, the model description information includes one or more of the following information: information indicating the function of the model; information indicating the type of the input parameters of the model; information indicating the format of the input parameters of the model; information indicating the preprocessing rules of the input parameters of the model; information indicating the type of the output parameters of the model; information indicating the format requirements of the output parameters of the model; information indicating the preprocessing rules of the output parameters of the model; information indicating the application scenario of the model; information indicating the deployment location of the model; information indicating the capability requirements for using the model; information indicating the performance monitoring indicators of the model; information indicating the location of the model; information indicating the effective use scope of the model; information indicating the generalization characteristics of the model; information indicating the version of the model; information indicating the accuracy of the model; information indicating the compilation format of the model data; information indicating the storage format of the model data; information indicating the computational complexity of the model; information indicating the model complexity of the model; information indicating the size of the model.

[0285] FIG7 is a schematic diagram of the structure of an access network device provided by an embodiment of the present application. The access network device 700 shown in FIG7 may be a first access network device. The access network device 700 includes a communication module 710. The communication module 710 is used to receive third information sent by a first core network device, wherein the third information includes a fourth identifier, and the information contained in the fourth identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

[0286] In some implementations, the first identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0287] In some implementations, the first identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0288] In some implementations, the second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

[0289] In some implementations, the identifier associated with the set of models supported by the terminal device is defined or transmitted according to one or more of the following granularities: the version identifier granularity associated with the hardware configuration of the terminal device, the version identifier granularity associated with the software configuration of the terminal device, the second identifier granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity, and the channel model granularity.

[0290] In some implementations, the third information also includes one or more of the following: a model identifier, used to identify one or more models in the model deployment information or in the model set; and model description information, used to describe one or more models in the model deployment information or in the model set.

[0291] In some implementations, the communication module 710 is also used to: send fourth information to the second access device, and the fourth information includes one or more of the following information: a fifth identifier, the information included in the fifth identifier is a subset of the information included in the fourth identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set.

[0292] In some implementations, the model description information includes one or more of the following information: information indicating the function of the model; information indicating the type of the input parameters of the model; information indicating the format of the input parameters of the model; information indicating the preprocessing rules of the input parameters of the model; information indicating the type of the output parameters of the model; information indicating the format requirements of the output parameters of the model; information indicating the preprocessing rules of the output parameters of the model; information indicating the application scenario of the model; information indicating the deployment location of the model; information indicating the capability requirements for using the model; information indicating the performance monitoring indicators of the model; information indicating the location of the model; information indicating the effective use scope of the model; information indicating the generalization characteristics of the model; information indicating the version of the model; information indicating the accuracy of the model; information indicating the compilation format of the model data; information indicating the storage format of the model data; information indicating the computational complexity of the model; information indicating the model complexity of the model; information indicating the size of the model.

[0293] FIG8 is a schematic diagram of the structure of an access network device provided in one embodiment of the present application. The access network device 800 shown in FIG8 may be a first access network device. The access network device 800 includes a communication module 810. The communication module 810 is configured to receive first information sent by a terminal device, the first information including a first identifier associated with the model deployment information of the terminal device.

[0294] In some implementations, the first identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0295] In some implementations, the first identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0296] In some implementations, the second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

[0297] In some implementations, the identifier associated with the set of models supported by the terminal device is defined or transmitted according to one or more of the following granularities: the version identifier granularity associated with the hardware configuration of the terminal device, the version identifier granularity associated with the software configuration of the terminal device, the second identifier granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity, and the channel model granularity.

[0298] In some implementations, the communication module 810 is also used to: send fifth information to the second access network device, and the fifth information includes one or more of the following: a sixth identifier, the information contained in the sixth identifier is a subset of the information contained in the first identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set.

[0299] In some implementations, the communication module 810 is also used to: send sixth information to the first core network device, and the sixth information includes one or more of the following: a seventh identifier, and the information contained in the seventh identifier is a subset of the information contained in the first identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set.

[0300] In some implementations, the communication module 810 is also used to: receive seventh information sent by the first core network device, and the seventh information includes one or more of the following: an eighth identifier, the information contained in the eighth identifier is a subset of the information contained in the seventh identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set.

[0301] In some implementations, the model description information includes one or more of the following information: information indicating the function of the model; information indicating the type of the input parameters of the model; information indicating the format of the input parameters of the model; information indicating the preprocessing rules of the input parameters of the model; information indicating the type of the output parameters of the model; information indicating the format requirements of the output parameters of the model; information indicating the preprocessing rules of the output parameters of the model; information indicating the application scenario of the model; information indicating the deployment location of the model; information indicating the capability requirements for using the model; information indicating the performance monitoring indicators of the model; information indicating the location of the model; information indicating the effective use scope of the model; information indicating the generalization characteristics of the model; information indicating the version of the model; information indicating the accuracy of the model; information indicating the compilation format of the model data; information indicating the storage format of the model data; information indicating the computational complexity of the model; information indicating the model complexity of the model; information indicating the size of the model.

[0302] FIG9 is a schematic diagram of the structure of a core network device provided in another embodiment of the present application. The core network device 900 shown in FIG9 may be a first core network device. The core network device 900 includes a communication module 910. The communication module 910 is configured to receive sixth information sent by a first access network device, the sixth information including a seventh identifier, the information contained in the seventh identifier being a subset of the information contained in the first identifier, and the first identifier being associated with the model deployment information of the terminal device.

[0303] In some implementations, the first identifier is associated with one or more of the following: a hardware configuration of the terminal device; a software configuration of the terminal device; a set of models supported by the terminal device.

[0304] In some implementations, the first identifier includes one or more of the following: a version identifier associated with the hardware configuration of the terminal device; a version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of the hardware configuration of the terminal device and the software configuration of the terminal device; an identifier associated with a set of models supported by the terminal device.

[0305] In some implementations, the second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

[0306] In some implementations, the identifier associated with the set of models supported by the terminal device is defined or transmitted according to one or more of the following granularities: the version identifier granularity associated with the hardware configuration of the terminal device, the version identifier granularity associated with the software configuration of the terminal device, the second identifier granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity, and the channel model granularity.

[0307] In some implementations, the sixth information also includes one or more of the following: a model identifier, used to identify one or more models in the model deployment information or in the model set; and model description information, used to describe one or more models in the model deployment information or in the model set.

[0308] In some implementations, the communication module 910 is also used to: send seventh information to a third access network device, the seventh information including one or more of the following: an eighth identifier, the information contained in the eighth identifier is a subset of the information contained in the seventh identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set; wherein the third access network device is the same device as the first access network device or a different device.

[0309] In some implementations, the communication module 910 is also used to: send eighth information to the second core network device, and the eighth information includes one or more of the following: a ninth identifier, the information contained in the ninth identifier is a subset of the information contained in the seventh identifier; a model identifier, used to identify one or more models in the model deployment information or in the model set; model description information, used to describe one or more models in the model deployment information or in the model set.

[0310] In some implementations, the model description information includes one or more of the following information: information indicating the function of the model; information indicating the type of the input parameters of the model; information indicating the format of the input parameters of the model; information indicating the preprocessing rules of the input parameters of the model; information indicating the type of the output parameters of the model; information indicating the format requirements of the output parameters of the model; information indicating the preprocessing rules of the output parameters of the model; information indicating the application scenario of the model; information indicating the deployment location of the model; information indicating the capability requirements for using the model; information indicating the performance monitoring indicators of the model; information indicating the location of the model; information indicating the effective use scope of the model; information indicating the generalization characteristics of the model; information indicating the version of the model; information indicating the accuracy of the model; information indicating the compilation format of the model data; information indicating the storage format of the model data; information indicating the computational complexity of the model; information indicating the model complexity of the model; information indicating the size of the model.

[0311] FIG10 is a schematic block diagram of an apparatus according to an embodiment of the present application. The dotted lines in FIG10 indicate that the unit or module is optional. Apparatus 1000 may be used to implement the method described in the above method embodiment. Apparatus 1000 may be a chip, a terminal device, or a network device.

[0312] The device 1000 may include one or more processors 1010. The processor 1010 may support the device 1000 to implement the method described in the method embodiment above. The processor 1010 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another 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, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0313] The apparatus 1000 may further include one or more memories 1020. The memories 1020 store programs that can be executed by the processor 1010, causing the processor 1010 to perform the methods described in the above method embodiments. The memories 1020 may be independent of the processor 1010 or integrated into the processor 1010.

[0314] The apparatus 10000 may further include a transceiver 1030. The processor 1010 may communicate with other devices or chips via the transceiver 1030. For example, the processor 1010 may transmit and receive data with other devices or chips via the transceiver 1030.

[0315] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present application, and the program enables a computer to execute the method performed by the terminal device, access network device, or core network device in each embodiment of the present application.

[0316] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the methods performed by the terminal device, access network device, or core network device in each embodiment of the present application.

[0317] The present application also provides a computer program that can be applied to the communication device provided in the present application and enables a computer to execute the method performed by the terminal device, access network device, or core network device in each embodiment of the present application.

[0318] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0319] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0320] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

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

[0322] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0323] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0324] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

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

[0326] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0327] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0328] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0330] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device sends first information to the network device, where the first information includes a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

2. The method according to claim 1, characterized in that The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

3. The method according to claim 1 or 2, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

4. The method according to claim 3, characterized in that The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

5. The method according to claim 3 or 4, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

6. The method according to any one of claims 1 to 5, characterized in that The network device is an access network device or a core network device.

7. A wireless communication method, characterized in that: include: The first core network device receives first information sent by a terminal device, where the first information includes a first identifier, and the first identifier is associated with model deployment information of the terminal device.

8. The method according to claim 7, characterized in that The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

9. The method according to claim 7 or 8, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

10. The method according to claim 9, characterized in that The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

11. The method according to claim 9 or 10, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

12. The method according to any one of claims 7 to 11, characterized in that The method further comprises: The first core network device stores the first information in the context information of the terminal device.

13. The method according to any one of claims 7 to 12, characterized in that The method further comprises: The first core network device sends second information to the second core network device, where the second information includes a third identifier, and the information included in the third identifier is a subset of the information included in the first identifier.

14. The method according to any one of claims 7 to 13, characterized in that The method further comprises: The first core network device sends third information to the first access network device, where the third information includes one or more of the following: a fourth identifier, wherein information contained in the fourth identifier is a subset of the information contained in the first identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

15. The method according to claim 14, characterized in that The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

16. A wireless communication method, characterized in that: include: The first access network device receives third information sent by the first core network device, where the third information includes a fourth identifier, and information included in the fourth identifier is a subset of information included in the first identifier, and the first identifier is associated with model deployment information of the terminal device.

17. The method according to claim 16, characterized in that The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

18. The method according to claim 16 or 17, characterized in that The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

19. The method according to claim 18, characterized in that The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

20. The method according to claim 18 or 19, characterized in that The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

21. The method according to any one of claims 16 to 20, characterized in that The third information also includes one or more of the following: A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

22. The method according to any one of claims 16 to 21, characterized in that The method further comprises: The first access network device sends fourth information to the second access device, where the fourth information includes one or more of the following information: A fifth identifier, wherein information contained in the fifth identifier is a subset of information contained in the fourth identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

23. The method according to claim 21 or 22, characterized in that The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

24. A wireless communication method, characterized in that: include: The first access network device receives first information sent by a terminal device, where the first information includes a first identifier, and the first identifier is associated with model deployment information of the terminal device.

25. The method according to claim 24, characterized in that The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

26. The method according to claim 24 or 25, characterized in that The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

27. The method according to claim 26, characterized in that The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

28. The method according to claim 26 or 27, characterized in that The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

29. The method according to any one of claims 24 to 28, characterized in that The method further comprises: The first access network device sends fifth information to the second access network device, where the fifth information includes one or more of the following: A sixth identifier, wherein information included in the sixth identifier is a subset of the information included in the first identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

30. The method according to any one of claims 24 to 29, characterized in that The method further comprises: The first access network device sends sixth information to the first core network device, where the sixth information includes one or more of the following: A seventh identifier, wherein information included in the seventh identifier is a subset of the information included in the first identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

31. The method according to any one of claims 24 to 30, characterized in that The method further comprises: The third access network device receives the seventh information sent by the first core network device, where the seventh information includes one or more of the following: An eighth identifier, wherein information contained in the eighth identifier is a subset of the information contained in the seventh identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information, used to describe one or more models in the model deployment information or in the model set; The third access network device is the same device as the first access network device or a different device.

32. The method according to any one of claims 29 to 31, characterized in that The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

33. A wireless communication method, characterized in that: include: The first core network device receives sixth information sent by the first access network device, where the sixth information includes a seventh identifier, and information included in the seventh identifier is a subset of information included in the first identifier, and the first identifier is associated with model deployment information of the terminal device.

34. The method according to claim 33, characterized in that The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

35. The method according to claim 33 or 34, characterized in that The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

36. The method according to claim 35, characterized in that The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

37. The method according to claim 35 or 36, characterized in that The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

38. The method according to any one of claims 33 to 37, characterized in that The sixth information also includes one or more of the following: A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

39. The method according to any one of claims 33 to 38, characterized in that The method further comprises: The first core network device sends seventh information to the third access network device, where the seventh information includes one or more of the following: An eighth identifier, wherein information contained in the eighth identifier is a subset of the information contained in the seventh identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information, used to describe one or more models in the model deployment information or in the model set; The third access network device is the same device as the first access network device or a different device.

40. The method according to any one of claims 33 to 39, characterized in that The method further comprises: The first core network device sends eighth information to the second core network device, where the eighth information includes one or more of the following: A ninth identifier, wherein information contained in the ninth identifier is a subset of the information contained in the seventh identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

41. The method according to any one of claims 38 to 40, characterized in that The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

42. A terminal device, characterized in that: include: A communication module is used to send first information to a network device, wherein the first information includes a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

43. The terminal device according to claim 42, characterized in that: The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

44. The terminal device according to claim 42 or 43, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

45. The terminal device according to claim 44, characterized in that: The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

46. ​​The terminal device according to claim 44 or 45, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

47. The terminal device according to any one of claims 42 to 46, characterized in that: The network device is an access network device or a core network device.

48. A core network device, characterized in that: The core network device is a first core network device, and the first core network device includes: The communication module is used to receive first information sent by a terminal device, where the first information includes a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

49. The core network device according to claim 48, characterized in that: The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

50. The core network device according to claim 48 or 49, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

51. The core network device according to claim 50, characterized in that: The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

52. The core network device according to claim 50 or 51, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

53. The core network device according to any one of claims 48 to 52, characterized in that: The communication module is also used for: The first information is stored in the context information of the terminal device.

54. The core network device according to any one of claims 48 to 53, characterized in that: The communication module is also used for: Send second information to the second core network device, where the second information includes a third identifier, and the information included in the third identifier is a subset of the information included in the first identifier.

55. The core network device according to any one of claims 48 to 54, characterized in that: The communication module is also used for: Sending third information to the first access network device, where the third information includes one or more of the following: a fourth identifier, wherein information contained in the fourth identifier is a subset of the information contained in the first identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

56. The core network device according to claim 55, characterized in that: The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

57. An access network device, characterized in that: The access network device is a first access network device, and the first access network device includes: A communication module is used to receive third information sent by a first core network device, wherein the third information includes a fourth identifier, and the information contained in the fourth identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

58. The access network device according to claim 57, characterized in that: The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

59. The access network device according to claim 57 or 58, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

60. The access network device according to claim 59, characterized in that: The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

61. The access network device according to claim 59 or 60, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

62. The access network device according to any one of claims 57 to 61, characterized in that: The third information also includes one or more of the following: A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

63. The access network device according to any one of claims 57 to 62, characterized in that: The communication module is also used for: Sending fourth information to the second access device, where the fourth information includes one or more of the following information: A fifth identifier, wherein information contained in the fifth identifier is a subset of information contained in the fourth identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

64. The access network device according to claim 62 or 63, characterized in that: The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

65. An access network device, characterized in that: The access network device is a first access network device, and the first access network device includes: The communication module is used to receive first information sent by a terminal device, where the first information includes a first identifier, and the first identifier is associated with the model deployment information of the terminal device.

66. The access network device according to claim 65, characterized in that: The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

67. The access network device according to claim 65 or 66, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

68. The access network device according to claim 67, characterized in that: The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

69. The access network device according to claim 67 or 68, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

70. The access network device according to any one of claims 65 to 69, characterized in that: The communication module is also used for: Sending fifth information to the second access network device, where the fifth information includes one or more of the following: A sixth identifier, wherein information included in the sixth identifier is a subset of the information included in the first identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

71. The access network device according to any one of claims 65 to 70, characterized in that: The communication module is also used for: Sending sixth information to the first core network device, where the sixth information includes one or more of the following: A seventh identifier, wherein information included in the seventh identifier is a subset of the information included in the first identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

72. The access network device according to any one of claims 65 to 71, characterized in that: The communication module is also used for: Receive seventh information sent by the first core network device, where the seventh information includes one or more of the following: An eighth identifier, wherein information contained in the eighth identifier is a subset of the information contained in the seventh identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

73. The access network device according to any one of claims 70 to 72, characterized in that: The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

74. A core network device, characterized in that: The core network device is a first core network device, and the first core network device includes: A communication module is used to receive sixth information sent by a first access network device, wherein the sixth information includes a seventh identifier, and the information contained in the seventh identifier is a subset of the information contained in the first identifier, and the first identifier is associated with the model deployment information of the terminal device.

75. The core network device according to claim 74, characterized in that: The first identifier is associated with one or more of the following: The hardware configuration of the terminal device; Software configuration of the terminal device; The model set supported by the terminal device.

76. The core network device according to claim 74 or 75, characterized in that: The first identifier includes one or more of the following: A version identifier associated with the hardware configuration of the terminal device; A version identifier associated with the software configuration of the terminal device; a second identifier, the second identifier being associated with a combination of a hardware configuration of the terminal device and a software configuration of the terminal device; The identifier associated with the model set supported by the terminal device.

77. The core network device according to claim 76, characterized in that: The second identifier includes one or more information fields, wherein, when the second identifier includes multiple information fields, the second identifier includes a first information field and a second information field, the information in the first information field is associated with the hardware configuration of the terminal device, and the information in the second information field is associated with the software configuration of the terminal device.

78. The core network device according to claim 76 or 77, characterized in that: The identifier associated with the model set supported by the terminal device is defined or transmitted according to one or more of the following granularities: The version identification granularity associated with the hardware configuration of the terminal device, the version identification granularity associated with the software configuration of the terminal device, the second identification granularity, the terminal device granularity, the protocol layer granularity, the frequency point granularity, the frequency band granularity, the frequency band combination granularity and the channel model granularity.

79. The core network device according to any one of claims 74 to 78, characterized in that: The sixth information also includes one or more of the following: A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

80. The core network device according to any one of claims 74 to 79, characterized in that: The communication module is also used for: Sending seventh information to the third access network device, where the seventh information includes one or more of the following: An eighth identifier, wherein information contained in the eighth identifier is a subset of the information contained in the seventh identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information, used to describe one or more models in the model deployment information or in the model set; The third access network device is the same device as the first access network device or a different device.

81. The core network device according to any one of claims 74 to 80, characterized in that: The communication module is also used for: Sending eighth information to the second core network device, where the eighth information includes one or more of the following: A ninth identifier, wherein information contained in the ninth identifier is a subset of the information contained in the seventh identifier; A model identifier, used to identify one or more models in the model deployment information or in the model set; Model description information is used to describe one or more models in the model deployment information or in the model set.

82. The core network device according to any one of claims 79 to 81, characterized in that: The model description information includes one or more of the following information: Information indicating the functionality of the model; Information indicating the types of input parameters of the model; Information indicating the format of the model's input parameters; Information indicating preprocessing rules for the model's input parameters; Information indicating the kind of output parameters of the model; Information indicating the format requirements for the model's output parameters; Information indicating preprocessing rules for output parameters of the model; Information indicating the application scenario of the model; information indicating where the model is deployed; Information indicating capability requirements for using the model; Information indicating performance monitoring metrics of the model; Information indicating the location of the model; Information indicating the effective range of use of the model; Information indicating the generalization properties of the model; Information indicating the version of the model; Information indicating the accuracy of the model; Information indicating the compilation format of the model data; Information indicating the storage format of the model data; Information indicating the computational complexity of the model; information indicating the model complexity of the model; Information indicating the size of the model.

83. A terminal device, characterized in that: It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes the method as described in any one of claims 1 to 6.

84. A core network device, characterized in that: It includes a transceiver, a memory and a processor, the memory is used to store programs, the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the core network device executes the method as described in any one of claims 7 to 15 or 33 to 41.

85. An access network device, characterized in that: It includes a transceiver, a memory and a processor, the memory is used to store programs, the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the access network device executes the method as described in any one of claims 16 to 23 or 24 to 32.

86. A device, characterized in that It comprises a processor for calling a program from a memory so that the apparatus executes a method as claimed in any one of claims 1 to 6, 7 to 15, 16 to 23, 24 to 32, or 33 to 41.

87. A chip, characterized in that: It comprises a processor for calling a program from a memory so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 6, 7 to 15, 16 to 23, 24 to 32, or 33 to 41.

88. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method as claimed in any one of claims 1 to 6, 7 to 15, 16 to 23, 24 to 32, or 33 to 41.

89. A computer program product, characterized in that Comprising a program which causes a computer to execute the method as claimed in any one of claims 1 to 6, 7 to 15, 16 to 23, 24 to 32, or 33 to 41.

90. A computer program, characterized in that The computer program causes a computer to execute the method of any one of claims 1 to 6, 7 to 15, 16 to 23, 24 to 32, or 33 to 41.

Images