NETWORK SERVICE FOR MODULARLY CONSTRUCTING A SOFTWARE DEFINED RADIO

• US 20100185541A1
• Filed: 03/30/2010
• Published: 07/22/2010
• Est. Priority Date: 09/30/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Parikh, Vishesh M., Huitema, Christian, Hassan, Amer A.
• Granted Patent: US 8,346,900 B2
• Time in Patent Office: Days
• US Class Current: 705/34
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: H04B 1/0032 with analogue quadrature frequency conversion to and from the baseband quadrature modulators and demodulators per se H03D3/007, H03C3/40
• CPC Class Codes: H04H 60/04 Studio equipment; Interconnection of studios
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Systems and methods are provided that disclose a network service for modularly constructing a software defined radio (“SDR”). A server system provides an SDR kernel (i.e., a potentially platform-neutral definition of digital signal processing functionality and control operations necessary to implement the core portion of a software defined radio implementing a particular radio standard) to a client system. The client system may select a desired SDR kernel through a variety of means disclosed herein. While some SDR kernels may be provided for free and unrestricted use, others may be purchased or subscribed to and additionally restricted by digital rights management (“DRM”) policies. Based upon the agreed upon payment terms and any other restrictions, a customized set of DRM policies may be applied by the server system to the SDR kernel before sending it to a client system. Additionally, the server system may provide a description of governmental regulations applicable to a given locality.

Claims

1. A method for distributing an SDR kernel comprising acts of:

under control of a server system;

receiving a locality identifier from a client system, the locality identifier identifying a particular locality;

selecting an SDR kernel based at least in part on the received locality identifier; and

sending to the client system the selected SDR kernel.

2. The method of claim 1, further comprising acts of:

under control of a server system;

receiving user authentication information from the client system;

determining if the user authentication information matches authentication information for a registered user; and

in response to a determination that the user authentication does not match the authentication information for a registered user, directing a user of the client system to register.

3. The method of claim 1, further comprising acts of:

under control of a server system;

prior to receiving the locality identifier from the client system, sending a list of locality identifiers to the client system, wherein the list of locality identifiers includes the received locality identifier;

querying a locality database to generate a list of radio standard identifiers, each radio standard identifier identifying a particular radio standard used in a locality identified by the locality identifier;

sending the list of radio standard identifiers to the client system;

receiving a selected radio standard identifier from the client system;

sending a list of SDR kernel identifiers to the client system, each SDR kernel identifier identifying an SDR kernel, the SDR kernel describing an SDR kernel component for implementing the particular radio standard identified by the selected radio standard identifier;

receiving a selected SDR kernel identifier from the client system; and

wherein the SDR kernel sent to the client system comprises the SDR kernel identified by the selected SDR kernel identifier.

4. The method of claim 3, wherein pricing and publisher information are sent along with each SDR kernel identifier in the list of SDR kernel identifiers sent to the client system.

5. The method of claim 3, further comprising acts of:

under control of a server system;

sending a list of payment options to the client system;

receiving a selected payment option from the client system;

obtaining account information for an account to be billed; and

collecting payment from the account to be billed according to the selected payment option.

6. The method of claim 5, wherein the account information is obtained by receiving it from the client system.

7. The method of claim 5, wherein the account information is obtained by retrieving it from a database.

8. The method of claim 5, wherein the payment options include paying a fixed price for a finite duration of usage of the SDR kernel identified by the selected SDR kernel identifier.

9. The method of claim 5, wherein the payment options include paying a periodic fee for usage of the SDR kernel identified by the selected SDR kernel identifier.

10. The method of claim 5, wherein the payment options include paying a fixed price for an unlimited duration of usage of the SDR kernel identified by the selected SDR kernel identifier.

11. The method of claim 5, further comprising acts of:

under control of a server system;

securing the SDR kernel identified by the selected SDR kernel identifier by encrypting it using a digital rights management (“

DRM”

) component; and

adding DRM policies to the secured SDR kernel, the DRM policies generated in part to enforce terms of the selected payment option.

12. A method for configuring a client system with an SDR kernel, the method comprising:

operating at least one processor in the client system;

sending a locality identifier to a server system, the locality identifier indicating a locality of the client system;

receiving an SDR kernel from the server system based on the sent locality identifier;

consulting regulations data related to allowed usage of frequency bands in the locality of the client system; and

enabling the client system to communicate using the SDR kernel via a particular frequency based on the consulting of the regulations data.

13. The method of claim 12, further comprising:

operating the at least one processor in the client system;

receiving the regulations data from the server system based on the sent locality identifier.

14. A server system for sending an SDR kernel comprising:

a data storage medium storing a plurality of SDR kernels; and

a server engine constructed to;

receive a locality identifier, the locality identifier identifying a particular locality; and

send an SDR kernel of the plurality of SDR kernels, wherein the sent SDR kernel is selected based at least in part on the received locality identifier.

15. The server system of claim 14, further comprising:

a data storage medium storing a plurality of locality identifiers;

a data storage medium storing a plurality of radio standard identifiers;

a data storage medium storing a plurality of SDR kernel identifiers, each of the SDR kernel identifiers identifying one of the plurality of SDR kernels;

a data storage medium storing a standard-kernel mapping of radio standard identifiers to SDR kernel identifiers, the kernel-standard mapping indicating which SDR kernels describe implementations of each radio standard; and

wherein the server engine is additionally constructed to;

prior to receiving the received locality identifier, send a list of locality identifiers, wherein the list of locality identifiers includes the received locality identifier;

send a list of radio standard identifiers;

receive a selected radio standard identifier;

send a list of SDR kernel identifiers associated with the selected radio standard identifier according to the standard-kernel mapping;

receive a selected SDR kernel identifier; and

wherein the sent SDR kernel is identified by the selected SDR kernel identifier.

16. The server system of claim 15, further comprising:

a data storage medium storing a locality-standard mapping of locality identifiers to radio standard identifiers, the locality-standard mapping indicating radio standards typically used within each locality; and

wherein the sent list of radio standard identifiers comprises radio standard identifiers associated with the received locality identifier according to the locality-standard mapping.

17. The server system of claim 16, further comprising:

a data storage medium storing a locality-regulation mapping of locality identifiers to regulation data, the locality-regulation mapping effectively indicating regulations applicable to each locality;

a data storage medium storing user data, the user data including the last selected locality identifier; and

wherein the server engine is additionally constructed to send regulation data associated with the last selected locality identifier according to the locality-regulation mapping.

18. The server system of claim 14, further comprising:

a payment engine for processing financial transactions; and

wherein the server engine is additionally constructed to;

send a list of payment options;

receive a selected payment option;

obtain account information; and

send to the payment engine the obtained account information and the selected payment options for processing.

19. The server system of claim 18, further comprising:

a DRM engine for securing an SDR kernel, the DRM engine securing the SDR kernel in part according to the selected payment option; and

wherein the server engine is additionally constructed to send an SDR kernel identified by the selected SDR kernel identifier along with the selected payment option to the DRM engine.

20. The server system of claim 18, further comprising a data storage medium storing user data, the user data including account information;

and wherein the obtained account information is retrieved from the user data.