COMMUNICATION BETWEEN THE MOBILE DEVICE AND THE FMA SERVER Sample Clauses

COMMUNICATION BETWEEN THE MOBILE DEVICE AND THE FMA SERVER. All the requests from the user are sent to the FMA server, which implies that the user will need to have an internet connection in order to use the mobile application. All the requests from the mobile device have the same format, regardless of their complexity. This format is the one defined by Eureva (one of the EAGLE technology partners), and is based on Blinkster, the image recognition technology developed by Eureva. All the requests will specify the task to be done (for example, image recognition or login), and will provide the information needed for that task. Most of the text parameters are sent as “Optional Fields”, so that in the future it will be possible to add, delete or modify some fields without changing the structure of the request. For detailed information on the request format, please see the complete description on Appendix 9.1. The response sent to the mobile device also has a defined format, built by the FMA server by processing the data received from the EAGLE server. Therefore, if any modification is done on the structure of the EAGLE items, the mobile application will not be impacted, and there will be no need to publish a new version. The communication between the mobile device and the FMA server is based on SOAP, and each request contains a “request-id”, which is saved by the FMA server in order to build a history of the user actions. If any problem arises during the use of the application, this information will help the system to inform the user of what went wrong and what he should do in order to correct the problem.
Sample 1
AutoNDA by SimpleDocs

Related to COMMUNICATION BETWEEN THE MOBILE DEVICE AND THE FMA SERVER

  • COMMUNICATION BETWEEN YOU AND XXXXX 24.1 Subject to any applicable laws, the Licensee authorised XXXXX to communicate with it by means of telephone, e-mail, fax, text or any mobile phone messaging services to the Licensees mobile device, laptop and/or computer.

  • COMMUNICATION BETWEEN US 12.1 If you wish to contact us in writing, or if any condition in this XXXX requires you to give us notice in writing, you can send this to us by e-mail at xxxxxxxxxxxx@xxxxxxxxxxxx.xx. We will confirm receipt of this by contacting you in writing, normally by e-mail.

  • COMMUNICATION BETWEEN THE PARTIES A copy of all communications relating to the subject matter of this Agreement between the Issuer, the Guarantor and the Noteholders or Couponholders and any of the Paying Agents (other than the Agent) shall be sent to the Agent by the other relevant Paying Agent.

  • COMMUNICATIONS BETWEEN THE PARTIES A copy of all communications relating to the subject matter of this Agreement between the Issuer and any Paying Agent (other than the Agent) shall be sent to the Agent.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Developer and Connecting Transmission Owner Notice Developer and Connecting Transmission Owner shall each notify the other Party, first orally and then in writing, of the release of any Hazardous Substances, any asbestos or lead abatement activities, or any type of remediation activities related to the Large Generating Facility or the Attachment Facilities, each of which may reasonably be expected to affect the other Party. The notifying Party shall: (i) provide the notice as soon as practicable, provided such Party makes a good faith effort to provide the notice no later than twenty-four hours after such Party becomes aware of the occurrence; and (ii) promptly furnish to the other Party copies of any publicly available reports filed with any Governmental Authorities addressing such events.

  • Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.

  • PROHIBITION ON CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT To the extent applicable, Supplier certifies that during the term of this Contract it will comply with applicable requirements of 2 C.F.R. § 200.216.

  • wire Unbundled ISDN Digital Loops These will be provisioned according to industry standards for 2-Wire Basic Rate ISDN services and will come standard with a test point, OC, and a DLR. NewPhone will be responsible for providing BellSouth with a Service Profile Identifier (SPID) associated with a particular ISDN-capable Loop and customer. With the SPID, BellSouth will be able to adequately test the circuit and ensure that it properly supports ISDN service.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!