1. A system for timing an event for a requesting entity, comprising:
A first server comprising a first timing module and a first store of timed events, wherein the first timing module is configured to receive a timing request from the requesting entity, associate the timing request with a specified event time, store the timing request in the first store, and direct a second timing module to store the timing request and the specified event time in a second store of timed events; and
A second server, the second timing module and the second store of timed events, wherein the first store is substantially similar to the second store;
Wherein the first timing module and the second timing module are configured such that the requesting entity receives a single notice of the requested event if the specified event time occurs.
2. The system of claim 1, further comprising:
A plurality of servers, wherein each server has a timing module and a store of timed events each substantially similar to the first store,
Wherein the plurality of timing modules are configured such that the requesting entity receives a single notice of the requested event if the specified event time occurs.
3. The system of claim 1 wherein the first store is configured as a directory configured to have a plurality of timer tick entries, wherein each timer tick entry corresponds a specified time interval, such that a sum of the specified time intervals corresponds to a maximum event time, wherein the first timing module is further configured to store the timing request in the first store by associating the timing request with a timer tick of the plurality of timer ticks in accordance with the specified event time.
4. The system of claim 1 wherein the first timing module is further configured to accept a timing cancellation request from the requesting entity, wherein upon receipt of the cancellation request the first timing module is further configured to delete the timing request from the first store and direct the second timing module to delete the timing request from the second store.
5. The system of claim 1 wherein the first timing module is further configured to accept a timing modification request from the requesting entity, wherein upon receipt of the modification request the first timing module is further configured to modify the timing request from the first store, update the specified event time, and direct the second timing module to modify the timing request and the specified event time in the second store.
6. The system of claim 1, further comprising:
A plurality of servers, wherein each server has a timing module and a store of timed events each substantially similar to the first store, wherein the first server, the second server, and the plurality of servers comprise a plurality of directory servers configured to operate together, such that one directory server of the plurality of directory servers acts as a primary server with other directory servers and other directory servers of the plurality of directory servers acting as secondary servers, wherein the first timing module is located on the primary server.
7. The system of claim 6 wherein if the primary server fails or is taken off line, then a selected directory server of the other directory servers is nominated to become a new primary directory server such that the selected directory server’s timing module becomes a new primary timing module.
8. The system of claim 6 wherein the first store is configured as a directory with one entry acting as the base entry and a plurality of subordinate entries each corresponding to a different requested event time slot, wherein the first timing module stores each received requested event as a subordinate entry to a subordinate entry of the plurality of subordinate entries according to a requested event time slot.
9. The system of claim 8 wherein each timing module in the directory servers of the plurality of directory servers is configured to receive and process an update to a timed event in the data store and replicate the update to other timing modules in the plurality of directory servers.
10. The system of claim 6 wherein the requesting entity sends a search request related to a timing request, the system further comprising:
A distributed user agent that determines which directory of the plurality of directories has a highest available bandwidth and directs the search request to the directory of the plurality of directories having the highest available bandwidth.
11. The system of claim 1 wherein the requesting entity is associated with a high speed access point in a telecommunication network and wherein the timed event provides a guard timer for call data records prepared by the high speed access point, such that the specified event time corresponds to a waiting time for a mid-call event.
12. A method for timing an event for a requesting entity, comprising:
Receiving a timing request from the requesting entity in a first timing module in a first server;
Associating the timing request with a specified event time;
Storing the timing request in a first store of timed events in the first server;
Directing a second timing module on a second server to store the timing request and the specified event time in a second store of timed events, wherein the first store is substantially similar to the second store; and
Configuring the first timing module and the second timing module such that the requesting entity receives a single notice of the requested event if the specified event time occurs.
13. The method of claim 1, further comprising:
Configuring a plurality of timing modules, each timing module located a server of a plurality of servers and having a store of timed events substantially similar to the first store such that the requesting entity receives a single notice of the requested event if the specified event time occurs.
14. The method of claim 1, further comprising
Configuring the first store as a directory comprising a plurality of timer tick entries, such that each timer tick entry corresponds to a specified time interval, wherein a sum of the specified time intervals corresponds to a maximum event time; and
Storing the timing request in the first store by the first timing module by associating the timing request with a timer tick of the plurality of timer ticks in accordance with the specified event time.
15. The method of claim 1, further comprising:
Accepting a timing cancellation request from the requesting entity by the first timing module;
Deleting the timing request from the first store by the first timing module; and
Directing the second timing module to delete the timing request from the second store.
16. The method of claim 1, further comprising:
Accepting a timing modification request from the requesting entity by the first timing module;
Modifying the timing request in the first store to update the specified event time; and
Directing the second timing module to modify the timing request and the specified event time in the second store.
17. The method of claim 1, further comprising:
Configuring a plurality of servers, including the first server and the second server, to operate together as a plurality of directory servers, wherein each server includes a timing module and a store of timed events, each substantially similar to the first store, and such that one directory server of the plurality of directory servers acts as a primary server with other directory servers and other directory servers of the plurality of directory servers acting as secondary servers, wherein the first timing module is located on the primary server.
18. The method of claim 17, further comprising:
Nominating a selected directory server of the other directory servers to become a new primary directory server if the primary server fails or is taken off line, such that the selected directory server’s timing module becomes a new primary timing module.
19. The method of claim 17, further comprising:
Configuring the first store as a directory with one entry acting as the base entry and a plurality of subordinate entries each corresponding to a different requested event time slot; and
Storing by the first timing module each received requested event as a subordinate entry to a subordinate entry of the plurality of subordinate entries according to a requested event time slot.
20. The method of claim 19, further comprising:
Receiving and processing an update to a timed event in the first store by the timing module; and
Replicating the update to other timing modules in the plurality of directory servers.
21. The method of claim 17 wherein the requesting entity sends a search request related to a timing request, the system further comprising:
Determining by a distributed user agent which directory of the plurality of directories has a highest available bandwidth; and
Directing the search request to the directory of the plurality of directories having the highest available bandwidth.
22. The method of claim 1 wherein the requesting entity is associated with a high speed access point in a telecommunication network and wherein the timed event provides a guard timer for call data records prepared by the high speed access point, such that the specified event time corresponds to a waiting time for a mid-call event.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
What is claimed is:
1. A mold-in fastening member that can be molded into a resin article, which comprises:
a substrate having a front surface and a back surface;
a plurality of engaging elements provided on the front surface;
a plurality of anchoring elements provided on the back surface, the anchoring elements being embedded into the resin article to fix the mold-in fastening member thereto;
a ferrite-containing layer formed on the front surface;
marginal portions continuously extending along respective lengthwise edges of the substrate; and
grooves formed on the substrate, which extend along the respective marginal portions to render the marginal portions easily bending relative to the substrate.
2. The mold-in fastening member according to claim 1, wherein the ferrite-containing layer is formed on the front surface within an area of the engaging elements, and not formed on the marginal portions.
3. The mold-in fastening member according to claim 1, wherein the ferrite-containing layer comprises ferrite particles and a binder resin.
4. The mold-in fastening member according to claim 1, wherein the ferrite-containing layer has a thickness of 0.2 to 2.0 mm.
5. The mold-in fastening member according to claim 1, wherein each of the marginal portions has a width of about 1 to 5 mm.
6. The mold-in fastening member according to claim 1, wherein the grooves are formed on one of the front surface and the back surface.
7. The mold-in fastening member according to claim 6, wherein a depth of the grooves is 50 to 90% of a thickness of the substrate.
8. The mold-in fastening member according to claim 1, wherein the grooves are formed on both the front surface and the back surface.
9. The mold-in fastening member according to claim 8, wherein a total of depths of the grooves on the front surface and the back surface is 50 to 90% of a thickness of the substrate.
10. The mold-in fastening member according to claim 1, wherein the anchoring elements continuously extend along the lengthwise direction of the substrate.
11. A process for producing a mold-in fastening member that can be molded into a resin article, which comprises the steps of:
preparing a fastening tape comprising a substrate having a front surface and a back surface, a plurality of engaging elements provided on the front surface, a plurality of anchoring elements provided on the back surface which are to be embedded into the resin article to fix the mold-in fastening member thereto, marginal portions continuously extending along respective lengthwise edges of the substrate, and grooves which extend along the respective marginal portions to render the marginal portions easily bending relative to the substrate;
applying a ferrite-containing resin liquid to the front surface within an area of the engaging elements by a needle-coating method; and
drying the applied ferrite-containing resin liquid.
12. A process for producing a molded resin article having a fastening member comprising a substrate having a front surface and a back surface, a plurality of engaging elements provided on the front surface, a plurality of anchoring elements provided on the back surface, a ferrite-containing layer formed on the front surface, marginal portions continuously extending along respective lengthwise edges of the substrate and grooves formed on the substrate which extend along the respective marginal portions to render the marginal portions easily bending relative to the substrate, the process comprising the steps of:
fitting the fastening member to a recess formed on a mold so that the engaging elements are received in the recess and the marginal portions are placed on shoulders of the recess to keep the grooves inside the shoulders;
sealing the front surface in the recess by press-contacting the marginal portions with the shoulder by a magnetic attracting force between the ferrite-containing layer and a magnet disposed at the bottom of the recess;
injecting a foaming resin into the mold; and
curing the foaming resin, thereby embedding the anchoring elements into the cured foaming resin.