Communication method and apparatus, and storage medium and program product

Abstract

Provided in the embodiments of the present application are a communication method and apparatus, and a storage medium and a program product. The method comprises: a terminal device receiving first information, wherein the first information is used for querying capability information of the terminal device; and the terminal device further sending second information, wherein the second information is used for indicating M capability information sets supported by the terminal device, the second information comprises at least one frequency band combination supported by the terminal device, each of the at least one frequency band combination is associated with one or more of the M capability information sets, and the M capability information sets are used by the terminal device to perform capability updates. In this way, on the basis of indications of associations between frequency band combinations and capability information sets, repeated reporting of frequency band combination capabilities can be avoided, and the signaling overhead for reporting a plurality of capability information sets can be reduced, such that when subsequently performing capability updates, a terminal device can report updated capabilities with a relatively low signaling overhead.

Description

Communication methods, devices, storage media, and software products

[0001] This application claims priority to Chinese Patent Application No. 202510127890.0, filed on January 27, 2025, with the China National Intellectual Property Administration, entitled “Communication Method, Apparatus, Storage Medium and Program Product”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method, apparatus, storage medium, and program product. Background Technology

[0003] Different terminal devices have varying capabilities due to differences in hardware or software versions. To better serve these terminal devices, network devices need to know their capabilities in order to configure and schedule them appropriately. Typically, terminal devices report their capability information based on query messages from network devices. Because the size of this capability information is large, the signaling overhead for transmitting capabilities over the air interface is significant.

[0004] In certain scenarios, the capabilities of terminal devices may need to be updated. For example, when a terminal device overheats, it may change its capabilities to prevent device shutdown and protect user health from high temperatures; or when the terminal device is low on battery, it may change its capabilities to extend usage time. When a terminal device needs to update its capabilities, it will report the updated capability information.

[0005] How to reduce the signaling overhead during the initial capability reporting of terminal devices while also taking into account the signaling overhead of subsequent capability updates is a problem that urgently needs to be solved. Summary of the Invention

[0006] This application discloses a communication method, apparatus, storage medium, and program product that can reduce the signaling overhead of capability reporting.

[0007] Firstly, embodiments of this application provide a communication method. This method can be applied to a terminal-side device, such as a terminal or a communication / processing module within the terminal, or circuits or chips in the terminal responsible for communication functions (e.g., modem chips, also known as baseband chips, or system-on-chip (SoC) chips or system-in-package (SIP) chips containing a modem core), or circuits or chips in the terminal responsible for processing functions (e.g., graphics processing unit (GPU)). Taking the application of this method to a terminal device as an example, in this method, the terminal device receives first information, which is used to query the terminal device's capability information. The terminal device also sends second information, which is used to indicate M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device, each of the at least one frequency band combination being associated with one or more capability information sets in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

[0008] In this example, the network device sends a first message to query the terminal device's capability information. The terminal device then sends a second message indicating M sets of capability information it supports. This second message includes at least one frequency band combination supported by the terminal device. Each of these frequency band combinations is associated with one or more of the aforementioned M sets of capability information, which are used by the terminal device for capability updates. This association between frequency band combinations and capability information sets avoids redundant reporting of frequency band combination capabilities, reduces signaling overhead and latency from reporting multiple capability information sets, and facilitates subsequent capability updates by the terminal device with less signaling overhead.

[0009] Secondly, embodiments of this application provide a communication method. This method can be applied to network-side devices, such as network-side access network equipment, modules (e.g., circuits, chips, or chip systems) within the access network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the functions of the access network equipment. Taking the application of this method to a network device as an example, in this method, the network device sends first information, which is used to query the capability information of a terminal device. The network device also receives second information, which is used to indicate M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more capability information sets in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

[0010] In conjunction with the first and / or second aspects described above, in one possible implementation, the at least one frequency band combination includes a first frequency band combination, and the second information includes first identification information, which indicates that the first frequency band combination belongs to one or more capability information sets among M capability information sets.

[0011] This example uses the identification information of the frequency band combination to indicate which one or more capability information sets the frequency band combination belongs to. This can avoid the repeated reporting of frequency band combination capabilities and reduce the signaling overhead of reporting multiple capability information sets.

[0012] Optionally, the first identification information can be a bit string, with each bit corresponding to a set of capability information.

[0013] In conjunction with the first and / or second aspects described above, in another possible implementation, the second information includes a first capability information set, which includes at least one of the frequency band combinations. The second information includes second identification information corresponding to the second capability information set, which indicates a second frequency band combination that is a frequency band combination among at least one frequency band combination included in the first capability information set. The second capability information set is one of M capability information sets.

[0014] By reporting the first capability information set, when the frequency band combination contained in other capability information sets is the same as that in the multiple frequency band combinations contained in the first capability information set, the same frequency band combination can be indicated by the identification information, without having to report the other capability information set again. This can reduce the signaling overhead of reporting duplicate frequency band combinations in multiple capability information sets.

[0015] The first capability information set can be one of the aforementioned M capability information sets. Alternatively, the first capability information set can be a capability information set other than the aforementioned M capability information sets.

[0016] Optionally, the second identification information is the position or sequence number of the second frequency band combination in at least one frequency band combination included in the first capability information set.

[0017] In conjunction with the first and / or second aspects described above, in one possible implementation, the second information further includes a first reference set, which comprises capability parameters common to M capability information sets. The second information also includes a third capability information set, which includes a first capability parameter that is different from the capability parameters in the first reference set. This third capability information set is any one of the M capability information sets.

[0018] Terminal devices report a reference set, which includes common capability parameters from M capability information sets. This way, when reporting other capability information sets, only the parameters that differ from or have different values ​​than those in the reference set need to be reported, thus reducing the signaling overhead of repeatedly reporting capability parameters.

[0019] The common capability parameter among the aforementioned M capability information sets can be understood as follows: if capability parameter G is present in K of the aforementioned M capability information sets, then this capability parameter G is called the common capability parameter among the M capability information sets. Here, K can be a positive integer greater than or equal to 2 and less than or equal to M.

[0020] In conjunction with the first and / or second aspects described above, in another possible implementation, the second information further includes a second reference set, which includes capability parameters of M capability information sets. The second information also includes a fourth capability information set, which includes second capability parameters. These second capability parameters are one or more capability parameters in the second reference set that are not supported by the fourth capability information set, and / or capability parameters supported by the fourth capability information set that have different values ​​from those in the second reference set. The fourth capability information set is any one of the M capability information sets.

[0021] By reporting a second reference set, when reporting other capability information sets, it is only necessary to indicate the capability parameters or values ​​that the capability information set does not support relative to the second reference set. This can reduce the signaling overhead of repeatedly reporting capability parameters.

[0022] The aforementioned second reference set includes the capability parameters of the M capability information sets. This can be understood as the second reference set including all capability parameters of the M capability information sets.

[0023] In one possible implementation, the second information is further used to indicate the set of capability information currently in effect for the terminal device, which is one of M capability information sets. By indicating whether a new capability is in effect, the activation time of the new capability is aligned between the terminal device and the network device.

[0024] In conjunction with the first aspect above, in one possible implementation, the terminal device further sends third information, which is used to request an update to the terminal device's capability information. The third information instructs the terminal device's capability information to be updated to a fifth capability information set, which is one of M capability information sets.

[0025] In this example, when a terminal device updates its capabilities, it can use the identifier of the capability information set to indicate which capability information set to update to, thus saving signaling overhead.

[0026] In conjunction with the first aspect above, in one possible implementation, the terminal device also receives fourth information, which is used to indicate the identifier of the effective capability information set.

[0027] In conjunction with the first aspect described above, in one possible implementation, the terminal device further receives a first message indicating a radio resource control (RRC) configuration. This first message includes fifth information indicating that the RRC configuration is full.

[0028] Network devices need to configure and schedule terminal devices based on the updated capabilities of the terminal devices. This solution uses a full configuration approach for reconfiguration. Under full configuration, terminal devices and network devices can clear and release the original configuration parameters, release and re-establish the wireless bearer for communication, thus reducing the complexity of network device implementation.

[0029] In conjunction with the second aspect above, in one possible implementation, the network device further receives third information, which is used to request an update to the capability information of the terminal device. The third information instructs the terminal device to update its capability information to a fifth capability information set, which is one of M capability information sets.

[0030] In conjunction with the second aspect above, in one possible implementation, the network device also sends a fourth message, which is used to indicate the identifier of the effective capability information set.

[0031] In conjunction with the second aspect above, in one possible implementation, in response to the third information, the network device further sends a first message indicating RRC configuration, the first message including fifth information indicating that the RRC configuration is full configuration.

[0032] In conjunction with the first and / or second aspects above, in one possible implementation, the third information is carried in any of the following messages: capability update request message, RRC connection establishment completion message, RRC recovery completion message, RRC reconstruction completion message, and RRC reconfiguration completion message.

[0033] Thirdly, this application provides a communication device. This method can be applied to a terminal-side device, such as a terminal or a communication module / processing module within a terminal, or a circuit or chip in the terminal responsible for communication functions (e.g., a modem chip, also known as a baseband chip, or a system-on-a-chip containing a modem core or a system-in-package chip), or a circuit or chip in the terminal responsible for processing functions (e.g., a graphics processor). Taking the application of this method to a terminal device as an example, in this method, the terminal device receives first information, which is used to query the terminal device's capability information. The terminal device also sends second information, which is used to indicate a reference capability information set supported by the terminal device. The terminal device also sends third information, which, together with the reference capability information set, is used to determine a first capability information set, which is the capability information set currently used by the terminal device. The reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set.

[0034] In this example, the network device sends first information to query the capability information of the terminal device. The terminal device sends second and third information. The second information indicates a reference capability information set supported by the terminal device. The third information and the reference capability information set are used to determine a first capability information set, which is the capability information set currently used by the terminal device. The reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information indicates that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set. Thus, determining other capability information sets based on the third information and the reference capability information set avoids duplicate reporting of frequency band combination capabilities, reduces signaling overhead and latency in reporting capability information sets, and also facilitates subsequent capability updates by the terminal device with less signaling overhead.

[0035] Fourthly, embodiments of this application provide a communication method. This method can be applied to network-side devices, such as network-side access network equipment, modules (e.g., circuits, chips, or chip systems) within the access network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the functions of the access network equipment. Taking the application of this method to a network device as an example, in this method, the network device sends first information, which is used to query the capability information of a terminal device. The network device also receives second information, which is used to indicate a set of reference capability information supported by the terminal device. The network device also receives third information, which, together with the set of reference capability information, is used to determine a first set of capability information, which is the set of capability information currently used by the terminal device. The set of reference capability information includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first set of capability information includes a first frequency band combination, which is a frequency band combination in the set of reference capability information.

[0036] In conjunction with the third and / or fourth aspects described above, in one possible implementation, the third information indicates the identifier of the first frequency band combination, which is the position or sequence number of the first frequency band combination in the reference capability information set.

[0037] In conjunction with the third and / or fourth aspects described above, in one possible implementation, the second information includes a first reference set, which includes common capability parameters from multiple capability information sets supported by the terminal device, and the third information includes a first capability parameter, which is a capability parameter different from those in the first reference set, wherein the first capability information set includes the first capability parameter.

[0038] In conjunction with the third and / or fourth aspects above, in another possible implementation, the second information includes a second reference set, which includes capability parameters of multiple capability information sets supported by the terminal device; the third information includes a second capability parameter, which is one or more capability parameters in the second reference set that are not supported by the first capability information set, and / or capability parameters supported by the first capability information set that have different values ​​from those in the second reference set.

[0039] In conjunction with the third aspect described above, in one possible implementation, the terminal device further sends a first message, which requests an update to the terminal device's capability information, and the first message includes the third information described above.

[0040] In conjunction with the third aspect mentioned above, in one possible implementation, the terminal device also receives fourth information, which is used to indicate the identifier of the effective capability information set.

[0041] In conjunction with the third aspect above, in one possible implementation, the terminal device further receives a second message, which is used to indicate RRC configuration. The second message includes fifth information, which is used to indicate that the RRC configuration is a full configuration.

[0042] In conjunction with the fourth aspect above, in one possible implementation, the network device further receives a first message, which requests an update to the terminal device's capability information, and the first message includes third information.

[0043] In conjunction with the fourth aspect above, in one possible implementation, the network device further sends a second message to indicate RRC configuration, the second message including fifth information to indicate that the RRC configuration is full configuration.

[0044] In conjunction with the third and / or fourth aspects mentioned above, in one possible implementation, the third information is carried in any of the following messages: capability update request message, RRC connection establishment completion message, RRC recovery completion message, RRC reconstruction completion message, and RRC reconfiguration completion message.

[0045] Fifthly, this application provides a communication device. This method can be applied to a terminal-side device, such as a terminal or a communication / processing module within a terminal, or a circuit or chip in the terminal responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-a-chip containing a modem core or a system-in-package chip), or a circuit or chip in the terminal responsible for processing functions (such as a graphics processor). Taking the application of this method to a terminal device as an example, in this method, the terminal device receives first information, which is used to query the terminal device's capability information. The terminal device also sends second information, which includes a first frequency band combination supported by the terminal device. The second information also includes first identification information, which is used to indicate that the first frequency band combination belongs to one or more capability sets among M capability information sets. These M capability information sets are used by the terminal device to perform capability updates.

[0046] Sixthly, embodiments of this application provide a communication method. This method can be applied to network-side devices, such as network-side access network equipment, modules (e.g., circuits, chips, or chip systems) within the access network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the functions of the access network equipment. Taking the application of this method to a network device as an example, in this method, the network device sends first information, which is used to query the capability information of a terminal device. The network device also receives second information. The second information includes a first frequency band combination supported by the terminal device, and the second information also includes first identification information, which is used to indicate that the first frequency band combination belongs to one or more capability sets among M capability information sets, and the M capability information sets are used by the terminal device to update its capabilities.

[0047] Seventhly, this application provides a communication device. The method can be applied to a terminal-side device, such as a terminal or a communication module / processing module within a terminal, or a circuit or chip responsible for communication functions within the terminal (e.g., a modem chip, also known as a baseband chip, or a system-on-a-chip containing a modem core or a system-in-package chip), or a circuit or chip responsible for processing functions within the terminal (e.g., a graphics processor). Taking the method applied to a terminal device as an example, in this method, the terminal device receives first information, which is used to query the terminal device's capability information. The terminal device also sends second information, which is used to indicate M sets of capability information supported by the terminal device. The second information includes a first set of capability information, which includes at least one frequency band combination. The second information includes second identification information corresponding to the second set of capability information, which is used to indicate a second frequency band combination. The second frequency band combination is a frequency band combination among the at least one frequency band combination included in the first set of capability information. The second set of capability information is one of the M sets of capability information, and the M sets of capability information are used by the terminal device to perform capability updates.

[0048] Eighthly, embodiments of this application provide a communication method. This method can be applied to network-side devices, such as network-side access network equipment, modules (e.g., circuits, chips, or chip systems) within the access network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the functions of the access network equipment. Taking the application of this method to a network device as an example, in this method, the network device sends first information, which is used to query the capability information of a terminal device. The network device also receives second information. The second information is used to indicate M sets of capability information supported by the terminal device. The second information includes a first set of capability information, which includes at least one frequency band combination. The second information includes second identification information corresponding to the second set of capability information, which is used to indicate a second frequency band combination. The second frequency band combination is a frequency band combination among the at least one frequency band combination included in the first set of capability information. The second set of capability information is one of the M sets of capability information, and the M sets of capability information are used by the terminal device to perform capability updates.

[0049] For other implementation methods of aspects five through eight, please refer to the records of aspects one and two above, which will not be repeated here.

[0050] Ninthly, this application provides a communication device that has the functions of the first aspect described above. For example, the communication device includes modules, units, or means that perform the operations involved in the first aspect. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0051] In one implementation, the communication device includes: a communication module for receiving first information, the first information being used to query capability information of a terminal device;

[0052] The communication module is further configured to send second information, which indicates M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more sets of capability information in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

[0053] In one possible implementation, the at least one frequency band combination includes a first frequency band combination, and the second information includes first identification information, which indicates that the first frequency band combination belongs to one or more capability information sets among M capability information sets.

[0054] In one possible implementation, the second information includes a first capability information set, the first capability information set including at least one frequency band combination, the second information including second identification information corresponding to the second capability information set, the second identification information being used to indicate the second frequency band combination, the second frequency band combination being a frequency band combination among at least one frequency band combination included in the first capability information set, and the second capability information set being a capability information set among the M capability information sets.

[0055] In one possible implementation, the second identification information is the position or sequence number of the second frequency band combination within at least one frequency band combination included in the first capability information set.

[0056] In one possible implementation, the second information further includes a first reference set, which includes common capability parameters among the M capability information sets. The second information also includes a third capability information set, which includes a first capability parameter that is different from the capability parameter in the first reference set. The third capability information set is any one of the M capability information sets.

[0057] In another possible implementation, the second information further includes a second reference set, which includes capability parameters of M capability information sets. The second information also includes a fourth capability information set, which includes second capability parameters. The second capability parameters are one or more capability parameters in the second reference set that are not supported by the fourth capability information set, and / or capability parameters supported by the fourth capability information set that have different values ​​from those in the second reference set. The fourth capability information set is any one of the M capability information sets.

[0058] In one possible implementation, the second information is further used to indicate the set of capability information currently in effect for the terminal device, which is one of M sets of capability information.

[0059] In one possible implementation, the communication module is further configured to send third information, which requests an update to the capability information of the terminal device. The third information instructs the terminal device's capability information to be updated to a fifth capability information set, which is one of the M capability information sets.

[0060] In one possible implementation, the communication module is further configured to receive a fourth piece of information, which indicates the identifier of the effective set of capability information.

[0061] In one possible implementation, the communication module is further configured to receive a first message indicating RRC configuration, the first message including fifth information indicating that the RRC configuration is full configuration.

[0062] In one possible implementation, the third information is carried in any of the following messages: capability update request message, RRC connection establishment complete message, RRC recovery complete message, RRC reconstruction complete message, and RRC reconfiguration complete message.

[0063] In a tenth aspect, this application also provides a communication device that has the functions of the second aspect described above. For example, the communication device includes modules, units, or means that perform the operations involved in the second aspect described above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0064] In one implementation, the communication device includes: a communication module for sending first information, the first information being used to query capability information of a terminal device;

[0065] The communication module is further configured to receive second information, which indicates M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more sets of capability information in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

[0066] In one possible implementation, the communication module is further configured to receive third information, which requests an update to the capability information of the terminal device. The third information instructs the capability information of the terminal device to be updated to a fifth capability information set, which is one of the M capability information sets.

[0067] In one possible implementation, the communication module is also used to send a fourth message, which indicates the identifier of the effective capability information set.

[0068] In one possible implementation, the communication module is further configured to send a first message in response to the third information, the first message indicating RRC configuration, the first message including fifth information indicating that the RRC configuration is a full configuration.

[0069] For other implementation methods, please refer to the description in the ninth aspect above, which will not be repeated here.

[0070] In the eleventh aspect, this application provides a communication device that has the functions of the third aspect described above. For example, the communication device includes modules, units, or means that perform the operations involved in the third aspect described above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0071] In one implementation, the communication device includes: a communication module for receiving first information, the first information being used to query capability information of a terminal device;

[0072] The communication module is also used to send second information, which is used to indicate a set of reference capability information supported by the terminal device;

[0073] The communication module is further configured to send third information, which, together with the reference capability information set, is used to determine a first capability information set, which is the capability information set currently used by the terminal device; wherein, the reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set.

[0074] In one possible implementation, the third information indicates the identifier of the first frequency band combination, which is the position or sequence number of the first frequency band combination in the reference capability information set.

[0075] In one possible implementation, the second information includes a first reference set, which includes common capability parameters from multiple capability information sets supported by the terminal device, and the third information includes a first capability parameter, which is a capability parameter different from those in the first reference set, wherein the first capability information set includes the first capability parameter.

[0076] In another possible implementation, the second information includes a second reference set, which includes capability parameters of multiple capability information sets supported by the terminal device, and the third information includes a second capability parameter, which is one or more capability parameters in the second reference set that are not supported by the first capability information set, and / or capability parameters supported by the first capability information set that have different values ​​from those in the second reference set.

[0077] In one possible implementation, the communication module is further configured to send a first message requesting an update to the capability information of the terminal device, the first message including the third information.

[0078] For other implementation methods, please refer to the aforementioned records, which will not be repeated here.

[0079] In a twelfth aspect, this application also provides a communication device that has the functions of the fourth aspect described above. For example, the communication device includes modules, units, or means that perform the operations involved in the fourth aspect described above. These modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0080] In one implementation, the communication device includes: a communication module for sending first information, the first information being used to query capability information of a terminal device;

[0081] The communication module is also used to receive second information, which is used to indicate a set of reference capability information supported by the terminal device;

[0082] The communication module is further configured to receive third information, which, together with the reference capability information set, is used to determine a first capability information set, which is the capability information set currently used by the terminal device; wherein, the reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set.

[0083] In one possible implementation, the communication module is further configured to receive a first message, which requests an update to the capability information of the terminal device, the first message including the third information.

[0084] For other implementation methods, please refer to the aforementioned records, which will not be repeated here.

[0085] In a thirteenth aspect, this application provides a communication system, including the communication apparatus of the ninth aspect and the tenth aspect, or including the communication apparatus of the eleventh aspect and the twelfth aspect.

[0086] In a fourteenth aspect, this application provides a communication device including a processor configured to perform methods provided in any of the possible embodiments of the first to eighth aspects by executing a computer program or computer-executable instructions stored in a memory, and / or by logic circuitry.

[0087] One possible implementation also includes memory. Alternatively, the memory and processor can be integrated together.

[0088] One possible implementation also includes an interface circuit.

[0089] In one possible implementation, the device is a chip or chip system.

[0090] In a fifteenth aspect, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the method provided in any of the possible embodiments of the first to eighth aspects.

[0091] In a sixteenth aspect, this application provides a computer program product that, when run on a computer, causes the computer to perform a method as provided in any of the possible embodiments of the first to eighth aspects.

[0092] It is understood that the apparatus described in the ninth aspect, the tenth aspect, the eleventh aspect, the twelfth aspect, the thirteenth aspect, the fourteenth aspect, the computer storage medium described in the fifteenth aspect, or the computer program product described in the sixteenth aspect are all used to perform the methods provided in any of the first to eighth aspects. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. Attached Figure Description

[0093] The accompanying drawings used in the embodiments of this application are described below.

[0094] Figure 1 is a schematic diagram of a communication system provided in an embodiment of this application;

[0095] Figure 2 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0096] Figures 3-5 are schematic diagrams illustrating capability switching in several application scenarios provided in the embodiments of this application;

[0097] Figure 6 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0098] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application;

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

[0100] Figure 9 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0101] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0102] Figure 1 illustrates a possible, non-limiting system diagram. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, it also includes an Internet 300. RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0103] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or evolutionary systems beyond 5G (e.g., 6th generation, 6G mobile communication systems). RAN 100 can also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless-fidelity (Wi-Fi) system based on the IEEE 802.11 standard. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0104] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0105] 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, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0106] In another possible scenario, multiple RAN nodes assist the terminal in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0107] 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.

[0108] A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR) devices, augmented reality (AR) devices, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, light UEs, reduced-capability UEs (REDCAP UEs), point-of-sale (POS) machines, customer-premises equipment (CPE), etc. The terminal can also be a vehicle device, such as a complete vehicle device, an in-vehicle module, an in-vehicle chip, an on-board unit (OBU), or a telematics box (T-BOX). The embodiments of this application do not limit the device form of the terminal.

[0109] Communication between access network devices and terminal devices follows a specific protocol layer structure. This protocol layer may include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer may include at least one of the following: RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, or Physical (PHY) layer, etc. The user plane protocol layer may include at least one of the following: Service Data Adaptation Protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or Physical layer, etc.

[0110] For the network elements in the ORAN system and their corresponding protocol layer functions, please refer to Table 1:

[0111] Table 1

[0112] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0113] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0114] In this embodiment, the base station is also referred to as an access network device. The apparatus used to implement the functions of the access network device can be the access network device itself; it can also be any apparatus capable of supporting the access network device in implementing these functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the access network device or used in conjunction with the access network device. In this embodiment, the example of an access network device being used to implement the functions of the access network device is used only and does not constitute a limitation on the solutions of this embodiment.

[0115] It is understood that this application can be applied between access network equipment and terminals.

[0116] It should be understood that the number and type of each device in the communication system shown in Figure 1 are for illustrative purposes only, and this application is not limited thereto. In actual applications, the communication system may include more terminals, more access network devices, and other network elements, such as core network devices and / or network elements used to implement artificial intelligence functions.

[0117] It is understandable that all or part of the functions implemented by one or more of the terminals, access network equipment, core network equipment, or network elements used to implement artificial intelligence functions can be virtualized, that is, implemented through one or more of dedicated or general-purpose processors and corresponding software modules. Among these, the transmit and receive functions of the terminals and access network equipment, which involve air interface transmission, can be implemented in hardware. Core network equipment, such as operation administration and maintenance (OAM) network elements, can also be virtualized. Optionally, one or more of the functions of the virtualized terminals, access network equipment, core network equipment, or network elements used to implement artificial intelligence functions can be implemented by cloud devices, such as cloud devices in over-the-top (OTT) systems.

[0118] The following explains several terms used in the embodiments of this application:

[0119] 1. Terminal device capabilities (also known as terminal device capability information)

[0120] In this solution, the capabilities of the terminal device can refer to its wireless access capabilities, or be understood as its access layer capabilities. The capabilities of the terminal device can be divided into the following levels:

[0121] (1) Per-UE capabilities. For example, the protocol versions supported by the terminal device, the PDCP layer capabilities supported by the terminal device, the MAC layer capabilities, etc.

[0122] (2) Per-band capabilities. Per-band capabilities can be, for example, capabilities specific to a particular frequency band. These per-band capabilities are typically related to the radio frequency capabilities of the terminal device.

[0123] (3) Band combination (BC) capability. Band combination capability is typically used to describe the carrier aggregation (CA) capability supported by the terminal device. Carrier aggregation is a commonly used method to increase communication bandwidth. Carrier aggregation refers to providing services to the terminal device simultaneously using multiple carriers, with each carrier having at least one component carrier (CC) operating for the terminal device. Table 2 shows a schematic of a band combination (bandA+bandB+bandC). In existing carrier aggregation technologies, there is usually one primary cell (PCell), and other serving cells are secondary cells (SCells). Secondary cells can be activated or deactivated during use. For example, if there is no data transmission for a period of time, the network device may deactivate the secondary cell, and may consider reactivating it when data is transmitted again.

[0124] Table 2

[0125] Carrier aggregation includes the aggregation of multiple carriers within a single frequency band, as well as the aggregation of multiple carriers across multiple frequency bands. The following is an example of a multi-band combination, such as band A having one carrier, and bands B and C each having two carriers. The carrier aggregation capability supported by the terminal device is demonstrated by reporting the capabilities of the supported frequency band combinations. For a frequency band combination, the terminal device needs to indicate the frequency band identifiers included in the combination, the capabilities of each frequency band, and the capabilities of the carriers in each frequency band.

[0126] For a given combination of frequency bands supported by a terminal device, the following capabilities are also included:

[0127] (1) Capabilities per band combination level (perBC). Capabilities per band combination level indicate the capabilities of the band combination, such as the power class of the band combination, whether the band combination supports multiple tracking areas (TAs), etc.

[0128] (2) Per-band-per-BC capability (i.e., capability for a specific frequency band within a frequency band combination). The terminal device indicates the feature set combination (FSC) corresponding to each frequency band combination. The feature set combination contains the feature set (FS) corresponding to each frequency band in the frequency band combination, which is the capability per-band-per-BC, also known as the capability per feature set level (per FS).

[0129] It should be noted that the capabilities at the per-band level and per-band combination level, as well as the capabilities at the per-band level mentioned above, are band-specific capabilities. The capabilities at the per-band level and per-band combination level are further restrictions on the capabilities of a specific band within a band combination. Capabilities at the per-band level are general capabilities for that band. For example, if a terminal device reports support for capability A at the per-band level of band A, then capability A should be supported on band A in all band combinations composed of band A (e.g., band A + band B, band A + band C). However, for capabilities at the per-band level and per-band combination level, the terminal device can report different capabilities in different band combinations. For instance, the terminal device might report support for capability B on band A in the band A + band B combination, but report no support for capability B on band A in the band A + band C combination (e.g., capability B is defaulted). In other words, in this example, capability A is defined at the per-band level, and capability B is defined at the per-band level and per-band combination level.

[0130] (3) Carrier-level capabilities (referred to as per CC capabilities). This capability refers to the capability of a specific component carrier within a specific frequency band in a frequency band combination. For example, the subcarrier spacing (SCS) supported by the carrier, the maximum number of multiple-input multiple-output (MIMO) layers, and the maximum carrier bandwidth. This type of capability can also be called featuresetperCC (FSPC) capability.

[0131] 2. Idle state

[0132] The idle state can also be called the RRC idle state. When a terminal device is in the idle state, it does not retain the RRC context. The RRC context is the parameter used to establish communication between the terminal device and the network device. The RRC context can include security context, terminal device capability information, etc. Simultaneously, the terminal device has not established a connection with the core network device, meaning the core network device is in CN-IDLE (core network idle state). Since the terminal device has no data to transmit, it will enter a sleep state, shutting down its transceiver unit to reduce power consumption. Terminal devices in the idle state only periodically wake up to receive paging messages.

[0133] 3. Connected state

[0134] The connected state can also be called the RRC connected state. When the terminal device is in the connected state, the terminal device has established an RRC context. The parameters required for communication between the terminal device and the network device have been obtained by both parties. The network device assigns a cell radio network temporary identifier (C-RNTI) to the accessing terminal device. At the same time, the terminal device also establishes a connection with the core network device, that is, the core network device is in CN_CONNECTED (core network connected state). At this time, if the terminal device is transmitting data, it is in continuous reception state until the data transmission is completed and it enters a waiting state, then switches to connected state discontinuous reception (DRX) to save power. If there is still data to be transmitted, the terminal device returns to the continuous reception state.

[0135] 4. Inactive state

[0136] The inactive state can also be called the RRC inactive state, deactivated state, or RRC deactivated state. When the terminal device is in the inactive state, the RRC context is maintained between the terminal device and the network device. Simultaneously, the terminal device establishes a connection with the core network device, meaning the core network device is in the CN_CONNECTED (core network connected state). At this time, switching to the connected state for data reception is relatively fast and does not incur additional core network signaling overhead. Furthermore, the terminal device in the inactive state also enters a sleep state. Therefore, the inactive state can meet the requirements of reducing connection latency, signaling overhead, and power consumption.

[0137] The architecture of the embodiments of this application has been described above. The methods of the embodiments of this application will be described in detail below.

[0138] Referring to Figure 2, a flowchart illustrating a communication method provided in an embodiment of this application is shown. Optionally, this method can be applied to the aforementioned communication system, such as the communication system shown in Figure 1. The communication method shown in Figure 2 may include steps 201-202. Steps 201-202 are as follows:

[0139] 201. The network device sends first information, which is used to query the capability information of the terminal device. Accordingly, the terminal device receives the first information.

[0140] For example, the capability information of the terminal device refers to the aforementioned wireless access capabilities of the terminal device. Optionally, this first information is carried in a capability query message.

[0141] 202. The terminal device sends second information, which indicates M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device, each of the at least one frequency band combination being associated with one or more of the aforementioned M sets of capability information. These M sets of capability information are used by the terminal device for capability updates, where M is a positive integer greater than or equal to 2. Accordingly, the network device receives the second information.

[0142] Each capability information set corresponds to a set of capabilities supported by the terminal device, and each capability information set may include at least one capability parameter. Here, the capabilities of the terminal device can refer to its wireless access capabilities, or be understood as access layer capabilities. From the perspective of the protocol stack, a capability information set may include capabilities of each layer of the wireless access protocol stack supported by the terminal device, such as physical layer capabilities, MAC capabilities, RLC capabilities, PDCP capabilities, SDAP capabilities, etc. It can also be divided according to capability granularity; for example, a capability information set may include terminal device-level capabilities, frequency band-level capabilities, carrier-level capabilities, frequency band combination-level capabilities, or cell-level / cell group-level capabilities. For a detailed description of the capabilities of the terminal device, please refer to the foregoing descriptions, which will not be repeated here.

[0143] This example illustrates the band combination capability supported by the terminal device. This band combination capability can include capabilities at the band combination level (e.g., power level, simultaneous multi-carrier transmission and reception capability, multi-TA capability), the capabilities of each band in the band combination, and the capabilities of each component carrier in the band (e.g., carrier bandwidth, subcarrier spacing, number of MIMO layers). It should be noted that this embodiment is not limited to the above capability structure and terminology, and is also applicable to future next-generation capability structures. For example, the above-mentioned band combination can be replaced by carrier combination, cell combination, band set, etc. The band combination capability in this embodiment refers to a type of capability that can describe the multi-band, multi-carrier, or multi-cell capabilities supported by the terminal device. It can employ carrier aggregation (concurrent transmission / reception) working mode, inter-carrier handover (round-robin transmission / reception) working mode, or other evolved multi-carrier working modes, etc.

[0144] These M capability information sets are used for terminal device capability updates. It can be understood that when the terminal device performs a subsequent capability update, it reports the updated capability information set, which is one of these M capability information sets. The M capability information sets correspond to the M capabilities supported by the terminal device, or can be understood as M sets of capabilities. The terminal device can switch between these M sets of capabilities to communicate with the network device according to the scenario or requirements. For example, the terminal device may correspond to a different capability information set for overheating, energy saving, single SIM, and dual SIM modes, such as capability information sets 1, 2, 3, and 4 respectively. The terminal device can switch between these four capability information sets to use for communication with the network device based on the current scenario and requirements.

[0145] The "at least one frequency band combination" supported by the aforementioned terminal device can be understood as the capability of the terminal device supporting at least one frequency band combination. The "at least one frequency band combination" refers to at least one frequency band combination included in the M capability information sets supported by the aforementioned terminal device. A capability information set may contain one or more frequency band combinations supported by the terminal device; a frequency band combination may be a capability supported by the terminal device in one capability information set, or it may be a capability supported by the terminal device in multiple capability sets.

[0146] The following describes several implementation methods for associating each frequency band combination in the at least one frequency band combination with one or more capability information sets in the M capability information sets.

[0147] In one possible implementation, the at least one frequency band combination includes a first frequency band combination, and the second information includes first identification information, which indicates that the first frequency band combination belongs to one or more capability information sets among the M capability information sets.

[0148] In other words, based on the first identification information, the network device knows the capability information set to which the first frequency band combination supported by the terminal device belongs. For example, the first frequency band combination is bandA+bandB, and capability information set 1 and capability information set 2 in the M capability information sets both include bandA+bandB. Based on the aforementioned first identification information, the network device knows that capability information set 1 and capability information set 2 both include bandA+bandB. For example, the first identification information can be a bit string, with each bit corresponding to a capability information set. The capability information set corresponding to each bit in the bit string can be assigned in a preset order. For example, the first bit, starting from the leftmost bit, corresponds to the first capability information set, the second bit corresponds to the second capability information set, and so on. A bit set to 1 indicates that the corresponding capability information set includes the frequency band combination (or can be understood as the capability information set supporting the frequency band combination); a bit set to 0 indicates that the corresponding capability information set does not include the frequency band combination (or can be understood as the capability information set not supporting the frequency band combination). For example, referring to Table 3 below, the terminal device supports band combination 1 (BC#1) (e.g., band A + band B), band combination 2 (BC#2) (e.g., band A + band C), and band combination 3 (BC#3) (e.g., band B + band C). When M is 3, the identifier information corresponding to BC#1 is 100, indicating that capability information set 1 supports (or includes) band A + band B, while capability information sets 2 and 3 do not support (or do not include) band A + band B. The identifier information corresponding to BC#2 is 011, indicating that capability information set 1 does not support (or does not include) band A + band C, while capability information sets 2 and 3 both support (or include) band A + band C. The identifier information corresponding to BC#3 is 100, indicating that capability information set 1 supports (or includes) band B + band C, while capability information sets 2 and 3 do not support (or do not include) band B + band C.

[0149] Table 3

[0150] The above example uses bit strings as the indication, but other representations can also be used, and this scheme does not restrict this.

[0151] This example uses the identification information of the frequency band combination to indicate which one or more capability information sets the frequency band combination belongs to. This can avoid the repeated reporting of frequency band combination capabilities and reduce the signaling overhead of reporting multiple capability information sets.

[0152] In another possible implementation, the second information includes a first capability information set, which includes at least one frequency band combination. The second information also includes second identification information corresponding to the second capability information set, which indicates a second frequency band combination that is a frequency band combination among the at least one frequency band combination included in the first capability information set. The second capability information set is one of the M capability information sets.

[0153] The second information includes second identification information corresponding to the second capability information set. This can be replaced by the second capability information set including the second identification information, which indicates that the second capability information set includes a first frequency band combination. One implementation of the second identification information indicating that the second capability information set includes a first frequency band combination is that the second identification information is an identifier of the first frequency band combination, and the second capability information set includes the second identification information, meaning that the second capability information includes a first frequency band combination. The first frequency band combination is a frequency band combination in the first capability information set, and the identifier of the first frequency band combination can be the position of the first frequency band combination within at least one frequency band combination in the first capability information set.

[0154] The first capability information set can be one of the aforementioned M capability information sets. Alternatively, the first capability information set can be a capability information set other than the aforementioned M capability information sets, i.e., it is a reference capability information set (or baseline capability information set). Optionally, the capability information set reported by the terminal device as the first capability information set can be pre-negotiated between the network device and the terminal device, for example, a pre-negotiated frequency band combination list (BC list) is the first capability information set. Alternatively, the first capability information set is predefined by the protocol, for example, the first capability information set is the capability information set ranked first among the M capability information sets. Alternatively, the terminal device can send indication information indicating which capability information set is the first capability information set. The first capability information set includes multiple frequency band combinations. The second identification information corresponding to the second capability information set can indicate that the second capability information set includes a second frequency band combination, and that the second frequency band combination is a frequency band combination included in the first capability information set. Optionally, the aforementioned second identification information is the position or sequence number of the second frequency band combination in at least one frequency band combination included in the first capability information set.

[0155] In other words, by reporting the first capability information set, when the frequency band combination contained in other capability information sets is the same as the frequency band combination contained in the first capability information set, the same frequency band combination can be indicated by the identification information, without having to report the other capability information set again. This can reduce the signaling overhead of reporting duplicate frequency band combinations in multiple capability information sets.

[0156] For example, as shown in Table 4 below:

[0157] Table 4

[0158] The above example takes into account the large number of frequency band combinations supported by terminal devices and the high probability of duplicate capabilities associated with different frequency band combinations. Therefore, a new capability reporting method is proposed to avoid duplicate reporting of frequency band combinations.

[0159] The above example uses the terminal device's ability to report frequency band combination (BC). The following section introduces other capabilities of the terminal device (such as terminal device-level capabilities, frequency band-level capabilities, etc.).

[0160] In one possible implementation, the second information further includes a first reference set, which includes common capability parameters among the M capability information sets. The second information also includes a third capability information set, which includes a first capability parameter that is different from the capability parameters in the first reference set. The third capability information set is any one of the M capability information sets.

[0161] The common capability parameter among the aforementioned M capability information sets can be understood as follows: if capability parameter G is included in K of the M capability information sets, then this capability parameter G is called the common capability parameter among the M capability information sets. Here, K can be a positive integer greater than or equal to 2 and less than or equal to M. For example, the first reference set can be the capability parameter included in every one of the M capability information sets. This first reference set can also be called the minimum capability information set, etc.

[0162] It should be noted that the aforementioned first reference set may be one of the M capability information sets, or it may not belong to any of the M capability information sets.

[0163] In other words, the terminal device reports a reference set, which includes common capability parameters from M capability information sets. Thus, when reporting other capability information sets, only the parameters that differ from or have different values ​​than those in the reference set need to be reported, thereby reducing the signaling overhead of repeatedly reporting capability parameters.

[0164] For example, as shown in Table 5:

[0165] Table 5

[0166] In another possible implementation, the second information further includes a second reference set, which includes capability parameters of the M capability information sets. The second information also includes a fourth capability information set, which includes second capability parameters. The second capability parameters are one or more capability parameters that are not supported by the fourth capability information set in the second reference set, and / or capability parameters that are supported by the fourth capability information set and have different values ​​from those in the second reference set. The fourth capability information set is any one of the M capability information sets.

[0167] The second reference set mentioned above includes the capability parameters of the M capability information sets. This can be understood as the second reference set including all capability parameters of the M capability information sets. For example, capability information set 1 includes capability parameter D and capability parameter E; capability information set 2 includes capability parameter D; capability information set 3 includes capability parameter F; then the second reference set includes capability parameter D, capability parameter E, and capability parameter F.

[0168] The aforementioned second capability parameter is one or more capability parameters that are not supported by the fourth capability information set in the second reference set. That is, by reporting the second reference set, when reporting other capability information sets, it is only necessary to indicate the capability parameters or values ​​that the capability information set does not support relative to the second reference set. This can reduce the signaling overhead of repeatedly reporting capability parameters.

[0169] For example, as shown in Table 6:

[0170] Table 6

[0171] It should be noted that the second reference set mentioned above may include all capability parameters and all values, or it may only include all capability parameters and some values, etc. This solution does not impose any restrictions on this.

[0172] The above example introduces several implementation methods for a terminal device to report M sets of capability information. In one possible implementation, the second information is also used to indicate the set of capability information currently in effect (or used, applied, etc.) for the terminal device, which is one of the M sets of capability information. That is, when the terminal device reports the M sets of capability information it supports, it also indicates the set of capability information currently in effect. This makes it easier for the network device to know the capabilities currently used by the terminal device. For example, the set of capability information currently in effect is indicated by an identifier indicating the set of capability information currently in effect. For example, if M=4, the identifiers of the four capability information sets are indicated by 2 bits: the identifier of the first capability information set is 00, the identifier of the second capability information set is 01, the identifier of the third capability information set is 10, and the identifier of the fourth capability information set is 11. Optionally, the second information may also indicate that the identifier of the currently in effect capability information set is one of the above four identifiers.

[0173] In certain scenarios, the capabilities of terminal devices may need to be updated. For example, when a terminal device overheats, it may change its capabilities to prevent device malfunction or damage to user health due to high temperatures; or when the terminal device is low on battery, it may change its capabilities to extend usage time; or when there is interference from other systems, such as Bluetooth or WiFi communication interfering with wireless communication on certain frequency bands, the terminal device may change its capabilities to avoid interference on those bands; or, if the terminal device is a dual-SIM device, it may change its capabilities when switching between single-SIM and dual-SIM communication. In other words, there is a need for terminal devices to change their capabilities in various scenarios.

[0174] Based on this, in one possible implementation, the terminal device further sends third information, which requests an update to the terminal device's capability information. This third information instructs the terminal device to update its capability information to a fifth capability information set, which is one of the M capability information sets. Accordingly, the network device receives this third information.

[0175] In this example, when a terminal device updates its capabilities, it can indicate which capability information set to update to using the identifier of the capability information set. For details, please refer to the aforementioned description; it will not be repeated here. Of course, other indication methods can also be used, and this solution does not restrict them.

[0176] Optionally, this third information is carried in an RRC message. For example, a capability update request message, an RRC connection establishment completion message, an RRC recovery completion message, an RRC reconstruction completion message, or an RRC reconfiguration completion message. For a description of this part, please refer to the embodiments shown in Figures 3-5 below, which will not be detailed here. The aforementioned capability update request message is used by the terminal device to request capability updates from the network device. This application does not limit the name of this message, and the capability update request message can be replaced with other message names, etc.

[0177] In one possible implementation, the network device sends indication information to the terminal device to indicate whether it accepts or rejects the terminal device's capability update request. For example, the network device sends fourth information indicating the identifier of the effective capability information set. The effective capability information set indicated by the network device can also be understood as the capability information set that the network device agrees to use by the terminal device, or the capability information set that the network device allows the terminal device to activate. Accordingly, the terminal device receives the fourth information. For example, the network device indicates that the effective capability information set is capability information set #1 (identified as 1) or capability information set #2 (identified as 2). If the effective capability information set is indicated as #2, it can be considered that the network device agrees to the terminal device's capability update request. After receiving the response message from the network device, the terminal device applies the updated capabilities to communicate with the network device. If the effective capability information set is indicated as #1, it can be considered that the network device rejects the terminal device's request. After receiving the response message from the network device, the terminal device still uses the original capabilities to communicate with the network device. Alternatively, the fourth information can be used to indicate whether the updated capability information set is effective. For example, the fourth piece of information is 1 bit. Setting this bit to 1 indicates that the new capability is active, while setting it to 0 indicates that the new capability is not active; alternatively, this bit may indicate that the new capability is active if present, but by default, it indicates that the new capability is not active. By indicating whether the new capability is active, the timing of the new capability's activation is aligned between the terminal device and the network device. In this way, the terminal device uses the set of active capability information to communicate with the network device.

[0178] In one possible implementation, in response to the third information described above, the network device sends a first message indicating the RRC configuration. For example, the first message could be an RRC reconfiguration message. Optionally, the first message includes indication information indicating whether the RRC configuration is based on the updated capability information of the terminal device. In one example, the network device sends a sixth message indicating the identifier of the set of capability information referenced (or replaced by, based on) by which the RRC configuration (which can be understood as the current RRC configuration) is based. The implementation of this sixth message can be referred to the description of the fourth information described above, and will not be repeated here. In yet another example, the network device sends a seventh message indicating whether the RRC configuration is based on the updated capability information, or, in other words, indicating whether the terminal device has taken effect with the updated capability information. For example, the seventh information may be a 1-bit bit. A bit set to 1 indicates that the RRC configuration is based on the updated capabilities, while a bit set to 0 indicates that the RRC configuration is based on the capabilities before the update (or the old capabilities). Alternatively, the presence of this bit indicates that the RRC configuration is based on the updated capabilities, while the default bit indicates that the RRC configuration is based on the capabilities before the update. Or, the presence of this bit indicates that the terminal device has the updated capabilities enabled, or it can be understood as instructing the terminal device to communicate with the network device based on the updated capabilities; the absence of this bit indicates that the terminal device has not enabled the updated capabilities, or it can be understood as instructing the terminal device to communicate with the network device based on the unupdated capabilities (the capabilities before sending the capability update request). Optionally, the first message includes a fifth information, which indicates that the RRC configuration is a full configuration. A full configuration can also be understood as a complete configuration or a fully configured configuration. The opposite of a full configuration is a partial configuration (which can also be understood as an incremental configuration (delta configuration)). A partial configuration can be understood as an update based on the network device's previous RRC configuration. Accordingly, the terminal device determines the updated RRC configuration based on the saved RRC configuration and the incremental configuration issued by the network device. A full configuration can be understood as the terminal device clearing its saved RRC configuration and using the full configuration issued by the network device, and optionally, using certain default configurations (i.e., protocol-preset configuration parameters) to determine the updated RRC configuration. Accordingly, the terminal device receives the aforementioned first message. For example, based on this first message, the terminal device clears the stored radio configuration, releases and creates a new radio bearer, and applies the default physical layer parameters. For example, the RRC reconfiguration message sent by the network device to the terminal device carries an information element enabling full configuration. After receiving the RRC reconfiguration message containing the full configuration, the terminal device performs a full configuration.For example, the terminal device clears the private radio configuration and public radio configuration, applies the default Layer 1 parameters, applies the default MAC cell group configuration, releases the SDAP entity, releases the data radio bearer (DRB), and creates a new DRB using the new packet data convergence protocol (PDCP) and logical channel configuration.

[0179] In this scenario, network devices need to configure and schedule terminal devices based on the updated capabilities of the terminal devices. This solution uses a full configuration approach for reconfiguration. If incremental configuration is used, the network device needs to compare the differences between the capabilities before and after the update to determine the incremental configuration portion. Since the capabilities of a terminal device may involve multiple features and functions, and the number of capability parameters in each capability information set is enormous, incremental reconfiguration is highly complex for network devices. This embodiment proposes that, in the scenario of capability updates, the network device issues a full configuration to the terminal device based on the updated capabilities of the terminal device, thereby avoiding the need for the network device to compare the new and old capabilities and reducing the implementation complexity of the network device.

[0180] The above example illustrates how a network device can use full configuration when a terminal device requests a capability update. It should be noted that this application does not restrict the network device from using full configuration upon receiving a capability update from a terminal device. Whether or not to use full configuration may depend on the network device's implementation strategy, etc., and this solution does not impose any restrictions on this.

[0181] Based on the above processing, terminal devices can use the updated capabilities to communicate with network devices.

[0182] In this example, the network device sends a first message to query the terminal device's capability information. The terminal device then sends a second message indicating M sets of capability information it supports. This second message includes at least one frequency band combination supported by the terminal device. Each of these frequency band combinations is associated with one or more of the aforementioned M sets of capability information, which are used by the terminal device for capability updates. This association between frequency band combinations and capability information sets avoids redundant reporting of frequency band combination capabilities, reduces signaling overhead and latency from reporting multiple capability information sets, and facilitates subsequent capability updates by the terminal device with less signaling overhead.

[0183] The above communication method will now be described in conjunction with several implementation scenarios of embodiments of this application.

[0184] Scenario 1: The terminal device is in RRC connection state.

[0185] Referring to Figure 3, the communication method may include steps 301-305, as follows:

[0186] 301. The network device sends first information, which is used to query the capability information of the terminal device. Accordingly, the terminal device receives the first information.

[0187] 302. The terminal device sends second information, which indicates M sets of capability information supported by the terminal device. The second information includes a first frequency band combination supported by the terminal device and also includes first identification information, which indicates that the first frequency band combination belongs to one or more capability sets among the M sets of capability information. The M sets of capability information are used by the terminal device to update its capabilities. Accordingly, the network device receives the second information.

[0188] The second information in this example is also used to indicate the set of capability information currently in effect for the terminal device, which is one of the M sets of capability information.

[0189] For details on this part, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0190] This example illustrates how the second information also includes first identification information, which indicates that the first frequency band combination belongs to one or more capability sets among the M capability information sets. Alternatively, step 302 can also involve: the terminal device sending second information indicating the M capability information sets supported by the terminal device. This second information includes a first capability information set, which includes at least one frequency band combination. The second information also includes second identification information corresponding to the second capability information set, indicating a second frequency band combination that is one of the at least one frequency band combination included in the first capability information set. This second capability information set is one of the M capability information sets used by the terminal device for capability updates. Correspondingly, the network device receives the second information. For a detailed description of this part, please refer to the description of step 202 in the embodiment shown in Figure 2; it will not be repeated here.

[0191] Optionally, the second information may further include a first reference set, which includes common capability parameters among the M capability information sets. The second information may also include a third capability information set, which includes a first capability parameter that is different from the capability parameter in the first reference set. The third capability information set may be any one of the M capability information sets.

[0192] Alternatively, the aforementioned second information may also include a second reference set, which includes capability parameters of the M capability information sets. The second information may also include a fourth capability information set, which includes second capability parameters. The second capability parameters are one or more capability parameters in the second reference set that are not supported by the fourth capability information set, and / or capability parameters supported by the fourth capability information set that have different values ​​from those in the second reference set. The fourth capability information set may be any one of the M capability information sets.

[0193] For details on this part, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0194] 303. The terminal device sends third information, which requests an update to the terminal device's capability information. This third information instructs the terminal device to update its capability information to a third capability information set, which is one of the M capability information sets. Correspondingly, the network device receives this third information.

[0195] In this scenario, the terminal device is in RRC connected state. The terminal device requests a capability update. For example, the terminal device can report the identifier of a third capability information set so that the network device knows the updated capability information requested by the terminal device. Optionally, this third information can be carried in a capability update request message.

[0196] For details on this part, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0197] 304. The network device sends a fourth message, which indicates the identifier of the effective capability information set. Accordingly, the terminal device receives the fourth message.

[0198] Alternatively, network devices can instruct the acceptance or rejection of capability update requests from terminal devices.

[0199] For details on this part, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0200] 305. Network devices perform RRC configuration on terminal devices based on the updated capabilities.

[0201] In one possible implementation, in response to the aforementioned third information, the network device sends a first message indicating an RRC configuration. For example, the first message could be an RRC reconfiguration message. Optionally, the first message includes fifth information indicating that the RRC configuration is a full configuration. Optionally, the first message includes sixth information indicating the identifier of the capability set referenced by the RRC configuration; or, the first message includes seventh information indicating whether the RRC configuration is based on updated capabilities. For a detailed description of this part, please refer to step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0202] In one possible implementation, the communication method does not include step 304. When the network device performs RRC configuration on the terminal device based on the updated capabilities, the network device may indicate whether this reconfiguration is a response to the capability update, or indicate the effective capability identifier, etc.

[0203] This example illustrates capability updates when the terminal device is in RRC connected state. It should be noted that the example shown in Figure 3, where the terminal device reports M sets of capability information and performs capability updates, is presented to the same network device. Understandably, the terminal device can also report M sets of capability information to a first network device and send capability update requests to a second network device. For example, after initial registration, the terminal device reports M sets of capability information to the first network device, which then stores the UE capabilities in the core network device. The terminal device can then move, for example, in either RRC connected state or non-RRC connected state. The terminal device sending capability changes can occur at the new base station (such as the second network device) it moves to. In this case, referring to Figure 3, steps 301 and 302 correspond to the first network device, and steps 303-305 correspond to the second network device. For details, please refer to the embodiment shown in Figure 3; further elaboration is omitted here.

[0204] Scenario 2: The terminal device undergoes an RRC state transition (from RRC idle state or RRC inactive state to RRC connected state).

[0205] Referring to Figure 4, the communication method may include steps 401-407, as follows:

[0206] 401. The network device sends first information, which is used to query the capability information of the terminal device. Accordingly, the terminal device receives the first information.

[0207] 402. The terminal device sends second information, which indicates M sets of capability information supported by the terminal device. The second information includes a first frequency band combination supported by the terminal device and also includes first identification information, which indicates that the first frequency band combination belongs to one or more capability sets among the M sets of capability information. The M sets of capability information are used by the terminal device to update its capabilities. Accordingly, the network device receives the second information.

[0208] For details on this part, please refer to the description of step 302 in the embodiment shown in Figure 3, which will not be repeated here.

[0209] 403. The network device forwards the M capability information sets to the core network device. Accordingly, the core network device receives and stores the M capability information sets.

[0210] After receiving the terminal device's capability information, the network device forwards it to the core network device, and the core network stores the terminal device's capabilities.

[0211] 404. Network device releases RRC connection.

[0212] For example, when there is no ongoing service, the previous serving base station releases the RRC connection, and the terminal device enters the RRC idle state. After release, the base station deletes the context information stored for that terminal device. This context information includes the terminal device's capability information.

[0213] 405. The terminal device sends an RRC connection establishment request, which indicates the identifier of the capability information set for this RRC connection to take effect. Accordingly, the network device receives the RRC connection establishment request.

[0214] For example, when a service arrives, the terminal device requests to establish an RRC connection. During the RRC connection establishment process, the terminal device indicates which capability is applied (or activated) for this RRC connection. For instance, the terminal device indicates an identifier for the set of capability information to be applied. In one possible implementation, this identifier is carried in the RRC connection establishment completion message.

[0215] Understandably, the above implementation method also applies to RRC reconstruction and RRC recovery scenarios. For example, when a terminal device undergoes RRC reconstruction (such as due to the failure of the primary serving cell's radio link) or recovers from an inactive RRC state to a connected RRC state, the identifier of the capability information set applied (or activated) during the RRC connection reconstruction or recovery process can be indicated. For instance, the message carrying the identifier of the capability information set can be an RRC connection reconstruction completion message or an RRC connection recovery completion message. Of course, the identifier of the capability information set can also be carried in a capability update request message; this solution does not limit this.

[0216] 406. The network device sends a request to the core network device to obtain the set of M capability information.

[0217] For example, in an RRC establishment scenario, after receiving a connection establishment request from a terminal device, the network device obtains a set of M capability information of the terminal device stored in the core network device (e.g., access and mobility management function, AMF) and determines the set of capability information for this RRC connection application based on the identifier indicated by the terminal device.

[0218] For example, in an RRC reconstruction scenario, the network device obtains a set of M capability information stored in the terminal device context from, for example, the previous serving base station.

[0219] For example, in the RRC recovery scenario, the network device stores a set of M capability information of the non-connected terminal device.

[0220] 407. The network device performs RRC configuration on the terminal device based on the updated capability information set.

[0221] In one possible implementation, the network device sends a first message indicating RRC configuration. For example, the first message could be an RRC reconfiguration message. Optionally, the first message includes fifth information indicating that the RRC configuration is a full configuration. Optionally, the first message indicates the identifier of the capability information set referenced in this RRC configuration. Alternatively, the first message indicates whether the configuration is a reconfiguration based on the identifier of the capability information set requested by the terminal device during connection establishment (e.g., the first message could indicate true or false). In one example, the network device sends a sixth message indicating the identifier of the capability information set referenced (or replaced by the referenced / based on) by the RRC configuration (which can be understood as this RRC configuration or the current RRC configuration). The implementation of this sixth message can be referred to the description of the fourth message in the embodiment shown in Figure 2, and will not be repeated here. In another example, the network device sends a seventh message, which is used to indicate whether the RRC configuration is based on the updated capability information. For example, the seventh message is 1 bit. If the bit is set to 1, it indicates that the RRC configuration is based on the updated capability. If the bit is set to 0, it indicates that the RRC configuration is based on the capability before the update (or can be understood as the old capability). Alternatively, the presence of this bit indicates that the RRC configuration is based on the updated capability. If the bit is set to default, it indicates that the RRC configuration is based on the capability before the update.

[0222] Optionally, the network device can use the full configuration during the first RRC configuration after the RRC connection is established.

[0223] For details on this part, please refer to the description of step 305 in the embodiment shown in Figure 3, which will not be repeated here.

[0224] This example illustrates capability updates during a terminal device's RRC state transition. It's important to note that after a terminal device enters a disconnected state, the base station can delete the terminal device's capabilities. When the terminal device re-enters the connected state (possibly by a different base station), the base station that established the RRC connection with the terminal device can retrieve the terminal device's capabilities from the core network equipment. In this case, steps 401, 402, and 403 correspond to the first network device, step 404 to the second network device, and steps 405, 406, and 407 to the third network device. The first and second network devices can be the same or different. The second and third network devices can also be the same or different. Furthermore, the first, second, and third network devices can all be different from each other. For example, after the first network device queries the terminal device's capabilities, the terminal device switches to the second network device, and the second network device then releases the terminal device into the RRC idle state. The third network device is the one that re-establishes the RRC connection for the terminal device.

[0225] Scenario 3: Cell handover scenario for terminal device (from source cell to target cell).

[0226] Referring to Figure 5, the communication method may include steps 501-508, as follows:

[0227] 501. The first network device sends first information, which is used to query the capability information of the terminal device. Accordingly, the terminal device receives the first information.

[0228] For example, the first network device could be a source base station, etc.

[0229] 502. The terminal device sends second information, which indicates M sets of capability information supported by the terminal device. The second information includes a first frequency band combination supported by the terminal device and also includes first identification information, which indicates that the first frequency band combination belongs to one or more capability sets among the M sets of capability information. The M sets of capability information are used by the terminal device to update its capabilities. Accordingly, the first network device receives the second information.

[0230] For details on this part, please refer to the description of step 302 in the embodiment shown in Figure 3, which will not be repeated here.

[0231] 503. The first network device forwards the M capability information sets to the second network device. Accordingly, the second network device receives the M capability information sets and stores them.

[0232] 504. The terminal device sends a capability update request, which indicates the identifier of the updated capability information set. Accordingly, the first network device receives the request.

[0233] 505. The first network device sends a handover request to the second network device to request the handover of the aforementioned terminal device to the second network device. The second network device approves (or agrees to) the handover request, sends a handover request confirmation to the first network device, and provides the first network device with a first RRC message (e.g., an RRC reconfiguration message). This message is used to carry information related to the target cell (e.g., target cell identifier, security algorithm, etc.) or configuration information of the target cell (e.g., configuration information of random access resources). The first RRC message is forwarded by the first network device to the terminal device.

[0234] For example, before the serving base station (source base station, i.e., the first network device) instructs the terminal device to switch to the target base station (i.e., the second network device) for a first time period (e.g., 1 second), the serving base station receives a capability update request sent by the terminal device. The source base station sends the M sets of capability information contained in the terminal device context and the identifier of the updated capability information set indicated by the terminal device to the target base station. The target base station generates a first RRC message based on the updated capability information set and forwards it to the terminal device through the source base station.

[0235] Alternatively, within a first time period (e.g., 1 second) after the serving base station (source base station, i.e., the first network device) instructs the terminal device to switch to the target base station (i.e., the second network device), the serving base station receives a capability update request sent by the terminal device. The source base station sends the M sets of capability information contained in the terminal device context and the identifier of the capability information set previously used by the terminal device (i.e., the identifier of the capability information set before the update) to the target base station. At this time, the target base station is unaware that the terminal device has undergone a capability update, and still generates a first RRC message based on the previously used capability information set, and sends it to the source base station, which then forwards the first RRC message to the terminal device.

[0236] When a terminal device undergoes inter-base station handover, the target base station can obtain the terminal device's capabilities from the core network equipment or from the source base station.

[0237] 506. The terminal device releases the connection to the source cell and initiates access to the target cell for handover.

[0238] The terminal device receives the first RRC message from the target base station sent by the source base station, instructing the terminal device to perform a handover. The terminal device releases the source cell connection and initiates access to the target cell for the handover.

[0239] 507. The terminal device sends a second RRC message to the second network device to indicate that the handover is complete. The second RRC message can be a response message to the first RRC message; for example, the second RRC message is an RRC reconfiguration completion message. The second RRC message also indicates the identifier of the updated capability information set.

[0240] If the terminal device sends a capability update request within 1 second of receiving the handover command, then after successfully establishing random access with the target base station, the terminal device sends a second RRC message to the target base station. This second RRC message again instructs the terminal device to request a capability update and indicates the identifier of the updated capability information set. By including the capability update request in the second message, the terminal device can send the capability update request to the target base station more quickly after accessing the target cell when it has a capability update need near the handover time, reducing the latency of capability updates in handover scenarios.

[0241] 508. The second network device performs RRC configuration on the terminal device based on the updated capability information set.

[0242] For details on this part, please refer to the description of step 407 in the embodiment shown in Figure 4, which will not be repeated here.

[0243] This example illustrates a scenario where a terminal device is updating its capabilities during cell handover. It's important to note that when a terminal device undergoes a handover in connected mode, M sets of capabilities are sent from the source base station to the target base station. However, this source base station may not be the base station that queried the terminal device for UE capabilities. In this case, steps 501 and 502 can correspond to the first network device, and steps 503, 504, and 505 can correspond to the second network device. The first and second network devices can be the same or different.

[0244] Referring to Figure 6, a flowchart illustrating another communication method provided in this application embodiment is shown. Optionally, this method can be applied to the aforementioned communication system, such as the communication system shown in Figure 1. The communication method shown in Figure 6 may include steps 601-603. Steps 601-603 are as follows:

[0245] 601. The network device sends first information, which is used to query the capability information of the terminal device. Accordingly, the terminal device receives the first information.

[0246] Optionally, the first information includes filtering conditions for capability queries. That is, when querying the capabilities of a terminal device, the network device instructs the frequency band (also known as a frequency range) to be queried as a filtering condition to filter the frequency band combinations reported by the terminal device. In this way, the frequency band combinations reported by the terminal device only include those composed of the frequency bands queried by the network device, and do not include frequency bands not queried by the network device. Thus, the network device can query only the frequency bands of interest, such as only the frequency bands managed by a specific operator. For a description of this step, please refer to the description of step 201 in the embodiment shown in Figure 2, which will not be repeated here.

[0247] 602. The terminal device sends second information, which indicates a set of reference capability information supported by the terminal device. Accordingly, the network device receives the second information.

[0248] The reference capability information set can be one or more of the multiple capability information sets supported by the terminal device. Alternatively, it may not belong to any of the multiple capability information sets supported by the terminal device. Reporting this reference capability information set facilitates the reporting of other capabilities by the terminal device. For a description of the multiple capability information sets supported by the terminal device, please refer to step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0249] In one possible implementation, the reference capability information set includes multiple frequency band combinations supported by the terminal device. For example, the reference capability information set includes all frequency band combinations supported by the terminal device. For a description of the frequency band combinations supported by the terminal device, please refer to step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0250] Optionally, the reference capability information set can be independent of the frequency band filtering conditions queried by the network device; in other words, the reference capability information set reported by the terminal device ignores the frequency band filtering conditions issued by the network device. However, if the frequency band combinations included in the reference capability set are determined based on the frequency bands queried by the network device, when the terminal device moves between different base stations, if the target base station the terminal device moves to has a different frequency band than the source base station, the target base station may re-trigger the capability query, requiring the terminal device to report the frequency band combinations associated with the target base station's interest. This increases the signaling overhead of the terminal device frequently reporting the reference capability set, or may lead to a misalignment between the terminal device and the network device when indicating the capabilities of the current application. For example, if the terminal device and the network device are not referencing the same reference capability information set, the identifier for the frequency band combination indicated by the terminal device for the current application may point to different frequency band combinations. In this solution, the reference capability information set is independent of the network device's filtering conditions, so the reference capability information set will not change frequently, ensuring alignment between the terminal device and the network device.

[0251] 603. The terminal device further sends third information, which, together with a reference capability information set, is used to determine a first capability information set, which is the capability information set currently used by the terminal device. The reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information indicates that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set. Accordingly, the network device receives the third information.

[0252] In one possible implementation, the third information indicates the identifier of the first frequency band combination, which is the position or sequence number of the first frequency band combination in the reference capability information set. For example, the identifier of the first frequency band combination is 1, 2, etc. Optionally, the identifier of the first frequency band combination is 1, the identifier of the second frequency band combination is 2, and so on. For example, the reference capability information set includes all 1000 frequency band combinations that the terminal device may support, each frequency band combination has a unique identifier (e.g., from 1 to 1000), and the reference capability information set includes the capabilities of 1000 frequency band combinations. For example, the currently used capability information set includes BC#1 to BC#200, i.e., the first 200 frequency band combinations, and the terminal device indicates the identifiers of these 200 frequency band combinations. It is understood that for frequency band combinations with the same frequency band composition, the identifier of one frequency band combination corresponds to a unique associated frequency band combination capability. If any capability parameter associated with frequency band combinations with the same frequency band composition is different, then two different frequency band combinations can correspond to each other. For example, the band combination {bandA+bandB} can correspond to two different capabilities: 1. {bandA: 1CC, 2-layer MIMO, 100MHz carrier bandwidth}, {bandB: 1CC, 2-layer MIMO, 60MHz carrier bandwidth}; 2. {bandA: 1CC, 2-layer MIMO, 80MHz carrier bandwidth}, {bandB: 1CC, 2-layer MIMO, 80MHz carrier bandwidth}. These two capabilities correspond to two band combinations, each with a different band combination identifier. For example, the first capability corresponds to BC#1, and the second capability corresponds to BC#2.

[0253] In another possible implementation, the third information indicates the identifier of the first frequency band combination and the identifier of the feature set FS associated with each frequency band in the first frequency band combination. Each feature set includes capability parameters for each frequency band level and each frequency band combination level. For example, the aforementioned {bandA+bandB} can correspond to the same identifier for the same frequency band combination (e.g., BC#1), but this identifier BC#1 is associated with two (sets of) different capabilities: the first capability has feature sets {FS#1, FS#2} associated with each frequency band; the second capability has feature sets {FS#3, FS#4} associated with each frequency band. In this case, the terminal device indicates the currently used frequency band combination capability by indicating not only the identifier of the frequency band combination but also the identifier of the feature set associated with each frequency band in the frequency band combination, thus reducing the total number of frequency band combinations.

[0254] In the example above, based on the indication of the third information and combined with the aforementioned set of reference capability information, the network device can know the first set of capability information currently used by the terminal device. This avoids the repeated reporting of frequency band combination capabilities, reduces the signaling overhead of reporting capability information sets, and also facilitates the reporting of updated capabilities by the terminal device with less signaling overhead when updating capabilities in the future.

[0255] Understandably, the second and third information mentioned above can be carried in the same message. For example, both the second and third information can be carried in the UE capability information, which can refer to the terminal device's radio access capabilities. In one possible implementation, the terminal device receives a capability query message sent by the network device and reports its capability information to the network device. Of course, the second and third information can also be carried in different messages. For example, the second information can be carried in the UE capability information, and the third information can be carried in the terminal device's request for capability updates message. This solution does not impose any restrictions on this.

[0256] In one possible implementation, the set of capability information currently used by the terminal device can be determined based on the filtering conditions of the network device. That is, the terminal device can indicate that the currently used frequency band combination only includes the frequency bands queried by the network device in the query message, and does not include frequency bands not queried by the network device.

[0257] The above example illustrates the situation where the reference capability information set contains a frequency band combination that is the same as the frequency band combination in the first capability information set. It is understandable that if the first capability information set also contains other frequency band combinations that do not belong to the aforementioned reference capability information set, the terminal device can directly report the other frequency band combinations without relying on the reference capability information set.

[0258] The above example uses the terminal device's ability to report frequency band combination (BC). The following section introduces other capabilities of the terminal device (such as terminal device-level capabilities, frequency band-level capabilities, etc.).

[0259] In one possible implementation, the second information further includes a first reference set, which includes common capability parameters from multiple capability information sets supported by the terminal device. The third information includes a first capability parameter, which is a capability parameter different from those in the first reference set. The first capability information set includes the first capability parameter.

[0260] For example, the first reference set includes a set of minimum capability parameters for capabilities other than the capabilities of the aforementioned frequency band combinations.

[0261] For details regarding this introduction, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0262] In this example, for other capabilities reported by the terminal device (such as terminal device-level capabilities, frequency band-level capabilities, etc.), a first reference set is reported. This first reference set includes capability parameters common to multiple capability information sets. In this way, when reporting other capability information sets, only the parameters that are different from or have different values ​​than the capability parameters in the first reference set need to be reported, which can reduce the signaling overhead of repeatedly reporting capability parameters.

[0263] In another possible implementation, the second information includes a second reference set, which includes capability parameters of multiple capability information sets supported by the terminal device, and the third information includes a second capability parameter, which is one or more capability parameters in the second reference set that are not supported by the first capability information set, and / or capability parameters supported by the first capability information set that have different values ​​from those in the second reference set.

[0264] For example, the second reference set includes a set of maximum capability parameters for capabilities other than the aforementioned frequency band combinations (also referred to as the full capabilities supported by the terminal device). Preferably, the maximum capability of the terminal device may be related to key performance indicators of the network device or communication system. The initial reporting of the set of maximum capability parameters by the terminal device helps the network device accurately determine the peak performance of the terminal device and ensure that the network performance indicators are met. For details on this, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0265] In this example, for other capabilities reported by the terminal device (such as terminal device-level capabilities, frequency band-level capabilities, etc.), a second reference set is reported. In this way, when reporting other capability information sets, it is only necessary to indicate the capability parameters or values ​​that the capability information set does not support relative to the second reference set. This can reduce the signaling overhead of repeatedly reporting capability parameters.

[0266] Optionally, the second and third information can be carried in different messages. In this case, the third information can be carried in any of the following messages: capability update request message, RRC connection establishment completion message, RRC recovery completion message, RRC reconstruction completion message, and RRC reconfiguration completion message. For a detailed description of this part, please refer to Figures 3, 4, and 5 above, which will not be repeated here. For example, in an RRC state transition scenario, the terminal device can indicate the identifier of the currently effective frequency band combination or feature set identifier, and / or the differences between the currently effective capabilities (such as terminal device-level capabilities or frequency band-level capabilities) and the aforementioned first or second reference set in the RRC connection establishment / reconstruction / recovery completion message. Furthermore, in a cell handover scenario, if the terminal device has sent a capability update request to the source base station within 1 second of receiving the handover command, then after successfully accessing the target base station, it can optionally request a capability update again in the RRC reconfiguration completion message, indicating the currently effective frequency band combination capabilities and / or terminal device-level capabilities and frequency band-level capabilities.

[0267] For example, the terminal device further sends a first message requesting an update to its capability information, the first message including third information. Then, the network device sends a fourth message indicating the identifier of the effective capability information set. Accordingly, the terminal device receives the fourth message. For a description of this part, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0268] In one possible implementation, in response to the aforementioned third information, the network device sends a second message indicating RRC configuration. Optionally, the second message includes fifth information indicating that the RRC configuration is full. Accordingly, the terminal device receives the second message. For a description of this part, please refer to the description of step 202 in the embodiment shown in Figure 2, which will not be repeated here.

[0269] In one possible implementation, when a terminal device requests a capability update, if the request does not indicate updated capability information, the network device may default to using the reference capability information set corresponding to the unindicated frequency band combination, or the first or second reference set corresponding to terminal device-level capabilities, frequency band-level capabilities, etc. For example, if the terminal device only indicates the identifier of the currently effective frequency band combination when requesting a capability update, without indicating the currently effective terminal device-level capabilities, frequency band-level capabilities, etc., then the network device will default to the aforementioned first or second reference set.

[0270] In another possible implementation, when a terminal device requests a capability update, it only indicates the frequency band combination capabilities and / or terminal device-level capabilities, frequency band-level capabilities, etc., that have changed compared to the previously indicated capabilities. If the terminal device-level capabilities, frequency band-level capabilities, etc., have not changed compared to the previously indicated effective terminal device-level capabilities, frequency band-level capabilities, etc., the network device defaults to using the previously indicated effective terminal device-level capabilities, frequency band-level capabilities, etc. If the capabilities of a frequency band combination have not changed compared to the previously indicated effective frequency band combination capabilities, the network device defaults to using the previously indicated effective frequency band combination capabilities. If only the terminal device-level capabilities, frequency band-level capabilities, etc., have changed, and the capabilities of the frequency band combination have not changed compared to the previously indicated effective frequency band combination capabilities, the terminal device, when requesting a capability update, may only indicate the currently effective terminal device-level capabilities, frequency band-level capabilities, etc. In this case, the network device defaults to either the currently effective frequency band combination capabilities being the same as the previously indicated effective frequency band combination capabilities, or the network device defaults to the previously indicated effective frequency band combination capabilities not having changed.

[0271] In this example, the network device sends first information to query the capability information of the terminal device. The terminal device sends second and third information. The second information indicates a reference capability information set supported by the terminal device. The third information and the reference capability information set are used to determine a first capability information set, which is the capability information set currently used by the terminal device. The reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information indicates that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set. Thus, determining other capability information sets based on the third information and the reference capability information set avoids duplicate reporting of frequency band combination capabilities, reduces signaling overhead and latency in reporting capability information sets, and also facilitates subsequent capability updates by the terminal device with less signaling overhead.

[0272] On the other hand, terminal devices do not need to report M sets of capability information in advance; they only need to report a reference set of capability information, and on this basis, they can flexibly report other sets of capability information.

[0273] Referring to Figure 7, another communication method provided in this application embodiment is illustrated. Optionally, this method can be applied to the aforementioned communication system, such as the communication system shown in Figure 1. The communication method shown in Figure 7 may include steps 701-705. Steps 701-705 are as follows:

[0274] 701. The network device sends first information, which is used to query the capability information of the terminal device. Accordingly, the terminal device receives the first information.

[0275] 702. The terminal device sends second information, which indicates a first set of capability information supported by the terminal device. Accordingly, the network device receives the second information.

[0276] For example, the first set of capability information supported by the terminal device can be M sets of capability information supported by the terminal device. Optionally, the M sets of capability information shown in the embodiment of Figure 2 can be used for reporting. Alternatively, the set of capability information supported by the terminal device can be the reference set of capability information shown in the embodiment of Figure 6. Or, it can be the set of capability information currently used by the terminal device, etc. This solution does not impose any restrictions on this.

[0277] 703. The terminal device further sends third information, which requests an update to the terminal device's capability information. This third information instructs the terminal device to update its capability information to a second capability information set. This second capability information set is different from the first capability information set described above. Accordingly, the network device receives this third information.

[0278] 704. Optionally, the network device sends a fourth message indicating its ability to receive updated capability information from the terminal device. Accordingly, the terminal device receives the fourth message.

[0279] Alternatively, network devices can also indicate whether to accept or reject capability update requests from end devices.

[0280] 705. The network device sends a first message, which is used to indicate the RRC configuration.

[0281] For example, the first message could be an RRC reconfiguration message.

[0282] For example, the first message includes a seventh piece of information, which indicates whether the current RRC configuration is based on the updated capability information of the terminal device, or can be understood as indicating that the terminal device has the updated capability information in effect. In one example, the seventh piece of information is 1 bit. A bit set to 1 indicates that the RRC configuration is based on the updated capability, and a bit set to 0 indicates that the RRC configuration is based on the capability before the update (or can be understood as the old capability); or, the presence of this bit indicates that the RRC configuration is based on the updated capability, and the default bit indicates that the RRC configuration is based on the capability before the update; or, the presence of this bit indicates that the terminal device has the updated capability in effect, or can be understood as indicating that the terminal device communicates with the network device according to the updated capability, and the absence of this bit indicates that the terminal device has not had the updated capability in effect, or can be understood as indicating that the terminal device communicates with the network device according to the unupdated capability (the capability before sending the capability update request).

[0283] The terminal device receives the first message and determines whether to activate the new capability based on the seventh information in the first message. If the seventh information indicates that the terminal device should activate the new capability, or if the seventh information indicates that the RRC configuration is based on the updated capability, the terminal device uses the updated capability to communicate with the network device.

[0284] This example demonstrates how instructing network devices in the RRC configuration whether to configure based on updated capabilities allows for greater flexibility in determining when new capabilities should take effect. For instance, upon receiving a capability update request from a terminal device, the network device can still send an RRC configuration based on the previous capabilities. In this case, the first message might indicate that the new capability is not taking effect, or indicate that the current RRC configuration is based on the previous capabilities. Only after the network device determines that it can communicate with the terminal device using the new capabilities should it instruct the terminal device to take effect. This approach, on the one hand, better coordinates with the network device's resource allocation algorithms and scheduling strategies, enabling the network device to adjust network decisions based on the updated capabilities of the terminal device, reducing the impact on services; on the other hand, it allows the network device more time to determine the incremental configuration based on the new capabilities, avoiding a full reconfiguration and ensuring communication continuity, thus preventing service interruptions.

[0285] It should be noted that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0286] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below. It is understood that the division of multiple units or modules in the various apparatus embodiments of this application is only a logical division based on function and is not intended to limit the specific structure of the apparatus. In specific implementations, some functional modules may be subdivided into more smaller functional modules, and some functional modules may be combined into a single functional module. However, regardless of whether these functional modules are subdivided or combined, the general flow executed by the apparatus is the same. For example, some apparatuses include a receiving unit and a transmitting unit. In some designs, the transmitting unit and the receiving unit can also be integrated into a communication unit, which can implement the functions implemented by the receiving unit and the transmitting unit. Typically, each unit corresponds to its own program code (or program instructions). When the program code corresponding to each unit runs on the processor, it causes the unit to be controlled by the processing unit to execute the corresponding flow and thus achieve the corresponding function.

[0287] This application also provides an apparatus for implementing any of the above methods. For example, a communication apparatus is provided that includes a module (or means) for implementing the steps performed by the terminal device in any of the above methods.

[0288] For example, referring to FIG8, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device is used to implement the aforementioned communication method, such as the communication method shown in FIG2-FIG5.

[0289] As shown in Figure 8, the device may include a communication module 801, as detailed below:

[0290] Communication module 801 is used to receive first information, which is used to query the capability information of the terminal device;

[0291] The communication module 801 is further configured to send second information, which indicates M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more sets of capability information in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

[0292] In one possible implementation, the at least one frequency band combination includes a first frequency band combination, and the second information includes first identification information, which indicates that the first frequency band combination belongs to one or more capability information sets among M capability information sets.

[0293] In one possible implementation, the second information includes a first capability information set, the first capability information set including at least one frequency band combination, the second information including second identification information corresponding to the second capability information set, the second identification information being used to indicate the second frequency band combination, the second frequency band combination being a frequency band combination among at least one frequency band combination included in the first capability information set, and the second capability information set being a capability information set among the M capability information sets.

[0294] In one possible implementation, the second information further includes a first reference set, which includes common capability parameters among the M capability information sets. The second information also includes a third capability information set, which includes a first capability parameter that is different from the capability parameter in the first reference set. The third capability information set is any one of the M capability information sets.

[0295] In another possible implementation, the second information further includes a second reference set, which includes capability parameters of M capability information sets. The second information also includes a fourth capability information set, which includes second capability parameters. The second capability parameters are one or more capability parameters in the second reference set that are not supported by the fourth capability information set, and / or capability parameters supported by the fourth capability information set that have different values ​​from those in the second reference set. The fourth capability information set is any one of the M capability information sets.

[0296] In one possible implementation, the communication module 801 is further configured to send third information, which requests an update to the capability information of the terminal device. The third information instructs the capability information of the terminal device to be updated to a fifth capability information set, which is one of the M capability information sets.

[0297] In one possible implementation, the communication module 801 is further configured to receive fourth information, which is used to indicate the identifier of the effective capability information set.

[0298] In one possible implementation, the communication module 801 is further configured to receive a first message indicating RRC configuration, the first message including fifth information indicating that the RRC configuration is full configuration.

[0299] For a description of each of the above modules, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0300] This application also provides an apparatus for implementing any of the above methods. For example, a communication apparatus is provided that includes a module (or means) for implementing the steps performed by the network device in any of the above methods.

[0301] For example, referring to FIG8, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device is used to implement the aforementioned communication method, such as the communication method shown in FIG2-FIG5.

[0302] As shown in Figure 8, the device may include a communication module 801, as detailed below:

[0303] The communication module 801 is used to send first information, which is used to query the capability information of the terminal device;

[0304] The communication module 801 is further configured to receive second information, which indicates M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more sets of capability information in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

[0305] In one possible implementation, the communication module 801 is further configured to receive third information, which requests an update to the capability information of the terminal device. The third information instructs the capability information of the terminal device to be updated to a fifth capability information set, which is one of the M capability information sets.

[0306] In one possible implementation, the communication module 801 is further configured to send a fourth message indicating the identifier of the effective capability information set.

[0307] In one possible implementation, the communication module 801 is further configured to send a first message in response to the third information, the first message indicating RRC configuration, the first message including fifth information indicating that the RRC configuration is a full configuration.

[0308] For a description of each of the above modules, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0309] This application also provides an apparatus for implementing any of the above methods. For example, a communication apparatus is provided that includes a module (or means) for implementing the steps performed by the terminal device in any of the above methods.

[0310] For example, referring to FIG8, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device is used to implement the aforementioned communication method, such as the communication method shown in FIG6.

[0311] As shown in Figure 8, the device may include a communication module 801, as detailed below:

[0312] Communication module 801 is used to receive first information, which is used to query the capability information of the terminal device;

[0313] The communication module 801 is also used to send second information, which is used to indicate the set of reference capability information supported by the terminal device;

[0314] The communication module 801 is further configured to send third information, the third information and the reference capability information set being used to determine a first capability information set, the first capability information set being the capability information set currently used by the terminal device; wherein, the reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first capability information set includes a first frequency band combination, the first frequency band combination being the frequency band combination in the reference capability information set.

[0315] In one possible implementation, the third information indicates the identifier of the first frequency band combination, which is the position or sequence number of the first frequency band combination in the reference capability information set.

[0316] In one possible implementation, the second information includes a first reference set, which includes common capability parameters from multiple capability information sets supported by the terminal device, and the third information includes a first capability parameter, which is a capability parameter different from those in the first reference set, wherein the first capability information set includes the first capability parameter.

[0317] In another possible implementation, the second information includes a second reference set, which includes capability parameters of multiple capability information sets supported by the terminal device, and the third information includes a second capability parameter, which is one or more capability parameters in the second reference set that are not supported by the first capability information set, and / or capability parameters supported by the first capability information set that have different values ​​from those in the second reference set.

[0318] In one possible implementation, the communication module 801 is further configured to send a first message, which requests an update to the capability information of the terminal device, and the first message includes the third information.

[0319] For a description of each of the above modules, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0320] This application also provides an apparatus for implementing any of the above methods. For example, a communication apparatus is provided that includes a module (or means) for implementing the steps performed by the network device in any of the above methods.

[0321] For example, referring to FIG8, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device is used to implement the aforementioned communication method, such as the communication method shown in FIG6.

[0322] As shown in Figure 8, the device may include a communication module 801, as detailed below:

[0323] The communication module 801 is used to send first information, which is used to query the capability information of the terminal device;

[0324] The communication module 801 is also configured to receive second information, which is used to indicate the set of reference capability information supported by the terminal device;

[0325] The communication module 801 is further configured to receive third information, the third information and the reference capability information set being used to determine a first capability information set, the first capability information set being the capability information set currently used by the terminal device; wherein, the reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first capability information set includes a first frequency band combination, the first frequency band combination being a frequency band combination in the reference capability information set.

[0326] In one possible implementation, the communication module 801 is further configured to receive a first message, which requests an update to the capability information of the terminal device, and the first message includes the third information.

[0327] For a description of each of the above modules, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0328] It should be understood that the division of modules in the above devices is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, modules in a communication device can be implemented by a processor calling software; for example, a communication device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each module in the device. The processor can be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the modules in the device can be implemented as hardware circuits. The functionality of some or all units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD), such as a field-programmable gate array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the above units. All modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0329] Referring to FIG9, a schematic diagram of the hardware structure of another communication device provided in an embodiment of this application is shown. The communication device 900 shown in FIG9 includes one or more processors 901 (a processor is illustrated in the figure).

[0330] Processor 901 is a circuit with signal processing capabilities. In one implementation, processor 901 can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, processor 901 can achieve certain functions through the logical relationships of hardware circuits. These logical relationships of hardware circuits are fixed or reconfigurable. For example, processor 901 can be a hardware circuit implemented as an ASIC or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to achieve the functions of some or all of the above modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as a type of ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), or deep learning processing unit (DPU). The processor 901 is used to execute related programs to implement the functions required by the units in the communication device of the present application embodiment, or to execute the communication method of the method embodiment of the present application.

[0331] Optionally, the communication device 900 may also include a memory (e.g., memory 903, memory 904, memory 905) (shown as dashed lines in the figure). This memory is used to store instructions executed by the processor 901, or to store input data required for the processor 901 to execute instructions, or to store data generated after the processor 901 executes instructions.

[0332] Optionally, the memory may be located within the one or more processors (e.g., memory 903), or outside the one or more processors (e.g., memory 904, memory 905), or may include a storage portion located within the one or more processors and a storage portion located outside the one or more processors.

[0333] In this embodiment, the memory (e.g., memory 903, memory 904, memory 905) may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0334] Optionally, the communication device 900 may also include a communication interface 902 (shown as a dashed line in the figure). The processor 901 and the communication interface 902 are coupled together. The communication interface 902 can be a transceiver or interface circuit, a bus, a module, or other type of communication interface.

[0335] The memory can store programs. When the program stored in the memory is executed by the processor 901, the processor 901 and the communication interface 902 are used to execute the various steps of the communication method of the embodiments of this application.

[0336] As can be seen, each module in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms or a portion of the processing circuits in these processors.

[0337] Furthermore, the modules in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these modules are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or for implementing the functions of the modules of the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and GPU, etc.

[0338] It should be noted that although the device 900 shown in Figure 9 only illustrates the memory, processor, and communication interface, those skilled in the art should understand that in specific implementations, device 900 may also include other devices necessary for normal operation. Furthermore, depending on specific needs, those skilled in the art should understand that device 900 may also include hardware devices for implementing other additional functions. Moreover, those skilled in the art should understand that device 900 may only include the devices necessary for implementing the embodiments of this application, and not necessarily all the devices shown in Figure 9.

[0339] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform one or more steps of any of the above methods.

[0340] This application also provides a computer program product containing instructions. When the computer program product is run on a computer or processor, it causes the computer or processor to perform one or more steps of any of the methods described above.

[0341] It is understood that in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A. In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementation, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index, or indirectly indicating the information to be instructed by indicating other information, wherein there is an association between the other information and the information to be instructed. It is also possible to indicate only a part of the information to be instructed, while the other parts of the information to be instructed are known or agreed upon in advance. For example, the instruction of specific information can also be achieved by using the arrangement order of various information in advance (e.g., as specified by a protocol), thereby reducing the instruction overhead to a certain extent. The information to be instructed can be sent as a whole or divided into multiple sub-information to be sent separately, and the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0342] It should be understood that in the description of this application, unless otherwise stated, " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B can represent A or B; where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" do not necessarily imply difference. In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0343] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. The coupling, direct coupling, or communication connection shown or discussed between each other may be indirect coupling or communication connection through some interfaces, apparatuses, or units, and may be electrical, mechanical, or other forms.

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

[0345] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be read-only memory (ROM), random access memory (RAM), or magnetic media, such as floppy disks, hard disks, magnetic tapes, magnetic disks, or optical media, such as digital versatile discs (DVDs), or semiconductor media, such as solid-state disks (SSDs).

[0346] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of the embodiments of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of this application should be covered within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive first information, which is used to query the capability information of the terminal device; Send a second message, which indicates the M sets of capability information supported by the terminal device. The second message includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more sets of capability information in the M sets of capability information. The M sets of capability information are used by the terminal device to update its capabilities. M is a positive integer greater than or equal to 2.

2. The method according to claim 1, characterized in that, The at least one frequency band combination includes a first frequency band combination, and the second information includes first identification information, which is used to indicate that the first frequency band combination belongs to one or more capability information sets among the M capability information sets.

3. The method according to claim 1, characterized in that, The second information includes a first capability information set, the first capability information set including at least one of the frequency band combinations, the second information includes second identification information corresponding to the second capability information set, the second identification information is used to indicate the second frequency band combination, the second frequency band combination is a frequency band combination among at least one frequency band combination included in the first capability information set, and the second capability information set is a capability information set among the M capability information sets.

4. The method according to claim 3, characterized in that, The second identification information is the position or sequence number of the second frequency band combination in at least one frequency band combination included in the first capability information set.

5. The method according to claim 1, characterized in that, The second information also includes a first reference set, which includes common capability parameters from the M capability information sets. The second information also includes a third capability information set, which includes a first capability parameter, which is a capability parameter different from those in the first reference set. The third capability information set is any one of the M capability information sets; or... The second information also includes a second reference set, which includes capability parameters of the M capability information sets. The second information also includes a fourth capability information set, which includes second capability parameters. The second capability parameters are one or more capability parameters in the second reference set that are not supported by the fourth capability information set, and / or capability parameters supported by the fourth capability information set that have different values ​​from those in the second reference set. The fourth capability information set is any one of the M capability information sets.

6. The method according to any one of claims 1 to 5, characterized in that, The second information is also used to indicate the set of capability information currently in effect for the terminal device, wherein the set of capability information currently in effect is one of the M sets of capability information.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Send a third message, the third message being used to request an update to the capability information of the terminal device, the third message instructing the capability information of the terminal device to be updated to a fifth capability information set, the fifth capability information set being one of the M capability information sets.

8. The method according to claim 7, characterized in that, The method further includes: Receive a fourth piece of information, which is used to indicate the identifier of the effective capability information set.

9. The method according to claim 7 or 8, characterized in that, The method further includes: A first message is received, which is used to indicate the Radio Resource Control (RRC) configuration. The first message includes fifth information, which is used to indicate that the RRC configuration is a full configuration.

10. The method according to any one of claims 7 to 9, characterized in that, The third information is carried in any of the following messages: Capability update request message, RRC connection establishment complete message, RRC recovery complete message, RRC reconstruction complete message, RRC reconfiguration complete message.

11. A communication method, characterized in that, include: Receive first information, which is used to query the capability information of the terminal device; Send a second message, the second message being used to indicate the set of reference capability information supported by the terminal device; A third message is sent, which, together with the reference capability information set, is used to determine a first capability information set, which is the capability information set currently used by the terminal device; wherein, the reference capability information set includes at least one frequency band combination supported by the terminal device, and the third message is used to indicate that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set.

12. The method according to claim 11, characterized in that, The third information indicates the identifier of the first frequency band combination, which is the position or sequence number of the first frequency band combination in the reference capability information set.

13. The method according to claim 11, characterized in that, The second information includes a first reference set, which includes common capability parameters from multiple capability information sets supported by the terminal device; the third information includes a first capability parameter, which is a capability parameter different from those in the first reference set; wherein, the first capability information set includes the first capability parameter; or, The second information includes a second reference set, which includes capability parameters of multiple capability information sets supported by the terminal device. The third information includes a second capability parameter, which is one or more capability parameters in the second reference set that are not supported by the first capability information set, and / or capability parameters supported by the first capability information set that have different values ​​from those in the second reference set.

14. The method according to any one of claims 11 to 13, characterized in that, The method further includes: Send a first message, which requests an update to the capability information of the terminal device, and the first message includes the third information.

15. The method according to claim 14, characterized in that, The method further includes: Receive a fourth piece of information, which is used to indicate the identifier of the effective capability information set.

16. The method according to any one of claims 11 to 15, characterized in that, The method further includes: A second message is received, which is used to indicate the RRC configuration. The second message includes fifth information, which is used to indicate that the RRC configuration is a full configuration.

17. The method according to any one of claims 11 to 16, characterized in that, The third information is carried in any of the following messages: Capability update request message, RRC connection establishment complete message, RRC recovery complete message, RRC reconstruction complete message, RRC reconfiguration complete message.

18. A communication method, characterized in that, include: Send a first message, which is used to query the capability information of the terminal device; The terminal device receives second information, which indicates M sets of capability information supported by the terminal device. The second information includes at least one frequency band combination supported by the terminal device. Each frequency band combination is associated with one or more sets of capability information in the M sets of capability information. The M sets of capability information are used by the terminal device to perform capability updates, where M is a positive integer greater than or equal to 2.

19. The method according to claim 18, characterized in that, The at least one frequency band combination includes a first frequency band combination, and the second information includes first identification information, which is used to indicate that the first frequency band combination belongs to one or more capability information sets among the M capability information sets.

20. The method according to claim 18, characterized in that, The second information includes a first capability information set, the first capability information set including at least one of the frequency band combinations, the second information includes second identification information corresponding to the second capability information set, the second identification information is used to indicate the second frequency band combination, the second frequency band combination is a frequency band combination among at least one frequency band combination included in the first capability information set, and the second capability information set is a capability information set among the M capability information sets.

21. The method according to claim 18, characterized in that, The second information also includes a first reference set, which includes common capability parameters from the M capability information sets. The second information also includes a third capability information set, which includes a first capability parameter, which is a capability parameter different from those in the first reference set. The third capability information set is any one of the M capability information sets; or... The second information also includes a second reference set, which includes capability parameters of the M capability information sets. The second information also includes a fourth capability information set, which includes second capability parameters. The second capability parameters are one or more capability parameters in the second reference set that are not supported by the fourth capability information set, and / or capability parameters supported by the fourth capability information set that have different values ​​from those in the second reference set. The fourth capability information set is any one of the M capability information sets.

22. The method according to any one of claims 18 to 21, characterized in that, The method further includes: The third information is received, which is used to request an update to the capability information of the terminal device. The third information indicates that the capability information of the terminal device is updated to a fifth capability information set, which is one of the M capability information sets.

23. The method according to claim 22, characterized in that, The method further includes: Send a fourth message, which is used to indicate the identifier of the effective capability information set.

24. The method according to claim 22 or 23, characterized in that, The method further includes: In response to the third information, a first message is sent, the first message being used to indicate RRC configuration, the first message including fifth information, the fifth information being used to indicate that the RRC configuration is a full configuration.

25. A communication method, characterized in that, include: Send a first message, which is used to query the capability information of the terminal device; Receive second information, the second information being used to indicate a set of reference capability information supported by the terminal device; The third information and the reference capability information set are used to determine a first capability information set, which is the capability information set currently used by the terminal device; wherein, the reference capability information set includes at least one frequency band combination supported by the terminal device, and the third information is used to indicate that the first capability information set includes a first frequency band combination, which is a frequency band combination in the reference capability information set.

26. The method according to claim 25, characterized in that, The second information includes a first reference set, which includes common capability parameters from multiple capability information sets supported by the terminal device; the third information includes a first capability parameter, which is a capability parameter different from those in the first reference set; wherein, the first capability information set includes the first capability parameter; or, The second information includes a second reference set, which includes capability parameters of multiple capability information sets supported by the terminal device. The third information includes a second capability parameter, which is one or more capability parameters in the second reference set that are not supported by the first capability information set, and / or capability parameters supported by the first capability information set that have different values ​​from those in the second reference set.

27. The method according to claim 25 or 26, characterized in that, The method further includes: A first message is received, which is used to request an update of the capability information of the terminal device, and the first message includes the third information.

28. The method according to any one of claims 25 to 27, characterized in that, The method further includes: Send a second message, which is used to indicate the RRC configuration. The second message includes fifth information, which is used to indicate that the RRC configuration is a full configuration.

29. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 1-28.

30. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the method as described in any one of claims 1-28 is performed.

Images