본문 바로가기

Protocol/TETRA

14.2.7 Intra-CMCE primitive summary

14.2.7 Intra-CMCE primitive summary

The sub-entities inside CMCE shall be responsible for setting parameters in each PDU it is sending. These parameters
are used in the lower layers in the transmission process. These parameters are not visible outside the MS protocol stack,
[code]CMCE(Circuit Mode Control Entity) 내에 각각에 PDU 내에 설정하는 파라메터 값을 전송하는데 보조 엔티티 는 책임을 져야 할 것이다.
이 파라메터 들은 전송 프로세스내에 Low layer들 내에서 선택했을 것이다.
그 파라메터 값들은 MS(Mobile Station)프로토콜 스택 이상으로는 보이지 않는다.[/code]

but shall affect to the functions inside the protocol stack.
[code]하지만 프로토콜 스택 내에 기능에는 영향을 미칠 것이다.[/code]

14.2.7.1 Down link CC PDU parameters

The following parameters shall accompany each PDU in addition to the PDU contents (SDU).
[code]뒤에 올 파라메터는 PDU 컨텐츠에 각각에 PDU을 추가할 것이다.[/code]

The contents of the SDUs are defined in clause 14.7.
[code]SDU 의 컨텐츠는 14.7 장에 선언되어 있다.[/code]

These parameters shall be valid for rd route (see clause 17.3.4 for ri route parameters):
[code]이 파라메터 들은 rd 루트를 위해 유효할 것이다.[/code]

• received TETRA address;
• received address type;
• channel change response required.

[code]
DOWN LINK CC PDU 에는 TETRA 주소, 주소 형식을 받고 채널 전환 응답이 필요하다.[/code]

The D-CALL RESTORE PDU should be a SDU in the RESTORE confirm primitive and the parameters used in this primitive shall be:
[code]D-CALL 복구 PDU는 해야한다. primitive 복귀하는 확인을내에 SDU를 그리고 파라메터를 프리미티브내에서 선택했을 것이다.[/code]

• SDU;
• restoration result.

14.2.7.2 Uplink CC PDU parameters

Each PDU shall convey following information as parameters in addition to the PDU contents. The contents of the PDUs
are defined in clause 14.7. These parameters shall be valid for rd route (see clause 17.3.4 for ri route parameters):
[code]각각에 PDU 는 PDU 에 정보를 더하고 매개변수로 정보를 옮긴 뒤에 운반할 것이다.[/code]

• endpoint identifier;
• layer 2 service;
• PDU priority;
• stealing permission;
• stealing repeats flag.

The MS shall send the U-RESTORE REQUEST PDU as an SDU in the RESTORE request primitive.
[code]MS(Mobile Station)는 RESTORE request primitive 내에 SDU 에 U-RESTORE REQUEST PDU를 전송할 것이다. [/code]

The parameters used in this primitive shall be:
• SDU;
• layer 2 service;
• PDU priority;
• stealing permission;
• stealing repeats flag.

14.2.7.3 Downlink SS PDU parameters
Each PDU shall convey following information as parameters in addition to the PDU contents. The contents of the PDUs
are defined in clause 14.7. These parameters shall be valid for re route (see clause 17.3.4 for ri route parameters):
[code]PDU 내용에 파라메터 정보를 추가한 뒤에 각각에 PDU를 전달할 것이다.
그 PDU들의 내용은14.7장에 선언되어 있다
기 파라메터들은 re 루트을 위해서 유효할 것이다. (ri 루트 파라메터를 위해서 17.3.4장을 보라 )[/code]

• channel change response required;
• received TETRA address;
• received address type.

14.2.7.4 Uplink SS PDU parameters
Each PDU shall convey following information as parameters in addition to the PDU contents. The contents of the PDUs
are defined in clause 14.7. These parameters shall be valid for re route (see clause 17.3.4 for ri route parameters):
[code]PDU 컨텐츠들에 파라메터의 정보를 추가한 뒤에 각각에 PDU 들을 전달할 것이다.
그 PDU들에 내용은 14.7장에 선언되어 있을 것이다.
이 파라메터들은 re 루트에 유효할 것이다. (ri 루트 파라메터를 위해 17.3.4 를 보도록 하자)[/code]

• layer 2 service;
• PDU priority;
• stealing permission.

14.2.7.5 Down link SDS PDU parameters
Each PDU shall convey following information as parameters in addition to the PDU contents. The contents of the PDUs
are defined in clause 14.7. These parameters shall be valid for rf route (see clause 17.3.3 for ri route parameters):
[code]PDU 컨텐츠들에 파라메터의 정보를 추가한 뒤에 각각에 PDU 들을 전달할 것이다.
그 PDU들에 내용은 14.7장에 선언되어 있을 것이다.
[/code]
• received TETRA address;
• received address type.

14.2.7.6 Uplink SDS PDU parameters
Each PDU shall convey following information as parameters in addition to the PDU contents. The contents of the PDUs
are defined in clause 14.7. These parameters shall be valid for rf route (see clause 17.3.4 for ri route parameters):
• layer 2 service;
• PDU priority;
• stealing permission.

14.2.7.7 CMCE management primitives
14.2.7.7.0 ACTIVITY request
The parameter used in this primitive shall be:

• call state (see clause 17.3.9).
14.2.7.7.1 BREAK indication
There are no parameters associated with this primitive.

14.2.7.7.1a BUSY indication
There are no parameters associated with this primitive.

14.2.7.7.2 CANCEL request
The parameter used in this primitive shall be:

• handle.
14.2.7.7.3 CLOSE indication
There are no parameters associated with this primitive.

14.2.7.7.4 CONFIGURE indication
The parameters used in this primitive shall be:
• endpoint identifier;
• endpoint status.

14.2.7.7.5 CONFIGURE request
The parameters used in this primitive shall be:
• add temporary GSSI;
• circuit mode type (see clause 14.8.2);
• channel change accepted (see clause 17.3.9);
• leave assigned channel;
• delete temporary GSSI;
• encryption flag;
• call identifier;
• endpoint identifier;
• simplex/duplex;
• slots per frame;
• switch U-plane on/off;
• Tx grant.

14.2.7.7.6 IDENTITIES request
The parameter used with this primitive shall be:
• list of attached GSSIs;
• list of detached GSSIs.

14.2.7.7.6a IDLE indication
There are no parameters associated with this primitive.

14.2.7.7.6b INFO indication
The parameters used with this primitive shall be:
• broadcast parameters (see clause 17.3.9);
• subscriber class match (see clause 17.3.9).

14.2.7.7.7 OPEN indication
There are no parameters associated with this primitive.

14.2.7.7.8 REOPEN indication
There are no parameters associate with this primitive.

14.2.7.7.9 REPORT indication
The parameter used in this primitive shall be:

• transfer result.

14.2.7.7.10 RESUME indication
There are no parameters associated with this primitive.

'Protocol > TETRA' 카테고리의 다른 글

State transition diagram for the PC sub-entity  (0) 2013.09.25
14.3 Overview of services required by the CMCE  (0) 2013.09.25
14.2.6 Internal routes  (0) 2013.09.25
CMCE System View  (0) 2013.09.25
14.2 Overview of CMCE  (0) 2013.09.25