The search functionality is under construction.
The search functionality is under construction.

Keyword Search Result

[Keyword] address conflict(2hit)

1-2hit
  • A Cost-Efficient LDPC Decoder for DVB-S2 with the Solution to Address Conflict Issue

    Yan YING  Dan BAO  Zhiyi YU  Xiaoyang ZENG  Yun CHEN  

     
    PAPER-Digital Signal Processing

      Vol:
    E93-A No:8
      Page(s):
    1415-1424

    In this paper, a cost-efficient LDPC decoder for DVB-S2 is presented. Based on the Normalized Min-Sum algorithm and the turbo-decoding message-passing (TDMP) algorithm, a dual line-scan scheduling is proposed to enable hardware reusing. Furthermore, we present the solution to the address conflict issue caused by the characteristic of the parity-check matrix defined by DVB-S2 LDPC codes. Based on SMIC 0.13 µm standard CMOS process, the LDPC decoder has an area of 12.51 mm2. The required operating frequency to meet the throughput requirement of 135 Mbps with maximum iteration number of 30 is 105 MHz. Compared with the latest published DVB-S2 LDPC decoder, the proposed decoder reduces area cost by 34%.

  • Name-Based Address Mapping for Virtual Private Networks

    Peter SURANYI  Yasushi SHINJO  Kazuhiko KATO  

     
    PAPER-Internet

      Vol:
    E92-B No:1
      Page(s):
    200-208

    IPv4 private addresses are commonly used in local area networks (LANs). With the increasing popularity of virtual private networks (VPNs), it has become common that a user connects to multiple LANs at the same time. However, private address ranges for LANs frequently overlap. In such cases, existing systems do not allow the user to access the resources on all LANs at the same time. In this paper, we propose name-based address mapping for VPNs, a novel method that allows connecting to hosts through multiple VPNs at the same time, even when the address ranges of the VPNs overlap. In name-based address mapping, rather than using the IP addresses used on the LANs (the real addresses), we assign a unique virtual address to each remote host based on its domain name. The local host uses the virtual addresses to communicate with remote hosts. We have implemented name-based address mapping for layer 3 OpenVPN connections on Linux and measured its performance. The communication overhead of our system is less than 1.5% for throughput and less than 0.2 ms for each name resolution.