Functional Requirements Mobile Network Operator Mno
Functional Requirements Mobile Network Operator Mno Sample Clauses
Related to Functional Requirements Mobile Network Operator Mno
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.
Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.
Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.
Conversion of Wholesale Services to Network Elements or Network Elements to Wholesale Services Upon request, BellSouth shall convert a wholesale service, or group of wholesale services, to the equivalent Network Element or Combination that is available to Global Dialtone pursuant to Section 251 of the Act and under this Agreement or convert a Network Element or Combination that is available to Global Dialtone pursuant to Section 251 of the Act and under this Agreement to an equivalent wholesale service or group of wholesale services offered by BellSouth (collectively “Conversion”). BellSouth shall charge the applicable nonrecurring switch-as-is rates for Conversions to specific Network Elements or Combinations found in Exhibit A. BellSouth shall also charge the same nonrecurring switch-as-is rates when converting from Network Elements or Combinations. Any rate change resulting from the Conversion will be effective as of the next billing cycle following BellSouth’s receipt of a complete and accurate Conversion request from Global Dialtone. A Conversion shall be considered termination for purposes of any volume and/or term commitments and/or grandfathered status between Global Dialtone and BellSouth. Any change from a wholesale service/group of wholesale services to a Network Element/Combination, or from a Network Element/Combination to a wholesale service/group of wholesale services, that requires a physical rearrangement will not be considered to be a Conversion for purposes of this Agreement. BellSouth will not require physical rearrangements if the Conversion can be completed through record changes only. Orders for Conversions will be handled in accordance with the guidelines set forth in the Ordering Guidelines and Processes and CLEC Information Packages as referenced in Sections 1.13.1 and 1.13.2 below.
Network Requirements (A) The Contractor shall maintain and monitor a network of appropriate Network Providers that is supported by written agreements and is sufficient to provide adequate access to all Covered Services for all Enrollees, including those with limited English proficiency or physical or mental disabilities. In establishing and maintaining the network of Network Providers the Contractor shall consider:
Wireless Operator Data In addition to Section 20 (Information Authorization) of the General Terms, you acknowledge that we or Zelle® may use information on file with your wireless operator to further verify your identity and to protect against or prevent actual or potential fraud or unauthorized use of the Service. By using the Zelle® Payment Service, you authorize your wireless operator (AT&T, Sprint, T-Mobile, US Cellular, Verizon, or any other branded wireless operator) to disclose your mobile number, name, address, email, network status, customer type, customer role, billing type, mobile device identifiers (IMSI and IMEI) and other subscriber status and device details, if available, to us or our Service Providers solely to allow verification of your identity and to compare information you have provided to us or to Zelle® with your wireless operator account profile information for the duration of our business relationship. See Zelle®’s Privacy Policy at xxxxx://xxx.xxxxxxxx.xxx/privacy-policy for how it treats your data. Please review our Privacy Policy in order to better understand our commitment to maintaining your privacy, as well as our use and disclosure of your information.
AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.
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.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
