Description:RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

FIELD OF INVENTION
[0002] The embodiments of the present disclosure generally relate to Low Power Wireless Area Network (LPWAN) solutions. More particularly, the present disclosure relates to a system and a method for identifying devices and assigning optimized Radio Resource Control (RRC) inactivity timers.

BACKGROUND
[0003] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0004] A Low Power Wireless Area Network (LPWAN) network is designed to cater Internet-of-things (IoT) devices with different needs using conventional solutions. Some devices are fixed while other devices are mobile. Some devices are provided with external power supply and some devices are battery operated. Certain use cases require the battery to last for up to 10 years without manual intervention. The Third Generation Partnership Project (3GPP) has provided conventional solutions through which fixed wireless devices, which can have battery life of up to ten years. To meet the battery life requirement, the LPWAN offers power saving modes and utilize the power saving mode effectively for conserving power in these fixed IoT devices. By defining appropriate wake-up intervals and adjusting sleep durations based on the application requirements, developers can minimize power consumption during idle periods, leading to significant battery savings. In addition, data transmission time and the inactivity period also need to be kept as low as possible for the device to have an optimal battery savings. In the current implementations, using optimized power saving timers, optimized transmission protocols and lower inactivity timers help to achieve the power saving requirements. External power supply devices mostly use connection-oriented data transmission protocols for better reliability. Such devices need to have higher inactivity timers to maintain a persistent connection until connection between the devices and the server is closed gracefully from both the ends. On the other hand, battery operated devices use connection-less data transmission protocols to reduce the unnecessary transmission overhead and need to have lowest possible inactivity timers to return to sleep at the earliest to conserve battery life. In a network with such diverse variety of fixed devices with different power saving requirements, the conventional solutions are unable to provide adequate solutions.
[0005] There is, therefore, a need in the art to provide a system and a method that can mitigate the problems associated with the conventional solutions and provide an efficient system that may handle wide range of requirements associated with the diverse variety of fixed devices.

OBJECTS OF THE INVENTION
[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are listed herein below.
[0007] It is an object of the present disclosure to provide a system and a method a method for identifying devices and assigning optimized Radio Resource Control (RRC) inactivity timers to the devices.
[0008] It is an object of the present disclosure to provide a system that receives a request from the devices for exchange of radio resources, where the request is based on an attach process transmitted by the devices to a core network.
[0009] It is an object of the present disclosure to provide a system that generates mapped radio bearers associated with the devices based on the request.
[0010] It is an object of the present disclosure to provide a system that identifies the devices based on the one or more mapped radio bearers a battery operated device or an external power supplied device based on a subscriber profile identification (SPID) value received from the core network and correspondingly assigns an Radio Resource Control (RRC) inactivity timer based on the SPID value.

SUMMARY
[0011] This section is provided to introduce certain objects and aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0012] In an aspect, the present disclosure relates to a system for assigning optimized inactivity timers. The system includes a processor communicatively coupled to a Radio Access Network (RAN) node. The system includes a memory operatively coupled with the processor, wherein said memory stores instructions which, when executed by the processor, cause the processor to receive a request from one or more devices for exchange of one or more radio resources. The request is based on an attach process transmitted by the one or more devices to a core network. The processor generates one or more mapped radio bearers associated with the one or more devices based on the request. The processor identifies at least one device among the one or more devices based on the one or more mapped radio bearers a battery operated device or an external power supplied device through information preconfigured and received from the core network. The processor correspondingly assigns a Radio Resource Control (RRC) inactivity timer with a preconfigured value based on the identification of the device.
[0013] In an embodiment, the attach process may be include an Initial Context Setup (ICS) request received by the processor from the core network.
In an embodiment, the processor may be configured to receive a subscriber profile identification (SPID) as the information from the core network through the ICS request and configuring the RRC inactivity timer based on the SPID and configuring the RRC inactivity timer based on the SPID.
[0014] In an embodiment, the processor may be configured to establish the RRC connection based on the SPID received in the ICS request and apply the RRC inactivity timer to the battery operated device or the external power supplied device.
[0015] In an embodiment, upon detection of the device as the battery operated device, the processor may be configured to assign a minimum value as the preconfigured value with the RRC inactivity timer.
[0016] In an embodiment, upon detection of the device as the external power supplied device, the processor may be configured to assign a predetermined value as the preconfigured value with the RRC inactivity timer.
[0017] In an aspect, the present disclosure relates to a method for assigning optimized inactivity timers. The method includes receiving, by a processor, associated with a system, a request from one or more devices for exchange of one or more radio resources. The request is based on an attach process transmitted by the one or more devices to a core network. The method includes generating, by the processor, one or more mapped radio bearers associated with the one or more devices based on the request. The method includes identifying, by the processor, at least one device among the one or more devices based on the one or more mapped radio bearers as a battery operated device or an external power supplied device through information preconfigured and received from the core network. The method includes correspondingly assigning a RRC inactivity timer with a preconfigured value based on the identification of the device.
[0018] In an embodiment, the method may include receiving, by the processor, the attach process including an ICS request from the core network.
[0019] In an embodiment, the method may include receiving, by the processor, a SPID as the information from the core network through the ICS request and configuring the RRC inactivity timer based on the SPID.
[0020] In an embodiment, the method may include establishing, by the processor, the RRC connection based on the SPID received in the ICS request and applying the RRC inactivity timer to the battery operated device or the external power supplied device.
[0021] In an embodiment, the method may include assigning, by the processor, upon detection of the device as the battery operated device, a minimum value as the preconfigured value with the RRC inactivity timer.
[0022] In an embodiment, the method may include assigning, by the processor, upon detection of the external power supplied device, a predetermined value as the preconfigured value with the RRC inactivity timer.
[0023] In an aspect, the present disclosure relates to a user equipment (UE) for sending requests. The UE includes one or more processors communicatively coupled to a processor associated with a system. The one or more processors are coupled with a memory, and wherein said memory stores instructions which, when executed by the one or more processors, cause the one or more processors to transmit a request from for exchange of one or more radio resources. The processor is configured to receive the request from the UE. The request is based on an attach process transmitted by the UE to a core network. The processor is configured to generate one or more mapped radio bearers associated with the UE based on the request. The processor is configured to identify at least UE among one or more UEs based on the one or more mapped radio bearers as a battery operated device and an external power supplied device through information preconfigured and received from the core network. The processor correspondingly assigns a RRC inactivity timer with a preconfigured value based on the identification of the UE.

BRIEF DESCRIPTION OF DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.
[0025] FIG. 1 illustrates an example system architecture (100) of the proposed system (106), in accordance with an embodiment of the present disclosure.
[0026] FIG. 2 illustrates an example block diagram (200) of a proposed system (106), in accordance with an embodiment of the present disclosure.
[0027] FIG. 3 illustrates an example flow diagram (300) of a conventional system.
[0028] FIG. 4 illustrates an example flow diagram (400) of the proposed system (106), in accordance with an embodiment of the present disclosure.
[0029] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented. In an embodiment, the system (106) or the UE (102) may be implemented as the computer system (500).
[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.

DETAILED DESCRIPTION
[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0032] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0033] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.
[0034] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0035] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
[0036] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0037] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0038] The present disclosure describes a system and a method where a network can assign different Radio Resource Control (RRC) inactivity timers to battery operated devices and non-battery operated devices. This is achieved by configuring different subscriber profile identifications (SPIDs) provisioned to battery operated devices and non-battery operated devices in a Home Subscriber Service (HSS) of a core network. The HSS passes on this info to a Mobility Management Entity (MME) through during a attach process transmitted to the serving Radio Access Network (RAN) node through an Initial Context Setup (ICS) request. Based on the SPID value received in ICS request, the RAN node may configure different RRC inactivity timers to the battery operated devices and non-battery operated devices.
[0039] Various embodiments of the present disclosure will be explained in detail with reference to FIGs. 1-5.
[0040] FIG. 1 illustrates an example system architecture (100) of the proposed system (102), in accordance with an embodiment of the present disclosure.
[0041] As illustrated in FIG. 1, one or more user equipments (102-1, 102-2…102-N) may be connected to the proposed system (106) through a network (104). The system (106) may also be referred as a Radio Access Network (RAN) node (106) throughout the disclosure. A person of ordinary skill in the art will understand that the one or more user equipments (102-1, 102-2…102-N) may be collectively referred as the user equipments (102) and individually referred as the user equipment (102). The RAN node may be connected to a core network (108). The UEs (102) may also include a mix of fixed wireless Internet-of-things (IoT) devices with external power supply with no power saving mode support and fixed wireless IoT devices with an inbuilt battery that requests for power saving modes to conserve the battery life.
[0042] In an embodiment, the user equipment (102) may include, but not be limited to, a mobile, a laptop, etc. Further, the user equipment (102) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, audio aid, microphone, or keyboard. Further, the user equipment (102) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, and a mainframe computer. Additionally, input devices for receiving input from a user such as a touchpad, touch-enabled screen, electronic pen, and the like may be used.
[0043] In an embodiment, the network (104) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (104) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0044] In an embodiment, the system (106) may receive a request from one or more devices (102) for exchange of one or more radio resources, where the request may be based on an attach process transmitted by the one or more devices (102) to a core network (108). The attach process may be an Initial Context Setup (ICS) request received by the system (106) from the core network (108). Further, the system (106) may receive a subscriber profile identification (SPID) as the information preconfigured and received from the core network (108) through the ICS request and further configure the RRC inactivity timer based on the SPID. The SPID may be transmitted by a Home Subscriber entity (HSS) entity to a Mobile Management Entity (MME) entity within the core network and through the ICS towards the RAN (106).
[0045] In an embodiment, the core network (108) may be a core network entity (including a Mobility Management Entity (MME)) that receives the attach process from the IoT devices. The core network (108) may also include the HSS where the subscriber profile is created for all the Subscriber Identity Module/ International Mobile Subscriber Identity (SIM/IMSI) assigned and corresponding to the one or more devices (102). The subscriber profile may include the SPID which can be assigned when the SIM is provisioned. The MME on receiving the attach process, may create a session with a serving gateway and activate a default data bearer towards the devices (102) as part of the ICS request. The RAN node (106), on receiving the ICS request, creates the one or more mapped radio bearers towards the devices (102) and applies a common RRC inactivity timer with a pre-configured value associated with the one or more radio bearers for all the devices (102). Whenever the device (102) initiates data transactions, the RRC connection is established, and RAN node (106) waits for inactivity from the devices (106) to start the RRC inactivity timer. Once the last data packet is exchanged over the radio bearer, the RAN node (106) may initiate the RRC inactivity timer and when the RRC inactivity timer expires, the RAN node (106) may release the RRC connection. Further, the RRC inactivity timer may be applied to all the devices (102). The core network (108) may generate separate SPIDs to subscribers of battery operated devices and subscribers of non-battery operated devices.
[0046] In an embodiment, the system (106) may establish the RRC connection based on the SPID received in the ICS request and apply the RRC inactivity timer to the battery operated device or the external power supplied device.
[0047] In an embodiment, the system (106) may generate one or more mapped radio bearers associated with the one or more devices (102) based on the request.
[0048] In an embodiment, the system (106) may identify at least one device (102) among the one or more devices (102) based on the one or more mapped radio bearers as a battery operated device or an external power supplied device through information received from the core network (108). The system (106) may correspondingly assign a Radio Resource Control (RRC) inactivity timer with a preconfigured value based on the identification of the device (102).
[0049] In an embodiment, the system (106) may assign the SPID = a for subscribers of the battery operated devices and the SPID= b assigned to subscribers of non-battery operated devices. When the battery operated devices try to attach to the network, the HSS may transmit the assigned subscriber profile id= a in an “Update location Answer” message to the MME. The MME may further transmit the SPID to the system (106) through the ICS request.
[0050] In an embodiment, the system (106) may assign separate a SPID to SIM cards provisioned for battery operated devices and non-battery operated devices (external power supplied devices) in the core network, (108) specifically at the HSS.
[0051] In an embodiment, the system (106) upon detection of the device (102) as the battery operated device, may assign a minimum value as the preconfigured value with the RRC inactivity timer. When the battery operated device initiates a data transaction and when the final data packet is sent, the system (106) may start the RRC inactivity timer and upon expiry of the RRC inactivity timer, may release the RRC connection. Once the RRC connection is released, the battery operated device may go to a sleep mode for conserving the battery.
[0052] In an embodiment, the system (106) upon detection of the device (102) as the external power supplied device, may assign a predetermined value as the preconfigured value with the RRC inactivity timer. When a data transaction is initiated with the non-battery operated device and when the final data packet is sent, the system (106) may start the RRC inactivity timer and upon expiry of the RRC inactivity timer, may release the RRC connection. Once the RRC connection is released, the non-battery operated device may go to another mode.
[0053] FIG. 2 illustrates an example block diagram (200) of a proposed system (106), in accordance with an embodiment of the present disclosure.
[0054] Referring to FIG. 2, the system (106) may comprise one or more processor(s) (202) that may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (106). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.
[0055] In an embodiment, the system (106) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output (I/O) devices, storage devices, and the like. The interface(s) (206) may also provide a communication pathway for one or more components of the system (106). Examples of such components include, but are not limited to, processing engine(s) (208) and a database (210), where the processing engine(s) (208) may include, but not be limited to, a data ingestion engine (212), and other engine(s) (214). In an embodiment, the other engine(s) (214) may include, but not limited to, a data management engine, an input/output engine, and a notification engine.
[0056] In an embodiment, the processing engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (106) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (106) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.
[0057] In an embodiment, the processor (202) may receive a request from the one or more devices (102) via the data ingestion engine (212). The request may be from the one or more devices (102) for exchange of one or more radio resources. The processor (202) may store the request in the database (210). The request may be based on an attach process transmitted by the one or more devices (102) to a core network (108).
[0058] In an embodiment, the attach process may include an ICS request received by the processor (202) from the core network (108). Further, the processor (202) may receive a SPID as the information preconfigured and received from the core network (108)and configure the RRC inactivity timer based on the SPID..
[0059] In an embodiment, the processor (202) may establish the RRC connection based on the SPID received in the ICS request and apply the RRC inactivity timer to the battery operated device or the external power supplied device.
[0060] In an embodiment, the processor (202) may generate one or more mapped radio bearers associated with the one or more devices (102) based on the request.
[0061] In an embodiment, the processor (202) may identify at least one device (102) among the one or more devices (102) based on the one or more mapped radio bearers as a battery operated device or an external power supplied device through information received from the core network (108). The processor (202) may correspondingly assign a Radio Resource Control (RRC) inactivity timer with a preconfigured value based on the identification of the device (102).
[0062] In an embodiment, the processor (202) upon detection of the device (102) as the battery operated device, may assign a minimum value as the preconfigured value with the RRC inactivity timer. When the battery operated device initiates a data transaction and when the final data packet is sent, the processor (202) may start the RRC inactivity timer and upon expiry of the RRC inactivity timer, may release the RRC connection. Once the RRC connection is released, the battery operated device may go to a sleep mode for conserving the battery.
[0063] In an embodiment, the processor (202) may assign separate a SPID to SIM cards provisioned for battery operated devices and non-battery operated devices (external power supplied devices) in the core network, (108) specifically
[0064] In an embodiment, the processor (202) upon detection of the device (102) as the external power supplied device, may assign a predetermined value as the preconfigured value with the RRC inactivity timer. When a data transaction is initiated with the non-battery operated device and when the final data packet is sent, the processor (202) may start the RRC inactivity timer and upon expiry of the RRC inactivity timer, may release the RRC connection. Once the RRC connection is released, the non-battery operated device may go to another mode.
[0065] FIG. 3 illustrates an example flow diagram (300) of a conventional system.
[0066] As illustrated in FIG. 3, the flow diagram (300) may include the following steps.
[0067] At step 312: A battery operated IoT device (302) may request a RRC connection with a base station (306).
[0068] At step 314: The battery operated IoT device (302) may transmit an attach process with Power Saving Mode (PSM) support to a core network (308). The core network (308) may setup context and create data bearer based on the attach process.
[0069] At step 316: The core network (308) may transmit an initial context setup message to the base station (306).
[0070] At step 318: The base station (306) may transmit an attach accept message to the battery operated IoT device (302).
[0071] At step 320: The base station (306) may apply an “m” second inactivity timer for the data bearer.
[0072] At step 322: The external power supplied IoT device (304) may request a RRC connection with a base station (306).
[0073] At step 324: The external power supplied IoT device (304) may transmit an attach process with no PSM support to a core network (308). The core network (308) may setup context and create data bearer based on the attach process.
[0074] At step 326: The core network (308) may transmit an initial context setup message to the base station (306).
[0075] At step 328: The base station (306) may transmit an attach accept message to the external power supplied IoT device (304).
[0076] At step 330: The base station (306) may apply an “m” second inactivity timer for the data bearer and initiate data transaction.
[0077] At step 332: The last data packet may be exchanged from the battery operated IoT device (302) with the core network (308) via the base station (306).
[0078] At step 334: The base station (306) may start the inactivity timer. The inactivity timer may be m second for a data bearer.
[0079] At step 336: The base station (306) may release the RRC connection associated with the battery operated IoT device (302) and end the inactivity timer.
[0080] At step 338: The base station (306) may initiate the data transaction.
[0081] At step 340: The last data packet may be exchanged from the external power supplied IoT device (304) with the core network (308) via the base station (306). The base station (306) may start the inactivity timer.
[0082] At step 342: The base station (306) may release the RRC connection associated with the external power supplied IoT device (304) after the inactivity timer has expired.
[0083] At step 344: The base station (306) may apply the same inactivity timer to all the devices.
[0084] FIG. 4 illustrates an example flow diagram (400) of the proposed system (106), in accordance with an embodiment of the present disclosure.
[0085] As illustrated in FIG. 4, the flow diagram (400) may include the following steps.
[0086] At step 414: A battery operated IoT device (402) may request a RRC connection with a base station (406).
[0087] At step 416: The battery operated IoT device (402) may transmit an attach process to the MME/AMF (408).
[0088] At step 418: The MME/AMF (408) may transmit an update location request to a HSS (410). The HSS (410) may assign the SPID = a for subscribers of the battery operated IoT device (402) and the SPID= b assigned to subscribers of non-battery operated device/ external power supplied IoT device (404).
[0089] At step 420: The MME/AMF (408) may transmit an update location request message including the SPID to the HSS (410). The base station (406) may configure an inactivity timer of “n” seconds against the ICS request with SPID.
[0090] At step 422: The HSS (410) may transmit an update location answer message (with SPID = a) to the MME/AMF (408).
[0091] At step 424: The MME/AMF (408) may transmit the initial context setup request message to the base station (406) along with the SPID value
[0092] At step 426: The base station (406) may transmit an attach accept message to the battery operated IoT device (402).
[0093] At step 428: The battery operated IoT device (402) may transmit an attach complete message to the MME/AMF (408) based on the attach accept message.
[0094] At step 430: The base station (406) may apply an “n” second RRC inactivity timer with SPID = a.
[0095] At step 432: The external power supplied IoT device (404) may request the RRC connection with the base station (406).
[0096] At step 434: The external power supplied IoT device (404) may transmit an attach process with no PSM support message to the MME/AMF (408).
[0097] At step 436: MME/AMF (408) may transmit an update location request message to the HSS (410).
[0098] At step 438: The HSS (410) may transmit an update location answer message (SPID=b) to the MME/AMF (408).
[0099] At step 440: The MME/AMF (408) may transmit initial context setup request message to the base station (406) along with the SPID value.
At step 442: The base station (406) may transmit an attach accept message to the external power supplied IoT device (404). The base station (406) may configure an inactivity timer of “m” seconds against the ICS request with SPID value b.
[00100] At step 444: The external power supplied IoT device (404) may transmit an attach complete message to the MME/AMF (408).
[00101] At step 446: The base station (406) may apply an “m” second RRC inactivity timer with SPID value b.
[00102] At step 448: The battery operated IoT device (402) may initiate data transaction.
[00103] At step 450: The last data packet transferred by the battery operated IoT device (402) may be received by the base station (406) and the base station (406) may start the RRC inactivity timer. The RRC inactivity timer may be N second for the data bearer.
[00104] At step 452: The base station (406) may release the RRC connection associated with the battery operated IoT device (402) and end the timer.
[00105] At step 454: The battery operated IoT device (402) may go into a sleep mode.
[00106] At step 456: The external power supplied IoT device (404) may initiate data transaction.
[00107] At step 458: The last data packet transferred by the external power supplied IoT device (404) may be received by the base station (406) and the base station (406) may start the RRC inactivity timer. The RRC inactivity timer may be m second for the data bearer.
[00108] At step 460: The base station (406) may release the RRC connection associated with the external power supplied IoT device (404) and end the timer.
[00109] At step 462: The external power supplied IoT device (404) may go into an idle mode and listen for incoming packets (data packets).
[00110] At step 464: Separate RRC inactivity timers may be implemented for different devices.
[00111] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented. In an embodiment, the system (106) or the UE (102) may be implemented as the computer system (500).
[00112] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (560) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.
[00113] In an embodiment, the main memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input/output system (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces).
[00114] In an embodiment, the bus (520) may communicatively couple the processor(s) (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).
[00115] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.
[00116] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

ADVANTAGES OF THE INVENTION
[00117] The present disclosure provides identification of battery-operated devices at the core network based on subscriber profile identification (SPID) value assigned to the devices.
[00118] The present disclosure provides a system that checks the SPID value in an Initial Context Setup (ICS) request and based on the SPID value configures the RRC inactivity timer to the devices.
[00119] The present disclosure provides a system that identifies the devices as a battery operated device or an external power supplied device based on the SPID value and correspondingly assigns a Radio Resource Control (RRC) inactivity timer based on the SPID value.

 
, Claims:1. A system (106) for assigning optimized inactivity timers, the system (106) comprising:
a processor (202) communicatively coupled to a Radio Access Network (RAN) node (110);
a memory (204) operatively coupled with the processor (202), wherein said memory (204) stores instructions which, when executed by the processor (202), cause the processor (202) to:
receive a request from one or more devices (102) for exchange of one or more radio resources, wherein the request is based on an attach process transmitted by the one or more devices (102) to a core network (108);
generate one or more mapped radio bearers associated with the one or more devices (102) based on the request;
identify at least one device among the one or more devices (102) based on the one or more mapped radio bearers as a battery operated device or an external power supplied device through information preconfigured and received from the core network; and
correspondingly assign a Radio Resource Control (RRC) inactivity timer with a preconfigured value based on the identification of the device (102).
2. The system (106) as claimed in claim 1, wherein the attach process comprises an Initial Context Setup (ICS) request received by the processor (202) from the core network (108).
3. The system (106) as claimed in claim 2, wherein the processor (202) is configured to receive a subscriber profile identification (SPID) as the information from the core network (108) through the ICS request and configure the RRC inactivity timer based on the SPID.
4. The system (106) as claimed in claim 2, wherein the processor (202) is configured to establish the RRC connection based on the SPID received in the ICS request and apply the RRC inactivity timer to the battery operated device or the external power supplied device. .
5. The system (106) as claimed in claim 1, wherein upon detection of the device (102) as the battery operated device, the processor (202) is configured to assign a minimum value as the preconfigured value with the RRC inactivity timer.
6. The system (106) as claimed in claim 1, wherein upon detection of the device as the external power supplied device, the processor (202) is configured to assign a predetermined value as the preconfigured value with the RRC inactivity timer.
7. A method for assigning optimized inactivity timers, the method comprising:
receiving, by a processor (202), associated with a system (106), a request from one or more devices (102) for exchange of one or more radio resources, wherein the request is based on an attach process transmitted by the one or more devices (102) to a core network (108);
generating, by the processor (202), one or more mapped radio bearers associated with the one or more devices (102) based on the request; and
identifying, by the processor (202), at least one device (102) among the one or more devices (102) based on the one or more mapped radio bearers as a battery operated device or an external power supplied device through information preconfigured and received from the core network (108); and
correspondingly assigning a Radio Resource Control (RRC) inactivity timer with a preconfigured value based on the identification of the device (102).
8. The method as claimed in claim 7, comprising receiving, by the processor (202), the attach process comprising an Initial Context Setup (ICS) request from the core network (108).
9. The method as claimed in claim 8, comprising receiving, by the processor (202), a subscriber profile identification (SPID) as the information from the core network (108) through the ICS request and configuring the RRC inactivity timer based on the SPID value.
10. The method as claimed in claim 9, comprising establishing, by the processor (202), the RRC connection based on the SPID received in the ICS request and applying the RRC inactivity timer to the battery operated device or the external power supplied device. .
11. The method as claimed in claim 7, comprising assigning, by the processor (202), upon detection of the device (102) as the battery operated device, a minimum value as the preconfigured value with the RRC inactivity timer.
12. The method as claimed in claim 7, comprising assigning, by the processor (202), upon detection of the external power supplied device, a predetermined value as the preconfigured value with the RRC inactivity timer.
13. A user equipment (UE) (102) for sending requests, the UE (102) comprising:
one or more processors communicatively coupled to a processor (202) associated with a system (106), wherein the one or more processors are coupled with a memory, and wherein said memory stores instructions which, when executed by the one or more processors, cause the one or more processors to:
transmit a request from for exchange of one or more radio resources,
wherein the processor (202) is configured to:
receive the request from the UE (102), wherein the request is based on an attach process transmitted by the UE (102) to a core network;
generate one or more mapped radio bearers associated with the UE (102) based on the request; and
identify at least UE (102) among one or more UEs (102) based on the one or more mapped radio bearers as a battery operated device and an external power supplied device through information preconfigured and received from the core network; and
correspondingly assign a Radio Resource Control (RRC) inactivity timer with a preconfigured value based on the identification of the UE (102).