转: Wi-Fi Aware™

http://www.wi-fi.org/zh-hans/news-events/newsroom/wi-fi-aware-wi-fi-certified?utm_source=newsletter-simplified-chinese&utm_medium=email&utm_campaign=newsletter-february-2015

 

Wi-Fi Aware™ 今年底将为WI-FI CERTIFIED™ 设备提供周边服务发现功能

设备能够在建立连接前感知周边服务

201516日,内华达州拉斯维加斯讯――随着在线社交应用、本地应用及移动应用以爆发性速度增长,Wi-Fi®即将推出全新功能,帮助用户在建立Wi-Fi连接之前轻松发现附近设备、应用与信息。这种解决方案名为Wi-Fi Aware™,将于今年年底部署于Wi-Fi CERTIFIED™产品。

Wi-Fi Aware背后的“周边感知”技术能够在后台连续运行,发送极小量的消息,帮助多种应用实现服务发现功能。Wi-Fi Aware认证设备能够在连接之前发现服务,进一步提高Wi-Fi技术为游戏、点对点消息和媒体共享等社交应用以及距离评估、背景通知和优惠信息等针对具 体地点的服务便利性。发现服务后,用户即可发起应用,通过Wi-Fi Direct® 或传统Wi-Fi建立连接,使用这些服务。

Wi-Fi Alliance 总裁兼首席执行官埃德加·菲格诺(Edgar Figueroa)说:“我们知道,用户希望在社区和本地应用中尽可能多地使用Wi-Fi,Wi-Fi Aware是一项激动人心的技术突破,帮助用户在建立连接之前更轻松地了解附近存在哪些有趣服务。Wi-Fi Aware改变了周边服务的发起方式,能够实现多种点对点服务体验,对此我们非常高兴。”

Wi-Fi Aware认证项目上市之时正值智能手机取代功能手机、移动设备日益增加的功能正在为移动应用市场带来蓬勃生机之际。随着移动生态系统的发展,Wi-Fi 也在不断进步,实现基于附近信息的新型应用,为移动设备赋予显著优势,根据个人偏好为用户带来个性化体验。

Wi-Fi Aware在行动

Wi-Fi Aware可以在拥挤环境下和室内正常运行,且具有减少功耗的优势。移动设备上的应用可以使用Wi-Fi Aware向其他设备提供服务或寻找其他设备的服务。发现服务后,用户即可“选择”与发现的设备建立连接――通常无需使用互联网连接。

Wi-Fi Aware的价值在社交应用、本地应用和移动应用中得到体现。应用本身可以利用Wi-Fi Aware认证设备的技术发现附近的对等设备提供的宝贵服务。例如,用户可以下载购物应用,该 应用利用Wi-Fi Aware寻找附近可用的用户偏好品牌。在另一个例子中,设备通过点唱机应用可以识别彼此,以便在场馆或派对中根据用户偏好定制播放列表。

埃德加·菲格诺说:“我们才刚刚开始想象Wi-Fi Aware的用途。当然,人们将利用这种技术发现视频游戏组件、照片共享机遇和本地信息资源。除此之外,Wi-Fi Aware在多种尚待确定的其他服务中的潜力也令我们期待不已。”

请登录www.wi-fi.org/wi-fi-aware了解更多资源,包括生 动展示Wi-Fi Aware技术的视频动画。《Wi-Fi Alliance周边感知联网规范》(Wi-Fi Neighbor Awareness Networking Specification)是即将上市的Wi-Fi Aware认证项目的基础,该《规范草案》已可购买。

– See more at: http://www.wi-fi.org/zh-hans/news-events/newsroom/wi-fi-aware-wi-fi-certified?utm_source=newsletter-simplified-chinese&utm_medium=email&utm_campaign=newsletter-february-2015#sthash.ERYGZi5I.dpuf

FW: Understanding the Different HDMI Versions (1.0 to 2.0)

http://www.audioholics.com/hdtv-formats/understanding-difference-hdmi-versions

by — September 11, 2013

HDMI Versions - Keep Up!

HDMI Versions – Keep Up!

HDMI has changed versions so many times it’s been hard to keep up for most people. We’ve talked about the versions as part of other articles and documents, but it seemed fitting that we’d formulate and maintain a definitive document outlining the changes in a straightforward and easy-to-digest manner for all concerned.

Hopefully this article helps you understand the format differences and aids in your ability to discern what features are important to you as you shop for HDMI-equipped products.

HDMI 1.0

Release date: December 2002

Specs:

  • Single-cable digital audio/video connection with a maximum bitrate of 4.9Gbps.
  • Supports up to 165Mpixels/sec video (1080p at 60Hz or UXGA)
  • 8-channels of 192kHz/24-bit audio (PCM)

Abstract: The original HDMI v1.0 spec was and remains sufficient for most purposes. The reason is that it is a solid backwards-compatible format that can , through PCM audio handle all of the high definition audio formats present today. The key is having a player that can decode these native HD audio formats to uncompressed PCM. DSD and DVD-audio cannot be natively sent over HDMI 1.0. What HDMI 1.0 fails to do, is account for additional bandwidth provided by Deep Color (10- 12 and 16-bit color depths). It also does not support the new xvYCC color space.

Practical Issues and tips: Most CableTV set-top boxes use HDMI 1.0. The maximum output for this spec is 1080p at 60Hz with 8-bit color depth. Regardless of any display of higher version of HDMI you may have, the source will always limit the maximum bit-depth potential. An HDMI 1.0 device can still pull 8 channels of uncompressed PCM audio and as is perfectly fine for most users.

HDMI 1.1

Release date: May 2004

Specs:

  • Added support for DVD Audio
  • Slight mechanical and electrical spec changes

Abstract: HDMI 1.1 simply added the ability for the system to transmit DVD-Audio signal over the cbale form the player to the receiving device. If both devices are rated to v1.1 then a DVD-Audio signal can be sent and received. Please note that by “DVD-Audio” we mean the high resolution audio format, not the audio present on a typical DVD disc.

Practical Issues and tips: HDMI 1.1 is very common and was the first spec to hit the mass market apart from CableTV set-top boxes. Many AV receivers came out with this spec and are fine for handling DVD-Audio and uncompressed PCM audio.

HDMI 1.2

Release date: August 2005

Specs:

  • Added DSD (Direct Stream Digital) support, allowing native transmission of Super Audio CD (SACD) content at up to 8 channels
  • Enabled and acknowledged an HDMI Type A connector for PC-based sources
  • Permitted PC sources to use native RGB color-space with the optional ability to also support the YCbCr color space for consumer electronics applications
  • Mandated that HDMI 1.2 and later displays support low-voltage sources such as those found with PCI Express technology (the current display interface standard for PC video cards)

Abstract: HDMI 1.2 was the biggest jump since the introduction of HDMI. It really brought the PC market into focus and was developed and announced so as to compete better with the emerging VESA DisplayPort standard. For those still clinging to their universal DVD players, HDMI v1.2 finally delivered the promise of a true one-cable solution for all current high-definition audio sources.

Practical Issues and tips: If you want to utilize a fully native universal DVD player without converting the SACD to PCM then HDMI 1.2 is required. We’ve found that if the player does a good job at conversion, however, v1.2 isn’t always that important.

HDMI 1.2a

Release date: December 2005

Specs:

  • Fully specified Consumer Electronic Control (CEC) features, command sets, and compliance tests
  • Minor changes to CEC (Consumer Electronic Control) spec

Abstract: This incremental change clarified one of the earlier promises of HDMI, Consumer Electronic Control – a feature that promised “smart” interoperability between components. Unfortunately, this wasn’t exactly standardized across the board and, as a result, nearly all manufacturers products only interface within their own brands. Of all things, this is the most disappointing failure of HDMI to-date.

Practical Issues and tips: This is a common format for manufacturers using CEC. There is no practical reason to prefer 1.2a over 1.2. If you don’t intend to use the native DSD signal from an SACD player via HDMI, v1.1 is just as good as 1.2 or 1.2a.

HDMI 1.3

Release date: June 2006

Specs:

  • Increased single-link bandwidth to 340 MHz (10.2 Gbps)
  • Optionally supports 10-bit, 12-bit, and 16-bit “Deep Color” per channel (over one billion colors) up from 8-bit
  • Allowed the use of xvYCC color space (previously just sRGB or YCbCr)
  • Incorporated automatic audio “lip” syncing capability
  • Supported output of native Dolby TrueHD and DTS-HD Master Audio streams for external decoding by AV receivers
  • Made available a new Type C “mini” connector for devices such as camcorders
  • Added gamut Metadata transmission capability
  • Added Reference Cable Equalizer mandate to high frequency displays to recapture degraded copper cable signal

Abstract: To be plain, this update was a complete disaster. First of all, nobody asked for HDMI 1.3, except perhaps the companies behind the new high definition audio formats. Of course TrueHD and DTS-HD, the lossless audio codec formats used on HD DVDs and Blu-ray Discs could be decoded into uncompressed audio by the players. This makes 1.3 irrelevant for audio. What made HDMI 1.3 such as disaster was the increased bandwidth requirements – which hit an already suffering cable market with new requirements for digital signal transmission. Before HDMI 1.3, it was almost impossible to get a non-active copper HDMI cable to pass 1080p at distances greater than 50 feet. After HDMI 1.3, with the addition of Deep Color, that distance shrank to less than 20 feet, causing industry-wide failures on installed cabling systems.

Expensive active solutions started coming on-board to alleviate some of the problems within several months but even today there is a large amount of consumer confusion regarding cable certification and how far a signal will travel over copper cables. The spec also mandated that HDMI 1.3-compliant displays (sinks) which took advantage of high frequency content (Deep Color) must implement built-in cable equalization to help compensate for cable losses through copper cables. Thanks to several companies dedicated to certifying their products for specific distances, this issue is slowly becoming more manageable. The first product on the market with HDMI 1.3 was the PlayStation 3 gaming console.

Practical Issues and tips: HDMI 1.3 is a requirement for Deep Color support or use of the new xvYCC expanded color space. If high definition audio is important to you, you still may not need v1.3 if your player can decode the native HD audio formats into uncompressed PCM audio. This uncompressed audio, up to 8 channels, can be sent over HDMI 1.0.Typically, 24p support coincides with v1.3, however this is nothing more than coincidence of when both format and spec came into popularity.

HDMI 1.3a

Release date: November 2006

Specs:

  • Cable and Sink modifications for Type C
  • Source termination recommendation
  • Removed undershoot and maximum rise/fall time limits.
  • CEC capacitance limits changed
  • RGB video quantization range clarification
  • audio control commands added to CEC and commands for timer control brought back in an altered form
  • Concurrently released compliance test specification included

Abstract: An incremental change, v1.3a is mostly an adjustment for manufacturers utilizing CEC features as well as those integrating the new Type C connector (seen only in smaller form factor products and quite rare to-date).

Practical Issues and tips: There is no consumer-focused practical difference between HDMI v1.3a and v1.3.

HDMI 1.3b

Release date: March 2007

Specs:

No difference in features, performance or function over HDMI 1.3a.  HDMI 1.3b defines testing for products based on the 1.3a spec.

Abstract: HDMI 1.3b does not add anything over 1.3a.  It simply adds parameters for testing products.

Practical Issues and Tips: There is no consumer-focused practical difference between HDMI v1.3a and v1.3b.

HDMI 1.3b1

Release date: November 2007

Specs:

  • No difference in features, performance or function over HDMI 1.3a.  HDMI 1.3b1 defines testing for products based on the HDMI type C Mini connector.

Abstract: HDMI 1.3b1 does not add features or performance to HDMI 1.3a.  It simply adds parameters for testing products that use the HDMI type C Mini connector.

Practical Issues and Tips: There is no consumer-focused practical difference between HDMI v1.3a and v1.3b1.

HDMI 1.3c

Release date: August 2008

Specs:

  • No difference in features, performance or function over HDMI 1.3a, but rather testing for products based on active HDMI cables.

Abstract: HDMI 1.3c does not add features or performance to HDMI 1.3a.  HDMI 1.3c simply adds parameters for testing products based on active HDMI cables.

Practical Issues and Tips: There is no consumer-focused practical difference between HDMI v1.3a and v1.3c.

HDMI 1.4

Release Date: May 2009

Specs:

  • Ethernet over HDMI: Adds support for ethernet over HDMI for connected devices.
  • Audio Return Channel:  Allows an HDMI-connected TV with a built-in tuner to send audio data “upstream” to a surround audio system, eliminating the need for a separate audio cable.
  • 3D Support: Defines input/output protocols for major 3D video formats, paving the way for true 3D gaming and 3D home theater applications.
  • Support for 4K x 2K resolution (3840 x 2160) at 24Hz, 25Hz, and 30Hz and 4096 x 2160 at 24Hz.
  • Real-time signaling of content types between display and source devices enables a TV to optimize picture settings based on content type
  • Additional Color Spaces – Adds support for sYCC601, AdobeRGB, and AdobeYCC601, which are used in digital photography and computer graphics
  • HDMI Micro Connector – A new, smaller connector for phones and other portable devices, supporting video resolutions up to 1080p.
  • Automotive Connection System – New cables and connectors for automotive video systems, designed to meet the unique demands of the motoring environment

Abstract: A major update that brings support for 3D, Ethernet network, bi-directional audio communications, and increased support of digital photography and digital computer color space standards.

Practical Issues and tips: HDMI 1.4’s biggest feature is 3D support and home 3D viewing; Ethernet over HDMI (eliminating the need for a separate ethernet cable run); Audio return channel will further reduce cable clutter by allowing your TV to send its audio to your receiver without the need for an additional audio cable run; the HDMI micro connector brings HDMI to smaller devices and mobile; and the support for photographic and computer color spaces which makes HDMI a viable connector on cameras and computers.

HDMI 1.4a

Release Date: March 2010

Specs:

  • Added 3D format for broadcast content
  • Abstract: An incremental change to allow broadcast support of 3D content.

HDMI 1.4b

Release Date: October 2011
 
Specs:
  • Enabled 3D 1080p video at 120 Hz so that each eye can receive full HD (1080p 60Hz—or 120 Hz total) per Eye

Abstract: An incremental change to allow for Full HD (1080p) viewing of 3D content.

Practical Issues and tips: Allows for 3D content to be viewed in full HD.

HDMI 2.0

Release Date: September 2013

Specs:

  • Increases bandwidth to 18Gbps
  • Resolutions up to 4K@50/60 (2160p), (4 times the clarity of 1080p/60 video resolution)
  • Up to 32 audio channels
  • Up to 1536kHz audio sample frequency
  • Simultaneous delivery of dual video streams to multiple users on the same screen
  • Simultaneous delivery of multi-stream audio to multiple users (Up to 4)
  • Support for the wide angle theatrical 21:9 video aspect ratio
  • Dynamic synchronization of video and audio streams
  • Updated CEC extensions for more expanded command and control of consumer electronics devices through a single control point
  • Support for 4:2:0 chroma subsampling
  • Support for 25 fps 3D formats
  • Backward compatible with high speed (category 2) HDMI cables

Abstract: This is a major update that increases bandwidth to 18Gbps and includes support for 4k video—including dual video to the same display to multiple users.  Audio is increased from 8 to 32 channels including simultaneous delivery of multichannel audio to a maximum of four users.  Audio sample frequency is increased to 1536kHz.

Summary

We’ll be sure to keep this document up to date as soon as any HDMI changes are made and will attempt to clarify any questions or issues raised by readers when going through this list. HDMI seems confusing at first, but if handled well by a manufacturer, the differences can be nearly transparent to consumers. The difficulty comes when selecting budget products that may not implement all of the capabilities needed to maximize the potential of HDMI. In these scenarios it’s important to not just pay attention to the version of HDMI, but how HDMI is utilized within the product. For example, HDMI “switching” on a receiver implies that no audio is pulled from the HDMI cable, however if the receiver functions as an HDMI “repeater” then users can expect to pull at least multi-channel PCM audio from the connection.

Stay tuned, because if the past is any indication of the future (and it is) HDMI isn’t done yet and will continue to evolve in the years to come.

MMI String

###232#                  Access call duration directly

*#3228#                   Check current software version

*#2886#                   MMI testing

How to Remotely access the iLO4 of Home HP MicroServer Gen8 behind a corporation firewall

By ssh local port forward, we can access the iLO4 and Remote console of Home from the corporation network which protected by firewall,  with only 80 and 433 ports opened via proxy.

 

HOME

HP Proliant MicroServer Gen8
iLO4 Advance License installed
iLO4  IP=HOME_ILO4_IP               ( Local IP of iLO4 port,   172.24.0.xxx )

WAN Router
WNR2000 V3
DD-WRT build 24160,
Remote ssh login enabled
WAN IP=HOME_WAN_IP              ( 220.234.xxx.xxx, public IP )

 

OFFICE

Network:

Only out going 89/443 allowed via HTTP Proxy:
OFFICE_PROXY_IP : OFFICE_PROXY_PORT

Linux workstation:
Ubuntu 10.10
Open JDK v7.0      Installed
CorkScrew             Installed

 

Windows workstation:

Windows 7
putty 0.63   Installed

How to Accesss ILO4 and Remote Console

by using SSH local port forward,  From Office Workstation to Home SSH Server (Router),  we can assess iLO4 and Remote Console in Office.

 

Linux:

#!/bin/sh

# Http proxy of Corp
HTTP_PROXY_HOST=OFFICE_PROXY_IP
HTTP_PROXY_PORT=OFFICE_PROXY_PROXY

#  Home ssh server
SSH_HOST=HOME_WAN_IP
SSH_PORT=443
SSH_USER=xxxx

#  Home ILO4 Host
REMOTE_ILO_HOST=HOME_ILO4_IP
REMOTE_ILO_PORT=”22 23 17990 80 443 17988 161 162 623″

# Office Workstation  ILO4 IP
BIND_ILO_HOST=127.0.0.1
#BIND_ILO_HOST=192.168.127.8

#Generate proxy config file

ILO_SSH_PROXY_CONFIG=/tmp/ilo_ssh_config

echo “Host ${DDWRT_SSH_HOST}” > ${ILO_SSH_PROXY_CONFIG}
echo “ProxyCommand corkscrew ${HTTP_PROXY_HOST} ${HTTP_PROXY_PORT} %h %p” >> ${ILO_SSH_PROXY_CONFIG}
echo “port ${DDWRT_SSH_PORT}” >> ${ILO_SSH_PROXY_CONFIG}

echo “Host ${LINUX_SSH_HOST}” >> ${ILO_SSH_PROXY_CONFIG}
echo “ProxyCommand corkscrew ${HTTP_PROXY_HOST} ${HTTP_PROXY_PORT} %h %p” >> ${ILO_SSH_PROXY_CONFIG}
echo “port ${LINUX_SSH_PORT}” >> ${ILO_SSH_PROXY_CONFIG}

ILO_OPT_LIST=””
for p in ${REMOTE_ILO_PORT}; do
ILO_OPT_LIST=”${ILO_OPT_LIST} -L ${BIND_ILO_HOST}:${p}:${REMOTE_ILO_HOST}:${p}”
done

# Stop local services already bind to the local ILO4 Ports
sudo /etc/init.d/ssh stop
sudo /etc/init.d/lighttpd stop

# Setup SSH local forward link from Office to Home
echo “sudo ssh -N -f -F ${ILO_SSH_PROXY_CONFIG} ${ILO_OPT_LIST} ${SSH_USER}@${SSH_HOST}”
sudo ssh -N -f -F ${ILO_SSH_PROXY_CONFIG} ${ILO_OPT_LIST} ${SSH_USER}@${SSH_HOST}

SSH_PID=`pgrep -f “${ILO_OPT_LIST}”`

# Access the iLO4 via firefox browser
firefox https://${BIND_ILO_HOST}/

# Launch the Java remote console from iLO4

# cleanup,  stop the ssh local forward
sudo kill -9 ${SSH_PID}

 

Windows 7:

Config putty iLO4 session as following:

Config  Connection/Proxy/HTTP proxy

Config  Connection/SSH/Tunnels,  by add follow local port forwarding:

(BIND_ILO_HOST -> HOME_ILO4_IP)

22 23 17990 80 443 17988 161 162 623

Launch firefox,  and   goto https:// BIND_ILO_HOST  => iLO4 Panel Access

Launch  remote console/ .iNET.IRC from iLO4 panel

 

 Note:

Note:

If the PC support Intel AMT technology, you may meet the error 10013 when try to forward 623 port,
because the port 623 have been taken by the LMS.exe service:

Solution: Disable the LMS service

Launch the terminal with admin permission, and run:

sc stop “UNS”
sc stop “LMS”
Or disable it forever:

sc config “UNS” start= disabled
sc config “LMS” start= disabled

 

*********************************************

iLO 2 Advanced License Keys:
35DPH-SVSXJ-HGBJN-C7N5R-2SS4W
35SCR-RYLML-CBK7N-TD3B9-GGBW2

 

DNS software: rbldnsd

rbldnsd:
http://www.corpit.ru/mjt/rbldnsd.html

git://git.corpit.ru/rbldnsd.git

RBLDNSD :- Meaning is “DNS daemon suitable for running DNS-based blocklists”.
rbldnsd is a small DNS-protocol daemon which is designed to handle queries to DNS-based IP-listing or NAME-listing services. Such services are a simple way to share/publish a list of IP addresses or (domain) names which are “listed” for for some reason, for example in order to be able to refuse a service to a client which is “listed” in some blocklist.

http://linux.die.net/man/8/rbldnsd

 http://www.blue-quartz.com/rbl/

Example

http://www.uceprotect.net/en/?m=6&s=10

 

Setup within Debian

# Disable existed DNS service
update-rc.d bind9 disable
/etc/init.d/bind9 stop

# Install rbldnsd

setup.zip