Download joyn Blackbird Product Definition Document Version 5.0 17

GSM Association
Non-confidential
Official Document RCC.60 - joyn Blackbird Product Definition Document
A Blackbird device acting as Legacy device complies with the following requirements
irrespective of the other party’s device type (as a result of what is defined in
section ‎2.3.5.3.2):




Supports Legacy device features.
Is configured as a Legacy device.
Supports capability discovery with reference only to Legacy capabilities.
Capability discovery ignores new Blackbird capabilities (e.g. does not present them in
address book).
The following exceptions to the rules above apply:
 User Experience (UX)/User Interface (UI) modifications to Legacy features remain in
place (e.g. the joyn setup icon may be visible or the device wizard may contain a
section about joyn).
 Network initiated configuration request via SMS remains supported (especially for
open market variants).
A Legacy device in a Blackbird network shall:



2.3.5
Be able to correctly manage a Blackbird configuration.
Ignore new Blackbird capabilities in capability discovery.
Comply with the requirements stated throughout this document.
Technical Implementation
2.3.5.1 Specification References
2.3.5.1.1
Configuration over cellular networks
The configuration over cellular networks shall be done as described in [RCC.07 RCS 5.1]
section 2.3.3.1 and 2.3.3.2 with only the Hyper Text Transfer Protocol (HTTP) solution being
in scope for joyn Blackbird as it is also needed when configuring over non-cellular networks
(see section ‎2.3.5.1.2). For the HTTP based mechanism, section 2.3.3.2 of [RCC.07 RCS
5.1] and its subsections shall apply in their entirety. If the network cannot authorize the user
(as described in section 2.3.1) an HTTP 511 Response will be returned as indicated in
section 2.3.3.2.4 of [RCC.07 RCS 5.1], which will (as indicated in [RCC.07 RCS 5.1]) result
in the use of the procedures in section 2.3.3.3 of [RCC.07 RCS 5.1]. In that case if the IMSI
is available (as described in section 2.3.1), a device implementing joyn Blackbird shall not
ask the user for the MSISDN, and shall instead attempt the configuration providing only the
IMSI in the HTTP request
The error scenarios described in section ‎2.3.1 correspond to those in section 2.3.3.3.3 of
[RCC.07 RCS 5.1] where a HTTP 403 FORBIDDEN response shall be interpreted as a
permanent error and any other error response including HTTP 511 NETWORK
AUTHENTICATION REQUIRED as a temporary one. HTTP 511 NETWORK
AUTHENTICATION REQUIRED shall trigger the manual configuration process described in
section 2.3.2. A permanent error may also be signalled through a HTTP 200 OK response
including a body indicating that the client should be disabled (i.e. version and validity set to -
V5.0
Page 21 of 127