BSD socket interface
BSD socket is provided as the application interface. This makes it easy to reuse the network applications of POSIX software, including Linux. POSIX software engineer resources can also be used for application development.
Best-class performance in the industry
Optimized high-performance networking
Field-proven results in high-speed, multi-session video streaming products.
Checksum offloading support enables faster speeds at the hardware level.
Supports IP multicast function
Supports an IP multicast sending and receiving function, which enables the same data to be sent to multiple specified destinations at the same time. This is effective for distributing large-sized media data such as video or audio.
Adjustable memory size
PrCONNECT/Pro has a function selection switch for adjusting the overall code size. If the DHCP client, DNS client, IP multicast, or AutoIP function is not needed, this function selection switch can be used to specify the unused function during system configuration so that the function module is not embedded. The code is adjusted to the minimum required size to prevent wasteful memory consumption.
Supports various platforms
componentizes source code dependent on the target system, such as the operating
system, CPU, or NIC (Network Interface Card), as environment-dependent parts.
In addition, TCP/IP Stack is coded in C language. As a result, PrCONNECT/Pro has
excellent portability, making it easy to support various platforms. PrCONNECT/Pro is configured to run on eT-Kernel as
standard. On eT-Kernel, it runs on various profiles such as eT-Kernel
Multi-Core Edition and eT-Kernel/POSIX.
When eT-Kernel is
used, PrCONNECT/Pro can be implemented either as a library or as a T-Kernel
subsystem. (Refer to T-Engine's
Software Architecture Configuration for more information about
subsystems.) Socket API is provided as the interface even when PrCONNECT/Pro Stack is
implemented as a T-Kernel subsystem. When implemented as a T-Kernel subsystem,
PrCONNECT/Pro can also be used from a loadable system program or process
application. Loadable drivers can be added dynamically to PrCONNECT/Pro.
Various protocols provided as standard
PrCONNECT/Pro implements the following protocols as standard.
• DHCP client / DNS client / FTP client / FTP server / TELNET server
• IPv4/ARP/ICMP/IGMP/AutoIP, etc.
Many available optional protocols
The functions needed for use in the application can be selected. Dual stack for IPv4/IPv6 is also available.
||IPv4/IPv6 dual stack|
||HTTP server, HTTP server/SSL（https server）, HTML compiler|
|PrCONNECT/Pro other options||DNS server, DHCP server, IPSec, IKE library, RIPv1/v2, NAT, PPPoE etc|
* These optional protocols are released as required. The product configuration may be changed. Please contact us for details such as the release date.
Sample drivers and sample applications
A device driver that supports the network controller used in the system must be created for PrCONNECT/Pro. The following source code is included as standard as a sample for this device driver. In addition, sample source code for various applications are included as standard.
• Device driver for Ethernet
o RZ/A1 built-in Ethernet controller
o Zynq-7000 built-in Ethernet controller
o CycloneVSoC built-in Ethernet controller
o i.MX6 built-in Ethernet controller
• FTP sample application (server/client)
• TELNET sample application (server)
In addition to the samples included as standard, a wide range of controllers with a successful record of operation are available. Please feel free to contact us for details.
• Motorola 5282c3
• Intel 8255x
• SMSC LAN91C111
• SMSC LAN9118
• Marvell WLAN
• MPC8272/48, MPC8349 built-in Ethernet controller, etc.
Source code provided
PrCONNECT/Pro is provided as source code.
Maintenance service and customization service
The following maintenance service is provided. The maintenance service enables developers to use PrCONNECT/Pro with peace of mind.
• Response to email inquiries regarding the product
• Minor version upgrades
In addition, a customization service is available for supporting PrCONNECT/Pro in different environments, such as a custom real-time operating system or hardware.
RFC Support in PrCONNECT/Pro Series
|General||1122||Requirements for Internet Hosts|
||793||Transmission Control Protocol|
|1323||TCP Extensions for High Performance|
|2414||Increasing TCP's Initial Window (Obsoleted by RFC3390)|
|UDP||768||User Datagram Protocol|
|894||A Standard for the Transmission of IP|
|919||Broadcasting Internet Datagrams|
|922||Broadcasting Internet datagrams in the presence of subnets|
|950||Internet Standard Subnetting Procedure|
|1112||Host Extensions for IP Multicasting (IGMP)|
||826||Ethernet Address Resolution Protocol|
||792||Internet Control Message Protocol|
|1191||Path MTU discovery|
||894||Standard for the Transmission of IP Datagrams over Ethernet Networks|
|1662||PPP in HDLC-like Framing|
|1144||Compressing TCP/IP headers for low-speed serial links [VJ Compression]|
|1332||The PPP Internet protocol Control Protocol (IPCP)|
|1877||PPP Internet Protocol Control Protocol Extensions for Name Server Addresses (Options 129, 131 supported)|
|1994||PPP Challenge Handshake Authentication Protocol (CHAP)|
||1034||Domain names - concepts and facilities|
|1035||Domain Names - Implementation and Specification|
||2131||Dynamic Host Configuration Protocol|
|2132||DHCP Options and BOOTP Vendor Extensions|
||959||File Transfer Protocol|
|Mail||821||Simple Mail Transfer Protocol|
|822||STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGESPost Office Protocol - Version 3|
|1869||SMTP Service Extensions|
|1939||Post Office Protocol - Version 3|
|2045||Multipurpose Internet Mail Extensions (MIME)|
Part One: Format of Internet Message Bodies
|2046||Multipurpose Internet Mail Extensions (MIME)|
Part Two: Media Types
|2047||MIME (Multipurpose Internet Mail Extensions)|
Part Three: Message Header Extensions for Non-ASCII Text
|2048||Multipurpose Internet Mail Extensions (MIME)|
Part Four: Registration Procedures)
|2049||Multipurpose Internet Mail Extensions (MIME)|
Part Five: Conformance Criteria and Examples
|HTTP||1866||Hypertext Markup Language - 2.0|
|1867||Form-based File Upload in HTML|
|1945||Hypertext Transfer Protocol -- HTTP/1.0|
|2616||Hypertext Transfer Protocol -- HTTP/1.1|
Successful operation has been demonstrated on the following operating systems.