1461121136-3bac93c8-e81c-4b00-b2b4-5db101a383d2

1. A method of operating a mobile phone telecommunications network, comprising the steps of:
using a servicing mobile switching center (servicing MSC) of the network to receive at least one short message service (SMS) text message and to generate a mobile application part (MAP) message as a result of reception of the SMS text message;
transmitting the MAP message from the servicing MSC to at least one service control point (SCP) of the network;
implementing the SCP in the network as a single network element;
operating the SCP to process the MAP message by determining a subsequent handling of the at least one SMS text message and by interrogating the MAP message to obtain information from the MAP message about a sender of the SMS text message and to determine whether or not there is sufficient credit on an account of the sender to allow sending of the at least one SMS text message onwards towards an intended receiver; and
using the information in determining the subsequent handling of the at least one SMS text message, wherein if processing of the MAP message by the SCP determines that the MAP message should be sent onwards towards the intended receiver, then the SCP sends the MAP message onwards towards the receiver by sending it directly to a networking mobile switching center (networking MSC).
2. The method according to claim 1, in that the servicing MSC receives the at least one SMS text message from a mobile phone.
3. The method according to claim 1, in that the MAP message generated by the servicing MSC contains information about the at least one SMS text message received by the servicing MSC.
4. The method according to claim 1, in that the MAP message generated by the servicing MSC contains at least part of the at least one SMS text message received by the servicing MSC.
5. The method according to claim 1, in that processing of the MAP message by the SCP comprises the step of determining whether or not the MAP message should be sent onwards towards the intended receiver.
6. The method according to claim 1, in that the information comprises details of an identity of the sender of the at least one SMS text message received by the servicing MSC, and is used in determining whether or not SMS text messages from the sender should be sent onwards towards the intended receiver.
7. The method according to claim 1, in that when processing of the MAP message by the SCP comprises determining that the MAP message should not be sent onwards towards the intended receiver, the SCP discards the MAP message.
8. The method according to claim 1, in that the SCP changes a destination address of the MAP message to send it onwards towards the receiver.
9. The method according to claim 1, in that processing of the MAP message by the SCP comprises the step of charging the sender of the at least one SMS text message received by the servicing MSC.
10. The method according to claim 9, in that processing of the MAP message by the SCP comprises the step of charging the sender of the at least one SMS text message received by the servicing MSC if the MAP message is sent onwards towards the intended receiver.
11. The method according to claim 9, in that processing of the MAP message by the SCP comprises the step of charging the sender of the at least one SMS text message received by the servicing MSC before the MAP message is sent onwards towards the intended receiver.
12. The method according to claim 9, in that the step of using the information is performed by charging the sender of the at least one SMS text message received by the servicing MSC.
13. The method according to claim 12, in that the information comprises details of an identity of the sender of the at least one SMS text message received by the servicing MSC, and is used to access the account of the sender and to charge the sender.
14. The method according to claim 12, in that the information comprises details of a length of the MAP message, and is used to charge the sender.
15. The method according to claim 1, in that processing of the MAP message by the SCP comprises the step of triggering dispatch of a message to the sender of the at least one SMS text message received by the servicing MSC.
16. The method according to claim 15, in that the step of using the information is performed by triggering dispatch of the message to the sender of the at least one SMS text message received by the servicing MSC.
17. The method according to claim 16, in that the information comprises details of an identity of the sender of the at least one SMS text message received by the servicing MSC, and is used to access the account of the sender to determine a credit available, and to trigger dispatch of a message to the sender if the credit is insufficient to allow sending of the message onwards towards the intended receiver.
18. The method according to claim 1, in that processing of the MAP message by the SCP comprises the step of analyzing the MAP message.
19. The method according to claim 1, in that the SCP provides at least one service logic program (SLP) defining at least one process carried out by the SCP.
20. The method according to claim 19, in that processing of the MAP message by the SCP comprises the step of running the at least one SLP.
21. The method according to claim 1, in that the MAP message received by the SCP comprises an SMS text MAP message which is generated by the servicing MSC as a result of receipt of an SMS text message.
22. The method according to claim 21, in that the SCP provides at least one SMS SLP which defines the at least one process carried out by the SCP on the SMS text MAP message.
23. The method according to claim 22, in that processing of the SMS text MAP message by the SCP comprises the step of running at least one SMS SLP.
24. A mobile phone telecommunications network, comprising:
a servicing mobile switching center (servicing MSC) having a message receiver;
a mobile application part (MAP) message generator;
a MAP message transmitter; and
at least one service control point (SCP) implemented as a single network element and having a MAP message receiver and a MAP message processor, the message receiver of the servicing MSC receiving at least one short message service (SMS) text message and the MAP message generator of the servicing MSC generates a MAP message as a result of reception of the SMS text message, and the MAP message transmitter of the servicing MSC sends this to the MAP message receiver of the SCP, the MAP message receiver of the SCP receiving the MAP message, and the MAP message processor of the SCP processing the MAP message by determining whether or not the at least one SMS text message should be sent onwards towards an intended receiver by interrogating the MAP message to obtain information from the MAP message about a sender of the SMS text message and to determine whether or not there is sufficient credit on an account of the sender to allow sending of the at least one SMS text message onwards towards an intended receiver, and by using the information in determining the subsequent handling of the at least one SMS text message, wherein if processing of the MAP message by the SCP determines that the MAP message should be sent onwards towards the intended receiver, then the SCP sends the MAP message onwards towards the receiver by sending it directly to a networking mobile switching center (networking MSC).
25. A service control point (SCP) implemented as a single network element, comprising:
a receiver for receiving at least one mobile application part (MAP) message generated as a result of reception of a short message service (SMS) text message; and
a processor for processing the MAP message by determining whether or not the SMS text message should be sent onwards towards an intended receiver by interrogating the MAP message to obtain information from the MAP message about a sender of the SMS text message and to determine whether or not there is sufficient credit on an account of the sender to allow sending of the at least one SMS text message onwards towards an intended receiver, and by using the information in determining the subsequent handling of the SMS text message, wherein if processing of the MAP message by the SCP determines that the MAP message should be sent onwards towards the intended receiver, then the SCP sends the MAP message onwards towards the receiver by sending it directly to a networking mobile switching center (networking MSC).
26. The SCP according to claim 25, in that the SCP processor provides or accesses software for processing the MAP message.
27. The SCP according to claim 26, in that the processing software comprises at least one service logic program (SLP).
28. The SCP according to claim 27, in that processing of the at least one MAP message by the SCP processor of the SCP comprises running the at least one SLP.
29. The SCP according to claim 27, in that the processing software comprises at least one SMS SLP which defines at least one process carried out by the SCP processor of the SCP on SMS text MAP messages.
30. The SCP according to claim 29, in that processing of the SMS text MAP message by the SCP processor of the SCP comprises running at least one SMS SLP.

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 hydraulic pressure control apparatus comprising:
hydraulic pressure control member which adjusts or switches hydraulic pressure of fluid applied to an object to be controlled;
an upper case and a lower case that receive the hydraulic pressure control member and have an inside wall for forming a passage for the fluid; and
a plate member interposed between the upper case and the lower case, the plate member being made of non-porous material and having a plurality of through holes to define a filter that filters the fluid flowing through the passage,
the upper case and the lower case cooperating with the plate member in forming the passage for the fluid,
wherein the plate member includes at least one communication hole for forming the passage for the fluid in cooperation with the upper case and the lower case, and
wherein said communication hole has a diameter greater than a diameter of a said through hole.
2. A hydraulic pressure control apparatus according to claim 1, wherein the hydraulic pressure control member has an actuator that receives the hydraulic pressure of a working fluid as a supply pressure and operates in response to a switching control signal to output a control pressure, and wherein the filter is provided directly on the upstream side of the actuator.
3. A hydraulic pressure control apparatus according to claim 2, wherein the hydraulic pressure control member has a valve that is operated by the control pressure outputted by the actuator to control the supply or discharge of the hydraulic pressure applied to the object to be controlled.
4. A hydraulic pressure control apparatus according to claim 1, further comprising a magnet that is provided on the inside wall of the passage on the upstream side of the filter.
5. A hydraulic pressure control apparatus according to claim 1, wherein the plurality of through holes are formed in the plate member by a laser.
6. A hydraulic pressure control apparatus according to claim 1, wherein the through holes have a diameter of 0.002 mm to 0.2 mm.
7. A hydraulic pressure control apparatus comprising:
hydraulic pressure control member which adjusts or switches hydraulic pressure of fluid applied to an object to be controlled;
an upper case and a lower case that receive the hydraulic pressure control member and have an inside wall for forming a passage for the fluid; and
a plate member interposed between the upper case and the lower case, the plate member being made of non-porous material and having a plurality of through holes to define a filter that filters the fluid flowing through the passage,
the upper case and the lower case cooperating with the plate member in forming the passage for the fluid,
wherein the plate member includes at least one communication hole for forming the passage for the fluid in cooperation with the upper case and the lower case, and
wherein said communication hole has a diameter substantially corresponding to a diameter of said passage as defined in at least one of said upper case and said lower case.

1461121126-ec0459f9-07bb-4f01-a412-09ff571b87de

1. An electrical device comprising:
a control unit; and
a near field communication device connected to the control unit.
2. The electrical device according to claim 1, further comprising:
a housing having an inner surface and an outer surface, the near field communication device being positioned on the inner surface, a marker being arranged on the outer surface at a location where the near field communication device is positioned on the inner surface.
3. The electrical device according to claim 1, wherein:
the electrical device is an energy storage module for a hand power tool, the energy storage module having an energy store; and
the control unit is configured to (i) record status parameters from the energy store and (ii) make the status parameters available for reading via the near field communication device.
4. The electrical device according to claim 1, wherein:
the electrical device is a power tool; and
the control unit is configured to at least one of:
record status parameters from the power tool and make the status parameters available for reading via the near field communication device;
receive operating parameters via the near field communication device and control the power tool according to the operating parameters.
5. The electrical device according to claim 1, wherein at least one of the near field communication device and the control unit are connected to a memory that is readable and writtable.
6. The electrical device according to claim 1, wherein the near field communication device is configured to read an NFC tag.
7. An electrical device system comprising:
at least one electrical device having a control unit and a near field communication device connected to the control unit; and
a readwrite device configured to use near field communication to at least one one of (i) send data to the near field communication device and (ii) receive data from the near field communication device.
8. The electrical device system according to claim 7, wherein the readwrite device has a remote communication device.
9. The electrical device system according to claim 7, wherein the readwrite device is a mobile phone.
10. A electrical device system comprising:
an electrical device having a control unit and a near field communication device connected to the control unit, the near field communication device being configured to read an NFC tag; and
a plurality of NFC tags, each NFC tag of the plurality of NFC tags having a readable memory configured to store different operating parameters for the electrical device.
11. The electrical device system of claim 7, wherein the readwrite device is configured to display at least one of (i) the sent data and (ii) the received data.

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. An apparatus comprising:
a first logic configured to determine an identifier associated with a packet and a flow count index associated with the identifier;
a flow counter coupled to the first logic and configured to count a number of flows associated with the flow count index, wherein the flow counter comprises one or more flow count indices associated with one or more identifiers and flow counts corresponding to respective one or more flow count indices;
a second logic, coupled to the first logic and the flow counter, wherein the second logic is configured to analyze the packet to determine if the packet is a part of a new flow that has not been counted in the flow counter, and increment the flow counter if the packet is part of a new flow;
wherein the second logic increments the flow counter by incrementing a flow count corresponding to the flow count index associated with the identifier;
a flow table coupled to the second logic and comprising stored statistics on packets, wherein said packets are sampled at a flow sampling rate determined by a priority is bound to a source identifier of the packet;
wherein the flow sampling rate causes a greater number of statistics to be stored for a high-priority source than for a lower priority source.
2. The apparatus of claim 1, wherein flows are a stream of packets between a particular source and a particular destination and characterized by a specific set of parameters.
3. The apparatus of claim 2, wherein the set of parameters comprises IP protocol type, IP type of service, input logical interface.
4. The apparatus in claim 1, wherein the second logic is further configured to:
determine whether the flow count has exceeded a threshold;
update a statistic for the first packet in the flow table when the flow count has not exceeded the threshold;
trigger an event when the flow count has exceeded the threshold.
5. The apparatus in claim 4 wherein the second logic is further configured to reset the flow count.
6. The apparatus in claim 4 wherein the event comprises not updating a statistic for the packet in the flow table and passing the packet.
7. The apparatus in claim 4 wherein the event comprises dropping the packet.
8. The apparatus in claim 7, further comprising a drop counter that is configured to count the number of packets dropped.
9. The apparatus of claim 1, wherein the identifier is configurable.
10. The apparatus in claim 1 wherein the identifier is an internet protocol address of the source of the packet.
11. The apparatus in claim 1 wherein the flow counter is a hash table in the first logic.
12. The apparatus of claim 1,
wherein the second logic is configured to sample packets of a first flow at a first sampling rate based on a first source identifier of a packet associated with the first flow;
wherein the second logic is configured to sample packets of a second flow at a second sampling rate based on a second source identifier of a packet associated with the second flow;
wherein the first sampling rate is different than the second sampling rate.
13. A method comprising the computer-implemented steps of:
determining an identifier associated with a packet and a flow count index associated with the identifier;
identifying a flow counter that indicates a number of flows associated with the flow count index, wherein the flow counter comprises one or more flow count indices associated with one or more identifiers and flow counts corresponding to respective one or more flow count indices;
analyzing the packet to determine when the packet is a part of a new flow that has not been counted in the flow counter;
incrementing the flow counter when the packet is part of a new flow;
wherein incrementing the flow counter comprises incrementing the flow counts corresponding to the one or more flow count indices associated with the identifier;
storing statistics on packets, wherein the packets are sampled at a flow sampling rate determined by a priority that is bound to a source identifier of the packet;
wherein the flow sampling rate causes a greater number of statistics to be stored for a high-priority source than for a lower priority source;
wherein the method is performed by one or more computing devices.
14. The method of claim 13, wherein determining an identifier associated with a packet is performed in one or more electronic circuits.
15. The method of claim 13, where the identifier identifies a group of source devices from which the packet originated.
16. The method of claim 13, further comprising the computer-implemented steps of:
determining whether the number of flows associated with the identifier has exceeded a threshold;
updating a statistic for the packet when the number of flows has not exceeded the threshold;
triggering an event when the number of flows has exceeded the threshold.
17. The method of claim 16, wherein the event comprises dropping the packet.
18. The method of claim 17, further comprising storing statistics of the dropped packet.
19. The method of claim 13, further comprising:
sampling packets of a first flow at a first sampling rate based on a first source identifier of a packet associated with the first flow;
sampling packets of a second flow at a second sampling rate based on a second source identifier of a packet associated with the second flow;
wherein the first sampling rate is different than the second sampling rate.
20. A system comprising:
means for determining an identifier associated with a packet;
means for determining a flow count index associated with the identifier;
means for identifying a flow counter that indicates a number of flows associated with the flow count index, wherein the flow counter comprises one or more flow count indices associated with one or more identifiers and flow counts corresponding to respective one or more flow count indices;
means for analyzing the packet to determine when the packet is a part of a new flow that has not been counted in the flow counter;
means for incrementing the flow counter when the packet is part of a new flow;
wherein incrementing the flow counter comprises incrementing the flow counts corresponding to the one or more flow count indices associated with the identifier;
means for storing statistics on packets, wherein the packets are sampled at a flow sampling rate determined by a priority that is bound to a source identifier of the packet;
wherein the flow sampling rate causes a greater number of statistics to be stored for a high-priority source than for a lower priority source.
21. The system of claim 20, wherein the means for determining an identifier associated with a packet comprises one or more electronic circuits.
22. The system of claim 20, wherein the identifier identifies a group of source devices from which the packet originated.
23. The system of claim 20, further comprising:
means for determining whether the number of flows associated with the identifier has exceeded a threshold;
means for updating a statistic for the packet when the number of flows has not exceeded the threshold;
means for triggering an event when the number of flows has exceeded the threshold.
24. The system of claim 23, wherein the event comprises dropping the packet.
25. The system of claim 24, further comprising means for storing statistics of the dropped packet.