Abstract: A fiber cleaver (100) for cleaving an optical fiber (106). A monobloc fiber handling element (116) defines a pair of spaced apart fiber holding portions (120) each defining an elongated fiber receiving aperture (122) for receiving a respective part of the optical fiber (106) thereinto. The fiber handling element (116) is deformable between open, closed and tensing configurations. In the open configuration, the fiber receiving apertures (122) extend coaxially and the fiber receiving apertures (122) have an open width. In the closed configuration, the fiber receiving apertures (122) have a closed width smaller than the open width. In the tensing configuration, the fiber receiving apertures (122) have the closed width and an inter-aperture distance is larger than in the open and closed configurations. An actuator (104) is operatively coupled to the fiber handling element (116) for moving the latter between the open closed and tensing configurations.

Abstract: A fiber cleaver (100) for cleaving an optical fiber (106). A monobloc fiber handling element (116) defines a pair of spaced apart fiber holding portions (120) each defining an elongated fiber receiving aperture (122) for receiving a respective part of the optical fiber (106) thereinto. The fiber handling element (116) is deformable between open, closed and tensing configurations. In the open configuration, the fiber receiving apertures (122) extend coaxially and the fiber receiving apertures (122) have an open width. In the closed configuration, the fiber receiving apertures (122) have a closed width smaller than the open width. In the tensing configuration, the fiber receiving apertures (122) have the closed width and an inter-aperture distance is larger than in the open and closed configurations. An actuator (104) is operatively coupled to the fiber handling element (116) for moving the latter between the open closed and tensing configurations.

Abstract: A method in a Code Division Multiple Access (CDMA) 2000 packet data network of negotiating reporting mechanisms for accounting records, and sending accounting records from a Packet Data Service Node (PDSN) to an accounting server such as a Home Radius Server utilizing the Radius protocol. The PDSN sends an Access Request (AR) message to the accounting server, via any intermediate nodes, and includes (a) an Accounting Capability (AC) attribute indicating that the PDSN can accumulate a plurality of accounting records and send the accumulated accounting records in a container in a single message, and (b) an Accounting Handling (AH) attribute indicating a plurality of alternative reporting methods that trigger the PDSN to send a container. The Home Radius Server then sends an Access Accept (AA) message to the PDSN that (a) confirms that the Home Radius Server can receive accounting records in containers, and (b) indicates a preferred reporting method for triggering the PDSN to send a container.

Abstract: The invention is a method, a system, and network nodes for charging for services in a data communications network having a User, a Service Provider, an Accounting Manager and an Accounting Storage. When a user wants to access a service, it sends a request to the Accounting Manager that validates the request in order to send a service credential to the User and a user credential to the Service Provider. The User then sends a service request to the Service Provider and the requested service is initiated. When the service is terminated, the Service Provider sends an accounting message to the Accounting Manager that sends the accounting data to the Accounting Storage that stores the data, and, upon reception of an acknowledgement, deletes the data it sent to the Accounting Storage. Also described are the system and the network nodes for carrying out the invention.

Abstract: The invention is a method for software deployment in a data communications network comprising an Initiator, a Service Provider, and a Peer. The Initiator selects a service and sends an interface request related to the service to the Service Provider. The Service Provider authenticates the request and responds with the interface that the Initiator uses to prepare a service request that is sent to the Service Provider. The Service Provider sends an invitation to the Peer that, if it accepts the service, sends an accept service message to the Service Provider that builds the software for the service and distributes it to the Initiator and the Peer that both install the software, and the service is initiated.

Abstract: The invention relates to a solution for prepaid access to an Internet Protocol (IP) network, and particularly a third generation (3G) network. A user has a prepaid account configured in his terminal and in a Prepaid Server (PPS). When the user wants to access the network, an access server requests that the PPS authenticates the terminal and, if accepted, responds with a message informing the access server of how much the terminal can utilise network resources before a re-authentication is necessary. When this limit is met, the access server re-requests authentication until the user disconnects or the account is exhausted, in which case the user is denied further access.