UE capability reporting method and apparatus

Abstract

The present application provides a UE capability reporting method and an apparatus, which are used for reducing signaling overheads of UE capability reporting and adapting to a product development pace. Capability information of a terminal device comprises capability information related to features and corresponding identifiers, so that the capability information of each feature is isolated from basic capability information of the terminal device, and the capability information of each feature is also independent of each other, thereby decoupling reporting sequences (or reporting positions). By means of the identifiers, the capability information of the features are flexibly added to or deleted from the capability information of the terminal device, such that on the one hand, a certain feature can be developed in advance to adapt to a product release pace and a market pace, and on the other hand, signaling overheads can be reduced.

Description

A UE capability reporting method and device

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to the Chinese Patent Application No. 202411239673.2, filed on September 5, 2024, and entitled "A UE capability reporting method and device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, and in particular to a UE capability reporting method and device. BACKGROUND

[0004] Due to different hardware conditions or different software versions, the capabilities of different terminal devices can also be different. In order to better provide services for terminal devices, network devices need to know the capabilities of terminal devices in order to configure and schedule terminal devices.

[0005] With the evolution of standard protocol versions, new terminal device features are constantly introduced, and the UE capability reporting code stream is also getting larger and larger. According to the current UE capability information reporting method, the features that are not supported by the terminal device cannot be completely trimmed in the UE capability code stream, resulting in large signaling overhead. Moreover, according to the current UE capability information reporting method, the UE capabilities related to different features are coupled with each other, which results in that the feature capabilities can be completely determined only after all features are discussed and the protocol is closed, so that the feature development depends on the protocol closing pace and cannot be consistent with the product release or market pace, which will affect the development pace of the product.

[0006] In summary, how to reduce the signaling overhead of UE capability reporting and how to adapt to the product development pace are problems to be solved. SUMMARY

[0007] The present application provides a UE capability reporting method and device for reducing the signaling overhead of UE capability reporting and adapting to the product development pace.

[0008] In a first aspect, the present application provides a communication method, the execution subject of the method can be a terminal device, or a chip or circuit on the terminal device side. Taking the terminal device as an example, the method comprises: receiving a capability query message and sending first capability information of the terminal device, the first capability information comprising a first identifier and capability information related to a first feature, the first identifier being used to identify the first feature or the capability information related to the first feature.

[0009] At present, the capability information coding of a terminal device for a specific feature can be determined only after all features discussed in the 3GPP protocol version are finalized, because the capability information of each feature is coupled with each other, for example, the location (or the reporting order) of the capability related to each feature in the capability information of the terminal device needs to be fixed. However, in the present application, the identification corresponding to the capability information related to each feature is included in the capability information of the terminal device, so that the capability information of each feature can be isolated from the basic capability information of the terminal device, and the capability information of each feature is also independent of each other, which realizes the decoupling of the reporting order (or the reporting location), so that the present application can flexibly add the capability information of a new feature in the capability information of the terminal device through the identification. Compared with the way of reporting the capability information of each feature in a fixed order (or a fixed location), the present application can develop a certain feature in advance without waiting for other features to be finalized, so that it can adapt to the product release rhythm and market rhythm. For example, based on the implementation of R15, the feature of R17 extension can be directly developed without waiting for the finalization of the R16 extension. For another example, a certain feature in the R17 version can be implemented without waiting for the finalization of all parameters before the feature in the R17 version, or in other words, without waiting for the finalization of any other feature in the R17 version. Compared with extending the RRC protocol according to the version, the complexity of implementing a certain feature or certain features is lower. Moreover, because the features of the same / different versions are isolated, for each version, the development for a specific feature can be performed without waiting for all features to be stable and the protocol to be finalized, which can shorten the development cycle.

[0010] Moreover, according to the scheme of the present application, the capability information of each feature is decoupled in the capability information of the terminal device, so that the capability information of the terminal device can be tailored for the features that are not supported, thereby reducing the capability reporting overhead of the terminal device.

[0011] In a second aspect, the present application provides a communication method, and the execution subject of the method can be a network device, or a chip or circuit on the network device side. Taking the network device as an example, the method comprises: sending a capability query message and receiving first capability information of a terminal device, the first capability information comprising a first identification and capability information related to a first feature, the first identification being used for identifying the first feature, or being used for identifying the capability information related to the first feature.

[0012] At present, the capability information coding of a terminal device for a specific feature can be determined only after all features discussed in the 3GPP protocol version are finalized, because the capability information of each feature is coupled with each other, for example, the location (or the reporting order) of the capability related to each feature in the capability information of the terminal device needs to be fixed. In the present application, by including the identifier corresponding to the capability information related to each feature in the capability information of the terminal device, the capability information of each feature can be isolated from the basic capability information of the terminal device, and the capability information of each feature is also independent of each other, realizing the decoupling of the reporting order (or the reporting location), so that the present application can flexibly add the capability information of a new feature in the capability information of the terminal device through the identifier. Compared with the way of reporting the capability information of each feature in a fixed order (or a fixed location), the present application can develop a certain feature in advance without waiting for other features to be finalized, so as to adapt to the product release rhythm and market rhythm. For example, based on the implementation of R15, the feature of R17 extension can be directly developed without waiting for the finalization of the R16 extension. For another example, a certain feature in R17 version can be implemented without waiting for the finalization of all parameters before the feature in R17 version, or in other words, without waiting for the finalization of any other feature in R17 version. Compared with extending the RRC protocol according to the version, the complexity of implementing a certain feature or certain features is lower. Moreover, because the features of the same / different versions are isolated, for each version, the development for a specific feature can be performed without waiting for all features to be stable and the protocol to be finalized, so as to shorten the development cycle.

[0013] Moreover, according to the scheme of the present application, the capability information of each feature is decoupled in the capability information of the terminal device, so that the capability information of the terminal device can be tailored for the unsupported features, thereby reducing the capability reporting overhead of the terminal device.

[0014] Based on the first aspect and the second aspect, the following designs can be made:

[0015] In a possible design, the first feature related capability information includes at least one of the following: first feature related terminal device specific capability information, first feature related frequency band specific capability information, or first feature related frequency band combination specific capability information. Through the above design, the network device can obtain the detailed capability of the terminal device with respect to the first feature.

[0016] In a possible design, the first capability information includes the first identifier and the first characteristic-related capability information, including: the first capability information includes terminal device-specific capability information, the terminal device-specific capability information includes the first identifier and first characteristic-related terminal device-specific capability information; and / or, the first capability information includes first frequency band-specific capability information, the first frequency band-specific capability information includes the first identifier and first characteristic-related first frequency band-specific capability information; and / or, the first capability information includes first frequency band combination-specific capability information, the first frequency band combination-specific capability information includes the first identifier and first characteristic-related first frequency band combination-specific capability information.

[0017] By including the first characteristic-related identifier in each level, the first characteristic-related capability information can be flexibly reported in the UE capability of each level.

[0018] In a possible design, the first capability information further indicates that a second frequency band in a second frequency band combination corresponds to a first feature set identifier, the first feature set identifier is used to indicate that a first feature set in a first feature set collection and a second feature set in a second feature set collection are supported on the second frequency band in the second frequency band combination, and the position of the first feature set in the first feature set collection is the same as the position of the second feature set in the second feature set collection. Through the foregoing design, the basic capability information and the first characteristic-related capability information can be associated, so that the network device can obtain the complete capability of the second frequency band in the second frequency band combination.

[0019] In a possible design, any one feature set in the first feature set collection includes the first characteristic-related capability information.

[0020] In a possible design, any one feature set in the second feature set collection includes the basic capability information or the second characteristic-related capability information.

[0021] In a possible design, the number of feature sets included in the first feature set collection is the same as the number of feature sets included in the second feature set collection. Through the design, the basic capability information and the first characteristic-related capability information can be associated.

[0022] In a possible design, the first capability information further indicates that a first carrier of a third frequency band in a third frequency band combination corresponds to a first carrier feature set identifier, the first carrier feature set identifier is used to indicate that a first carrier feature set in a first carrier feature set collection and a second carrier feature set in a second carrier feature set collection are supported on the first carrier of the third frequency band in the third frequency band combination, and the position of the first carrier feature set in the first carrier feature set collection is the same as the position of the second carrier feature set in the second carrier feature set collection.

[0023] By the above design, the basic capability information and the capability information related to the first characteristic can be associated, so that the network device can obtain complete capability of the first carrier of the third frequency band in the third frequency band combination.

[0024] In a possible design, any one of the first set of carrier feature sets includes the capability information related to the first characteristic.

[0025] In a possible design, any one of the second set of carrier feature sets includes the basic capability information or the capability information related to the third characteristic.

[0026] In a possible design, the number of the carrier feature sets included in the first set of carrier feature sets is the same as the number of the carrier feature sets included in the second set of carrier feature sets. This design facilitates association of the basic capability information and the capability information related to the first characteristic.

[0027] In a possible design, the first capability information includes the first identifier and the capability information related to the first characteristic, including: the first capability information includes first information related to the first characteristic, and the first information includes the first identifier and at least one of the following: terminal device-specific capability information related to the first characteristic; first frequency band-specific capability information related to the first characteristic; or, first frequency band combination-specific capability information related to the first characteristic.

[0028] The above design decouples the capability information related to the first characteristic from the basic capability information in terms of hierarchy, and the capability information related to the first characteristic is carried in a separate information element and includes the first identifier in the information element. In this way, on the one hand, the coding structure of the basic capability information can be avoided to be changed, and the implementation complexity is reduced. On the other hand, one first identifier can be used to identify the capability information related to the first characteristic at different levels, and the signaling overhead can be reduced.

[0029] In a possible design, the capability information of the terminal device further includes second information related to the basic capability information, and the second information includes the basic capability information specific to the first frequency band combination.

[0030] In a possible design, the position of the basic capability information specific to the first frequency band combination in the second information is the same as the position of the capability information related to the first characteristic and specific to the first frequency band combination in the first information; or, the capability information related to the first characteristic and specific to the first frequency band combination includes a frequency band list, and the frequency band list indicates a frequency band included in the first frequency band combination; or, the capability information related to the first characteristic and specific to the first frequency band combination includes a first index, and a value of the first index is related to the position of the basic capability information specific to the first frequency band combination in the second information.

[0031] In this way, the base capability information of the first frequency band combination can be associated with the capability information of the first frequency band combination related to the first characteristic, so that the network device obtains the complete capability of the first frequency band combination.

[0032] In a possible design, the number of the frequency band combinations of the capability information related to the frequency band combination in the first information is the same as the number of the frequency band combinations of the capability information related to the frequency band combination in the second information. In this way, the base capability information of the first frequency band combination can be associated with the capability information of the first frequency band combination related to the first characteristic.

[0033] In a possible design, the terminal device supports the first feature set in the first information and the second feature set in the second information on the second frequency band in the second frequency band combination; the position of the first feature set in the feature set corresponding to the second frequency band of the second frequency band combination in the first information is the same as the position of the second feature set in the feature set corresponding to the second frequency band of the second frequency band combination in the second information, or the first feature set is associated with the second index, and the value of the second index is related to the position of the second feature set in the feature set corresponding to the second frequency band of the second frequency band combination in the second information.

[0034] In this way, the base capability information of the second frequency band of the second frequency band combination can be associated with the capability information of the second frequency band of the second frequency band combination related to the first characteristic, so that the network device obtains the complete capability of the second frequency band in the second frequency band combination.

[0035] In a possible design, the number of the feature set corresponding to the second frequency band of the second frequency band combination in the first information is the same as the number of the feature set corresponding to the second frequency band of the second frequency band combination in the second information. In this way, the base capability information of the second frequency band of the second frequency band combination can be associated with the capability information of the second frequency band of the second frequency band combination related to the first characteristic.

[0036] In a possible design, the first characteristic is one of the following: reduced capability or low complexity terminal, sidelink enhancement, mobility enhancement, multiple input multiple output, carrier aggregation, low latency service, extended reality, artificial intelligence, deterministic experience, or dual connectivity.

[0037] In a possible design, the method further includes: sending the second capability information of the terminal device, the second capability information including the first indication information, the first indication information being used to indicate to maintain or release or add the capability information of the first characteristic.

[0038] In a possible design, the second capability information can not include the base capability information.

[0039] If the basic capability information of the terminal device does not change, the terminal device only updates the capability information by adding or modifying the capability related to the feature, and the terminal device can further reduce the signaling overhead by reporting the capability information related to the feature and not reporting the basic capability information.

[0040] In a third aspect, the present application also provides a communication apparatus, which implements any of the methods provided in the first aspect. The communication apparatus can be implemented in hardware, or in software that is executed by the hardware. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0041] In a possible implementation, the communication apparatus includes a processor configured to support the communication apparatus to perform the corresponding functions of the terminal device in the above methods. The communication apparatus can further include a memory coupled with the processor, which stores program instructions and data necessary for the communication apparatus. Optionally, the communication apparatus further includes an interface circuit for supporting the communication between the communication apparatus and other devices such as network devices.

[0042] In a possible implementation, the communication apparatus includes corresponding functional modules for implementing the steps in the above methods. The functions can be implemented in hardware, or in software that is executed by the hardware. The hardware or software includes one or more modules corresponding to the functions described above.

[0043] In a possible implementation, the structure of the communication apparatus includes processing units and communication units, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the first aspect, which will not be repeated here.

[0044] In a fourth aspect, the present application also provides a communication apparatus, which implements any of the methods provided in the second aspect. The communication apparatus can be implemented in hardware, or in software that is executed by the hardware. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0045] In a possible implementation, the communication apparatus includes a processor configured to support the communication apparatus to perform the corresponding functions of the network device in the above methods. The communication apparatus can further include a memory coupled with the processor, which stores program instructions and data necessary for the communication apparatus. Optionally, the communication apparatus further includes an interface circuit for supporting the communication between the communication apparatus and other devices such as terminal devices.

[0046] In a possible implementation, the communication apparatus includes respective functional modules for implementing the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0047] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0048] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0049] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0050] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0051] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0052] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0053] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method provided in the second aspect, which will not be repeated here.

[0054] In an eleventh aspect, a communication system is provided, and the system includes the apparatus (e.g., a terminal device) of the first aspect and the apparatus (e.g., a network device) of the second aspect.

[0055] The technical effects of the technical solutions of any one of the third aspect to the eleventh aspect can be described with reference to the technical effects of the technical solutions of the first aspect, and the repeated parts will not be described herein. BRIEF DESCRIPTION OF DRAWINGS

[0056] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0057] FIG. 2 is a schematic diagram of an architecture of an open communication system according to an embodiment of the present application;

[0058] FIG. 3 is a schematic diagram of an open access network device according to an embodiment of the present application;

[0059] FIG. 4 is a schematic diagram of carrier aggregation according to an embodiment of the present application;

[0060] FIG. 5 is a schematic diagram of capability information according to an embodiment of the present application;

[0061] FIG. 6 is a schematic diagram of a feature set combination according to an embodiment of the present application;

[0062] FIG. 7 is a flowchart of a communication method according to an embodiment of the present application;

[0063] FIG. 8 is a schematic diagram of a structure of first capability information according to an embodiment of the present application;

[0064] FIG. 9 is a schematic diagram of a structure of first capability information according to an embodiment of the present application;

[0065] FIG. 10 is a schematic diagram of a structure of first capability information according to an embodiment of the present application;

[0066] FIG. 11 is a schematic diagram of a structure of first capability information according to an embodiment of the present application;

[0067] FIG. 12 is a schematic diagram of a feature set association according to an embodiment of the present application;

[0068] FIG. 13 is a schematic diagram of a structure of first capability information according to an embodiment of the present application;

[0069] FIG. 14 is a schematic diagram of a carrier feature set association according to an embodiment of the present application;

[0070] FIG. 15 is a schematic diagram of a structure of first capability information according to an embodiment of the present application;

[0071] FIG. 16 is a schematic diagram of a capability information association according to an embodiment of the present application;

[0072] FIG. 17 is a diagram of an example of capability information association according to embodiments of the present disclosure;

[0073] FIG. 18 is a diagram of an example of a communication device according to embodiments of the present disclosure;

[0074] FIG. 19 is a diagram of an example of a communication device according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0075] Embodiments of the present disclosure provide technical solutions that can be applied to various wireless communication systems. For example, the method provided by the embodiments of the present disclosure can be applied to a communication system related to the 3rd Generation Partnership Project (3GPP), such as a long term evolution (LTE) communication system, a 5th generation (5G) mobile communication system, or other next-generation mobile communication systems, such as a 6th generation (6G) communication system, or other similar communication systems. Other similar communication systems can include wireless fidelity (WIFI), vehicle to everything (V2X), internet of things (IoT) systems, narrow band internet of things (NB-IoT) systems, and the like.

[0076] Please refer to FIG. 1, which shows a network architecture of a communication system that can include at least one network device and at least one terminal device. FIG. 1 takes one terminal device as an example of the at least one terminal device, and takes one network device as an example of the at least one network device. The network device can be an access network device, or the network device includes an access network device and a core network. The network architecture shown in FIG. 1 is only illustrative, and the number of terminal devices and / or network devices can be fewer or more. The communication system described in the embodiments of the present disclosure is used to more clearly illustrate the technical solutions of the embodiments of the present disclosure, and does not limit the communication system to which the embodiments of the present disclosure are applicable. Those skilled in the art can know that, as the network architecture evolves, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems. When applying the technical solutions of the embodiments of the present disclosure to other communication systems, the devices, components, modules, etc. in the embodiments can be replaced by corresponding devices, components, modules in other communication systems, without limitation.

[0077] The network device related in the embodiments of the present application is mainly an access network device, therefore in the following, unless otherwise specified, the "network device" refers to a radio access network (RAN) device, which can be simply referred to as an access network device. The RAN can be a 3GPP related cellular system, for example, a 5G mobile communication system, or a future-oriented evolved system (for example, a 6G mobile communication system). The RAN can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), or a virtualized RAN (vRAN) and the like. The RAN can also be a communication system in which two or more of the above systems are fused. The RAN device can also be referred to as a RAN node, a RAN entity, or an access node and the like.

[0078] In a possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, and the like. The RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node / host node, or a radio controller, and the like. The RAN node can also be a server, a wearable device, a vehicle or a vehicle-mounted device, and the like. For example, the RAN node in the V2X technology can be a road side unit (RSU).

[0079] In another possible scenario, a RAN node can be a module or unit that completes part of functions of a base station; or multiple RAN nodes cooperate to assist a terminal device to implement wireless access, and different RAN nodes respectively implement part of functions of a base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU), etc. The functions of a CU can be implemented by one entity, or can also be implemented by different entities. For example, the functions of a CU can be further divided, that is, the control plane and the user plane are separated and implemented by different entities, respectively, as a control plane CU entity (that is, a CU-control plane (CP) entity) and a user plane CU entity (that is, a CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the RAN node. The CU and the DU can be separately arranged, or can also be included in the same network element, for example, in a baseband unit (BBU).

[0080] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in an ORAN system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in this application. Any one of the CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0081] The CU and the DU can be configured according to protocol layer functions of a wireless network that they implement: for example, the CU is configured to implement functions of a packet data convergence protocol (PDCP) layer and protocol layers above the PDCP layer (such as a radio resource control (RRC) layer and / or a service data adaptation protocol (SDAP) layer, etc.); the DU is configured to implement functions of protocol layers below the PDCP layer (such as a radio link control (RLC), a MAC layer, and / or a physical (PHY) layer, etc.). For specific descriptions of the above protocol layers, reference can be made to relevant technical specifications of the 3GPP or technical specifications of other applicable communication protocols. The above division of processing functions of the CU and the DU according to protocol layers is merely an example, and the division can also be made in other manners, which is not limited by the present application.

[0082] FIG. 2 shows an example diagram of an O-RAN system. It should be understood that the O-RAN system can also include other components in addition to the components shown in FIG. 2, which are not specifically limited herein. As shown in FIG. 2, the access network device can communicate with the core network (CN) through a backhaul link, and can communicate with the terminal device through an air interface. For example, the access network device can include a baseband unit (BBU) and a radio unit (RU). The BBU includes at least one CU and at least one DU, and the CU and the DU can communicate through at least one midhaul link. The RU can implement functions of a lower physical layer (Lower PHY) and a radio frequency (RF). In some examples, the RU can be a 3GPP transmission reception point (TRP) or a remote radio head (RRH) or other similar functional entity. In some examples, the Low-PHY can include part of PHY processing, such as fast Fourier transform (FFT), inverse fast Fourier transformation (IFFT), digital beamforming and filtering, etc. The BBU can communicate with the CN through a backhaul link, and the RU can communicate with at least one terminal device through an air interface. The BBU can communicate with at least one RU through a fronthaul link, and the BBU and the RU can be co-located or not co-located.

[0083] FIG. 3 is a diagram illustrating a network element function division and protocol layer structure of an O-RAN device. It should be noted that the configuration of the CU and the DU shown in FIG. 3 is only an example, and the CU and the DU can be configured to have functions according to needs. For example, the CU or the DU can be configured to have more protocol layer functions, or the CU or the DU can be configured to have partial processing functions of the protocol layer. The DU and the RU can be co-located or not co-located. The DU and the RU can exchange control plane information and user plane information through a lower-layer split-control, user and synchronization (LLS-CUS) interface via a fronthaul link. The LLS-CUS can include an LLS-C interface and an LLS-U interface that provide a control plane (C-Plane) and a user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and the RU. The DU and the RU have an LLS-M interface of the fronthaul link to exchange management information, and the management plane (M-Plane) refers to non-real-time management operations between the DU and the RU.

[0084] The DU and the RU can cooperate to jointly implement the functions of the PHY layer. One DU can be connected to one or more RUs. The functions of the DU and the RU can be configured in multiple ways according to design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement intermediate radio frequency functions. For another example, the DU is configured to implement high-layer functions in the PHY layer, and the RU is configured to implement low-layer functions in the PHY layer or implement the low-layer functions and radio frequency functions. The high-layer functions in the PHY layer can include a part of the functions of the PHY layer that are closer to the MAC layer, and the low-layer functions in the PHY layer can include another part of the functions of the PHY layer that are closer to the intermediate radio frequency side.

[0085] In the embodiments of the present application, the apparatus for implementing the functions of the network device can be the network device itself, or an apparatus capable of supporting the network device to implement the functions, such as a chip system or a combined device or component that can implement the functions of the network device, which can be installed in the network device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0086] In the embodiments of the present application, all the terminal devices capable of communicating data with the base station can be regarded as terminal devices. The terminal device is also referred to as a terminal, a user equipment (UE), a mobile station, or a mobile terminal, etc. The terminal device can be widely applied to various scenarios, such as D2D communication, V2X communication, machine-type communication (MTC), IoT, virtual reality, augmented reality, industrial control, automatic driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, or smart city, etc. For example, the terminal device can be a mobile phone, a computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a mechanical arm, a camera, a robot, or a smart home device (such as a television, an air conditioner, a sweeping machine, a sound box, a set-top box), a relay, a customer premise equipment (CPE), etc.

[0087] As introduced above, various terminal devices can be regarded as vehicle-mounted terminal devices if they are located on a vehicle (for example, placed / installed in the vehicle). The vehicle-mounted terminal device can be built-in as one or more components or units in a vehicle-mounted module, a vehicle-mounted module group, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit of the vehicle, and the vehicle can implement the method of the present application through the built-in vehicle-mounted module, vehicle-mounted module group, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit. The vehicle-mounted terminal device can be a whole vehicle device, a vehicle-mounted module, a vehicle, an on board unit (OBU), a roadside unit (RSU), a telematics box (T-box), a chip, or a system on chip (SOC), etc. The above chip or SOC can be installed in the vehicle, OBU, RSU, or T-box.

[0088] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device itself, or a device capable of supporting the terminal device to implement the function, such as a chip system or a combination device or component capable of implementing the function of the terminal device, which can be installed in the terminal device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0089] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0090] The technical background of the present application is introduced below.

[0091] In order to better provide services for terminal devices, the network device needs to know the capabilities of the terminal devices, so as to configure and schedule the terminal devices.

[0092] In the 5G system, the capabilities of the terminal devices can be divided into several levels. For example, as shown in FIG. 4, the level structure represents the structure of the capability information of the terminal devices. The capability information of the terminal devices can include:

[0093] - terminal device-specific capability information (also referred to as per UE capability or UE capability): applicable to all frequency bands and frequency band combinations. The terminal device-specific capability information includes the capabilities supported by the terminal device on all frequency bands. The terminal device-specific capability can include one or more of accessStratumRelease, pdcp-Parameters, rlc-Parameters, mac-Parameters, phy-Parameters, measAndMobParameters, and the like.

[0094] - band-specific capability information (also referred to as per band capability or band capability): usually related to the radio frequency capability of the terminal device. The band-specific capability information includes the capability of the terminal device on a specific frequency band. The capability can be different on different frequency bands. The band-specific capability can include one or more of FreqBandIndicatorNR, mimo-ParametersPerBand, bwp-WithoutRestriction, and the like. The band-specific capability information of the terminal device can be included in the supportedBandList. The frequency band list includes at least one frequency band supported by the terminal device. The frequency band corresponding to the band-specific capability information is indicated by the frequency band identifier.

[0095] - Band combination (BC) specific capability information (also referred to as per BC capability or band combination capability): The capability is a band combination related capability, which is mainly related to the capability of carrier aggregation (CA) and DC supported by the terminal device. One band combination can be composed of one or more bands supported by the terminal device configured for carrier aggregation or dual connectivity and the carriers included in the bands. That is, for one band combination reported by the terminal device, the network device can configure the carriers included in the bands in the band combination to the terminal device for carrier aggregation or dual connectivity transmission. In addition, from the capability signaling structure, the capability of a single band or a single carrier can also be reported through the signaling structure of the band combination. The band combination supported by the terminal device is usually related to the radio frequency capability and baseband capability of the terminal device. The band combination specific capability information of the terminal device can be included in the supported band combination list (supportedBandCombinationList).

[0096] The band combination list contains at least one band combination (BandCombination) supported by the terminal device. Each band combination can include one or more of the band list (BandList) corresponding to the band combination, the CA parameter (ca-ParametersNR), the multi-rAT dual connectivity (MRDC) parameter (mrdc-Parameters), the power level and other band combination specific capability information. The band list contains the bands (band) that make up the band combination.

[0097] Each band combination can also be associated with a feature set combination (FSC), which can be associated through a feature set combination identifier (FeatureSetCombinationId). The FSC contains the capability information of each band in the band combination (per BC per band capability). The FSC can also indicate the capability information of the carrier on the band (per CC capability).

[0098] per BC per band capability refers to a capability for a frequency band in a band combination. Each frequency band in a band combination can be associated with one or more feature sets (FS). A terminal device can report a combination of per BC per band capability for a band combination by reporting one or more rows of feature sets (FS). FIG. 5 shows an example of reporting different capabilities (such as including per CC capability and / or per BC per band capability) for a band combination by multiple rows of feature sets (FS) in a capability signaling structure. As shown in FIG. 5, a band combination BC 1 is composed of band A, band B and band C. For the band combination BC 1, a terminal device can report 3 rows of FS, each corresponding to a combination of BC capability that the terminal device can support. In the first row of FS, the FS of band A is FS1 (it can be understood that the ID of the FS is 1, and the following is similar), the FS of band B is FS2, and the FS of band C is FS3, which can be regarded as a combination of BC capability that a network can configure to the terminal device. In the second row of FS, the FS of band A is still FS1, the FS of band B is FS4, and the FS of band C is FS5, since the FS of band B is different from that in the first row of FS, and the FS of band C is different from that in the first row of FS, the combination of BC capability corresponding to the second row of FS is different from that in the first row. Different FSs correspond to different carrier capabilities, for example, a terminal device supports 5 carriers, in the first row of FS, 1 carrier on band A (it means that the terminal device supports one carrier on band A, and the following is similar), 2 carriers on band B, and 2 carriers on band C, for example, as shown in FIG. 6; in the second row of FS, 1 carrier on band A, 2 carriers on band B, and 1 carrier on band C. According to the capability information reported by the terminal device shown in FIG. 5, when a network device configures a band combination BC 1 for a terminal device, it can configure the carriers on which the terminal device works according to the feature set of each frequency band in the same row of FS. When the network device needs to switch the configuration, it can send RRC reconfiguration signaling to the terminal device to instruct the terminal device to switch to the configuration corresponding to the second row of feature sets. The feature set of a frequency band can be identified by a feature set identifier (FS ID). The FS ID can be zero, for example, in the third row of FS in FIG. 5, the FS ID of band C is FS 0, which means that the terminal device does not have uplink transmission capability and downlink transmission capability on band C, that is, it does not support receiving downlink signals and transmitting uplink signals on the carriers of band C.Each FS includes a FeatureSetDownlink information element (IE) for reporting downlink transmission capability and a FeatureSetUplink IE for reporting uplink transmission capability, to respectively indicate the uplink transmission capability and the downlink transmission capability of the terminal device. The per BC per band capability can also be referred to as a band feature set.

[0099] The per CC capability refers to the capability for a carrier on a frequency band in a band combination. The information of the per CC capability can be expressed in the form of a carrier list. Each carrier is associated with a FeatureSetPerCC (FSPC). The FSPC indicates the capability of the corresponding carrier, for example, including one or more of the subcarrier spacing (SCS) supported by the carrier, the maximum number of multiple-input multiple-output (MIMO) layers, the maximum carrier bandwidth, and the like. For example, the frequency band 1 in the band combination BC 1 can correspond to a carrier list including 3 component carriers (CC1, CC2, CC3), indicating that the terminal device supports at most 3 component carriers on the frequency band 1. Taking CC1 as an example, CC1 is associated with FSPC 1, and the FSPC 1 indicates the MIMO capability, the channel state information (CSI) measurement capability, the modulation type, and the like of CC1. Each FSPC includes a FeatureSetDownlinkPerCC IE for reporting downlink transmission capability and a FeatureSetUplinkPerCC IE for reporting uplink transmission capability, to respectively indicate the uplink transmission capability and the downlink transmission capability of the terminal device. The per CC capability can also be referred to as a carrier feature set.

[0100] The above introduces the related content of the capability reporting of the terminal device. The following introduces the problems existing in the current capability reporting of the terminal device.

[0101] With the evolution of the NR version, new features are constantly introduced, and the corresponding UE capabilities are also added to the terminal device's capability information. According to the structure of the terminal device's capability information in the foregoing, the newly added features are extended in each layer of the terminal device's capability information according to the version. From the perspective of abstract syntax notation one (ASN.1), that is, the encoding of the terminal device's capability information, for the unsupported features, the terminal device's capability information cannot be completely tailored to these features, resulting in a large terminal device capability reporting overhead, especially for per band and per BC UE capabilities, which causes a large overhead on each band and BC.

[0102] Moreover, according to the current UE capability information reporting manner, the UE capabilities related to different features are coupled with each other. For example, a new feature is proposed for the current 3GPP protocol version, but the reporting manner of the feature can be determined only after all the features discussed in the current 3GPP protocol version are finalized. For example, only after all the features discussed in the current 3GPP protocol version are finalized, the reporting order (which can also be understood as the extension order), the reporting content, and the like of each feature can be determined, so that the encoding structure of the terminal device's capability information can be determined. Therefore, after the current 3GPP protocol version is finalized, the encoding structure of the terminal device's capability information can be completely determined, and the corresponding features can be developed. However, the pace of 3GPP discussion does not necessarily match the pace of product release or market, which may affect the development pace of products.

[0103] A feature can be understood as a specific enhancement, or a specific function, or a specific service, or a specific terminal device type, or a specific network device type, or a specific capability. A feature has a corresponding capability. For example, a terminal device has / supports a first feature, the first feature corresponds to a first capability, and then the terminal device has the first capability; or the first capability corresponds to the first feature, and then the terminal device having the first capability can indicate that the terminal device supports the first feature. With the continuous development of communication technology, the 3GPP protocol is also constantly evolving, and each evolution will correspondingly produce one or more features. For example, 3GPP R16 introduces the URLLC feature compared with R15; R17 introduces the "Redcap", "sidelink enhancement", "mobility enhancement", and the like compared with R16. The first feature can be one or more features introduced by multiple versions, and the multiple versions include future versions. For example, the first feature includes one or more of the following features: "Redcap", "sidelink enhancement", "mobility enhancement", "MIMO", "CA", "low latency service", "XR", "AI", "deterministic experience", or "DC", and the like.

[0104] Based on this, the embodiment of the present application provides a communication method and device, which are used for reducing the signaling overhead of UE capability reporting and how to adapt to the product development rhythm. The method and the device are based on the same inventive concept. Since the principles of the method and the device for solving problems are similar, the implementation of the device and the method can be mutually referred to, and the repeated parts will not be described again.

[0105] In the embodiment of the present application, “when”, “if” and “whether” all refer to the objective situation that the device will make corresponding processing, and are not limited to time, and do not require the device to have a judgment action when implemented, nor mean that there are other limitations. Unless otherwise specified, “if” and “whether” can be replaced, “when” and “in the case of” can be replaced. “When” and “if” / “whether” can be replaced.

[0106] In the embodiment of the present application, “at least one” refers to one or more, and “multiple” refers to two or more. “And / or” describes the association between the associated objects, indicating that there can be three relationships, for example, A and / or B can represent the following situations: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects before and after it. “At least one of the following” or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0107] In addition, unless otherwise stated, the ordinal numbers “first”, “second”, etc. mentioned in the embodiments of the present application are used to distinguish a plurality of objects, and are not used to limit the size, content, order, time sequence, priority or importance of the plurality of objects.

[0108] In the present application, the carrier can also be referred to as a component carrier (CC). The feature set (FS) can also be referred to as a characteristic set, etc.

[0109] It should be noted that the names of cells, fields, containers, lists, and the names of information in the present application are only exemplary names.

[0110] In the present application, the basic capability information is only a substitute for some capability information, and the present application does not limit the name of the capability information.

[0111] In addition, for the convenience of description, the identity associated with the characteristic-related capability information is described as the identity associated with the characteristic, for example, the first identity is the identity associated with the first characteristic-related capability information, and for the convenience of description, the first identity is referred to as the first characteristic-associated identity.

[0112] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

[0113] As shown in FIG. 7, it is a flowchart of a UE capability reporting method provided by the embodiments of the present application.

[0114] S701, the network device sends a capability query message. Correspondingly, the terminal device receives the capability query message.

[0115] The capability query message is used to query the capability information of the terminal device.

[0116] S702, the terminal device sends the first capability information of the terminal device. Correspondingly, the network device receives the first capability information of the terminal device.

[0117] Optionally, the first capability information can be included in a first message, and the first message is used to report the capability information of the terminal device. For example, the first message can be a UE capability information message.

[0118] The first capability information includes at least one characteristic-related capability information and at least one identity associated with the characteristic. The identity associated with the characteristic can be understood as an identity used to identify the characteristic or an identity used to identify the characteristic-related capability information. The identities associated with different characteristics can be different.

[0119] Optionally, the correspondence between the characteristics and the identities can be pre-defined by a protocol or configured by the network device. For example, the protocol stipulates that the identity of the first characteristic is the first identity, the identity of the second characteristic is the second identity, and so on. For another example, the network device indicates the correspondence between the characteristics and the identities through signaling (such as system information), and the correspondence includes that the first characteristic corresponds to the first identity, the second characteristic corresponds to the second identity, and so on. The embodiments of the present application do not limit the specific implementation form of the correspondence between the characteristics and the identities, for example, the correspondence between the characteristics and the identities is shown in Table 1.

[0120] Table 1

[0121] For example, taking the first characteristic as an example, the first capability information includes the first characteristic-related capability information and the first identity. The first identity is used to identify the first characteristic or is used to identify the at least one capability information related to the first characteristic.

[0122] The first characteristic related capability information can comprise a first string, or a first octet string, or a first bit string. The first characteristic related capability information can describe at least one capability information related to the first characteristic. It can be understood that the first characteristic related capability information can only comprise extended capability information related to the first characteristic. For example, the first characteristic related capability information can comprise first characteristic related capability information extended in a specific version.

[0123] For example, the first characteristic related capability information can comprise at least one of: first characteristic related per UE capability information, first characteristic related per band capability information, first characteristic related per BC capability information, first characteristic related feature set, or first characteristic related carrier feature set.

[0124] For example, the first characteristic is one of: reduced capability or low capability terminal (RedCap), sidelink enhancement, mobility enhancement, MIMO, carrier aggregation, low latency service, extended reality (XR), artificial intelligence (AI), determinism experience, or dual connection (DC). Similarly, the second characteristic, the third characteristic, and so on in the following can also be one of the above characteristics.

[0125] The structure of the first capability information will be described in detail below.

[0126] The reporting of the newly added features can only determine the data structure of the capability information of the terminal device after all the features discussed in the 3GPP protocol version are finalized, and in the data structure, the capability information of each feature is coupled with each other, for example, the position (or the reporting order) in the capability information of the terminal device is fixed. In the present application, by including the identifier corresponding to the feature-related capability information in the capability information of the terminal device, the capability information of each feature can be isolated from the basic capability information of the terminal device, and the capability information of each feature is also independent of each other, realizing the decoupling of the reporting order (or the reporting position), so that the present application can flexibly add the capability information of a new feature in the capability information of the terminal device through the identifier. Compared with the way of reporting the capability information of each feature in a fixed order (or a fixed position), the present application can develop a certain feature in advance without waiting for other features to be finalized, so as to adapt to the product release rhythm and market rhythm. For example, based on the implementation of R15, the R17 extended feature can be directly developed without waiting for the finalization of the R16 extended feature. For another example, a certain feature in the R17 version can be implemented without waiting for the finalization of all the parameters before the feature in the R17 version, or in other words, without waiting for the finalization of any other feature in the R17 version. Compared with extending the RRC protocol according to the version, the complexity of implementing a certain feature or certain features is lower. Moreover, since the features of the same / different versions are isolated, for each version, the development of a specific feature can be carried out without waiting for all the features to be stable and the protocol to be finalized, so as to shorten the development cycle.

[0127] Moreover, according to the scheme of the present application, the capability information of each feature is no longer coupled with each other in the capability information of the terminal device, so for the unsupported features, the capability information of the terminal device can be trimmed to remove these features, so as to reduce the capability reporting overhead of the terminal device.

[0128] The present application provides two exemplary structures of the first capability information.

[0129] The first structure: the feature-related capability information of the corresponding level is extended in each level capability information of the first capability information, and the identifier associated with the feature-related capability information is included in the level capability information. For example, the first capability information can include one or more of the following capability information: terminal device-specific capability information, frequency band-specific capability information, frequency band combination-specific capability information, feature set collection or carrier feature set collection. The first feature-related capability information of the corresponding level can be extended in each level capability information of the first capability information, and the first identifier is included in the level capability information. The following describes each level IE, and the first capability information can include one or more of the following:

[0130] 1. Terminal device-specific capability information

[0131] The terminal device-specific capability information can include access stratum version, PDCP parameter, RLC parameter, MAC parameter, PHY parameter, measurement and addition parameter, and the like. The access stratum version and the like mentioned above can be understood as basic capability information specific to the terminal device. The basic capability information of the terminal device can be understood as basic capability that the terminal device needs to support to establish a connection with the network device and perform transmission, and can also be understood as terminal device capability introduced in the initial version of the standard.

[0132] Optionally, in the terminal device-specific capability information, at least one feature-related terminal device-specific capability information and an identifier associated with the at least one feature respectively can also be included. The identifier associated with the at least one feature respectively can be understood as an identifier associated with the at least one feature-related terminal device-specific capability information respectively. Taking the first feature as an example, in the terminal device-specific capability information, the first feature-related terminal device-specific capability information and the first identifier can be included.

[0133] In a possible implementation manner, the first UE capability list can be included in the terminal device-specific capability information. The first UE capability list can include at least one feature-related terminal device-specific capability information and an identifier associated with the at least one feature respectively (or an identifier associated with the at least one feature-related terminal device-specific capability information respectively). For example, the first UE capability list can include the first identifier and the first feature-related terminal device-specific capability information. Optionally, the first UE capability list can also include the second identifier and the second feature-related terminal device-specific capability information, the third identifier and the third feature-related terminal device-specific capability information, and the like. The second identifier and the third identifier have similar functions to the first identifier, and will not be described here.

[0134] Taking the first feature as MIMO and the second feature as XR as examples, the first capability information can be as shown in FIG. 8. In the first UE capability list, the MIMO-associated identifier MIMO-ID, UE-CapabilityMIMO-PerUE and the XR-associated identifier XR-ID, UE-CapabilityXR-PerUE can be included. The UE-CapabilityMIMO-PerUE includes the first identifier and the first feature-related terminal device-specific capability information, and the UE-CapabilityXR-PerUE includes the second identifier and the second feature-related terminal device-specific capability information. It should be understood that the names of the information in FIG. 8 are only examples, and do not limit the naming of the information.

[0135] For example, the information element carrying the first UE capability list can be as follows:

[0136] Wherein, the UE-CapabilityPerUE-FeatureList is a first UE capability list, which can carry at least one set of terminal device specific capability information related to at least one feature; the maxNrofFeature is the maximum number of features, which can be an integer greater than or equal to 1; the UE-CapablityPerUE can carry a set of terminal device specific capability information related to one feature, and the set of terminal device specific capability information related to one feature can include terminal device specific capability information and its identifier; the featureCapabilityId is used to identify the feature or the feature related capability information or the feature related terminal device specific capability information, for example, a first identifier, a second identifier, etc.; the featureCapability is used to carry the feature related capability information or the feature related terminal device specific capability information indicated by the featureCapabilityId. Wherein, the capability information can be carried by a string or a byte string or a bit string, and the contents included in the featureCapability corresponding to different features can be different. In the above example, the featureCapabilityId and / or the featureCapability can be optional fields or mandatory fields, which are not limited herein. The number of UE-CapablityPerUE included in the first UE capability list can also be 0.

[0137] As an optional solution, the first UE capability list can add or modify the feature related terminal device specific capability information reported by the first list. Wherein, the first list can include at least one set of terminal device specific capability information, and each set of terminal device specific capability information can include one feature related terminal device specific capability information and the identifier associated with the feature. Optionally, in the case that the identifier included in the first list is not reported by the terminal device before or not stored by the network device, it means that the new feature capability information is added; in the case that the identifier included in the first list is the identifier reported by the terminal device before or stored by the network device, it means that the capability information of the previous feature is updated or modified.

[0138] The first UE capability list can also delete or release the feature or the feature related terminal device specific capability information by the second list. Wherein, the second list can include at least one identifier associated with at least one feature or at least one feature related capability information.

[0139] Based on the above solution, the information element carrying the first UE capability list can be as follows:

[0140] The UE-CapabilityPerUEFeatureToAddModList is a first list, which can include at least one UE-CapabilityPerUE, and each UE-CapabilityPerUE can include a set of terminal device-specific capability information, which can include an identity of a feature and terminal device-specific capability information related to the feature.

[0141] The UE-CapabilityPerUEFeatureToReleaseList is a second list, which can include at least one identity of a feature, used to indicate to delete or release terminal device-specific capability information related to the at least one feature.

[0142] 2. Band-specific capability information

[0143] Optionally, the first capability information can include band-specific capability information of at least one frequency band. Taking a first frequency band as an example, the band-specific capability information of the first frequency band includes one or more of the following: a band identity (bandNR) of the first frequency band, MIMO parameters (mimo-ParametersPerBand) of the first frequency band, extended cyclic prefix capability (extendedCP), modulation order capability (such as pdsch-256QAM-FR2 or pusch-256QAM), bandwidth part related capability (such as bwp-WithoutRestriction or bwp-SameNumerology or bwp-DiffNumerology), and the like. The above-mentioned example capability information can be understood as basic band-specific capability information of the first frequency band.

[0144] Optionally, the band-specific capability information can further include at least one feature-related band-specific capability information and an identity of the at least one feature, respectively. The identity of the at least one feature can be understood as an identity of the at least one feature-related band-specific capability information, respectively. The band-specific capability information can further include a first identity and first feature-related band-specific capability information, wherein the first feature-related band-specific capability information can include first feature-related band-specific capability information of at least one frequency band. If there is another feature, such as a second feature, the band-specific capability information can further include a second identity and second feature-related band-specific capability information, wherein the second feature-related band-specific capability information can include second feature-related band-specific capability information of at least one frequency band, and so on.

[0145] Optionally, the first characteristic related capability information specific to the first frequency band comprises an identity of the first frequency band (e.g. a band number of the first frequency band), or comprises an index of the first frequency band, the index of the first frequency band being related to a position of the first frequency band in the at least one frequency band included in the first capability information. For example, the first capability information comprises capability information specific to the first frequency band, capability information specific to the second frequency band and capability information specific to the third frequency band, the index of the first frequency band is 0 (or 1).

[0146] Optionally, the number of frequency bands included in the basic capability information in the first capability information is the same as the number of frequency bands included in the capability information related to each characteristic (e.g. the first characteristic, the second characteristic, etc.) in the first capability information. The capability information of the same position of the frequency bands in the capability information related to each characteristic (e.g. the first characteristic) in the basic capability information corresponds to the same frequency band. In other words, the number and the order of the capability information of the frequency bands in the basic information is the same as the number and the order of the capability information of the frequency bands in the capability information related to each characteristic (e.g. the first characteristic).

[0147] The capability information specific to a certain frequency band (e.g. the first frequency band) in the basic capability information and the capability information specific to the frequency band related to each characteristic (e.g. the first characteristic, the second characteristic, etc.) are combined as the capability information of the terminal device on the first frequency band. In other words, the terminal device should support the capability information specific to the frequency band in the basic capability information reported by the terminal device on the frequency band, and the capability information specific to the frequency band related to each characteristic (e.g. the first characteristic, the second characteristic, etc.).

[0148] In a possible implementation, the second UE capability list can be included in the capability information specific to the frequency band, the second UE capability list can comprise at least one characteristic related capability information specific to the frequency band and an identity associated with the at least one characteristic respectively. For example, taking the first frequency band as an example, the second UE capability list can comprise a first identity and the first characteristic related capability information specific to the frequency band, the first characteristic related capability information specific to the frequency band comprises the first characteristic related capability information specific to the frequency band of at least one frequency band. Optionally, the second UE capability list can further comprise a second identity and the second characteristic related capability information specific to the frequency band, a third identity and the third characteristic related capability information specific to the frequency band, etc., the second characteristic related capability information specific to the frequency band comprises the second characteristic related capability information specific to the frequency band of at least one frequency band, the third characteristic related capability information specific to the frequency band comprises the third characteristic related capability information specific to the frequency band of at least one frequency band.

[0149] Taking the first feature as MIMO and the second feature as XR as an example, the first capability information can be as shown in FIG. 9, where the second UE capability list includes an MIMO-associated identifier MIMO-ID, UE-CapabilityMIMO-PerBand, and an XR-associated identifier XR-ID, UE-CapabilityXR-PerBand. UE-CapabilityMIMO-PerBand includes at least one band-specific capability information related to the first feature, and UE-CapabilityXR-PerBand includes at least one band-specific capability information related to the second feature. It should be understood that the names of the information in FIG. 9 are only examples and do not limit the naming of the information.

[0150] For example, the information element carrying the second UE capability list can be as follows:

[0151] wherein UE-CapabilityPerBandFeatureList is the second UE capability list, which can carry at least one set of band-specific capability information related to at least one feature; UE-CapablityPerBand can carry a set of band-specific capability information related to one feature, and the set of band-specific capability information related to one feature can include band-specific capability information and its identifier; featureCapabilityId is used to identify the feature or the feature-related capability information or the feature-related band-specific capability information; and featureCapability is used to carry the feature-related capability information or the feature-related band-specific capability information indicated by featureCapabilityId. The featureCapability used to carry the capability information can be a character string, a byte string, or a bit string, and the contents included in the featureCapability corresponding to different features can be different. In the above example, featureCapabilityId and / or featureCapability can be optional fields or mandatory fields, which are not limited herein. The number of UE-CapablityPerBand included in the second UE capability list can also be 0.

[0152] As an optional solution, the second UE capability list can add or modify the reported feature-related band-specific capability information by a third list. The third list can include at least one set of band-specific capability information, and each set of band-specific capability information can include one feature-related band-specific capability information and an identifier associated with the feature. Optionally, when the third list includes an identifier that has not been reported by the terminal device or stored by the network device, it means that new feature capability information is added; when the third list includes an identifier that has been reported by the terminal device or stored by the network device, it means that the capability information of the previous feature is updated or modified.

[0153] The second UE capability list can also delete or release the feature or feature-related band-specific capability information by a fourth list. The fourth list can include at least one feature or at least one identifier associated with the feature.

[0154] Based on the above solutions, the information element carrying the second UE capability list can be as follows:

[0155] The UE-CapabilityPerBandFeatureToAddModList is the third list, which can include at least one UE-CapabilityPerBand. One UE-CapabilityPerBand can include one set of band-specific capability information, which can include an identifier associated with one feature and feature-related band-specific capability information.

[0156] The UE-CapabilityPerBandFeatureToReleaseList is the fourth list, which can include at least one identifier associated with at least one feature, indicating to delete or release the band-specific capability information related to the at least one feature.

[0157] 3. Band combination-specific capability information

[0158] Optionally, the first capability information can include at least one band combination-specific capability information of a band combination. Taking a first band combination as an example, the band combination-specific capability information of the first band combination includes one or more of a band list specific to the first band combination (bandList), CA parameters of the first band combination, MRDC parameters, power class, etc. The above example capability information can be understood as basic capability information specific to the first band combination.

[0159] Optionally, the capability information specific to the first frequency band combination can further comprise at least one characteristic related capability information specific to the first frequency band combination, and an identifier respectively associated with the at least one characteristic related capability information specific to the first frequency band combination. The identifier respectively associated with the at least one characteristic related capability information specific to the first frequency band combination can be understood as an identifier respectively associated with the at least one characteristic related capability information specific to the first frequency band combination. Taking the first frequency band combination as an example, the capability information specific to the first frequency band combination can further comprise a first identifier and a first characteristic related capability information specific to the first frequency band combination. If there are other characteristics, such as a second characteristic, the capability information specific to the first frequency band combination can further comprise other characteristic related capability information specific to the first frequency band combination and an identifier respectively associated with the other characteristic related capability information specific to the first frequency band combination.

[0160] Optionally, the first characteristic related capability information specific to the first frequency band combination comprises a list of frequency bands included in the first frequency band combination (e.g., BandList), or comprises an index of the first frequency band combination, the index of the first frequency band combination being related to a position of the first frequency band combination in the at least one frequency band combination included in the first capability information. For example, the first capability information comprises capability information of the first frequency band combination, capability information of a second frequency band combination, and capability information of a third frequency band combination, the index of the first frequency band combination is 0 (or 1).

[0161] Optionally, the number of frequency band combinations included in the basic capability information in the first capability information is the same as the number of frequency band combinations included in the capability information related to each characteristic (e.g., the first characteristic, the second characteristic, etc.) in the first capability information. The capability information of the frequency band combination at the same position in the capability information related to each characteristic (e.g., the first characteristic) in the basic capability information corresponds to the same frequency band combination. In other words, the number and order of the capability information of the frequency band combination in the basic information is the same as the number and order of the capability information of the frequency band combination in the capability information related to each characteristic (e.g., the first characteristic).

[0162] The capability information specific to the first frequency band combination in the basic capability information and the capability information specific to the first frequency band combination related to each characteristic (e.g., the first characteristic, the second characteristic, etc.) in the first capability information are combined to form the capability information of the terminal device on the first frequency band combination. In other words, the terminal device should support the capability information specific to the first frequency band combination in the basic capability information reported by the terminal device, and the capability information specific to the first frequency band combination related to each characteristic (e.g., the first characteristic, the second characteristic, etc.) on the first frequency band combination.

[0163] In a possible implementation, the third UE capability list can be included in the capability information specific to the band combination, and the third UE capability list can include at least one characteristic related capability information specific to the band combination, and an identification associated with the at least one characteristic respectively. For example, taking the first band combination as an example, the third UE capability list can include a first identification and the first characteristic related capability information specific to the first band combination. Optionally, the third UE capability list can further include a second identification and the second characteristic related capability information specific to the first band combination, a third identification and the third characteristic related capability information specific to the first band combination, and so on.

[0164] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as shown in FIG. 10, where the third UE capability list includes an MIMO associated identification MIMO-ID, UE-CapabilityMIMO-PerBC and an XR associated identification XR-ID, UE-CapabilityXR-PerBC, the UE-CapabilityMIMO-PerBC includes the first characteristic related capability information specific to the first band combination, and the UE-CapabilityXR-PerBC includes the second characteristic related capability information specific to the first band combination. It should be understood that the names of the information in FIG. 10 are only examples, and do not limit the naming of the information.

[0165] For example, the information element carrying the third UE capability list can be as follows:

[0166] The bandCombinationFeatureList is a third UE capability list, and can carry at least one set of band combination specific capability information related to at least one feature; the UE-CapablityPerBC can carry one set of band combination specific capability information related to one feature, and the one set of band combination specific capability information related to one feature can include band combination specific capability information and an identifier thereof; the featureCapabilityId is used to identify the feature or the feature related capability information or the feature related band combination specific capability information; and the featureCapability is used to carry the feature related capability information or the feature related band combination specific capability information indicated by the featureCapabilityId. The featureCapability used to carry the capability information can be a character string, a byte string or a bit string, and the featureCapability includes different contents corresponding to different features. In the above example, the featureCapabilityId and / or the featureCapability can be optional fields or mandatory fields, which is not limited herein. The number of UE-CapablityPerBand included in the third UE capability list can also be 0.

[0167] As an optional solution, the third UE capability list can add or modify the reported feature related band combination specific capability information through a fifth list, and the fifth list can include at least one set of band combination specific capability information related to the first band combination, and each set of band combination specific capability information related to the first band combination can include one feature related band combination specific capability information and an identifier associated with the feature. Optionally, when the identifier included in the fifth list is not reported by the terminal device or stored by the network device, it means that new feature capability information is added; when the identifier included in the fifth list is reported by the terminal device or stored by the network device, it means that the capability information of the previous feature is updated or modified.

[0168] The third UE capability list can also delete or release the feature or the feature related band combination specific capability information through a sixth list, and the sixth list can include at least one feature or at least one identifier associated with the feature.

[0169] Based on the above solution, the information element carrying the third capability information can be as follows:

[0170] bandCombinationFeatureToAddModList is a fifth list, which can include at least one UE-CapabilityPerBC, and one UE-CapabilityPerBC can include a set of first band combination specific capability information, which can include an identity of a feature and the first band combination specific capability information associated with the feature.

[0171] bandCombinationFeatureToReleaseList is a sixth list, which can include at least one identity of a feature, for indicating to delete or release the first band combination specific capability information associated with the feature.

[0172] 4. Feature Set Collection

[0173] The Feature Set Collection is used to provide a pool of downlink and / or uplink feature sets. The first capability information can include a second feature set collection, and one or more features in the second feature set collection can include a capability information specific to one of the bands in the band combination. For example, the second feature set collection can be FeatureSets or featureSetsDownlink or featureSetsUplink. For example, one or more downlink features in the second feature set collection can include one or more of intraBandFreqSeparation, scalingFactor, Synchronization Signal / Physical Broadcast Channel Block (SSB) related capability (e.g., scellWithoutSSB or csi-RS-MeasSCellWithoutSSB), search space related capability (e.g., type1-3-CSS or searchSpaceSharingCA-DL), etc. For another example, one or more uplink features in the second feature set collection can include one or more of scalingFactor, intraBandFreqSeparation, search space related capability (e.g., searchSpaceSharingCA-UL), Sounding Reference Signal (SRS) related information (e.g., supportedSRS-Resources), supplementary uplink carrier related capability (e.g., dynamicSwitchSUL or simultaneousTxSUL-NonSUL), etc. The above-mentioned capability information can be understood as the basic capability information included in the second feature set collection.

[0174] Optionally, the first capability information can further comprise at least one feature set collection associated with at least one feature, and an identifier associated with the at least one feature, respectively. The identifier associated with the at least one feature can be understood as an identifier associated with the at least one feature set collection, respectively. Taking the first feature as an example, the first capability information can further comprise a first identifier and a first feature set collection associated with the first feature. The first feature set collection is used to provide a pool of downlink and / or uplink feature sets associated with the first feature. The first feature set collection comprises at least one feature set. Any feature set in the first feature set collection comprises capability information associated with the first feature on a frequency band in the frequency band combination. It can be understood that if there is another feature, for example, a second feature, the first capability information can further comprise a third feature set collection associated with the second feature, wherein the third feature set collection is used to provide a pool of downlink and / or uplink feature sets associated with the second feature. Any feature set in the third feature set collection comprises capability information associated with the second feature on a frequency band in the frequency band combination.

[0175] In one example, the number of feature sets included in different feature set collections in the first capability information is the same. For example, the number of feature sets included in the first feature set collection can be the same as the number of feature sets included in the second feature set collection. The number of feature sets included in the first feature set collection can also be the same as the number of feature sets included in a feature set collection associated with another feature, for example, the third feature set collection associated with the second feature.

[0176] The above-mentioned feature set collection (for example, the first feature set collection, the second feature set collection, etc.) can be a set of downlink feature sets (FeatureSetsDownlink) of downlink transmission capability, or a set of uplink feature sets (FeatureSetsUplink) of uplink transmission capability.

[0177] In a possible implementation, the first capability information can include at least one characteristic-related feature set collection and an identifier associated with the at least one characteristic-related feature set collection in a form of a list. Further, the downlink feature set collection and the uplink feature set collection can be carried in different lists. For example, the first capability information can include a fourth UE capability list and / or a fifth UE capability list. The fourth UE capability list can include at least one characteristic-related downlink feature set collection and an identifier associated with the at least one characteristic. For example, the fourth UE capability list can include a first identifier and a first characteristic-related downlink feature set collection. Optionally, the fourth UE capability list can further include a second identifier and a second characteristic-related downlink feature set collection, a third identifier and a third characteristic-related downlink feature set collection, and so on. The fifth UE capability list can include at least one characteristic-related uplink feature set collection and an identifier associated with the at least one characteristic. For example, the fifth UE capability list can include a first identifier and a first characteristic-related uplink feature set collection. Optionally, the fifth UE capability list can further include a second identifier and a second characteristic-related uplink feature set collection, a third identifier and a third characteristic-related uplink feature set collection, and so on.

[0178] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as shown in FIG. 11, where the downlink feature set collection and the uplink feature set collection are related to the basic capability information. MIMO-ID is the first identifier, and FeaturSetsDownlinkMIMO is the first characteristic-related downlink feature set collection. XR-ID is the second identifier, and FeaturSetsDownlinkXR is the second characteristic-related downlink feature set collection. MIMO-ID is the first identifier, and FeaturSetsUplinkMIMO is the first characteristic-related uplink feature set collection. XR-ID is the second identifier, and FeaturSetsUplinkXR is the second characteristic-related uplink feature set collection. It should be understood that the names of the information in FIG. 11 are only examples and do not limit the naming of the information.

[0179] For example, the information element carrying the fourth UE capability list can be as follows:

[0180] The featureSetsDownlinkFeatureList is a fourth UE capability list, which can carry at least one feature-related downlink feature set; the FeatureSetsDownlinkFeature can carry one feature-related downlink feature set and its identifier; the featureCapabilityId is used to identify the feature-related capability information or the feature-related feature set; the featureCapability is used to carry the feature-related capability information or the feature-related feature set indicated by the featureCapabilityId; the maxDownlinkFeatureSets is used to indicate the maximum number of downlink feature sets contained; the FeatureSetDownlinkFeature is used to carry one downlink feature set in the feature-related feature set, which includes the capability information of the terminal device on one downlink frequency band in the frequency band combination. The capability information can be a string, a byte string or a bit string. The featureCapability corresponding to different features can include different contents. In the above example, the featureCapabilityId and / or the featureCapability can be optional fields or mandatory fields, which are not limited herein.

[0181] For example, the information element carrying the fifth UE capability list can be as follows:

[0182] The featureSetsUplinkFeatureList is a fifth UE capability list, and can carry at least one feature-related uplink feature set collection; the FeatureSetsUplinkFeature can carry one feature-related uplink feature set collection and an identifier thereof; the featureCapabilityId is used to identify feature-related capability information or feature-related feature set collection capability information; the featureCapability is used to carry the feature-related capability information or feature-related feature set collection indicated by the featureCapabilityId; the maxUplinkFeatureSets is used to indicate the maximum number of included uplink feature sets; and the FeatureSetUplinkFeature is used to carry one uplink feature set in the feature-related feature set collection, which includes the capability information of the terminal device on one uplink frequency band in the frequency band combination. The capability information can be a character string, a byte string, or a bit string. The featureCapability corresponding to different features can include different contents. In the above example, the featureCapabilityId and / or the featureCapability can be optional fields or mandatory fields, which are not limited herein.

[0183] According to the foregoing technical background, the first capability information can indicate a feature set identifier corresponding to a frequency band in a frequency band combination. For example, the feature set identifier associated with each frequency band in the frequency band combination is included in the feature set combination (featureSetCombination) corresponding to the frequency band combination. In this application, the feature set identifier can indicate the feature set located at the same position in the feature set collection related to each feature (e.g., the first feature, the second feature, etc.) and the feature set collection related to the basic capability information supported by the terminal device on the corresponding frequency band in the frequency band combination. For example, the feature set identifier associated with the second frequency band in the second frequency band combination can indicate the feature set located at the same position in the feature set collection related to the first feature and the feature set collection related to the basic capability information supported on the second frequency band in the second frequency band combination. For example, if the feature set identifier is 1, it indicates that the first feature set in the feature set collection related to the first feature and the first feature set in the feature set collection related to the basic capability information are supported. If there are other features, the feature set identifier associated with the second frequency band in the second frequency band combination can indicate the feature set located at the same position in the feature set collection related to the other features supported on the second frequency band in the second frequency band combination.

[0184] Specifically, the downlink feature set identifier associated with the second frequency band in the second frequency band combination can indicate that the same position feature set in the first characteristic related downlink feature set collection and the basic capability information related downlink feature set collection is supported on the second frequency band in the second frequency band combination. If there are other characteristics, the downlink feature set identifier associated with the second frequency band in the second frequency band combination can indicate that the downlink feature set in the same position in the other characteristic related downlink feature set collection is supported on the second frequency band in the second frequency band combination. The uplink feature set identifier associated with the second frequency band in the second frequency band combination can indicate that the same position feature set in the first characteristic related uplink feature set collection and the basic capability information related uplink feature set collection is supported on the second frequency band in the second frequency band combination. If there are other characteristics, the uplink feature set identifier associated with the second frequency band in the second frequency band combination can indicate that the uplink feature set in the same position in the other characteristic related uplink feature set collection is supported on the second frequency band in the second frequency band combination. Here, whether the terminal device supports the feature set in the other characteristic related feature set collection depends on whether the terminal device supports the other characteristic.

[0185] Taking FIG. 11 as an example, assuming that the first downlink feature set identifier and the first uplink feature set identifier associated with the second frequency band in the second frequency band combination, the first downlink feature set identifier indicates the second downlink feature set in the downlink feature set collection, and the first uplink feature set identifier indicates the first uplink feature set in the uplink feature set collection, the terminal device supports the second downlink feature set in the first characteristic related downlink feature set collection and the second downlink feature set in the basic capability information related downlink feature set collection on the second frequency band in the second frequency band combination in the downlink transmission direction, and optionally, if there are other characteristics, can also support the second downlink feature set in the other characteristic related downlink feature set collection, and supports the first uplink feature set in the first characteristic related uplink feature set collection and the first uplink feature set in the basic capability information related uplink feature set collection on the second frequency band in the second frequency band combination in the uplink transmission direction, and optionally, if there are other characteristics, can also support the first uplink feature set in the other characteristic related uplink feature set collection. As shown in FIG. 12, see the connection line in the figure.

[0186] 5、Carrier feature set collection

[0187] The carrier feature set collection is used to provide a pool of uplink and / or downlink carrier feature sets. Included in a carrier feature set is capability information of a terminal device on one carrier of the feature set. The first capability information can include a second carrier feature set collection, and one or more carrier feature sets in the second carrier feature set collection can include capability information of one carrier on a band in a band combination. For example, the second carrier feature set collection can be featureSetsDownlinkPerCC or featureSetsUplinkPerCC. For example, one or more downlink carrier feature sets in the second carrier feature set collection can include one or more of a subcarrier spacing (supportedSubcarrierSpacingDL), a bandwidth (supportedBandwidthDL), a number of MIMO layers (maxNumberMIMO-LayersPDSCH), a modulation order (supportedModulationOrderDL), etc. of the carrier. For another example, one or more uplink carrier feature sets in the second carrier feature set collection can include one or more of a subcarrier spacing (supportedSubcarrierSpacingUL), a bandwidth (supportedBandwidthUL), a MIMO related capability (e.g., maxNumberMIMO-LayersCB-PUSCH or maxNumberSRS-ResourcePerSet), a modulation order (supportedModulationOrderUL), etc. of the carrier. The above-mentioned example capability information can be understood as basic capability included in the second feature set collection.

[0188] Optionally, the first capability information can further comprise at least one set of carrier feature sets associated with a feature and at least one identifier associated with the at least one feature respectively. The at least one identifier associated with the at least one feature can be understood as at least one identifier associated with the at least one set of carrier feature sets associated with the at least one feature respectively. Taking a first feature as an example, the first capability information can further comprise a first identifier and a first set of carrier feature sets associated with the first feature, the first set of carrier feature sets being configured to provide a pool of downlink and / or uplink carrier feature sets associated with the first feature. The first set of carrier feature sets comprises at least one carrier feature set. Any carrier feature set in the first set of carrier feature sets comprises capability information associated with the first feature on a carrier of a frequency band in the frequency band combination or comprises capability information associated with the first feature on one carrier in one feature set. It can be understood that if there is another feature, for example, a second feature, the first capability information can further comprise a third set of carrier feature sets associated with the second feature, wherein the third set of carrier feature sets is configured to provide a pool of downlink and / or uplink carrier feature sets associated with the second feature. Any carrier feature set in the third set of carrier feature sets comprises capability information associated with the second feature on a carrier of a frequency band in the frequency band combination.

[0189] In one example, the number of carrier feature sets included in different sets of carrier feature sets in the first capability information is the same. For example, the number of carrier feature sets included in the first set of carrier feature sets can be the same as the number of carrier feature sets included in the second set of carrier feature sets. The number of carrier feature sets included in the first set of carrier feature sets can also be the same as the number of carrier feature sets included in a set of carrier feature sets associated with another feature, for example, the third set of carrier feature sets associated with the second feature.

[0190] The above-mentioned carrier feature sets (for example, the first set of carrier feature sets, the second set of carrier feature sets, etc.) can be a set of downlink carrier feature sets (i.e., FeatureSetDownlinkPerCC) of downlink transmission capability or a set of uplink carrier feature sets (i.e., FeatureSetUplinkPerCC) of uplink transmission capability.

[0191] In a possible implementation, the first capability information can include at least one set of feature sets related to a characteristic and an identifier associated with the at least one set of feature sets related to the characteristic respectively in a form of a list. Further, the set of downlink carrier feature sets and the set of uplink carrier feature sets can be carried by different lists. For example, the first capability information can include a sixth UE capability list and / or a seventh UE capability list. The sixth UE capability list can include at least one set of downlink carrier feature sets related to a characteristic and an identifier associated with the at least one set of downlink carrier feature sets related to the characteristic respectively. For example, the sixth UE capability list can include a first identifier and a set of downlink carrier feature sets related to a first characteristic, and further include a second identifier and a set of downlink carrier feature sets related to a second characteristic, a third identifier and a set of downlink carrier feature sets related to a third characteristic, and so on. The seventh UE capability list can include at least one set of uplink carrier feature sets related to a characteristic and an identifier associated with the at least one set of uplink carrier feature sets related to the characteristic respectively. For example, the seventh UE capability list can include a first identifier and a set of uplink carrier feature sets related to a first characteristic, and further include a second identifier and a set of uplink carrier feature sets related to a second characteristic, a third identifier and a set of uplink carrier feature sets related to a third characteristic, and so on.

[0192] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as shown in FIG. 13, in which the set of downlink carrier feature sets and the set of uplink carrier feature sets are related to the basic capability information. MIMO-ID is the first identifier, FeaturSetsDownlinkPerCC-MIMO is the set of downlink carrier feature sets related to the first characteristic, XR-ID is the second identifier, and FeaturSetsDownlinkPerCC-XR is the set of downlink carrier feature sets related to the second characteristic. MIMO-ID is the first identifier, FeaturSetsUplinkPerCC-MIMO is the set of uplink carrier feature sets related to the first characteristic, XR-ID is the second identifier, and FeaturSetsUplinkPerCC-XR is the set of uplink carrier feature sets related to the second characteristic. It should be understood that the names of the information in FIG. 13 are only examples and do not limit the naming of the information.

[0193] For example, the information element carrying the sixth UE capability list can be as follows:

[0194] The featureSetsDownlinkPerCC-FeatureList is a sixth UE capability list, which can carry at least one feature-related downlink carrier feature set collection; the FeatureSetDownlinkPerCC-Feature can carry one feature-related downlink carrier feature set collection and its identifier; the featureCapabilityId is used to identify feature-related capability information or feature-related carrier feature set collection capability information; the featureCapability is used to carry the feature-related capability information or feature-related carrier feature set collection indicated by the featureCapabilityId; the maxPerCC-FeatureSets is used to indicate the maximum number of included carrier feature sets; the FeatureSetDownlinkPerCC-Feature is used to carry one downlink carrier feature set in the feature-related feature set collection, which includes the capability information of the terminal device on one downlink band in the band combination. The capability information can be a character string, a byte string or a bit string. The featureCapability corresponding to different features can include different contents. In the above example, the featureCapabilityId and / or the featureCapability can be optional fields or mandatory fields, which are not limited herein.

[0195] For example, the information element carrying the seventh UE capability list can be as follows:

[0196] The featureSetsUplinkPerCC-FeatureList is a seventh UE capability list, and can carry at least one feature-related uplink carrier feature set collection; the FeatureSetsUplinkPerCC-Feature can carry one feature-related uplink carrier feature set collection and an identifier thereof; the featureCapabilityId is used to identify feature-related capability information or capability information of the feature-related carrier feature set collection; the featureCapability is used to carry the feature-related capability information or the feature-related carrier feature set collection indicated by the featureCapabilityId; the maxPerCC-FeatureSets is used to indicate the maximum number of included carrier feature sets; and the FeatureSetUplinkPerCC-Feature is used to carry one uplink carrier feature set in the feature-related feature set collection, which includes capability information of the terminal device on one uplink band in the band combination. The capability information can be a character string, a byte string or a bit string, and the featureCapability corresponding to different features can include different contents. In the above example, the featureCapabilityId and / or the featureCapability can be optional fields or mandatory fields, which are not limited herein.

[0197] According to the foregoing technical background, the first capability information can indicate a carrier feature set identifier corresponding to a carrier of a band in the band combination. For example, the carrier feature set identifier corresponding to the band in the band combination includes the carrier feature set identifier associated with each carrier in the band. In this application, the carrier feature set identifier can indicate that the terminal device supports the carrier feature set at the same position in the first feature-related carrier feature set collection and the basic capability information-related carrier feature set collection on the carrier corresponding to the band in the band combination. For example, the carrier feature set identifier associated with the third band in the third band combination can indicate that the first feature-related carrier feature set collection and the basic capability information-related carrier feature set collection at the same position are supported on the carrier corresponding to the third band in the third band combination. For example, if the carrier feature set identifier is 1, it indicates that the first carrier feature set in the first feature-related carrier feature set collection and the first carrier feature set in the basic capability information-related carrier feature set collection are supported. Optionally, if there are other features, the carrier feature set at the same position in the other feature-related carrier feature set collection can also be supported.

[0198] Specifically, the first carrier of the third frequency band in the third frequency band combination is associated with the first downlink carrier feature set identifier, which indicates the same downlink carrier feature set in the first feature related downlink carrier feature set collection and the basic capability information related downlink carrier feature set collection. Optionally, if there are other features, the same downlink carrier feature set in the other feature related downlink carrier feature set collection can also be supported. The third frequency band in the third frequency band combination is associated with the uplink feature set identifier, which indicates the same uplink carrier feature set in the first feature related uplink carrier feature set collection and the basic capability information related uplink carrier feature set collection. Optionally, if there are other features, the same uplink carrier feature set in the other feature related uplink carrier feature set collection can also be supported.

[0199] Taking FIG. 13 as an example, assuming that the first carrier of the third frequency band in the third frequency band combination is associated with the first downlink carrier feature set identifier and the first uplink carrier feature set identifier, the first downlink carrier feature set identifier indicates the first downlink carrier feature set in the downlink carrier feature set collection, and the first uplink carrier feature set identifier indicates the second uplink carrier feature set in the uplink carrier feature set collection, the terminal device supports the first downlink carrier feature set in the first feature related downlink carrier feature set collection and the first downlink carrier feature set in the basic capability information related downlink carrier feature set collection in the downlink transmission direction of the first carrier of the third frequency band in the third frequency band combination. Optionally, if there are other features, the first downlink carrier feature set in the other feature related downlink carrier feature set collection can also be supported, and the second uplink carrier feature set in the first feature related uplink carrier feature set collection and the second uplink carrier feature set in the basic capability information related uplink carrier feature set collection can be supported in the uplink transmission direction. As shown in FIG. 14, see the connection line in the figure.

[0200] The second structure: including the information element carrying at least one feature related capability information and the information element carrying the basic capability information in the first capability information. Wherein, the information element where one feature related capability information is located can include one identifier associated with the feature and the capability information specific to each level of the feature. In this structure, it is not necessary to repeatedly include the feature related identifier in each level.

[0201] For example, taking the first characteristic as an example, the first capability information includes first information related to the first characteristic, and the first information includes the first identifier and capability information of each level related to the first characteristic. That is, the first information includes the first identifier and at least one of the following: terminal device-specific capability information related to the first characteristic, frequency band-specific capability information related to the first characteristic, frequency band combination-specific capability information related to the first characteristic, a first feature set collection, or a first carrier feature set collection. Wherein, any one feature set in the first feature set collection includes capability information related to the first characteristic on a frequency band in a frequency band combination. Any one carrier feature set in the first carrier feature set collection includes capability information related to the first characteristic on a carrier in the feature set. Optionally, the first capability information can also include third information related to the second characteristic, etc.

[0202] Optionally, the first capability information can also include second information, and the second information can include basic capability information. The second information can include basic capability information of each level, such as terminal device-specific basic capability information (such as access layer version information of the terminal device, PDCP layer capability, etc., for details, see the above description), frequency band-specific basic capability information (such as extended CP of the frequency band, modulation mode, power level, MIMO capability, etc., for details, see the above description), frequency band combination-specific basic capability information (such as carrier aggregation capability of the frequency band combination, dual connection (DC) capability, power level, etc., for details, see the above description), a second feature set collection, or a second carrier feature set collection. Wherein, any one feature set in the second feature set collection includes basic capability information on a frequency band in a frequency band combination, such as intraBandFreqSeparation, scalingFactor, scellWithoutSSB of the frequency band, etc., for details, see the above description. Any one carrier feature set in the second carrier feature set collection includes basic capability information on a carrier in the feature set, such as subcarrier spacing, bandwidth, etc., of the carrier, for details, see the above description.

[0203] The above-mentioned feature set collection (such as the first feature set collection, the second feature set collection, etc.) can be a downlink feature set collection (FeatureSetsDownlink) of downlink transmission capability, or an uplink feature set collection (FeatureSetsUplink) of uplink transmission capability. The above-mentioned carrier feature set (such as the first carrier feature set collection, the second carrier feature set collection, etc.) can be a downlink carrier feature set (FeatureSetDownlinkPerCC) of downlink transmission capability, or an uplink carrier feature set (FeatureSetUplinkPerCC) of uplink transmission capability.

[0204] Optionally, the capability information related to each feature can be carried in the same list, such as the eighth UE capability list. For example, taking the first feature as MIMO and the second feature as XR, the first capability information can be as shown in FIG. 15. In FIG. 15, MIMO-ID is the first identifier, and the MIMO-related UE capability (UE-CapabilityForMIMO) includes the capability information related to each level of MIMO. XR-ID is the second identifier, and the XR-related UE capability (UE-CapabilityForXR) includes the capability information related to each level of XR. Optionally, the XR-related UE capability has a similar level structure as the MIMO-related UE capability. It should be understood that the names of the information in FIG. 15 are only examples and do not limit the naming of the information.

[0205] It should be noted that the MIMO-ID can be outside the MIMO-related UE capability (UE-CapabilityForMIMO), and the XR-ID can be outside the XR-related UE capability (UE-CapabilityForXR), as shown in FIG. 15. Alternatively, the MIMO-ID can be in the MIMO-related UE capability (UE-CapabilityForMIMO), and the XR-ID can be in the XR-related UE capability (UE-CapabilityForXR), which is not specifically limited here.

[0206] Although the capability information related to each feature and the basic capability information are decoupled at the IE level, the information in the capability information related to each feature and the information in the basic capability information are associated.

[0207] For example, the capability information related to each feature and the capability information specific to the terminal device in the basic capability information are associated. In other words, the terminal device supports the capability information specific to the terminal device in the capability information related to each feature and the basic capability information specific to the terminal device. For example, taking the first feature, the terminal device supports the capability information specific to the terminal device in the capability information related to the first feature and the basic capability information specific to the terminal device.

[0208] For another example, the capability information related to each feature and the capability information specific to the frequency band in the basic capability information are associated. For example, the capability information related to each feature and the capability information specific to the first frequency band in the basic capability information are associated. In other words, the terminal device supports the capability information specific to the first frequency band in the capability information related to each feature and the basic capability information specific to the first frequency band on the first frequency band. For example, taking the first feature, the terminal device supports the capability information specific to the first frequency band in the capability information related to the first feature and the basic capability information specific to the first frequency band on the first frequency band.

[0209] For another example, each feature set associated with a feature group in the base capability information is associated with a feature set associated with a feature group in the capability information of each feature. For example, each feature set associated with a feature group in the base capability information is associated with a feature set associated with a feature group in the capability information of the first feature. In other words, the terminal device supports each feature set associated with a feature group in the base capability information and a feature set associated with a feature group in the capability information of the first feature. For example, the terminal device supports each feature set associated with a feature group in the base capability information and a feature set associated with a feature group in the capability information of the first feature.

[0210] For another example, each feature set associated with a feature group in the base capability information is associated with a feature set associated with a feature group in the capability information of each feature. For example, each feature set associated with a feature group in the base capability information is associated with a feature set associated with a feature group in the capability information of the first feature. In other words, the terminal device supports each feature set associated with a feature group in the base capability information and a feature set associated with a feature group in the capability information of the first feature. For example, the terminal device supports each feature set associated with a feature group in the base capability information and a feature set associated with a feature group in the capability information of the first feature.

[0211] For another example, each feature set associated with a feature group in the base capability information is associated with a feature set associated with a feature group in the capability information of each feature. For example, each feature set associated with a feature group in the base capability information is associated with a feature set associated with a feature group in the capability information of the first feature. In other words, the terminal device supports each feature set associated with a feature group in the base capability information and a feature set associated with a feature group in the capability information of the first feature. For example, the terminal device supports each feature set associated with a feature group in the base capability information and a feature set associated with a feature group in the capability information of the first feature.

[0212] The following takes the first information and the second information as an example to introduce the scheme of making the information in the first information and the information in the second information exist in the correlation.

[0213] For the capability information specific to the first frequency band:

[0214] In one possible mode, the capability information specific to the first frequency band in the first information and the capability information specific to the first frequency band in the second information can include the same frequency band identifier.

[0215] In another possible mode, the position of the first frequency band in the at least one frequency band included in the first information is the same as the position of the first frequency band in the at least one frequency band included in the second information. Optionally, the number of frequency bands of the capability information specific to the frequency band included in the first information is the same as the number of frequency bands of the capability information specific to the frequency band included in the second information.

[0216] In still another possible mode, the capability information specific to the first frequency band in the first information can include an index of the first frequency band, and the index of the first frequency band is related to the position of the first frequency band in the at least one frequency band included in the second information. For example, the first information includes the capability information specific to the first frequency band, the capability information specific to the second frequency band and the capability information specific to the third frequency band, and the index of the first frequency band is 0 (or 1).

[0217] For the capability information specific to the first frequency band combination:

[0218] In one possible mode, the capability information specific to the first frequency band combination in the first information includes a frequency band list, and the frequency band list indicates the frequency bands included in the first frequency band combination. It can be understood that the capability information specific to the first frequency band combination in the first information and the capability information specific to the first frequency band combination in the second information can include the same frequency band list.

[0219] In another possible mode, the position of the capability information specific to the first frequency band combination related to the first characteristic in the second information is the same as the position of the capability information specific to the first frequency band combination related to the first characteristic in the first information. Optionally, the number of frequency band combinations of the capability information specific to the frequency band combination included in the first information is the same as the number of frequency band combinations of the capability information specific to the frequency band combination included in the second information.

[0220] In still another possible mode, the capability information specific to the first frequency band combination related to the first characteristic includes a first index, and the value of the first index is related to the position of the capability information specific to the first frequency band combination in the second information. For example, the first information includes the capability information specific to the first frequency band combination, the capability information specific to the second frequency band combination and the capability information specific to the third frequency band combination, and the index of the first frequency band is 0 (or 1).

[0221] For the feature set corresponding to the second frequency band in the second frequency band combination in the second information:

[0222] In one possible manner, the position of the first feature set in the feature set corresponding to the second frequency band in the second frequency band combination in the first information is the same as the position of the second feature set in the feature set corresponding to the second frequency band in the second frequency band combination in the second information. Optionally, the number of the feature set corresponding to the second frequency band in the second frequency band combination in the first information is the same as the number of the feature set corresponding to the second frequency band in the second frequency band combination in the second information. The terminal device supports the feature set in the same position corresponding to the frequency band in the second frequency band combination in the first information, and the feature set in the same position corresponding to the frequency band in the second frequency band combination in the second information.

[0223] For example, taking the frequency band combination 1 as an example, the frequency band combination 1 includes the frequency band 1 and the frequency band 2, as shown in FIG. 16, the feature sets connected by the dashed line have the association relationship. As can be seen from FIG. 16, in the feature set combination set (second information) in the first capability information, the number of the feature set of the frequency band included in each feature set combination is the same as the number of the feature set of the frequency band included in each feature set combination in the same position in the feature set combination set (first information) in the MIMO related UE capability in the eighth UE capability list. For example, the number of the feature set of the frequency band included in the frequency band combination 1 in two positions in FIG. 16 is 2 (i.e., the feature set of the frequency band 1 and the feature set of the frequency band 2). The terminal device can support the feature set in the same position of the frequency band 1 and the frequency band 2 in the two feature set combinations on the frequency band combination 1. That is, one of the capabilities supported by the terminal device on the frequency band combination 1 is to support the first feature set associated with the frequency band 1 of the frequency band combination 1 in the basic capability information and the first feature set associated with the frequency band 1 of the frequency band combination 1 in the MIMO related UE capability information on the frequency band 1 of the frequency band combination 1, and support the first feature set associated with the frequency band 2 of the frequency band combination 1 in the basic capability information and the first feature set associated with the frequency band 2 of the frequency band combination 1 in the MIMO related UE capability information on the frequency band 2 of the frequency band combination 1. Another capability supported by the terminal device on the frequency band combination 1 is to support the second feature set associated with the frequency band 1 of the frequency band combination 1 in the basic capability information and the second feature set associated with the frequency band 1 of the frequency band combination 1 in the MIMO related UE capability information on the frequency band 1 of the frequency band combination 1, and support the second feature set associated with the frequency band 2 of the frequency band combination 1 in the basic capability information and the second feature set associated with the frequency band 2 of the frequency band combination 1 in the MIMO related UE capability information on the frequency band 2 of the frequency band combination 1.

[0224] Another association manner is that the first feature set is associated with the second index, and the value of the second index is related to the position of the feature set corresponding to the second frequency band pair in the second frequency band combination in the second information. The terminal device supports the feature set corresponding to the frequency band in the second frequency band combination in the first information and the feature set corresponding to the same index of the frequency band in the second frequency band combination in the second information. For example, taking the frequency band combination 1 as an example, the frequency band combination 1 includes the frequency band 1 and the frequency band 2, as shown in FIG. 17. It is assumed that the index 0 represents the first feature set, the index 1 represents the second feature set, the index 2 represents the third feature set, and so on. As can be seen from FIG. 17, the first feature set associated with the frequency band 1 of the frequency band combination 1 in the MIMO-related UE capability information includes the index 1, and the second feature set includes the index 0. The first feature set associated with the frequency band 2 of the frequency band combination 1 includes the index 1, and the second feature set includes the index 0. Therefore, one of the capabilities supported by the terminal device on the frequency band combination 1 is that the terminal device supports the first feature set associated with the frequency band 1 of the frequency band combination 1 in the basic capability information and the second feature set associated with the frequency band 1 of the frequency band combination 1 in the MIMO-related UE capability information on the frequency band 1 of the frequency band combination 1, and supports the first feature set associated with the frequency band 2 of the frequency band combination 1 in the basic capability information and the second feature set associated with the frequency band 2 of the frequency band combination 1 in the MIMO-related UE capability information on the frequency band 2 of the frequency band combination 1. Another capability supported by the terminal device on the frequency band combination 1 is that the terminal device supports the second feature set associated with the frequency band 1 of the frequency band combination 1 in the basic capability information and the first feature set associated with the frequency band 1 of the frequency band combination 1 in the MIMO-related UE capability information on the frequency band 1 of the frequency band combination 1, and supports the second feature set associated with the frequency band 2 of the frequency band combination 1 in the basic capability information and the first feature set associated with the frequency band 2 of the frequency band combination 1 in the MIMO-related UE capability information on the frequency band 2 of the frequency band combination 1.

[0225] The above introduces two structures of the capability information.

[0226] In some scenarios, the terminal device can update the capability information to the network device. Optionally, if the basic capability information of the terminal device does not change, and the terminal device only increases or modifies the feature-related capability when updating the capability information, the terminal device can report the feature-related capability information without reporting the basic capability information. For example, the terminal device can send the second capability information of the terminal device, and the second capability information includes the first indication information, and the first indication information is used to indicate the maintenance or release or addition of the capability information of the first feature. Optionally, the second capability information can not include the basic capability information.

[0227] Taking the first structure above as an example, the second capability information can include the first UE capability list to the seventh UE capability list. The signaling structure of the first UE capability list to the seventh UE capability list can refer to the related description in the first structure above, which will not be repeated here.

[0228] Taking the second structure as an example, the second capability information can include the first information and the capability information related to the characteristics, and does not include the second information.

[0229] For example, in a scenario where the terminal device updates the capability information by adding or modifying the capability related to the characteristics, the basic capability information of the terminal device does not change, and the terminal device newly opens a characteristic or closes a characteristic in the connected state. In this case, the basic capability information can not change.

[0230] As an optional manner, in the above updating scheme, the terminal device can further indicate to the network device that the basic capability information of the terminal device does not change or remains unchanged.

[0231] It should be noted that some hierarchical capability information is omitted in FIGS. 8-17, for example, in FIG. 8, the information included in the supported frequency band list, the supported BC list, the feature set combination, the downlink feature set set and the like is omitted, in FIG. 9, the information included in the supported BC list, the feature set combination, the downlink feature set set and the like is omitted, in FIG. 10, the information included in the supported frequency band list, the feature set combination, the downlink feature set set and the like is omitted, in FIG. 11, the information included in the supported frequency band list, the supported BC list, the feature set combination, the downlink feature set set and the like is omitted, in FIG. 12, the information included in the terminal device specific capability information, the supported frequency band list, the supported BC list, the downlink feature set set and the like is omitted, in FIG. 13, the information included in the supported frequency band list, the supported BC list, the feature set combination, the downlink feature set set and the like is omitted, in FIG. 14, the information included in the terminal device specific capability information, the supported frequency band list, the supported BC list, the downlink feature set set and the like is omitted, in FIG. 15, the information included in the downlink feature set set, the uplink feature set set, the downlink carrier feature set set, the uplink carrier feature set set and the like is omitted, in FIG. 16 and FIG. 17, the information included in the terminal device specific capability information, the supported frequency band list, the supported BC list, the downlink feature set set and the like is omitted, and the specific omitted content can be referred to the capability information shown in FIG. 4. In addition, FIGS. 8-11 and 13 are combined with each other.

[0232] In addition, the information in FIGS. 8-17 is only an example, and in specific implementation, the capability information can include information other than the illustration, or include part of the information in the illustration, and the like.

[0233] The reporting of the newly added features can only determine the data structure for encoding the capability information of the terminal device after all the features discussed in the 3GPP protocol version are finalized, and in the data structure, the positions (or the reporting order) of the capability information of each feature in the capability information of the terminal device are fixed. In the present application, by including the identifier corresponding to the capability information of the feature in the capability information of the terminal device, the capability information of each feature can be isolated from the basic capability information of the terminal device, and the capability information of each feature is also independent of each other, realizing the decoupling of the reporting order (or the reporting position), so that the present application can flexibly add the capability information of a new feature in the capability information of the terminal device through the identifier. Compared with the way of reporting the capability information of each feature in a fixed order (or a fixed position), the present application can develop a feature in advance without waiting for other features to be finalized, so as to adapt to the product release rhythm and market rhythm.

[0234] Moreover, through the scheme of the present application, the positions (or the reporting order) of the capability information of each feature in the capability information of the terminal device are not fixed, so for the features not supported, the capability information of the terminal device can be trimmed to remove these features, thereby reducing the capability reporting overhead of the terminal device.

[0235] Based on the same inventive concept as the method embodiment, the present application embodiment provides a communication apparatus, the structure of which can be as shown in FIG. 18, including a communication unit 1601 and a processing unit 1602.

[0236] In an implementation manner, the communication apparatus can be specifically used for implementing the method performed by the terminal device in the embodiment of FIG. 7, and the apparatus can be the terminal device itself, or a chip or chip set or part of a chip in the terminal device for executing the related method functions. The processing unit 1602 is configured to receive a capability query message through the communication unit 1601, and send the first capability information of the terminal device. The first capability information includes a first identifier and first feature-related capability information, and the first identifier is used for identifying the first feature or the first feature-related capability information.

[0237] In an implementation manner, the communication apparatus can be specifically used for implementing the method performed by the network device in the embodiment of FIG. 7, and the apparatus can be the network device itself, or a chip or chip set or part of a chip in the network device for executing the related method functions. The processing unit 1602 is configured to send a capability query message through the communication unit 1601, and receive the first capability information of the terminal device. The first capability information includes a first identifier and first feature-related capability information, and the first identifier is used for identifying the first feature or the first feature-related capability information.

[0238] The division of the modules in the embodiments of the present application is illustrative, and is merely a logical function division. In actual implementation, another division manner can be used. In addition, each function module in each embodiment of the present application can be integrated in one processor, or can be physically separated, or two or more modules can be integrated in one module. The integrated module can be realized in the form of hardware or in the form of a software function module. It can be understood that the functions or implementation of each module in the embodiments of the present application can be further referred to the related description of the method embodiments.

[0239] In a possible manner, a communication device can be as shown in FIG. 19. The device can be a communication device or a chip in a communication device. The communication device can be a terminal device in the above embodiments or a network device in the above embodiments. The device includes a processor 1701 and a communication interface 1702, and can further include a memory 1703. The processing unit 1602 can be the processor 1701. The communication unit 1601 can be the communication interface 1702. Optionally, the processor 1701 and the memory 1703 can be integrated together.

[0240] The processor 1701 can be a CPU or a digital processing unit, etc. The communication interface 1702 can be a transceiver, an interface circuit such as a transceiver circuit, a transceiver chip, etc. The device further includes a memory 1703 for storing programs executed by the processor 1701. The memory 1703 can be a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and can also be a volatile memory such as a random-access memory (RAM). The memory 1703 can be any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but is not limited to this.

[0241] The processor 1701 is configured to execute program codes stored in the memory 1703, and is specifically configured to execute the actions of the processing unit 1602. Details are not described herein again. The communication interface 1702 is specifically configured to execute the actions of the communication unit 1601. Details are not described herein again.

[0242] The specific connection medium between the communication interface 1702, the processor 1701 and the memory 1703 in the embodiments of the present application is not limited. In FIG. 19, the memory 1703, the processor 1701 and the communication interface 1702 are connected through a bus 1704, which is represented by a thick line in FIG. 19. The connection mode between other components is only illustrative and is not limited. The bus can be divided into an address bus, a data bus, a control bus and the like. For convenience of representation, only one thick line is used in FIG. 19, but it does not mean that there is only one bus or only one type of bus.

[0243] The embodiments of the present application also provide a computer readable storage medium for storing computer software instructions required for the processor to execute the above-mentioned processes, which contains programs required for the processor to execute the above-mentioned processes.

[0244] The embodiments of the present application also provide a communication system, which includes a communication device for realizing the transmitter function in the embodiment of FIG. 7 and a communication device for realizing the receiver function in the embodiment of FIG. 7.

[0245] The above-mentioned embodiments are applicable to the scenario that the terminal device reports the capability information of the terminal device to the network device. Based on the same inventive concept as the method embodiments, the embodiments of the present application provide another communication method and device, which are applicable to the scenario that the network device sends a configuration to the terminal device.

[0246] As described above, with the continuous development of wireless communication technology, multiple versions of wireless communication technology protocols are introduced. Generally, more new features are introduced in the lower version than in the upper version, for example, R16 introduces more new features than R15. The new features are also relative. The so-called "new" is relative to the upper version, for example, R16 introduces "Ultra-reliable and low latency communications (URLLC) features" compared with R15; R17 introduces "Redcap", "sidelink enhancement", "mobility enhancement" and other features compared with R16.

[0247] With the evolution of communication protocol versions and the introduction of various new features, the radio resource control protocol in the 3GPP protocol will also be expanded accordingly. At present, the RRC protocol is expanded according to the version, and each version contains extended parameters of different features. The coupling between different features is serious, and the complexity of feature implementation is high. Specifically embodied in:

[0248] 1. The configurations related to different features are coupled with each other. The terminal device cannot completely cut off the configurations related to the unsupported features, but still needs to interpret the related configurations, occupy memory and improve the implementation complexity.

[0249] 2. Different feature related configurations are coupled with each other, and the terminal cannot implement the features in advance, but needs to wait until all feature configurations in the version are determined. The specific reasons can be referred to the description in the previous embodiment.

[0250] To solve the above problems, for different feature configuration parameters, the feature related configuration parameters can be encapsulated together, and the configuration parameters of different features are distinguished by the identifier corresponding to the feature. For example, the configuration parameters related to the first feature can be contained in a specific first information, and identified by a first identifier. In the embodiments of the present application, the parameters newly added in each version are isolated and designed according to the features. Compared with extending the RRC protocol according to the version, encapsulating the related parameters of the features together can isolate the features, so that complete pruning based on the features can be realized. For example, without implementing the features of R16 extension, the features of R17 extension can be directly implemented. For another example, when implementing a feature in R17 version, all parameters before the feature in R17 version do not need to be parsed, or in other words, any other feature in R17 version does not need to be implemented. Compared with extending the RRC protocol according to the version, the complexity of implementing a feature or some features is lower. And because the features in the same / different versions are isolated, for each version, the development for a specific feature can be carried out without waiting for all features to be stable and the protocol to be sealed, which can shorten the development cycle.

[0251] Specifically, the network device can send a second message, and correspondingly, the terminal device can receive the second message. The second message can include parameters configured for the terminal device, and the terminal device can work based on the configured parameters, for example, the terminal device can perform uplink and downlink data transmission or uplink and downlink signaling transmission or measurement according to the configuration. For example, the second message can include one or more of radio bearer configuration, measurement configuration, primary cell group configuration, secondary cell group configuration, sidelink configuration, serving cell configuration, or BWP configuration. For each configuration, the second message can include one or more, and each configuration includes at least one parameter or at least one parameter. The configuration parameters in the above examples can be understood as basic configuration parameters.

[0252] The RRC configuration parameters can include configuration parameters of different levels. For example, the RRC reconfiguration message can include parameters for the UE, such as a radio bearer configuration. Of course, the parameters for the UE can also include other possible parameters, such as a measurement configuration, and the like. The radio bearer configuration can include parameters of one or more signalling radio bearers (SRBs), data radio bearers (DRBs). The RRC reconfiguration message can also include cell group related parameters, which can include a master cell group related configuration and a secondary cell group related configuration. Each cell group related configuration can include configuration of one or more RLC bearers, a MAC related configuration, one or more buffer status report (BSR) configurations, a PHY configuration, and configuration of one or more serving cells, and the like. The configuration of one or more serving cells can include a master cell configuration or a secondary cell configuration. The serving cell configuration can also include configuration of one or more BWPs. The configuration of each BWP can also include configuration of one or more channels. The one or more channels can be a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical downlink control channel (PUCCH), a physical downlink shared channel (PUSCH), and the like. The RRC reconfiguration message can also include other configurations, which are not described in detail herein. In the embodiments of the present application, the different configurations described above (such as the radio bearer related configuration, the RLC bearer related configuration, the BSR related configuration, the serving cell related configuration, the BWP related configuration, the channel related configuration, and the like) are referred to as configuration parameters of different levels (or levels, ranks). The level related configuration can also include new levels added in the future, in addition to the above-mentioned related classification methods. In the following description, the parameters of different levels are described by taking the cell group, the serving cell, the BWP, or the channel as an example.

[0253] The embodiments of the present application do not limit the specific name of the second message. For example, the second message can be an RRC reconfiguration message, an RRC resume message, an RRC reestablishment message, an RRC connection setup message, a system information (SI) message, and the like.

[0254] The second message can also include a feature configuration list including a first configuration identity and first configuration parameters, wherein the first configuration parameters include first feature related configuration parameters, and the first configuration identity is used to identify the first feature or the first information. Optionally, in order to represent the correspondence between the configuration parameters in the feature configuration list and the basic configuration parameters, the configuration parameters of a certain level related to the feature in the feature configuration list can be contained in the corresponding level of the information element definition of the basic configuration parameters. The terminal device uses the configuration parameters of a certain level related to the feature in the feature configuration list and the configuration parameters of the level in the basic configuration parameters together, for example, as the complete configuration of the level. For example, a second configuration parameter specific to BWP is added / extended in the first feature, and the second configuration parameter specific to BWP can be included in the BWP information element definition (such as BWP or BWP-Uplink or BWP-UplinkCommon or BWP-UplinkDedicated or BWP-Downlink or BWP-DownlinkCommon or BWP-UplinkDedicated, etc.) in the basic configuration parameters; for another example, a third configuration parameter specific to a serving cell is added / extended in the second feature, and the third configuration parameter specific to the serving cell can be included in the serving cell information element definition (such as ServingCellConfig or ServingCellConfigCommon or ServingCellConfigCommonSIB, etc.) in the basic configuration parameters.

[0255] Specifically, taking the configuration related to the RedCap feature in the RRC reconfiguration message as an example, the following can be shown:

[0256] The featureConfigList is a feature configuration list, configured to carry one or more feature configuration parameters; the featureConfigToRemoveList is configured to release or delete one or more feature configuration parameters; the featureConfigToAddModList is configured to add or modify one or more feature configuration parameters; it can be understood that the featureConfigToRemoveList and the featureConfigToAddModList are optional, that is, the featureConfigList can directly include one or more FeatureConfigInfo; the FeatureConfigInfo is configured to configure a feature configuration parameter, including the featureConfigId and the featureConfig; the featureConfigId is a configuration identifier (for example, a first configuration identifier), configured to identify a feature or a configuration parameter related to the feature; the featureConfig is configured to carry the configuration parameter related to the feature indicated by the featureConfigId. The feature configuration parameter can be a string, a byte string or a bit string, and the featureConfig of different features can include different contents.

[0257] Taking the RedCap feature as an example, when the featureConfigId indicates the RedCap feature, the encoding / decoding of the featureConfig is defined by FeatureConfigRedCap, wherein the FeatureConfigRedCap includes the configuration parameter newly added / expanded / related to the RedCap feature, which can include one or more of the configuration parameter specific to a terminal device, the configuration parameter specific to a cell group, the configuration parameter specific to a cell, the configuration parameter specific to a BWP, etc. Specifically, the FeatureConfigRedCap can be shown as follows:

[0258] rrm-MeasRelaxationReportingConfig is an example of terminal device specific configuration parameter related to RedCap feature; CellGroupRedCap is used to carry other configuration parameters related to RedCap feature, which can include one or more of the following: configuration parameters specific to cell group, configuration parameters specific to cell, configuration parameters specific to BWP, etc. CellGroupRedCap can be included in the information element definition of CellGroupConfig, to indicate that the parameters included in CellGroupRedCap correspond to the parameters in CellGroupConfig. For example, if the secondaryCellGroup is included in the basic configuration parameters (e.g. CellGroupConfig), and the secondaryCellGroup is also included in the RedCap feature configuration parameters (e.g. CellGroupRedCap), then the secondaryCellGroup configuration parameters of the terminal device include the above two parts.

[0259] Specifically, CellGroupRedCap and CellGroupConfig can be shown as follows:

[0260] Wherein, cellGroupId is a cell group identifier, used to identify a cell group; SpCellConfigRedCap is used to carry configuration parameters related to RedCap feature, which are specific to the serving cell (e.g. further carried in ServingCellConfigCommonRedCap); servCellIndex is a serving cell identifier, used to identify a serving cell.

[0261] ServingCellConfigCommonRedCap can be included in the information element definition of ServingCellConfigCommon, to indicate that the configuration parameters included in ServingCellConfigCommonRedCap correspond to the configuration parameters in ServingCellConfigCommon. For example, if the configuration parameters of the first cell are included in the basic configuration parameters (e.g. ServingCellConfigCommon), and the configuration parameters of the first cell are also included in the RedCap feature configuration parameters (e.g. ServingCellConfigCommonRedCap), then the configuration parameters of the first cell of the terminal device include the above two parts.

[0262] Specifically, ServingCellConfigCommonRedCap and ServingCellConfigCommon can be shown as follows:

[0263] wherein, physCellId is a physical cell identifier, used to indicate a cell; downlinkConfigCommonRedCap is used to carry downlink configuration parameters of a cell related to RedCap characteristics; uplinkConfigCommonRedCap and supplementaryUplinkRedCap are used to carry uplink configuration parameters of a cell related to RedCap characteristics. DownlinkConfigCommonRedCap can be included in the signaling definition of DownlinkConfigCommon, to represent that the configuration parameters in DownlinkConfigCommonRedCap and the configuration parameters in downlinkConfigCommon are corresponding; similarly, UplinkConfigCommonRedCap can be included in the signaling definition of UplinkConfigCommon, to represent that the configuration parameters in UplinkConfigCommonRedCap and the configuration parameters in UplinkConfigCommon are corresponding.

[0264] It can be understood that the parameters in the BWP and other levels are similar, which will not be repeated here. The parameter names in all the above examples are only examples, and do not limit the naming of each information. The configuration parameters in the above examples can be optional or mandatory, depending on the specific circumstances of each parameter, which is not limited in the present embodiment.

[0265] The above describes the method provided by the embodiments of the present application by taking the terminal device and the network device as an example. In the present application, each embodiment can be independently implemented or implemented based on certain internal relationship; different implementation manners in each embodiment can be combined or independently implemented. In order to realize the functions in the method provided by the embodiments of the present application, the steps executed by the terminal device can be realized by different functional entities constituting the terminal device. The steps executed by the network device can be realized by different functional entities constituting the network device.

[0266] Those skilled in the art will appreciate that embodiments of the present application can be readily used as software, hardware, or a combination of software and hardware. In a software embodiment, various software modules in accordance with embodiments of the present application are stored in a memory such as a computer memory or disk storage for use by, or in connection with, the software on the computer system. The software can provide for programs to be transferred to another computer readable medium (e.g., a removable medium, or a medium conveyed through a computer network) for use in a different system.

[0267] The present application is described in reference to the flow diagrams and / or block diagrams of the methods, apparatus (systems) and computer program products according to this application. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks.

[0268] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flow diagrams and / or block diagrams block or blocks.

[0269] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks.

[0270] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method for reporting terminal device capability, characterized in that, comprising: receiving a capability enquiry message; sending first capability information of the terminal device, the first capability information comprising a first identity and first feature-related capability information, the first identity being used for identifying a first feature or for identifying the first feature-related capability information. 2.A method for reporting terminal device capability, characterized in that, comprising: sending a capability enquiry message; receiving first capability information of the terminal device, the first capability information comprising a first identity and first feature-related capability information, the first identity being used for identifying a first feature or for identifying the first feature-related capability information.

3. The method of claim 1 or 2, wherein, The first feature-related capability information comprises at least one of: first feature-related terminal device-specific capability information, first feature-related frequency band-specific capability information, or first feature-related frequency band combination-specific capability information.

4. The method according to any one of claims 1 to 3, characterized in that, The first capability information comprises a first identity and first feature-related capability information, comprising: The first capability information comprises terminal device-specific capability information, the terminal device-specific capability information comprising the first identity and the first feature-related terminal device-specific capability information; and / or, the first capability information comprises first frequency band-specific capability information, the first frequency band-specific capability information comprising the first identity and the first feature-related first frequency band-specific capability information; and / or, the first capability information comprises first frequency band combination-specific capability information, the first frequency band combination-specific capability information comprising the first identity and the first feature-related first frequency band combination-specific capability information.

5. The method according to any one of claims 1 to 4, wherein The first capability information further indicates that a second frequency band in a second frequency band combination corresponds to a first feature set identity, the first feature set identity being used for indicating that a first feature set in a first feature set collection and a second feature set in a second feature set collection are supported on the second frequency band in the second frequency band combination; The position of the first feature set in the first feature set collection is the same as the position of the second feature set in the second feature set collection.

6. The method of claim 5, wherein, Any feature set in the first feature set collection comprises the first feature-related capability information.

7. The method of claim 5 or 6, wherein, Any feature set in the second feature set collection comprises basic capability information or second feature-related capability information.

8. The method according to any one of claims 5 to 7, wherein, The number of feature sets included in the first feature set collection is the same as the number of feature sets included in the second feature set collection.

9. The method according to any one of claims 1 to 8, wherein, The first capability information further indicates that a first carrier of a third frequency band in a third frequency band combination corresponds to a first carrier feature set identity, the first carrier feature set identity being used for indicating that a first carrier feature set in a first carrier feature set collection and a second carrier feature set in a second carrier feature set collection are supported on the first carrier of the third frequency band in the third frequency band combination; The position of the first carrier feature set in the first carrier feature set collection is the same as the position of the second carrier feature set in the second carrier feature set collection.

10. The method of claim 9, wherein, Any carrier feature set in the first carrier feature set collection comprises the first feature-related capability information.

11. The method of claim 9 or 10, wherein, Any carrier feature set in the second carrier feature set collection comprises basic capability information or third characteristic related capability information.

12. The method according to any one of claims 9 to 11, characterized in that, The number of carrier feature sets included in the first carrier feature set collection is the same as the number of carrier feature sets included in the second carrier feature set collection.

13. The method of claim 1 or 2, wherein, The first capability information comprises a first identifier and first characteristic related capability information, which comprises: The first capability information comprises first information related to the first characteristic, and the first information comprises the first identifier and at least one of the following: The first characteristic related terminal device specific capability information; The first characteristic related first frequency band specific capability information; Or, the first characteristic related first frequency band combination specific capability information.

14. The method of claim 13, wherein, The capability information of the terminal device further comprises second information related to basic capability information, and the second information comprises basic capability information specific to the first frequency band combination.

15. The method of claim 14, wherein, The position of the basic capability information specific to the first frequency band combination in the second information is the same as the position of the first characteristic related capability information specific to the first frequency band combination in the first information. Or, the first characteristic related capability information specific to the first frequency band combination comprises a frequency band list, and the frequency band list indicates frequency bands included in the first frequency band combination. Or, the first characteristic related capability information specific to the first frequency band combination comprises a first index, and the value of the first index is related to the position of the basic capability information specific to the first frequency band combination in the second information.

16. The method of claim 15, wherein, The number of frequency band combinations of the capability information specific to the frequency band combination included in the first information is the same as the number of frequency band combinations of the capability information specific to the frequency band combination included in the second information.

17. The method of any one of claims 13-16, wherein, The terminal device supports the first feature set in the first information and the second feature set in the second information on a second frequency band in a second frequency band combination. The position of the first feature set in the feature set corresponding to the second frequency band of the second frequency band combination in the first information is the same as the position of the second feature set in the feature set corresponding to the second frequency band of the second frequency band combination in the second information, or the first feature set is associated with a second index, and the value of the second index is related to the position of the second feature set in the feature set corresponding to the second frequency band of the second frequency band combination in the second information.

18. The method of claim 17, wherein, The number of feature sets corresponding to the second frequency band of the second frequency band combination in the first information is the same as the number of feature sets corresponding to the second frequency band of the second frequency band combination in the second information.

19. The method of any one of claims 1-18, wherein, The first characteristic is one of the following characteristics: reduced capability or low capability terminal, sidelink enhancement, mobility enhancement, multiple input multiple output (MIMO), carrier aggregation, low latency service, extended reality (XR), artificial intelligence (AI), deterministic experience, or dual connectivity (DC).

20. The method of any one of claims 1-19, wherein, The method further comprises: sending second capability information of the terminal device, wherein the second capability information comprises first indication information, and the first indication information is used to indicate to maintain or release or add capability information of the first characteristic.

21. A communications device, characterized by comprising means or modules for performing the method of any one of claims 1, 3-20.

22. A communications device, characterized by comprising means or modules for performing the method of any one of claims 2-20.

23. A communications device, characterized by comprising a processor and a memory for storing program instructions which, when executed by the processor, cause the method of any one of claims 1, 3-20 to be performed.

24. A communications device, characterized by comprising a processor and a memory for storing program instructions which, when executed by the processor, cause the method of any one of claims 2-20 to be performed.

25. A computer readable storage medium, characterized in that, The computer readable storage medium has stored therein computer readable instructions which, when executed on a communications device, cause the method of any one of claims 1, 3-20 or the method of any one of claims 2-20 to be performed.

26. A computer program product, characterised in that, The computer program product, when executed on a device, causes the device to perform the method of any one of claims 1, 3-20 or the method of any one of claims 2-20.

Images