Detailed Description
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
As shown in fig. 1, communication system 100 may include a terminal 110 and a network device 120. Network device 120 may communicate with terminal 110 over the air. Multi-service transmission is supported between the terminal 110 and the network device 120.
It should be understood that embodiments of the present application are illustrated by way of example only with respect to communication system 100, and embodiments of the present application are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced machine type communications (ENHANCED MACHINE-Type Communications, eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.
In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminals 110 (e.g., UEs) located within the coverage area.
The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.
Terminal 110 may be any terminal including, but not limited to, a terminal that employs a wired or wireless connection with network device 120 or other terminals.
For example, the terminal 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolution network, etc.
The terminal 110 may be used for Device-to-Device (D2D) communication.
The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (ACCESS AND Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the Core network device 130 may also be a packet Core evolution (Evolved Packet Core, EPC) device of the LTE network, for example, a session management function+a data gateway (Session Management Function +core PACKET GATEWAY, SMF +pgw-C) device of the Core network. It should be appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form new network entities by dividing the functions of the core network, which is not limited in this embodiment of the present application.
Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface.
For example, the terminal establishes an air interface connection with the access network device through an NR interface, and is used for transmitting user plane data and control plane signaling; the terminal can establish control plane signaling connection with AMF through NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), can establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with AMF through NG interface 2 (N2 for short); the UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with the data network through an NG interface 6 (N6 for short); the AMF may establish a control plane signaling connection with the SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).
Fig. 1 illustrates one base station, one core network device, and two terminals, alternatively, the wireless communication system 100 may include a plurality of base station devices and may include other numbers of terminals within the coverage area of each base station, which is not limited by the embodiment of the present application.
It should be noted that fig. 1 is only an exemplary system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that "corresponding" mentioned in the embodiments of the present application may mean that there is a direct correspondence or an indirect correspondence between the two, may mean that there is an association between the two, and may also be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other means that may be used to indicate relevant information in devices (e.g., including terminals and network devices), and the present application is not limited to the specific implementation thereof. Such as predefined may refer to what is defined in the protocol. It should be further understood that, in the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited by the present application.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.
The protocol specifies that for one downlink data transmission, its corresponding HARQ feedback information can only be sent on one determined carrier, which is either a PCell or a PUCCH SCell. Specifically, the network side issues PDSCH-ServingCellConfig configuration for each carrier through radio resource control (Radio Resource Control, RRC) signaling, and optionally, a PUCCH Cell corresponding to a physical downlink shared channel (Physical Downlink SHARED CHANNEL, PDSCH) under the carrier may be configured in PDSCH-ServingCellConfig. If the pucch-Cell IE is not configured, HARQ feedback information corresponding to the PDSCH is transmitted on the PCell; if the PUCCH-Cell IE is configured, HARQ feedback information corresponding to the PDSCH is transmitted on the configured carrier, and the carrier must be a PUCCH SCell.
Therefore, the above scheme cannot dynamically change the carrier wave for transmitting the HARQ feedback information, and only one carrier wave for transmitting the HARQ feedback information can be used fixedly in a period of time, so that the flexibility of the HARQ feedback is poor, and a plurality of problems are caused. One of the problems is listed below.
TDD systems are limited to uplink and downlink configurations, and have a problem that the delay is higher than FDD in terms of packet transmission and HARQ feedback, as shown in fig. 2. Because the current scheme only supports the transmission of the HARQ feedback information through a specific carrier, the different uplink and downlink time slot ratios between two (or more) carriers cannot be fully utilized, and HARQ advanced feedback is realized.
For this reason, the following technical solutions of the embodiments of the present application are provided. The technical scheme of the embodiment of the application provides a method for dynamically indicating carriers, which realizes flexible assignment of the carriers corresponding to HARQ feedback information at any moment.
In order to facilitate understanding of the technical solution of the embodiments of the present application, the technical solution of the present application is described in detail below through specific embodiments. The above related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.
In the technical solution of the embodiment of the present application, the description of the "carrier" may be replaced by the "cell", and similarly, the description of the "cell" may be replaced by the "carrier". The description about "carrier identification" may be replaced with "serving cell identification (ServCellIndex)", and likewise, the description about "ServCellIndex" may be replaced with carrier identification.
Fig. 3 is a flowchart illustrating a method for indicating a carrier according to an embodiment of the present application, as shown in fig. 3, where the method for indicating a carrier includes the following steps:
Step 301: the terminal determines a first carrier based on a predefined rule or an indication of a network side, and transmits a PUCCH on the first carrier, wherein the PUCCH is used for bearing HARQ feedback information corresponding to first downlink data transmission.
In the embodiment of the present application, the terminal receives downlink control information (Downlink Control Information, DCI) carrying scheduling information (e.g., time-frequency resource information, etc.) of the first downlink data transmission, where the first DCI further carries first indication information, where the first indication information is used to indicate a first time domain position of HARQ feedback information corresponding to the first downlink data transmission. In some optional embodiments, the first indication information is a PDSCH-to-harq_ feedback timing indicator field, which is used to indicate a deviation of a first time domain position of HARQ feedback information corresponding to the first downlink data transmission from a time domain position of the first downlink data transmission.
It should be appreciated that the first downlink data transmission is carried in PUSCH. The PUCCH is used to carry HARQ feedback information corresponding to the first downlink data transmission, which may also be understood that the PUCCH is used to carry HARQ feedback information corresponding to the PUSCH.
In the embodiment of the application, the terminal determines the first carrier based on a predefined rule or an indication of a network side, wherein the first carrier is a carrier used for transmitting a PUCCH, and the PUCCH is used for carrying HARQ feedback information corresponding to first downlink data transmission. Here, the first carrier may be referred to as a PUCCH cell.
How the terminal determines the first carrier is described below in connection with different schemes.
Scheme one
In the embodiment of the application, the terminal determines the first carrier based on the predefined rule.
In some alternative embodiments, the terminal checks whether there are available PUCCH resources on all carriers in a specific order; wherein, the usable PUCCH resource refers to a PUCCH resource corresponding to the first time domain position; 1) If there is a usable PUCCH resource in one carrier, the terminal determines the one carrier as a first carrier; 2) If there are a plurality of carriers and available PUCCH resources, the terminal determines one carrier from the plurality of carriers as a first carrier.
In the above solution, optionally, the terminal checks whether there are available PUCCH resources on all carriers according to a specific order, which may be implemented by: the terminal checks the PUCCH configuration of all carriers according to the sequence from small to large of the serving cell index; for each carrier, determining whether the carrier is configured with a PUCCH resource corresponding to the first time domain location based on the PUCCH configuration of the carrier.
In the above solution, optionally, the determining, by the terminal, one carrier from the plurality of carriers as the first carrier may be implemented by:
the first mode is that the terminal selects a carrier with the minimum service cell index from the plurality of carriers as a first carrier; or alternatively
Mode two), the terminal selects a carrier with the largest service cell index from the plurality of carriers as a first carrier; or alternatively
Mode three) the terminal randomly selects one carrier from the multiple carriers as a first carrier.
According to the scheme provided by the embodiment of the application, through rule setting, the terminal can flexibly select different carriers to perform HARQ feedback.
Scheme II
In the embodiment of the application, the terminal determines the first carrier based on the high-layer signaling.
In some optional embodiments, the terminal determines, based on a first mapping table configured by the network side through RRC signaling, a carrier identifier corresponding to the first time domain location, and determines a first carrier based on the carrier identifier corresponding to the first time domain location; wherein the first mapping table comprises a mapping relation between at least one time slot and carrier identification.
In the above scheme, the total number of time slots in the first mapping table is determined based on the following: mapping relation between subcarrier spacing and number of slots in a frame.
According to the scheme provided by the embodiment of the application, through high-layer signaling configuration, the terminal can flexibly select different carriers to perform HARQ feedback.
Scheme III
In the embodiment of the application, the terminal determines the first carrier based on the DCI.
In some optional embodiments, the terminal determines the first carrier based on a carrier identifier indicated by the DCI at the network side.
Scheme I) the DCI includes a first field, where the first field is used to indicate a first carrier identifier, and a carrier corresponding to the first carrier identifier is a carrier used to transmit the PUCCH.
As an example, the first field is a PUCCH carrier (PUCCH carrier) field.
Scheme II) the DCI includes a second field, where the second field is used to indicate a second carrier identifier, and a carrier corresponding to the second carrier identifier is a carrier used to transmit the PUCCH and/or a carrier used to transmit the PDCCH, where the PDCCH is used to schedule the carrier where the DCI is located.
As an example, the second field is a carrier indication (Carrier indicator) field.
Scheme II-1) in some optional embodiments, if the carrier in which the DCI is located is a PCell, the carrier corresponding to the second carrier identification indicated by the second field is a carrier used for transmitting the PUCCH.
Scheme II-2) in some optional embodiments, if the carrier in which the DCI is located is SCell, the carrier corresponding to the second carrier identifier indicated by the second field is both a carrier used for transmitting the PDCCH and a carrier used for transmitting the PUCCH.
In the above scheme, the terminal determines the use of the carrier corresponding to the second carrier identifier indicated by the second field based on the third field. As an example, the third field may be referred to as PucchOnThisCarrier field. In some optional embodiments, the third field is located in a cross-carrier scheduling configuration (CrossCarrierSchedulingConfig), and a serving cell index indicated by a scheduling cell identification field in the cross-carrier scheduling configuration corresponds to a second carrier identification indicated by the second field; or the third field is located in the DCI.
According to the scheme provided by the embodiment of the application, through DCI, the terminal can flexibly select different carriers to perform HARQ feedback.
By implementing the technical scheme of the embodiment of the application, the HARQ feedback time delay of the multi-carrier TDD system can be reduced, and the user satisfaction of the mobile network and the supporting capability of the mobile network to various industries can be improved.
Fig. 4 is a second flowchart of a method for indicating a carrier according to an embodiment of the present application, as shown in fig. 4, where the method for indicating a carrier includes the following steps:
Step 401: the network equipment indicates a first carrier to a terminal, wherein the first carrier is used for the terminal to transmit a PUCCH, and the PUCCH is used for bearing HARQ feedback information corresponding to first downlink data transmission.
In the embodiment of the present application, the network device may be a base station.
In the embodiment of the present application, the network device sends DCI to the terminal, where the DCI carries scheduling information of the first downlink data transmission, and the first DCI further carries first indication information, where the first indication information is used to indicate a first time domain position of HARQ feedback information corresponding to the first downlink data transmission. In some optional embodiments, the first indication information is a PDSCH-to-harq_ feedback timing indicator field, which is used to indicate a deviation of a first time domain position of HARQ feedback information corresponding to the first downlink data transmission from a time domain position of the first downlink data transmission.
In the embodiment of the application, the network device indicates a first carrier to the terminal, wherein the first carrier is used for the terminal to transmit a PUCCH, and the PUCCH is used for bearing HARQ feedback information corresponding to first downlink data transmission. Here, the first carrier may be referred to as a PUCCH cell.
How the network device indicates the first carrier is described below in connection with different schemes.
Scheme A
In the embodiment of the application, the network device configures a first mapping table for the terminal through RRC signaling, wherein the first mapping table is used for determining a carrier identifier corresponding to the first time domain position by the terminal, and determining a first carrier based on the carrier identifier corresponding to the first time domain position; wherein the first mapping table comprises a mapping relation between at least one time slot and carrier identification.
In the above scheme, the total number of time slots in the first mapping table is determined based on the following: mapping relation between subcarrier spacing and number of slots in a frame.
According to the scheme provided by the embodiment of the application, through high-layer signaling configuration, the terminal can flexibly select different carriers to perform HARQ feedback.
It should be noted that the scheme a in fig. 4 corresponds to the scheme two in fig. 3.
Scheme B
In the embodiment of the present application, the network device indicates, to the terminal, a carrier identifier through the DCI, where the carrier identifier is used for the terminal to determine a first carrier.
Scheme I) the DCI includes a first field, where the first field is used to indicate a first carrier identifier, and a carrier corresponding to the first carrier identifier is a carrier used to transmit the PUCCH.
As an example, the first field is a PUCCH carrier (PUCCH carrier) field.
Scheme II) the DCI includes a second field, where the second field is used to indicate a second carrier identifier, and a carrier corresponding to the second carrier identifier is a carrier used to transmit the PUCCH and/or a carrier used to transmit the PDCCH, where the PDCCH is used to schedule the carrier where the DCI is located.
As an example, the second field is a carrier indication (Carrier indicator) field.
Scheme II-1) in some optional embodiments, if the carrier in which the DCI is located is a PCell, the carrier corresponding to the second carrier identification indicated by the second field is a carrier used for transmitting the PUCCH.
Scheme II-2) in some optional embodiments, if the carrier in which the DCI is located is SCell, the carrier corresponding to the second carrier identifier indicated by the second field is both a carrier used for transmitting the PDCCH and a carrier used for transmitting the PUCCH.
Further, the network device indicates, to the terminal, the use of the carrier corresponding to the second carrier identifier indicated by the second field through a third field, for example, the third field is used to indicate that the carrier corresponding to the second carrier identifier indicated by the second field is not only a carrier used for transmitting the PDCCH, but also a carrier used for transmitting the PUCCH, or the third field is used to indicate that the carrier corresponding to the second carrier identifier indicated by the second field is only a carrier used for transmitting the PDCCH. In some optional embodiments, the third field is located in a cross-carrier scheduling configuration (CrossCarrierSchedulingConfig), and a serving cell index indicated by a scheduling cell identification field in the cross-carrier scheduling configuration corresponds to a second carrier identification indicated by the second field; or the third field is located in the DCI.
According to the scheme provided by the embodiment of the application, through DCI, the terminal can flexibly select different carriers to perform HARQ feedback.
By implementing the technical scheme of the embodiment of the application, the HARQ feedback time delay of the multi-carrier TDD system can be reduced, and the user satisfaction of the mobile network and the supporting capability of the mobile network to various industries can be improved.
It should be noted that the scheme B in fig. 4 corresponds to the scheme three in fig. 3.
The following describes the technical scheme of the embodiment of the present application with reference to specific application examples.
Application example 1
The carrier carrying the PUCCH is uniquely determined by the protocol defining a rule (i.e. a predefined rule) that is followed by both the terminal and the network.
Step 1), a terminal receives DCI for scheduling downlink data transmission (or PDSCH transmission), wherein the terminal determines a first time domain position of HARQ feedback information corresponding to the downlink data transmission through PDSCH-to-harq_ feedback timing indicator in the DCI.
Step 2), the terminal checks whether conditions for transmitting HARQ feedback information are met on all possible carriers according to a specific sequence. In a specific scheme, a terminal checks whether PUCCH resources are configured at a first time domain position or not in order of small serving cell index (ServCellIndex) and PUCCH configuration (PUCCH-Config) of each carrier.
Step 3) if there are a plurality of carriers and available PUCCH resources, then:
a) The terminal selects a carrier wave with the minimum Serv CellIndex value to transmit a PUCCH carrying HARQ feedback information; or alternatively
B) The terminal selects a carrier with the largest Serv CellIndex value to transmit a PUCCH carrying HARQ feedback information; or alternatively
C) The terminal randomly selects one carrier to transmit the PUCCH carrying the HARQ feedback information.
The proposal has the advantages that the signaling indication is not needed by the network side, and the signaling is not changed.
Application instance two
The network side configures a global mapping table through RRC signaling, and when PDSCH-to-harq_ feedback timing indicator in DCI for scheduling downlink data transmission points to a certain slot, the terminal may query the mapping table to learn the carrier that should be selected at this time. As an example, fig. 5 illustrates a mapping table, in which numerals represent corresponding carrier identifications, i.e., servCellIndex.
In particular implementations, the format of the RRC signaling may be expressed as shown in table 1 below.
TABLE 1
Fig. 6 shows a schematic diagram of selecting carriers based on a mapping table, comprising the steps of:
step 1) the terminal receives DCI on carrier 1, where the DCI is used to schedule downlink data transmission, where PDSCH-to-harq_ feedback timing indicator in the DCI indicates k1=4, and the terminal may determine that PUCCH is transmitted in the 4 th slot after the slot in which the DCI is located, where the PUCCH carries HARQ feedback information corresponding to the downlink data transmission.
And 2) the terminal checks the mapping table to obtain the servCellIndex value corresponding to the time slot at the moment as 2.
Step 3) the terminal performs PUCCH transmission on carrier 2.
In the above scheme, the total number of slots (or the length of the mapping table) in the configuration in RRC signaling should consider the following two factors: on the one hand, carriers with different subcarrier intervals are adopted, and the total time slot number in one frame is different; on the other hand, the configuration should be long enough to contain all possible slot positions to facilitate configuration. Based on this, the total number of slots configured in the above RRC signaling can be determined with reference to the mapping relationship between the subcarrier spacing and the number of slots in the frame specified in the protocol, and as an example, table 2 below gives the mapping relationship between the subcarrier spacing and the number of slots in the frame, where μ represents a parameter corresponding to the subcarrier spacing,Representing the number of slots within a frame. The total number of slots configured in RRC signaling may be 160.
TABLE 2
Application example three
When downlink data transmission is scheduled through DCI, the carrier wave carrying the PUCCH is dynamically indicated through the DCI, so that more flexible PUCCH carrier wave switching can be realized.
Scheme a
A PUCCH carrier field is added to the DCI to specify a carrier identifier (i.e., servCellIndex) corresponding to HARQ feedback information corresponding to downlink data transmission. As an example, the format of the DCI may be DCI formats 1_1, 1_2, and some of the fields in DCI formats 1_1, 1_2 are shown in table 3 below.
TABLE 3 Table 3
It should be noted that the number of bits occupied by the PUCCH carrier field may be set according to the requirement, and the number of bits occupied by the PUCCH carrier field is 0 to 3 bits as an example.
Scheme b
The original fields in the DCI are reinterpreted, and Carrier indicator fields in the DCI may be reinterpreted as an example. For the Carrier indicator field, this field is currently used to indicate another carrier on which the PDCCH is scheduling the present carrier. Table 4 below gives the contents of CrossCarrierSchedulingConfig configured by RRC signaling, where schedulingCellId in CrossCarrierSchedulingConfig corresponds to the carrier indicated by Carrier indicator field.
TABLE 4 Table 4
Currently schedulingCellId is only set to be valid when the own cell is SCell (since PCell can only be scheduled by itself), so the following rules can be adopted for reinterpretation:
If cif-Presence is set to True (i.e., a Carrier indicator field appears in the DCI is acknowledged), and the current cell is PCell, a Carrier indicator field in the DCI indicates a carrier carrying HARQ feedback information corresponding to the downlink data transmission scheduled this time.
Scheme c
The original fields in the DCI are reinterpreted, and Carrier indicator fields in the DCI may be reinterpreted as an example. For the Carrier indicator field, this field is currently used to indicate another carrier on which the PDCCH is scheduling the present carrier. Further, the meaning of Carrier indicator field is extended so that it represents both the carrier on which PDCCH scheduling is performed and the carrier on which HARQ is fed back.
As an implementation, to activate the meaning of Carrier indicator field extension, a PucchOnThisCarrier field may be added in CrossCarrierSchedulingConfig to indicate whether the carrier of PUCCH is also controlled by Carrier indicator field, as shown in table 5 below.
TABLE 5
As another implementation, to activate the meaning of Carrier indicator field extension, a PucchOnThisCarrier field may be directly added to the DCI to indicate whether the carrier of the PUCCH is also controlled by the Carrier indicator field, as shown in table 6 below.
TABLE 6
Scheme b saves DCI resources more than scheme a.
Table 7 below gives a comparison of different ways of indicating PUCCH cells.
TABLE 7
Fig. 7 is a schematic diagram of the structural composition of a device for indicating a carrier according to an embodiment of the present application, which is applied to a terminal, as shown in fig. 7, where the device for indicating a carrier includes:
a determining unit 701, configured to determine a first carrier based on a predefined rule or an indication of a network side;
a transmission unit 702, configured to transmit a PUCCH on the first carrier, where the PUCCH is used to carry HARQ feedback information corresponding to the first downlink data transmission.
In some alternative embodiments, the apparatus further comprises: a receiving unit 703, configured to receive DCI, where the DCI carries scheduling information of the first downlink data transmission, and the first DCI further carries first indication information, where the first indication information is used to indicate a first time domain position of HARQ feedback information corresponding to the first downlink data transmission.
In some optional embodiments, the determining unit 701 is configured to:
checking whether available PUCCH resources exist on all carriers according to a specific sequence; wherein, the usable PUCCH resource refers to a PUCCH resource corresponding to the first time domain position;
If available PUCCH resources exist in one carrier, determining the one carrier as a first carrier;
if there are a plurality of carriers and available PUCCH resources, one carrier is determined from the plurality of carriers as a first carrier.
In some optional embodiments, the determining unit 701 is configured to check PUCCH configurations of all carriers in order of small serving cell index to large serving cell index; for each carrier, determining whether the carrier is configured with a PUCCH resource corresponding to the first time domain location based on the PUCCH configuration of the carrier.
In some optional embodiments, the determining unit 701 is configured to select, from the plurality of carriers, a carrier with a minimum serving cell index as a first carrier; or selecting the carrier with the largest serving cell index from the plurality of carriers as a first carrier; or randomly selecting one carrier from the plurality of carriers as the first carrier.
In some optional embodiments, the determining unit 701 is configured to determine, based on a first mapping table configured by the network side through RRC signaling, a carrier identifier corresponding to the first time domain location, and determine a first carrier based on the carrier identifier corresponding to the first time domain location; wherein the first mapping table comprises a mapping relation between at least one time slot and carrier identification.
In some alternative embodiments, the total number of time slots in the first mapping table is determined based on: mapping relation between subcarrier spacing and number of slots in a frame.
In some optional embodiments, the determining unit 701 is configured to determine the first carrier based on a carrier identifier indicated by the DCI at the network side.
In some optional embodiments, the DCI includes a first field, where the first field is used to indicate a first carrier identity, and a carrier corresponding to the first carrier identity is a carrier used to transmit the PUCCH.
In some alternative embodiments, the first field is a PUCCH carrier field.
In some optional embodiments, the DCI includes a second field, where the second field is used to indicate a second carrier identifier, and a carrier corresponding to the second carrier identifier is a carrier used to transmit the PUCCH and/or a carrier used to transmit the PDCCH, where the PDCCH is used to schedule a carrier where the DCI is located.
In some optional embodiments, if the carrier on which the DCI is located is a primary cell PCell, a carrier corresponding to the second carrier identifier indicated by the second field is a carrier used for transmitting the PUCCH.
In some optional embodiments, if the carrier on which the DCI is located is a secondary cell SCell, the carrier corresponding to the second carrier identifier indicated by the second field is both a carrier for transmitting the PDCCH and a carrier for transmitting the PUCCH.
In some optional embodiments, the determining unit 701 is further configured to determine, based on a third field, a purpose of the carrier corresponding to the second carrier identifier indicated by the second field.
In some optional embodiments, the third field is located in a cross-carrier scheduling configuration, and a serving cell index indicated by a scheduling cell identification field in the cross-carrier scheduling configuration corresponds to a second carrier identification indicated by the second field; or the third field is located in the DCI.
In some alternative embodiments, the second field is a carrier indication field.
Those skilled in the art will appreciate that the implementation functions of the units in the apparatus for indicating a carrier wave shown in fig. 7 can be understood with reference to the related description of the foregoing method. The functions of the respective units in the carrier wave indicating device shown in fig. 7 may be implemented by a program running on a processor or by a specific logic circuit.
Fig. 8 is a schematic diagram ii of the structure of a device for indicating a carrier according to an embodiment of the present application, which is applied to a network device, as shown in fig. 8, where the device for indicating a carrier includes:
an indication unit 801, configured to indicate a first carrier to a terminal, where the first carrier is used for the terminal to transmit a PUCCH, and the PUCCH is used for carrying HARQ feedback information corresponding to the first downlink data transmission.
In some alternative embodiments, the apparatus further comprises: a sending unit 802, configured to send DCI to the terminal, where the DCI carries scheduling information of the first downlink data transmission, and the first DCI further carries first indication information, where the first indication information is used to indicate a first time domain position of HARQ feedback information corresponding to the first downlink data transmission.
In some optional embodiments, the indication unit 801 is configured to configure, through RRC signaling, a first mapping table for the terminal, where the first mapping table is used for the terminal to determine a carrier identifier corresponding to the first time domain location, and determine a first carrier based on the carrier identifier corresponding to the first time domain location; wherein the first mapping table comprises a mapping relation between at least one time slot and carrier identification.
In some alternative embodiments, the total number of time slots in the first mapping table is determined based on: mapping relation between subcarrier spacing and number of slots in a frame.
In some optional embodiments, the indication unit 801 is configured to indicate, to the terminal, a carrier identifier, where the carrier identifier is used by the terminal to determine the first carrier.
In some optional embodiments, the DCI includes a first field, where the first field is used to indicate a first carrier identity, and a carrier corresponding to the first carrier identity is a carrier used to transmit the PUCCH.
In some alternative embodiments, the first field is a PUCCH carrier field.
In some optional embodiments, the DCI includes a second field, where the second field is used to indicate a second carrier identifier, and a carrier corresponding to the second carrier identifier is a carrier used to transmit the PUCCH and/or a carrier used to transmit the PDCCH, where the PDCCH is used to schedule a carrier where the DCI is located.
In some optional embodiments, if the carrier on which the DCI is located is a PCell, the carrier corresponding to the second carrier identifier indicated by the second field is a carrier used for transmitting the PUCCH.
In some optional embodiments, if the carrier in which the DCI is located is an SCell, the carrier corresponding to the second carrier identifier indicated by the second field is both a carrier used for transmitting the PDCCH and a carrier used for transmitting the PUCCH.
In some optional embodiments, the indication unit 801 is configured to indicate, to the terminal, the use of the carrier corresponding to the second carrier identifier indicated by the second field through a third field.
In some optional embodiments, the third field is located in a cross-carrier scheduling configuration, and a serving cell index indicated by a scheduling cell identification field in the cross-carrier scheduling configuration corresponds to a second carrier identification indicated by the second field; or the third field is located in the DCI.
In some alternative embodiments, the second field is a carrier indication field.
Those skilled in the art will appreciate that the implementation functions of the units in the apparatus for indicating a carrier wave shown in fig. 8 can be understood with reference to the related description of the foregoing method. The functions of the respective units in the carrier wave indicating device shown in fig. 8 may be implemented by a program running on a processor or by a specific logic circuit.
Fig. 9 is a schematic block diagram of a communication device 900 according to an embodiment of the present application. The communication device may be a terminal or a network device, and the communication device 900 shown in fig. 9 includes a processor 910, and the processor 910 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 9, the communication device 900 may also include a memory 920. Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the method in the embodiments of the present application.
Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.
Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
Wherein transceiver 930 may include a transmitter and a receiver. Transceiver 930 may further include antennas, the number of which may be one or more.
Optionally, the communication device 900 may be specifically a network device in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the communication device 900 may be specifically a mobile terminal/terminal according to an embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the mobile terminal/terminal in each method according to the embodiment of the present application, which is not described herein for brevity.
Fig. 10 is a schematic structural view of a chip of an embodiment of the present application. The chip 1000 shown in fig. 10 includes a processor 1010, and the processor 1010 may call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 10, the chip 1000 may further include a memory 1020. Wherein the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in embodiments of the present application.
The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.
Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.
Optionally, the chip 1000 may further include an output interface 1040. Wherein the processor 1010 may control the output interface 1040 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the chip may be applied to a mobile terminal/terminal in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal in each method in the embodiment of the present application, which is not described herein for brevity.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing a computer program.
Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal in each method of the embodiment of the present application, which is not described herein for brevity.
The embodiment of the application also provides a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.
Optionally, the computer program product may be applied to a mobile terminal/terminal in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal in each method of the embodiment of the present application, which are not described herein for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the computer program may be applied to a mobile terminal/terminal in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the mobile terminal/terminal in each method in the embodiment of the present application, which is not described herein for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.