Author: claimsbot

1. A method for making requests on behalf of a mobile device, the method, comprising:
detecting that a sequence of requests from the mobile device have a reproducible pattern;
replicating the sequence of requests, at an entity distinct from the mobile device using the reproducible pattern;
sending, by the entity, the sequence of requests on behalf of the mobile device to conserve resources at the mobile device;
wherein, responses to the sequence of requests are provided to the mobile device.
2. The method of claim 1, further comprising,
identifying a triggering event which causes initiation of the sequent of requests;
wherein, the sequence of requests occur at predictable time frames relative to the triggering event.
3. The method of claim 2, further comprising,
detecting occurrence of the triggering event at the mobile device;
intercepting requests at the mobile device and preventing the requests from being sent from the mobile device.
4. The method of claim 2, further comprising,
simulating the sequence of events at the entity;
sending, sending, by the entity, the sequence of requests on behalf of the mobile device.
5. The method of claim 3, wherein, the preventing the requests from being sent from the mobile device comprises preventing device radio of the mobile device from being powered on from an off state.
6. The method of claim 1,
wherein, the entity is a proxy server able to communicate wirelessly with the mobile device;
wherein, the proxy server sends the sequence of requests to one or more destinations over a non-cellular connection.
7. The method of claim 6, wherein, the reproducible pattern is detected by the proxy server.
8. The method of claim 6,
wherein, the reproducible pattern is detected by a local proxy on the mobile device and communicated to the proxy server for replication;
wherein, an atomic process is created from the sequence of events.
9. The method of claim 1, wherein, the reproducible pattern is detected from parameters in destination addresses addressed by the sequence of requests.
10. The method of claim 1, wherein, the reproducible pattern in the sequence of requests includes a reproducible timing pattern.
11. The method of claim 1, wherein, the reproducible pattern in the sequence of requests includes a reproducible periodicity pattern.
12. The method of claim 1, wherein, the sequence of requests are directed towards different addressable entities of a server of one application on the mobile device.
13. A method for simulating traffic requests from a mobile device, the method comprising:
predicting that a request is to be made by the mobile device, in advance of the request being sent to a destination by the mobile device;
making the request, at an entity separate from the mobile device, on behalf of the mobile device to the destination.
14. The method of claim 13, wherein, the request is one of a sequence of requests detected as a traffic pattern for an application on the mobile device which is at least partly repeatable.
15. The method of claim 14, wherein, the sequence of requests are directed to different addressable entities identified by different destination addresses at the host server for the application.
16. The method of claim 13,
wherein, the entity further simulates the request and the simulation is based on a traffic pattern of outgoing requests by an application on the mobile device;
wherein, the destination is a host server for the application.
17. The method of claim 13, further comprising, creating or updating an application profile for the application using the traffic pattern.
18. The method of claim 17, further comprising, using the application profile to simulate traffic requests for other mobile devices having the same application.
19. The method of claim 13, further comprising,
detecting sets of traffic patterns of outgoing requests,
wherein, each set is detected for one of multiple applications on the mobile device.
20. The method of claim 19 further comprising,
predicting requests to be made by multiple applications on the mobile device;
making the requests, at the entity separate from the mobile device, on behalf of the mobile device to destinations associated with the multiple applications.
21. The method of claim 13, wherein, prediction of the request is made by a detection of a traffic pattern for prior outgoing requests from the mobile device.
22. The method of claim 21, wherein, the traffic pattern is characterized by timing of the prior out going requests or destination addresses of the prior out going requests.
23. The method of claim 21, further comprising, comparing destination addresses of the prior outgoing requests with one another to identify the traffic pattern.
24. The method of claim 21, wherein, the traffic pattern is identified from parameters in the destination addresses which indicate that the prior outgoing requests are directed to one server.
25. The method of claim 21, wherein, the traffic pattern is identified from parameters in the destination addresses which indicate that the prior outgoing requests are originate from a same application on the mobile device.
26. The method of claim 21, further comprising, comparing destination addresses of the prior outgoing requests for the application with a list of known addresses in identifying the traffic pattern.
27. The method of claim 13, wherein, the predicting includes a prediction of timing or destination address of the request.
28. The method of claim 13, further comprising, preventing the request from being sent by the mobile device for device battery conservation and network resource conservation; wherein, a response to the request sent by the entity on behalf of the mobile device, is sent to the mobile device from the destination.
29. A system for simulating traffic requests from a mobile device, the system comprising:
a proxy server which predicts that a request is to be made by the mobile device, in advance of the request being sent to a destination by the mobile device;
wherein, the proxy server simulates the request and sends the request on behalf of the mobile device to a destination addressed by the request.
30. The system of claim 29,
wherein, the proxy server makes the prediction of the request through detection of a traffic pattern for prior outgoing requests from the mobile device;
wherein, the request is originated by an application on the mobile device;
wherein, the request is one of a sequence of requests detected for the application which is at least partly repeatable.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A plug connector comprising:
a plug connector body having a front portion and a rear portion, the front portion including a first surface and said front portion being sized to fit within a mating receptacle connector, the rear portion having a second surface disposed at a level on the plug connector body that is above the first surface, the connector body further including a ramped surface disposed on said rear portion proximate to said front portion, the ramped surface being inclined at an angle relative to said front portion first surface and extending away from said front portion, said ramped surface having a length that extends at least part way between the level of said front portion first surface and said rear portion second surface;
a latching member including a first end attached to the rear portion and a second end that is cantilevered from the first end thereof, the latching member second end extending over a portion of said rear portion second surface and over a portion of said front portion first surface; and,
an actuator having a first end that protrudes beyond said rear portion and a second end that extends toward said front portion, the actuator second end being interposed between said latching member and said ramped surface, whereby movement of said actuator second end along said ramped surface rearwardly away from said front portion causes said latching member second end to be raised above said front portion first side surface.
2. The connector of claim 1, wherein said actuator second end further includes a lobe which rides against said ramped surface and slides upwardly toward said rear portion second surface as said actuator is pulled in a direction away from said front portion, the upward movement of said lobe causing it to press against said latching member and lift said latching member first end away from said front portion first surface.
3. The plug connector of claim 2, wherein said lobe has a cylindrical configuration which is oriented transverse to said ramped surface.
4. The plug connector of claim 1, wherein said latching member first end includes at least one engagement hook that is capable of extending into an opening in a surface of a opposing mating structure, when said plug connector is inserted into said opposing mating structure.
5. The plug connector of claim 4, wherein said latching member is partially biased against said actuator and said engagement hook thereof is biased toward said front portion first surface.
6. The plug connector of claim 1, wherein said front portion first surface is a top surface thereof and said second portion side surface is a top surface thereof.
7. The plug connector of claim 1, wherein said rear portion includes a channel and said actuator and latching member are disposed in the channel, said channel terminating at one end thereof in a ramped surface that extends toward said front portion.
8. The plug connector of claim 7, wherein said channel is T-shaped including a longitudinal body portion and two wing portions extending transversely to the channel body portion, and said latching member is T-shaped, said latching member including a longitudinal body portion received in said channel body portion and two wing portions, which are received in said channel wing portions, said actuator extending within said channel body portion.
9. The plug connector of claim 8, wherein latching member body portion is offset upwardly with respect to said latching member wing portions to define an intervening space within said channel body portion, said actuator being received within said intervening space.
10. The plug connector of claim 9, wherein said latching member is attached to said connector body rear portion at said latching member wing portions, and said latching member second end is offset downwardly with respect to said latching member body portion.
11. The plug connector of claim 8, wherein said actuator is capable of longitudinal movement in said intervening space and said connector includes means for limiting the longitudinal movement of said actuator on said connector body rear portion.
12. The plug connector of claim 11, wherein said actuator movement limiting means includes a stop member disposed in said channel and said actuator includes an opening formed in said actuator that receives the stop member therein.
13. The plug connector of claim 1, wherein said actuator first end includes a pull tab.
14. The plug connector of claim 13, wherein said pull tab includes a finger opening that may be grasped by a user.
15. A connector comprising:
a connector body having a mating end for mating with an opposing connector and a rear end disposed opposite the mating end, the rear end defining an entry location for a cable containing electrical wires to enter into said connector body, said connector body further including distinct first and second portions. the first portion of the connector body being sized to fit within a receptacle portion of the opposing connector and the second portion of said connector body being larger than said connector body first portion, said connector body second portion including a channel disposed in a top surface thereof and extending in a longitudinal direction between said connector body first portion and said connector body rear end, the channel including an inclined cam surface proximate said connector body first portion;
a latching member having opposing first and second ends interconnected by a longitudinal body portion, the first end including a free end defining an engagement portion that extends over said connector body first portion, the engagement portion including at least one engagement hook for engaging said opposing connector, the latching member second end being attached to the connector body second portion top surface, latching member second end to said connector body portion top surface the attachment permitting said latching member to move between first and second operative positions; and,
an actuator for moving said engagement member engagement portion between said first and second operative positions, the actuator having opposing first and second ends, the actuator first end being interposed between said latching member and said connector body member second portion, said actuator second end extending rearwardly of said connector second portion and including an enlarged section for grasping by a user, said actuator first end including a cam end disposed proximate to said connector body second portion cam surface and between said latching member body portion and said connector body second portion, whereby movement of said actuator by a user in a first direction moves said cam end along said connector body second portion inclined cam surface, and said cam end contacts said latching member, thereby raising said latching member engagement portion in said first direction.
16. The connector of claim 15, wherein said actuator second end enlarged section includes a pull tab with an opening for receiving the finger of a user.
17. The connector of claim 15, wherein said connector body second portion channel receives both said actuator and said engagement member therein.
18. The connector of claim 17, wherein said latching member is T-shaped and said latching member second end includes a pair of wing portions extending transversely outwardly from said latching member body portion, said latching member second end being attached to said connector body second portion at the latching member wing portions.
19. The connector of claim 18, wherein said latching member wing portions are vertically offset form said latching member body portion to define an intervening space between said latching member body portion and a base of said channel.
20. The connector of claim 15, wherein said channel cam surface is angled downwardly from said connector body second portion toward said connector body first portion.
21. The connector of claim 15, wherein said actuator cam end includes a cylindrical portion that extends transversely to said latching member body portion.
22. The connector of claim 15, further including means for limiting movement of said actuator upon said connector body second portion.
23. The connector of claim 22, wherein the actuator movement limiting means includes at least one stop member projecting within said channel and at least one slot formed in said actuator, a length of said slot being longer than a corresponding length of said stop member.
24. The connector of claim 18, wherein said channel is T-shaped and includes a longitudinal body portion and two wing portions extending transversely thereto, said latching member wing portions being received within said channel wing portions.
25. The connector of claim 15, further including a electromagnetic interference (\u201cEMI\u201d) gasket disposed on said connector body first portion, between said latching member engagement portion and said connector body second portion.
26. The connector of claim 15, wherein the EMI gasket is a flexible loop.
27. The connector of claim 15, wherein said engagement portion includes a pair of engagement hooks spaced apart from each other in a direction transverse to said latching member body portion.
28. A cable connector with mating with an opposing connector, comprising:
a connector housing having a mating end for mating to the opposing connector and a rear end, the rear end having an opening disposed therein for receiving at least one electrical wire therein, said rear end being larger than the mating end, said rear end having a channel formed in a top surface thereof, the channel extending longitudinally in the top surface and including an inclined cam surface formed therein,
a T-shaped latch member disposed on said rear end, the latch member including a body portion that is received in said channel and which extends between a latch member latching end and a latch member fixed end, the fixed end including two wing portions that are attached to said connector housing so that the latch member latching end is free to deflect in a vertical direction; and,
an actuator for deflecting said latch member latching member, the actuator including an enlarged free end and a pulling end, the actuator free end being disposed in said channel proximate to said ramped surface and interposed between said latch member and said connector housing, whereby when said actuator is pulled, said actuator free end moves against said an inclined cam surface and said actuator deflects said latch member latching end vertically.
29. The cable connector of claim 28, wherein said actuator pulling end has a hole disposed therein to accommodate a user’s finger.
30. The cable connector of claim 28, wherein said latch member latching end is spaced vertically apart from said latch member fixed end.
31. The cable connector of claim 28, wherein said latch member latching end includes a pair of engagement hooks disposed thereon.
32. The cable connector of claim 28, wherein said actuator pulling end has a hole disposed therein to accommodate a user’s finger.
33. The cable connector of claim 28, wherein said one of said actuator and said channel includes a lug formed therein for engaging a slot formed in the other of said actuator and channel.

1. A readerwriter apparatus for readingwriting data fromto an RFID tag according to an instruction from a host apparatus, comprising:
a tag search instruction receiving unit that receives a tag search instruction from the host apparatus, the tag search instruction including at least one of a data read instruction and a data write instruction on the RFID tag;
a tag identification information requesting unit that transmits to the RFID tag a request for transmission of tag identification information uniquely identifying the RFID tag when the tag search instruction receiving unit receives the tag search instruction; and
a data processing requesting unit that transmits at least one of a data read request and a data write request to the RFID tag identified by the tag identification information based on the at least one of the read instruction and the write instruction when receiving the tag identification information transmitted from the RFID tag in response to the request for transmission transmitted from the tag identification information requesting unit.
2. The readerwriter apparatus according to claim 1, wherein
the tag search instruction includes at least one of a read size of data to be read and a write size of data to be written, and
when the at least one of the read size and the write size included in the tag search instruction exceeds a maximum size of data that allows the at least one of the read request and the write request to include as a request, the data processing requesting unit determines a size equal to or smaller than the maximum size to be a size of data requested by the at least one of the read request and the write request, and transmits to the RFID tag at least one of a read request and a write request for a plurality of pieces of data divided by the determined size.
3. The readerwriter apparatus according to claim 1, wherein
the tag search instruction includes a plurality of pieces of address information indicating a memory area of the RFID tag, the memory area being for the at least one of the data to be read and the data to be written, and
the data processing requesting unit transmits the at least one of the read request and the write request for each piece of address information included in the tag search instruction.
4. A computer-readable recording medium that stores therein a computer program for controlling a readerwriter apparatus for readingwriting data fromto an RFID tag according to an instruction from a host apparatus, the computer program causing a computer to execute:
receiving a tag search instruction from the host apparatus, the tag search instruction including at least one of a data read instruction and a data write instruction on the RFID tag;
transmitting to the RFID tag a request for transmission of tag identification information uniquely identifying the RFID tag when the tag search instruction is received; and
transmitting at least one of a data read request and a data write request to the RFID tag identified by the tag identification information based on the at least one of the read instruction and the write instruction upon reception of the tag identification information transmitted from the RFID tag in response to the request for transmission.
5. A data access system comprising:
a readerwriter apparatus that readswrites data fromto an RFID tag storing therein given data; and
a host apparatus that transmits at least one of a data read instruction and a data write instruction on the RFID tag to the readerwriter apparatus, wherein
the host apparatus comprises
a tag search instruction generating unit that generates a tag search instruction including the at least one of the read instruction and the write instruction; and
a tag search instruction transmitting unit that transmits the tag search instruction generated by the tag search instruction generating unit to the readerwriter apparatus, and

the readerwriter apparatus comprises
a tag search instruction receiving unit that receives the tag search instruction from the host apparatus;
a tag identification information requesting unit that transmits to the RFID tag a request for transmission of tag identification information uniquely identifying the RFID tag when the tag search instruction receiving unit receives the tag search instruction; and
a data processing requesting unit that transmits at least one of a data read request and a data write request to the RFID tag identified by the tag identification information based on the at least one of the read instruction and the write instruction when receiving the tag identification information transmitted from the RFID tag in response to the request for transmission transmitted from the tag identification information requesting unit.
6. A data access control method for controlling a readerwriter apparatus for readingwriting data fromto an RFID tag according to an instruction from a host apparatus, the control method comprising:
generating in the host apparatus a tag search instruction including at least one of a read instruction and a write instruction;
transmitting from the host apparatus the generated tag search instruction to the readerwriter apparatus;
transmitting from the readerwriter apparatus to the RFID tag a request for transmission of tag identification information uniquely identifying the RFID tag when the readerwriter apparatus receives the tag search instruction from the host apparatus; and
transmitting at least one of a data read request and a data write request from the readerwriter apparatus to the RFID tag identified by the tag identification information based on the at least one of the read instruction and the write instruction when the readerwriter apparatus receives the tag identification information transmitted from the RFID tag in response to the transmitted request for transmission.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method of authenticating a user of a terminal referred of as a first terminal, and suitable for communicating with a service provider via a first communications network, the method comprising the steps of the service provider requesting an authentication of the user of the first terminal before providing a service to the first terminal, and the authentication of the user is based on user authentication performed with regard to a second terminal.
2. The authentication method according to claim 1, wherein the first and second terminals are suitable for communicating via the first communications network, said second terminal being suitable for receiving data from the first terminal via a short-range second communications network, and the method comprises the following steps:
the second terminal receiving a request to deliver authentication data from the first terminal via the second network; and
transmitting authentication data from the second terminal via the first network.
3. The authentication method according to claim 2, wherein the request for authentication data issued by the first terminal includes a destination address on the first network to which the authentication data is to be sent.
4. The authentication method according to claim 2, wherein the step of requesting the delivery of authentication data is performed in a request step by the first terminal requesting a transaction identifier from an entity suitable for delivering transaction identifiers, and the data subsequently transmitted includes the transaction identifier.
5. The authentication method according to claim 4, wherein the first terminal is fitted with a signal emitter suitable for conveying data, and the second terminal receives the signals emitted by the emitter and from said emitted data, it extracts data indicating the destination to which the authentication data is to be sent.
6. The authentication method according to claim 5, wherein the signal is a graphic displayed on a screen and the second terminal includes a camera device for capturing the graphic.
7. A terminal suitable for using a service made available by a service provider after authentication, said terminal adapted for receiving a service via a communications network, and comprising means for requesting an authentication based on user authentication performed with regard to another terminal.
8. The terminal according to claim 7, the terminal adapted for communicating with said other terminal via the first network, the terminal also being suitable for transmitting data to said other terminal via a second network, the terminal comprising:
means for requesting authentication data to be provided to another terminal via the second network; and
means for receiving a service via the first network, which service is based on the requested authentication data.
9. The terminal according to claim 8, further comprising means for incorporating a destination address in the request for authentication data, which destination address is on the first network and is to have the authentication data sent thereto.
10. The terminal according to claim 9, further comprising:
means for requesting a transaction identifier from an entity suitable for delivering transaction identifiers; and
means for including said transaction identifier in the request to provide authentication data.
11. A terminal suitable for communicating via at least one communications network and for receiving data via a second network, said terminal comprising:
means for requesting authentication of a user of the terminal; and
means for sending the resulting authentication data to another terminal for authentication purposes.
12. The terminal according to claim 9, said terminal adapted for communicating via at least one communications network and for receiving data from another terminal via a second network, the terminal comprising:
means for receiving a request to provide authentication data coming from another terminal over the second network; and
means for transmitting said authentication data via the first network in order to be used for authenticating the other terminal.
13. The terminal according to claim 12, further comprising means for extracting a destination address on the first network from said request to provide authentication data, and means for sending said authentication data to said destination address.
14. The terminal according to claim 13, further comprising means for extracting a transaction identifier from said request to provide authentication data and means for sending said transaction identifier over the first network.
15. A non-transitory computer program product for being performed on a terminal as defined in claim 7, the program comprising code instructions that, when the program is executed by a processor, perform an authentication step based on means for requesting an authentication based on user authentication performed with regard to another terminal.
16. A non-transitory computer program product for being performed on a terminal as defined in claim 11, the program comprising code instructions that, when the program is executed by a processor, perform a step of authenticating a user of the terminal, and a step of sending the resulting authentication data to another terminal for authentication purposes.