ORTB
中 / EN

Device§3.2.18 · Bid Request

Device 对象用于描述用户当前进行交互所使用的设备的相关信息。设备信息涵盖其硬件、平台、地理位置(location)以及运营商(carrier)相关数据。此处所述的设备可以指代移动电话(mobile handset)、台式计算机、机顶盒(set top box)或其他数字设备。译稿校对中ENThis object provides information pertaining to the device through which the user is interacting. Device information includes its hardware, platform, location, and carrier data. The device can refer to a mobile handset, a desktop computer, set top box, or other digital device.

AttributeTypeDescription
ua
string用户代理(User Agent)字符串,即浏览器标识。ENBrowser user agent string.
geo
object设备的地理位置,假定为用户当前位置,由 Geo 对象定义(参见第 3.2.19 节)。ENLocation of the device assumed to be the user’s current location defined by a Geo object (Section 3.2.19).
dnt
integer请勿追踪(Do Not Track,DNT)标志,由浏览器在请求头中设置:0 = 追踪不受限制,1 = 请勿追踪。ENStandard “Do Not Track” flag as set in the header by the browser, where 0 = tracking is unrestricted, 1 = do not track.
lmt
integer限制广告追踪(Limit Ad Tracking,LAT)信号,由商业平台背书(commercially endorsed,如 iOS、Android):0 = 追踪不受限制,1 = 须按商业平台指引限制追踪。EN“Limit Ad Tracking” signal commercially endorsed (e.g., iOS, Android), where 0 = tracking is unrestricted, 1 = tracking must be limited per commercial guidelines.
ip
string距离设备最近的 IPv4 地址。ENIPv4 address closest to device.
ipv6
string距离设备最近的 IP 地址(IPv6 格式)。ENIP address closest to device as IPv6.
devicetype
integer设备大类。参见列表 5.21(List 5.21)。ENThe general type of device. Refer to List: Device Types in AdCOM 1.0.
枚举 Device Types · 8 个值
1Mobile/Tablet - General
2Personal Computer
3Connected TV
4Phone
5Tablet
6Connected Device
7Set Top Box
8OOH Device
make
string设备制造商(如 “Apple”)。ENDevice make (e.g., “Apple”).
model
string设备型号(如 “iPhone”)。ENDevice model (e.g., “iPhone”).
os
string设备操作系统(如 “iOS”)。ENDevice operating system (e.g., “iOS”).
osv
string操作系统版本(Operating System Version,如 “3.1.2”)。ENDevice operating system version (e.g., “3.1.2”).
hwv
string硬件版本(Hardware Version,如 iPhone 5S 对应 “5S”)。ENHardware version of the device (e.g., “5S” for iPhone 5S).
h
integer屏幕物理高度,单位为像素。ENPhysical height of the screen in pixels.
w
integer屏幕物理宽度,单位为像素。ENPhysical width of the screen in pixels.
ppi
integer屏幕尺寸,以每线性英寸像素数(Pixels Per Inch)表示。ENScreen size as pixels per linear inch.
pxratio
float物理像素与设备无关像素(device independent pixels)的比值。ENThe ratio of physical pixels to device-independent pixels (DIPS).
js
integer是否支持 JavaScript:0 = 否,1 = 是。ENSupport for JavaScript, where 0 = no, 1 = yes.
geofetch
integer指示 banner 广告中运行的 JavaScript 代码是否可以使用地理位置 API(geolocation API):0 = 否,1 = 是。ENIndicates if the geolocation API will be available to JavaScript code running in the banner, where 0 = no, 1 = yes.
flashver
string浏览器支持的 Flash 版本。ENVersion of Flash supported by the browser.
language
string浏览器语言,采用 ISO-639-1-alpha-2 编码。ENBrowser language using ISO-639-1-alpha-2. Only one of language or langb should be present.
carrier
string运营商或互联网服务提供商(ISP)(如 “VERIZON”)。取值为交易平台(exchange)预先整理(curated)的字符串名称,该名称列表应事先向竞价方(bidder)公布。ENCarrier or ISP (e.g., “VERIZON”) using exchange curated string names which should be published to bidders a priori.
mccmnc
string以移动国家码–移动网络码(MCC–MNC)拼接编码表示的移动运营商(如 “310-005” 标识美国的 Verizon Wireless CDMA 网络)。更多示例参见 https://en.wikipedia.org/wiki/Mobile_country_code。注意:MCC 与 MNC 两部分之间的连字符为必需,用于消除解析歧义。ENMobile carrier as the concatenated MCC-MNC code (e.g., “310-005” identifies Verizon Wireless CDMA in the USA). Refer to https://en.wikipedia.org/wiki/Mobile_country_code for further examples. Note that the dash between the MCC and MNC parts is required to remove parsing ambiguity. The MCC-MNC values represent the SIM installed on the device and do not change when a device is roaming. Roaming may be inferred by a combination of the MCC-MNC, geo, IP and other data signals.
connectiontype
integer网络连接类型。参见列表 5.22(List 5.22)。ENNetwork connection type. Refer to List: Connection Types in AdCOM 1.0.
枚举 Connection Types · 7 个值
1Ethernet; Wired Connection
2WIFI
3Cellular Network - Unknown Generation
4Cellular Network - 2G
5Cellular Network - 3G
6Cellular Network - 4G
7Cellular Network - 5G
ifa
string广告主用标识符(Identifier for Advertisers,IFA),经平台许可供广告主使用,以明文(in the clear,即未经哈希处理)传递。ENID sanctioned for advertiser use in the clear (i.e., not hashed)
Unless prior arrangements have been made between the buyer and the seller directly, the value in this field is expected to be an ID derived from a call to an advertising API provided by the device’s Operating System.
didsha1
string硬件设备 ID(Device ID,如 IMEI),经 SHA1 哈希处理。ENDeprecated as of OpenRTB 2.6.
didmd5
string硬件设备 ID,经 MD5 哈希处理。ENDeprecated as of OpenRTB 2.6.
dpidsha1
string平台设备 ID(Device Platform ID,如 Android ID),经 SHA1 哈希处理。ENDeprecated as of OpenRTB 2.6.
dpidmd5
string平台设备 ID,经 MD5 哈希处理。ENDeprecated as of OpenRTB 2.6.
macsha1
string设备 MAC 地址,经 SHA1 哈希处理。ENDeprecated as of OpenRTB 2.6.
macmd5
string设备 MAC 地址,经 MD5 哈希处理。ENDeprecated as of OpenRTB 2.6.
ext
object供交易平台对 OpenRTB 进行专属扩展(exchange-specific extensions)的占位对象。ENPlaceholder for exchange-specific extensions to OpenRTB.

最佳实践(Best Practice)

官方规范

目前业界尚无具备影响力的开源列表可用于设备制造商(make)、型号(model)、操作系统(os)或运营商(carrier)属性。交易平台通常采用商业产品或其他自有列表来定义这些属性。在合适的开放标准出现之前,规范强烈建议交易平台将其使用的设备制造商、型号、操作系统及运营商取值列表事先公布给竞价方。译稿校对中ENThere are currently no open source lists available for device make, model, operating system, or carrier attributes. Exchanges typically use commercial products or other proprietary lists to define these attributes. Until a suitable open standard is available, exchanges are strongly encouraged to publish to bidders the device make, model, operating system, and carrier lists that they use.

在移动端正确判定设备 IP 并非易事。典型做法是:从 x-forwarded-for 请求头的最左侧开始读取,跳过运营商私有网段(如 10.x.x.x 或 192.x.x.x),必要时还需比对已知的运营商 IP 段。规范敦促交易平台在向竞价方透出设备 IP 取值之前,务必仔细研究并实现该逻辑。译稿校对中ENCorrectly determining the IP address of a device in the mobile world is not always simple. It is typical to start with the left-most address in the x-forwarded-for header, skipping private network addresses (e.g., 10.x.x.x or 192.x.x.x), and potentially comparing against known carrier IP ranges. Exchanges are urged to carefully research and implement this logic before exposing the device IP address to bidders.

译注

译者注

Device:OpenRTB 2.5 中该对象通常作为 BidRequest 的子对象传递,字段定义见规范第 3.2.18 节。业内文档中一般保留英文对象名 Device,便于与协议字段对照。译稿校对中

platform:此处指设备运行的平台环境(如操作系统、运行环境),而非媒体平台(Platform 在不同上下文含义不同,注意区分)。译稿校对中

location:指设备侧获取的地理位置信息(经纬度),通常由 Geo 对象承载,与 IP 推断位置有所区别。译稿校对中

carrier(对象级):特指移动网络运营商(如中国移动、Verizon),对应字段为 Device.carrier,取值为运营商 ID(通常来自 Mobile Carrier List)。译稿校对中

mobile handset:译为“移动电话/移动手持设备”,业界口语常称“移动端”,但规范译文中建议保持术语严谨。译稿校对中

dnt vs lmt:dnt 对应 W3C 的 Do Not Track 标准(源自浏览器 DNT 头),是 Web 侧的通用信号;lmt 对应移动操作系统层面的“限制广告追踪”开关(iOS 的 Limit Ad Tracking、Android 的 Opt out of Ads Personalization),二者来源不同、不可混用。如今在 ATT / 隐私合规语境下,lmt 常与 ifa 是否可用联动判断。译稿校对中

ifa:即 IDFA / GAID(AAID)这类广告标识符。“sanctioned” 强调该标识是经平台许可、专为广告用途设计的,这也是它与 did、dpid 等硬件/平台标识在合规属性上的根本区别。译稿校对中

*did vs dpid***:did(device ID)指硬件级标识,如 IMEI;dpid(device platform ID)指操作系统平台级标识,如 Android ID。两者均要求以哈希值传递,与 ifa 的明文形成对照。注意:随着 iOS 14.5+ 与 Android 隐私沙盒推进,上述多数标识在实际投放中已基本退出使用,但协议字段仍然保留。译稿校对中

mccmnc:MCC(移动国家码)+ MNC(移动网络码)是标识运营商网络的最精确方式,carrier 字段是字符串化的简化表达。连字符 “-” 是硬性格式要求,解析时不可省略。译稿校对中

carrier(字段级):此处的取值并非自由文本,而是交易平台维护的受控词表(curated string names),必须事先同步给竞价方,否则会造成数据口径不一致——这也是最佳实践第一段反复强调公布列表的原因。译稿校对中

pxratio:即业界常说的“设备像素比”(DPR),如 iPhone Retina 屏通常为 2 或 3。与 h / w(物理像素)配合,可换算出逻辑分辨率,用于创意素材适配。译稿校对中

geofetch:特指 banner 创意内的 JS 能否调用浏览器的地理位置 API(如 navigator.geolocation),与 Device.geo(交易所侧下发的定位)是两回事。译稿校对中

x-forwarded-for:代理链路中记录客户端 IP 的标准请求头,格式为逗号分隔的 IP 序列。移动端流量常经运营商 CGNAT(运营商级 NAT),最左侧 IP 可能是内网地址,故规范给出“从左向右跳过私有网段”的判定建议。译稿校对中

ext:OpenRTB 各层对象均保留的 ext 扩展位,用于承载协议未定义的平台私有字段,解析时建议做容错处理。译稿校对中

字段描述已与 2.6 官方 draft 对账;2.5 独有字段来自第三方 Go 实现源(Apache 2.0),官方 PDF 兜底校对 · 初稿校对中