Prima facie case
31 I will start by considering whether UbiPark has established a prima facie case in relation to its claim for a final injunction to restrain TMA from making threats of infringement proceedings. In considering whether UbiPark has a prima facie case, it is necessary to take into account the partial reverse onus that will apply at trial, namely that it will be for TMA to establish that UbiPark's technology, in particular the UbiPark App, infringes the 335 Patent.
32 Claim 1 of the 335 Patent (with added numbering, for ease of reference) is in the following terms:
A system including:
(1) a communication system; and
(2) a computer program executable by a mobile communication device associated with an entity, the entity being a user which is associated with a vehicle for parking within a restricted area, the restricted area being a vehicular parking area, wherein the mobile communication device is configured to:
(a) receive one or more entry signals from the communication system when the entity approaches an entry point of a restricted area;
(b) determine a received signal strength of the one or more entry signals;
(c) determine if one or more entry criteria have been satisfied based on the received signal strength of the one or more entry signals in order to generate and transfer an entry request;
(d) in response to the one or more entry criteria being satisfied, generate and transfer, to the communication system, the entry request;
(e) receive, from the communication system, authorisation data indicative of the entity being granted access to enter the restricted area by an access control system;
(f) receive one or more exit signals from the communication system when the entity approaches an exit point of the restricted area;
(g) determine a received signal strength of the one or more exit signals;
(h) determine if one or more exit criteria have been satisfied based on the received signal strength of the one or more exit signals in order to generate and transfer an exit request; and
(i) in response to the one or more exit criteria being satisfied, generate and transfer, to the communication system the exit request indicative of the authorisation data in order to exit the restricted area.
33 For the purposes of the interlocutory injunction application, UbiPark is prepared to assume that its system satisfies the integers in paragraphs (2)(a) and (b) of claim 1. UbiPark contends, however, that the integers in paragraphs (2)(c) and (d) are not present in its system (putting to one side the configuration of its system used or proposed to be used at Perth Airport).
34 Before setting out UbiPark's contentions regarding paragraphs (2)(c) and (d) of claim 1, I note that UbiPark submits that claim 1 is directed to a solution, as described in the specification to the 335 Patent, that allows a user to have the carpark barrier open automatically when their car is located in the correct position at the carpark barrier, without the user having to do anything. UbiPark submits that that solution is based on assessing the strength of the entry signal, and using that to infer the location of the user's vehicle, and hence when to transmit an entry request to the system so that the barrier can be opened.
35 UbiPark submits that that is also the approach that TMA uses for its commercial product, ZipBy, which it launched soon after filing the priority document for the 335 Patent. UbiPark submits that that is not the approach taken by UbiPark's system.
36 UbiPark contends that its system does not have the integers in paragraphs (2)(c) and (d) of claim 1.
37 Paragraph 2(c) requires the mobile communication device (that is, the user's smartphone) to be configured to determine if one or more "entry criteria" have been satisfied "based on the received signal strength" of the one or more entry signals in order to generate and transfer an entry request.
38 While UbiPark accepts that the UbiPark App determines and records the signal strength for each Bluetooth signal that it identifies and receives, UbiPark contends that what the UbiPark App does not do is to determine whether any entry criterion is satisfied based on that determination of received signal strength (putting the Perth Airport configuration to one side). UbiPark relies on the evidence of Mr Van De Camp as to how its system works. Mr Van De Camp states at paragraphs 47-51 of his affidavit that, while the UbiPark App measures and records the signal power for each Bluetooth signal that it receives, the UbiPark App "does not do anything with that information that is relevant to the operation of the App" (putting the Perth Airport configuration to one side). Mr Van De Camp also states, for the sake of clarity, that the UbiPark system "does not determine whether a user can enter, or exit, a car park by reference to the measured signal power for the Bluetooth signal". Accordingly, UbiPark submits, the integer in paragraph (2)(c) is not present in its system.
39 Paragraph (2)(d) requires the mobile communication device (that is, the user's smartphone) to be configured to, "in response to" to the one or more entry criteria being satisfied, generate and transfer to the communication system the entry request.
40 UbiPark contends that, even if it be assumed that the message that the UbiPark App sends to the UbiPark server when the user presses the button on the screen is an "entry request", that entry request is sent "in response to" the user pressing the button on the App; it is not sent "in response to" the App receiving the Universally Unique Identifier (UUID) for the Bluetooth beacon. Again, UbiPark relies on the evidence of Mr Van De Camp as to how the UbiPark system works. At paragraphs 26-30 of his affidavit, Mr Van De Camp refers to the user pressing the entry button for the carpark on the carpark entry message screen. Accordingly, UbiPark contends, the integer in paragraph (2)(d) is not present in its system.
41 I will now refer to TMA's contentions in response, which rely on the independent expert evidence of Mr Sizer.
42 TMA contends that UbiPark's case is premised on an incorrect interpretation of the concept of receiving a signal. TMA contends, on the basis of Mr Sizer's evidence, that Bluetooth signals may be received by a smartphone, even if their signal strength is too low to allow them to be correctly decoded (and the UUID for the beacon ascertained): see, eg, Mr Sizer's second report at paragraph 8.1.3.
43 Further, TMA contends that each of UbiPark's two non-infringement contentions is incorrect, relying on the evidence in Mr Sizer's reports.
44 Mr Sizer addresses the integer in paragraph (2)(c) of claim 1 in row 11 of Annex A to his first report. Mr Sizer expresses the view that this feature of claim 1 is present in the UbiPark system. He states that the mobile communication device (that is, the smartphone) "determines that an entry criterion, being the reception of identifiable Bluetooth signals from an entry beacon, is satisfied by the received signal strength being sufficient to allow the beacon's Bluetooth messages to be correctly decoded". In Mr Sizer's view, that criterion needs to be satisfied in order for the mobile communication device to generate and transfer an entry request.
45 Mr Sizer addresses the integer in paragraph (2)(d) of claim 1 in row 12 of Annex A to his first report. He expresses the view that this feature of claim 1 is present in the UbiPark system. Mr Sizer refers back to his response to the integer in paragraph (2)(c). He also states that: after the user presses the "Open Lane X" button, the smartphone communicates to the server the request to open the boom gate before which their vehicle is located; this communication from the smartphone to the server requesting opening of the boom gate is an entry request sent to the server from the smartphone via the communication system; the App sends a communication message to the server, advising it of the fact that it has received the beacon's signal; this communication from the smartphone also constitutes an entry request.
46 As is apparent from the above, even though UbiPark focuses its contentions on paragraphs (2)(c) and (d) of claim 1, there is an issue between the parties as to the concept of receiving an entry signal in paragraph (2)(a). This issue appears to be contextually relevant in considering the competing contentions of the parties as to paragraphs (2)(c) and (d). In brief outline, UbiPark contends that a smartphone only "receives" an entry signal from a Bluetooth beacon when the signal is sufficiently strong that the smartphone can decode it. On the other hand, TMA contends that a smartphone "receives" an entry signal from a Bluetooth beacon whenever a signal is received, whether or not the smartphone can decode it. The difference between the parties appears to be largely one of construction of the patent, rather than a different view as to the relevant science. It appears to me that both constructions are plausible. I do not consider it necessary or appropriate to go beyond this at this stage.
47 In relation to paragraph (2)(c) of claim 1, the difference between the parties can be summarised as follows. UbiPark contends that, under its system, the smartphone does not do anything with the signal strength data that it receives. Accordingly, UbiPark contends, the smartphone does not determine if one or more "entry criteria" have been satisfied "based on the received signal strength" of the one or more entry signals (from the Bluetooth beacon). TMA, on the other hand, contends that, under the UbiPark system, one of the entry criteria is the receipt (and continued receipt) of a signal from the Bluetooth beacon that is of sufficient strength to be decoded. Accordingly, TMA contends, the smartphone does determine if one or more "entry criteria" have been satisfied "based on the received signal strength" of the one or more entry signals. It seems to me that this is largely an issue of construction of the patent, as distinct from a dispute as to the relevant science or the facts. In my view, each party's construction has merit and could succeed at trial.
48 In relation to paragraph (2)(d) of claim 1, the difference between the parties can be summarised as follows. UbiPark contends that, under its system, the entry request is generated and transferred in response to the user pressing the button on the relevant screen on the UbiPark App on their smartphone; the entry request is not generated and transferred in response to the one or more entry criteria being satisfied. TMA's contentions in relation to paragraph (2)(d) overlap with its contentions about paragraph (2)(c). TMA contends that one of the entry criteria is the receipt (and continued receipt) of a signal from a Bluetooth beacon of sufficient strength to be decoded. TMA contends that, under the UbiPark system, the generation and transfer of an entry request depends upon continued satisfaction of that criterion. Again, it seems to me that the issue is largely one of construction of the patent. In my view, each party's construction has merit and could succeed at trial.
49 In light of the above, UbiPark has established that it has a prima facie case in relation to its claim for a final injunction pursuant to s 128(1) of the Patents Act to restrain TMA from threatening infringement proceedings against UbiPark and its customers.
50 Insofar as the configuration of UbiPark's system at Perth Airport is concerned, while it may be accepted that UbiPark's non-infringement contentions regarding paragraphs (2)(c) and (d) of claim 1 may not be available in respect of that configuration, as noted above, UbiPark proposes a carve out from any interlocutory injunction to address any potential use of such a configuration.