Wireless communication method and device

Abstract

Embodiments of the present application provide a wireless communication method and a device. A terminal device can support various capability sets, and can activate some of the capability sets supported by the terminal device. Different capability sets may correspond to different performances, such that more refined terminal energy saving can be realized. The wireless communication method comprises: a terminal device activates N capability sets among M capability sets supported by the terminal device, wherein M and N are both positive integers, M≥2 and N=1, or N≥2 and N<M.

Description

Wireless communication method and device Technical Field

[0001] The present invention relates to the field of communications, and more specifically, to a method and device for wireless communications. Background Art

[0002] Currently, to achieve terminal energy conservation, New Radio (NR) terminal functions can be tailored, reducing terminal and network performance in exchange for terminal energy conservation or cost reduction. However, current terminal energy conservation technology still needs to be further improved.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a method and device for wireless communication, wherein the terminal device can support multiple capability sets and can activate some of the capability sets it supports. Since different capability sets can correspond to different performances, more refined terminal energy saving can be achieved.

[0005] In a first aspect, a wireless communication method is provided, the method comprising:

[0006] The terminal device activates N capability sets among the M capability sets it supports;

[0007] Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

[0008] In a second aspect, a wireless communication method is provided, the method comprising:

[0009] The network device obtains M capability sets supported by the terminal device;

[0010] The network device determines N activated capability sets among the M capability sets;

[0011] Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

[0012] In a third aspect, a terminal device is provided for executing the method in the first aspect.

[0013] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.

[0014] In a fourth aspect, a network device is provided for executing the method in the second aspect.

[0015] Specifically, the network device includes a functional module for executing the method in the above second aspect.

[0016] In a fifth aspect, a terminal device is provided, comprising a processor and a memory; the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, so that the terminal device executes the method in the above-mentioned first aspect.

[0017] In a sixth aspect, a network device is provided, comprising a processor and a memory; the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, so that the network device executes the method in the above-mentioned second aspect.

[0018] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above.

[0019] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.

[0020] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.

[0021] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.

[0022] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.

[0023] Through the above technical solution, the terminal device can support M capability sets and can activate the N capability sets it supports. Since different capability sets can correspond to different performances, more refined terminal energy saving can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is a schematic diagram of a communication system architecture applied in an embodiment of the present application.

[0025] FIG2 is a schematic diagram of an energy-saving signal provided by the present application.

[0026] FIG3 is a schematic diagram of an energy-saving signal indicating monitoring of PDDCH provided by the present application.

[0027] FIG4 is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

[0028] FIG5 is a schematic diagram of a communication subsystem provided according to an embodiment of the present application.

[0029] FIG6 is a schematic diagram of a capability set provided according to an embodiment of the present application.

[0030] FIG7 is a schematic diagram of a capability set with an association relationship provided according to an embodiment of the present application.

[0031] FIG8 is a schematic flowchart of another wireless communication method provided according to an embodiment of the present application.

[0032] FIG9 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0033] FIG10 is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0034] FIG11 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0035] FIG12 is a schematic block diagram of a device provided according to an embodiment of the present application.

[0036] FIG13 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0038] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE-based access to unlicensed spectrum (LTE-U) system on unlicensed spectrum, NR-based access to unlicensed spectrum (NR-U) system on unlicensed spectrum, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Internet of Things (IoT), Wireless Fidelity (WFI) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system, sixth-generation communication (6G) system or other communication systems.

[0039] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine type communication (MTC), vehicle-to-vehicle (V2V) communication, sidelink (SL) communication, vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0040] In some embodiments, the communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, an independent (SA) networking scenario, or a non-standalone (NSA) networking scenario.

[0041] In some embodiments, the communication system in the embodiments of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiments of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0042] In some embodiments, the communication system in the embodiments of the present application can be applied to the FR1 frequency band (corresponding to the frequency band range of 410MHz to 7.125GHz), can also be applied to the FR2 frequency band (corresponding to the frequency band range of 24.25GHz to 52.6GHz), and can also be applied to new frequency bands such as high-frequency bands corresponding to the frequency band range of 52.6GHz to 71GHz or the frequency band range of 71GHz to 114.25GHz.

[0043] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0044] The terminal device can be a station (STA) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0045] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0046] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city or a wireless terminal device in a smart home, an in-vehicle communication device, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SoC), etc.

[0047] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0048] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a network device or base station (gNB) or a transmission reception point (TRP) in a vehicle-mounted device, a wearable device, and an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0049] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments, the network device may also be a base station set up in a location such as land or water.

[0050] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0051] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.

[0052] FIG1 exemplarily shows a network device and two terminal devices. In some embodiments, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0053] In some embodiments, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0054] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0055] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0056] The terms used in the embodiments of this application are intended only to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions.

[0057] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain it through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain it through C; it can also mean that there is an association between A and B.

[0058] It should be understood that the "at least one or at least one" mentioned in the embodiments of the present application can mean "one or more", and the "positive integer" mentioned in the embodiments of the present application can mean "values ​​such as 1, 2, 3...", and the "non-negative integer" mentioned in the embodiments of the present application can mean "values ​​such as 0, 1, 2, 3...", and the "integer" mentioned in the embodiments of the present application can mean "values ​​such as..., -3, -2, -1, 0, 1, 2, 3,...", and can be replaced with any possible value based on the requirements of the embodiment.

[0059] It should be understood that the figures and / or tables shown in the embodiments of the present application are merely examples. Specifically, in some cases, some of the information contained in the figures and / or tables shown in the embodiments of the present application may independently constitute an optional embodiment. For example, each row or column in the table may independently constitute an optional embodiment. The present application does not limit this.

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

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

[0062] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may be an evolution of an existing LTE protocol, NR protocol, Wi-Fi protocol, or a protocol related to other communication systems. The present application does not limit the protocol type.

[0063] In order to facilitate a better understanding of the embodiments of the present application, the technologies related to the present application are explained.

[0064] 5G technology adopts NR design, based on LTE's orthogonal frequency-division multiplexing (OFDM) + multiple input multiple output (MIMO) underlying air interface technology framework. Compared with LTE, it has made a lot of technical enhancements and improvements in system solution design, including support for higher frequency band range and larger carrier bandwidth, flexible frame structure, diversified parameter sets, optimized reference signal design, new coding, symbol-level resource scheduling, MIMO enhancement, latency reduction, coverage enhancement, mobility enhancement, terminal energy saving, signaling design optimization, a new network architecture, enhanced service quality of service (QoS) guarantee, network slicing, vehicle to everything (V2X), industry Internet of Things (IIoT), unlicensed spectrum design (New Radio-unlicensed, NR-U), and good support for multiple vertical industries.

[0065] Mobile Internet and Mobile Internet of Things (IoT) are the two main drivers of 5G development and offer broad prospects for the future of mobile communications. 5G defines three major application scenarios: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine type communication (mMTC). eMBB is primarily targeted at the mobile Internet, while URLLC and mMTC are targeted at the Mobile Internet of Things (IoT). The mobile Internet will build a comprehensive, user-centric information ecosystem. In recent years, user-centric needs such as ultra-high-definition video, virtual reality (VR), augmented reality (AR), distance education, remote work, telemedicine, and wireless home entertainment have become increasingly prevalent. These burgeoning new service demands inevitably place higher demands on mobile communication transmission bandwidth and data rates. At the same time, vertical industries such as the Mobile Internet of Things (IoT), the Industrial Internet, the Internet of Vehicles (IoV), smart grids, and smart cities are also rapidly transforming towards informatization and digitalization. In addition to smartphones, the forms of mobile terminals are also more diverse, including wearable devices, cameras, drones, robots, vehicle-mounted and ship-mounted terminal modules, and industry-customized terminals.

[0066] To facilitate a better understanding of the embodiments of the present application, the terminal energy-saving technology related to the present application is explained.

[0067] The 5G New Radio (NR) standard guarantees extremely high network system data rates, meeting the International Telecommunication Union (ITU) IMT-2020 minimum 5G data throughput performance requirements. Furthermore, terminal-side energy consumption is a key performance requirement of IMT-2020. Starting with Release 16 (R16), the NR standard has dedicated a dedicated project to optimizing terminal energy consumption.

[0068] In the R16 standard, energy-saving signals are introduced to achieve further energy saving for UEs in the RRC_CONNECTED state. The energy-saving signals are used in conjunction with the discontinuous reception (DRX) mechanism, and the terminal receives an indication of the energy-saving wake-up signal before the DRX activation period (DRX ON duration). When the terminal has data transmission in a DRX cycle, the energy-saving wake-up signal "wakes up" the terminal to monitor the Physical Downlink Control Channel (PDCCH) during the DRX On duration; otherwise, when the terminal has no data transmission in a DRX cycle, the energy-saving wake-up signal does not "wake up" the terminal, and the terminal does not need to monitor the PDCCH during the DRX On Duration. Compared with the DRX mechanism, when the terminal has no data transmission, the terminal can omit PDCCH monitoring during the DRX On duration, thereby achieving energy saving. The time the terminal spends outside the DRX On duration is called the inactive time, and the time during the DRX On Duration is called the active time. The process of indicating whether the terminal monitors the PDCCH during the DRX On Duration through the energy-saving signal is shown in Figure 2.

[0069] Release 17 (R17) further enhances energy conservation for UEs in the RRC_CONNECTED state, introducing an enhanced scheme for search space set group switching and a PDCCH skipping scheme that saves power when necessary. The R17 standard also enhances energy conservation for UEs in the RRC idle / RRC inactive states. UEs in the RRC idle / inactive state receive paging messages via DRX. Within a DRX cycle, there is a paging occasion (PO). The UE only receives paging messages during the PO and not during other paging occasions, thereby saving power. However, in reality, the probability of a UE being paged may be low. If a UE periodically detects the PDCCH during the corresponding PO but fails to detect the paging indication sent to it, power consumption will be wasted. Similar to the energy saving of connected UEs in the R16 standard, the R17 standard optimizes the energy saving of idle UEs receiving paging messages and introduces similar energy saving signals. One energy saving signal is called paging early indication (PEI), which is used to indicate whether the UE receives paging PDCCH at the target PO before the target PO arrives. The energy saving signal is carried on the PDCCH channel. The energy saving signal based on the PDCCH channel can also carry more energy saving information, such as sub-grouping information, which is used to indicate the UE sub-grouping corresponding to the energy saving information. Sub-grouping is a further grouping of multiple UEs corresponding to a PO calculated by the terminal identifier (UE_ID). The sub-grouping information combined with the energy saving information can more accurately indicate whether the UE needs to receive paging at the target PO.

[0070] As shown in FIG3 , a power saving signal indicates whether UEs in one or more paging subgroups receive paging on the corresponding PF or PO.

[0071] To facilitate a better understanding of the embodiments of the present application, a reduced capability terminal (RedCap UE) related to the present application is described.

[0072] Release 15 (R15) and Release 16 (R16) terminals are designed to support extremely high peak rates. Therefore, they require high terminal capabilities, which are determined by the following key aspects:

[0073] The LTE standard defines a maximum single-carrier bandwidth of 20MHz, with larger bandwidths achieved through multi-carrier aggregation. 5G NR ultimately defines a maximum carrier bandwidth of 100MHz for sub-6GHz bands, five times that of LTE. The maximum carrier bandwidth for millimeter-wave bands is 400MHz.

[0074] Due to its support for flexible time-domain scheduling and frame structure, terminals have relatively high processing speeds. Larger subcarrier spacing results in shorter time slots. All of this requires NR terminals to have exponentially higher processing speeds than LTE terminals.

[0075] The MIMO antenna size required by NR has also increased. The reference configuration for LTE terminals is one transmit and two receive antennas, while NR Release 15 requires dual transmit and four receive antennas for frequencies above 2500 MHz.

[0076] NR R15 / R16 also does not support half-duplex. All terminals are required to operate in full-duplex at the Frequency Division Duplex (FDD) frequency point.

[0077] These fundamental NR terminal capabilities place high demands on the radio frequency, baseband, and other modules, significantly exceeding those of LTE. However, some NR application scenarios, such as the Internet of Things, industrial automation, and wearable devices, do not require such high processing capacity and speed. These scenarios, in turn, demand low-volume and power-efficient communication hardware. Lightweight capabilities are a hallmark of these terminals. With this in mind, NR Release 17 is researching and introducing a reduced-capability terminal standard with reduced capabilities.

[0078] The Reduced Capability Terminal (RedCap UE) standard reduces some mandatory capabilities of NR Release 15 / 16. It defines corresponding terminal feature sets for these capabilities. The RedCap UE standard also further optimizes terminal identification, access procedures, and power consumption measurements to suit relevant application scenarios. Furthermore, the standard for compact terminals explicitly requires that these terminals not support complex feature sets, such as high reliability and low latency (HRLS) and carrier aggregation.

[0079] In the R17 and R18 standards, the capabilities of reduced-capability terminals are defined in terms of supported bandwidth, number of antennas, half-duplex capability, measurement capability, processing time relaxation, and peak rate.

[0080] In order to facilitate a better understanding of the embodiments of the present application, the problems solved by the present application are explained.

[0081] Both terminal energy-saving technologies and reduced-capacity terminals are tailored from the NR terminal functions defined in Release 15, sacrificing terminal and network performance in exchange for energy savings or lower costs. This is because the initial design goals for NR were large bandwidth and high speeds. Neither the network nor the terminal were optimized for low-data-volume services like IoT, nor was there consideration for terminal energy conservation. Optimization efforts to achieve these goals in the later stages of the standardization process increased system design complexity and decreased performance.

[0082] Currently, terminal devices have only one capability set, which they report through signaling when establishing a connection with the network. For an R15 terminal, in addition to meeting minimum requirements for supported bandwidth and number of antennas, all supported bandwidth (bands), features, and other information are reported as part of the capability set. Hardware resources corresponding to these capabilities are not clearly divided within the terminal, resulting in a single, comprehensive terminal that cannot be optimized for energy conservation in specific application scenarios. With the introduction of capabilities to reduce terminal power consumption and costs in R16, R17, and R18, new terminal types with corresponding capabilities have emerged, such as Reduced Capability Terminals (RedCap UEs). However, supporting these IoT services requires specific terminal types. If IoT services are still implemented on R15 terminals, terminal power consumption will not be effectively reduced.

[0083] Based on the existing problems in solving terminal energy saving, in the design of 6G systems, it is hoped that how to achieve terminal energy saving will be considered from the early stage of system design. This application proposes a new design scheme for multi-capability terminals. In different business or application scenarios, the terminal activates the corresponding capabilities to achieve communication with the network, thereby achieving power and reasonable use of the terminal.

[0084] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0085] FIG4 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application. The wireless communication method 200 may be executed by a terminal device, which may be the terminal device shown in FIG1 . Specifically, as shown in FIG4 , the wireless communication method 200 may include at least part of the following contents:

[0086] S210 , the terminal device activates N capability sets among the M capability sets it supports; wherein M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

[0087] It should be understood that FIG4 shows the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG4.

[0088] In the embodiment of the present application, M≥2, that is, the terminal device can support multiple capability sets, and different capability sets can correspond to different performances, thereby realizing more refined terminal energy saving.

[0089] In some embodiments, the capability set in the M capability sets includes at least one of the following information elements: supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, coding, modulation mode, measurement capability, air interface technology, basic parameter set, receiver architecture, receiver type, receiver capability, maximum transmit power, and supported features;

[0090] Among them, different capability sets in the M capability sets have different values ​​for at least some of the information elements.

[0091] For example, air interface technologies may include NR, LTE, WCDMA, Narrow Band Internet of Things (NB-IoT), MTC, GSM, WiFi, etc.

[0092] For example, the basic parameter set may include subcarrier spacing, cyclic prefix length, symbol length, etc.

[0093] For example, the receiver type may include an OFDM receiver and a wake-up receiver (WUR).

[0094] For example, the characteristics include energy-saving characteristics, coverage enhancement characteristics, URLLC characteristics, etc.

[0095] For example, receiver capabilities include receiver sensitivity parameters and the like.

[0096] In some embodiments, when a terminal device activates a certain capability set, for the network, the terminal device is a terminal type corresponding to the activated capability set.

[0097] In some embodiments, when a terminal device activates a certain capability set, the terminal device may be in a state corresponding to the activated capability set for the network.

[0098] In an embodiment of the present application, the hardware resources inside the terminal are trimmable, or sliceable. According to the division of the capability set, the slices can be activated and used independently, or they can have certain associations, such as some slices need to be activated jointly.

[0099] That is, in the embodiment of the present application, multiple capability sets need to meet the slicing requirements. Optionally, multiple capability sets can also correspond to multiple slicing requirements, or correspond to different business areas.

[0100] In some embodiments, at least some of the M capability sets are associated with each other. For example, the associated capability sets are activated simultaneously. In some embodiments, the associated relationships between the capability sets may be determined by a protocol, or the associated relationships between the capability sets may be configured by the network.

[0101] For example, the capability sets supported by the terminal device are capability sets 1, 2, and 3. Capability sets 1 and 3 can be activated independently, and capability set 2 can be activated jointly with capability set 1 or 3, but cannot be activated independently.

[0102] In some embodiments, when N≥2, the N capability sets are associated capability sets, that is, the terminal device activates N capability sets with associated relationships among the M capability sets supported by it.

[0103] In some embodiments, different capability sets in the M capability sets correspond to different services. For example, latency-sensitive services and non-latency-sensitive services correspond to different capability sets. For another example, gaming services, video services, voice services, and SMS services correspond to different capability sets.

[0104] In some embodiments, the activation and / or switching of capability sets within the M capability sets is associated with the type of service being executed. For example, when an IoT service is to be executed, the terminal device activates the capability set corresponding to the IoT service. For another example, when an IoT service is to be executed, the terminal device switches from another capability set to the capability set corresponding to the IoT service.

[0105] For example, a terminal device can activate N of the M supported capability sets to meet specific service requirements. The capabilities contained in these N capability sets can be targeted at supporting specific services, such as eMBB, IoT, and URLLC. Taking the IoT capability set as an example, since it primarily serves small data packet services with low requirements for peak rate and latency, requirements for supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, and coding can be relaxed. The terminal's hardware resources corresponding to this capability set can be activated individually, without activating all of the terminal's hardware resources, thereby reducing power consumption. For example, when executing eMBB services, a terminal device can activate a capability set corresponding to large bandwidth and high peak rate.

[0106] In some embodiments, different capability sets in the M capability sets correspond to different application scenarios. For example, application scenarios such as large data volume download, small data packet transmission, voice, positioning, perception, and XR each correspond to a different capability set.

[0107] In some embodiments, when different capability sets in the M capability sets correspond to different application scenarios, the activation and / or switching of capability sets in the M capability sets are associated with the application scenario. For example, when applied to a positioning scenario, the terminal device activates the capability set corresponding to the positioning scenario. For another example, when applied to a positioning scenario, the terminal device switches from another capability set to the capability set corresponding to the positioning scenario.

[0108] In some embodiments, different capability sets in the M capability sets correspond to different wireless access technologies, for example, NR, LTE, WCDMA, NB-IoT, MTC, GSM, WiFi, etc. correspond to different capability sets.

[0109] In some embodiments, when different capability sets in the M capability sets correspond to different radio access technologies, activation and / or switching of the capability sets in the M capability sets are associated with the accessed radio access technology.

[0110] For example, capability sets can be oriented towards different wireless access technologies, such as NR, LTE, WCDMA, NB-IoT, MTC, GSM, and WiFi. Different capability sets are activated for different wireless access technologies. In other words, different capability sets may support different air interface technologies.

[0111] In some embodiments, different capability sets in the M capability sets correspond to different hardware resource slicing requirements. For example, the hardware resources within the terminal are tailorable, or sliceable, and can be divided according to the capability sets. The slices can be activated and used independently, or they can have certain associations, such as some slices needing to be activated jointly.

[0112] In some embodiments, when different capability sets in the M capability sets correspond to different hardware resource slicing requirements, activation and / or switching of the capability sets in the M capability sets are associated with the required hardware resources.

[0113] In some embodiments, different capability sets in the M capability sets correspond to different Radio Resource Control (RRC) connection states, wherein the RRC connection state may include an RRC idle state, an RRC inactive state, and an RRC connected state.

[0114] In some embodiments, when different capability sets in the M capability sets correspond to different RRC connection states, activation and / or switching of capability sets in the M capability sets are associated with the RRC connection state.

[0115] For example, when the terminal is in different RRC connection states, different capability sets are activated. For example, when the terminal is in the RRC idle (RRC idle) / RRC deactivated (RRC inactive) state, the terminal may be in a low-capability, power-saving state, and the corresponding capability set needs to be activated, wherein the capability set can save power to the maximum extent while meeting certain connection establishment and state transition delays. When the terminal is in the RRC connection state, the terminal can activate the corresponding capability set according to the established service. When the terminal is performing state transition, it can automatically activate the corresponding capability set. For example, when the terminal switches to the idle / inactive state, it can switch to the default capability set to work. When the terminal switches to the connected state, the terminal can switch to the corresponding capability set.

[0116] In some embodiments, different capability sets in the M capability sets correspond to different communication parameters, wherein the communication parameters include but are not limited to at least one of the following: supported bands, number of antennas, half-duplex capability, mobility, processing time, coding, modulation mode, measurement capability, and transmission delay.

[0117] It should be noted that “different communication parameters” may refer to different communication parameters, or may refer to the same communication parameters but with different values.

[0118] In some embodiments, when different capability sets in the M capability sets correspond to different communication parameters, activation and / or switching of capability sets in the M capability sets are associated with the used communication parameters.

[0119] In some embodiments, different capability sets in the M capability sets correspond to different Quality of Service (QoS) requirements. In some embodiments, when different capability sets in the M capability sets correspond to different QoS requirements, activation and / or switching of capability sets in the M capability sets are associated with the required QoS.

[0120] In some embodiments, different capability sets in the M capability sets correspond to different radio bearers (RBs). In some embodiments, when different capability sets in the M capability sets correspond to different RBs, activation and / or switching of capability sets in the M capability sets are associated with the established RBs.

[0121] Specifically, when the network establishes a corresponding radio bearer, the terminal can activate the corresponding capability set. There is a corresponding relationship between the radio bearer and the capability set. Specifically, the network can also instruct the terminal to activate the corresponding capability set in the corresponding parameters of the radio bearer. For example, for the RB corresponding to the capability set, specific transmission resources or transmission resource configurations can be used, such as logical channel (Logical Channel, LCH) configuration, carrier configuration, media access control (Media Access Control, MAC) configuration, physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) resources, etc. For example, based on the combination of terminal capabilities, data for different application scenarios can be mapped to different RB / LCH / PUSCH, etc.

[0122] In some embodiments, different capability sets in the M capability sets correspond to different bandwidth parts (BWPs). In some embodiments, when different capability sets in the M capability sets correspond to different BWPs, activation and / or switching of capability sets in the M capability sets are associated with the activated BWP.

[0123] Specifically, the capability set activated by the terminal may correspond to the activated BWP. The network will configure the default BWP identity (Identity, ID) for the terminal through the default downlink BWP identity (defaultDownlinkBWP-Id) information. Or, a dormant downlink BWP (dormant DL BWP) may be configured for the terminal. These BWP types are designed to save energy for the terminal when there is no data scheduling. When the terminal switches to these types of BWP, the capability set corresponding to the type of BWP can be activated. When switching to other types of BWP, other capability sets can be activated.

[0124] In some embodiments, different capability sets in the M capability sets correspond to different terminal operating frequency bands. In some embodiments, when different capability sets in the M capability sets correspond to different terminal operating frequency bands, activation and / or switching of capability sets in the M capability sets are associated with the frequency band in which the terminal device operates.

[0125] Specifically, the capability set activated by a terminal is related to the frequency band in which it operates. For example, in low-frequency bands, where the number of beams is low and wireless signal coverage is good, the terminal can activate the capability set corresponding to the low-frequency band. In high-frequency bands, where the number of beams is high and wireless signal coverage is poor, the terminal can activate the capability set corresponding to the high-frequency band.

[0126] In some embodiments, different capability sets in the M capability sets correspond to different communication subsystems. In some embodiments, when different capability sets in the M capability sets correspond to different communication subsystems, activation and / or switching of capability sets in the M capability sets are associated with the communication subsystem corresponding to the terminal device.

[0127] Specifically, for a communication system having multiple communication subsystems, terminals communicating under different communication subsystems of the communication system may activate corresponding capability sets.

[0128] For example, as shown in Figure 5, a communications system can consist of a minimal, simplified core providing common capabilities such as endogenous intelligence, security, and flexible spectrum management. Specific optimizations are then implemented for four distinct capability areas: cloud connectivity, critical IoT, ubiquitous IoT, and sensing. One or two subsystems are designed for each capability area, with key technologies independently selected based on application scenarios, spectrum, and interface types, and hardware systems designed accordingly. For example, these subsystems could be categorized as: 6G broadband cellular, 6G D2D, 6G URLLC, 6G positioning and perception, 6G massive IoT, and 6G space communications. A black-box, specialized AI algorithm library replaces general-purpose and complex traditional software algorithms, achieving relative independence and optimization for each subsystem and significantly simplifying communication protocols. Multiple subsystems can be switched and combined through the switching and combination of various AI algorithms.

[0129] As shown in Figure 5, the communication system may include a minimalist core and several communication subsystems. The communication subsystems may be activated simultaneously or switched between each other.

[0130] For example, assuming a terminal supports multiple capability sets, allowing it to operate in different subsystems, such as 6G broadband cellular, 6G D2D, 6G URLLC, 6G positioning and perception, 6G massive IoT, and 6G space communications, the terminal can activate the corresponding capability set for each subsystem. As shown in Figure 6, a terminal can include a basic capability set and other specific capability sets, such as the eMBB capability set, URLLC capability set, IoT capability set, and positioning and perception capability set. Based on service needs, the terminal can switch between different capability sets or activate multiple capability sets simultaneously.

[0131] Furthermore, the service types established by a terminal and the subsystems it connects to may not necessarily correspond one-to-one with the terminal's capability set. As previously mentioned, the hardware resource slices corresponding to a terminal's capability set may be related, and some slices may require joint activation. Alternatively, some capability sets may be related, and the resources corresponding to them cannot be divided into different slices. In this case, some capability sets are related and require joint activation. These related capability sets can be considered a larger capability set. As shown in Figure 7, the eMBB capability set and the URLLC capability set are related and require simultaneous activation or deactivation. Furthermore, the positioning and sensing capability set and the IoT capability set are related and require simultaneous activation or deactivation. The eMBB capability set and the URLLC capability set can be combined to support eMBB and URLLC; the positioning and sensing capability set and the IoT capability set can be combined to support positioning and sensing and IoT. These two combined capability sets can be activated independently.

[0132] In some embodiments, before the terminal device activates the N capability sets, the terminal device receives first information, wherein the first information is used to instruct the terminal device to activate the N capability sets among the M capability sets that it supports.

[0133] In some embodiments, the first information is parameter information in RB establishment. Specifically, for example, the network device may instruct the terminal to activate a corresponding capability set in the corresponding radio bearer parameters. For example, for RBs corresponding to the capability set, specific transmission resources or transmission resource configurations may be used, such as LCH configuration, carrier configuration, MAC configuration, PUSCH resources, etc. For example, based on the terminal's capabilities, data for different application scenarios may be mapped to different RBs / LCHs / PUSCHs, etc.

[0134] In some embodiments, the first information is carried via Non-Access Stratum (NAS) signaling.

[0135] In some embodiments, when the first information is carried through NAS signaling, the NAS signaling is one of the following: service request signaling, protocol data unit (PDU) session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0136] In some embodiments, before the terminal device activates the N capability sets, the terminal device reports the M capability sets it supports. That is, when the terminal has multiple capability sets, the terminal can report the multiple capability sets to the network.

[0137] In some embodiments, the terminal device reports the M capability sets it supports in a periodic reporting manner. Specifically, for example, the reporting period may be agreed upon by a protocol, or the reporting period may be configured by a network device.

[0138] In some embodiments, the terminal device reports the M capability sets it supports by condition-triggered reporting. Specifically, for example, the triggering condition may be agreed upon by a protocol, or may be configured by a network device.

[0139] In some embodiments, the terminal device reports the M capability sets it supports by event triggering reporting. Specifically, for example, the triggering event may be agreed upon by a protocol, or the triggering event may be configured by a network device.

[0140] For example, the capability set reporting of the terminal may be unconditional reporting, periodic reporting, or conditional or event-triggered reporting. For example, the capability set may be reported when the terminal has not reported the capability set, or when the capability set reported by the terminal changes, or when the capability set reporting timer reported by the terminal times out, or when the capability set reported by the terminal does not include a changed capability set, or when the capability set reported by the terminal is reported periodically.

[0141] In some embodiments, the terminal device reports the M capability sets it supports through RRC signaling or NAS signaling.

[0142] In some embodiments, when the terminal device reports the M capability sets supported by it through RRC signaling, the RRC signaling is RRC signaling during the RRC connection establishment process, or the RRC signaling is RRC signaling after the RRC connection establishment is completed. For example, the capability set report of the terminal can be reported to the network through RRC signaling, such as reporting during the RRC connection establishment process, or reporting after the RRC connection establishment is completed. For example, the terminal reports the capability set through terminal assistance information (UE assistance information, UAI).

[0143] In some embodiments, when the terminal device reports the M capability sets it supports through NAS signaling, the NAS signaling is one of the following: service request signaling, PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process. For example, the terminal's capability set report can also be reported to the core network through NAS signaling, and sent to the base station by the core network. For example, the terminal reports the terminal's capability set in the service request signaling in the NAS signaling, or in the PDU session establishment signaling or process, or in the PDU session modification signaling or process.

[0144] In some embodiments, the terminal device reports the M capability sets it supports during the random access process.

[0145] For example, the capability set reporting of the terminal may also be indicated during the random access process, such as through message 1 (Msg1), message A (MsgA), message 3 (Msg3), and message B (MsgB) during the random access process. For example, it may be reported in the corresponding RRC message in the Physical Uplink Shared Channel (PUSCH) of MsgA or the PUSCH of Msg3 or message 5 (Msg5). For example, different capability sets of terminals may be represented by specific Physical Random Access Channel (PRACH) resource locations and / or preambles.

[0146] In some embodiments, the terminal device reports the M capability sets it supports to the target base station through the source base station. Specifically, the capability sets of the terminal device can also be obtained through interaction between base stations, such as during a handover process.

[0147] In some embodiments, the activation and switching of a terminal's capability set can be dynamically indicated via physical layer signaling or MAC layer signaling. For example, the network can determine the capability set that the terminal needs to activate based on the terminal's data cache status. For example, when the data cache is low or empty, the terminal's capability set is switched to a capability set with relatively low capabilities via physical layer or MAC layer signaling. When data arrives at the terminal, the terminal's capability set is switched to a capability set with relatively high capabilities via physical layer or MAC layer signaling.

[0148] Therefore, in an embodiment of the present application, the terminal device can support M capability sets and can activate the N capability sets it supports. Since different capability sets can correspond to different performances, more refined terminal energy saving can be achieved.

[0149] Specifically, by defining, reporting, and switching multiple capability sets supported by the terminal, the terminal can activate the corresponding capability set for different services, network subsystems, communication states, and communication parameters, thereby achieving energy conservation. At the same time, it can improve communication efficiency within the subsystem and simplify system complexity.

[0150] The above, in combination with Figures 4 to 7, describes in detail the terminal side embodiment of the present application. The following, in combination with Figure 8, describes in detail the network side embodiment of the present application. It should be understood that the network side embodiment and the terminal side embodiment correspond to each other, and similar descriptions can refer to the terminal side embodiment.

[0151] FIG8 is a schematic flow chart of a wireless communication method 300 according to an embodiment of the present application. The wireless communication method 300 may be performed by a network device, which may be the network device shown in FIG1 . Specifically, as shown in FIG8 , the wireless communication method 300 may include at least part of the following:

[0152] S310, the network device obtains M capability sets supported by the terminal device;

[0153] S320 , the network device determines N activated capability sets among the M capability sets; wherein M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

[0154] It should be understood that FIG8 shows the steps or operations of the wireless communication method 300, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG8.

[0155] In the embodiment of the present application, M≥2, that is, the terminal device can support multiple capability sets, and different capability sets can correspond to different performances, thereby realizing more refined terminal energy saving.

[0156] In some embodiments, the capability set in the M capability sets includes at least one of the following information elements: supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, coding, modulation mode, measurement capability, air interface technology, basic parameter set, receiver architecture, receiver type, receiver capability, maximum transmit power, and supported features;

[0157] Among them, different capability sets in the M capability sets have different values ​​for at least some of the information elements.

[0158] For example, air interface technologies may include NR, LTE, WCDMA, Narrow Band Internet of Things (NB-IoT), MTC, GSM, WiFi, etc.

[0159] For example, the basic parameter set may include subcarrier spacing, cyclic prefix length, symbol length, etc.

[0160] For example, the receiver type may include an OFDM receiver and a wake-up receiver (WUR).

[0161] For example, the characteristics include energy-saving characteristics, coverage enhancement characteristics, URLLC characteristics, etc.

[0162] For example, receiver capabilities include receiver sensitivity parameters and the like.

[0163] In some embodiments, when a terminal device activates a certain capability set, for the network, the terminal device is a terminal type corresponding to the activated capability set.

[0164] In some embodiments, when a terminal device activates a certain capability set, the terminal device may be in a state corresponding to the activated capability set for the network.

[0165] In an embodiment of the present application, the hardware resources inside the terminal are trimmable, or sliceable. According to the division of the capability set, the slices can be activated and used independently, or they can have certain associations, such as some slices need to be activated jointly.

[0166] That is, in the embodiment of the present application, multiple capability sets need to meet the slicing requirements. Optionally, multiple capability sets can also correspond to multiple slicing requirements, or correspond to different business areas.

[0167] In some embodiments, at least some of the M capability sets are associated with each other. For example, the associated capability sets are activated simultaneously. In some embodiments, the associated relationships between the capability sets may be determined by a protocol, or the associated relationships between the capability sets may be configured by the network.

[0168] For example, the capability sets supported by the terminal device are capability sets 1, 2, and 3. Capability sets 1 and 3 can be activated independently, and capability set 2 can be activated jointly with capability set 1 or 3, but cannot be activated independently.

[0169] In some embodiments, when N≥2, the N capability sets are associated capability sets, that is, the terminal device activates N capability sets with associated relationships among the M capability sets supported by it.

[0170] In some embodiments, different capability sets in the M capability sets correspond to different services respectively; or,

[0171] Different capability sets in the M capability sets correspond to different application scenarios; or,

[0172] Different capability sets in the M capability sets correspond to different wireless access technologies; or,

[0173] Different capability sets in the M capability sets correspond to different hardware resource slicing requirements; or,

[0174] Different capability sets in the M capability sets correspond to different RRC connection states; or,

[0175] Different capability sets in the M capability sets correspond to different communication parameters; or,

[0176] Different capability sets in the M capability sets correspond to different QoS requirements; or,

[0177] Different capability sets in the M capability sets correspond to different RBs; or,

[0178] Different capability sets in the M capability sets correspond to different BWPs; or,

[0179] Different capability sets in the M capability sets correspond to different terminal operating frequency bands; or,

[0180] Different capability sets in the M capability sets correspond to different communication subsystems.

[0181] In some embodiments, when different capability sets in the M capability sets correspond to different services, activation and / or switching of capability sets in the M capability sets are associated with the type of service being executed.

[0182] In some embodiments, when different capability sets in the M capability sets correspond to different application scenarios, activation and / or switching of capability sets in the M capability sets are associated with the application scenarios.

[0183] In some embodiments, when different capability sets in the M capability sets correspond to different radio access technologies, activation and / or switching of capability sets in the M capability sets are associated with the accessed radio access technology.

[0184] In some embodiments, when different capability sets in the M capability sets correspond to different hardware resource slicing requirements, activation and / or switching of capability sets in the M capability sets are associated with the required hardware resources.

[0185] In some embodiments, when different capability sets in the M capability sets correspond to different RRC connection states, activation and / or switching of capability sets in the M capability sets are associated with the RRC connection state.

[0186] In some embodiments, when different capability sets in the M capability sets correspond to different communication parameters, activation and / or switching of capability sets in the M capability sets are associated with the used communication parameters.

[0187] In some embodiments, when different capability sets in the M capability sets correspond to different QoS requirements, activation and / or switching of capability sets in the M capability sets are associated with the required QoS.

[0188] In some embodiments, when different capability sets in the M capability sets correspond to different RBs, activation and / or switching of capability sets in the M capability sets are associated with the established RBs.

[0189] In some embodiments, when different capability sets in the M capability sets correspond to different BWPs, activation and / or switching of capability sets in the M capability sets are associated with the activated BWP.

[0190] In some embodiments, when different capability sets in the M capability sets correspond to different terminal operating frequency bands, activation and / or switching of capability sets in the M capability sets are associated with the operating frequency band of the terminal device.

[0191] In some embodiments, when different capability sets in the M capability sets correspond to different communication subsystems, activation and / or switching of capability sets in the M capability sets are associated with the communication subsystem corresponding to the terminal device.

[0192] In some embodiments, the network device receives the M capability sets reported by the terminal device.

[0193] In some embodiments, the network device receives the M capability sets reported by the terminal device through periodic reporting.

[0194] In some embodiments, the network device receives the M capability sets reported by the terminal device through conditional triggering reporting.

[0195] In some embodiments, the network device receives the M capability sets reported by the terminal device through event-triggered reporting.

[0196] In some embodiments, the network device receives the M capability sets reported by the terminal device through RRC signaling or NAS signaling.

[0197] In some embodiments, when the terminal device reports the M capability sets through RRC signaling, the RRC signaling is RRC signaling during the RRC connection establishment process, or the RRC signaling is RRC signaling after the RRC connection establishment is completed.

[0198] In some embodiments, when the terminal device reports the M capability sets through NAS signaling, the NAS signaling is one of the following: service request signaling, PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0199] In some embodiments, the network device receives the M capability sets reported by the terminal device during the random access process.

[0200] In some embodiments, the network device receives the M capability sets reported by the terminal device through other network devices.

[0201] In some embodiments, the network device sends first information, wherein the first information is used to instruct the terminal device to activate the N capability sets among the M capability sets supported by the terminal device.

[0202] In some embodiments, the first information is parameter information in RB establishment, or the first information is carried through non-access stratum NAS signaling.

[0203] In some embodiments, when the first information is carried through NAS signaling, the NAS signaling is one of the following: service request signaling, protocol data unit PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0204] Therefore, in an embodiment of the present application, the terminal device can support M capability sets and can activate the N capability sets it supports. Since different capability sets can correspond to different performances, more refined terminal energy saving can be achieved.

[0205] The above text, in combination with Figures 4 to 8, describes in detail the method embodiment of the present application. The following text, in combination with Figures 9 to 13, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0206] FIG9 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG9 , the terminal device 400 includes:

[0207] The processing unit 410 is configured to activate N capability sets among the M capability sets supported by the terminal device;

[0208] Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

[0209] In some embodiments, at least some of the M capability sets are associated with each other.

[0210] In some embodiments, when N≥2, the N capability sets are associated capability sets.

[0211] In some embodiments, different capability sets in the M capability sets correspond to different services respectively; or,

[0212] Different capability sets in the M capability sets correspond to different application scenarios; or,

[0213] Different capability sets in the M capability sets correspond to different wireless access technologies; or,

[0214] Different capability sets in the M capability sets correspond to different hardware resource slicing requirements; or,

[0215] Different capability sets in the M capability sets correspond to different radio resource control RRC connection states; or,

[0216] Different capability sets in the M capability sets correspond to different communication parameters; or,

[0217] Different capability sets in the M capability sets correspond to different quality of service (QoS) requirements; or

[0218] Different capability sets in the M capability sets correspond to different radio bearers (RBs); or

[0219] Different capability sets in the M capability sets correspond to different bandwidth parts BWP respectively; or,

[0220] Different capability sets in the M capability sets correspond to different terminal operating frequency bands; or,

[0221] Different capability sets in the M capability sets correspond to different communication subsystems.

[0222] In some embodiments, when different capability sets in the M capability sets correspond to different services, activation and / or switching of capability sets in the M capability sets are associated with the type of service being executed.

[0223] In some embodiments, when different capability sets in the M capability sets correspond to different application scenarios, activation and / or switching of capability sets in the M capability sets are associated with the application scenarios.

[0224] In some embodiments, when different capability sets in the M capability sets correspond to different radio access technologies, activation and / or switching of capability sets in the M capability sets are associated with the accessed radio access technology.

[0225] In some embodiments, when different capability sets in the M capability sets correspond to different hardware resource slicing requirements, activation and / or switching of capability sets in the M capability sets are associated with the required hardware resources.

[0226] In some embodiments, when different capability sets in the M capability sets correspond to different RRC connection states, activation and / or switching of capability sets in the M capability sets are associated with the RRC connection state.

[0227] In some embodiments, when different capability sets in the M capability sets correspond to different communication parameters, activation and / or switching of capability sets in the M capability sets are associated with the used communication parameters.

[0228] In some embodiments, when different capability sets in the M capability sets correspond to different QoS requirements, activation and / or switching of capability sets in the M capability sets are associated with the required QoS.

[0229] In some embodiments, when different capability sets in the M capability sets correspond to different RBs, activation and / or switching of capability sets in the M capability sets are associated with the established RBs.

[0230] In some embodiments, when different capability sets in the M capability sets correspond to different BWPs, activation and / or switching of capability sets in the M capability sets are associated with the activated BWP.

[0231] In some embodiments, when different capability sets in the M capability sets correspond to different terminal operating frequency bands, activation and / or switching of capability sets in the M capability sets are associated with the operating frequency band of the terminal device.

[0232] In some embodiments, when different capability sets in the M capability sets correspond to different communication subsystems, activation and / or switching of capability sets in the M capability sets are associated with the communication subsystem corresponding to the terminal device.

[0233] In some embodiments, before the terminal device activates the N capability sets, the terminal device 400 further includes:

[0234] The communication unit 420 is configured to receive first information, wherein the first information is used to instruct the terminal device to activate the N capability sets among the M capability sets supported by the terminal device.

[0235] In some embodiments, the first information is parameter information in RB establishment, or the first information is carried through non-access stratum NAS signaling.

[0236] In some embodiments, when the first information is carried through NAS signaling, the NAS signaling is one of the following: service request signaling, protocol data unit PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0237] In some embodiments, before the terminal device activates the N capability sets, the terminal device 400 further includes:

[0238] The communication unit 420 is configured to report the M capability sets supported by it.

[0239] In some embodiments, the communication unit 420 is specifically configured to:

[0240] Report the M capability sets it supports by periodic reporting; or,

[0241] Report the M capability sets it supports by means of conditional trigger reporting; or,

[0242] The M capability sets supported by it are reported in an event-triggered reporting manner.

[0243] In some embodiments, the communication unit 420 is specifically configured to:

[0244] The M capability sets supported by it are reported through RRC signaling or NAS signaling.

[0245] In some embodiments, when the terminal device reports the M capability sets it supports through RRC signaling, the RRC signaling is RRC signaling during the RRC connection establishment process, or the RRC signaling is RRC signaling after the RRC connection establishment is completed.

[0246] In some embodiments, when the terminal device reports the M capability sets it supports through NAS signaling, the NAS signaling is one of the following: service request signaling, PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0247] In some embodiments, the communication unit 420 is specifically configured to:

[0248] The M capability sets supported by it are reported during the random access process.

[0249] In some embodiments, the communication unit 420 is specifically configured to:

[0250] The source base station reports the M capability sets supported by the target base station to the target base station.

[0251] In some embodiments, the capability set in the M capability sets includes at least one of the following information elements: supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, coding, modulation scheme, measurement capability, air interface technology, basic parameter set, receiver architecture, receiver type, receiver capability, maximum transmit power, and supported features;

[0252] Among them, different capability sets in the M capability sets have different values ​​for at least some of the information elements.

[0253] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0254] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 400 are respectively for realizing the corresponding processes of the terminal device in the method 200 shown in Figure 4. For the sake of brevity, they will not be repeated here.

[0255] FIG10 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. As shown in FIG10 , the network device 500 includes:

[0256] The communication unit 510 is configured to obtain M capability sets supported by the terminal device;

[0257] The processing unit 520 is configured to determine N activated capability sets from the M capability sets;

[0258] Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

[0259] In some embodiments, at least some of the M capability sets are associated with each other.

[0260] In some embodiments, when N≥2, the N capability sets are associated capability sets.

[0261] In some embodiments, different capability sets in the M capability sets correspond to different services respectively; or,

[0262] Different capability sets in the M capability sets correspond to different application scenarios; or,

[0263] Different capability sets in the M capability sets correspond to different wireless access technologies; or,

[0264] Different capability sets in the M capability sets correspond to different hardware resource slicing requirements; or,

[0265] Different capability sets in the M capability sets correspond to different radio resource control RRC connection states; or,

[0266] Different capability sets in the M capability sets correspond to different communication parameters; or,

[0267] Different capability sets in the M capability sets correspond to different quality of service (QoS) requirements; or

[0268] Different capability sets in the M capability sets correspond to different radio bearers (RBs); or

[0269] Different capability sets in the M capability sets correspond to different bandwidth parts BWP respectively; or,

[0270] Different capability sets in the M capability sets correspond to different terminal operating frequency bands; or,

[0271] Different capability sets in the M capability sets correspond to different communication subsystems.

[0272] In some embodiments, when different capability sets in the M capability sets correspond to different services, activation and / or switching of capability sets in the M capability sets are associated with the type of service being executed.

[0273] In some embodiments, when different capability sets in the M capability sets correspond to different application scenarios, activation and / or switching of capability sets in the M capability sets are associated with the application scenarios.

[0274] In some embodiments, when different capability sets in the M capability sets correspond to different radio access technologies, activation and / or switching of capability sets in the M capability sets are associated with the accessed radio access technology.

[0275] In some embodiments, when different capability sets in the M capability sets correspond to different hardware resource slicing requirements, activation and / or switching of capability sets in the M capability sets are associated with the required hardware resources.

[0276] In some embodiments, when different capability sets in the M capability sets correspond to different RRC connection states, activation and / or switching of capability sets in the M capability sets are associated with the RRC connection state.

[0277] In some embodiments, when different capability sets in the M capability sets correspond to different communication parameters, activation and / or switching of capability sets in the M capability sets are associated with the used communication parameters.

[0278] In some embodiments, when different capability sets in the M capability sets correspond to different QoS requirements, activation and / or switching of capability sets in the M capability sets are associated with the required QoS.

[0279] In some embodiments, when different capability sets in the M capability sets correspond to different RBs, activation and / or switching of capability sets in the M capability sets are associated with the established RBs.

[0280] In some embodiments, when different capability sets in the M capability sets correspond to different BWPs, activation and / or switching of capability sets in the M capability sets are associated with the activated BWP.

[0281] In some embodiments, when different capability sets in the M capability sets correspond to different terminal operating frequency bands, activation and / or switching of capability sets in the M capability sets are associated with the operating frequency band of the terminal device.

[0282] In some embodiments, when different capability sets in the M capability sets correspond to different communication subsystems, activation and / or switching of capability sets in the M capability sets are associated with the communication subsystem corresponding to the terminal device.

[0283] In some embodiments, the communication unit 510 is specifically configured to:

[0284] Receive the M capability sets reported by the terminal device.

[0285] In some embodiments, the communication unit 510 is specifically configured to:

[0286] Receiving the M capability sets reported by the terminal device in a periodic reporting manner; or,

[0287] Receiving the M capability sets reported by the terminal device through conditional trigger reporting; or,

[0288] Receive the M capability sets reported by the terminal device through event-triggered reporting.

[0289] In some embodiments, the communication unit 510 is specifically configured to:

[0290] Receive the M capability sets reported by the terminal device through RRC signaling or NAS signaling.

[0291] In some embodiments, when the terminal device reports the M capability sets through RRC signaling, the RRC signaling is RRC signaling during the RRC connection establishment process, or the RRC signaling is RRC signaling after the RRC connection establishment is completed.

[0292] In some embodiments, when the terminal device reports the M capability sets through NAS signaling, the NAS signaling is one of the following: service request signaling, PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0293] In some embodiments, the communication unit 510 is specifically configured to:

[0294] Receive the M capability sets reported by the terminal device during the random access process.

[0295] In some embodiments, the communication unit 510 is specifically configured to:

[0296] Receive the M capability sets reported by the terminal device through other network devices.

[0297] In some embodiments, the communication unit 510 is further used to send first information, wherein the first information is used to instruct the terminal device to activate the N capability sets among the M capability sets supported by the terminal device.

[0298] In some embodiments, the first information is parameter information in RB establishment, or the first information is carried through non-access stratum NAS signaling.

[0299] In some embodiments, when the first information is carried through NAS signaling, the NAS signaling is one of the following: service request signaling, protocol data unit PDU session establishment signaling, NAS signaling during the PDU session establishment process, PDU session modification signaling, and NAS signaling during the PDU session modification process.

[0300] In some embodiments, the capability set in the M capability sets includes at least one of the following information elements: supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, coding, modulation scheme, measurement capability, air interface technology, basic parameter set, receiver architecture, receiver type, receiver capability, maximum transmit power, and supported features;

[0301] Among them, different capability sets in the M capability sets have different values ​​for at least some of the information elements.

[0302] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0303] It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 500 are respectively for implementing the corresponding processes of the network device in the method 300 shown in Figure 7. For the sake of brevity, they will not be repeated here.

[0304] Figure 11 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in Figure 11 includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0305] In some embodiments, as shown in FIG11 , the communication device 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0306] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0307] In some embodiments, as shown in FIG11 , the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, the transceiver 630 may send information or data to other devices, or receive information or data sent by other devices.

[0308] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

[0309] In some embodiments, the processor 610 may implement the functions of a processing unit in a terminal device, or the processor 610 may implement the functions of a processing unit in a network device, which will not be described in detail here for the sake of brevity.

[0310] In some embodiments, the transceiver 630 may implement the functions of a communication unit in a terminal device, which will not be described in detail here for the sake of brevity.

[0311] In some embodiments, the transceiver 630 may implement the function of a communication unit in a network device, which will not be described in detail here for the sake of brevity.

[0312] In some embodiments, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0313] In some embodiments, the communication device 600 may specifically be a terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0314] Figure 12 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 700 shown in Figure 12 includes a processor 710, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0315] In some embodiments, as shown in FIG12 , the apparatus 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0316] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0317] In some embodiments, the processor 710 may implement the functions of a processing unit in a terminal device, or the processor 710 may implement the functions of a processing unit in a network device, which will not be described in detail here for the sake of brevity.

[0318] In some embodiments, the apparatus 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips. Optionally, the processor 710 may be located inside or outside the chip.

[0319] In some embodiments, the input interface 730 may implement the function of a communication unit in a terminal device, or the input interface 730 may implement the function of a communication unit in a network device.

[0320] In some embodiments, the apparatus 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips. Optionally, the processor 710 may be located inside or outside the chip.

[0321] In some embodiments, the output interface 740 may implement the function of a communication unit in a terminal device, or the output interface 740 may implement the function of a communication unit in a network device.

[0322] In some embodiments, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0323] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the terminal device in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0324] In some embodiments, the device mentioned in the embodiments of the present application may also be a chip, such as a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0325] FIG13 is a schematic block diagram of a communication system 800 provided in an embodiment of the present application. As shown in FIG13 , the communication system 800 includes a terminal device 810 and a network device 820 .

[0326] Among them, the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they will not be repeated here.

[0327] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0328] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0329] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0330] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0331] In some embodiments, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0332] In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0333] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0334] In some embodiments, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0335] In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0336] The embodiment of the present application also provides a computer program.

[0337] In some embodiments, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0338] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0339] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0340] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

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

[0344] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

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

Claims

1. A wireless communication method, characterized in that: include: The terminal device activates N capability sets among the M capability sets it supports; Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

2. The method according to claim 1, characterized in that At least some of the M capability sets are associated with each other.

3. The method according to claim 1 or 2, characterized in that When N≥2, the N capability sets are associated capability sets.

4. The method according to any one of claims 1 to 3, characterized in that Different capability sets in the M capability sets correspond to different services respectively; or, Different capability sets in the M capability sets correspond to different application scenarios respectively; or, Different capability sets in the M capability sets correspond to different wireless access technologies respectively; or, Different capability sets in the M capability sets correspond to different hardware resource slice requirements; or, Different capability sets in the M capability sets correspond to different radio resource control RRC connection states; or, Different capability sets in the M capability sets correspond to different communication parameters respectively; or, Different capability sets in the M capability sets correspond to different quality of service QoS requirements; or, Different capability sets in the M capability sets correspond to different radio bearers RB respectively; or, Different capability sets in the M capability sets correspond to different bandwidth parts BWP respectively; or, Different capability sets in the M capability sets correspond to different terminal operating frequency bands; or, Different capability sets in the M capability sets correspond to different communication subsystems respectively.

5. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different services respectively, activation and / or switching of capability sets in the M capability sets are associated with the executed service type.

6. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different application scenarios respectively, activation and / or switching of capability sets in the M capability sets are associated with the application scenarios.

7. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different radio access technologies respectively, activation and / or switching of capability sets in the M capability sets are associated with the accessed radio access technology.

8. The method according to claim 4, characterized in that In the case where different capability sets in the M capability sets correspond to different hardware resource slicing requirements, respectively, activation and / or switching of capability sets in the M capability sets are associated with the required hardware resources.

9. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different RRC connection states respectively, activation and / or switching of capability sets in the M capability sets are associated with the RRC connection state.

10. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different communication parameters respectively, activation and / or switching of capability sets in the M capability sets are associated with the used communication parameters.

11. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different QoS requirements respectively, activation and / or switching of capability sets in the M capability sets are associated with the required QoS.

12. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different RBs respectively, activation and / or switching of capability sets in the M capability sets are associated with the established RBs.

13. The method according to claim 4, characterized in that In the case that different capability sets in the M capability sets correspond to different BWPs respectively, activation and / or switching of capability sets in the M capability sets are associated with the activated BWP.

14. The method according to claim 4, characterized in that In the case where different capability sets in the M capability sets correspond to different terminal operating frequency bands, respectively, activation and / or switching of capability sets in the M capability sets are associated with the operating frequency band of the terminal device.

15. The method according to claim 4, characterized in that In the case where different capability sets in the M capability sets correspond to different communication subsystems, the M capability sets The activation and / or switching of the capability set in the combination is associated with the communication subsystem corresponding to the terminal device.

16. The method according to any one of claims 1 to 15, characterized in that Before the terminal device activates the N capability sets, the method further includes: The terminal device receives first information, wherein the first information is used to instruct the terminal device to activate the N capability sets among the M capability sets supported by the terminal device.

17. The method according to claim 16, characterized in that The first information is parameter information in RB establishment, or the first information is carried through non-access layer NAS signaling.

18. The method according to claim 17, characterized in that In the case where the first information is carried through NAS signaling, the NAS signaling is one of the following: service request signaling, protocol data unit PDU session establishment signaling, NAS signaling during PDU session establishment, PDU session modification signaling, and NAS signaling during PDU session modification.

19. The method according to any one of claims 1 to 18, characterized in that Before the terminal device activates the N capability sets, the method further includes: The terminal device reports the M capability sets supported by it.

20. The method of claim 19, wherein: The terminal device reports the M capability sets supported by it, including: The terminal device reports the M capability sets supported by it in a periodic reporting manner; or, The terminal device reports the M capability sets supported by it in a condition-triggered reporting manner; or, The terminal device reports the M capability sets it supports by means of event-triggered reporting.

21. The method of claim 19, wherein: The terminal device reports the M capability sets supported by it, including: The terminal device reports the M capability sets it supports through RRC signaling or NAS signaling.

22. The method according to claim 21, characterized in that In the case where the terminal device reports the M capability sets it supports through RRC signaling, the RRC signaling is the RRC signaling during the RRC connection establishment process, or the RRC signaling is the RRC signaling after the RRC connection establishment is completed.

23. The method of claim 21, wherein: In the case where the terminal device reports the M capability sets it supports through NAS signaling, the NAS signaling is one of the following: service request signaling, PDU session establishment signaling, NAS signaling during PDU session establishment, PDU session modification signaling, and NAS signaling during PDU session modification.

24. The method of claim 19, wherein: The terminal device reports the M capability sets supported by it, including: The terminal device reports the M capability sets it supports during the random access process.

25. The method of claim 19, wherein: The terminal device reports the M capability sets supported by it, including: The terminal device reports the M capability sets supported by it to the target base station through the source base station.

26. The method according to any one of claims 1 to 25, characterized in that The capability set in the M capability sets includes at least one of the following information elements: supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, coding, modulation mode, measurement capability, air interface technology, basic parameter set, receiver architecture, receiver type, receiver capability, maximum transmit power and supported features; Among them, the values ​​of at least some information elements in different capability sets among the M capability sets are different.

27. A method of wireless communication, characterized in that: include: The network device obtains M capability sets supported by the terminal device; The network device determines N capability sets activated from the M capability sets; Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

28. The method of claim 27, wherein: At least some of the M capability sets are associated with each other.

29. The method according to claim 27 or 28, characterized in that When N≥2, the N capability sets are associated capability sets.

30. The method according to any one of claims 27 to 29, characterized in that Different capability sets in the M capability sets correspond to different services respectively; or, Different capability sets in the M capability sets correspond to different application scenarios respectively; or, Different capability sets in the M capability sets correspond to different wireless access technologies respectively; or, Different capability sets in the M capability sets correspond to different hardware resource slice requirements; or, Different capability sets in the M capability sets correspond to different radio resource control RRC connection states; or, Different capability sets in the M capability sets correspond to different communication parameters respectively; or, Different capability sets in the M capability sets correspond to different quality of service QoS requirements; or, Different capability sets in the M capability sets correspond to different radio bearers RB respectively; or, Different capability sets in the M capability sets correspond to different bandwidth parts BWP respectively; or, Different capability sets in the M capability sets correspond to different terminal operating frequency bands; or, Different capability sets in the M capability sets correspond to different communication subsystems respectively.

31. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different services respectively, activation and / or switching of capability sets in the M capability sets are associated with the executed service type.

32. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different application scenarios respectively, activation and / or switching of capability sets in the M capability sets are associated with the application scenarios.

33. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different radio access technologies respectively, activation and / or switching of capability sets in the M capability sets are associated with the accessed radio access technology.

34. The method of claim 30, wherein: In the case where different capability sets in the M capability sets correspond to different hardware resource slicing requirements, respectively, activation and / or switching of capability sets in the M capability sets are associated with the required hardware resources.

35. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different RRC connection states respectively, activation and / or switching of capability sets in the M capability sets are associated with the RRC connection state.

36. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different communication parameters respectively, activation and / or switching of capability sets in the M capability sets are associated with the used communication parameters.

37. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different QoS requirements respectively, activation and / or switching of capability sets in the M capability sets are associated with the required QoS.

38. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different RBs respectively, activation and / or switching of capability sets in the M capability sets are associated with the established RBs.

39. The method of claim 30, wherein: In the case that different capability sets in the M capability sets correspond to different BWPs respectively, activation and / or switching of capability sets in the M capability sets are associated with the activated BWP.

40. The method of claim 30, wherein: In the case where different capability sets in the M capability sets correspond to different terminal operating frequency bands, respectively, activation and / or switching of capability sets in the M capability sets are associated with the operating frequency band of the terminal device.

41. The method of claim 30, wherein: In the case where different capability sets in the M capability sets correspond to different communication subsystems respectively, activation and / or switching of capability sets in the M capability sets are associated with the communication subsystem corresponding to the terminal device.

42. The method according to any one of claims 27 to 41, characterized in that The network device obtains M capability sets supported by the terminal device, including: The network device receives the M capability sets reported by the terminal device.

43. The method of claim 42, wherein: The network device receives the M capability sets reported by the terminal device, including: The network device receives the M capability sets reported by the terminal device in a periodic reporting manner; or, The network device receives the M capability sets reported by the terminal device in a condition-triggered reporting manner; or, The network device receives the M capability sets reported by the terminal device through event-triggered reporting.

44. The method of claim 42, wherein: The network device receives the M capability sets reported by the terminal device, including: The network device receives the M capability sets reported by the terminal device through RRC signaling or NAS signaling.

45. The method of claim 44, wherein: In the case where the terminal device reports the M capability sets through RRC signaling, the RRC signaling is the RRC signaling during the RRC connection establishment process, or the RRC signaling is the RRC signaling after the RRC connection establishment is completed.

46. ​​The method of claim 44, wherein: In the case where the terminal device reports the M capability sets through NAS signaling, the NAS signaling is one of the following: service request signaling, PDU session establishment signaling, NAS signaling during PDU session establishment, PDU session modification signaling, and NAS signaling during PDU session modification.

47. The method of claim 42, wherein: The network device receives the M capability sets reported by the terminal device, including: The network device receives the M capability sets reported by the terminal device during the random access process.

48. The method of claim 42, wherein: The network device receives the M capability sets reported by the terminal device, including: The network device receives the M capability sets reported by the terminal device through other network devices.

49. The method according to any one of claims 27 to 48, characterized in that The method further comprises: The network device sends first information, wherein the first information is used to instruct the terminal device to activate the N capability sets among the M capability sets supported by the terminal device.

50. The method of claim 49, wherein: The first information is parameter information in RB establishment, or the first information is carried through non-access layer NAS signaling.

51. The method of claim 50, wherein: In the case where the first information is carried through NAS signaling, the NAS signaling is one of the following: service request signaling, protocol data unit PDU session establishment signaling, NAS signaling during PDU session establishment, PDU session modification signaling, and NAS signaling during PDU session modification.

52. The method according to any one of claims 27 to 51, characterized in that The capability set in the M capability sets includes at least one of the following information elements: supported bandwidth, number of antennas, half-duplex capability, mobility, processing time, coding, modulation mode, measurement capability, air interface technology, basic parameter set, receiver architecture, receiver type, receiver capability, maximum transmit power and supported features; Among them, the values ​​of at least some information elements in different capability sets among the M capability sets are different.

53. A terminal device, characterized in that: include: A processing unit, configured to activate N capability sets among the M capability sets supported by the terminal device; Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

54. A network device, characterized in that: include: A communication unit, used to obtain M capability sets supported by the terminal device; A processing unit, configured to determine N capability sets to be activated from among the M capability sets; Wherein, M and N are both positive integers, M≥2, N=1, or N≥2 and N<M.

55. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method as claimed in any one of claims 1 to 26.

56. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the network device executes the method as claimed in any one of claims 27 to 52.

57. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 26.

58. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 27 to 52.

59. A computer-readable storage medium, characterized in that Used for storing a computer program, when the computer program is executed, the method according to any one of claims 1 to 26 is implemented.

60. A computer-readable storage medium, characterized in that Used to store a computer program, when the computer program is executed, the method according to any one of claims 27 to 52 is implemented.

61. A computer program product, characterized in that The method comprises computer program instructions, and when the computer program instructions are executed, the method according to any one of claims 1 to 26 is implemented.

62. A computer program product, characterized in that Comprising computer program instructions, when the computer program instructions are executed, the method according to any one of claims 27 to 52 is implemented.

63. A computer program, characterized in that When the computer program is executed, the method according to any one of claims 1 to 26 is implemented.

64. A computer program, characterized in that When the computer program is executed, the method according to any one of claims 27 to 52 is implemented.

Images