reference may be made below to specific elements , numbered in accordance with the attached figures . the discussion below should be taken to be exemplary in nature , and not as limiting of the scope of the present invention . the scope of the present invention is defined in the claims , and should not be considered as limited by the implementation details described below , which as one skilled in the art will appreciate , can be modified by replacing elements with equivalent functional elements . while prior art reference us 20130024523a1 addresses the signaling storm scenario , it does not help with per flow sequence storage in the ggsn . the overhead of storage of flow sequence numbers and the task of changing the sequence number in both directions per tcp packet for tens of millions of flows is quite substantial . this disclosure presents a different system and method whereby a network element such as a ggsn leverages its proxy role and utilizes the http redirect mechanism to eliminate the above - said overhead . accordingly , it should be readily appreciated that in order to overcome the deficiencies and shortcomings of the existing solutions , it would be advantageous to have a solution for eliminating per flow overhead and also preventing tcp signaling storm during content enrichment . as discussed , an issue in content enrichment is the fact that when content is enriched ( i . e ., modified ) the tcp packet size changes and the tcp sequence number reflecting number of bytes sent in the pack become out of sync with the counter maintained at the user and server ends . the present disclosure is generally directed to a system and method for eliminating the need for an in path gateway to maintain and alter tcp related counters for each flow that goes through the gateway and is subject to content enrichment procedures . since the gateway does not need to alter the tcp counters this system and method of content enrichment disclosed herein is not susceptible to tcp signaling storms . fig5 illustrates a signal flow for an exemplary process of this disclosure . it will be appreciated that the steps involved in activating a pdp are not shown for the sake of simplicity . the establishment of a tcp session 508 is shown as a single bidirectional line prior to http signaling that is subject to content enrichment in fig5 . a network element ( e . g ., gateway ggsn ) 504 receives the http request 510 from the ue 502 . analyzing the uniform resource locator ( url ), it determines that this request needs to be enriched 512 . the ggsn 504 computes the size of the enriched header needed in this case . it then creates a substitution string of this size to be placed in the redirect url as explained below . a substitution string carries an identifier directly or that is implied . the redirect url such that redirect url = original requested url + substitution string . the substitution string may comprise : i ) a marker ; or ii ) marker + he placeholder . the ggsn 504 then issues the redirect 514 to the ue 502 with this as redirect url . with that it sends tcp fin to indicate this tcp connection needs to be terminated . the tcp connection is terminated with rst - ack 516 . upon receiving the http redirect the ue 502 issues a new http request to the redirected url 518 which again comes to ggsn 504 . the ggsn 504 identifies the marker and realizes that the marker and he placeholder in the url need to be replaced by the appropriate x - header . it proceeds to restore the original url and augment x - header to it in step 520 . the marker + he placeholder add up exactly to the size of the x - header . this operation does not require the tcp sequence number to be changed . the ggsn 504 can reduce the delay cause by redirection by precomputing the x - header and use the marker as a key to insert the correct x - header . the resulting request 522 is then sent to the server 506 . the server 506 will then acknowledge ( ack ) the tcp sequence number received 105 . this signal can now flow through ggsn unmodified since that is what ue 502 expects as well . from this point onwards the normal tcp flow continues and ggsn &# 39 ; s header enrichment has no impact whether the session terminates or lasts very long . fig6 is a flow chart illustrating a method executed by a network element such as a ggsn . ggsn is a gateway in the path of tcp communication between user and internet servers . in step 602 , a message is received at ggsn from a source node ( i . e ., mobile device ) addressed to a destination node ( i . e ., the server ). in step 604 , the ggsn identifies if the request needs to be enriched ( i . e ., header enrichment ). in step 606 , the ggsn computes the size of padding by adding x - headers and a marker , i . e ., create a redirect url by augmenting the original url with marker + he size placeholder . in step 608 , it sends a redirect message to the source node . in step 610 , ggsn receives a message from the source node addressed to the destination node with an augmented url ( i . e ., with marker ). in step 612 , the ggsn removes the marker + he padding from the url ; inserts he information in the header . in step 614 , send the header enriched message to the destination . in one aspect of the disclosure a network element such as a ggs utilizes its ability to alter the upper layer constructs such as http redirect . further , a ggsn can change the url in anticipation of enrichment it needs to do . for example , it can add marker and placeholder as suffix to the original url as discussed above . the size of the marker and placeholder could be made exactly to match the size of enrichment text that needs to be done . when the user browser receives the redirect url , it will initiate another tcp connection with redirected url in an http packet . since this url contains extra bytes of marker and placeholder , the tcp sequence number will include them as well . in another aspect of this disclosure , when the redirected http request reaches the ggsn , the marker in the url tells the ggsn that the url has been pre - adjusted for the content enrichment . therefore the ggsn can now safely remove the marker and the placeholder and add the content enrichment information in the http packet . thus the original url is restored and the ggsn can forward this to an internet server without modifying the tcp sequence since the tcp sequence is already correct for the overall http packet . the server unaware of original request , redirection and content enrichment continues to process the request and acknowledges all the bytes received in the tcp packet . this will be fine with the user since that is what is expected . from this point onwards the user and server can continue to communicate without the need for the ggsn to be altering the tcp sequence numbers . in another aspect of this invention , the resumption or termination of tcp session will not cause signaling storm since the ue and server are already in sync with respect to acknowledgments . as discussed above , the embodiments disclosed herein allow for enrichment of upper layer protocol content in tcp based sessions when such sessions pass through mobile packet core gateways such as a ggsn in 2g / 3g networks or p - gw in 4g mobile networks . the network element 700 as described above and further illustrated in fig7 preferably is located in the core network ( including being integrated with an mme ) or the functions as described herein may be divided among a plurality of network elements in the core network . however , in other embodiments the network element is not located physically at the core network but is logically located between the core network and the enodebs ( enbs ). the network element may have a controller , logic , memory , interface , and input / output which may be implemented using any suitable hardware , software and / or firmware configured as shown in fig7 . fig7 comprises one or more system control logic 704 coupled with at least one or all of the processor ( s ) 702 , system memory 706 , a network interface 708 ( including a transceiver 708 a ), and input / output ( i / o ) devices 710 . the processor ( s ) 702 may include one or more single - core or multi - core processors . the processor ( s ) 702 may include any combination of general - purpose processors and dedicated processors ( e . g ., graphics processors , application processors , baseband processors , etc .). system control logic 704 for one embodiment may include any appropriate interface controllers to provide for any suitable interface to at least one of the processor ( s ) 702 and / or to any suitable device or component in the packet core network in communication with system control logic 704 . system control logic 704 for one embodiment may include one or more memory controller ( s ) to provide an interface to system memory 706 . system memory 706 may be used to load and store data and / or instructions such as the knowledge database and logger function discussed above . system memory 706 for one embodiment may include any suitable volatile memory , such as suitable dynamic random access memory ( dram ), for example . system memory 706 may also include non - volatile memory including one or more tangible , non - transitory computer - readable media used to store data and / or instructions , for example , such as the embodiments described herein . the non - volatile memory may include flash memory , for example , and / or may include any suitable non - volatile storage device ( s ), such as one or more hard disk drive ( s ) ( hdd ( s )), one or more compact disk ( cd ) drive ( s ), and / or one or more digital versatile disk ( dvd ) drive ( s ). the memory 706 may include a storage resource physically part of a device . for example , the memory 704 may be accessed over a network via the network interface 708 and / or over input / output ( i / o ) devices 710 . the transceiver in network interface 708 may provide a radio interface to communicate over one or more network ( s ) and / or with any other suitable device . network interface 708 may include any suitable hardware and / or firmware . the network interface 708 may further include a plurality of antennas to provide a multiple input , multiple output radio interface . network interface 708 for one embodiment may include , for example , a wired network adapter , a wireless network adapter , a telephone modem , and / or a wireless modem . for one embodiment , at least one of the processor ( s ) 702 may be packaged together with logic for one or more controller ( s ) of system control logic 704 . for one embodiment , at least one of the processor ( s ) 702 may be integrated on the same die with logic for one or more controller ( s ) of system control logic 704 . in various embodiments , the i / o devices 710 may include user interfaces designed to enable user interaction with peripheral component interfaces designed to enable peripheral component interaction and / or sensors designed to determine environmental conditions and / or location information related to the network element or system . in various embodiments , the peripheral component interfaces may include , but are not limited to , a non - volatile memory port , a universal serial bus ( usb ) port , an audio jack , and a power supply interface . alternatively , some embodiments and methods discussed above may be implemented by a non - transitory computer - readable medium storing a program for performing the process . the computer readable medium may store ( in any appropriate format ) those program elements which are appropriate to perform the method . the term “ non - transitory computer readable medium ” refers to any medium , a plurality of the same , or a combination of different media , that participate in providing data ( e . g ., instructions , data structures ) which may be read by a computer , a processor or a like device . such a medium may take many forms , including but not limited to , non - volatile media , volatile media , and transmission media . non - volatile media may include , for example , optical or magnetic disks and other persistent memory . volatile media may include dynamic random access memory ( dram ), which typically constitutes the main memory . common forms of computer - readable media include , for example , a floppy disk , a flexible disk , hard disk , magnetic tape , any other magnetic medium , a cd - rom , dvd , any other optical medium , a random access memory ( ram ), a programmable read only memory ( prom ), an erasable programmable read only memory ( eprom ), a flash electrically erasable programmable read only memory ( flash - eeprom ), any other memory chip or cartridge , a carrier wave as described hereinafter , or any other medium from which a computer can read . in an embodiment , a server computer , network element or centralized authority may not be necessary or desirable . for example , an embodiment may be practiced on one or more devices without a central authority . in such an embodiment , any functions described herein as performed by the server computer or data described as stored on the server computer may instead be performed by or stored on one or more such devices . although process ( or method ) steps may be described or claimed in a particular sequential order , such processes may be configured to work in different orders . in other words , any sequence or order of steps that may be explicitly described or claimed does not necessarily indicate a requirement that the steps be performed in that order unless specifically indicated . further , some steps may be performed simultaneously despite being described or implied as occurring non - simultaneously ( e . g ., because one step is described after the other step ) unless specifically indicated . moreover , the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto , does not necessarily imply that the illustrated process or any of its steps are necessary to the embodiment ( s ), and does not imply that the illustrated process is preferred . in this disclosure , devices or networked elements that are described as in “ communication ” with each other or “ coupled ” to each other need not be in continuous communication with each other or in direct physical contact , unless expressly specified otherwise . in the foregoing specification , embodiments have been described with reference to specific exemplary embodiments thereof . it will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims . the specification and drawings are , accordingly , to be regarded in an illustrative sense rather than a restrictive sense .