Apparatus, method and computer program

Abstract

An apparatus is provided that includes means for collecting energy-related information associated with one or more control plane transactions of an application programming interface of a network entity and means for reporting the energy-related information associated with the one or more control plane transactions.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to communication systems, and specifically, but not exclusively, to apparatus, methods, and computer programs relating to energy-related information. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or as a facility that provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] These communication networks operate according to standards (such as those provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards include the so-called 5G (fifth generation) standard issued by 3GPP. Summary of the Invention

[0004] Some exemplary embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments of this disclosure, nor are they intended to be used to limit its scope. Other features, aspects, and elements will readily become apparent to those skilled in the art in light of this disclosure.

[0005] According to a first aspect, an apparatus is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: collecting energy-related information associated with one or more control plane transactions of an application programming interface of a network entity (e.g., supported therein, configured to be supported therein); and reporting energy-related information associated with the one or more control plane transactions.

[0006] Energy-related information associated with one or more control plane transactions may include information about the type of one or more control plane transactions within the control plane transaction.

[0007] This device can be made to update the count when the corresponding control plane transaction occurs.

[0008] The device can be configured to update a count for one or more control plane transactions based on the type of the control plane transaction, wherein at least two different types of control plane transactions cause the count to be updated with different values.

[0009] The corresponding count can be provided for the corresponding type of control plane transaction, and for each transaction of the same type, the corresponding count is updated with the same value.

[0010] The apparatus can be caused to perform determining whether the collected energy related information associated with one or more control plane transactions has reached a respective reporting threshold, and reporting the energy related information associated with one or more control plane transactions when the reporting threshold has been reached.

[0011] The reporting threshold can comprise a count threshold associated with the count or a respective count.

[0012] The apparatus can be caused to perform periodically reporting the energy related information associated with one or more control plane transactions.

[0013] A control plane transaction of the one or more control plane transactions is associated with at least one of: a user equipment; a network slice; or a data network name.

[0014] The energy related information associated with one or more control plane transactions can comprise information identifying at least one of: a user equipment, a given network slice, or a given data network name associated with a respective control plane transaction.

[0015] The apparatus can provide a network function. The apparatus can be an access node. The apparatus can provide an operation, administration and maintenance function.

[0016] According to a second aspect, a method, the method comprising: collecting energy related information associated with one or more control plane transactions of an application programming interface of a network entity (e.g. at which it is supported, configured to be supported at which); and reporting the energy related information associated with one or more control plane transactions.

[0017] The energy related information associated with one or more control plane transactions can comprise information on a type of one or more of the control plane transactions.

[0018] The method can comprise updating the count when a respective control plane transaction occurs.

[0019] The method can comprise updating the count for one or more control plane transactions based on a type of the control plane transaction, at least two different types of control plane transactions causing the count to be updated with different values.

[0020] The respective count can be provided for a respective type of control plane transaction, and for each transaction of the same type, the respective count is updated with the same value.

[0021] The method can comprise determining whether the collected energy related information associated with one or more control plane transactions has reached a respective reporting threshold, and reporting the energy related information associated with one or more control plane transactions when the reporting threshold has been reached.

[0022] The reporting threshold can comprise a count threshold associated with the count or respective count.

[0023] The method can comprise periodically reporting energy-related information associated with one or more control plane transactions.

[0024] A control plane transaction of the one or more control plane transactions is associated with at least one of: a user equipment; a network slice; or a data network name.

[0025] The energy-related information associated with the one or more control plane transactions can comprise information identifying at least one of: a user equipment, a given network slice, or a given data network name associated with a respective control plane transaction.

[0026] The method can be performed by an apparatus. The apparatus can provide a network function. The apparatus can be an access node. The apparatus can provide an operation, administration and maintenance function.

[0027] According to a third aspect, there is provided an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving energy-related information associated with one or more control plane transactions; and using the received energy-related information associated with the one or more control plane transactions to provide charging information.

[0028] The charging information can comprise a charging data record.

[0029] The energy-related information can be as described in relation to the first aspect.

[0030] The apparatus can provide a charging function.

[0031] According to a fourth aspect, there is provided a method comprising: receiving energy-related information associated with one or more control plane transactions; and using the received energy-related information associated with the one or more control plane transactions to provide charging information.

[0032] The charging information can comprise a charging data record.

[0033] The energy-related information can be as described in relation to the second aspect.

[0034] The method can be performed by an apparatus. The apparatus can provide a charging function.

[0035] According to a fifth aspect, there is provided an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving energy-related information associated with one or more control plane transactions; and means for analysing the received energy-related information associated with one or more control plane transactions to provide an energy-related information analysis.

[0036] The energy-related information can be as described with reference to the first aspect.

[0037] The apparatus can provide a network data analytics function.

[0038] According to a sixth aspect, there is provided a method comprising: receiving energy-related information associated with one or more control plane transactions; and analysing the received energy-related information associated with one or more control plane transactions to provide an energy-related information analysis.

[0039] The energy-related information can be as described with reference to the second aspect.

[0040] The method can be performed by an apparatus. The apparatus can provide a network data analytics function.

[0041] Further aspects and features can be gleaned from the claims.

[0042] According to a further aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform any of the preceding methods.

[0043] According to a further aspect, there is provided a computer program comprising instructions which, when executed, cause any of the preceding methods to be performed.

[0044] According to an aspect, there is provided a computer program comprising computer executable instructions which cause any of the preceding methods to be performed.

[0045] According to an aspect, there is provided a computer readable medium comprising instructions stored thereon for performing at least one of the above methods.

[0046] According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions which, when executed by an apparatus, cause the apparatus to perform any of the methods set out herein.

[0047] According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions which, when executed, cause any of the preceding methods to be performed.

[0048] According to an aspect, there is provided a non-transitory tangible storage medium comprising program instructions stored thereon for performing at least one of the above methods.

[0049] In the foregoing description, numerous different aspects have been described. It is understood that additional aspects can be provided by combinations of any two or more of the aspects described herein.

[0050] Various other aspects are described in the detailed description and in the claims. BRIEF DESCRIPTION OF DRAWINGS

[0051] Some example embodiments will now be described, by way of non-limiting and illustrative examples only, with reference to the accompanying FIGS.:

[0052] Figure 1 A representation of a fifth generation (5G) communication system is shown;

[0053] Figure 2 A representation of an apparatus of a communication system in accordance with some example embodiments is shown; Figure 1

[0054] Figure 3 An example process of some example embodiments is shown;

[0055] Figure 4 Interaction between some parts of a 5G communication system of some example embodiments is shown;

[0056] Figure 5 Another example process of some example embodiments is shown;

[0057] Figure 6 A method of some example embodiments is shown;

[0058] Figure 7 Another method of some example embodiments is shown; and

[0059] Figure 8 A further method of some example embodiments is shown. DETAILED DESCRIPTION

[0060] In the following, some example embodiments of the present disclosure are provided in a 5G system. However, this is by way of illustrative and non-limiting examples only and other example embodiments of the present disclosure can be provided in other systems (or combinations thereof).

[0061] Figure 1 ​A schematic representation of a communication system operating based on a fifth generation radio access technology, often referred to as a 5G system (5GS), is shown, and some example embodiments can be implemented therein. The 5GS can comprise a (radio) access network ((R)AN), a 5G core network (5GC), one or more application functions (AFs), and one or more data networks (DN). A user equipment (UE) can access or connect to one or more DNs via the 5GS.

[0062] The 5G (R)AN can comprise one or more base stations or radio access network (RAN) nodes, such as gNodeBs (gNBs). A base station or RAN node can comprise one or more distributed units connected to a central unit.

[0063] The 5GC can comprise various network functions, such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Location Management Function (LMF), a User Data Management (UDM), a User Plane Function (UPF), a Network Data Repository (NRF), a Network Exposure Function (NEF), a Service Communication Proxy (SCP), an Edge Application Server Discovery Function (EASDF), a Network Data Analytics Function (NWDAF), a Policy Control Function (PCF), a Network Slice Access Control Function (NSACF), a Network Slice Specific Authentication and Authorization Function (NSSAAF), and / or a Network Slice Selection Function (NSSF).

[0064] Figure 2 An example of an apparatus 200 is illustrated.

[0065] The apparatus 200 can comprise or implement one or more network functions as illustrated in Figure 1 The apparatus 200 can have at least one processor; and at least one memory storing instructions of one or more network functions as illustrated in Figure 1 The instructions, when executed by at least one of the at least one processor, cause operations or actions of the one or more network functions to be performed.

[0066] Alternatively, the apparatus 200 can comprise or implement at least part of a radio access node as illustrated in Figure 1 The apparatus 200 can have at least one processor; and at least one memory storing instructions of one or more network functions as illustrated in Figure 1 The instructions, when executed by at least one of the at least one processor, cause operations or actions of the radio access node to be performed.

[0067] Alternatively, the apparatus 200 can comprise or implement an operation, administration, and maintenance function. The apparatus 200 can have at least one processor; and at least one memory storing instructions of the operation, administration, and maintenance function that, when executed by at least one of the at least one processor, cause operations or actions of the operation, administration, and maintenance function to be performed.

[0068] In some examples, the apparatus 200 can comprise at least one random access memory (RAM) 211a, and / or at least one read-only memory (ROM) 211b. The apparatus 200 can comprise at least one processor 212, 213, and / or a network interface 214. The at least one processor 212, 213 can be coupled to the at least one memory, which in some examples is the RAM 211a and the ROM 211b. The at least one processor 212, 213 can be configured to execute suitable software code 215.

[0069] The software code 215 may, for example, comprise software code of at least one of the following: a network function, an operation, administration, and maintenance function, or a radio access node. The software code can comprise software code that allows, enables, or otherwise facilitates the apparatus to perform one or more operations of various example embodiments of the present disclosure (or portions thereof).

[0070] 5G communication systems, and upcoming 6G communication systems, are increasingly being designed to be energy efficient (e.g., to reduce their energy consumption) and to improve their energy efficiency.

[0071] Some example embodiments relate to energy efficiency. This can be in a 5G network, a 6G network, or higher, or any other suitable network.

[0072] In some example embodiments, a network can support energy consumption monitoring at per network slice and / or per subscriber granularity. This can be subject to the policies of the operator of the network.

[0073] In some example embodiments, a network can be able to monitor energy consumption for serving third parties. This can be subject to the policies of the operator of the network and / or subject to agreements with the third parties.

[0074] In some example embodiments, a network can be able to expose information about energy consumption for serving third parties. This can be subject to the policies of the operator of the network and / or subject to agreements with the third parties.

[0075] In some example embodiments, the network can be able to expose information about energy consumption for a service to an authorized third party. The information can include energy consumption information related to conditions of an energy credit (e.g., when energy consumption is reaching an energy credit). This can be subject to the policies of the operator of the network.

[0076] Some example embodiments relate to monitoring of energy consumption at a control plane. Some example embodiments relate to collection of energy related information. Some example embodiments relate to collection of counting information associated with control plane transactions. The counting information can provide energy related information.

[0077] The control plane transaction can involve a UE or can be between two or more network functions.

[0078] The control plane transaction can be an application programming interface of a network entity (e.g., at which it is supported, configured to be supported). The network entity can support or provide a network function.

[0079] In some example embodiments, the 5GC can be configured to handle and / or accommodate mechanisms that allow, enable, or otherwise facilitate a CSP (communication service provider) and / or an operator to learn about energy consumed in the network for a particular purpose caused by control plane signaling.

[0080] In some example embodiments, a control plane transaction can be identified. The control plane transaction can be logged. The control plane transaction can be logged in at least one of: NF level; NF instance level; NF service instance level; NF / slice level; NF / slice / DNN level; slice level; DNN level; or per UE level. This can depend on the level of granularity required. The network operator can assign metrics to each of these control plane transactions. This can be used to derive the overall energy consumption. This can be because NF service level transactions received at or responded by a particular NF are aggregated. This can be aggregated per API transaction or per API message.

[0081] For example, OAM (Operation, Administration, and Maintenance) functions can collect information about the number of control plane transactions per service operation at one or more or all of the above granularity levels. For example, OAM can report the number or volume of transactions in one or more CDRs (Charging Data Records) or other reporting mechanisms. Control plane transactions can be logged at at least one of: NF level; NF instance level; NF service instance level; NF / slice level; NF / slice / DNN level; slice level; DNN level; or per UE level. For example, the number of control plane transactions can be reported per slice; per DNN; or per UE. For example, the number of control plane transactions per slice, for a given DNN, and for a given UE.

[0082] The CDR or other report can report the identity and / or type of control plane transaction. This can be per UE. The CDR or other report can alternatively or additionally report the relevant number of control plane transactions.

[0083] One or more functions (e.g. OAM functions, or systems, or any other suitable “background” system or function) can assign a weight to each control plane transaction.

[0084] Alternatively, the NF providing the number of control plane transactions can send a weighted average or count for control plane transactions. The NF can determine the weighted count or average. The weight per control plane transaction can be provided at the NF providing the weighted average or count. In some examples, the type and / or identity of the control plane transaction type can be omitted. In some example embodiments, the weighted average can be sent to a CHF and / or NWDAF.

[0085] In some example embodiments, a respective count can be determined for each type of control plane transaction. In other example embodiments, a single count can be provided. The amount by which the count is updated can depend on the type of control plane transaction.

[0086] By way of non-limiting and illustrative example only, the weight for a control plane transaction using Npcf AM Policy Association-Create can be 2 points. The weight for a control plane transaction using Npcf AM Policy Association-Update can be 1 point. Each control plane transaction type can be associated with a respective weight. The respective weight is applied to the count for the respective control plane transaction depending on the type of control plane transaction.

[0087] In some example embodiments, alternatively or additionally, the respective weight can depend on at least one of: NF instance; slice; AF instance identity; or the like.

[0088] Alternatively or additionally, the count information can alternatively or additionally be reported to a NWDAF or other consumer of this information.

[0089] For example, the PCF can register for updates from the NWDAF to understand the energy consumption limits that can have been defined for third parties.

[0090] The NF profile can provide information of the NF instance. The NF profile can be stored in the NRF and can be fetched from the NRF during e.g. NF discovery. The NF profile for a NF can comprise an energy profile assigned to the service provided by the NF. The energy profile can indicate the number of control plane transactions to be collected. The energy profile can indicate whether a weight is to be applied by the NF. The energy profile can indicate the energy related information to be reported by the NF. The energy profile can indicate a reporting trigger or a reporting frequency. The energy provision can define a measurement unit (e.g. weight) for control plane transactions of a service and / or service instance and / or NF. The measurement unit can depend on the time of day and / or the location of the NF instance associated with the control plane transaction and / or other factors that can influence the cost of the control plane transaction.

[0091] The profile can provide an identity of the NF instance. The identity can be unique. The profile can provide a type of the NF. The profile can provide a status of the instance.

[0092] For example, the NF profile can be defined in the following table.

[0093] The NF service definition for a NF service can provide information about a given NF service instance and can be fetched from e.g. the NRF. The NF service definition can be part of the NF profile of the NF instance. The NF service definition for a NF service can comprise an energy profile assigned to the service provided by the NF. The energy profile can indicate the number of control plane transactions to be collected. The energy profile can indicate whether a weight is to be applied by the NF. The energy profile can indicate the information to be reported by the NF. The energy profile can indicate a reporting trigger or a reporting frequency. The energy provision can define a measurement unit (e.g. weight) for control plane transactions of a service and / or service instance and / or NF. The measurement unit can depend on the time of day and / or the location associated with the control plane transaction.

[0094] The definition can provide an identity of the service instance within a given NF instance. The identity can be unique. The definition can provide a name of the service instance. For example, the NF service definition can be defined in the following table.

[0095] The NWDAF (or other function) can register with the NRF to learn or determine the state and up-to-date NF profile and / or NF service definition. The NF profile and / or NF service definition can be as described previously. The NF profile and / or NF service definition can allow, enable, or otherwise facilitate the NWDAF (or other function) to be aware of the energy profile.

[0096] When the NWDAF provides energy usage information to a consumer of analytics (e.g. PCF), the NF load level information definition is used by the NWDAF. The NWDAF provides “NF load level information” and when the NWDAF provides “NF load level information”, and this includes energy usage information, the NWDAF can provide “NF load level information” to, for example, a PCF. The NF load level information definition for a NF service can include the energy profile usage that is assigned to the service provided by the NF, data has been collected from the NF. This would provide information related to energy usage associated with control plane transactions that are associated with the NF. This can be, for example, in the form of a count such as described previously.

[0097] The definition can provide a type of NF instance. The definition can provide an identity of the NF instance. The definition provides an identity of a set of NF instances. The definition can provide an identity of a single network slice selection assistance information, S-NSSAI. If the S-NSSAI is provided during a subscription for an event notification procedure, it is provided.

[0098] The definition can include an application function identifier that identifies an application function (e.g. third party) associated with the service.

[0099] For example, the NF load level information definition can be defined in the following table.

[0100] Reference Figure 3 which schematically illustrates a method of some example embodiments.

[0101] As mentioned at SI, the AF and / or NEF provides parameters related to traffic impact, AM (access and mobility policy) and / or the like. These parameters can include one or more profiles or definitions described herein. The parameters can include energy profile parameters related to control plane transactions. These parameters can be provided to the NWDAF, PCF and / or UDM. Such a request can also be monitored by the 5GC. In some example embodiments, the AF is an external entity to the 5GC. The 5GC can take into account the analysis and identification of energy consumption for transactions with the AF.

[0102] At S2, as mentioned, the NWDAF can determine the load or energy usage associated with control plane transactions. This can be based on energy profile usage information.

[0103] At S3, as mentioned, during registration and / or PDU (Protocol Data Unit) session procedures, the AMF and / or SMF can subscribe to notifications from the NWDAF. These notifications can include information related to energy usage associated with control plane transactions. For example, counts (such as the aforementioned) or units consumed can be provided on a per slice and / or AF basis. Based on the notifications, the AMF and / or SMF can implement associated policies for the AM and / or SMF.

[0104] Some example embodiments can allow, enable, or otherwise facilitate the 5GC (e.g., NWDAF) to learn or determine energy consumption based on control plane signaling. The 5GC (e.g., NWDAF) can dynamically learn energy consumption.

[0105] Some example embodiments can allow, enable, or otherwise facilitate the 5GC (e.g., NWDAF) to learn or determine whether more reporting is being exchanged between the UPF and the SMF. These reports can be provided via the control plane.

[0106] In some example embodiments, if the control plane reporting involves location updates to the NWDAF associated with a UE, the NDWAF can de-activate the location update trigger by updating the subscription. Alternatively, the NWDAF can reduce the number of location reports to only X within Y minutes.

[0107] Based on various levels (such as slice, UE, and / or the like), based on energy consumption status, these can be enhanced at the AMF to extend or limit the number of UE location reports to NF consumers.

[0108] The OAM and / or NWDAF can be configured to dynamically provide information related to energy consumption associated with control plane transactions.

[0109] Reference is made to Figure 4 which schematically illustrates interactions between some parts of a 5G communication system of some example embodiments. In Figure 4 a count of the number of control plane transactions is collected or determined by a network function, NF (e.g., AMF or SMF) and / or by a radio access node, RAN. A report on the count is provided to at least one of: a charging function, CHF; or a network data analytics function, NWDAF. It should be appreciated that in some example embodiments, the count is reported only to the CHF; and in other example embodiments, the count is reported only to the NWDAF.

[0110] The NWDAF can use the received reports to perform energy analytics. For example, the NWDAF can determine control operations that cost more for a UE, or for a slice or for a DNN. For example, the NWDAF can determine the energy load consumed by a slice for serving during peak hours or off-peak hours and define SLA (Service Level Agreement) for the corresponding slice accordingly. For example, the NWDAF can determine the load consumed at the 5GS for serving a specific AF that has been implemented for a traffic impact scenario.

[0111] The NWDAF can provide output to NFs that subscribe to this information for charging, exposure, trend analysis or policy actions.

[0112] The NWDAF can provide output to OSS. The OSS can decide whether a NF is underutilized and can be shut down or whether a NF is overutilized and needs additional network resources.

[0113] The NWDAF can provide output to a Network Exposure Function, NEF, for exposure for analytics.

[0114] The CHF can provide output to a NEF for exposing charging related information.

[0115] The CHF can provide output to a charging entity.

[0116] Reference is made to Figure 5 wherein a method of some example embodiments is shown.

[0117] At 1, it is mentioned that a network function producer provides a service. The service can be provided by a service operation or by other signaling. The network function can provide a control plane network function for the service. For example, the service can be provided by way of a network slice.

[0118] At 2, it is mentioned that it is determined whether the network function is configured to report control plane transaction counts. The determination can be based on a network function profile or a definition of the network function service. The network function profile or the definition of the network function service can be as described before.

[0119] If it is determined that the network function is not configured to report control plane transaction counts for the service, the method reverts to the part of the method mentioned at 1.

[0120] If it is determined that the network function is configured to report control plane transaction counts, the part of the method referred to at 3 is performed. In this part of the method, the network function will update the count for control plane transactions. For example, a counter can be provided. The counter can be incremented or decremented with each control plane transaction. The counter can be implemented as a hardware counter, a software counter, or a combination of hardware and software.

[0121] In some example embodiments, each control plane transaction causes the counter to change the count by 1. This can be used in cases where the network function reports the count of the counter without weighting.

[0122] In other example embodiments, the amount by which the counter is changed will depend on the type of control plane transaction. This can be used in cases where the network function reports the count of the counter with weighting.

[0123] At 4, it is determined whether the count will be reported. The count of the counter can be reported periodically. A reporting frequency can be defined. The count can be associated with a time window. Alternatively, the count can be reported when it reaches a given threshold. In some examples, the reporting can include information about the time taken to reach the threshold count.

[0124] In some example embodiments, the count can be reported together with other information unrelated to the control plane transaction count. This can be used to reduce signalling. In some examples, information about the time period associated with the count can be reported together with the count.

[0125] If it is determined that the counter will not be reported, the method falls back to the part of the method referred to at 1.

[0126] If it is determined that the counter will be reported, a determination is made as to whether the counter is reported with weighting, as referred to at 5.

[0127] If it is determined that the counter will not be reported with weighting, the network function reports information related to the count and information about the type of control plane transaction, as referred to at 6. Subsequently, the method falls back to the part of the method referred to at 1.

[0128] If it is determined that the counter will be reported with weighting, the network function reports a weighted count value, as referred to at 7. In this case, there is no need to include information about the type of control plane transaction. Subsequently, the method falls back to the part of the method referred to at 1.

[0129] The NF or RAN can be configured or requested on the control plane to report the count. The count can be provided by:

[0130] A control plane transaction count is provided per service type / control plane transaction type. For example, each control plane transaction can increment the count by one; or

[0131] A weighted count. For example, each control plane transaction increments the count by a weight for the control plane transaction type.

[0132] The NF / RAN can receive a request to report the count by configuration or via a subscription / notification procedure.

[0133] The CHF can report information to a charging and / or exposure function.

[0134] The NWDAF can provide output to the NEF for exposure for analytics. The NWDAF can provide output to a PCF (e.g., so that the PCF can take policy actions based on the analytics performed by the NWDAF), or to an OSS (e.g., so that the OSS can decide whether a function is underutilized and can be shut down).

[0135] Reference Figure 6 which illustrates a method of some example embodiments.

[0136] The method can be performed by an apparatus. The apparatus can be configured to implement a network function (or part of a network function), an operation, administration and maintenance function (or part of an operation, administration and maintenance function), an access node (or part of an access node). In some example embodiments, the access node can be a centralized unit.

[0137] The apparatus can comprise suitable circuitry for providing the method.

[0138] Alternatively or additionally, the apparatus can comprise at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to provide the method.

[0139] Alternatively or additionally, the apparatus can be such as discussed in Figure 2 connection with

[0140] The method can be provided by computer program code or computer executable instructions.

[0141] The method can comprise, as mentioned at Al, collecting energy related information associated with one or more control plane transactions of an application programming interface of a network entity (e.g., at which it is supported, configured to be supported).

[0142] The method can comprise, as mentioned at A2, reporting the energy related information associated with the one or more control plane transactions. It will be appreciated that Figure 6The method outlined in the Summary can be modified to include any of the features previously described.

[0143] Reference is made to Figure 7 which illustrates methods of some example embodiments.

[0144] The method can be performed by an apparatus. The apparatus can provide a network function. The network function can comprise a charging function.

[0145] The apparatus can comprise suitable means, such as circuitry for providing the method and / or network function.

[0146] Alternatively or additionally, the apparatus can comprise at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to at least provide the following method and / or network function.

[0147] Alternatively or additionally, the apparatus can be such as Figure 2 as discussed in connection with

[0148] The method can be provided by computer program code or computer executable instructions.

[0149] The method can comprise, as mentioned at B1, receiving energy related information associated with one or more control plane transactions.

[0150] The method can comprise, as mentioned at B2, analysing the received energy related information associated with one or more control plane transactions to provide an energy related information analysis.

[0151] It will be appreciated that Figure 7 The method outlined in the Summary can be modified to include any of the features previously described.

[0152] Reference is made to Figure 8 which illustrates methods of some example embodiments.

[0153] The method can be performed by an apparatus. The apparatus can provide a network function. The network function can comprise a network data analytics function.

[0154] The apparatus can comprise suitable means, such as circuitry for providing the method and / or network function.

[0155] Alternatively or additionally, the apparatus can comprise at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to at least provide the following method and / or network function.

[0156] Alternatively or additionally, the apparatus can be such as Figure 2The method can be provided by computer program code or computer executable instructions.

[0157] The method can be provided by computer program code or computer executable instructions.

[0158] The method can comprise, as mentioned at CI, receiving energy related information associated with one or more control plane transactions.

[0159] The method can comprise, as mentioned at C2, analysing the received energy related information associated with one or more control plane transactions to provide an energy related information analysis.

[0160] It will be appreciated that, Figure 8 The method outlined in the Summary can be modified to include any of the features described previously.

[0161] The computer program code can be downloaded and stored in one or more memories of the apparatus described herein.

[0162] Thus, although certain example embodiments have been described above by way of non-limiting and illustrative examples, and with reference to certain example architectures, techniques and standards for communication systems operated by mobile network operators, additional example embodiments can be applied to any other suitable form of communication system than those illustrated and described herein. For example, some example embodiments have been described in relation to a 5G communication system (5GS). It will be appreciated that other example embodiments can be provided in any other suitable communication system(s) or in any suitable combination with a 5GS.

[0163] As used herein, “at least one of ” and “one or more of ” and similar phrases, where a list of two or more elements is preceded by “at least one of” or “one or more of”, means at least one of any individual element in the list of two or more elements or at least one of any two or more of the elements in the list of two or more elements or at least all of all the elements in the list of two or more elements. As used herein, “and / or”, when used between two or more elements, means at least one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0164] As used herein, unless expressly stated to the contrary, performance of the respective feature, step, or functionality "in response to" an event is not indicative of performance of the respective feature, step, or functionality immediately in response to the event, as one or more intermediate features, steps, or functionalities can be performed (at least partially) between performance of the respective feature, step, or functionality and the event. Similarly, performance of the respective feature, step, or functionality "based on" an event is not indicative of performance of the respective feature, step, or functionality solely based on the event, as the respective feature, step, or functionality can additionally be based, at least in part, on one or more other features, steps, or functionalities other than the event.

[0165] In general, the various example embodiments of the present disclosure can be implemented in hardware or special-purpose circuits, software, logic, or any combination thereof. Some aspects of the disclosure can be implemented in hardware, while other aspects can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited in this regard. While various aspects of the disclosure can be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein can be implemented in, as non-limiting and illustrative examples, hardware, software, firmware, special-purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0166] As used herein, the term "circuitry" can refer to one or more, combined or separate, hardware circuits implemented in, for example, only analog circuitry and / or only digital circuitry, and (a) a hardware-only circuit implementation (such as only analog circuitry and / or only digital circuitry), and (b) a combination of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuits with software / firmware, and (ii) any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus, such as a handset or server, to perform various functions, and (c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but has no software (firmware) present during operation.

[0167] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation that has a sole hardware circuit implementation or a sole processor or processor(s) implementation or a sole hardware circuit implementation and a sole processor or processor(s) implementation, as these terms are terms of art to those skilled in the art. As a further example, as used herein, the term circuitry also covers an implementation that has a hardware circuit and a processor (or multiple processors) and their associated software and / or firmware that are collectively configured to perform various aspects of the techniques described herein.

[0168] Various example embodiments of the present disclosure can be implemented by computer software executable by a data processor of the mobile device (such as a processor entity), or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, can be stored in any apparatus-readable data storage medium and includes program instructions to implement specific tasks. The program product can include one or more computer-executable components that, when executed by the program, configure the computer, or data processor, to perform any of the example embodiments of the present disclosure (or portions thereof). The one or more computer-executable components can include, but are not limited to, software agents, objects, and / or classes to perform specific tasks. Computer software products typically include at least one program instructions (or piece of code), that is stored in, or transmitted over, a data storage medium, such as a flash memory, a RAM memory, ROM memory, EEPROM memory, optical storage, or magnetic storage elements, or any suitable data storage medium known in the art.

[0169] Additionally, in this respect, it should be noted that any blocks of the logical flow of the figures can represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software can be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as DVD and the data variants thereof, CD. The physical media is non-transitory media.

[0170] As used herein, the term "non-transitory" is solely to the limitation of the medium itself (i.e., tangible, as opposed to signals), and not to the durability of the data stored thereon (e.g., RAM vs. ROM).

[0171] The memory can be of any type appropriate for the local technical environment and can be implemented using any appropriate data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processor can be of any type appropriate for the local technical environment, and can include at least one of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), FPGAs, gate level circuits and processors (based on multi-core processor architectures, as non-limiting and illustrative examples).

[0172] Example embodiments of the present disclosure can be practiced in a variety of components such as integrated circuit modules. The design of integrated circuits is by nature a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on semiconductor substrates.

[0173] The foregoing description has provided by way of non-limiting and illustrative examples a full and informative description of the various example embodiments of the present disclosure. However, various modifications and adaptations can become apparent to those skilled in the relevant arts in view of the foregoing description, when read, not sequentially, in conjunction with the appended drawings and the associated detailed description of the disclosure. Indeed, other example embodiments encompassed within the scope of the present disclosure may be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. It is intended that the scope of the various example embodiments of the present disclosure, including their products, be limited only by the appended claims. Apart from their respective aspects and features, various example embodiments falling outside the scope of the claims, if any, are to be interpreted as examples useful for understanding the various example embodiments of the present disclosure. It should be noted that different claims may be pursued in related applications, such as divisional or continuation applications, with different claim scopes.

Claims

1. An apparatus comprising: A component used to collect energy-related information associated with one or more control plane transactions of the application programming interface of a network entity; as well as A component for reporting energy-related information associated with the one or more control plane transactions.

2. The apparatus of claim 1, wherein the energy-related information associated with the one or more control plane transactions includes information about the type of one or more control plane transactions.

3. The apparatus of claim 1 or 2, wherein the component for collecting energy-related information is configured to update the count when a corresponding control plane transaction occurs.

4. The apparatus of claim 3, wherein the component for collecting energy-related information associated with the one or more control plane transactions is configured to update the count for the one or more control plane transactions based on the type of the control plane transaction, wherein at least two different types of the control plane transactions cause the count to be updated with different values.

5. The apparatus of claim 3 or 4, wherein the corresponding count is provided for a corresponding type of control plane transaction, and for each transaction of the same type, the corresponding count is updated with the same value.

6. The apparatus according to any one of the preceding claims, comprising a component for determining whether the collected energy-related information associated with the one or more control plane transactions has reached a corresponding reporting threshold, and wherein, when the reporting threshold has been reached, the component for reporting is configured to report the energy-related information associated with the one or more control plane transactions.

7. The apparatus of claim 6, wherein when claim 6 is subordinate to claim 3, 4 or 5, the reporting threshold includes a counting threshold associated with the count or the corresponding count.

8. The apparatus according to any one of the preceding claims, wherein the reporting component is configured to periodically report the energy-related information associated with the one or more control plane transactions.

9. The apparatus according to any one of the preceding claims, wherein the control plane transaction in the one or more control plane transactions is associated with at least one of the following: User equipment; network slice; or data network name.

10. The apparatus of claim 9, wherein the energy-related information associated with the one or more control plane transactions includes information identifying at least one of: the user equipment, the given network slice, or the given data network name associated with the corresponding control plane transaction.

11. An apparatus comprising: A component used to receive energy-related information associated with one or more control plane transactions; as well as Components for providing billing information using the received energy-related information associated with the one or more control plane transactions.

12. The apparatus of claim 11, wherein the billing information includes billing data records.

13. An apparatus comprising: A component used to receive energy-related information associated with one or more control plane transactions; as well as A component for analyzing the received energy-related information associated with the one or more control plane transactions to provide energy-related information analysis.

14. The apparatus of claim 11, 12 or 13, wherein the information related to the energy-related information associated with the one or more control plane transactions includes information about the type of one or more control plane transactions.

15. The apparatus according to any one of claims 11 to 14, wherein one or more control plane transactions are associated with at least one of: User equipment; network slice; and data network name.

16. The apparatus of claim 15, wherein the energy-related information associated with the one or more control plane transactions includes information identifying at least one of: the user equipment, the given network slice, or the given data network name associated with the corresponding control plane transaction.

17. A method comprising: Collect energy-related information associated with one or more control plane transactions of the application programming interface of network entities; as well as Report the energy-related information associated with the one or more control plane transactions.

18. The method of claim 17, wherein the energy-related information associated with the one or more control plane transactions includes information about the type of one or more control plane transactions among the control plane transactions.

19. The method of claim 17 or 18, further comprising updating the count when a corresponding control plane transaction occurs.

20. The method of claim 19, further comprising updating the count for the one or more control plane transactions based on the type of the control plane transaction, wherein at least two different types of the control plane transaction cause the count to be updated with different values.

21. The method of claim 19 or 20, wherein the corresponding count is provided for a corresponding type of control plane transaction, and for each transaction of the same type, the corresponding count is updated with the same value.

22. The method of any one of claims 17 to 21, comprising determining whether the collected energy-related information associated with the one or more control plane transactions has reached a corresponding reporting threshold, and when the reporting threshold has been reached, reporting the energy-related information associated with the one or more control plane transactions.

23. A method comprising: Receive energy-related information associated with one or more control plane transactions; as well as The received energy-related information, associated with the one or more control plane transactions, is used to provide billing information.

24. A method comprising: Receive energy-related information associated with one or more control plane transactions; as well as Analyze the received energy-related information associated with the one or more control plane transactions to provide energy-related information analysis.

25. A computer program comprising executable instructions that, when the executable instructions are executed, perform the method of any one of claims 17 to 24.

Images