Log in
Enquire now
‌

US Patent 7616716 Synchronisation in a receiver

Patent 7616716 was granted and assigned to University of Bristol on November, 2009 by the United States Patent and Trademark Office.

OverviewStructured DataIssuesContributors

Contents

Is a
Patent
Patent
0

Patent attributes

Current Assignee
University of Bristol
University of Bristol
0
Patent Jurisdiction
United States Patent and Trademark Office
United States Patent and Trademark Office
0
Patent Number
76167160
Patent Inventor Names
Mark Anthony Beach0
Christopher Williams0
Date of Patent
November 10, 2009
0
Patent Application Number
112183140
Date Filed
August 31, 2005
0
Patent Primary Examiner
‌
Shuwang Liu
0
Patent abstract

A radio receiver is suitable for use in an OFDM wireless communications system, in which it is necessary to identify a timing point at a start of a frame. In order to ensure optimum performance of the receiver in multipath environments, it should be synchronised with the first received multipath component, although one or more of the delayed multipath components may be stronger than the first component. A method of determining the time position of the first received multipath component, determines a correlator function from the received signal, and determines the required timing point from a falling edge in a derivative of the correlator function.

Timeline

No Timeline data yet.

Further Resources

Title
Author
Link
Type
Date
No Further Resources data yet.

References

Find more entities like US Patent 7616716 Synchronisation in a receiver

Use the Golden Query Tool to find similar entities by any field in the Knowledge Graph, including industry, location, and more.
Open Query Tool
Access by API
Golden Query Tool
Golden logo

Company

  • Home
  • Press & Media
  • Blog
  • Careers
  • WE'RE HIRING

Products

  • Knowledge Graph
  • Query Tool
  • Data Requests
  • Knowledge Storage
  • API
  • Pricing
  • Enterprise
  • ChatGPT Plugin

Legal

  • Terms of Service
  • Enterprise Terms of Service
  • Privacy Policy

Help

  • Help center
  • API Documentation
  • Contact Us
By using this site, you agree to our Terms of Service.