Re: Free Software Nokia Service Tool V1 .0
Anastacia Iacono
The Nokia OST tool or the Nokia Online Service Tool (OST) is an official firmware flash tool for all Nokia Android devices. OST tool can flash Nokia firmware with .nb0 and .mlf extensions. It lets you update your phone or restore it to stock. You can download the latest Nokia OST Tool 6.3.7, OST LA 6.2.8, 6.0.4, and 6.1.2 below. Please note that the OST works only with Windows 32-bit and 64-bit and is unavailable for macOS and Linux.
Please note that you cannot use the official version of the Nokia OST Tool as it is meant to be used by certified engineers at Nokia service centers. If you use the official tool without patching, you will be prompted to enter a user login and account password. Once you replace the original OnlineUpdateTool.exe and MobileFlashDll.dll with the modified versions, you can use the OST Tool without login credentials like username and password.
The Nokia Service Tool Drivers are a set of drivers developed by Nokia, designed to assist technicians in diagnosing and troubleshooting various Nokia mobile devices. These drivers help to establish a reliable connection between a Nokia mobile device and a computer running the appropriate software.
The drivers are specifically designed for use with Nokia's proprietary tools, which are used by authorized Nokia service centers for device repairs and firmware upgrades. Using these drivers, technicians can perform a wide range of functions on Nokia devices, including flashing new firmware, unlocking network restrictions, and resolving hardware issues.
The Nokia Service Tool Drivers are an essential component for any Nokia repair technician, as they provide the necessary connectivity between devices and software to perform detailed diagnostics and repairs.
II. The appellant requests that the decision under appeal be set aside and a patent be granted on the basis of one of three claim sets (main request, first and second auxiliary requests) filed with a facsimile letter on 30 April 2008.
"1. A method for implementing charging in a telecommunications network which includes provider servers (SP1; S3) for providing services to customers and billing means (BS, BS') for receiving charging records and billing the customers, the customers using customer terminals (CT) connected to the telecommunications network for ordering services, the method comprising the steps of:
- in response to selecting said service, sending a first message to the customer terminal, said first message notifying the customer to make a contract concerning the selected service and including information about charging parameters for the selected service for generating charging records,
- receiving in a separate billing server (WD), after receiving said second message, at least one charging record generated in the customer terminal and associated with the selected service for forwarding said at least one charging record from the billing server to said billing means (BS, BS') for forming a bill."
III. The Board summoned the appellant to oral proceedings, as requested on an auxiliary basis. In an annex to the summons, the Board expressed and substantiated its preliminary opinion that all versions of claim 1 seemed to cover obvious embodiments of a charging method known from D4.
(a) The disclosure of D4, as far as understandable in view of a sketchy presentation and inconsistent terminology, is not relevant to the topic of the invention. While the application is about charging for selected "services", the Metropolitan Area Network (MAN) of D4 charges for data packets (Protocol Data Units, PDUs). Another conceptual difference is that D4 considers the sender, or source, of data to be the customer (i.e. as the party to be billed) whereas the customer according to the application is situated at the terminal which receives the selected service.
(b) Even if taken into consideration, D4 relates to different subject-matter at the implementation level. In particular, D4 does not disclose generation of charging records in a destination terminal. The Figure on page 8.3.3 of D4 may show a destination terminal and an associated Network Access Module which accommodates Charging Management Local Functions to generate and send charging data to the MAN operating system. However, the Network Access Module constitutes a remote network element serving a plurality of destination terminals rather than being dedicated to and integrated with a single terminal. A centralised accounting structure reflects the trend prevailing at the time of D4 (1992) and the application (priority of 1996) because accounting by the network is technically simpler and less expensive than a decentralised accounting structure which requires charging records to be generated in and collected from individual terminals. The skilled person would not shift complexity from a few specialised network elements to numerous cheap terminals. Therefore, D4 does not imply that the Network Access Module of page 8.3.3 might be an enhanced component (such as a modem) of a PC, for example.
(c) The claimed features have to be taken as a whole to evaluate their synergy. It is true that the exchange of contracting messages entails commercial aspects; the customer's contract is established with the billing server rather than with a provider server, thus allowing the customer to conclude ad hoc contracts with the billing server instead of having long-term contracts with multiple providers. However, considerable technical effects are also achieved: signalling traffic in the network is reduced, and the provider servers can operate with smaller databases.
(d) Regarding the amendment by the first auxiliary request, it may be generally known to charge network users for the content of a selected service rather than for individual data packets representing the service (D4). However, the explicit reference to content corroborates the conceptual difference of the claimed method over the teaching of D4 and, thus, helps to demonstrate that D4 is not a realistic starting point for an obviousness objection.
(e) The additional amendment by the second auxiliary request completes a package of features which enables reliable charge data records to be generated in the customer terminals. Since the invention delegates some accounting power from the network to potentially insecure customer terminals, digital signatures advantageously help to restore security and, while known as such, represent an efficient tool to safeguard the integrity and authenticity of charge data records to be sent to the billing server.
1.1 The application relates to a method and system for charging for services provided over a telecommunications network. While using an existing billing infrastructure (A1, page 4, lines 5 to 8 and lines 24/25), the method is supposed to eliminate a number of drawbacks mentioned in the application (page 3, last paragraph). The statement of grounds of appeal defines a more general objective problem: providing an "alternative solution" to charging for a selected service.
1.2 The thrust of the application is for a charging concept in which a separate billing server "negotiates an on-line contract with the customer" for the service selected, and the customer terminal measures its own receipt of services, generates charge data records and sends them to the billing server (A1, page 4, lines 11 to 23). The separate billing server may be handled by a billing service provider who is a separate organisational unit (A1, page 7, last paragraph).
1.3 Regarding the effects achieved, the application mentions a number of advantages: easy implementation, data security, easy market access for new service providers, customer's control of the billing process, compatibility with other payment methods, suitability for wireless networks, independence from data transfer protocols (A1, page 4, line 24 to page 5, line 13). Those advantages mirror the drawbacks to be overcome.
While the appellant has argued that the inventors' starting point and mindset were quite different from a Metropolitan Area Network described in D4, the Board considers this prior art to be highly relevant on an objective basis as can be seen from the following discussion.
2.1 D4, in particular the overview on page 8.3.3, describes charging and tariffing functions in Metropolitan Area Networks (MANs). D4 is not a patent specification but a scientific paper outlining principles in general language rather than in terms of technical implementation. However, D4 does disclose that each source of user data (corresponding to a provider server) is linked to the MAN via a Network Access Module, and another Network Access Module is arranged between the MAN and each destination of user data.
Measurements for charging purposes are taken at the source (see page 8.3.3, penultimate paragraph). Details are presented on page 8.3.4 which also implies a definition of the word "customer": "additional measurements are necessary to determine the amount of traffic delivered to the customer" (3rd paragraph from the bottom). In other words, D4 contemplates that the customer may be the recipient of the data transmission. (In practice, the recipient is the service provider's customer, and the service provider may be the network provider's customer.)
The flow of data packets (Protocol Data Units, PDUs) is measured (for charging purposes) "at the destination", and charging records are kept in the network "at the destination side" (see page 8.3.3, last paragraph). A prominent advantage of this option is that only data packets which reach the destination are charged for (D4, page 8.3.3, last paragraph, and page 8.3.5). In other words, the recipient of the data controls the initial part of the billing process (an effect also sought by A1, see page 4, last paragraph, and original claim 26).
More specifically, the second option of D4 is based on "Charging Management Local Functions" in the Network Access Module associated with the destination. For billing purposes, that module sends charging data to the MAN Operating System. The charging data may represent a summary of the measured data packets (see page 8.3.2, third bullet: "Need for near-real-time summarization procedures"); due to the huge volume of charging data, "some form of near-real-time elaboration is needed" (page 8.3.2, penultimate paragraph). Typical details of a charging data record are set out in D4, page 8.3.8 (centre part).
7fc3f7cf58