FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“SYSTEM AND METHOD OF PROVIDING ONE OR MORE SERVICES ACROSS MULTIPLE APNs”
We, Reliance Jio Infocomm Limited, an Indian National, of, 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad-380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF INVENTION:
The present invention relates generally to the field of wireless communication systems, and more particularly relates to providing one or more services to user devices.
BACKGROUND OF THE INVENTION:
The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
Today a wireless network, that is widely deployed to provide various communication services such as voice, video, data, advertisement, content, messaging, broadcasts, etc. usually comprises multiple access networks and support communications for multiple users it hosts by sharing the available network resources.
One example of such a network is Evolved Universal Terrestrial Radio Access (E-UTRA) which is a radio access network standard meant to be a replacement of Universal Mobile Telecommunications System (UMTS) and High-Speed Downlink Packet Access/High-Speed Uplink Packet Access (HSDPA/HSUPA) technologies specified in 3GPP releases 5 and beyond. Unlike HSPA, LTE's E-UTRA is a new air interface system, unrelated to and incompatible with W-CDMA. It provides higher data rates, lower latency and is optimized for packet data. The earlier UMTS Terrestrial Radio Access Network (UTRAN) is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP). The UMTS, which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as Wideband-Code Division Multiple Access (W-CDMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division-Synchronous Code Division Multiple Access (TD-SCDMA). The UMTS also supports enhanced 3G data communications protocols, such

as High-Speed Packet Access (HSPA), which provides higher data transfer speeds and capacity to associated UMTS networks.
Furthermore, as the demand for mobile data and voice access continues to increase, research and development continue to advance. the technologies are required not only to meet the growing demand for access but to also advance and enhance the users’ experience with user devices. Some of the technologies that have evolved starting GSM/EDGE, UMTS/HSPA, CDMA2000/EV-DO and TD-SCDMA radio interfaces with the 3GPP Release 8, e-UTRA is designed to provide a single evolution path for providing increase in data speeds, and spectral efficiency, and allowing the provision of more functionality.
Referring to Figure 1 describes a network LTE ecosystem and the different nodes related to it, and Figure 2 illustrates signaling data flow in the LTE Network between its’ different nodes, and particularly describes the essential entities in a call flow based on flow of data packet with respect to APN. A user device represents generally represent an end-single customer or a group of customers. The user device is the provisioning done in the SIM-card i.e. the user or a group of users, can have an enterprise plan (which usually comes with different APN and policy charging) or a normal data plan (with the existing APN).
The eNodeB (eNB) is responsible for the complete radio management of next generation network. When a user device latches, the eNB is responsible for Radio Resource Management, i.e. the eNB shall do the radio bearer control, radio admission control, allocation of uplink and downlink to user device etc. When a packet from the user device arrives at the eNB, the eNB shall compress the IP header and encrypt the data stream.
The Mobility management entity (MME) is a control entity responsible for all the control plane operations. All the NAS signaling originated at the user device terminates at the MME. The MME is also responsible for tracking area list management, selection of PGW/SGW and selection of other MMEs during handovers. It is the first contact point for the networks. The MME is also responsible for SGSN selection during legacy handovers.

The Serving Gateway (SGW) terminates the interface towards the eNB. For each user device associated with EPS, at any given point of time, there is a single Serving GW. The SGW acts a local mobility anchor for inter eNB handovers. It also acts a mobility anchor for inter 3GPP mobility. SGW is responsible for packet routing and forwarding, buffering the downlink packets and lawful interception. As eNB is responsible for uplink packet marking, SGW is responsible for downlink packet marking.
The Packet Data Network Gateway (PGW) is responsible for all the IP packet-based operations such as deep packet inspection, user device IP address allocation, Transport level packet marking in uplink and downlink, accounting etc. The PGW contacts the Policy and Charging Rules Function (PCRF) to determine the quality of service (QoS) for bearers. It is also responsible for uplink and downlink rate enforcement based on APN Aggregate Maximum Bit Rate (APN-AMBR).
The APN stands for Access Point Name, is a gateway (or Anchoring point) to which a user device (e.g., a mobile phone) gets attached to get access to the core network for the data service. Basically, it gets assigned by network based on the request from the user device. So, APN is a combination of user device setting (for request) and Network configuration. Thus, APN is a gateway between a GSM, GPRS, 3G or 4G service operator network and another computer network, frequently the public Internet. A user device making a data connection must be configured with an APN to present to the service operator. The service operator will then examine this identifier to determine what type of network connection should be created, for example: which IP addresses should be assigned to the wireless device, which security methods should be used, and how or if, it should be connected to some private customer network.
More specifically, the APN identifies the packet data network (PDN) that a mobile data user wants to communicate with. In addition to identifying a PDN, an APN may also be used to define the type of service, (e.g. connection to Wireless Application Protocol (WAP) server, Multimedia Messaging Service (MMS)) that is provided by the PDN. The APN is used in 3GPP data access networks, e.g. General Packet Radio Service (GPRS), evolved packet core (EPC).
The user device has proprietary files indicating status of device connection and which gets generated in system memory of device. The device has apns-conf.xml file

containing list of worldwide APNs mapped with MCC/MNC. This xml file or similar mechanism is present inside device telephony API of modem layer of device which provides APIs for monitoring the basic phone information such as the network type, the connection state and gets information about MCC/MNC.
In a conventional approach, an IMSI is an integral part of APN selection. For instance, when a user device is powered ON, the user device selects a preferred PLMN. The user device may also extract MCC/MNC from the selected PLMN and select the APN as per extracted MCC/MNC. Accordingly, the selected PLMN is then used instead of the IMSI for the APN selection. Table 1 below describes the role of APN between the end user’s equipment (UE) and all the entities of network as described above.

UE ENB MME S-GW P-GW HSS PCRF SPR
APN EPS Bearer ID DRB ID Default APN APN in Use APN in Use Default APN APN in Use -

E-RAB ID APN in Use EPS Bearer ID EPS Bearer ID - - -

S1 TEID (UL/DL) EPS Bearer ID - - - - -

QCI - - - - - -

ARP E-RAB ID S1 TEID (UL/DL) - - - -

UE-AMBR (UL/DL) S1 TEID (UL/DL) S5 TEID (UL/DL) S5 TEID (UL/DL) Subscribe d Profile QCI -

- S5 TEID (UL/DL) QCI QCI (Subscrib ed QCI, ARP, UE-AMBR, APN-AMBR) ARP

- QCI ARP ARP - Access

Profile

ARP - - APN (subscrib
ed QCI, ARP, APN-AMBR)

UE-AMBR - APN -
(UL/DL)

APN- - - AMBR
AMBR (UL/DL) (UL/DL)

- - AMBR SDF Filter
(UL/DL)

Subscribe TFT -
d Profile (Subscrib ed QCI, ARP, UE-AMBR, APN-AMBR) (UL/DL)

PCC Rule

PCC Rule
Table 1: Information in EPS entity after Initial Attach
Thus, APN plays an important role in the network ecosystem, hence, any change in the APN or introduction of new APN may cause an imbalance of IP traffic routing in the ecosystem and require changes to be made at the network as well as the user device side, thus, resulting in time consuming troubleshooting and loss in business. As most network operators use only single APN for data, the devices can either use NULL APN for Attach or advertise “APN X” specifically in the Attach Request. Moreover, currently the enterprise APN is same for all the customer and there are no separate APNs reserved for the use for enterprise customers. Also, there are no solutions to

administer the provisioning on real time basis for enterprise customer for specific whitelisting or define new rules to divert specific data across a specific APN as well as add other white-listed URL or device management URL. Therefore, in view of the above cited and other inherent limitations in the existing solutions, there exists a need in the art to provide a system and a method for providing one or more services to a user device over different APNs.
SUMMARY OF THE INVENTION
This section is provided to introduce certain objects and aspects of the present invention 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. In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present invention is to provide a system and a method for providing one or more services to at least one user device. Another object of the present invention is to provide a method and a system for providing one or more services to the at least one user device over different access point names (APNs), such that introduction of new APNs does not cause any imbalance of the IP traffic routing in the ecosystem and will also not result in the requirement of changes to be made at network as well as user device side. Yet another object of the present invention is to provide a solution to provision separate APNs for device administrative operations such as remote device management, SIM management services. Yet another object of the present invention is to provide method and system for segregation of the users (for example, based on Enterprise and Retail users) according to the use of data and the APN used respectively.
In order to achieve the aforementioned objectives, the present invention provides a method and system to provide one or more services to at least one user device. An aspect of the present invention relates to a method for providing one or more services to at least one user device. The method comprises receiving, at an eNodeB, an attach request from the at least one user device, wherein the attach request comprises of at least one unique identifier for the at least one user device and a request for the one or more services. Next, a packet data network gateway automatically configures one

or more access point names (APN) for the at least one user device based on the at least one unique identifier and an index of APN maintained at the packet data network gateway. Subsequently, the packet data network gateway dynamically detects a type of data associated with the one or more services. Further, the packet data network gateway forks an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device. Lastly, a packet data network, via the packet data network gateway, provides the one or more services to the at least one user device based on the forked APN.
Another aspect of the present invention relates to a system to provide one or more services to at least one user device. The system comprises of an eNodeB configured to receive an attach request from the at least one user device, wherein the attach request comprises of at least one unique identifier for the at least one user device and a request for the one or more services. The system further comprises of a packet data network gateway connected to the eNodeB, said packet data network gateway configured to automatically configure one or more access point names (APN) for the at least one user device based on the at least one unique identifier and an index of APN maintained at the packet data network gateway, to dynamically detect a type of data associated with the one or more services, and to fork an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device. The system also comprises of a packet data network connected to the packet data network gateway, said packet data network configured to provide the one or more services to the at least one user device based on the forked APN via the packet data network gateway.
BRIEF DESCRIPTION OF DRAWINGS
The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in 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 disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
Figure 1 illustrates an exemplary LTE network architecture diagram.
Figure 2 illustrates existing signaling data flow in the LTE Network.
Figure 3 illustrates an exemplary network architecture diagram indicating latching of a user device with radio access technologies (RATs), in accordance with exemplary embodiments of the present invention.
Figure 4 illustrates an exemplary network architecture diagram [400], in accordance with exemplary embodiments of the present invention.
Figure 5 illustrates an exemplary block diagram of Long-Term Evolution (LTE) eNodeB, in accordance with exemplary embodiments of the present invention.
Figure 6 illustrates an exemplary block diagram of a user device, in accordance with exemplary embodiments of the present invention.
Figure 7 illustrates an exemplary method flow diagram [700], depicting a method to for providing one or more services to at least one user device, in accordance with exemplary embodiments of the present invention.
Figure 8 illustrates an exemplary illustration of IP traffic routing in the LTE Network ecosystem, in accordance with exemplary embodiments of the present invention.
Figure 9 illustrates an exemplary method flow diagram depicting implementation of the solution of the present invention at the user device, in accordance with exemplary embodiments of the present invention.
Figure 10 illustrates an exemplary use case of providing one or more services to at least one user device, in accordance with exemplary embodiments of the present invention.
Figure 11 illustrates another exemplary use case of providing one or more services to at least one user device, in accordance with exemplary embodiments of the present invention.

Figure 12 illustrates another exemplary use case of providing one or more services to at least one user device, in accordance with exemplary embodiments of the present invention.
The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION OF THE INVENTION
In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of embodiments of the invention. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be restrictive.
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 invention as set forth.
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 in order to avoid obscuring the embodiments.
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a sequence 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.
Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a machine-readable medium. A processor(s) may perform the necessary tasks. ‘
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.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. 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.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the

context clearly 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.
As utilized herein, terms “component,” “system,” “platform,” “node,” “layer,” “selector,” “interface,” and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a process running on a processor, a processor, an object, an executable, a program, a storage device, and/or a computer. By way of illustration, an application running on a server and the server can be a component. One or more components can reside within a process and a component can be localized on one computer and/or distributed between two or more computers.
Further, these components can execute from various computer-readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry which is operated by a software application or a firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be any apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components.
In addition, the disclosed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering

techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, computer-readable carrier, or computer-readable media. For example, computer-readable media can include, but are not limited to, magnetic storage devices, e.g., hard disk; floppy disk; magnetic strip(s); optical disk (e.g., compact disk (CD), digital video disc (DVD), Blu-ray Disc™ (BD); smart card(s), flash memory device(s) (e.g., card, stick, key drive).
Moreover, terms like “source and/or destination user device (UE)”, “mobile station”, “smart computing device”, “user device”, “ user device ”, “device”, “smart mobile communications device”, “mobile communication device”, “mobile device”, “mobile subscriber station,” “access terminal,” “terminal,” “handset,” “originating device,” “terminating device,” and similar terminology refers to any electrical, electronic, electro-mechanical computing device or equipment or a combination of one or more of the above devices. Smart computing devices may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, pager, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device as may be obvious to a person skilled in the art. In general, a smart computing device is a digital, user-configured, computer networked device that can be operated autonomously. A smart computing device is one of the appropriate systems for storing data and other private/sensitive information. The smart computing device operates at all the seven levels of ISO reference model, but the primary function is related to the application layer along with the network, session and presentation layer. The smart computing device may also have additional features of a touch screen, apps ecosystem, physical and biometric security, etc. Further, a ‘smartphone’ is one type of “smart computing device” that refers to the mobility wireless cellular connectivity device that allows end users to use services on cellular networks such as including but not limited to 2G, 3G, 4G, 5G and/or the like mobile broadband internet connections with an advanced mobile operating system which combines features of a personal computer operating system with other features useful for mobile or handheld use. These smartphones can access the Internet, have a touchscreen user interface, can

run third-party apps including capability of hosting online applications, music players and are camera phones possessing high-speed mobile broadband 4G LTE internet with video calling, hotspot functionality, motion sensors, mobile payment mechanisms and enhanced security features with alarm and alert in emergencies. Mobility devices may include smartphones, wearable devices, smart-watches, smart bands, wearable augmented devices, etc. For the sake of specificity, the mobility device is referred to both feature phone and smartphones in present disclosure but does not limit the scope of the disclosure and may extend to any mobility device in implementing the technical solutions. The above smart devices including the smartphone as well as the feature phone including IoT devices enable the communication on the devices. Further, the foregoing terms are utilized interchangeably in the subject specification and related drawings.
Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” “owner,” and the like are employed interchangeably throughout the subject specification and related drawings, unless context warrants particular distinction(s) among the terms. It should be appreciated that such terms can refer to human entities, or automated components supported through artificial intelligence, e.g., a capacity to make inference based on complex mathematical formulations, that can provide simulated vision, sound recognition, decision making, etc. In addition, the terms “wireless network” and “network” are used interchangeable in the subject application, unless context warrants particular distinction(s) among the terms.
As used herein, a “processor” or “processing unit” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, a low-end microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

The present invention relates to a method and a system of providing one or more services to at least user device. The present invention solves the problem of introduction of new APN(s) such that the introduction does not cause any imbalance of the IP traffic routing in the ecosystem and also does not result in the requirement of changes to be made at network as well as user device side. The solution of the present invention provides provisioning for separate APN(s) for device administrative operations such as remote device management, SIM management services, and user enterprise data access.
Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present disclosure.
Referring to Figure 3 illustrates an exemplary network architecture diagram indicating latching of a user device [302] with radio access technologies (RATs), in accordance with exemplary embodiments of the present invention. As shown at [300A] and [300B] in Figure 3, the user device [302] is latched to a long-term evolution (LTE) network [310] and/or to a legacy (UTRAN/GSM) network [306] via the eNodeB [308] and NodeB/BTS [304] respectively. Therefore, Figure 3 indicates the latching of the user device [302] with various radio access technologies (RATs). Further, the wireless communication networks, with which the user device [302] is connected/latched, provides to the latched user device [302] one or more services (e.g., voice traffic, data traffic etc.) through base station/s of the said wireless network/s.
Furthermore, the exemplary network architecture diagram as indicated in Figure 3 illustrate exemplary wireless communication network(s)/network entities (i.e. the LTE network and the UTRAN/GSM network) and other network entities, such as other legacy networks, 5G-New Radio (NR) networks, etc. with which the user device [302] is latched can also be implemented. Also, in the exemplary implementation the user device [302] is one of a single SIM and a multi-SIM user device [302]. Therefore, in such exemplary implementation the latching of one of the single SIM and the multi-SIM user device [302] will be with one of a single radio access technologies (RAT) and multiple different radio access technologies (RATs), respectively.

Referring to Figure 4 illustrates an exemplary network architecture diagram [400], in accordance with exemplary embodiments of the present invention. As shown in Figure 4, the exemplary network architecture diagram [400] comprises a number of components/units such as including but not limited to a Mobility Management Entity (MME) [402], an Evolved Universal Terrestrial Access Network (E-UTRAN) [404], a Home Subscriber Server (HSS) [406], a serving gateway [408], a Packet data network [414] (PDN) gateway [410], a Serving GPRS Support Node (SGSN), a UMTS Terrestrial Radio Access Network (UTRAN), a GSM/EDGE Radio Access Network (GERAN), a policy and charging rules function (PCRF) etc. Further, only the units/components of the network architecture diagram [400] that are important are explained here. Also, the components as shown in the network architecture diagram [400] are connected with each other over various interfaces such as the MME [402] is connected to the E-UTRAN [404] over an S1-MME interface and the MME [402] is connected to the HHS [406] over an S6a interface etc.
The E-UTRAN [404] comprises a set of eNodeB [404A] connected to an Evolved Packet Core (EPC) through an S1 interface. Further, the eNodeB [404A] is configured to support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode or dual-mode operation. Also, the eNodeB [404A] is responsible for assigning one or more radio resources to the at least one user device [302]. The eNodeB [404A] is also configured to receive an attach request from the at least one user device [302], wherein the attach request comprises of at least one unique identifier for the at least one user device [302] and a request for the one or more services. For instance, the present invention encompasses that the at least one unique identifier comprises of an International Mobile Subscriber Identity (IMSI). In an instance of the present invention, the user device [302] is connected with the E-UTRAN [404]. The user device [302] is latched to the E-UTRAN [404] to avail one or more services from the corresponding network entity.
The MME (Mobility Management Entity) [402] is configured to manage a control plane, and to handle signaling related to mobility and security for E-UTRAN [404] access. The MME [402] is also responsible for tracking and paging of the at least one user device [302] in idle mode. The MME [402] is also a termination point of a Non-Access Stratum (NAS).

The Home Subscriber Server (HSS) [406] is a database that contains user-related and subscriber-related information. The HSS [406] also provides support functions in mobility management, call and session setup, user authentication and access authorization.
The gateways, i.e. the Serving Gateway (SGW) [408] and the packet data network gateway [410] (PGW) [410] deal with a user plane. The gateways are configured to transport an IP data traffic between the at least one user device [302] and one or more external networks. The SGW [408] is a point of interconnect between a radio-side and the EPC. Further, the SGW [408] serves the at least one user device [302] by routing an incoming and outgoing IP packets. The SGW [408] also acts an anchor point for an intra-LTE mobility (i.e. in case of handover between eNodeB [404A]s) and for mobility between LTE and other 3GPP accesses. Also, the SGW [408] is logically connected to another gateway, i.e. to the PGW [410].
The PDN GW [410] is a point of interconnect between the EPC and the external IP networks. These networks are called Packet data network [414] (PDN) [414] and is configured to route packets to and from one or more Packet data network [414]s (PDNs). The PGW [410] also performs various functions such as IP address/IP prefix allocation or policy control and charging, etc.
The PGW [410] is configured to automatically configure one or more access point names (APN) for the at least one user device [302] based on the at least one unique identifier and an index of APN maintained at the packet data network gateway [410]. For instance, the present invention encompasses that the index of APN comprises of a correlation of one or more APNs associated with the at least one user device [302] and the type of data associated with the one or more APNs. For instance, wherein the at least one user device [302] is an enterprise device, and one or more APNs for the at least one user device [302] comprises of at least an enterprise APN and other APN. The PGW [410] is also configured to dynamically detect a type of data associated with the one or more services. For example, the PGW [410] is configured to detect type of data as at least one of an administrative data and a user data.
The PGW [410] is further configured to fork an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device

[302]. The PGW [410] identifies an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device [302]. For instance, the present invention encompasses that the at least one parameter for the at least one user device [302] is pre-stored and known at the PGW [410], and comprises at least one of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI), media access control identifier (MAC ID), Integrated Circuit Card Identifier (ICCID) and a destination IP address.
The PGW [410] is also configured to facilitate providing the one or more services to the at least one user device [302] based on the forked APN by the PDN [414]. For instance, the PGW [410] is configured to facilitate providing the administrative data over a first APN (say, APN1) and a user data over a second APN (say, APN2).
In an instance, the PDN [414] may comprise of one or more servers for providing one or more services to the at least one user device [302], say an enterprise server and an administrative server. Furthering the previous example, if the one or more services are to be provided by the administrative server, meaning that the data type is administrative data, the PGW [410] identifies APN1 for transmitting the administrative data to the at least one user device [302]. In another instance, if the one or more services are to be provided by the enterprise server, meaning that the data type is user data for an enterprise user device [302], the PGW [410] identifies APN2 for transmitting the user data to the at least one user device [302].
In an instance of the present invention, the attach request further comprises of an indication of a pre-determined APN, accordingly, the PGW [410] is further configured to update the index of APN for the at least one user device [302] with the pre¬determined APN. The said instance of the present invention is further discussed in detail in reference to Figure 10.
In another instance of the present invention, the attach request further comprises of an indication of NULL APN, the packet data network gateway [410] is further configured to allocate an APN to the at least one user device [302]. The PGW [410] is further configured to update the index of APN for the at least one user device [302]

with the allocated APN. The said instance of the present invention is further discussed in detail in reference to Figure 11.
In yet another instance of the present invention, the attach request further comprises of an indication of a user-defined APN, the PGW [410] is further configured to update the index of APN for the at least one user device [302] with the user-defined APN. The said instance of the present invention is further discussed in detail in reference to Figure 12.
The system further comprises a rule setting engine [422] (not shown in the figure) configured to modify one or more rules for the type of data associated with the one or more APNs. The rule setting engine [422] is, thus, responsible to administer the provisioning, on real-time basis, for an enterprise user device [302] for specific whitelisting or defining new rules to divert specific data across a specific APN as well as add other white-listed URL or device management URL.
The system further comprises a billing module [424] (not shown in the figure) configured to bill the at least one user device [302] for the one or more services based on the providing of the one or more services over the forked APN. The present invention, thus, ensures that an end customer is not billed/charged for data usage for either device or SIM management purposes. The data provided through the specific APN for such device or SIM management may be billed to the ODM/device manufacturers/ device providers/service operator.
Referring to Figure 5 illustrates an exemplary block diagram of the LTE eNodeB [404A], in accordance with exemplary embodiments of the present invention. As depicted in the figure 2, the LTE eNodeB [404A] may include but is not limited to a call processing unit [502], a radio resource management unit [504], a self-organizing network (SON) module , E-GTPU, SCDP/UDP/IP protocols, X2-AP, S1-AP interfaces, MAC layer, RLC layer, PDCP layer, RRC layer, physical layer (PHY layer), a scheduler and any other such unit obvious to a person skilled in the art.
Referring to FIGURE6 illustrates an exemplary block diagram of a user device [302] [302, 600], in accordance with exemplary embodiments of the present invention. The user device [302, 600] as indicated in the Figure 6 comprises at least one subscriber

identity module (SIM)/universal integrated circuit card (UICC) [620]. The user device [302, 600] further may comprise a plurality of subsystems [602, 602A, 602B, 602C, 603, 604, 605 and 606], wherein said subsystems [602, 602A, 602B, 602C, 603, 604, 605 and 606] may include, but not limiting to, a modem subsystem [602] with a Baseband DSP processor [602C] and a plurality of radio interfaces [602A]. The user device [302, 600] may further include a cellular radio, a transmission/reception radio frequency (RF) connected to the antenna [607] for receiving and transmitting wireless services such as VoIP and Internet/Intranet services. Also, the user device [302, 600] may comprise an application processor [604], a memory subsystem [605], a power subsystem [606] and an external I/O interfaces subsystem [603]. The present disclosure further encompasses that the subscriber identity module [620] may comprise a processor [620B], an I/O interface [620A], a RAM temporary storage [620C], an EEPROM / Non- volatile Memory (NVM) [620D] and a SIM file system [620E]. Further, the EEPROM / Non- Volatile Memory (NVM) [620D] may consist of an operating system code, a code of other SIM applications and the Auto International Mobile Subscriber Identity (IMSI) Switch SIM application. The SIM file system [620E] and USIM application may contain elementary files and location parameters such as EFLOCI (Location Information), EFPSLOCI (PS Location Information), EFEPSLOCI (PS Location Information) and various other application-specific files used by various SIM applications running on the subscriber identity module [620] along with a plurality of context and configuration files of the Auto IMSI Switch SIM application.
Referring to Figure 7 illustrates an exemplary method flow diagram [700], depicting a method to enable interactive voice/multimedia response (IVMR), in accordance with exemplary embodiments of the present invention. As shown in figure 7 the method [700] begins at step [702]. At step [704], an attach request is received from the at least one user device [302] at the eNodeB [404A], wherein the attach request comprises of at least one unique identifier for the at least one user device [302] and a request for the one or more services. In an instance of the present invention, the at least one unique identifier comprises of an International Mobile Subscriber Identity (IMSI).
At step [706], the PGW [410] automatically configures one or more access point names (APN) for the at least one user device [302] based on the at least one unique identifier and an index of APN maintained at the packet data network gateway [410].

For example, where the at least one user device [302] is an enterprise device, the one or more APNs for the at least one user device [302] comprises of at least an enterprise APN. The present invention encompasses that the index of APN comprises of a correlation of one or more APNs associated with the at least one user device [302] and the type of data associated with the one or more APNs.
At step [708], the PGW [410] dynamically detects a type of data associated with the one or more services. For instance, the PGW [410] is configured to facilitate providing the administrative data over a first APN (say, APN1) and a user data over a second APN (say, APN2).
At step [708], the PGW [410] forks an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device [302]. The PGW [410] identifies an APN based on the detected type of data and at least one parameter of the at least one user device [302]. In an instance of the present invention, the at least one parameter comprises at least one of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI), media access control identifier (MAC ID), Integrated Circuit Card Identifier (ICCID) and a destination IP address.
At step [712], the PDN [414] provide, via the packet data network gateway [410], the one or more services to the at least one user device [302] based on the forked APN. For instance, the PGW [410] is configured to facilitate providing the administrative data over a first APN (say, APN1) and a user data over a second APN (say, APN2). For example, if the one or more services are to be provided by the administrative server, meaning that the data type is administrative data, the PGW [410] identifies APN1 for transmitting the administrative data to the at least one user device [302]. In another instance, if the one or more services are to be provided by the enterprise server, meaning that the data type is user data for an enterprise user device [302], the PGW [410] identifies APN2 for transmitting the user data to the at least one user device [302]. Thus, the present invention provides intelligently introducing new APN(s) so that no imbalance of the IP traffic routing is cause in the ecosystem. The method terminates at step [714].

The present invention further encompasses that in an instance the attach request further comprises of an indication of a pre-determined APN, the PGW [410] automatically configures the one or more access point names (APN) for the at least one user device [302] further comprises updating the index of APN for the at least one user device [302] with the pre-determined APN. The said instance of the present invention is further discussed in detail in reference to Figure 10.
The present invention further encompasses that in another instance the attach request further comprises of an indication of NULL APN, the PGW [410] allocates an APN to the at least one user device [302], and automatically configuring the one or more access point names (APN) for the at least one user device [302] further comprises updating the index of APN for the at least one user device [302] with the allocated APN. The said instance of the present invention is further discussed in detail in reference to Figure 11.
The present invention further encompasses that in yet another instance the attach request further comprises of an indication of a user-defined APN, PGW [410] the automatically configures the one or more access point names (APN) for the at least one user device [302] further comprises updating the index of APN for the at least one user device [302] with the user-defined APN. The said instance of the present invention is further discussed in detail in reference to Figure 11.
The present invention also encompasses updating, at a rule setting engine [422], one or more rules for the type of data associated with the one or more APNs. The rule setting engine [422] administers the provisioning, on real-time basis, for an enterprise user device [302] for specific whitelisting or defining new rules to divert specific data across a specific APN as well as add white-listed URL or device management URL.
The present invention also encompasses billing the at least one user device [302] for the one or more services, by a billing module [424], based on the providing of the one or more services over the forked APN. Thus, an end customer is not billed/charged for data usage for either device or SIM management purposes. The data provided through the specific APN for such device or SIM management may be billed to the ODM/device manufacturers/ device providers/service operator

Figure 8 illustrates an exemplary illustration of IP traffic routing in the LTE Network ecosystem, in accordance with exemplary embodiments of the present invention. As illustrated, from the network end and specifically at the PGW [410], the network maintains a unique “fork” to divert and channel specific data on the corresponding data pipe provided by the APN. For example, all user data can be routed via APN1 and device administrative data can be routed via APN2. Since the network maintains an indexing of APN 2 to APN 1, the network views each enterprise user device [302] over two APN paths (APN1 and APN2). Thus, forking of data at the PGW [410] is based on combination of application level IP of device management entities and unique MSISDN/IMEI/MAC-Id of the enterprise user device [302]. Thus, for any enterprise user device [302] for which the network operator wishes to assign a separate APN with already an existing APN in the ecosystem, the challenge arises to maintain two different APNs if the user device [302] isn’t ready for the new APN and the other network elements aren’t configured for it.
As also illustrated in Figure 8, the APN 2 forks out from the main tunnel and reaches the administrative IPs, which will be used by the operator for OTA, FOTA and to execute operations related to other management specific features. The other part of the forking will reach out to the IPs specific to the enterprise customer i.e. user data and will be prominent than the APN2 since administrative data does not require much of data rate hence the data rate for enterprise customer remains unaffected and the customer need not unnecessarily be taxed for consuming this data. In the above diagram, considering the case of administrative IPs, which are reachable through APN 2, a data packet of the same arriving at P-GW will always be checked based on MSISDN,IP, IMEI, MAC ID, etc. and thus will be routed through the APN2 towards that specific administrative entity. Thus, from an end user’s perspective, a single bearer or a pipe that carries data is experiences, and simultaneously, when viewed from the PGW [410] end, it will be seen as two pipes forking out, with two different APNs.
Figure 9 illustrates an exemplary method flow diagram depicting implementation of the solution of the present invention at the user device [302], in accordance with exemplary embodiments of the present invention. The implementation starts at step [902]. At step [904], an enterprise user device [302] with a valid network operator sim card transmits an attach request to the network, and requests for one or more

services. At step [906], using the solution of the present invention, the network determines, if the APN being configured is APN1. If the APN being configured is not APN1, then the device is determined as being a non-enterprise user device [302], the method proceeds to step [908] and data is provided over APN2 and the method terminates at step [918]. If the APN being configured is APN1, then the device is determined as being an enterprise user device [302] and the method proceeds to step [910] where APN1 is indexed to APN2 in the index of the APN maintained at the PGW [410]. At step [912], the method determines the type of data associated with the one or more services. At step [914A], in an event the data type is user data accessing data over enterprise SIM card/external world/internet, the data is provided to the at least one user device [302] over one APN (say, APN2) at step [916A]. At step [914B], in an event the data type is administrative data, say remote management via Remote Device Management Service, SIM OTA SERVER communication, the data is provided to the at least one user device [302] over one APN (say, APN1) at step [916B]. The method terminates at step [918].
Referring to Figure 10 illustrates an exemplary use case of providing one or more services to at least one user device [302], in accordance with exemplary embodiments of the present invention. At step [1002], the user device [302] when sending an attach request sets the trans_info flag as one (“1”) which indicates that the user device [302] has an APN which it will broadcast once the security and authentication request is transmitted from the user device [302] to the network at step [1004], and an authentication response from the network is received at the user device [302] at step [1006]. The APN2 which is being used in the network (LTE) architecture for an enterprise user device [302], all the end application devices will broadcast the same APN if the below following criteria is met that, firstly, the device is in default mode and the APN is being hardcoded in the software, secondly, no other APN is being set manually by the user, and thirdly, the info_trans_flag is always set to one whatever may be the case of device bootup.
After the authentication and security mode procedures at steps [1008] and [1010], the network prompts the user device [302] to share its APN via ESM information messages at step [1012]. Thus, the user device [302] advertises the APN2 to the network at step [1014], which is also reflected in the attach accept message at step

[1024]. At step [1016], a security mode command flows from the network to the user device [302]. At step [1018], a security mode complete response flows from the user device [302] to the network. At step [1020], the network sends RRC connection reconfiguration message to the user device [302], and in response the user device [302] transmits RRC connection reconfiguration complete message to the network. At step [1026], the network asks the user device [302] to activate default bearer context request and in response, at step [1028], the user device [302] transmits the attach complete message to the network. At step [1030], the user device [302] also transmits the activate default bearer context accept to the network. At step [1032], the network releases the RRC connection.
The data packet routing from the user device [302] to the network (the PGW [410]) and eventually to the PDN [414] will be done on APN2. If there is an APN1 for the enterprise user device [302], which is being deployed in the production environment would tend to hamper the current ecosystem since for all administrative IPs, the APN required for authentication would be APN 1 and hence the user device [302] won’t be able to reach the administrative servers and hence the user device [302] will be restrained from any further FOTA or updates hence calling in more troubleshoot which will result in loss of time. The data packet which are meant to be destined at any administrative server will be routed using the existing APN with the function of MSISDN and IP. The user data will eventually flow through the APN1.
Figure 11 illustrates another exemplary use case of providing one or more services to at least one user device [302], in accordance with exemplary embodiments of the present invention. At step [1102], the user device [302] when sending an attach request doesn’t advertise the APN, i.e. the info trans flag under attach request is set to zero (“0”). After the authentication request is transmitted from the user device [302] to the network at step [1104], and an authentication response from the network is received at the user device [302] at step [1106], and the security mode procedures at steps [1108] - [1118] have been completed, the network allocates the APN2 which will be used for data routing from the user device [302] to the PGW [410] and further to outside internet in attach accept message at step [1120].

If a SIM of the user device [302] has been configured for another APN1, the same will be allocated to the user device [302] in the attach accept, though the administrative servers won’t be reachable for which there may be multiple reasons. Firstly, in most of the user device [302]s there’s a check maintained at the modem layer which implies that the APN is being used as authentication parameter i.e. the APN2 (existing APN in the ecosystem) should be present at the SIM and the modem layer. Thus, when the APN1 has been deployed in the production environment for enterprise customers, the modem has APN2 and the network allocates APN1 which clearly indicates a mismatch hence Administrative servers won’t be reachable. Therefore, any operations or if FOTA being triggered to the device, it won’t be executed thus the failure rate will increase drastically for few customers who tend to avail the data using APN1. Secondly, if the authentication overrides, the IPs should be whitelisted for the user who will be using APN1, which is a time-consuming process which results in loss for that particular period of time. Thus, when an administrative data packet arrives, it will accordingly get routed through APN2 and for an enterprise user device [302] for which the APN1 has been deployed, the other data packets (user data) will get routed through the APN1.
At step [1122], the network asks the user device [302] to activate default bearer context request and in response, at step [1124], the user device [302] transmits the attach complete message to the network. At step [1126], the user device [302] also transmits the activate default bearer context accept to the network. At step [1128], the network releases the RRC connection.
Referring to Figure 12 illustrates another exemplary use case of providing one or more services to at least one user device [302], in accordance with exemplary embodiments of the present invention. In an instance, the end user might wish to change the APN of his/her choice (say, APN3) and this will result into a scenario where the APN entered by the user will be considered by the network. The said APN will then be indexed to APN2 from the backend. Though it is set from the modem end, on any UI the APN which user has entered will be displayed.
At step [1202], the user device [302] when sending an attach request sets the trans_info flag as one (“1”) which indicates that the user device [302] has an APN

which it will broadcast once the security and authentication request is transmitted from the user device [302] to the network at step [1204], and an authentication response from the network is received at the user device [302] at step [1206]. After Authentication and security mode procedures are completed in steps [1208] and [1210], the user device [302] advertises the APN3 using the ESM information message [1214] in response to an ESM information request [1212]. The same will be displayed in attach accept message at step [1224] though the network being intelligent enough to index it to the APN which is already present in the ecosystem. This will ensure the flow of user data continuously though it will have an impact of device administrative data. The device won’t be able to reach the administrative IPs since now the APN isn’t the same and there will be a mismatch in at the modem side hence effecting device reachability towards administrative IPs. Implementing the solution of the present invention, the administrative data is routed with APN2 and the user data on enterprise APN1.
At step [1216], a security mode command flows from the network to the user device [302]. At step [1218], a security mode complete response flows from the user device [302] to the network. At step [1220], the network sends RRC connection reconfiguration message to the user device [302], and in response the user device [302] transmits RRC connection reconfiguration complete message to the network at step [1222]. At step [1226], the network asks the user device [302] to activate default bearer context request and in response, at step [1228], the user device [302] transmits the attach complete message to the network. At step [1230], the user device [302] also transmits the activate default bearer context accept to the network. At step [1232], the network releases the RRC connection.
Thus, the present invention provides a novel solution of providing one or more services to the at least one user device [302] on different APN(s). Furthermore, by implementing the features of the present invention it is ensured that introduction of new APN(s) does not cause any imbalance of the IP traffic routing in the ecosystem and also does not result in the requirement of changes to be made at network as well as user device [302] side. The solution of the present invention also provides provisioning for separate APN(s) for device administrative operations and users’ enterprise data.

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 invention. These and other changes in the preferred embodiments of the invention 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 to be implemented merely as illustrative of the invention and not as a limitation.

We Claim
1. A method of providing one or more services to at least one user device [302],
the method comprising:
- receiving, at an eNodeB [404A], an attach request from the at least one user device [302], wherein the attach request comprises of at least one unique identifier for the at least one user device [302] and a request for the one or more services;
- automatically configuring, by a packet data network gateway [410], one or more access point names (APN) for the at least one user device [302] based on the at least one unique identifier and an index of APN maintained at the packet data network gateway [410];
- dynamically detecting, at the packet data network gateway [410], a type of data associated with the one or more services;
- forking, at the packet data network gateway [410], an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device [302];
- providing by a packet data network [414], via the packet data network gateway [410], the one or more services to the at least one user device [302] based on the forked APN.

2. The method as claimed in claim 1, wherein the at least one unique identifier comprises of an International Mobile Subscriber Identity (IMSI).
3. The method as claimed in claim 1, wherein the at least one parameter comprises at least one of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI), media access control identifier (MAC ID), Integrated Circuit Card Identifier (ICCID) and a destination IP address.
4. The method as claimed in claim 1, wherein the at least one user device [302] is an enterprise device, and one or more APNs for the at least one user device [302] comprises of at least an enterprise APN.

5. The method as claimed in claim 1, wherein the index of APN comprises of a correlation of one or more APNs associated with the at least one user device [302] and the type of data associated with the one or more APNs.
6. The method as claimed in claim 1, wherein the attach request further comprises of an indication of a pre-determined APN, the automatically configuring the one or more access point names (APN) for the at least one user device [302] further comprises updating the index of APN for the at least one user device [302] with the pre-determined APN.
7. The method as claimed in claim 1, wherein the attach request further comprises of an indication of NULL APN, the method further comprises allocating an APN to the at least one user device [302] by the packet data network gateway [410].
8. The method as claimed in claim 7, wherein the automatically configuring the one or more access point names (APN) for the at least one user device [302] further comprises updating the index of APN for the at least one user device [302] with the allocated APN.
9. The method as claimed in claim 1, wherein the attach request further comprises of an indication of a user-defined APN, the automatically configuring the one or more access point names (APN) for the at least one user device [302] further comprises updating the index of APN for the at least one user device [302] with the user-defined APN.
10. The method as claimed in claim 1, wherein the method further comprises updating, at a rule setting engine [422], one or more rules for the type of data associated with the one or more APNs.
11. The method as claimed in claim 1, the method further comprises billing the at least one user device [302] for the one or more services, by a billing module [424], based on the providing of the one or more services over the forked APN.
12. A system for providing one or more services to at least one user device [302], the system comprising:

- an eNodeB [404A] configured to receive an attach request from the at least one user device [302], wherein the attach request comprises of at least one unique identifier for the at least one user device [302] and a request for the one or more services;
- a packet data network gateway [410] connected to the eNodeB [404A], said packet data network gateway [410] configured to:

- automatically configure one or more access point names (APN) for the at least one user device [302] based on the at least one unique identifier and an index of APN maintained at the packet data network gateway [410],
- dynamically detect a type of data associated with the one or more services,
- forked an APN from the one or more APNs based on the detected type of data and at least one parameter of the at least one user device [302]; and
- a packet data network [414] connected to the packet data network
gateway [410], said packet data network [414] configured to provide the
one or more services to the at least one user device [302] based on the
forked APN via the packet data network gateway [410].
13. The system as claimed in claim 12, wherein the at least one unique identifier comprises of an International Mobile Subscriber Identity (IMSI).
14. The system as claimed in claim 12, wherein the at least one parameter comprises at least one of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI), media access control identifier (MAC ID), Integrated Circuit Card Identifier (ICCID) and a destination IP address.
15. The system as claimed in claim 12, wherein the at least one user device [302] is an enterprise device, and one or more APNs for the at least one user device [302] comprises of at least an enterprise APN.

16. The system as claimed in claim 12, wherein the index of APN comprises of a correlation of one or more APNs associated with the at least one user device [302] and the type of data associated with the one or more APNs.
17. The system as claimed in claim 12, wherein the attach request further comprises of an indication of a pre-determined APN, the packet data network gateway [410] is further configured to update the index of APN for the at least one user device [302] with the pre-determined APN.
18. The system as claimed in claim 12, wherein the attach request further comprises of an indication of NULL APN, the packet data network gateway [410] is further configured to allocate an APN to the at least one user device [302].
19. The system as claimed in claim 18, wherein the packet data network gateway [410] is further configured to update the index of APN for the at least one user device [302] with the allocated APN.
20. The system as claimed in claim 12, wherein the attach request further comprises of an indication of a user-defined APN, the packet data network gateway [410] is further configured to update the index of APN for the at least one user device [302] with the user-defined APN.
21. The system as claimed in claim 12, wherein the system further comprises a rule setting engine [422] configured to modify one or more rules for the type of data associated with the one or more APNs.
22. The system as claimed in claim 12, the system further comprises a billing module [424] configured to bill the at least one user device [302] for the one or more services based on the providing of the one or more services over the forked APN.