Christian Benkeser

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Benjamin Weber

> Home > Persons > Christian Benkeser

Publications

2015
[j8]
- view
  authority control:
- export record
  dblp key:
  - journals/jssc/KrollZWRTBBH15
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/jssc/KrollZWRTBBH15
Harald Kröll, Stefan Zwicky, Benjamin Weber, Christoph Roth, David Tschopp, Christian Benkeser, Andreas Peter Burg, Qiuting Huang:
An Evolved GSM/EDGE Baseband ASIC Supporting Rx Diversity. IEEE J. Solid State Circuits 50(7): 1690-1701 (2015)
[j7]
- view
  authority control:
- export record
  dblp key:
  - journals/vlsisp/WeberKBH15
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/vlsisp/WeberKBH15
Benjamin Weber, Harald Kröll, Christian Benkeser, Qiuting Huang:
On the Mapping of Incremental Redundancy into a Physical Layer ASIC. J. Signal Process. Syst. 78(3): 299-312 (2015)
2014
[c19]
- view
  authority control:
- export record
  dblp key:
  - conf/esscirc/KrollZWRBBH14
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/esscirc/KrollZWRBBH14
Harald Kroll, Stefan Zwicky, Benjamin Weber, Christoph Roth, Christian Benkeser, Andreas Peter Burg, Qiuting Huang:
An evolved EDGE PHY ASIC supporting soft-output equalization and Rx diversity. ESSCIRC 2014: 203-206
2013
[j4]
- view
  authority control:
- export record
  dblp key:
  - journals/vlsisp/KrollZWBH13
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/vlsisp/KrollZWBH13
Harald Kröll, Stefan Zwicky, Benjamin Weber, Christian Benkeser, Qiuting Huang:
Physical Layer Development Framework for OsmocomBB. J. Signal Process. Syst. 73(3): 301-314 (2013)

a service of

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.