RRC configuration procedures

Abstract

A method, apparatus, and computer program are described comprising: storing, at a terminal device, a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and determining, by the terminal device, a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

Description

[0001] RRC configuration procedures

[0002] Field

[0003] Example embodiments may relate to terminal devices, networks, network nodes, and methods for determining radio resource control (RRC) procedure delays.

[0004] Background

[0005] A radio access network may instruct a terminal device to change configuration to maintain or enhance communications between the terminal device and the radio access network. Performing this change of configuration may take time. Completion of this change of configuration may be required before other processes may take place. There remains an interest in providing the network with an indication of the time needed for a terminal device to complete a change in configuration.

[0006] Summary

[0007] The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention.

[0008] A first aspect provides a terminal device having at least one processor and at least one memory having instructions stored thereon which, when executed by the at least one processor, cause the apparatus to perform: storing, by the terminal device, a plurality of radio resource control, RRC, modules, including at least a first RRC module; obtaining, by the terminal device, a first delay for activating or deactivating the at least a first RRC module; receiving, at the terminal device, from a network node, an indication that the terminal device is to activate or deactivate the at least a first RRC module; determining, by the terminal device, whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication; and sending, from the terminal device, to the network node, an acknowledgement to the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0009] In some example embodiments sending the acknowledgment comprises sending a positive acknowledgement based on determining that activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0010] In some example embodiments sending the acknowledgement comprises sending anegative acknowledgment based on determining that activation or deactivation of the at least a first RRC module will not be complete within the first delay from reception of the indication.

[0011] In some example embodiments the instructions, when executed by the at least one processor, further cause the apparatus to perform: receiving, at the terminal device, after sending a negative acknowledgment, a retransmission of the indication that the terminal device is to activate or deactivate the at least a first RRC module.

[0012] In some example embodiments the instructions, when executed by the at least one processor, further cause the apparatus to perform: determining, by the terminal device, whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the retransmission of the indication; and sending from the terminal device, to the network node, an acknowledgement to the retransmission of the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the retransmission of the indication.

[0013] In some example embodiments the instructions, when executed by the processor, further cause the apparatus to perform: activating or deactivating the at least a first RRC module according to the received indication.

[0014] In some example embodiments the instructions, when executed by the at least one processor, further cause the apparatus to perform: ignoring at least one scheduling message from the network node scheduling transmission or reception by the terminal device before the activation or deactivation of the at least a first RRC module is completed, based on determining that activation or deactivation of the at least a first RRC module will not be complete within the first delay from reception of the indication.

[0015] In some example embodiments the instructions, when executed by the processor, further cause the apparatus to perform: sending, to the network node, an indication of a second delay for performing activation or deactivation of the at least a first RRC module.

[0016] In some example embodiments the acknowledgement message further comprises an indication of a second delay for performing activation or deactivation of the at least a first RRC module.

[0017] In some example embodiments the second delay is based on at least one of the following:a delay for activating or deactivating the at least a first RRC module estimated by the terminal device; and a delay for activating or deactivating the at least a first RRC module measured by the terminal device.

[0018] In some example embodiments the first delay for activating or deactivating the at least a first RRC module is obtained based on at least one of: a delay stored by the terminal device and corresponding to a standard specification; a delay indicated by capability signaling from the terminal device to the radio access network; a delay received by the terminal device from the radio access network; and a delay reported to the radio access network by the terminal device.

[0019] In some example embodiments the stored plurality of RRC modules further comprises at least a second RRC module; the received indication is an indication that the terminal device is to activate the at least a first RRC module and deactivate the at least a second RRC module; and the first delay is a sum of a third delay, for activating the at least a first RRC module, and a fourth delay, for deactivating the at least a second RRC module.

[0020] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0021] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0022] A second aspect provides a method comprising: storing, by a terminal device, a plurality of radio resource control, RRC, modules, including at least a first RRC module; obtaining, by the terminal device, a first delay for activating or deactivating the at least a first RRC module; receiving, at the terminal device, from a network node, an indication that the terminal device is to activate or deactivate the at least a first RRC module; determining, by the terminal device, whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication; and sending, from the terminal device, to the network node, an acknowledgement to the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0023] In some example embodiments, the second aspect may include any other feature mentioned with respect to the method of the first aspect.

[0024] A third aspect provides a terminal device comprising: means for storing a plurality of radioresource control, RRC, modules, including at least a first RRC module; means for obtaining a first delay for activating or deactivating the at least a first RRC module; means for receiving, from a network node, an indication that the terminal device is to activate or deactivate the at least a first RRC module; means for determining whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication; and means for sending, to the network node, an acknowledgement to the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0025] In some example embodiments, the third aspect may include any other feature mentioned with respect to the method of the first aspect.

[0026] A fourth aspect provides a computer program comprising instructions which, when executed by at least one processor, cause an apparatus to perform: storing a plurality of radio resource control, RRC, modules, including at least a first RRC module; obtaining a first delay for activating or deactivating the at least a first RRC module; receiving, from a network node, an indication that the apparatus is to activate or deactivate the at least a first RRC module; determining whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication; and sending, to the network node, an acknowledgement to the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0027] In some example embodiments, the fourth aspect may include any other feature mentioned with respect to the method of the first aspect.

[0028] A fifth aspect provides a non-transitory computer-readable storage medium having instructions stored thereon which, when executed by at least one processor, cause an apparatus to perform: storing a plurality of radio resource control, RRC, modules, including at least a first RRC module; obtaining a first delay for activating or deactivating the at least a first RRC module; receiving, from a network node, an indication that the apparatus is to activate or deactivate the at least a first RRC module; determining whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication; and sending, to the network node, an acknowledgement to the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.In some example embodiments, the fifth aspect may include any other feature mentioned with respect to the method of the first aspect.

[0029] A sixth aspect provides a terminal device comprising: means for storing radio resource control, RRC, modules; means for receiving, from a network node, at least a first RRC module; and means for, responsive to receiving the at least a first RRC module, sending, to the network node, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0030] In some example embodiments the means for receiving the at least a first RRC module is configured to receive the at least a first RRC module as part of an RRC configuration or RRC reconfiguration message.

[0031] In some example embodiments the means for sending the indication of the delay is configured to send the indication of the delay as part of an RRC configuration complete or RRC reconfiguration complete message.

[0032] In some example embodiments, the terminal device further comprises: means for determining that the activating or deactivating the at least a first RRC module can be performed in parallel with activating or deactivating at least a second RRC module; and means for determining a second delay, based at least in part on the determination, and wherein the second delay is a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module and activate or deactivate the at least a second RRC module, to activation or deactivation of the at least a first RRC module and activation or deactivation of the at least a second RRC module; and means for, responsive to receiving the at least a first RRC module, sending, to the network node, an indication of the second delay.

[0033] In some example embodiments, the terminal device further comprises: means for determining that the activating or deactivating of at least a first RRC module cannot be performed in parallel with activating or deactivating at least a third RRC module; and means for determining a third delay, based at least in part on the determination, and wherein the third delay is a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module and activate or deactivate the at least a third RRC module, to activation or deactivation of the at least a first RRC module and activation or deactivation of the at least a third RRC module;and means for, responsive to receiving the at least a first RRC module, sending, to the network node, an indication of the third delay.

[0034] In some example embodiments, the terminal device further comprises: means for receiving, from the network node, an indication of a set of RRC modules that can be activated or deactivated in parallel.

[0035] In some example embodiments, the terminal device further comprises means for determining the delay based at least in part on any one or more of: the capabilities of the terminal device; an amount of energy stored by the terminal device; and a priority or urgency of communications between the network node and the terminal device.

[0036] In some example embodiments the delay is a total delay, from receipt by the terminal device of an indication that the terminal device is to activate a set of RRC modules comprising the at least one RRC module, to activation of the set of RRC modules, further comprising means for determining the total delay.

[0037] In some example embodiments the means for determining the total delay is configured to determine the total delay based at least in part on at least one of: a determination of which RRC modules of the set can be activated in parallel; a determination of which RRC modules of the set cannot be activated in parallel; the capabilities of the terminal device; an amount of energy stored by the terminal device; and a priority or urgency of communications between the network node and the terminal device.

[0038] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0039] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0040] A seventh aspect provides a method comprising: storing, at a terminal device, radio resource control, RRC, modules; receiving, at the terminal device, from a network node, at least a first RRC module; and responsive to receiving the at least a first RRC module, sending, from the terminal device, to the network node, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first module, to activation or deactivation of the at least a first RRC module.In some example embodiments the at least a first RRC is received as part of an RRC configuration or RRC reconfiguration message.

[0041] In some example embodiments the indication of the delay is sent as part of an RRC configuration complete or RRC reconfiguration complete message.

[0042] In some example embodiments, the method further comprises determining that the activating or deactivating the at least a first RRC module can be performed in parallel with activating or deactivating at least a second RRC module; and determining a second delay, based at least in part on the determination, and wherein the second delay is a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module and activate or deactivate the at least a second RRC module, to activation or deactivation of the at least a first RRC module and activation or deactivation of the at least a second RRC module; and responsive to receiving the at least a first RRC module, sending, to the network node, an indication of the second delay.

[0043] In some example embodiments, the method further comprises determining that the activating or deactivating of at least a first RRC module cannot be performed in parallel with activating or deactivating at least a third RRC module; and determining a third delay, based at least in part on the determination, and wherein the third delay is a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module and activate or deactivate the at least a third RRC module, to activation or deactivation of the at least a first RRC module and activation or deactivation of the at least a third RRC module; and responsive to receiving the at least a first RRC module, sending, to the network node, an indication of the third delay.

[0044] In some example embodiments, the method further comprises receiving, from the network node, an indication of a set of RRC modules that can be activated or deactivated in parallel.

[0045] In some example embodiments, the method further comprises determining the delay based at least in part on any one or more of: the capabilities of the terminal device; an amount of energy stored by the terminal device; and a priority or urgency of communications between the network node and the terminal device.

[0046] In some example embodiments the delay is a total delay, from receipt by the terminal device of an indication that the terminal device is to activate a set of RRC modules comprising the at least one RRC module, to activation of the set of RRC modules, and the method further comprises determining the total delay.In some example embodiments the total delay is determined based at least in part on at least one of: a determination of which RRC modules of the set can be activated in parallel; a determination of which RRC modules of the set cannot be activated in parallel; the capabilities of the terminal device; an amount of energy stored by the terminal device; and a priority or urgency of communications between the network node and the terminal device.

[0047] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0048] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0049] An eighth aspect provides a terminal device having at least one processor and at least one memory having instructions stored thereon which, when executed by the at least one processor, cause the terminal device to perform: storing radio resource control, RRC, modules; receiving, from a network node, at least a first RRC module; and responsive to receiving the at least a first RRC module, sending, to the network node, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first module, to activation or deactivation of the at least a first RRC module.

[0050] In some example embodiments, the eighth aspect may include any other feature mentioned with respect to the method of the seventh aspect.

[0051] A ninth aspect provides a computer program comprising instructions which, when executed by at least one processor, cause an apparatus to perform: storing radio resource control, RRC, modules; receiving, from a network node, at least a first RRC module; and responsive to receiving the at least a first RRC module, sending, to the network node, an indication of a delay, from reception by the apparatus of an indication that the apparatus is to activate or deactivate the at least a first module, to activation or deactivation of the at least a first RRC module.

[0052] In some example embodiments, the ninth aspect may include any other feature mentioned with respect to the method of the seventh aspect.

[0053] A tenth aspect provides a non-transitory computer-readable storage medium havinginstructions stored thereon which, when executed by at least one processor, cause an apparatus to perform: storing radio resource control, RRC, modules; receiving, from a network node, at least a first RRC module; and responsive to receiving the at least a first RRC module, sending, to the network node, an indication of a delay, from reception by the apparatus of an indication that the apparatus is to activate or deactivate the at least a first module, to activation or deactivation of the at least a first RRC module.

[0054] In some example embodiments, the tenth aspect may include any other feature mentioned with respect to the method of the seventh aspect.

[0055] An eleventh aspect provides a network node comprising: means for sending, to a terminal device, at least a first RRC module, wherein the terminal device comprises means for storing radio resource control, RRC, modules; and means for receiving, from the terminal device, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0056] In some example embodiments, the network node further comprises: means for sending, to the terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and means for determining, based on the received indication of the delay and a time of sending the indication that the terminal device is to activate or deactivate the at least a first RRC module, a time at which the activation or deactivation of the at least a first RRC module will be complete.

[0057] A twelfth aspect provides a method comprising: sending, from a network node, to a terminal device, at least a first RRC module, wherein the terminal device comprises means for storing radio resource control, RRC, modules; and receiving, at the network node, from the terminal device, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0058] In some example embodiments, the method further comprises: sending, from the network node, to the terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and determining, by the network node, based on the received indication of the delay and a time of sending the indication that the terminal device is to activate or deactivate the at least a first RRC module, a time at which the activation or deactivation of the at least a first RRC module will be complete.A thirteenth aspect provides a network node having at least one processor and at least one memory having instructions stored thereon which, when executed by the at least one processor, cause the network node to perform: sending, to a terminal device, at least a first RRC module, wherein the terminal device comprises means for storing radio resource control, RRC, modules; and receiving, from the terminal device, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0059] In some example embodiments, the thirteenth aspect may include any other feature mentioned with respect to the method of the twelfth aspect.

[0060] A fourteenth aspect provides a computer program comprising instructions which, when executed by at least one processor, cause a network node to perform: sending, to a terminal device, at least a first RRC module, wherein the terminal device comprises means for storing radio resource control, RRC, modules; and receiving, from the terminal device, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0061] In some example embodiments, the fourteenth aspect may include any other feature mentioned with respect to the method of the twelfth aspect.

[0062] A fifteenth aspect provides a non-transitory computer-readable storage medium having instructions stored thereon which, when executed by at least one processor, cause an apparatus to perform: sending, to a terminal device, at least a first RRC module, wherein the terminal device comprises means for storing radio resource control, RRC, modules; and receiving, from the terminal device, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0063] In some example embodiments, the fifteenth aspect may include any other feature mentioned with respect to the method of the twelfth aspect.

[0064] A sixteenth aspect provides a terminal device comprising: means for storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; means for receiving, from a network node of a radio access network, an indication that the terminal device is to activate or deactivate the at least afirst RRC module; means for, responsive to receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module, activating or deactivating the at least a first RRC module according to the received indication; and means for sending, to the network node, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0065] In some example embodiments the means for receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module is configured to receive the indication via RRC signaling.

[0066] In some example embodiments the means for receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module is configured to receive the indication via medium access control, MAC, control element, MAC CE, signalling.

[0067] In some example embodiments, the terminal device further comprises means for determining the first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first module being activated or deactivated according to the indication.

[0068] In some example embodiments, the terminal device further comprises means for comparing the first delay to a second delay, wherein the means for sending the indication of the first delay to the network node is configured to send the delay based at least in part on the result of the comparison.

[0069] In some example embodiments the second delay is based on any one or more of: a delay stored by the terminal device, corresponding to a standard specification and associated with the activation or deactivation of the at least a first RRC module; a delay associated with the activation or deactivation of the at least a first RRC module indicated by capability signaling from the terminal device to the radio access network; a delay associated with the activation or deactivation of the at least a first RRC module received by the terminal device from the radio access network; and a delay associated with the activation or deactivation of the at least a first RRC module reported to the radio access network by the terminal device.

[0070] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0071] A seventeenth aspect provides a method comprising: storing, at a terminal device a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; receiving, by the terminal device, from a network node of a radio access network, an indication that the terminal device is to activate or deactivate the at least a first RRC module; responsive to receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module, activating or deactivating the at least a first RRC module according to the received indication; and sending, from the terminal device, to the network node, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0072] In some example embodiments the indication that the terminal device is to activate or deactivate the at least a first RRC module is received via RRC signaling.

[0073] In some example embodiments the indication that the terminal device is to activate or deactivate the at least a first RRC module received via medium access control, MAC, control element, MAC CE, signaling.

[0074] In some example embodiments, the method further comprises determining the first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first module and the at least a first module being activated or deactivated according to the indication.

[0075] In some example embodiments, the method further comprises comparing the first delay to a second delay, wherein the means for sending the indication of the first delay to the network node is configured to send the delay based at least in part on the result of the comparison.

[0076] In some example embodiments the second delay is based on any one or more of: a delay stored by the terminal device, corresponding to a standard specification and associated with the activation or deactivation of the at least a first RRC module; a delay associated with the activation or deactivation of the at least a first RRC module indicated by capability signaling from the terminal device to the radio access network; a delay associated with the activation or deactivation of the at least a first RRC module received by the terminaldevice from the radio access network; and a delay associated with the activation or deactivation of the at least a first RRC module reported to the radio access network by the terminal device.

[0077] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0078] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0079] An eighteenth aspect provides a terminal device having at least one processor and at least one memory having instructions stored thereon which, when executed by the at least one processor, cause the terminal device to perform: storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; receiving from a network node of a radio access network, an indication that the terminal device is to activate or deactivate the at least a first RRC module; responsive to receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module, activating or deactivating the at least a first RRC module according to the received indication; and sending to the network node, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0080] In some example embodiments, the eighteenth aspect may include any other feature mentioned with respect to the method of the seventeenth aspect.

[0081] A nineteenth aspect provides a computer program comprising instructions which, when executed by at least one processor, cause a terminal device to perform: storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; receiving from a network node of a radio access network, an indication that the terminal device is to activate or deactivate the at least a first RRC module; responsive to receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module, activating or deactivating the at least a first RRC module according to the received indication; and sending to the network node, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.In some example embodiments, the nineteenth aspect may include any other feature mentioned with respect to the method of the seventeenth aspect.

[0082] A twentieth aspect provides a non-transitory computer-readable storage medium having instructions stored thereon which, when executed by at least one processor, cause an apparatus to perform: storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; receiving from a network node of a radio access network, an indication that the apparatus is to activate or deactivate the at least a first RRC module; responsive to receiving the indication that the apparatus is to activate or deactivate the at least a first RRC module, activating or deactivating the at least a first RRC module according to the received indication; and sending to the network node, an indication of a first delay between receiving the indication that apparatus is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0083] In some example embodiments, the twentieth aspect may include any other feature mentioned with respect to the method of the seventeenth aspect.

[0084] An twenty-first aspect provides a network node comprising: means for sending, to a terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and means for receiving, from the terminal device, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0085] A twenty-second aspect provides a method comprising: sending, from a network node, to a terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and receiving, by the network node, from the terminal device, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0086] A twenty-third aspect provides a network node having at least one processor and at least one memory having instructions stored thereon which, when executed by the at least one processor, cause the network node to perform: sending, to a terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and receiving, from the terminal device, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRCmodule and the at least a first RRC module being activated or deactivated according to the indication.

[0087] A twenty-fourth aspect provides a computer program comprising instructions which, when executed by at least one processor, cause a network node to perform: sending, to a terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and receiving, from the terminal device, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0088] A twenty-fifth aspect provides a non-transitory computer-readable storage medium having instructions stored thereon which, when executed by at least one processor, cause an apparatus to perform: sending, to a terminal device, an indication that the terminal device is to activate or deactivate the at least a first RRC module; and receiving, from the terminal device, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0089] A twenty-sixth aspect provides a terminal device comprising: means for storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and means for determining a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0090] In some example embodiments, the terminal device further comprises: means for activating or deactivating the at least a first RRC module, and determining the first delay based at least in part on a time to complete the activating or deactivating the at least a first RRC module.

[0091] In some example embodiments, the terminal device further comprises: means for determining a second delay; means for comparing the first delay to the second delay; and means for sending, to a network node of a radio access network, based on a result of the comparison, an indication of the first delay.

[0092] In some example embodiments determining the second delay is configured to determine the second delay based on delay data, associated with the activation or deactivation of theat least a first RRC module, stored by the terminal device.

[0093] In some example embodiments the delay data comprises standard specified data, corresponding to delay data stored at the network node.

[0094] In some example embodiments the delay data comprises delays previously indicated to the radio access network.

[0095] In some example embodiments the delay data comprises at least one or more of: delays indicated to the radio access network in capability signalling; and delays reported to the radio access network.

[0096] In some example embodiments the first delay is associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling, and wherein the means for determining the second delay is configured to determine the second delay from delay data associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling.

[0097] In some example embodiments the first delay is associated with activation or deactivation of the at least a first RRC module responsive to medium access control, MAC, control element, MAC CE, signalling, and wherein the means for determining the second delay is configured to determine the second delay from delay data associated with activation or deactivation of the at least a first RRC module responsive to MAC CE signalling.

[0098] In some example embodiments the means for determining the second delay is configured to determine the second delay based on delay data and any one or more of: a number of RRC modules activated with the at least a first RRC module; and a type of module associated with the at least a first RRC module.

[0099] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0100] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0101] A twenty-seventh aspect provides a method comprising: storing, at a terminal device, a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and determining, by the terminal device, a firstdelay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0102] In some example embodiments the method further comprises activating or deactivating the at least a first RRC module, and determining the first delay based at least in part on a time to complete the activating or deactivating the at least a first RRC module.

[0103] In some example embodiments the method further comprises: determining a second delay; comparing the first delay to the second delay; and ending, to a network node of a radio access network, based on a result of the comparison, an indication of the first delay.

[0104] In some example embodiments determining the second delay is based on delay data, associated with the activation or deactivation of the at least a first RRC module, stored by the terminal device.

[0105] In some example embodiments the delay data comprises standard specified data, corresponding to delay data stored at the network node.

[0106] In some example embodiments the delay data comprises delays previously indicated to the radio access network.

[0107] In some example embodiments the delay data comprises at least one or more of: delays indicated to the radio access network in capability signalling; and delays reported to the radio access network.

[0108] In some example embodiments the first delay is associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling, and the second delay is determined from delay data associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling.

[0109] In some example embodiments the first delay is associated with activation or deactivation of the at least a first RRC module responsive to medium access control, MAC, control element, MAC CE, signalling, the second delay is determined from delay data associated with activation or deactivation of the at least a first RRC module responsive to MAC CE signalling.

[0110] In some example embodiments the second delay determined based on delay data and anyone or more of: a number of RRC modules activated with the at least a first RRC module; and a type of module associated with the at least a first RRC module.

[0111] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0112] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0113] A twenty-eighth aspect provides a terminal device having at least one processor and at least one memory having instructions stored thereon which, when executed by the at least one processor, cause the terminal device to perform: storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and determining a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0114] In some example embodiments, the twenty-eighth aspect may include any other feature mentioned with respect to the method of the twenty-seventh aspect.

[0115] A twenty-ninth aspect provides a computer program comprising instructions which, when executed by at least one processor, cause a terminal device to perform: storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and determining a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0116] In some example embodiments, the twenty-ninth aspect may include any other feature mentioned with respect to the method of the twenty-seventh aspect.

[0117] A thirtieth aspect provides a non-transitory computer-readable storage medium having instructions stored thereon which, when executed by at least one processor, cause an apparatus to perform: storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and determining a first delay, from reception by the apparatus of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.In some example embodiments, the thirtieth aspect may include any other feature mentioned with respect to the method of the twenty-seventh aspect.

[0118] Brief Description of the Drawings

[0119] Example embodiments will now be described by way of non-limiting example, with reference to the accompanying drawings, in which:

[0120] Fig. 1 illustrates an example of a communication system to which examples disclosed herein may be applied;

[0121] Fig. 2 is a signalling diagram of a method in accordance with example embodiments; Figs. 3 - 5 are flow diagrams of a methods in accordance with example embodiments; Fig. 6 is a signalling diagram of a method in accordance with example embodiments; Fig. 7 is a flow diagram of a method in accordance with example embodiments;

[0122] Fig. 8 is a schematic diagram of a system that may be used to implement one or more of the example embodiments; and

[0123] Fig. 9 shows tangible media for storing computer-readable code which when run by a computer may perform methods according to example embodiments described herein.

[0124] Detailed Description

[0125] The following embodiments are exemplary. Although the specification may refer to "an", "one", or "some" embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms "first," "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0126] For the purposes of the present disclosure, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).Embodiments described may be implemented in a communication system, such as any of the following radio access technologies (RATs) : World-wide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication system may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0127] As used herein, the term "network device" or "network node" refers to a node in a communication system via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a non-terrestrial network (NTN) node or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0128] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralised unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the centra l / centra I ized unit, CU, (e.g. server, host or node) operationally coupled to the DU, (e.g. a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some embodiments, the DUs may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, Service Data Application Protocol (SDAP) layer and a radio resource control (RRC) layer. Other functional splits are possible too. In practice, any processing task may be performed in either the CU and / or the DU and the boundary where theresponsibility is shifted between the CU and the DU may depend on the applied implementation.

[0129] The term "terminal device" refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and play-back appliances, vehicle-mounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0130] A term "resource", as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g. a physical resource block (PRB), a radio frame, a subframe, a time slot, an OFDM symbol, a subband, a frequency region, a sub-carrier, a beam, etc. The term "transmission" and / or "reception" may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0131] Fig. 1 illustrates an example of a communication system to which examples disclosed herein may be applied. The communication system or a cellular communication system may comprise a network node 110 providing one or more cells, such as cell 100, and a network node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0132] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication system. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprise physical downlink control channel (PDCCH) for transmitting controlinformation and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0133] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0134] In the case of multiple network nodes in the communication system, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes is called Xn interface.

[0135] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication system. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise e.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0136] Modular RRC configuration

[0137] With the advancement of radio communications technology, user equipments (UEs) having diverse UE capabilities and catering to different requirements / use cases were introduced to the market. Different UE types may be intended to satisfy or prioritise different performance metrics. For example, different UEs may be intended to prioritize the provision of high-speed data connectivity, enhanced energy efficiency, or ultra-lowlatency, to suit different use cases. In the 6G era, the range of UE applications with dissimilar characteristics, such as augmented / virtual reality (AR / VR), massive twinning, immersive smart cities, holographic communications, remote surgery, ambient-IoT, and V2X, is expected to grow. It is expected that devices customized for these use cases may be introduced to the market. The identification, interoperability, and coherent management of these various types of UEs would be one of the continuing challenges faced by the telecommunication systems.

[0138] Cellular mobile telecommunication systems are built on top of protocols that control how the data is transmitted between UEs and networks. These protocols are often divided into user plane (UP) and control plane (CP) sections, wherein the user plane is dedicated to the actual task of transmitting user data between a user and the network, the control plane is dedicated to ensuring that the user plane remains operational. The CP may therefore be used to establish the UP, and it is the CP may ensure the uninterrupted functioning of the UP.

[0139] The primary protocol used for the CP in UMTS / LTE / NR is the Radio Resource Control (RRC), whose specifications can be found in 3GPP TS 25.331 (UMTS), TS 36.331 (LTE) and TS 38.331 (NR). The RRC specifications define the mechanisms for setting up the connection, establishing other (UP) protocol layers and reconfiguring their parameters, as well as various procedures intended to maintain UP and CP operations.

[0140] Under the RRC protocol, a radio access network (RAN) may send RRC messages to a UE, and the UE may configure itself according to RRC messages. For example, a RAN may send an RRC reconfiguration message to a UE, indicating changes to the UE configuration (such as setting up, modifying, and / or releasing a radio bearer, a measurement configuration, and / or a secondary cell or a cell group). The RRC reconfiguration message may comprise a set of information elements indicating modifications to a UE configuration.

[0141] While this may allow a RAN to configure a UE, this scheme may result in the same information being communicated to a UE repeatedly in RRC reconfiguration messages. For example, a UE with low mobility (e.g., a UE that spends most of its time in a small group of cells) may receive many identical or similar RRC reconfiguration messages relating to cell specific aspects of the RRC configuration.

[0142] Transmitting / receiving the same information repeatedly may be an inefficient use of energy and radio resources. Additionally, the time taken to receive this information (e.g., the time taken to receive and process a RRC reconfiguration message to determine theconfiguration changes to make) may delay configuration of the UE according to this information, increasing latency.

[0143] A clear modular design for the RRC protocol may enable fast transitions between distinct operational modes such as power saving, MIMO, etc., with a low impact on signaling overhead and delays. Such a design may result in multiple benefits for both the UE and the network, including reduced latency due to the efficient data transmission, lower power consumption and more effective resource utilization.

[0144] In a modular design, aspects of an RRC configuration (such as a physical cell group configuration, serving cell configuration, measurement configuration, etc.) may be associated with respective module IDs. For example, an RRC module may be configured to associate a module ID with a set of information elements (e.g., relating to a physical cell group configuration, serving cell configuration, measurement configuration, radio bearer, etc.)

[0145] These RRC modules (e.g., sets of information elements relating to aspects of an RRC configuration and the associated RRC module IDs) may be indicated to the UE (for example, in an RRC configuration message, to provide the UE with a set of modules, or in an RRC reconfiguration message, to add to, modify, or remove from a set of modules).

[0146] When a UE has a set of stored modules, a RAN may indicate to the UE that it is to modify its RRC configuration (e.g., by adding aspects to the configuration, replacing aspects of the configuration, or releasing aspects from the configuration), by indicating the ID of a module to activate (e.g., by configuring the device according to the RRC module) or deactivate (e.g. by releasing that aspect of the configuration). For example, an RRC module may correspond to a periodic measurement reporting configuration, and activating the RRC module may configure the UE to send the periodic measurement reports, and deactivating the RRC module may release this aspect of the configuration (e.g., so that the UE does not send the periodic measurement reports associated with the RRC module).

[0147] Structure of a modular RRC configuration

[0148] A modular RRC configuration may be designed hierarchically. In a hierarchical RRC structure, higher-level RRC modules comprise lower-level RRC modules. For example, in some hierarchical RRC structures, the highest-level layer may comprise RRC profiles, with RRC profiles corresponding to alternative UE configurations. RRC profiles may be defined in terms of module IDs of lower-level RRC modules, which may in turn be defined in termsof information elements and / or IDs of even lower-level RRC modules (which themselves may be defined in terms of information elements and / or RRC module IDs).

[0149] An RRC profile in a modular RRC configuration may therefore correspond to a tree-like hierarchy of RRC modules. This allows for a comprehensive and organized representation of the RRC configuration.

[0150] A non-hierarchical RRC structure is also possible. In a non-hierarchical RRC structure, an RRC configuration may be defined in terms of IDs of individual feature-based modules (e.g., rather than the ID of an RRC profile). Each module may correspond to or represent a specific feature or functionality (e.g. without hierarchical dependencies).

[0151] In some cases, an RRC configuration may have multiple layers (e.g., some RRC modules may be defined in terms the IDs of other RRC modules), without the RRC configuration having an associated profile ID (e.g., the highest-layer is not necessarily an RRC profile).

[0152] By storing an RRC module at the UE, and associating that RRC module with an ID, the network can use the ID to indicate to the UE that it is to configure itself according to the module. This may reduce the size of the message used to indicate the configuration change (e.g., the configuration aspects to change may be indicated using the ID, rather than component information elements). This reduced message size may reduce signaling overhead, particularly in cases in which the UE would otherwise receive the same RRC reconfiguration message repeatedly.

[0153] This reduced size may also make using lower layer signaling (e.g., LI signaling, MAC CE or L2 signaling, rather than RRC L3 signaling) to indicate changes more practical, which may also reduce latency.

[0154] In some examples, an RRC configuration may comprise RRC configuration threads (RCT). Each RCT may be organized using configuration components that are organized "horizontally" and "vertically". A "horizontal" component may comprise configuration information elements that are independent of the bearer being used by the UE for e.g., MAC configuration which may be common for a given set of cells (or a cell group). The "vertical" components may be organized into SRB, DRB, Cell Specific Configuration parameters, etc.

[0155] The network can configure one or more RCTs at the same time, where the resultant effect of these RCTs determines the RRC configuration of the UE. In examples, the network canactivate or deactivate an RCT using L1 / L2 signaling (e.g., via MAC CE) or using L3 signaling (e.g., via RRC signaling). An RCT may be modified by switching the corresponding IDs for the configuration components (e.g., module IDs). The segregation of an RRC Profile into smaller RRC threads may make it easier to organize the different RRC information elements and categorize them for each service type.

[0156] RRC procedure delay assumption

[0157] A RAN (e.g., decision making nodes of a RAN) may assume that some UE procedures will be performed within a certain time (within a certain delay). For example, the RAN may assume that, from receipt of an RRC configuration or reconfiguration message, certain aspects of the configuration will be applied within a specified time of the UE receiving that message (e.g., this assumption may be based on an assumption that the UE complies with a relevant standard).

[0158] One example delay may be the delay, from receipt by a UE of an RRC message indicating that the UE is to switch its active bandwidth part (BWP) or change a parameter of its active BWP, until the UE is ready to send (or receive) transmissions (e.g., on the physical downlink shared channel, PDSCH, physical downlink control channel, PDCCH, or physical uplink shared channel, PUSCH).

[0159] This network assumption / UE performance requirement may be expressed as the time (e.g., in milliseconds) from the end of reception of the network -> UE message on the UE physical layer up to the time at which UE shall be ready for the reception of uplink grant for the UE -> network response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronization).

[0160] If the UE does not require the full time allowed by the assumed delay to configure the UE according to the RRC message, this may introduce unnecessary latency (e.g., a UE may be highly capable in principle, but the network and UE may be unable to utilize those capabilities to reduce this latency).

[0161] If the UE does require more time than this, the resources of the UL grant may effectively be wasted on a UE that cannot use them (e.g., because it has not finished configuring itself to use them). More generally, this UE behavior (of slow configuration) may be unexpected, leading to unexpected or undesirable results.Therefore, increasing the assumed delay may make compliance (with a radio standard / the network's assumption) easier, and reduce the chance of non-compliant behavior, while reducing the assumed delay may reduce latency (but increase the difficulty of complying with the network's assumptions).

[0162] It may be desirable for low capability (e.g., low processing power / low battery) devices to have access to the network, so simply reducing the delay assumed by the network may be undesirable.

[0163] It may be desirable for the network to obtain delay information based on which it can assume a more appropriate delay. It may be desirable for the network to obtain delay information that is more specific to an operation that is to be carried out. It may be desirable for the network to obtain delay information that is more specific to a UE (e.g., specific to a particular UE, or specific to a particular category of UE).

[0164] This may allow for the network's assumptions regarding the delay of certain RRC configuration related operations to be adapted to different devices or operations (e.g., allowing for a small assumed latency for higher capability UEs and / or less demanding tasks, while still providing for larger latencies for lower capability UEs and / or more demanding tasks).

[0165] The delay from the UE receiving a downlink message to the UE being ready to receive an uplink grant is discussed above. More generally, in some examples the network may assume that, after a delay from receipt by a UE of a message, instruction, or indication causing a change in RRC configuration, the change in RRC configuration will be complete (e.g., that the UE will function according to the changed configuration).

[0166] In view of the above, it may therefore be desirable to provide for RRC module based updates to RRC configurations, provide the network with information on delays in updating RRC configurations, and / or provide the network with information on delays in performing module based updates to RRC configuration.

[0167] In example embodiments discussed herein, specific RRC processing requirements may be defined for a message for changing only a specific module (or modules) within the RRC configuration. Specified delay requirements may be defined that may change according to the UE type as well as the content of the specific modules. For example, a network node may be configured with initial delay requirements, which may be updated based on information / indications obtained by the network. A network node may determine an initialdelay requirement for updating an RRC configuration based on the specific module updated, a property or category of said module, the UE, or a property or category of said UE.

[0168] In some examples, it may be useful for the UE to have access to delay requirements generally, or delay requirements relevant to the UE (e.g., if the delay requirements vary based on UE type).

[0169] In example embodiments, signaling is provided, enabling a UE to indicate delay behavior (e.g. which may be different from a network node's initial delay requirements). This may, for example, allow the network to account for the high capabilities of a UE (e.g., when scheduling an UL or DL transmission after indicating to the UE that it is to change configuration).

[0170] Some example embodiments combine one or more of the following:

[0171] 1. A specific RRC processing requirement (i.e., permitted delay) may be defined for a message that causes a UE to configure (i.e., activate) a specific module (e.g., only that module) within the RRC profile configuration.

[0172] 2. RRC processing requirements may vary for different UE types, i.e. the processing requirements for changing a particular module may be fixed for a given UE, but the processing delay requirements may have different values for different UE types.

[0173] 3. Configuration (i.e., activation) of specific RRC component modules could cause different delays depending on the parameter configuration contained within the module and the effort needed by a UE to configure the parameter setup.

[0174] 4. The difficulty of configuring (i.e., activating) specific component modules may be different for different UE types (e.g., the processing requirements may be based on a UE type and specific component module).

[0175] 5. A UE may indicate to network that it can support different processing delay than indicated by the default requirements for its type for each module: for example, the UE may indicate the delay requirements for some or all component modules as a response to the network when a new RRC profile / set of RRC modules is provided by the network to the UE , and / or when the network signals that the UE is to change a specific RRC module of the RRC profile / set of modules.

[0176] 6. A scalable mechanism may be used for informing activation delay for multiple component modules.

[0177] 7. If RRC modules are arranged as threads (e.g., which make up a full RRC profile), the delay for configuring a RRC thread (RCT) may be specified (e.g., an initial delay may be preconfigured / specified in a standard, and / or the UE may indicate a delay).In general, a UE indicated delay may be shorter, the same as or longer than an initial / preconfigured / standardized delay to accommodate different types of UEs and to support signaling delays associated with specific RRC component modules to the network.

[0178] Aspects disclosed herein consider specifying (e.g., in a standard specification) the delay for changing RRC component modules (e.g., by activating or deactivating an RRC module), which could be lower than that for changing the whole RRC profile. For a specific RRC configuration change message, the total delay could depend on the number of configuration modules that would be changed.

[0179] A (specified maximum or actual) delay could vary depending on the UE or UE type. For example, UE type 1 could complete activation of module A within 2ms but take 3ms for activation of module B. However, UE type 2 could take 3ms for activation of module A but could complete activation of module B within 2ms.

[0180] UEs, or some UEs, may be capable of activating modules (or some modules) in parallel, thereby completing the configuration within a shorter time. Some UEs may activate modules (or some modules) sequentially causing an additional delay. In some example embodiments, the network may indicate to UEs which modules could be activated parallelly if the UE has such capability and which modules to activate sequentially (e.g., due to interlinked functionality) when providing a modular RRC configuration to the UE.

[0181] In some examples, when a UE is first configured with RRC modules (e.g., via an RRC configuration message), the UE can indicate to the network a delay for configuring each RRC module with which it is configured, and / or a delay for configuring each component module in an RRC profile with which it is configured. The UE may indicate the delays to the network (e.g. in a list comprising the delays and respective RRC module IDs).

[0182] In some examples, the UE indicates a delay considering a switch from a current configuration (e.g. the delay for activating a given module accounting for other modules presently being active or inactive). Additionally or alternatively, in some examples the UE provides an absolute delay when the module is activated in isolation. In some examples, the UE provides the total delay for the activation of all the component modules of an RRC profile while also considering the possible parallel activation of modules (e.g., depending on UE specific performance capabilities).

[0183] Changing active RRC modulesIn some examples, a message may change component modules of an RRC profile. That is, the UE may receive a message indicating that RRC modules should be added to or removed from an RRC profile. For example, the message may indicate the ID of the RRC profile, a list of IDs of component RRC modules of the RRC profile to remove, and / or a list of IDs of RRC modules to add to the RRC profile. In some examples the RRC modules to add to the profile are already stored on the UE.

[0184] The RRC profile having the changed modules may in some examples be an active RRC profile. Changing a module of an active RRC profile may therefore correspond to activating and / or deactivating modules.

[0185] In the case of a modular approach to RRC that does not use RRC profiles (e.g., a set of RRC modules is considered active, but RRC modules are not organized into profiles), RRC modules may also be activate and / or deactivated (e.g., rather than activating or deactivating an RRC profile).

[0186] A message may be defined for commanding a UE to change the active modules.

[0187] In some examples, the message may be referred to as an RRCModuleChange message, and may have the following properties:

[0188] Signalling radio bearer: SRB1

[0189] RLC-SAP: AM

[0190] Logical channel: DCCH

[0191] Direction: Network to UE

[0192] In some examples with a profile based modular RRC structure, the RRCModuleChange message may comprise at least one or more of the following:

[0193] • a list of (at least one) RRC profile ID(s), and, for respective RRC profile IDs, respective lists of (at least one) RRC module IDs of RRC modules to add to the RRC profile corresponding to the RRC profile ID; and

[0194] • a list of (at least one) RRC profile ID(s), and, for respective RRC profile IDs, respective lists of (at least one) RRC module IDs of RRC modules to remove from the RRC profile corresponding to the RRC profile ID.

[0195] Where an RRC profile to which an RRC module is to be added or removed is the active RRC profile (i.e., the profile according to which the UE is configured), the UE may configure thedevice according to the updated RRC profile (e.g., by configuring the device according the RRC modules added to the active RRC profile, and / or by configuring the device based on the removal of the RRC modules removed from the active RRC profile).

[0196] A modular RRC structure does not necessarily maintain RRC profiles. For example, a UE may be configured according to a list of RRC modules (e.g., without those modules being associated with a particular RRC profile ID).

[0197] An RRCModuleChange message may in some examples comprise at least one or more of the following:

[0198] • a list of RRC module IDs of RRC modules to activate; and

[0199] • a list of RRC module IDs of RRC modules to deactivate.

[0200] In some examples, the UE may indicate that it has completed an RRC module change (e.g., an RRC module change prompted by an RRCModuleChange message as discussed above). This indication may be performed using a message. In some examples, the message may be referred to as an RRCModuleChangeComplete message, and may have the following properties:

[0201] Signalling radio bearer: SRB1

[0202] RLC-SAP: AM

[0203] Logical channel: DCCH

[0204] Direction: UE to Network

[0205] In some examples, the RRCModuleChangeComplete message may comprise at least one or more of the following :

[0206] • a total aggregated delay for activating the RRC modules activated responsive to the RRCModuleChange message;

[0207] • a total aggregated delay for activating the RRC modules of an RRC profile updated by an RRCModuleChange message; and

[0208] • a list of IDs of (at least one) module activated responsive to the RRCModuleChange message, and respective delays for activating modules.

[0209] Using the indicated delays, the network may factor the delays into module activation decisions (e.g., when communicating with delay-sensitive UEs).

[0210] RRC processing delaysAn RRC message for RRC profile component RRC module configuration (or for a change of active modules more generally), such as the RRCModuleChange message above, may be a different to a message changing a full RRC profile. A baseline or standard specified delay for performing the module change(s) of an RRCModuleChange message may therefore be different to a baseline or standard specified delay for performing a switch between two RRC profiles.

[0211] Further, in a configuration in which RRC modules are arranged in RRC threads (e.g., at least one RRC module ID per RRC thread), which in turn combine to form a full RRC profile, changing an RRC thread (e.g., activating or deactivating an RRC thread), or multiple active RRC threads, may be performed responsive to a different message to a message changing a full RRC profile. A baseline or standard specified delay for performing this change may therefore be different to a baseline or standard specified delay for performing a switch between two RRC profiles.

[0212] Table 1 below shows example delays associated with different messages changing aspects of a modular RRC configuration.

[0213] Table 1 :

[0214] > >

[0215]

[0216] > >

[0217]

[0218] In table 1, Nmod is a number of RRC modules changed as a result of an RRC message (e.g., a number of modules activated, or a number of modules deactivated, or total number of activations and deactivations). Tmodact refers to a baseline module change time (e.g., a module change time derived from or indicated by UE capability information). In some examples, a calculation comprising Tmodact may be used when UE capability information is available an includes Tmodact, and the calculation of the preceding row may be used when UE capability information including Tmodact is not available.

[0219] Ntrd is a number of RRC threads changed (e.g., a number of threads activated, or a number of threads deactivated, or a total number of thread activations and deactivations). Ttrdact refers to a baseline thread change time (e.g., a thread change time derived from or indicated by UE capability information).

[0220] Calculations of table 1 provide a way for the network to determine delays of RRC procedures. Performing an RRC reconfiguration may be slower than performing an RRC profile change, but may allow the network to configure a UE with new modules (i.e., modules that are not currently stored on the UE). An RRC module change may be determined to be faster than an RRC profile change (e.g., depending on the number of modules changed). The assumed delay for some procedures (or, in some examples, all procedures) may be based on UE capability information, e.g., if it is available. UE capability information may therefore be one way for a UE to indicate whether it can perform RRC operations such as the above faster or slower than a default value (e.g., by indicating a higher or lower Tmodact and / or Ttrdact).

[0221] While the network may use information from this table to determine UE delays, and make decisions regarding RRC procedures, the UE may in some examples use information from this table (e.g. information from a subset of this table). For example, the UE may perform calculations according to this table to compare a delay that the UE observes in practice to a delay that the network may assume based on this table (e.g., and indicate the observed delay to the network based on the comparison).The values and calculation methods shown in table 1 are examples. For example, the delay value for a single RRC module change may be larger or smaller than 2ms, the delay value for an RRC reconfiguration may be larger or smaller than 10ms, etc.

[0222] Additionally, or alternatively, changing different segments / parts of an RRC configuration may be associated with different delays. Changing a module associated with a particular segment may therefore be associated with a different delay to changing a module associated with a different segment. Table 2 below illustrates how delays for module changes associated with different segments may be calculated differently.

[0223] > >

[0224]

[0225] In some examples, the delay associated with changing a module associated with a segment of the RRC configuration, could be based on a UE indication, such as UE capability information (e.g., the delays in each row could respectively be based on a UE capability derived Tphyiscallcellgroupconfigurationact, Tservingcellconfigurationact, and Tmeasurementconfigurationact).

[0226] In some examples, standard delay values for module changes could be different to those shown in table 2. For example, the delay value for an RRC module change (physical cell group configuration) could be longer or shorter than 4ms. Table 2 shows that RRC module changes affecting different segments of an RRC configuration may have different associated standard delay values.

[0227] Additionally or alternatively, module activations and / or deactivations can be conducted (e.g., indicated) via medium access control (MAC) control elements (MAC CEs). In some examples, delays for module changes via MAC CE may be calculated separately fromdelays for module changes indicated via RRC signaling. Table 3 below shows examples of delays associated with MAC CE signaled RRC module (or thread) changes.

[0228] > >

[0229]

[0230] The values and calculation methods shown in table 3 are examples. For example, the delay value for an RRC thread change may be larger or smaller than 3ms.

[0231] In the absence of a delay value, the network may refer to some default delay value. For example, if the network has not obtained a delay value from the UE for activating (or deactivating) a specific module, the network may rely on a delay value derived from UE capabilities. For example, the network could obtain a delay value based on an explicit delay value capability (e.g., a specific capability listing an RRC module switching delay), or derive the delay value from a different capability, such as a UE type. In other examples, a default delay value could be the same regardless of UE capabilities.

[0232] For an RRC configuration message containing multiple RRC component modules, an estimate of the delay can be made by aggregating the delay considering the number of modules to be changed. The actual value could be different from the estimation due to the faster / slower activation of certain modules by certain UE types and / or due to the parallel activation of multiple modules by certain high performance UEs. In some examples it may be impractical to include delay information for each particular RRC component module that the network may decide to store on the UE in capability information, so in some examples it may be useful to permit a UE to indicate to the network delays for activating (or deactivating) modules.

[0233] Additionally, a UE may perform a module activation slower if it deems it to be less urgent or if the UE needs to save power by reducing its operational speed. In this scenario the UE could indicate that to the NW with the response to component configuration request.Therefore, additionally or alternatively to the above-described options of determining module (and thread) change delays based on standard specified / preconfigured defaults and UE capability information, the delay for activating (or deactivating) a module may be indicated to the network by the UE.

[0234] Fig. 2 is a signaling diagram of a method in accordance with example embodiments, designated generally by the reference numeral 200. Method 200 comprises signaling between a terminal device 210 (e.g., such as a UE) and a RAN node 220 (e.g., a base station such as a gNB, a distributed unit of a distributed base station, such as a gNB DU, or a centralized unit of a distributed base station, such as a gNB CU).

[0235] Method 200 starts at step 232. At step 232, terminal device 210 is in connected mode (e.g., connected to RAN node 220).

[0236] At step 234, RAN node 220 sends an RRC configuration message to terminal device 210. In an example with a hierarchical, profile based RRC structure, this RRC configuration message configures RRC profiles. The message configures 2 RRC profiles, Profile 1 and Profile 2. The network informs the UE to activate RRC profile 1. The message may indicate the component RRC modules of profile 1 and profile 2. The message may include the component RRC modules of profile 1 and profile 2. The component modules may be indexed so that the modules can be referred to by the module IDs.

[0237] Additionally, in some examples the modules within an RRC profile may be arranged in multiple RRC threads (RCTs).

[0238] In an example without an RRC profile based structure, the RRC configuration message may indicate a set of active RRC modules according to which terminal device 210 should be configured. In some examples, the message may include the RRC modules to be activated. In some examples, the message may include further RRC modules (e.g., for later activation). The component modules may be indexed so that the modules can be referred to by the module IDs.

[0239] At step 236, terminal device 210 sends an RRC configuration complete message to RAN node 220.

[0240] In an example with a hierarchical, profile based RRC structure, this RRC configuration complete message may be sent with an indication of a delay for switching profiles (e.g., from RRC profile 1 to RRC profile 2). The delay may be a delay from receipt of a messageindicating that the terminal device is to switch RRC profile, to the terminal device being configured according to an RRC profile that it is switched to. In some examples, this message may be sent with indications of delays for activating each of the component RRC modules of the RRC profiles (e.g., a delay from receipt of an indication that terminal device 210 is to activate an RRC module to the terminal device being configured according to the RRC module).

[0241] If the profiles are arranged as RTCs terminal device 210 may indicate the delay to activate each RCT.

[0242] In an example without an RRC profile based structure, the RRC configuration complete message may be sent with an indication of the delay for activating RRC modules received at step 234.

[0243] In examples, steps 234 - 236 may be carried out independently of steps 240 - 252.

[0244] At step 238, RAN node 220 decides to configure additional RRC modules to terminal device 210 (e.g., so that they may be activated later by indicating respective RRC module IDs).

[0245] At step 240, RAN node 220 sends an RRC reconfiguration message to terminal device 210.

[0246] RRC modules may be sent to terminal device 210 and associated with RRC module IDs so that the modules may be activated and / or added to RRC profiles.

[0247] In an example with a hierarchical, profile based RRC structure, this RRC reconfiguration message may additionally indicate RRC modules to add to or remove from RRC profiles (e.g., the active RRC profile or inactive RRC profiles).

[0248] In examples, this RRC reconfiguration message may indicate RRC modules to activate or deactivate.

[0249] At step 242, terminal device 210 stores the additional RRC modules.

[0250] At step 244, terminal device 210 sends an RRC reconfiguration complete message to RAN node 220, indicating a delay for activating the RRC modules received at step 240.

[0251] In examples, steps 238 - 244 may be carried out independently of steps 234 - 238 and steps 246 - 252.At step 246, RAN node 220 determines to activate RRC modules and / or deactivate RRC modules. RAN node 220 may assume an activation delay, based on a preconfigured (e.g., standardized) delays and / or terminal device capability information, or previous terminal device indications of delays for modules (e.g., received at step 236 or 244).

[0252] In the case of an RRC profile based RRC configuration, activating modules may comprise adding modules to the active RRC profile, and removing modules may comprise removing modules from the active profile, and configuring the terminal device according to the resulting changed active RRC profile.

[0253] In the case of a non-profile based RRC configuration, activating modules may comprise configuring the terminal device according to the activated RRC modules. Deactivating RRC modules may comprise configuring the terminal device according to a set of RRC modules that does not include the deactivated RRC modules.

[0254] In some cases, RAN node 220 may determine to use MAC CE based signaling to indicate the module change. The RAN node may in some examples determine a delay for a MAC CE based module change, e.g., based on preconfigured information (e.g., standardized or terminal device capability information derived delays for MAC CE indicated module changes) or other information previously provided by the terminal device (e.g., the terminal device 210 may provide delays for MAC CE based activation at step 236 or 244).

[0255] At step 248 RAN node 220 sends an RRC module change message with the module IDs of the modules to activate and / or deactivate (additionally, or alternatively, RAN node 220 could indicate that the terminal device is to activate a RCT.) In the case of an RRC profile based RRC configuration, the RAN node may indicate lists of RRC modules to add to or remove from a respective RRC profiles, with additions to and removals from the active RRC profile corresponding to activations and deactivations. In the case of a non profile based RRC configuration, the RRC module change message may indicate RRC modules to activate and / or deactivate.

[0256] In some examples, this information may be indicated via DCI or corresponding MAC CE based signaling.

[0257] In examples using MAC CE based signaling, terminal device 210 may respond with an acknowledgement message.At step 250, terminal device 210 activates and / or deactivates the modules as indicated. Terminal device 210 may determine the time (delay) required to perform the indicated activations and / or deactivations, individually and / or in total.

[0258] Step 252, terminal device 210 sends an RRC module change complete to the RAN node. In some examples, this message includes the determined total delay and / or the delays for the individual module activations / deactivations. In some examples, terminal device 210 may send these delays based on the delay being different from a previously sent delay (e.g., at step 236 or 244), or other network assumed delay (e.g., a UE capability and / or preconfigured specification-based delay), or based on a size and / or direction of the difference.

[0259] Step 252 is optional if step 248 comprises a MAC CE based indication. In some examples, at step 252, terminal device 210 sends a MAC CE based confirmation. In some examples, this confirmation comprises a total delay and / or delays for individual module activations.

[0260] Fig. 3 is a flow diagram of a method in accordance with example embodiments, designated generally by the reference numeral 300. Method 300 may be performed by a terminal device, such as terminal device 210 (e.g., such as a UE).

[0261] At step 310, the terminal device stores radio resource control, RRC, modules.

[0262] At step 320 the terminal device receives, from a network node, at least a first RRC module.

[0263] At step 330 responsive to receiving the at least a first RRC module, the terminal device sends, to the network node, an indication of a delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first module, to activation or deactivation of the at least a first RRC module.

[0264] By indicating a delay for activating received RRC modules to a network node, the approach to delay requirements can be more flexible. By indicating a delay for a particular RRC module, latency introduced by waiting for the completion of an RRC module change procedure may be less limited by the delay of the slowest RRC module change that the network node might encounter. Further, as UEs may indicate different delays, it may be possible to benefit from lower delay times for higher capability UEs, without preventing lower capability UEs from accessing the network due to having higher delay times.In some example embodiments, the at least a first RRC module is received as part of an RRC configuration or RRC reconfiguration message (or via RRC signaling more generally). In some examples, the at least a first RRC module is received via MAC CE signaling.

[0265] In some example embodiments, the indication of the delay is sent as part of an RRC configuration complete or RRC reconfiguration complete message (or via RRC signaling more generally). In some examples, the indication of the delay is sent via MAC CE signaling.

[0266] In some example embodiments, the method further comprises a step of determining that the activating or deactivating the at least a first RRC module can be performed in parallel with activating or deactivating at least a second RRC module. The method may further comprise a step of determining a second delay, based on the activating or deactivating of the first RRC module being performable in parallel with activating or deactivating the second RRC module. The second delay may be a delay from receiving an indication to activate or deactivate the first RRC module, and activate or deactivate the second RRC module, to completion of the indicated activation(s) and / or deactivation(s). The method may further comprise sending an indication of the second delay to the network node.

[0267] By determining a delay accounting for parallel activation and / or deactivation of the RRC modules, UE may indicate to the network a delay that utilizes parallel activation capabilities.

[0268] In some example embodiments, the UE may determine a delay accounting for parallel activation or deactivation of two modules not being possible / based on serial activation or deactivation being required.

[0269] In some example embodiments, the method further comprises receiving, from the network node, an indication of a set of RRC modules that can be activated or deactivated in parallel.

[0270] In some example embodiments, the method further comprises determining the delay based at least in part on any one or more of:

[0271] the capabilities of the terminal device;

[0272] an amount of energy stored by the terminal device; and

[0273] a priority or urgency of communications between the network node and the terminal device.

[0274] Providing terminal devices with the ability to indicate delays that are based on the presentcircumstances, such as a need for energy saving or a priority or urgency of communications between the network node and terminal device may allow for lower latency when necessary, without burdening other devices with strict delay requirements.

[0275] In some example embodiments, the delay is a total delay, from receipt by the terminal device of an indication that the terminal device is to activate a set of RRC modules comprising the at least one RRC module, to activation of the set of RRC modules, and the method further comprises determining the total delay.

[0276] In some example embodiments the total delay is determined based at least in part on at least one of:

[0277] a determination of which RRC modules of the set can be activated in parallel; a determination of which RRC modules of the set cannot be activated in parallel; the capabilities of the terminal device;

[0278] an amount of energy stored by the terminal device; and

[0279] a priority or urgency of communications between the network node and the terminal device.

[0280] In some example embodiments, activating an RRC module comprises configuring the terminal device according to the RRC module.

[0281] In some example embodiments, deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0282] A method corresponding to method 300 may be carried out at a network node.

[0283] In some example embodiments, the network node may determine, based on the indicated delay and a time of reception by the terminal device of an indication to activate or deactivate at least a first RRC module, a time at which or by which the indicated activation or deactivation of the at least a first RRC module will be complete.

[0284] Fig. 4 is a flow diagram of a method in accordance with example embodiments, designated generally by the reference numeral 400. Method 400 may be performed by a terminal device, such as terminal device 210 (e.g., such as a UE).

[0285] At step 410, a terminal device stores a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module.At step 420, the terminal device receives, from a network node of a radio access network, an indication that the terminal device is to activate or deactivate the at least a first RRC module.

[0286] At step 430, responsive to receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module, the terminal device activates or deactivates the at least a first RRC module according to the received indication.

[0287] At step 440, the terminal device sends to the network node, an indication of a first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first RRC module and the at least a first RRC module being activated or deactivated according to the indication.

[0288] By sending to the network node an indication of a delay between receiving an indication that the terminal device is to perform an activation or deactivation of an RRC module, and activation or deactivation of said RRC module, the terminal device may provide the network with accurate delay information for the activation or deactivation, which may facilitate better decisions at the network (e.g., facilitating lower latency scheduling).

[0289] In some example embodiments, the indication that the terminal device is to activate or deactivate the at least a first RRC module is received via RRC signaling. In some example embodiments, the indication that the terminal device is to activate or deactivate the at least a first RRC module is received via MAC CE signaling.

[0290] In some example embodiments, the method further comprises a step of determining, by the terminal device, the first delay between receiving the indication that the terminal device is to activate or deactivate the at least a first module being activated or deactivated according to the indication.

[0291] In some example embodiments, the method further comprises a step of comparing the first delay to a second delay, wherein the indication of the first delay is sent to the network node based at least in part on the result of the comparison.

[0292] By comparing the first delay to another delay, such as a delay corresponding to the delay available to the network node, the terminal device may determine whether the second delay is the same as or close to the first delay. If the first delay is indicated based on a difference of degree of difference from the delay assumed by the network, unnecessary signaling may be avoided if the delay is the same or sufficiently similar.In some example embodiments, the second delay is based on any one or more of:

[0293] • a delay stored by the terminal device, corresponding to a standard specification and associated with the activation or deactivation of the at least a first RRC module;

[0294] • a delay associated with the activation or deactivation of the at least a first RRC module indicated by capability signalling from the terminal device to the radio access network;

[0295] • a delay associated with the activation or deactivation of the at least a first RRC module received by the terminal device from the radio access network; and

[0296] • a delay associated with the activation or deactivation of the at least a first RRC module reported to the radio access network by the terminal device.

[0297] In some example embodiments activating an RRC module comprises configuring the terminal device according to the RRC module.

[0298] In some example embodiments deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0299] A method corresponding to method 400 may be carried out at a network node.

[0300] Fig. 5 is a flow diagram of a method in accordance with example embodiments, designated generally by the reference numeral 500. Method 500 may be performed by a terminal device, such as terminal device 210 (e.g., such as a UE).

[0301] At step 510 a terminal device stores a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module.

[0302] At step 520, the terminal device determines a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

[0303] By determining the activation delay of an RRC module, a terminal device may then indicate this to the network or determine whether a delay assumed by the network is accurate or acceptable, etc., which may allow for the terminal device to provide the network with relevant information for making scheduling decisions.

[0304] In some example embodiments, the method further comprises activating or deactivating, by the terminal device, the at least a first RRC module, and determining, by the terminaldevice, the first delay based at least in part on a time to complete the activating or deactivating the at least a first RRC module.

[0305] In some example embodiments, the method further comprises steps of:

[0306] • determining, by the terminal device, a second delay;

[0307] • comparing the first delay to the second delay; and

[0308] • sending, to a network node of a radio access network, based on a result of the comparison, an indication of the first delay.

[0309] In some example embodiments, the second delay is determined based on delay data associated with the activation or deactivation of the at least a first RRC module, stored by the terminal device.

[0310] In some example embodiments the delay data comprises standard specified data, corresponding to delay data stored at the network node. For example, the delay data may correspond to standard specified delay data at the network node, and the comparison may allow the terminal device to determine whether the measured delay corresponds to a default or standard specified delay.

[0311] In some example embodiments the delay data comprises delays previously indicated to the radio access network. This may allow the terminal device to determine whether the measured delay corresponds to a previously indicated delay relied upon by the network.

[0312] In some example embodiments the delay data comprises at least one or more of: delays indicated to the radio access network in capability signaling; and delays reported to the radio access network. Capability information may explicitly or implicitly indicate delays that the network node may base scheduling decisions on, and the comparison may therefore allow the terminal device obtain information indicative of the accuracy of the delays relied upon by the network.

[0313] In some example embodiments, the first delay is associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling, and the second delay is determined from delay data associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling.

[0314] In some example embodiments, the first delay is associated with activation or deactivation of the at least a first RRC module responsive to medium access control, MAC, control element, MAC CE, signalling, and the second delay determined from delay data associatedwith activation or deactivation of the at least a first RRC module responsive to MAC CE signalling.

[0315] Determining MAC CE or RRC triggered delays may provide separate data for MAC CE or RRC indicated RRC module switches, which may allow for more accurate decisions based on the delays.

[0316] In some example embodiments, the second delay is determined based on delay data and any one or more of: a number of RRC modules activated with the at least a first RRC module; and a type of module associated with the at least a first RRC module.

[0317] In some example embodiments, activating an RRC module comprises configuring the terminal device according to the RRC module.

[0318] In some example embodiments, deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0319] In some above described methods, terminal devices (such as UEs) determine activation times. In some examples, the UE uses a timer to determine an activation time for modules upon activation. In some examples, a UE may be implemented with an algorithm to determine activation time for inactive modules. For example, delay information for inactive modules may be inferred from properties of the inactive modules. UEs may store these delay values for reporting to the network.

[0320] In some examples, a UE may at some instances function in a manner which outside of the knowledge of the network. For example, a UE could be connected to another NW due to multi-sim usage and due to this implementation, the delay for module activation could be different to the specified delays (e.g., because resources are shared between networks).

[0321] Additionally, a UE may perform module activation slower if it deems activation to be less urgent or if the UE needs to save power by reducing its operational speed. This could also be due to overheating issues experienced by the UE. In this scenario, the UE could determine it necessary to complete the module activations with a slower speed than the network assumes (e.g., based on previous UE indications, or standard specifications). Methods described herein may provide methods by which the UE may effectively extend the time for performing module activation using a NACK message.

[0322] Fig. 6 is a signaling diagram of a method in accordance with example embodiments,designated generally by the reference numeral 600. Method 600 comprises signaling between a terminal device 210 (e.g., such as a UE) and a RAN node 220 (e.g., a base station such as a gNB, a distributed unit of a distributed base station, such as a gNB DU, or a centralized unit of a distributed base station, such as a gNB CU).

[0323] Steps 632 - 636 of method 600 correspond to steps 232 - 236 of method 200.

[0324] At step 638, RAN node 220 determines to activate RRC modules and / or deactivate RRC modules. RAN node 220 may assume a delay, based on a preconfigured (e.g., standardized) delays and / or terminal device capability information, or previous terminal device indications of delays for activating (or deactivating) modules (e.g., received at step 636).

[0325] In the case of an RRC profile based RRC configuration, activating modules may comprise adding modules to the active RRC profile, and removing modules may comprise removing modules from the active profile, and configuring the terminal device according to the resulting changed active RRC profile.

[0326] In the case of a non-profile based RRC configuration, activating modules may comprise configuring the terminal device according to the activated RRC modules. Deactivating RRC modules may comprise configuring the terminal device according to a set of RRC modules that does not include the deactivated RRC modules.

[0327] In some cases, RAN node 220 may determine to use MAC CE based signaling to indicate the module change. The RAN node may in some examples determine a MAC CE delay, e.g., based on preconfigured information (e.g., standardized or terminal device capability information derived delays for MAC CE indicated module changes) or other information previously provided by the terminal device (e.g., the terminal device 210 may provide delays for MAC CE based activation at step 636).

[0328] At step 640 RAN node 220 sends an RRC module change message with the module IDs of the modules to activate and / or deactivate (additionally, or alternatively, RAN node 220 could indicate that the terminal device is to activate a RCT.) In the case of an RRC profile based RRC configuration, the RAN node may indicate lists of RRC modules to add to or remove from a respective RRC profiles, with additions to and removals from the active RRC profile corresponding to activations and deactivations. In the case of a non-profile based RRC configuration, the RRC module change message may indicate RRC modules to activate and / or deactivate.In some examples, this information may be indicated via DCI or corresponding MAC CE based signaling.

[0329] At step 642, terminal device 210 initiates activation and / or deactivation of the modules as indicated.

[0330] At step 644, before the activation and / or deactivation initiated at step 642 is complete (and optionally before the activation and / or deactivation starts), terminal device 644 determines that the activation or deactivation will not be complete within the time expected / allowed by RAN node 220. The expected / allowed time may be based on a preconfigured, standard specified, time, based on capability information provided to the network, previously indicated delays, etc.

[0331] At step 646, terminal device 210, based on the determination of step 644, sends a negative acknowledgement message, indicating to the network that the terminal device 210 has not received the module change indication of step 640.

[0332] At step 648, terminal device 210 continues activation and / or deactivation of RRC module(s) as indicated.

[0333] At step 650, RAN node 220 resends the RRC module change message. The time expected / allowed by RAN node 220 for activation / deactivation of the module(s) may now start at reception of the retransmission, providing additional time to complete the indicated activation / deactivation.

[0334] At step 652, terminal device 210 sends a module change complete message, having activated and / or deactivated the RRC module(s) as indicated by RAN node 220.

[0335] Fig. 7 is a flow diagram of a method in accordance with example embodiments, designated generally by the reference numeral 700. Method 700 may be performed by a terminal device, such as terminal device 210 (e.g., such as a UE).

[0336] At step 710, a terminal device stores a plurality of radio resource control, RRC, modules, including at least a first RRC module.

[0337] At step 720, the terminal device obtains a first delay for activating or deactivating the at least a first RRC module.At step 730, the terminal device receives from a network node, an indication that the terminal device is to activate or deactivate the at least a first RRC module.

[0338] At step 740, the terminal device determines whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0339] At step 750, the terminal device sends, to the network node, an acknowledgement to the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0340] By acknowledging the indication based on whether the RRC module activation or deactivation of the indication will be complete within the first delay, the terminal device may have the option to effectively reset the delay, by indicating to the network node that it has not received the indication. This may allow the network node to infer that the terminal device will not activate or deactivate a module as indicated within the first delay.

[0341] In some example embodiments, sending the acknowledgment comprises sending a positive acknowledgement based on determining that activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the indication.

[0342] In some example embodiments, sending the acknowledgement comprises sending a negative acknowledgment based on determining that activation or deactivation of the at least a first RRC module will not be complete within the first delay from reception of the indication.

[0343] In some example embodiments, the method further comprises receiving, at the terminal device, after sending a negative acknowledgment, a retransmission of the indication that the terminal device is to activate or deactivate the at least a first RRC module.

[0344] In some example embodiments, the method further comprises determining, by the terminal device, whether activation or deactivation of the at least a first RRC module will be complete within the first delay from reception of the retransmission of the indication; and sending from the terminal device, to the network node, an acknowledgement to the retransmission of the indication, based on the determination of whether activation or deactivation of the at least a first RRC module will be complete within the first delay fromreception of the retransmission of the indication.

[0345] In some example embodiments, the method further comprises activating or deactivating the at least a first RRC module according to the received indication.

[0346] In some example embodiments, the method further comprises ignoring at least one scheduling message from the network node scheduling transmission or reception by the terminal device before the activation or deactivation of the at least a first RRC module is completed, based on determining that activation or deactivation of the at least a first RRC module will not be complete within the first delay from reception of the indication.

[0347] In some example embodiments, the method further comprises sending, to the network node, an indication of a second delay for performing activation or deactivation of the at least a first RRC module. Sending a delay to the network node may allow the terminal device to indicate a longer delay to the network node. If the network node relies on the second, longer delay, this may avoid further instances of sending the negative acknowledgement to effectively reset the first delay, reducing signaling.

[0348] In some example embodiments, the acknowledgement message further comprises an indication of a second delay for performing activation or deactivation of the at least a first RRC module.

[0349] In some example embodiments, the second delay is based on at least one of the following: a delay for activating or deactivating the at least a first RRC module estimated by the terminal device; and a delay for activating or deactivating the at least a first RRC module measured by the terminal device.

[0350] In some example embodiments, the first delay for activating or deactivating the at least a first RRC module is obtained based on at least one of: a delay stored by the terminal device and corresponding to a standard specification; a delay indicated by capability signaling from the terminal device to the radio access network; a delay received by the terminal device from the radio access network; and a delay reported to the radio access network by the terminal device.

[0351] In some example embodiments, the stored plurality of RRC modules further comprises at least a second RRC module; the received indication is an indication that the terminal device is to activate the at least a first RRC module and deactivate the at least a second RRC module; and the first delay is a sum of a third delay, for activating the at least a first RRCmodule, and a fourth delay, for deactivating the at least a second RRC module.

[0352] In some example embodiments, activating an RRC module comprises configuring the terminal device according to the RRC module.

[0353] In some example embodiments, deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

[0354] For completeness, FIG. 8 is a schematic diagram of components of one or more of the example embodiments described previously, which hereafter are referred to generically as a processing system 1800. The processing system 1800 may, for example, be comprised by the device referred to in the claims below.

[0355] The processing system 1800 may have a processor 1802, a memory 1804 closely coupled to the processor and comprised of a Random Access Memory (RAM) 1814 and a Read Only Memory (ROM) 1812, and, optionally, a user input 1810 and a display 1818. The processing system 1800 may comprise one or more network / apparatus interfaces 1808 for connection to a network / apparatus, e.g., a modem which may be wired or wireless. The network / apparatus interface 1808 may also operate as a connection to other apparatus such as device / apparatus which is not network side apparatus. Thus, direct connection between devices / apparatus without network participation is possible.

[0356] The processor 1802 is connected to each of the other components in order to control operation thereof.

[0357] The memory 1804 may comprise a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD). The ROM 1812 of the memory 1804 stores, amongst other things, an operating system 1815 and may store software applications 1816. The RAM 1814 of the memory 1804 is used by the processor 1802 for the temporary storage of data. The operating system 1815 may contain code which, when executed by the processor implements aspects of the methods 200, 300, 400, 500, 600, and 700 described above. Note that in the case of small device / apparatus the memory can be most suitable for small size usage i.e., not always a hard disk drive (HDD) or a solid state drive (SSD) is used.

[0358] The processor 1802 may take any suitable form. For instance, it may be a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors.The processing system 1800 may be a standalone computer, a server, a console, or a network thereof. The processing system 1800 and needed structural parts may be all inside device / apparatus such as loT device / apparatus i.e., embedded to very small size.

[0359] In some example embodiments, the processing system 1800 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partly or exclusively on the remote server device / apparatus. These applications may be termed cloud-hosted applications. The processing system 1800 may be in communication with the remote server device / apparatus in order to utilize the software application stored there.

[0360] FIG. 9 shows a tangible media, in the form of a removable memory unit 1910, storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. The removable memory unit 1910 may be a memory stick, e.g., a Universal Serial Bus (USB) memory stick, having internal memory 1930 storing the computer-readable code. The internal memory 1930 may be accessed by a computer system via a connector 1920. Of course, other forms of tangible storage media may be used, as will be readily apparent to those of ordinary skilled in the art. Tangible media can be any device / apparatus capable of storing data / information which data / information can be exchanged between devices / apparatus / network.

[0361] Embodiments of the present invention may be implemented in digital electronic circuitry, software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "memory" or "computer-readable medium" may be any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0362] As used in this application, the term 'circuitry' or "circuit" may refer to one or more, or all, of the following: (a) hardware-only circuit implementations, such as implementations in analog digital circuitry, and / or quantum circuitry and (b) combinations of hardware circuit(s) and software (and / or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)), with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform variousfunctions, and (c) any or all portions of hardware circuit(s), such as a microprocessor(s), processor(s) and / or quantum processor(s), that require software (e.g., firmware) for operation, but the software is not necessarily present when it is not needed for operation. This definition of 'circuitry' applies to all uses of this term in this application. As a further example, as used in this application, the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and / or firmware. The term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.

[0363] Reference to, where relevant, "computer-readable medium", "computer program product", "tangibly embodied computer program" etc., or a "processor" or "processing circuitry" etc. should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers / parallel architectures, but also specialised circuits such as field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), signal processing devices / apparatus and other devices / apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device / apparatus as instructions for a processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc.

[0364] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the abovedescribed functions may be optional or may be combined. Similarly, it will also be appreciated that the flow and signalling diagrams of Figures 2 - 7 are examples only and that various operations depicted therein may be omitted, reordered and / or combined.

[0365] It will be appreciated that the above-described example embodiments are purely illustrative and are not limiting on the scope of the invention. Other variations and modifications will be apparent to persons skilled in the art upon reading the present specification.

[0366] Moreover, the disclosure of the present application should be understood to include any novel features or any novel combination of features either explicitly or implicitly disclosed herein or any generalization thereof and during the prosecution of the present applicationor of any application derived therefrom, new claims may be formulated to cover any such features and / or combination of such features.

[0367] Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described example embodiments and / or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.

[0368] It is also noted herein that while the above describes various examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

[0369] List of abbreviations

[0370] 3GPP 3rd Generation Partnership Project

[0371] AMF Access and Mobility Management Function

[0372] AR Augmented Reality

[0373] BWP Bandwidth Part

[0374] CP Control Plane

[0375] DL Downlink

[0376] DRB Data Radio Bearer

[0377] gNB 5G Node-B

[0378] loT Internet of Things

[0379] LTE Long-Term Evolution

[0380] MAC Medium Access Control

[0381] MIMO Multiple Input Multiple Output

[0382] NR New Radio

[0383] NW Network

[0384] PDCP Protocol Data Convergence Protocol

[0385] PHY Physical layer

[0386] RAN Radio Access Network

[0387] RCT RRC Configuration Threads

[0388] RLC Radio Link Control

[0389] RRC Radio Resource Control

[0390] SRB Signalling Radio Bearer

[0391] UE User Equipment

[0392] UL UplinkUP User Plane

[0393] V2X Vehicle to everything VR Virtual Reality

Claims

55ClaimsWhat is claimed is:

1. A terminal device comprising:means for storing a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; andmeans for determining a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

2. The terminal device of claim 1, further comprising means for activating or deactivating the at least a first RRC module, and determining the first delay based at least in part on a time to complete the activating or deactivating the at least a first RRC module.

3. The terminal device of claim 1 or claim 2, further comprising:means for determining a second delay;means for comparing the first delay to the second delay; andmeans for sending, to a network node of a radio access network, based on a result of the comparison, an indication of the first delay.

4. The terminal device of claim 3, wherein the means for determining the second delay is configured to determine the second delay based on delay data, associated with the activation or deactivation of the at least a first RRC module, stored by the terminal device.

5. The terminal device of claim 4, wherein the delay data comprises standard specified data, corresponding to delay data stored at the network node.

6. The terminal device of claim 4, wherein the delay data comprises delays previously indicated to the radio access network.

7. The terminal device of claim 6, wherein the delay data comprises at least one or more of:delays indicated to the radio access network in capability signalling; and delays reported to the radio access network.

568. The terminal device of any of claims 4 - 7, wherein the first delay is associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling, and wherein the means for determining the second delay is configured to determine the second delay from delay data associated with activation or deactivation of the at least a first RRC module responsive to RRC signalling.

9. The terminal device of any of claims 4 - 7, wherein the first delay is associated with activation or deactivation of the at least a first RRC module responsive to medium access control, MAC, control element, MAC CE, signalling, and wherein the means for determining the second delay is configured to determine the second delay from delay data associated with activation or deactivation of the at least a first RRC module responsive to MAC CE signalling.

10. The terminal device of any of claims 4 - 9, wherein the means for determining the second delay is configured to determine the second delay based on delay data and any one or more of:a number of RRC modules activated with the at least a first RRC module; and a type of module associated with the at least a first RRC module.

11. The terminal device of any preceding claim, wherein activating an RRC module comprises configuring the terminal device according to the RRC module.

12. The terminal device of any preceding claim, wherein deactivating an RRC module comprises configuring the terminal device according to an RRC configuration that does not comprise the RRC module.

13. A method comprising:storing, at a terminal device, a plurality of radio resource control, RRC, modules, wherein the plurality of RRC modules comprises at least a first RRC module; and determining, by the terminal device, a first delay, from reception by the terminal device of an indication that the terminal device is to activate or deactivate the at least a first RRC module, to activation or deactivation of the at least a first RRC module.

Images