Terminal capability switching method and apparatus, terminal, network side device, and medium

Abstract

The present application relates to the technical field of communications, and discloses a terminal capability switching method and apparatus, a terminal, a network side device, and a medium. The terminal capability switching method in embodiments of the present application comprises: a terminal supporting at least two capability frameworks executes at least one of the following operations: executing switching between the at least two capability frameworks on the basis of first information sent by a network side device; and triggering the terminal itself to execute switching between the at least two capability frameworks, wherein the at least two capability frameworks comprise capability parameters of different values.

Description

Terminal capability switching methods, devices, terminals, network-side equipment and media

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411034180.5, filed on July 30, 2024, entitled “Terminal Capability Switching Method, Apparatus, Terminal, Network Side Equipment and Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a terminal capability switching method, apparatus, terminal, network-side equipment, and medium. Background Technology

[0004] In cellular communication standards, a terminal (or User Equipment, UE) provides the network-side equipment with a list of its supported functions (also known as a UE capability report), reporting the terminal capabilities it supports. The terminal will subsequently use the terminal capabilities reported in the UE capability report to transmit data with other devices (such as network-side equipment or other terminals).

[0005] However, this method of using terminal capabilities reported in the UE capability report for data transmission can easily lead to wasted terminal capabilities, resulting in lower terminal energy efficiency. For example, when the UE uses the terminal capabilities reported in the UE capability report for data transmission with low transmission rate requirements, the problem of wasted terminal capabilities will occur, thereby reducing terminal energy efficiency. Summary of the Invention

[0006] This application provides a terminal capability switching method, apparatus, terminal, network-side equipment, and medium, which can solve the problem of low terminal energy efficiency.

[0007] Firstly, a terminal capability switching method is provided, executed by the terminal, the method comprising:

[0008] Terminals that support at least two capability frameworks can perform at least one of the following operations:

[0009] Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks;

[0010] Trigger itself to switch between the at least two capability frameworks;

[0011] The at least two capability frameworks include capability parameters with different values.

[0012] Secondly, a terminal capability switching method is provided, executed by a network-side device, the method comprising:

[0013] The network-side device performs at least one of the following operations:

[0014] The network-side device sends first information to a terminal that supports at least two capability frameworks;

[0015] The network-side device receives the capability framework switching request sent by the terminal;

[0016] The first information is information related to the terminal performing a switch between the at least two capability frames, wherein the at least two capability frames include capability parameters with different values.

[0017] Thirdly, a terminal capability switching device is provided, applied to a terminal supporting at least two capability frameworks, the device comprising:

[0018] The first processing module is configured to perform at least one of the following operations:

[0019] Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks;

[0020] The terminal itself is triggered to switch between the at least two capability frameworks;

[0021] The at least two capability frameworks include capability parameters with different values.

[0022] Fourthly, a terminal capability switching device is provided, applied to network-side equipment, the device comprising at least one of the following:

[0023] The second sending module is used to send the first information to a terminal that supports at least two capability frameworks;

[0024] The second receiving module is used to receive the capability framework switching request sent by the terminal;

[0025] The first information is information related to the terminal performing a switch between the at least two capability frames, wherein the at least two capability frames include capability parameters with different values.

[0026] Fifthly, a terminal capability switching apparatus is provided, the apparatus being configured to perform the steps of the terminal capability switching method as described in the first or second aspect.

[0027] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the terminal capability switching method as described in the first aspect.

[0028] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the terminal capability switching method as described in the first aspect.

[0029] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the terminal capability switching method as described in the second aspect.

[0030] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the terminal capability switching method as described in the second aspect.

[0031] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the terminal capability switching method as described in the first or second aspect.

[0032] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the terminal capability switching method as described in the first aspect, and the network-side device can be used to perform the steps of the terminal capability switching method as described in the second aspect.

[0033] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the terminal capability switching method as described in the first or second aspect.

[0034] In a thirteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the terminal capability switching method as described in the first or second aspect.

[0035] In this embodiment, the terminal can trigger itself or, based on the first information sent by the network-side device, perform a switch between at least two capability frameworks. That is, the terminal can switch between high and low capabilities it supports by changing the values ​​of its own capability parameters. Compared with a terminal that only supports a single terminal capability (i.e., only the terminal capability reported by the UE capability report), the terminal in this embodiment can reduce the waste of terminal capabilities during data transmission by performing the switch between high and low capabilities, thereby improving terminal energy efficiency. Attached Figure Description

[0036] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0037] Figure 2 is a schematic diagram of the UE Capability reporting process in related technologies;

[0038] Figure 3 is a flowchart illustrating the implementation of a terminal capability switching method provided in an embodiment of this application;

[0039] Figure 4 is a flowchart illustrating a terminal capability switching method provided in an embodiment of this application;

[0040] Figure 5 is a flowchart illustrating another terminal capability switching method provided in an embodiment of this application;

[0041] Figure 6 is a schematic diagram illustrating another terminal capability switching method provided in the embodiments of this application;

[0042] Figure 7 is a schematic diagram of a terminal capability switching device provided in an embodiment of this application;

[0043] Figure 8 is a schematic diagram of another terminal capability switching device provided in an embodiment of this application;

[0044] Figure 9 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0045] Figure 10 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0046] Figure 11 is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0048] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0049] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0050] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0051] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0052] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0053] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0054] To facilitate understanding of the technical solutions provided in this application, the main technical concepts involved in the embodiments of this application are briefly described below.

[0055] 1. UE Category (Cat)

[0056] UE Category indicates the uplink and downlink data transmission capabilities supported by the terminal.

[0057] Prior to Release (R or Rel) 12, uplink and downlink data transmission capabilities were bundled together, meaning the definition included both uplink and downlink data transmission capabilities simultaneously, as detailed in Table 1 below.

[0058] Table 1 Examples of UE levels prior to R12

[0059] Starting with Release 12, the definition of UE Category distinguishes between uplink (UL) and downlink (DL). For example, the uplink data transmission rate (i.e., upload rate) is defined using UE UL Cat X, and the downlink data transmission rate (i.e., download rate) is defined using UE DL Cat Y. There are protocol-defined configuration combinations between UE UL Cat X and UE DL Cat Y, as detailed in Table 2 below.

[0060] Table 2 Examples of UE levels after R12

[0061] 2. UE Capability Reporting Mechanism

[0062] The UE Capability reporting mechanism refers to the process by which a 5G user terminal reports its basic capabilities and supported functions to a base station or controller. In other words, it reports the terminal capabilities that the UE supports (e.g., by reporting a UE capability report) so that the network can configure and schedule the terminal based on its capabilities and requirements.

[0063] According to protocol 38.331, the UE Capability reporting mechanism mainly involves two processes: UE Capability request and UE Capability reporting.

[0064] Referring to the schematic diagram of the UE Capability reporting process shown in Figure 2, when the base station needs the UE to report its UE Capability, the base station will send a UE Capability Enquiry command to the UE. After receiving the UE Capability Enquiry command, the UE will report its UE Capability Information according to the command.

[0065] UE Capability can be divided into different levels of capability. For example, UE Capability can be divided into the following three levels of capability:

[0066] 1) UE-specific UE Capability: Each UE may have different capabilities, which apply to all carriers and carrier combinations supported by the UE.

[0067] 2) UE Capability at the Band Combination Level: Each Band Combination can have different capabilities. For example, Band 3 and Band 77 may support a certain UE capability, while Band 1 and Band 78 may not support that UE capability.

[0068] 3) UE Capability at the Band Level: Each Band can have different capabilities. For example, Band 77 may support a certain UE capability, while Band 78 may not support that UE capability.

[0069] For example, considering that UE Capability is actually reported according to the protocol stack layers, UE Capability can also be divided into the following five levels of capability according to the protocol stack:

[0070] 1) UE Capability corresponding to the Packet Data Convergence Protocol (PDCP) layer: PDCP-Parameters;

[0071] 2) UE Capability corresponding to the Radio Link Control (RLC) layer: RLC-Parameters;

[0072] 3) UE Capability corresponding to the Media Access Control (MAC) layer: MAC-Parameters;

[0073] 4) UE Capability corresponding to the Physical (PHY) layer: Phy-Parameters;

[0074] 5) Radio Frequency (RF) related UE Capability: RF-Parameters.

[0075] Currently, in cellular communication standards such as NR and LTE, each terminal provides the network-side equipment with a list of its supported functions (also known as a UE capability report), reporting the terminal capabilities it supports. The network-side equipment configures or schedules the terminal based on the terminal capabilities reported in the UE capability report. As a result, the terminal will continue to use the terminal capabilities reported in the UE capability report to transmit data with other devices (such as network-side equipment or other terminals).

[0076] However, this method of using a single terminal capability (i.e., the terminal capability reported in the UE capability report) for data transmission creates a dependency relationship for many functions supported by the terminal (i.e., terminal capabilities). This means that each terminal must use functions that may not actually be necessary, which may result in each terminal using more terminal capabilities than required, leading to wasted terminal capabilities and reduced terminal energy efficiency.

[0077] For example, for a terminal that supports 2 transmit (Tx) lines and 4 receive (Rx) lines (which can achieve a transmission rate of 1Gbps), when performing data transmission with a transmission rate requirement of 10Mbps, the terminal only needs to use 1 Tx line and 2 Rx lines to meet the transmission rate requirement. However, since the terminal can only use its own supported 2 Tx lines and 4 Rx lines for data transmission, it results in a waste of terminal capacity and a reduction in terminal energy efficiency.

[0078] To address the problems existing in related technologies, this application provides a terminal capability switching method, apparatus, terminal, network-side equipment, and medium. Compared to a terminal that only supports a single terminal capability (i.e., the terminal capability reported by the UE capability report), the terminal in the embodiments of this application can change its supported terminal capabilities by performing switching between at least two capability frameworks. This helps to reduce the waste of terminal capabilities during data transmission and thus improve terminal energy efficiency.

[0079] The following description, in conjunction with the accompanying drawings, details a terminal capability switching method, apparatus, terminal, network-side device, and medium provided in this application through some embodiments and application scenarios.

[0080] For ease of description, the following unified explanation of the various terms involved in the embodiments of this application is provided first. (Unless otherwise specified, the following unified explanation of the various terms applies to the various implementations of this application. Since some terms appear later in the text, they will not be uniformly explained here, but will be explained when they first appear in the following text):

[0081] Network-side device: This can be network-side device 12 as shown in Figure 1. For an example of network-side device 12, please refer to the previous text. It will not be repeated here.

[0082] Terminal: can be terminal 11 in Figure 1. For an example of terminal 11, please refer to the previous text, which will not be repeated here.

[0083] Data transmission: includes at least one of data reception and data transmission.

[0084] Terminal capabilities: also known as terminal hardware capabilities, can be represented by relevant capability parameters of the transceiver in the terminal, such as the number of Tx lines, the number of Rx lines, and UE level-related parameters recorded in Tables 1 and 2.

[0085] In a first aspect, this application provides a terminal capability switching method, which is executed by a terminal. Referring to Figure 3, which is a flowchart illustrating the implementation of a terminal capability switching method provided in this application, the method may include the following steps:

[0086] Step S101: Terminals supporting at least two capability frameworks shall perform at least one of the following operations:

[0087] Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks;

[0088] Trigger itself to switch between the at least two capability frameworks;

[0089] The at least two capability frameworks include capability parameters with different values. Different capability parameters in the capability framework can be associated with different terminal capabilities (such as terminal capabilities related to uplink and downlink respectively, or terminal capabilities of different levels, etc.). For example, a capability framework may include one or more of the capability parameters associated with PDCP-Parameters, RLC-Parameters, MAC-Parameters, Phy-Parameters and RF-Parameters mentioned above.

[0090] In practice, the terminal switches between at least two capability frameworks based on the first information sent by the network-side device or by triggering itself to switch between them. This allows the terminal to switch its supported terminal capabilities from high to low or from low to high, thereby reducing the waste of terminal capabilities while ensuring that the terminal can transmit data normally, thus improving terminal energy efficiency.

[0091] Taking capability frameworks A and B, which contain different values ​​for the number of Tx lines and the number of Rx lines, as an example, the terminal supports capability frameworks A and B, that is, it has the ability to use the configuration or scheduling associated with capability frameworks A and B to transmit data.

[0092] In capability framework A, the number of Tx lines is 2 and the number of Rx lines is 4, while in capability framework B, the number of Tx lines is 1 and the number of Rx lines is 1. Besides the two different capability parameters, the number of Tx lines and the number of Rx lines, capability frameworks A and B can also contain other capability parameters with the same value.

[0093] When a terminal transmits data in multiple service scenarios, it switches between the two capability frameworks mentioned above based on the first information sent by the network-side device or by triggering its own switching. For example, in service scenarios with high terminal capability requirements, the terminal switches from capability framework B to capability framework A to use the configuration or scheduling corresponding to 2 Tx lines and 4 Rx lines for data transmission in the current service scenario, thus meeting the terminal capability requirements of the current service scenario. In service scenarios with lower terminal capability requirements, the terminal switches from capability framework A to capability framework B to use the configuration or scheduling corresponding to 1 Tx line and 1 Rx line for data transmission in the current service scenario, thereby reducing the waste of terminal capabilities. Thus, by switching between the two capability frameworks, the terminal can reduce the waste of terminal capabilities during data transmission while meeting the terminal capability requirements (such as transmission rate requirements) of different service scenarios, thereby improving terminal energy efficiency.

[0094] As can be seen from the above steps, the terminal can trigger itself or, based on the first information sent by the network-side device, perform a switch between at least two capability frameworks. That is to say, the terminal can switch between high and low capabilities it supports by changing the values ​​of its own capability parameters. Compared with a terminal that only supports a single terminal capability (i.e., only supports the terminal capability reported by the UE capability report), the terminal in this embodiment of the application can reduce the waste of terminal capabilities during data transmission by performing a switch between high and low capabilities, thereby improving the terminal's energy efficiency.

[0095] Optionally, the capability parameters in the capability framework include at least one of the following:

[0096] The number of transmission branches (Tx branches) of the terminal;

[0097] The number of receiving branches (Rx branches) in the terminal;

[0098] The maximum number of layers supported by the terminal downlink Multiple-Input Multiple-Output (MIMO);

[0099] The maximum number of layers supported by uplink MIMO in the terminal;

[0100] The peak downlink rate supported by the terminal;

[0101] The peak uplink rate supported by the terminal;

[0102] The number of downlink carriers supported by the terminal;

[0103] The number of uplink carriers supported by the terminal;

[0104] Uplink subcarrier spacing supported by the terminal;

[0105] Downlink subcarrier spacing supported by the terminal;

[0106] Downlink carrier bandwidth supported by the terminal;

[0107] Uplink carrier bandwidth supported by the terminal;

[0108] The downlink modulation and coding scheme (MCS) level or the maximum downlink MCS level supported by the terminal;

[0109] The uplink MCS level supported by the terminal or the maximum uplink MCS level;

[0110] The number of downlink Hybrid Automatic Repeat-reQuest Processes (HARQ Processes) supported by the terminal;

[0111] The number of uplink HARQ processes supported by the terminal;

[0112] The number of blind detections of the Physical Downlink Control Channel (PDCCH) or the number of Control Channel Elements (CCE) supported by the terminal;

[0113] Budget for the size of Downlink Control Information (DCI) supported by the terminal;

[0114] The number of Central Processing Units (CPUs), Ports, or Resources that the terminal supports for processing Channel State Information (CSI).

[0115] The maximum downlink transport block size (TBS) supported by the terminal;

[0116] Maximum uplink TBS supported by the terminal;

[0117] End-to-end latency requirements supported by the terminal;

[0118] The terminal supports Discontinuous Reception (DRX) configuration;

[0119] Processing delay requirements for receiving data through at least one downlink channel of the terminal;

[0120] Preparation delay requirement for at least one uplink channel transmission by the terminal;

[0121] Reliability requirements supported by the terminal;

[0122] The mobility requirements supported by the terminal;

[0123] Downlink synchronization requirements of the terminal;

[0124] Uplink synchronization requirements of the terminal;

[0125] Error Vector Magnitude (EVM) requirements for terminal-processed signals;

[0126] EVM requirements for signals transmitted by the terminal;

[0127] Measurement requirements for Radio Resource Management (RRM) of the terminal;

[0128] Terminal radio link monitoring (RLM) measurement requirements;

[0129] Duplex requirements supported by the terminal;

[0130] The range of frequency bands supported by the terminal;

[0131] Whether the terminal supports artificial intelligence (AI) capabilities or the AI ​​capabilities supported by the terminal, such as the type or size of the AI ​​capabilities supported by the terminal;

[0132] Whether the terminal supports sensing capabilities or the sensing capabilities supported by the terminal, such as the type or size of the sensing capabilities supported by the terminal.

[0133] In some embodiments, the method further includes:

[0134] The terminal sends information related to supporting multi-capability frameworks to the network-side device;

[0135] The information related to the support for the multi-capability framework includes at least one of the following:

[0136] The at least two capability frameworks;

[0137] The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks.

[0138] The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

[0139] In specific implementation, the terminal sends the at least two capability frameworks to the network-side device so that the network-side device can understand the different values ​​of one or more capability parameters supported by the terminal. Based on this, the network-side device can perform relevant scheduling or configuration of the terminal to ensure that the terminal can use the at least two capability frameworks for data transmission.

[0140] The terminal sends the second information to the network-side device to inform the network-side device that the terminal supports data transmission using the at least two capability frameworks. Based on this, the network-side device can send capability framework switching-related configurations or instructions to the terminal to control the terminal to perform capability framework switching under specific circumstances, or to control the terminal to switch to a specific capability framework for data transmission under specific circumstances.

[0141] The terminal sends the third information to the network-side device to inform the network-side device that the terminal supports switching between the at least two capability frames. Based on this, the network-side device can send capability frame usage-related configurations or instructions to the terminal so that the terminal can use a specific capability frame for data transmission under specific circumstances.

[0142] It is understandable that, through predefined protocols or pre-negotiation between the network-side device and the terminal, the terminal can also indirectly inform the network-side device of other information related to the support for the multi-capability framework by sending one or more of the aforementioned information.

[0143] For example, the terminal can indirectly inform the network-side device that it supports data transmission using the at least two capability frames by sending the at least two capability frames, and / or supports switching between the at least two capability frames.

[0144] For example, the protocol predefines three capability frameworks. The terminal informs the network-side device by sending a second message that the terminal supports using multiple capability frameworks for data transmission or supports switching between multiple capability frameworks. The network-side device can then know that the terminal supports the three capability frameworks.

[0145] Optionally, the information related to supporting multiple capability frameworks includes the at least two capability frameworks; the terminal sends the information related to supporting multiple capability frameworks to the network-side device, including at least one of the following:

[0146] Item A-1: ​​The terminal sends a combination of capability parameter values ​​corresponding to each of the at least two capability frames to the network-side device;

[0147] Item A-2: The terminal sends the parameter values ​​of one or more capability parameters associated with the at least two capability frames under different indices to the network-side device, wherein the different indices correspond to different capability frames;

[0148] Item A-3: The terminal sends a combination of capability parameter values ​​corresponding to different parts of the at least two capability frames to the network-side device;

[0149] The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

[0150] In practical implementation, for item A-1, the terminal sends all capability parameter values ​​contained in a capability frame as a combination, on a capability frame basis, so that the network-side device can quickly determine the parameter values ​​contained in each capability frame. For combinations of capability parameter values ​​corresponding to multiple capability frames, the terminal can send the multiple combinations of capability parameter values ​​to the network-side device separately, or send the multiple combinations of capability parameter values ​​to the network-side device together.

[0151] Taking the combination of capability parameter values ​​corresponding to the capability framework Radio Profile#1 as {Capability 1value#1, Capability 2value#1, ...} and the combination of capability parameter values ​​corresponding to the capability framework Radio Profile#2 as {Capability 1value#2, Capability 2value#2, ...} as an example, where Capability 1value#1 and Capability 1value#2 represent two possible values ​​for capability parameter 1, and Capability 2value#1 and Capability 2value#2 represent two possible values ​​for capability parameter 2.

[0152] The terminal can send the combination of the two capability parameter values ​​mentioned above to the network-side device in the form of a table. The information in this table includes:

[0153] Radio Profile#1={Capability 1value#1,Capability 2value#1,…}

[0154] Radio Profile#2={Capability 1value#2,Capability 2value#2,…}

[0155] For item A-2, the terminal sends the values ​​of a capability parameter in different capability frames as a combination, using capability parameters as the unit. The network-side device can combine the received capability parameter values ​​according to the index to obtain the capability frame, or perform subsequent operations such as configuration or scheduling at a more granular level from the perspective of capability parameters. For multiple capability parameter value combinations, the terminal can send each value combination separately to the network-side device, or send multiple value combinations together to the network-side device.

[0156] For example, for the capability parameter Capability 1, the terminal can send Capability 1 = {value 1} to the network-side device. i #1, value jThe information content of #2} is the above combination of values ​​for Capability 1, where value i #1 represents the value of Capability 1 in the capability framework corresponding to index i, where value... j #2 represents the value of Capability 1 in the capability framework corresponding to index j.

[0157] For item A-3, the terminal divides a capability framework into multiple parts, each containing different capability parameters. The terminal sends all the capability parameter values ​​contained in a part of a capability framework as a combination. The network-side device can combine the received capability framework parts to obtain the capability framework, or perform more granular configuration or scheduling operations based on the combination of capability parameter values ​​corresponding to different parts of the capability framework.

[0158] For a combination of capability parameter values ​​corresponding to each part of a capability framework, the terminal can send the combination of the multiple capability parameter values ​​to the network-side device separately, or send the combination of the multiple capability parameter values ​​to the network-side device together.

[0159] For example, if capability framework Radio profile #1 is divided into uplink and downlink parts, namely Radio Part 1 profile #1 and Radio Part 2 profile #1, and capability framework Radio profile #2 is also divided into uplink and downlink parts, namely Radio Part 1 profile #2 and Radio Part 2 profile #2, then the terminal can send the following information to the network-side device to report the combination of capability parameter values ​​corresponding to the uplink and downlink parts of the two capability frameworks:

[0160] Radio Part 1profile#1={Capability 1value#1,Capability 2value#1,…}

[0161] Radio Part 1profile#2={Capability 1value#2,Capability 2value#2,…}

[0162] Radio Part 2profile#1={Capability 3value#1,Capability 4value#1,…}

[0163] Radio Part 2profile#2={Capability 3value#2,Capability 4value#2,…}

[0164] In this context, Capability 1value#1 and Capability 1value#2 represent two possible values ​​for capability parameter 1, Capability 2value#1 and Capability 2value#2 represent two possible values ​​for capability parameter 2, Capability 3value#1 and Capability 3value#2 represent two possible values ​​for capability parameter 3, and Capability 4value#1 and Capability 4value#2 represent two possible values ​​for capability parameter 4.

[0165] In some implementations, the triggering of the switching between the at least two capability frameworks includes at least one of the following:

[0166] After sending a capability framework switching request to the network-side device, switch to the target capability framework;

[0167] After sending the capability framework switching request to the network-side device and receiving confirmation, switch to the target capability framework;

[0168] Send the capability framework switching request to the network-side device, and switch to the target capability framework after a set time elapsed after receiving confirmation feedback.

[0169] In practice, the terminal can first send a capability framework switching request to the network-side device, and then directly switch to the target capability framework after the capability framework switching request has been sent, so as to achieve a fast switching of capability framework.

[0170] Alternatively, after sending the capability framework switching request to the network-side device, the terminal can monitor the response of the network-side device. Upon receiving confirmation feedback corresponding to the capability framework switching request sent by the network-side device (i.e., after receiving confirmation), or after receiving the confirmation feedback and a certain period of time, the terminal switches to the target capability framework. Thus, the network-side device can flexibly control the terminal's capability framework switching by sending confirmation feedback, thereby having the ability to control the terminal's capability framework switching.

[0171] Optionally, the capability framework switching request includes: relevant information about the target capability framework to which the terminal requests to switch, such as the index of the target capability framework.

[0172] Optionally, the network-side device may determine whether to send a confirmation feedback corresponding to the capability framework switching request to the terminal based on network congestion or cell service status.

[0173] For example, if the network-side device anticipates that switching the terminal to the target capability framework will cause network congestion, it can send a corresponding denial feedback to the terminal or not send a corresponding confirmation feedback to the terminal, thereby rejecting the terminal's request to switch to the target capability framework and thus avoiding network congestion.

[0174] For example, a terminal sends a capability framework switching request to switch from a capability framework corresponding to a higher terminal capability to one corresponding to a lower terminal capability. When the network-side device detects that the terminal has higher terminal capability requirements in the current cell's service state, it sends a corresponding denial feedback to the terminal or does not send a corresponding confirmation feedback to the terminal to reject the terminal's request to switch to the target capability framework, thereby satisfying the terminal capability requirements of the current cell's service state.

[0175] In some implementations, the method further includes, before the terminal triggers itself to perform a switch between the at least two capability frameworks:

[0176] The terminal determines whether to trigger itself to switch between the at least two capability frameworks based on its own information.

[0177] The terminal's own information includes at least one of the following: terminal service status, terminal battery level, and terminal energy efficiency; the terminal service status includes service type (such as latency-sensitive service type, latency-insensitive service type, high-speed service type, or low-speed service type, etc.).

[0178] For example, when a terminal changes its own service status, such as changing from a high-speed service type to a low-speed service type, it can trigger itself to switch between the at least two capability frameworks in order to switch to a capability framework that is more compatible with the changed service status, thereby reducing the waste of terminal capabilities.

[0179] For example, when its own battery level is lower than a set value, the terminal can trigger itself to switch between the at least two capability frames in order to switch to the capability frame with lower power consumption, thereby increasing its own running time.

[0180] For example, when the terminal's own energy efficiency is lower than a set value, it can trigger itself to switch between the at least two capability frameworks in order to improve the terminal's energy efficiency by changing the terminal capability it uses.

[0181] In some embodiments, the method further includes:

[0182] The terminal determines the target capability framework it needs to switch to based on the target indication information sent by the network-side device;

[0183] The target indication information includes at least one of the following:

[0184] Index of the target capability framework;

[0185] A bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit. For example, if the terminal supports capability frameworks 1 and 2, which correspond to the first bit and the second bit in the bitmap respectively, the network device can send a bitmap with "01" to indicate that capability framework 2 (i.e. the capability framework corresponding to the bit with a value of 1) is the target capability framework that the terminal needs to switch to.

[0186] The start time of the target capability framework is used to indicate when the terminal switches to the target capability framework.

[0187] The duration of the target capability framework in effect is used to indicate how long the terminal needs to wait before switching to other capability frameworks after switching to the target capability framework.

[0188] The end time of the target capability framework is used to indicate when the terminal switches from the target capability framework to other capability frameworks.

[0189] Information used to instruct the terminal to switch the currently used capability framework, that is, to instruct the terminal to perform a capability framework switch.

[0190] In some embodiments, the method further includes at least one of the following:

[0191] The terminal switches to the target capability framework after a first time period following receipt of the target indication information;

[0192] After a second period of time following the receipt of the target indication information, the terminal switches to the target capability framework.

[0193] The first duration and the second duration can be configured by the network-side device or predefined by the protocol.

[0194] In specific implementation, the terminal switches to the target capability framework after a first time interval from the time the target indication information is received. Alternatively, the terminal switches to the target capability framework after a second time interval from the time the feedback of the target indication information is sent. The feedback of the target indication information may include: feedback of receiving or not receiving the target indication information, or feedback of correctly receiving or not correctly receiving the target indication information.

[0195] For example, a terminal can send an index to the network-side device indicating that it has received the target capability framework, but has not received feedback on the start time of the target capability framework's activation, and then switch to the target capability framework after a second period of time.

[0196] Optionally, when the terminal receives target indication information containing the start time of the target capability framework taking effect, it can determine, based on the network-side device configuration or the priority predefined by the protocol, which of the start time, the first duration, and the second duration should be used to determine when to switch to the target capability framework.

[0197] Optionally, the target indication information is carried by at least one of the following:

[0198] System information, such as System Information Block type 1 (SIB1) or System Information Block type x (SIBx), etc.

[0199] Radio Resource Control (RRC) signaling, such as serving cell configuration, RRC connection setup signaling, or RRC release signaling;

[0200] Media access control (MAC) control elements (CEs), such as carrying target indication information through a MAC CE specifically for capability framework indication, or adding the target indication information to a MAC CE for other function indications, etc.

[0201] DCI, such as UE-specific DCI for scheduling or not scheduling data, Group common DCI, or Common DCI, etc.

[0202] A wake-up signal is a signal used to restore a terminal from a standby or sleep state to an active state. When a network-side device sends a wake-up signal to wake up a terminal (i.e., to restore the terminal to an active state), it carries the target indication information in the wake-up signal to indicate the capability framework to be used after the terminal is woken up.

[0203] In some implementations, before the terminal determines the target capability framework it needs to switch to based on the target indication information sent by the network-side device, the method further includes:

[0204] The terminal sends auxiliary information to the network-side device;

[0205] The auxiliary information includes at least one of the following:

[0206] The desired capability framework of the terminal;

[0207] The terminal predicts the business situation within the target time period, such as the predicted business type or average data transmission rate within a future period.

[0208] The terminal's battery status;

[0209] The energy efficiency monitoring status of the terminal;

[0210] The average data transmission rate monitoring status of the terminal.

[0211] In this embodiment, the terminal sends auxiliary information to the network-side device to assist the network-side device in reasonably determining the target capability framework that the terminal needs to use. The network-side device then instructs the terminal to switch to the target capability framework through target indication information.

[0212] In some implementations, where the operation performed by the terminal includes switching between the at least two capability frameworks based on first information sent by the network-side device, the method further includes:

[0213] The terminal receives first information sent by the network-side device, the first information including at least one of: indication information related to capability framework switching, configuration information, and working mode;

[0214] Different working modes are associated with different capability frameworks, and the configuration information is: the configuration associated with each of the at least two capability frameworks.

[0215] In practice, the network-side device sends instruction information related to capability framework switching to the terminal. Based on the instruction information, the terminal can quickly know whether it needs to switch capability frameworks or determine which capability framework to switch to.

[0216] Alternatively, the network-side device can send the operating mode to the terminal, and the terminal can switch to the capability framework associated with the operating mode accordingly. In this way, the indication of capability framework switching can be achieved by indicating the operating mode, which can reduce communication overhead.

[0217] Optionally, if the received operating mode is energy-saving mode, the terminal switches to the first capability framework;

[0218] When the received operating mode is non-energy-saving mode, the terminal switches to the second capability framework, where the first capability framework and the second capability framework are different capability frameworks.

[0219] In practice, network-side equipment configuration associates capability frameworks with power-saving modes. The terminal uses the appropriate capability framework based on whether the power-saving mode is activated (i.e., whether the received operating mode is power-saving mode). Taking power-saving modes including DRX mode as an example, when DRX mode is activated (i.e., when the received operating mode is DRX mode), the UE switches to capability framework 1 (corresponding to the first capability framework); when DRX mode is not activated (i.e., when the received operating mode is not DRX mode), the UE switches to capability framework 2 (corresponding to the second capability framework).

[0220] Alternatively, the network-side device sends the configuration associated with each of the at least two capability frames. The terminal determines whether to perform a capability frame switch or which capability frame to switch to by using the relevant configuration or by using the relevant configuration activated by the network-side device. This can reduce the number of times relevant indication information is sent, thereby reducing communication overhead.

[0221] Optionally, the configuration associated with each of the at least two capability frameworks may include: relevant configurations required for the terminal to perform data transmission using the at least two capability frameworks (such as uplink-related configurations, downlink-related configurations, or cell-related configurations). After receiving the configuration information, the terminal determines the relevant configuration to use based on the capability framework it is using, that is, it uses the configuration associated with the capability framework it is using in the configuration information to perform data transmission. This eliminates the need for network-side devices to send additional data transmission-related configurations, thereby reducing communication overhead.

[0222] Optionally, the configuration information includes at least one of the following:

[0223] Bandwidth Part (BWP) configuration;

[0224] Service community configuration;

[0225] Uplink channel configuration, such as Random Access Channel (RACH) configuration, Physical Uplink Control Channel (PUCCH) configuration, or Physical Uplink Shared Channel (PUSCH) configuration, etc.

[0226] Uplink signal configuration, such as the configuration of the channel sounding reference signal (SRS);

[0227] Downlink channel configuration, such as PDCCH configuration or Physical Downlink Shared Channel (PDSCH) configuration, etc.

[0228] Downlink signal configuration, such as Synchronization Signal Block (SSB) configuration or Channel State Information-Reference Signal (CSI-RS) configuration;

[0229] Scheduled Request (SR) configuration;

[0230] Buffer Status Report (BSR) configuration;

[0231] CSI reporting configuration;

[0232] Carrier configuration;

[0233] Frequency band configuration;

[0234] Timer.

[0235] It is understood that the various information contained in the above configuration information can be used by the terminal to determine whether it needs to switch capability frameworks or to which capability framework to switch to, and all of the various information contained in the above configuration information, except for timers, can be used for data transmission.

[0236] In some implementations, the configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration; the method further includes:

[0237] The terminal performs at least one of the following operations based on the configuration information:

[0238] The terminal switches to the capability framework associated with the activated BWP;

[0239] The terminal switches to the capability framework associated with the activated Carrier;

[0240] The terminal switches to the capability framework associated with the active Band.

[0241] In practice, network-side device configuration associates the capability framework with BWP, Carrier, or Band. For example, after adding the configuration of the associated capability framework in the BWP configuration, Carrier configuration, or Band configuration, the network-side device sends it to the terminal as configuration information.

[0242] When a network-side device activates a BWP, Carrier, or Band, the terminal searches for the capability framework in the configuration information of the activated BWP, Carrier, or Band, and switches to that capability framework. Thus, the network-side device can indirectly instruct the terminal to switch capability frameworks and indirectly indicate which capability framework the terminal needs to switch to by activating (or switching) a BWP, Carrier, or Band.

[0243] Optionally, the handover reservation time requirement for at least one of the BWP, Carrier, and Band, when involving a switch of the terminal capability framework, differs from the handover reservation time requirement when it does not involve a switch of the terminal capability framework. This ensures that the terminal has sufficient time to perform the handover of the capability framework, as well as the handover of the BWP, Carrier, or Band. For example, in cases where the handover of the BWP, Carrier, or Band will cause a switch of the terminal capability framework (i.e., cases involving a switch of the terminal capability framework), the handover reservation time requirement for the handover of the BWP, Carrier, or Band in this case can be determined by combining the reservation time required for the switch of the capability framework, to ensure that the terminal has sufficient time to perform the handover of the capability framework, as well as the BWP, Carrier, or Band.

[0244] In some implementations, the configuration information includes a timer; the method further includes:

[0245] When the Timer is running, the terminal switches to the third capability framework associated with the Timer, which starts running when the terminal begins to use the third capability framework;

[0246] In response to the detection of the Timer expired (Expired), the terminal switches to the fourth capability framework associated with the Timer, which expired when its runtime exceeded the set usage time of the third capability framework. The third and fourth capability frameworks are different capability frameworks.

[0247] For example, the network-side device configures a timer associated with the usage time of capability framework 3 (for the third capability framework). This timer starts running when the terminal switches to capability framework 3. When the timer runs for longer than the set usage time of capability framework 3, that is, when the usage time of capability framework 3 exceeds the set usage time, the timer expires, and the terminal switches to capability framework 4 (corresponding to the fourth capability framework). Capability framework 4 can be configured by the network-side device or predefined by the protocol.

[0248] In some embodiments, the method further includes:

[0249] When the target event is met, the terminal switches to the fifth capability framework;

[0250] The target event includes at least one of the following:

[0251] Received a specific scheduling physical downlink control channel (PDCCH);

[0252] The average data rate within the observation window satisfies the first condition;

[0253] The average monitoring energy efficiency within the observation window meets the second condition;

[0254] The terminal's battery level meets the third condition;

[0255] The energy efficiency of the terminal meets the fourth condition;

[0256] The reference signal receiving power (RSRP) of the terminal satisfies the fifth condition.

[0257] In practice, the target event can be predefined by the protocol or configured by the network-side device. When the target event is met, the terminal switches to the capability framework associated with the target event (i.e., the fifth capability framework). The capability frameworks associated with different target events can be the same or different.

[0258] Optionally, the specific scheduling PDCCH is: a scheduling PDCCH that satisfies the sixth condition;

[0259] The sixth condition includes at least one of the following:

[0260] The number of frequency domain units scheduled is no greater than a first set value;

[0261] The scheduled TBS is no greater than the second set value.

[0262] Optionally, one or more of the first to sixth conditions, as well as the first and second set values, are configured by the network-side device or predefined by the protocol.

[0263] In some embodiments, the method further includes:

[0264] During the process of switching from one capability framework to another, the terminal performs at least one of the following:

[0265] No downlink reception is performed;

[0266] No uplink transmission is performed;

[0267] No measurements were taken.

[0268] In some implementations, the time (or minimum time required) for the terminal to switch from one capability framework to another can be configured by the network-side device or predefined by the protocol.

[0269] Optionally, the method further includes at least one of the following:

[0270] The terminal determines the target transition time and sends the target transition time to the network-side device.

[0271] The terminal receives the target conversion time configuration sent by the network-side device;

[0272] The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

[0273] In practice, the terminal can predefine the minimum time required to reserve based on the protocol, flexibly determine the target transition time, and report the target transition time to the network-side device; or, the network-side device can configure the target transition time.

[0274] In some implementations, one of the at least two capability frames is the default capability frame; the method further includes:

[0275] When the target conditions are met, the terminal uses the default capability framework for data transmission, and the target conditions include at least one of the following:

[0276] The terminal is in a disconnected state;

[0277] The terminal is in the process of random access;

[0278] The terminal did not receive any indication information related to the capability framework, such as no indication information related to capability framework switching, or no indication information related to the target capability framework.

[0279] In some implementations, the default capability framework and the target conditions can be configured by the network-side device or predefined by the protocol. For example, the protocol predefines the capability framework with index 0 as the default capability framework, or the network-side device configures a capability framework as the default capability framework.

[0280] Optionally, one of the at least two capability frameworks is the default capability framework; the method further includes at least one of the following:

[0281] The terminal determines the default capability framework and sends the default capability framework to the network-side device.

[0282] The terminal receives the configuration of the default capability framework sent by the network-side device.

[0283] For example, taking the network-side device as a base station, the terminal capability switching method provided in the above embodiments will be illustrated.

[0284] Example 1

[0285] Referring to the flowchart of the terminal capability switching method shown in Figure 4, the process mainly includes:

[0286] Step 1: The terminal sends the aforementioned information related to the multi-capability framework to the base station;

[0287] Step 2: The terminal determines the capability framework to use based on the capability framework-related indication information (such as the target indication information mentioned above) or configuration information sent by the base station.

[0288] In this example, the base station can directly indicate the capability framework that the terminal needs to use (i.e., the one it needs to switch to) by displaying instructions, such as by sending the aforementioned target indication information (e.g., the index of the target capability framework).

[0289] Alternatively, the base station can indirectly indicate the capability framework that the terminal needs to use by means of implicit indication, such as by sending the operating mode associated with the capability framework.

[0290] Alternatively, the terminal can determine the capability framework to use based on the configuration information sent by the base station. For example, the terminal can determine the capability framework to use based on the timer in the configuration information; or the terminal can determine the capability framework associated with the activated BWP, Carrier, or Band based on the BWP configuration, Carrier configuration, or Band configuration associated with different capability frameworks in the configuration information.

[0291] This enables a method for terminals to determine and use specific capability frameworks based on indication or configuration information related to the capability framework sent by the base station, which helps reduce terminal capability waste and thus improves terminal energy efficiency.

[0292] Example 2

[0293] Referring to the flowchart of the terminal capability switching method shown in Figure 5, the process mainly includes:

[0294] Step 1: The terminal sends the aforementioned information related to the multi-capability framework to the base station;

[0295] Step 2: Switching the terminal trigger capability framework.

[0296] Step 3: The base station confirms (i.e. allows) the switching of the terminal execution capability framework.

[0297] Step 4: The terminal determines the capability framework to use.

[0298] In this example, the terminal can determine whether to trigger a capability framework switch based on its own service status, power consumption, or energy efficiency. If a capability framework switch is triggered, the terminal sends a capability framework switch request to the base station. Subsequently, the terminal can either determine the capability framework to use and switch to that capability framework, or wait for the base station to confirm its capability framework switch before determining the capability framework to use and switching to that capability framework.

[0299] This enables terminals to proactively switch to a specific capability framework based on their own information, which helps reduce wasted terminal capabilities and improve terminal energy efficiency.

[0300] A second aspect of this application provides a terminal capability switching method, which is executed by a network-side device. Referring to Figure 6, which is a flowchart illustrating the implementation of a terminal capability switching method provided in this application, the method may include the following steps:

[0301] Step S201: The network-side device performs at least one of the following operations:

[0302] The network-side device sends first information to a terminal that supports at least two capability frameworks;

[0303] The network-side device receives the capability framework switching request sent by the terminal;

[0304] The first information is information related to the terminal performing a switch between the at least two capability frames, wherein the at least two capability frames include capability parameters with different values.

[0305] As can be seen from the above steps, the terminal can trigger itself or, based on the first information sent by the network-side device, perform a switch between at least two capability frameworks. That is to say, the terminal can switch between high and low capabilities it supports by changing the values ​​of its own capability parameters. Compared with a terminal that only supports a single terminal capability (i.e., only supports the terminal capability reported by the UE capability report), the terminal in this embodiment of the application can reduce the waste of terminal capabilities during data transmission by performing a switch between high and low capabilities, thereby improving the terminal's energy efficiency.

[0306] In some embodiments, the method further includes:

[0307] The network-side device receives information related to the multi-capability framework sent by the terminal.

[0308] The information related to the support for the multi-capability framework includes at least one of the following:

[0309] The at least two capability frameworks;

[0310] The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks.

[0311] The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

[0312] In some implementations, the information related to supporting multiple capability frameworks includes the at least two capability frameworks; the network-side device receives the information related to supporting multiple capability frameworks sent by the terminal, including at least one of the following:

[0313] The network-side device receives a combination of capability parameter values ​​corresponding to each of the at least two capability frames from the terminal.

[0314] The network-side device receives parameter values ​​from the terminal for one or more capability parameters associated with the at least two capability frames under different indices, where the different indices correspond to different capability frames.

[0315] The network-side device receives from the terminal a combination of capability parameter values ​​corresponding to different parts of the at least two capability frames;

[0316] The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

[0317] In some implementations, the capability framework switching request includes: information about the target capability framework to which the terminal requests to switch;

[0318] After the network-side device receives the capability framework switching request sent by the terminal, the method further includes:

[0319] The network-side device determines whether to send a confirmation feedback corresponding to the capability framework switching request to the terminal based on network congestion or cell service status.

[0320] In some embodiments, the method further includes:

[0321] The network-side device sends target indication information to the terminal, the target indication information being used to indicate the target capability framework that the terminal needs to switch to;

[0322] The target indication information includes at least one of the following:

[0323] Index of the target capability framework;

[0324] A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit;

[0325] The start time at which the target capability framework takes effect;

[0326] The duration for which the target capability framework is in effect;

[0327] The end time of the effective period of the target capability framework;

[0328] Information used to instruct the terminal to switch the currently used capability framework.

[0329] In some implementations, the target indication information is carried by at least one of the following:

[0330] System information;

[0331] Radio Resource Control (RRC) signaling;

[0332] Media Access Control (MAC) control element CE;

[0333] Downlink Control Information (DCI);

[0334] Wake-up signal.

[0335] In some embodiments, before the network-side device sends target indication information to the terminal, the method further includes:

[0336] The network-side device receives auxiliary information sent by the terminal;

[0337] The network-side device determines the target capability framework that the terminal needs to switch to based on the auxiliary information;

[0338] The auxiliary information includes at least one of the following:

[0339] The desired capability framework of the terminal;

[0340] The terminal predicts the business situation within the target time period;

[0341] The terminal's battery status;

[0342] The energy efficiency monitoring status of the terminal;

[0343] The average data transmission rate monitoring status of the terminal.

[0344] In some implementations, the first information includes at least one of the following:

[0345] Instructions related to capability framework switching;

[0346] Configuration information, which includes the configuration associated with each of the at least two capability frameworks;

[0347] Work modes, and different work modes are associated with different competency frameworks.

[0348] In some implementations, the configuration information includes at least one of the following:

[0349] Partial bandwidth BWP configuration;

[0350] Service community configuration;

[0351] Uplink channel configuration;

[0352] Uplink signal configuration;

[0353] Downlink channel configuration;

[0354] Downlink signal configuration;

[0355] Scheduler request SR configuration;

[0356] Cache Status Report (BSR) configuration;

[0357] Downlink Control Information (CSI) reporting configuration;

[0358] Carrier configuration;

[0359] Frequency band configuration;

[0360] Timer.

[0361] In some implementations, the configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration; the method further includes:

[0362] The network-side device activates at least one of the BWP, Carrier, and Band associated with the target capability framework to which the terminal needs to switch.

[0363] In some implementations, the handover reservation time requirement for at least one of the BWP, the Carrier, and the Band, when involving a change in the terminal capability framework, differs from the handover reservation time requirement when not involving a change in the terminal capability framework.

[0364] In some implementations, the configuration information includes a Timer that: starts running when the terminal begins using a specific capability framework, and expires when the running time exceeds the set usage time of the specific capability framework.

[0365] In some embodiments, the method further includes:

[0366] The network-side device configures a target event for the terminal, and the target event is associated with a specific capability framework.

[0367] The target event includes at least one of the following:

[0368] Received a specific scheduling physical downlink control channel (PDCCH);

[0369] The average data rate within the observation window satisfies the first condition;

[0370] The average monitoring energy efficiency within the observation window meets the second condition;

[0371] The terminal's battery level meets the third condition;

[0372] The energy efficiency of the terminal meets the fourth condition;

[0373] The reference signal received power RSRP of the terminal satisfies the fifth condition.

[0374] In some implementations, the specific scheduling PDCCH is: a scheduling PDCCH that satisfies the sixth condition;

[0375] The sixth condition includes at least one of the following:

[0376] The number of frequency domain units scheduled is no greater than a first set value;

[0377] The scheduled transport block size (TBS) is no larger than the second set value.

[0378] In some embodiments, the method further includes at least one of the following:

[0379] The network-side device receives the target conversion time sent by the terminal;

[0380] The network-side device sends the target conversion time configuration to the terminal;

[0381] The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

[0382] In some implementations, one of the at least two capability frames is the default capability frame; the method further includes at least one of the following:

[0383] The network-side device receives the default capability framework sent by the terminal;

[0384] The network-side device sends the configuration of the default capability framework to the terminal.

[0385] In some implementations, the capability parameters in the capability framework include at least one of the following:

[0386] The number of Tx branches in the terminal's transmission lines;

[0387] The number of Rx branches in the terminal's receiving lines;

[0388] The maximum number of downlink MIMO layers supported by the terminal;

[0389] The maximum number of layers supported by uplink MIMO in the terminal;

[0390] The peak downlink rate supported by the terminal;

[0391] The peak uplink rate supported by the terminal;

[0392] The number of downlink carriers supported by the terminal;

[0393] The number of uplink carriers supported by the terminal;

[0394] Uplink subcarrier spacing supported by the terminal;

[0395] Downlink subcarrier spacing supported by the terminal;

[0396] Downlink carrier bandwidth supported by the terminal;

[0397] Uplink carrier bandwidth supported by the terminal;

[0398] The downlink modulation and coding scheme MCS level or the maximum downlink MCS level supported by the terminal;

[0399] The uplink MCS level supported by the terminal or the maximum uplink MCS level;

[0400] The number of downlink Hybrid Automatic Repeat Request (HARQ) processes supported by the terminal;

[0401] The number of uplink HARQ processes supported by the terminal;

[0402] The number of blind detection PDCCHs or control channel elements (CCEs) supported by the terminal;

[0403] Budget for DCI size supported by the terminal;

[0404] The number of central processing units (CPUs), ports, or resources supported by the terminal for handling CSI calculations;

[0405] The maximum downlink transport block size (TBS) supported by the terminal;

[0406] Maximum uplink TBS supported by the terminal;

[0407] End-to-end latency requirements supported by the terminal;

[0408] The terminal supports discontinuous reception DRX configuration;

[0409] Processing delay requirements for receiving data through at least one downlink channel of the terminal;

[0410] Preparation delay requirement for at least one uplink channel transmission by the terminal;

[0411] Reliability requirements supported by the terminal;

[0412] The mobility requirements supported by the terminal;

[0413] Downlink synchronization requirements of the terminal;

[0414] Uplink synchronization requirements of the terminal;

[0415] Error vector amplitude (EVM) requirements for terminal-processed signals;

[0416] EVM requirements for signals transmitted by the terminal;

[0417] Terminal Radio Resource Management (RRM) Measurement Requirements;

[0418] Wireless link monitoring (RLM) measurement requirements for terminals;

[0419] Duplex requirements supported by the terminal;

[0420] The range of frequency bands supported by the terminal;

[0421] Does the terminal support AI capabilities, or does the terminal support AI capabilities?

[0422] Does the terminal support sensing capabilities, or does the terminal support sensing capabilities?

[0423] It should be noted that the terminal capability switching method embodiment provided in this application is a network-side device-side method embodiment corresponding to the terminal capability switching method embodiment described in the first aspect, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0424] The terminal capability switching method provided in this application can be executed by a terminal capability switching device. This application uses the example of a terminal capability switching device executing the terminal capability switching method to illustrate the terminal capability switching device provided in this application.

[0425] This application provides a terminal capability switching device. As an example, the terminal capability switching device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0426] The terminal capability switching device includes a receiving module (e.g., a first receiving module or a second receiving module), a transmitting module (e.g., a first transmitting module or a second transmitting module), and a processing module (e.g., a first processing module or a second processing module). The receiving module, transmitting module, and processing module can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as CPUs, microprocessors, digital signal processors (DSPs), AI processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving module and transmitting module can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0427] Specifically, referring to Figure 7, when the terminal capability switching device is a terminal or a component within a terminal, the terminal capability switching device 700 includes a first processing module 701, used to perform at least one of the following operations:

[0428] Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks;

[0429] The terminal itself is triggered to switch between the at least two capability frameworks;

[0430] The at least two capability frameworks include capability parameters with different values.

[0431] Optionally, the device further includes:

[0432] The first sending module 702 is used to send information related to supporting multi-capability frameworks to the network-side device;

[0433] The information related to the support for the multi-capability framework includes at least one of the following:

[0434] The at least two capability frameworks;

[0435] The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks.

[0436] The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

[0437] Optionally, the information related to supporting multiple capability frameworks includes the at least two capability frameworks;

[0438] The first sending module 702 is further configured to perform at least one of the following to send information related to supporting a multi-capability framework to the network-side device:

[0439] Send the combination of capability parameter values ​​corresponding to each of the at least two capability frames to the network-side device;

[0440] Send to the network-side device the parameter values ​​of one or more capability parameters associated with the at least two capability frames under different indices, where the different indices correspond to different capability frames;

[0441] Send the combination of capability parameter values ​​corresponding to different parts of the at least two capability frames to the network-side device;

[0442] The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

[0443] Optionally, the first processing module 701 is further configured to perform at least one of the following to trigger the terminal itself to perform a switch between the at least two capability frameworks:

[0444] After sending a capability framework switching request to the network-side device, switch to the target capability framework;

[0445] After sending the capability framework switching request to the network-side device and receiving confirmation, switch to the target capability framework;

[0446] Send the capability framework switching request to the network-side device, and switch to the target capability framework after a set time elapsed after receiving confirmation feedback.

[0447] Optionally, the first processing module 701 is further configured to determine, based on the information of the terminal itself, whether to trigger the terminal to perform a switch between the at least two capability frameworks;

[0448] The terminal's own information includes at least one of the following: terminal service status, terminal battery level, and terminal energy efficiency.

[0449] Optionally, the first processing module 701 is further configured to determine the target capability framework that the terminal itself needs to switch to based on the target indication information sent by the network-side device;

[0450] The target indication information includes at least one of the following:

[0451] Index of the target capability framework;

[0452] A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit;

[0453] The start time at which the target capability framework takes effect;

[0454] The duration for which the target capability framework is in effect;

[0455] The end time of the effective period of the target capability framework;

[0456] Information used to instruct the terminal to switch the currently used capability framework.

[0457] Optionally, the first processing module 701 is further configured to perform at least one of the following:

[0458] After receiving the target indication information, the system switches to the target capability framework after a first time period.

[0459] After a second period of time following the feedback of the target indication information, the system switches to the target capability framework.

[0460] Optionally, the target indication information is carried by at least one of the following:

[0461] System information;

[0462] Radio Resource Control (RRC) signaling;

[0463] Media Access Control (MAC) control element CE;

[0464] Downlink Control Information (DCI);

[0465] Wake-up signal.

[0466] Optionally, the device further includes:

[0467] The first sending module 702 is used to send auxiliary information to the network-side device;

[0468] The auxiliary information includes at least one of the following:

[0469] The desired capability framework of the terminal;

[0470] The terminal predicts the business situation within the target time period;

[0471] The terminal's battery status;

[0472] The energy efficiency monitoring status of the terminal;

[0473] The average data transmission rate monitoring status of the terminal.

[0474] Optionally, the device further includes:

[0475] The first receiving module 703 is configured to receive the first information sent by the network-side device when the operation performed by the terminal includes performing a switch between the at least two capability frames based on the first information sent by the network-side device, wherein the first information includes at least one of the following: indication information related to capability frame switching, configuration information, and working mode.

[0476] Different working modes are associated with different capability frameworks, and the configuration information is: the configuration associated with each of the at least two capability frameworks.

[0477] Optionally, the first processing module 701 is further configured to perform data transmission using the configuration associated with the capability framework used by the terminal itself.

[0478] Optionally, the first processing module 701 is further configured to perform the following steps:

[0479] If the received operating mode is energy-saving mode, switch to the first capability framework;

[0480] When the received operating mode is non-energy-saving mode, switch to the second capability framework. The first capability framework and the second capability framework are different capability frameworks.

[0481] Optionally, the configuration information includes at least one of the following:

[0482] Partial bandwidth BWP configuration;

[0483] Service community configuration;

[0484] Uplink channel configuration;

[0485] Uplink signal configuration;

[0486] Downlink channel configuration;

[0487] Downlink signal configuration;

[0488] Scheduler request SR configuration;

[0489] Cache Status Report (BSR) configuration;

[0490] Channel Status Information (CSI) reporting configuration;

[0491] Carrier configuration;

[0492] Frequency band configuration;

[0493] Timer.

[0494] Optionally, the configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration;

[0495] The first processing module 701 is further configured to perform at least one of the following operations based on the configuration information:

[0496] Switch to the capability framework associated with the active BWP;

[0497] Switch to the capability framework associated with the active Carrier;

[0498] Switch to the capability framework associated with the active Band.

[0499] Optionally, the handover reservation time requirement for at least one of the BWP, the Carrier, and the Band, when involving a switch of the terminal capability framework, is different from the handover reservation time requirement when not involving a switch of the terminal capability framework.

[0500] Optionally, the configuration information includes a timer; the first processing module 701 is further configured to perform the following steps:

[0501] When the Timer is running, the terminal switches to the third capability framework associated with the Timer, which starts running when the terminal begins to use the third capability framework;

[0502] In response to the detection of the Timer expired (Expired), the terminal switches to the fourth capability framework associated with the Timer, which expired when its runtime exceeded the set usage time of the third capability framework. The third and fourth capability frameworks are different capability frameworks.

[0503] Optionally, the first processing module 701 is further configured to switch to the fifth capability framework when the target event is met;

[0504] The target event includes at least one of the following:

[0505] Received a specific scheduling physical downlink control channel (PDCCH);

[0506] The average data rate within the observation window satisfies the first condition;

[0507] The average monitoring energy efficiency within the observation window meets the second condition;

[0508] The terminal's battery level meets the third condition;

[0509] The energy efficiency of the terminal meets the fourth condition;

[0510] The reference signal received power RSRP of the terminal satisfies the fifth condition.

[0511] Optionally, the specific scheduling PDCCH is: a scheduling PDCCH that satisfies the sixth condition;

[0512] The sixth condition includes at least one of the following:

[0513] The number of frequency domain units scheduled is no greater than a first set value;

[0514] The scheduled transport block size (TBS) is no larger than the second set value.

[0515] Optionally, the first processing module 701 is further configured to perform at least one of the following during the execution process of switching from one capability framework to another:

[0516] No downlink reception is performed;

[0517] No uplink transmission is performed;

[0518] No measurements were taken.

[0519] Optionally, the device further includes:

[0520] The first receiving module 703 is used to receive the target conversion time configuration sent by the network-side device;

[0521] And / or, the first processing module 701 is further configured to determine the target conversion time;

[0522] The device further includes:

[0523] The first sending module 702 is used to send the target conversion time to the network-side device;

[0524] The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

[0525] Optionally, one of the at least two capability frames is the default capability frame;

[0526] The first processing module 701 is further configured to perform data transmission using the default capability framework when target conditions are met, wherein the target conditions include at least one of the following:

[0527] The terminal is in a disconnected state;

[0528] The terminal is in the process of random access;

[0529] The terminal did not receive any instruction information related to the capability framework.

[0530] Optionally, one of the at least two capability frames is the default capability frame;

[0531] The device further includes:

[0532] The first receiving module 703 is used to receive the configuration of the default capability framework sent by the network-side device;

[0533] And / or, the first processing module 701 is further configured to determine a default capability framework;

[0534] The device further includes:

[0535] The first sending module 702 is used to send the default capability framework to the network-side device.

[0536] Optionally, the capability parameters in the capability framework include at least one of the following:

[0537] The number of Tx branches in the terminal's transmission lines;

[0538] The number of Rx branches in the terminal's receiving lines;

[0539] The maximum number of downlink MIMO layers supported by the terminal;

[0540] The maximum number of layers supported by uplink MIMO in the terminal;

[0541] The peak downlink rate supported by the terminal;

[0542] The peak uplink rate supported by the terminal;

[0543] The number of downlink carriers supported by the terminal;

[0544] The number of uplink carriers supported by the terminal;

[0545] Uplink subcarrier spacing supported by the terminal;

[0546] Downlink subcarrier spacing supported by the terminal;

[0547] Downlink carrier bandwidth supported by the terminal;

[0548] Uplink carrier bandwidth supported by the terminal;

[0549] The downlink modulation and coding scheme MCS level or the maximum downlink MCS level supported by the terminal;

[0550] The uplink MCS level supported by the terminal or the maximum uplink MCS level;

[0551] The number of downlink Hybrid Automatic Repeat Request (HARQ) processes supported by the terminal;

[0552] The number of uplink HARQ processes supported by the terminal;

[0553] The number of blind detection PDCCHs or control channel elements (CCEs) supported by the terminal;

[0554] Budget for DCI size supported by the terminal;

[0555] The number of central processing units (CPUs), ports, or resources supported by the terminal for handling CSI calculations;

[0556] The maximum downlink transport block size (TBS) supported by the terminal;

[0557] Maximum uplink TBS supported by the terminal;

[0558] End-to-end latency requirements supported by the terminal;

[0559] The terminal supports discontinuous reception DRX configuration;

[0560] Processing delay requirements for receiving data through at least one downlink channel of the terminal;

[0561] Preparation delay requirement for at least one uplink channel transmission by the terminal;

[0562] Reliability requirements supported by the terminal;

[0563] The mobility requirements supported by the terminal;

[0564] Downlink synchronization requirements of the terminal;

[0565] Uplink synchronization requirements of the terminal;

[0566] Error vector amplitude (EVM) requirements for terminal-processed signals;

[0567] EVM requirements for signals transmitted by the terminal;

[0568] Terminal Radio Resource Management (RRM) Measurement Requirements;

[0569] Wireless link monitoring (RLM) measurement requirements for terminals;

[0570] Duplex requirements supported by the terminal;

[0571] The range of frequency bands supported by the terminal;

[0572] Does the terminal support artificial intelligence (AI) capabilities, or does the terminal support AI capabilities?

[0573] Does the terminal support sensing capabilities, or does the terminal support sensing capabilities?

[0574] Referring to Figure 8, when the terminal capability switching device is a network-side device or a component of a network-side device, the terminal capability switching device 800 includes at least one of the following:

[0575] The second sending module 801 is used to send first information to a terminal that supports at least two capability frameworks;

[0576] The second receiving module 802 is used to receive the capability framework switching request sent by the terminal;

[0577] The first information is information related to the terminal performing a switch between the at least two capability frames, wherein the at least two capability frames include capability parameters with different values.

[0578] Optionally, the second receiving module 802 is further configured to receive information related to the support for a multi-capability framework sent by the terminal;

[0579] The information related to the support for the multi-capability framework includes at least one of the following:

[0580] The at least two capability frameworks;

[0581] The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks.

[0582] The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

[0583] Optionally, the information related to supporting multiple capability frameworks includes the at least two capability frameworks;

[0584] The second receiving module 802 is further configured to perform at least one of the following to receive information related to the multi-capability framework sent by the terminal:

[0585] Receive the combination of capability parameter values ​​corresponding to each of the at least two capability frames sent by the terminal;

[0586] The terminal sends parameter values ​​of one or more capability parameters associated with the at least two capability frameworks under different indices, where the different indices correspond to different capability frameworks.

[0587] Receive the combination of capability parameter values ​​corresponding to different parts of the at least two capability frames sent by the terminal;

[0588] The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

[0589] Optionally, the capability framework switching request includes: relevant information about the target capability framework to which the terminal requests to switch; the device further includes:

[0590] The second processing module 803 is used to determine, based on network congestion or cell service status, whether to send a confirmation feedback corresponding to the capability framework switching request to the terminal after the network-side device receives the capability framework switching request sent by the terminal.

[0591] Optionally, the second sending module 801 is further configured to send target indication information to the terminal, the target indication information being used to indicate the target capability framework to which the terminal needs to switch;

[0592] The target indication information includes at least one of the following:

[0593] Index of the target capability framework;

[0594] A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit;

[0595] The start time at which the target capability framework takes effect;

[0596] The duration for which the target capability framework is in effect;

[0597] The end time of the effective period of the target capability framework;

[0598] Information used to instruct the terminal to switch the currently used capability framework.

[0599] Optionally, the target indication information is carried by at least one of the following:

[0600] System information;

[0601] Radio Resource Control (RRC) signaling;

[0602] Media Access Control (MAC) control element CE;

[0603] Downlink Control Information (DCI);

[0604] Wake-up signal.

[0605] Optionally, the second receiving module 802 is further configured to receive auxiliary information sent by the terminal before the network-side device sends target indication information to the terminal;

[0606] The second processing module 803 is used to determine the target capability framework that the terminal needs to switch to based on the auxiliary information;

[0607] The auxiliary information includes at least one of the following:

[0608] The desired capability framework of the terminal;

[0609] The terminal predicts the business situation within the target time period;

[0610] The terminal's battery status;

[0611] The energy efficiency monitoring status of the terminal;

[0612] The average data transmission rate monitoring status of the terminal.

[0613] Optionally, the first information includes at least one of the following:

[0614] Instructions related to capability framework switching;

[0615] Configuration information, which includes the configuration associated with each of the at least two capability frameworks;

[0616] Work modes, and different work modes are associated with different competency frameworks.

[0617] Optionally, the configuration information includes at least one of the following:

[0618] Partial bandwidth BWP configuration;

[0619] Service community configuration;

[0620] Uplink channel configuration;

[0621] Uplink signal configuration;

[0622] Downlink channel configuration;

[0623] Downlink signal configuration;

[0624] Scheduler request SR configuration;

[0625] Cache Status Report (BSR) configuration;

[0626] Downlink Control Information (CSI) reporting configuration;

[0627] Carrier configuration;

[0628] Frequency band configuration;

[0629] Timer.

[0630] Optionally, the configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration;

[0631] The second processing module 803 is used to activate at least one of the BWP, Carrier, and Band associated with the target capability framework to which the terminal needs to switch.

[0632] Optionally, the handover reservation time requirement for at least one of the BWP, the Carrier, and the Band, when involving a switch of the terminal capability framework, is different from the handover reservation time requirement when not involving a switch of the terminal capability framework.

[0633] Optionally, the configuration information includes a Timer that satisfies the following conditions: it starts running when the terminal begins to use a specific capability framework, and it expires when the running time exceeds the set usage time of the specific capability framework.

[0634] Optionally, the device further includes:

[0635] The second processing module 803 is used to configure a target event for the terminal, the target event being associated with a specific capability framework;

[0636] The target event includes at least one of the following:

[0637] Received a specific scheduling physical downlink control channel (PDCCH);

[0638] The average data rate within the observation window satisfies the first condition;

[0639] The average monitoring energy efficiency within the observation window meets the second condition;

[0640] The terminal's battery level meets the third condition;

[0641] The energy efficiency of the terminal meets the fourth condition;

[0642] The reference signal received power RSRP of the terminal satisfies the fifth condition.

[0643] Optionally, the specific scheduling PDCCH is: a scheduling PDCCH that satisfies the sixth condition;

[0644] The sixth condition includes at least one of the following:

[0645] The number of frequency domain units scheduled is no greater than a first set value;

[0646] The scheduled transport block size (TBS) is no larger than the second set value.

[0647] Optionally, the second receiving module 802 is further configured to receive the target conversion time sent by the terminal;

[0648] And / or, the second sending module 801 is further configured to send the configuration of the target conversion time to the terminal;

[0649] The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

[0650] Optionally, one of the at least two capability frames is the default capability frame;

[0651] The second receiving module 802 is further configured to receive the default capability framework sent by the terminal;

[0652] And / or, the second sending module 801 is further configured to send the configuration of the default capability framework to the terminal.

[0653] Optionally, the capability parameters in the capability framework include at least one of the following:

[0654] The number of Tx branches in the terminal's transmission lines;

[0655] The number of Rx branches in the terminal's receiving lines;

[0656] The maximum number of downlink MIMO layers supported by the terminal;

[0657] The maximum number of layers supported by uplink MIMO in the terminal;

[0658] The peak downlink rate supported by the terminal;

[0659] The peak uplink rate supported by the terminal;

[0660] The number of downlink carriers supported by the terminal;

[0661] The number of uplink carriers supported by the terminal;

[0662] Uplink subcarrier spacing supported by the terminal;

[0663] Downlink subcarrier spacing supported by the terminal;

[0664] Downlink carrier bandwidth supported by the terminal;

[0665] Uplink carrier bandwidth supported by the terminal;

[0666] The downlink modulation and coding scheme MCS level or the maximum downlink MCS level supported by the terminal;

[0667] The uplink MCS level supported by the terminal or the maximum uplink MCS level;

[0668] The number of downlink Hybrid Automatic Repeat Request (HARQ) processes supported by the terminal;

[0669] The number of uplink HARQ processes supported by the terminal;

[0670] The number of blind detection PDCCHs or control channel elements (CCEs) supported by the terminal;

[0671] Budget for DCI size supported by the terminal;

[0672] The number of central processing units (CPUs), ports, or resources supported by the terminal for handling CSI calculations;

[0673] The maximum downlink transport block size (TBS) supported by the terminal;

[0674] Maximum uplink TBS supported by the terminal;

[0675] End-to-end latency requirements supported by the terminal;

[0676] The terminal supports discontinuous reception DRX configuration;

[0677] Processing delay requirements for receiving data through at least one downlink channel of the terminal;

[0678] Preparation delay requirement for at least one uplink channel transmission by the terminal;

[0679] Reliability requirements supported by the terminal;

[0680] The mobility requirements supported by the terminal;

[0681] Downlink synchronization requirements of the terminal;

[0682] Uplink synchronization requirements of the terminal;

[0683] Error vector amplitude (EVM) requirements for terminal-processed signals;

[0684] EVM requirements for signals transmitted by the terminal;

[0685] Terminal Radio Resource Management (RRM) Measurement Requirements;

[0686] Wireless link monitoring (RLM) measurement requirements for terminals;

[0687] Duplex requirements supported by the terminal;

[0688] The range of frequency bands supported by the terminal;

[0689] Does the terminal support AI capabilities, or does the terminal support AI capabilities?

[0690] Does the terminal support sensing capabilities, or does the terminal support sensing capabilities?

[0691] In practice, the terminal switches between at least two capability frameworks based on the first information sent by the network-side device or by triggering itself to switch between them. This allows the terminal to switch its supported terminal capabilities from high to low or from low to high, thereby reducing the waste of terminal capabilities while ensuring that the terminal can transmit data normally, thus improving terminal energy efficiency.

[0692] The terminal capability switching device provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 3 to 6 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0693] As shown in Figure 9, this application embodiment also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores a program or instructions that can run on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various steps of the terminal capability switching method embodiment described in the first aspect above, and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various steps of the terminal capability switching method embodiment described in the second aspect above, and achieve the same technical effect. To avoid repetition, this will not be repeated here.

[0694] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG3. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the terminal capability switching device shown in FIG7. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0695] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0696] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 10 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0697] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0698] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1001 can transmit it to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0699] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0700] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor 1010.

[0701] The processor 1010 is configured to perform at least one of the following operations:

[0702] Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks;

[0703] Trigger itself to switch between the at least two capability frameworks;

[0704] The at least two capability frameworks include capability parameters with different values.

[0705] As can be seen from the above steps, the terminal can trigger itself or, based on the first information sent by the network-side device, perform a switch between at least two capability frameworks. That is to say, the terminal can switch between high and low capabilities it supports by changing the values ​​of its own capability parameters. Compared with a terminal that only supports a single terminal capability (i.e., only supports the terminal capability reported by the UE capability report), the terminal in this embodiment of the application can reduce the waste of terminal capabilities during data transmission by performing a switch between high and low capabilities, thereby improving the terminal's energy efficiency.

[0706] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the terminal capability switching method embodiment described in the first aspect, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0707] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG6. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0708] Specifically, this application embodiment also provides a network-side device, which may be the terminal capability switching device shown in FIG8. As shown in FIG11, the network-side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. The antenna 111 is connected to the radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the radio frequency device 112. The radio frequency device 112 processes the received information and transmits it through the antenna 111.

[0709] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 113, which includes a baseband processor.

[0710] The baseband device 113 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG11. One of the chips is, for example, a baseband processor, which is connected to the memory 115 via a bus interface to call the program in the memory 115 and execute the network device operation shown in the above method embodiment.

[0711] The network-side device may also include a network interface 116, such as a Common Public Radio Interface (CPRI).

[0712] Specifically, the network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 115 and executable on processor 114. Processor 114 calls the instructions or programs in memory 115 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0713] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described terminal capability switching method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0714] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0715] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described terminal capability switching method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0716] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0717] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described terminal capability switching method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0718] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the terminal capability switching method as described in the first aspect above, and the network-side device can be used to perform the steps of the terminal capability switching method as described in the second aspect above.

[0719] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0720] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0721] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for switching terminal capabilities, wherein, The method includes: Terminals that support at least two capability frameworks can perform at least one of the following operations: Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks; Trigger itself to switch between the at least two capability frameworks; The at least two capability frameworks include capability parameters with different values.

2. The method according to claim 1, wherein, The method further includes: The terminal sends information related to supporting multi-capability frameworks to the network-side device; The information related to the support for the multi-capability framework includes at least one of the following: The at least two capability frameworks; The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks. The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

3. The method according to claim 2, wherein, The information related to supporting multiple capability frameworks includes the at least two capability frameworks; the terminal sends the information related to supporting multiple capability frameworks to the network-side device, including at least one of the following: The terminal sends a combination of capability parameter values ​​corresponding to each of the at least two capability frames to the network-side device; The terminal sends to the network-side device the parameter values ​​of one or more capability parameters associated with the at least two capability frames under different indices, where the different indices correspond to different capability frames; The terminal sends a combination of capability parameter values ​​corresponding to different parts of the at least two capability frames to the network-side device. The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

4. The method according to any one of claims 1-3, wherein, The triggering of itself to switch between the at least two capability frameworks includes at least one of the following: After sending a capability framework switching request to the network-side device, switch to the target capability framework; After sending the capability framework switching request to the network-side device and receiving confirmation, switch to the target capability framework; Send the capability framework switching request to the network-side device, and switch to the target capability framework after a set time elapsed after receiving confirmation feedback.

5. The method according to any one of claims 1-4, wherein, Before the terminal triggers itself to perform a switch between the at least two capability frameworks, the method further includes: The terminal determines whether to trigger itself to switch between the at least two capability frameworks based on its own information. The terminal's own information includes at least one of the following: terminal service status, terminal battery level, and terminal energy efficiency.

6. The method according to any one of claims 1-5, wherein, The method further includes: The terminal determines the target capability framework it needs to switch to based on the target indication information sent by the network-side device; The target indication information includes at least one of the following: Index of the target capability framework; A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit; The start time at which the target capability framework takes effect; The duration for which the target capability framework is in effect; The end time of the effective period of the target capability framework; Information used to instruct the terminal to switch the currently used capability framework.

7. The method according to claim 6, wherein, The method further includes at least one of the following: The terminal switches to the target capability framework after a first time period following receipt of the target indication information; After a second period of time following the receipt of the target indication information, the terminal switches to the target capability framework.

8. The method according to claim 6 or 7, wherein, The target indication information is carried through at least one of the following: System information; Radio Resource Control (RRC) signaling; Media Access Control (MAC) control element CE; Downlink Control Information (DCI); Wake-up signal.

9. The method according to any one of claims 6-8, wherein, Before the terminal determines the target capability framework it needs to switch to based on the target indication information sent by the network-side device, the method further includes: The terminal sends auxiliary information to the network-side device; The auxiliary information includes at least one of the following: The desired capability framework of the terminal; The terminal predicts the business situation within the target time period; The terminal's battery status; The energy efficiency monitoring status of the terminal; The average data transmission rate monitoring status of the terminal.

10. The method according to any one of claims 1-9, wherein, When the operations performed by the terminal include switching between the at least two capability frameworks based on the first information sent by the network-side device, the method further includes: The terminal receives first information sent by the network-side device, the first information including at least one of: indication information related to capability framework switching, configuration information, and working mode; Different working modes are associated with different capability frameworks, and the configuration information is: the configuration associated with each of the at least two capability frameworks.

11. The method according to claim 10, wherein, The method further includes: The terminal uses the configuration associated with its own capability framework to perform data transmission.

12. The method according to claim 10 or 11, wherein, The method further includes: When the received operating mode is energy-saving mode, the terminal switches to the first capability framework; When the received operating mode is non-energy-saving mode, the terminal switches to the second capability framework, where the first capability framework and the second capability framework are different capability frameworks.

13. The method according to any one of claims 10-12, wherein, The configuration information includes at least one of the following: Partial bandwidth BWP configuration; Service community configuration; Uplink channel configuration; Uplink signal configuration; Downlink channel configuration; Downlink signal configuration; Scheduler request SR configuration; Cache Status Report (BSR) configuration; Channel Status Information (CSI) reporting configuration; Carrier configuration; Frequency band configuration; Timer.

14. The method according to claim 13, wherein, The configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration; the method further includes: The terminal performs at least one of the following operations based on the configuration information: The terminal switches to the capability framework associated with the activated BWP; The terminal switches to the capability framework associated with the activated Carrier; The terminal switches to the capability framework associated with the active Band.

15. The method according to claim 14, wherein, The handover reservation time requirement for at least one of the BWP, the Carrier, and the Band, when involving a handover of the terminal capability framework, is different from the handover reservation time requirement when it does not involve a handover of the terminal capability framework.

16. The method according to any one of claims 13-15, wherein, The configuration information includes a timer; the method further includes: When the Timer is running, the terminal switches to the third capability framework associated with the Timer, which starts running when the terminal begins to use the third capability framework; In response to the detection of the Timer expired (Expired), the terminal switches to the fourth capability framework associated with the Timer, which expired when its runtime exceeded the set usage time of the third capability framework. The third and fourth capability frameworks are different capability frameworks.

17. The method according to any one of claims 1-16, wherein, The method further includes: When the target event is met, the terminal switches to the fifth capability framework; The target event includes at least one of the following: Received a specific scheduling physical downlink control channel (PDCCH); The average data rate within the observation window satisfies the first condition; The average monitoring energy efficiency within the observation window meets the second condition; The terminal's battery level meets the third condition; The energy efficiency of the terminal meets the fourth condition; The reference signal received power RSRP of the terminal satisfies the fifth condition.

18. The method according to claim 17, wherein, The specific scheduling PDCCH is: the scheduling PDCCH that satisfies the sixth condition; The sixth condition includes at least one of the following: The number of frequency domain units scheduled is no greater than a first set value; The scheduled transport block size (TBS) is no larger than the second set value.

19. The method according to any one of claims 1-18, wherein, The method further includes: During the process of switching from one capability framework to another, the terminal performs at least one of the following: No downlink reception is performed; No uplink transmission is performed; No measurements were taken.

20. The method according to any one of claims 1-19, wherein, The method further includes at least one of the following: The terminal determines the target transition time and sends the target transition time to the network-side device. The terminal receives the target conversion time configuration sent by the network-side device; The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

21. The method according to any one of claims 1-20, wherein, One of the at least two capability frameworks is the default capability framework; the method further includes: When the target conditions are met, the terminal uses the default capability framework for data transmission, and the target conditions include at least one of the following: The terminal is in a disconnected state; The terminal is in the process of random access; The terminal did not receive any instruction information related to the capability framework.

22. The method according to any one of claims 1-21, wherein, One of the at least two capability frameworks is the default capability framework; the method further includes at least one of the following: The terminal determines the default capability framework and sends the default capability framework to the network-side device. The terminal receives the configuration of the default capability framework sent by the network-side device.

23. The method according to any one of claims 1-22, wherein, The capability parameters in the capability framework include at least one of the following: The number of Tx branches in the terminal's transmission lines; The number of Rx branches in the terminal's receiving lines; The maximum number of downlink MIMO layers supported by the terminal; The maximum number of layers supported by uplink MIMO in the terminal; The peak downlink rate supported by the terminal; The peak uplink rate supported by the terminal; The number of downlink carriers supported by the terminal; The number of uplink carriers supported by the terminal; Uplink subcarrier spacing supported by the terminal; Downlink subcarrier spacing supported by the terminal; Downlink carrier bandwidth supported by the terminal; Uplink carrier bandwidth supported by the terminal; The downlink modulation and coding scheme MCS level or the maximum downlink MCS level supported by the terminal; The uplink MCS level supported by the terminal or the maximum uplink MCS level; The number of downlink Hybrid Automatic Repeat Request (HARQ) processes supported by the terminal; The number of uplink HARQ processes supported by the terminal; The number of blind detection PDCCHs or control channel elements (CCEs) supported by the terminal; Budget for DCI size supported by the terminal; The number of central processing units (CPUs), ports, or resources supported by the terminal for handling CSI calculations; The maximum downlink transport block size (TBS) supported by the terminal; Maximum uplink TBS supported by the terminal; End-to-end latency requirements supported by the terminal; The terminal supports discontinuous reception DRX configuration; Processing delay requirements for receiving data through at least one downlink channel of the terminal; Preparation delay requirement for at least one uplink channel transmission by the terminal; Reliability requirements supported by the terminal; The mobility requirements supported by the terminal; Downlink synchronization requirements of the terminal; Uplink synchronization requirements of the terminal; Error vector amplitude (EVM) requirements for terminal-processed signals; EVM requirements for signals transmitted by the terminal; Terminal Radio Resource Management (RRM) Measurement Requirements; Wireless link monitoring (RLM) measurement requirements for terminals; Duplex requirements supported by the terminal; The range of frequency bands supported by the terminal; Does the terminal support artificial intelligence (AI) capabilities, or does the terminal support AI capabilities? Does the terminal support sensing capabilities, or does the terminal support sensing capabilities? 24. A method for switching terminal capabilities, wherein, The method includes: The network-side device performs at least one of the following operations: The network-side device sends first information to a terminal that supports at least two capability frameworks; The network-side device receives the capability framework switching request sent by the terminal; The first information is information related to the terminal performing a switch between the at least two capability frames, wherein the at least two capability frames include capability parameters with different values.

25. The method according to claim 24, wherein, The method further includes: The network-side device receives information related to the multi-capability framework sent by the terminal. The information related to the support for the multi-capability framework includes at least one of the following: The at least two capability frameworks; The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks. The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

26. The method according to claim 24 or 25, wherein, The information related to supporting multiple capability frameworks includes the at least two capability frameworks; the network-side device receives the information related to supporting multiple capability frameworks sent by the terminal, including at least one of the following: The network-side device receives a combination of capability parameter values ​​corresponding to each of the at least two capability frames from the terminal. The network-side device receives parameter values ​​from the terminal for one or more capability parameters associated with the at least two capability frames under different indices, where the different indices correspond to different capability frames. The network-side device receives from the terminal a combination of capability parameter values ​​corresponding to different parts of the at least two capability frames; The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

27. The method according to any one of claims 24-26, wherein, The capability framework switching request includes: relevant information about the target capability framework to which the terminal requests to switch; After the network-side device receives the capability framework switching request sent by the terminal, the method further includes: The network-side device determines whether to send a confirmation feedback corresponding to the capability framework switching request to the terminal based on network congestion or cell service status.

28. The method according to any one of claims 24-27, wherein, The method further includes: The network-side device sends target indication information to the terminal, the target indication information being used to indicate the target capability framework that the terminal needs to switch to; The target indication information includes at least one of the following: Index of the target capability framework; A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit; The start time at which the target capability framework takes effect; The duration for which the target capability framework is in effect; The end time of the effective period of the target capability framework; Information used to instruct the terminal to switch the currently used capability framework.

29. The method according to claim 28, wherein, The target indication information is carried through at least one of the following: System information; Radio Resource Control (RRC) signaling; Media Access Control (MAC) control element CE; Downlink Control Information (DCI); Wake-up signal.

30. The method according to claim 28 or 29, wherein, Before the network-side device sends target indication information to the terminal, the method further includes: The network-side device receives auxiliary information sent by the terminal; The network-side device determines the target capability framework that the terminal needs to switch to based on the auxiliary information; The auxiliary information includes at least one of the following: The desired capability framework of the terminal; The terminal predicts the business situation within the target time period; The terminal's battery status; The energy efficiency monitoring status of the terminal; The average data transmission rate monitoring status of the terminal.

31. The method according to any one of claims 24-30, wherein, The first information includes at least one of the following: Instructions related to capability framework switching; Configuration information, which includes the configuration associated with each of the at least two capability frameworks; Work modes, and different work modes are associated with different competency frameworks.

32. The method according to claim 31, wherein, The configuration information includes at least one of the following: Partial bandwidth BWP configuration; Service community configuration; Uplink channel configuration; Uplink signal configuration; Downlink channel configuration; Downlink signal configuration; Scheduler request SR configuration; Cache Status Report (BSR) configuration; Downlink Control Information (CSI) reporting configuration; Carrier configuration; Frequency band configuration; Timer.

33. The method according to claim 32, wherein, The configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration; the method further includes: The network-side device activates at least one of the BWP, Carrier, and Band associated with the target capability framework to which the terminal needs to switch.

34. The method according to claim 33, wherein, The handover reservation time requirement for at least one of the BWP, the Carrier, and the Band, when involving a handover of the terminal capability framework, is different from the handover reservation time requirement when it does not involve a handover of the terminal capability framework.

35. The method according to any one of claims 31-34, wherein, The configuration information includes a Timer, which satisfies the following conditions: it starts running when the terminal begins to use a specific capability framework, and it expires when the running time exceeds the set usage time of the specific capability framework.

36. The method according to any one of claims 24-35, wherein, The method further includes: The network-side device configures a target event for the terminal, and the target event is associated with a specific capability framework. The target event includes at least one of the following: Received a specific scheduling physical downlink control channel (PDCCH); The average data rate within the observation window satisfies the first condition; The average monitoring energy efficiency within the observation window meets the second condition; The terminal's battery level meets the third condition; The energy efficiency of the terminal meets the fourth condition; The reference signal received power RSRP of the terminal satisfies the fifth condition.

37. The method of claim 36, wherein, The specific scheduling PDCCH is: the scheduling PDCCH that satisfies the sixth condition; The sixth condition includes at least one of the following: The number of frequency domain units scheduled is no greater than a first set value; The scheduled transport block size (TBS) is no larger than the second set value.

38. The method according to any one of claims 24-37, wherein, The method further includes at least one of the following: The network-side device receives the target conversion time sent by the terminal; The network-side device sends the target conversion time configuration to the terminal; The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

39. The method according to any one of claims 24-38, wherein, One of the at least two capability frameworks is the default capability framework; the method further includes at least one of the following: The network-side device receives the default capability framework sent by the terminal; The network-side device sends the configuration of the default capability framework to the terminal.

40. The method according to any one of claims 24-39, wherein, The capability parameters in the capability framework include at least one of the following: The number of Tx branches in the terminal's transmission lines; The number of Rx branches in the terminal's receiving lines; The maximum number of downlink MIMO layers supported by the terminal; The maximum number of layers supported by uplink MIMO in the terminal; The peak downlink rate supported by the terminal; The peak uplink rate supported by the terminal; The number of downlink carriers supported by the terminal; The number of uplink carriers supported by the terminal; Uplink subcarrier spacing supported by the terminal; Downlink subcarrier spacing supported by the terminal; Downlink carrier bandwidth supported by the terminal; Uplink carrier bandwidth supported by the terminal; The downlink modulation and coding scheme MCS level or the maximum downlink MCS level supported by the terminal; The uplink MCS level supported by the terminal or the maximum uplink MCS level; The number of downlink Hybrid Automatic Repeat Request (HARQ) processes supported by the terminal; The number of uplink HARQ processes supported by the terminal; The number of blind detection PDCCHs or control channel elements (CCEs) supported by the terminal; Budget for DCI size supported by the terminal; The number of central processing units (CPUs), ports, or resources supported by the terminal for handling CSI calculations; The maximum downlink transport block size (TBS) supported by the terminal; Maximum uplink TBS supported by the terminal; End-to-end latency requirements supported by the terminal; The terminal supports discontinuous reception DRX configuration; Processing delay requirements for receiving data through at least one downlink channel of the terminal; Preparation delay requirement for at least one uplink channel transmission by the terminal; Reliability requirements supported by the terminal; The mobility requirements supported by the terminal; Downlink synchronization requirements of the terminal; Uplink synchronization requirements of the terminal; Error vector amplitude (EVM) requirements for terminal-processed signals; EVM requirements for signals transmitted by the terminal; Terminal Radio Resource Management (RRM) Measurement Requirements; Wireless link monitoring (RLM) measurement requirements for terminals; Duplex requirements supported by the terminal; The range of frequency bands supported by the terminal; Does the terminal support AI capabilities, or does the terminal support AI capabilities? Does the terminal support sensing capabilities, or does the terminal support sensing capabilities? 41. A terminal capability switching device, wherein, The device, applicable to terminals supporting at least two capability frameworks, includes: The first processing module is configured to perform at least one of the following operations: Based on the first information sent by the network-side device, perform a switch between the at least two capability frameworks; The terminal itself is triggered to switch between the at least two capability frameworks; The at least two capability frameworks include capability parameters with different values.

42. The apparatus according to claim 41, wherein, The device further includes: The first sending module is used to send information related to supporting multi-capability frameworks to the network-side device; The information related to the support for the multi-capability framework includes at least one of the following: The at least two capability frameworks; The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks. The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

43. The apparatus according to claim 42, wherein, The information related to supporting multiple capability frameworks includes the at least two capability frameworks; The first sending module is further configured to perform at least one of the following to send information related to supporting a multi-capability framework to the network-side device: Send the combination of capability parameter values ​​corresponding to each of the at least two capability frames to the network-side device; Send to the network-side device the parameter values ​​of one or more capability parameters associated with the at least two capability frames under different indices, where the different indices correspond to different capability frames; Send the combination of capability parameter values ​​corresponding to different parts of the at least two capability frames to the network-side device; The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

44. The apparatus according to any one of claims 41-43, wherein, The first processing module is further configured to perform at least one of the following to trigger the terminal itself to perform a switch between the at least two capability frameworks: After sending a capability framework switching request to the network-side device, switch to the target capability framework; After sending the capability framework switching request to the network-side device and receiving confirmation, switch to the target capability framework; Send the capability framework switching request to the network-side device, and switch to the target capability framework after a set time elapsed after receiving confirmation feedback.

45. The apparatus according to any one of claims 41-44, wherein, The first processing module is further configured to determine, based on the terminal's own information, whether to trigger the terminal itself to switch between the at least two capability frameworks; The terminal's own information includes at least one of the following: terminal service status, terminal battery level, and terminal energy efficiency.

46. ​​The apparatus according to any one of claims 41-45, wherein, The first processing module is further configured to determine the target capability framework that the terminal itself needs to switch to based on the target indication information sent by the network-side device; The target indication information includes at least one of the following: Index of the target capability framework; A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit; The start time at which the target capability framework takes effect; The duration for which the target capability framework is in effect; The end time of the effective period of the target capability framework; Information used to instruct the terminal to switch the currently used capability framework.

47. The apparatus according to claim 46, wherein, The first processing module is further configured to perform at least one of the following: After receiving the target indication information, the system switches to the target capability framework after a first time period. After a second period of time following the feedback of the target indication information, the system switches to the target capability framework.

48. The apparatus according to claim 46 or 47, wherein, The device further includes: The first sending module is used to send auxiliary information to the network-side device; The auxiliary information includes at least one of the following: The desired capability framework of the terminal; The terminal predicts the business situation within the target time period; The terminal's battery status; The energy efficiency monitoring status of the terminal; The average data transmission rate monitoring status of the terminal.

49. The apparatus according to any one of claims 41-48, wherein, The device further includes: The first receiving module is configured to receive the first information sent by the network-side device when the operation performed by the terminal includes switching between the at least two capability frames based on the first information sent by the network-side device, wherein the first information includes at least one of the following: indication information related to capability frame switching, configuration information, and working mode. Different working modes are associated with different capability frameworks, and the configuration information is: the configuration associated with each of the at least two capability frameworks.

50. The apparatus according to claim 49, wherein, The first processing module is also used to perform data transmission using the configuration associated with the capability framework used by the terminal itself.

51. The apparatus according to claim 49 or 50, wherein, The first processing module is further configured to perform the following steps: If the received operating mode is energy-saving mode, switch to the first capability framework; When the received operating mode is non-energy-saving mode, switch to the second capability framework. The first capability framework and the second capability framework are different capability frameworks.

52. The apparatus according to claim 49, wherein, The configuration information includes at least one of BWP configuration, Carrier configuration, and Band configuration; The first processing module is further configured to perform at least one of the following operations based on the configuration information: Switch to the capability framework associated with the active BWP; Switch to the capability framework associated with the active Carrier; Switch to the capability framework associated with the active Band.

53. The apparatus according to claim 49, wherein, The configuration information includes a timer; the first processing module is further configured to perform the following steps: When the Timer is running, the terminal switches to the third capability framework associated with the Timer, which starts running when the terminal begins to use the third capability framework; In response to the detection of the Timer expired (Expired), the terminal switches to the fourth capability framework associated with the Timer, which expired when its runtime exceeded the set usage time of the third capability framework. The third and fourth capability frameworks are different capability frameworks.

54. The apparatus according to any one of claims 41-53, wherein, The first processing module is also used to switch to the fifth capability framework when the target event is met; The target event includes at least one of the following: Received a specific scheduling physical downlink control channel (PDCCH); The average data rate within the observation window satisfies the first condition; The average monitoring energy efficiency within the observation window meets the second condition; The terminal's battery level meets the third condition; The energy efficiency of the terminal meets the fourth condition; The reference signal received power RSRP of the terminal satisfies the fifth condition.

55. The apparatus according to any one of claims 41-54, wherein, The first processing module is further configured to perform at least one of the following during the execution process of switching from one capability framework to another: No downlink reception is performed; No uplink transmission is performed; No measurements were taken.

56. The apparatus according to any one of claims 41-55, wherein, The device further includes: The first receiving module is used to receive the target conversion time configuration sent by the network-side device; And / or, the first processing module is further configured to determine the target conversion time; The device further includes: The first sending module is used to send the target conversion time to the network-side device; The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

57. The apparatus according to any one of claims 41-56, wherein, One of the at least two capability frameworks is the default capability framework; The first processing module is further configured to perform data transmission using the default capability framework when target conditions are met, wherein the target conditions include at least one of the following: The terminal is in a disconnected state; The terminal is in the process of random access; The terminal did not receive any instruction information related to the capability framework.

58. The apparatus according to any one of claims 41-57, wherein, One of the at least two capability frameworks is the default capability framework; The device further includes: The first receiving module is used to receive the configuration of the default capability framework sent by the network-side device; And / or, the first processing module is further configured to determine a default capability framework; The device further includes: The first sending module is used to send the default capability framework to the network-side device.

59. A terminal capability switching device, wherein, Applied to network-side devices, the device includes at least one of the following: The second sending module is used to send the first information to a terminal that supports at least two capability frameworks; The second receiving module is used to receive the capability framework switching request sent by the terminal; The first information is information related to the terminal performing a switch between the at least two capability frames, wherein the at least two capability frames include capability parameters with different values.

60. The apparatus according to claim 59, wherein, The second receiving module is also used to receive information related to the support of a multi-capability framework sent by the terminal; The information related to the support for the multi-capability framework includes at least one of the following: The at least two capability frameworks; The second piece of information describes that the terminal supports data transmission using the at least two capability frameworks. The third piece of information describes that the terminal supports switching between the at least two capability frameworks.

61. The apparatus according to claim 59 or 60, wherein, The information related to supporting multiple capability frameworks includes the at least two capability frameworks; The second receiving module is further configured to perform at least one of the following to receive information related to the multi-capability framework sent by the terminal: Receive the combination of capability parameter values ​​corresponding to each of the at least two capability frames sent by the terminal; The terminal sends parameter values ​​of one or more capability parameters associated with the at least two capability frameworks under different indices, where the different indices correspond to different capability frameworks. Receive the combination of capability parameter values ​​corresponding to different parts of the at least two capability frames sent by the terminal; The combination of capability parameter values ​​includes the parameter value of at least one capability parameter.

62. The apparatus according to any one of claims 59-61, wherein, The capability framework switching request includes: information related to the target capability framework to which the terminal requests to switch; the device further includes: The second processing module is used to determine, after the network-side device receives the capability framework switching request sent by the terminal, whether to send a confirmation feedback corresponding to the capability framework switching request to the terminal based on the network congestion situation or the cell service status.

63. The apparatus according to any one of claims 59-62, wherein, The second sending module is further configured to send target indication information to the terminal, the target indication information being used to indicate the target capability framework to which the terminal needs to switch; The target indication information includes at least one of the following: Index of the target capability framework; A bitmap, wherein each bit in the bitmap is used to indicate whether the terminal needs to use the capability framework corresponding to each bit; The start time at which the target capability framework takes effect; The duration for which the target capability framework is in effect; The end time of the effective period of the target capability framework; Information used to instruct the terminal to switch the currently used capability framework.

64. The apparatus according to claim 63, wherein, The second receiving module is further configured to receive auxiliary information sent by the terminal before the network-side device sends target indication information to the terminal; The device further includes: The second processing module is used to determine the target capability framework that the terminal needs to switch to based on the auxiliary information. The auxiliary information includes at least one of the following: The desired capability framework of the terminal; The terminal predicts the business situation within the target time period; The terminal's battery status; The energy efficiency monitoring status of the terminal; The average data transmission rate monitoring status of the terminal.

65. The apparatus according to any one of claims 59-64, wherein, The first information includes at least configuration information, which includes at least one of BWP configuration, Carrier configuration, and Band configuration; the device further includes: The second processing module is used to activate at least one of the BWP, Carrier, and Band associated with the target capability framework to which the terminal needs to switch.

66. The apparatus according to any one of claims 59-65, wherein, The device further includes: The second processing module is used to configure target events for the terminal, the target events being associated with a specific capability framework; The target event includes at least one of the following: Received a specific scheduling physical downlink control channel (PDCCH); The average data rate within the observation window satisfies the first condition; The average monitoring energy efficiency within the observation window meets the second condition; The terminal's battery level meets the third condition; The energy efficiency of the terminal meets the fourth condition; The reference signal received power RSRP of the terminal satisfies the fifth condition.

67. The apparatus according to any one of claims 59-66, wherein, The second receiving module is further configured to receive the target conversion time sent by the terminal; And / or, the second sending module is further configured to send the configuration of the target conversion time to the terminal; The target conversion time is the time reserved for the execution process of the terminal switching from one capability framework to another.

68. The apparatus according to any one of claims 59-67, wherein, One of the at least two capability frameworks is the default capability framework; The second receiving module is further configured to receive the default capability framework sent by the terminal; And / or, the second sending module is further configured to send the configuration of the default capability framework to the terminal.

69. A terminal, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the terminal capability switching method as described in any one of claims 1 to 23.

70. A network-side device, wherein, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the terminal capability switching steps as described in any one of claims 24 to 40.

71. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the terminal capability switching method as described in any one of claims 1 to 23, or implement the steps of the terminal capability switching method as described in any one of claims 24 to 40.

Images