1. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 1 Process Flow for TSS - Supplier This document describes the process and interdialogue rules in the NeBI interface between TSS and subcontractors. Security: Public

2. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 2 Document history 2003-12-11Ove FritzC 2004-02-23Lars AbrellD 2005-10-11Per RudalPE1RenegOrder init av FNS uppdaterad, ny slide ExecuteOrder med OEA justerade format (master slide), puts 2005-10-11Per RudalPE2FNS ändrat till Supplier, puts av slide Villkor 2005-11-04Per RudalPE3Nya slides Dialogöversikt o Affärsregler. ExecuteOrder med OEA borttagen tills vidare. 2005-11-04Hans GustePE3_1Rubrik Affärsregler ändrad till Interdialogregler, Approved tillagt sid 1 2005-11-18Anders HultinPE3_2Interdialogregler kommenterade efter internt Relacommöte 2005-12-07Per RudalPE4Interdialogreglerna uppdaterade efter e-gs-forum 29/11. CancelOrder: ruta 6b, “ESN2”, är ny. RenegOrderBySup: ruta 12, “manuell hantering” är borttagen. 2005-12-23Per RudalPE5Interdialogreglerna uppdaterade efter e-gs-forum 14/12 (h-regel 4, tillägg 4-6) Nya slides: 2 Transaktionsmönster, 3 Omsändning o larm 2006-01-16Per RudalPE6Uppdatering efter e-gs-forum 11/1: slide 2, Transaktionsmönster; slide 3, Omsändning, heart-beat o larm; slide 11, Inderdialogregler 2, punkt 2, 3, 6. 2006-06-20Per RudalEVersion för gränssnittsdokument J. PE7 utgår. Röd reservationstext i Interdialogreglerna borttagen. 2006-06-20Per RudalFVersion för gränssnittsdokument K. Ny slide 9, RenegotiateOrder initierad av Supplier alt B. 2006-06-20Per RudalPG1Dialog för leveransgodkännande, “ExecuteOrder med OEA” återinförd (jmfr PE1 o PE2 ovan) 2006-10-20Per RudalPG2slide 3: Omsändning http-nivå Telia: 3*120s -> 7*4min slide 4 Dialogöversikt + slide 9, Reneg Supplier alt B + slide 11, EO m levgodk: version 3.1 -> 4.0 2006-11-08Per RudalGVersion för gränssnittsdokument L 2006-12-01Per RudalPH1Version för gränssnittsdokument M Ny layout. Ny slide 6, NegotiateOrder med förhandling + slide 4, Dialogöversikt uppdaterad 2007-01-19Hans Guste, Per RudalPH2Translation to English. New doc name “NeBi_proc_TSS-Supplier PH2”. New slide Dialogue rules. Inter-dialogue rules updated. 2007-01-31Per RudalHProcess version for NeBI_doc_TSS-Supplier_M.doc (no changes except for version and date) 2007-02-15Per RudalPI1Process version for NeBI_doc_TSS-Supplier_PN1.doc: added dialogue InvoiceDetail

3. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 3 Transaction pattern Responder 2. Request (dialog + trans) 4. ebMS header validation 13. ebMS header validation NeBI Application Trans B Trans A Initiator 8. Request (dialog + trans) 11. Request (dialog + trans) 16. Request (dialog + trans) 6. Ack / Error 15. Ack / Error 1. 7. 9. 10. 17. Dialog X The dialogue above is an example. The dialogue X consists of two transactions, A and B, that are inititiated by different parties. The internal flow of a party is determined by the party itself (the figure function names are just examples). The focus of the figure is the common NeBI-interface which shows the transaction pattern for all transactions used in the interface: a) A transaction request is an http-request holding one ebMS-message including a business document, e g an Order b) A transaction reply is a new http-request holding one ebMS-message containing an MSH-ack or Error 3. ebMS service + action (=dialog + trans) 5. MSHack / Error 14. MSHack / Error 12. ebMS service + action (=dialog + trans) B2B

4. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 4 Resending, heart-beat and alarm 1.Resending on http-level If http-return is not received for an http-request, then: TSSwill resend the http-request every 4min 7times Eltelwill resend the http-request every 120s during 24h 2.Resending on transaction level If MSH-ack (Message Service Handler Acknowledgment) is not received for a transaction, then: TSSwill resend the trans every 10 minutes during 24h (given http-return is received, see 1 above) Relacomwill resend the trans with increasing interval during 24h Eltelwill resend the trans every 10 minutes during 24h (given http-return is received, see 1 above) 3.Heart-beat TSS sends fictitious orders (also called Topaz-order) every 15 minutes to be able to supervise the functionality of the flow also when normal traffic is low. 4.Transaction alarm TSSIf OA is not received by TSS within X minutes after OR is sent, TSS supervision staff will be notified (historically called 15-minutes alarm). The time is configurable per business agreement. Relacomwill supervise TSS heart-beat Eltelwill supervise TSS heart-beat This slide describes the resending pattern, heart-beats and alarms for (missing) events in the NeBI interface. All values are configurable. Current values are indicated.

5. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 5 Dialogue overview 1.NegotiateOrder [nebi.biz:BC:NegotiateOrder_3.0] 2.NegotiateOrder with order content negotiation[nebi.biz:BC:NegotiateOrder_4.0] 3.RenegotiateOrder initiated by TSS[nebi.biz:BC:RenegotiateOrder_3.0] 4.RenegotiateOrder intiiated by Supplier alt A[nebi.biz:BC:RenegotiateOrder_3.0] 5.RenegotiateOrder initiated by Supplier alt B[nebi.biz:BC:RenegotiateOrder_4.0] 6.CancelOrder [nebi.biz:BC:CancelOrder_3.0] 7.ExecuteOrder [nebi.biz:BC:ExecuteOrder_3.0] 8.ExecuteOrder with delivery acceptance[nebi.biz:BC:ExecuteOrder_4.0] 9.InvoiceDetail [nebi.biz:BC:InvoiceDetail_4.0]

6. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 6 NegotiateOrder [nebi.biz:BC:NegotiateOrder_3.0] TSS B2BApplication Supplier B2BApplication 1. OrderRequest ByBuyer d) Reject order c) Accept order a) Send order NeBI 2. OrderAcknowledgment BySupplier 3. DialogueCancellation BySupplier b) Is the order acceptable?

7. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 7 NegotiateOrder with order content negotiation [nebi.biz:BC:NegotiateOrder_4.0] TSS B2BApplication Supplier B2BApplication 1. OrderRequest ByBuyer d) Reject order c) Accept order a) Send order NeBI 2. OrderAcknowledgment BySupplier 3. DialogueCancellation BySupplier b) Is the order acceptable? e) Change order 4. OrderRequest BySupplier 5. OrderAcknowledgment ByBuyer g) Accept changed order 6. DialogueCancellation ByBuyer h) Reject order f) Is the change acceptable? i) Change Supplier order

8. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 8 RenegotiateOrder initiated by TSS [nebi.biz:BC:RenegotiateOrder_3.0] TSS B2BApplication Supplier B2BApplication 1. OrderUpdateRequest ByInitiator d) Reject change c) Accept change a) Change order NeBI 2. OrderUpdateAcknowledgment ByResponder 3. DialogueCancellation ByResponder b) Is the change acceptable?

9. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 9 RenegotiateOrder initiated by Supplier alt A [nebi.biz:BC:RenegotiateOrder_3.0] TSS B2BApplication Supplier B2BApplication NeBI a) Request Order change 1. OrderUpdateProposalRequest ByInitiator 2. DialogueCancellation ByResponder c) Reject the change request 3. OrderUpdateRequest ByResponder d) Change the order e) If the OUPR concerns a cancellation the dialogue is ended and TSS initiates a new CancelOrder dialogue. b) Is the change acceptable? h) Reject the change g) Accept the change 4. OrderUpdateAcknowledgment ByInitiator 5. DialogueCancellation ByInitiator f) Is the change acceptable?

10. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 10 RenegotiateOrder initiated by Supplier alt B [nebi.biz:BC:RenegotiateOrder_4.0] TSS B2BApplication Supplier B2BApplication NeBI a) Change order 1. OrderUpdateRequest BySupplier 2. OrderUpdateAcknowledgment ByBuyer c) Accept order change 3. DialogueCancellation ByBuyer d) Reject order change b) Is the change acceptable?

11. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 11 CancelOrder [nebi.biz:BC:CancelOrder_3.0] TSS B2BApplication Supplier B2BApplication 1. OrderCancellationRequest d) Reject cancellation c) Accept cancellation a) Cancel order NeBI 2. OrderCancellation 3. DialogueCancellation ByResponder Comments to c) If Supplier wants payment for the cancelled order, Reason.Name is set to 'faktureras’ in OC and ESN2+OE are sent in an ExecuteOrder dialogue. In rare occasions, Supplier will not able to send ”OC faktureras”. This will not give TSS problems. b) Is the cancellation acceptable?

12. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 12 ExecuteOrder [nebi.biz:BC:ExecuteOrder_3.0] TSS B2BApplication Supplier B2BApplication NeBI b) Send status 1. ExecutionStatusNotification 1 a) ESN1 is sent for every status change before workreport c) Send workreport 2. ExecutionStatusNotification 2 d) Send executedreport 3. OrderExecuted Workreport = ’Arbetsrapport’ Executedreport = ’Åtagande klart’

13. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 13 ExecuteOrder with delivery acceptance [nebi.biz:BC:ExecuteOrder_4.0] TSS B2BApplication Supplier B2BApplication NeBI b) Send status 1. ExecutionStatusNotification 1 a) ESN1 is sent for every status change before workreport c) Send workreport 2. ExecutionStatusNotification 2 d) Send executedreport 3. OrderExecutedRequest 5. OrderExecutedAcknowledgment g) Accept executedreport 4. OrderExecutedDenial f) Reject executedreport e) Is executedreport acceptable?

14. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 14 InvoiceDetail [nebi.biz:BC:InvoiceDetail_4.0] TSS B2BApplication Supplier B2BApplication NeBI a) Send InvoiceDetail 1. InvoiceDetail 2. InvoiceDetailAcknowledgment c) Ok 3. InvoiceDetailComplaint d) Not Ok b) Is the InvoiceDetail Correct? a) ID is sent for every InvoiceDetailPart

15. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 15 Dialogue rules 1.A dialogue defines a transaction pattern between two parties 2.A conversation is an instance of a dialogue. It is identified by its conversationId which must be unique. 3.Every transaction contains a conversationId so that the receiving part can associate the transaction with a conversation

16. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 16 Inter-dialogue rules 1 Within each dialogue the process rules are illustrated by the sequence diagrams in the previous slides. The following slides describe inter-dialogue rules that are rules that apply to concurrent dialogues that concern the same order. Principal rules 1.The first dialogue for every order is NegotiateOrder 2.Concurrent dialogues concerning the same order are permitted 3.Transactions are not permitted towards an order with a completed ExecuteOrder dialogue 4.An order is identified by its OrderId which must be unique The rule means that every NegotiateOrder dialogue concerns a new order with a unique orderid (see below for order resend though). When a new unique order is rejected in the NegotiateOrder dialogue using DialogueCancellation, then the order, including its orderid, is regarded as non-existant. The orderid of the rejected order may be reused in a new NegotiateOrder dialogue. In a dialogue of type ”NegotiateOrder with order content negotiation” all transactions, possibly including multiple OrderRequest transactions operate on the same order, thus using the same orderId. 5.Resending an order is allowed if the “resend flag” is set When resending, the order content is identical, apart from the resend flag. Resending is done when an order needs to be sent through the regular channel at a time when it has already reached Supplier through a reserve channel.

17. dokID: Telia AB CIO Office nr 2002/007/1, rev PI1, 2007-02-15 [Approved: J Alatalo, SIG] sid 17 Inter-dialogue rules 2 Exceptions, additions and explanations 1.The dialogue NegotiateOrder must be finished before starting ExecuteOrder [OA before ESN/OE] Info: Some violation of the rule occurs for technical reasons, since the IT components between the business application endpoints not always manage to maintain the original business application transaction sequence. The reason is that the IT components have parallel execution threads. This problem is most common during recovery after a stop. 2.ESN2/OE is not allowed to be sent during an ongoing RenegOrderBySup Info: If RenegOrderBySup is not responded in a timely manner, the Supplier should contact TSS through other channels. 3.Workreport (ESN2) confirms cancellation request (OCR) [ESN2 = OC + ESN2] Explanation: Supplier does not need to confirm OCR with OC if Supplier sends ESN2 in the dialogue ExecuteOrder, see slide CancelOrder. 4.In the dialogue RenegOrderBySup, an ”impossible” orderchange (OUR) as an answer to OUPR may be rejected by the Supplier Info: Subsequent status reporting (ESN/OE) is allowed, but cannot be handled by TSS. Manual routines must be used. 5.A new dialogue RenegOrderBySup may be initiated while a RenegOrderBySup is ongoing Info: TSS will however reject the new RenegOrderBySup. Supplier must wait for the ongoing dialogue to complete or contact TSS through other channels in order to solve the problem.