WO2020063521A1

WO2020063521A1 - Capability reporting method and apparatus

Info

Publication number: WO2020063521A1
Application number: PCT/CN2019/107245
Authority: WO
Inventors: 邝奕如; 王丁; 王键
Original assignee: 华为技术有限公司
Priority date: 2018-09-27
Filing date: 2019-09-23
Publication date: 2020-04-02
Also published as: CN110958603B; CN110958603A

Abstract

The present application provides a capability reporting method and apparatus, relating to the field of communication technology, and being able to solve the problem in the prior art that large signaling overheads are caused when a terminal reports capability. Said method comprises: a terminal device sending to a network device a capability message, the capability message comprising a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit, the first information unit including a capability parameter of a frequency band level, and the second information unit including a capability parameter of a carrier level. The method is applied in the process of a terminal reporting a capability message.

Description

Method and device for reporting capacity

Technical field

The present application relates to the field of communication technologies, and in particular, to a method and device for reporting capabilities.

Background technique

Generally, after the terminal accesses the network, it can report its capabilities to the network device. Specifically, the terminal reports a capability message to the network device, where the capability message carries one or more capability parameters used to characterize the capability of the terminal. Capability parameters include, for example, Packet Data Convergence Protocol (PDCP) parameters, physical layer parameters, radio frequency parameters, and measurement parameters.

Among them, the terminal can support multiple levels of capability parameters. The following capability (ie, the terminal's capability in the downlink direction) is taken as an example. When the terminal uses frequency band combination for communication, the terminal is in one of a frequency band of a frequency band combination. This capability parameter includes a capability parameter at a frequency band level and a capability parameter at a carrier level.

At present, when a terminal reports a capability message, the identity of the information element (FeatureSetDownlinkPerCC, FeatureSetDownlinkPerCC) corresponding to the capability parameter at the frequency band level and the carrier level capability parameter is included in the FeatureSetDownlinkPerCCIE, so that it can be indexed to The capability parameter of the corresponding carrier level. However, in this method, each time a carrier-level capability parameter is reported, it is generally necessary to report at least one band-level capability parameter, which results in a large signaling overhead.

Summary of the Invention

The embodiments of the present application provide a method and a device for reporting a capability, so as to reduce signaling overhead in the capability reporting process.

To achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

In a first aspect, an embodiment of the present application provides a capability reporting method, which is applied to a terminal device or a chip of a terminal device. The method includes: the terminal device sends a capability message to a network device, and the capability message includes a first information unit and a first Two information units, and an association relationship between the first information unit and a second information unit. The first information unit includes a capability parameter at a frequency band level, and the second information unit includes a capability parameter at a carrier level. It can be seen that when the terminal reports the capability parameter, it is not necessary to report the capability parameter of each carrier level (such as multiple capability parameters indicated by dashed box 501 in FIG. 1), but correspondingly report the capability parameter of at least one frequency band (such as dashed box 401 in FIG. 1). Indicated multiple capability parameters), that is, the terminal may report only one type of band-level capability parameter at a time, and reduce the capability of the band-level by reporting the identifier of the band-level capability parameter associated with the carrier-level capability parameter. Probability of repeated reporting of parameters, thereby reducing signaling overhead when the terminal is reporting capabilities.

In a second aspect, an embodiment of the present application provides a terminal. The terminal includes a transceiver and a processor.

A processor for determining whether the terminal is in a connected state, and if so, controlling the transceiver to send a capability message to the network device; if not, establishing a connection with the network device, and then using the established RRC connection to send the capability to the network device Message.

A transceiver for sending a capability message to a network device, the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit, and the first information unit includes a capability parameter at a frequency band level, The second information element contains a carrier level capability parameter.

In a third aspect, an embodiment of the present application provides a capability reporting method, which is applied to a terminal or a chip of a terminal. 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, a terminal device in an idle state performs a Radio Resource Control (RRC) connection and establishes an RRC connection with a network device. The connected terminal device can use the existing RRC connection to send a capability message to the network device.

The capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit. The first information unit includes a capability parameter at a frequency band level, and the second information unit includes a capability parameter at a carrier level. .

It should be noted that the capability reporting method provided in the embodiment of the present application can be applied to a terminal reporting an uplink capability, and it can also be applied to a terminal reporting a downlink capability. If the capability parameter is an uplink capability parameter, the first information element includes an uplink capability parameter at a frequency band level, and the second information element 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 frequency band level, and the second information unit includes a downlink capability parameter at a carrier level.

In a possible design of the first aspect or 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 identifier.

In a possible design of the first aspect or the second aspect or the third aspect, the capability message further includes a third information unit. When the capability parameter is a downlink capability parameter, the first information unit may be a FeatureSetDownlinkIE, the second information unit may be an information unit corresponding to the carrier-level capability parameter (FeatureSetDownlinkPerCCIE), and the third information unit (FeatureSetIE) corresponds to one of the terminals. A capability parameter of a frequency band of various frequency band combinations.

Optionally, 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, the first identifier is an identifier corresponding to the first information unit, and the second identifier is a second information unit. The corresponding ID.

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 or the second aspect or the third aspect, the capability message further includes a third information unit and a fourth information unit. When the capability parameter is a downlink capability parameter, the first information unit is a newly defined information unit, which is referred to as FeatureSetDownlinkParaIE, the second information unit is FeatureSetDownlinkPerCCIE, the third information unit is FeatureSetIE, and the fourth information unit is FeatureSetDownlinkIE.

The fourth information unit includes 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 includes an 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 includes a first information unit, a second information unit, a third information unit, and a fourth information unit. The first information unit is FeatureSetDownlinkParaieIE, the second information unit is FeatureSetDownlinkPerCCIE, the third information unit is FeatureSetIE, and the fourth information unit is LinkSetElement (FeatureSetDownlinkIE).

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. The association between the first identifier and the at least one second identifier is included in a fourth information unit.

The third information unit contains a fourth identifier.

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

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

In the case of an RRC connection, the terminal device sends a capability message to the network device. The capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit. The first information unit includes a frequency band. Level capability parameter, the second information element contains a carrier level capability parameter.

In a possible design, the first information unit further includes a carrier level parameter set, and the carrier level parameter set includes at least two second identifiers, and the second identifier is an identifier corresponding to the second information unit.

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

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

Exemplarily, the following row capability parameter is taken as an example. The capability message includes a first information unit (FeatureSetDownlinkIE), a second information unit (FeatureSetDownlinkPerCCIE), and a third information unit (FeatureSetIE).

The FeatureSet IE includes a first identifier, and the first identifier is an identifier corresponding to the first information unit (ie, FeatureSetDownlinkId).

FeatureSetDownlink IE includes a downlink capability parameter and a carrier level parameter set at a frequency band level. The carrier level parameter set includes at least two second identifiers, and the second identifier is an identifier corresponding to the second information unit (ie, FeatureSetDownlinkPerCCId). The association between the first information unit and the second information unit is carried in the first information unit through the second identifier.

FeatureSetDownlinkPerCC contains capability parameters at the carrier level.

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

The network device receives a capability message sent by the terminal device. The capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and a second information unit. The first information unit includes a capability parameter at a frequency band level. The information element contains the capability parameters at the carrier level.

In a possible design, 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 identifier.

In a possible design, the capability message further includes a third information unit. When the capability parameter is a downlink capability parameter, the first information unit may be a FeatureSetDownlinkIE, the second information unit may be an information unit corresponding to the carrier-level capability parameter (FeatureSetDownlinkPerCCIE), and the third information unit (FeatureSetIE) corresponds to one of the terminals. A capability parameter of a frequency band of various frequency band combinations.

In a possible design, the capability message further includes a third information unit and a fourth information unit. When the capability parameter is a downlink capability parameter, the first information unit is a newly defined information unit, which is referred to as FeatureSetDownlinkParaIE, the second information unit is FeatureSetDownlinkPerCCIE, the third information unit is FeatureSetIE, and the fourth information unit is FeatureSetDownlinkIE.

In a possible design, the capability message includes a first information unit, a second information unit, a third information unit, and a fourth information unit. The first information unit is FeatureSetDownlinkParaieIE, the second information unit is FeatureSetDownlinkPerCCIE, the third information unit is FeatureSetIE, and the fourth information unit is LinkSetElement (FeatureSetDownlinkIE).

The third information unit contains a fourth identifier.

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

In the case of an RRC connection, the network device receives a capability message sent by the terminal device. The capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit. The first information unit includes Band-level capability parameters, and the second information element contains a carrier-level capability parameter.

FeatureSetDownlinkPerCC contains capability parameters at the carrier level.

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

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

According to an eighth aspect, a terminal is provided, including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the terminal is running, the processor executes the computer execution instruction stored in the memory, so that the terminal executes a program such as The capability reporting method of any one of the first aspect, the second aspect, or the third aspect described above.

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

According to a tenth aspect, a network device is provided, including: a processor and a memory; the memory is configured to store computer execution instructions, and when the network device is running, the processor executes the computer execution instructions stored in the memory to enable the network The device performs the capability reporting method according to any one of the fifth aspect or the sixth aspect.

According to an eleventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the capability reporting method of any one of the above aspects.

In a twelfth aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to execute the capability reporting method of any of the above aspects.

According to a thirteenth aspect, a circuit system is provided. The circuit system includes a processing circuit configured to execute the capability reporting method according to any one of the above aspects.

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

The technical effects brought by any one of the design methods in the second aspect to the fourteenth aspect may refer to the technical effects brought by the different design methods in the first aspect, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a first structural diagram of a capability message in the prior art; FIG.

FIG. 2 is a second structural diagram of a capability message in the prior art; FIG.

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

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 according to an embodiment of the present application;

7 is a schematic structural diagram of a capability message according to an embodiment of the present application;

8 is a schematic structural diagram of a capability message according to an embodiment of the present application;

9 is a schematic structural diagram of a capability message according to an embodiment of the present application;

10 is a schematic structural diagram of a capability message according to an embodiment of the present application;

11 is a schematic structural diagram of a capability message according to an embodiment of the present application;

12 is a schematic structural diagram of a capability message according to an embodiment of the present application;

13 is a schematic structural diagram of a capability message according to an embodiment of the present application;

14 is a schematic structural diagram of a capability message according to an embodiment of the present application;

15 is a schematic structural diagram of a capability message according to 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” in the specification of the present application and the drawings are used to distinguish different objects, or to distinguish different processes on the same object, rather than to describe a specific order of the objects. Furthermore, the terms "including" and "having" as well as any variations of them mentioned in the description of the present application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that contains a series of steps or units is not limited to the listed steps or units, but optionally also includes other steps or units not listed, or optionally also Include other steps or units inherent to these processes, methods, products, or equipment. It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used as examples, illustrations or illustrations. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present application should not be construed as more preferred or more advantageous than other embodiments or designs. Rather, the use of the words "exemplary" or "for example" is intended to present the relevant concept in a concrete manner.

First, some technical terms will be described in conjunction with the process of terminal reporting capabilities in the prior art.

Generally, a terminal may use a carrier aggregation (CA) technology or a dual carrier (DC) technology to combine two or more carriers, and then communicate through a combined frequency band to improve the terminal's service capabilities. In the prior art, a terminal sends a capability message to a network device, and the capability message carries a capability parameter of the terminal.

The structure of the capability message may be as shown in FIG. 1, and the capability message carries multiple IEs. The content in the solid line boxes 1 to 5 in FIG. 1 is an IE, and each IE corresponds to an identifier. The terminal may index one or more capability parameters of the terminal on a frequency band of a combination of frequency bands through different levels of IE.

Among them, FeatureSetCombinationIE is a band combination level information unit, and FeatureSetCombinationIE contains one or more bandlevel information units (FeatureSetsPerBandIE) in the band combination.

FeatureSetsPerBand IE, which contains information elements (FeatureSet IE) corresponding to one or more capability parameters of a frequency band in a frequency band combination.

FeatureSetIE, a capability parameter corresponding to a frequency band in a frequency band combination. It should be noted that FeatureSetIE includes an identification of a downlink capability parameter (FeatureSetDownlinkIE) of a capability parameter of a frequency band in a frequency band combination. The identifier of FeatureSetDownlinkIE can be recorded as FeatureSetDownlinkId, and FeatureSetDownlinkId is used to index to the corresponding FeatureSetDownlinkIE . FeatureSetIE also includes an identifier of an uplink parameter (FeatureSetUplinkIE) of a capability parameter of a frequency band combination. The identity of FeatureSetUplinkIE can be recorded as FeatureSetUplinkId, and FeatureSetUplinkId is used to index to the corresponding FeatureSetUplinkIE. The above-mentioned downlink capability parameter part (FeatureSetDownlink) and the above-mentioned uplink capability parameter (FeatureSetUplink) part constitute a kind of capability parameter of a frequency band in a complete frequency band combination.

FeatureSetDownlink IE, which includes the identification of the information element (FeatureSetDownlinkPerCC) corresponding to the frequency-level capability parameter and the carrier-level capability parameter. Among them, the identifier of FeatureSetDownlinkPerCC and IE can be recorded as FeatureSetDownlinkPerCCId, which is used to index the capability parameter to the carrier level.

FeatureSetUplinkIE, which includes the identification of the information element (FeatureSetUplinkPerCC) of the frequency-level capability parameter and the carrier-level capability parameter. The identifier of FeatureSetUplinkPerCC IE can be recorded as FeatureSetUplinkPerCCId, which is used to index the capability parameter to the carrier level.

FeatureSetDownlinkPerCC, ie, contains downlink capability parameters at the carrier level.

FeatureSetUplinkPerCC, ie, contains uplink capability parameters at the carrier level.

The following set of capability parameters (FeatureSetDownlink) is used as an example. The frequency-level capability parameters included in FeatureSetDownlink (such as multiple capability parameters in dashed box 401 in Figure 1) can be indexed with the carrier-level capability parameters indexed by FeatureSetDownlinkPerCCId included in FeatureSetDownlink As shown in FIG. 1, a plurality of capability parameters in a dashed box 501) constitutes a type of downlink capability parameter on a frequency band in a frequency band combination of a terminal. The same applies to the uplink capability parameter part (FeatureSetUplink). For specific capability parameters included in an uplink capability parameter on a frequency band in a frequency band combination of the terminal, refer to the foregoing description of FeatureSetDownlink.

FeatureSetIE contains FeatureSetDownlinkId and FeatureSetUplinkId. The IE corresponding to FeatureSetDownlinkId contains the capability parameters at the frequency band level (corresponding to multiple capability parameters in the dashed box 401 in Figure 1) and FeatureSetDownlinkPerCCId. The five capability parameters in dashed box 501 in 1 correspond to 5); similarly, the IE corresponding to FeatureSetUplinkId includes the capability parameter at the frequency band level and FeatureSetUplinkPerCCId, and the capability parameter at the carrier level included in the IE corresponding to FeatureSetUplinkPerCCId.

The system architecture involved in the embodiments of the present application is as follows:

As shown in FIG. 3, the communication system includes an access network device (only one is shown as an example in the figure), a plurality of terminal devices (such as terminal 1 to terminal 6 in FIG. 3) that communicate with the access network device, Core network equipment (only one is shown as an example in the figure) for communication with the access network equipment.

The communication system shown in FIG. 3 can be applied to a current Long Term Evolution (LTE) or an advanced Long Term Evolution (LTE-A) system, and can also be applied to a 5G network currently being developed or a future In other networks, of course, it can also be applied to a system of LTE and 5G mixed networking, which is not specifically limited in the embodiment of the present application. Among them, in different networks, the core network equipment, access network equipment, and terminal equipment in the communication system may correspond to different names. Those skilled in the art can understand that the name does not constitute a limitation on the equipment itself.

The core network device referred to in the embodiments of the present application is a device deployed in the core network to provide services to terminals. In systems using different wireless access technologies, the names of core network devices with similar wireless communication functions may be different. 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, Access and Mobility Management Function). When applied to the LTE system, the core network device may be Mobility Management Entity (MME). For the convenience of description only, in the embodiments of the present application, the foregoing devices that can provide services to terminals are collectively referred to as core network equipment.

An access network device is a device that is deployed in a wireless access network to provide wireless communication functions. The access network equipment involved in the embodiments of the present application may include, for example, but not limited to, various types of macro base stations, micro base stations (also referred to as small stations), relay stations, transmission and reception points (TRP), and the next generation. Network nodes (gNodeB, gNB), evolved NodeB (ng-eNB) connected to the next-generation core network, etc., may also include wireless local area network (WLAN) access equipment such as non-WLAN Radio access network equipment for 3GPP systems.

Terminal equipment is mainly used to receive or send data. Optionally, the terminals involved in the embodiments of the present application may include, for example, but not limited to, various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem; also Can include subscriber unit, cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, handheld device, knee A laptop computer, a machine type communication (MTC) terminal, a user equipment (UE), and the like. In the embodiments of the present application, the terminal device may also be referred to as a terminal, which will be collectively described herein and will not be described in detail hereinafter.

Optionally, the terminal device, access network device, and core network device in FIG. 3 may be implemented by multiple devices, respectively, or the access network device and core network device may also be implemented by one device, for example, may be implemented in one device. Different functional modules, which are not specifically limited in the embodiments of the present application. It can be understood that the foregoing function module may be a network element in a hardware device, a software function running on a hardware device, or a virtualization function instantiated on a platform (for example, a cloud platform).

For example, the terminal device, the access network device, and the core network device in the embodiment of the present application may be implemented by using the communication device in FIG. 4. FIG. 4 is a schematic diagram of 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, a communication line 402, a 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 processors for controlling the execution of the program of the solution of the present application. integrated circuit.

The communication line 402 may include a path for transmitting information between the aforementioned components.

The communication interface 404 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .

The memory 403 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types that can store information and instructions The dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this. The memory may exist independently, and is connected to the processor through the communication line 402. The memory can also be integrated with the processor.

The memory 403 is configured to store computer execution instructions for executing the solutions in the embodiments of the present application, and the execution is controlled by the processor 401. The processor 401 is configured to execute computer execution 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 a specific implementation, as an embodiment, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4.

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

It can be understood that FIG. 4 only shows an exemplary hardware structure diagram of a communication device. In order to implement the technical solution of the embodiment of the present application, the communication device 400 may further include other components. Limitation.

The above-mentioned communication device 400 may be a general-purpose device or a special-purpose device. In a specific 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 device 400.

Generally, a network device needs to make some network decisions based on the capabilities of the terminal. For example, the network device can deliver the resource configuration corresponding to the terminal to the terminal according to the terminal capability, so that the terminal uses the configured available resources for communication. The network device may send a capability request message to the terminal, and receive the capability message fed back by the terminal, so as to execute a network decision according to the capability message.

See FIG. 2 for another capability message structure in the prior art. Among them, boxes 1 to 9 each represent an IE. For specific content contained in each IE, refer to the capability message shown in FIG. 1. I won't repeat them here.

It can be seen from the structure of the capability message in Fig. 1 and Fig. 2 that in the prior art, the following capability parameters are taken as an example. Since FeatureSetDownlinkPerCCId is included in FeatureSetDownlinkIE, generally, every time a FeatureSetDownlinkPerCC is reported, it is reported at least A FeatureSetDownlink IE. However, in addition to FeatureSetDownlinkPerCCId, multiple FeatureSetDownlink IEs also include band-level capability parameters. When the parameters in FeatureSetDownlinkPerCC are changed, FeatureSetDownlinkPeriod's band-level capability parameters may not change. However, as long as FeatureSetDownlinkPerCC is changed, it is necessary to report FeatureSetDownlinkIE, and the reported FeatureSetDownlinkIE may cause the same band-level capability parameters. , Resulting in repeated reporting of capability parameters at this frequency band level, increasing the signaling overhead when the terminal reports capabilities.

In order to solve the above technical problems, an embodiment of the present application provides a capability reporting method. The capability reporting method provided by the embodiment of the present application will be specifically described below with reference to FIGS. 5 to 13.

The capability reporting method in the embodiment of the present application is applied to a process in which a terminal reports a capability to a network device. Referring to FIG. 5, the method includes the following steps:

S501. The network device sends a capability request message (UECapabilityEnquiry) to the terminal device.

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

The network device may be an access network device shown in FIG. 3.

The capability request message is used to request the capability of the terminal in one or more radio access technologies (Radio Access Technology, RAT). RAT includes but is not limited to: New Radio (NR) technology, Evolved-Universal Mobile Telecommunications System, Terrrestrial Radio Access, E-UTRA technology, and Evolved Universal Mobile Communication System terrestrial Wireless access and new wireless (Evolved-Universal Mobile Telecommunications System Terrestrial Radio Access New Radio, E-UTRA-NR) dual connection technology, universal mobile communication system terrestrial wireless access (Universal Mobile Telecommunications System Terrestrial Radio Access, UTRA) technology, Enhanced data rate global mobile communication system evolution wireless access network (Enhanced Data Rate Global System, Mobile Communication, Evolution Radio Access Network, GERAN) technology and code division multiple access 2000 technology (CDMA2000-1XRTT).

It should be noted that when the network needs to know the terminal capabilities, it can initiate a capability request message to a connected terminal to request the required terminal capabilities.

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

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

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

A capability parameter of a frequency band in a frequency band combination of a terminal device includes a capability parameter in a first information unit and a capability parameter in a second information unit.

In the embodiment of the present application, the capability message structure may be different according to the types of the first information unit and the second information unit. The following is a detailed description of each message structure in four cases.

Case 1: The capability message includes a first information unit, a second information unit, and a third information unit.

Among them, the following row capability parameters are taken as an example. The first information unit may be FeatureSetDownlinkIE, and the second information unit may be FeatureSetDownlinkPerCCIE. In addition, the FeatureSetDownlinkPerCCId and the FeatureSetDownlinkIE are decoupled, that is, the FeatureSetDownlinkIE is deleted from the FeatureSetDownlinkPerCCId, so that the FeatureSetDownlinkIE only includes the downlink capability parameter at the frequency band level and does not include the FeatureSetDownlinkPerCCId. FeatureSetDownlinkPerCC includes downlink capability parameters at the carrier level. The third information unit corresponds to a type of downlink capability parameter of a frequency band in a frequency band combination of the terminal, that is, a FeatureSetIE.

FeatureSetIE includes an association relationship between a first identifier and at least one second identifier. The first identifier is an identifier corresponding to FeatureSetDownlink, ie, it may be a FeatureSetDownlinkId, and the second identifier is an identifier corresponding to FeatureSetDownlinkPerCC, which may be a FeatureSetDownlinkPerCCId. The association relationship between FeatureSetDownlinkIE and FeatureSetDownlinkPerCC may be the association relationship between FeatureSetDownlinkId and FeatureSetDownlinkPerCCI, that is, the association relationship between the first identifier and at least one second identifier is used to indicate the association relationship between FeatureSetDownlinkIE and at least one FeatureSetDownlinkPerCCIE.

It should be noted that the following row capability parameters are taken as an example for description. For the specific form of the uplink capability parameters, 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 unit may be FeatureSetUplinkIE, and the second information unit may be FeatureSetUplinkPerCCIE. In addition, the FeatureSetUplinkPerCCId and the FeatureSetUplinkIE are decoupled, that is, the FeatureSetUplinkPerCCId in the FeatureSetUplinkIE is deleted, so that the FeatureSetUplinkIE only includes the uplink capability parameter at the frequency level and does not include the FeatureSetUplinkPerCCId. FeatureSetUplinkPerCC contains uplink capability parameters at the carrier level. The third information unit corresponds to an uplink capability parameter of a frequency band in a frequency band combination of the terminal, that is, it may be a FeatureSetIE.

FeatureSetIE includes an association relationship between a first identifier and at least one second identifier. The first identifier is an identifier corresponding to FeatureSetUplink, ie, it may be a FeatureSetUplinkId, and the second identifier is an identifier corresponding to FeatureSetUplinkPerCC, which may be a FeatureSetUplinkPerCCId. The association relationship between FeatureSetUplinkIE and FeatureSetUplinkPerCC may be the association relationship between FeatureSetUplinkId and FeatureSetUplinkPerCCI, that is, the association relationship between the first identifier and at least one second identifier is used to indicate the association relationship between FeatureSetUplinkIE and at least one FeatureSetUplinkPerCCIE.

Exemplarily, the following capability parameters are taken as an example. FIG. 6 shows a capability message reported by a terminal according to an embodiment of the present application. The capability message includes two FeatureSet IEs, and the capability message also includes two FeatureSetDownlink IEs, which characterize the terminal. Supports two types of downlink capability parameters at the frequency band level. The capability message also includes three FeatureSetDownlinkPerCCIEs, indicating that the terminal supports three types of carrier level downlink capability parameters. Among them, FeatureSet IE1 includes the association relationship between FeatureSetDownlinkId1 and FeatureSetDownlinkPerCCId1, FeatureSetDownlinkPerCCId2, FeatureSetDownlinkPerCCId3, which means that a downlink capability parameter of a frequency band in a frequency band combination of the terminal includes the downlink capability parameter of the frequency band included in IE corresponding to FeatureSetDownlinkId1 The downlink capability parameter of the carrier level included in the IE corresponding to FeatureSetDownlinkPerCCId1, and a downlink capability parameter of one frequency band in another frequency band combination of the terminal includes the downlink capability parameter of the frequency band included in the IE corresponding to FeatureSetDownlinkId1 and the IE corresponding to FeatureSetDownlinkPerCCId2. Carrier-level downlink capability parameters. A type of downlink capability parameter for one frequency band in another frequency band combination of the terminal includes downlink-level capability parameters of the frequency band contained in the IE corresponding to FeatureSetDownlinkId1 and carrier-level downlink capability parameters of the IE corresponding to FeatureSetDownlinkPerCCId3 . Similarly, the IE corresponding to FeatureSet IE2 includes the relationship between FeatureSetDownlinkId2 and FeatureSetDownlinkPerCCId1, FeatureSetDownlinkPerCCId2, FeatureSetDownlinkPerCCId3, and is used to characterize the terminal's three other downlink capability parameters.

In addition, the capability message structure shown in FIG. 6 can also be represented by FIG. 7. Among them, each IE in FIG. 7 (such as the IEs indicated by the solid-line boxes 1 to 5) and the capability parameters included in each IE can refer to the description in FIG. 6, and will not be repeated here. It should be noted that in FIG. 7, the horizontal line in the FeatureSetDownlinkIE indicates that the FeatureSetDownlinkIE is decoupled from the FeatureSetDownlinkPerCCId, that is, the FeatureSetDownlinkPerCCId is deleted in the FeatureSetDownlinkIE. In addition, FIG. 6 exemplarily shows carrier-level downlink capability parameters 1, carrier-level downlink capability parameters 2, carrier-level downlink capability parameters 3, and FIG. 7 does not show downlink capability parameters of all three carrier levels. Only the carrier level downlink capability parameter 1 included in the IE corresponding to FeatureSetDownlinkPerCCId1 is shown (see multiple capability parameters shown by dashed box 501 in FIG. 7 and other carrier level capability parameters not shown), and the downlink capability Parameter 1 is only a part of the downlink capability parameters at the carrier level. Similarly, FIG. 6 exemplarily shows the downlink capability parameter 1 at the frequency band level and the downlink capability parameter 2 at the frequency band level, and FIG. 7 only shows the downlink capability parameter 1 at the frequency level included in the IE corresponding to FeatureSetDownlinkId1 (including the figure) A plurality of capability parameters shown by a dashed box 401 in FIG. 7 and other capability parameters at a frequency band level (not shown), and the downlink capability parameter 1 is only a part of the downlink capability parameters at a frequency band level. FIG. 6 shows the IE corresponding to FeatureSet IE1 and FeatureSet IE2, and FIG. 7 shows only FeatureSet IE1.

It should be noted that, in the above FIG. 6 and FIG. 7, the number of IEs included in the capability message may have other conditions, which is not limited in the embodiment of the present application.

Case 2: In the embodiment of the present application, a new information unit is defined to indicate a capability parameter of a frequency band level. Specifically, the following row capability parameter is taken as an example. The capability message includes a first information unit (ie, a new information unit, for example, as FeatureSetDownlinkParaIE), a second information unit (FeatureSetDownlinkPerCCIE), a third information unit (FeatureSetIE), and a first information unit. Four information units (FeatureSetDownlink IE). It should be noted that the newly defined information unit is an exemplary information unit. 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 elements appearing below are similar.

The FeatureSet IE includes an association relationship between the first identifier and the fourth identifier. The first identifier is the identifier of FeatureSetDownlinkPara, ie, it is recorded as FeatureSetDownlinkParaId, and the fourth identifier is the identifier of FeatureSetDownlink, ie, FeatureSetDownlinkId. The relationship between FeatureSetDownlinkPara IE and FeatureSetDownlink IE may be the relationship between FeatureSetDownlinkParaId and FeatureSetDownlinkId, that is, the relationship between the first identifier and the fourth identifier may indicate the relationship between FeatureSetDownlinkParaIE and FeatureSetDownlinkIE.

FeatureSetDownlinkPara IE includes downlink capability parameters at the frequency band level and does not include the second identifier. The second identifier is the identifier of FeatureSetDownlinkPerCC, ie, it can be FeatureSetDownlinkPerCCId.

FeatureSetDownlinkIE includes at least one second identifier. FIG. 8 shows an exemplary structure of a capability message when the FeatureSetDownlink IE contains a FeatureSetDownlinkPerCCId. FIG. 9 illustrates an exemplary structure of a capability message when the FeatureSetDownlinkIE contains 3 FeatureSetDownlinkPerCCIds. Of course, the number of FeatureSetDownlinkPerCCIds specifically included in the FeatureSetDownlink IE can be flexibly set according to the application scenario, and this embodiment of the present application does not limit this.

FeatureSetDownlinkPerCC IE contains downlink capability parameters at the carrier level.

Therefore, referring to FIG. 8, the capability message includes the IEs shown in blocks 1 to 14, and the downlink capability parameters of the terminal on a frequency band of a frequency band combination include the following:

1. The first type of downlink capability parameters includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId1 contained in FeatureSet1 are indexed to the corresponding IE, the downlink capability parameter 1 of the frequency band contained in the IE corresponding to FeatureSetDownlinkParaId1 and the downlink capability parameter 1 at the carrier level indexed by FeatureSetDownlinkId1 The first type of downlink capability parameter.

2. The second type of downlink capability parameter includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId2 included in the IE corresponding to FeatureSet2 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId1 contains the frequency-level capability parameter 1 and the carrier-level capability parameter 2 indexed by FeatureSetDownlinkId2 Forms the second type of downlink capability parameter.

3. The third type of downlink capability parameters includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId3 contained in the IE corresponding to FeatureSet3 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId1 contains the frequency-level capability parameter 1 contained in the IE corresponding to FeatureSet3 and the carrier-level capability parameter 3 indexed by FeatureSetDownlinkId3. Forms a third type of downlink capability parameter.

4. The fourth type of downlink capability parameter includes: FeatureSetDownlinkParaId2 and FeatureSetDownlinkId1 included in the IE corresponding to FeatureSet 4 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId2 corresponds to the frequency level capability parameter 2 contained in the IE and the carrier level capability parameter 1 indexed by FeatureSetDownlinkId1 Forms the fourth type of downlink capability parameter.

5. The fifth type of downlink capability parameters includes: FeatureSetDownlinkParaId2 and FeatureSetDownlinkId2 included in the IE corresponding to FeatureSet5 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId2 corresponds to the bandwidth level capability parameter 2 and the carrier level capability parameter 2 indexed by FeatureSetDownlinkId2. Forms the fifth type of downlink capability parameter.

6. The sixth type of downlink capability parameters includes: FeatureSetDownlinkParaId2 and FeatureSetDownlinkId3 contained in the IE corresponding to FeatureSet 6 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId2 corresponds to the bandwidth level capability parameter 2 and the carrier level capability parameter 3 indexed by FeatureSetDownlinkId3 Forms the sixth type of downlink capability parameter.

The capability message structure of FIG. 8 may also be represented by FIG. 10. Among them, only the IE corresponding to FeatureSetDownlinkParaId1 and the IE corresponding to FeatureSetDownlinkPerCCId1 are shown in FIG. 10. Similarly, the capability message structure shown in FIG. 9 can also be expressed in other forms, as shown in the related descriptions of FIG. 8 and FIG. 10, and each downlink capability parameter in FIG. 9 specifically includes a carrier-level downlink capability parameter and a frequency band. For the downlink capability parameter of the level, refer to the description of FIG. 8 described above, which will not be repeated here.

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

Case 3: The same type of IE included in the capability message in Case 2 above. The following row capability parameters are taken as an example. The capability message includes a first information unit (FeatureSetDownlinkParaIE), a second information unit (FeatureSetDownlinkPerCCIE), a third information unit (FeatureSetIE), and a fourth information unit (FeatureSetDownlinkIE). Among them, the capability parameters included in FeatureSetDownlinkPerCC and FeatureSetDownlinkPara IE can refer to the description in Case 2, and will not be repeated here.

FeatureSetDownlinkIE includes a first identifier and a second identifier. The first identifier is the identifier corresponding to FeatureSetDownlinkPara, ie, it may be a FeatureSetDownlinkParaId, and the second identifier is the identifier corresponding to FeatureSetDownlinkPerCC, and may be the featureSetDownlinkPerCCId. The relationship between FeatureSetDownlinkPara IE and FeatureSetDownlinkPerCC IE may be the relationship between FeatureSetDownlinkParaId and FeatureSetDownlinkPerCCId. The first identifier and at least one second identifier have an association relationship, and the association relationship is used to indicate the relationship between FeatureSetDownlinkPara and IE and FeatureSetDownlinkPerCC.

It should be noted that in each FeatureSetDownlinkIE, each FeatureSetDownlinkParaId corresponds to at least one FeatureSetDownlinkPerCCId. FIG. 11 shows the structure of a capability message when one FeatureSetDownlinkParaId corresponds to one FeatureSetDownlinkPerCCId, and FIG. 12 shows the structure of a capability message when one FeatureSetDownlinkParaId corresponds to three FeatureSetDownlinkPerCCIds. Of course, the number of FeatureSetDownlinkPerCCId corresponding to each FeatureSetDownlinkParaId can be set separately, which is not limited here.

FeatureSetIE includes a fourth identifier, and the fourth identifier is FeatureSetDownlinkId.

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

1. The first capability parameter includes: the IE index corresponding to FeatureSetDownlinkId1 to the corresponding FeatureSetDownlinkIE, and then the IE index corresponding to FeatureSetDownlinkId1 to the carrier level capability parameter 1 and the band level capability parameter 1, the carrier level capability parameter 1 and the frequency band The capability parameter 1 of the level constitutes the first capability parameter.

2. The second type of capability parameter includes the carrier level capability parameter 2 and the frequency band level capability parameter 1 which are indexed by the IE index corresponding to FeatureSetDownlinkId2.

3. The third capability parameter includes: a carrier-level capability parameter 3 and a band-level capability parameter 1 which are indexed by the IE index corresponding to FeatureSetDownlinkId3.

4. The fourth type of capability parameter includes: a carrier level capability parameter 1 and a frequency band level capability parameter 2 to which the IE index corresponding to FeatureSetDownlinkId4 corresponds.

5. The fifth capability parameter includes: a carrier-level capability parameter 2 and a band-level capability parameter 2 that are indexed by the IE index corresponding to FeatureSetDownlinkId5.

6. The sixth capability parameter includes: a carrier-level capability parameter 3 and a band-level capability parameter 2 which are indexed by the IE index corresponding to FeatureSetDownlinkId1.

The capability message structure of FIG. 11 may also be represented by FIG. 13. Similarly, the capability message structure shown in FIG. 12 may also be expressed in other forms. For details, refer to the related descriptions of FIG. 11 and FIG. 12, and details are not described herein again.

Case 4: The following row capability parameters are taken as an example. The capability message includes a first information unit (FeatureSetDownlinkIE), a second information unit (FeatureSetDownlinkPerCCIE), and a third information unit (FeatureSetIE). The downlink capability parameters included in the FeatureSetDownlinkPerCCIE can be referred to the descriptions in the

above cases

1, 2, and 3, and are not repeated here.

FeatureSetIE contains a first identifier, and the first identifier is an identifier corresponding to the first information unit (ie, FeatureSetDownlinkId).

FIG. 14 is a schematic structural diagram of a capability message. Therefore, the downlink capability parameters of the terminal on one frequency band of one frequency band combination include the following:

1. The first type of downlink capability parameter includes: FeatureSetDownlink IE1 index to the corresponding FeatureSetDownlink IE, and then the IE index corresponding to FeatureSetDownlinkId1 to the carrier-level downlink capability parameter 1 and the band-level downlink capability parameter 1, and the carrier-level downlink capability parameter 1 And the downlink capability parameter 1 of the frequency band level constitutes the first downlink capability parameter.

2. The second type of downlink capability parameter includes: a downlink capability parameter 2 of the carrier level and a downlink capability parameter 1 of a frequency band indexed by the IE index corresponding to FeatureSetDownlinkId1.

3. The third type of downlink capability parameter includes: a downlink capability parameter 3 of a carrier level and a downlink capability parameter 1 of a frequency band indexed by the IE index corresponding to FeatureSetDownlinkId1.

The capability message of FIG. 14 can also be represented by FIG. 15. For a detailed description of the capability message, refer to the descriptions of

cases

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

It can be understood that, for a terminal's uplink capability parameter of a frequency band in a frequency band combination, reference may be made to related expressions of the downlink capability parameter, and details are not described herein again.

It should be noted that the third information unit (FeatureSetIE) includes the uplink capability parameter and the downlink capability parameter of the terminal, that is, the FeatureSetIE corresponds to both the terminal's capability in the uplink direction (uplink capability) and the terminal in the downlink direction. A FeatureSet IE can characterize at least one uplink capability and at least one downlink capability of a terminal. Taking the uplink capability of the terminal corresponding to the FeatureSet IE as an example, the first information unit includes an uplink capability parameter at a frequency band level, and the second information unit includes an uplink capability parameter at a carrier level. Taking the downlink capability of the terminal corresponding to the FeatureSet IE as an example, the first information unit includes a downlink capability parameter at a frequency band level, and the second information unit includes a downlink capability parameter at a carrier level.

It should be noted that before sending a 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 connection state, since the RRC connection with the access network device has been established, the RRC connection can be used to send the capability message to the access network device directly. 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.

Exemplarily, when the terminal reports its capabilities in NR and E-UTRA, the capability message carries a container of NR and an E-UTRA container. Among them, the container of the NR includes an IE having any of the structures shown in FIG. 6 to FIG. 13. The capabilities supported by the terminal in the NR are reported. The E-UTRA container includes the The IE of any structure reports the capabilities supported by the terminal in E-UTRA.

In the capability reporting method provided in the embodiment of the present application, the capability message reported by the terminal includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit. The first information unit includes a capability parameter at a frequency band level and does not include an identifier of the capability parameter at a carrier level, and the second information element includes a capability parameter at a carrier level. It can be seen that when a terminal reports a carrier-level capability parameter, it is not necessary to report a carrier-level capability parameter (for example, a carrier-level capability parameter indicated by a dashed box 501 in FIG. 1), and it corresponds to reporting at least one band-level capability parameter (e.g., FIG. 1 Band-level capability parameters indicated by dashed box 401), that is, the terminal can report multiple carrier-level capability parameters at the same time as reporting a band-level capability parameter, reducing band-level capability parameters Probability of repeated reporting, thereby reducing signaling overhead when the terminal reports capabilities.

It can be understood that, in order to implement the foregoing functions, the terminal in the embodiments of the present application includes a hardware structure and / or a software module corresponding to each function. With reference to the units and algorithm steps of each example described in the embodiments disclosed in this application, the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.

The embodiments of the present application may divide the functional units of the terminal according to the foregoing method examples. 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 above integrated unit may be implemented in the form of hardware or in the form of software functional unit. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. There may be another division manner in actual implementation.

FIG. 16 shows a schematic block diagram of a communication device provided in an embodiment of the present application. The communication device 1600 may be an independent device or a chip that can be used for the device. The communication device 1600 may be the foregoing terminal or a network device. The communication device 1600 includes a processing unit 1602 and a communication unit 1603.

When the communication device 1600 is a terminal, the processing unit 1602 may be used to support the terminal to determine whether it is in a connected state / idle state, thereby determining whether to establish an RRC connection with the access network device, and / or for the scheme described herein. Other processes. The communication unit 1603 is used to support communication between the terminal and other network elements (such as the access network device described above), for example, to support the terminal to perform S501 and S502 in FIG. 5 and / or other processes used in the scheme described herein. .

When the communication device 1600 is a network device, the processing unit 1602 may be configured to support the network device for the process described herein, for example, allocate corresponding communication resources to the terminal. The communication unit 1603 is used to support communication between a network device and other network elements (such as the above-mentioned terminal, etc.), for example, to support the network device to perform S501 and S502 in FIG. 5 and / or other processes used in the scheme described herein.

Optionally, the communication device 1600 may further include a storage unit 1601 for storing program code and data of the communication device 1600. The data may include, but is not limited to, original data or intermediate data.

In a possible manner, the processing unit 1602 may be a controller or the processor 401 or the processor 405 shown in FIG. 4, for example, it may be a central processing unit (Central Processing Unit), a general-purpose processor, and digital signal processing ( Digital Signal Processing (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any of them combination. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. A processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication unit 1603 may be a transceiver, a transceiver circuit, or the communication interface 404 shown in FIG. 4 and the like. The storage unit 1601 may be a memory 403 shown in FIG. 4.

A person of ordinary skill in the art may understand that in the foregoing embodiments, all or part may be implemented by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center via a wired (e.g., Coaxial cable, optical fiber, Digital Subscriber Line (DSL) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like including one or more available medium integration. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a Digital Video Disc (DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)), etc. .

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or integrated. To another system, or some features can be ignored and not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical or other forms.

A unit described as a separate component may or may not be physically separated, and a component displayed as a unit may or may not be a physical unit, which may be located in one place, or may be distributed to multiple network devices (such as terminal devices). )on. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

In addition, each functional unit in each embodiment 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 above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.

Through the description of the above embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general hardware, and of course, also by hardware, but in many cases the former is a better implementation. . Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk , Hard disk or optical disk, etc., includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods of the embodiments of the present application.

The above are only specific implementations of this application, but the scope of protection of this application is not limited to this. Changes or replacements within the technical scope disclosed in this application should be covered by the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A capability reporting method, including:

The terminal device sends the capability message to a network device, where the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit, and the first information unit includes a frequency band level Capability parameter, the second information unit includes a carrier level capability parameter.
The capability reporting method according to 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.
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, and 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.
The capability reporting method according to claim 3, wherein the capability message further includes a third information unit, and the third information unit includes an association relationship between the first identifier and at least one second identifier, and The third information unit corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal.
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 the first identifier. The identifier corresponding to the two information units.
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, and the first identifier is the first identifier An identifier corresponding to an information unit, and the fourth identifier is an identifier corresponding to the fourth information unit.
The capability reporting method according to claim 6, wherein the capability message further comprises a third information unit, and the third information unit includes an association relationship between the first identifier and the fourth identifier.
The capability reporting method according to 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 first information unit and The association relationship of the second information unit is an association relationship between the first identifier and at least one second identifier.
The capability reporting method according to claim 8, wherein the capability message further includes a third information unit, the third information unit includes a fourth identifier, and the fourth identifier is an identifier of the fourth information unit.
The capability reporting method according to any one of claims 1 to 9, wherein:

The first information unit includes an uplink capability parameter at a frequency band level, and the second information unit includes an uplink capability parameter at a carrier level, or

The first information unit includes a downlink capability parameter at a frequency band level, and the second information unit includes a downlink capability parameter at a carrier level.
The capability reporting method according to any one of claims 1 to 10, wherein a capability parameter of a frequency band in a frequency band combination of the terminal device includes a capability parameter in a first information unit and a second A capability parameter in an information unit.
A capability reporting method, including:

The access network device receives a capability message sent by the terminal device. The capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit. The first information unit includes a frequency band level. The second information unit includes a carrier-level capability parameter.
The capability reporting method according to 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.
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, and 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.
The capability reporting method according to claim 14, wherein the capability message further includes a third information unit, and the third information unit includes an association relationship between the first identifier and at least one second identifier, and the The third information unit corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal.
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 the first identifier. The identifier corresponding to the two information units.
The capability reporting method according to claim 16, wherein an association relationship between the first information unit and a second information unit is an association relationship between a first identifier and a fourth identifier, and the first identifier is the first identifier An identifier corresponding to an information unit, and the fourth identifier is an identifier corresponding to the fourth information unit.
The capability reporting method according to claim 17, wherein the capability message further comprises a third information unit, and the third information unit includes an association relationship between the first identifier and the fourth identifier.
The capability reporting method according to claim 16, wherein the fourth information unit further comprises a first identifier, the first identifier is an identifier corresponding to the first information unit, and the first information unit and The association relationship of the second information unit is an association relationship between the first identifier and at least one second identifier.
The capability reporting method according to claim 19, wherein the capability message further includes a third information unit, the third information unit includes a fourth identifier, and the fourth identifier is an identifier of the fourth information unit.
The capability reporting method according to any one of claims 12 to 20, wherein

The first information unit includes an uplink capability parameter at a frequency band level, and the second information unit includes an uplink capability parameter at a carrier level, or

The first information unit includes a downlink capability parameter at a frequency band level, and the second information unit includes a downlink capability parameter at a carrier level.
The capability reporting method according to any one of claims 12 to 21, wherein a capability parameter of a frequency band in a frequency band combination of the terminal device includes a capability parameter in a first information unit and a second A capability parameter in an information unit.
A terminal characterized by comprising: a processor, a memory, a bus, and a communication interface;

The memory is used to store computer execution instructions, the processor is connected to the memory through the bus, and when the terminal is running, the processor executes the computer execution instructions stored in the memory so that all the The terminal executes the capability reporting method according to any one of claims 1-11.
A network device, comprising: a processor, a memory, a bus, and a communication interface;

The memory is used to store computer execution instructions, and the processor is connected to the memory through the bus. When the network device is running, 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 claims 12-22.
A readable storage medium, comprising a program or an instruction, and when the program or the instruction is executed, the method for reporting a capability according to any one of claims 1 to 11 is implemented, or The capability reporting method according to any one of 12 to 22 is implemented.
A terminal includes: a transceiver and a processor:

The processor is configured to determine whether the terminal is in a connected state, and if so, control the transceiver to send a capability message to a network device, and if not, establish a connection with the network device and use the established The RRC connection sends the capability message to the network device;

The transceiver is configured to send the capability message to the network device, where the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit, and the first An information unit includes a capability parameter at a frequency band level, and the second information unit includes a capability parameter at a carrier level.
The terminal according to claim 26, wherein the first information unit does not include a second identifier, and the second identifier is an identifier corresponding to the second information unit.
The terminal according to claim 26 or 27, 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, and the first identifier is The identifier corresponding to the first information unit, and the second identifier is an identifier corresponding to the second information unit.
The terminal according to claim 28, wherein the capability message further includes a third information unit, and the third information unit includes an association relationship between the first identifier and at least one second identifier, and the third The information unit corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal.
The terminal according to claim 26 or 27, 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 the second information The ID corresponding to the unit.
The terminal according to claim 30, 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, and the first identifier is the first information An identifier corresponding to the unit, and the fourth identifier is an identifier corresponding to the fourth information unit.
The terminal according to claim 31, wherein the capability message further includes a third information unit, and the third information unit includes an association relationship between the first identifier and the fourth identifier.
The terminal according to claim 30, wherein the fourth information unit further comprises a first identifier, the first identifier is an identifier corresponding to the first information unit, the first information unit and the second information unit The association relationship between the information units is an association relationship between the first identifier and at least one second identifier.
The terminal according to claim 33, wherein the capability message further includes a third information unit, the third information unit includes a fourth identifier, and the fourth identifier is an identifier of the fourth information unit.
The terminal according to any one of claims 26 to 34, wherein

The first information unit includes an uplink capability parameter at a frequency band level, and the second information unit includes an uplink capability parameter at a carrier level, or

The first information unit includes a downlink capability parameter at a frequency band level, and the second information unit includes a downlink capability parameter at a carrier level.
The terminal according to any one of claims 26 to 35, wherein a capability parameter of a frequency band in a frequency band combination of the terminal device includes a capability parameter in a first information unit and a second information unit Capability parameter in.
A capability reporting method, including:

The terminal device establishes a connection with the network device, or the terminal device communicates with the network device;

In the case of an RRC connection, the terminal device sends a capability message to the network device. The capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit. The first information unit includes a frequency band. Level capability parameter, the second information element contains a carrier level capability parameter.
The capability reporting method according to claim 37, wherein the first information unit further includes a carrier-level parameter set, and the carrier-level parameter set includes at least two second identifiers, and the second identifier is the second identifier The identifier corresponding to the second information unit.
The method according to claim 37, wherein the capability information further comprises a third information unit, and 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, and the first identifier is an identifier corresponding to the first information unit.
The method according to claim 37, wherein the association relationship between the first information unit and the second information unit is an association relationship between a band-level capability parameter and a second identifier.
A communication method, comprising:

The network device receives a capability message sent by the terminal device, where the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit, and the first information unit includes a frequency band level capability Parameter, the second information unit includes a carrier level capability parameter.
The method according to claim 41, wherein the first information unit does not include a second identifier, and the second identifier is an identifier corresponding to the second information unit.
The method according to claim 41, wherein the capability message further includes a third information unit, and the third information unit includes an association relationship between the first identifier and at least one second identifier, and the third The information unit corresponds to a capability parameter of a frequency band in a frequency band combination of the terminal.
The method according to claim 41, wherein the capability message further comprises a third information unit and a fourth information unit, and the third information unit includes an association between the first identifier and at least one second identifier In a relationship, the fourth information unit includes at least one second identifier, and the second identifier is an identifier corresponding to the second information unit.
The method according to claim 44, wherein the first information unit is FeatureSetDownlinkParaie, the second information unit is FeatureSetDownlinkPerCCIE, the third information unit is FeatureSetIE, and the fourth information unit is Link Information Element (FeatureSetDownlinkIE).
A capability reporting method, including:

When an RRC connection exists, the network device receives a capability message sent by the terminal device, where the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit The first information unit includes a capability parameter at a frequency band level, and the second information unit includes a capability parameter at a carrier level.
The method according to claim 46, wherein the first information unit further comprises a carrier level parameter set, the carrier level parameter set includes at least two second identifiers, and the second identifier is a second information unit The corresponding ID.
The method according to claim 46, wherein the capability information further comprises a third information unit, and 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, and the first identifier is an identifier corresponding to the first information unit.
The capability reporting method according to any one of claims 46 to 48, wherein a capability parameter of a frequency band in a frequency band combination of the terminal device includes a capability parameter in a first information unit and a second A capability parameter in an information unit.
A chip is characterized in that it comprises a processor, 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 execution of claim 1- The capability reporting method according to any one of 11.
A chip is characterized in that it comprises a processor, 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 execution of claim 12- The capability reporting method according to any one of 22.