CN111614443B

CN111614443B - Terminal capability reporting and information receiving method, terminal and network equipment

Info

Publication number: CN111614443B
Application number: CN201910406599.1A
Authority: CN
Inventors: 鲁智; 潘学明; 陈晓航; 李娜
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2019-05-10
Filing date: 2019-05-10
Publication date: 2023-04-25
Anticipated expiration: 2039-05-10
Also published as: CN111614443A

Abstract

The invention provides a terminal capability reporting and information receiving method, a terminal and network equipment, wherein the terminal capability reporting method comprises the following steps: transmitting indication information to the network equipment; the indication information indicates the capability of the terminal for supporting the physical shared channel out-of-order scheduling and a bandwidth threshold value; the bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target BWP, and the bandwidth size of the target BWP is smaller than or equal to the bandwidth threshold value. The embodiment of the invention can enable the network equipment to acquire the capability of the terminal, so that when the mixed services are subjected to out-of-order scheduling, the scheduling can be performed based on the capability of the terminal and actual requirements, the reliable transmission of the high-priority service is ensured, and the large influence on other services is avoided.

Description

Terminal capability reporting and information receiving method, terminal and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method for reporting terminal capability, an information receiving method, a terminal, and a network device.

Background

Future 5G mobile communication systems need to accommodate more diverse scenarios and service requirements than previous mobile communication systems. The main scenes of the future 5G include mobile broadband enhancement (eMBB), ultra-high reliability ultra-low latency communication (URLLC), large-scale internet of things (mctc), and the like, and these scenes put forward requirements of high reliability, low latency, large bandwidth, wide coverage, and the like for the corresponding communication systems.

For physical shared channels, such as physical downlink shared channels (Physical Downlink Shared Channel, PDSCH), terminals currently support in-order (in order) grant scheduling and in-order hybrid automatic repeat request (Hybrid Automatic Repeat request, HARQ) scheduling. Sequential grant scheduling as shown in fig. 1A, a first scheduling grant (scheduling grant) is received earlier than a second scheduling grant for a terminal such as a User Equipment (UE), and the UE receives a PDSCH2 scheduled by the first scheduling grant earlier than the second scheduling grant, i.e., a PDSCH1 starting symbol earlier than a PDSCH2 starting symbol. In-order HARQ scheduling as shown in fig. 1B, the arrival time of the first PDSCH1 is earlier than the arrival time of the second PDSCH2 (e.g., the PDSCH1 starting symbol time is earlier than the PDSCH2 starting symbol), the HARQ acknowledgement ACK feedback 1 (i.e., HARQ-ACK feedback 1) of the first received PDSCH1 precedes the HARQ-ACK feedback 2 of the second received PDSCH 2.

For a terminal supporting both the eMBB service and the URLLC service, after the base station gNB schedules PDSCH transmission of one eMBB service, there may be a arrival of the URLLC service, and PDSCH transmission of one URLLC service needs to be scheduled. I.e. the post-scheduled PDSCH starting symbol is earlier than the pre-scheduled PDSCH starting symbol. This is known as out of order (out of order) grant scheduling. Furthermore, due to the low latency requirement of the URLLC traffic, the HARQ-ACK feedback of the post-scheduled (received) URLLC PDSCH may need to be fed back before the HARQ-ACK feedback of the eMBB PDSCH, i.e. the HARQ-ACK of the post-scheduled (received) PDSCH is instead fed back preferentially, referred to as out-of-order HARQ scheduling. Out-of-order grant scheduling and out-of-order HARQ scheduling are beneficial for guaranteeing transmission of high priority traffic, but have higher requirements for terminal capabilities.

However, the capability of the terminal to support out-of-order grant scheduling and out-of-order HARQ scheduling is not specified at present, so that the terminal cannot guarantee the transmission of high-priority service under the condition of supporting multiple mixed services.

Disclosure of Invention

The embodiment of the invention provides a terminal capability reporting and information receiving method, a terminal and network equipment, which are used for solving the problem that the transmission of high-priority service cannot be ensured under the condition that the terminal supports multiple mixed services at present.

In order to solve the technical problems, the embodiment of the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a method for reporting terminal capability, which is applied to a terminal, and includes:

transmitting indication information to the network equipment;

the indication information indicates the capability of the terminal for supporting out-of-order scheduling of the physical shared channel and a bandwidth threshold value; the bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target BWP, and the bandwidth size of the target BWP is smaller than or equal to the bandwidth threshold value.

In a second aspect, an embodiment of the present invention provides an information receiving method, applied to a network device, including:

receiving indication information from a terminal;

In a third aspect, an embodiment of the present invention provides a terminal, including:

the sending module is used for sending the indication information to the network equipment;

In a fourth aspect, an embodiment of the present invention provides a network device, including:

the receiving module is used for receiving the indication information from the terminal;

In a fifth aspect, an embodiment of the present invention provides a terminal, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the computer program when executed by the processor implements the steps of the method for reporting terminal capability.

In a sixth aspect, an embodiment of the present invention provides a network device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the computer program is executed by the processor to implement the steps of the above information receiving method.

In a seventh aspect, an embodiment of the present invention provides a computer readable storage medium having a computer program stored thereon, where the computer program when executed by a processor implements the steps of the terminal capability reporting method or implements the steps of the information receiving method.

In the embodiment of the invention, the network equipment can acquire the capability of the terminal by sending the indication information indicating the capability of the terminal to the network equipment, so that when the out-of-order scheduling is carried out for a plurality of mixed services, the scheduling can be carried out based on the capability of the terminal and the actual requirements, the reliable transmission of high-priority services such as URLLC services is ensured, and the large influence on other services is avoided.

Drawings

FIG. 1A is a schematic diagram of a prior art sequential grant schedule;

fig. 1B is a schematic diagram of sequential HARQ scheduling in the prior art;

fig. 2A is a schematic diagram of PDSCH out-of-order HARQ scheduling in an embodiment of the present invention;

fig. 2B is a schematic diagram of PUSCH out-of-order grant scheduling in an embodiment of the present invention;

fig. 2C is a schematic diagram of PDSCH out-of-order grant scheduling in an embodiment of the present invention;

fig. 3 is a flowchart of a terminal capability reporting method according to an embodiment of the present invention;

fig. 4 is a flowchart of an information receiving method according to an embodiment of the present invention;

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

fig. 6 is a schematic diagram of a network device according to an embodiment of the present invention;

FIG. 7 is a second schematic diagram of a terminal according to an embodiment of the present invention;

fig. 8 is a second schematic diagram of a network device according to an embodiment of the invention.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.

In order to facilitate understanding of the present invention, first, PDSCH out-of-order scheduling and PUSCH out-of-order scheduling in the embodiments of the present invention will be described with reference to fig. 2A, fig. 2B, and fig. 2C, respectively.

As shown in fig. 2A, if the UE receives PDSCH transmission of the eMBB service at time t1 and then a certain URLLC service arrives, the UE receives PDSCH transmission of the URLLC service at time t2 (t 1 is earlier than t 2), but due to the requirement of low latency of the URLLC service, HARQ-ACK2 of the post-received URLLC PDSCH needs to be fed back before HARQ-ACK 1 of the eMBB PDSCH, and HARQ-ACK of the post-received PDSCH is preferentially fed back instead to be referred to as PDSCH out-of-order HARQ scheduling.

As shown in fig. 2B, if the gNB schedules the PUSCH transmission of the eMBB service at time t3 (i.e. sends a scheduling grant), then a certain URLLC service arrives, and the gNB schedules the PUSCH transmission of the URLLC service at time t4 (t 3 is earlier than t 4) (i.e. sends a scheduling grant), but due to the requirement of low latency of the URLLC service, the post-scheduled URLLC PUSCH transmission is required before the eMBB PUSCH transmission (i.e. the post-scheduled PUSCH start symbol is earlier than the pre-scheduled PUSCH start symbol), and the post-scheduled URLLC PUSCH is instead preferentially transmitted as PUSCH out-of-order grant scheduling.

As shown in fig. 2C, if the gNB schedules a PDSCH transmission of an eMBB service (i.e., sends a scheduling grant) at time t5, then a certain URLLC service arrives, and the gNB schedules a PDSCH transmission of the URLLC service (i.e., sends a scheduling grant) at time t6 (t 5 is earlier than t 6), but due to the requirement of low latency of the URLLC service, the post-scheduled URLLC PDSCH may occur before the previously-scheduled eMBB PDSCH (i.e., the URLLC PDSCH starting symbol is earlier than the eMBB PDSCH starting symbol), and the post-scheduled PDSCH priority transmission is instead referred to as PDSCH out-of-order grant scheduling.

In the embodiment of the present invention, for PDSCH, out-of-order grant scheduling and out-of-order HARQ scheduling may be collectively referred to as out-of-order scheduling. For PUSCH, out-of-order grant scheduling may be referred to as out-of-order scheduling.

Referring to fig. 3, fig. 3 is a flowchart of a method for reporting terminal capability, which is provided in an embodiment of the present invention, and is applied to a terminal, as shown in fig. 3, and includes the following steps:

step 301: and sending the indication information to the network equipment.

The indication information indicates the capability of the terminal for supporting the physical shared channel out-of-order scheduling and the bandwidth threshold value. The Bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target Bandwidth Part (BWP) having a Bandwidth size less than or equal to (i.e., less than or equal to) the Bandwidth threshold value.

Optionally, the physical shared channel may be at least one of the following:

a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH);

physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

In particular, when the terminal sends the indication information to the network device, the capability of supporting PDSCH out-of-order scheduling and the capability of supporting PUSCH out-of-order scheduling can be reported simultaneously, or the capability of supporting neither PDSCH out-of-order scheduling nor PUSCH out-of-order scheduling is reported, or the capability of supporting PDSCH out-of-order scheduling and the capability of supporting PUSCH out-of-order scheduling are reported, or the capability of supporting PDSCH out-of-order scheduling and the capability of not supporting PUSCH out-of-order scheduling are reported, which is not limited by the embodiment of the invention.

According to the terminal capability reporting method, the indicating information indicating the terminal capability is sent to the network equipment, so that the network equipment can acquire the capability of the terminal, when out-of-order scheduling is performed on various mixed services, scheduling can be performed based on the terminal capability and actual requirements, reliable transmission of high-priority services such as URLLC services is ensured, and great influence on other services is avoided.

In the embodiment of the present invention, for PDSCH and PUSCH, the terminal may have, but is not limited to, the following four capabilities, which are respectively described below.

Terminal capability 1:

wherein, the terminal capability 1 is a capability of PDSCH out-of-order scheduling supported by the terminal, and the terminal capability 1 may include:

1) If the bandwidth size of the downlink BWP configured on one carrier is less than or equal to the first bandwidth threshold value (i.e., the bandwidth sizes of all configured downlink BWP are less than or equal to the first bandwidth threshold value), the terminal processes the first PDSCH and the second PDSCH on the carrier (i.e., on the carrier BWP);

2) Alternatively, if the bandwidth size of any one of the configured downlink BWP (i.e., all configured downlink BWP) is greater than the first bandwidth threshold, the terminal processes (e.g., processes only) one of the first PDSCH and the second PDSCH on the carrier; and for another unprocessed PDSCH, the terminal may choose to discard; the processing PDSCH may be understood as decoding PDSCH, and after decoding PDSCH, corresponding HARQ-ACK feedback may be performed. For all or part of the discarded PDSCH, it can be understood that the UE stops decoding PDSCH and feeds back NACK for the discarded part.

Wherein, the first PDSCH and the second PDSCH are scheduled out of order in one downlink BWP, and the scheduling time of the first PDSCH is earlier than the scheduling time of the second PDSCH. The scheduling time of the first PDSCH may be understood as: the time of the scheduling grant for transmitting the first PDSCH. The scheduling time of the second PDSCH may be understood as: the time of the scheduling grant for transmitting the second PDSCH.

It is noted that for out-of-order grant scheduling, the time to receive the first PDSCH is later than the time to receive the second PDSCH; and for out-of-order HARQ scheduling, the time to receive the first PDSCH is earlier than the time to receive the second PDSCH.

Optionally, the first PDSCH and the second PDSCH may be any one of the following: overlapping in the time domain, non-overlapping in the frequency domain, and overlapping in both the time and frequency domains. And when the 2 PDSCHs overlap in both time and frequency domains, the terminal only needs to decode one of the 2 PDSCHs, such as the second PDSCH, in the frequency domain overlap region.

Optionally, one of the first PDSCH and the second PDSCH may be any one of the following:

a second PDSCH; namely, a post-scheduled PDSCH of the first PDSCH and the second PDSCH; in this way, since the service priority corresponding to the PDSCH scheduled later in out-of-order scheduling is generally higher, prioritizing the PDSCH scheduled later can be beneficial to ensuring reliable transmission of high priority services

PDSCH of the first PDSCH and the second PDSCH with high priority; in this way, PDSCH with high priority can be preferentially processed, which is beneficial to ensuring reliable transmission of high-priority traffic.

It should be noted that, for terminal capability 1, the terminal behavior is not changed due to BWP handover. That is, if the terminal can process 2 PDSCHs on a certain downlink BWP, the terminal can process 2 PDSCHs, which are out-of-order scheduled in the downlink BWP, on any one configured downlink BWP, and out-of-order scheduling can be performed on all configured downlink BWPs.

In the case of 1) above, the terminal may process the first PDSCH and the second PDSCH at the same time when processing the first PDSCH and the second PDSCH. Further in this case, the terminal may support PDSCH processing capability (PDSCH processing capability) 1 and PDSCH processing capability 2 simultaneously on carrier BWP. The PDSCH processing capability described above can be understood as PDSCH processing time (PDSCH processing time).

In the case of 2) above, for a downlink BWP with a bandwidth size less than or equal to the first bandwidth threshold value, the terminal may support PDSCH processing capability 1 and PDSCH processing capability 2 simultaneously on the downlink BWP, and when out-of-order scheduling, the terminal may process only one of 2 PDSCH of out-of-order scheduling on the downlink BWP, optionally discard the other PDSCH.

Further, for downlink BWP with bandwidth size larger than the first bandwidth threshold, the terminal supports only one PDSCH processing capability on the downlink BWP, and when out-of-order scheduling, the terminal processes only one of 2 PDSCH of out-of-order scheduling on the downlink BWP, optionally discards the other PDSCH. And when the terminal supports only one PDSCH processing capability, it can be divided into the following two cases:

case one: supporting PDSCH processing capability 1

In this case, if the first PDSCH does not have a corresponding additional demodulation reference signal (additional DMRS), out-of-order scheduling is not allowed. Or if the first PDSCH has an additional DMRS and the second PDSCH does not have an additional DMRS, the out-of-order scheduling is allowed, and at this time, the terminal processes only one of the first PDSCH and the second PDSCH, and optionally discards the other PDSCH.

And a second case: supporting PDSCH processing capability 2

In this case, out-of-order scheduling is allowed, the terminal processes only one of the first PDSCH and the second PDSCH, optionally discarding the other PDSCH.

Terminal capability 2:

wherein, the terminal capability 2 is a capability of PDSCH out-of-order scheduling supported by the terminal, and the terminal capability 2 may include:

3) If the bandwidth size of the activated downlink BWP on one carrier is smaller than or equal to the second bandwidth threshold value, the terminal processes the third PDSCH and the fourth PDSCH on the activated downlink BWP;

4) Or, if the bandwidth size of the activated downlink BWP is greater than the second bandwidth threshold value, the terminal processes (such as processes only) one of the third PDSCH and the fourth PDSCH on the activated downlink BWP; and for another unprocessed PDSCH, the terminal may choose to discard; the processing PDSCH may be understood as decoding PDSCH, and after decoding PDSCH, corresponding HARQ-ACK feedback may be performed. For all or part of the discarded PDSCH, it can be understood that the UE stops decoding PDSCH and feeds back NACK for the discarded part.

Wherein, the third PDSCH and the fourth PDSCH are scheduled out-of-order in the activated downlink BWP, and the scheduling time of the third PDSCH is earlier than the scheduling time of the fourth PDSCH. The scheduling time of the third PDSCH may be understood as: and a time of transmitting the scheduling grant of the third PDSCH. The scheduling time of the fourth PDSCH may be understood as: the time of the scheduling grant of the fourth PDSCH is transmitted.

It is noted that, for out-of-order grant scheduling, the time to receive the third PDSCH is later than the time to receive the fourth PDSCH; and for out-of-order HARQ scheduling, the time to receive the third PDSCH is earlier than the time to receive the fourth PDSCH.

Optionally, the third PDSCH and the fourth PDSCH may be any one of the following: overlapping in the time domain, non-overlapping in the frequency domain, and overlapping in both the time and frequency domains. And when the 2 PDSCHs overlap in both time and frequency domains, the terminal only needs to decode one of the 2 PDSCHs, such as the fourth PDSCH, in the frequency domain overlap region.

Optionally, one of the third PDSCH and the fourth PDSCH may be any one of the following:

a fourth PDSCH; namely, a post-scheduled PDSCH among the third PDSCH and the fourth PDSCH; in this way, the service priority corresponding to the PDSCH scheduled later during out-of-order scheduling is generally higher, so that the PDSCH scheduled later is processed preferentially, which can be beneficial to ensuring the reliable transmission of the high-priority service;

PDSCH with high priority among the third PDSCH and the fourth PDSCH; in this way, PDSCH with high priority can be preferentially processed, which is beneficial to ensuring reliable transmission of high-priority traffic.

It should be noted that, for terminal capability 2, the terminal behavior may change due to BWP handover. That is, if the bandwidth size of the switched downlink BWP (i.e., the activated downlink BWP) is changed from less than or equal to the second bandwidth threshold value to greater than the second bandwidth threshold value, the terminal may be changed from being able to process 2 PDSCH to being unable to process 2 PDSCH. For downlink BWP with bandwidth size smaller than or equal to the second bandwidth threshold value, out-of-order scheduling can be performed on the downlink BWP; and for downstream BWP with bandwidth size greater than the second bandwidth threshold value, out-of-order scheduling cannot be performed thereon.

In the case of 3) above, the terminal may process the third PDSCH and the fourth PDSCH at the same time when processing the third PDSCH and the fourth PDSCH. Further in this case, the terminal may support PDSCH processing capability 1 and PDSCH processing capability 2 simultaneously on the activated downlink BWP. The PDSCH processing capability described above may be understood as PDSCH processing time.

In the case of 4) above, for an activated downlink BWP with a bandwidth size less than or equal to the second bandwidth threshold value, the terminal may support PDSCH processing capability 1 and PDSCH processing capability 2 simultaneously on the downlink BWP, and when out-of-order scheduling, the terminal may process only one of 2 PDSCH of out-of-order scheduling on the downlink BWP, optionally discarding the other PDSCH.

Further, for an active downlink BWP with a bandwidth size greater than the second bandwidth threshold, the terminal supports only one PDSCH processing capability on the downlink BWP, and when out-of-order scheduling, the terminal processes only one of the 2 PDSCH of out-of-order scheduling on the downlink BWP, optionally discards the other PDSCH. And when the terminal supports only one PDSCH processing capability, it can be divided into the following two cases:

case one: supporting PDSCH processing capability 1

In this case, if the third PDSCH does not have a corresponding additional DMRS, out-of-order scheduling is not allowed. Or if the third PDSCH has an additional DMRS and the fourth PDSCH does not have an additional DMRS, the out-of-order scheduling is allowed, and at this time, the terminal processes only one of the third PDSCH and the fourth PDSCH, and optionally discards the other PDSCH.

And a second case: supporting PDSCH processing capability 2

In this case, out-of-order scheduling is allowed, the terminal processes only one of the third PDSCH and the fourth PDSCH, optionally discarding the other PDSCH.

Note that, the PDSCH processing capability 1 described above can be seen from the following table 1, and table 1 is a PDSCH processing time (PDSCH processing time for PDSCH processing capability 1) related to the PDSCH processing capability 1. The PDSCH processing capability 2 described above can be seen from the following table 2, and table 2 is the PDSCH processing time (PDSCH processing time for PDSCH processing capability 2) for the PDSCH processing capability 2.

TABLE 1

TABLE 2

Terminal capability 3:

wherein, the terminal capability 3 is a capability of PUSCH out-of-order scheduling supported by a terminal, and the terminal capability 3 may include:

5) If the bandwidth size of the uplink BWP configured on one carrier is smaller than or equal to the third bandwidth threshold value (i.e., the bandwidth sizes of all configured uplink BWP are smaller than or equal to the third bandwidth threshold value), the terminal processes the first PUSCH and the second PUSCH on the carrier (i.e., on the carrier BWP); wherein the first PUSCH and the second PUSCH do not overlap in the time domain;

6) Or if the bandwidth size of any one of the configured uplink BWP (i.e., all configured uplink BWP) is greater than the third bandwidth threshold, the terminal processes (e.g., only processes) one of the first PUSCH and the second PUSCH on the carrier; and for another unprocessed PUSCH, the terminal may choose to discard; this PUSCH processing may be understood as preparing PUSCH data, and after the preparation is completed, a corresponding PUSCH transmission may be performed.

Wherein, the first PUSCH and the second PUSCH are scheduled out of order in one uplink BWP, and the scheduling time of the first PUSCH is earlier than the scheduling time of the second PUSCH. The scheduling time of the first PUSCH may be understood as: the time of the scheduling grant of the first PUSCH is transmitted. The scheduling time of the second PUSCH may be understood as: and sending the scheduling grant time of the second PUSCH.

Alternatively, the first PUSCH and the second PUSCH may overlap in the time domain. And when the 2 PUSCHs overlap in the time domain, the terminal only needs to process one of the 2 PUSCHs, such as the second PUSCH.

Optionally, one of the first PUSCH and the second PUSCH may be any one of the following:

a second PUSCH; namely, post-scheduled PUSCH among the first PUSCH and the second PUSCH; in this way, since the service priority corresponding to the PUSCH scheduled later in out-of-order scheduling is generally higher, prioritizing the PUSCH scheduled later can be beneficial to ensuring reliable transmission of high priority services.

The PUSCH of the first PUSCH and the second PUSCH having the higher priority; in this way, the PUSCH with high priority can be processed preferentially, which is beneficial to ensuring the reliable transmission of the high priority service.

It should be noted that, for terminal capability 3, the terminal behavior is not changed due to BWP handover. That is, if the terminal can process 2 PUSCHs on a certain uplink BWP, the terminal can process 2 PUSCHs which are randomly scheduled in the uplink BWP on any one configured uplink BWP, and can perform out-of-order scheduling on all configured uplink BWPs.

In the case of 5) above, the terminal may process the first PUSCH and the second PUSCH simultaneously when processing the first PUSCH and the second PUSCH. Further in this case, the terminal may support both PUSCH processing capability (PUSCH processing capability) 1 and PUSCH processing capability 2 on carrier BWP. The PUSCH processing capability described above can be understood as PUSCH time capability (PUSCH timing capability).

In the case of 6) above, for an uplink BWP with a bandwidth size less than or equal to the third bandwidth threshold value, the terminal may support PUSCH processing capability 1 and PUSCH processing capability 2 simultaneously on the uplink BWP, and when out-of-order scheduling, the terminal may process only one of 2 PUSCHs scheduled out-of-order on the uplink BWP, and may choose to discard the other PUSCH.

Further, for uplink BWP with bandwidth size larger than the third bandwidth threshold, the terminal supports only one PUSCH processing capability on the uplink BWP, and when out-of-order scheduling, the terminal processes only one of 2 PUSCHs scheduled out-of-order on the uplink BWP, and optionally discards the other PUSCH. And when the terminal supports only one PUSCH processing capability, it can be divided into the following two cases:

case one: supporting PUSCH processing capability 1

In this case, if the first PUSCH has no corresponding additional DMRS, out-of-order scheduling is not allowed. Or if the first PUSCH has an additional DMRS and the second PUSCH has no additional DMRS, the out-of-order scheduling is allowed, and at this time, the terminal processes only one of the first PUSCH and the second PUSCH, and may choose to discard the other PUSCH.

And a second case: supporting PUSCH processing capability 2

In this case, out-of-order scheduling is allowed, the terminal processes only one of the first PUSCH and the second PUSCH, optionally discarding the other PUSCH.

Terminal capability 4:

wherein, the terminal capability 4 is a capability of PUSCH out-of-order scheduling supported by a terminal, and the terminal capability 4 may include:

7) If the bandwidth size of the activated uplink BWP on one carrier is smaller than or equal to the fourth bandwidth threshold value, the terminal processes the third PUSCH and the fourth PUSCH on the activated uplink BWP; wherein the third PUSCH and the fourth PUSCH do not overlap in the time domain;

8) Or if the bandwidth size of the activated uplink BWP is greater than the fourth bandwidth threshold, the terminal processes (such as processes only) one of the third PUSCH and the fourth PUSCH on the activated uplink BWP; and for another unprocessed PUSCH, the terminal may choose to discard; this PUSCH processing may be understood as preparing PUSCH data, whereas after the preparation is completed, a corresponding PUSCH transmission may be performed.

Wherein the third PUSCH and the fourth PUSCH are scheduled out-of-order in the activated uplink BWP, and the scheduling time of the third PUSCH is earlier than the scheduling time of the fourth PUSCH. The scheduling time of the third PUSCH may be understood as: and sending the time of the scheduling grant of the third PUSCH. The scheduling time of the second PUSCH may be understood as: and sending the scheduling grant time of the fourth PUSCH.

Alternatively, the third PUSCH and the fourth PUSCH described above may overlap in the time domain. And when the 2 PUSCHs overlap in the time domain, the terminal only needs to process one of the 2 PUSCHs, such as the fourth PUSCH.

Optionally, one of the third PUSCH and the fourth PUSCH may be any one of the following:

a fourth PUSCH; namely, post-scheduled PUSCHs in the third PUSCH and the fourth PUSCH; in this way, the service priority corresponding to the PUSCH scheduled later during out-of-order scheduling is generally higher, so that the PUSCH scheduled later is processed preferentially, which can be beneficial to ensuring the reliable transmission of the high-priority service;

the PUSCH of the third PUSCH and the fourth PUSCH having the highest priority; in this way, the PUSCH with high priority can be processed preferentially, which is beneficial to ensuring the reliable transmission of the high priority service.

It should be noted that, for the terminal capability 4, the terminal behavior may change due to BWP handover. That is, if the bandwidth size of the switched uplink BWP (i.e., the activated uplink BWP) is changed from being less than or equal to the fourth bandwidth threshold value to being greater than the fourth bandwidth threshold value, the terminal may be changed from being able to process 2 PUSCHs to being unable to process 2 PUSCHs. For uplink BWP with bandwidth size smaller than or equal to the fourth bandwidth threshold value, out-of-order scheduling can be performed on the uplink BWP; and for uplink BWP with bandwidth size greater than the fourth bandwidth threshold value, out-of-order scheduling cannot be performed thereon.

In the case of 7) above, the terminal may process the third PUSCH and the fourth PUSCH simultaneously when processing the third PUSCH and the fourth PUSCH. Further in this case, the terminal may support both PUSCH processing capability 1 and PUSCH processing capability 2 on the activated uplink BWP. The PUSCH processing capability described above may be understood as PUSCH time capability.

In the case of 8), for the activated uplink BWP with the bandwidth size smaller than or equal to the fourth bandwidth threshold value, the terminal may support PUSCH processing capability 1 and PUSCH processing capability 2 simultaneously on the uplink BWP, and when out-of-order scheduling, the terminal processes only one of 2 PUSCHs scheduled out-of-order on the uplink BWP, optionally discarding the other PUSCH.

Further, for the activated uplink BWP with the bandwidth size larger than the fourth bandwidth threshold, the terminal supports only one PUSCH processing capability on the uplink BWP, and when in out-of-order scheduling, the terminal processes only one of 2 PUSCHs scheduled out-of-order on the uplink BWP, and optionally discards the other PUSCH. And when the terminal supports only one PUSCH processing capability, it can be divided into the following two cases:

case one: supporting PUSCH processing capability 1

In this case, if the third PUSCH has no corresponding additional DMRS, out-of-order scheduling is not allowed. Or if the third PUSCH has an additional DMRS and the fourth PUSCH has no additional DMRS, allowing out-of-order scheduling, and at this time, the terminal only processes one of the third PUSCH and the fourth PUSCH, and optionally discards the other PUSCH.

And a second case: supporting PUSCH processing capability 2

In this case, out-of-order scheduling is allowed, the terminal processes only one of the third PUSCH and the fourth PUSCH, optionally discarding the other PUSCH.

Note that, the PUSCH processing capability 1 described above can be seen from the following table 3, and table 3 is the PUSCH preparation time (PUSCH preparation time for PUSCH timing capability 1) for the PUSCH time capability 1. The PUSCH processing capability 2 described above can be seen as shown in table 4 below, table 4 being PUSCH preparation time (PUSCH preparation time for PUSCH timing capability 2) for PUSCH time capability 2.

TABLE 3 Table 3

μ	PUSCH preparation time N ₂ [ symbol ]]
		0	10
1	12
		2	23
3	36

TABLE 4 Table 4

μ	PUSCH preparation time N ₂ [ symbol ]]
		0	5
1	5.5
		2	11for frequency range 1

It can be understood that the first bandwidth threshold value, the second bandwidth threshold value, the third bandwidth threshold value and the fourth bandwidth threshold value may be the same or different, which is not limited by the embodiment of the present invention according to the actual situation.

Referring to fig. 4, fig. 4 is a flowchart of an information receiving method according to an embodiment of the present invention, where the method is applied to a network device, as shown in fig. 4, and the method includes the following steps:

step 401: indication information is received from the terminal.

The indication information indicates the capability of the terminal for supporting out-of-order scheduling of the physical shared channel and a bandwidth threshold value; the bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target BWP, and the bandwidth size of the target BWP is less than or equal to the bandwidth threshold value.

In the embodiment of the invention, the network equipment can acquire the capability of the terminal, so that when the out-of-order scheduling is carried out for a plurality of mixed services, the scheduling can be carried out based on the capability of the terminal and actual requirements, the reliable transmission of high-priority services such as URLLC services is ensured, and the great influence on other services is avoided.

The foregoing embodiments are used for explaining the terminal capability reporting method and the information receiving method of the present invention, and the terminal and the network device of the present invention will be explained with reference to the embodiments and the accompanying drawings.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 5, the terminal 50 includes:

a sending module 51, configured to send indication information to a network device;

The terminal of the embodiment of the invention can report the capability to the network equipment, so that the network equipment can schedule based on the capability of the terminal and actual requirements when carrying out disorder scheduling on various mixed services, ensure the reliable transmission of high-priority services and avoid great influence on other services.

In an embodiment of the present invention, optionally, the physical shared channel includes at least one of the following:

PDSCH；

PUSCH。

optionally, the capability of PDSCH out-of-order scheduling supported by the terminal includes:

if the bandwidth size of the downlink BWP configured on one carrier is smaller than or equal to a first bandwidth threshold value, the terminal processes the first PDSCH and the second PDSCH on the carrier;

or if the bandwidth size of any one of the configured downlink BWP is greater than the first bandwidth threshold, the terminal processes one of the first PDSCH and the second PDSCH on the carrier;

wherein the first PDSCH and the second PDSCH are scheduled out of order in one downlink BWP, and the scheduling time of the first PDSCH is earlier than the scheduling time of the second PDSCH.

Optionally, one of the first PDSCH and the second PDSCH is any one of the following:

the second PDSCH;

PDSCH of the first PDSCH and the second PDSCH having a high priority.

if the bandwidth size of the activated downlink BWP on one carrier is smaller than or equal to the second bandwidth threshold value, the terminal processes the third PDSCH and the fourth PDSCH on the activated downlink BWP;

Or if the bandwidth size of the activated downlink BWP is greater than the second bandwidth threshold value, the terminal processes one of the third PDSCH and the fourth PDSCH on the activated downlink BWP;

wherein the third PDSCH and the fourth PDSCH are out-of-order scheduled in the activated downlink BWP, and the scheduling time of the third PDSCH is earlier than the scheduling time of the fourth PDSCH.

Optionally, one of the third PDSCH and the fourth PDSCH is any one of the following:

the fourth PDSCH;

PDSCH of the third PDSCH and the fourth PDSCH with a high priority.

Optionally, the capability of PUSCH out-of-order scheduling supported by the terminal includes:

if the bandwidth size of the uplink BWP configured on one carrier is smaller than or equal to a third bandwidth threshold value, the terminal processes the first PUSCH and the second PUSCH on the carrier;

or if the bandwidth size of any one of the configured uplink BWP is greater than the third bandwidth threshold, the terminal processes one of the first PUSCH and the second PUSCH on the carrier;

the first PUSCH and the second PUSCH are scheduled out of order in one uplink BWP, and the scheduling time of the first PUSCH is earlier than the scheduling time of the second PUSCH.

Optionally, one of the first PUSCH and the second PUSCH is any one of the following:

the second PUSCH;

and the higher-priority PUSCH in the first PUSCH and the second PUSCH.

if the bandwidth size of the activated uplink BWP on one carrier is smaller than or equal to the fourth bandwidth threshold value, the terminal processes the third PUSCH and the fourth PUSCH on the activated uplink BWP;

or if the bandwidth size of the activated uplink BWP is greater than the fourth bandwidth threshold, the terminal processes one of the third PUSCH and the fourth PUSCH on the activated uplink BWP;

wherein the third PUSCH and the fourth PUSCH are scheduled out of order in the activated uplink BWP, and the scheduling time of the third PUSCH is earlier than the scheduling time of the fourth PUSCH.

Optionally, one of the third PUSCH and the fourth PUSCH is any one of the following:

the fourth PUSCH;

and the higher-priority PUSCH in the third PUSCH and the fourth PUSCH.

Referring to fig. 6, fig. 6 is a schematic structural diagram of a network device according to an embodiment of the present invention, as shown in fig. 6, the network device 60 includes:

A receiving module 61 for receiving the instruction information from the terminal;

The network equipment of the embodiment of the invention can acquire the reporting capability of the terminal, so that when the mixed services are subjected to out-of-order scheduling, the scheduling can be performed based on the terminal capability and actual requirements, the reliable transmission of the high-priority service is ensured, and the large influence on other services is avoided.

The embodiment of the invention also provides a terminal, which comprises a processor and a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program realizes each process of the terminal capability reporting method embodiment when being executed by the processor, and can achieve the same technical effect, and the repetition is avoided, so that the description is omitted.

Specifically, fig. 7 is a schematic hardware structure of a terminal for implementing various embodiments of the present invention, where a terminal 700 includes, but is not limited to: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, processor 710, and power supply 711. It will be appreciated by those skilled in the art that the terminal structure shown in fig. 7 is not limiting of the terminal and that the terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. In the embodiment of the invention, the terminal comprises, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.

The radio frequency unit 701 is configured to send indication information to a network device; the indication information indicates the capability of the terminal for supporting the physical shared channel out-of-order scheduling and a bandwidth threshold value; the bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target BWP, and the bandwidth size of the target BWP is smaller than or equal to the bandwidth threshold value.

The terminal 700 of the embodiment of the present invention may implement each process implemented in the embodiment of the method shown in fig. 3 and achieve the same beneficial effects, and in order to avoid repetition, the description is omitted here.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 701 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communication, specifically, receiving downlink data from a base station, and then processing the received downlink data by the processor 710; and, the uplink data is transmitted to the base station. Typically, the radio unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio unit 701 may also communicate with networks and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user through the network module 702, such as helping the user to send and receive e-mail, browse web pages, access streaming media, etc.

The audio output unit 703 may convert audio data received by the radio frequency unit 701 or the network module 702 or stored in the memory 709 into an audio signal and output as sound. Also, the audio output unit 703 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the terminal 700. The audio output unit 703 includes a speaker, a buzzer, a receiver, and the like.

The input unit 704 is used for receiving an audio or video signal. The input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, the graphics processor 7041 processing image data of still pictures or video obtained by an image capturing apparatus (such as a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 706. The image frames processed by the graphics processor 7041 may be stored in memory 709 (or other storage medium) or transmitted via the radio unit 701 or the network module 702. The microphone 7042 can receive sound, and can process such sound into audio data. The processed audio data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 701 in the case of a telephone call mode.

The terminal 700 also includes at least one sensor 705, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 7061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 7061 and/or the backlight when the terminal 700 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when the accelerometer sensor is stationary, and can be used for recognizing the terminal gesture (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; the sensor 705 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., and will not be described again here.

The display unit 706 is used to display information input by a user or information provided to the user. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 707 is operable to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 7071 or thereabout using any suitable object or accessory such as a finger, stylus, etc.). The touch panel 7071 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 710, and receives and executes commands sent from the processor 710. In addition, the touch panel 7071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 707 may include other input devices 7072 in addition to the touch panel 7071. In particular, other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

Further, the touch panel 7071 may be overlaid on the display panel 7061, and when the touch panel 7071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 710 to determine a type of a touch event, and then the processor 710 provides a corresponding visual output on the display panel 7061 according to the type of the touch event. Although in fig. 7, the touch panel 7071 and the display panel 7061 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 7071 and the display panel 7061 may be integrated to implement the input and output functions of the terminal, which is not limited herein.

The interface unit 708 is an interface to which an external device is connected to the terminal 700. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 708 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 700 or may be used to transmit data between the terminal 700 and an external device.

The memory 709 may be used to store software programs as well as various data. The memory 709 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 709 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 710 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 709 and calling data stored in the memory 709, thereby performing overall monitoring of the terminal. Processor 710 may include one or more processing units; preferably, the processor 710 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 710.

The terminal 700 may also include a power supply 711 (e.g., a battery) for powering the various components, and the power supply 711 may preferably be logically coupled to the processor 710 via a power management system, such as to perform charge, discharge, and power management functions via the power management system.

In addition, the terminal 700 may further include some functional modules, which are not shown, and are not described herein.

The embodiment of the invention also provides a network device, which comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program realizes the processes of the information receiving method embodiment applied to the network device when being executed by the processor, can achieve the same technical effects, and is not repeated here.

Specifically, fig. 8 is a schematic hardware structure of a network device implementing various embodiments of the present invention, where the network device 80 includes, but is not limited to: bus 81, transceiver 82, antenna 83, bus interface 84, processor 85 and memory 86.

In an embodiment of the present invention, the network device 80 further includes: a computer program stored on the memory 86 and executable on the processor 85, which when executed by the processor 85 performs the steps of:

Receiving indication information from a terminal; the indication information indicates the capability of the terminal for supporting the physical shared channel out-of-order scheduling and a bandwidth threshold value; the bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target BWP, and the bandwidth size of the target BWP is smaller than or equal to the bandwidth threshold value _。

A transceiver 82 for receiving and transmitting data under the control of a processor 85.

The network device 80 of the embodiment of the present invention may implement each process implemented in the method embodiment shown in the foregoing figures, and achieve the same beneficial effects, and in order to avoid repetition, a detailed description is omitted here.

In fig. 8, a bus architecture (represented by bus 81), the bus 81 may comprise any number of interconnected buses and bridges, with the bus 81 linking together various circuits, including one or more processors, represented by processor 85, and memory, represented by memory 86. The bus 81 may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. Bus interface 84 provides an interface between bus 81 and transceiver 82. The transceiver 82 may be one element or may be a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 85 is transmitted over a wireless medium via the antenna 83, and further, the antenna 83 receives the data and transmits the data to the processor 85.

The processor 85 is responsible for managing the bus 81 and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 86 may be used to store data used by processor 85 in performing operations.

Alternatively, the processor 85 may be CPU, ASIC, FPGA or a CPLD.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements each process of the terminal capability reporting method embodiment, or each process of the information receiving method embodiment, and can achieve the same technical effect, and in order to avoid repetition, a detailed description is omitted herein. The computer readable storage medium is, for example, read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.

The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.

Claims

1. The terminal capability reporting method is applied to a terminal and is characterized by comprising the following steps:

transmitting indication information to the network equipment;

the indication information indicates the capability of the terminal for supporting out-of-order scheduling of the physical shared channel and a bandwidth threshold value; the bandwidth threshold value indicates that the terminal can process at least 2 out-of-order scheduled physical shared channels in a target bandwidth portion BWP, and the bandwidth size of the target BWP is less than or equal to the bandwidth threshold value.

2. The reporting method of claim 1, wherein the physical shared channel comprises at least one of:

a physical downlink shared channel PDSCH;

physical uplink shared channel PUSCH.

3. The reporting method of claim 2, wherein the capability of PDSCH out-of-order scheduling supported by the terminal includes:

4. The reporting method of claim 3, wherein one of the first PDSCH and the second PDSCH is any one of:

the second PDSCH;

PDSCH of the first PDSCH and the second PDSCH having a high priority.

5. The reporting method of claim 2, wherein the capability of PDSCH out-of-order scheduling supported by the terminal includes:

6. The reporting method of claim 5, wherein one of the third PDSCH and the fourth PDSCH is any one of:

the fourth PDSCH;

PDSCH of the third PDSCH and the fourth PDSCH with a high priority.

7. The reporting method of claim 2, wherein the capability of PUSCH out-of-order scheduling supported by the terminal includes:

8. The reporting method of claim 7, wherein one of the first PUSCH and the second PUSCH is any one of:

the second PUSCH;

And the higher-priority PUSCH in the first PUSCH and the second PUSCH.

9. The reporting method of claim 2, wherein the capability of PUSCH out-of-order scheduling supported by the terminal includes:

10. The reporting method of claim 9, wherein one of the third PUSCH and the fourth PUSCH is any one of:

the fourth PUSCH;

and the higher-priority PUSCH in the third PUSCH and the fourth PUSCH.

11. An information receiving method applied to a network device, comprising:

receiving indication information from a terminal;

12. A terminal, comprising:

13. The terminal of claim 12, wherein the capability of PDSCH out-of-order scheduling supported by the terminal comprises:

14. The terminal of claim 12, wherein the capability of PDSCH out-of-order scheduling supported by the terminal comprises:

15. The terminal of claim 12, wherein the capability of PUSCH out-of-order scheduling supported by the terminal comprises:

16. The terminal of claim 12, wherein the capability of PUSCH out-of-order scheduling supported by the terminal comprises:

the capability of the PUSCH out-of-order scheduling supported by the terminal includes:

17. A network device, comprising:

18. A terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the computer program when executed by the processor implements the steps of the terminal capability reporting method according to any one of claims 1 to 10.

19. A network device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the computer program is executed by the processor to implement the steps of the information receiving method of claim 11.

20. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the terminal capability reporting method according to any one of claims 1 to 10, or the steps of the information receiving method according to claim 11.