Apparatus and method for a network device

Abstract

An apparatus for a network device, the apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to: receive, from a further network device, an indication to request, from a terminal device associated with the network device, first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by the further network device, transmit a request for the first information to the terminal device, receive a response comprising the first information.

Description

[0001] Title: Apparatus and Method for a Network Device

[0002] Specification

[0003] Field of the Disclosure

[0004] Various example embodiments relate to an apparatus for a network device.

[0005] Further example embodiments relate to a method for a network device .

[0006] Further example embodiments relate to an apparatus for a terminal device.

[0007] Further example embodiments relate to a method for a terminal device .

[0008] Background

[0009] Communication systems such as, e.g., wireless communication systems may be used for wireless exchange of information between two or more entities, e.g., comprising one or more terminal devices, e.g., user equipment (UE) , and one or more network devices such as, e.g., base stations. Summary

[0010] Various example embodiments of the disclosure are set out by the independent claims. The example 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 example embodiments of the disclosure.

[0011] Some examples relate to an apparatus for a network device, the apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to: receive, from a further network device, e.g., from at least one further network device, an indication to request, from a terminal device associated with the network device, first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by the further network device, transmit a request for the first information to the terminal device, receive a response comprising the first information. In some examples, this may enable the network device to, for example at least temporarily, collect the first information, e.g., information related to the capabilities of the terminal device, as, e.g., specified by the further network device. In some examples, such collected information may be used, e.g., for providing at least parts of the collected information, e.g., to at least one further device.

[0012] In some examples, at least one of the network device or the terminal device may adhere to and / or may be based on some accepted (and / or planned) specification, e.g., standard, e.g., 3GPP standard, such as, e.g., 3G, 4G, 5G, 6G, or some other wireless communication standard. In some examples, the network device may, e.g., be a base station, e.g., gNB .

[0013] In some examples, the terminal device may, e.g., be a user equipment, UE .

[0014] In some examples, the terminal device may, e.g., be served by the network device.

[0015] In some examples, the network device may, e.g., be a source gNB currently serving the terminal device, and the further network device may, e.g., be a potential target gNB for the terminal device.

[0016] In some examples, the network device may receive an indication to request the first information from more than one further network device, e.g., from multiple devices, e.g., multiple further gNB.

[0017] In some examples, the instructions, when executed by the at least one processor, cause the network device to: transmit at least a part of the first information to at least one further entity .

[0018] In some examples, the transmission of the first information (or at least a part thereof, respectively) may be triggered, e.g., by an event. In some examples, a trigger for the transmission of the first information may, e.g., be related to a handover procedure.

[0019] In some examples, the transmission of the first information (or at least a part thereof, respectively) may be performed at a predetermined point in time, e.g., as selected by the network device. In some examples, the first information (or at least a part thereof, respectively) , which may, e.g., comprise the requested capability, may be sent, e.g., immediately, to a further entity, e.g., network device, e.g., associated with a core network, e.g., together with the request from the further network device, e.g., gNB . In some examples, the first information may, e.g., be stored, e.g., at the core network, e.g., for new, e.g., future, setup processes.

[0020] In some examples, the at least one the further entity is at least one of: a) the further network device (e.g., a further gNB, e.g., a potential target gNB for a handover process of the terminal device and / or other neighbor gNB) , or b) an Access and Mobility Function, AMF, or another network device associated with the core network.

[0021] In some examples, the instructions, when executed by the at least one processor, cause the network device to: transmit at least a part of the first information within a handover request to the further network device.

[0022] In some examples, the instructions, when executed by the at least one processor, cause the network device to: determine which part of the first information to transmit to the at least one further entity, transmit at least the determined part to the at least one further entity.

[0023] In other words, in some examples, the network device may, e.g., choose which portion of the first information to provide, e.g., transmit, to the at least one further entity, e.g., in the course of preparing a handover procedure, e.g., within a handover request. Hence, in some examples, the network device may omit, e.g., decide to not transmit, at least one portion of the first information. In some examples, the indication characterizes or comprises at least one of: a) a capability filter (e.g., characterizing the capabilities of the terminal device) , or b) at least one frequency band for which the network device should request capabilities of the terminal device, e.g., as specified by the further network device. In some examples, this enables the further network device, e.g., a potential target gNB, to cause the network device, e.g., a currently serving, e.g., source, gNB, to request specific capability information from the terminal device, e.g., related to capabilities of the terminal device as may, e.g., be specified by the further network device, e.g., using the indication.

[0024] In some examples, one or more UE capabilities as may, e.g., be specified by the indication, may, e.g., be based on some other information, such as, e.g., based on a list of cells as, e.g., supported by a target gNB, or a subset of frequency bands to be used by a target gNB, or the like.

[0025] In other words, in some examples, the further network device may use the principle according to the disclosure to instruct the network device to request, e.g., collect, capability information of the terminal device the further network device is, e.g., currently, interested in. In other words, in some examples, this may enable to initiate a collection of capability information of the terminal device by the network device, even if the network device itself would not, e.g., on its own initiative, collect such capability information of the terminal device, e.g., because the network device itself is, e.g., currently, not interested in this specific capability information as may be requested by the further network device.

[0026] In some examples, the instructions, when executed by the at least one processor, cause the network device to: request, from the terminal device, to provide one or more sets of capabilities of the terminal device, based on the indication, transmit at least one set of the one or more sets of capabilities of the terminal device to the at least one further entity. In some examples, requesting to provide the one or more sets of capabilities may e.g. be accomplished by using the request for the first information.

[0027] In some examples, the instructions, when executed by the at least one processor, cause the network device to: receive second information from the terminal device, the second information characterizing at least one of: a) capability filter information last inquired from the terminal device, or b) an indication of capabilities the terminal device is currently using, e.g., an indication of a set of capabilities the terminal device is currently using. In other words, in some examples, the terminal device may, e.g., indicate a set of capabilities it is using, i.e., a set it is sending to the network, e.g., in case the terminal device uses several sets of capabilities. In some examples, the terminal device may transmit the second information on its own initiative, e.g., without receiving any request, such as, e.g., the request for the first information. In some examples, the terminal device may, e.g., transmit the second information repeatedly, e.g., event-based, or periodically.

[0028] In some examples, the network device may, e.g., nevertheless, transmit the request for the first information to the terminal device, e.g., based on receiving the indication from the further network device. In some examples, the network device may, e.g., transmit the request for the first information to the terminal device after having received the second information from the terminal device. In some examples, the network device may, e.g., transmit the request for the first information to the terminal device before, e.g., without, having received the second information from the terminal device .

[0029] In some examples, the instructions, when executed by the at least one processor, cause the network device to: store at least one of a) the first information, or b) the second information. In some examples, the network device may store at least one of the first information or the second information locally, e.g., at the network device. In some examples, the network device may store at least one of the first information or the second information in a database, e.g., a common database, which may, e.g., be accessible by the network device and at least one further device (e.g., further network device and / or other entity) .

[0030] In some examples, the instructions, when executed by the at least one processor, cause the network device to: receive the indication, determine, whether the first information is available at the network device or at a or the common database, and, based on the determination, transmit at least one of a) the first information, or b) a reference to the first information as stored in the database to the at least one further entity. In some examples, this may enable to avoid transmitting request (s) for such capability information of a terminal device to the respective terminal device, which is already available at the network device or at the common database. In some examples, e.g., if the determination yields that the first information is not available at the network device or at the common database, the network device may transmit a corresponding request to the terminal device. Some examples relate to an apparatus for a network device , the apparatus comprising means for : receiving, from a further network device , an indication to request , from a terminal device associated with the network device , first information comprising requested capabilities of the terminal device , wherein the requested capabilities are determined by the further network device , transmitting a request for the first information to the terminal device , receiving a response comprising the first information .

[0031] In some examples , the means for receiving the indication, transmitting the request to the terminal device , receiving the response comprising the first information may, e . g . , comprise at least one processor, and at least one memory storing instructions that , when executed by the at least one processor, cause the network device to perform at least one of the aforementioned aspects of receiving the indication, transmitting the request , receiving the response .

[0032] In some examples , the means for receiving the indication, transmitting the request to the terminal device , receiving the response comprising the first information may, e . g . , comprise circuitry configured to perform at least one of the aforementioned aspects of receiving the indication, transmitting the request , receiving the response .

[0033] Some examples relate to a method for a network device , comprising : receiving, from a further network device , an indication to request , from a terminal device associated with the network device , first information comprising requested capabilities of the terminal device , wherein the requested capabilities are determined by the further network device , transmitting a request for the first information to the terminal device, receiving a response comprising the first information .

[0034] Some examples relate to an apparatus for a network device, the apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to: transmit to a further network device, which is associated with (e.g., currently serving) a terminal device, an indication to request, from the terminal device, first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by the network device. In some examples, the network device may, e.g., be a potential target gNB for a handover of the terminal device from the further network device, which may, e.g., at least temporarily act as a source gNB, e.g., currently serving the terminal device, e.g., user equipment.

[0035] In some examples, the instructions, when executed by the at least one processor, cause the network device to: receive at least a part of the first information. In some examples, this may enable a, for example potential, target gNB to attain capability information of the user equipment the potential target gNB is interested in, even if the terminal device is currently not served by the potential target gNB.

[0036] Some examples relate to an apparatus for a network device, the apparatus comprising means for: transmitting to a further network device, which is associated with a terminal device, an indication to request, from the terminal device, first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by the network device. In some examples, the means for transmitting the indication may, e.g., comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to perform the aspect of transmitting the indication.

[0037] In some examples, the means for transmitting the indication may, e.g., comprise circuitry configured to perform the aspect of transmitting the indication.

[0038] Some examples relate to a method for a network device, comprising: transmitting to a further network device, which is associated with a terminal device, an indication to request, from the terminal device, first information characterizing capabilities of the terminal device as specified by the network device.

[0039] Some examples relate to an apparatus for a terminal device, the apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to: receive, from a network device, a request for first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by a further network device, transmit a response comprising the first information. In some examples, the terminal device may, e.g., be a user equipment which is, e.g., currently served by the network device, e.g., gNB, e.g., a source gNB for a potential future handover process.

[0040] In some examples, the instructions, when executed by the at least one processor, cause the terminal device to perform at least one of: a) transmitting second information to the network device, the second information characterizing at least one of: al) capability filter information last inquired from the terminal device, or a2) an indication of capabilities the terminal device is currently using, or b) including the second information in a Radio Resource Control message.

[0041] As already mentioned above, in some examples, the terminal device may transmit the second information on its own initiative, e.g., without receiving any request, such as, e.g., the request for the first information. In some examples, the terminal device may, e.g., transmit the second information repeatedly, e.g., event-based (e.g., if the capabilities of the terminal device have changed, e.g., due to some reason) , or periodically.

[0042] Some examples relate to an apparatus for a terminal device, the apparatus comprising means for: receiving, from a network device, a request for first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by a further network device, transmitting a response comprising the first information.

[0043] In some examples, the means for receiving the request, transmitting the response may, e.g., comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to perform the aspects of receiving the request, transmitting the response.

[0044] In some examples, the means for receiving the request, transmitting the response may, e.g., comprise circuitry configured to perform the aspects of receiving the request, transmitting the response.

[0045] Some examples relate to a method for a terminal device, comprising: receiving, from a network device, a request for first information comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by a further network device, transmitting a response comprising the first information.

[0046] Some examples relate to a network device, comprising at least one apparatus according to the disclosure. In some examples, the network device may, e.g., be a gNB . In some examples, the network device may, e.g., be an Access and Mobility Function, e.g., based on some accepted (and / or planned) specification, e.g., standard .

[0047] Some examples relate to a terminal device, e.g., user equipment, comprising at least one apparatus according to the disclosure .

[0048] Some examples relate to a communication system, e.g., a wireless, e.g., cellular, communication system, comprising at least one of: a) an apparatus according to the disclosure, or b) a network device according to the disclosure, or c) a terminal device according to the disclosure.

[0049] Some examples relate to a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least some aspects of the method according to the disclosure.

[0050] Some examples relate to a computer-readable storage medium, for example a non-transitory computer-readable storage medium, comprising the computer program according to the disclosure.

[0051] Some examples relate to a data carrier signal carrying and / or characterizing the computer program according to the disclosure . Brief Description of the Figures

[0052] Fig. 1A schematically depicts a simplified block diagram according to some examples,

[0053] Fig. IB schematically depicts a simplified block diagram according to some examples,

[0054] Fig. 2 schematically depicts a simplified block diagram according to some examples,

[0055] Fig. 3 schematically depicts a simplified flow chart according to some examples,

[0056] Fig. 4 schematically depicts a simplified flow chart according to some examples,

[0057] Fig. 5 schematically depicts a simplified flow chart according to some examples,

[0058] Fig. 6 schematically depicts a simplified block diagram according to some examples,

[0059] Fig. 7 schematically depicts a simplified flow chart according to some examples,

[0060] Fig. 8 schematically depicts a simplified flow chart according to some examples,

[0061] Fig. 9 schematically depicts a simplified flow chart according to some examples,

[0062] Fig. 10 schematically depicts a simplified flow chart according to some examples,

[0063] Fig. 11A schematically depicts a simplified block diagram according to some examples, Fig . 11B schematically depicts a simplified block diagram according to some examples,

[0064] Fig . 12 schematically depicts a simplified flow chart according to some examples,

[0065] Fig . 13A schematically depicts a simplified block diagram according to some examples,

[0066] Fig . 13B schematically depicts a simplified block diagram according to some examples,

[0067] Fig . 14 schematically depicts a simplified flow chart according to some examples,

[0068] Fig . 15 schematically depicts a simplified signaling diagram according to some examples,

[0069] Fig . 16 schematically depicts a simplified signaling diagram according to some examples,

[0070] Fig . 17 schematically depicts a simplified block diagram according to some examples.

[0071] Description of some Example Embodiments

[0072] Some examples, Fig. 1A, 2, 3, relate to an apparatus 100 for a network device 10, the apparatus 100 comprising at least one processor 102, and at least one memory 104 storing instructions 106 that, when executed by the at least one processor 102, cause the network device 10 to: receive 300, from a further network device 20, an indication IND to request, from a terminal device 30 associated with the network device 10, first information II comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by the further network device 20, transmit 302 a request REQ-11 for the first information II to the terminal device 30, receive 304 a response RESP-I1 comprising the first information II. In some examples, this may enable the network device 10 to, for example at least temporarily, collect the first information II, e.g., information related to the capabilities of the terminal device 30, as, e.g., specified by the further network device 20.

[0073] In some examples, such collected information may be used, e.g., for providing at least parts of the collected information, e.g., to at least one further device 20, e.g., upon request of another entity 20, 22, such as, e.g., the further network device 20, or, for example, after receiving 304 the response RESP-I1.

[0074] In some examples, Fig. 2, at least one of the network device 10 or the further network device 20 or the terminal device 30 may adhere to and / or may be based on some accepted (and / or planned) specification, e.g., standard, such as, e.g., 3G, 4G, 5G, 6G, or some other wireless communication standard.

[0075] In some examples, Fig. 2, the network device 10 may, e.g., be a base station, e.g., gNB . In some examples, the terminal device 30 may, e.g., be a user equipment, UE . In some examples, the terminal device 30 may, e.g., be served by the network device 10.

[0076] In some examples, Fig. 2, the network device 10 may, e.g., be a source gNB currently serving the terminal device 30, and the further network device 20 may, e.g., be a potential target gNB for the terminal device 30.

[0077] In some examples, Fig. 3, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: transmit 306 at least a part II' of the first information Il to at least one further entity 20, 22.

[0078] In some examples, the at least one the further entity 20, 22 is at least one of: a) the further network device 20 (e.g., a further gNB, e.g., a potential target gNB for a handover process of the terminal device 30) , or b) an Access and Mobility Function, AMF, 22.

[0079] In some examples, Fig. 4, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: transmit 306a at least a part II' of the first information Il within a handover request to the further network device 20, also see, for example, arrow a5 of Fig. 15, which is explained in detail further below.

[0080] In some examples, Fig. 4, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: transmit 306b at least a part II' of the first information Il to an Access and Mobility Function 22, also see, for example, arrow al8 of Fig. 16, which is explained in detail further below.

[0081] In some examples, Fig. 3, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to at least temporarily store 308 the first information II, e.g., locally, e.g., at the network device 10, and / or in a database DB accessible by the network device 10 and at least one further device 20, 22.

[0082] In some examples, Fig. 5, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: determine 310 which part II' of the first information II to transmit to the at least one further entity, transmit 312 at least the determined part II' to the at least one further entity .

[0083] In other words, in some examples, Fig. 2, the network device 10 may, e.g., choose which portion of the first information II to provide, e.g., transmit, to the at least one further entity 20, 22, e.g., in the course of preparing a handover procedure, e.g., within a handover request. Hence, in some examples, the network device 10 may omit, e.g., decide to not transmit, at least one portion of the first information.

[0084] In some examples, Fig. 6, the indication IND characterizes or comprises at least one of: a) a capability filter CAP-FILT, or b) at least one frequency band FB for which the network device 10 should request capabilities of the terminal device 30, e.g., as specified by the further network device 20. In some examples, this enables the further network device 20, e.g., a potential target gNB, to cause the network device 10, e.g., a currently serving, e.g., source, gNB, to request specific capability information from the terminal device 30, e.g., related to capabilities of the terminal device 30 as may, e.g., be specified by the further network device 20, e.g., using the indication IND.

[0085] In other words, in some examples, the further network device 20 may use the principle according to the disclosure to instruct the network device 10 to request, e.g., collect, capability information of the terminal device 30 the further network device 20 is, e.g., currently, interested in. In other words, in some examples, this may enable to initiate a collection of capability information of the terminal device 30 by the network device 10, even if the network device 10 itself would not, e.g., on its own initiative, collect such capability information of the terminal device 30, e.g., because the network device 10 itself is, e.g., currently, not interested in this specific capability information as may be specified and / or requested by the further network device 20.

[0086] In some examples, Fig. 7, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: request 320, from the terminal device 30, to provide one or more sets of capabilities of the terminal device 30, based on the indication IND, transmit 324 at least one set SET-CAP of the one or more sets of capabilities of the terminal device 30 to the at least one further entity 20, 22. In some examples, requesting 320 to provide the one or more sets of capabilities may e.g. be accomplished by using a request REQ', which, in some examples, may, e.g., be the request REQ-11 for the first information II. Block 322 of Fig. 7 symbolizes the network device 10 receiving a response RESP' from the terminal device 30 to the request REQ', wherein the response RESP' may, e.g., comprise the requested one or more sets of capabilities of the terminal device 30.

[0087] In some examples, Fig. 8, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: receive 330 second information 12 from the terminal device 30, the second information 12 characterizing at least one of: a) capability filter information last inquired from the terminal device 30 (e.g., by the network device 10) , or b) an indication of capabilities the terminal device 30 is currently using. In some examples, the terminal device 30 may, e.g., transmit the second information 12 on its own initiative, e.g., without receiving any request, such as, e.g., the request REQ-11 for the first information II. In some examples, the terminal device 30 may, e.g., transmit the second information 12 repeatedly and / or, e.g., event-based, or periodically .

[0088] In some examples, Fig. 8, the network device 10 may, e.g., nevertheless, transmit the request REQ-11, REQ' for the first information to the terminal device 30, e.g., based on receiving the indication IND (see, for example block 300 of Fig. 3) from the further network device 20.

[0089] In some examples, the network device 10 may, e.g., transmit the request REQ-11, REQ' for the first information to the terminal device 30 after having received the second information 12 from the terminal device.

[0090] In some examples, the network device 10 may, e.g., transmit the request REQ-11, REQ' for the first information to the terminal device 30 before, e.g., without, having received the second information 12 from the terminal device 30.

[0091] In some examples, Fig. 8, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: store 332 at least one of a) the first information II (e.g., potentially in the form of one or more capability sets SET-CAP, see, for example, Fig. 7) , or b) the second information 12. In some examples, Fig. 2, the network device 10 may store at least one of the first information II or the second information 12 locally, e.g., at the network device 10. In some examples, the network device 10 may store at least one of the first information II or the second information 12 in a database, e.g., a common database, DB, which may, e.g., be accessible by the network device 10 and at least one further device 20, 22 (e.g., further network device 20 and / or other entity such as, e.g., the AMF 22) . In some examples, the database DB may be local (not shown) to the network device 10 or any of the further entities 20, 22.

[0092] In some examples, Fig. 9, the instructions 106, when executed by the at least one processor 102, cause the network device 10 to: receive 340 the indication IND, determine 342, whether the first information II is (e.g., already) available at the network device 10 or at a or the common database DB, and, based on the determination DET, transmit 344 at least one of a) the first information II, or b) a reference REF-11 to the first information II as stored in the database DB to the at least one further entity 20, 22. In some examples, this may enable to avoid transmitting request (s) REQ-11 (Fig. 2) for such capability information of a terminal device 30 to the respective terminal device 30, which is already available at the network device 10 or at the common database DB .

[0093] In some examples, Fig. 9, e.g., if the determination DET yields that the first information II is not available at the network device 10 or at the common database DB, the network device 10 may transmit 302 (see Fig. 3) a corresponding request REQ-11 to the terminal device 30.

[0094] Some examples, Fig. IB, relate to an apparatus 100' for a network device 10, the apparatus 100' comprising means 102' for: receiving 300, from a further network device, an indication IND to request, from a terminal device associated with the network device, first information comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by the further network device, transmitting 302 a request for the first information to the terminal device, receiving 304 a response comprising the first information. In some examples, Fig. IB, the means 102' for receiving 300 the indication, transmitting 302 the request to the terminal device, receiving 304 the response comprising the first information may, e.g., comprise at least one processor 102 (see, for example, Fig. 1A) , and at least one memory 104 storing instructions 106 that, when executed by the at least one processor 102, cause the network device 10 to perform at least one of the aforementioned aspects of receiving 300 the indication, transmitting 302 the request, receiving 304 the response .

[0095] In some examples, Fig. IB, the means 102' for receiving 300 the indication, transmitting 302 the request to the terminal device, receiving 304 the response comprising the first information may, e.g., comprise circuitry 104' configured to perform at least one of the aforementioned aspects of receiving 300 the indication, transmitting 302 the request, receiving 304 the response.

[0096] In some examples, Fig. 2, the apparatus 100, 100' or a respective functionality, may be provided for, e.g., assigned to or integrated in, the network device 10. In some examples (not shown) , the apparatus 100, 100' or a respective functionality, may also be provided for, e.g., assigned to or integrated in, the further network device 20.

[0097] Some examples, Fig. 3, relate to a method for a network device 10, comprising: receiving 300, from a further network device, an indication to request, from a terminal device associated with the network device, first information comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by the further network device, transmitting 302 a request for the first information to the terminal device, receiving 304 a response comprising the first information.

[0098] Some examples, Fig. 2, 10, 11A, relate to an apparatus 200 for a network device 20 (e.g., the further network device 20 as referred to above) , the apparatus 200 comprising at least one processor 202, and at least one memory 204 storing instructions 206 that, when executed by the at least one processor 202, cause the network device 20 to: transmit 350 (Fig. 10) to a further network device (e.g., network device 10 referred to above) , which is associated with (e.g., currently serving) a terminal device 30, an indication IND to request, from the terminal device 30, first information II comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by the network device 20. In some examples, the network device 20 may, e.g., be a potential target gNB for a handover of the terminal device 30 from the further network device 10, which may, e.g., at least temporarily act as a source gNB, e.g., currently serving the terminal device, e.g., user equipment.

[0099] In some examples, Fig. 10, the instructions 206, when executed by the at least one processor 202, cause the network device 20 to: receive 352 at least a part II' of the first information II. In some examples, Fig. 2, this may enable a, for example potential, target gNB 20 to attain capability information of the user equipment 30 the potential target gNB 20 is interested in, even if the user equipment 30 is currently not served by the potential target gNB 20, but, for example by the source gNB 10.

[0100] Some examples, Fig. 11B, relate to an apparatus 200' for a network device 20, the apparatus 200' comprising means 202' for: transmitting 350 to a further network device 10, which is associated with a terminal device 30, an indication to request, from the terminal device, first information comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by the network device.

[0101] In some examples, Fig. 11B, the means 202' for transmitting 350 the indication may, e.g., comprise at least one processor 202 (see, for example, Fig. 11A) , and at least one memory 204 storing instructions 206 that, when executed by the at least one processor 202, cause the network device 20 to perform the aspect of transmitting 350 the indication.

[0102] In some examples, Fig. 11B, the means 202' for transmitting 350 the indication may, e.g., comprise circuitry 204' configured to perform the aspect of transmitting 350 the indication .

[0103] Some examples, Fig. 10, relate to a method for a network device 20, comprising: transmitting 350 to a further network device 10, which is associated with a terminal device 30, an indication IND to request, from the terminal device, first information comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by the network device 20.

[0104] Some examples, Fig. 2, 12, 13A, relate to an apparatus 400 for a terminal device 30, the apparatus 400 comprising at least one processor 402, and at least one memory 404 storing instructions 406 that, when executed by the at least one processor 402, cause the terminal device 30 to: receive 500, from a network device 10, a request REQ-11 for first information II comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by a further network device 20, transmit 502 a response RESP-I1 comprising the first information II. In some examples, the terminal device 30 may, e.g., be a user equipment which is, e.g., currently served by the network device, e.g., gNB, e.g., a source gNB 10 for a potential future handover process.

[0105] In some examples, Fig. 14, the instructions 406, when executed by the at least one processor 402, cause the terminal device 30 to perform at least one of: a) transmitting 510 second information 12 to the network device 10, the second information 12 characterizing at least one of: al) capability filter information last inquired from the terminal device (e.g., using the request REQ-11, see, for example, block 302 of Fig. 3) , or a2) an indication of capabilities the terminal device 30 is currently using, or b) including 512 the second information 12 in a Radio Resource Control, RRC, message, e.g., an RRC Setup Complete message, see, for example, arrow al2 of Fig. 16 explained in detail further below.

[0106] As already mentioned above, in some examples, the terminal device 30 may transmit the second information 12 on its own initiative, e.g., without receiving any request, such as, e.g., the request REQ-11 for the first information. In some examples, the terminal device 30 may, e.g., transmit the second information 12 repeatedly, e.g., event-based (e.g., if the capabilities of the terminal device have changed, e.g., due to some reason) , or periodically.

[0107] Some examples, Fig. 13B, relate to an apparatus 400' for a terminal device 30, the apparatus 400' comprising means 402' for: receiving 500, from a network device, a request for first information comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by a further network device, transmitting 502 a response comprising the first information.

[0108] In some examples, Fig. 13B, the means 402' for receiving 500 the request, transmitting 502 the response may, e.g., comprise at least one processor 402 (see, for example, Fig. 13A) , and at least one memory 404 storing instructions 406 that, when executed by the at least one processor 402, cause the terminal device 30 to perform the aspects of receiving 500 the request, transmitting 502 the response.

[0109] In some examples, Fig. 13B, the means 402' for receiving 500 the request, transmitting 502 the response may, e.g., comprise circuitry 404' configured to perform the aspects of receiving 500 the request, transmitting 502 the response.

[0110] Some examples, Fig. 12, relate to a method for a terminal device 30, comprising: receiving 500, from a network device 10, a request REQ-11 for first information II comprising requested capabilities of the terminal device 30, wherein the requested capabilities are determined by a further network device 20, transmitting 502 a response RESP-I1 comprising the first information II, e.g., to the network device 10.

[0111] Some examples, Fig. 2, relate to a network device 10, 20, 22 comprising at least one apparatus 100, 100', 200, 200' according to the disclosure. In some examples, the network device 10, 20 may, e.g., be a gNB . In some examples, the network device may, e.g., be an Access and Mobility Function, 22, e.g., based on some accepted (and / or planned) specification, e.g., standard.

[0112] Some examples, Fig. 2, relate to a terminal device, e.g., user equipment, 30 comprising at least one apparatus 400, 400' according to the disclosure. Some examples, Fig. 2, relate to a communication system 1000, e.g., a wireless, e.g., cellular, communication system, comprising at least one of: a) an apparatus 100, 100', 200, 200', 400, 400' according to the disclosure, or b) a network device 10, 20, 22 according to the disclosure, or c) a terminal device 30 according to the disclosure.

[0113] In the following, further aspects and examples are disclosed, which, in some examples, may be combined with at least one of the aspects and / or examples disclosed above.

[0114] Fig. 15 schematically depicts a simplified signaling diagram according to some examples. Element El symbolizes a terminal device, e.g., user equipment ("UE") , e.g. at least similar to element 30 of Fig. 2. Element E2a symbolizes a source gNB currently serving the UE El, e.g., at least similar to element 10 of Fig. 2. Element E2b symbolizes a potential target gNB, e.g., at least similar to element 20 of Fig. 2.

[0115] Arrow al symbolizes the target gNB E2b indicating to the source gNB E2a a UE capability filter characterizing information related to the UE ' s capabilities the target gNB E2b is interested to obtain. In some examples, the indication al of Fig. 15 may, e.g., at least be similar to the indication IND of Fig. 3, see, for example, block 300. In some examples, the indication al may characterize a subset of UE capabilities of the UE El the target gNB would like to obtain. Arrow a2 of Fig. 15 symbolizes the source gNB E2a enquiring, e.g., requesting, UE capabilities as specified by the target gNB (arrow al) from the UE El, e.g., using the information as received from the target gNB E2b via arrow al .

[0116] In some examples, the UE may send the requested information, e.g., in the form of one or more capability containers, to the source gNB E2a, see arrow a3. In some examples, the requested information (e.g., at least similar to the first information II, see, for example Fig. 2) may be sent, e.g., all at a same time, e.g., within one message from the UE to the source gNB.

[0117] In some other examples, the requested information may be sent from the UE to the source gNB using more than one message, e.g., using one message for sending, for example one, capability container.

[0118] In some examples, Fig. 15, the UE may send one or more measurements, see arrow a4, to the source gNB, e.g., indicating that a handover is required, e.g., towards the target gNB.

[0119] In some examples, the source gNB may send a handover request a5 to the target gNB, wherein, in some examples, the handover request a5 may include information related to the UE capabilities, e.g., based on the information requested using arrow a2.

[0120] In some examples, the target gNB may reply to the handover request a5 with a handover acknowledge a6. In some examples, the source gNB may send a handover command a 7 to the UE . In some examples, the UE may connect to the target gNB, see arrow a8.

[0121] Fig. 16 schematically depicts a simplified signaling diagram according to some examples. Similar to Fig. 15, element El of Fig. 16 symbolizes a UE . Element E2c of Fig. 16 symbolizes an initial gNB, e.g., a gNB initially serving the UE El. Element E2d of Fig. 16 symbolizes a new gNB, e.g. serving the UE El at a later stage. Element E3 of Fig. 16 symbolizes an Access and Mobility Function (AMF) . In some examples, the UE may request an RRC connection setup, see arrow alO of Fig. 16, wherein the UE capabilities may not yet be known at this stage. In some examples, the network may set up the RRC connection, see arrow all, e.g., based on mandatory UE capabilities. In some examples, the UE may indicate a completion of the RRC connection setup, see arrow al2. In some examples, at this stage, the UE El has an RRC connection with the initial gNB E2c.

[0122] Arrow al3 symbolizes an initial UE message from the initial gNB to the AMF according to some examples, the message al3 e.g. characterizing an identifier of the UE El, e.g., a UE ID, and, for example, a desired UE capability filter for UE capabilities .

[0123] In some examples, the AMF E3 may indicate its stored UE capabilities to the initial gNB E2c, see arrow al4. In some examples, at this stage, the AMF may not (yet) have any UE capabilities, which, in some examples, may also be signalled using arrow al4. Thus, in some examples, the principle according to the disclosure may be used to obtain UE capability information.

[0124] Arrow al5 of Fig. 16 symbolizes that another gNB, e.g., the "new" gNB E2d, may indicate to the initial gNB E2c, e.g., using a UE capability filter, a subset of UE capabilities of the UE El the new gNB E2d is interested to obtain. In some examples, the indication al5 may be fully independent, e.g., from the RRC procedures as, e.g., symbolized by arrows alO, all, al2, and may, e.g., be performed, for example, whenever a neighbouring relation between the gNBs E2c, E2d is known.

[0125] Arrow al6 of Fig. 16 symbolizes the initial gNB E2c requesting, from the UE, the UE capabilities, as, e.g., specified by at least one of a) the new gNB E2d (e.g., using the indication al5) , or b) the AMF E3 (see, for example, arrow al4) . In other words, in some examples, at least one of the devices E2d, E3 may specify (see arrows al4, al5) one or more capabilities of the UE which the initial gNB E2c should determine, e.g., by requesting from the UE, and, in some examples, the initial gNB may request this information as, e.g., specified by at least one of the devices E2d, E3, e.g., using the request al6.

[0126] In some examples, the UE El may send the requested information, e.g., related to the specified capabilities of the UE, to the network, e.g., to the initial gNB, see arrow all. In some examples, the requested information may be sent, for example, "one by one", e.g., using one message from the UE to the initial gNB per unit of the requested information (e.g., per capability container) . In some examples, one or more units of requested information, e.g., in the form of one or more capability containers, may be sent by the UE to the initial gNB within one message.

[0127] In some examples, the initial gNB E2c may send a message al8 comprising at least a portion of the requested information (e.g., as specified by at least one of the devices E2d, E3, see the arrows al4, al5) to the AMF E3. In some examples, the AMF E3 may store the received information, e.g., characterizing the requested UE capability information, e.g., based on a received UE capability filter or ID, e.g., instead of overwriting a potentially existing UE capability.

[0128] In some examples, after that, the RRC connection may be released for the initial gNB, see arrow al9. In some examples, e.g., after that, the UE El may reselect to another cell, e.g., associated with the new gNB E2d, see element E4 of Fig.

[0129] 16.

[0130] In some examples, Fig. 16, the UE El may send a new RRC Setup Request a20 in the new cell. Arrow a21 symbolizes an RRC Setup in the new cell, and arrow a22 symbolizes the UE sending an RRC Setup Complete message, e.g., including a Non-Access Stratum (NAS) container that may include the initial UE message. In some examples, the new gNB E2d may send the initial UE message to the AMF E3, see arrow a23, e.g., adding a filter identification or UE capability filter to the message a23.

[0131] In some examples, Fig. 16, e.g., when the AMF E3 sends an initial UE context setup, see arrow a24, it may include a correct UE capability (e.g., based on the indicated UE ID and UE capability filter) to the message a24.

[0132] In some examples, e.g., by using the principle according to the disclosure, the new gNB E2d now knows a, for example needed, UE capability and can, for example, avoid a, for example additional, UE capability enquiry in this phase. Rather, in some examples, the new gNB E2d may, e.g., directly, configure the UE with the needed configuration, see the example RRC Reconfiguration message a25. Arrow a26 symbolizes the UE sending an RRC Reconfiguration Complete message to the new gNB E2d.

[0133] Some examples, Fig. 17, relate to a computer program PRG comprising instructions INSTR which, when executed by an apparatus 100, 100', 200, 200', 400, 400', cause the apparatus 100, 100', 200, 200', 400, 400' to perform at least some aspects of the method (s) according to the disclosure. Some examples, Fig. 17, relate to a computer-readable storage medium SM, for example a non-transitory computer-readable storage medium, SM, comprising the computer program PRG according to the disclosure.

[0134] Some examples, Fig. 17, relate to a data carrier signal DCS carrying and / or characterizing the computer program PRG according to the disclosure.

[0135] In some examples, the principle according to the disclosure may, e.g., be used to enable a communication system 1000 (Fig. 2) or a network device 10, 20, 22 to collect, e.g., build and store, UE capability information, e.g., in the background (e.g., repeatedly, e.g., regularly or periodically) .

[0136] In some examples, the principle according to the disclosure may, e.g., be used to, e.g., promptly, deliver correct capability information of a terminal device, e.g., for a new handover target. In some examples, a UE may be requested to provide at least a part of its capability information, e.g., in the form of one or more capability containers, e.g., according to information specified by at least one further entity 20, 22 (Fig. 2) , the information e.g. characterizing or representing one or more capability filters (e.g., with different frequency bands requested for each such capability filter) . In some examples, the UE may provide the requested capability information in the order they are requested. In other words, in some examples, the UE may, e.g., process one capability request or enquiry first, then the next capability request or enquiry, and so on.

[0137] In some examples, Fig. 2, a target gNB 20 may indicate in advance (e.g., during an Xn setup or via another, e.g., new, procedure) to the source gNB 10 a UE capability that it requires, e.g., to configure the UE 30 for a handover from the source gNB 10 to the target gNB 20. In some examples, the indication may, e.g., characterize or comprise a UE capability band filter for a UE capability enquiry or request the target gNB 20 may wish to use for the UE 30, or, in some examples, e.g., in general, one or more bands for which the target gNB 20 may wish to obtain the UE capabilities. In some examples, the source gNB 10 may request the UE 30 to send the relevant capabilities, e.g., to the source gNB 10, e.g., when (e.g., while) the UE 30 is connected to the source gNB 10.

[0138] In some examples, the gNB 10 may request from UE 30 one or more, e.g., several, sets of UE capabilities, and, in some examples, e.g., after collecting all of the several sets of UE capabilities, the gNB 10 may send at least a part of these several sets of UE capabilities to a further entity, such as the AMF 22.

[0139] In some examples, e.g., when a UE makes a new call setup and an initial message is sent from the new gNB to the AMF, see, for example, arrow a23 of Fig. 16, the gNB may include information e.g. about needed band combinations of the UE into the message a23. In some examples, the AMF E3 may then, e.g., directly, include the correct UE capability into the message a24, and the new gNB E2d can, e.g., avoid an additional UE capability enquiry.

[0140] In some examples, Fig. 16, e.g., alternatively or additionally, the UE El may include information characterizing a latest "UE capability band filter", e.g., into the message al2, e.g., to let the initial gNB E2c know which capabilities were last inquired or the UE is currently utilizing (e.g., in case the UE capabilities have changed due to some reason) . In some examples, the use of multiple capability sets may allow to have only specific band combinations in the capabilities.

[0141] In some examples, Fig. 2, the gNB 10 may store band combination specific UE capability information, e.g., to a common data base DB . In some examples, in this case, e.g., when a handover is triggered, the gNB 10 may fetch a neighboring cell-optimized capability from the database DB, or, alternatively may deliver keys to the common database DB, e.g., to check available capabilities.

[0142] In some examples, Fig. 2, the principle according to the disclosure enables a target gNB 20 to configure the UE 30, e.g., for a desired feature, e.g., without first enquiring a respective UE capability. In some examples, this may enable to avoid temporary performance problems, e.g., for the UE, or even a failure, e.g., if the UE actually needs a fast handover to a next cell of a new gNB 20 (e.g., since a conventional UE capability enquiry may take some time, but a handover might need to be fast) .

[0143] In some examples, Fig. 2, the principle according to the disclosure enables to avoid or mitigate problems as may be experienced by conventional communication systems, where a UE triggers a new RRC setup, e.g., after an initial UE connection. In this case, in conventional approaches, a UE capability is typically already stored to an AMF, and the AMF may deliver the capability for a gNB in the initial context setup. In this case the old capability may be collected in totally different side of the network in the AMF area and hence may not actually at all be useful for the new RRC setup. In this case, in a conventional approach, the gNB may need to enquiry the capability again from the UE . This causes additional delay for the connection setup procedure, reducing the ef ficiency of the UE configuration ( since it will be based on only very basic mandatory capabilities ) . After the gNB receives the UE capability it updates the AMF with new capability and in this case AMF will overwrite the existing capability with new . Hence the same problem may continue after every setup i f the UE is operating in an area where the cell capabilities change . In some examples , at least some of these problems may be avoided or mitigated by using the principle according to the disclosure .

Claims

Claims1. An apparatus (100) for a network device (10) , the apparatus (100) comprising at least one processor (102) , and at least one memory (104) storing instructions (106) that, when executed by the at least one processor (102) , cause the network device (10) to: receive (300) , from a further network device (20) , an indication (IND) to request, from a terminal device (30) associated with the network device (10) , first information (II) comprising requested capabilities of the terminal device, wherein the requested capabilities are determined by the further network device (20) , transmit (302) a request (REQ-11) for the first information (II) to the terminal device (30) , receive (304) a response (RESP-I1) comprising the first information (II) .

2. The apparatus (100) according to claim 1, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: transmit (306; 306a; 306b) at least a part (II' ) of the first information (II) to at least one further entity (20, 22) .

3. The apparatus (100) according to claim 2, wherein the at least one the further entity (20, 22) is at least one of: a) the further network device (20) , or b) an access and mobility function (22) .

4. The apparatus (100) according to any of the preceding claims, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: transmit (306a) at least a part (II' ) ofthe first information (II) within a handover request (a5) to the further network device (20) .

5. The apparatus (100) according to any of the claims 2 to4, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: determine (310) which part (II' ) of the first information (II) to transmit to the at least one further entity (20, 22) , transmit (312) at least the determined part (II' ) to the at least one further entity (20, 22) .

6. The apparatus (100) according to any of the preceding claims, wherein the indication (IND) characterizes or comprises at least one of: a) a capability filter (CAP- FILT) , or b) at least one frequency band (FB) for which the network device (10) should request capabilities of the terminal device (30) .

7. The apparatus (100) according to any of the preceding claims, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: request (320) , from the terminal device (30) , to provide one or more sets of capabilities of the terminal device (30) , based on the indication (IND) , transmit (324) at least one set (SET-CAP) of the one or more sets of capabilities of the terminal device (30) to the at least one further entity (20, 22) .

8. The apparatus (100) according to any of the preceding claims, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: receive (330) second information (12) from the terminal device (30) , the second information (12) characterizing at least one of: a) capability filterinformation last inquired from the terminal device (30) , or b) an indication of capabilities the terminal device (30) is currently using.

9. The apparatus (100) according to any of the preceding claims, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: store (332) at least one of a) the first information (II) , or b) the second information (12) .

10. The apparatus (100) according to any of the preceding claims, wherein the instructions (106) , when executed by the at least one processor (102) , cause the network device (10) to: receive (340) the indication (IND) , determine (342) , whether the first information (II) is available at the network device (10) or at a common database (DB) , based on the determination (342) , transmit (344) at least one of a) the first information (II) , or b) a reference (REF-11) to the first information (II) as stored in the database (DB) to the at least one further entity (20, 22 ) .

11. An apparatus (100' ) for a network device (10) , the apparatus (100' ) comprising means (102' ) for: receiving (300) , from a further network device (20) , an indication (IND) to request, from a terminal device (30) associated with the network device (10) , first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by the further network device (20) , transmitting (302) a request (REQ-11) for the first information (II) to the terminal device (30) , receiving (304) a response (RESP- II) comprising the first information (II) .

12. A method for a network device (10) , comprising: receiving(300) , from a further network device (20) , an indication (IND) to request, from a terminal device (30) associated with the network device (10) , first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by the further network device (20) , transmitting (302) a request (REQ-11) for the first information (II) to the terminal device (30) , receiving (304) a response (RESP- II) comprising the first information (II) .

13. An apparatus (200) for a network device (20) , the apparatus (200) comprising at least one processor (202) , and at least one memory (104) storing instructions (206) that, when executed by the at least one processor (202) , cause the network device (20) to: transmit (350) to a further network device (20) , which is associated with a terminal device (30) , an indication (IND) to request, from the terminal device (30) , first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by the network device (20) .

14. The apparatus (200) according to claim 13, wherein the instructions (206) , when executed by the at least one processor (202) , cause the network device (20) to: receive (352) at least a part (II' ) of the first information (II) .

15. An apparatus (200' ) for a network device (20) , the apparatus (200' ) comprising means (202' ) for: transmitting (350) to a further network device (20) , which is associated with a terminal device (30) , an indication (IND) to request, from the terminal device(30) , first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by the network device (20) .

16. A method for a network device (20) , comprising: transmitting (350) to a further network device (20) , which is associated with a terminal device (30) , an indication (IND) to request, from the terminal device (30) , first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by the network device (20) .

17. An apparatus (400) for a terminal device (30) , the apparatus (400) comprising at least one processor (402) , and at least one memory (404) storing instructions (406) that, when executed by the at least one processor (402) , cause the terminal device (30) to: receive (500) , from a network device (10) , a request (REQ-11) for first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by a further network device (20) , transmit (502) a response (RESP-I1) comprising the first information (II) .

18. The apparatus (400) according to claim 18, wherein the instructions (406) , when executed by the at least one processor (402) , cause the terminal device (30) to perform at least one of: a) transmitting (510) second information (12) to the network device (10) , the second information (12) characterizing at least one of: al) capability filter information last inquired from the terminal device (30) , or a2) an indication ofcapabilities the terminal device (30) is currently using, or b) including (512) the second information (12) in a Radio Resource Control message (al2) .

19. An apparatus (400' ) for a terminal device (30) , the apparatus (400' ) comprising means (402' ) for: receiving (500) , from a network device (10) , a request (REQ-11) for first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by a further network device (20) , transmitting (502) a response (RESP-I1) comprising the first information (II) .

20. A method for a terminal device (30) , comprising: receiving (500) , from a network device (10) , a request (REQ-11) for first information (II) comprising requested capabilities of the terminal device (30) , wherein the requested capabilities are determined by a further network device (20) , transmitting (502) a response (RESP- II) comprising the first information (II) .

21. A network device (10, 20; 22) comprising at least one apparatus (100; 100' ; 200; 200' ) according to any of the claims 1 to 11 or 13 to 15.

22. A terminal device (40) comprising at least one apparatus(400; 400' ) according to any of the claims 17 to 19.

23. A communication system (1000) comprising at least one of: a) an apparatus (100; 100' ; 200; 200' ; 400; 400' ) according to any of the claims 1 to 11 or 13 to 15 or 17 to 19, or b) a network device (10, 20, 22) according to claim 21, or c) a terminal device (30) according to claim 22.

24. A computer program (PRG) comprising instructions (INSTR) which, when executed by an apparatus (100; 100' ; 200; 200' ; 400; 400' ) , cause the apparatus (100; 100' ; 200; 200' ; 400; 400' ) to perform at least some aspects of the method according to any of the claims 12 or 16 or 20.

25. A computer-readable storage medium, for example a non- transitory computer-readable storage medium, comprising the computer program (PRG) according to claim 24.

26. A data carrier signal carrying and / or characterizing the computer program (PRG) according to claim 24.

Images