PReq — Preparation Request

Preparation timing and version differences

Full updates in Core 2.3.1.1

Req 246 specifies an update for all Card Range Data, without serialNum, “every 12 hours at maximum”. If the received Card Range Data contains an error, it permits a complete or partial update once per hour at maximum. This is the source wording for this edition; it is not the older 24-hour rule.

Source: Core 2.3.1.1, §5.6, Seq 5.77, Req 246, page 155.

Partial updates and the hourly limit

Req 246 specifies partial updates with serialNum once per hour at maximum. Req 303 specifies Error 103 when the 3DS Server submits more than one Card Range Data request within one hour. These limits apply per registered Directory Server.

Source: Core 2.3.1.1, §5.6, Req 246 and 303, pages 155, 156.

The 24-hour rule in Core 2.2.0

Req 246 requires a cache-refresh call to each registered DS at least every 24 hours and at most once per hour, conditional on no errors found during PRes processing. This is a historical comparison, not the wording of the 2.3.1.1 requirement.

Source: Core 2.2.0, §5.6, Seq 5.66, Req 246, page 119.

A separate 24-hour connection-retry window

After a second failure to complete the initial TCP/IP connection and TLS handshake, Req 249 specifies retries at 60-second intervals within a 24-hour window until successful. This is a transport-failure recovery rule, not the ordinary cache-refresh schedule.

Source: Core 2.3.1.1, §5.6, Seq 5.82, Req 249, page 155.