RosettaNet簡介 報告人：關貿網路 朱啟光

前言 電子商務的發展 企業間商業標準架構應運而生 從提供型錄式資訊服務的電子商店(B2C)，演進到企業間(B2B)商業處理自動化 RosettaNet、ebXML、BizTalk。

模式一 ERP Web server Company A Internet Company B

模式二 ERP ERP Business processes, Business processes, business documents Transport, routing, packaging Business processes, business documents Transport, routing, packaging Business processes, business documents Company B Internet Company A

B2B EC的演進 商業應用程式間的交談，達成企業間商業交易 建立在標準的商業流程及商業文件之上 Business process and document integration EDI

B2B EC 標準架構 商業處理層 技術服務層 商業處理層 技術服務層 標準商業流程及商業文件， 安全可靠的溝通管道，做為上層運作的基礎 各種標準 水平整合: ebXML 產業垂直整合: RosettaNet (資訊技術、電子零組件、及半導體製造業) 技術服務架構:Vitria Framework,BizTalk Framework

ebXML 簡介 1999年9月由聯合國制定電子商務標準的組織OASIS和UN/CEFACT共同推動的企業間電子商務標準。EbXML主要任務在於提供一個開放式的XML底層架構，以利各方在安全、一致的環境下達成共通的電子商務資訊互動。 其基本訴求為使用XML技術，提供不同規模的企業間的垂直和水平整合。提供低成本的軟體製作，供中小企業之用，也顧到大企業的需求。通用性的處理程序、用語、及編碼。制定註冊機制以達成開放性及提高互通性。提供安全的遞送路徑、封包方式以確保商業訊息送收的安全。

ebXML架構說明 ebXML相容 註用及儲存庫 A B 公 公 司 司 B2B EC 架構 概念圖 4. 查訊得知並 取得A公司的商 業處理能力及 細節 2. 製作ebXML相容軟體 ebXML相容 註用及儲存庫 A B 公 公 3. 製作並登錄CPP 司 5. 向A公司請求 司 做ebXML式交 易，同意後便 進行軟體製作 6. 初使化動作過後，程式間便依之前協定進行商業交談 B2B EC 架構 概念圖

RosettaNet 一個非營利協會所制定的企業間電子商務標準 主要目的是為高科技的資訊技術、電子零組件、及半導體製造產業建立供應鏈管理體系 RosettaNet所定的B2B EC是一個具有上層商業處理與下層技術服務的整體架構 在上層商業處理方面，主要在於制定企業夥伴間標準商業處理程序 依照功能性共分成七群(cluster)核心商業處理程序，包括交易夥伴及商品資訊之收集、維護，產品資訊之分送及更新，訂單管理，庫存管理，市場資訊管理，售後服務及支援，製造資訊之交換 每一群又分成幾個段(segment)，每段含有幾個夥伴間程序介面(partner interface process, PIP) 每個PIP定義程式對程式間以XML標準商業文件為基礎的對話程序

抽象概念

RosettaNet 從商業運作的角度來看，一個PIP主要內容是特定的商業工作流程及其流程中所帶動的文件 商業資訊決策系統 為求文件一致， RosettaNet定義了商業和技術字典，前者為提供商業詞彙，後者為各行業的技術用語 需求處理 形成回應文件 成功 失敗 RosettaNet制定了RNIF (RosettaNet Implementation Framework) ，當中定義了工作平台間訊息交換協定(protocol)，以支應上層PIP在文件遞送上的基礎 形成需求文件 回應處理 買方 賣方 PIP 商業資訊決策系統

RosettaNet 對照前面ebXML的架構，RosettaNet提供完整的商業處理程序及工作平台 RosettaNet並不制定註冊機制及CPP/CPA，因此在商業夥伴的探索及建立夥伴關係上必須靠人工達成 UDDI(Universal Description, Discovery Integration) by IBM, Microsoft and Ariba 另一個B2B EC標準Vitria Framework則是制定了相當於RNIF角色的下層技術服務

RosettaNet 宗旨及任務 宗旨 任務 Dynamic, flexible trading networks Operational efficiency New business opportunities 任務 促進網際網路商業標準的合作發展及快速建置 創造共通的商業語言及開放式的電子化商業程序，為全球高科技交易網路帶來利益及提昇演進的腳步

什麼是RosettaNet RosettaNet是由超過400家資訊技術業、 電子零組件業、及半導體製造業廠商所組成的協會，共創及推廣開放式的電子標準商業程序 RosettaNet名稱是以the Rosetta Stone而得名 RosettaNet創造電子商務標準語言，包括商業程序及商業文件 促成供應鏈電子化 建立有彈性的交易夥伴關係 降低成本、提昇產量

什麼是RosettaNet標準內容 RosettaNet標準是集合高科技公司的專業知識，共創而成的非獨占性的電子商務方案，其內容包括 商業及技術字典 RosettaNet Business Dictionary、RosettaNet Technical Dictionary 下層技術服務架構 RosettaNet Implementation Framework (RNIF) 商業訊息及程序規範 RosettaNet Partner Interface Processes™(PIPs™) 以上標準規範可由www.rosettanet.org免費取得

概念說明 一 交易夥伴 備妥內容 放入信封 送出 提出需求的交易夥伴準備好商業文件，載明需求內容

概念說明 二 交易夥伴 備妥內容 放入信封 送出 備妥的商業文件包裝成XML及MIME規格做成的傳輸信封內

概念說明 三 交易夥伴 備妥內容 放入信封 送出 用預定的埠際協定(HTTP(s)、SMTP等)送到交易夥伴的URI

概念說明 四 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 備妥內容 收文 Trading Partner 交易夥伴收到信件

概念說明 五 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 備妥內容 收文 Trading Partner 解開以檢驗信封內的處理資訊及商業文件是否正確

概念說明 六 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 備妥內容 收文 Trading Partner 根據RosettaNet規範處理驗證過後的商業文件及程序

概念說明 七 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 備妥內容 收文 Trading Partner 將回應的內容以信封包裝後回覆 備妥內容 放入信封 送出 收文 解開信封 處理內容 Trading Partner Trading Partner

概念說明 八 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 備妥內容 收文 交易夥伴間以此模式，依照RosettaNet規範繼續交談直到完成商業程序 備妥內容 放入信封 送出 收文 解開信封 處理內容 Trading Partner Trading Partner

RosettaNet技術組件 Partner Interface Processes (PIPsTM) Dictionaries and Codes RosettaNet Implementation Framework (RNIF) Core

技術組件-PIP 整合式的商業程序，其中規範了 商業文件的結構及格式 參與商業活動的交易夥伴的活動、決策、及角色扮演

技術組件-PIP 分類方式是依照高階商業功能(cluster)及次功能(segment)而訂 Cluster 3: Transaction and Distribution Segment B : Transportation and Distribution PIP 3B3 – Distribute Shipment Status PIP 3B4 – Query Shipment Status PIP 3B18 – Notify of Shipment Documentation Segment A : Quote and Order Entry Segment C : Returns and Finance

技術組件-PIP PIP規範是可供下載的.zip檔放在Rosettanet網站，內容包括 規格書(.doc) + 勘誤表 XML DTD說明商業文件的結構內容 訊息使用說明 編碼、定義、訊息出現次數

技術組件-PIP 規範是遵循Open-EDI Reference Model (ISO/IEC 14662)的概念制定而成，包括 商業運作觀點(Business Operational View, BOV) 以商業角度看待商業交易 功能服務觀點(Functional Service View, FSV) 以技術角度看待商業交易 製作架構觀點(Implementation Framework View, IFV) RosettaNet下層技術服務製作的架構

PIP摘要 解開信封 放入信封 處理內容 送出 PIP規定一個特定商業活動商業文件的結構及格式 商業文件表示成XML文件 交易夥伴 交易夥伴 備妥內容 放入信封 送出 收文 解開信封 處理內容 Trading Partner Trading Partner PIP也規定交易夥伴間交換文件的協定

技術組件 - 字典 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 備妥內容 收文 Trading Partner

標準碼 交易夥伴識別號 (DUNS®)

標準碼使用時機 交易夥伴識別號(DUNS®) PIPsTM 用來識別交易夥伴及其位址

交易夥伴的識別 DUNS® Numbering “Data Universal Numbering System” Managed by DUN and Bradstreet (www.dnb.com) Nine Digit Number No Embedded Intelligence Guaranteed Unique Partner Identifier Used in Every RosettaNet PIPTM

範例 00-825-575 4 ------------- - | | | ----> Check Digit | ------------- - | | | ----> Check Digit | ---------------> Company Identification

Network Component Communications Reference Model 總覽 Common Dictionary Common AdminPIPs POLICY Common PIPs PKI TPA Compliance SPECS. IT Specific Dictionary and PIPs Network Protocols Base Spec. PIP Metamodel PIP Design patterns Network Component Communications Reference Model ARCHITECTURE EC Specific RNIF LAYERS Core Common Supply Chain

RNIF簡介 RosettaNet Implementation Framework Core RNIF (usually pronounced R-NIF) RNIF 1.1 Defines RosettaNet Object (RNO), RNIF 2.0 Defines RosettaNet Business Message Specifies how to transport RosettaNet Objects and Business Messages between trading partners’ network applications (Remember those PIPsTM? This is how the Business Document Payload is packaged and transported.)

RNIF 解開信封 放入信封 處理內容 送出 交易夥伴 交易夥伴 RNIF制定以XML及MIMI為依據的“信封套”，以便放入商業文件 備妥內容 放入信封 送出 收文 解開信封 處理內容 Trading Partner Trading Partner

RNIF比較 RNIF 1.1 RNIF 2.0 Attach- ments RosettaNet Business Document PIPTM1B1 PIP2A1 PIP3B3 PIP3B4 RNIF 1.1 RNIF 2.0 Attach- ments RosettaNet Business Document Service Content Preamble Header Service Header Service Header + + + + MIME Packaging S/MIME Envelope Encrypted Payload Container RNIF Version ID Service Message Digital Signature Preamble Header Delivery Header Digital Signature + + + + + MIME Packaging RosettaNet Object (RNO) RosettaNet Business Message

The Preamble is the first component of the service message and contains elements that are global to the RosettaNet service and elements that are common to the Service Header and the Service Content. The Preamble Header is an XML document. PIPTM1B1 PIP2A1 PIP3A2 PIP3A4 RNIF 1.1 RNIF 2.0 Attach- ments RosettaNet Business Document Service Content Preamble Header Service Header Service Header + + + + MIME Packaging S/MIME Envelope Encrypted Payload Container RNIF Version ID Service Message Digital Signature Preamble Header Delivery Header Digital Signature + + + + + MIME Packaging RosettaNet Object (RNO) RosettaNet Business Message

RNIF 1.1 RNIF 2.0 The Service Header contains: Process Controls Transaction Controls Action Controls Signal Controls The Service Header is an XML document. PIPTM1B1 PIP2A1 PIP3A2 PIP3A4 RNIF 1.1 RNIF 2.0 Attach- ments RosettaNet Business Document Service Content Preamble Header Service Header Service Header + + + + MIME Packaging S/MIME Envelope Encrypted Payload Container RNIF Version ID Service Message Digital Signature Preamble Header Delivery Header Digital Signature + + + + + MIME Packaging RosettaNet Object (RNO) RosettaNet Business Message

RNIF Process Controls identify the RosettaNet PIPTM, version, sender and receiver services, process instance ID, etc. Transaction Controls contain info relating to the transaction like global transaction code, instance ID, etc. Action Controls contain info related to a specific PIP action. (like is this request or response) Signal Controls contain info related to a specific PIP signal. (like what kind of signal is this)

Ubiquitous Communications e-Business Communications RNIF OSI Layered Ubiquitous Communications Reference Model Internet and WWW Protocol Stack RosettaNet Layers e-Business Communications Network Layer Data Link Layer Physical Layer Application Layer Session Layer Transport Layer HTTPS SSLv3 TCP/IP HTTP Process Layer Transfer Layer Agent Layer Service Layer Security Layer Action/Signal Layer Transaction Layer

The RosettaNet Business Document or Service Content is the business document payload as defined by a particular PIP. Under RNIF 2.0, it may refer to attachments or consist of non-RosettaNet content. The RosettaNet Business Document is an XML document. RosettaNet Object (RNO) Service Header Preamble Header + Digital Signature RNIF Version ID PIPTM1B1 PIP2A1 PIP3A2 PIP3A4 MIME Packaging Service Message RosettaNet Business Message Encrypted Payload Container Delivery Header S/MIME Envelope RNIF 1.1 RNIF 2.0 Attach- ments Service Content RosettaNet Business Document

Technical Components - RNIF MIME-Version: 1.0 Content-Type: Multipart/Related; boundary="RN-part-boundary"; type="Application/x-RosettaNet“ Content-Description: This is the RosettaNet business message --RN-part-boundary Content-Type: Application/XML; RNSubType="preamble-header" Content-Description: This is the Preamble Header part of the business message [The Preamble Header goes here] Content-Type: Application/XML; RNSubType="service-header" Content-Description: This is the Service Header part of the business message [The Service Header goes here] RNSubType="service-content" Content-Description: This is the Service Content [The Business Content goes here] --RN-part-boundary-- Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header + Digital Signature RNIF Version ID PIP1B1 PIP2A1 PIP3A2 PIP3B4 MIME Packaging Service Message RosettaNet Business Message Encrypted Payload Container Delivery Header S/MIME Envelope RNIF 1.1 RNIF 2.0 Attach- ments Service Content RosettaNet Business Document

RNIF 1.1 RNIF 2.0 MIAGCSqGSIb3DQEHA6CAMIACAQAxgDCCASAC MIME-Version: 1.0 Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=smime.p7m MIAGCSqGSIb3DQEHA6CAMIACAQAxgDCCASAC AQAwgYgwgYIxCzAJBgNVBAYTAlVTMRMwEQYD VQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhN b25yb3ZpYTEMMAoGA1UEChMDU1RDMRQwEgYD VQQLEwtEZXZlbG9wbWVudDEnMCUGA1UEAxMe U1RDIFRlc3QgQ2VydGlmaWNhdGUgQXV0aG9y aXR5AgECMA0GCSqGSIb3DQEBAQUABIGADytB 2IkYlPqgivlcnQiCPJxWDcshCKUaOm9/k07d etAfX0f1LaEA23qFolSmevKrNZcUlMfm32HT UdZQpHj9Iy8da5GNI9OW+5EB7W7XoiJgyfeD 6m2X3UfwnPJJUnOlC6klVBzpalFHXOw5rK2Z eGIGjiPiIq4p1DmkKlfLle4wggEgAgEAMIGI MIGCMQswCQYDVQQGEwJVUzETMBEGA1UECBMK Q2FsaWZvcm5pYTERMA8GA1UEBxMITW9ucm92 ... RosettaNet Object (RNO) Service Header Preamble Header + Digital Signature RNIF Version ID PIPTM1B1 PIPTM2A1 PIPTM 3A2 3B4 MIME Packaging Service Message RosettaNet Business Message Encrypted Payload Container Delivery Header S/MIME Envelope RNIF 1.1 RNIF 2.0 Attach- ments Service Content RosettaNet Business Document

RosettaNet Object (RNO) Service Header Preamble Header + Digital Signature RNIF Version ID PIPTM 1B1 PIP2A1 PIP3A2 PIP3A4 MIME Packaging Service Message RosettaNet Business Message Encrypted Payload Container Delivery Header S/MIME Envelope RNIF 1.1 RNIF 2.0 Attach- ments Service Content RosettaNet Business Document The version ID identifies RosettaNet Implementation Framework version for interoperability purposes. Part of the RNIF 2.0 Preamble Header serves the same purpose.

The RosettaNet Object is created by concatenating the Version ID, Service Message, Signature Length and Signature. The RosettaNet Object is sent to the trading partner using HTTPS … RosettaNet Object (RNO) Service Header Preamble Header + Digital Signature RNIF Version ID PIPTM 1B1 PIPTM 2A1 PIP3A2 PIP3B4 MIME Packaging Service Message RosettaNet Business Message Encrypted Payload Container Delivery Header S/MIME Envelope RNIF 1.1 RNIF 2.0 Attach- ments Service Content RosettaNet Business Document

…while the RosettaNet Business Message wraps everything using standard MIME packaging. The RosettaNet Business Message may be sent using HTTP, HTTPS or SMTP (other protocols to be specified in the future). RosettaNet Object (RNO) Service Header Preamble Header + Digital Signature RNIF Version ID PIPTM 1B1 PIP2A1 PIP3A2 PIP3B4 MIME Packaging Service Message RosettaNet Business Message Encrypted Payload Container Delivery Header S/MIME Envelope RNIF 1.1 RNIF 2.0 Attach- ments Service Content RosettaNet Business Document

RNIF 2.0 Support for multiple transfer protocols Transfer-independent message format (MIME & S/MIME) Support for both SMTP and HTTP(S) FTP, message queues, and others in the future Transfer-level headers for debugging

RNIF 2.0 Support for end-to-end and persistent encryption S/MIME-based packaging for digital signatures and content enveloping Support for attachments and message manifest Support for 3rd party (hub-based) routing (due to Delivery Header)

3B18 RN3B18 is to carry elements of “Invoice” and “Packing List” to the other party for declaration and cargo documents. “Invoice” is for billing to the buyer. “Packing List” tells the consignee how to pack the cargo (including the information of dimension, weight, pieces, packing method….). Invoice No. ：Packing List No. = 1 ：　　1 (generic) = n ：　　1 (specific)

續 1:N 1:M ShipmentKey PackingListNo InvoiceNo p.s. N, M > 0 Generic -- As per shipper’s request A shipment is grouped by pre-assigned HAWB by internal serial number

續 PAK-B PAK-A INV-1 INV-2 RN3B18 TYPE A TYPE B Packing List for

3B18 PIP 使用對象 Electronic Components (EC) Information Technology (IT) Semiconductor Manufacturing (SM)

3B18 BOV 參與角色 Seller Buyer 3PL or 4PL

3B18 BOV 內容 Bill of Landing Commercial Invoice Packing List …

3B18 BOV

3B18 FSV

3B18 IFV Table 5‑1: Business Message and Communications Specification # Business Message Guideline Digital Signature Required? SSL[1] Required? 1. Shipping Documentation Notification Guideline Y 1.1. Receipt Acknowledgment Guideline

應用範例 流程 出貨 指示 取貨 訂艙 資訊 進倉 國內 清關 起飛 到達 國外 清關 到貨 簽收 訊息 3B18 N/A 3B3 3B3 文件 N/A 托運單 報單 艙單 簽收單 (POD) Invoice No. Packing List 進倉計畫 提供者 Shipper N/A 承攬業 報關業 航空公司 通關網/ Overseas Agents 交換 對象 承攬業者 N/A 貨棧 貨棧 Shipper 海關 目的地 海關 Shipper 承攬業 Shipper 承攬業

3B3,3B4 PIP 使用對象 Electronic Components (EC) Information Technology (IT)

3B3 BOV The "Distribute Shipment Status" Partner Interface Process™ (PIP) enables a transport service provider to distribute shipment status information to another party, such as a consignee, a third-party logistics firm, a shipper, or another transport service provider.

應用範例 流程 出貨 指示 取貨 訂艙 資訊 進倉 國內 清關 起飛 到達 國外 清關 到貨 簽收 訊息 3B18 N/A 3B3 3B3 文件 N/A 托運單 報單 艙單 簽收單 (POD) Invoice No. Packing List 進倉計畫 提供者 Shipper N/A 承攬業 報關業 航空公司 通關網/ Overseas Agents 交換 對象 承攬業者 N/A 貨棧 貨棧 Shipper 海關 目的地 海關 Shipper 承攬業 Shipper 承攬業 3B4由shipper主動對Hub或LSP發出查詢貨況

3B3 BOV

3B3 SFV

3B4 The "Query Shipment Status" Partner Interface Process™ (PIP) enables (1) a party, such as a consignee, third-party logistics firm, or shipper, to query for the status of one or more shipments, and (2) a transport service provider to answer the query.

3B4 BOV

3B4 FSV

3B3 & 3B4

挑戰 There are many “standards” from which to choose. The specifications are being improved, which means they are changing. Some aspects of the specifications are ambiguous. The readability of the existing documentation needs to be improved. The enterprise readiness effort for RosettaNet implementations is often underestimated.

導入準則 Base on “Shipping & Logistics for IT Manufacture Project(SLIM) for Plan D”

導入準則

測試進程 Level 0:Partner Engagement Level 1:Connectivity Level 2:Syntax & Domain Value Checking Level3 : Data Content Validation

SAP R/3 IDOC Connector SAPR3 IDoc Source Connector SAPR3 IDoc Target Connector Both implement SAP’s tRFC protocol

SAPR3 IDoc Source Connector Receive IDOCs from a SAP/R/3 system Generate BusinessWare events (String) Send to Record Mapper Convert it into IDL events (by using MTDParser) Pushs it to the Channel Target flow to publish to channels

SAPR3 IDoc Target Connector A multi-threaded Subscriber flow receives IDL events Record Mapper converts it into String event IDOC target flow converts the events into IDOCs and pushes them to SAP/R3