Patent Application
20250227740
This application pertains to the field of communication technologies, and particularly relates to a capability indication method, a terminal, and a non-transitory medium.
Currently, in a new radio (NR) system, if a network-side device does not configure a dedicated physical uplink control channel (PUCCH) resource for a terminal, the terminal may transmit data to the network-side device with a common PUCCH resource for communication with the network-side device.
However, since the network-side device may not be able to determine a capability of the terminal to support a transmission function (such as a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, and a capability to support frequency hopping between two adjacent repetitions), the network-side device may be unable to configure the transmission function for the terminal. As a result, the data transmission with the common PUCCH resource between the terminal and the network-side device may fail.
Consequently, communication performance is degraded.
A first aspect provides a capability indication method, applied to a terminal. The method includes: transmitting, by a terminal, random access information on a random access resource. A target capability of the terminal is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions.
A second aspect provides a capability indication apparatus. The capability indication apparatus includes a transmission module. The transmission module is configured to transmit random access information on a random access resource. A target capability of the terminal is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions.
A third aspect provides a terminal. The terminal includes a processor and a memory. The memory stores a program or instructions capable of running on the processor. When the program or instructions are executed by the processor, the steps of the method according to the first aspect are implemented.
A fourth aspect provides a terminal, including a processor and a communication interface. The communication interface is configured to transmit random access information on a random access resource. A target capability of the terminal is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions.
A fifth aspect provides a capability indication system, including a terminal and a network-side device. The terminal may be configured to execute the steps of the method according to the first aspect.
A sixth aspect provides a non-transitory readable storage medium. The non-transitory readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, the steps of the method according to the first aspect are implemented.
A seventh aspect provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instructions, to implement the steps of the method according to the first aspect.
An eighth aspect provides a computer program/program product. The computer program/program product is stored in a non-transitory storage medium. The computer program/program product is executed by at least one processor, to implement the steps of the method according to the first aspect.
The following clearly describes technical solutions in embodiments of this application with reference to the accompanying drawings in the embodiments of this application. It is clear that the described embodiments are only some rather than all embodiments of this application. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of this application shall fall within the protection scope of this application.
The following describes terms used in the embodiments of this application.
In an NR system, a terminal may feedback uplink control information (UCI) to a network-side device via a PUCCH. A PUCCH resource is configured by the network-side device.
Typically, PUCCH resources are classified into common PUCCH resources and dedicated PUCCH resources.
The common PUCCH resource is a PUCCH resource used before configuration of a dedicated PUCCH resource by the network-side device. The common PUCCH resource is a configured PUCCH resource shared by a plurality of users or a common PUCCH resource configured for each serving cell; and a PUCCH on the common PUCCH resource may be referred to as a common PUCCH.
A dedicated PUCCH resource is a PUCCH resource dedicatedly configured by the network-side device for a terminal after a radio resource control (RRC) connection is established between the terminal and the network-side device.
Currently, a new terminal type, namely, Redcap terminal, is proposed in standards of the 3rd generation partnership project (3GPP). Typically, the Redcap terminal meets the following requirements: low costs, low complexity, a certain degree of coverage enhancement, and power saving.
Usually, a Redcap terminal may have single receiving antenna or two receiving antennas.
The terms “first”, “second”, and the like in this specification and claims of this application are used to distinguish between similar objects rather than to describe a specific order or sequence. It should be understood that terms used in this way are interchangeable in appropriate circumstances so that the embodiments of this application can be implemented in other orders than the order illustrated or described herein. In addition, “first” and “second” are usually used to distinguish objects of a same type, and do not restrict a quantity of objects. For example, there may be one or a plurality of first objects. In addition, “and/or” in the specification and claims represents at least one of connected objects, and the character “/” usually indicates an “or” relationship between associated objects.
It should be noted that technologies described in the embodiments of this application are not limited to a long term evolution (LTE)/LTE-Advanced (LTE-A) system, and may also be applied to other wireless communication systems, for example, code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and other systems. The terms “system” and “network” in the embodiments of this application are often used interchangeably. The technology described herein may be used in the foregoing systems and radio technologies, and may be used in other systems and radio technologies. In the following descriptions, a new radio (NR) system is described for an illustration purpose, and NR terms are used in most of the following descriptions, although these technologies may also be applied to other applications than an NR system application, for example, the 6th generation (6G) communication system.
Currently, if the network-side device does not configure a dedicated PUCCH resource for the terminal, the terminal can only use a common PUCCH resource. However, in some scenarios (such as a non-terrestrial network (NTN)), using a PUCCH on which transmission is performed with a common PUCCH resource (for example, used for Msg 4 hybrid automatic repeat request (HARQ)) leads to substandard receiving performance, resulting in failure in random access. Consequently, all channels for services (such as voice over new radio (VoNR) and low-speed data transmission) cannot be used for transmission, leading to the failure in the data transmission with the common PUCCH resource between the terminal and the network-side device. Usually, to address the above issue, the network-side device can configure a transmission function for the terminal (such as PUCCH repetition, inter-slot frequency hopping, and frequency hopping between two adjacent repetitions), to prevent the situation that all channels for services cannot be used for transmission. However, since the network-side device may not be able to determine a capability of the terminal to support a transmission function (such as a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, and a capability to support frequency hopping between two adjacent repetitions), the network-side device may be unable to configure the transmission function for the terminal. As a result, the data transmission with the common PUCCH resource between the terminal and the network-side device may still fail
However, in this embodiment of this application, the terminal may transmit random access information on a random access resource, and the capability of the terminal to support a transmission function is at least indicated by at least one of the random access resource or the random access information. Therefore, the network-side device can determine the capability to support a transmission function. This can avoid the situation that the network-side device may be unable to configure the foregoing transmission function for the terminal. In this way, the failure in the data transmission with the common PUCCH resource between the terminal and the network-side device can be avoided.
The following describes in detail a capability indication method and apparatus, a terminal, and a non-transitory medium provided in embodiments of this application through some embodiments and application scenarios thereof with reference to accompanying drawings.
Step 101: A terminal transmits random access information on a random access resource.
In this embodiment of this application, a target capability of the terminal is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions.
Optionally, in this embodiment of this application, when no radio resource control (RRC) connection is established between the terminal and the network-side device, or when no dedicated PUCCH resource is configured for the terminal by the network-side device, the terminal may transmit random access information on the random access resource, to indicate the target capability to the network-side device.
Optionally, in this embodiment of this application, the target capability is a capability of the terminal to perform transmission with a common PUCCH resource; and the target capability may be one set of capabilities or a plurality of sets of capabilities.
Optionally, in this embodiment of this application, the target capability is provided as a plurality of sets of target capabilities, where each set of the target capabilities are capabilities corresponding to one type of user equipment (UE) for the terminal.
Herein, one type of UE may be any of the following: RedCap UE or non-RedCap UE.
Each set of target capabilities may be capabilities of one type of UE for the terminal to use a common PUCCH resource for transmission.
It can be understood that capabilities of different types of UE to use a common PUCCH resource for PUCCH repetition, inter-slot frequency hopping, and frequency hopping between two adjacent repetitions can be reported independently.
The capability to support PUCCH repetition may be a capability to perform PUCCH repetition with a common PUCCH resource. The capability to support PUCCH repetition may indicate support of PUCCH repetition with a common PUCCH resource or nonsupport of PUCCH repetition with a common PUCCH resource.
Herein, the PUCCH repetition may be PUCCH repetition for feedback of Msg 4 HARQ or another PUCCH repetition performed in a case that the terminal cannot access a dedicated PUCCH resource. The PUCCH repetition may be inter-slot repetition, intra-slot repetition, or cross-slot repetition.
Herein, a PUCCH format for transmission in the PUCCH repetition may be at least one of the following: a PUCCH format 1 or a PUCCH format 0. Certainly, the PUCCH format may alternatively be another PUCCH format. This is not limited in this embodiment of this application.
Optionally, in this embodiment of this application, in a case that the target capability includes the capability to support PUCCH repetition, the target capability includes at least one of the following:
For example, it is assumed that the target capability is two sets of capabilities, such as capability 1 and capability 2. The capability 1 may include the capability to support dynamic PUCCH repetition, and the capability 2 may include the capability to support semi-static PUCCH repetition. It can be understood that the capability to support dynamic PUCCH repetition and the capability to support semi-static PUCCH repetition may be two independent capabilities.
For another example, the target capability is one set of capabilities, for example, capability 1. The capability 1 may include the capability to support dynamic PUCCH repetition and the capability to support semi-static PUCCH repetition. It can be understood that the capability to support dynamic PUCCH repetition and the capability to support semi-static PUCCH repetition may alternatively be one capability.
The capability to support inter-slot frequency hopping maybe a capability to support inter-slot frequency hopping with a common PUCCH resource. The capability to support inter-slot frequency hopping may indicate support of inter-slot frequency hopping with a common PUCCH resource or nonsupport of inter-slot frequency hopping with a common PUCCH resource.
The capability to support frequency hopping between two adjacent repetitions may be a capability to support frequency hopping between two adjacent repetitions with a common PUCCH resource. The capability to support frequency hopping between two adjacent repetitions may indicate support of frequency hopping between two adjacent repetitions with a common PUCCH resource or nonsupport of frequency hopping between two adjacent repetitions with a common PUCCH resource.
The time unit may be any of the following: a system frame, a slot, a mini-slot, or the like.
Optionally, in this embodiment of this application, the random access resource may be a common PUCCH resource.
Optionally, in this embodiment of this application, the random access resource includes at least one of the following:
The PRACH resource includes at least one of the following:
For example, it is assumed that the target capability includes the capability to support PUCCH repetition, and the PRACH resource includes the PRACH time domain resource. If the terminal supports PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on a PRACH time domain resource 1, to indicate to the network-side device that the terminal supports PUCCH repetition with a common PUCCH resource; or if the terminal does not support PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on a PRACH time domain resource 2, to indicate to the network-side device that the terminal does not support PUCCH repetition with a common PUCCH resource.
It should be noted that for explanation regarding indication of the target capability with another resource in the PRACH resource (that is, a PRACH frequency domain resource, and/or a PRACH sequence, and/or a scrambling sequence of a PRACH sequence, and/or a PRACH format), reference can be made to the detailed descriptions of indicating the target capability with the PRACH time domain resource. In this embodiment of this application, details are not described herein.
Herein, the first PRACH resource indicates whether the terminal performs PRACH repetition.
For example, it is assumed that the target capability includes the capability to support PUCCH repetition. If the terminal performs PRACH repetition, it may be considered that the terminal supports PUCCH repetition with a common PUCCH resource.
It should be noted that for explanation regarding indication of another capability with a PRACH resource (for example, the capability to support inter-slot frequency hopping and/or the capability to support frequency hopping between two adjacent repetitions), reference can be made to the detailed descriptions of indicating the capability to support PUCCH repetition with a PRACH resource. In this embodiment of this application, details are not described herein.
The Msg A PUSCH resource includes at least one of the following:
It can be understood that the target capability may be implicitly indicated by the Msg A PUSCH resource.
For example, it is assumed that the target capability includes the capability to support PUCCH repetition, and the Msg A PUSCH resource includes the Msg A PUSCH group. During 2-step random access (2-step RACH), if the terminal supports PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on an Msg A PUSCH group A, to indicate to the network-side device that the terminal supports PUCCH repetition with a common PUCCH resource; or if the terminal does not support PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on an Msg A PUSCH group B, to indicate to the network-side device that the terminal does not support PUCCH repetition with a common PUCCH resource.
It should be noted that for explanation regarding indication of the target capability with another resource in the Msg A PUSCH resource (that is, an Msg A PUSCH frequency domain resource, and/or an Msg A PUSCH DMRS resource, and/or an Msg A PUSCH group), reference can be made to the detailed descriptions of indicating the target capability with the Msg A PUSCH time domain resource. In this embodiment of this application, details are not described herein.
Herein, the first Msg A PUSCH resource indicates whether the terminal performs Msg A PUSCH repetition.
It should be noted that for explanation regarding indication of another capability with the Msg A PUSCH resource (that is, the capability to support inter-slot frequency hopping and/or the capability to support frequency hopping between two adjacent repetitions), reference can be made to the detailed descriptions of indicating the capability to support PUCCH repetition with an Msg A PUSCH resource. In this embodiment of this application, details are not described herein.
The Msg A resource includes at least one of the following:
For example, it is assumed that the target capability includes the capability to support PUCCH repetition, and the Msg A resource includes the Msg A time domain resource. During 2-step RACH, if the terminal supports PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on an Msg A time domain resource 1, to indicate to the network-side device that the terminal supports PUCCH repetition with a common PUCCH resource; or if the terminal does not support PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on an Msg A time domain resource 2, to indicate to the network-side device that the terminal does not support PUCCH repetition with a common PUCCH resource.
It should be noted that for explanation regarding indication of another capability with the Msg A resource (that is, the capability to support inter-slot frequency hopping and/or the capability to support frequency hopping between two adjacent repetitions), reference can be made to the detailed descriptions of indicating the capability to support PUCCH repetition with an Msg A resource. In this embodiment of this application, details are not described herein.
The Msg 3 PUSCH resource includes at least one of the following:
For example, it is assumed that the target capability includes the capability to support PUCCH repetition, and the Msg 3 PUSCH resource includes the Msg 3 PUSCH time domain resource. During 4-step random access (4-step RACH), if the terminal supports PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on an Msg 3 PUSCH time domain resource 1, to indicate to the network-side device that the terminal supports PUCCH repetition with a common PUCCH resource; or if the terminal does not support PUCCH repetition with a common PUCCH resource, the terminal may transmit the random access information on an Msg 3 PUSCH time domain resource 2, to indicate to the network-side device that the terminal does not support PUCCH repetition with a common PUCCH resource.
Herein, the first Msg 3 PUSCH resource indicates whether the terminal supports Msg 3 PUSCH repetition.
It should be noted that for explanation regarding indication of another capability with the Msg 3 PUSCH resource (that is, the capability to support inter-slot frequency hopping and/or the capability to support frequency hopping between two adjacent repetitions), reference can be made to the detailed descriptions of indicating the capability to support PUCCH repetition with an Msg 3 PUSCH resource. In this embodiment of this application, details are not described herein.
Optionally, in this embodiment of this application, the random access information includes at least one of the following:
It can be understood that the target capability may be explicitly indicated by the information carried by the Msg A PUSCH, and/or explicitly indicated by the information carried by the Msg 3 PUSCH.
In the capability indication method provided in this embodiment of this application, the terminal may transmit the random access information on the random access resource, and the target capability of the terminal is at least indicated by at least one of the random access resource or the random access information, so that the network-side device can determine the target capability, where the target capability includes at least one of the capability to support PUCCH repetition, the capability to support inter-slot frequency hopping, or the capability to support frequency hopping between two adjacent repetitions. The terminal may at least indicate the target capability of the terminal to the network-side device with at least one of the random access resource or the random access information, so that the situation that the network-side device is unable to configure a transmission function for the terminal (that is, PUCCH repetition, inter-slot frequency hopping, and frequency hopping between two adjacent repetitions) can be avoided. This prevents failure in data transmission with the common PUCCH resource between the terminal and the network-side device, thereby improving communication performance.
Because the terminal can indicate the target capability of the terminal to the network-side device with at least one of the random access resource or the random access information, the reliability of the PUCCH repetition on the common PUCCH resource is improved, ensuring a success rate for HARQ feedback before establishment of the RRC connection.
Certainly, in a case that the target capability is provided as a plurality of sets of capabilities, each set of capabilities may include different capabilities. Each set of capabilities may be indicated by a combination of a different PRACH resource, and/or Msg A PUSCH resource, and/or Msg A resource, and/or Msg 3 PUSCH resource. Examples are given below for description.
Optionally, in this embodiment of this application, the target capability is provided as a plurality of sets of target capabilities, the random access resource is provided in plurality, and the random access information is provided in plurality, where each set of the target capabilities are at least indicated by at least one of the following: at least one of the random access resources or at least one piece of the random access information.
For example, it is assumed that the target capability includes the capability to support intra-slot PUCCH repetition and the capability to support inter-slot PUCCH repetition, and the random access resource includes a PRACH sequence. In this case, four preamble groups may be defined on each PRACH occasion. As shown in Table 1, if the terminal only supports intra-slot PUCCH repetition and does not support inter-slot PUCCH repetition, the terminal may transmit the random access information on a PRACH in group A, to indicate to the network-side device that the terminal only supports intra-slot PUCCH repetition and does not support inter-slot PUCCH repetition; if the terminal only supports inter-slot PUCCH repetition and does not support intra-slot PUCCH repetition, the terminal may transmit the random access information on a PRACH in group B, to indicate to the network-side device that the terminal only supports inter-slot PUCCH repetition and does not support intra-slot PUCCH repetition; if the terminal supports inter-slot PUCCH repetition and intra-slot PUCCH repetition, the terminal may transmit the random access information on a PRACH in group C, to indicate to the network-side device that the terminal supports inter-slot PUCCH repetition and intra-slot PUCCH repetition; and if the terminal does not support inter-slot PUCCH repetition and intra-slot PUCCH repetition, the terminal may transmit the random access information on a PRACH in group D, to indicate to the network-side device that the terminal does not support inter-slot PUCCH repetition and intra-slot PUCCH repetition.
Certainly, the terminal may also indicate the capability of the terminal to support PUCCH repetition to the network-side device, so that the network-side device can determine, based on the capability to support PUCCH repetition, the capability of the terminal to support inter-slot frequency hopping and/or the capability to support frequency hopping between two adjacent repetitions. Examples are given below for description.
Optionally, in this embodiment of this application, in a case that the target capability is the capability to support PUCCH repetition, a first capability of the terminal is represented by the target capability. The first capability includes at least one of the following: the capability to support inter-slot frequency hopping or the capability to support frequency hopping between two adjacent repetitions. In a case that the capability to support PUCCH repetition indicates support of PUCCH repetition, the network-side device can determine that the terminal supports inter-slot frequency hopping and/or frequency hopping between two adjacent repetitions.
In a case that the capability to support PUCCH repetition indicates nonsupport of PUCCH repetition, the network-side device can determine that the terminal does not support inter-slot frequency hopping and/or frequency hopping between two adjacent repetitions.
It can be learned that since the terminal can report only the representation of the capability to support PUCCH repetition to the network-side device, the network-side device can determine at least one of the capability of the terminal to support inter-slot frequency hopping or the capability to support frequency hopping between two adjacent repetitions, and therefore resources for reporting the capability of the terminal can be saved.
Certainly, the network-side device may determine that the capability of the terminal to support inter-slot frequency hopping and the capability to support frequency hopping between two adjacent repetitions are mandatory. Examples are given below for description.
Optionally, in this embodiment of this application, in a case that the target capability is the capability to support PUCCH repetition, the capability of the terminal to support inter-slot frequency hopping indicates support of inter-slot frequency hopping, and the capability of the terminal to support frequency hopping between two adjacent repetitions indicates support of frequency hopping between two adjacent repetitions.
It can be understood that the network-side device may determine by default that the terminal supports inter-slot frequency hopping and/or frequency hopping between two adjacent repetitions.
In this way, it can be learned that resources for reporting the capability of the terminal can be saved because the network-side device by default determines that the terminal supports inter-slot frequency hopping and/or frequency hopping between two adjacent repetitions and the terminal does not need to report.
The capability indication method provided in this embodiment of this application may be executed by a capability indication apparatus. The capability indication apparatus provided in an embodiment of this application is described by using an example in which the capability indication method is executed by the capability indication apparatus provided in this embodiment of this application.
The transmission module 61 is configured to transmit random access information on a random access resource. A target capability of the capability indication apparatus 60 is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions.
In a possible implementation, the random access resource includes at least one of the following: a PRACH resource; an Msg A PUSCH resource; an Msg A resource; or an Msg 3 PUSCH resource.
In a possible implementation, the PRACH resource includes at least one of the following: a PRACH time domain resource; a PRACH frequency domain resource; a PRACH sequence; a scrambling sequence of a PRACH sequence; a PRACH format; or a first PRACH resource. The first PRACH resource indicates whether the capability indication apparatus 60 performs PRACH repetition.
In a possible implementation, the Msg A PUSCH resource includes at least one of the following: an Msg A PUSCH time domain resource; an Msg A PUSCH frequency domain resource; an Msg A PUSCH DMRS resource; an Msg A PUSCH group; or a first Msg A PUSCH resource. The first Msg A PUSCH resource indicates whether the capability indication apparatus 60 performs Msg A PUSCH repetition.
In a possible implementation, the Msg A resource includes at least one of the following: an Msg A time domain resource; an Msg A frequency domain resource; or an Msg A DMRS resource.
In a possible implementation, the Msg 3 PUSCH resource includes at least one of the following: an Msg 3 PUSCH time domain resource; an Msg 3 PUSCH frequency domain resource; an Msg 3 PUSCH DMRS resource; an Msg 3 PUSCH payload size; or a first Msg 3 PUSCH resource. The first Msg 3 PUSCH resource indicates whether the capability indication apparatus 60 performs Msg 3 PUSCH repetition.
In a possible implementation, the random access information includes at least one of the following: information carried by an Msg A PUSCH; or information carried by an Msg 3 PUSCH.
In a possible implementation, in a case that the target capability includes the capability to support PUCCH repetition, the target capability includes at least one of the following: a capability to support dynamic PUCCH repetition; a capability to support semi-static PUCCH repetition; a capability to support intra-slot PUCCH repetition; a capability to support inter-slot PUCCH repetition; a capability to support single-TRP PUCCH repetition; a capability to support multi-TRP PUCCH repetition; a capability to support PUCCH repetition based on a PUCCH format; a capability to support PUCCH repetition based on a PUCCH resource; a capability to support PUCCH repetition based on an available time unit; or a capability to support PUCCH repetition based on a physical time unit.
In a possible implementation, in a case that the target capability is the capability to support PUCCH repetition, a first capability of the capability indication apparatus 60 is represented by the target capability. The first capability includes at least one of the following: the capability to support inter-slot frequency hopping or the capability to support frequency hopping between two adjacent repetitions.
In a possible implementation, in a case that the target capability is the capability to support PUCCH repetition, the capability of the capability indication apparatus 60 to support inter-slot frequency hopping indicates support of inter-slot frequency hopping, and the capability of the capability indication apparatus 60 to support frequency hopping between two adjacent repetitions indicates support of frequency hopping between two adjacent repetitions.
In a possible implementation, the target capability is provided as a plurality of sets of target capabilities, where each set of the target capabilities are capabilities corresponding to one type of UE for the capability indication apparatus 60.
In a possible implementation, the target capability is provided as a plurality of sets of target capabilities, the random access resource is provided in plurality, and the random access information is provided in plurality. Each set of the target capabilities are at least indicated by at least one of the following: at least one of the random access resources or at least one piece of the random access information.
In a possible implementation, the target capability is a capability of the capability indication apparatus 60 to perform transmission with a common PUCCH resource.
For the capability indication apparatus provided in this embodiment of this application, the capability indication apparatus may at least indicate the target capability of the capability indication apparatus to the network-side device with at least one of the random access resource or the random access information, so that the situation that the network-side device is unable to configure a transmission function for the capability indication apparatus (that is, PUCCH repetition, inter-slot frequency hopping, and frequency hopping between two adjacent repetitions) can be avoided. This prevents failure in data transmission with the common PUCCH resource between the capability indication apparatus and the network-side device, thereby improving communication performance.
The capability indication apparatus in this embodiment of this application may be an electronic device such as an electronic device with an operating system, or a component in an electronic device such as an integrated circuit or chip. The electronic device may be a terminal or another device other than the terminal. For example, the terminal may include but is not limited to the types of the terminal 11 listed above, and the another device may be a server, a network attached storage (NAS), or the like. This is not limited in this embodiment of this application.
The capability indication apparatus provided in this embodiment of this application can implement the processes implemented in the method embodiment of
Optionally, in this embodiment of this application, as shown in
An embodiment of this application further provides a terminal, including a processor and a communication interface. The communication interface is configured to transmit random access information on a random access resource. A target capability of the terminal is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions. This terminal embodiment corresponds to the foregoing method embodiment on the terminal side. All processes and implementations in the foregoing method embodiment are applicable to this terminal embodiment, with the same technical effects achieved.
The terminal 100 includes but is not limited to at least part of these components: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.
Persons skilled in the art can understand that the terminal 100 may further include a power supply (such as a battery) for supplying power to the components. The power supply may be logically connected to the processor 110 through a power management system. In this way, functions such as charge management, discharge management, and power consumption management are implemented by using the power management system. The structure of the terminal shown in
It should be understood that in this embodiment of this application, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The graphics processing unit 1041 processes image data of a still picture or video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in a form of a liquid crystal display, an organic light-emitting diode, and the like. The user input unit 107 includes at least one of a touch panel 1071 or another input device 1072. The touch panel 1071 is also referred to as a touchscreen. The touch panel 1071 may include two parts: a touch detection apparatus and a touch controller. The another input device 1072 may include but is not limited to a physical keyboard, a function button (such as a volume control button or an on/off button), a trackball, a mouse, and a joystick. Details are not described herein.
In this embodiment of this application, the radio frequency unit 101 receives downlink data from a network-side device and sends the data to the processor 110 for processing; and the radio frequency unit 101 can send uplink data to the network-side device. Generally, the radio frequency unit 101 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, and a duplexer.
The memory 109 may be configured to store software programs or instructions and various data. The memory 109 may include a first storage area for storing a program or instructions and a second storage area for storing data. The first storage area may store an operating system, an application program or instructions required by at least one function (for example, sound play function or image play function), and the like. In addition, the memory 109 may include a volatile memory or a non-volatile memory, or the memory 109 may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 109 in this embodiment of this application includes but is not be limited to these memories and any other applicable types of memories.
The processor 110 may include one or more processing units. Optionally, the processor 110 may integrate an application processor and a modem processor. The application processor mainly processes operations related to an operating system, user interface, application program, and the like. The modem processor, for example, a baseband processor, mainly processes radio communication signals. It can be understood that the modem processor may alternatively be not integrated in the processor 110.
The radio frequency unit 101 is configured to transmit random access information on a random access resource.
The target capability of the terminal is at least indicated by at least one of the following: the random access resource or the random access information. The target capability includes at least one of the following: a capability to support PUCCH repetition, a capability to support inter-slot frequency hopping, or a capability to support frequency hopping between two adjacent repetitions.
For the terminal provided in this embodiment of this application, the terminal may at least indicate the target capability of the terminal to the network-side device with at least one of the random access resource or the random access information, so that the situation that the network-side device is unable to configure a transmission function for the terminal (that is, PUCCH repetition, inter-slot frequency hopping, and frequency hopping between two adjacent repetitions) can be avoided. This prevents failure in data transmission with the common PUCCH resource between the terminal and the network-side device, thereby improving communication performance.
An embodiment of this application further provides a non-transitory readable storage medium, where the non-transitory readable storage medium stores a program or instructions. When the program or the instructions are executed by a processor, the processes of the foregoing capability indication method embodiment are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein.
The processor is a processor in the terminal in the foregoing embodiment. The non-transitory readable storage medium includes a non-transitory computer-readable storage medium such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disc.
An embodiment of this application further provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instructions, so that the processes in the foregoing capability indication method embodiment are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein.
It should be understood that the chip mentioned in this embodiment of this application may also be referred to as a system-on-chip, an SoC, a system-on-a-chip, or a system on a chip, or the like.
An embodiment of this application further provides a computer program/program product. The computer program/program product is stored in a non-transitory storage medium, and the computer program/program product is executed by at least one processor, to implement the processes of the foregoing capability indication method embodiment, with the same technical effects achieved. To avoid repetition, details are not described herein.
An embodiment of this application further provides a capability indication system, including a terminal and a network-side device. The terminal may be configured to execute the steps of the foregoing capability indication method.
It should be noted that in this specification, the term “comprise”, “include”, or any other variant thereof is intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. Without more restrictions, an element preceded by the statement “includes a . . . ” does not preclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. In addition, it should be noted that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the sequence shown or discussed, and may further include performing functions at substantially the same time or in a reverse sequence according to the involved functions. For example, the described method may be performed in a sequence different from the described sequence, and steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.
According to the description of the foregoing implementations, persons skilled in the art can clearly understand that the method in the foregoing embodiment may be implemented by software in combination with a necessary general hardware platform. Certainly, the method in the foregoing embodiment may alternatively be implemented by hardware. However, in many cases, the former is a preferred implementation. Based on such an understanding, the technical solutions of the present invention essentially or the part contributing to the prior art may be implemented in a form of a computer software product. The computer software product is stored in a non-transitory storage medium (such as a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of this application.
The foregoing describes the embodiments of this application with reference to the accompanying drawings. However, this application is not limited to the foregoing embodiments. The foregoing embodiments are merely illustrative rather than restrictive. As instructed by this application, persons of ordinary skill in the art may develop many other forms without departing from essence of this application and the protection scope of the claims, and all such forms fall within the protection scope of this application.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202211177484.8 | Sep 2022 | CN | national |
This application is a Bypass Continuation Application of International Patent Application No. PCT/CN2023/120143 filed Sep. 20, 2023, and claims priority to Chinese Patent Application No. 202211177484.8 filed Sep. 26, 2022, the disclosures of which are hereby incorporated by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2023/120143 | Sep 2023 | WO |
| Child | 19091245 | US |
