TW201632027A - Carrier aggregation in communications - Google Patents

Abstract

A solution comprising determining for a terminal device of a cellular communication system, a configuration for carrier aggregation with at least one serving cell configured to be scheduled by means of cross-carrier scheduling; determining, a mapping between a serving cell index of the configured serving cell to be scheduled by means of cross-carrier scheduling and a scheduling cell-specific carrier indicator field value; causing, in the network node, transmission of a configuration message to the terminal device for the carrier aggregation, the configuration message comprising at least one information element indicating at least one cell to be scheduled by means of the cross-carrier scheduling and transmitting control information to the terminal device, the control information comprising a carrier indicator field, wherein the carrier indicator field value is based on said mapping between the serving cell index and the scheduling cell-specific carrier indicator field.

Description

Carrier aggregation in communication

The invention relates to communication.

3GPP LTE-A (Long Term Evolution Technology Upgrade) includes the concept of a primary cell (PCell) and a secondary cell (SCell) to support carrier aggregation. Carrier aggregation is introduced in LTE-A to provide increased bandwidth and thereby provide increased bit rate. Each aggregated carrier is referred to as a component carrier (CC) or otherwise referred to as a cell or a serving cell. When carrier aggregation is implemented, several serving cells are provided, and each component carrier has a serving cell. The coverage of the serving cell may vary, for example, due to the path loss experienced. One of the serving cells is referred to as a primary serving cell, which uses a primary component carrier (DL and UL PCC). The other component carriers are called secondary component carriers (DL and UL SCC), which are used by the secondary serving cell.

According to one aspect, the subject matter of the independent request item is provided. Embodiments are defined in the dependency request.

One or more examples of the embodiments to be implemented are described in more detail in the drawings and the following description. Other features will become apparent from the description and drawings and claims.

10‧‧‧Processing Circuit

12‧‧‧Configuration Circuit

14‧‧‧Control information generator

16‧‧‧ mapping circuit

18‧‧‧Configuration Information Generator

20‧‧‧ memory

22‧‧‧Communication interface

24‧‧‧Computer Program Products

26‧‧‧Database

50‧‧‧Processing Circuit

52‧‧‧ mapping circuit

54‧‧‧TX/RX controller

60‧‧‧ memory

62‧‧‧Communication interface

64‧‧‧Computer Program Products

66‧‧‧Database

100‧‧‧Small base station

102‧‧‧ Large base station

104‧‧‧ Terminal devices

106‧‧‧ Terminal devices

In the following, the invention will be described in more detail based on the preferred embodiments in accordance with the accompanying drawings.

1 depicts an example of a wireless communication system that can be used in the implementation of an embodiment of the present invention; FIG. 2 depicts an example of carrier aggregation; FIG. 3 depicts an example of self-scheduling; and FIG. 4 depicts a cross-carrier Example of cross-carrier scheduling; FIG. 5 is an exemplary communication diagram of a procedure for carrier aggregation according to an embodiment of the present invention; and FIG. 6 and FIG. 7 depict carrier aggregation according to an embodiment of the present invention An example of a program; Figures 8 and 9 depict block diagrams of an example of a device in accordance with an embodiment of the present invention.

The following examples are illustrative. Although the specification may refer to "a", "an" or "an" embodiment in the various aspects, this does not necessarily mean that each embodiment is the same or that the features are only applicable to a single embodiment. . A single feature of a different embodiment may also be combined to provide other embodiments. In addition, it should be understood that the words "comprise" and "comprising" are not used to limit that the described embodiments are only those that have been described, and such embodiments may also include features not specifically mentioned. structure.

Figure 1 depicts an example of a wireless communication scheme that can be used in the implementation of embodiments of the present invention. Referring to FIG. 1, a cellular communication system can include a radio access network including a base station configured to provide radio coverage in a predetermined geographic area. The base stations may include a large base station (eNB) 102 configured to provide radio coverage of a terminal device (UE) 106 over a relatively large area, such as across a few square miles. In a densely populated hotspot where capacity is required to be increased, a small base station (eNB) 100 is arranged to provide a high data rate service of the terminal device (UE) 104. Such a small base station can be called a micro base station, a special micro base station or a femto base station. These small base stations typically have a significantly smaller coverage than the large base station 102. The cellular communication system can operate in accordance with the 3rd Generation Partnership Project (LTE) Long Term Evolution (LTE) upgrade or its evolutionary version (eg, 5G).

When carrier aggregation is implemented, more than one component carrier is used by the UE. These component carriers may be in the same location (e.g., in the large base station) or in different locations (e.g., one component carrier is in the large base station and other component carriers are in the small base station). Carrier aggregation can be configured by using consecutive component carriers within the same operating band. This may be impossible, for example, due to operator frequency allocation scenarios. The discontinuous allocation may be intra-band, that is, the component carriers belong to the same operating band, but have gaps therebetween, or it may be inter-band, where the component carriers belong to Different operating bands. Figure 2 depicts carrier aggregation. Regarding scheduling, carrier aggregation has two main types. To be an alternative, when receiving a grant, resources are scheduled on the same carrier (ie, self-scheduled), or cross-carrier scheduling can be used, where a downlink containing a carrier's scheduling grant is received on a different carrier. Road control information. For cross-carrier scheduling, a scheduled cell also carries scheduling grants for other cells, which are thus represented as (cross-carrier) scheduled cells. Figure 3 depicts the self-scheduled, and Figure 4 depicts the cross-carrier scheduling.

A cross-carrier schedule based on Rel-10 uses a field in a UL/DL schedule grant, which is represented as a Carrier Indicator Field (CIF). In Rel-10, the CIF is limited to 3 bits, which is supported by the LTE specification, which is sufficient to enable cross-carrier scheduling of up to 5 component carriers. The carrier indication field is part of a scheduled UL/DL grant procedure and the carrier indication field is transmitted within downlink control information (DCI).

The cross-carrier scheduling of carrier aggregation is UE capability. A cross-carrier scheduling for carrier aggregation of the UE is configured for each configured component carrier, respectively.

In 3GPP LTE Rel-10, the CIF carried in the DCI is limited to 3 bits, and the value of the CIF is equal to a serving cell index. The CIF value defines the carrier associated with the scheduled UL/DL grant, and the CIF value also affects the user-specific search space location of the downlink control channel under which the UE is searching. The individual search space information according to the CIF value (0...7) may be as follows. A candidate entity downlink control channel (PDCCH) set for monitoring is defined according to the search space, wherein a search space at an aggregation level is defined by a candidate PDCCH set. For each serving cell monitoring the PDCCH, a Control Channel Element (CCE) corresponding to the candidate PDCCH of the search space is defined. The following can be considered: a common search space, a PDCCH (or Enhanced Physical Downlink Control Channel (EPDCCH)) UE-specific search space, whether the monitored UE is configured with the carrier indication field, the serving cell monitoring the PDCCH/EPDCCH, and/or The number of candidate PDCCH/EPDCCHs monitored in the search space. The carrier indicates that the field value is the same as the serving cell index.

The configuration of this cross-carrier scheduling is defined as follows. The cif-Presence-r10 in the PhysicalConfigDedicated indicates whether the CIF exists in the PDCCH Downlink Control Information (DCI) of the PCell. A CIF value of 0 indicates a PCell, and another SCell can be addressed with a ServCellIndex parameter, that is, the CIF value is the same as the ServCellIndex parameter. Thus, each SCell can be configured to have this cross-carrier schedule as part of the SCell addition or modification. The configuration of the SCell with the cross-carrier scheduling as part of the SCell addition or modification is implemented by the CrossCarrierSchedulingConfig parameter, which is part of the PhysicalConfigDedicatedSCell parameter.

Support for Rel-13 with respect to carrier aggregation enhancements that can be scheduled to schedule up to 32 component carriers. Provision of a mechanism for LTE carrier aggregation of up to 32 component carriers of the downlink (DL) and uplink (UL), if any, including enhancements to DL control signaling for up to 32 component carriers (including self-scheduled and cross-carrier scheduling).

According to the CrossCarrierSchedulingConfig parameter, together with Rel-10 LTE carrier aggregation, one of the SchedulingCellInfo parameters is specified to indicate whether cross-carrier scheduling is enabled. The "SchedulingCellInfo parameter" indicating "self" means The SCell transmits its own PDCCH, ie, the cross-carrier scheduling is not enabled. It can be indicated by cif-Presence-10 whether the SCell is a scheduled cell that can interactively arrange another cell (in the Rel-10, the SCell can also be made into a scheduled cell that can interactively arrange another SCell). On the other hand, if cross-carrier scheduling is enabled (i.e., the SCell is alternately arranged with another cell), the SchedulingCellInfo parameter indicates "other", which means that some "other" serving cells transmit the PDCCH DCI.

A SchedulingCellId parameter informs the UE which cell to signal the downlink assignment and uplink grant for the SCell under consideration. This operation is extended to 32 component carriers (ie, 32 serving cells), which means that from the UE's point of view, this means that the serving cell index needs to be increased from [0,...,7] to [0,.. ., 31]. This may also affect the cross-carrier scheduling operation.

The cross-carrier scheduling principle can be extended by increasing the CIF length from 3 bits to 5 bits to enable cross-carrier scheduling of up to 32 component carriers. However, the above requires a larger DCI format, and thus there is a higher possibility of DCI loss detection (i.e., a higher coding rate at the same aggregation level). In addition, there is a higher probability of having the same size of DCI and the need to additionally add bits at the end of the DCI (to prevent ambiguity), which further increases the DCI block error rate. If the two DCIs have the same size, it is possible to add zeros at the end to produce different sizes.

Let us now describe an embodiment of carrier aggregation in accordance with FIG. Figure 5 is a diagram depicting a method of communicating cross-carrier scheduling parameters between network elements of the cellular communication system. The network component may It is a network node, an access node, a base station, a terminal device, a server computer, or a host computer. For example, the server or host computer can generate a virtual network that allows the host computer to communicate with the terminal device. In general, virtual network construction may involve the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). In another embodiment, the network node may be a terminal device. Network virtualization may involve platform virtualization, which is often combined with resource virtualization. Network virtualization can be categorized as the integration of many networks or portions of the network into the external virtual network of the server or host computer. The goal of external network virtualization is optimal network sharing. Another type is the internal virtual network construction that provides network-like functionality to software containers on a single system. The virtual network construction can also be used to test the terminal device.

Referring to FIG. 5, in item 501, a network node determines a carrier aggregation configuration for a terminal device and at least one cell is configured to be scheduled in a cross-carrier schedule. In an embodiment, the configuration includes more than eight serving cells for carrier aggregation. However, the embodiments of the present invention are not limited to the number used as an example. In an embodiment, the network node may determine a mapping between a serving cell index of the configured serving cell and a scheduled cell specific carrier indication field value arranged in a cross-carrier schedule.

In item 502, in accordance with the decision, the network node transmits a configuration message to the carrier device for carrier aggregation. The configuration information includes at least one information element indicating that at least one cell is scheduled with the cross-carrier schedule. In item 503, the terminal device aggregates carriers from the network The node receives the configuration information. In an embodiment, in item 504, the network node can implement the mapping. In item 505, the network node transmits control information (e.g., DCI) to the terminal device, the control information including a carrier indication field, wherein the carrier indication field value is based on the serving cell index and the scheduled cell The specific carrier indicates the mapping between the fields.

In an embodiment, the mapping may be based on a mapping rule in which the serving cell index of the serving cell scheduled in the cross-carrier scheduling is mapped to the scheduled cell specific carrier indication field values, for example, in ascending or descending order.

In item 506, the terminal device receives the control information from the network node.

In another embodiment with respect to FIG. 5, in item 501, a network node determines a carrier aggregation configuration for a terminal device and at least one cell is configured to be arranged in a cross-carrier schedule for use in carrier aggregation. The number of configured cells may be greater than 8 cells, and the number of cells arranged by a single scheduled cell in a cross-carrier schedule is 8 or less. In item 502, in accordance with the decision, the network node transmits a configuration message to the carrier device for carrier aggregation. The configuration information includes at least one information element indicating that at least one cell is scheduled by the single scheduled cell in the cross-carrier scheduling such that the number of cells scheduled by the cross-carrier scheduling is 8 or less. In item 503, the terminal device receives the configuration information from the network node for carrier aggregation. In item 504, the network node implements mapping of the serving cell to a scheduled cell specific carrier indication value.

In item 505, the network node transmits, via a scheduled cell, downlink control information about the downlink control serving cell to the terminal device. The downlink control information includes a carrier indication field. The carrier indication field value is a mapping 504 that indicates a field value based on a particular cell to a scheduled cell. In item 506, the terminal device receives the downlink control information from the network node, wherein the terminal device implements a reverse-scheduled cell-specific mapping from a carrier indication field to a serving cell to obtain a scheduled cell Control information.

In one embodiment, the mapping between the serving cell and a scheduled cell specific carrier indication field value in the network of item 504 and the reverse mapping in the UE of item 506 are based on the same mapping rules. This mapping rule can be based on a predetermined mapping rule.

In another option, the eNB itself may determine a mapping between the serving cell and a scheduled carrier specific carrier indication field value and inform the predetermined UE about the mapping rule. In this case, the UE may use the mapping 506 between the scheduled cell-specific CIF and a serving cell according to the RRC signal. The RRC signal is explicitly sent, that is, the configuration information 502 may also indicate that the CIF is used for a predetermined SCell or RRC signal (ie, the configuration information 502) to configure the SCell and indicate which cell is the scheduled cell and then according to the This mapping 506 is used by predetermined mapping rules. The DCI carries a CIF, where according to the mapping, the UE knows which SCell is being scheduled.

The terminal device and the network node may maintain predetermined mapping rules (eg, a mapping table or some other data node) for mapping between the serving cell index, the corresponding scheduled cell identifier, and the carrier indication field. Structure). In another option, appropriate mapping rule information can be determined 501 in the network node and provided from the network node to the terminal device, for example by using the RRC signal 502.

In an embodiment, the number of scheduled cells according to a single scheduled cell may be limited to 8 or less cells. Interpretation and mapping of CIF values in DCI does not require an increase in 3-bit CIF length to support more than 8 serving cells. This limitation does not affect cross-carrier scheduling operations because there is PDCCH/EPDCCH blocking for a large number of scheduled cells according to a single scheduled cell (ie, PDCCH/from this single scheduled cell is required) EPDCCH transmits a lot of DCI).

In an embodiment, the serving cell index to CIF mapping may be implemented such that the CIF indicates the serving cell index of the configured cell of the single scheduled cell only in ascending order, even if the 3-bit CIF is limited to a value from 0 to 7. A serving cell index with a cell greater than 7 can be provided.

The serving cell index CIF mapping can be implemented as follows. For example, assume that the UE is configured with carrier aggregation of 14 cells/carriers and the configuration defines two scheduled cells for each of the 14 cells (cross-carrier). For these 14 cells, the scheduled cells for each of the cells according to the higher layer configuration are shown in Table 1.

In this example, consider two scheduled cells with SchedulingCellId#0 and SchedulingCellId#1. When the PCell's ServCellIndex is 0 each time, the first schedule in this example is small. The area is PCell, and the second scheduled cell is an SCell with ServingCellIndex 1. In the 14 cells (ServCellIndex-r13 is [0, ..., 13]), in addition to self-scheduling according to PCell, 5 cells are configured for cross-carrier scheduling according to PCell (Cell #3, 4, 5, 6, 10), and a first scheduled SCell (with ServingCellIndex 1) configured to arrange cell #1 (ie, self-scheduled) and for cells #2, 7, 8, 9, 11 , 12, 13 cross-carrier scheduling. For the PCell, the serving cell index of the cell to be scheduled is sorted according to the increasing order of the serving cell index, and the related CIF (that is, the defined mapping) is allocated for the cross-carrier scheduling shown in Table 2.

Therefore, CIF=2 in the DCI on the PCell maps to ServCellIndex-r13=4, and CIF=5 indicates ServCellIndex-r13=10. Thus, for the second scheduled cell, the same mapping as described above is implemented (see Table 3).

Thus, for each cell scheduled by the same cell, the CIF value of the cell is determined by the location of the serving cell index of the cell sorted in ascending order. The UE implementation can maintain such a mapping table according to the configuration.

In another example, it is assumed that there are 14 carriers (ServCellIndexes 0...13) in which 7 carriers are arranged in a cross-carrier manner, for example, by PCell (ServCellIndex = 0). Let us assume that the even cell is arranged by the PCell in a cross-carrier manner, and a mapping between CIF=0...7 and the serving cell index=0, 2, 4, 6, 8, 10, 12 is required. To determine the mapping, two options are provided that include predetermined mapping rules and explicit RRC signals. According to a rule, CIF=0 is mapped to ServCellIndex=0, and CIF=1 is mapped to ServCellIndex=2. . . . . . , CIF=6 is mapped to ServCellIndex=12 (in ascending order). This is similar to Table 2 above. Regarding the explicit RRC signal, any mapping is possible, for example, the mapping can be:

This can be implemented to the RRC specification as follows. When SCell is added, it is given a sCellIndex value (equal to ServCellIndex):

Within the RadioResourceConfigDedicatedSCell, there is a PhysicalConfigDedicatedSCell that includes a cross-carrier scheduling configuration:

(Other than this) The above also distinguishes between the scheduled cell (the ServCellIndex of the scheduled cell) and the case where the configured SCell is to be scheduled. The CIF value to be used can be added to this SCell (see cifInSchedulingCell-r13...INTEGER(0..7) below) (for example, when SCell is configured with sCellIndex=6, the setting can be CIF=1):

In an embodiment, up to 8 component carriers can be arranged by a scheduling cell, and the cross-carrier scheduling operation can be extended without supporting the CIF size in the downlink control information format to support more than 8 serving cells.

In another embodiment, the ServCellIndexes are organized in a descending order, and/or any other suitable ServCellIndex ordering rules may be defined and implemented. The definition of this rule enables the mapping to require no additional RRC signals.

In another embodiment, the mapping may be configurable, that is, for example, when adding an SCell scheduled by a given cell, the RRC signal may explicitly indicate a mapping between CIF and ServCellIndex. If the ServCellIndex of the added SCell is between the ServCellIndexes of the existing SCells, the mapping of the previous SCells can be maintained, that is, the addition of the SCell to be scheduled does not change the mapping of other CIFs. The above may be performed in the RRC, for example, by adding a parameter like cifValueInSchedulingCell in the CrossCarrierSchedulingConfig. In this case, with respect to Tables 2 and 3, the mapping of the two scheduled cells is provided directly by the higher layer signals in this example.

The CIF value may also affect user-specific search space definitions for PDCCH and EPDCCH, where the CIF value provides a search space offset for each of the scheduled cells. This can be extended to match the mapping table/program as follows. 1) The CIF value can be used to replace the ServingCellId in the search space definition; in this case, the search space remains fairly small at the maximum offset of M*7, but may be slightly different from defining the CIF value ( As a solution to CIF mapping). In this case, n_CIF is the CIF value of the mapping table. 2) In another option, the ServingCellId may be used in the PDCCH/EPDCCH user-specific search space definition; in this case, as in the case of extending CIF to 5 bits, the exact offset of M*31 is Define the same search space. In this case, n_CIF is defined as ServingCellId. Here, M means the number of candidate PDCCHs to be monitored in a given search space.

An embodiment can increase cross-carrier scheduling capabilities. Cross-carrier scheduling of up to 32 component carriers is possible without increasing the CIF size. For 32 component carriers, 4 or more scheduled cells can be configured, and each scheduled cell is limited to arranging 8 or less cells. Therefore, the cross-carrier scheduling is extended to up to 32 cells without increasing the CIF length in the DCI format. DCI decoding performance is not affected by negative, and there is less likelihood of DCIs of the same size. The CIF pair ServingCellId mapping for each scheduled cell is performed, where the mapping can be provided by a simple rule (incremental, decremental order, etc.) or by a higher layer signal (eg, an RRC signal). Up to 8 carriers can be arranged by the single scheduled cell.

In an embodiment, a scheduled cell-specific carrier indication field value obtained according to the mapping rule may be used in the downlink control information to identify a corresponding scheduled serving cell. In an embodiment, a scheduled cell-specific carrier indication field value obtained according to the mapping rule may be used to identify a search space corresponding to the cross-carrier scheduled serving cell.

Let us now describe this cross-carrier scheduling embodiment in more detail in accordance with Figures 6 and 7. Referring to FIG. 6, in item 601, a network node determines, for a terminal device, a configuration of carrier aggregation of at least one cell arranged in a cross-carrier schedule. This configuration includes more than 8 serving cells for carrier aggregation. However, the embodiments of the present invention are not limited to the number used as an example. In an embodiment, the network node may determine a mapping between a serving cell index of the configured serving cell and a scheduled cell specific carrier indication field value arranged in a cross-carrier schedule.

In item 602, in accordance with the decision, the network node transmits a configuration message to the carrier device for carrier aggregation. The configuration information includes at least one information element indicating that at least one cell is scheduled with the cross-carrier schedule.

In an embodiment, in item 603, the network node can implement the mapping.

In item 604, the network node transmits control information (e.g., DCI) to the terminal device, the control information including a carrier indication field, wherein the carrier indication field value is based on the serving cell index and the scheduled cell The specific carrier indicates the mapping between the fields. In an embodiment, the mapping may be based on a mapping rule, wherein the serving cell index of the serving cell arranged by the cross-carrier scheduling is mapped to the scheduled cell-specific carrier indication field values, for example, in ascending or descending order.

Referring to Figure 7, in item 701, a terminal device receives a configuration information from a network node for carrier aggregation. The configuration information includes at least one information element indicating that at least one cell is scheduled in a cross-carrier schedule.

In item 702, the terminal device receives control information on the cross-carrier scheduled serving cell from the network node via a scheduled cell. The control information includes a carrier indication field, wherein the carrier indication field value is based on a mapping between a serving cell index and a scheduled cell specific carrier indication field value.

In item 703, the terminal device may utilize a mapping between the serving cell index, the corresponding scheduled cell identifier, and the carrier indication field. The terminal device can maintain a predetermined mapping rule (eg, a mapping table) to The mapping between the serving cell index, the corresponding scheduled cell identifier and the carrier indication field is performed. In another option, the appropriate mapping rule information can be determined and received in the network device from the network node, for example, with the configuration information.

An embodiment provides an apparatus including at least one processing and at least one memory (including a computer code), wherein the at least one memory and the computer code are configured with the at least one processor to cause the apparatus to implement the above The base station or the program of the network node. Accordingly, the at least one processor, the at least one memory, and the computer program code can be considered as embodiments of means for executing the program of the base station or the network node. Figure 8 depicts a block diagram of the structure of such a device. The apparatus can be included in the base station or the network node, for example, the apparatus can constitute a chipset or circuit in the base station or in the network node. In some embodiments, the device is the base station or the network node. The apparatus includes a processing circuit 10 including the at least one processor. The processing circuit 10 can include a configuration circuit 12 configured to determine a configuration of more than eight serving cells for carrier aggregation for a terminal device and at least one cell configured to be arranged in a cross-carrier schedule for inter-carrier scheduling The number of cells arranged by a single scheduled cell is 8 or less. The configuration circuit 12 can be configured to determine the configuration and output information to a configuration information generator 18. The configuration information generator 18 is configured to transmit a configuration information to the carrier device to the carrier aggregation. The configuration information includes at least one information element indicating that at least one cell is scheduled with the cross-carrier scheduling such that the number of cells scheduled by a single scheduled cell in a cross-carrier schedule is 8 or less. In order to serve the community For mapping between the corresponding scheduled cell identifier and the carrier indication field, a mapping circuit 16 is configured to maintain a predetermined mapping rule (eg, a mapping table). In another option, the mapping circuit 16 is configured to determine appropriate mapping rule information. The mapping circuit 16 can be configured to provide predetermined mapping rules to the terminal device (e.g., by using an RRC signal). A control information generator 14 is configured to transmit control information (e.g., DCI) regarding the cross-carrier scheduled serving cell to the terminal device via a scheduled cell. The control information includes a carrier indication field. The processing circuit 10 can include the circuits 12 through 18 as sub-circuits or can be considered as computer program modules executed by the same physical processing circuit. The memory 20 can store one or more computer program products 24 including program instructions that explicitly describe the operation of the circuits 12-18. The memory 20 can further store, for example, a database 26 including definitions for carrier aggregation. The apparatus can further include a communication interface 22 that provides radio communication capabilities with the terminal devices. The communication interface 22 can include a radio communication circuit capable of wireless communication and includes a radio frequency signal processing circuit and a baseband signal processing circuit. The baseband signal processing circuit can be configured to implement the functions of the transmitter and/or receiver. In some embodiments, the communication interface can be coupled to a wireless radio head including at least one antenna, and in some embodiments, radio frequency signal processing relative to a remote location of the base station. In these embodiments, the communication interface may perform only some RF signal processing or fully implement RF signal processing. The connection between the communication interface and the wireless broadband headend device can be an analog connection or a digital connection. In some embodiments, the communication interface can include a fixed communication circuit that can be wired.

An embodiment provides another apparatus including at least one processor and at least one memory (including a computer code), wherein the at least one memory and the computer code are configured with the at least one processor to cause the apparatus The program of the above terminal device is implemented. Therefore, the at least one processor, the at least one memory, and the computer program code can be regarded as an embodiment of a device for executing the above-described program of the terminal device. Figure 9 depicts a block diagram of the structure of such a device. The device may be included in the terminal device, for example, the device may constitute a chip set or circuit in the terminal device. In some embodiments, the device is the terminal device. The apparatus includes a processing circuit 50 including the at least one processor. The processing circuit 50 can include a TX/RX controller 54 configured to receive configuration information for carrier aggregation from a network node. The configuration information includes at least one information element indicating that at least one cell is scheduled in a cross-carrier schedule such that the number of cells scheduled by the single scheduled cell in the cross-carrier schedule is 8 or less. The TX/RX controller 54 is further configured to receive control information regarding the cross-carrier scheduled serving cell from the network node via a scheduled cell. The control information includes a carrier indication field. The TX/RX controller 54 is configured to receive the control information and output the information to a mapping circuit 52. The mapping circuit 52 is configured to utilize a mapping between a serving cell index, a corresponding scheduled cell identifier, and a carrier indication field. In order to map the serving cell index, the corresponding scheduled cell identifier, and the carrier indication field, a predetermined mapping rule (eg, a mapping table) may be maintained in the memory 60. In another option, appropriate mapping information (e.g., in the configuration information) can be received from the network node in the TX/RX controller 54. This treatment Circuitry 50 may include such circuits 52, 54 as sub-circuits or may be considered as computer program modules executed by the same physical processing circuit. The memory 60 can store one or more computer program products 64 including program instructions that explicitly describe the operation of the circuits 52, 54. The apparatus can further include a communication interface 62 that provides radio communication capabilities with base stations of one or more cellular communication networks. The communication interface 62 can include a radio communication circuit that can communicate wirelessly and includes a radio frequency signal processing circuit and a baseband signal processing circuit. The baseband signal processing circuit can be configured to implement the functions of the transmitter and/or receiver. In some embodiments, the communication interface 62 can include a fixed communication circuit that can be wired.

As used in this application, the term "circuitry" means all of the following: (a) hardware-only circuit implementation, for example, implemented only in analog and/or digital circuits; (b) circuits and a combination of software and/or firmware, for example, if applicable: (i) a combination of processors or processor cores; or (ii) a portion of a processor/software that includes a digital signal processor, software, and At least one memory that works together to cause a device to perform a particular function; and (c) a circuit, such as a microprocessor or portion of a microprocessor, even though the software or firmware does not actually exist, but they A soft body or firmware is required for operation.

This "circuitry" definition applies to all uses of this term in this application. As another example, the term "circuitry" as used in this application will also cover only one processor (or multiple processors) or a portion of a processor (eg, one core of a multi-core processor) And its (or their) software and/or firmware implementation, the term "electricity" The road will also cover (for example and if applicable to a particular component) a baseband integrated circuit, an application specific integrated circuit (ASIC) and/or a field programmable gate for a device in accordance with an embodiment of the present invention. Array (FPGA) circuit.

The techniques described herein may be implemented by various means, such that a device that implements one or more functions of a corresponding mobile entity as described in an embodiment includes not only conventional art devices, but also includes an embodiment for implementation. The device that functions as one or more of the corresponding devices, and it may include individual devices for each individual function, or the device may be configured to perform two or more functions.

The processes or methods described above with respect to Figures 1 through 9 may also be implemented in the form of one or more computer programs defined by one or more computer programs. It should be considered that the computer program also includes modules of computer programs. For example, the above process can be implemented in a computer program or a larger algorithmic program mode. The computer program may be in the form of a source code, an object code or some intermediate form, and may be stored in a carrier, which may be any entity or device capable of carrying the program. Such carriers include transitory and/or non-transitory computer media, such as recording media, computer memory, read-only memory, electrical carrier signals, telecommunications signals, and software distribution packages. Depending on the processing power required, the computer program can be executed in a single electronic digital processing unit, or the computer program can be distributed among some processing units.

The invention can be applied to a cellular or mobile communication system as defined above, but can be applied to other suitable communication systems as well. Protocols used, specifications of cellular communication systems, their network components and Terminal devices are rapidly evolving. Such developments may require additional changes to the described embodiments. Therefore, all words and descriptions should be interpreted as broadly and their description is not intended to be limiting.

Those skilled in the art will readily appreciate that the concepts of the present invention can be implemented in various ways as the technology advances. The present invention and its embodiments are not limited to the above examples, but may be varied within the scope of the patent application.

Claims (32)

A method comprising: determining, in a network node for a terminal device of a cellular communication system, a configuration for carrier aggregation and configuring at least one serving cell to be arranged in a cross-carrier schedule; In the node, determining a mapping between the serving cell index of the configured serving cell scheduled by the cross-carrier scheduling and a specific carrier indication field value of a scheduled cell; in the network node, transmitting a configuration information to the carrier aggregation to The terminal device, the configuration information includes at least one information element, which indicates that at least one cell is scheduled in a cross-carrier schedule; in the network node, control information is transmitted to the terminal device, and the control information includes a carrier indication field. The carrier indication field value is a mapping between the serving cell index and the specific carrier indication field of the scheduling cell. The method of claim 1, wherein the mapping is based on a mapping rule, wherein the serving cell index of the serving cell scheduled by the cross-carrier scheduling is mapped to the scheduled carrier specific carrier field value in an ascending or descending manner. . A method of any of the preceding claims, wherein the mapping is transmitted to the terminal device in the configuration information. A method as in any preceding claim, wherein the configuration comprises more than eight serving cells for carrier aggregation. A method according to any of the preceding claims, wherein the number of cells arranged by a single scheduled cell in a cross-carrier schedule is 8 or less. The method of any of the preceding claims, further comprising maintaining, in the network node, information of a predetermined mapping rule for mapping between the serving cell and the specific carrier indication field value of the scheduled cell. A method as in any preceding claim, wherein the scheduled cell specific carrier is used to indicate a field value to identify a search space for the corresponding scheduled serving cell. A method, comprising: receiving, in a terminal device of a cellular communication system, configuration information for carrier aggregation from a network node, the configuration information including at least one information element indicating that at least one cross-carrier scheduling is arranged a cell; receiving, in the terminal device, control information from the network node, the control information including a carrier indication field, wherein the carrier indication field value is based on a serving cell index and a scheduled cell specific carrier indication field The mapping between values. The method of claim 8, wherein the mapping is based on a mapping rule, wherein the serving cell index of the serving cell scheduled by the cross-carrier scheduling is mapped to the scheduled cell-specific carrier indication field value in ascending or descending order. . The method of claim 8 or 9, wherein the mapping is transmitted to the terminal device in the configuration information. The method of any one of claims 8 to 10, further comprising maintaining, in the terminal device, information of a predetermined mapping rule for mapping between the serving cell and the scheduled cell specific carrier indication field value. The method of claim 11, wherein the mapping rule indicates a mapping between the serving cell index of the cross-carrier scheduled cell, the corresponding scheduled cell identifier, and the corresponding carrier indication field. A method as claimed in any one of claims 8 to 12, comprising the configuration of more than 8 serving cells for carrier aggregation. The method of any one of claims 8 to 13, wherein the number of cells arranged by a single scheduled cell in a cross-carrier schedule is 8 or less. The method of any one of claims 8 to 14, wherein the scheduled cell specific carrier is used to indicate a field value to identify a search space of the corresponding scheduled serving cell. An apparatus comprising: at least one processor; and at least one memory comprising a computer program code, wherein the at least one memory and the computer program code and the at least one processor are configured to cause the device to target a hive One of the communication systems determines a configuration for carrier aggregation and at least one serving cell is configured to be arranged in a cross-carrier schedule; determining a serving cell index and a schedule for the configured serving cell scheduled by cross-carrier scheduling The cell-specific carrier indicates a mapping between field values; transmitting, to the terminal device, a configuration information to the terminal device, the configuration information including at least one information element, indicating that at least one cell is scheduled in a cross-carrier scheduling; Transmitting control information to the terminal device, the control information includes a carrier indication field, wherein the carrier indication field value is based on a mapping between the serving cell index and the specific carrier indication field of the scheduling cell. The apparatus of claim 16, wherein the mapping is based on a mapping rule, wherein the serving cell index of the serving cell scheduled by the cross-carrier scheduling is mapped to the scheduled carrier specific carrier field value in an ascending or descending manner. . The device of claim 16 or 17, wherein the at least one memory and the computer program code and the at least one processor are configured to cause the apparatus to transmit the mapping to the terminal device in the configuration information. The apparatus of any one of claims 16 to 18, wherein the configuration comprises more than 8 serving cells for carrier aggregation. The apparatus of any one of claims 16 to 19, wherein the number of cells arranged by a single scheduled cell in a cross-carrier schedule is 8 or less. The apparatus of any one of claims 16 to 20, wherein the at least one memory and the computer code and the at least one processor are configured to cause the apparatus to maintain a specific cell for the serving cell and the scheduling cell The carrier indicates information of a predetermined mapping rule for mapping between field values. The apparatus of any one of claims 16 to 21, wherein the scheduled cell specific carrier is used to indicate a field value to identify a search space of the corresponding scheduled serving cell. A device comprising: At least one processor; and at least one memory comprising a computer program code, wherein the at least one memory and the computer code and the at least one processor are configured to cause the device to: receive from a network node for Carrier configuration information, the configuration information including at least one information element indicating that at least one cell is scheduled in a cross-carrier schedule; receiving control information from the network node, the control information including a carrier indication field, wherein the carrier indication The field value is based on a mapping between a serving cell index and a scheduled cell specific carrier indication field value. The device of claim 23, wherein the mapping is based on a mapping rule, wherein the serving cell index of the serving cell scheduled by the cross-carrier scheduling is mapped to the scheduled cell specific carrier indication field value in an ascending or descending manner. . The apparatus of claim 23 or 24, wherein the mapping is transmitted to the terminal device in the configuration information. The apparatus of any one of claims 23 to 25, wherein the at least one memory and the computer code and the at least one processor are configured to cause the apparatus to maintain a specific one for the serving cell and the scheduled cell The carrier indicates information of a predetermined mapping rule for mapping between field values. The apparatus of claim 23 or 26, wherein the mapping rule indicates a mapping between the serving cell index of the cross-carrier scheduled cells, the corresponding scheduled cell identifiers, and the corresponding carrier indication field. The apparatus of any one of claims 23 to 27, wherein the number of cells arranged by a single scheduled cell in a cross-carrier schedule is 8 or less. The apparatus of any one of claims 23 to 28, wherein the scheduled cell specific carrier is used to indicate a field value to identify a search space of the corresponding scheduled serving cell. A device comprising means for performing the steps of the method of any of the preceding claims 1 to 15. A computer program product embodied on a distribution medium readable by a computer and including program instructions for executing the program requests 1 to 15 when the program instructions are loaded into a device method. A computer program product embodied on a non-transitory distribution medium readable by a computer and including program instructions, when the program instructions are loaded into the computer, the program instructions are executed as in claim 1 A computer program of any of the 15 method steps.