WO2011098661A1

WO2011098661A1 - Method and apparatus for providing utilization of data profiling for radio resource management

Info

Publication number: WO2011098661A1
Application number: PCT/FI2010/051098
Authority: WO
Inventors: Brian Martin
Original assignee: Nokia Corporation
Priority date: 2010-02-15
Filing date: 2010-12-30
Publication date: 2011-08-18

Abstract

A method and apparatus are provided that may enable the provision of radio resource management by using data profiling.In this regard, for example, communication nodes such as mobile terminals or other machines such as sensors or the like that may not necessarily be mobile may be enabled to provide a data profile to the network. The data profile may be usable by the network allocate resources accordingly.

Description

METHOD AND APPARATUS FOR PROVIDING UTILIZATION

OF DATA PROFILING FOR RADIO RESOURCE MANAGEMENT

TECHNOLOGICAL FIELD

Embodiments of the present invention relate generally to radio resource management technology and, more particularly, relate to an apparatus and method for providing utilization of data profiling for radio resource management.

BACKGROUND

The modern communications era has brought about a tremendous expansion of wireline and wireless networks. Computer networks, television networks, and telephony networks are experiencing an unprecedented technological expansion, fueled by consumer demand. Wireless and mobile networking technologies have addressed related consumer demands, while providing more flexibility and immediacy of information transfer.

As wireless networks continue to evolve and the number and capabilities of devices that utilize wireless network resources continue to increase, a strain may sometimes be placed on the resources of the network and the resources of the devices. Accordingly, it may be desirable to develop mechanisms by which resource management may be accomplished for both the network and the devices operating within the network.

BRIEF SUMMARY OF EXAMPLE EMBODIMENTS

A method and apparatus are therefore provided that may enable the provision of radio resource management by using data profiling. In this regard, for example, communication nodes such as mobile terminals or other machines such as sensors or the like that may not necessarily be mobile may be enabled to provide a data profile to the network. The data profile may be usable by the network allocate resources accordingly.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein: FIG. 1 illustrates one example of a communication system according to an example embodiment of the present invention;

FIG. 2 illustrates a block diagram showing an apparatus for providing a data profile for radio resource management in accordance with an example embodiment of the present invention;

FIG. 3 illustrates a block diagram showing another apparatus for providing a data profile for radio resource management in accordance with an example embodiment of the present invention;

FIG. 4 illustrates a flowchart of a method for providing a data profile for radio resource management according to an example embodiment of the present invention; and

FIG. 5 illustrates another flowchart of a method for providing a data profile for radio resource management in accordance with an example embodiment of the present invention.

DETAILED DESCRIPTION

Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms "data," "content," "information" and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

Additionally, as used herein, the term 'circuitry' refers to (a) hardware- only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. 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 includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.

As defined herein a "computer-readable storage medium," which refers to a physical storage medium (e.g., volatile or non-volatile memory device), can be differentiated from a "computer-readable transmission medium," which refers to an electromagnetic signal.

As indicated above, it may be beneficial to enable networks to conduct resource allocations based on data profiles provided from communication nodes of the corresponding networks. Some resource allocation strategies involve having

communication terminals such as mobile terminals report quality of service (QoS) requirements to enable networks to manipulate network configurations and resource allocations by way of altering maximum data rates and transfer methods to improve reliability. Some networks also employ fast dormancy to utilize indications from mobile terminals regarding their immediate needs to transfer data or signaling to facilitate the networks ability to put the mobile terminals n a more battery-efficient state when possible. Networks may also employ timer based or inactivity based conditional triggers to alter mobile terminal communication states to improve resource management based on current conditions. However, each of the resource management strategies described above typically involves dynamic responses to current conditions. Given the potential for mobility of some devices and the unpredictability of device communications when human involvement with initiating such communications, having a data profile that offers a static or predictable assessment of device resource requirements has not been easy to provide.

Some embodiments of the present invention may enable a data profile to be provided by communication nodes (mobile or fixed) that enables a static or relatively predictable assessment of device resource requirements. In this regard, for example, data profile information that is descriptive of the frequency at which (e.g., how often) corresponding QoS requirements are applicable or definite times during which corresponding QoS requirements are applicable may enable the network to plan and utilize its resource allocations in an efficient manner to improve network capacity, coverage, power consumption of network devices, and/or the like. As such, by including within a data profile a temporal aspect or temporal characteristics descriptive of resource requirements for the corresponding device, network performance may be enhanced.

Although embodiments of the present invention may be practiced in connection with mobile terminals (e.g., cellular phones and other wireless communication devices typically carried by people or other mobile entities), embodiments may also be practiced in connection with other machines or devices that may not be mobile or have limited mobility. Machine type communication (MTC) is a form of data communication that involves one or more entities that do not necessarily need human interaction. The entities involved in MTC may communicate with each other (e.g., machine-to-machine or M2M communication) or with network devices such as servers or other service platforms. In some examples, the entities (or machines) may include one or more sensors or other nodes or devices that gather information that can be passed to a network or computing device directly or via some form of gateway device. In some cases, the network may be the Internet or some more localized computing network. It may be assumed that many of the machines or entities are stationary or at least limited in movement to locations within a relatively limited geographic area. Many of the machines or entities may also have somewhat predictable communication patterns involving relatively limited amounts of data.

Accordingly, due to the relatively fewer complications associated with communication volume and frequency and the relatively predictable nature of the volume and frequency of communications involving some machines or entities, machines or entities associated with MTC may be good candidates for use in connection with embodiments that utilize data profiles with temporal characteristic associated therewith. However, embodiments of the present invention should not be limited only to MTC communications and can also be practiced in connection with mobile terminal applications and communications in general.

FIG. 1 illustrates a generic system diagram in which devices such as a mobile terminal 10 and one or more other machines (e.g., sensor 20), which are examples of communication nodes, are shown in an example communication environment in which embodiments of the present invention may be employed. As shown in FIG. 1, an embodiment of a system in accordance with an example embodiment of the present invention may include a first communication device (e.g., mobile terminal 10) and/or other communication devices (e.g., one or more machines such as sensor 20) capable of communication with a network 30 and perhaps also each other. In an example

embodiment, the mobile terminal 10 and the sensor 20 may be in (or be capable of being placed in) communication with each other and with the network 30 via an access point such as a base station, node B (NB), evolved node B (eNB) or other access mechanism or device. In some cases, embodiments of the present invention may further include one or more network devices with which the mobile terminal 10 and/or the sensor 20 may communicate to provide, request and/or receive information such as a service platform 40, which may be a part of or in communication with the network 30.

The network 30 may include a collection of various different nodes, devices or functions that may be in communication with each other via corresponding wired and/or wireless interfaces. As such, the illustration of FIG. 1 should be understood to be an example of a broad view of certain elements of the system and not an all inclusive or detailed view of the system or the network 30. One or more communication nodes such as the mobile terminal 10 and the sensor 20 may be in communication with each other via the network 30 or via device to device (D2D) communication and each may include an antenna or antennas for transmitting signals to and for receiving signals from a base site (e.g., an access point), which could be, for example a base station that is a part of one or more cellular or mobile networks or an access point that may be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN), such as the Internet. In turn, other devices such as processing elements (e.g., personal computers, server computers or the like) may be coupled to the mobile terminal 10 and/or the sensor 20 via the network 30 and the access point. In some embodiments, the network 30 may employ one or more mobile access mechanisms such as wideband code division multiple access (W-CDMA), CDMA2000, global system for mobile communications (GSM), general packet radio service (GPRS), long term evolution (LTE) and/or the like may be supported.

In some example embodiments, the mobile terminal 10 may be a mobile communication device such as, for example, a personal digital assistant (PDA), wireless telephone, mobile computing device, camera, video recorder, audio/video player, positioning device (e.g., a global positioning system (GPS) device), game device, television device, radio device, or various other like devices or combinations thereof. As such, the mobile terminal 10 may include a processor and memory for storing instructions, which when executed by the processor, cause the mobile terminal 10 to operate in a particular way or execute specific functionality. The mobile terminal 10 may also include communication circuitry and corresponding hardware/software to enable communication with other devices.

The sensor 20 may be a mobile device such as a small battery operated device configured to detect local parameters or environmental conditions for reporting to a remote location. However, in other embodiments the sensor 20 may merely be an example of one or more communication nodes (fixed or mobile) capable of performing MTC communication (e.g., communication without human interaction). As such, each sensor may include some form of detection device or circuitry to measure a physical parameter or other measurable value along with some communication circuitry for enabling the sensor to communicate information to the network 30. Sensors may also include memory and processing circuitry in some instances, and the processing circuitry may direct operation of the corresponding sensors, at least with respect to communication of information to the network 30. In some cases, the sensor 20 may be replaced by some other type of machine that may be a mobile or fixed communication device.

As shown in FIG. 1, one or more of the communication nodes (e.g., sensor 20 and mobile terminal 10) may be positioned within the coverage area of one or more respective access points that may access the network 30 directly or via another network with which the network 30 is capable of communication. The service platform 40 may then communicate with the communication nodes to provide a service thereto. In an example embodiment, the service platform 40 may be a device or node such as a server or other processing circuitry. The service platform 40 may have any number of functions or associations with various services. As such, for example, the service platform 40 may be a platform such as a dedicated server, backend server, or server bank associated with a particular information source, function or service. As such, the service platform 40 may represent one or more of a plurality of different services or information sources. The functionality of the service platform 40 may be provided by hardware and/or software components configured to operate in accordance with known techniques for the provision of information to users of communication devices, except as modified as described herein.

In an exemplary embodiment, the service platform 40 may be embodied as or host a MTC server. As such, the service platform 40 may be an entity that

communicates with a network (e.g., a public land mobile network (PLMN) such as network 30) and sometimes also other MTC devices (e.g., the mobile terminal 10 and/or the sensor) via the network 30. The service platform 40, acting as the MTC server, may include an interface that can be accessed by a user that is using services provided by service platform 40. As such, for example, the service platform 40 may provide, among other things, data storage and processing, and other services related to communication with the communication nodes. In some cases, the service platform 40 may have multiple functionalities and provide multiple services. Thus, for example, the service platform 40 may also provide services related to managing resource allocations for the network 30 and/or managing or participating in management of a communication state of the communication nodes in order to reduce battery consumption or other resource

consumption of the respective communication nodes.

In an example embodiment, the communication nodes (e.g., the mobile terminal 10 and/or the sensor 20) may be configured to include or otherwise employ an apparatus according to an example embodiment of the present invention. FIG. 2 illustrates a schematic block diagram of an apparatus 50 for providing data profiling information for use in radio resource management according to an example embodiment of the present invention. In some embodiments, the service platform 40, or another network entity, may include an apparatus according to an example embodiment. FIG. 3 illustrates a schematic block diagram of an apparatus 55 for utilizing data profiling information for radio resource management according to an example embodiment of the present invention.

An example embodiment of the invention will now be described with reference to FIG. 2, in which certain elements of the apparatus 50 for providing data profiling information for use in radio resource management are displayed. The apparatus 50 of FIG. 2 may be employed, for example, on a communication node or a variety of other devices. However, it should be noted that the components, devices or elements described below may not be mandatory and thus some may be omitted in certain embodiments. Additionally, some embodiments may include further components, devices or elements beyond those shown and described herein.

Referring now to FIG. 2, the apparatus 50 may include or otherwise be in communication with a processor 70, a communication interface 74 and a memory device 76. The memory device 76 may include, for example, one or more volatile and/or nonvolatile memories. In other words, for example, the memory device 76 may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device). The memory device 76 may be configured to store information, data, applications, instructions or the like for enabling the apparatus to carry out various functions in accordance with example embodiments of the present invention. For example, the memory device 76 could be configured to buffer input data for processing by the processor 70. Additionally or alternatively, the memory device 76 could be configured to store instructions for execution by the processor 70.

The processor 70 may be embodied in a number of different ways. For example, the processor 70 may be embodied as one or more of various processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In an example embodiment, the processor 70 may be configured to execute instructions stored in the memory device 76 or otherwise accessible to the processor 70. Alternatively or additionally, the processor 70 may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 70 may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 70 is embodied as an ASIC, FPGA or the like, the processor 70 may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor 70 is embodied as an executor of software instructions, the instructions may specifically configure the processor 70 to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor 70 may be a processor of a specific device (e.g., a communication node) adapted for employing embodiments of the present invention by further configuration of the processor 70 by instructions for performing the algorithms and/or operations described herein. The processor 70 may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor 70.

Meanwhile, the communication interface 74 may be any means such as a device or circuitry embodied in either hardware, software, or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the apparatus. In this regard, the communication interface 74 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. In some environments, the communication interface 74 may alternatively or also support wired communication. As such, for example, the

communication interface 74 may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.

The user interface 72 may be in communication with the processor 70 to receive an indication of a user input at the user interface 72 and/or to provide an audible, visual, mechanical or other output to the user. As such, the user interface 72 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen, soft keys, a microphone, a speaker, or other input/output mechanisms. In some examples, the processor 70 may comprise user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as, for example, a speaker, ringer, microphone, display, and/or the like. The processor 70 and/or user interface circuitry comprising the processor 70 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (e.g., software and/or firmware) stored on a memory accessible to the processor 70 (e.g., memory device 76, and/or the like).

In an example embodiment, the processor 70 may be embodied as, include or otherwise control a data profiler 80. The data profiler 80 may be any means such as a device or circuitry operating in accordance with software or otherwise embodied in hardware or a combination of hardware and software (e.g., processor 70 operating under software control, the processor 70 embodied as an ASIC or FPGA specifically configured to perform the operations described herein, or a combination thereof) thereby configuring the device or circuitry to perform the corresponding functions of the data profiler 80 as described herein. Thus, in examples in which software is employed, a device or circuitry (e.g., the processor 70 in one example) executing the software forms the structure associated with such means.

In an example embodiment, the data profiler 80 is configured to determine information descriptive of network usage characteristics of the apparatus 50 (or a device employing the apparatus 50) or of one or more applications of the apparatus 50. The information determined may form a data profile to be sent by direction of the processor 70 via the communication interface 74 to the service platform 40 for use by network control functions to manage network resource consumption. As such, for example, if a device such as the apparatus 50 (or a device employing the apparatus 50) is a relatively simple machine that performs a specific function, the data profiler 80 may be configured to determine a radio resource usage pattern of the device based on the type of device, known communication patterns for similar devices, analysis of past device performance, and/or the like. Similarly, if the device employs one or more applications, the data profiler 80 may be configured to determine a radio resource usage pattern for each respective application based on the type of application, known communication patterns for similar applications, analysis of past application performance, and/or the like. For devices that primarily engage in MTC, determining resource usage pattern information may be relatively simple based on historic knowledge of device behavior. Similarly, for certain applications that have predictable usage patterns that may be employed by a mobile terminal or user equipment, determining resource usage patterns may also be relatively simple based on knowledge of application behavior. However, for unpredictable applications, determining usage patterns may either be complex, or may not be attempted at all.

In an example embodiment, the data profile determined by the data profiler 80 may include information descriptive of expected data rates, expected data quantities, expected frequency of data transmissions (e.g. how often data transmissions occur), data criticality (e.g., time limits for complete receipt of data, requirements for error free data, etc.), preferred transfer method (e.g., packet switched data, short message service (SMS) data, etc.) or any other information that may be useful in relation to managing network resource consumption and/or device battery consumption. In some embodiments, the data profile also includes a validity time indicating a time period during which the data profile is to be considered valid. As such, the validity time of the data profile may include an expiration time for the data profile or may define specific non-contiguous periods of time during which the data profile is considered valid. As yet another possibility, the validity time may indicate how often usage patterns change for the corresponding device or application associated with the data profile. Accordingly, the data profile may include information descriptive of resource consumption behavior and/or requirements of an application or device. However, the data profile may include information beyond just quantitative and/or qualitative characteristics. In this regard, for example, the data profile may include information indicative of temporal characteristics of resource usage so that planning may be conducted prospectively to manage network radio resources and/or device battery consumption to account for load conditions or other priorities of the network. The temporal characteristics may be descriptive of temporal limitations (e.g., expiry time or discrete intervals or patterns) or continuous limitations (e.g., fixed for a particular application for as long as the corresponding application is active or registered).

In an example embodiment, after the data profile is determined, the apparatus 50 may transmit the data profile (e.g., under control of the processor 70 and via the communication interface 74) to a network entity (e.g., the service platform 40). In some cases, a single data profile may be sent for each application that is active on a particular device. However, in other situations, only one data profile (perhaps including information descriptive of multiple applications, or including a composite profile generated responsive to input regarding multiple applications) may be provided for each device. The network entity may then use the information from one or a plurality of data profiles received in order to manage network radio resources.

In some embodiments, data profiles may originate from each respective application of a device and be signaled via a standard interface to a protocol stack of the device (e.g., the mobile terminal 10) to enable third party applications a standard interface when designing and writing applications. Thereafter, the data profile may be signaled over a radio interface via either access stratum (AS) or non-access stratum (NAS) signaling based on desirable implementation options that are employed. Furthermore, in some cases, the data profile may be provided by application dependent methods (e.g., via transport control protocol/internet protocol (TCP/IP)). If changes to a data profile are required or desirable due to changes in the situation of the apparatus 50, the data profiler 80 may be configured to confirm conditions relative to the data profile and update the data profile accordingly. As such, the data profiler 80 may be configured to periodically, randomly or in response to specific events, update the data profile or evaluate whether to update the data profile. In some instances, the data profile may be provided at initial registration when a subscriber registers for a service or when an MTC device registers with an MTC server. Meanwhile, for devices that perform a particular specific function, the data profile may be relatively fixed. Thus, an application/radio protocol interface may not be necessary in such cases.

In an example embodiment, the data profile may be a listing of

information defining one or more corresponding parameters or may be one of a plurality of predefined profiles that can be uniquely identified. However, in other examples, the data profile may include options for various parameters listed in a preferred or prioritized order.

Moreover, in some cases, multiple acceptable data profiles may be sent that are suitable or acceptable from the perspective of the communication node. The multiple acceptable data profiles may be provided in association with information indicating preference to enable the network entity to select an acceptable profile to consider for resource management purposes that is best suited to the network entities efforts to manage resource consumption. The network entity may then signal back to the communication node the data profile to implement to thereby configure or restrict the communication node in a manner that is most preferred for the communication node under the circumstances.

By providing the data profile to the service platform 40, a network entity that can manage radio resource consumption (e.g., a radio network controller (R C)) and the communication node (which may provide input for radio resource control (RRC) may both have knowledge of expected radio resource usage of a specific application or specific device or type of device. Thus, radio resource consumption may be managed based on one or a plurality of data profiles.

In some embodiments, as will be described in greater detail below, the data profiler 80 may actually receive a data profile from a network entity (e.g., the service platform 40). In such example embodiments, for example, the service platform 40 may take action to dictate the data profile that is to be implemented at the apparatus 50 in order to conduct load balancing or other resource consumption management functions. In response to receipt of a data profile from the service platform 40, the data profiler 80 may be configured to interface with the apparatus 50 to provide direction for operational parameters or limits that are to be employed to conform to the data profile received.

At the service platform 40, another apparatus 55 may be provided for receiving and processing data profiles. FIG. 3 illustrates a block diagram of the apparatus 55 according to an example embodiment. The apparatus 55 may include or otherwise be in communication with a processor 70', a communication interface 74' and a memory device 76'. Although some embodiments may not include any user interface and no such user interface is shown in FIG. 3, the apparatus 55 could also include a user interface.

Functional capabilities and basic structure of the processor 70', the communication interface 74' and the memory device 76' may be similar to the corresponding capabilities and basic structure described above in relation to the processor 70, the communication interface 74 and the memory device 76 described above in connection with the description of FIG. 2. Accordingly, specific details of the structure of the processor 70', the communication interface 74' and the memory device 76' will not be repeated. However, it should be noted that exact details such as memory size and construction or processor speed and/or the like may be different (and perhaps larger/faster) for the apparatus 55 of FIG. 3 than for the corresponding devices of the apparatus 50 of FIG. 2.

In an example embodiment, the processor 70' may be embodied as, include or otherwise control a data profile manager 90. The data profile manager 90 may be any means such as a device or circuitry operating in accordance with software or otherwise embodied in hardware or a combination of hardware and software (e.g., processor 70' operating under software control, the processor 70' embodied as an ASIC or FPGA specifically configured to perform the operations described herein, or a combination thereof) thereby configuring the device or circuitry to perform the corresponding functions of the data profile manager 90 as described herein. Thus, in examples in which software is employed, a device or circuitry (e.g., the processor 70' in one example) executing the software forms the structure associated with such means.

The data profile manager 90 may be configured to receive a data profile from one or more communication nodes and manage network radio resource consumption based on the data profile(s) received. The data profile manager 90 may thereafter be configured to manage resource allocations or consumption of the apparatus 55 to provide services that conform to data profile requirements to the extent practicable. Furthermore, in some embodiments, the data profile manager 90 is further configured to indicate an allowed profile to a communication node (e.g., the mobile terminal 10 or sensor 20). As such, the data profile manager 90 may be configured to enable the potential for network initiated modification, alteration, restriction, or directed switching of a data profile at any time. In some instances, the data profile manager 90 may dictate data profiles to devices or applications based on efforts to limit loading at high traffic periods or to optimize resource allocations without having received any data profile from a corresponding device or application. However, in other examples, the data profile manager 90 may utilize its capability for sending an allowed data profile to alter existing operations based on received data profiles in response to conditions indicating that certain performance criteria are not being met or are in danger of not being met. As such, the data profile manager 90 may act in a proactive or responsive fashion in alternative embodiments and operations relative to receipt of data profiles from external devices may be conducted independent of or in combination with operations relative to allowed data profiles being sent from the data profile manager 90. Sending of allowed data profiles to devices may be particularly useful in connection with devices that have multiple known profiles with corresponding characteristics that may provide the data profile manager 90 with a constructive listing of available profile options that can be selected from according to current conditions.

Control of the provision of allowed profiles may be accomplished using simple or complex signaling. In some instances, default profiles having standard parameters or parameters corresponding to predefined profiles may be selected from options that are available to the data profile manager 90 in order to reduce an amount of signaling that may be needed between the network entity and the communication node. Accordingly, the data profile manager 90 may dictate device or application parameters to manage network loading or resource consumption and also to dictate operations (e.g., device state) of the communication node to promote power savings at the communication node as well. Thus, for example, the data profile manager 90 may act to wake up a mobile terminal or other machine only at predefined times according to the data profile currently being employed.

Accordingly, some embodiments of the present invention may provide a network entity (e.g., the service platform 40, which may act as an MTC server in some cases) with the ability to receive or dictate data profile information to manage network resource consumption. Accordingly, network capacity, coverage, power consumption (e.g., of communication nodes), and/or other resources may be managed in an efficient manner. For example, if a particular application sends or receives data for a duration of one minute in every ten minute interval, a data profile indicative of this behavior may be communicated to the network entity to allow the network to plan ahead and assign the same resources that will serve the particular application to nine other similar applications at staggered intervals over a ten minute period in order to efficiently distribute usage of the resources over time. Thus, instead of dynamically adjusting resource allocations in real time responsive to current conditions relative to QoS requests, proactive measures may be taken to provide more efficient resource allocation. Additionally, if the network entity can anticipate application or device resource needs in the future, the network entity may be enabled to place communication nodes in advantageous states (e.g., sleep/awake states) to conserve battery resources or power consumption. As such, the data profile of some exemplary embodiments may provide not only qualitative and/or quantitative

characteristics for expected resource usage by a communication node, but also an indication of temporal characteristics regarding such usage so that definite times during which the communication node and/or the network entity are to perform RRC state changes. FIGS. 4 and 5 are each flowcharts of a method and program product according to example embodiments of the invention. It will be understood that each block or step of the flowcharts, and combinations of blocks in the flowcharts, may be

implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device of the communication node or network entity and executed by a processor in the communication node or network entity. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the instructions which execute on the computer or other programmable apparatus create means for implementing the functions specified in the flowcharts block(s). These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowcharts block(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus implement the functions specified in the flowcharts block(s).

Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions, combinations of operations for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

In this regard, a method according to one embodiment of the invention from the perspective of a communication node, as shown in FIG. 4, may include determining, at a communication node, a data profile of the communication node at operation 100. The data profile may define at least a temporal characteristic of radio resource consumption of the communication node. The method may further include providing the data profile to a network entity at alternative operation 110 or operating in accordance with a provided data profile at alternative operation 120. In some cases, the method may further include an optional operation of determining whether to update the data profile (e.g., periodically, randomly, or in response to particular event) at operation 130.

In some embodiments, certain ones of the operations above may be modified or further amplified as described below. It should be appreciated that, except where specifically noted, each of the modifications or amplifications below may be included with the operations above either alone or in combination with any others among the features described herein. In this regard, for example, determining the data profile may include determining the data profile responsive to receipt of information indicative of an allowed profile received from a network entity. In an example embodiment, determining the data profile may include determining the data profile at the device implementing the method. In some embodiments, providing the data profile to the network entity may include indicating which of a plurality of profiles the communication node supports. The temporal characteristics may include temporary or continuous temporal aspects.

Moreover, the data profile may further include qualitative and/or quantitative

characteristics in addition to the temporal characteristics.

In an example embodiment, an apparatus for performing the method of

FIG. 4 above may comprise a processor (e.g., the processor 70) configured to perform some or each of the operations (100-130) described above. The processor may, for example, be configured to perform the operations (100-130) by performing hardware implemented logical functions, executing stored instructions, or executing algorithms for performing each of the operations. Alternatively, the apparatus may comprise means for performing each of the operations described above. In this regard, according to an example embodiment, examples of means for performing operations 100-130 may comprise, for example, the processor 70, the data profiler 80, and/or a device or circuit for executing instructions or executing an algorithm for processing information as described above.

An example of an apparatus according to an example embodiment may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to perform the operations 100-130 (with or without the modifications and amplifications described above in any combination).

An example of a computer program product according to an example embodiment may include at least one computer-readable storage medium having computer-executable program code portions stored therein. The computer-executable program code portions may include program code instructions for performing operation 100-130 (with or without the modifications and amplifications described above in any combination).

In an alternative embodiment from the perspective of a network entity (e.g., the service platform 40 or a MTC server associated with the service platform 40), a method for providing radio resource management according to one embodiment of the present invention, as shown in FIG. 5, may include determining, at a network entity, a data profile of a communication node at operation 210. The data profile may define at least a temporal characteristic of radio resource consumption of the communication node. The method may further include providing the data profile to the communication node at optional alternative operation 220. However, in some embodiments, determining the data profile may be performed responsive to receiving the data profile from the communication node at alternative operation 200. The method may further include allocating network resources based on the data profile at operation 230. In some cases, the method may further include an optional operation of receiving update to the data profile (e.g., periodically, randomly, or in response to particular event) at operation 240.

In some embodiments, certain ones of the operations above may be modified or further amplified as described below. It should be appreciated that, except where specifically noted, each of the modifications or amplifications below may be included with the operations above either alone or in combination with any others among the features described herein. Furthermore, it should be appreciated that where alternative paths between blocks of FIG. 5 are provided, alternative embodiments are envisioned for each alternative combination of paths that can be traced. In this regard, for example, determining the data profile may include determining an allowed data profile based on network load conditions. In some embodiments, providing the data profile to the communication node may include indicating which of a plurality of default or standard profiles the communication node is to implement. The temporal characteristics may include temporary or continuous temporal aspects. Moreover, the data profile may further include qualitative and/or quantitative characteristics in addition to the temporal characteristics.

In an example embodiment, an apparatus for performing the method of FIG. 5 above may comprise a processor (e.g., the processor 70') configured to perform some or each of the operations (200-240) described above. The processor may, for example, be configured to perform the operations (200-240) by performing hardware implemented logical functions, executing stored instructions, or executing algorithms for performing each of the operations. Alternatively, the apparatus may comprise means for performing each of the operations described above. In this regard, according to an example embodiment, examples of means for performing operations 200-240 may comprise, for example, the processor 70', the data profile manager 90, and/or a device or circuit for executing instructions or executing an algorithm for processing information as described above.

An example of an apparatus according to an example embodiment may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to perform the operations 200-240 (with or without the modifications and amplifications described above in any combination).

An example of a computer program product according to an example embodiment may include at least one computer-readable storage medium having computer-executable program code portions stored therein. The computer-executable program code portions may include program code instructions for performing operation 200-240 (with or without the modifications and amplifications described above in any combination).

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

WHAT IS CLAIMED IS:

1. A method comprising:

determining, at a communication node, a data profile of the communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and

causing provision of the data profile to a network entity or causing operation in accordance with the data profile.

2. The method of claim 1, further comprising determining whether to update the data profile.

3. The method of claim 2, wherein determining whether to update the data profile comprises determining whether to update the data profile periodically, randomly, or in response to a particular event.

4. The method of any of claims 1 to 3, wherein determining the data profile comprises determining the data profile responsive to receipt of information indicative of an allowed profile received from the network entity.

5. The method of any of claims 1 to 4, wherein causing provision of the data profile to the network entity comprises indicating which of a plurality of profiles the communication node supports.

6. The method of any of claims 1 to 5, wherein the temporal characteristic comprises a temporary or continuous temporal aspect and wherein the data profile comprises qualitative or quantitative characteristics in addition to the temporal

characteristic.

7. An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: determine, at a communication node, a data profile of the communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and

cause provision of the data profile to a network entity or cause operation in accordance with the data profile.

8. The apparatus of claim 7, wherein the at least one memory and computer program code are further configured to, with the at least one processor, cause the apparatus to determine whether to update the data profile.

9. The apparatus of claim 8, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to determine whether to update the data profile by determining whether to update the data profile periodically, randomly, or in response to a particular event.

10. The apparatus of any of claims 7 to 9, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to determine the data profile by determining the data profile responsive to receipt of information indicative of an allowed profile received from the network entity.

11. The apparatus of any of claims 7 to 10, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to cause provision of the data profile to the network entity by indicating which of a plurality of profiles the communication node supports.

12. The apparatus of any of claims 7 to 11, wherein the temporal characteristic comprises a temporary or continuous temporal aspect and wherein the data profile comprises qualitative or quantitative characteristics in addition to the temporal

characteristic.

13. An apparatus comprising :

means for determining, at a communication node, a data profile of the

communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and means for causing provision of the data profile to a network entity or means for causing operation in accordance with the data profile.

14. The apparatus of claim 13, further comprising means for determining whether to update the data profile.

15. The apparatus of claim 14, wherein means for determining whether to update the data profile comprises means for determining whether to update the data profile periodically, randomly, or in response to a particular event.

16. The apparatus of any of claims 13 to 15, wherein means for determining the data profile comprises means for determining the data profile responsive to receipt of information indicative of an allowed profile received from the network entity.

17. The apparatus of any of claims 13 to 16, wherein means for causing provision of the data profile to the network entity comprises means for indicating which of a plurality of profiles the communication node supports.

18. The apparatus of any of claims 13 to 17, wherein the temporal characteristic comprises a temporary or continuous temporal aspect and wherein the data profile comprises qualitative or quantitative characteristics in addition to the temporal

characteristic.

19. A computer program product comprising at least one computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions including program code instructions that when executed at least cause an apparatus to:

determine, at a communication node, a data profile of the communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and

20. The computer program product of claim 19, further comprising program code instructions for determining whether to update the data profile.

21. The computer program product of claim 20, wherein program code instructions for determining whether to update the data profile include instructions for determining whether to update the data profile periodically, randomly, or in response to a particular event.

22. The computer program product of any of claims 19 to 21, wherein program code instructions for determining the data profile include instructions for determining the data profile responsive to receipt of information indicative of an allowed profile received from the network entity.

23. The computer program product of any of claims 19 to 22, wherein program code instructions for causing provision of the data profile to the network entity include instructions for indicating which of a plurality of profiles the communication node supports.

24. The computer program product of any of claims 19 to 23, wherein the temporal characteristic comprises a temporary or continuous temporal aspect and wherein the data profile comprises qualitative or quantitative characteristics in addition to the temporal characteristic.

25. A method comprising:

determining, at a network entity, a data profile of a communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and

allocating network resources based on the data profile.

The method of claim 25, further comprising providing the data profile to the communication node.

27. The method of claim 26, wherein providing the data profile to the communication node comprises indicating which of a plurality of default or standard profiles the communication node is to implement.

28. The method of any of claims 25 to 27, wherein determining the data profile is performed responsive to receiving the data profile from the communication node.

29. The method of any of claims 25 to 28, further comprising receiving an update to the data profile periodically, randomly, or in response to a particular event.

30. The method of any of claims 25 to 29, wherein determining the data profile comprises determining an allowed data profile based on network load conditions.

31. The method of any of claims 25 to 30, wherein the temporal characteristic includes temporary or continuous temporal aspects and wherein the data profile includes qualitative or quantitative characteristics in addition to the temporal characteristic.

32. An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:

determine, at a network entity, a data profile of a communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and

allocate network resources based on the data profile.

33. The apparatus of claim 32, wherein the at least one memory and computer program code are further configured to, with the at least one processor, cause the apparatus to provide the data profile to the communication node.

34. The apparatus of claim 33, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to provide the data profile to the communication node by indicating which of a plurality of default or standard profiles the communication node is to implement.

35. The apparatus of any of claims 32 to 34, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to determine the data profile responsive to receiving the data profile from the communication node.

36. The apparatus of any of claims 32 to 35, wherein the at least one memory and computer program code are further configured to, with the at least one processor, cause the apparatus to receive an update to the data profile periodically, randomly, or in response to a particular event.

37. The apparatus of any of claims 32 to 36, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus to determine the data profile by determining an allowed data profile based on network load conditions.

38. The apparatus of any of claims 32 to 37, wherein the temporal characteristic includes temporary or continuous temporal aspects and wherein the data profile includes qualitative or quantitative characteristics in addition to the temporal characteristic.

39. An apparatus comprising:

means for determining, at a network entity, a data profile of a communication node, the data profile defining at least a temporal characteristic of radio resource consumption of the communication node; and

means for allocating network resources based on the data profile.

40. The apparatus of claim 39, further comprising means for providing the data profile to the communication node.

41. The apparatus of claim 40, wherein means for providing the data profile to the communication node comprises means for indicating which of a plurality of default or standard profiles the communication node is to implement.

42. The apparatus of any of claims 39 to 41, wherein determining the data profile is performed responsive to receiving the data profile from the communication node.

43. The apparatus of any of claims 39 to 42, further comprising means for receiving an update to the data profile periodically, randomly, or in response to a particular event.

44. The apparatus of any of claims 39 to 43, wherein means for determining the data profile comprises means for determining an allowed data profile based on network load conditions.

45. The apparatus of any of claims 39 to 44, wherein the temporal characteristic includes temporary or continuous temporal aspects and wherein the data profile includes qualitative or quantitative characteristics in addition to the temporal characteristic.

46. A computer program product comprising at least one computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions including program code instructions that when executed at least cause an apparatus to:

allocate network resources based on the data profile.

47. The computer program product of claim 46, further comprising program code instructions for providing the data profile to the communication node.

48. The computer program product of claim 47, wherein program code instructions for providing the data profile to the communication node include instructions for indicating which of a plurality of default or standard profiles the communication node is to implement.

49. The computer program product of any of claims 46 to 48, wherein program code instructions for determining the data profile are executed responsive to receiving the data profile from the communication node.

50. The computer program product of any of claims 46 to 48, further comprising program code instructions for receiving an update to the data profile periodically, randomly, or in response to a particular event.

51. The computer program product of any of claims 46 to 48, wherein program code instructions for determining the data profile include instructions for determining an allowed data profile based on network load conditions.

52. The computer program product of any of claims 46 to 48, wherein the temporal characteristic includes temporary or continuous temporal aspects and wherein the data profile includes qualitative or quantitative characteristics in addition to the temporal characteristic.