Knowledge Base
Last Updated: 2026-07-30
Routing Activation analysis starts with the response and TCP stream state. A rejection before UDS, a confirmation-required state, and later session instability are different branches that require different evidence.
A Routing Activation response or later stream change is being treated as a downstream ECU diagnosis.
Observed
Controlled windows show distinct pre-UDS rejection, confirmation-required, and later stream-continuation branches.
Supported interpretation
Classify the observed control branch and TCP continuation before drawing any downstream conclusion.
Not established
OEM behavior, production gateway state, downstream forwarding, ECU response, and root cause are not established by these windows.
Recommended next check
Confirm the implementation profile and inspect the complete TCP stream before assigning a deployment cause.
Read this as a role-based swimlane: it shows observed request/response order, not an unproven causal chain.
Observed: Controlled windows show distinct pre-UDS rejection, confirmation-required, and later stream-continuation branches.
Not established: OEM behavior, production gateway state, downstream forwarding, ECU response, and root cause are not established by these windows.
Next check: Confirm the implementation profile and inspect the complete TCP stream before assigning a deployment cause.
Tester
Gateway / ECU
Evidence boundary
Routing Activation Request -> DoIP entity
<- observed response code or confirmation state
Downstream forwarding and ECU response are not established
Follow the same TCP stream before assigning a cause
No. It proves routing activation completed at the DoIP control layer, not downstream forwarding or ECU response.
These summaries group approved records without extending what any individual window establishes.
Problem signal: A Routing Activation response is read as an ECU diagnostic result.
Observed: Controlled 0x00, 0x03, and 0x06 branches contain no UDS on the rejected stream.
Supported interpretation: The observed branch ends before UDS.
Not established: A universal response-code meaning, OEM behavior, or root cause.
Next check: Check the implementation profile and full stream.
Evidence IDs: EVID-ROUTING-REJECT-00-01, EVID-ROUTING-REJECT-03-01, EVID-ROUTING-REJECT-06-01
Problem signal: 0x11 is treated as either usable routing or a final failure.
Observed: One controlled sequence later reaches 0x10; another ends with TCP FIN before UDS.
Supported interpretation: 0x11 requires later response and socket-state evidence.
Not established: A universal timer or production outcome.
Next check: Follow the same TCP stream to its next control response or close.
Evidence IDs: EVID-RA-CONFIRMATION-POLL-SUCCESS-01, EVID-RA-CONFIRMATION-PENDING-FIN-01
Use the complete TCP stream to separate control-layer rejection from later diagnostic failure.
Each example identifies whether it is a controlled simulator observation or a redacted field-evidence window. The evidence record bounds what the sequence can and cannot establish.
Controlled source-address rejection
Evidence reference: EVID-ROUTING-REJECT-00-01
A controlled simulator rejects the attempted routing activation before UDS begins.
Evidence signals
Real Timeline
It identifies a control-layer rejection without assigning an ISO/OEM root cause.
Controlled duplicate-source rejection
Evidence reference: EVID-ROUTING-REJECT-03-01
A later connection reuses an active tester source role and is rejected before UDS.
Evidence signals
Real Timeline
The capture does not identify which production client lifecycle would create duplicate use.
Controlled capacity branch
Evidence reference: EVID-ROUTING-REJECT-06-01
The configured simulator emits 0x06 while its configured capacity branch is occupied.
Evidence signals
Real Timeline
This is not a normative ISO/OEM interpretation of 0x06.
Confirmation-required controlled sequence
Evidence reference: EVID-RA-CONFIRMATION-POLL-SUCCESS-01
A controlled version-0x02 sequence receives 0x11, later receives 0x10, then completes a positive diagnostic exchange.
Evidence signals
Real Timeline
It documents only the configured simulator confirmation branch, not a universal OEM procedure.
Confirmation timeout branch
Evidence reference: EVID-RA-CONFIRMATION-PENDING-FIN-01
A configured simulator retains the confirmation-required state and later closes the TCP session without a 0x10 or UDS exchange.
Evidence signals
Real Timeline
This confirms only the simulator timeout behavior, not a universal confirmation timer or production cause.
These packet-level checkpoints are the smallest proof units behind the article narrative.
Control response
DoIP entity -> tester
0x0006 response establishes the observed control branch.
Read it with the source scope and following TCP stream.
Rejected stream
tester -> DoIP entity
No UDS appears after the rejection.
Places the observed failure before UDS.
Confirmation sequence
same TCP stream
0x11 may later transition to 0x10.
Diagnostic usability is not assumed before the final active state.
This is the condensed engineering verdict the analyzer would put in front of the operator.
Classify the response code and TCP stream first.
Keep simulator configuration separate from ISO/OEM claims.
These are cases where the tool symptom can point in the wrong direction unless the packet timeline is checked.
Symptom: 0x11 is called a final failure.
Packet truth: The controlled sequence later reaches 0x10.
Risk: The tester may stop before confirmation completes.
Symptom: 0x06 is presented as universal socket exhaustion.
Packet truth: Only the configured simulator capacity branch is observed.
Risk: A protocol decoder label is mistaken for a production root cause.
Use this order in real troubleshooting so packet evidence narrows the branch before repair effort expands.
These are the interpretation traps that real packet evidence helps avoid.
This page uses controlled-simulator evidence for its rejection and confirmation cases. It does not identify BMW, another OEM, or production gateway behavior.
Response-code wording must remain scoped to the applicable Evidence Record and implementation profile.
A rejected 0x0006 response with no UDS on that TCP stream is pre-UDS Routing Activation rejection.
A 0x11 response requires follow-up confirmation and socket-state evidence; do not treat it as equivalent to either immediate usability or a final failure.
Only the configured confirmation-required state in its evidence window; inspect the later response and TCP state.
Use nearby guides to move from protocol filtering to root-cause troubleshooting without leaving the knowledge base.