P2P
Remote access per device
Open a registered device’s remote interface through its Client access URL. Review its service status, term and concurrent connection limit, and create, replace or revoke access URLs.
此技术资料目前以英语提供。翻译发布后将在此处显示。
WAVERSA / VIDEO SYSTEMS
服务与订阅
Explore device connectivity, AI subscriptions and management by vendor for ongoing operation.
01 / Services
P2P · DDNS · AI subscriptions
Link P2P remote access, named DDNS addresses and selected AI subscriptions for WServer devices to each device and its purchasing organization.
DDNS
A memorable device address
Open a device’s P2P access page through its registered name. Use the name instead of a long access URL, with the address linked to the current URL reported by the device.
AI SUBSCRIPTION
Select features and channels
Distinguish included features from subscriptions, then choose the features, camera channel count and monthly or yearly term from the AI cards offered for sale. Approved subscriptions are reflected in the device’s licence.
From device registration to the remote interface
Device registration
Register the device with the service using the organization code and purchase PIN.
Waversa services
Link the P2P access URL, DDNS name and AI subscription entitlements to the device.
Remote interface
Open the access page through the access URL or named address, then sign in with the device account.
An illustration of how the services connect. Actual access and video conditions depend on the site network and service status.
02 / Management
Device and subscription management by vendor
Devices and subscriptions are managed by purchasing organization. The supplier manages service policies, while each vendor (installer or reseller) reviews its own organization’s devices and service status in one vendor console.
TECHNOLOGY
Technical advantages
Registration verified with a device-specific key
A device registers with the organization code and purchase PIN, proves possession of its own key, and then receives a device ID and access URL. The private key does not leave the device, and requests to register or refresh a named address are verified by the device’s signature.
An HTTPS certificate for each named address
Each registered DDNS name receives its own certificate and is served over HTTPS. When an access URL is replaced, the named address follows the new URL reported by the device.
Access path separate from device login
The access URL leads to the device’s access page; use of the device is confirmed by a separate device-account login. Access URLs can be revoked or replaced per device.
AI entitlements delivered in a signed licence
The AI features, camera channel count and term of an approved subscription are delivered to the device in a signed licence. The device applies the scope of its AI features according to that licence.
Access separated by organization
A vendor account belongs to a single purchasing organization and cannot view another organization’s devices, access URLs or invoices. The supplier console and vendor console use separate accounts and login sessions.
Signature-verified, targeted firmware releases
Only firmware with a verified signature is published, and each release is offered to all devices or to selected organizations and devices. This supports staged rollouts that begin with a small group before widening.
MANAGEMENT
Management advantages
Make access addresses easier to manage
Link a named device address to its access URL so installation sites are easier to identify. Manage URL replacement and revocation while keeping the separate device-account login for remote access.
Review the AI features you need
Check access to each AI card and the number of camera channels covered. Distinguish the concurrent connection limit for remote access from AI channel counts when reviewing a site’s configuration.
See your organization’s devices together
The vendor console brings device names, platform and firmware, P2P status, DDNS addresses, AI subscriptions and last-reported times together. Review multiple devices using the same information.
Connect service terms with billing records
Review subscription terms, status, quantities and purchase-order references alongside the organization’s billing details. Identify P2P devices nearing expiry and unpaid invoices when reviewing renewals and contracts.
Vendors handle site tasks directly
Vendors rename devices and create, replace or revoke access URLs within their own organization. Policies such as connection limits, service suspension and subscription approval remain with the supplier, keeping responsibilities distinct.
Change history and billing records are retained
Device deletion, edits to firmware version or platform details, and changes to release targets are recorded in an audit log. Issued billing records are retained when a device is deleted.
From registration to ongoing review
Register the organization and its contacts
The supplier prepares the purchasing organization and enrollment policy. Installer or reseller staff apply for vendor verification under that organization, then use approved accounts to manage its devices.
Connect the device
Register from the device using the organization code and purchase PIN, then check the Client access URL and service connection status. Add a DDNS name when required.
Select AI features and service terms
Choose the channel count and term for the AI cards offered. Confirm the entitlement after supplier approval or automatic approval, according to the organization’s policy.
Review devices, subscriptions and billing
Vendors view their own organization’s service status and billing details. The supplier manages operational changes such as connection limits, service suspension and contract changes.
Supplier and vendor responsibilities
| Role | Scope | Main tasks |
|---|---|---|
| Supplier administrator | Purchasing organizations and service policies | Manage organizations and vendor-account approval, device enrollment policies, P2P limits and activation or suspension, DDNS suspension or resumption, subscription approval or cancellation, and invoice issuance. |
| Vendor · Installer or reseller contact | The single purchasing organization assigned to the account | Manage device names and access URLs, and view P2P, DDNS, AI subscription and billing information for that organization. Maintain its contact details and purchase PIN. |
What to review for devices and contracts
| Item | Information and controls |
|---|---|
| New device enrollment | Set whether registration is allowed, the trial term for new P2P devices and their concurrent connection limit. New enrollment policy is separate from suspending an existing device’s service. |
| P2P access and DDNS | Review the device’s service term, concurrent connection limit, status and named address. Permissions for creating, replacing or revoking access URLs are separate from service suspension. |
| AI features and service terms | Review included or subscribed AI cards, monthly or yearly terms, approval status and camera channel counts. Distinguish cancellation at the end of a term from immediate cancellation by the supplier. |
| Device replacement and subscription transfer | An AI subscription can move to another device in the same purchasing organization, subject to the destination’s existing subscriptions and channel count. A P2P subscription cannot be transferred to a different device. |
| Correcting a P2P device’s organization | The supplier can change the registered organization only when the device has no billing history, pending subscription or paid subscription. Registering again with a different organization code does not change ownership. |
- Confirm available features, sale status, trial terms and pricing for the device, product and contract. AI quantities refer to camera channels; P2P limits refer to concurrent connections.
- P2P trials expire without automatic conversion to a paid service. Check the selected product and contract for AI trial, renewal and cancellation terms.
- Invoice and payment-status management does not imply automatic card charging or a payment gateway.