{"id":402229,"date":"2024-10-20T05:00:11","date_gmt":"2024-10-20T05:00:11","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-3531-22022\/"},"modified":"2024-10-26T08:53:01","modified_gmt":"2024-10-26T08:53:01","slug":"bs-iso-3531-22022","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-3531-22022\/","title":{"rendered":"BS ISO 3531-2:2022"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Table of Contents <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4 FIX session 4.1 General <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | Figure 1 \u2014 Conceptual view of FIX session layer 4.2 Sequence numbers <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.3 Identifying the FIX session 4.3.1 General 4.3.2 The FIX session profile Table 1 \u2014 The FIX session profiles 4.3.3 Identification of FIX session peers <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4.3.4 Validation of SendingTime(52) 4.3.5 Additional fields available for peer identification 4.4 Establishing a FIX connection 4.4.1 Transport layer requirements <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.4.2 Using the TestMessageIndicator(464) to explicitly identify testing 4.4.3 Application layer encryption 4.4.4 Heartbeat interval 4.4.5 Heartbeat interval determination <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.4.5.1 Acceptor requires a specific heartbeat interval 4.4.5.2 Acceptor requires initiator specify a value within a heartbeat interval range 4.4.5.3 Acceptor accepts the initiator specified heartbeat interval 4.4.6 Maximum message size 4.4.7 Specifying application version <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4.4.8 Specifying supported message types 4.4.9 Identification of application system and FIX session processor3F 4.4.10 Responding to a request to establish a FIX session Table 2 \u2014 Fields in the Logon(35=A) message used for authentication <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | Figure 2 \u2014 FIX connection establishment <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4.4.11 Initial synchronization of messages in a FIX connection 4.4.12 Synchronization after successful logon <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | Figure 3 \u2014 ResendRequest(35=2) sent by acceptor after Logon(35=A) acknowledgement <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Figure 4 \u2014 ResendRequest(35=2) sent by initiator after Logon(35=A) acknowledgement <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Figure 5 \u2014 ResendRequest(35=2) sent by initiator and acceptor after Logon(35=A) acknowledgement <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 4.5 Extended features for FIX session and FIX connection initiation 4.5.1 Using NextExpectedMsgSeqNum(789) to synchronize a FIX session <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Figure 6 \u2014 Using NextExpectedMsgSeqNum(789) to synchronize the session during the logon process <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 4.5.2 Using ResetSeqNumFlag(141) to reset FIX session for 24 h connectivity 4.5.3 Using ResetSeqNumFlag(141) to reset FIX session during FIX connection establishment6F 4.5.4 Using initiator state to restore acceptor session state7F <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 4.6 Message exchange during a FIX connection <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 4.6.1 FIX connection keep alive (heartbeat) 4.6.2 Garbled message processing 4.6.3 Missing sequence number 4.6.4 Rejecting invalid messages <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Figure 7 \u2014 Session layer reject using Reject(35=3) due to invalid message received 4.6.5 Test Request Processing <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Figure 8 \u2014 Issuing a TestRequest(35=1) to determine if peer is still responsive 4.7 FIX connection termination <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 4.7.1 Normal logout processing Figure 9 \u2014 Successful Logout scenario <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 4.7.2 Logout without acknowledgement from peer Figure 10 \u2014 Logout(35=5) acknowledgement not received <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 4.7.3 Logout with retransmission of missed messages Figure 11 \u2014 Processing of ResendRequest(35=2) messages before Logout(35=5) acknowledgement <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 4.7.4 When to terminate a FIX connection by terminating the transport layer connection instead of sending a Logout(35 = 5) 4.8 Extended features for FIX connection Termination 4.8.1 Using NextExpectedMsgSeqNum(789) when terminating FIX connection due to invalid MsgSeqNum(34)9F <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.9 Message recovery 4.9.1 Ordered message processing 4.9.2 Request retransmission of messages <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 12 \u2014 Using ResendRequest(35=2) message to request missed message and subsequent messages <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 13 \u2014 Using ResendRequest(35=2) message to request only the missed message <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 4.9.3 Responding to a ResendRequest(35 = 2) message Figure 14 \u2014 ResendRequest(35=2) with Gap Fill processing <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 4.9.4 Possible duplicates 4.9.5 Gap fill process <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 4.9.5.1 Example using SequenceReset(35 = 4) to gap fill over multiple messages <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 15 \u2014 Example using the SequenceReset(35=4) to gap fill over multiple messages. 4.9.6 Sequence reset <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 16 \u2014 Performing a sequence reset instead of gap fill in response to a ResendRequest(35=2) 4.9.7 Processing inbound possible duplicate messages (PossDup(43) set to \u201cY\u201d) 4.9.8 Processing gaps when receiving FIX session layer messages <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table 3 \u2014 Response by message type 4.10 Resending an unacknowledged application message <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure 17 \u2014 Application layer resend using PossResend(97) 4.10.1 The difference between application layer resend and session layer retransmission <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 18 \u2014 The difference between application layer resend and session layer retransmission 4.11 FIX session state matrix <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 4.11.1 FIX logon process state transition diagram <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 4.11.2 FIX logout process state transition diagram <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 5 FIX session profiles 5.1 FIX.4.2 session profile 5.1.1 Profile identification 5.1.2 Application version identification <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 5.2 FIX4 session profile 5.2.1 Profile identification 5.2.2 Application version identification 5.3 FIXT session profile 5.3.1 Profile identification 5.3.2 Multiple application version support over a single FIXT session 5.3.3 Session default application version identification <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 5.3.4 Message type default application version 5.3.5 Explicit application version per message Table 4 \u2014 Application version precedence 5.3.6 Use of extension packs <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table 5 \u2014 Extension pack precedence 5.3.7 Use of a custom application version Table 6 \u2014 Custom application version precedence 5.4 Lightweight FIXT (LFIXT session profile) <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 5.4.1 Profile identification 5.4.2 Application version identification 5.4.3 LFIXT transport layer requirements 5.4.4 LFIXT compatible mode Figure 19 \u2014 FIXT peer connected to LFIXT peer operating under compatible mode Table 7 \u2014 Session layer messages when peer uses LFIXT session profile under compatible mode <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 5.4.5 LFIXT succinct mode Figure 20 \u2014 LFIXT peer connected to LFIXT peer operating under succinct mode Table 8 \u2014 Session layer messages when peer uses LFIXT session profile under succinct mode 5.4.6 LFIXT and FIXT operating mode interoperability Table 9 \u2014 Interoperability between LFIXT and FIXT peers by operating mode <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 5.4.7 Validation of message sequence numbers 5.4.8 Application layer recovery 5.4.9 LFIXT initiator connects to LFIXT acceptor Table 10 \u2014 LFIXT Logon(35=A) initiator <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 21 \u2014 LFIXT logon process <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 5.4.10 FIXT initiator connects to LFIXT acceptor (compatible mode) Table 11 \u2014 FIXT Logon(35=A) initiator <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Figure 22 \u2014 FIXT initiator connecting to LFIXT acceptor in compatible mode logon <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Figure 23 \u2014 LFIXT initiator connecting to FIXT acceptor in compatible mode logon <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 5.4.11 Receipt of ResendRequest(35 = 2) message from a FIXT peer <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Figure 24 \u2014 LFIXT resetting sequence numbers in LFIXT compatible mode <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 5.4.12 Processing invalid messages 6 FIX message routing 6.1 Message routing details \u2013 one firm-to-one firm (point-to-point) Table 12 \u2014 Message routing example, single session between two firms 6.2 Message routing details \u2013 third party message routing <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure 25 \u2014 Message routing example, single session between multiple firms 7 Transmitting alternatively encoded messages over a FIX session <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 7.1 Use of Attachment group 8 Components 8.1 AttachmentGrp <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 8.2 AttachmentKeywordGrp 8.3 HopGrp <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 8.4 MsgTypeGrp 8.5 StandardHeader <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 8.6 StandardTrailer 9 Messages 9.1 Heartbeat message <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 9.2 TestRequest message 9.3 ResendRequest message 9.4 Reject message <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 9.5 SequenceReset message 9.6 Logout message <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 9.7 Logon message <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 9.8 XMLnonFIX message 10 Fields <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | 11 Code sets 11.1 ApplLevelRecoveryIndicatorCodeSet <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 11.2 ApplVerIDCodeSet 11.3 AttachmentEncodingTypeCodeSet <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | 11.4 EncryptMethodCodeSet 11.5 GapFillFlagCodeSet 11.6 MsgDirectionCodeSet <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 11.7 MsgTypeCodeSet 11.8 PossDupFlagCodeSet 11.9 PossResendCodeSet <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 11.10 ResetSeqNumFlagCodeSet 11.11 SessionRejectReasonCodeSet <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 11.12 SessionStatusCodeSet 11.13 TestMessageIndicatorCodeSet <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Financial services. Financial information eXchange session layer – FIX session layer<\/b><\/p>\n |