UE capability reporting method and device

Abstract

The invention provides a UE (User Equipment) capability reporting method and device, which are used for reducing signaling overhead of UE capability reporting and how to adapt to a product development rhythm. According to the method and the device, the identification corresponding to the capability information related to the characteristics is included in the capability information of the terminal equipment, the capability information of each characteristic can be isolated from the basic capability information of the terminal equipment, and the capability information of each characteristic is mutually independent, so that decoupling of a reporting sequence (or a reporting position) is realized, and the user experience is improved. Therefore, the capability information of the characteristic can be flexibly added or deleted in the capability information of the terminal equipment through the identifier, on one hand, a certain characteristic can be developed in advance so as to adapt to the product release rhythm and the market rhythm, and on the other hand, the signaling overhead can be reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a UE capability reporting method and apparatus. Background Technology

[0002] Due to differences in hardware or software versions, the capabilities of different terminal devices may vary. In order to better serve terminal devices, network devices need to know the capabilities of the terminal devices in order to configure and schedule them.

[0003] As standard protocol versions evolve and new terminal device features are continuously introduced, the reported UE capability stream becomes increasingly large. Under the current method of reporting UE capability information, features not supported by the terminal device cannot be completely removed from the UE capability stream, resulting in significant signaling overhead. Furthermore, the current method of reporting UE capability information involves inter-coupling between UE capabilities related to different features. This means that feature capabilities can only be fully finalized after all features have been discussed and the protocol is finalized. This makes feature development dependent on the protocol finalization schedule, which may not align with product release or market pace, impacting product development timelines.

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

[0005] This application provides a UE capability reporting method and apparatus to reduce the signaling overhead of UE capability reporting and to adapt to the product development pace.

[0006] Firstly, this application provides a communication method. The execution subject of this method can be a terminal device, or a chip or circuit on the terminal device side. Taking a terminal device as an example, the method includes: receiving a capability query message and sending first capability information of the terminal device. The first capability information includes a first identifier and capability information related to a first characteristic. The first identifier is used to identify the first characteristic, or to identify capability information related to the first characteristic.

[0007] Currently, the capability information encoding of a specific terminal device can only be determined after all features discussed in the 3GPP protocol version are finalized, because the capability information of each feature is interdependent; for example, the position (or reporting order) of capability-related features in the terminal device's capability information needs to be fixed. However, this application, by including identifiers corresponding to feature-related capability information in the terminal device's capability information, isolates the capability information of each feature from the basic capability information of the terminal device, and ensures that the capability information of each feature is independent of each other, achieving decoupling of the reporting order (or reporting position). Therefore, this application can flexibly add new feature capability information to the terminal device's capability information using identifiers. Compared to the method of reporting capability information of each feature in a fixed order (or fixed position), this application can develop a feature in advance without waiting for other features to be finalized, thus adapting to product release and market rhythms. For example, based on R15, there is no need to wait for the R16 extended feature to be finalized; R17 extended features can be developed directly. As another example, to implement a feature in R17, there is no need to wait for all parameters of that feature in R17 to be finalized, or in other words, there is no need to wait for any other features in R17 to be finalized.

[0008] Compared to extending the RRC protocol by version, implementing one or more features is less complex. Furthermore, due to the isolation between features in the same / different versions, development can begin on specific features without waiting for all features to be stable and the protocol to be finalized, thus shortening the development cycle.

[0009] Furthermore, through the solution of this application, the capability information of each feature is decoupled from the capability information of the terminal device. Therefore, for unsupported features, these features can be removed from the capability information of the terminal device, thereby reducing the capability reporting overhead of the terminal device.

[0010] Secondly, this application provides a communication method, the execution subject of which can be a network device, or a chip or circuit on the network device side. Taking a network device as an example, the method includes: sending a capability query message and receiving first capability information of a terminal device, the first capability information including a first identifier and capability information related to a first characteristic, the first identifier being used to identify the first characteristic, or to identify capability information related to the first characteristic.

[0011] Currently, the capability information encoding of a specific terminal device can only be determined after all features discussed in the 3GPP protocol version are finalized, because the capability information of each feature is interdependent; for example, the position (or reporting order) of capability-related features in the terminal device's capability information needs to be fixed. However, this application, by including identifiers corresponding to feature-related capability information in the terminal device's capability information, isolates the capability information of each feature from the basic capability information of the terminal device, and ensures that the capability information of each feature is independent of each other, achieving decoupling of the reporting order (or reporting position). Therefore, this application can flexibly add new feature capability information to the terminal device's capability information using identifiers. Compared to the method of reporting capability information of each feature in a fixed order (or fixed position), this application can develop a feature in advance without waiting for other features to be finalized, thus adapting to product release and market rhythms. For example, based on R15, there is no need to wait for the R16 extended feature to be finalized; R17 extended features can be developed directly. As another example, to implement a feature in R17, there is no need to wait for all parameters of that feature in R17 to be finalized, or in other words, there is no need to wait for any other features in R17 to be finalized.

[0012] Compared to extending the RRC protocol by version, implementing one or more features is less complex. Furthermore, due to the isolation between features in the same / different versions, development can begin on specific features without waiting for all features to be stable and the protocol to be finalized, thus shortening the development cycle.

[0013] Furthermore, through the solution of this application, the capability information of each feature is decoupled from the capability information of the terminal device. Therefore, for unsupported features, these features can be removed from the capability information of the terminal device, thereby reducing the capability reporting overhead of the terminal device.

[0014] Based on the first and second aspects mentioned above, the following design can be made:

[0015] In one possible design, the capability information related to the first characteristic includes 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, or frequency band combination-specific capability information related to the first characteristic. This design enables the network device to obtain detailed capabilities of the terminal device regarding the first characteristic.

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

[0017] By including the identifier associated with the first feature in each level, the capability information related to the first feature can be flexibly reported in the UE capabilities at each level.

[0018] In one possible design, the first capability information further indicates that the second frequency band in the second frequency band combination corresponds to a first feature set identifier. The first feature set identifier is used to indicate that the second frequency band in the second frequency band combination supports the first feature set in the first feature set set and the second feature set in the second feature set set. The position of the first feature set in the first feature set set is the same as the position of the second feature set in the second feature set set. Through the above design, the basic capability information and the capability information related to the first characteristic can be associated, thereby enabling the network device to obtain the complete capabilities of the second frequency band in the second frequency band combination.

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

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

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

[0022] In one possible design, the first capability information further indicates that the first carrier of the third frequency band in the third frequency band combination corresponds to a first carrier feature set identifier, which is used to indicate that the first carrier feature set in the first carrier feature set and the second carrier feature set in the second carrier feature set 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 is the same as the position of the second carrier feature set in the second carrier feature set.

[0023] Through the above design, basic capability information and capability information related to the first characteristic can be associated, thereby enabling network devices to obtain the complete capability of the first carrier of the third frequency band in the third frequency band combination.

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

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

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

[0027] In one possible design, the first capability information includes a first identifier and capability information related to a first characteristic, including: the first capability information includes first information related to the first characteristic, the first information including 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 at the hierarchical level. The capability information related to the first characteristic is carried in a separate information cell, and the information cell includes a first identifier. In this way, on the one hand, it can avoid changing the encoding structure of the basic capability information and reduce the implementation complexity; on the other hand, the capability information of each level related to the first characteristic can be identified by a first identifier, which can reduce signaling overhead.

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

[0030] In one 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 specific to the first frequency band combination related to the first characteristic in the first information; or, the capability information specific to the first frequency band combination related to the first characteristic includes a frequency band list indicating the frequency bands included in the first frequency band combination; or, the capability information specific to the first frequency band combination related to the first characteristic includes a first index, the value of which is related to the position of the basic capability information specific to the first frequency band combination in the second information.

[0031] This method allows the basic capability information specific to the first frequency band combination to be associated with the capability information specific to the first frequency band combination related to the first characteristic, thereby enabling the network device to obtain the complete capabilities of the first frequency band combination.

[0032] In one possible design, the number of frequency band combinations included in the first information is the same as the number of frequency band combinations included in the second information. This approach facilitates the association of basic capability information specific to the first frequency band combination with capability information specific to the first characteristic.

[0033] In one possible design, the terminal device supports a first feature set in the first information and a 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 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 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 in the second information.

[0034] This method allows the basic capability information of the second frequency band in the second frequency band combination to be associated with the capability information of the second frequency band in the second frequency band combination related to the first characteristic, thereby enabling the network device to obtain the complete capability of the second frequency band in the second frequency band combination.

[0035] In one possible design, 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. This approach facilitates the association of the basic capability information of the second frequency band of the second frequency band combination with the capability information of the second frequency band of the second frequency band combination related to the first characteristic.

[0036] In one possible design, the first characteristic is one of the following: capability reduction or low-capability 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 one possible design, the method further includes: sending second capability information of the terminal device, the second capability information including first indication information, the first indication information being used to indicate capability information for maintaining, releasing or adding a first feature.

[0038] In one possible design, the second capability information may not include the basic capability information.

[0039] If the basic capability information of the terminal device has not changed, updating the capability information of the terminal device only involves adding or modifying feature-related capabilities. By reporting feature-related capability information instead of basic capability information, the terminal device can further reduce signaling overhead.

[0040] Thirdly, this application also provides a communication device that implements any of the methods provided in the first aspect. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0041] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the terminal device in the methods described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and devices such as network devices.

[0042] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0043] In one possible implementation, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the first aspect, and will not be repeated here.

[0044] Fourthly, this application also provides a communication device that implements any of the methods provided in the second aspect above. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0045] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the network device described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and devices such as terminal devices.

[0046] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

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

[0048] Fifthly, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the methods of the first aspect and any possible design through logic circuits or execution code instructions.

[0049] In a sixth aspect, a communication device is provided, including a processor and an interface circuit. The interface circuit is configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is configured to implement the methods of the second aspect and any possible design described above through logic circuits or execution code instructions.

[0050] In a seventh aspect, a computer-readable storage medium is provided that stores a computer program or instructions which, when executed by a processor, implement the methods in any possible design of the first aspect and any of the aspects described above.

[0051] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions which, when executed by a processor, implement the methods in any possible design of the second aspect and any of the aspects described above.

[0052] A ninth aspect provides a chip system including a processor and potentially a memory for implementing the methods described in the first aspect and any possible designs thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0053] In a tenth aspect, a chip system is provided, comprising a processor and potentially a memory, for implementing the methods of any possible design in the second aspect and any of the preceding aspects. The chip system may be composed of chips or may include chips and other discrete devices.

[0054] Eleventhly, a communication system is provided, the system comprising the apparatus of the first aspect (such as a terminal device) and the apparatus of the second aspect (such as a network device).

[0055] The technical effects that can be achieved by any of the technical solutions in the third to eleventh aspects mentioned above can be described with reference to the technical effects that can be achieved by the technical solution in the first aspect mentioned above, and the repeated parts will not be repeated. Attached Figure Description

[0056] Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of this application;

[0057] Figure 2 This is a schematic diagram of the architecture of an open communication system according to an embodiment of this application;

[0058] Figure 3 This is a schematic diagram of an open access network device according to an embodiment of this application;

[0059] Figure 4 This is a schematic diagram of a carrier aggregation embodiment of this application;

[0060] Figure 5 This is a schematic diagram of capability information according to an embodiment of this application;

[0061] Figure 6 This is a schematic diagram of a feature set combination according to an embodiment of this application;

[0062] Figure 7 This is a flowchart illustrating a communication method according to an embodiment of this application;

[0063] Figure 8 This is a schematic diagram of the structure of a first capability information according to an embodiment of this application;

[0064] Figure 9 This is a schematic diagram of the structure of a first capability information according to an embodiment of this application;

[0065] Figure 10 This is a schematic diagram of the structure of a first capability information according to an embodiment of this application;

[0066] Figure 11 This is a schematic diagram of the structure of a first capability information according to an embodiment of this application;

[0067] Figure 12 This is a schematic diagram of feature set association according to an embodiment of this application;

[0068] Figure 13 This is a schematic diagram of the structure of a first capability information according to an embodiment of this application;

[0069] Figure 14This is a schematic diagram of carrier feature set association according to an embodiment of this application;

[0070] Figure 15 This is a schematic diagram of the structure of a first capability information according to an embodiment of this application;

[0071] Figure 16 This is a schematic diagram illustrating capability information association according to an embodiment of this application;

[0072] Figure 17 This is a schematic diagram illustrating capability information association according to an embodiment of this application;

[0073] Figure 18 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0074] Figure 19 This is a schematic diagram of the structure of a communication device according to an embodiment of this application. Detailed Implementation

[0075] The technical solutions provided in the embodiments of this application can be applied to various wireless communication systems. For example, the methods provided in the embodiments of this application can be applied to communication systems related to the 3rd Generation Partnership Project (3GPP), such as Long Term Evolution (LTE) communication systems, 5th Generation (5G) mobile communication systems, or other next-generation mobile communication systems, such as 6th Generation (6G) communication systems, or other similar communication systems. Other similar communication systems may include Wireless Fidelity (WIFI), Vehicle-to-Everything (V2X), Internet of Things (IoT) systems, Narrow Band Internet of Things (NB-IoT) systems, and so on.

[0076] Please see Figure 1 This illustrates a network architecture for a communication system, which may include at least one network device and at least one terminal device. Figure 1 Taking at least one terminal device as an example and at least one network device as an example, the network device can be an access network device, or the network device can include both access network devices and core network devices. Figure 1The network architecture shown is merely illustrative; the number of terminal devices and / or network devices may be fewer or more. The communication systems described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application and do not constitute a limitation on the communication systems to which the embodiments of this application are applicable. Those skilled in the art will understand that, with the evolution of network architectures, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. When applying the technical solutions of the embodiments of this application to other communication systems, the devices, components, modules, etc., in the embodiments can be replaced with corresponding devices, components, modules, etc., in other communication systems, without limitation.

[0077] The network devices involved in the embodiments of this application are mainly access network devices. Therefore, unless otherwise specified, the term "network device" in the following text refers to radio access network (RAN) devices, which can be simply referred to as access network devices. RAN can be a 3GPP-related cellular system, such as a 5G mobile communication system, or a future-oriented evolution system (such as a 6G mobile communication system). RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a virtualized RAN (vRAN), etc. RAN can also be a communication system that integrates two or more of the above systems. RAN devices can also be called RAN nodes, RAN entities, or access nodes, etc.

[0078] In one possible scenario, a 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, or a base station in a future mobile communication system. A RAN node can also be a macro base station, a micro base station, an indoor station, a relay node, a donor / host node, or a radio controller. RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, a RAN node can be a roadside unit (RSU).

[0079] In another possible scenario, a RAN node can be a module or unit that performs some of the functions of a base station; or multiple RAN nodes can collaborate to assist terminal devices in achieving wireless access, with different RAN nodes performing some of the functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The functions of a CU can be implemented by a single entity or by different entities. For example, the functions of a CU can be further divided, separating the control plane and the user plane and implementing them through different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). This CU-CP entity and CU-UP entity can be coupled with a DU to jointly complete the functions of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in a baseband unit (BBU).

[0080] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0081] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (e.g., the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of protocol layers below the PDCP layer (e.g., the Radio Link Control (RLC) layer, the MAC layer, and / or the Physical (PHY) layer). For specific descriptions of the above-mentioned protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols. The above division of the processing functions of the CU and DU according to protocol layers is merely an example; other division methods are also possible, and this application does not impose any limitations.

[0082] Figure 2 An example diagram of an O-RAN system is shown. It should be understood that an O-RAN system may also include... Figure 2 Other components besides those shown are not specifically limited here. For example... Figure 2As shown, access network equipment can communicate with the core network (CN) via a backhaul link and with terminal equipment via an air interface. For example, access network equipment may include a baseband unit (BBU) and a radio unit (RU). The BBU includes at least one core unit (CU) and at least one dual unit (DU), which can communicate via at least one midhaul link. The RU can implement lower physical layer (PHY) and radio frequency (RF) functions. In some examples, the RU may be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities. In some examples, the low-PHY may include PHY processing functions such as fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming, and filtering. The BBU can communicate with the CN via a backhaul link, and the RU can communicate with at least one terminal device via an air interface. The BBU can communicate with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located.

[0083] Figure 3 This diagram illustrates the network element functional division and protocol layer structure of an O-RAN device. It should be noted that... Figure 3 The configurations of CU and DU shown are merely examples; the functions of CU and DU can be configured as needed. For instance, CU or DU can be configured to have more protocol layer functions, or to have only partial protocol layer processing functions. DU and RU can be co-located or not. DU and RU can exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include separate control plane and user plane interfaces.

[0084] The control plane (C-Plane) and user plane (U-Plane) use LLS-C and LLS-U interfaces. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link. The management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0085] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0086] In the embodiments of this application, the means for implementing the functions of the network device can be the network device itself, or it can be a means that supports the network device in implementing the functions, such as a chip system or a combination of devices or components that can implement the functions of the network device. This means can be installed in the network device. The embodiments of this application do not limit the specific technology or specific device form used in the network device.

[0087] In this application embodiment, any device capable of data communication with a base station can be considered a terminal device. Terminal devices are also called terminals, user equipment (UE), mobile stations, or mobile terminals. Terminal devices can be widely used in various scenarios, such as D2D communication, V2X communication, machine-type communication (MTC), IoT, virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, or smart cities. For example, terminal devices can be: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, robotic arms, cameras, robots, or smart home devices (such as televisions, air conditioners, robot vacuums, speakers, set-top boxes), relays, customer premises equipment (CPE), etc.

[0088] The various terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can all be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit. In-vehicle terminal devices can be vehicle equipment, in-vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), telematics boxes (T-boxes), chips, or systems on chips (SOCs), etc. These chips or SOCs can be installed in vehicles, OBUs, RSUs, or T-boxes.

[0089] In the embodiments of this application, the device for implementing the functions of the terminal device can be the terminal device itself, or a device capable of supporting the terminal device in implementing the functions, such as a chip system or a combination of devices or components capable of implementing the functions of the terminal device. This device can be installed in the terminal device. The embodiments of this application do not limit the specific technology or specific device form used in the terminal device.

[0090] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0091] The technical background of this application is described below.

[0092] In order to better serve terminal devices, network devices need to know the capabilities of the terminal devices in order to configure and schedule them.

[0093] In 5G systems, the capabilities of terminal devices can be divided into several levels. For example, such as... Figure 4 As shown, this hierarchical structure represents the structure of the terminal device's capability information. The terminal device's capability information may include:

[0094] - Device-specific capability information (also known as device-level capabilities, per-UE capabilities, or UE capabilities): Applicable to all frequency bands and combinations thereof. Device-specific capability information includes capabilities supported by the device across all frequency bands. Device-specific capabilities may include one or more of the following: access stratum release, PDCP parameters, RLC parameters, MAC parameters, PHY parameters, and measurement and addition parameters.

[0095] - Band-specific capability information (also known as band-level capability, per-band capability, or frequency band capability): This is typically related to the radio frequency (RF) capabilities of a terminal device. Band-specific capability information includes the terminal device's capabilities on a specific frequency band. This capability may differ across different frequency bands. Band-specific capabilities may include one or more of the following: band identifier (FreqBandIndicatorNR), MIMO parameters (mimo-ParametersPerBand), and unrestricted bandwidth portion (bwp-WithoutRestriction). The terminal device's band-specific capability information may be included in the supported band list. The band list includes at least one frequency band supported by the terminal device. The band identifier indicates the frequency band corresponding to the band-specific capability information.

[0096] - Band combination (BC) specific capability information (also known as per BC capability or band combination capability): This capability is related to band combinations, which are mainly associated with the carrier aggregation (CA) and DC capabilities supported by the terminal device. A band combination can consist of one or more bands and the carriers included in those bands that the terminal device supports for carrier aggregation or dual connectivity. In other words, for a band combination reported by a terminal device, the network device can configure the carriers included in that band combination for that terminal device to perform carrier aggregation or dual connectivity transmission. Furthermore, from a capability signaling structure perspective, the capability of a single band or a single carrier can also be reported through the signaling structure of a band combination. The band combinations supported by a terminal device are usually related to the terminal device's radio frequency (RF) and baseband (BBS) capabilities. The band combination specific capability information of the terminal device can be included in the supported band combination list.

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

[0098] Each frequency band combination can also be associated with a feature set combination (FSC), which can be identified by a FeatureSetCombinationId. The FSC contains capability information for each band in the frequency band combination (per BC per band capability). The FSC can also indicate the capability information for the carriers in that band (per CC capability).

[0099] The per BC per band capability refers to the capability for a specific frequency band within a frequency band combination. Each frequency band in a frequency band combination can be associated with one or more feature sets (FS). Terminal devices can report a combination of per BC per band capabilities for a frequency band combination by reporting one or more lines of feature sets (FS). Figure 5 An exemplary diagram illustrates how different capabilities (e.g., per CC capability and / or per BC per band capability) of a frequency band combination are reported using a multi-line feature set (FS) in a capability signaling structure. Figure 5As shown, band combination BC1 consists of band A, band B, and band C. For band combination BC1, the terminal device can report three lines of FS (Frequency Files), each corresponding to a combination of BC capabilities that the terminal device can support. In the first line of FS, the FS for band A is FS1 (which can be understood as FS ID 1, similar below), the FS for band B is FS2, and the FS for band C is FS3. These can be considered as a combination of BC capabilities that the network can configure for the terminal device. In the second line of FS, the FS for band A is still FS1, the FS for band B is FS4, and the FS for band C is FS5. Since the FS for band B is different from the FS for band B in the first line of FS, and the FS for band C is different from the FS for band C in the first line of FS, the combination of BC capabilities corresponding to the second line of FS is different from that in the first line. Different FS correspond to different carrier capabilities. For example, if the terminal device supports 5 carriers, in the first line of FS, it can report 1 carrier on band A (indicating that the terminal device supports one carrier on band A, similar below), 2 carriers on band B, and 2 carriers on band C, for example... Figure 6 As shown; in the second line, FS can report 1 carrier on band A, 2 carriers on band B, and 1 carrier on band C. According to... Figure 5 The terminal device reports capability information as shown. When configuring frequency band combination BC1 for the terminal device, the network device can configure the carrier for the terminal device's operation based on the feature sets of each frequency band in the same row of FS. When the network device needs to switch configurations, it can send RRC reconfiguration signaling to the terminal device to instruct it to switch to the configuration corresponding to the second row of feature sets. A frequency band's feature set can be identified using a feature set identifier (FS ID). The FS ID can be zero, for example, Figure 5 In the third row of FS, the FS ID for band C is FS 0, indicating that the terminal device does not have uplink or downlink transmission capabilities on band C, meaning it does not support receiving downlink signals or transmitting uplink signals on the carrier of band C. Each FS includes a FeatureSetDownlink information element (IE) for reporting downlink transmission capabilities and a FeatureSetUplink information element for reporting uplink transmission capabilities, used to indicate the uplink and downlink transmission capabilities of the terminal device, respectively. The per BC per band capability can also be called the frequency band feature set.

[0100] Per CC capability refers to the capability of carriers on a frequency band within a frequency band combination. Information on 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, including, for example, one or more of the following: subcarrier spacing (SCS), maximum number of multiple-input multiple-output (MIMO) layers, and maximum carrier bandwidth. For example, frequency band 1 in frequency band combination BC 1 can correspond to a carrier list containing three component carriers (CC1, CC2, CC3), indicating that the terminal device supports a maximum of three component carriers on frequency band 1. Taking CC1 as an example, CC1 is associated with FSPC 1, which indicates CC1's MIMO capability, channel state information (CSI) measurement capability, modulation type, etc. Each FSPC includes FeatureSetDownlinkPerCC cells for reporting downlink transmission capabilities and FeatureSetUplinkPerCC cells for reporting uplink transmission capabilities, which respectively indicate the uplink and downlink transmission capabilities of the terminal equipment. The per CC capability can also be called the carrier feature set.

[0101] The above describes the relevant content regarding the reporting of terminal device capabilities. The following section discusses the existing problems in the current reporting of terminal device capabilities.

[0102] As NR versions evolve, new features are continuously introduced, and the corresponding UE capabilities are constantly added to the terminal device's capability information. Based on the structure of the terminal device's capability information described earlier, newly added features are expanded according to the version within each layer of the terminal device's capability information. From the perspective of abstract syntax notation one (ASN.1), which encodes the terminal device's capability information, unsupported features cannot be completely removed from the terminal device's capability information, resulting in significant overhead for capability reporting, especially for UE capabilities per band and per BC, where the overhead is substantial at each band and BC.

[0103] Furthermore, based on the current methods of reporting UE capability information, UE capabilities related to different features are interdependent. For example, a new feature proposed for the current 3GPP protocol version can only have its reporting method determined after all features discussed in the current 3GPP protocol version are finalized. To illustrate, only after all features discussed in the current 3GPP protocol version are finalized can the reporting order (or extension order), reporting content, etc., of each feature be determined, thereby determining the encoding structure of the terminal device's capability information. Therefore, the encoding structure of the terminal device's capability information can only be fully determined after the 3GPP protocol version is finalized, and only then can the development of the corresponding feature begin. However, the pace of 3GPP discussions does not necessarily coincide with product releases or market rhythms, which can impact the product development schedule.

[0104] A feature can be understood as a specific enhancement, a specific function, a specific service, a specific terminal device type, a specific network device type, or a specific capability. A feature has a corresponding capability. For example, if a terminal device has / supports a first feature, and the first feature corresponds to a first capability, then the terminal device has the first capability; or, if the first capability corresponds to the first feature, then the terminal device having the first capability indicates 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 generate one or more features. For example, 3GPP R16 introduced the URLLC feature compared to R15; R17 introduced features such as "Redcap," "sidelink enhancement," and "mobility enhancement" compared to R16. A first feature can be one or more features introduced in multiple versions, including future versions. For example, a first feature includes one or more of the following: "Redcap," "sidelink enhancement," "mobility enhancement," "MIMO," "CA," "low latency service," "XR," "AI," "deterministic experience," or "DC," etc.

[0105] Based on this, embodiments of this application provide a communication method and apparatus for reducing the signaling overhead of UE capability reporting and adapting to product development pace. The method and apparatus are based on the same inventive concept. Since the principles by which the method and apparatus solve problems are similar, their implementations can be mutually referenced, and repeated details will not be elaborated further.

[0106] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" can be substituted, and "when" and "in the case of" can be substituted. "When" and "if" / "if" can be substituted.

[0107] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.

[0108] For example, at least one of a, b, or c can be represented as: 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 a single or multiple.

[0109] Furthermore, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects.

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

[0111] It should be noted that the names of information elements, fields, containers, lists, and information in this application are merely exemplary names.

[0112] In this application, the basic capability information is merely a euphemism for some capability information, and this application does not limit the name of the capability information.

[0113] Furthermore, for ease of description, this application describes the identifier associated with the capability information related to the feature as the identifier associated with the feature. For example, the first identifier is the identifier associated with the capability information related to the first feature. For ease of description, the first identifier is referred to as the identifier associated with the first feature.

[0114] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0115] like Figure 7 The diagram shown is a flowchart illustrating a UE capability reporting method provided in an embodiment of this application.

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

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

[0118] S702, the terminal device sends its first capability information. Correspondingly, the network device receives the terminal device's first capability information.

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

[0120] The first capability information includes capability information related to at least one characteristic and an identifier associated with each characteristic. The identifier associated with a characteristic can be understood as identifying that characteristic or the capability information related to that characteristic. Different characteristics may be associated with different identifiers.

[0121] Optionally, the correspondence between features and identifiers can be predefined by the protocol or configured by the network device. For example, the protocol specifies that the identifier of the first feature is the first identifier, and the identifier of the second feature is the second identifier, etc. Alternatively, the network device may indicate the correspondence between features and identifiers through signaling (e.g., system information), whereby the correspondence includes the first feature corresponding to the first identifier, the second feature corresponding to the second identifier, etc. This application does not limit the specific implementation of the correspondence between features and identifiers; for example, the correspondence between features and identifiers is shown in Table 1.

[0122] Table 1

[0123] characteristic logo MIMO 00000 XR 00001 AI 00002 … …

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

[0125] The capability information related to the first feature may include a first string, a first byte string, or a first bit string. The capability information related to the first feature may describe at least one capability related to the first feature. It is understood that the capability information related to the first feature may include only extended capability information related to the first feature. For example, the capability information related to the first feature may include capability information related to the first feature that has been extended / added in a specific version.

[0126] For example, the capability information related to the first characteristic may include at least one of the following: capability information specific to the terminal device (per UE capability) related to the first characteristic, capability information specific to the frequency band (per band capability) related to the first characteristic, capability information specific to the frequency band combination (per BC capability) related to the first characteristic, feature set related to the first characteristic, or carrier feature set related to the first characteristic.

[0127] For example, the first characteristic is one of the following: capability reduction or low-capability terminal (RedCap), sidelink enhancement, mobility enhancement, MIMO, carrier aggregation, low-latency service, extended reality (XR), artificial intelligence (AI), deterministic experience, or dual connection (DC). Similarly, the second characteristic, third characteristic, etc., mentioned below can also be one of the above characteristics.

[0128] The structure of the first capability information will be explained in detail below.

[0129] Currently, the reporting of newly added features can only be done after all features discussed in the 3GPP protocol version have been finalized, allowing for the determination of the data structure for encoding the terminal device's capability information. In this data structure, the capability information of each feature is coupled, for example, its position (or reporting order) within the terminal device's capability information is fixed. However, this application, by including identifiers corresponding to feature-related capability information in the terminal device's capability information, isolates the capability information of each feature from the basic capability information of the terminal device, and ensures that the capability information of each feature is independent of each other, achieving decoupling of the reporting order (or reporting position). Therefore, this application can flexibly add new feature capability information to the terminal device's capability information using identifiers. Compared to the method of reporting feature capability information in a fixed order (or fixed position), this application allows for the early development of a feature without waiting for other features to be finalized, thus adapting to product release and market rhythms. For example, based on R15, there is no need to wait for the R16 extended feature release; R17 extended features can be developed directly. For example, implementing a feature in version R17 does not require waiting for all parameters of that feature in previous versions of R17 to be finalized, or in other words, it does not require waiting for any other features in version R17 to be finalized. Compared to the RRC protocol, which extends by version, implementing one or more features is less complex. Furthermore, due to the same...

[0130] The features of different versions are isolated, so for each version, there is no need to wait for all features to be stable and the protocol to be closed before development can be carried out for specific features, which can shorten the development cycle.

[0131] Furthermore, with the solution proposed in this application, the capability information of each feature is no longer coupled to each other in the capability information of the terminal device. Therefore, for unsupported features, these features can be removed from the capability information of the terminal device, thereby reducing the capability reporting overhead of the terminal device.

[0132] This application provides two exemplary structures for first capability information.

[0133] The first structure involves extending the capability information of each level of the first capability information with capability information related to each characteristic of the corresponding level, and including an identifier associated with the capability information related to that characteristic in the capability information of that level. For example, the first capability information may 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 set, or carrier feature set set. Capability information related to the first characteristic of the corresponding level can be extended into the capability information of each level of the first capability information, and a first identifier can be included in the capability information of that level. The following description, in conjunction with each level of IE, shows that the first capability information may include one or more of the following:

[0134] 1. Terminal device-specific capability information

[0135] Terminal device-specific capability information may include access layer version, PDCP parameters, RLC parameters, MAC parameters, PHY parameters, measurement and addition parameters, etc. The access layer version and other capability information 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 the basic capabilities that the terminal device needs to support to establish a connection and transmit data with network devices, or as the terminal device capabilities introduced in the initial version of the standard.

[0136] Optionally, the terminal device-specific capability information may further include terminal device-specific capability information related to at least one characteristic, and identifiers associated with each of the at least one characteristic. The identifiers associated with each of the at least one characteristic can be understood as identifiers associated with the terminal device-specific capability information related to each of the at least one characteristic. Taking the first characteristic as an example, the terminal device-specific capability information may include terminal device-specific capability information related to the first characteristic and a first identifier.

[0137] In one possible implementation, the terminal device-specific capability information may include a first UE capability list. The first UE capability list may include terminal device-specific capability information related to at least one feature, and identifiers associated with each of the at least one feature.

[0138] (Or, identifiers associated with the terminal device-specific capability information related to at least one feature). For example, the first UE capability list may include a first identifier and terminal device-specific capability information related to the first feature. Optionally, the first UE capability list may also include a second identifier and terminal device-specific capability information related to the second feature, a third identifier and terminal device-specific capability information related to the third feature, and so on. The second and third identifiers function similarly to the first identifier and will not be elaborated further here.

[0139] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as follows: Figure 8 As shown, the first UE capability list may include the MIMO-ID associated with MIMO, the UE-CapabilityMIMO-PerUE, and the XR-ID associated with XR, the UE-CapabilityXR-PerUE. The UE-CapabilityMIMO-PerUE includes terminal device-specific capability information related to the first identifier and the first feature, while the UE-CapabilityXR-PerUE includes terminal device-specific capability information related to the second identifier and the second feature. It should be understood that... Figure 8 The names of the information provided are merely examples and do not constitute a limitation on the naming of the information.

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

[0141]

[0142] In this context, UE-CapabilityPerUE-FeatureList is the first UE capability list, which can carry at least one set of terminal device-specific capability information related to at least one feature; maxNrofFeature is the maximum number of features, and its value can be an integer greater than or equal to 1; UE-CapabilityPerUE can carry a set of terminal device-specific capability information related to a feature, which may include terminal device-specific capability information and its identifier; featureCapabilityId is used to identify the feature or feature-related capability information or feature-related terminal device-specific capability information, such as a first identifier, a second identifier, etc.; featureCapability is used to carry the feature-related capability information or feature-related terminal device-specific capability information indicated by featureCapabilityId. The capability information can be a string, byte string, or bit string, and the content of featureCapability corresponding to different features can be different. In the above example, featureCapabilityId and / or featureCapability can be optional or required fields, and there is no restriction here. The number of UE-CapabilityPerUEs included in the first UE capability list can also be 0.

[0143] As an optional approach, the first UE capability list can be used to add or modify reported feature-specific capability information related to the terminal device. The first list may include at least one set of terminal device-specific capability information, each set of which may include a feature-related terminal device-specific capability and an identifier associated with that feature. Optionally, if the first list includes an identifier that the terminal device has not previously reported or that the network device has not stored, it signifies the addition of new feature capability information; if the first list includes an identifier that the terminal device has previously reported or that the network device has stored, it signifies updating or modifying the previous feature capability information.

[0144] The first UE capability list can also delete or release terminal device-specific capability information related to features through a second list. The second list may include an identifier associated with at least one feature or at least one feature-related capability information.

[0145] Based on the above scheme, the information cells carrying the first UE capability list can be as follows:

[0146]

[0147] Among them, UE-CapabilityPerUEFeatureToAddModList is the first list, which may include at least one UE-CapabilityPerUE. A UE-CapabilityPerUE may include a set of terminal device-specific capability information, specifically including an identifier associated with a feature and terminal device-specific capability information related to that feature.

[0148] UE-CapabilityPerUEFeatureToReleaseList is a second list that may include an identifier associated with at least one feature, used to indicate the deletion or release of terminal device-specific capability information related to that feature.

[0149] 2. Frequency band specific capability information

[0150] Optionally, the first capability information may include band-specific capability information for at least one frequency band. Taking the first frequency band as an example, the first frequency band-specific capability information includes the band identifier (bandNR) of the first frequency band and the MIMO parameters of the first frequency band.

[0151] One or more of the following: (mimo-ParametersPerBand), extended cyclic prefix capability (extendedCP), modulation order capability (e.g., pdsch-256QAM-FR2 or pusch-256QAM), and bandwidth-related capability (e.g., bwp-WithoutRestriction, bwp-SameNumerology, or bwp-DiffNumerology). The capability information exemplified above can be understood as basic capability information specific to the first frequency band.

[0152] Optionally, the frequency-band specific capability information may further include at least one characteristic-related frequency-band specific capability information, and identifiers associated with each of the at least one characteristic. The identifiers associated with each of the at least one characteristic can be understood as identifiers associated with each of the at least one characteristic-related frequency-band specific capability information. The frequency-band specific capability information may also include a first identifier and frequency-band specific capability information related to a first characteristic, wherein the frequency-band specific capability information related to the first characteristic may include frequency-band specific capability information related to at least one frequency band. If other characteristics, such as a second characteristic, exist, the frequency-band specific capability information may also include a second identifier and frequency-band specific capability information related to the second characteristic, wherein the frequency-band specific capability information related to the second characteristic may include frequency-band specific capability information related to at least one frequency band, and so on.

[0153] Optionally, the capability information specific to the first frequency band related to the first characteristic may include an identifier of the first frequency band (e.g., the band number of the first frequency band) or an index of the first frequency band, the index of which relates to the position of the first frequency band within at least one frequency band included in the first capability information. For example, if the first capability information includes 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, then the index of the first frequency band is 0 (or 1).

[0154] 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 frequency bands 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. In other words, the number of frequency bands in the capability information of the frequency bands in the basic information is the same as the number of frequency bands in the capability information of the frequency bands related to each characteristic (e.g., the first characteristic), and the order is the same.

[0155] The basic capability information includes frequency band-specific capability information (e.g., the first frequency band), and the frequency band-specific capability information related to each characteristic (e.g., the first characteristic, the second characteristic, etc.) combined to form the terminal device's capability information on the first frequency band. In other words, the terminal device should support the frequency band-specific capability information in its reported basic capability information, as well as the frequency band-specific capability information related to each characteristic (e.g., the first characteristic, the second characteristic, etc.), on that frequency band.

[0156] In one possible implementation, the frequency band-specific capability information may include a second UE capability list. This second UE capability list may include frequency band-specific capability information related to at least one feature, and identifiers associated with each of these features. For example, taking a first frequency band as an example, the second UE capability list may include a first identifier and frequency band-specific capability information related to a first feature. This first feature-related frequency band-specific capability information includes frequency band-specific capability information related to the first feature of at least one frequency band. Optionally, the second UE capability list may also include a second identifier and frequency band-specific capability information related to a second feature, a third identifier and frequency band-specific capability information related to a third feature, etc. The second feature-related frequency band-specific capability information includes frequency band-specific capability information related to the second feature of at least one frequency band, and the third feature-related frequency band-specific capability information includes frequency band-specific capability information related to the third feature of at least one frequency band.

[0157] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as follows: Figure 9As shown, the second UE capability list includes the MIMO-ID associated with MIMO, the XR-ID associated with UE-CapabilityMIMO-PerBand, and the XR-ID and XR-PerBand associated with UE-CapabilityMIMO-PerBand. UE-CapabilityMIMO-PerBand includes band-specific capability information related to at least one band's first characteristic, and UE-CapabilityXR-PerBand includes band-specific capability information related to at least one band's second characteristic. It should be understood that... Figure 9 The names of the information provided are merely examples and do not constitute a limitation on the naming of the information.

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

[0159]

[0160] In this context, `UE-CapabilityPerBandFeatureList` is the second UE capability list, which can carry at least one set of frequency-band-specific capability information related to at least one feature; `UE-CapabilityPerBand` can carry a set of frequency-band-specific capability information related to a feature, which may include frequency-band-specific capability information and its identifier; `featureCapabilityId` is used to identify a feature or feature-related capability information or feature-related frequency-band-specific capability information; `featureCapability` is used to carry the feature-related capability information or feature-related frequency-band-specific capability information indicated by `featureCapabilityId`. The capability information can be carried as a string, byte string, or bit string, and the content of `featureCapability` may differ for different features. In the above example, `featureCapabilityId` and / or `featureCapability` can be optional or required fields, without restriction. The number of `UE-CapabilityPerBand` entries in the second UE capability list can also be 0.

[0161] As an optional approach, the second UE capability list can add to or modify the reported feature-related frequency-band specific capability information through a third list. The third list can include at least one set of frequency-band specific capability information, each set including a feature-related frequency-band specific capability and an identifier associated with that feature. Optionally, if the third list includes an identifier that the terminal device has not previously reported or that the network device has not stored, it means adding new feature capability information; if the third list includes an identifier that the terminal device has previously reported or that the network device has stored, it means updating or modifying the previous feature capability information.

[0162] The second UE capability list can also delete or release feature-specific or feature-related frequency band-specific capability information through a fourth list. The fourth list may include at least one feature or an identifier associated with at least one feature.

[0163] Based on the above scheme, the information cells carrying the second UE capability list can be as follows:

[0164]

[0165] Among them, UE-CapabilityPerBandFeatureToAddModList is a third list, which may include at least one UE-CapabilityPerBand. A UE-CapabilityPerBand may include a set of frequency band-specific capability information, specifically including an identifier associated with a feature and frequency band-specific capability information related to that feature.

[0166] UE-CapabilityPerBandFeatureToReleaseList is a fourth list, which may include an identifier associated with at least one feature to indicate the deletion or release of frequency band-specific capability information related to that feature.

[0167] 3. Capability information specific to frequency band combinations

[0168] Optionally, the first capability information may include band-specific capability information for at least one band combination. Taking the first band combination as an example, the band-specific capability information may include one or more of the following: a band list specific to the first band combination, CA parameters, MRDC parameters, power rating, etc. The capability information exemplified above can be understood as basic capability information specific to the first band combination.

[0169] Optionally, the capability information specific to a frequency band combination may further include capability information specific to at least one characteristic related to the frequency band combination, and identifiers associated with each of the at least one characteristic. The identifiers associated with each of the at least one characteristic can be understood as identifiers associated with the capability information specific to the frequency band combination related to each of the at least one characteristic. Taking a first frequency band combination as an example, the capability information specific to the frequency band combination may further include a first identifier and capability information specific to the first frequency band combination related to the first characteristic. If other characteristics, such as a second characteristic, exist, the capability information specific to the first frequency band combination may further include capability information specific to the first frequency band combination related to the other characteristics and identifiers associated with the other characteristics.

[0170] Optionally, the capability information specific to the first frequency band combination related to the first characteristic may include a list of frequency bands included in the first frequency band combination (e.g., a BandList), or may include an index of the first frequency band combination, the index of which is related to the position of the first frequency band combination in at least one frequency band combination included in the first capability information. For example, if the first capability information includes capability information for the first frequency band combination, capability information for the second frequency band combination, and capability information for the third frequency band combination, then the index of the first frequency band combination is 0 (or 1).

[0171] Optionally, the number of frequency band combinations included in the basic capability information of 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 frequency band combinations 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 of frequency band combinations in the capability information of frequency band combinations in the basic information is the same as the number of frequency band combinations in the capability information of frequency band combinations related to each characteristic (e.g., the first characteristic), and the order is the same.

[0172] 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.), 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 it reports, as well as 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.

[0173] In one possible implementation, the capability information specific to a frequency band combination may include a third UE capability list. This third UE capability list may include capability information specific to the frequency band combination related to at least one characteristic, and identifiers associated with each of these characteristics. For example, taking a first frequency band combination as an example, the third UE capability list may include capability information specific to the first frequency band combination related to a first identifier and a first characteristic. Optionally, the third UE capability list may also include capability information specific to the first frequency band combination related to a second identifier and a second characteristic, a third identifier and a third characteristic, and so on.

[0174] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as follows: Figure 10 As shown, the third UE capability list includes the MIMO-ID associated with MIMO and the UE-CapabilityMIMO-PerBC, and the XR-ID associated with XR and the UE-CapabilityXR-PerBC. The UE-CapabilityMIMO-PerBC includes capability information specific to the first frequency band combination related to the first characteristic, and the UE-CapabilityXR-PerBC includes capability information specific to the first frequency band combination related to the second characteristic. It should be understood that... Figure 10 The names of the information provided are merely examples and do not constitute a limitation on the naming of the information.

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

[0176]

[0177] Among them, bandCombinationFeatureList is the third UE capability list, which can carry at least one set of capability information specific to a frequency band combination related to at least one feature; UE-CapabilityPerBC can carry a set of capability information specific to a frequency band combination related to a feature, and a set of capability information specific to a frequency band combination related to a feature can include capability information specific to the frequency band combination and its identifier;

[0178] featureCapabilityId is used to identify a feature or feature-related capability information, or feature-related capability information specific to a combination of frequency bands.

[0179] `featureCapability` is used to carry feature-related capability information or feature-related frequency band-specific capability information indicated by `featureCapabilityId`. The capability information can be a string, byte string, or bit string, and the content of `featureCapability` can differ for different features. In the example above, `featureCapabilityId` and / or `featureCapability` can be optional or required fields, without restriction. The number of `UE-CapabilityPerBand` entries in the third UE capability list can also be 0.

[0180] As an optional approach, the third UE capability list can add or modify the reported feature-related frequency band combination-specific capability information through a fifth list. The fifth list can include at least one set of capability information specific to the first frequency band combination. Each set of capability information specific to the first frequency band combination can include a feature-related capability information specific to the first frequency band combination and an identifier associated with that feature. Optionally, if the fifth list includes an identifier that the terminal device has not previously reported or that the network device has not stored, it means adding new feature capability information; if the fifth list includes an identifier that the terminal device has previously reported or that the network device has stored, it means updating or modifying the previous feature capability information.

[0181] The third UE capability list can also be a sixth list by deleting or releasing capability information specific to a feature or a feature-related frequency band combination. The sixth list may include at least one feature or an identifier associated with at least one feature.

[0182] Based on the above scheme, the information cell carrying third-party capability information can be as follows:

[0183]

[0184]

[0185] Among them, bandCombinationFeatureToAddModList is the fifth list, which may include at least one UE-CapabilityPerBC. A UE-CapabilityPerBC may include a set of capability information specific to the first frequency band combination, specifically including an identifier associated with a feature and capability information specific to the first frequency band combination related to that feature.

[0186] The bandCombinationFeatureToReleaseList is the sixth list, which may include an identifier associated with at least one feature to indicate the deletion or release of capability information specific to the first frequency band combination associated with the at least one feature.

[0187] 4. Feature set

[0188] The feature set set is used to provide a pool of downlink and / or uplink feature sets. The first capability information may include a second feature set set, where one or more feature sets may include capability information specific to a frequency band within a frequency band combination. For example, the second feature set set may be FeatureSets, FeatureSetsDownlink, or FeatureSetsUplink. For instance, one or more downlink feature sets in the second feature set set may include one or more of the following: intraband frequency separation capability, scaling factor, synchronization signal / physical broadcast channel block (SSB) related capabilities (e.g., scellWithoutSSB or csi-RS-MeasSCellWithoutSSB), search space related capabilities (e.g., type1-3-CSS or searchSpaceSharingCA-DL), etc. For example, one or more uplink features in the second feature set may include one or more of the following: scaling factor, in-band frequency separation capability, search space correlation capability (e.g., searchSpaceSharingCA-UL), sounding reference signal (SRS) related information (e.g., supportedSRS-Resources), and supplementary uplink carrier correlation capability (e.g., dynamicSwitchSUL or simultaneousTxSUL-NonSUL). The capability information exemplified above can be understood as the basic capabilities included in the second feature set.

[0189] Optionally, the first capability information may further include at least one feature set related to a characteristic, and at least one identifier associated with each characteristic. The identifier associated with each of the at least one characteristic can be understood as the identifier associated with each of the at least one feature set related to that characteristic. Taking a first characteristic as an example, the first capability information may further include a first identifier and a first feature set related to the first characteristic. The first feature set is used to provide a pool of downlink and / or uplink feature sets related to the first characteristic. The first feature set includes at least one feature set. Any feature set in the first feature set includes capability information related to the first characteristic in the frequency band of the frequency band combination. It is understood that if other characteristics, such as a second characteristic, exist, the first capability information may further include a third feature set related to the second characteristic, wherein the third feature set is used to provide a pool of downlink and / or uplink feature sets related to the second characteristic. Any feature set in the third feature set includes capability information related to the second characteristic in the frequency band of the frequency band combination.

[0190] In one example, the different feature sets in the first capability information include the same number of feature sets. For instance, the number of feature sets included in the first feature set can be the same as the number of feature sets included in the second feature set. The number of feature sets included in the first feature set can also be the same as the number of feature sets included in other feature set sets related to other characteristics (e.g., a third feature set related to the second characteristic).

[0191] The aforementioned feature set (e.g., the first feature set, the second feature set, etc.) can be a set of downlink feature sets for downlink transmission capability (FeatureSetsDownlink) or a set of uplink feature sets for uplink transmission capability (FeatureSetsUplink).

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

[0193] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as follows: Figure 11 As shown, the downlink feature set and uplink feature set are related to basic capability information. MIMO-ID is the first identifier, and FeatureSetsDownlinkMIMO is the downlink feature set related to the first feature; XR-ID is the second identifier, and FeatureSetsDownlinkXR is the downlink feature set related to the second feature. Similarly, MIMO-ID is the first identifier, and FeatureSetsUplinkMIMO is the uplink feature set related to the first feature; XR-ID is the second identifier, and FeatureSetsUplinkXR is the uplink feature set related to the second feature. It should be understood that... Figure 11 The names of the information provided are merely examples and do not constitute a limitation on the naming of the information.

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

[0195]

[0196] In this configuration, `featureSetsDownlinkFeatureList` is the fourth UE capability list, which can carry at least one feature-related downlink feature set; `FeatureSetsDownlinkFeature` can carry a feature-related downlink feature set and its identifier; `featureCapabilityId` is used to identify the feature or feature-related capability information or feature set capability information; `featureCapability` is used to carry the feature-related capability information or feature set indicated by `featureCapabilityId`; `maxDownlinkFeatureSets` indicates the maximum number of downlink feature sets included; and `FeatureSetDownlinkFeature` is used to carry one downlink feature set from the feature-related feature set, which includes the terminal device's capability information on a downlink frequency band in a frequency band combination. The capability information can be carried as a string, byte string, or bit string, and the content of `featureCapability` may differ for different features. In the above example, `featureCapabilityId` and / or `featureCapability` may be optional or required fields, and no restriction is placed here.

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

[0198]

[0199] In this configuration, `featureSetsUplinkFeatureList` is the fifth UE capability list, which can carry at least one feature-related uplink feature set; `FeatureSetsUplinkFeature` can carry a feature-related uplink feature set and its identifier; `featureCapabilityId` is used to identify the feature or feature-related capability information or feature set capability information; `featureCapability` is used to carry the feature-related capability information or feature set indicated by `featureCapabilityId`; `maxUplinkFeatureSets` indicates the maximum number of uplink feature sets included; and `FeatureSetUplinkFeature` is used to carry one uplink feature set from the feature-related feature set, which includes the terminal device's capability information on one uplink frequency band in the frequency band combination. The capability information can be carried as a string, byte string, or bit string, and the content of `featureCapability` can differ for different features. In the above example, `featureCapabilityId` and / or `featureCapability` can be optional or required fields, without restriction.

[0200] As described in the foregoing technical background, the first capability information can indicate the feature set identifier corresponding to the frequency band in the frequency band combination. For example, the feature set combination corresponding to the frequency band combination includes the feature set identifier associated with each frequency band in the frequency band combination. In this application, the feature set identifier can indicate that the terminal device supports the feature set set related to each feature (e.g., the first feature, the second feature, etc.) and the feature set set related to the basic capability information in the corresponding frequency band of the frequency band combination, which are located at the same position. For example, the feature set identifier associated with the second frequency band in the second frequency band combination can indicate the feature set in the feature set related to the first feature and the feature set set related to the basic capability information in the second frequency band of the second frequency band combination, which are located at the same position. For example, if the feature set identifier is 1, it indicates the first feature set in the feature set set related to the first feature and the first feature set in the feature set set related to the basic capability information. If other features exist, the feature set identifier associated with the second frequency band in the second frequency band combination can indicate the feature set in the feature set set related to other features located at the same position in the second frequency band of the second frequency band combination.

[0201] Specifically, the downlink 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 downlink feature set set related to the first characteristic and the downlink feature set set related to basic capability information on the second frequency band in the second frequency band combination. If other characteristics exist, the downlink feature set identifier associated with the second frequency band in the second frequency band combination can indicate the downlink feature set located at the same position in the downlink feature set set related to other characteristics on the second frequency band in the second frequency band combination. Similarly, the uplink 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 uplink feature set set related to the first characteristic and the uplink feature set set related to basic capability information on the second frequency band in the second frequency band combination. If other characteristics exist, the uplink feature set identifier associated with the second frequency band in the second frequency band combination can indicate the uplink feature set located at the same position in the uplink feature set set related to other characteristics on the second frequency band in the second frequency band combination. Here, whether the terminal device supports the feature set in the feature set set related to other characteristics depends on whether the terminal device supports the other characteristics.

[0202] by Figure 11 For example, assuming that in the second frequency band combination, the second frequency band is associated with a first downlink feature set identifier and a first uplink feature set identifier, the first downlink feature set identifier indicates the second downlink feature set in the downlink feature set set, and the first uplink feature set identifier indicates the first uplink feature set in the uplink feature set set, then the terminal device in the second frequency band combination supports the second downlink feature set in the downlink transmission direction related to the first characteristic and the second downlink feature set in the basic capability information related downlink feature set set. Optionally, if other characteristics exist, it can also support the second downlink feature set in the downlink feature set set related to other characteristics. In the uplink transmission direction, it supports the first uplink feature set in the uplink feature set set related to the first characteristic and the first uplink feature set in the uplink feature set set related to the basic capability information. Optionally, if other characteristics exist, it can also support the first uplink feature set in the uplink feature set set related to other characteristics. Figure 12 As shown, please refer to the connecting lines in the figure.

[0203] 5. Carrier feature set set

[0204] A carrier feature set is used to provide a pool of uplink and / or downlink carrier feature sets. The carrier feature set includes capability information of the terminal device on a carrier within the feature set. First capability information may include a second carrier feature set, and one or more carrier feature sets in the second carrier feature set may include capability information of a carrier on a frequency band in a frequency band combination. For example, the second carrier feature set may be featureSetsDownlinkPerCC or featureSetsUplinkPerCC. For instance, one or more downlink carrier feature sets in the second carrier feature set may include one or more of the following: supported subcarrier spacing (DL), supported bandwidth (DL), maxNumberMIMO-LayersPDSCH, and supported modulation order (DL). As another example, one or more uplink carrier feature sets in the second carrier feature set may include the carrier subcarrier spacing.

[0205] (supported Subcarrier Spacing UL), bandwidth (supported Bandwidth UL), MIMO-related capabilities (e.g., maxNumberMIMO-LayersCB-PUSCH or maxNumberSRS-ResourcePerSet), modulation order

[0206] One or more of the following: (supportedModulationOrderUL), etc. The capability information exemplified above can be understood as the basic capabilities included in the second feature set.

[0207] Optionally, the first capability information may further include at least one set of carrier feature sets related to a characteristic and at least one identifier associated with each characteristic. The identifier associated with each of the at least one characteristic can be understood as the identifier associated with each set of carrier feature sets related to the at least one characteristic. Taking a first characteristic as an example, the first capability information may further include a first identifier and a first set of carrier feature sets related to the first characteristic. The first set of carrier feature sets is used to provide a pool of downlink and / or uplink carrier feature sets related to the first characteristic. The first set of carrier feature sets includes at least one carrier feature set. Any carrier feature set in the first set of carrier feature sets includes capability information related to the first characteristic on a carrier in a frequency band within a frequency band combination, or includes capability information related to the first characteristic on a carrier within a feature set. It is understood that if other characteristics, such as a second characteristic, exist, the first capability information may further include a third set of carrier feature sets related to the second characteristic, wherein the third set of carrier feature sets is used to provide a pool of downlink and / or uplink carrier feature sets related to the second characteristic. Any carrier feature set in the third set of carrier feature sets includes capability information related to the second characteristic on a carrier in a frequency band within a frequency band combination.

[0208] In one example, the number of carrier feature sets included in different carrier feature set sets in the first capability information is the same. For example, the number of carrier feature sets included in the first carrier feature set set can be the same as the number of carrier feature sets included in the second carrier feature set set. The number of carrier feature sets included in the first carrier feature set set can also be the same as the number of carrier feature sets included in other characteristic-related carrier feature set sets (e.g., the third carrier feature set set related to the second characteristic).

[0209] The aforementioned carrier feature set (e.g., the first carrier feature set, the second carrier feature set, etc.) can be a set of downlink carrier feature sets (i.e., FeatureSetDownlinkPerCC) for downlink transmission capability, or a set of uplink carrier feature sets (i.e., FeatureSetUplinkPerCC) for uplink transmission capability.

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

[0211] Taking MIMO as the first characteristic and XR as the second characteristic as an example, the first capability information can be as follows: Figure 13 As shown, the downlink carrier feature set and the uplink carrier feature set are related to basic capability information. MIMO-ID is the first identifier, FeatureSetsDownlinkPerCC-MIMO is the downlink carrier feature set related to the first characteristic, XR-ID is the second identifier, and FeatureSetsDownlinkPerCC-XR is the downlink carrier feature set related to the second characteristic. Similarly, MIMO-ID is the first identifier, FeatureSetsUplinkPerCC-MIMO is the uplink carrier feature set related to the first characteristic, and XR-ID is the second identifier, and FeatureSetsUplinkPerCC-XR is the uplink carrier feature set related to the second characteristic. It should be understood that... Figure 13 The names of the information provided are merely examples and do not constitute a limitation on the naming of the information.

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

[0213]

[0214] In this configuration, `featureSetsDownlinkPerCC-FeatureList` is the sixth UE capability list, which can carry at least one feature-related downlink carrier feature set. `FeatureSetDownlinkPerCC-Feature` can carry a feature-related downlink carrier feature set and its identifier. `featureCapabilityId` identifies the feature, feature-related capability information, or feature-related carrier feature set capability information. `featureCapability` carries the feature-related capability information or feature-related carrier feature set indicated by `featureCapabilityId`. `maxPerCC-FeatureSets` indicates the maximum number of carrier feature sets included. `FeatureSetDownlinkPerCC-Feature` carries one downlink carrier feature set from the feature-related feature set, including the terminal device's capability information in one downlink frequency band of the frequency band combination. The capability information can be a string, byte string, or bit string, and the content of `featureCapability` can differ for different features. In the above example, `featureCapabilityId` and / or `featureCapability` can be optional or required fields, without restriction.

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

[0216]

[0217] Among them, featureSetsUplinkPerCC-FeatureList is the seventh UE capability list, which can carry at least one feature-related uplink carrier feature set; FeatureSetsUplinkPerCC-Feature can carry a feature-related uplink carrier feature set and its identifier.

[0218] featureCapabilityId is used to identify a feature or feature-related capability information or a feature-related carrier feature set capability information;

[0219] `featureCapability` is used to carry feature-related capability information or a set of carrier feature sets indicated by `featureCapabilityId`; `maxPerCC-FeatureSets` indicates the maximum number of carrier feature sets included; `FeatureSetUplinkPerCC-Feature` is used to carry an uplink carrier feature set from the feature-related feature set, which includes the terminal device's capability information in an uplink frequency band within the frequency band combination. The capability information can be carried as a string, byte string, or bit string, and the content of `featureCapability` may differ for different features. In the above example, `featureCapabilityId` and / or `featureCapability` may be optional or required fields, without restriction.

[0220] As described in the foregoing technical background, the first capability information can indicate the carrier feature set identifier corresponding to the carrier of the frequency band in the frequency band combination. For example, the feature set corresponding to the frequency band in the frequency band combination includes the carrier feature set identifier associated with each carrier in that frequency band. In this application, the carrier feature set identifier can indicate that the terminal device supports carrier feature sets located at the same position in the carrier feature set related to each characteristic (e.g., the first characteristic, the second characteristic, etc.) and the carrier feature set related to the basic capability information on the carrier of the frequency band in the frequency band combination. For example, the carrier feature set identifier associated with the third frequency band in the third frequency band combination can indicate that the carrier feature set located at the same position in the carrier feature set related to the first characteristic and the carrier feature set related to the basic capability information on the carrier of the third frequency band in the third frequency band combination. For example, if the carrier feature set identifier is 1, it indicates that the first carrier feature set in the carrier feature set related to the first characteristic and the first carrier feature set in the carrier feature set related to the basic capability information are supported. Optionally, if other characteristics also exist, carrier feature sets located at the same position in the carrier feature set related to other characteristics can also be supported.

[0221] Specifically, the downlink carrier feature set identifier associated with the first carrier of the third frequency band in the third frequency band combination can indicate that the carrier feature set at the same position in the downlink carrier feature set related to the first characteristic and the downlink carrier feature set related to basic capability information on the first carrier of the third frequency band in the third frequency band combination supports downlink carrier feature sets at the same position. Optionally, if other characteristics exist, downlink carrier feature sets at the same position in the downlink carrier feature set sets related to other characteristics can also be supported. The uplink feature set identifier associated with the third frequency band in the third frequency band combination can indicate that the first carrier of the third frequency band in the third frequency band combination supports uplink carrier feature sets at the same position in the uplink carrier feature set set related to the first characteristic and the uplink carrier feature set set related to basic capability information. Optionally, if other characteristics exist, uplink carrier feature sets at the same position in the uplink carrier feature set sets related to other characteristics can also be supported.

[0222] by Figure 13 For example, assuming that the first carrier of the third frequency band in the third frequency band combination is associated with a first downlink carrier feature set identifier and a first uplink carrier feature set identifier, where the first downlink carrier feature set identifier indicates the first downlink carrier feature set in the downlink carrier feature set set, and the first uplink carrier feature set identifier indicates the second uplink carrier feature set in the uplink carrier feature set set, then the terminal device, in the third frequency band combination, supports the first downlink carrier feature set in the downlink transmission direction related to the first characteristic and the first downlink carrier feature set in the basic capability information related downlink carrier feature set set. Optionally, if other characteristics exist, it can also support the first downlink carrier feature set in the downlink carrier feature set set related to other characteristics, and in the uplink transmission direction, it supports the second uplink carrier feature set in the uplink carrier feature set set related to the first characteristic and the second uplink carrier feature set in the uplink carrier feature set set related to the basic capability information. Figure 14 As shown, please refer to the connecting lines in the figure.

[0223] The second structure includes information cells carrying at least one feature-related capability information and information cells carrying basic capability information. The information cell containing feature-related capability information may include an identifier associated with that feature, as well as capability information specific to that feature at each level. In this structure, it is not necessary to repeatedly include the feature-related identifier at each level.

[0224] For example, taking a first characteristic as an example, the first capability information includes first information related to the first characteristic. The first information includes a first identifier and capability information at various levels related to the first characteristic. Specifically, the first information includes a 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, or a first carrier feature set. Wherein, any feature set in the first feature set includes capability information related to the first characteristic on a frequency band within the frequency band combination. Any carrier feature set in the first carrier feature set includes capability information related to the first characteristic on a carrier within the feature set. Optionally, the first capability information may also include third information related to a second characteristic, etc.

[0225] Optionally, the first capability information may also include second information. The second information may include basic capability information at various levels, such as terminal device-specific basic capability information (e.g., access layer version information, PDCP layer capabilities, etc., see above for details), frequency band-specific basic capability information (e.g., extended CP, modulation scheme, power level, MIMO capability, etc., see above for details), frequency band combination-specific basic capability information (e.g., carrier aggregation capability, dual connection (DC) capability, power level, etc., see above for details), a second feature set, or a second carrier feature set. Any feature set in the second feature set includes basic capability information on the frequency band within the frequency band combination, such as intraBandFreqSeparation, scalingFactor, scellWithoutSSB, etc., see above for details. Any carrier feature set in the second carrier feature set includes basic capability information on one carrier within the feature set, such as subcarrier spacing, bandwidth, etc., see above for details.

[0226] The aforementioned feature set (e.g., the first feature set, the second feature set, etc.) can be a downlink feature set of downlink transmission capability.

[0227] (FeatureSetsDownlink) can also be a set of uplink feature sets representing uplink transmission capabilities (FeatureSetsUplink). The aforementioned carrier feature sets...

[0228] (For example, the first carrier feature set, the second carrier feature set, etc.) can be the downlink carrier feature set of downlink transmission capability (i.e., FeatureSetDownlinkPerCC) or the uplink carrier feature set of uplink transmission capability (i.e., FeatureSetUplinkPerCC).

[0229] 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 MIMO as the first feature and XR as the second feature, the first capability information can be as follows: Figure 15 As shown. Here, MIMO-ID is the first identifier, and MIMO-related UE capabilities (UE-CapabilityForMIMO) include capability information for each MIMO-related level; XR-ID is the second identifier, and XR-related UE capabilities (UE-CapabilityForXR) include capability information for each XR-related level. Optionally, the hierarchical structure of XR-related UE capabilities is similar to that of MIMO-related UE capabilities. It should be understood that... Figure 15 The names of the information provided are merely examples and do not constitute a limitation on the naming of the information.

[0230] It should be noted that MIMO-ID can be outside of MIMO-related UE capabilities (UE-CapabilityForMIMO), and XR-ID can be outside of XR-related UE capabilities (UE-CapabilityForXR), such as... Figure 15 As shown. Alternatively, MIMO-ID can also be found in MIMO-related UE capabilities (UE-CapabilityForMIMO), and XR-ID can be found in XR-related UE capabilities (UE-CapabilityForXR), without specific limitations here.

[0231] Although the capability information related to each feature and the basic capability information are decoupled at the IE level, there is a correlation between the capability information related to each feature and the information in the basic capability information.

[0232] For example, the capability information related to each feature is associated with the terminal device-specific capability information within the basic capability information. In other words, the terminal device supports both the terminal device-specific capability information within the capability information related to each feature and the terminal device-specific basic capability information. For instance, taking the first feature as an example, the terminal device supports both the terminal device-specific capability information within the capability information related to the first feature and the terminal device-specific basic capability information.

[0233] For example, the capability information related to each characteristic is associated with the frequency band-specific capability information within the basic capability information. Taking the first frequency band as an example, the capability information related to each characteristic is associated with the first frequency band-specific capability information within the basic capability information. In other words, the terminal device supports both the first frequency band-specific capability information and the first frequency band-specific basic capability information within the capability information related to each characteristic on the first frequency band. For instance, taking the first characteristic as an example, the terminal device supports both the first frequency band-specific capability information and the first frequency band-specific basic capability information within the capability information related to the first characteristic on the first frequency band.

[0234] For example, the capability information related to each characteristic is associated with the capability information specific to the frequency band combination within the basic capability information. Taking the first frequency band combination as an example, the capability information related to each characteristic is associated with the capability information specific to the first frequency band combination within the basic capability information. In other words, the terminal device supports the capability information related to each characteristic and the capability information specific to the first frequency band combination within the basic capability information on the first frequency band combination. For example, taking the first characteristic as an example, the terminal device supports the capability information specific to the first frequency band combination within the capability information related to the first characteristic and the capability information specific to the first frequency band combination within the basic capability information on the first frequency band combination.

[0235] For example, there is a correlation between the feature sets in the capability information related to each characteristic and the feature sets in the basic capability information. Taking the second frequency band in the second frequency band combination as an example, there is a correlation between the feature sets associated with the second frequency band in the capability information related to each characteristic and the feature sets associated with the second frequency band in the basic capability information. In other words, the terminal device supports the feature sets associated with the second frequency band in the capability information related to each characteristic and the feature sets associated with the second frequency band in the basic capability information on the second frequency band in the second frequency band combination. For example, taking the first characteristic as an example, the terminal device supports the first feature set in the capability information related to the first characteristic and the second feature set in the basic capability information on the second frequency band in the second frequency band combination. The band-related feature sets can be indicated by feature set identifiers, which will not be elaborated here. Across frequency bands in the second frequency band combination, the terminal device supports the feature sets at the same positions corresponding to the frequency bands in the second frequency band combination in the first information, and the feature sets at the same positions corresponding to the frequency bands in the second frequency band combination in the second information.

[0236] For example, the carrier feature sets in the capability information related to each characteristic and the basic capability information are correlated. Taking the first carrier of the third frequency band in the third frequency band combination as an example, the carrier feature sets associated with the first carrier of the third frequency band in the capability information related to each characteristic and the carrier feature sets associated with the first carrier of the third frequency band in the basic capability information are correlated. In other words, the terminal device supports the carrier feature sets associated with the first carrier of the third frequency band in the capability information related to each characteristic and the carrier feature sets associated with the first carrier of the third frequency band in the basic capability information on the first carrier of the third frequency band in the third frequency band combination. For example, taking the first characteristic as an example, the terminal device supports the first carrier feature set in the first information and the second carrier feature set in the second information on the first carrier of the third frequency band in the third frequency band combination. The carrier-associated feature sets can be indicated by carrier feature set identifiers, which will not be elaborated here.

[0237] The following uses the first information and the second information as examples to introduce a scheme to establish a relationship between the information in the first information and the information in the second information.

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

[0239] In one possible approach, 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 may include the same frequency band identifier.

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

[0241] In another possible approach, the capability information specific to a first frequency band in the first information may include an index of the first frequency band, the index of which relates to the position of the first frequency band within at least one frequency band included in the second information. For example, if the first information includes capability information specific to a first frequency band, capability information specific to a second frequency band, and capability information specific to a third frequency band, then the index of the first frequency band is 0 (or 1).

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

[0243] In one possible approach, the capability information specific to the first frequency band combination in the first information includes a frequency band list indicating 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 may include the same frequency band list.

[0244] In another possible approach, 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 specific to the first frequency band combination related to the first characteristic in the first information. Optionally, the number of frequency band combinations included in the first information is the same as the number of frequency band combinations included in the second information.

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

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

[0247] In one possible approach, the position of the first 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 corresponding to the second frequency band in the second information. Optionally, the number of feature sets corresponding to the second frequency band in the second frequency band combination in the first information is the same as the number of feature sets corresponding to the second frequency band in the second information. The terminal device supports feature sets at the same position corresponding to frequency bands in the second frequency band combination in the first information, as well as feature sets at the same position corresponding to frequency bands in the second frequency band combination in the second information.

[0248] For example, taking frequency band combination 1 as an example, frequency band combination 1 includes frequency band 1 and frequency band 2, such as Figure 16 As shown, the feature sets connected by dashed lines have a correlation. According to... Figure 16 It can be seen that in the feature set combination set (second information) in the first capability information, the number of frequency band feature sets included in each feature set combination is the same as the number of frequency band feature sets included in each feature set combination at the same position in the feature set combination set set (first information) of the MIMO-related UE capabilities in the eighth UE capability list. For example Figure 16In both locations, frequency band combination 1 includes two feature sets (i.e., the feature set of frequency band 1 and the feature set of frequency band 2). The terminal device can support the feature sets at the same locations in frequency bands 1 and 2 within frequency band combination 1. That is, one capability supported by the terminal device on frequency band combination 1 is: on frequency band 1 of frequency band combination 1, it supports the first feature set associated with frequency band 1 in basic capability information and the first feature set associated with frequency band 1 in MIMO-related UE capability information; on frequency band 2 of frequency band combination 1, it supports the first feature set associated with frequency band 2 in basic capability information and the first feature set associated with frequency band 2 in MIMO-related UE capability information. Another capability supported by the terminal device on band combination 1 is that it supports the second feature set associated with band 1 of band combination 1 in the basic capability information and the second feature set associated with band 1 of band combination 1 in the MIMO-related UE capability information on band 1 of band combination 1. It also supports the second feature set associated with band 2 of band combination 1 in the basic capability information and the second feature set associated with band 2 of band combination 1 in the MIMO-related UE capability information on band 2 of band combination 1.

[0249] Another association method involves associating the first feature set with the second index. 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 in the second frequency band combination within the second information. The terminal device supports feature sets corresponding to frequency bands in the second frequency band combination within the first information, as well as feature sets with the same index corresponding to frequency bands in the second frequency band combination within the second information. For example, taking frequency band combination 1 as an example, frequency band combination 1 includes frequency band 1 and frequency band 2, such as... Figure 17 As shown. Assume index 0 represents the first feature set, index 1 represents the second feature set, index 2 represents the third feature set, and so on. According to... Figure 17It can be seen that in the MIMO-related UE capability information, the first feature set associated with band 1 of band combination 1 includes index 1, and the second feature set includes index 0. Similarly, the first feature set associated with band 2 of band combination 1 includes index 1, and the second feature set includes index 0. Therefore, one capability supported by the terminal device on band combination 1 is: supporting the first feature set associated with band 1 of basic capability information and the second feature set associated with band 1 of MIMO-related UE capability information on band 1; and supporting the first feature set associated with band 2 of basic capability information and the second feature set associated with band 2 of MIMO-related UE capability information on band 2 of band combination 1. Another capability supported by the terminal device on band combination 1 is that it supports the second feature set associated with band 1 of the basic capability information and the first feature set associated with band 1 of the MIMO-related UE capability information on band 1 of band combination 1. It also supports the second feature set associated with band 2 of the basic capability information and the first feature set associated with band 2 of the MIMO-related UE capability information on band 2 of band combination 1.

[0250] The above describes two structures for capability information.

[0251] In some scenarios, terminal devices can update capability information to network devices. Optionally, if the terminal device's basic capability information remains unchanged, and the update only involves adding or modifying feature-related capabilities, the terminal device can report the feature-related capability information but not the basic capability information. For example, the terminal device can send second capability information, which includes first indication information used to indicate whether to maintain, release, or add capabilities related to a first feature. Optionally, this second capability information may not include the basic capability information.

[0252] Taking the first structure described above as an example, the second capability information may include the first UE capability list to the seventh UE capability list, etc. The signaling structure of the first UE capability list to the seventh UE capability list can be found in the relevant description in the first structure described above, and will not be repeated here.

[0253] Taking the second structure mentioned above as an example, the second capability information may include capability information related to characteristics, such as the first information, but does not include the second information.

[0254] For example, scenarios where the basic capability information of a terminal device has not changed, and the terminal device updates its capability information only to add or modify feature-related capabilities include: when a connected terminal device enables or disables a new feature, its basic capability information may not change.

[0255] As an alternative approach, in the above update scheme, the terminal device may also indicate to the network device that the terminal device's basic capability information has not changed or remains unchanged.

[0256] It should be noted that the above Figures 8 to 17 The text omits some capability information at certain levels, for example, Figure 8 Information such as the supported frequency band list, supported BC list, feature set combination, and downlink feature set set is omitted from the capability information. Figure 9 Information included in the supported BC list, feature set combination, and downlink feature set set is omitted. Figure 10 Information included in the supported frequency band list, feature set combination, downlink feature set set, and other capability information is omitted. Figure 11 Information such as the supported frequency band list, supported BC list, feature set combination, and downlink feature set set is omitted from the capability information. Figure 12 Information specific to terminal devices, such as the list of supported frequency bands, the list of supported frequency bands (BCs), and the set of downlink feature sets, is omitted. Figure 13 Information such as the supported frequency band list, supported BC list, feature set combination, and downlink feature set set is omitted from the capability information. Figure 14 Information specific to terminal devices, such as the list of supported frequency bands, the list of supported frequency bands (BCs), and the set of downlink feature sets, is omitted. Figure 15 Information included in capability information such as downlink feature set, uplink feature set, downlink carrier feature set, and uplink carrier feature set is omitted. Figure 16 and Figure 17 Information specific to terminal devices, such as the list of supported frequency bands, the list of supported BCs, and the set of downlink feature sets, has been omitted. For details on the omitted information, please refer to [link to relevant documentation]. Figure 4 The displayed capability information. In addition... Figures 8-11 and Figure 13 They are combined with each other.

[0257] in addition, Figures 8 to 17 The information shown is only an example. In actual implementation, capability information may include information other than that shown in the diagram, or may include some of the information shown in the diagram, etc.

[0258] Currently, the reporting of newly added features can only be done after all features discussed in the 3GPP protocol version have been finalized, allowing for the determination of the data structure for encoding the terminal device's capability information. In this data structure, the position (or reporting order) of each feature's capability information within the terminal device's capability information is fixed. However, this application, by including identifiers corresponding to feature-related capability information within the terminal device's capability information, isolates the capability information of each feature from the terminal device's basic capability information, ensuring that the capability information of each feature is independent of each other. This decoupling of the reporting order (or reporting position) allows this application to flexibly add new feature capability information to the terminal device's capability information using identifiers. Compared to the method of reporting feature capability information in a fixed order (or fixed position), this application allows for the early development of a feature without waiting for other features to be finalized, thus adapting to product release and market rhythms.

[0259] Furthermore, with the solution of this application, the position (or reporting order) of the capability information of each feature in the capability information of the terminal device is not fixed. Therefore, for unsupported features, these features can be removed from the capability information of the terminal device, thereby reducing the capability reporting overhead of the terminal device.

[0260] Based on the same inventive concept as the method embodiments, this application provides a communication device, the structure of which can be as follows: Figure 18 As shown, it includes a communication unit 1601 and a processing unit 1602.

[0261] In one embodiment, the communication device can specifically be used to implement Figure 7 In the embodiments described, the method executed by the terminal device can be the terminal device itself, or a chip or chipset within the terminal device, or a part of a chip used to execute the relevant method function. Specifically, the processing unit 1602 is configured to receive a capability query message via the communication unit 1601, and to send first capability information of the terminal device. The first capability information includes a first identifier and capability information related to a first characteristic, wherein the first identifier is used to identify the first characteristic, or to identify capability information related to the first characteristic.

[0262] In one embodiment, the communication device can specifically be used to implement Figure 7 In the embodiments, the method executed by the network device can be the network device itself, or a chip or chipset within the network device, or a part of a chip used to execute the relevant method function. The processing unit 1602 is configured to send a capability query message via the communication unit 1601, and to receive first capability information from the terminal device. The first capability information includes a first identifier and capability information related to a first characteristic, wherein the first identifier is used to identify the first characteristic, or to identify capability information related to the first characteristic.

[0263] The module division in this application embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules. It is understood that the functions or implementations of the modules in the embodiments of this application can be further described in the relevant descriptions of the method embodiments.

[0264] In one possible approach, the communication device can be as follows: Figure 19 As shown, the device can be a communication device or a chip within a communication device, wherein the communication device can be the terminal device in the above embodiments or the network device in the above embodiments. The device includes a processor 1701 and a communication interface 1702, and may also include a memory 1703. The processing unit 1702 can be the processor 1701. The communication unit 1701 can be the communication interface 1702. Optionally, the processor 1701 and the memory 1703 can also be integrated together.

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

[0266] The processor 1701 is used to execute the program code stored in the memory 1703, specifically to perform the actions of the aforementioned processing unit 1602, which will not be described in detail here. The communication interface 1702 is specifically used to perform the actions of the aforementioned communication unit 1601, which will not be described in detail here.

[0267] This application embodiment does not limit the specific connection medium between the communication interface 1702, processor 1701, and memory 1703. This application embodiment... Figure 19The memory 1703, processor 1701, and communication interface 1702 are connected via a bus 1704. Figure 19 The connections between other components are shown in bold lines only and are not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, Figure 19 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0268] This application also provides a computer-readable storage medium for storing computer software instructions required to execute the processor, including a program required to execute the processor.

[0269] This application also provides a communication system, including methods for implementing... Figure 7 In the embodiments, a communication device for transmitting functions and for implementing Figure 7 The embodiment is a communication device with receiver function.

[0270] The above embodiments are applicable to scenarios where a terminal device reports its capability information to a network device. Based on the same inventive concept as the method embodiments, this application provides another communication method and apparatus, applicable to scenarios where a network device sends configuration information to a terminal device.

[0271] As mentioned earlier, with the continuous development of wireless communication technology, multiple versions of wireless communication technology protocols have been introduced. Generally speaking, the backward version introduces more new features than the forward version; for example, Release 16 (R16) introduces more new features than Release 15. These new features are also relative; the term "new" refers to the backward version relative to the forward version. For example, R16 introduced "Ultra-reliable and low latency communications (URLLC)" compared to R15; R17 introduced features such as "low-cost 5G terminals (Redcap)," "sidelink enhancements," and "mobility enhancements" compared to R16.

[0272] As communication protocol versions evolve and new features are introduced, the Radio Resource Control (RRC) protocol in 3GPP also expands accordingly. Currently, the RRC protocol expands according to version, with each version containing extended parameters for different features. These features are heavily coupled, resulting in high complexity in implementation. Specifically:

[0273] 1. The configurations related to different features are coupled with each other. For unsupported features, the terminal device implementation cannot completely cut off the configurations related to these features. It is still necessary to interpret the relevant configurations, which consumes memory and increases the implementation complexity.

[0274] 2. The configurations related to different features are coupled with each other. In terms of terminal implementation, it is not possible to implement features in advance. Instead, it is necessary to wait until all feature configurations in the version are finalized. For details, please refer to the description in the previous embodiment.

[0275] To address the aforementioned issues, configuration parameters related to different characteristics can be encapsulated together, with each characteristic's configuration parameter distinguished by an identifier corresponding to that characteristic. For example, configuration parameters related to a first characteristic can be contained within specific first information, identified by a first identifier. In this embodiment, parameters added in each version are isolated and designed according to characteristics. Compared to extending the RRC protocol by version, encapsulating characteristic-related parameters together achieves isolation between characteristics, enabling complete feature-based tailoring. For instance, based on R15, features extended in R16 do not need to be implemented; features extended in R17 can be implemented directly. Similarly, implementing a specific feature in R17 does not require parsing all parameters prior to that feature in R17, or implementing any other features in R17. Compared to extending the RRC protocol by version, implementing one or more features is less complex. Furthermore, due to the isolation between features in the same / different versions, development of specific features can begin without waiting for all features to be stable and the protocol to be finalized, shortening the development cycle.

[0276] Specifically, the network device can send a second message, and the terminal device can receive the second message accordingly. The second message may include parameters configured for the terminal device, which can operate based on these parameters. For example, the terminal device can perform uplink / downlink data transmission or uplink / downlink signaling transmission, or perform measurements, according to the configuration. For instance, the second message may include one or more of the following: 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 may include one or more parameters, 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.

[0277] RRC configuration parameters include configuration parameters for various levels. For example, an RRC reconfiguration message may include UE-specific parameters, such as radio bearer configuration. UE-specific parameters may also include other possible parameters, such as measurement configuration. Radio bearer configuration may include parameters for one or more signaling radio bearers (SRBs) and data radio bearers (DBRs). RRC reconfiguration messages may also include cell group-related parameters, which may include primary cell group-related configurations and secondary cell group-related configurations. Each cell group-related configuration may include configurations for one or more RLC bearers, MAC-related configurations, one or more buffer status report (BSR) configurations, PHY configurations, and configurations for one or more serving cells. The configurations for one or more serving cells may include primary cell configurations or secondary cell configurations. Serving cell configurations may also include configurations for one or more BWPs. Each BWP configuration may also include configurations for one or more channels. One or more channels can be physical uplink control channels (PUCCH), physical uplink shared channels (PUSCH), physical downlink control channels (PUCCH), physical downlink shared channels (PUSCH), etc. RRC reconfiguration messages may also include other configurations, which will not be described in detail here. In the embodiments of this application, the above-mentioned different configurations (e.g., radio bearer-related configurations, RLC bearer-related configurations, BSR-related configurations, serving cell-related configurations, BWP-related configurations, channel-related configurations, etc.) are referred to as configuration parameters of different levels (or grades, levels). In addition to the existing classification methods, level-related configurations may also include new levels added in the future. In the following description, parameters of different levels are illustrated using cell groups, serving cells, BWPs, or channels as examples.

[0278] The specific name of the second message is not limited in the embodiments of this application. For example, the second message may be an RRC reconfiguration message, an RRC recovery message, an RRC reconstruction message, an RRC connection establishment message, a system information (SI) message, etc.

[0279] The second message may also include a feature configuration list, which includes a first configuration identifier and first configuration parameters. The first configuration parameters include configuration parameters related to a first feature, and the first configuration identifier identifies the first feature or first information. Optionally, to characterize the correspondence between configuration parameters in the feature configuration list and basic configuration parameters, configuration parameters at a specific level related to a feature in the feature configuration list can be included in the corresponding information element definition of the basic configuration parameters. The terminal device combines the configuration parameters at a specific level related to a feature in the feature configuration list with the configuration parameters at that level in the basic configuration parameters, for example, as the complete configuration for that level. For example, if a second configuration parameter specific to BWP is added or extended in the first feature, this second configuration parameter can be included in the BWP information element definition in the basic configuration parameters (e.g., BWP, BWP-Uplink, BWP-UplinkCommon, BWP-UplinkDedicated, BWP-Downlink, BWP-DownlinkCommon, or BWP-UplinkDedicated information elements); as another example, if a third configuration parameter specific to the serving cell is added or extended in the second feature, this third configuration parameter specific to the serving cell can be included in the serving cell information element definition in the basic configuration parameters (e.g., ServingCellConfig, ServingCellConfigCommon, or ServingCellConfigCommonSIB information elements).

[0280] Specifically, taking the inclusion of RedCap feature-related configurations in an RRC reconfiguration message as an example, the following example can be used:

[0281]

[0282]

[0283] The system comprises three lists: `featureConfigList`, which contains configuration parameters for one or more features; `featureConfigToRemoveList`, which releases or removes configuration parameters for one or more features; and `featureConfigToAddModList`, which adds or modifies configuration parameters for one or more features. Both `featureConfigToRemoveList` and `featureConfigToAddModList` are optional; `featureConfigList` can directly contain one or more `FeatureConfigInfo` entries. `FeatureConfigInfo` configures the parameters for a feature and includes `featureConfigId` and `featureConfig`. `featureConfigId` is a configuration identifier (e.g., a first configuration identifier) ​​used to identify a feature or its associated configuration parameters. `featureConfig` carries the configuration parameters associated with the feature indicated by `featureConfigId`. These configuration parameters can be strings, byte strings, or bit strings, and the content of `featureConfig` can differ for different features.

[0284] Taking RedCap features as an example, when featureConfigId indicates a RedCap feature, the encoding / decoding of featureConfig is defined through FeatureConfigRedCap. FeatureConfigRedCap includes configuration parameters added / extended / related to the RedCap feature, which may include one or more of the following: terminal device-specific configuration parameters, cell group-specific configuration parameters, cell-specific configuration parameters, BWP-specific configuration parameters, etc. Specifically, FeatureConfigRedCap can be exemplified as follows:

[0285]

[0286] Here, `rrm-MeasRelaxationReportingConfig` is an example of terminal device-specific configuration parameters related to RedCap features; `CellGroupRedCap` is used to carry other configuration parameters related to RedCap features, which may include one or more of the following: cell group-specific configuration parameters, cell-specific configuration parameters, BWP-specific configuration parameters, 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 basic configuration parameters (e.g., `secondaryCellGroup`) include secondary cell group configuration parameters, and the RedCap feature configuration parameters (e.g., `CellGroupRedCap`) also include secondary cell group configuration parameters, then the terminal device's secondary cell group configuration parameters include both of the above parts.

[0287] Specifically, CellGroupRedCap and CellGroupConfig can be exemplified as follows:

[0288]

[0289]

[0290] Among them, cellGroupId is the cell group identifier, used to identify the cell group; SpCellConfigRedCap is used to carry the service cell-specific configuration parameters related to RedCap features (e.g., further carried in ServingCellConfigCommonRedCap); servCellIndex is the service cell identifier, used to identify the service cell.

[0291] 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 both of the above parts.

[0292] Specifically, ServingCellConfigCommonRedCap and ServingCellConfigCommon can be exemplified as follows:

[0293]

[0294]

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

[0296] Understandably, the parameters in BWP and other layers are similar, and will not be elaborated upon here. The parameter names in all the examples above are merely examples and do not limit the naming of each piece of information. The configuration parameters in the examples above can be optional or mandatory, depending on the specific circumstances of each parameter, and are not restricted in this embodiment.

[0297] The methods provided in this application are described above using terminal devices and network devices as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent relationships; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions of the methods provided in the above-described embodiments, the steps executed by the terminal device can be implemented by different functional entities constituting the terminal device. The steps executed by the network device can be implemented by different functional entities constituting the network device.

[0298] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0299] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations 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, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0300] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0301] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0302] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

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