8.42 Enter protocol mode+CPROT
27.0073GPPAT command set for User Equipment (UE)Release 18TS
Table 102: +CPROT action command syntax
|
Command |
Possible response(s) |
|
+CPROT=<proto>[,<version>[,<lsap1>[,…[<lsapN>]]]] |
CONNECT NO CARRIER OK ERROR +CME ERROR: <err> |
|
+CPROT=? |
+CPROT: <proto1>[,(list of supported <version>s)[,(list of supported <lsap1>s)[,…[,(list of supported <lsapN>s)]]]] [<CR><LF>+CPROT: <proto2>[,(list of supported <version>s)[,(list of supported <lsap1>s)[,…[,(list of supported <lsapN>s)]]]] […]] |
Description
Set command informs TA that TE wants to establish a peer-to-peer protocol <proto> or upper layer connection (indicating by the <lsap>s setting) with the MT on the link from which the command was received. This command can be used in case the link between TE and MT does not provide itself such a mechanism.
If MT has succeeded in establishing a logical link between application protocols and external interface, it will send CONNECT message to the TE. Otherwise, the NO CARRIER response will be returned.
If the CONNECT response is received, TE can start sending <proto> or upper layer frames.
The connection shall always return for <proto> mode when the protocol session is ended. When the MT receives a disconnect request from its peer entity, it will process it and send OK response to the TE indicating its capability for receiving new AT commands. Since <proto> or upper layers can be accessed in other ways, TA must have pre-knowledge of the fact that connection is initiated with AT+CPROT command. This means that switch to <proto> mode must include some sort of notification to the protocol entity.
This command can be aborted by sending a <proto> or upper layer disconnection frame. In that case, MT will return in command mode by sending the OK response.
Refer clause 9.2 for possible <err> values.
Test command returns values supported as compound values.
Defined values
<proto>: integer type
0 OBEX (refer IrDA Object Exchange Protocol [44]).
…15 reserved by the present document
16… manufacturer specific
<version>: version number of <proto>: string type
<lsap1>: integer type; defines a level of service or application protocol on the top of <proto> layer. It may refer to services or protocols defined in other standards development organizations (SDOs).
1 IrMC level 1 (Minimum Level) Only .(refer [43] clause 2.9.4)
2 IrMC level 1 and 2 (Minimum and Access Levels) Only. .(refer [43] clause 2.9.4)
4 IrMC level 1, 2 and 3 (Minimum, Access, Index Levels) Only- implies static index support. .(refer [43] clause 2.9.4)
8 IrMC level 1, 2 and 4 (Minimum, Access and Sync Levels) Only-implies unique index support. .(refer [43] clause 2.9.4)
10 IrMC level 1, 2, 3 and 4 (Minimum, Access, Index and Sync Levels)-implies support of static and unique index. .(refer [43] clause 2.9.4)
…15 reserved by the present document
16… manufacturer specific
<lsap2>…<lsapN>: integer type
In case <lsapN>,<lsapN+1> received in the +CPROT command identifies protocol layers, the protocol identified by N+1 shall be on the top of the protocol identified by N on a framework point of view.
0…15 reserved by the present document
16… manufacturer specific
Implementation
Optional.