The URI Channel is unique for each device on which your application is installed. It has to be unique for each device, since that's what tells the MPN service which device to send the notification to. It serves the same purpose as Device Tokens for Apple Push Notifications and Registration IDs for Google Cloud Messaging.
You can send the URI Channel to your server by sending some HTTP GET or POST request to your server, with the URI Chnnael as the input parameter.
Here are some guidelines for comminicating your server taken from MSDN :
Each time your app starts, you should pass the URI from your push channel to the cloud service that sends out the push notifications. It is also recommended that you pass the device ID to your cloud service so that the cloud service can track to which devices the URIs are assigned. If a URI changes, then the cloud service can replace the old URI for that device ID. Windows Phone does not provide a framework to do this, since in most scenarios apps and cloud services already have their own protocols that they use to communicate with each other.
Best practices for communicating with your cloud service include:
The app should authenticate with its corresponding cloud service.
The app should encrypt its notification channel URI before sending the URI to its corresponding cloud service.
If your cloud service will be using notifications properties that do not exist in Windows Phone OS 7.0 then you should pass the OS version information to your cloud service so that the cloud service can correctly downgrade the notifications for Windows Phone OS 7.0 clients.
The cloud service should validate the notification channel URI received from its corresponding app and store it in a secure manner.
When a session is initiated from the app, the notification channel URI should always be sent to its corresponding cloud service.
The cloud service should have a status code that it can send to its corresponding app that will trigger the app to create a new notification channel URI.