PIDX PIP Specification. P22: Send Invoice Response. Version 1.0
|
|
- Nelson McDonald
- 5 years ago
- Views:
Transcription
1 PIDX PIP Specification P22: Send Invoice Response Version 1.0 July 9, 2014
2 Table of Contents Document Version History Introduction Document Purpose Document Conventions Intended Audience References PIDX XML Transaction Standards, version RosettaNet Implementation Framework, version 2.0 (RNIF2) PIDX Dictionary Framework Other References Scope Send Invoice Response Partner Interface Process PIP Roles PIP Activities PIP P22 Business Rules and Constraints Data Requirements Optional Service Content Data Service Header Data Fundamental Business Data Entities inreplyto Business Signals Scope of Business Signals Base-level Validation Rules Process Control TRP requirements PIDX RNIF PIP Specification P22 Page 2 of 15 PIDX PIP P22 Invoice Response v1_0
3 6.1 Transport security Routing PIDX RNIF PIP Specification P22 Page 3 of 15 PIDX PIP P22 Invoice Response v1_0
4 Document Version History Date Version Author(s) Description 18 Mar Darren Ebanks, Rick Conner, Gary Strickland SLB internal Trading Partner Integration Process 20 Feb 2013 Draft John Stukes Updated PIP content 30 Jan Gary Strickland, Rick Conner, Larry Dyer Updated PIP content 20 Jun Gary Strickland Added PIP content 24 Jun Rick Conner, Larry Dyer, Darren Ebanks, Gary Strickland 1 Jul Rick Conner, Larry Dyer, Darren Ebanks, Gary Strickland 9 Jul Darren Ebanks, Paul O Shaughnessy, Gary Strickland Edited PIP for completeness, accuracy, and readability Added content Edited for completeness, accuracy, and readability PIDX RNIF PIP Specification P22 Page 4 of 15 PIDX PIP P22 Invoice Response v1_0
5 1 Introduction 1.1 Document Purpose Partner Interface Process (PIP) P22 Send Invoice Response is used with the PIP P21 Send Invoice to align a seller s invoicing process with a buyer s accounts payable process. This PIP specification provides information necessary to accomplish that alignment: Trading partner business roles Business activities executed by the roles The type and sequence of business documents exchanged by the role interactions while executing these activities The time, security, authentication, and performance constraints of these interactions The PIP specification focuses on the public business processes buyers and sellers use to create, transform, transmit, and process invoice response action messages. The specification does NOT identify the invoice response action message payload requirements; the buyer and seller MUST agree on payload requirements, and those requirements MUST be included in the seller s invoice response implementation guide. The trading partners executing the Send Invoice Response PIP must understand the processes in order to determine how trading partner data requirements can be addressed. 1.2 Document Conventions The Send Invoice Response PIP specification adopts the conventions expressed in the Internet Engineering Task Force s (IETF) Request for Comments (RFC) 2119 Key Words for Use in RFCs to Indicate Requirement Levels. The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC Intended Audience The targeted audience of the Send Invoice Response PIP specification includes trading partner technical and business personnel with the responsibility to align invoicing and accounts payable systems, as well as third party technology providers facilitating that alignment. 1.4 References The Send Invoice Response PIP specification relies on information in RosettaNet Implementation Framework, version 2.0 (RNIF2) and PIDX standards (Implementation Guide, Dictionary Framework, schemas, message guidelines). Users of the Send Invoice Response PIP specification MUST understand the content and purpose of the related documents. PIDX RNIF PIP Specification P22 Page 5 of 15 PIDX PIP P22 Invoice Response v1_0
6 1.4.1 PIDX XML Transaction Standards, version 2.0 PIDX XML Transaction standards consist of the standards master, the implementation guidelines, dictionaries, schemas, header message guidelines, and PIP specifications. Those documents should be considered integral parts of this PIP specification. The Send Invoice Response PIP specification does not restate material from referenced documents unless restatement adds clarity to the specification. There may be multiple versions of the invoice response schema. Trading partners implementing this PIP must agree on the version of invoice response schema that a buyer will use to send an invoice response to a seller. The invoice response schema used in the Send Invoice Response PIP MUST be identified in the seller s implementation guide RosettaNet Implementation Framework, version 2.0 (RNIF2) RNIF2 describes the transport, routing, and packaging (TRP) data and processing requirements. The PIDX XML Transaction Standards version 2.0 are based on RNIF2, but do not restate them. Accordingly, to understand how to execute the Send Invoice Response PIP, trading partners MUST have a solid understanding of RNIF2 and how the PIDX standards restrict that framework PIDX Dictionary Framework The PIDX standards use the XML Data Dictionary created in the PIDX XML Transaction Standards, version 1.0 to define service content XML elements: Data Dictionary V1-0.xls The elements in the message headers are defined in the following PIDX message guidelines: Preamble: PIDXPreambleMessageGuidelineV1_0.html Delivery Header: PIDXDeliveryHeaderMessageGuidelineV1_0.html Service Header: PIDXServiceHeaderMessageGuidelineV1_0.html Other References In addition to standards and specifications described above, trading partners implementing the Send Invoice Response PIP should be familiar with the following specifications and standards: XML 1.0 and W3C XML Schema The PIDX invoice response schema version agreed to by trading partners executing the Send Invoice Response PIP The PIDX library schema version agreed to by the trading partners executing the Send Invoice Response PIP General Internet protocols Encryption standards MIME and S/MIME Digital signatures and the Secure Socket Layer (SSL) PIDX RNIF PIP Specification P22 Page 6 of 15 PIDX PIP P22 Invoice Response v1_0
7 Buyer and seller process, data and TRP requirements and restrictions 1.5 Scope The Send Invoice Response PIP describes the processes and choreography to send an invoice response and acknowledge its receipt and processing status. To initiate an instance of the Send Invoice Response PIP, the buyer must have received and processed internally a PIDX invoice action message. The PIDX PIP P21: Send Invoice specification describes the roles, activities, and processes involved in sending an invoice action message to a buyer. Those processes are out of scope in the Send Invoice Response PIP. The Send Invoice Response PIP payload requirements are not described in this PIP specification. The invoice response payload requirements of the seller are described in the seller s invoice response implementation guide. 2 Send Invoice Response Partner Interface Process The Send Invoice Response Partner Interface Process (PIP) is used in aligning a seller s invoicing process with the buyer s payment approval process. There are two types of business processes involved in the PIP: private processes, and public processes. Private processes are business processes internal to each trading partner. Public processes are business processes that involve interactions with trading partners. The sequence diagram in figure 1 shows the relationship between public and some well-known private processes. While PIDX PIPs focus on public processes, private and public processes are interdependent. Accordingly, the Send Invoice Response PIP references private processes when those references provide clarity to the Send Invoice Response PIP. PIDX RNIF PIP Specification P22 Page 7 of 15 PIDX PIP P22 Invoice Response v1_0
8 Figure 1: Send Invoice Response PIP public and private processes The use case diagram in figure 2 shows the trading partner roles in the Send Invoice Response PIP, and the required activities (public processes) each role must execute. Figure 2: Send Invoice Response PIP trading partner roles and required activities PIDX RNIF PIP Specification P22 Page 8 of 15 PIDX PIP P22 Invoice Response v1_0
9 2.1 PIP Roles PIDX PIPs are based on a peer-to-peer message exchange model: Messages are exchanged between two trading partners: a buyer and a seller. The involvement of third parties to facilitate the exchange does not change the peer-to-peer message exchange model. Accordingly, the only roles described in the Send Invoice Response PIP are those of a buyer and a seller. 2.2 PIP Activities There are three required activities in the Send Invoice Response PIP: 1. The buyer sends an invoice response action message to the seller 2. The buyer and the seller validate syntax and structure of inbound messages (base-level validation) 3. The seller sends a business signal message to the buyer All other processes in the Send Invoice Response PIP are private processes. 3 PIP P22 Business Rules and Constraints Trading partners executing the Send Invoice Response PIP must agree on the business rules and process constraints for the PIP. The business rules that MUST be agreed to by the trading partners are listed in Table 1. The buyer and seller MAY add business rules and constraints not included in this list. Non-repudiation required Time to acknowledge Retry count limit for technical failures Business rule/constraint Authorization required to send invoice response Non-repudiation of origin and content Secure transport required Payload encryption required Validation limited to message syntax, structure (base-level validation) Payload will be validated against seller s business rules and data requirements before sending a business signal (content-level validation) Required value hh:mm:ss 0 count limit PIDX RNIF PIP Specification P22 Page 9 of 15 PIDX PIP P22 Invoice Response v1_0
10 URL to which the buyer must send the PIDX invoice response action message URL URL to which the seller must send the PIDX business signal message SSL required Server certificate required to for buyer to identify seller server Buyer certificate required to identify the buyer URL Table 1: Send Invoice Response business rules 4 Data Requirements Payload data requirements are specified in the seller s implementation guide. There may be multiple versions of the XML schemas controlling the structure and syntax of the Send Invoice Response PIP service content. The buyer and the seller MUST agree on which version of the PIDX library and the invoice response schema to use. The schemas agreed to by the buyer and seller MUST be published in the seller s Send Invoice Response Implementation Guidelines. The PIDX XML Transaction Standards define many optional information items in the PIDX schemas that control the structure, syntax, and required content of the invoice response service content. The buyer and seller MUST agree on which of the elements are required, and which are conditional. The seller MUST publish an implementation guide that includes the schemas and schema versions to be used, the service content required data, and any required attachments. 4.1 Optional Service Content Data Most of the data elements in PIDX XML schemas are optional. Required and conditional data elements MUST be agreed to by the buyer and seller, and described in the seller s implementation guide. When the seller s implementation guide does not define an optional XML information item as required or conditional, the information item is optional, and it MAY be included in the Send Invoice Response PIP service content. Optional information items included in the service content MUST NOT cause the invoice response to fail validation in the seller s system. 4.2 Service Header Data Fundamental Business Data Entities PIDX standards require each PIP specification to prescribe the values of certain business data elements. Table 2 contains a list of those elements, their definition, and, if possible the values that MUST be specified in each instance of this PIP. The values that must be used are in quotes. If a value cannot be specified in this section, the trading partners executing the PIP MUST agree on the value to use. PIDX RNIF PIP Specification P22 Page 10 of 15 PIDX PIP P22 Invoice Response v1_0
11 Other service header elements and their values are described in the PIDX General Implementation Guidelines, version 2.0. Element Name Definition Required Value BusinessActivityIdentifier An identifier which specifies a business activity Trading partners to agree PIDX requires the name of the XML schema to be used fromrole.globalpartnerroleclassificationcode Code identifying a party's role in the Buyer supply chain torole.globalpartnerroleclassificationcode Code identifying a party's role in the Seller supply chain fromservice.globalbusinessservicecode Code identifying a business service Buyer Service network component toservice.globalbusinessservicecode Code identifying a business service Seller Service network component GlobalBusinessActionCode Code identifying a business action Trading partners pipversion.versionidentifier Identifies the version of the PIP specification used to agree inreplyto A buyer sends an invoice response action message in response to a seller s originating invoice action message. The invoice response action message service header MUST uniquely identify the originating field ticket action message in the inreplyto element structure: inreplyto.actioncontrol.messagetrackingid.instanceidentifier The value of the messagetrackingid.instanceidentifier uniquely identifies the invoice action message for tracking purposes. The value of the InstanceIdentifier element is the value of the messagetrackingid.instanceidentifier element in the delivery header of the originating field ticket action message. 5 Business Signals The Send Invoice Response PIP requires the seller to send to the buyer a business signal containing the validation status of the invoice response action message. PIDX RNIF PIP Specification P22 Page 11 of 15 PIDX PIP P22 Invoice Response v1_0
12 5.1 Scope of Business Signals Business signals communicate the status of processing events of the invoice response action message in the seller s system. The seller s system MUST return a business signal reporting the base-level validation status of the following events: 1. The receipt and successful base-level validation of a message (Receipt Acknowledgment) 2. The receipt of an out-of-sequence message (Exception with a type of General Exception ) a. Example: If a buyer requires the seller to send a field ticket before sending an invoice, and the buyer receives the invoice before receiving the field ticket, the buyer MUST return a receipt acknowledgement exception with exception type of General Exception 3. The receipt of a message that has invalid grammar; it did not pass base-level validation (Exception with a type of Receipt Acknowledgment Exception ) Optionally, trading partners MAY agree to report content validation events in the business signal. Content validation includes validating that the invoice response action message s payload complies with the seller s business rules and data requirements. If the seller validates the invoice response payload before sending the receipt acknowledgment/exception to the buyer, then the buyer and seller MAY agree that the business signal returned includes both base-level validation and content-level validation. If the invoice response payload does not comply with the seller s business rules and service content data requirements, the seller MUST return an exception business signal. The Figure 3: Content-level validation activity diagram exception type is General Exception and the error code to use is PRF.DICT.VALERR. The activity diagram in figure 3 shows the process and message flow when the payload of an invoice response action message is validated before creating a receipt acknowledgment or exception signal. 5.2 Base-level Validation Rules The four XML parts of a PIDX message (preamble, delivery header, service header and service content) MUST be validated against a PIDX DTD and message guidelines (for the three header documents) or a PIDX invoice PIDX RNIF PIP Specification P22 Page 12 of 15 PIDX PIP P22 Invoice Response v1_0
13 response schema (for the service content). The following is the minimum level of validation required for each of the XML body parts. Validating for compliance with these rules is called base-level validation: 1. The XML document MUST be compliant with its corresponding DTD or schema 2. Where an element s data type and/or length is specified in the corresponding schema (in the case of the service content) or Message Guideline (in the case of the header parts), the element MUST be validated against the schema or Message Guideline 3. In validating header documents, where the cardinality specification of an element in the Message Guideline is different from the corresponding specification in the DTD, the specification in the Message Guideline is more accurate and MUST be adhered to 4. In validating header documents, where the sequence or naming of an element in the Message Guideline is different from the corresponding specification in the DTD, the specification in the DTD is more accurate and MUST be adhered to If a message does not comply with one or more of the above rules, then it MUST be deemed invalid, and the seller MUST return an exception business signal. 5.3 Process Control While executing a Send Invoice Response PIP, if an exception occurs in the seller s system after the seller returns a receipt acknowledgement business signal to the seller, the seller MUST return a Notification of Failure process control message. RosettaNet defines process control PIP 0A1 Notification of Failure to communicate process exceptions occurring outside of the context of the current process instance. For example, if the buyer and seller agree to base-level validation, the seller will return a business signal to the seller with base-level validation status. After the buyer receives the business signal from the seller, the Send Invoice Response process has completed in the buyer s system. However, the seller continues to process the payload of the buyer s invoice response action message to determine compliance with the seller s business rules and service content data requirements. If the seller s payload does not comply with the seller s business rules and data requirements, the process ends in an exception state in the seller s system. When this happens, the seller MUST notify the buyer of the exception event by sending a Notification of Failure. Figure 4 illustrates the process sequence and flow of messages in this example. PIDX RNIF PIP Specification P22 Page 13 of 15 PIDX PIP P22 Invoice Response v1_0
14 Figure 4: Out of bounds processing error sequence diagram 6 TRP requirements The PIDX transport, routing, and packaging (TRP) standard is based on the RosettaNet Implementation Framework 2.0 (RNIF2). RNIF2 utilizes existing standards including MIME multi-part/related, MIME multipart/signed, multipart/mixed, HTTP(S), SSL, PKCS#7, SMTP, and XML. Trading partners implementing the Send Invoice Response PIP MUST understand RNIF2, PIDX restrictions to RNIF2, and the standards used by RNIF2 including MIME, HTTP(S), and PKCS# Transport security Secure transport (SSL) is REQUIRED for the invoice response action message and the signal message exchanged between the buyer and seller. 6.2 Routing The buyer and the seller executing the Send Invoice Response PIP MUST use HTTP/S to send the action and signal messages. Accordingly, each trading partner must specify the URL to which the other trading partner must send messages: The seller must specify the URL to which the buyer sends the invoice response action message The buyer must specify the URL to which the seller sends the business signal One or both of the trading partners executing the Send Invoice Response PIP may direct the other trading partner to send messages to a third party technology service provider for processing. The trading partner that engages the third party technology service provider MUST provide the other trading partner with the service provider s URL. The engagement of a third party technology service provider by a trading partner does not change the PIDX peerto-peer message exchange model: Delivering a PIDX message to an intermediary at the direction of the intended PIDX RNIF PIP Specification P22 Page 14 of 15 PIDX PIP P22 Invoice Response v1_0
15 PIDX RNIF PIP Specification P22 Page 15 of 15 PIDX PIP P22 Invoice Response v1_0
16 ERROR: undefined OFFENDING COMMAND: ~ STACK:
PIDX PIP Specification. P11: Send Field Ticket. Version 1.0
PIDX PIP Specification P11: Send Field Ticket Version 1.0 July 8, 2014 Table of Contents 1 Introduction... 4 1.1 Document Purpose... 4 1.2 Document Conventions... 4 1.3 Intended Audience... 4 1.4 References...
More informationImplementing OAGIS within the RosettaNet Implementation Framework Version 2.0
The Open Applications Group and RosettaNet Implementing OAGIS within the RosettaNet Implementation Framework Version 2.0 Kurt Kanaskie, Lucent Technologies, kkanaskie@lucent.com Introduction There are
More informationRosetta Net vs. ebxml Security Solutions and Exception Handling
HELSINKI UNIVERSITY OF TECHNOLOGY 15.5.2002 T-86.161 Special Topics in Information Technology for Production II, 2002. Rosetta Net vs. ebxml Security Solutions and Exception Handling Pekka Kantola, Janne
More informationebxml Transport Routing and Packaging Overview and Requirements
ebxml Transport Routing and Packaging Overview and Requirements This paper provides an overview of the Transport Routing and Packaging It describes: an overview and description of the scope of the group's
More informationRequest for Comments: 5402 Category: Informational February 2010 ISSN:
Independent Submission T. Harding, Ed. Request for Comments: 5402 Axway Category: Informational February 2010 ISSN: 2070-1721 Abstract Compressed Data within an Internet Electronic Data Interchange (EDI)
More informationMonitor Industry-Speak Scenarios
How-to Guide SAP NetWeaver 2004s How To Monitor Industry-Speak Scenarios Version 1.00 Sept 2006 Applicable Releases: SAP NetWeaver 2004s SPS07 End-to-End Process Integration Enabling Business-to-Business
More informationWeek 11: MIS 3537: Internet and Supply Chains
Week 11: and Case MIS 3537: Internet and Supply Chains and 2003: Video and and 7 C s of Strategic Collaboration 1. Connection with Purpose and People 2. Clarity of Purpose 3. Congruence of Mission, Strategy
More informationSMPTE Standards Transition Issues for NIST/FIPS Requirements
SMPTE Standards Transition Issues for NIST/FIPS Requirements Contents 2010.5.20 DRM inside Taehyun Kim 1 Introduction NIST (National Institute of Standards and Technology) published a draft special document
More informationInternet Security Enhanced Security Services for S/MIME. Thomas Göttlicher
Internet Security Enhanced Security Services for S/MIME Thomas Göttlicher April 20, 2004 Contents 1 Introduction 3 2 Technical 4 2.1 Internet Layer........................... 4 2.2 Compatibility...........................
More informationImplementation Guide for Delivery Notification in Direct
Implementation Guide for Delivery Notification in Direct Contents Change Control... 2 Status of this Guide... 3 Introduction... 3 Overview... 3 Requirements... 3 1.0 Delivery Notification Messages... 4
More informationJ2EE APIs and Emerging Web Services Standards
J2EE APIs and Emerging Web Services Standards Session #4 Speaker Title Corporation 1 Agenda J2EE APIs for Web Services J2EE JAX-RPC APIs for Web Services JAX-RPC Emerging Web Services Standards Introduction
More informationOffice of the Government Chief Information Officer XML SCHEMA DESIGN AND MANAGEMENT GUIDE PART I: OVERVIEW [G55-1]
Office of the Government Chief Information Officer XML SCHEMA DESIGN AND MANAGEMENT GUIDE PART I: OVERVIEW [G-] Version. November 00 The Government of the Hong Kong Special Administrative Region COPYRIGHT
More informationSend and Receive Exchange Use Case Test Methods
Send and Receive Exchange Use Case Test Methods Release 1 Version 1.0 October 1, 2017 Send and Receive Exchange Test Methods Release 1 Version 1.0 Technology Sponsor [Name] [Email] [Telephone] Signature
More informationChapter 7 - Web Service Composition and E-Business Collaboration
Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 dessloch@informatik.uni-kl.de Chapter 7 - Web Service Composition and E-Business Collaboration Motivation
More information21. Business Process Analysis (3)
21. Business Process Analysis (3) DE + IA (INFO 243) - 2 April 2008 Bob Glushko 1 of 43 4/1/2008 3:34 PM Plan for Today's Class Business Transaction Patterns Business Signals Collaborations and Choreography
More informationOctober 4, 2000 Expires in six months. SMTP Service Extension for Secure SMTP over TLS. Status of this Memo
Internet Draft draft-hoffman-rfc2487bis-04.txt October 4, 2000 Expires in six months Paul Hoffman Internet Mail Consortium Status of this Memo SMTP Service Extension for Secure SMTP over TLS This document
More informationOverview and Benefits of SEEBURGER AS2 Spokes. Trading Partner Integration Using SEEBURGER'S BIS:AS2 Spoke
Overview and Benefits of SEEBURGER AS2 Spokes Trading Partner Integration Using SEEBURGER'S BIS:AS2 Spoke Technical Documentation Contents 1 CLASSIC EDI AND ITS COST PROBLEM 2 1.1 VAN (VALUE ADDED NETWORK)...
More informationSAP Pharma Network Onboarding Guide
Onboarding Guide - Final Review SAP Pharma Network Document Version: 0.18 2016-08-10 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These include field
More informationRID IETF Draft Update
RID IETF Draft Update Kathleen M. Moriarty INCH Working Group 5 August 2004 This work was sponsored by the Air Force under Air Force Contract Number F19628-00-C-0002. "Opinions, interpretations, conclusions,
More informationSupport For E-Business. Support for E-Business
Support For E-Business Michael B. Spring Department of Information Science and Telecommunications University of Pittsburgh spring@imap.pitt.edu http://www.sis.pitt.edu/~spring Support for E-Business Organizations
More informationEnabler Release Definition for MMS
Enabler Release Definition for MMS Candidate Version 1.3 11 May 2011 Open Mobile Alliance OMA-ERELD-MMS-V1_3-20110511-C OMA-ERELD-MMS-V1_3-20110511-C Page 2 (17) Use of this document is subject to all
More informationPKCS #15: Conformance Profile Specification
Table of Contents PKCS #15: Conformance Profile Specification RSA Laboratories August 1, 2000 1 INTRODUCTION... 2 1 REFERENCES AND RELATED DOCUMENTS... 2 2 DEFINITIONS... 2 3 SYMBOLS AND ABBREVIATIONS...
More informationCorporates Cash Management
SWIFT Certified Applications Corporates Cash Management Technical validation Guide 2017 Version 1.1 February 2017 Legal notices Copyright SWIFT 2017. All rights reserved. You may copy this publication
More informationAir Transport & Travel Industry. Principles, Functional and Business Requirements PNRGOV
Air Transport & Travel Industry Principles, Functional and Business Requirements Version 15.1 Endorsed by WCO Council in July 2016 Table of Contents 1 INTRODUCTION... 3 1.1 PURPOSE... 3 1.2 SCOPE... 3
More informationTrilateral On-line Filing Group. 6 th December SCIT
Trilateral On-line Filing Group 6 th December 1999 - SCIT Agenda Overview of document structure Appendix I Trilateral Standard PKI Signature Mechanisms Wrapping, Signing, Packaging Transmission Appendix
More informationGS1 Finland Synkka Data Pool - AS2 Connection
Synkka Data Pool - AS2 Connection Connectivity Guide Version 0.4, Draft/Approved, 2017.06.16. Document Summary Document Item Document Name Current Value GS1 Finland Synkka Data Pool - AS2 Connection (Connectivity
More informationGreen Star Volume Certification. Process Guide
Green Star Volume Certification Process Guide Contents Executive Summary... 3 Volume Certification... 3 The Volume Certification Process Guide... 3 Questions?... 4 Volume Certification Summary... 5 Stage
More informationDirect Message Exhange (Web Service)
Direct Message Exhange (Web Service) Datatransmission Message exchange between the customer and Customs happens to an ever-increasing extent in XML-format. In addition to data transfer via EDI operators,
More informationETSI TS V (201
TS 124 481 V13.3.0 (201 17-01) TECHNICAL SPECIFICATION LTE; Mission Critical Services (MCS) group management; Protocol specification (3GPP TS 24.481 version 13.3.0 Release 13) 1 TS 124 481 V13.3.0 (2017-01)
More informationCo-Ordinated Retail Market Message Guide
Co-Ordinated Retail Market Message Guide ROI Implementation Market Gateway Activity Document Information Business Area: Status: Author/s: ESB Networks Final ESBN Version Number: 3.1 Reason for Change Co-Ordinated
More informationPAA PKI Mutual Recognition Framework. Copyright PAA, All Rights Reserved 1
PAA PKI Mutual Recognition Framework Copyright PAA, 2009. All Rights Reserved 1 Agenda Overview of the Framework Components of the Framework How It Works Other Considerations Questions and Answers Copyright
More informationCS 356 Internet Security Protocols. Fall 2013
CS 356 Internet Security Protocols Fall 2013 Review Chapter 1: Basic Concepts and Terminology Chapter 2: Basic Cryptographic Tools Chapter 3 User Authentication Chapter 4 Access Control Lists Chapter 5
More informationFunctional Design ecm Test scenarios for the EFET Test facility Trader tests (Broker process) Product tests
Functional Design ecm Test scenarios for the EFET Test facility Trader tests (Broker process) Product tests Arnhem, May 2006 Author M. Adriaensen / Y. Slee / L. van Vught By order of EFET author : M. Adriaensen
More informationX12 Implementation Guidelines For Inbound 997 v (I )
X12 Implementation Guidelines For Inbound 997 v004010 (I9974010) 997-4010 (i9974010) 1 10/12/2009 997 Functional Acknowledgment Functional Group ID=FA Introduction: This Draft Standard for Trial Use contains
More informationSecurity Assertions Markup Language (SAML)
Security Assertions Markup Language (SAML) The standard XML framework for secure information exchange Netegrity White Paper PUBLISHED: MAY 20, 2001 Copyright 2001 Netegrity, Inc. All Rights Reserved. Netegrity
More informationREVISED RECOMMENDATION TO NAESB EXECUTIVE COMMITTEE For Quadrant: Retail Electric, Retail Gas, Wholesale Gas
1. RECOMMENDED ACTION: EFFECT OF EC VOTE TO ACCEPT RECOMMENDED ACTION: X Accept as requested X Change to Existing Practice Accept as modified below Status Quo Decline 2. TYPE OF DEVELOPMENT/MAINTENANCE
More informationProceedings of the 35th Hawaii International Conference on System Sciences P2P in B2BI
0-7695-1435-9/02 $17.00 (c) 2002 IEEE 1 P2P in B2BI Christoph Bussler Oracle Corporation, Redwood Shores, CA 94065, USA Chris.Bussler@Oracle.com Abstract The integration of applications (application-toapplication
More informationData Transport. Publisher's Note
Data Transport Publisher's Note This document should be considered a draft until the message formats have been tested using the latest release of the Apache Foundation's SOAP code. When those tests are
More informationNational Identity Exchange Federation. Web Services System- to- System Profile. Version 1.1
National Identity Exchange Federation Web Services System- to- System Profile Version 1.1 July 24, 2015 Table of Contents TABLE OF CONTENTS I 1. TARGET AUDIENCE AND PURPOSE 1 2. NIEF IDENTITY TRUST FRAMEWORK
More informationSSL Certificates Certificate Policy (CP)
SSL Certificates Last Revision Date: February 26, 2015 Version 1.0 Revisions Version Date Description of changes Author s Name Draft 17 Jan 2011 Initial Release (Draft) Ivo Vitorino 1.0 26 Feb 2015 Full
More informationDirectLine for Business AS2 USER GUIDE
DirectLine for Business AS2 USER GUIDE Contents BMO AS2 Service...1 Introduction... 1 Overview... 1 ICS AS2 Mailbox User... 2 AS2 Mailbox Service Setup...3 Before You Begin... 3 Connectivity Testing...
More informationRID IETF Draft Update
RID IETF Draft Update Kathleen M. Moriarty INCH Working Group 29 March 2005 This work was sponsored by the Air Force under Air Force Contract Number F19628-00-C-0002. "Opinions, interpretations, conclusions,
More informationIntegration Architecture Of SDMS
Integration Architecture Of SDMS 20 May 2017 Version 1.0 (Rakesh Ranjan, Consultant-IT) Table of Content 1 ABOUT SDMS...2 2 OBJECTIVE & STRUCTURE OF THIS DOCUMENT...2 3 TRANSACTIONAL SERVICES...3 3.1 HIGH
More informationMedical Associates Health Plans and Health Choices
Medical Associates Health Plans and Health Choices 270/271 HIPAA Transaction Companion Guide HIPAA V5010X279A1 VERSION: 2.0 DATE: 06/21/2016 1 Disclosure Statement This material contains confidential,
More informationConfiguring SSL. SSL Overview CHAPTER
CHAPTER 8 Date: 4/23/09 This topic describes the steps required to configure your ACE (both the ACE module and the ACE appliance) as a virtual Secure Sockets Layer (SSL) server for SSL initiation or termination.
More informationXML based Business Frameworks. - II- Description grid for XML frameworks
1 / 14 XML based Business Frameworks - II- Description grid for XML frameworks 2 / 14 Document administration Reference Version State Exploitation Sender 20030905.D2.2.XML-BBF.1 2.1 A.Rizk Written by Checked
More informationCERTIFICATE POLICY CIGNA PKI Certificates
CERTIFICATE POLICY CIGNA PKI Certificates Version: 1.1 Effective Date: August 7, 2001 a Copyright 2001 CIGNA 1. Introduction...3 1.1 Important Note for Relying Parties... 3 1.2 Policy Identification...
More informationBeginning To Define ebxml Initial Draft
Beginning To Define ebxml Initial Draft File Name Version BeginningToDefineebXML 1 Abstract This document provides a visual representation of how the ebxml Architecture could work. As ebxml evolves, this
More informationImplementing Secure Socket Layer
This module describes how to implement SSL. The Secure Socket Layer (SSL) protocol and Transport Layer Security (TLS) are application-level protocols that provide for secure communication between a client
More informationRECOMMENDATION TO GISB EXECUTIVE COMMITTEE
RECOMMENDATION TO GISB EXECUTIVE COMMITTEE Requester: Group 8760 Request No.: R99035 1. Recommended Action: Effect of EC Vote to Accept Recommended Action: Accept as requested X Change to Existing Practice
More informationISO/IEC INTERNATIONAL STANDARD
INTERNATIONAL STANDARD ISO/IEC 23009-1 First edition 2012-04-01 Information technology Dynamic adaptive streaming over HTTP (DASH) Part 1: Media presentation description and segment formats Technologies
More informationOracle Supplier Network
Oracle Supplier Network Buyer s Guide to Connecting 11i Release 4.3 Part No. B19153-01 June 2005 Oracle Supplier Network Buyer s Guide to Connecting 11i, Release 4.3 Part No. B19153-01 Copyright 2005,
More informationMaintaining Contact Information in Ariba
Schlumberger (SLB) uses the Ariba Network for ecommerce and collaboration with its suppliers. Use of Ariba provides a streamlined P2P process and gives visibility to both the Buyer and Seller over end-toend
More informationFunctional Acknowledgment
997 Functional Acknowledgment Functional Group=FA Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997)
More informationWide Area Network Device Presence Protocol (WAN DPP)
[MS-GRVWDPP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationB2B Integration Using Seeburger AS2 Adapter with PI 7.1 Ehp1
B2B Integration Using Seeburger AS2 Adapter with PI 7.1 Ehp1 Applies to: SAP NetWeaver Process Integration 7.1x, Seeburger 2.1x Summary This article is about preliminary design & configuration aspects
More informationElectronic fee collection Information exchange between service provision and toll charging
Provläsningsexemplar / Preview INTERNATIONAL STANDARD ISO 12855 Second edition 2015-12-15 Electronic fee collection Information exchange between service provision and toll charging Perception du télépéage
More informationSpecification. OpenPEPPOL AISBL. Transport Infrastructure Coordinating Community. ICT - Models. PEPPOL Transport Infrastructure AS2 Profile
Specification OpenPEPPOL AISBL Transport Infrastructure Coordinating Community ICT - Models PEPPOL Transport Infrastructure Profile Authors: Edmund Gray IT Sligo Ireland Martin Forsberg, ESV, Sweden Version:
More informationGlossary of Exchange Network Related Groups
Glossary of Exchange Network Related Groups CDX Central Data Exchange EPA's Central Data Exchange (CDX) is the point of entry on the National Environmental Information Exchange Network (Exchange Network)
More informationHP Instant Support Enterprise Edition (ISEE) Security overview
HP Instant Support Enterprise Edition (ISEE) Security overview Advanced Configuration A.03.50 Mike Brandon Interex 03 / 30, 2004 2003 Hewlett-Packard Development Company, L.P. The information contained
More informationSelf-Assessment Questionnaire A
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire A and Attestation of Compliance All cardholder data functions outsourced. No Electronic Storage, Processing, or Transmission
More informationVendor Partnership Manual. Section 6 EDI
Section 6 No changes have occurred in this chapter since our last update in January 2017. TABLE OF CONTENTS 1. Electronic Data Interchange Trading Partner Agreement... 1 2. Requirements - Shopko Stores
More informationAUTACK. Secure authentication and acknowledgement message. Edition 2012
Secure authentication and acknowledgement message Edition 2012 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 4 4. Segments Description... 5 5. Segments Layout... 6 6. Example(s)...
More informationElectronic Transmission of Prescriptions Message Signing Requirements
NHS Restricted ETP Message Signing Requirements Programme NHS CFH Sub-Prog/ Project Prog. Director Sub Prog/ Proj Mgr ETP Tim Donohoe Ian Lowry National Prog Org Prog /Proj Doc NPFIT ETP EDB 0064 Author
More informationCategory: Standards Track January 1999
Network Working Group P. Hoffman Request for Comments: 2487 Internet Mail Consortium Category: Standards Track January 1999 Status of this Memo SMTP Service Extension for Secure SMTP over TLS This document
More informationImplementing RosettaNet Business-to-Business Integration Using J2EE and Web Services
Implementing RosettaNet Business-to-Business Integration Using J2EE and Web Services Juho Tikkala November 29 2004 DEM Solutions Oy Part 1 The Thesis Background E-business, connecting information systems
More informationXML ALONE IS NOT SUFFICIENT FOR EFFECTIVE WEBEDI
Chapter 18 XML ALONE IS NOT SUFFICIENT FOR EFFECTIVE WEBEDI Fábio Ghignatti Beckenkamp and Wolfgang Pree Abstract: Key words: WebEDI relies on the Internet infrastructure for exchanging documents among
More informationTelemetry Data Sharing Using S/MIME
Telemetry Data Sharing Using S/MIME Item Type text; Proceedings Authors Kalibjian, Jeffrey R. Publisher International Foundation for Telemetering Journal International Telemetering Conference Proceedings
More informationB2B STRATEGIES FOR COMPETITIVE ADVANTAGE. ebxml TRP.
B2B STRATEGIES FOR COMPETITIVE ADVANTAGE ebxml TRP Goal The ebxml goal: To accomplish cross-industry XML-based business process integration. Business events are building blocks that must be understood.
More informationGovernment of Ontario IT Standard (GO ITS) GO-ITS Number 56.3 Information Modeling Standard
Government of Ontario IT Standard (GO ITS) GO-ITS Number 56.3 Information Modeling Standard Version # : 1.6 Status: Approved Prepared under the delegated authority of the Management Board of Cabinet Queen's
More informationSTAR Naming and Design Rules. Version 1.0
Version 1.0 March 2007 Revision History Revision Date Version Initial Version March 13, 2007 1.0 Table of Contents 1. Introduction...1 1.1 Purpose...1 1.2 Objective... 1 1.3 Scope...1 1.4 Prerequisites...1
More informationTHE ROLE OF STANDARDS IN B2B COMMUNICATION
THE ROLE OF STANDARDS IN B2B COMMUNICATION Eva Söderström School of Humanities and Informatics, University of Skoevde Box 408, 541 28 Skoevde, Sweden ABSTRACT Recent developments in e.g. technology have
More informationTALQ Specification Overview
TALQ Specification Overview TALQ Technical Working Group March 2015 References [1] TALQ Consortium http://www.talq-consortium.org/ [2] RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1 (http://www.tools.ietf.org/html/rfc2616)
More informationSWIFT Certified Applications RTGS. Technical validation Guide Version 1.1
SWIFT Certified Applications RTGS Technical validation Guide 2018 Version 1.1 February 2018 Legal notices Copyright SWIFT 2018. All rights reserved. You may copy this publication within your organisation.
More information997 Transaction 997 IBM Subset - Functional Acknowledgment /2009
997 IBM Subset - Functional Acknowledgment - 003040-07/2009 Introduction: Functional Group ID=FA This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional
More informationE-invoicing Standard Solution
E-invoicing Standard Solution Service overview page 1/6 Corporation Table of Contents 1 Introduction...3 2 E-invoicing Service overview...3 3 Common features...5 3.1 customers...5 3.2 Interchange network...5
More informationSecurity Information for SAP Asset Strategy and Performance Management
Master Guide SAP Asset Strategy and Performance Management Document Version: 2.0 2018-03-09 Security Information for SAP Asset Strategy and Performance Management Typographic Conventions Type Style Example
More informationETSI TR V1.1.1 ( )
TR 119 400 V1.1.1 (2016-03) TECHNICAL REPORT Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for trust service providers supporting digital signatures and related services
More informationISO/IEC TR TECHNICAL REPORT. Information technology Dynamic adaptive streaming over HTTP (DASH) Part 3: Implementation Guidelines
TECHNICAL REPORT ISO/IEC TR 23009-3 First edition 2015-05-01 Information technology Dynamic adaptive streaming over HTTP (DASH) Part 3: Implementation Guidelines Technologies de l'information Diffusion
More informationELECTRONIC RECORDING MEMORANDUM OF UNDERSTANDING
ELECTRONIC RECORDING MEMORANDUM OF UNDERSTANDING THIS MEMORANDUM OF UNDERSTANDING ( MOU ) is between Mary Louise Garcia, Tarrant County Clerk, ( CLERK ), Tarrant County ( COUNTY ), Manatron, Inc. A Thomson
More informationCollateral Management
SWIFT Certified Applications Collateral Management Technical validation Guide 2018 Version 1.1 February 2018 Legal notices Copyright SWIFT 2018. All rights reserved. You may copy this publication within
More information[MC-SMP]: Session Multiplex Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MC-SMP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationDirectTrust Governmental Trust Anchor Bundle Standard Operating Procedure
DirectTrust Governmental Trust Anchor Bundle Standard Operating Procedure Change Control Date Version Description of changes 15-December- 2016 1-December- 2016 17-March- 2016 4-February- 2016 3-February-
More informationCALIFORNIA INDEPENDENT SYSTEM OPERATOR CORPORATION FERC ELECTRIC TARIFF FIRST REPLACEMENT VOLUME NO. II Original Sheet No. 727 METERING PROTOCOL
FIRST REPLACEMENT VOLUME NO. II Original Sheet No. 727 METERING PROTOCOL FIRST REPLACEMENT VOLUME NO. II Original Sheet No. 728 METERING PROTOCOL Table of Contents MP 1 OBJECTIVES, DEFINITIONS AND SCOPE
More informationETSI TS V ( )
TS 129 250 V14.0.0 (2017-07) TECHNICAL SPECIFICATION LTE; Nu reference point between SCEF and PFDF for sponsored data connectivity (3GPP TS 29.250 version 14.0.0 Release 14) 1 TS 129 250 V14.0.0 (2017-07)
More informationProof of concept AS4. Version 1 Revision ITC-KG AS4 Proof of Concept 16 January 2014 Draft INT
ITC-KG AS4 Proof of Concept 16 January 2014 Draft Proof of concept AS4 Version 1 Revision 02 2014-01-08 ENTSOG AISBL; Av. de Cortenbergh 100, 1000-Brussels; Tel: +32 2 894 5100; Fax: +32 2 894 5101; info@entsog.eu,
More informationPrivacy-Enabled NFTs: User-Mintable, Non-Fungible Tokens With Private Off-Chain Data
Privacy-Enabled NFTs: User-Mintable, Non-Fungible Tokens With Private Off-Chain Data Philip Stehlik Lucas Vogelsang August 8, 2018 1 Abstract Privacy-enabled NFTs (non-fungible tokens) are user-mintable
More informationDigital Certificates. PKI and other TTPs. 3.3
Digital Certificates. PKI and other TTPs. 3.3 1 Certification-service providers Spanish Law 59/03 Art. 2.2 or Directive 1999/93/EC Art. 2.11: Certification-service providers means an entity or a legal
More informationConfiguring SSL. SSL Overview CHAPTER
7 CHAPTER This topic describes the steps required to configure your ACE appliance as a virtual Secure Sockets Layer (SSL) server for SSL initiation or termination. The topics included in this section are:
More informationINTERNET TRANSACTION SERVICES CORE
11.19.2015 INTERNET TRANSACTION SERVICES CORE User Guide Version 1.0.2 CAQH CORE Operating Rules Connectivity Specification v2.2.0 Contents Contents 1 Introduction... 3 2 Specifications... 4 2.1 CORE Connectivity
More informationOpen ebook File Format 1.0. DRAFT VERSION 001 November 5, 1999
Open ebook File Format 1.0 DRAFT VERSION 001 November 5, 1999 Open ebook File Format 1.0 DRAFT VERSION 001 November 5, 1999 This is a draft recommendation. Changes will be made in response to further internal
More informationUsing the Cisco ACE Application Control Engine Application Switches with the Cisco ACE XML Gateway
Using the Cisco ACE Application Control Engine Application Switches with the Cisco ACE XML Gateway Applying Application Delivery Technology to Web Services Overview The Cisco ACE XML Gateway is the newest
More informationInternet Streaming Media Alliance Ultravox Provisional Specification Version 1.0 November 2007
Internet Streaming Media Alliance Ultravox Provisional Specification Version 1.0 November 2007 ISMA Ultravox Part 1: Introduction Page 1 of 6 November 2007 ISMA SPECIFICATION LIMITATIONS AND CONDITIONS
More informationNew Distribution Capability (NDC)
Together Let s Build Air Retailing Guide to the NDC Certification & Registration Program Scope of NDC Registration and Certification Program I. Certification: NDC Certified/NDC Capable 1. What Do We Certify?
More informationonem2m-ts-0008-coap Protocol Binding-V CoAP Protocol Binding Technical Specification
1 2 3 Document Number Document Name: O NEM2M T ECHNICAL SPECIFICATION onem2m-ts-0008-coap Protocol Binding-V-0.5.0 CoAP Protocol Binding Technical Specification Date: 2014-08-01 Abstract: The specification
More informationNon-SAP Backend System Readiness Check
Configuration Guide SAP Information Collaboration Hub for Life Sciences Document Version: 1.1 Final Date: SAP Information Collaboration Hub for Life Sciences Typographic Conventions Type Style Example
More informationError Handling Strategy
Handling Strategy Draft DCC Guidance Document June 2016 Page 1 of 13 Contents 1. Introduction 3 1.1. Purpose 3 1.2. Scope 3 1.3. General Provisions 3 2. Management 5 2.1. Classification 5 2.2. Handling
More informationeidas Interoperability Architecture Version November 2015
eidas Interoperability Architecture Version 1.00 6. November 2015 1 Introduction This document specifies the interoperability components of the eidas-network, i.e. the components necessary to achieve interoperability
More informationEXBO e-signing Automated for scanned invoices
EXBO e-signing Automated for scanned invoices Signature Policy Document OID: 0.3.2062.7.2.1.12.1.0 Approval Status: Approved Version: 1.0 Page #: 1 of 13 1. Introduction 1.1. Scope This document covers
More informationCisco Collaborative Professional Services Unified Computing System Technical Consulting Accelerator Service (ASF-CPSC-UCST)
Page 1 of 1 Service : Advanced Services Fixed Price Cisco Collaborative Professional Services Unified Computing System Technical Consulting Accelerator Service (ASF-CPSC-UCST) This document describes Advanced
More information