Commands. Commands or parameters you directly submit into the Services or that you direct us to submit on your behalf that are transmitted to a Monitor to assist you in monitoring and/or managing certain Patient’s Devices. Commands are not Data. Data. Patient data or information collected from a Device through a Monitor and uploaded to the Services and data submitted by you through the Services. Device. Any implanted cardiac device compatible with Xxxxxx.xxx™ PCN that is obtained from us or any of our subsidiaries or affiliates. Heightened Cybersecurity Requirements. All applicable laws, rules, regulations, directives and governmental requirements, and national standards, or industry or public authority schemes and sanctions, which are applicable to you or your Users relating to the security of network and information systems and security breach and incident reporting requirements, in particular the Cybersecurity Directive ((EU) 2016/1148), Commission Implementing Regulation ((EU) 2018/151), or applicable national implementing legislation, the Network and Information Systems Regulations 2018 (SI 506/2018), all as amended or updated from time to time. Locations. Any place where you receive the Services or where the Services are performed. For example, “your Locations” include the clinical sites where Patients are treated. “Our Locations” include our facilities or other places where we perform the Services.
Commands. START: At any time, you can text START to the long code +00-0000000000 to obtain additional information. STOP: At any time, you can text STOP to the long code +00-0000000000. This will prevent you from receiving any future Head Digital Works Private Limited SMS Alerts, following the confirmation message(s) described above in the "What if I don't want to receive any more service messages?" section. How are the messages sent? Privacy Notice
Commands. Commands or parameters you directly submit into the Services or that you direct us to submit on your behalf that are transmitted to a Monitor to assist you in monitoring and/or managing certain Patient’s Devices. Commands are not Data. Data Protection Laws. All applicable laws, regulations, directives and governmental requirements relating in any way to the privacy, confidentiality, security, integrity and protection of personal data, as amended or superseded from time to time, and any related national implementing legislation. Data. Patient data or information collected from a Device through a Monitor and uploaded to the Services and data submitted by you through the Services. Device. Any implanted cardiac device compatible with Xxxxxx.xxx™ PCN that is obtained from us or any of our subsidiaries or affiliates. Locations. Any place where you receive the Services or where the Services are performed. For example, “your Locations” include the clinical sites where Patients are treated. “Our Locations” include our facilities or other places where we perform the Services.
Commands. 3.1 The Customer is required to quote anyone or more of the login credentials and any other identifiers as shall be prescribed by the Bank from time to time in order to log-on to the Service and give Commands to the Bank Online. Commands in connection with the Service shall not be considered to be received by the Bank unless they are given in such manner as the Bank may prescribe from time to time and until the Bank has actually received them. The Bank will only accept a Command if it has been effected through the Service using an appropriate login credentials and any other identifiers in accordance with these Terms and Conditions.
3.2 The Customer requests and authorizes the Bank to treat all apparently valid Commands received by the Bank as commands properly authorized by the Customer, even if they conflict with the terms of any other mandates given by the Customer at any time concerning the Customer's Accounts or affairs. Subject to the Bank's obligations in Clause 3.1 above, the Bank shall be under no other obligation to check the authenticity of Commands or the authority of the person(s) giving them.
3.3 The Customer is responsible for the accuracy and completeness of Commands and for ensuring that they will achieve the Customer's intended purpose. The Bank is not liable for any loss or delay where the contents of a Command are inaccurate or incomplete nor the Bank shall be responsible or liable for acting in good faith upon a Command and the Customer shall indemnify the Bank for any loss, damage or expense the Bank may incur as a result thereof.
3.4 Any Command given in connection with the Service by quoting the login credentials and such other identifiers of the Customer as prescribed by the Bank, once given, may not be rescinded or withdrawn without the consent of the Bank. All such Commands given, as understood and acted on by the Bank in good faith, shall be irrevocable and binding on the Customer whether given by the Customer or by any other person purporting to be the Customer.
3.5 In the event that the Customer requests the Bank to cancel or modify any Command, the Bank will make all reasonable efforts to comply with the Customer's request. However, the Bank is not liable for any failure to cancel or modify the Command if such a request is received at a time or under circumstances that renders the Bank unable to comply with the Customer's request.
3.6 The Bank is entitled to debit the Customer's Accounts, wherever they are situated and whenever they ...
Commands. The DB-0 Interface between S-CSC and HSS SHALL implement the following commands;- • Server-Assignment-Request/Answer (SAR/SAA) command pair as defined in 3GPP TS 29.228 [1] section 6.1.2. • Registration-Termination-Request/Answer (RTR/RTA) command pair as defined in 3GPP TS 29.228 [1] section 6.1.3. • Push-Profile-Request/Answer (PPR/PPA) command pair as defined in 3GPP TS 29.228 [1] section 6.2.2. • Multimedia-Auth-Request/Answer (MAR/MAA) command pair as defined in 3GPP TS 29.228 [1] section 6.3.
Commands. The DB-0 Interface between S-CSC and HSS and between S-CSC and SLS SHALL implement the following commands;- • Server-Assignment-Request (SAR) command as defined in 3GPP TS 29.228 [1] section 6.1.2. • Multimedia-Auth-Request (MAR) command as defined in 3GPP TS 29.228 [1] section 6.3. NOTE: Only Request messages are sent to the SLS. The SLS only inserts the HSS address information in the Diameter message header, to allow the S-CSC to route the request to the correct HSS for the subscriber whom the request relates to.
Commands. The DB-0 Interface between I-CSC and HSS shall implement the following commands;-
Commands. There shall be two types of commands: database commands and control commands.
Commands. The DB-0 Interface between I-CSC and HSS shall implement the following commands;- User-Authentication-Request/Answer (UAR/UAA) command pair as defined in 3GPP TS 29.228 [1] section 6.1.1. • Location-Info-Request/Answer (LIR/LIA) command pair as defined in 3GPP TS 29.228 [1] section 6.1.4.
Commands. The DB-2 interface to the HSS from the Service Broker/SCIM, the Parlay X Gateway and the Application Server SHALL implement the following commands;- • User-Data-Request/Answer (UDR/UDA) command pair as defined in 3GPP TS 29.328 [1] section 6.1.1. • Profile-Update-Request/Answer (PUR/PUA) command pair as defined in 3GPP TS 29.328 [1] section 6.1.2. • Subscribe-Notifications-Request/Answer (SNR/SNA) command pair as defined in 3GPP TS 29.328 [1] section 6.1.3. • Push-Notification-Request/Answer (PNR/PNA) command pair as defined in 3GPP TS 29.328 [1] section 6.1.4.
