Patent Description:
Group signalling was introduced in LTE Rel-<NUM> as part of euCA (enhancing LTE CA utilisation) Wl with the aim to reduce the required signalling to configure SCells. To achieve this, group signalling relies on the fact that many parameters, even though configured for each SCell, can actually have the same value across different SCells. Therefore, the ASN. <NUM> signalling below (from <NUM> v <NUM>. <NUM>) was introduced to enable the configuration of sCell groups, where multiple serving cells may apply the same configuration if belonging to a given SCell group.

It should be noted that since there is a field for SCG group signalling (sCellGroupToAddModListSCG), this feature can be supported in the SN for both LTE-DC and NE-DC.

Concerning procedures for group signalling, the ones related to addition/modification of SCell groups are performed in <NUM> v15. <NUM> as follows:.

Group signalling for NR was not yet discussed. However, from contributions submitted to RAN2 meetings (References [<NUM>], [<NUM>]), it would be similar to the approach defined for LTE (detailed above). Therefore, the present disclosure assumes that group signalling could be present in TS <NUM> in Release-<NUM> time frame, and it would be similar to the LTE approach.

There currently exist certain challenge(s). Current group signalling is not clear on the interaction between SCell group signalling configuration and Individual SCell configuration. Namely, the following issues are present:.

It is not clear how the UE should verify "Need OR" fields (that should be released if not present) against radioResourceConfigCommonSCell fields configured via both Individual SCell and SCell group signalling. A "Need OR" field is optional, and if a message is received by a UE and the information element/value for the "Need OR" field is absent, the UE should discontinue/stop using/delete any existing value for the field. For instance, after the UE had an SCell configured via group signalling (radioResourceConfigCommonSCell), if it receives another message for delta configuration against this given SCell (i.e. a message for changing the configuration of this SCell), it is not clear whether "Need OR" fields not received in this configuration message should be released or not. The same issue will happen for NR, when NR SCell group signalling is defined, with "Need R" fields.

Since procedures in LTE (and likely also adopted for NR) state that the UE should apply the SCell group configuration for parameters not already configured for its current SCell, current modification of an SCell group configuration cannot be performed. Even though procedures are described for this behaviour in <NUM> v15. <NUM>, those should only be applied for parameters not already configured for a given SCell. This approach can work when adding SCells, since any parameters included in Individual SCell configuration would take precedence over parameters included in SCell group signalling. However, once the UE applies both configurations (single and group SCell one) upon SCell addition, a subsequent change of SCell group configuration may not be effective, since the parameters therein may already be part of UEs current SCell configuration and thus will not be reconfigured according to current behaviour.

Apart from the uncertainty described above on the behaviour between SCell group signalling configuration and Individual SCell configuration, for NR-DC, it is also not clear the interaction between group signalling configuration applied to MCG and group signalling configuration applied to SCG. Therefore, a third issue is described below:.

In LTE-DC, it is possible for the MN to configure separate SCell groups for the MCG and SCG, however, for NR-DC, the MN and SN can configure an SCell group independently. This may cause a collision as both the MN and the SN may configure an SCell group with the same SCell group index comprising of different set of cells associated to the MCG or the SCG.

3GPP contribution "<NPL>, proposes mechanisms for reducing signaling overhead when SCells are configured by grouping SCells according to common characteristics.

Aspects of this disclosure provide a method performed by a wireless device, a method performed by a base station, a wireless device, a base station and a computer program product for handling group signalling of secondary cell, SCell, configuration information as defined in the claims.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:.

It should be noted that the examples below focus on E-UTRA handling (i.e. examples are performed based on <NUM> v15. <NUM>), but similar examples are considered or envisaged also for the NR case (i.e. examples based on <NUM>).

It should also be noted that the term "Individual SCell configurations" (or "individual configuration information") refers to configurations received in a field signalled only for a single SCell in dedicated signalling, e.g. SCellToAddModExt.

For fields in an RRC message, where the absence implies that the corresponding field should be released, the UE should verify whether this field is not present in either a received configuration for an SCell or in a received SCell group signalling. Therefore, this approach can be used when the UE receives both Individual SCell configuration and SCell group configuration (referred to herein as "group configuration information") in the same RRC message. For instance, if the RRC message only includes an Individual SCell configuration and no SCell group configuration, the fields and conditions of the Individual SCell configuration will override any stored configuration (i.e. any field configured with SCell group which is absent in the Individual SCell configuration with "Optional Need OR" will be released).

In another example, if the RRC message only includes a SCell group configuration with some optional "Need OR" fields absent, these parameters will be released.

An example based on <NUM> v15. <NUM> is given below.

In solution <NUM> the UE should remember whether a given parameter was configured via SCell group configuration or Individual SCell configuration.

In one example, parameter A and parameter B are both optional "Need OR", where parameter A is configured with an Individual SCell configuration, and parameter B is configured with a SCell group configuration.

If the UE receives an RRC message which contains only an Individual SCell configuration with parameters A and B absent, the UE will release parameter A, but maintain parameter B.

If the UE receives an RRC message which contains only a SCell group configuration with parameters A and B absent, the UE will release parameter B, but maintain parameter A.

If the UE receives an RRC message which contains only an Individual SCell configuration with parameter A absent, but including parameter B, the UE will release parameter A and replace parameter B with the received value.

If the UE receives an RRC message which contains only a SCell group configuration with parameter B absent, but including parameter A, the UE will release parameter B, but maintain the stored value of parameter A.

If the UE receives an RRC message which contains both an Individual SCell configuration with parameter B and a SCell group configuration with parameter A, the UE will replace both parameters A and B with the received value (since the Individual SCell configuration had parameter A absent, this parameter should be released, but the SCell group configuration contained parameter A and thus that value is used).

The IE RadioResourceConfigCommonSIB and IE RadioResourceConfigCommon are used to specify common radio resource configurations in the system information and in the mobility control information, respectively, e.g., the random access parameters and the static physical layer parameters. Optional need OR fields configured in IE RadioResourceConfisCommon within IE SCellToAddMod are only released if not present in an IE RadioResourceConfisCommon within IE SCellToAddMod. Optional need OR fields configured in IE RadioResourceConfisCommon within IE SCellConfigCommon are only released if not present in an IE RadioResourceConfisCommon within IE SCellConfigCommon.

The IE RadioResourceConfigDedicated is used to setup/modify/release RBs, to modify the MAC main configuration, to modify the SPS configuration and to modify dedicated physical configuration. Optional need OR fields configured in IE RadioResourceConfigDedicated within IE SCellToAddMod are only released if not present in an IE RadioResourceConfigDedicated within IE SCellToAddMod. Optional need OR fields configured in IE RadioResourceConfigDedicated within IE SCellConfigCommon are only released if not present in an IE RadioResourceConfigDedicated within IE SCellConfisCommon.

In this solution, if the UE has been configured with an Individual SCell configuration for an SCell, and the UE in a subsequent RRC message receives an SCell group configuration for the SCell, any configuration received in the SCell group configuration would be overwritten for the specific SCell.

In some embodiments, any parameter with need code "Need OR" absent from the SCell group configuration which was previously configured will be released.

In other embodiments, any parameter with need code "Need OR" absent from the SCell group configuration will be ignored by the UE.

An example based on <NUM> v15. <NUM> is given below.

In other embodiments, the signalling can be extended to include a new indication which indicates whether the SCell group configurations (including behaviour for 'need' codes) will overwrite any stored configuration. If the indication is absent, the UE will only apply configurations for parameters previously configured with SCell group configurations.

In this solution the configuration of SCell group would only be provided for SCell addition case. Even though this may prevent gains from SCell group signalling for delta configuration, it would be an alternative to keep the feature in a low level of complexity while still having considerable gains from it in SCell addition case. Furthermore, this solution <NUM> may be used either with solution <NUM> or <NUM>.

The current definition of an SCell group includes an SCell Group Index where each SCell included is configured with the SCellGroupIndex.

In some embodiments, the SCellGroup configuration can instead be extended to include a list of cells for which the configurations apply to. An example configuration of this can be seen below:
<IMG>.

In another solution that can address both Problem <NUM> and <NUM> described above, field conditions for signalling within SCell group configuration could be made entirely optional - without any further condition. In this manner, only necessary fields are included in SCell group configuration and there would be no need to define in RRC procedures that Individual SCell configuration takes precedence over SCell group configuration. Since all fields would be optional in SCell group configuration, Individual SCell configuration should handle the configuration of all fields in an RRC message where the absence means that the according field should be released. In other words, those field conditions would be checked only against Individual SCell configuration, which thus should include all relevant fields that have such condition.

The IE RadioResourceConfigCommonSIB and IE RadioResourceConfigCommon are used to specify common radio resource configurations in the system information and in the mobility control information, respectively, e.g., the random access parameters and the static physical layer parameters. Fields configured in IE RadioResourceConfisCommon within IE SCellConfigCommon are optional and do not follow the field conditions described in IE RadioResourceConfigCommon.

The IE RadioResourceConfigDedicated is used to setup/modify/release RBs, to modify the MAC main configuration, to modify the SPS configuration and to modify dedicated physical configuration. Fields configured in IE RadioResourceConfigDedicated within IE SCellConfigCommon are optional and do not follow the field conditions described in IE RadioResourceConfigDedicated.

To avoid RRC configuration errors due to joint use of group signalling by MN and SN in NR-DC, the MN and SN can coordinate which SCell group indices can be used by each node, e.g. via inter-node messages, standardised separation. An example is provided below, taking <NUM> v15. <NUM> as a baseline, and considering SCell group signalling for NR would adopt a similar structure as the one for LTE.

Alternatively, an implicit indication can be used, where the same SCell group index is used for both the MCG and the SCG, but the UE maintains independent lists for the different cell groups. An example is provided below, as a possible description of this solution in <NUM>, and considering SCell group signalling for NR would adopt a similar structure as the one for LTE.

"In NR-DC, the UE may receive two independent SCellGroupToAddMod:.

In this case, the UE maintains two independent SCellGroupToAddMod, and independently performs all the procedures in clause <NUM>. <NUM> for each SCellGroupToAddMod, unless explicitly stated otherwise.

In other embodiments, the SCell group index is not introduced, and instead the SCell group configurations include an explicit list of which SCells the configurations apply to, similar to the example in Solution <NUM>.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network <NUM>, network nodes <NUM> and 160b, and WDs <NUM>, 110b, and 110c. in practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node <NUM> and wireless device (WD) <NUM> are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

UE <NUM> may be any UE identified by the <NUM>rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

<FIG> shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

Host computer <NUM> and the connected UEs <NUM>, <NUM> are configured to communicate data and/or signalling via OTT connection <NUM>, using access network <NUM>, core network <NUM>, any intermediate network <NUM> and possible further infrastructure (not shown) as intermediaries.

Wireless connection <NUM> between UE <NUM> and base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE <NUM> using OTT connection <NUM>, in which wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments enable delta signalling of SCell group configurations which reduces the signalling load and/or reduce the complexity of SCell group configuration where delta signalling is not enabled, and thereby provide benefits such as reduced user waiting time and improved SCell group configuration.

In certain embodiments, measurements may involve proprietary UE signalling facilitating host computer <NUM>'s measurements of throughput, propagation times, latency and the like.

<FIG> is a flowchart illustrating a method performed by a wireless device for handling group signalling of SCell configuration information. The method begins at step <NUM> with receiving configuration information for at least a first SCell. The configuration information comprises values for one or more fields in a set of fields. In some embodiments, the configuration information is received in a RRC message. The received configuration information is group configuration information comprising values for the one or more fields that is applicable to a group of SCells that includes the first SCell.

The method shown in <FIG> further comprises a step <NUM> of determining whether to configure the first SCell according to the received configuration information. At step <NUM>, the method comprises configuring the first SCell based on the result of the step of determining.

In some embodiments, the method depicted in <FIG> further comprises a step of utilising radio resources from the configured first SCell. The method may also comprise steps of providing user data and forwarding the user data to a host computer via the first SCell.

In some embodiments, the set of fields comprises a first field, and the first field is a field for which an absence of a value in the received configuration information is to cause a default action in the wireless device to release, discard, delete or stop using a previously-stored value for the first field. In some such embodiments, the received configuration information does not include a value for the first field.

In some of these embodiments, in line with solution <NUM> above, the received configuration information is group configuration information and step <NUM> comprises determining whether the wireless device has a value for the first field for the first SCell obtained from individual configuration information. The individual configuration information comprises values for the one or more fields that is applicable to the first SCell. Step <NUM> also comprises determining whether to perform the default action for the first field based on whether the wireless device has a value for the first field for the first SCell obtained from individual configuration information.

Determining whether to perform the default action may comprise determining that the default action is to be performed if, or only if, the wireless device does not have a value for the first field for the first SCell obtained from the individual configuration information. Otherwise, it is determined that the value for the first field for the first SCell obtained from the individual configuration information is to be maintained.

In some embodiments, step <NUM> further comprises receiving the individual configuration information. In alternative embodiments, the individual configuration information is received prior to receiving the group configuration information.

In some embodiments, in line with solutions <NUM> and <NUM> above, step <NUM> comprises determining that the values for the one or more fields in the received configuration information are to be used for the first SCell in place of any previously-stored values for the one or more fields. In some such embodiments, in accordance with solution <NUM>, the received configuration information does not include a value for the first field, and step <NUM> further comprises either: performing the default action for the first field and releasing, discarding, deleting or stopping using the previously-stored value for the first field; or ignoring the absent value for the first field and maintaining the previously-stored value for the first field for the first SCell.

Optionally, the method of <FIG> can further comprise receiving an indication relating to the received configuration information. This indication indicates whether the received configuration information is to be used to replace previously-stored values for the one or more fields. In some such embodiments, the received configuration information is group configuration information. If in these embodiments the indication is absent, or if the indication indicates that the received group configuration information is not to replace previously-stored values for the one or more fields from individual configuration information, then step <NUM> comprises determining to use a value for a field in the set of fields in the group configuration information if, or only if, the previously-stored value of the field in the set of fields was received in group configuration information.

In alternative embodiments, in line with solution <NUM> above, the wireless device has a stored value for the first field that was previously received in individual configuration information or group configuration information. The individual configuration information comprised values for the one or more fields that are applicable to the first SCell, and the group configuration information comprised values for the one or more fields that are applicable to a group of SCells including the first SCell. In such embodiments, step <NUM> comprises receiving one of individual configuration information and group configuration information. The determining in step <NUM> is based on whether the stored value for the first field was previously received in individual configuration information or group configuration information and whether the received configuration information is individual configuration information or group configuration information. In some of these embodiments, if the stored value of the first field was previously received in individual configuration information and the received configuration information is individual configuration information, it is determined that the default action for the first field is to be performed to release, discard, delete or stop using the previously-stored value for the first field. If, on the other hand, the stored value of the first field was previously received in individual configuration information and the received configuration information is group configuration information, it is determined that the previously-stored value for the first field is to be used. Finally, if the stored value of the first field was previously received in group configuration information and the received configuration information is individual configuration information, it is determined that the previously-stored value for the first field is to be used.

In accordance with solution <NUM> above, in some embodiments the received configuration information is for adding the first SCell as a SCell for the wireless device. The received configuration information may be only for adding the first SCell as a SCell for the wireless device. In these embodiments, the received configuration information does not relate to a SCell that is an existing SCell for the wireless device.

In some embodiments, in line with solution <NUM> above, the group configuration information comprises values for the one or more fields that are applicable to a group of SCells including the first SCell, and the group configuration information further comprises a list of SCells in the group of SCells that the group configuration information applies to. In alternative embodiments, the group configuration information comprises values for the one or more fields that are applicable to a group of SCells, the group configuration information further comprises a first list of SCells in a MCG that the group configuration information applies to, and a second list of SCells in a SCG that the group configuration information applies to. In such embodiments, the first list and the second list may be identified by a same index or by different indices.

In some embodiments, the received group configuration information comprises values for the one or more fields that are applicable to a group of SCells including the first SCell. Each of the fields is an optional field.

<FIG> is a flowchart illustrating a method performed by a base station for handling group signalling of SCell configuration information. The method begins at step <NUM> with sending configuration information for at least a first SCell to a wireless device. The configuration information comprises values for one or more fields in a set of fields. The method further comprises step <NUM> of providing an indication relating to the configuration information to the wireless device. The indication indicates whether the configuration information is to be used to replace previously-stored values for the one or more fields.

Optionally, the method further comprises determining whether the values for the one or more fields in the group configuration information are to replace previously-stored values for the one or more fields from individual configuration information.

In some embodiments, an indication that values for the one or more fields in the group configuration information are not to replace previously-stored values for the one or more fields from individual configuration information is provided by a negative indication, or by an absence of a positive indication.

<FIG> is a flowchart illustrating a method performed by a base station for handling group signalling of SCell configuration information in accordance with solution <NUM> above. The method comprises step <NUM> of sending group configuration information for a group of SCells comprising a first SCell to a wireless device. The group configuration information comprises values for one or more fields in a set of fields. In some embodiments, the group configuration information further comprises a list of SCells in the group of SCells that the group configuration information applies to. Alternatively, the group configuration information may comprise values for one or more fields in a set of fields, where each of the fields is an optional field.

In some embodiments, the method further comprises obtaining user data and forwarding the user data to a host computer or a wireless device via the first SCell.

<FIG> relate to the solutions to problem <NUM> described above.

<FIG> is a flowchart illustrating a method performed by a first network node for handling group signalling of SCell configuration information in DC. This method is not covered by the claims and is included for illustration purpose. The first network node is operating as a MN for DC. The method comprises a step <NUM> of sending a signal to a second network node that is operating as a SN for DC. The signal comprises an indication of one or more indices that can be used by the MN and/or the SN for identifying a group of SCells that can be configured using group configuration information. The group configuration information comprises values for one or more fields that are applicable to a group of SCells.

<FIG> is a flowchart illustrating a method performed by a second network node for handling group signalling of SCell configuration information in DC. This method is not covered by the claims and is included for illustration purpose. The second network node is operating as a SN for DC. The method comprises a step <NUM> of sending a signal to a first network node that is operating as a MN for DC. The signal comprises an indication of one or more indices that can be used by the MN and/or the SN for identifying a group of SCells that can be configured using group configuration information. The group configuration information comprises values for one or more fields that are applicable to a group of SCells. In some embodiments, DC is New Radio-DC.

The signal in <FIG> can be an explicit indication or an implicit indication. In some embodiments, the indication indicates a range of indices that can be used by the MN and/or the SN. In some such embodiments, the indication indicates a respective range of indices that can be used by the MN and the SN. In some embodiments, the indication indicates an index to be used for both a MCG managed by the MN, and a SCG managed by the SN.

<FIG> is a block diagram of a wireless device <NUM> according to various embodiments. The wireless device <NUM> comprises processing circuitry (or logic) <NUM>. The processing circuitry <NUM> controls the operation of the wireless device <NUM> and can implement the methods described herein in relation to a wireless device <NUM>. The processing circuitry <NUM> can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the wireless device <NUM> in the manner described herein. In particular implementations, the processing circuitry <NUM> can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the methods described herein in relation to wireless devices.

In some embodiments, the wireless device <NUM> may optionally comprise a communications interface <NUM>. The communications interface <NUM> can be for use in communicating with other nodes, for example a base station or other network node.

For example, the communications interface <NUM> can be configured to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar. The processing circuitry <NUM> may be configured to control the communications interface <NUM> to transmit to and/or receive from other nodes requests, resources, information, data, signals, or similar.

Optionally, the wireless device <NUM> may comprise a memory <NUM>. In some embodiments, the memory <NUM> can be configured to store program code that can be executed by the processing circuitry <NUM> to perform the methods described herein in relation to wireless devices. Alternatively or in addition, the memory <NUM> can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry <NUM> may be configured to control the memory <NUM> to store any requests, resources, information, data, signals, or similar that are described herein.

<FIG> is a block diagram of a base station <NUM> according to various embodiments. The base station <NUM> comprises processing circuitry (or logic) <NUM>. The processing circuitry <NUM> controls the operation of the base station <NUM> and can implement the methods described herein in relation to a base station <NUM>. The processing circuitry <NUM> can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the base station <NUM> in the manner described herein. In particular implementations, the processing circuitry <NUM> can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the methods described herein in relation to base stations.

In some embodiments, the base station <NUM> may optionally comprise a communications interface <NUM>. The communications interface <NUM> can be for use in communicating with other nodes, for example a wireless device, another base station or other network node.

Optionally, the base station <NUM> may comprise a memory <NUM>. In some embodiments, the memory <NUM> can be configured to store program code that can be executed by the processing circuitry <NUM> to perform the methods described herein in relation to base stations. Alternatively or in addition, the memory <NUM> can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry <NUM> may be configured to control the memory <NUM> to store any requests, resources, information, data, signals, or similar that are described herein.

<FIG> is a block diagram of a first network node <NUM> according to various embodiments. The first network node is not covered by the claims and is described for illustration purpose. The first network node <NUM> comprises processing circuitry (or logic) <NUM>. The processing circuitry <NUM> controls the operation of the first network node <NUM> and can implement the methods described herein in relation to a first network node <NUM>. The processing circuitry <NUM> can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the first network node <NUM> in the manner described herein. In particular implementations, the processing circuitry <NUM> can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the methods described herein in relation to network nodes.

In some embodiments, the first network node <NUM> may optionally comprise a communications interface <NUM>. The communications interface <NUM> can be for use in communicating with other nodes, for example a wireless device, a base station or another network node.

Optionally, the first network node <NUM> may comprise a memory <NUM>. In some embodiments, the memory <NUM> can be configured to store program code that can be executed by the processing circuitry <NUM> to perform the methods described herein in relation to base stations. Alternatively or in addition, the memory <NUM> can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry <NUM> may be configured to control the memory <NUM> to store any requests, resources, information, data, signals, or similar that are described herein.

<FIG> is a block diagram of a second network node <NUM> according to various embodiments. The first network node is not covered by the claims and is described here for illustration purpose. The second network node <NUM> comprises processing circuitry (or logic) <NUM>. The processing circuitry <NUM> controls the operation of the second network node <NUM> and can implement the methods described herein in relation to a second network node <NUM>. The processing circuitry <NUM> can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the second network node <NUM> in the manner described herein. In particular implementations, the processing circuitry <NUM> can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of the methods described herein in relation to network nodes.

In some embodiments, the second network node <NUM> may optionally comprise a communications interface <NUM>. The communications interface <NUM> can be for use in communicating with other nodes, for example a wireless device, a base station or another network node.

Optionally, the second network node <NUM> may comprise a memory <NUM>. In some embodiments, the memory <NUM> can be configured to store program code that can be executed by the processing circuitry <NUM> to perform the methods described herein in relation to base stations. Alternatively or in addition, the memory <NUM> can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry <NUM> may be configured to control the memory <NUM> to store any requests, resources, information, data, signals, or similar that are described herein.

Claim 1:
A method performed by a wireless device for handling group signalling of secondary cell, SCell, configuration information, the method comprising:
receiving (<NUM>) configuration information for at least a first SCell, wherein the configuration information comprises values for one or more fields in a set of fields, wherein the received configuration information is group configuration information and wherein the group configuration information comprises values for the one or more fields that are applicable to a group of SCells including the first SCell, wherein the group configuration information further comprises a list of SCells in the group of SCells that the group configuration information applies to;
determining (<NUM>) whether to configure the first SCell according to the received configuration
information; and
configuring (<NUM>) the first SCell based on the result of the determining (<NUM>).