CN110958603A

CN110958603A - Capability reporting method and device

Info

Publication number: CN110958603A
Application number: CN201811137734.9A
Authority: CN
Inventors: 邝奕如; 王丁; 王键
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-09-27
Filing date: 2018-09-27
Publication date: 2020-04-03
Anticipated expiration: 2038-09-27
Also published as: CN110958603B; WO2020063521A1

Abstract

The application provides a capability reporting method and device, relates to the technical field of communication, and can solve the problem that signaling overhead is high when a terminal reports capability in the prior art. The method comprises the following steps: the terminal device sends a capability message to the network device, wherein the capability message comprises a first information unit, a second information unit and an association relation between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level. The method is applied to the process of reporting the capability message by the terminal.

Description

Capability reporting method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a capability reporting method and apparatus.

Background

Generally, after accessing a network, a terminal may report its own capability to a network device. Specifically, the terminal reports a capability message to the network device, where the capability message carries one or more capability parameters for characterizing the capability of the terminal. The capability parameters include, for example, Packet Data Convergence Protocol (PDCP) parameters, physical layer parameters, radio frequency parameters, measurement parameters, and the like.

Wherein, the terminal can support multiple levels of capability parameters, taking downlink capability (i.e. capability of the terminal in downlink direction) as an example, when the terminal uses a frequency band combination for communication, one capability parameter of the terminal in one frequency band of one frequency band combination comprises a frequency band level capability parameter and a carrier level capability parameter.

Currently, when reporting the capability message, the terminal includes an identifier of an information element (featuresetdownlinlinpercc information element, featuresetdownlinlinpercc IE) corresponding to the capability parameter of the band level and the capability parameter of the carrier level in a FeatureSetDownlink IE, so that the capability parameter of the corresponding carrier level can be indexed according to the identifier of the featuresetdownlinlinpercc IE. However, in this method, each time a capability parameter of a carrier level is reported, at least one capability parameter of a band level needs to be reported, which results in a large signaling overhead.

Disclosure of Invention

The embodiment of the application provides a capability reporting method and a capability reporting device, so as to reduce signaling overhead in a capability reporting process.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an embodiment of the present application provides a capability reporting method, where the method is applied to a terminal device or a chip of the terminal device, and the method includes: the terminal device sends a capability message to the network device, wherein the capability message comprises a first information unit, a second information unit and an association relation between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level. It can be seen that, when reporting the capability parameters, the terminal does not need to report the capability parameters of at least one band level (e.g., multiple capability parameters indicated by a dashed box 501 in fig. 1) correspondingly every time it reports the capability parameters of one carrier level (e.g., multiple capability parameters indicated by a dashed box 401 in fig. 1), that is, the terminal may report the capability parameters of one band level only once, and the probability of repeatedly reporting the capability parameters of the band level is reduced by reporting the identifier of the capability parameters of the band level associated with the capability parameters of the carrier level, thereby reducing the signaling overhead when the terminal reports the capability.

In a second aspect, embodiments of the present application provide a terminal including a transceiver and a processor.

And the processor is used for determining whether the terminal is in a connection state, controlling the transceiver to send the capability message to the network equipment if the terminal is in the connection state, establishing connection with the network equipment if the terminal is not in the connection state, and then sending the capability message to the network equipment by using the established RRC connection.

The transceiver is used for sending a capability message to the network equipment, wherein the capability message comprises a first information unit and a second information unit, and the association relationship between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level.

In a third aspect, an embodiment of the present application provides a capability reporting method, where the method is applied to a terminal or a chip of the terminal, and the method includes:

the terminal device establishes a connection with the network device, or the terminal device communicates with the network device.

The terminal device sends a capability message to the network device.

For example, the terminal device in an idle state performs Radio Resource Control (RRC) connection, and establishes RRC connection with the network device. The connected terminal device may send a capability message to the network device using the existing RRC connection.

The capability message comprises a first information unit and a second information unit, and the association relationship between the first information unit and the second information unit, wherein the first information unit comprises the capability parameter of the frequency band level, and the second information unit comprises the capability parameter of the carrier level.

It should be noted that the capability reporting method provided in the embodiment of the present application may be applied to the terminal reporting the uplink capability, and may also be applied to the terminal reporting the downlink capability. If the capability parameter is an uplink capability parameter, the first information unit includes an uplink capability parameter at a band level, and the second information unit includes an uplink capability parameter at a carrier level. If the capability parameter is a downlink capability parameter, the first information unit includes a downlink capability parameter at a band level, and the second information unit includes a downlink capability parameter at a carrier level.

In a possible design of the first aspect, the second aspect, or the third aspect, the first information unit does not include a second identifier, and the second identifier is an identifier corresponding to the second information unit. That is, the first information unit is decoupled from the second identification.

In a possible design of the first aspect, the capability message further includes a third information element. When the capability parameter is a downlink capability parameter, the first information element may be a FeatureSetDownlink IE, the second information element may be an information element (FeatureSetDownlink percc IE) corresponding to a carrier level capability parameter, and the third information element (FeatureSet IE) may correspond to a capability parameter of a frequency band combination of the terminal.

Optionally, the association relationship between the first information unit and the second information unit is an association relationship between a first identifier and at least one second identifier, where the first identifier is an identifier corresponding to the first information unit, and the second identifier is an identifier corresponding to the second information unit.

Optionally, the third information unit includes an association relationship between the first identifier and at least one second identifier.

In a possible design of the first aspect, the second aspect, or the third aspect, the capability message further includes a third information element and a fourth information element. When the capability parameter is a downlink capability parameter, the first information element is a newly defined information element, which is marked as a featuresetdownlinlinepara IE, the second information element is a featuresetdownlinlinepercc IE, the third information element is a FeatureSet IE, and the fourth information element is a featuresetdownlinlineie.

The fourth information unit comprises at least one second identifier, and the second identifier is an identifier corresponding to the second information unit.

The association relationship between the first information unit and the second information unit is the association relationship between the first identifier and the fourth identifier, the first identifier is an identifier corresponding to the first information unit, and the fourth identifier is an identifier corresponding to the fourth information unit.

The third information unit contains the association relationship between the first identifier and the fourth identifier.

In a possible design of the first aspect, the second aspect or the third aspect, the capability message contains a first information element, a second information element, a third information element and a fourth information element. The first information element is a FeatureSetDownlinkPara IE, the second information element is a featuresetdownlinlnpercc IE, the third information element is a FeatureSet IE, and the fourth information element is a link information element (FeatureSetDownlink IE).

The association relationship between the first information unit and the second information unit is the association relationship between the first identifier and at least one second identifier. The association of the first identity and the at least one second identity is contained in a fourth information unit.

The third information element contains a fourth identification.

In a fourth aspect, an embodiment of the present application provides a capability reporting method, where the method is applied to a terminal or a chip of the terminal. The method comprises the following steps:

the terminal device establishes a connection with the network device, or the terminal device communicates with the network device. For example, the terminal device in an idle state performs Radio Resource Control (RRC) connection, and establishes RRC connection with the network device. The connected terminal device may send a capability message to the network device using the existing RRC connection.

Under the condition that RRC connection exists, the terminal equipment sends a capability message to the network equipment, wherein the capability message comprises a first information unit, a second information unit and an association relation between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level.

In one possible design, the first information unit further includes a carrier level parameter set, where the carrier level parameter set includes at least two second identifiers, and the second identifiers are identifiers corresponding to the second information units.

Optionally, the capability message further includes a third information unit, where the third information unit corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal, and the third information unit includes a first identifier, where the first identifier is an identifier corresponding to the first information unit.

Optionally, the association relationship between the first information unit and the second information unit is an association relationship between a capability parameter at a frequency band level and the second identifier.

Illustratively, the capability message includes a first information element (FeatureSetDownlink IE), a second information element (FeatureSetDownlinkPerCC IE), and a third information element (FeatureSet IE), as an example of the following capability parameter.

Wherein, the FeatureSet IE contains a first identifier, and the first identifier is an identifier corresponding to the first information element (i.e., FeatureSetDownlinkId).

The FeatureSetDownlink IE contains a band-level downlink capability parameter and a carrier-level parameter set, where the carrier-level parameter set includes at least two second identifiers, and the second identifiers are identifiers corresponding to the second information elements (i.e., FeatureSetDownlink percbid). And the incidence relation between the first information unit and the second information unit is carried in the first information unit through the second identifier for incidence.

The featuresettdowlinkpercc IE contains the carrier-level capability parameters.

In a fifth aspect, an embodiment of the present application provides a communication method, where the method is applied to a network device or a chip of the network device. The method comprises the following steps:

the network equipment receives a capability message sent by the terminal equipment, wherein the capability message comprises a first information unit, a second information unit and an incidence relation between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level.

In one possible design, the first information unit does not include the second identifier, and the second identifier is an identifier corresponding to the second information unit. That is, the first information unit is decoupled from the second identification.

In one possible design, the capability message further includes a third information element. When the capability parameter is a downlink capability parameter, the first information element may be a FeatureSetDownlink IE, the second information element may be an information element (FeatureSetDownlink percc IE) corresponding to a carrier level capability parameter, and the third information element (FeatureSet IE) may correspond to a capability parameter of a frequency band combination of the terminal.

In one possible design, the capability message further includes a third information element and a fourth information element. When the capability parameter is a downlink capability parameter, the first information element is a newly defined information element, which is marked as featuresetdownlinlineparamie, the second information element is featuresetdownlinlinepercc IE, the third information element is FeatureSet IE, and the fourth information element is featuresetdownlinlineie.

In one possible design, the capability message includes a first information element, a second information element, a third information element, and a fourth information element. The first information element is a FeatureSetDownlinkPara IE, the second information element is a featuresetdownlinlnpercc IE, the third information element is a FeatureSet IE, and the fourth information element is a link information element (FeatureSetDownlink IE).

The third information element contains a fourth identification.

In a sixth aspect, an embodiment of the present application provides a capability reporting method, where the method is applied to a network device or a chip of the network device. The method comprises the following steps:

under the condition that RRC connection exists, the network equipment receives a capability message sent by the terminal equipment, wherein the capability message comprises a first information unit, a second information unit and an association relation between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level.

In one possible design of any one of the above aspects, the one capability parameter of the one frequency band in the one frequency band combination of the terminal device includes a capability parameter in the first information element and a capability parameter in the second information element.

In a seventh aspect, an embodiment of the present application provides a terminal, where the terminal has a function of implementing the capability reporting method in any one of the first aspect, the second aspect, the third aspect, or the fourth aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In an eighth aspect, there is provided a terminal comprising: a processor and a memory; the memory is configured to store computer executable instructions, and when the terminal runs, the processor executes the computer executable instructions stored in the memory, so that the terminal performs the capability reporting method according to any one of the first aspect, the second aspect, or the third aspect.

In a ninth aspect, an embodiment of the present application provides a network device, where the terminal has a function of implementing the capability reporting method in any one of the fifth aspect and the sixth aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a tenth aspect, there is provided a network device comprising: a processor and a memory; the memory is configured to store computer execution instructions, and when the network device runs, the processor executes the computer execution instructions stored in the memory, so that the network device executes the capability reporting method according to any one of the fifth aspect or the sixth aspect.

In an eleventh aspect, a computer-readable storage medium is provided, which stores instructions that, when executed on a computer, enable the computer to perform the capability reporting method of any one of the above aspects.

In a twelfth aspect, a computer program product is provided that comprises instructions, which when run on a computer, cause the computer to perform the capability reporting method of any of the above aspects.

In a thirteenth aspect, a circuit system is provided, where the circuit system includes a processing circuit configured to execute the capability reporting method in any one of the above aspects.

In a fourteenth aspect, a chip is provided, where the chip includes a processor, and the processor is coupled to a memory, and the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the method for reporting a capability in any one of the above aspects is implemented.

For technical effects brought by any one of the design manners in the second aspect to the fourteenth aspect, reference may be made to technical effects brought by different design manners in the first aspect, and details are not described herein.

Drawings

FIG. 1 is a diagram illustrating a structure of a capability message in the prior art;

FIG. 2 is a diagram illustrating a structure of a capability message in the prior art;

fig. 3 is a schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 5 is a flowchart of a capability reporting method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 11 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 12 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 13 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 14 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 15 is a schematic structural diagram of a capability message provided in an embodiment of the present application;

fig. 16 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

The terms "first" and "second" and the like in the description and drawings of the present application are used for distinguishing different objects or for distinguishing different processes for the same object, and are not used for describing a specific order of the objects. Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

First, some technical terms are described in conjunction with the process of reporting capability of a terminal in the prior art.

Generally, a terminal may combine two or more carriers using, for example, a Carrier Aggregation (CA) technology or a Dual-carrier (DC) technology, and then communicate through a combined frequency band to improve the traffic capacity of the terminal. In the prior art, a terminal sends a capability message to a network device, where the capability message carries a capability parameter of the terminal.

The structure of the capability message may be as shown in fig. 1, the capability message carrying a plurality of IEs. The contents in solid line boxes 1 to 5 in fig. 1 are an IE, and each IE corresponds to an identifier. The terminal may index one or more capability parameters of the terminal on one frequency band of one frequency band combination step by step through different levels of IEs.

Wherein, the featurestatcombination IE is a band combination level information element, and the featurestatcombination IE contains one or more band level information elements (featurebistband IE) in the band combination.

The FeatureSet band IE contains information elements (FeatureSet IE) corresponding to one or more capability parameters for a band in a band combination.

FeatureSet IE, a capability parameter for a band in a band combination. It should be noted that the FeatureSet IE includes an identification of a downlink capability parameter (FeatureSetDownlink IE) of a capability parameter of one band in a band combination, the identification of the FeatureSetDownlink IE can be denoted as FeatureSetDownlink id, and the FeatureSetDownlink id is used to index into the corresponding FeatureSetDownlink IE. The FeatureSet IE also includes an identification of an uplink parameter (FeatureSetUplink IE) of a capability parameter for a band of a band combination, which may be denoted as FeatureSetUplinkId, which is used to index into the corresponding featuresetuplinkie. The downlink capability parameter part (featurestanddown) and the uplink capability parameter part (featurestapplink) constitute a capability parameter of a band of a complete band combination.

The FeatureSetDownlink IE includes an identifier of an information element (FeatureSetDownlinkPerCC IE) corresponding to the band-level capability parameter and the carrier-level capability parameter. Wherein, the identifier of the FeatureSetDownlinkPerCC IE may be denoted as featuresetdownlinlinperccid for indexing to the capability parameter of the carrier level.

The FeatureSetUplink IE includes an identifier of an information element (FeatureSetUplinkPerCC IE) corresponding to the band-level capability parameter and the carrier-level capability parameter. Wherein, the identifier of FeatureSetUplinkPerCC IE can be denoted as featuresetuplinkpercbid for indexing to the capability parameter at the carrier level.

Featuresettdowlinkpercc IE containing the downlink capability parameter at the carrier level.

Featurestappenkpercc IE containing uplink capability parameters at carrier level.

Taking the downlink capability parameter part (featurestanddown) as an example, the band-level capability parameters (e.g., the plurality of capability parameters in dashed box 401 of fig. 1) contained in the featurestanddown IE and the carrier-level capability parameters (e.g., the plurality of capability parameters in dashed box 501 of fig. 1) indexed by featurestanddown perccid contained in the featurestanddown IE may constitute a downlink capability parameter on one band of a band combination of the terminal. Similarly, the specific capability parameter included in one uplink capability parameter in one frequency band of one frequency band combination of the terminal can be referred to the above description of FeatureSetDownlink.

The FeatureSet IE includes FeatureSetDownlinkId and FeatureSetUplinkId, the IE corresponding to featuresetdownlinlkid includes band-level capability parameters (corresponding to the plurality of capability parameters in dashed box 401 in fig. 1) and featuresetdownlinlkpercld, the carrier-level capability parameters (corresponding to the 5 capability parameters in dashed box 501 in fig. 1) included in the IE corresponding to featuresetdownlinlkpercld; similarly, the IE corresponding to FeatureSetUplinkId contains the capability parameter at the band level and the capability parameter at the carrier level contained in the IE corresponding to featuresetuplinkpercbid.

The system architecture related to the embodiment of the application is as follows:

as shown in fig. 3, the communication system includes access network devices (only one is exemplarily shown in the figure), a plurality of terminal devices (e.g., terminal 1 to terminal 6 in fig. 3) communicating with the access network devices, and core network devices (only one is exemplarily shown in the figure) communicating with the access network devices.

The communication system shown in fig. 3 may be applied to a current Long Term Evolution (LTE) or LTE-Advanced (LTE-a) system, may also be applied to a currently established 5G network or another network in the future, and of course, may also be applied to a system of LTE and 5G hybrid networking, which is not specifically limited in this embodiment of the present invention. In different networks, the core network device, the access network device, and the terminal device in the communication system may correspond to different names, and those skilled in the art will understand that the names do not limit the devices themselves.

The core network device referred to in the embodiments of the present application is a device deployed in a core network to provide a service for a terminal. In systems employing different radio access technologies, the names of core network devices with similar wireless communication capabilities may differ. For example, when the capability reporting method of the embodiment of the present application is applied to a 5G system, the core network device may be an Access and Mobility Management Function (AMF), and when the capability reporting method is applied to an LTE system, the core network device may be a Mobility Management Entity (MME). For convenience of description only, in the embodiments of the present application, the above-mentioned devices capable of providing services for the terminal are collectively referred to as core network devices.

An access network device is a device deployed in a radio access network to provide wireless communication functions. The access network device according to the embodiment of the present application may include, for example and without limitation, a macro base station, a micro base station (also referred to as a small station), a relay station, a Transmission Reception Point (TRP), a next generation network Node (g NodeB, gNB), an evolved Node B (ng-eNB) connected to a next generation core network, and the like in various forms, and may further include a wireless access network device of a non-3 GPP system, such as a Wireless Local Area Network (WLAN) access device.

The terminal device is mainly used for receiving or sending data. Alternatively, the terminal involved in the embodiments of the present application may include, for example but not limited to, various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capability; and may also include subscriber units (subscriber units), cellular phones (cellular phones), smart phones (smart phones), wireless data cards, Personal Digital Assistant (PDA) computers, tablet computers, handheld devices (hand), laptop computers (laptop computers), Machine Type Communication (MTC) terminals (terminals), User Equipment (UE), and the like. In this embodiment of the present application, the terminal device may also be referred to as a terminal, which is described herein in a unified manner and is not described in detail below.

Optionally, the terminal device, the access network device, and the core network device in fig. 3 may be implemented by multiple devices, or the access network device and the core network device may also be implemented by one device, for example, may be implemented as different functional modules in one device, which is not specifically limited in this embodiment of the present application. It is to be understood that the functional modules may be network elements in a hardware device, software functions running on a hardware device, or virtualization functions instantiated on a platform (e.g., a cloud platform).

For example, the terminal device, the access network device, and the core network device in this embodiment may all be implemented by the communication device in fig. 4. Fig. 4 is a schematic diagram illustrating a hardware structure of a communication device according to an embodiment of the present application. The communication device 400 includes at least one processor 401, communication lines 402, memory 403 and at least one communication interface 404.

The processor 401 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

The communication link 402 may include a path for communicating information between the aforementioned components.

The communication interface 404 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be separate and coupled to the processor via a communication line 402. The memory may also be integral to the processor.

The memory 403 is used for storing computer-executable instructions for implementing the embodiments of the present application, and is controlled by the processor 401 to execute. The processor 401 is configured to execute the computer-executable instructions stored in the memory 403, so as to implement the capability reporting method provided in the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 401 may include one or more CPUs such as CPU0 and CPU1 in fig. 4 as an example.

In particular implementations, communication device 400 may include multiple processors, such as processor 401 and processor 405, for one embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

It is to be understood that fig. 4 only shows an exemplary hardware structure diagram of the communication device, and the communication device 400 may further include other components for implementing the technical solution of the embodiment of the present application, which is not limited by the embodiment of the present application.

The communication device 400 described above may be a general purpose device or a special purpose device. In a particular implementation, the communication device 400 may be a device having a similar structure as in fig. 4. The embodiment of the present application does not limit the type of the communication apparatus 400.

Generally, the network device needs to make some network decisions according to the capability of the terminal, for example, the network device may issue a resource configuration corresponding to the terminal according to the capability of the terminal, so that the terminal uses the configured available resources to perform communication. The network device can send the capability request message to the terminal and receive the capability message fed back by the terminal, thereby executing the network decision according to the capability message.

Referring to fig. 2, another capability message structure in the prior art is shown. Where each of the blocks 1 to 9 represents an IE. The specific content contained in each IE may be referred to the capability message shown in fig. 1. And will not be described in detail herein.

As can be seen from the structures of the capability messages in fig. 1 and fig. 2, in the prior art, taking the following capability parameter as an example, since the featuresetdownlinkpercld is included in the featuresetdownlinlink IE, each time a featuresetdownlinlink percc IE is reported, at least one featuresetdownlinlink IE is reported accordingly. However, the plurality of featuresettownlink IEs include a capability parameter of a band level in addition to the featuresettownlinkpercld. When parameters in the FeatureSetDownlinkPerCC IE change, the capability parameters of the band level contained in the FeatureSetDownlink IE may not change, however, as long as the featuresetdownlinlinkpercc IE changes, more FeatureSetDownlink IEs need to be reported, and the reported FeatureSetDownlink IE may cause the capability parameters of the band level to be the same, which causes the capability parameters of the band level to be repeatedly reported, and increases signaling overhead when the terminal reports the capability.

In order to solve the foregoing technical problem, an embodiment of the present invention provides a capability reporting method, and the capability reporting method provided in the embodiment of the present invention will be specifically described below with reference to fig. 5 to 13.

The capability reporting method of the embodiment of the application is applied to the process of reporting the capability to the network equipment by the terminal. Referring to fig. 5, the method includes the steps of:

s501, the network device sends a capability request message (UECapabilityEnquiry) to the terminal device.

Correspondingly, the terminal equipment receives the capability request message sent by the network equipment.

The network device may be an access network device as shown in fig. 3.

The capability request message is used to request the capability of the terminal in one or more Radio Access Technologies (RATs). RATs include, but are not limited to: new Radio (NR) technology, Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) technology, Evolved Universal Mobile Telecommunications System Terrestrial Radio Access and New Radio (E-UTRA-NR) dual connectivity technology, Universal Mobile Telecommunications System Terrestrial Radio Access (Universal Mobile Telecommunications System Terrestrial Radio Access, E-UTRA-NR) technology, Enhanced Data Rate Universal Mobile Telecommunications System Evolved Radio Access Network (Enhanced Data for Mobile Telecommunications System Evolution Radio Access, Access a) technology, Enhanced Data Rate Universal Mobile Telecommunications System Evolution Radio Access Network (Enhanced Data for Mobile Telecommunications System Communication Access) technology, and CDMA2000 multiple Access technology (XRTT-2000).

It should be noted that, when the network needs to know the terminal capability, a capability request message may be initiated to a terminal in a CONNECTED state (CONNECTED) to request the required terminal capability.

S502, the terminal device sends a capability message (UECapabilityInformation) to the network device.

Correspondingly, the network equipment receives the capability message sent by the terminal equipment.

The capability message comprises at least one first information unit and at least one second information unit, and the association relationship between the first information unit and the second information unit, wherein the first information unit comprises the capability parameter of the frequency band level. The second information element contains a capability parameter at the carrier level.

One capability parameter of one frequency band combination of the terminal device comprises the capability parameter in the first information element and the capability parameter in the second information element.

In the embodiment of the present application, the capability message structure may be different according to the types of the first information element and the second information element. Each message structure is described in detail in 4 cases below.

Case 1: the capability message contains a first information element, a second information element and a third information element.

For example, the first information element may be a FeatureSetDownlink IE, and the second information element may be a FeatureSetDownlink percc IE. And, the featuresetdownlinkpercld and FeatureSetDownlink IE are decoupled, i.e., the featuredownlinkpercld in the featuredownlink IE is deleted, so that the featurestandlineid IE contains only the band-level downlink capability parameter and not the featurestanddownlinkpercld. The FeatureSetDownlinkPerCC IE contains a carrier-level downlink capability parameter. The third information element corresponds to a downlink capability parameter of a frequency band in a frequency band combination of the terminal, and may be FeatureSet IE.

The FeatureSet IE includes an association between a first identifier and at least one second identifier, where the first identifier is an identifier corresponding to the FeatureSetDownlink IE, that is, the first identifier may be a featuresetdownlinlink id, and the second identifier is an identifier corresponding to the featuresetdownlinlink perccc IE, that is, the second identifier may be a featuresetdownlinlink percid. The association of the FeatureSetDownlink IE and the FeatureSetDownlinkPerCC IE may be an association of a FeatureSetDownlink id and a FeatureSetDownlinkPerCCI, i.e. an association of the first identifier and the at least one second identifier is used to indicate an association of the FeatureSetDownlink IE and the at least one FeatureSetDownlinkPerCC IE.

It should be noted that, the following capability parameters are taken as an example for explanation, and the specific form of the uplink capability parameters may refer to the related description of the downlink capability parameters. Specifically, the form of the uplink capability parameter in the capability message is specifically:

the first information element may be a FeatureSetUplink IE and the second information element may be a FeatureSetUplinkPerCC IE. And, the featurestappeckpercld and the featurestapplink IE are decoupled, that is, the featurestappeccid in the featurestapplink IE is deleted, so that the featurestappelink IE contains only the band-level uplink capability parameter but not the featurestappeckpercld. The featurestapplinkpercc IE contains the uplink capability parameter at the carrier level. The third information element corresponds to an uplink capability parameter of a frequency band in a frequency band combination of the terminal, and may be FeatureSet IE.

The FeatureSet IE includes an association between a first identifier and at least one second identifier, where the first identifier is an identifier corresponding to the FeatureSetUplink IE, that is, the first identifier may be a FeatureSetUplinkId, and the second identifier is an identifier corresponding to the featuresetuplinkperccc IE, that is, the second identifier may be a featuresetsetupdateuplinkpercpid. The association of the FeatureSetUplink IE and the FeatureSetUplinkPerCC IE may be an association of a FeatureSetUplinkId and a featuresetuplinkpcci, i.e. an association of the first identity and the at least one second identity is used to indicate an association of the FeatureSetUplink IE and the at least one FeatureSetUplinkPerCC IE.

Exemplarily, taking a downlink capability parameter as an example, fig. 6 shows a capability message reported by a terminal according to an embodiment of the present application, where the capability message includes 2 FeatureSet IEs, the capability message further includes 2 FeatureSet downlink IEs, a downlink capability parameter for representing that the terminal supports 2 band levels, and the capability message further includes 3 FeatureSet downlink percc IEs for representing that the terminal supports 3 carrier levels. Wherein, the FeatureSet IE1 includes a correlation between FeatureSetDownlinkId1 and featuresetdownlinkpercld 1, featuresetdownlinlinpercld 5656 2 and featuresetdownlinlinpercld 3, which means that one downlink capability parameter of one frequency band in one frequency band combination of the terminal includes a downlink capability parameter of a frequency band level included in an IE corresponding to featuresetdownlinlinedpercpid 1 and a downlink capability parameter of a carrier level included in an IE corresponding to featuresetdownlinlinccid 1, one downlink capability parameter of one frequency band in another frequency band combination of the terminal includes a downlink capability parameter of a frequency band level included in an IE corresponding to featuresetdownlinlinld 1 and a downlink capability parameter of a carrier level included in a featuredownlinlinld corresponding to featuredownlinlinld 362, and one downlink capability parameter of a frequency band level included in a frequency band combination of the featuredownlinlinld includes a downlink capability parameter of a downlink capability level included in a frequency band corresponding to featuredownlinlinld 3 and a downlink capability parameter of a downlink capability of a carrier level included in a featuredownlinlinld corresponding to a featuredownlink combination of a featuredownlink. Similarly, the IE corresponding to the FeatureSet IE2 includes a correlation between FeatureSetDownlinkId2 and featuresetdownlinkpercld 1, featuresetdownlinlinkpercld 2, featuresetdownlinlinkpercld 3, for characterizing 3 other downlink capability parameters of the terminal.

In addition, the capability message structure shown in fig. 6 can also be represented by fig. 7. In fig. 7, each IE (IE indicated by solid line boxes 1 to 5) and the capability parameters included in each IE may refer to the description in fig. 6, and are not described herein again. Note that, in fig. 7, the horizontal line in the FeatureSetDownlink IE indicates that the FeatureSetDownlink IE is decoupled from the featuresetdownlinkpercbid, that is, the featuresetdownlinkpercbid is deleted in the FeatureSetDownlink IE. In addition, fig. 6 exemplarily shows a carrier-level downlink capability parameter 1, a carrier-level downlink capability parameter 2, and a carrier-level downlink capability parameter 3, fig. 7 does not show downlink capability parameters of all 3 carrier levels, and only shows a carrier-level downlink capability parameter 1 (see a plurality of capability parameters shown by a dashed-line box 501 in fig. 7 and other carrier-level capability parameters not shown) included in an IE corresponding to featuresetsetdownlinlinedperccid 1, and the downlink capability parameter 1 is only a part of the carrier-level downlink capability parameters. Similarly, fig. 6 exemplarily shows a downlink capability parameter 1 at a band level and a downlink capability parameter 2 at a band level, fig. 7 shows only the downlink capability parameter 1 at a band level (including a plurality of capability parameters shown by a dashed box 401 in fig. 7 and other band-level capability parameters not shown) included in an IE corresponding to the FeatureSetDownlinkId1, and the downlink capability parameter 1 is only a part of the downlink capability parameters at a band level. Fig. 6 shows an IE corresponding to FeatureSet IE1 and FeatureSet IE2, only FeatureSet IE1 being shown in fig. 7.

It should be noted that, in the above fig. 6 and fig. 7, there may be other situations in the number of IEs included in the capability message, and this embodiment of the present application is not limited to this situation.

Case 2: in the embodiment of the present application, a new information element is defined for indicating the capability parameter of the band level. Specifically, for example, the capability message includes a first information element (i.e., a new information element, for example, denoted as featuresetdownlinlinepara IE), a second information element (featuresetdownlinlinepercc IE), a third information element (FeatureSet IE), and a fourth information element (featuresetdownlinlineie). It should be noted that the newly defined information unit is an exemplary information unit, and in practical applications, the specific name and form of the new information unit may be set separately, which is not limited in the embodiment of the present application. The new information element appears below similarly.

Wherein, the FeatureSet IE contains the association relationship of the first identification and the fourth identification. The first identity is an identity of a FeatureSetDownlinkPara IE, for example denoted featuresetdownlinlinkpara id, and the fourth identity is an identity of a FeatureSetDownlink IE, i.e. a featuresetdownlinlink id. The association of the FeatureSetDownlinkPara IE and the FeatureSetDownlink IE may be an association of a featuresetdownlinlinkpara id and a featuresetdownlinlinlinlinlinlinlinlink id, i.e. the association of the first identifier and the fourth identifier may indicate an association of a featuresetdownlinlinkpara IE and a FeatureSetDownlink IE.

The FeatureSetDownlinkPara IE contains the downlink capability parameter at the band level and does not contain the second identifier, which is the identifier of the featuresetdownlinlinkperccc IE, i.e., the featuresetdownlinlinkpercpid.

The FeatureSetDownlink IE includes at least one second identity. Fig. 8 shows an exemplary structure of the capability message when the FeatureSetDownlinkIE contains one featuresetdownlinkpercbid. Fig. 9 shows an exemplary structure of the capability message when the FeatureSetDownlink IE contains 3 featuresetdownlinkpercbid. Of course, the number of featuresetdownlinkpercld specifically included in the FeatureSetDownlink IE may be flexibly set according to an application scenario, and this is not limited in the embodiment of the present application.

The featuresettdowlinkpercc IE contains the downlink capability parameter at the carrier level.

Thus, referring to fig. 8, the capability message contains the IEs shown in blocks 1 to 14, and the downlink capability parameters of the terminal on one frequency band of one frequency band combination include the following:

1. the first downlink capability parameter includes: the featuresettdowlinklaaid 1 and featuresettdowlinklid 1 contained in featuresett 1 index into the corresponding IE, and the downlink capability parameter 1 at the band level contained in the IE corresponding to featuresettdowlinklaaid 1 and the downlink capability parameter 1 at the carrier level indexed by featuresettdowlinklid 1 constitute a first downlink capability parameter.

2. The second downlink capability parameter includes: the featuresettringdownlinkparaid 1 and featuresettringdownlinkid 2 contained in the IE corresponding to FeatureSet 2 index into the corresponding IE, and the capability parameter 1 at the band level contained in the IE corresponding to featuresettringdownlinkparaid 1 and the capability parameter 2 at the carrier level indexed by featuresettringdownlinkid 2 constitute a second downlink capability parameter.

3. The third downlink capability parameter includes: the corresponding IE is indexed by the featuresettdowlinklopald 1 and the featuresettdowlinkld 3 contained in the IE corresponding to FeatureSet 3, and the third downlink capability parameter is constituted by the capability parameter 1 at the band level contained in the IE corresponding to featuresettdowlinklladd 1 and the capability parameter 3 at the carrier level indexed by featuresetteendowlinkld 3.

4. The fourth downlink capability parameter includes: the corresponding IE is indexed by featuresettdowlinklopald 2 and featuresettlinklld 1 contained in the IE corresponding to FeatureSet 4, and the fourth downlink capability parameter is constituted by a capability parameter 2 at a band level contained in the IE corresponding to featuresettlinklladd 2 and a capability parameter 1 at a carrier level indexed by featuresettlinklld 1.

5. The fifth downlink capability parameter includes: the featuresetteendowlinklopald 2 and the featuresetteenlinklld 2 contained in the IE corresponding to FeatureSet 5 are indexed into the corresponding IE, and the capability parameter 2 at the band level contained in the IE corresponding to featuresetteendowlinklladd 2 and the capability parameter 2 at the carrier level indexed by featuresetteendowlinklld 2 constitute a fifth downlink capability parameter.

6. The sixth downlink capability parameter includes: the featuresetteendowlinklopald 2 and the featuresetteenlinklld 3 contained in the IE corresponding to FeatureSet 6 are indexed into the corresponding IE, and the capability parameter 2 of the band level contained in the IE corresponding to featuresetteendowlinklladd 2 and the capability parameter 3 of the carrier level indexed by featuresetteendowlinklld 3 form a sixth downlink capability parameter.

The capability message structure of fig. 8 may also be represented by fig. 10. Fig. 10 shows only IE corresponding to featuresettdowlinkparaid 1 and IE corresponding to featuresettdowlinkpercbid 1. Similarly, the capability message structure shown in fig. 9 may also be represented in other forms, which may be referred to in the description of fig. 8 and fig. 10, and each of the downlink capability parameters in fig. 9 specifically includes a downlink capability parameter at a carrier level and a downlink capability parameter at a frequency band level, which may be referred to in the description of fig. 8, and is not repeated here.

It can be understood that, for a detailed explanation of the uplink capability parameter of a terminal in a frequency band of a frequency band combination, reference may be made to the above description of the downlink capability parameter, and details are not described here.

Case 3: the same IE type as contained in the capability message in case 2 above. Taking the following capability parameters as an example, the capability message includes a first information element (featuresetdownlinlinepara IE), a second information element (featuresetdownlinlinepercc IE), a third information element (FeatureSet IE), and a fourth information element (FeatureSetDownlink IE). The capability parameters included in the FeatureSetDownlinkPerCC IE and featuresetdownlinlinepar IE may be referred to the description in case 2, and are not described herein again.

The feature esetdownlink IE includes a first identifier and a second identifier, the first identifier is an identifier corresponding to the feature esetdownlinlinkpara IE, that is, the feature esetdeenunlinkpara id, and the second identifier is an identifier corresponding to the feature esetdeeninkpercc IE, that is, the feature esetdeenitwlnpercid. The association of the FeatureSetDownlinkPara IE and the FeatureSetDownlinkPerCC IE may be an association of a featuresetdownlinlinkpara id and a featuresetdownlinlinkpercpid, and the first identifier and the at least one second identifier have an association indicating an association of the featuresetdownlinlinkpara IE and the featuresetdownlinlinkpercc IE.

It should be noted that in each featuresetdownlinlink IE, each featuresetdownlinlinkparaid corresponds to at least one featuresetdownlinlinlinlnpcid. Fig. 11 shows the structure of the capability message when one featuresetdownlinlinekperaid corresponds to one featuresetdownlinlinekpercpid, and fig. 12 shows the structure of the capability message when one featuresetdownlinlinekparaid corresponds to 3 featuresetdownlinlinekpercpid. Of course, the number of FeatureSetDownlinkPerCCIds corresponding to each FeatureSetDownlinkParaId may be set separately, and is not limited herein.

The FeatureSet IE includes a fourth identity, which is a FeatureSetDownlinkId.

Thus, the capability parameters of the terminal on one frequency band of one frequency band combination include the following:

1. the first capability parameter includes: an IE corresponding to the FeatureSetDownlinkId1 indexes a corresponding FeatureSetDownlink IE, and then an IE corresponding to the featuresetdownlinlid 1 indexes a carrier level capability parameter 1 and a frequency band level capability parameter 1, and the carrier level capability parameter 1 and the frequency band level capability parameter 1 form a first capability parameter.

2. The second capability parameter includes: capability parameter 2 at carrier level and capability parameter 1 at frequency band level indexed by IE corresponding to featuresettdowlinkld 2.

3. The third capability parameter includes: capability parameter 3 at carrier level and capability parameter 1 at frequency band level indexed by IE corresponding to featuresettdowlinkld 3.

4. The fourth capability parameter includes: capability parameter 1 at carrier level and capability parameter 2 at frequency band level indexed by IE corresponding to featuresettdowlinkld 4.

5. The fifth capability parameter includes: capability parameter 2 at carrier level and capability parameter 2 at band level indexed by IE corresponding to featuresettdowlinkld 5.

6. The sixth capability parameter includes: capability parameter 3 at carrier level and capability parameter 2 at band level indexed by IE corresponding to featuresettdowlinkld 1.

The capability message structure of fig. 11 is also represented by fig. 13. Similarly, the capability message structure shown in fig. 12 can also be expressed in other forms, and reference can be made to the description of fig. 11 and fig. 12, which is not described herein again.

Case 4: taking the following capability parameter as an example, the capability message contains a first information element (FeatureSetDownlinkIE), a second information element (FeatureSetDownlinkPerCC IE), and a third information element (FeatureSet IE). For the downlink capability parameters included in the FeatureSetDownlinkPerCC IE, reference may be made to the descriptions in the

above cases

1, 2, and 3, and details are not described here again.

The FeatureSet IE contains a first identity, which is the identity to which the first information element corresponds (i.e. the FeatureSetDownlinkId).

Fig. 14 is a diagram illustrating a structure of a capability message. Therefore, the downlink capability parameters of the terminal on one frequency band of one frequency band combination include the following parameters:

1. the first downlink capability parameter includes: the featuresettdowlink IE1 indexes the corresponding featuresettdowlink IE, and the IE corresponding to the featuresettdowlink id1 indexes the carrier level downlink capability parameter 1 and the frequency band level downlink capability parameter 1, and the carrier level downlink capability parameter 1 and the frequency band level downlink capability parameter 1 form a first downlink capability parameter.

2. The second downlink capability parameter includes: and (3) a downlink capability parameter 2 at a carrier level and a downlink capability parameter 1 at a frequency band level indexed by an IE corresponding to the FeatureSetdownlinkId 1.

3. The third downlink capability parameter includes: and (3) a downlink capability parameter at a carrier level and a downlink capability parameter at a frequency band level, which are indexed by an IE corresponding to the FeatureSetdownlinkId 1.

The capability message of fig. 14 may also be represented by fig. 15. For the detailed description of the capability message, reference may be made to the descriptions of

cases

1, 2, and 3, which are not described herein again.

It can be understood that, in the case of the uplink capability parameter of the terminal in one frequency band of one frequency band combination, reference may be made to the above-mentioned related expression of the downlink capability parameter, and details are not described here.

It should be noted that the third information element (FeatureSet IE) includes an uplink capability parameter and a downlink capability parameter of the terminal, that is, the FeatureSet IE corresponds to both the capability (uplink capability) of the terminal in the uplink direction and the capability of the terminal in the downlink direction, and one FeatureSet IE may represent at least one uplink capability and at least one downlink capability of the terminal. Taking the uplink capability of the terminal corresponding to the FeatureSet IE as an example, the first information element includes uplink capability parameters at a band level, and the second information element includes uplink capability parameters at a carrier level. Taking the downlink capability of the terminal corresponding to the FeatureSet IE as an example, the first information element includes a downlink capability parameter at a band level, and the second information element includes a downlink capability parameter at a carrier level.

It should be noted that, before sending the capability message to the access network device, the terminal needs to establish an RRC connection with the access network device, so as to send the capability message to the access network device through the RRC connection. Optionally, if the terminal is in the RRC connected state, because the RRC connection with the access network device is already established, the terminal may directly send the capability message to the access network device through the RRC connection. If the terminal is in an idle state, the terminal may first establish an RRC connection with the access network device, and then send a capability message to the access network device.

Illustratively, when the terminal reports its capability in NR and E-UTRA, the NR container (container) and the E-UTRA container are carried in the capability message. Wherein, the container of the NR includes an IE having any one of the structures shown in fig. 6 to 13 for reporting the capability supported by the terminal in the NR, and the container of the E-UTRA includes an IE having any one of the structures shown in fig. 6 to 13 for reporting the capability supported by the terminal in the E-UTRA.

In the capability reporting method provided by the embodiment of the application, the capability message reported by the terminal includes the first information unit and the second information unit, and the association relationship between the first information unit and the second information unit. The first information unit contains the capability parameter of the frequency band level and does not contain the identifier of the capability parameter of the carrier level, and the second information unit contains the capability parameter of the carrier level. It can be seen that, when the terminal reports the capability parameters of the carrier level, it is not necessary to report the capability parameters of at least one band level (e.g., the capability parameters of the band level indicated by the dashed line frame 401 in fig. 1) every time the terminal reports the capability parameters of one carrier level (e.g., the capability parameters of the carrier level indicated by the dashed line frame 501 in fig. 1), that is, the terminal may report a plurality of capability parameters of the carrier level associated with the terminal while reporting the capability parameters of one band level, so as to reduce the probability of repeatedly reporting the capability parameters of the band level, and further reduce the signaling overhead when the terminal reports the capability.

It is to be understood that, in order to implement the above functions, the terminal in the embodiments of the present application includes a hardware structure and/or a software module corresponding to each function. The elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein may be embodied in hardware or in a combination of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present teachings.

In the embodiment of the present application, the terminal may be divided into the functional units according to the above method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 16 shows a schematic block diagram of a communication apparatus provided in an embodiment of the present application. The communication device 1600 may be a stand-alone device or may be a chip usable with a device. The communication device 1600 may be the terminal or the network device. The communication apparatus 1600 includes: a processing unit 1602 and a communication unit 1603.

When communications apparatus 1600 is a terminal, processing unit 1602 can be employed to enable the terminal to determine whether to be in a connected/idle state, to determine whether to establish an RRC connection with an access network device, and/or to perform other procedures for aspects described herein. The communication unit 1603 is used to support communication between the terminal and other network elements (e.g., the access network equipment described above, etc.), e.g., to support the terminal to perform S501 and S502 in fig. 5, and/or other processes for the schemes described herein.

When the communications apparatus 1600 is a network device, the processing unit 1602 can be configured to support the network device for processes described herein, such as allocating corresponding communication resources for a terminal. The communication unit 1603 is used to support communication between the network device and other network elements (e.g., the above-mentioned terminals, etc.), for example, to support the network device to perform S501 and S502 in fig. 5, and/or other processes for the schemes described herein.

Optionally, the communication device 1600 may further include a storage unit 1601 for storing program codes and data of the communication device 1600, which may include, but is not limited to, raw data or intermediate data, etc.

In one possible approach, the Processing Unit 1602 may be a controller or the processor 401 or the processor 405 shown in fig. 4, and may be, for example, a Central Processing Unit (CPU), a general purpose processor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication unit 1603 may be a transceiver, a transceiving circuit, or the communication interface 404 shown in fig. 4, or the like. The storage unit 1601 may be the memory 403 shown in fig. 4.

Those of ordinary skill in the art will understand that: in the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may also be distributed on a plurality of network devices (e.g., terminal devices). Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus necessary general hardware, and certainly, the present application can also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application may be substantially implemented or a part of the technical solutions contributing to the prior art may be embodied in the form of a software product, where the computer software product is stored in a readable storage medium, such as a floppy disk, a hard disk, or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the method of the embodiments of the present application.

The above is only an embodiment of the present application, but the scope of the present application is not limited thereto, and variations or substitutions within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A capability reporting method is characterized by comprising the following steps:

and the terminal equipment sends the capability message to the network equipment, wherein the capability message comprises a first information unit, a second information unit and an incidence relation between the first information unit and the second information unit, the first information unit comprises the capability parameter at the frequency band level, and the second information unit comprises the capability parameter at the carrier level.

2. The capability reporting method of claim 1, wherein the first information unit does not include a second identifier, and the second identifier is an identifier corresponding to the second information unit.

3. The capability reporting method according to claim 1 or 2, wherein the association relationship between the first information unit and the second information unit is an association relationship between a first identifier and at least one second identifier, the first identifier is an identifier corresponding to the first information unit, and the second identifier is an identifier corresponding to the second information unit.

4. The capability reporting method of claim 3, wherein the capability message further includes a third information element, the third information element includes an association relationship between the first identifier and at least one second identifier, and the third information element corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal.

5. The capability reporting method according to claim 1 or 2, wherein the capability message further includes a fourth information unit, the fourth information unit includes at least one second identifier, and the second identifier is an identifier corresponding to the second information unit.

6. The capability reporting method according to claim 5, wherein the association relationship between the first information unit and the second information unit is an association relationship between a first identifier and a fourth identifier, the first identifier is an identifier corresponding to the first information unit, and the fourth identifier is an identifier corresponding to the fourth information unit.

7. The capability reporting method of claim 6, wherein the capability message further includes a third information element, and the third information element includes an association relationship between the first identifier and a fourth identifier.

8. The capability reporting method of claim 5, wherein the fourth information unit further includes a first identifier, the first identifier is an identifier corresponding to the first information unit, and the association relationship between the first information unit and the second information unit is an association relationship between the first identifier and at least one second identifier.

9. The capability reporting method of claim 8, wherein the capability message further includes a third information element, the third information element includes a fourth identifier, and the fourth identifier is an identifier of the fourth information element.

10. The capability reporting method according to any of the claims 1 to 9,

the first information element comprises an uplink capability parameter at a band level and the second information element comprises an uplink capability parameter at a carrier level, or,

the first information unit includes a downlink capability parameter at a band level, and the second information unit includes a downlink capability parameter at a carrier level.

11. The capability reporting method according to any of claims 1 to 10, wherein a capability parameter of a frequency band in a frequency band combination of the terminal device comprises a capability parameter in a first information element and a capability parameter in a second information element.

12. A capability reporting method is characterized by comprising the following steps:

the method comprises the steps that access network equipment receives a capability message sent by terminal equipment, wherein the capability message comprises a first information unit, a second information unit and an incidence relation between the first information unit and the second information unit, the first information unit comprises a capability parameter at a frequency band level, and the second information unit comprises a capability parameter at a carrier level.

13. The capability reporting method of claim 12, wherein the first information unit does not include a second identifier, and the second identifier is an identifier corresponding to the second information unit.

14. The capability reporting method according to claim 12 or 13, wherein the association relationship between the first information unit and the second information unit is an association relationship between a first identifier and at least one second identifier, the first identifier is an identifier corresponding to the first information unit, and the second identifier is an identifier corresponding to the second information unit.

15. The capability reporting method of claim 14, wherein the capability message further includes a third information element, the third information element includes an association relationship between the first identifier and at least one second identifier, and the third information element corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal.

16. The capability reporting method according to claim 12 or 13, wherein the capability message further includes a fourth information unit, the fourth information unit includes at least one second identifier, and the second identifier is an identifier corresponding to the second information unit.

17. The capability reporting method of claim 16, wherein the association relationship between the first information unit and the second information unit is an association relationship between a first identifier and a fourth identifier, the first identifier is an identifier corresponding to the first information unit, and the fourth identifier is an identifier corresponding to the fourth information unit.

18. The capability reporting method of claim 17, wherein the capability message further includes a third information element, and the third information element includes an association relationship between the first identifier and a fourth identifier.

19. The capability reporting method of claim 16, wherein the fourth information unit further includes a first identifier, the first identifier is an identifier corresponding to the first information unit, and the association relationship between the first information unit and the second information unit is an association relationship between the first identifier and at least one second identifier.

20. The capability reporting method of claim 19, wherein the capability message further includes a third information element, the third information element includes a fourth identifier, and the fourth identifier is an identifier of the fourth information element.

21. The capability reporting method according to any of the claims 12 to 20,

22. The capability reporting method of any one of claims 12 to 21, wherein a capability parameter of a frequency band in a frequency band combination of the terminal device comprises a capability parameter in a first information element and a capability parameter in a second information element.

23. A terminal, comprising: a processor, a memory, a bus, and a communication interface;

the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the terminal runs, the processor executes the computer execution instructions stored in the memory, so that the terminal executes the capability reporting method according to any one of claims 1 to 11.

24. A network device, comprising: a processor, a memory, a bus, and a communication interface;

the memory is configured to store computer executable instructions, the processor is connected to the memory through the bus, and when the network device runs, the processor executes the computer executable instructions stored in the memory, so that the network device executes the capability reporting method according to any one of claims 12 to 22.

25. A readable storage medium, characterized by comprising a program or instructions, which when executed, implements the capability reporting method according to any one of claims 1 to 11, or implements the capability reporting method according to any one of claims 12 to 22.