14.5.2 Group CC procedures
The CC procedures handled by CC shall be applicable for circuit mode calls for both speech and data.
[code]CC 말하고 데이터를 양쪽무데에게 서킷모드콜들에을 지원하는 것에 의해서 CC 의 절차를 다룰 것이다.[/code]
The circuit mode speech and data group calls shall be set-up as point-to-multipoint calls.
[code]서킷모드로 말하고 데이터 그룹콜을 P-TO-M CALL ㅇ서 설정할 때[/code]
The specification below shall be applicable for the procedures that reside in the MS.
[code]특정 아래로 MS 내에 거주하는 절차를 위해서 적용할 수 있을 것이다.[/code]
14.5.2.1 Call set-up procedures
a) Normal group call
The normal group call procedures provide support for one type of call set-up, where the MS is placed immediately into the call upon receipt of the D-SETUP PDU if the called user application can support the call and with immediate action being taken by the called user application, refer to figure 14.16.
[code]
콜설정의 하나의 형태를 위해서 기본그룹 콜 절차 제공 지원을 한다.
MS 는 D-SETUP PDU 의 receipt 위의 call 내애서 즉시알아낸다.
만약 called 한 사용자가 call 그리고 called 사용자 요청에 지금의 액션전에 얻을 수 있다는것을 지원을 한다면
[/code]
The set-up signalling procedures shall allow immediate communication to take place
between the calling and called user applications without the possibility of having an alerting process and without an explicit response from the called user application stating that the user has answered.
[code]
setup signalling 절차를 바로 전달을 허용해야할 것이다.
calling 그리고 called 사용자 요구 밖에서 경고 프로세스를 얻으수있지 않고 그리고 caleld 사용자 요청으로 사용자에게 응답을 시작한것 에의해 명시적으로 답변하는 동안에 알아 낼 것이다.
[/code]
The call priority may affect whether the user application accepts the call or not.
[code]
콜에 중요도가 발생하는걸 인지할 것이다. 사용자 요청 승낙에 call 혹은 not
[/code]
NOTE: The behaviour of the user application between the reception of the incoming set-up signalling and the acceptance/reject of the call is outside the scope of the present document.
[code]
incoming 설정 시그널링 의 reception 그리고 현재 문서내에 범위 밖에 있는 콜의 받아들임/거부 의 범위에서 사용자 요청의 행동이다.
[/code]
The MS does not signal that acceptance or rejection to the BS. user
[code]
MS는 시그널을 받아들이거나 거부하지 않을 것이다. BS 으로
[/code]
b) Acknowledged group call
An acknowledged group call allows the SwMI to poll members of the called group during the call.
[code]
call 의 그룹 수신 허가는 SwMI 에서 member 들 끼리 called group call을 하는 동안 묻는다.
[/code]
The call may be through connected to the calling MS either before polling or after polling has taken place (see clause 14.5.2.6), refer to figure 14.17.
[code]
calling MS 을 연결을 통해서 어쩌면 폴링이전 또는 폴링 이후 알아내어 얻었을 것이다.
[/code]
c) Broadcast call
The call set-up procedure for broadcast call shall be the same as that for group call as shown in figure 14.16. However,
in this case the called MSs shall not be allowed to subsequently request transmit permission.
[code]
브로드캐스팅읠 위한 콜 설정 절차 는 그림의 그룹콜을 하기위해 그것과 같을 것이다.
[/code]
14.5.2.1.1 Incoming call
Notification of the arrival of an incoming call to the CC sub-entity shall be made by the reception of a D-SETUP PDU which shall be delivered to the user application in a TNCC-SETUP indication primitive via the TNCC-SAP.
[code]
도착하는 콜에 도착의 통지가 하기 위해서 D-SETUP PDU 의 reception 에 의해 CC sub-entity가 만들어진다.
TNCC-SETUP indication primitive 는 TNCC-SAP를 거친 것에 사용자 요청을 위해 전달할 것이다.
[/code]
The CC shall enter state MT-CALL-SETUP. If the user application can support the call, it shall immediately return a TNCC-SETUP response primitive.
[code]
CC는 MT-CALL-SETUP 상태로 들어갈 것이다. 만약 사용자 요구를 지원한다면 CALL이 그것은 즉시 TNCC-SETUP response primitive를 반환할 것이다.
[/code]
On reception of a TNCC-SETUP response primitive the CC sub-entity shall enter state CALL ACTIVE and take the following actions, which are dependent upon the information contained within the PDU elements, see figure 14.16, right hand side:
[code]
TNCC-SETUP response prmitive 의 reception 위에 CC sub-entity 는 CALL ACTIVE 상태에 들어가고 다음 동작을 얻을 것이다. 독립되지 않은 정보에 실려 있을 PDU 요소에
[/code]
• the call identifier shall be used as the reference to this call in subsequent PDUs for the duration of the call;
[code]
이 콜의 식별자는 CALL 이 지속하는 동안 다음에 일어난 call을 조회선택할 것이다.
[/code]
• when CC receives TNCC-SETUP response primitive indicating that the called user application has accepted
[code]
CC는 받을 것이다 TNCC-SETUP response prmitive 는 called 사용자 지원 을 받아들여 담을 것이다.
[/code]
the incoming call, the CC sub-entity shall enter state CALL ACTIVE and start timer T310. The D-SETUP PDU shall contain an indication in the transmission grant element whether the MS should switch to U-plane reception.
[code]
incomming call, CC sub-entity는 CALL ACTIVE 상태에 들어갈것이다 그리고 T310 타이머를 시작한다.
D-SETUP PDU 는 담고 있을 것이다. transmission grant element 내에서 MS U-plane reception을 위해 switch 를 인지하고
[/code]
If the D-SETUP PDU contains an indication that the MS is allowed to request transmission permission it may follow the transmission control procedures described in clause 14.5.2.2.1 a).
[code]
D-SETUP PDU는 담고 있을 것이다. 지시를 그것은 MS 가 허락한 요청 전송허가 이다. 그것은 다음 전송 제어 절차를 묘사하고 있다 그림을 보아
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration accepting the channel change;
[code]
CC sub-entity는 전송할 것이다. CONFIGURE reqeust primitive 를 lower layer configureation 허락을 위해서 채널을 변경한다.
[/code]
• where the called user application is unable to accept the request for a certain target service, the call shall be rejected locally by issuing a TNCC-RELEASE request primitive via the TNCC-SAP and the CC shall enter state IDLE. No negotiation with the BS shall be possible.
[code]
called 사용자는 어디서 접근을 할수없나, 그 요청은 확실한 타겟 서비스를 위한것이다. call은 거부햇었을 것이다. TNCC-RELEASE request primitive가 TNCC-SAP를 통해 공표했던것에 내부에서 그리고 CC는 IDLE상태로 들어갈 것이다. BS가 가능했었던 것과 함께 협상은 없을 것이다.
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration rejecting the channel change.
[code]
CC sub-entity 는 전송해야할 것이다. CONFIGURE request primitive 가 lower layer configureation 을 거부하기 위해서 채널 변경을한다.
[/code]
14.5.2.1.2 Outgoing call
A user application initiates call establishment by transferring a TNCC-SETUP request primitive across the TNCC-SAP to the CC sub-entity. The TNCC-SETUP request primitive shall be handled by a CC sub-entity that is in state IDLE.
[code]
TNCC-SETUP request prmitivei 맞은편에 TNCC-SAP 에서 CC sub-entity로 전송하기를 위한 사용자 요청 초기화 call 시설은
CC sub-entity 에 의한 핸들일 일것이다. TNCC-SETUP request prmitive 의 그것인 IDLE 상태내 일것이다.
[/code]
The CC shall select a PDU priority based on the requested access priority value as defined in clause 14.5.6.2.
[code]
CC 다음 장에 요청되었던 접근 중요 값 에 PDU 중요 중심이 선택된다.
[/code]
The CC shall convert this request into a U-SETUP PDU and send it.
[code]
CC 는 U-SETUP PDU 로 요구를 변경해서 보낸것이다.
[/code]
The CC sub-entity shall then enter the MO-CALL-SETUP state and start timer T303, see figure 14.16 - left hand side.
[code]
CC sub-entity는 MO-CALL-SETUP 로 들어갈것이다. 그리고 t303 타이머를 시작한다.
[/code]
The following text describes the normal call set-up procedures:
[code]
다음 텍스트 묘사는 기본 콜 설정 절차이다.
[/code]
• to indicate the progress of the transmission of the U-SETUP PDU the CC may receive one or more REPORT indication primitives.
[code]
U-SETUP PDU의 전송의 지시
CC 하나를 받거나 더 많이 받을 것이다. REPORT indication primitive 를
[/code]
If the CC receives a REPORT indication primitive informing that the PDU transmission has failed, timer T303 shall be stopped, and the CC sub-entity shall inform the user application with a TNCC-RELEASE indication primitive and return to state IDLE;
[code]
CC 가 REPORT indication primitive가 알림을 받으면 그것은 PDU 전송 실패한것이다, 타이머 T303은 멈췃을 것이다, 그리고 CC sub-entity 알릴 것이다. TNCC-RELEASE indication primitive 그리고 idle 상태를 돌리는 거소가 함께
[/code]
• the SwMI may respond to the reception of the U-SETUP PDU with a D-CALL PROCEEDING PDU. Upon reception of the D-CALL PROCEEDING PDU, the CC shall inform the user application by issuing a TNCC-PROCEED indication primitive, stop timer T303, and start timer T302;
[code]
SwMi는 D-CALL PROCEEDING PDU 와 함께 U-SETUP PDU의 reception으로 답할 것이다.
D-CALL PROCEEDING PDU 의 reception 위에, CC는 TNCC-PROCEED indication primitive 를 발급하므로서 사용자 요청을 알려야할 것이다.
T303 타이머는 멈추고, T302 타이머가 시작할 것이다.
[/code]
• the D-CALL PROCEEDING PDU shall contain a call identifier which shall be used as the reference to this call in subsequent PDUs for the duration of the call;
[code]
D-CALL PROCEEDING PDU 는 콜 식별자를 담을 것이다. 전화하는 시간을 다음의 PDU들에서 현재 CALL 로 사용 되었을 것이다.
[/code]
• the D-INFO PDU shall not be used to allocate a call identifier;
[code]
D-INFO PDU는 선택하지 않을 것이다. 분배를 콜에 식별자를
[/code]
• on reception of a D-INFO PDU after reception of D-CALL PROCEEDING PDU but before the call set-up is completed, the CC shall start timer T302 from the value indicated in the call time out, set-up phase element if that element is present;
[code]
D-INFO PDU 의 reception 이후에 D-CALL PROCEEDING PUD 의 reception
하지만 콜 설정 완료 이전에 ,
CC는 T302 타이머를 시작할 것이다. call time out 내의 지시한 값에 의해서
설정 상태 요소
만약 그 요소는 소개한다.
[/code]
• if the call through connection is ready at the time when the D-CALL PROCEEDING PDU should have been sent, a D-CONNECT PDU should be sent instead. In this instance the D-CONNECT PDU shall allocate the call identifier;
[code]
call 일 연결을 통하면 시간이 준비되었다 D-CALL PROCEEDING PDU 가 전송해야 할것이다. D-CONNECT PDU 는 대신에 전송햇 해야할것이다.
그 인스턴스 안에서 D-CONNECT PDU 는 할당할 것이다. call 식별자를
[/code]
• on receipt of a D-CONNECT PDU, the CC shall enter state CALL-ACTIVE, and inform the user application with a TNCC-SETUP confirm primitive, and stop timer T302 or T303 and start timer T310.
[code]
D-CONNENCT PDU 의 receipt, CC 는 CALL-ACTIVE 상태로 진입할 것이다. 그리고 TNCC-SETUP confirm primitive 가 있는 사용자 요청을 알린다.
그리고 T302 나 T303 타이머를 정지 하거나 T310 타이머를 시작한다.
[/code]
The D-CONNECT PDU shall contain an indication as to whether the CC has been given permission to transmit.
[code]
D-CONNECT PDU 는 인지한 지시를 담아야할 것이다.
CC 는 전달 허가를 주었다.
[/code]
If transmission is not granted and the D-CONNECT PDU contains an indication that the MS is allowed to request transmission permission it may follow the transmission control procedures defined in clause 14.5.2.2.1.
[code]
만약 전달 허가가나지 않았거나 D-CONNECT PDU 지시를 담는다면 MS 는 요청 전달 허가를 허락할것이다. 그것은 다음 전송허가 절차 에 묘사되어 있을 것이다.
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration accepting the channel change. If the CC has been given permission to transmit then it shall start timer T311;
[code]
CC sub-entity 는 전달할것이다.
CONFIGURE reqeust primitive를 lower layer configuration 의 채널이 변경되는걸 받아들이기 위해서
CC 는 전송 허가를 줄것이다 그렇다면 T311 타이머가 시작되었을 것이다.
[/code]
• where the D-CONNECT or D-CALL PROCEEDING PDU indicates that the offered service is different to the one requested, and if the service offered is acceptable to the CC sub-entity according to the selected lowest service in the TNCC-SETUP request primitive, then the call shall continue.
[code]D-CONNECT 혹은 D-CALL PROCEEDING PDU는 가르킬 것이다. 그것은 그 서비스를 제공할 것이다. 요청했던 다른
그리고 CC sub-entity TNCC-SETUP request primitive 내의 선택된 lowest 서비스를 위해 sub-entity에 따라서 서비스 지원을 받아들일수 있을 것이다. call은 계속 될 것이다.
[/code]
If it is not acceptable, then the CC shall disconnect the call using the procedures in clause 14.5.2.3.1;
[code]
그것을 받아들이지 않는다면 CC 는 disconnect할것이다. 14장에 절차에 의해서 call이
[/code]
• the network may support other signalling from the calling MS to the SwMI and vice versa during the call setup phase using U-INFO and D-INFO PDUs, for example, for the purpose of showing the progress of a call setup.
[code]
network는 제공해야할 것이다. 다른 시그널링을 calling ms 에 의해서 SwMI으로 그리고 U-INFO 그리고 D-INFO PDU들을 사용하는데 불량한 콜 설정중이라면 예로 call 설정의 보여주는 진행을 목적으로
[/code]
• on reception of a group addressed D-SETUP PDU after reception of D-CALL PROCEEDING PDU (and optionally D-INFO PDU), if the call identifier in the D-SETUP is the same as the call identifier in the D-CALL PROCEEDING PDU and the calling party address in the D-SETUP PDU does not contain the MS's own address, the CC sub-entity shall enter state CALL ACTIVE, stop timer T302 and start timer T310.
[code]
그룹 주소을 쓰다 reception D-SETUP PDU 후에 D-CALL PROCEEDING PUD 의 reception (그리고 선택한 D-INFO PDU), 만약 D-SETUP 내의 call 식별자가 D-CALL PROCEEDING 내 콜 식별자와 같다면 그리고 D-SETUP PDU 가 MS 소유의 주소를 담지 않은것내의 calling party address ,
CC sub-entity 는 CALL ACTIVE 상태로 들어갈 것이다,
T302 타이머는 정지하고 T310 타이머는 시작할 것이다.
[/code]
The D-SETUP PDU shall contain an indication in the transmission grant element whether the MS should switch to U-plane reception.
[code]
D-SETUP PDU는 transmission grant 요소를 인지해 지시를 담을 것이다.
MS 는 U-plane reception 을 스위칭할 것이다.
[/code]
If the D-SETUP PDU contains an indication that the MS is allowed to request transmission permission it may follow the transmission control procedures described in clause 14.5.2.2.1 a).
[code]
D-SETUP PDU는 지시를 담는다. MS 는 request transmission permission 을 허락할 것이다. 그것은 다음에 장에 transmission control 절차를 담고 있을 것이다.
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration accepting the channel change.
[code]
CC sub-entity는 전송할 것이다. CONFIGURE request primitive를 lower layer configureation 이 채널 변경을 받아들이기 위해서
[/code]
CC shall ignore the D-SETUP PDUif the calling party address is the same as the MS's own address and shall send a CONFIGURE request primitive for lower layer configuration ignoring the channel change.
[code]
CC는 무사힐 것이다 D-SETUP PDU 를 만약 calling party address 가 MS이 소유하고 있는 주소 그리고 lower layer configuration 채널전환을 무시하기위해 전송해야할 CONFIGURE request primitive 와 같을 때
[/code]
A MS following a group addressed D-SETUP in the manner described in this clause shall cancel its request to transmit if it requested to transmit in the U-SETUP PDU.
[code]
이장에서 취소한느 방법을 묘사한 것에 MS 다음에 그룹 주소를 D-SETUP 에 쓰는 것은 그것은 U-SETUP PDU 내 전달하기 위해 요청햇던 것일 것이다.
[/code]
NOTE 1: The SwMI should either send the D-CONNECT PDU granting transmit permission first or supply the calling party address in the D-SETUP PDU (or both) to prevent the MS that is about to be granted transmit permission following the group addressed D-SETUP PDU.
[code]
SwMI는 D-CONNECT PDU 첫번째로 허가 전달 을 들어주거나 D-SETUP PDU 가 막기 위해서 calling party address 를 공급하며 둘중에 하나를 전달할 것이다. MS 는 전달허가를 승인할것이다. 다음에 그룹에 D-SETUP PDU 에 주소를 적기 위해서
[/code]
NOTE 2: Handling of the TNCC-SETUP request primitive may be affected by the MS being active in a MM procedure, this being indicated to CC from MLE via the MLE-BUSY indication primitive, refer to clause 18.3.5.4.
[code]
TNCC-SETUP request primitive 의 핸들은 어쩌면 MS 처음 활성화에 영향을 미칠것이다. 그것은 MLE-BUSY indication primitive 를 통한 MLE 에 의해서 처음 지시했던 CC 이다,
[/code]
The exact nature of the interaction between MM/MLE and CC is outside the scope of this part of the present document but it is recommended that CC not accept a TNCC-SETUP request primitive while MM is busy.
[code]
상호작용 되는 MM/MLE 그리고 CC 는 현재 문서 범위외에 정확히 나온다 그러나 CC를 적용하지않는걸 추천한다. TNCC-SETUP request primitive 가 MM 으로 busy 하는 동안
[/code]
14.5.2.1.3 Colliding calls
Call collisions can occur when both the SwMI and the MS simultaneously send a D-SETUP PDU and a U-SETUP PDU.
[code]
콜이 충돌이 일어난다면은 SwMi 긜고 MS 가 D-SETUP PDU 그리고 U-SETUP PDU 에 동시 전송할 때
[/code]
Two call set-ups are colliding when a D-SETUP PDU is received within the window where the CC waits for a call identifier from the SwMI after a U-SETUP PDU has been issued. The MS shall be able to handle two types of call collision:
[code]
두개의 콜이 충돌할 때 D-SETUP PDU는 받았을 것이다. 윈도우내에서 CC 가 SwMI에 의해서 call 식별자를 기다린 후에 U-SETUP PDU 가 발행했을때
MS 는 콜 충돌에 2개의 핸들형식으로 충족할 수 있을 것이다.
[/code]
• if the colliding calls are call set-up attempts for the same group and the requested basic services are compatible and the calling MS is a member of that group and layer 2 has not indicated successful transmission of the U-SETUP PDU, then the MS CC shall attempt to discard the outgoing call set-up attempt by sending a CANCEL request primitive to the lower layers to cancel sending of the U-SETUP PDU.
[code]
만약 call 이 출돌한다면 call 설정이 시도할것이다. 같은 그룹을 위해서 그리고 기본 서비스 에 맞게 요청을 햇었ㅇ르 것이다. 그리고 calling MS 는 그룹에 맴버다. 그리고 레이어 2는 소유하지 지시했던 것을 못했을 것이다. 성공한 U-SETUP PDU전송을, 그렇다면 MS CC 는 시도할것이다
CANCEL request primitive 에서 lower layer 가 U-SETUP PDU를 전송하는걸 취소하는 것에 의해서 나가는 call을 설정한다.
[/code]
If cancellation is successful, the MS shall accept the incoming call.
[code]
성공적으로 취소되었을 때 MS는 incoming call을 받아들인다.
[/code]
If cancellation is unsuccessful or if layer 2 has indicated successful transmission of the U-SETUP PDU, the MS shall continue its own call set-up and wait for a D-CALL PROCEEDING and/or D-CONNECT PDU (and/or D-RELEASE PDU);
[code]
만약 성공적으지 않았다면 layer2 는 지시했었을 것이다 U-SETUP PDU의 성공적인 전송을, MS 는 계속해서 할 것이다. 그것은 소유권을 가진 call setup 그리고 D-CALL PROCEEDING and/or D-CONNECT PDU 를 위해서 기다린다.
[/code]
• if the call set-up attempts are not to the same group, then the MS shall either keep its call attempt or accept the incoming call as defined in clause 14.5.2.1.1.
[code]
call setup 를 시도하면 같은 그룹이 아닐때 그렇다면 MS는 어느한 곳을 보관 할것이다 그것은 call 을 시도하거나 Incoming call을 시도할것이다.
[/code]
In the latter case the MS shall first cancel its call set-up locally, if still possible, or otherwise send a U-DISCONNECT
PDU for its own call set-up, refer clause 14.5.2.3.1.
[code]
다음 케이스 내에 MS 는 처음 취소할 것이다. 그것은 call setup은 가까울 것이다. 그것은 가능하거나 U-DISCONNECT PDU 내 내부적으로 전송할것이다. 소유권을 가진 CALL 설정을 위해서
[/code]
If MAC requested a response with the parameter channel change response required value set to "true" with the CC message the CC shall select the proper radio resource by issuing MLE-CONFIGURE request primitive with value "reject" in the first case or "accept" in the latter case. Refer to clause 14.5.3.2.
[code]
만약 MAC에서 응답을 요청햇었다면 응답은 파라메터 채널 변경 응답이 필요한 값 으로 TRUE로 설정되어 있다 CC 메시지 와 함게 CC는 선택할것이다. 알맞는 레이도 리소스를 MLE-CONFIGURE request prmitivie 에 의해서 MLE-CONFIGURE request primitive "reject" 과 함께 처음 케이스 "accept" 케이스내에서 다음 케이스로
[/code]
14.5.2.1.4 Unsuccessful call set-up
Unsuccessful call set-up shall refer specifically to those instances where a circuit mode connection was not successfully established.
[code]
실패한 콜 설정은 특히 그 인스턴스에게 보낼 것이다. 서킷 모드연결을 얻지못했을 때
[/code]
It shall not refer to call disconnection or call rejection. If a PDU is not responded to prior to the expiry of the corresponding timer, the procedure in clause 14.5.2.3.5 shall apply.
[code]
만약 call 해제 혹은 call 거부를 보내지 못한다면 만약에 PDU 가 대응되는 타이머에 절차에 응답하지 못한다면 이전에 만료된
[/code]
All timers available are listed in clause 14.6.
[code]
모든 타이머들을 얻을 수 있는 리스트는 14.6 장에 있다.
[/code]
When CC receives a REPORT indication primitive indicating that the lower layers have not been successful (failed
transfer) in the sending of any of the call set-up PDUs, then the CC sub-entity shall return to state IDLE and inform the
user application with a TNCC-RELEASE indication primitive accompanied with a cause of the disconnection.
[code]
CC는 받을 것이다. REPORT indication primitive에 지시를 그것은 lower layer를 성공적으로 얻을 것이다. 어떤 call setup PDU 의 전송내에서 그렇다면 CC sub-entity 는 반송할 것이다. IDLE 상태를 그리고 전달할 것이다. 사용자 요구에 TNCC-RELEASE indication primitive 와 함께해 수행한다. 연결해제의 목적이 되는...
[/code]
14.5.2.1.5 Call rejection
If the user application decides to reject the incoming call set-up request as defined in clause 14.5.2.1.1, it shall immediately transfer a TNCC-RELEASE request primitive to the CC sub-entity.
[code]
콜의 거부
만약 사용자 요청에 걸려오는 콜의 설정 요청을 거부 결정을 내린다. 14.5.2.1.1 장내에 선언되어 있다.
만약 즉시 전송을 TNCC-RELEASE request primitive CC sub-entity 에게 한다면
[/code]
This request shall locally clear the call identifier. The CC sub-entity shall then change to state IDLE.
[code]
그 요청은 가까운곳에서 call 식별자가 초기화 될 것이다.
그 CC subentity 는 IDLE 상태로 변해야할 것이다.
[/code]
14.5.2.2 Call maintenance procedures
The call maintenance procedures described in this clause may be applied when the MS is in states MO-CALL SETUP, MT-CALL SETUP or CALL-ACTIVE.
[code]
call 에 유지 절차 묘사는 이장에 적용 되어 있다.
MS 는 MO-CALL SETUP 상태 내, MT-CALL SETUP 이나 CALL-ACTIVE
[/code]
The main state CALL-ACTIVE can comprise several sub-states.
[code]
메인 CALL-ACTIVE 상태는 몇개의 보조 상태로 구성되어 있다.
[/code]
NOTE: The D-INFO PDU can be used for other purposes than those defined in the protocol specifications contained in the present document.
[code]
D-INFO PDU 는 다른 목적을 위해서 선택한다.
그 목적은 현재 문서에 프로토콜 스펙에 실려 선언되어 있는 것들이다.
[/code]
14.5.2.2.1 Transmission control procedures
a) Request-to-transmit
The SwMI shall fully control which MS is allowed to transmit. To facilitate this, the MS shall request permission to transmit, and permission shall be granted before the MS can begin circuit mode traffic permission. MSs may request permission to transmit, if the SwMI allows it by a "transmission request permission" element even if another party is transmitting.
[code]
SwMI 는 모두 컨트롤 해야할 것이다. MS 는 전송을 허락할 것이다. 쉽게 한다.
MS 는 전송 하기 위해 요청 허가를 할 것이다, 그리고 MS 가 서킷모드 트레픽 허가를 하기 전에 허락을 승인할 것이다.
MS 들은 전송하기 위해서 요청 허가, 그것은 SwMI 를 허락할 것이다. "tranmission request permission" 요소 조차도
만약 다른 파티를 전송한다면은
[/code]
In this case the SwMI should normally wait for that party to finish the transmission before granting the other user application. Pre-emptive priority requests are dealt with in clause 14.5.2.2.1 f).
[code]
그 케이스에서는 SwMI 가 파티가 종료하기 위해서 정상적으로 기다려야한다. 전송 전에 허락한다. 다른 사용자 요청을.
우선권을 가진 중요한 요청는 14.5.2.2.1 장에 처리되어 있다.
[/code]
The SwMI normally gives the first permission to transmit to the calling MS when a new call has been set-up. However, the calling user application may allow the called users to request permission to transmit first. The calling CC shall in that case set the "request to transmit" bit accordingly in the U-SETUP PDU.
[code]
SwMI 는 정상적으로 준다. 첫번째 calling MS 를 새로운 콜을 설정할때 의 전송 허가. 그러나 그 전화하는 사용자 신청는 허락하기를 바란다. called 사용자 에서 첫번째 전송 요청 허가를 하기 위해서. calling CC 는 "request to transmit" bit 에 맞춰서 설정 케이스 내에서 해야할 것이다. U-SETUP PDU에서
[/code]
When a user within a call wants to transmit, a TNCC-TX request primitive shall be sent to CC via the TNCC-SAP.
[code]
언제 사용자는 call 전송을 원하나, TNCC-TX request primitive 는 전송했었을 것이다. CC 에게 TNCC-SAP 를 통해서
[/code]
The CC shall send this request in a U-TX DEMAND PDU. The TX-DEMAND Priority level should be set to low or high priority, unless this is a pre-emptive priority request, see clause 14.5.2.2.1 f), see figure 14.18.
[code]
CC는 U-TX DEMAND PDU 요청을 전송해야할 것이다.
TX-DEMAND 중요 레벨은 낮거나 높은 중요도로 설정되어야할 것이다. 하지 않으면 pre-emptive prority request,
[/code]
The progress of the transmission of the U-TX DEMAND PDU shall be given locally to the CC in one or more REPORT indication primitives.
[code]
U-TX DEMAND PDU의 전송 작업은 는 내부의 CC 에게 혹은 많은 REPORT indication primitive 에게 줘야할 것이다.
[/code]
If the CC receives a REPORT indication primitive as a response to the sending of the U-TX DEMAND PDU informing that the PDU transmission has failed, the CC shall inform the user application by a TNCC-TX confirm primitive.
[code]
만약 CC 를 받는다면 REPORT indication primitive 가 전송하고 있는 U-TX DEMAND PDU 알리는것을 전송하기 위해서 응답 할 때하고
그것은 PDU 가 전달을 실패했다는 것이다. 그 CC SMS TNCC-TX confirm primitive 에의한 사용자 요청에 알릴 것이다.
[/code]
If a user application wants to withdraw his request-to-transmit before it has been granted, a TNCC-TX request primitive shall be sent from the user application to the TNCC-SAP.
[code]
만약 사용자 요청을 요청을 취소하기를 원한다면 그의 request-to-transmit 전에 그것을 승인했을 것이다, TNCC-TX request primitive 는 전송했었을 것이다. 사용자 요청 TNCC-SAP 를 하기 위해서
[/code]
The CC shall send this request in a U-TX CEASED PDU. The CC shall send the U-TX CEASED PDU with the stealing permission set to "immediate stealing" and stealing repeats flag set so that the permission to transmit will be released immediately if allocated.
[code][/code]
No CC protocol response shall be received from the SwMI for this message.
[code]
메시지를 위해서 SwMi에 의해서 CC 프로토콜 응답이 응답 받는지 않았다면
[/code]
b) Response to request-to-transmit
During a call in progress and when the SwMI has decided which MS shall be given permission to transmit, the SwMI
shall send a D-TX GRANTED PDU as an individual message to the granted MS.
[code]
call 이 작업하는 동안 그리고 SwMI 뚜렷하게 SwMi에게 전송 허락을 주어야할 것이다.
[/code]
Upon reception of a D-TX GRANTED PDU indicating "transmission granted", the CC sub-entity shall send this information to the user application in a TNCC-TX confirm primitive.
[code]
D-TX GRANTED PDU의 "transmission granted" 지시의 reception 위로 CC sub-entity 는 전송해야할 것이다. 그 정보를 TNCC-TX confirm primitive 내에 사용자 신청을 위해서이다.
[/code]
The other MSs involved in the call shall be informed with a D-TX GRANTED PDU addressed with the group address.
[code]
다른 MS들은 call 내에 신고할것이다 복잡하게 그룹 주소와 함께 D-TX GRANTED PDU 주소를 쓸것이다.
[/code]
That D-TX GRANTED PDU shall indicate that permission to transmit has been granted to another user. The CC shall send this information to the user application in a TNCC-TX indication primitive and shall remain in state CALL-ACTIVE, see figure 14.18.
[code]
그 D-TX GRANTED PDU 는 지시해야할 것이다. 그것은 다른 사용자에게 전송을 허락하기 위해서 이다.
그 CC 는 TNCC-TX indication primitive 그리고 CALL-ACTIVE 상태로 남겨지기 위해서 전송해야할 것이다.
[/code]
If the SwMI places the transmission request in a queue this shall be indicated to the MS concerned using the "transmission request queued" parameter value in the D-TX GRANTED PDU.
[code]
SwMI 잘리에 D-TX GRANTED PDU 내의 "tranmission request queued" 파라메터 값 을 사용하여 관계되어진 MS 를 표시하기 위해서 queue 내의 전송 요청한다.
[/code]
If the SwMI rejects the transmission request this may be indicated to the MS concerned using the "transmission not granted" parameter value in the D-TX GRANTED PDU.
[code]
만약 SwMi에 전송요청을 거부한다면 이것은 D-TX GRANTED PDU 내에 MS 관련 되어져 사용한 "transmission not granted" 파라메터 값을 지시하기 위해서
[/code]
In either case, the MSs concerned shall remain in state CALL-ACTIVE.
[code]
MS들은 관계되어 CALL-ACTIVE 상태 로 남아 있을 것이다.
[/code]
Upon reception of a D-TX GRANTED PDU indicating "transmission granted" or "transmission granted to another user", the CC sub-entity shall issue a CONFIGURE request primitive.
[code]
D-TX GRANTED PDU 의 reception 위에 지시할 것이다. "transmission grnated" or "transmission granted to another user"를
CC sub-entity 는 CONFIGURE request primitive 를 이야기할 것이다.
[/code]
The primitive shall carry as a parameter whether the transmit permission has been granted to this CC sub-entity or to another CC sub-entity, and to switch the U-Plane on.
[code]
primitive 는 인지한 파타메터에 나를 것이다.
CC sub-entity 나 다른 CC sub-entity 으로 전송 제어 허가를 위해서 그리고 U-Plane on 스위칭한다.
[/code]
The MS given permission to transmit shall start timer T311.
If the D-TX GRANTED PDU indicates "transmission granted to another user" and contains the MS's own address as the transmitting party address then that MS should not switch to U-plane reception.
[code]
MS 는 시작해야하는 T311 타이머에게 허가를 줄것이다.
만약 D-TX GRANTED PDU 가 "transmission granted to anther user" 그리고 MS들의 전송 파티 주소의 소유를 가진 주소를 표시해야 한다면
그것은 MS 가 U-plane reception 스위칭을 하지 않을 것이다.
[/code]
However it shall not switch to U-plane transmission until it receives a D-TX GRANTED PDU indicating "transmission granted".
[code]
그러나 그게 U-plane을 전송할 때까지 switch 하지 않는다.
그 D-TX GRANTED PDU 가 "transmission granted" 지시를 받는다면
[/code]
Though the MS shall switch to U-Plane receive if it receives a "transmission granted to another user" response to its transmission request and the transmitting party address in the D-TX GRANTED PDU is not the MS's own address, the MS shall require an explicit response to its transmission request: one of "transmission granted", "transmission not granted" or "transmission queued".
[code]
MS 가 U-plane이 받아 스위치 함에도 불구하고
"transmission granted to anther user" 응답을 받았다면
그것을 전송 요청 그리고 D-TX GRANTED PDU 가 MS들의 소유권의 주소가 아닌 전송 파티 주소, 명시적 응답을 위해 필요할 것이다.
"transmission granted", "transmission not granted" or "transmisson queued" 중 하나를 전송 요청한다.
[/code]
NOTE 1: The SwMI should either send the individually addressed D-TX GRANTED PDU ("transmission granted") first or
supply the transmitting party address in the group addressed D-TX GRANTED PDU ("transmission granted to another user") to prevent the MS that is about to be granted transmit permission switching to U-plane receive. As defined in ETS 300 396-5 [11],
clause 9, this is mandatory for the SwMI when granting transmit permission to a Direct Mode MS which is operating through a Direct Mode gateway.
[code]
SwMI 는 각각의 D-TX GRANTED PDU ("transmission granted") 첫번째 주소 나
U-plane을 받기 위해서 전송 허가 스위칭 에 관한걸 막기 위해서 D-TX GRANTED PDU ("transmission granted to another user") 그룹 주소내에 있는 파티 주소를 전송하는것을 지원한다.
이것은 SwMI Direct mode gatewya 명령을 통해서 Direct Mode MS에 허가를 전송 허락하기 위해서 이고
[/code]
(This mandatory requirement applies only if the SwMI has accepted a request from the gateway to operate as a Direct Mode gateway.)
[code]
이것은 의무적인 요구를 적용 한다. 만약 SwMI에 요청을 허락하였다면 Direct mode gateway 에 명령을 하기위한 것에 의해서
[/code]
Upon reception of a D-TX GRANTED PDU indicating "transmission granted to another user", and if the CC sub-entity has issued a U-TX DEMAND PDU to the lower layers and has not yet received a REPORT indication primitive indicating successful or unsuccessful transmission, then the CC sub-entity shall send a CANCEL request primitive to the lower layers to cancel transmission (and retransmissions) of that PDU.
[code]
D-TX GRANTED PDU 의 reception 은 "transmission granted to another user"를 지시를 한다. 그리고 CC sub-entity 는 이야기할 것이다. U-TX DEMAND PDU 가 lower layers 그리고 REPORT indication primitivei 가 아직도 성공 혹은 전송을 실패한걸 받지 않았을 때
그렇다면 CC sub-entity 는 PDU의 전송 취소를 하기 위해 lower layer 에서 CANCEL reqeust primitive 를 전송해야할 것이다.
[/code]
NOTE 2: The above procedure may sometimes stop re transmissions by the awarded MS as well as retransmissions by any other MSs that are requesting transmit permission.
[code]
절차 위에 어떤 시간에이 멈춰야한다면은 부여한 MS 에 재전송을 지나 어떤 다른 MS들에 전송 요청 허가에 의해서 이다.
[/code]
NOTE 3: If the SwMI queues any other transmission requests that it received then it should, at a convenient time, send D-TX GRANTED PDUs containing the "transmit request queued" parameter value to the MSs concerned. For transmission requests that are neither granted nor queued, and if the user application still wishes to transmit, then it has to send another TNCC-TX request primitive to the CC.
[code]
만약 SwMI queue들이 어떤 다른 전송 요청이라면 그것은 받았을 것이다. 그것은 편리한 시간에 할 것이다.
D-TX GRANTED PDU 는 MS 들과 관계된 "transmit request queued" 파라메터 값을 담을 것이다.
전송 허가를 위해서
그것은 queue 또한 허락할 것이다. 그리고 사용자 신청에 전송을 아직 바랄 것이다. 그것은 다른 TNCC-TX request primitiv 에서 CC로 전송하기 위해서이다.
[/code]
After reception of a D-TX GRANTED PDU indicating "transmission granted", and while it still has permission to transmit, the CC shall ignore any group addressed D-TX GRANTED or D-TX INTERRUPT PDUs it may receive (and any layer 2 channel assignment received with those PDUs by issuing an MLE-CONFIGURE request primitive ignoring the channel change, if requested).
[code]
D-TX GRANTED PDU가 "transmission granted" 의 지시를 받아 들인 후에, 그리고 전송 허가를 얻는 동안, CC는 어느 그룹 주소들 D-TX GRANTED or D-TX INTERRUPT PDU 들을 무시할 것이다. 그것은 응답할 지도 모른다. (그리고 어떤 2채널 레이어 임무를 받을 것이다. 그 PDU들과 함께 MLE-CONFIGURE request primitive 채널 변경 무시 에 의해서
[/code]
If the CC sends a U-TX DEMAND PDU whilst another MS is transmitting, the SwMI should normally wait for that party to finish the transmission (identified by the receipt of a U-TX CEASED PDU), before granting transmission permission to the other user application. On receipt of the U-TX DEMAND PDU, the SwMI may send a D-TX GRANTED PDU indicating whether the request-to-transmit is queued or rejected. Pre-emptive priority requests are dealt with in clause 14.5.2.2.1 f).
[code]
다른 MS 에게 전달하는 동안 U-TX DEMAND PDU 가 CC 를 전송한다면은, 파티에 전송을 완료하기 위해 SwMI는 보통 기다려야한다,
다른 사용자 신청 이전에 전송 허가를 하면.
U-TX DEMAND PDU 의 receipt,
SwMI가 D-TX GRANTED PDU 는 지시를 인지해 request-to-transmit 는 queued 나 거부한 것을 전송할지도 모른다.
이장에 선매권있는 중요 요청을 처리한다.
[/code]
The SwMI shall not send an unsolicited D-TX GRANTED PDU but it is recognized that a race/error condition may result in the MS receiving one.
[code]
SwMI 는 부탁받지 않았던 D-TX GRANTED PDU 를 전송하지 않을 것이다.
받고 있는 하나의 결과가 race/error 상태인지 알수 있을지도 모른다
[/code]
The CC may choose to follow an unsolicited individually addressed D-TX GRANTED PDU indicating "transmission granted" but if the CC does not want to transmit/send data then it shall use the U-TX CEASED PDU, as it does normally at the end of a speech or data item, to reject the transmission grant.
[code]
CC 는 부탁받지 않은 각각의 주소 D-TX GRANTED PDU 가 지시한 "transmission granted" 을 따라서 선택했을지도 모른다 하지만 CC는 transmit/send data 하는걸 원하지 않는다 그렇다면 U-TX CEASED PDU 를 선택해야할 것이다, 말하는 혹은 데이터의 끝에 기본적으로 했었을 것이다.
전송 허가 거부를
[/code]
c) Permission to transmit withdrawn
The SwMI may decide to interrupt transmission when resources are required for another call or when the SwMI requires that the call should temporarily pause.
[code]
SwMI 는 interrupt transmission 에 결정을 내려야했었을 것이다
다른 콜을 위해서 리소스를 요청했었을 때 또는 SwMI 가 필요에 의해 일시적으로 멈춰야할때
[/code]
In this case the SwMI should send a D-TX WAIT PDU to all MSs in that call (permitting or denying transmission requests according to the "transmission request permission" element).
[code]
SwMI 는 이 케이스에서 call 내에 모든 MS 들로 D-TX WAIT PDU 를 전달한다.
[/code]
On reception of the D-TX WAIT PDU the CC sub-entity shall send a TNCC-TX indication primitive to the user application
indicating that the transmission is waiting. The CC shall stop timer T311, if activated, enter state WAIT, and send a CONFIGURE request primitive to switch the U-Plane off.
[code]
D-TX WAIT PDU 의 reception 에 CC 보조 엔티티는 사용자 요청 지시로 TNCC-TX indication primitive 를 전송할 것이다.
전달을 기다리라고. CC 는 T311 타이머를 멈춰야할 것이다,
만약 활성화되어 있다면 WAIT 상태로 진입할 것이다,
그리고 U-Plane off 를 하기 위해서 CONFIGURE request primitive 를 전달할 것이다.
[/code]
The CC shall accept any layer 2 channel allocation and await further instructions on the channel that they have been directed to.
[code]
CC 는 어떤 레이어 2채널 할당을 승낙해야할 것이다 그리고 채널에 미래의 명령들을 기다린다 안내를 얻기 위해서
[/code]
If a request-to-transmit has been queued at the time when the D-TX WAIT PDU is received, the MS shall be allowed to withdraw its request-to-transmit by means of the U-TX CEASED PDU as described in clause 14.5.2.2.1 e).
[code]
만약 시간에 request-to-transmit queued 를 얻었다면 D-TX WAIT PDU 를 받았던 때일 것이다, MS 는 묘사된 U-TX CEASED 에 의해서 request-to-transmit 내부적으로 허락을 해야할 것이다.
[/code]
A group-addressed D-TX WAIT PDU shall apply to all the MSs in the call (including the transmitting MS). Optionally, the D-TX WAIT PDU may also be sent individually addressed to the transmitting MS enabling the SwMI to obtain a layer 2 acknowledgement from that MS.
[code]
콜 내에 모든 MS 들에게 그룹 주소 D-TX WAIT PDU 를 적용해야할 것이다.
선택적으로,
D-TX WAIT PDU 는 MS에 레이어 2 를 획득했다고 응답하기 위해서 전송하는 MS에 SwMI를 활성화 하고 각각의 주소들에 전송할지도 모른다.
[/code]
If the SwMI sends a D-TX WAIT PDU because it wishes to use an assigned channel for another call, it shall send a
layer 2 channel allocation with the D-TX WAIT PDU directing the MS to a signalling channel other than the assigned
channel.
[code]
SwMI에 D-TX WAIT PDU을 전송한다면 그건 다른 콜을 위해서 선언되어 있던 채널을 선택하기를 원하기 때문이다,
그것은 D-TX WAIT PDU 가 직접적으로 레이어 2 채널을 할당해 전송해야할 것이다.
MS 에서 시그널링 채널과 다르게 할당할 것이다.
[/code]
This is to prevent the change in usage marker associated with re-allocation of the assigned channel to the other call causing the waiting MS to drop the interrupted call.
[code]
이것은 콜을 인터럽트한것을 떨어뜨리기 위해서 할당되어 있는 채널의 재할당과 관련되어 있는 것을 변경해 적용시켜 다른 콜이 MS 를 기다리게 할것이다.
[/code]
d) Permission to continue with withdrawn call
[code][/code]
There are three cases as follows:
[code][/code]
1) If no MS was granted transmission at the time when the SwMI sent the D-TX WAIT PDU, or if an MS was granted transmission at the time of the D-TX WAIT PDU but the SwMI does not wish that transmission to continue, then either a D-TX CONTINUE PDU with the continue element set to "not continue", or a D-TX GRANTED PDU with the transmission grant element set to "transmission not granted", shall be sent as a group message to all MSs in the group. The CC shall accept any layer 2 channel allocation.
[code]
만약 MS 가 시간에 허가했던 전송이 아니면 SwMI 는 D-TX WAIT PDU를 전송했을것이다, 또는 MS 가 D-TX WAIT PDU 의 시간에 허락일수도있다.
하지만 SwMI는 계속 전송을 원하지 않을 것이다, 진행 요소가 "not continue" 로 설정되면 D-TX CONTINUE PDU 는 양쪽중에 또는 전송 허가 요소가 "transmission not granted" 로 설정하면 D-TX GRANTED PDU 도 계속 전송하지 않을 것이다,
그룹내 모든 MS들의 로 그룹 메시지를 보내야할지도 모른다.
그건 CC 가 어떤 레이어 2 채널을 할당해 허용할 것일지도 모른다.
[/code]
All CC sub-entities shall return to state CALL-ACTIVE but the U-plane shall not be switched on and the MS shall assume that any previous transmission permission no longer applies. If the D-TX CONTINUE PDU contains an indication that the MS is allowed to request transmission permission, it may follow the transmission control procedures described in clause 14.5.2.2.1 a).
[code]
모든 CC 서브 엔티티들은 CALL-ACTIVE 상태를 반환해야할 것이다 하지만 U-plane 은 스위칭하지 않았을 것이다 그리고 MS 는 어떤 이전 전송 허가를 길게 적용하지 않는걸 가정해야 할 것이다. D-TX CONTINUE PDU에 지시를 담고 있다면 MS 는 request transmission permission 을 허락했었을 것이다.
이장에 묘사되어 있는 전송 제어 절차를 따를지도 모른다.
[/code]
2) If there was one MS granted transmission at the time when the SwMI sent the D-TX WAIT PDU, and if the SwMI wishes that transmission to continue,
then either a D-TX CONTINUE PDU with the Continue element set to "continue" shall be sent as a group message to the group, or a D-TX GRANTED PDU with the transmission grant element set to "transmission granted" shall be sent to the granted MS and a D-TX GRANTED PDU with the transmission grant element set to "transmission granted to another" shall be sent as a group message to the group.
[code]
만약 하나의 MS를 시간내에 전송을 허락했었다면 SwMI 가 D-TX WAIT PUD 를 전송햇었을 때, 그리고 SwMI 가 계속 전송을 원한다면,
진행 요소가 "continue" 로 설정되어 그룹으로 그룹 메시지를 전송해야하거나 또는
전송 허가 요소가 "transmission granted" 로 설정되 MS 에허가를 전송해야할 때 그리고
D-TX GRANTED PDU 가 전송 허가 요소 가 "transmission granted to another"설정한 것과 함께 그룹에 그룹메시지를 전달할 때 이다.
[/code]
The CC shall accept any layer 2 channel allocation. If a D-TX CONTINUE PDU with the Continue element set to "continue" is sent, it shall give the earlier granted MS permission to continue transmission. The MS granted permission to transmit shall start timer T311.
[code]
CC 는 어떤 레이어 2채널을 할당을 허락해야한 다면
진행 요소가 "continue"로 설정되어DJ DLtSMS D-TX CONTINUE PDU 은 전송했을 것이다,
그것은 전송을 계속 하기 위해 초기에 MS 에 허가를 줘야했을 것이다.
MS 전송허가를 전송하기 위해서 T311 타이머를 시작해야할 것이다.
[/code]
All CC sub-entities shall return to state CALL ACTIVE and shall send a CONFIGURE request primitive to the lower layers to switch the U-plane on.
[code]
CC 보조 엔티티들은 CALL ACTIVE 상태를 반환하거나 U-plane on 을 스위칭을 위해 CONFIGURE request primitive 를 lower layer들에게 보내야할 것이다.
[/code]
A group-addressed D-TX CONTINUE PDU shall apply to all the MSs in the call (including the awarded MS).
[code]
그룹 주소들은 D-TX CONTINUE PDU 를 콜 내에 모든 MS 들에게 적용해야할 것이다.
[/code]
Optionally, the D-TX CONTINUE PDU may also be sent individually addressed to the awarded MS enabling the SwMI to obtain a layer 2 acknowledgement from that MS.
[code]
선택적으로,
D-TX CONTINUE PDU 는 MS가 layer 2 를 얻었다는걸 확인해주기 위해서 각각의 주소를 MS에 활성화하고 있는 SwMI에게 수여했던 것을 전송했었을 것이다.
[/code]
3) If there was one MS granted transmission at the time when the SwMI sent the D-TX WAIT PDU but the SwMI wishes to give the transmission permission to the other party or if no MS was granted transmission at the time when the SwMI sent the D-TX WAIT PDU and the SwMI wishes to give the transmission permission now to one party, the SwMI may first send a D-TX CONTINUE PDU.
[code]
만약 MS 가 시간내에 전송을 허가했었다면 SwMI 는 D-TX WAIT PDU 를 전송했었던 때이다.
하지만 SwMI 가 다른 파티 로 전송을 허가를 주기를 바라는 때나
시간내에 전송 허가를 받은 MS 가 아니라면 D-TX WAIT PDU 를 전송한 상태이거나 SwMI 가 하나의 파티에 전송 허가를 지금 주기를 원할 때,
SwMI 는 D-TX CONTINUE PDU 를 처음 전송할 지도 모른다.
[/code]
If a MS has requested permission to transmit during the period when the transmission was withdrawn, the SwMI should first send a D-TX CONTINUE PDU as a group message with the Continue element set to "not continue".
[code][/code]
A D-TX GRANTED PDU should then be sent as an individual message to the granted MS with information element transmission grant set to "transmission granted" and as a group message to the rest of the group with information element transmission grant set to "transmission granted to another user".
[code][/code]
When receiving either D-TX CONTINUE or D-TX GRANTED PDU the CC sub-entity shall return to state CALL-ACTIVE.
[code][/code]
In addition when receiving D-TX GRANTED PDU CC shall send a CONFIGURE request primitive to the lower layers to switch the U-plane on.
[code][/code]
If the MS is in state WAIT and it receives a D-TX GRANTED PDU, it shall return to state CALL-ACTIVE and obey the instruction in the D-TX GRANTED PDU.
[code][/code]
e) End of Transmission
[code][/code]
At the end of a transmission the user application shall send a TNCC-TX request primitive to the TNCC-SAP indicating ceased transmission.
[code][/code]
The CC sub-entity shall send this information in a U-TX CEASED PDU and stop timer T311.
[code][/code]
The CC shall send the U-TX CEASED PDU with the stealing permission set to "immediate stealing" and the stealing repeats flag set.
[code][/code]
Upon reception of the U-TX CEASED PDU, the SwMI normally sends a D-TX CEASED PDU to the group informing the group members that the transmission has now ceased.
[code][/code]
Upon reception of a D-TX CEASED PDU the CC shall send this information to the user application in a TNCC-TX indication primitive (transmission ceased) and the CC shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane off, see figure 14.18.
[code][/code]
Also, if the CC that is sending the U-TX CEASED PDU receives a REPORT indication of either successful or unsuccessful transmission of that PDU by the lower layers, then it shall behave as if it had received a D-TX CEASED PDU i.e. it shall send a TNCC-TX indication (transmission ceased) to the user application and shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane off.
[code][/code]
If a D-TX CEASED PDU is received but no REPORT indication of successful transmission of the U-TX CEASED PDU then the CC shall send a CANCEL request primitive to the lower layers to stop retransmissions of the U-TX CEASED PDU.
[code][/code]
NOTE 4: The requirement for the CC to cancel retransmissions may apply if the SwMI sends only a group-addressed D-TX CEASED PDU and the transmitting MS does not receive a layer 2 acknowledgement.
[code][/code]
If there was a request for transmission already queued in the SwMI when the U-TX CEASED PDU was received, the SwMI may send a D-TX GRANTED PDU as an individual message to the granted MS and another D-TX GRANTED PDU as a group message to the rest of the group as described in clause 14.5.2.2.1. b), without sending an explicit D-TX CEASED PDU. However, the SwMI should first send at least a layer 2 acknowledgement to the MS that sent the U-TX CEASED PDU so that the MS can stop its U-plane transmission and start accepting group addressed D-TX GRANTED PDUs.
[code][/code]
The SwMI shall not send an unsolicited, individually addressed D-TX CEASED PDU but it is recognized that a race/error condition may result in the MS receiving one. If CC receives an unsolicited, individually addressed D-TX CEASED PDU it shall send this information further on to the user application in a TNCC-TX indication primitive (transmission ceased) and shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane off.
[code][/code]
f) Stop-transmission order
If a MS wishes to interrupt the transmitting MS with a pre-emptive priority request, it shall send a U-TX DEMAND PDU indicating the level of priority in the "TX demand priority" element. If the SwMI supports transmission interruption, it shall send a D-TX INTERRUPT PDU to the MS which currently has permission to transmit.
[code][/code]
Upon reception of an individually addressed D-TX INTERRUPT PDU the CC sub-entity shall remain in state CALL-ACTIVE, and shall stop timer T311.
[code][/code]
The CC shall send information to the user application in a TNCC TX indication primitive indicating transmission interrupt and the CC sub-entity shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane accordingly (see clause 14.5.2.4).
[code][/code]
The SwMI should send a D-TX INTERRUPT PDU as a group message to the rest of the group indicating that the permission to transmit has been (or will be) allocated to another user, see figure 14.18. Upon reception of the D-TX INTERRUPT PDU the CC sub-entity shall remain in state CALL ACTIVE and shall send a TNCC-TX indication primitive to the user application indicating transmission interrupt. The SwMI should then send a D-TX GRANTED PDU as an individual message to the MS that requested the priority transmission.
[code][/code]
The D-TX INTERRUPT PDU shall indicate that transmission is granted to another user and then the MS shall switch to (or remain in) U-plane reception. Otherwise, if there is a delay before the pre-emptive priority transmission, the SwMI
may indicate "transmission not granted" in the D-TX INTERRUPT PDU. Then the MS shall switch the U-plane off and wait for a D-TX GRANTED PDU.
[code][/code]
g) Expiry of timer T311: call transmission timer.
Upon expiry of timer T311, CC shall remain in state ACTIVE, shall send a TNCC-TX indication primitive to the user application and a U-TX CEASED PDU to the peer entity.
[code][/code]
14.5.2.2.2 Call status information procedures
The D-INFO PDU can be used for carrying call status messages from SwMI to the MS. When a D-INFO PDU is received, depending on the notification, the following actions shall be taken by CC:
[code][/code]
a) call in queue:
- when the SwMI has put a call into a queue, if the D-INFO PDU contains a value for the call time-out, set-up phase, the CC shall start timer T302 using that value.
[code][/code]
The CC shall send the information further on to the application in a TNCC-NOTIFY indication primitive.
[code][/code]
If the call is queued at call set-up time the D-INFO PDU should be preceded by a D-CALL PROCEEDING PDU;
[code][/code]
b) call is proceeding:
- this may be sent to the calling user application during the call set-up phase to indicate that the call set-up time will be longer than for a normal call set-up. The information that the call time-out, set-up phase value shall be changed is made available to the CC sub-entity in the D-INFO PDU. The CC shall start T302 using the new timer value. The CC shall send the information further on to the application in a TNCC-NOTIFY indication primitive;
[code][/code]
c) prolonging the call time-out time:
- the SwMI may decide to change the call time-out time by sending a D-INFO PDU with a new T310 value. Upon reception of the D-INFO PDU containing the "call time-out" element, T310 shall be started using the defined value. If the SwMI supplies a T310 value in the D-INFO PDU, it shall set the value of the "reset call time-out timer" element of the PDU to indicate reset of T310;
[code][/code]
- the SwMI may also choose to reset the call time-out time and start it again using the current defined value. Upon reception of the D-INFO PDU with the "reset call time-out timer" element indicating that T310 shall be reset, T310 shall be started using the value defined earlier;
[code][/code]
- in either case, the Timer value shall be sent further on to the application in a TNCC-NOTIFY indication primitive;
- the SwMI may also change the call timeout time during call restoration by supplying the "call time-out" element in the D-CALL RESTORE PDU, refer to clause 14.5.2.2.4. If the SwMI supplies a T310 value in the D-CALL RESTORE PDU, it shall set the value of the "reset call time-out timer" element of the PDU to indicate reset of T310.
[code][/code]
14.5.2.2.3 Call modification procedures
The MS service user may modify the service of an existing call. To initiate a modification the user application shall issue a TNCC-MODIFY request primitive and the CC sub-entity shall send a U-INFO PDU and wait for a D-INFO PDU from the SwMI before changing any of the current service parameters. The SwMI should not send D-INFO PDU to modify a service while an ongoing U-Plane transmission is in progress.
[code][/code]
When a service has been changed by the SwMI, the SwMI should indicate this to all parties by issuing the D-INFO PDU. Upon reception of a D-INFO PDU indicating an acceptable service modification the CC sub-entity shall send it to the application in a TNCC-MODIFY indication primitive, and the CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration.
[code][/code]
If the SwMI is unable to provide the requested service, it should either send a D-INFO PDU to the requesting party containing the current service (unchanged), or send a D-INFO PDU to all parties containing an alternative service.
[code][/code]
For example, if a user application requests an increase from a 1-slot per frame call to a 4-slots per frame call, and the SwMI is unable to allocate more than 2 slots to the call, it may offer a 2-slots per frame call in the D-INFO PDUs.
[code][/code]
The service may be changed between any combination of one or more of the following:
[code][/code]
• a clear call may be changed to an encrypted call; or
• an encrypted call may be changed to a clear call;
• a 4-slots-per-frame call may be changed to a 1-slot, 2-slot or 3-slot call;
• a 3-slot call may be changed to a 1-slot, 2-slot or 4-slot call;
• a 2-slot call may be changed to a 1-slot, 3-slot or 4-slot call;
• a 1-slot call may be changed to a 2-slot, 3-slot or 4-slot call;
• a circuit mode type (TCH/S, TCH/7.2, TCH/4.8 or TCH/2.4) may be changed to a different circuit mode type
(with the requested interleaving depth in the case of TCH/4.8 or TCH/2.4);
• a protected circuit mode data type (TCH/4.8 or TCH/2.4) may be changed to a different interleaving depth
from the set of permissible values (N = 1, 4 or 8).
[code][/code]
NOTE: The clear and encrypted calls refer to the end-to-end clear and encrypted calls. The end-to-end encryption control is independent of the air interface encryption control. It is also possible to change between the circuit mode speech teleservice and a circuit mode unprotected (speech, encrypted) bearer service.
[code][/code]
The encryption state of each transmission, defined using D-TX GRANTED, can be set independently by the encryption control element in the U-TX DEMAND PDU. The SwMI should not change the requested encryption state in the responding D-TX GRANTED PDU from that requested in the U-TX DEMAND PDU.
[code][/code]
If the MS cannot support a new service combination indicated by D-INFO, D-TX GRANTED or D-TX INTERRUPT, the user application or the CC as appropriate shall disconnect or leave the call, refer to clause 14.5.2.3. The U-DISCONNECT PDU shall contain disconnection cause "requested service not available". In case the rejection results from unsupported encryption flag state the disconnect cause shall be "Called party does not support encryption" or "Called party requires encryption".
[code][/code]
14.5.2.2.4 Call restoration procedures
Call restoration of a group call shall only take place in the CC sub-entity when the CC has entered state CALL-ACTIVE. The CC sub-entity should keep information on whether it is active in a group call or an individual call.
[code][/code]
When the CC receives a BREAK indication primitive, the CC shall switch the U-Plane off as described in clause 14.5.2.4 and shall remain in state CALL-ACTIVE. If the CC had permission to transmit/send data at that time the CC shall assume that the permission is now ended as if the CC had sent a U-TX CEASED PDU.
[code][/code]
If the MS is in state WAIT when it receives a BREAK indication primitive then it shall behave as if it had received a D-TX CONTINUE PDU with the continue element set to "not continue". It shall then obey the instructions in the D-CALL RESTORE
PDU.
[code][/code]
If the CC receives a RESUME indication primitive indicating that the C-Plane may now be used again, it shall issue a U-CALL RESTORE PDU containing the GSSI or GTSI and the call identifier of the call which CC wants to restore.
[code][/code]
If a temporary address is used in the call then it shall be used as the GSSI. If the MS is participating in a call within a
group that does not belong to current network (e.g. the MS has migrated and the group belongs to its home network) the CC shall use the full GTSI of the group in the U-CALL RESTORE PDU.
[code][/code]
If the CC wishes to continue transmission in the new cell, or keep a queued transmission request valid in the new cell, it shall indicate so in the request to transmit/send data information element in the U-CALL RESTORE PDU.
[code][/code]
A MS which has requested for transmit permission on a previous cell and has received a "transmission request queued" esponse or no response at all on that cell, may either refresh the transmission request by requesting for transmit permission in the U-CALL RESTORE PDU on the new cell, or withdraw the transmission request by requesting for receive permission in the U-CALL RESTORE PDU on the new cell. A MS which attempts call restoration having received a "transmission request queued" indication on a previous cell can assume that its transmission request is still held in the SwMI's queue unless the MS receives a "transmission not granted" indication within the call restoration signalling. After sending a U-CALL RESTORE PDU,
[code][/code]
the CC shall start Timer T307 and wait for a D-CALL RESTORE PDU.
[code][/code]
When the CC receives a D-CALL RESTORE PDU, timer T307 shall be stopped and the call shall be resumed with the new parameters, see figure 14.19. The CC shall obey the transmission granting in the transmission grant information element, refer to clause 14.5.2.2.1.
[code][/code]
Timer T310 shall be reset and started only if the "Reset call timeout" information element value is 1 (Reset call time-out timer T310); the T310 value shall be taken from the D-CALL RESTORE PDU call timeout information element and, if not present in the PDU, from the previous value (provided in D-CONNECT, D-CONNECT ACKNOWLEDGE, D-SETUP or D-INFO PDU). If appropriate the CC shall issue a CONFIGURE request primitive to switch the U-Plane on using the procedure in clause 14.5.2.4.
[code][/code]
If a MS restores to a cell without requesting for transmit permission and receives an individually addressed D-CALL RESTORE PDU with "Call status" element having value "Call is queued" (indicating that the cell has no available traffic resources), the value of the "Transmission grant" element in the D-CALL RESTORE PDU shall be "Transmission not granted".
[code][/code]
If the call subsequently proceeds to traffic (it may be cleared while queued), the MS shall expect to receive one of the following PDUs; the MS shall then expect no further signalling for the call restoration:
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission granted to another user". The MS shall switch the U-plane on; the MS is authorized to receive traffic;
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission not granted". The MS shall retain its current U-plane state (and shall perform the channel change).
[code][/code]
If a MS restores to a cell, requests for transmit permission, and receives an individually addressed D-CALL RESTORE PDU with "Call status" element having value "Call is queued" (indicating that the cell has no available traffic resources), the value of the "Transmission grant" element in the D-CALL RESTORE PDU shall be either "Transmission request queued" (MS shall wait for further signalling to indicate the result of its request to transmit) or "Transmission not granted" (MS's request to transmit is rejected). If the call subsequently proceeds to traffic (it may be cleared while queued), the MS shall expect to receive one of the following PDUs:
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission granted to another user". The MS shall switch the U-plane on; the MS is authorized to receive traffic; the MS shall, if its request to transmit was not rejected by the "Call is queued" D-CALL RESTORE PDU, wait for further signalling to indicate the result of its request to transmit;
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission not granted". The MS shall retain its current U-plane state (and shall perform the channel change); the MS's request to transmit, if still outstanding following receipt of the "Call is queued" D-CALL RESTORE PDU, is rejected;
[code][/code]
• individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission request queued". The MS shall not switch the U-plane on (but shall perform the channel change); the MS shall wait for further signalling to indicate the result of its request to transmit. The SwMI shall not use this value of the "Transmission grant" element if the "Call is queued" D-CALL RESTORE PDU rejected the MS's request to transmit; MS behaviour if it receives such a response in this context is outside the scope of the present document;
[code][/code]
• individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission
grant" element having value "Transmission granted". The MS shall switch the U-plane on; the MS is
authorized to transmit. The SwMI shall not use this value of the "Transmission grant" element if the "Call is
queued" D-CALL RESTORE PDU rejected the MS's request to transmit; MS behaviour if it receives such a
response is described in clause 14.5.2.2.1 b) (refer to text describing handling of unsolicited transmission
grant).
[code][/code]
The call length timer T310 shall continue running during the call restoration and on expiry of T310, the procedure defined in clause 14.5.2.3.4 shall apply.
[code][/code]
If the call cannot be restored the CC shall receive a REOPEN indication primitive indicating that the call is lost.
[code][/code]
Upon reception of REOPEN indication primitive or on expiry of timer T307, the CC shall then stop all T3xx timers, clear the call identifier and temporary group address if applicable, and return to state IDLE and it shall send a TNCC-RELEASE indication primitive to the user application with the cause for disconnection, see figure 14.20.
[code][/code]
If the SwMI provides a new call identifier with the D-CALL RESTORE PDU, CC shall use it in all subsequent signalling relating to that call. The MS shall not send any other call related signalling than U-CALL RESTORE PDU, after a cell change, before it has received a D-CALL RESTORE PDU (and possible new call identifier) from the SwMI.
[code][/code]
A MS which is queueing for a traffic channel during restoration and which has an outstanding transmission request, may cancel that transmission request by sending a U-TX CEASED PDU. A MS which is queueing for a traffic channel during restoration and which does not have an outstanding transmission request, may make a transmission request by sending a U-TX DEMAND PDU, providing the SwMI has not disallowed transmission requests (via the "transmission request permission" element).
[code][/code]
If there is more than one circuit mode call active at the time when the MLE-BREAK indication primitive was received, each call shall be restored separately and hence U-CALL RESTORE and D-CALL RESTORE PDUs shall be exchanged one by one for each call.
[code][/code]
14.5.2.2.5 DTMF procedures
When a user application requires to transfer DTMF digits to other user applications during a circuit mode call, it shall issue a TNCC-DTMF request primitive to the CC entity. The DTMF protocol to be used is specified is clause 14.5.1.2.5.
[code][/code]
NOTE 1: The DTMF signalling can be used only after either a D-CONNECT or D-SETUP PDU has been received and the TETRA call is established.
NOTE 2: DTMF signalling may not function correctly during a group call (group addressed basic link LLC acknowledged service is required). The support of DTMF signalling during group calls is outside the scope of the present document.
[code][/code]
14.5.2.2.6 Temporary address handling procedures
The SwMI may allocate a temporary group address for a group call in a D-CONNECT, D-SETUP, D-CALL RESTORE or D-INFO PDU. The temporary address shall be a valid layer 2 address in the MS for reception of group addressed messages for the duration of the call.
[code][/code]
In addition, if the MS calls a group that is not attached in the MS (i.e. the group address is not a valid layer 2 address) when it is registered in the home SwMI of that group, and if the D-CONNECT PDU does not contain the temporary address element, then the MS shall implicitly assume temporary membership of the called group address for the duration of the call. This temporary membership shall apply only after receipt of the D-CONNECT PDU. However, if the D-CONNECT PDU contains the basic service information element with the ommunication type sub-element indicating "point to point" then the MS shall not adopt the called address as a temporary address.
[code][/code]
If the call was set up using a SNA, the calling MS shall not implicitly assume temporary membership of the called group address to which
the SNA corresponds;
[code][/code]
this restriction is imposed because the MS may not know the called group address to which the SNA corresponds, in which case it cannot assume temporary membership of the group.
[code][/code]
NOTE 1: If the SwMI is unsure whether the group address for the call is a valid layer 2 address for the calling MS, the SwMI should allocate the group address as a temporary address to the calling MS; this recommendation is made because if the group address for the call is not a valid layer 2 address, and the SwMI doesn't allocate the group address for the call as a temporary address, the MS will articipate in the call but will ignore all group addressed call maintenance signalling.
[code][/code]
NOTE: 2 In this procedure, if the MS calls a group that it is not a member of (when it is registered in the home SwMI of that group) then it may assume temporary membership of the called group address without having received a temporary address element in the D-CONNECT PDU.
[code][/code]
If the calling user has made an erroneous selection of communication type then this could result in the calling MS adopting another MS's
individual address as a temporary group address. Therefore the SwMI should check that the called address in a requested group call is actually a group address;
[code][/code]
if it is not then the SwMI should either disconnect the call or correct the communication type to "point to point" when sending the D-CONNECT PDU (the SwMI may also choose to correct the communication type to "point to point" in a D-CALL PROCEEDING, D-INFO or D-ALERT PDU).
[code][/code]
The CC sub-entity shall send a CONFIGURE request primitive informing the lower layers of the new temporary address and if required the change of basic service from individual to group call.
[code][/code]
When the call is then released, the CC sub-entity shall send a CONFIGURE request primitive informing the lower layers that the temporary group address is not longer valid (see clause 14.5.2.3).
[code][/code]
14.5.2.2.7 Calls to and from external subscribers
An external subscriber can call TETRA group numbers. The signalling needed between an external subscriber and a gateway is outside the scope of the present document. The signalling between the SwMI and the called group is the same as that for a mobile originated group call.
[code][/code]
The CC procedures handled by CC shall be applicable for circuit mode calls for both speech and data.
[code]CC 말하고 데이터를 양쪽무데에게 서킷모드콜들에을 지원하는 것에 의해서 CC 의 절차를 다룰 것이다.[/code]
The circuit mode speech and data group calls shall be set-up as point-to-multipoint calls.
[code]서킷모드로 말하고 데이터 그룹콜을 P-TO-M CALL ㅇ서 설정할 때[/code]
The specification below shall be applicable for the procedures that reside in the MS.
[code]특정 아래로 MS 내에 거주하는 절차를 위해서 적용할 수 있을 것이다.[/code]
14.5.2.1 Call set-up procedures
a) Normal group call
The normal group call procedures provide support for one type of call set-up, where the MS is placed immediately into the call upon receipt of the D-SETUP PDU if the called user application can support the call and with immediate action being taken by the called user application, refer to figure 14.16.
[code]
콜설정의 하나의 형태를 위해서 기본그룹 콜 절차 제공 지원을 한다.
MS 는 D-SETUP PDU 의 receipt 위의 call 내애서 즉시알아낸다.
만약 called 한 사용자가 call 그리고 called 사용자 요청에 지금의 액션전에 얻을 수 있다는것을 지원을 한다면
[/code]
The set-up signalling procedures shall allow immediate communication to take place
between the calling and called user applications without the possibility of having an alerting process and without an explicit response from the called user application stating that the user has answered.
[code]
setup signalling 절차를 바로 전달을 허용해야할 것이다.
calling 그리고 called 사용자 요구 밖에서 경고 프로세스를 얻으수있지 않고 그리고 caleld 사용자 요청으로 사용자에게 응답을 시작한것 에의해 명시적으로 답변하는 동안에 알아 낼 것이다.
[/code]
The call priority may affect whether the user application accepts the call or not.
[code]
콜에 중요도가 발생하는걸 인지할 것이다. 사용자 요청 승낙에 call 혹은 not
[/code]
NOTE: The behaviour of the user application between the reception of the incoming set-up signalling and the acceptance/reject of the call is outside the scope of the present document.
[code]
incoming 설정 시그널링 의 reception 그리고 현재 문서내에 범위 밖에 있는 콜의 받아들임/거부 의 범위에서 사용자 요청의 행동이다.
[/code]
The MS does not signal that acceptance or rejection to the BS. user
[code]
MS는 시그널을 받아들이거나 거부하지 않을 것이다. BS 으로
[/code]
b) Acknowledged group call
An acknowledged group call allows the SwMI to poll members of the called group during the call.
[code]
call 의 그룹 수신 허가는 SwMI 에서 member 들 끼리 called group call을 하는 동안 묻는다.
[/code]
The call may be through connected to the calling MS either before polling or after polling has taken place (see clause 14.5.2.6), refer to figure 14.17.
[code]
calling MS 을 연결을 통해서 어쩌면 폴링이전 또는 폴링 이후 알아내어 얻었을 것이다.
[/code]
c) Broadcast call
The call set-up procedure for broadcast call shall be the same as that for group call as shown in figure 14.16. However,
in this case the called MSs shall not be allowed to subsequently request transmit permission.
[code]
브로드캐스팅읠 위한 콜 설정 절차 는 그림의 그룹콜을 하기위해 그것과 같을 것이다.
[/code]
14.5.2.1.1 Incoming call
Notification of the arrival of an incoming call to the CC sub-entity shall be made by the reception of a D-SETUP PDU which shall be delivered to the user application in a TNCC-SETUP indication primitive via the TNCC-SAP.
[code]
도착하는 콜에 도착의 통지가 하기 위해서 D-SETUP PDU 의 reception 에 의해 CC sub-entity가 만들어진다.
TNCC-SETUP indication primitive 는 TNCC-SAP를 거친 것에 사용자 요청을 위해 전달할 것이다.
[/code]
The CC shall enter state MT-CALL-SETUP. If the user application can support the call, it shall immediately return a TNCC-SETUP response primitive.
[code]
CC는 MT-CALL-SETUP 상태로 들어갈 것이다. 만약 사용자 요구를 지원한다면 CALL이 그것은 즉시 TNCC-SETUP response primitive를 반환할 것이다.
[/code]
On reception of a TNCC-SETUP response primitive the CC sub-entity shall enter state CALL ACTIVE and take the following actions, which are dependent upon the information contained within the PDU elements, see figure 14.16, right hand side:
[code]
TNCC-SETUP response prmitive 의 reception 위에 CC sub-entity 는 CALL ACTIVE 상태에 들어가고 다음 동작을 얻을 것이다. 독립되지 않은 정보에 실려 있을 PDU 요소에
[/code]
• the call identifier shall be used as the reference to this call in subsequent PDUs for the duration of the call;
[code]
이 콜의 식별자는 CALL 이 지속하는 동안 다음에 일어난 call을 조회선택할 것이다.
[/code]
• when CC receives TNCC-SETUP response primitive indicating that the called user application has accepted
[code]
CC는 받을 것이다 TNCC-SETUP response prmitive 는 called 사용자 지원 을 받아들여 담을 것이다.
[/code]
the incoming call, the CC sub-entity shall enter state CALL ACTIVE and start timer T310. The D-SETUP PDU shall contain an indication in the transmission grant element whether the MS should switch to U-plane reception.
[code]
incomming call, CC sub-entity는 CALL ACTIVE 상태에 들어갈것이다 그리고 T310 타이머를 시작한다.
D-SETUP PDU 는 담고 있을 것이다. transmission grant element 내에서 MS U-plane reception을 위해 switch 를 인지하고
[/code]
If the D-SETUP PDU contains an indication that the MS is allowed to request transmission permission it may follow the transmission control procedures described in clause 14.5.2.2.1 a).
[code]
D-SETUP PDU는 담고 있을 것이다. 지시를 그것은 MS 가 허락한 요청 전송허가 이다. 그것은 다음 전송 제어 절차를 묘사하고 있다 그림을 보아
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration accepting the channel change;
[code]
CC sub-entity는 전송할 것이다. CONFIGURE reqeust primitive 를 lower layer configureation 허락을 위해서 채널을 변경한다.
[/code]
• where the called user application is unable to accept the request for a certain target service, the call shall be rejected locally by issuing a TNCC-RELEASE request primitive via the TNCC-SAP and the CC shall enter state IDLE. No negotiation with the BS shall be possible.
[code]
called 사용자는 어디서 접근을 할수없나, 그 요청은 확실한 타겟 서비스를 위한것이다. call은 거부햇었을 것이다. TNCC-RELEASE request primitive가 TNCC-SAP를 통해 공표했던것에 내부에서 그리고 CC는 IDLE상태로 들어갈 것이다. BS가 가능했었던 것과 함께 협상은 없을 것이다.
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration rejecting the channel change.
[code]
CC sub-entity 는 전송해야할 것이다. CONFIGURE request primitive 가 lower layer configureation 을 거부하기 위해서 채널 변경을한다.
[/code]
14.5.2.1.2 Outgoing call
A user application initiates call establishment by transferring a TNCC-SETUP request primitive across the TNCC-SAP to the CC sub-entity. The TNCC-SETUP request primitive shall be handled by a CC sub-entity that is in state IDLE.
[code]
TNCC-SETUP request prmitivei 맞은편에 TNCC-SAP 에서 CC sub-entity로 전송하기를 위한 사용자 요청 초기화 call 시설은
CC sub-entity 에 의한 핸들일 일것이다. TNCC-SETUP request prmitive 의 그것인 IDLE 상태내 일것이다.
[/code]
The CC shall select a PDU priority based on the requested access priority value as defined in clause 14.5.6.2.
[code]
CC 다음 장에 요청되었던 접근 중요 값 에 PDU 중요 중심이 선택된다.
[/code]
The CC shall convert this request into a U-SETUP PDU and send it.
[code]
CC 는 U-SETUP PDU 로 요구를 변경해서 보낸것이다.
[/code]
The CC sub-entity shall then enter the MO-CALL-SETUP state and start timer T303, see figure 14.16 - left hand side.
[code]
CC sub-entity는 MO-CALL-SETUP 로 들어갈것이다. 그리고 t303 타이머를 시작한다.
[/code]
The following text describes the normal call set-up procedures:
[code]
다음 텍스트 묘사는 기본 콜 설정 절차이다.
[/code]
• to indicate the progress of the transmission of the U-SETUP PDU the CC may receive one or more REPORT indication primitives.
[code]
U-SETUP PDU의 전송의 지시
CC 하나를 받거나 더 많이 받을 것이다. REPORT indication primitive 를
[/code]
If the CC receives a REPORT indication primitive informing that the PDU transmission has failed, timer T303 shall be stopped, and the CC sub-entity shall inform the user application with a TNCC-RELEASE indication primitive and return to state IDLE;
[code]
CC 가 REPORT indication primitive가 알림을 받으면 그것은 PDU 전송 실패한것이다, 타이머 T303은 멈췃을 것이다, 그리고 CC sub-entity 알릴 것이다. TNCC-RELEASE indication primitive 그리고 idle 상태를 돌리는 거소가 함께
[/code]
• the SwMI may respond to the reception of the U-SETUP PDU with a D-CALL PROCEEDING PDU. Upon reception of the D-CALL PROCEEDING PDU, the CC shall inform the user application by issuing a TNCC-PROCEED indication primitive, stop timer T303, and start timer T302;
[code]
SwMi는 D-CALL PROCEEDING PDU 와 함께 U-SETUP PDU의 reception으로 답할 것이다.
D-CALL PROCEEDING PDU 의 reception 위에, CC는 TNCC-PROCEED indication primitive 를 발급하므로서 사용자 요청을 알려야할 것이다.
T303 타이머는 멈추고, T302 타이머가 시작할 것이다.
[/code]
• the D-CALL PROCEEDING PDU shall contain a call identifier which shall be used as the reference to this call in subsequent PDUs for the duration of the call;
[code]
D-CALL PROCEEDING PDU 는 콜 식별자를 담을 것이다. 전화하는 시간을 다음의 PDU들에서 현재 CALL 로 사용 되었을 것이다.
[/code]
• the D-INFO PDU shall not be used to allocate a call identifier;
[code]
D-INFO PDU는 선택하지 않을 것이다. 분배를 콜에 식별자를
[/code]
• on reception of a D-INFO PDU after reception of D-CALL PROCEEDING PDU but before the call set-up is completed, the CC shall start timer T302 from the value indicated in the call time out, set-up phase element if that element is present;
[code]
D-INFO PDU 의 reception 이후에 D-CALL PROCEEDING PUD 의 reception
하지만 콜 설정 완료 이전에 ,
CC는 T302 타이머를 시작할 것이다. call time out 내의 지시한 값에 의해서
설정 상태 요소
만약 그 요소는 소개한다.
[/code]
• if the call through connection is ready at the time when the D-CALL PROCEEDING PDU should have been sent, a D-CONNECT PDU should be sent instead. In this instance the D-CONNECT PDU shall allocate the call identifier;
[code]
call 일 연결을 통하면 시간이 준비되었다 D-CALL PROCEEDING PDU 가 전송해야 할것이다. D-CONNECT PDU 는 대신에 전송햇 해야할것이다.
그 인스턴스 안에서 D-CONNECT PDU 는 할당할 것이다. call 식별자를
[/code]
• on receipt of a D-CONNECT PDU, the CC shall enter state CALL-ACTIVE, and inform the user application with a TNCC-SETUP confirm primitive, and stop timer T302 or T303 and start timer T310.
[code]
D-CONNENCT PDU 의 receipt, CC 는 CALL-ACTIVE 상태로 진입할 것이다. 그리고 TNCC-SETUP confirm primitive 가 있는 사용자 요청을 알린다.
그리고 T302 나 T303 타이머를 정지 하거나 T310 타이머를 시작한다.
[/code]
The D-CONNECT PDU shall contain an indication as to whether the CC has been given permission to transmit.
[code]
D-CONNECT PDU 는 인지한 지시를 담아야할 것이다.
CC 는 전달 허가를 주었다.
[/code]
If transmission is not granted and the D-CONNECT PDU contains an indication that the MS is allowed to request transmission permission it may follow the transmission control procedures defined in clause 14.5.2.2.1.
[code]
만약 전달 허가가나지 않았거나 D-CONNECT PDU 지시를 담는다면 MS 는 요청 전달 허가를 허락할것이다. 그것은 다음 전송허가 절차 에 묘사되어 있을 것이다.
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration accepting the channel change. If the CC has been given permission to transmit then it shall start timer T311;
[code]
CC sub-entity 는 전달할것이다.
CONFIGURE reqeust primitive를 lower layer configuration 의 채널이 변경되는걸 받아들이기 위해서
CC 는 전송 허가를 줄것이다 그렇다면 T311 타이머가 시작되었을 것이다.
[/code]
• where the D-CONNECT or D-CALL PROCEEDING PDU indicates that the offered service is different to the one requested, and if the service offered is acceptable to the CC sub-entity according to the selected lowest service in the TNCC-SETUP request primitive, then the call shall continue.
[code]D-CONNECT 혹은 D-CALL PROCEEDING PDU는 가르킬 것이다. 그것은 그 서비스를 제공할 것이다. 요청했던 다른
그리고 CC sub-entity TNCC-SETUP request primitive 내의 선택된 lowest 서비스를 위해 sub-entity에 따라서 서비스 지원을 받아들일수 있을 것이다. call은 계속 될 것이다.
[/code]
If it is not acceptable, then the CC shall disconnect the call using the procedures in clause 14.5.2.3.1;
[code]
그것을 받아들이지 않는다면 CC 는 disconnect할것이다. 14장에 절차에 의해서 call이
[/code]
• the network may support other signalling from the calling MS to the SwMI and vice versa during the call setup phase using U-INFO and D-INFO PDUs, for example, for the purpose of showing the progress of a call setup.
[code]
network는 제공해야할 것이다. 다른 시그널링을 calling ms 에 의해서 SwMI으로 그리고 U-INFO 그리고 D-INFO PDU들을 사용하는데 불량한 콜 설정중이라면 예로 call 설정의 보여주는 진행을 목적으로
[/code]
• on reception of a group addressed D-SETUP PDU after reception of D-CALL PROCEEDING PDU (and optionally D-INFO PDU), if the call identifier in the D-SETUP is the same as the call identifier in the D-CALL PROCEEDING PDU and the calling party address in the D-SETUP PDU does not contain the MS's own address, the CC sub-entity shall enter state CALL ACTIVE, stop timer T302 and start timer T310.
[code]
그룹 주소을 쓰다 reception D-SETUP PDU 후에 D-CALL PROCEEDING PUD 의 reception (그리고 선택한 D-INFO PDU), 만약 D-SETUP 내의 call 식별자가 D-CALL PROCEEDING 내 콜 식별자와 같다면 그리고 D-SETUP PDU 가 MS 소유의 주소를 담지 않은것내의 calling party address ,
CC sub-entity 는 CALL ACTIVE 상태로 들어갈 것이다,
T302 타이머는 정지하고 T310 타이머는 시작할 것이다.
[/code]
The D-SETUP PDU shall contain an indication in the transmission grant element whether the MS should switch to U-plane reception.
[code]
D-SETUP PDU는 transmission grant 요소를 인지해 지시를 담을 것이다.
MS 는 U-plane reception 을 스위칭할 것이다.
[/code]
If the D-SETUP PDU contains an indication that the MS is allowed to request transmission permission it may follow the transmission control procedures described in clause 14.5.2.2.1 a).
[code]
D-SETUP PDU는 지시를 담는다. MS 는 request transmission permission 을 허락할 것이다. 그것은 다음에 장에 transmission control 절차를 담고 있을 것이다.
[/code]
The CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration accepting the channel change.
[code]
CC sub-entity는 전송할 것이다. CONFIGURE request primitive를 lower layer configureation 이 채널 변경을 받아들이기 위해서
[/code]
CC shall ignore the D-SETUP PDUif the calling party address is the same as the MS's own address and shall send a CONFIGURE request primitive for lower layer configuration ignoring the channel change.
[code]
CC는 무사힐 것이다 D-SETUP PDU 를 만약 calling party address 가 MS이 소유하고 있는 주소 그리고 lower layer configuration 채널전환을 무시하기위해 전송해야할 CONFIGURE request primitive 와 같을 때
[/code]
A MS following a group addressed D-SETUP in the manner described in this clause shall cancel its request to transmit if it requested to transmit in the U-SETUP PDU.
[code]
이장에서 취소한느 방법을 묘사한 것에 MS 다음에 그룹 주소를 D-SETUP 에 쓰는 것은 그것은 U-SETUP PDU 내 전달하기 위해 요청햇던 것일 것이다.
[/code]
NOTE 1: The SwMI should either send the D-CONNECT PDU granting transmit permission first or supply the calling party address in the D-SETUP PDU (or both) to prevent the MS that is about to be granted transmit permission following the group addressed D-SETUP PDU.
[code]
SwMI는 D-CONNECT PDU 첫번째로 허가 전달 을 들어주거나 D-SETUP PDU 가 막기 위해서 calling party address 를 공급하며 둘중에 하나를 전달할 것이다. MS 는 전달허가를 승인할것이다. 다음에 그룹에 D-SETUP PDU 에 주소를 적기 위해서
[/code]
NOTE 2: Handling of the TNCC-SETUP request primitive may be affected by the MS being active in a MM procedure, this being indicated to CC from MLE via the MLE-BUSY indication primitive, refer to clause 18.3.5.4.
[code]
TNCC-SETUP request primitive 의 핸들은 어쩌면 MS 처음 활성화에 영향을 미칠것이다. 그것은 MLE-BUSY indication primitive 를 통한 MLE 에 의해서 처음 지시했던 CC 이다,
[/code]
The exact nature of the interaction between MM/MLE and CC is outside the scope of this part of the present document but it is recommended that CC not accept a TNCC-SETUP request primitive while MM is busy.
[code]
상호작용 되는 MM/MLE 그리고 CC 는 현재 문서 범위외에 정확히 나온다 그러나 CC를 적용하지않는걸 추천한다. TNCC-SETUP request primitive 가 MM 으로 busy 하는 동안
[/code]
14.5.2.1.3 Colliding calls
Call collisions can occur when both the SwMI and the MS simultaneously send a D-SETUP PDU and a U-SETUP PDU.
[code]
콜이 충돌이 일어난다면은 SwMi 긜고 MS 가 D-SETUP PDU 그리고 U-SETUP PDU 에 동시 전송할 때
[/code]
Two call set-ups are colliding when a D-SETUP PDU is received within the window where the CC waits for a call identifier from the SwMI after a U-SETUP PDU has been issued. The MS shall be able to handle two types of call collision:
[code]
두개의 콜이 충돌할 때 D-SETUP PDU는 받았을 것이다. 윈도우내에서 CC 가 SwMI에 의해서 call 식별자를 기다린 후에 U-SETUP PDU 가 발행했을때
MS 는 콜 충돌에 2개의 핸들형식으로 충족할 수 있을 것이다.
[/code]
• if the colliding calls are call set-up attempts for the same group and the requested basic services are compatible and the calling MS is a member of that group and layer 2 has not indicated successful transmission of the U-SETUP PDU, then the MS CC shall attempt to discard the outgoing call set-up attempt by sending a CANCEL request primitive to the lower layers to cancel sending of the U-SETUP PDU.
[code]
만약 call 이 출돌한다면 call 설정이 시도할것이다. 같은 그룹을 위해서 그리고 기본 서비스 에 맞게 요청을 햇었ㅇ르 것이다. 그리고 calling MS 는 그룹에 맴버다. 그리고 레이어 2는 소유하지 지시했던 것을 못했을 것이다. 성공한 U-SETUP PDU전송을, 그렇다면 MS CC 는 시도할것이다
CANCEL request primitive 에서 lower layer 가 U-SETUP PDU를 전송하는걸 취소하는 것에 의해서 나가는 call을 설정한다.
[/code]
If cancellation is successful, the MS shall accept the incoming call.
[code]
성공적으로 취소되었을 때 MS는 incoming call을 받아들인다.
[/code]
If cancellation is unsuccessful or if layer 2 has indicated successful transmission of the U-SETUP PDU, the MS shall continue its own call set-up and wait for a D-CALL PROCEEDING and/or D-CONNECT PDU (and/or D-RELEASE PDU);
[code]
만약 성공적으지 않았다면 layer2 는 지시했었을 것이다 U-SETUP PDU의 성공적인 전송을, MS 는 계속해서 할 것이다. 그것은 소유권을 가진 call setup 그리고 D-CALL PROCEEDING and/or D-CONNECT PDU 를 위해서 기다린다.
[/code]
• if the call set-up attempts are not to the same group, then the MS shall either keep its call attempt or accept the incoming call as defined in clause 14.5.2.1.1.
[code]
call setup 를 시도하면 같은 그룹이 아닐때 그렇다면 MS는 어느한 곳을 보관 할것이다 그것은 call 을 시도하거나 Incoming call을 시도할것이다.
[/code]
In the latter case the MS shall first cancel its call set-up locally, if still possible, or otherwise send a U-DISCONNECT
PDU for its own call set-up, refer clause 14.5.2.3.1.
[code]
다음 케이스 내에 MS 는 처음 취소할 것이다. 그것은 call setup은 가까울 것이다. 그것은 가능하거나 U-DISCONNECT PDU 내 내부적으로 전송할것이다. 소유권을 가진 CALL 설정을 위해서
[/code]
If MAC requested a response with the parameter channel change response required value set to "true" with the CC message the CC shall select the proper radio resource by issuing MLE-CONFIGURE request primitive with value "reject" in the first case or "accept" in the latter case. Refer to clause 14.5.3.2.
[code]
만약 MAC에서 응답을 요청햇었다면 응답은 파라메터 채널 변경 응답이 필요한 값 으로 TRUE로 설정되어 있다 CC 메시지 와 함게 CC는 선택할것이다. 알맞는 레이도 리소스를 MLE-CONFIGURE request prmitivie 에 의해서 MLE-CONFIGURE request primitive "reject" 과 함께 처음 케이스 "accept" 케이스내에서 다음 케이스로
[/code]
14.5.2.1.4 Unsuccessful call set-up
Unsuccessful call set-up shall refer specifically to those instances where a circuit mode connection was not successfully established.
[code]
실패한 콜 설정은 특히 그 인스턴스에게 보낼 것이다. 서킷 모드연결을 얻지못했을 때
[/code]
It shall not refer to call disconnection or call rejection. If a PDU is not responded to prior to the expiry of the corresponding timer, the procedure in clause 14.5.2.3.5 shall apply.
[code]
만약 call 해제 혹은 call 거부를 보내지 못한다면 만약에 PDU 가 대응되는 타이머에 절차에 응답하지 못한다면 이전에 만료된
[/code]
All timers available are listed in clause 14.6.
[code]
모든 타이머들을 얻을 수 있는 리스트는 14.6 장에 있다.
[/code]
When CC receives a REPORT indication primitive indicating that the lower layers have not been successful (failed
transfer) in the sending of any of the call set-up PDUs, then the CC sub-entity shall return to state IDLE and inform the
user application with a TNCC-RELEASE indication primitive accompanied with a cause of the disconnection.
[code]
CC는 받을 것이다. REPORT indication primitive에 지시를 그것은 lower layer를 성공적으로 얻을 것이다. 어떤 call setup PDU 의 전송내에서 그렇다면 CC sub-entity 는 반송할 것이다. IDLE 상태를 그리고 전달할 것이다. 사용자 요구에 TNCC-RELEASE indication primitive 와 함께해 수행한다. 연결해제의 목적이 되는...
[/code]
14.5.2.1.5 Call rejection
If the user application decides to reject the incoming call set-up request as defined in clause 14.5.2.1.1, it shall immediately transfer a TNCC-RELEASE request primitive to the CC sub-entity.
[code]
콜의 거부
만약 사용자 요청에 걸려오는 콜의 설정 요청을 거부 결정을 내린다. 14.5.2.1.1 장내에 선언되어 있다.
만약 즉시 전송을 TNCC-RELEASE request primitive CC sub-entity 에게 한다면
[/code]
This request shall locally clear the call identifier. The CC sub-entity shall then change to state IDLE.
[code]
그 요청은 가까운곳에서 call 식별자가 초기화 될 것이다.
그 CC subentity 는 IDLE 상태로 변해야할 것이다.
[/code]
14.5.2.2 Call maintenance procedures
The call maintenance procedures described in this clause may be applied when the MS is in states MO-CALL SETUP, MT-CALL SETUP or CALL-ACTIVE.
[code]
call 에 유지 절차 묘사는 이장에 적용 되어 있다.
MS 는 MO-CALL SETUP 상태 내, MT-CALL SETUP 이나 CALL-ACTIVE
[/code]
The main state CALL-ACTIVE can comprise several sub-states.
[code]
메인 CALL-ACTIVE 상태는 몇개의 보조 상태로 구성되어 있다.
[/code]
NOTE: The D-INFO PDU can be used for other purposes than those defined in the protocol specifications contained in the present document.
[code]
D-INFO PDU 는 다른 목적을 위해서 선택한다.
그 목적은 현재 문서에 프로토콜 스펙에 실려 선언되어 있는 것들이다.
[/code]
14.5.2.2.1 Transmission control procedures
a) Request-to-transmit
The SwMI shall fully control which MS is allowed to transmit. To facilitate this, the MS shall request permission to transmit, and permission shall be granted before the MS can begin circuit mode traffic permission. MSs may request permission to transmit, if the SwMI allows it by a "transmission request permission" element even if another party is transmitting.
[code]
SwMI 는 모두 컨트롤 해야할 것이다. MS 는 전송을 허락할 것이다. 쉽게 한다.
MS 는 전송 하기 위해 요청 허가를 할 것이다, 그리고 MS 가 서킷모드 트레픽 허가를 하기 전에 허락을 승인할 것이다.
MS 들은 전송하기 위해서 요청 허가, 그것은 SwMI 를 허락할 것이다. "tranmission request permission" 요소 조차도
만약 다른 파티를 전송한다면은
[/code]
In this case the SwMI should normally wait for that party to finish the transmission before granting the other user application. Pre-emptive priority requests are dealt with in clause 14.5.2.2.1 f).
[code]
그 케이스에서는 SwMI 가 파티가 종료하기 위해서 정상적으로 기다려야한다. 전송 전에 허락한다. 다른 사용자 요청을.
우선권을 가진 중요한 요청는 14.5.2.2.1 장에 처리되어 있다.
[/code]
The SwMI normally gives the first permission to transmit to the calling MS when a new call has been set-up. However, the calling user application may allow the called users to request permission to transmit first. The calling CC shall in that case set the "request to transmit" bit accordingly in the U-SETUP PDU.
[code]
SwMI 는 정상적으로 준다. 첫번째 calling MS 를 새로운 콜을 설정할때 의 전송 허가. 그러나 그 전화하는 사용자 신청는 허락하기를 바란다. called 사용자 에서 첫번째 전송 요청 허가를 하기 위해서. calling CC 는 "request to transmit" bit 에 맞춰서 설정 케이스 내에서 해야할 것이다. U-SETUP PDU에서
[/code]
When a user within a call wants to transmit, a TNCC-TX request primitive shall be sent to CC via the TNCC-SAP.
[code]
언제 사용자는 call 전송을 원하나, TNCC-TX request primitive 는 전송했었을 것이다. CC 에게 TNCC-SAP 를 통해서
[/code]
The CC shall send this request in a U-TX DEMAND PDU. The TX-DEMAND Priority level should be set to low or high priority, unless this is a pre-emptive priority request, see clause 14.5.2.2.1 f), see figure 14.18.
[code]
CC는 U-TX DEMAND PDU 요청을 전송해야할 것이다.
TX-DEMAND 중요 레벨은 낮거나 높은 중요도로 설정되어야할 것이다. 하지 않으면 pre-emptive prority request,
[/code]
The progress of the transmission of the U-TX DEMAND PDU shall be given locally to the CC in one or more REPORT indication primitives.
[code]
U-TX DEMAND PDU의 전송 작업은 는 내부의 CC 에게 혹은 많은 REPORT indication primitive 에게 줘야할 것이다.
[/code]
If the CC receives a REPORT indication primitive as a response to the sending of the U-TX DEMAND PDU informing that the PDU transmission has failed, the CC shall inform the user application by a TNCC-TX confirm primitive.
[code]
만약 CC 를 받는다면 REPORT indication primitive 가 전송하고 있는 U-TX DEMAND PDU 알리는것을 전송하기 위해서 응답 할 때하고
그것은 PDU 가 전달을 실패했다는 것이다. 그 CC SMS TNCC-TX confirm primitive 에의한 사용자 요청에 알릴 것이다.
[/code]
If a user application wants to withdraw his request-to-transmit before it has been granted, a TNCC-TX request primitive shall be sent from the user application to the TNCC-SAP.
[code]
만약 사용자 요청을 요청을 취소하기를 원한다면 그의 request-to-transmit 전에 그것을 승인했을 것이다, TNCC-TX request primitive 는 전송했었을 것이다. 사용자 요청 TNCC-SAP 를 하기 위해서
[/code]
The CC shall send this request in a U-TX CEASED PDU. The CC shall send the U-TX CEASED PDU with the stealing permission set to "immediate stealing" and stealing repeats flag set so that the permission to transmit will be released immediately if allocated.
[code][/code]
No CC protocol response shall be received from the SwMI for this message.
[code]
메시지를 위해서 SwMi에 의해서 CC 프로토콜 응답이 응답 받는지 않았다면
[/code]
b) Response to request-to-transmit
During a call in progress and when the SwMI has decided which MS shall be given permission to transmit, the SwMI
shall send a D-TX GRANTED PDU as an individual message to the granted MS.
[code]
call 이 작업하는 동안 그리고 SwMI 뚜렷하게 SwMi에게 전송 허락을 주어야할 것이다.
[/code]
Upon reception of a D-TX GRANTED PDU indicating "transmission granted", the CC sub-entity shall send this information to the user application in a TNCC-TX confirm primitive.
[code]
D-TX GRANTED PDU의 "transmission granted" 지시의 reception 위로 CC sub-entity 는 전송해야할 것이다. 그 정보를 TNCC-TX confirm primitive 내에 사용자 신청을 위해서이다.
[/code]
The other MSs involved in the call shall be informed with a D-TX GRANTED PDU addressed with the group address.
[code]
다른 MS들은 call 내에 신고할것이다 복잡하게 그룹 주소와 함께 D-TX GRANTED PDU 주소를 쓸것이다.
[/code]
That D-TX GRANTED PDU shall indicate that permission to transmit has been granted to another user. The CC shall send this information to the user application in a TNCC-TX indication primitive and shall remain in state CALL-ACTIVE, see figure 14.18.
[code]
그 D-TX GRANTED PDU 는 지시해야할 것이다. 그것은 다른 사용자에게 전송을 허락하기 위해서 이다.
그 CC 는 TNCC-TX indication primitive 그리고 CALL-ACTIVE 상태로 남겨지기 위해서 전송해야할 것이다.
[/code]
If the SwMI places the transmission request in a queue this shall be indicated to the MS concerned using the "transmission request queued" parameter value in the D-TX GRANTED PDU.
[code]
SwMI 잘리에 D-TX GRANTED PDU 내의 "tranmission request queued" 파라메터 값 을 사용하여 관계되어진 MS 를 표시하기 위해서 queue 내의 전송 요청한다.
[/code]
If the SwMI rejects the transmission request this may be indicated to the MS concerned using the "transmission not granted" parameter value in the D-TX GRANTED PDU.
[code]
만약 SwMi에 전송요청을 거부한다면 이것은 D-TX GRANTED PDU 내에 MS 관련 되어져 사용한 "transmission not granted" 파라메터 값을 지시하기 위해서
[/code]
In either case, the MSs concerned shall remain in state CALL-ACTIVE.
[code]
MS들은 관계되어 CALL-ACTIVE 상태 로 남아 있을 것이다.
[/code]
Upon reception of a D-TX GRANTED PDU indicating "transmission granted" or "transmission granted to another user", the CC sub-entity shall issue a CONFIGURE request primitive.
[code]
D-TX GRANTED PDU 의 reception 위에 지시할 것이다. "transmission grnated" or "transmission granted to another user"를
CC sub-entity 는 CONFIGURE request primitive 를 이야기할 것이다.
[/code]
The primitive shall carry as a parameter whether the transmit permission has been granted to this CC sub-entity or to another CC sub-entity, and to switch the U-Plane on.
[code]
primitive 는 인지한 파타메터에 나를 것이다.
CC sub-entity 나 다른 CC sub-entity 으로 전송 제어 허가를 위해서 그리고 U-Plane on 스위칭한다.
[/code]
The MS given permission to transmit shall start timer T311.
If the D-TX GRANTED PDU indicates "transmission granted to another user" and contains the MS's own address as the transmitting party address then that MS should not switch to U-plane reception.
[code]
MS 는 시작해야하는 T311 타이머에게 허가를 줄것이다.
만약 D-TX GRANTED PDU 가 "transmission granted to anther user" 그리고 MS들의 전송 파티 주소의 소유를 가진 주소를 표시해야 한다면
그것은 MS 가 U-plane reception 스위칭을 하지 않을 것이다.
[/code]
However it shall not switch to U-plane transmission until it receives a D-TX GRANTED PDU indicating "transmission granted".
[code]
그러나 그게 U-plane을 전송할 때까지 switch 하지 않는다.
그 D-TX GRANTED PDU 가 "transmission granted" 지시를 받는다면
[/code]
Though the MS shall switch to U-Plane receive if it receives a "transmission granted to another user" response to its transmission request and the transmitting party address in the D-TX GRANTED PDU is not the MS's own address, the MS shall require an explicit response to its transmission request: one of "transmission granted", "transmission not granted" or "transmission queued".
[code]
MS 가 U-plane이 받아 스위치 함에도 불구하고
"transmission granted to anther user" 응답을 받았다면
그것을 전송 요청 그리고 D-TX GRANTED PDU 가 MS들의 소유권의 주소가 아닌 전송 파티 주소, 명시적 응답을 위해 필요할 것이다.
"transmission granted", "transmission not granted" or "transmisson queued" 중 하나를 전송 요청한다.
[/code]
NOTE 1: The SwMI should either send the individually addressed D-TX GRANTED PDU ("transmission granted") first or
supply the transmitting party address in the group addressed D-TX GRANTED PDU ("transmission granted to another user") to prevent the MS that is about to be granted transmit permission switching to U-plane receive. As defined in ETS 300 396-5 [11],
clause 9, this is mandatory for the SwMI when granting transmit permission to a Direct Mode MS which is operating through a Direct Mode gateway.
[code]
SwMI 는 각각의 D-TX GRANTED PDU ("transmission granted") 첫번째 주소 나
U-plane을 받기 위해서 전송 허가 스위칭 에 관한걸 막기 위해서 D-TX GRANTED PDU ("transmission granted to another user") 그룹 주소내에 있는 파티 주소를 전송하는것을 지원한다.
이것은 SwMI Direct mode gatewya 명령을 통해서 Direct Mode MS에 허가를 전송 허락하기 위해서 이고
[/code]
(This mandatory requirement applies only if the SwMI has accepted a request from the gateway to operate as a Direct Mode gateway.)
[code]
이것은 의무적인 요구를 적용 한다. 만약 SwMI에 요청을 허락하였다면 Direct mode gateway 에 명령을 하기위한 것에 의해서
[/code]
Upon reception of a D-TX GRANTED PDU indicating "transmission granted to another user", and if the CC sub-entity has issued a U-TX DEMAND PDU to the lower layers and has not yet received a REPORT indication primitive indicating successful or unsuccessful transmission, then the CC sub-entity shall send a CANCEL request primitive to the lower layers to cancel transmission (and retransmissions) of that PDU.
[code]
D-TX GRANTED PDU 의 reception 은 "transmission granted to another user"를 지시를 한다. 그리고 CC sub-entity 는 이야기할 것이다. U-TX DEMAND PDU 가 lower layers 그리고 REPORT indication primitivei 가 아직도 성공 혹은 전송을 실패한걸 받지 않았을 때
그렇다면 CC sub-entity 는 PDU의 전송 취소를 하기 위해 lower layer 에서 CANCEL reqeust primitive 를 전송해야할 것이다.
[/code]
NOTE 2: The above procedure may sometimes stop re transmissions by the awarded MS as well as retransmissions by any other MSs that are requesting transmit permission.
[code]
절차 위에 어떤 시간에이 멈춰야한다면은 부여한 MS 에 재전송을 지나 어떤 다른 MS들에 전송 요청 허가에 의해서 이다.
[/code]
NOTE 3: If the SwMI queues any other transmission requests that it received then it should, at a convenient time, send D-TX GRANTED PDUs containing the "transmit request queued" parameter value to the MSs concerned. For transmission requests that are neither granted nor queued, and if the user application still wishes to transmit, then it has to send another TNCC-TX request primitive to the CC.
[code]
만약 SwMI queue들이 어떤 다른 전송 요청이라면 그것은 받았을 것이다. 그것은 편리한 시간에 할 것이다.
D-TX GRANTED PDU 는 MS 들과 관계된 "transmit request queued" 파라메터 값을 담을 것이다.
전송 허가를 위해서
그것은 queue 또한 허락할 것이다. 그리고 사용자 신청에 전송을 아직 바랄 것이다. 그것은 다른 TNCC-TX request primitiv 에서 CC로 전송하기 위해서이다.
[/code]
After reception of a D-TX GRANTED PDU indicating "transmission granted", and while it still has permission to transmit, the CC shall ignore any group addressed D-TX GRANTED or D-TX INTERRUPT PDUs it may receive (and any layer 2 channel assignment received with those PDUs by issuing an MLE-CONFIGURE request primitive ignoring the channel change, if requested).
[code]
D-TX GRANTED PDU가 "transmission granted" 의 지시를 받아 들인 후에, 그리고 전송 허가를 얻는 동안, CC는 어느 그룹 주소들 D-TX GRANTED or D-TX INTERRUPT PDU 들을 무시할 것이다. 그것은 응답할 지도 모른다. (그리고 어떤 2채널 레이어 임무를 받을 것이다. 그 PDU들과 함께 MLE-CONFIGURE request primitive 채널 변경 무시 에 의해서
[/code]
If the CC sends a U-TX DEMAND PDU whilst another MS is transmitting, the SwMI should normally wait for that party to finish the transmission (identified by the receipt of a U-TX CEASED PDU), before granting transmission permission to the other user application. On receipt of the U-TX DEMAND PDU, the SwMI may send a D-TX GRANTED PDU indicating whether the request-to-transmit is queued or rejected. Pre-emptive priority requests are dealt with in clause 14.5.2.2.1 f).
[code]
다른 MS 에게 전달하는 동안 U-TX DEMAND PDU 가 CC 를 전송한다면은, 파티에 전송을 완료하기 위해 SwMI는 보통 기다려야한다,
다른 사용자 신청 이전에 전송 허가를 하면.
U-TX DEMAND PDU 의 receipt,
SwMI가 D-TX GRANTED PDU 는 지시를 인지해 request-to-transmit 는 queued 나 거부한 것을 전송할지도 모른다.
이장에 선매권있는 중요 요청을 처리한다.
[/code]
The SwMI shall not send an unsolicited D-TX GRANTED PDU but it is recognized that a race/error condition may result in the MS receiving one.
[code]
SwMI 는 부탁받지 않았던 D-TX GRANTED PDU 를 전송하지 않을 것이다.
받고 있는 하나의 결과가 race/error 상태인지 알수 있을지도 모른다
[/code]
The CC may choose to follow an unsolicited individually addressed D-TX GRANTED PDU indicating "transmission granted" but if the CC does not want to transmit/send data then it shall use the U-TX CEASED PDU, as it does normally at the end of a speech or data item, to reject the transmission grant.
[code]
CC 는 부탁받지 않은 각각의 주소 D-TX GRANTED PDU 가 지시한 "transmission granted" 을 따라서 선택했을지도 모른다 하지만 CC는 transmit/send data 하는걸 원하지 않는다 그렇다면 U-TX CEASED PDU 를 선택해야할 것이다, 말하는 혹은 데이터의 끝에 기본적으로 했었을 것이다.
전송 허가 거부를
[/code]
c) Permission to transmit withdrawn
The SwMI may decide to interrupt transmission when resources are required for another call or when the SwMI requires that the call should temporarily pause.
[code]
SwMI 는 interrupt transmission 에 결정을 내려야했었을 것이다
다른 콜을 위해서 리소스를 요청했었을 때 또는 SwMI 가 필요에 의해 일시적으로 멈춰야할때
[/code]
In this case the SwMI should send a D-TX WAIT PDU to all MSs in that call (permitting or denying transmission requests according to the "transmission request permission" element).
[code]
SwMI 는 이 케이스에서 call 내에 모든 MS 들로 D-TX WAIT PDU 를 전달한다.
[/code]
On reception of the D-TX WAIT PDU the CC sub-entity shall send a TNCC-TX indication primitive to the user application
indicating that the transmission is waiting. The CC shall stop timer T311, if activated, enter state WAIT, and send a CONFIGURE request primitive to switch the U-Plane off.
[code]
D-TX WAIT PDU 의 reception 에 CC 보조 엔티티는 사용자 요청 지시로 TNCC-TX indication primitive 를 전송할 것이다.
전달을 기다리라고. CC 는 T311 타이머를 멈춰야할 것이다,
만약 활성화되어 있다면 WAIT 상태로 진입할 것이다,
그리고 U-Plane off 를 하기 위해서 CONFIGURE request primitive 를 전달할 것이다.
[/code]
The CC shall accept any layer 2 channel allocation and await further instructions on the channel that they have been directed to.
[code]
CC 는 어떤 레이어 2채널 할당을 승낙해야할 것이다 그리고 채널에 미래의 명령들을 기다린다 안내를 얻기 위해서
[/code]
If a request-to-transmit has been queued at the time when the D-TX WAIT PDU is received, the MS shall be allowed to withdraw its request-to-transmit by means of the U-TX CEASED PDU as described in clause 14.5.2.2.1 e).
[code]
만약 시간에 request-to-transmit queued 를 얻었다면 D-TX WAIT PDU 를 받았던 때일 것이다, MS 는 묘사된 U-TX CEASED 에 의해서 request-to-transmit 내부적으로 허락을 해야할 것이다.
[/code]
A group-addressed D-TX WAIT PDU shall apply to all the MSs in the call (including the transmitting MS). Optionally, the D-TX WAIT PDU may also be sent individually addressed to the transmitting MS enabling the SwMI to obtain a layer 2 acknowledgement from that MS.
[code]
콜 내에 모든 MS 들에게 그룹 주소 D-TX WAIT PDU 를 적용해야할 것이다.
선택적으로,
D-TX WAIT PDU 는 MS에 레이어 2 를 획득했다고 응답하기 위해서 전송하는 MS에 SwMI를 활성화 하고 각각의 주소들에 전송할지도 모른다.
[/code]
If the SwMI sends a D-TX WAIT PDU because it wishes to use an assigned channel for another call, it shall send a
layer 2 channel allocation with the D-TX WAIT PDU directing the MS to a signalling channel other than the assigned
channel.
[code]
SwMI에 D-TX WAIT PDU을 전송한다면 그건 다른 콜을 위해서 선언되어 있던 채널을 선택하기를 원하기 때문이다,
그것은 D-TX WAIT PDU 가 직접적으로 레이어 2 채널을 할당해 전송해야할 것이다.
MS 에서 시그널링 채널과 다르게 할당할 것이다.
[/code]
This is to prevent the change in usage marker associated with re-allocation of the assigned channel to the other call causing the waiting MS to drop the interrupted call.
[code]
이것은 콜을 인터럽트한것을 떨어뜨리기 위해서 할당되어 있는 채널의 재할당과 관련되어 있는 것을 변경해 적용시켜 다른 콜이 MS 를 기다리게 할것이다.
[/code]
d) Permission to continue with withdrawn call
[code][/code]
There are three cases as follows:
[code][/code]
1) If no MS was granted transmission at the time when the SwMI sent the D-TX WAIT PDU, or if an MS was granted transmission at the time of the D-TX WAIT PDU but the SwMI does not wish that transmission to continue, then either a D-TX CONTINUE PDU with the continue element set to "not continue", or a D-TX GRANTED PDU with the transmission grant element set to "transmission not granted", shall be sent as a group message to all MSs in the group. The CC shall accept any layer 2 channel allocation.
[code]
만약 MS 가 시간에 허가했던 전송이 아니면 SwMI 는 D-TX WAIT PDU를 전송했을것이다, 또는 MS 가 D-TX WAIT PDU 의 시간에 허락일수도있다.
하지만 SwMI는 계속 전송을 원하지 않을 것이다, 진행 요소가 "not continue" 로 설정되면 D-TX CONTINUE PDU 는 양쪽중에 또는 전송 허가 요소가 "transmission not granted" 로 설정하면 D-TX GRANTED PDU 도 계속 전송하지 않을 것이다,
그룹내 모든 MS들의 로 그룹 메시지를 보내야할지도 모른다.
그건 CC 가 어떤 레이어 2 채널을 할당해 허용할 것일지도 모른다.
[/code]
All CC sub-entities shall return to state CALL-ACTIVE but the U-plane shall not be switched on and the MS shall assume that any previous transmission permission no longer applies. If the D-TX CONTINUE PDU contains an indication that the MS is allowed to request transmission permission, it may follow the transmission control procedures described in clause 14.5.2.2.1 a).
[code]
모든 CC 서브 엔티티들은 CALL-ACTIVE 상태를 반환해야할 것이다 하지만 U-plane 은 스위칭하지 않았을 것이다 그리고 MS 는 어떤 이전 전송 허가를 길게 적용하지 않는걸 가정해야 할 것이다. D-TX CONTINUE PDU에 지시를 담고 있다면 MS 는 request transmission permission 을 허락했었을 것이다.
이장에 묘사되어 있는 전송 제어 절차를 따를지도 모른다.
[/code]
2) If there was one MS granted transmission at the time when the SwMI sent the D-TX WAIT PDU, and if the SwMI wishes that transmission to continue,
then either a D-TX CONTINUE PDU with the Continue element set to "continue" shall be sent as a group message to the group, or a D-TX GRANTED PDU with the transmission grant element set to "transmission granted" shall be sent to the granted MS and a D-TX GRANTED PDU with the transmission grant element set to "transmission granted to another" shall be sent as a group message to the group.
[code]
만약 하나의 MS를 시간내에 전송을 허락했었다면 SwMI 가 D-TX WAIT PUD 를 전송햇었을 때, 그리고 SwMI 가 계속 전송을 원한다면,
진행 요소가 "continue" 로 설정되어 그룹으로 그룹 메시지를 전송해야하거나 또는
전송 허가 요소가 "transmission granted" 로 설정되 MS 에허가를 전송해야할 때 그리고
D-TX GRANTED PDU 가 전송 허가 요소 가 "transmission granted to another"설정한 것과 함께 그룹에 그룹메시지를 전달할 때 이다.
[/code]
The CC shall accept any layer 2 channel allocation. If a D-TX CONTINUE PDU with the Continue element set to "continue" is sent, it shall give the earlier granted MS permission to continue transmission. The MS granted permission to transmit shall start timer T311.
[code]
CC 는 어떤 레이어 2채널을 할당을 허락해야한 다면
진행 요소가 "continue"로 설정되어DJ DLtSMS D-TX CONTINUE PDU 은 전송했을 것이다,
그것은 전송을 계속 하기 위해 초기에 MS 에 허가를 줘야했을 것이다.
MS 전송허가를 전송하기 위해서 T311 타이머를 시작해야할 것이다.
[/code]
All CC sub-entities shall return to state CALL ACTIVE and shall send a CONFIGURE request primitive to the lower layers to switch the U-plane on.
[code]
CC 보조 엔티티들은 CALL ACTIVE 상태를 반환하거나 U-plane on 을 스위칭을 위해 CONFIGURE request primitive 를 lower layer들에게 보내야할 것이다.
[/code]
A group-addressed D-TX CONTINUE PDU shall apply to all the MSs in the call (including the awarded MS).
[code]
그룹 주소들은 D-TX CONTINUE PDU 를 콜 내에 모든 MS 들에게 적용해야할 것이다.
[/code]
Optionally, the D-TX CONTINUE PDU may also be sent individually addressed to the awarded MS enabling the SwMI to obtain a layer 2 acknowledgement from that MS.
[code]
선택적으로,
D-TX CONTINUE PDU 는 MS가 layer 2 를 얻었다는걸 확인해주기 위해서 각각의 주소를 MS에 활성화하고 있는 SwMI에게 수여했던 것을 전송했었을 것이다.
[/code]
3) If there was one MS granted transmission at the time when the SwMI sent the D-TX WAIT PDU but the SwMI wishes to give the transmission permission to the other party or if no MS was granted transmission at the time when the SwMI sent the D-TX WAIT PDU and the SwMI wishes to give the transmission permission now to one party, the SwMI may first send a D-TX CONTINUE PDU.
[code]
만약 MS 가 시간내에 전송을 허가했었다면 SwMI 는 D-TX WAIT PDU 를 전송했었던 때이다.
하지만 SwMI 가 다른 파티 로 전송을 허가를 주기를 바라는 때나
시간내에 전송 허가를 받은 MS 가 아니라면 D-TX WAIT PDU 를 전송한 상태이거나 SwMI 가 하나의 파티에 전송 허가를 지금 주기를 원할 때,
SwMI 는 D-TX CONTINUE PDU 를 처음 전송할 지도 모른다.
[/code]
If a MS has requested permission to transmit during the period when the transmission was withdrawn, the SwMI should first send a D-TX CONTINUE PDU as a group message with the Continue element set to "not continue".
[code][/code]
A D-TX GRANTED PDU should then be sent as an individual message to the granted MS with information element transmission grant set to "transmission granted" and as a group message to the rest of the group with information element transmission grant set to "transmission granted to another user".
[code][/code]
When receiving either D-TX CONTINUE or D-TX GRANTED PDU the CC sub-entity shall return to state CALL-ACTIVE.
[code][/code]
In addition when receiving D-TX GRANTED PDU CC shall send a CONFIGURE request primitive to the lower layers to switch the U-plane on.
[code][/code]
If the MS is in state WAIT and it receives a D-TX GRANTED PDU, it shall return to state CALL-ACTIVE and obey the instruction in the D-TX GRANTED PDU.
[code][/code]
e) End of Transmission
[code][/code]
At the end of a transmission the user application shall send a TNCC-TX request primitive to the TNCC-SAP indicating ceased transmission.
[code][/code]
The CC sub-entity shall send this information in a U-TX CEASED PDU and stop timer T311.
[code][/code]
The CC shall send the U-TX CEASED PDU with the stealing permission set to "immediate stealing" and the stealing repeats flag set.
[code][/code]
Upon reception of the U-TX CEASED PDU, the SwMI normally sends a D-TX CEASED PDU to the group informing the group members that the transmission has now ceased.
[code][/code]
Upon reception of a D-TX CEASED PDU the CC shall send this information to the user application in a TNCC-TX indication primitive (transmission ceased) and the CC shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane off, see figure 14.18.
[code][/code]
Also, if the CC that is sending the U-TX CEASED PDU receives a REPORT indication of either successful or unsuccessful transmission of that PDU by the lower layers, then it shall behave as if it had received a D-TX CEASED PDU i.e. it shall send a TNCC-TX indication (transmission ceased) to the user application and shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane off.
[code][/code]
If a D-TX CEASED PDU is received but no REPORT indication of successful transmission of the U-TX CEASED PDU then the CC shall send a CANCEL request primitive to the lower layers to stop retransmissions of the U-TX CEASED PDU.
[code][/code]
NOTE 4: The requirement for the CC to cancel retransmissions may apply if the SwMI sends only a group-addressed D-TX CEASED PDU and the transmitting MS does not receive a layer 2 acknowledgement.
[code][/code]
If there was a request for transmission already queued in the SwMI when the U-TX CEASED PDU was received, the SwMI may send a D-TX GRANTED PDU as an individual message to the granted MS and another D-TX GRANTED PDU as a group message to the rest of the group as described in clause 14.5.2.2.1. b), without sending an explicit D-TX CEASED PDU. However, the SwMI should first send at least a layer 2 acknowledgement to the MS that sent the U-TX CEASED PDU so that the MS can stop its U-plane transmission and start accepting group addressed D-TX GRANTED PDUs.
[code][/code]
The SwMI shall not send an unsolicited, individually addressed D-TX CEASED PDU but it is recognized that a race/error condition may result in the MS receiving one. If CC receives an unsolicited, individually addressed D-TX CEASED PDU it shall send this information further on to the user application in a TNCC-TX indication primitive (transmission ceased) and shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane off.
[code][/code]
f) Stop-transmission order
If a MS wishes to interrupt the transmitting MS with a pre-emptive priority request, it shall send a U-TX DEMAND PDU indicating the level of priority in the "TX demand priority" element. If the SwMI supports transmission interruption, it shall send a D-TX INTERRUPT PDU to the MS which currently has permission to transmit.
[code][/code]
Upon reception of an individually addressed D-TX INTERRUPT PDU the CC sub-entity shall remain in state CALL-ACTIVE, and shall stop timer T311.
[code][/code]
The CC shall send information to the user application in a TNCC TX indication primitive indicating transmission interrupt and the CC sub-entity shall send a CONFIGURE request primitive to the lower layers to switch the U-Plane accordingly (see clause 14.5.2.4).
[code][/code]
The SwMI should send a D-TX INTERRUPT PDU as a group message to the rest of the group indicating that the permission to transmit has been (or will be) allocated to another user, see figure 14.18. Upon reception of the D-TX INTERRUPT PDU the CC sub-entity shall remain in state CALL ACTIVE and shall send a TNCC-TX indication primitive to the user application indicating transmission interrupt. The SwMI should then send a D-TX GRANTED PDU as an individual message to the MS that requested the priority transmission.
[code][/code]
The D-TX INTERRUPT PDU shall indicate that transmission is granted to another user and then the MS shall switch to (or remain in) U-plane reception. Otherwise, if there is a delay before the pre-emptive priority transmission, the SwMI
may indicate "transmission not granted" in the D-TX INTERRUPT PDU. Then the MS shall switch the U-plane off and wait for a D-TX GRANTED PDU.
[code][/code]
g) Expiry of timer T311: call transmission timer.
Upon expiry of timer T311, CC shall remain in state ACTIVE, shall send a TNCC-TX indication primitive to the user application and a U-TX CEASED PDU to the peer entity.
[code][/code]
14.5.2.2.2 Call status information procedures
The D-INFO PDU can be used for carrying call status messages from SwMI to the MS. When a D-INFO PDU is received, depending on the notification, the following actions shall be taken by CC:
[code][/code]
a) call in queue:
- when the SwMI has put a call into a queue, if the D-INFO PDU contains a value for the call time-out, set-up phase, the CC shall start timer T302 using that value.
[code][/code]
The CC shall send the information further on to the application in a TNCC-NOTIFY indication primitive.
[code][/code]
If the call is queued at call set-up time the D-INFO PDU should be preceded by a D-CALL PROCEEDING PDU;
[code][/code]
b) call is proceeding:
- this may be sent to the calling user application during the call set-up phase to indicate that the call set-up time will be longer than for a normal call set-up. The information that the call time-out, set-up phase value shall be changed is made available to the CC sub-entity in the D-INFO PDU. The CC shall start T302 using the new timer value. The CC shall send the information further on to the application in a TNCC-NOTIFY indication primitive;
[code][/code]
c) prolonging the call time-out time:
- the SwMI may decide to change the call time-out time by sending a D-INFO PDU with a new T310 value. Upon reception of the D-INFO PDU containing the "call time-out" element, T310 shall be started using the defined value. If the SwMI supplies a T310 value in the D-INFO PDU, it shall set the value of the "reset call time-out timer" element of the PDU to indicate reset of T310;
[code][/code]
- the SwMI may also choose to reset the call time-out time and start it again using the current defined value. Upon reception of the D-INFO PDU with the "reset call time-out timer" element indicating that T310 shall be reset, T310 shall be started using the value defined earlier;
[code][/code]
- in either case, the Timer value shall be sent further on to the application in a TNCC-NOTIFY indication primitive;
- the SwMI may also change the call timeout time during call restoration by supplying the "call time-out" element in the D-CALL RESTORE PDU, refer to clause 14.5.2.2.4. If the SwMI supplies a T310 value in the D-CALL RESTORE PDU, it shall set the value of the "reset call time-out timer" element of the PDU to indicate reset of T310.
[code][/code]
14.5.2.2.3 Call modification procedures
The MS service user may modify the service of an existing call. To initiate a modification the user application shall issue a TNCC-MODIFY request primitive and the CC sub-entity shall send a U-INFO PDU and wait for a D-INFO PDU from the SwMI before changing any of the current service parameters. The SwMI should not send D-INFO PDU to modify a service while an ongoing U-Plane transmission is in progress.
[code][/code]
When a service has been changed by the SwMI, the SwMI should indicate this to all parties by issuing the D-INFO PDU. Upon reception of a D-INFO PDU indicating an acceptable service modification the CC sub-entity shall send it to the application in a TNCC-MODIFY indication primitive, and the CC sub-entity shall send a CONFIGURE request primitive for lower layer configuration.
[code][/code]
If the SwMI is unable to provide the requested service, it should either send a D-INFO PDU to the requesting party containing the current service (unchanged), or send a D-INFO PDU to all parties containing an alternative service.
[code][/code]
For example, if a user application requests an increase from a 1-slot per frame call to a 4-slots per frame call, and the SwMI is unable to allocate more than 2 slots to the call, it may offer a 2-slots per frame call in the D-INFO PDUs.
[code][/code]
The service may be changed between any combination of one or more of the following:
[code][/code]
• a clear call may be changed to an encrypted call; or
• an encrypted call may be changed to a clear call;
• a 4-slots-per-frame call may be changed to a 1-slot, 2-slot or 3-slot call;
• a 3-slot call may be changed to a 1-slot, 2-slot or 4-slot call;
• a 2-slot call may be changed to a 1-slot, 3-slot or 4-slot call;
• a 1-slot call may be changed to a 2-slot, 3-slot or 4-slot call;
• a circuit mode type (TCH/S, TCH/7.2, TCH/4.8 or TCH/2.4) may be changed to a different circuit mode type
(with the requested interleaving depth in the case of TCH/4.8 or TCH/2.4);
• a protected circuit mode data type (TCH/4.8 or TCH/2.4) may be changed to a different interleaving depth
from the set of permissible values (N = 1, 4 or 8).
[code][/code]
NOTE: The clear and encrypted calls refer to the end-to-end clear and encrypted calls. The end-to-end encryption control is independent of the air interface encryption control. It is also possible to change between the circuit mode speech teleservice and a circuit mode unprotected (speech, encrypted) bearer service.
[code][/code]
The encryption state of each transmission, defined using D-TX GRANTED, can be set independently by the encryption control element in the U-TX DEMAND PDU. The SwMI should not change the requested encryption state in the responding D-TX GRANTED PDU from that requested in the U-TX DEMAND PDU.
[code][/code]
If the MS cannot support a new service combination indicated by D-INFO, D-TX GRANTED or D-TX INTERRUPT, the user application or the CC as appropriate shall disconnect or leave the call, refer to clause 14.5.2.3. The U-DISCONNECT PDU shall contain disconnection cause "requested service not available". In case the rejection results from unsupported encryption flag state the disconnect cause shall be "Called party does not support encryption" or "Called party requires encryption".
[code][/code]
14.5.2.2.4 Call restoration procedures
Call restoration of a group call shall only take place in the CC sub-entity when the CC has entered state CALL-ACTIVE. The CC sub-entity should keep information on whether it is active in a group call or an individual call.
[code][/code]
When the CC receives a BREAK indication primitive, the CC shall switch the U-Plane off as described in clause 14.5.2.4 and shall remain in state CALL-ACTIVE. If the CC had permission to transmit/send data at that time the CC shall assume that the permission is now ended as if the CC had sent a U-TX CEASED PDU.
[code][/code]
If the MS is in state WAIT when it receives a BREAK indication primitive then it shall behave as if it had received a D-TX CONTINUE PDU with the continue element set to "not continue". It shall then obey the instructions in the D-CALL RESTORE
PDU.
[code][/code]
If the CC receives a RESUME indication primitive indicating that the C-Plane may now be used again, it shall issue a U-CALL RESTORE PDU containing the GSSI or GTSI and the call identifier of the call which CC wants to restore.
[code][/code]
If a temporary address is used in the call then it shall be used as the GSSI. If the MS is participating in a call within a
group that does not belong to current network (e.g. the MS has migrated and the group belongs to its home network) the CC shall use the full GTSI of the group in the U-CALL RESTORE PDU.
[code][/code]
If the CC wishes to continue transmission in the new cell, or keep a queued transmission request valid in the new cell, it shall indicate so in the request to transmit/send data information element in the U-CALL RESTORE PDU.
[code][/code]
A MS which has requested for transmit permission on a previous cell and has received a "transmission request queued" esponse or no response at all on that cell, may either refresh the transmission request by requesting for transmit permission in the U-CALL RESTORE PDU on the new cell, or withdraw the transmission request by requesting for receive permission in the U-CALL RESTORE PDU on the new cell. A MS which attempts call restoration having received a "transmission request queued" indication on a previous cell can assume that its transmission request is still held in the SwMI's queue unless the MS receives a "transmission not granted" indication within the call restoration signalling. After sending a U-CALL RESTORE PDU,
[code][/code]
the CC shall start Timer T307 and wait for a D-CALL RESTORE PDU.
[code][/code]
When the CC receives a D-CALL RESTORE PDU, timer T307 shall be stopped and the call shall be resumed with the new parameters, see figure 14.19. The CC shall obey the transmission granting in the transmission grant information element, refer to clause 14.5.2.2.1.
[code][/code]
Timer T310 shall be reset and started only if the "Reset call timeout" information element value is 1 (Reset call time-out timer T310); the T310 value shall be taken from the D-CALL RESTORE PDU call timeout information element and, if not present in the PDU, from the previous value (provided in D-CONNECT, D-CONNECT ACKNOWLEDGE, D-SETUP or D-INFO PDU). If appropriate the CC shall issue a CONFIGURE request primitive to switch the U-Plane on using the procedure in clause 14.5.2.4.
[code][/code]
If a MS restores to a cell without requesting for transmit permission and receives an individually addressed D-CALL RESTORE PDU with "Call status" element having value "Call is queued" (indicating that the cell has no available traffic resources), the value of the "Transmission grant" element in the D-CALL RESTORE PDU shall be "Transmission not granted".
[code][/code]
If the call subsequently proceeds to traffic (it may be cleared while queued), the MS shall expect to receive one of the following PDUs; the MS shall then expect no further signalling for the call restoration:
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission granted to another user". The MS shall switch the U-plane on; the MS is authorized to receive traffic;
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission not granted". The MS shall retain its current U-plane state (and shall perform the channel change).
[code][/code]
If a MS restores to a cell, requests for transmit permission, and receives an individually addressed D-CALL RESTORE PDU with "Call status" element having value "Call is queued" (indicating that the cell has no available traffic resources), the value of the "Transmission grant" element in the D-CALL RESTORE PDU shall be either "Transmission request queued" (MS shall wait for further signalling to indicate the result of its request to transmit) or "Transmission not granted" (MS's request to transmit is rejected). If the call subsequently proceeds to traffic (it may be cleared while queued), the MS shall expect to receive one of the following PDUs:
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission granted to another user". The MS shall switch the U-plane on; the MS is authorized to receive traffic; the MS shall, if its request to transmit was not rejected by the "Call is queued" D-CALL RESTORE PDU, wait for further signalling to indicate the result of its request to transmit;
[code][/code]
• group or individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission not granted". The MS shall retain its current U-plane state (and shall perform the channel change); the MS's request to transmit, if still outstanding following receipt of the "Call is queued" D-CALL RESTORE PDU, is rejected;
[code][/code]
• individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission grant" element having value "Transmission request queued". The MS shall not switch the U-plane on (but shall perform the channel change); the MS shall wait for further signalling to indicate the result of its request to transmit. The SwMI shall not use this value of the "Transmission grant" element if the "Call is queued" D-CALL RESTORE PDU rejected the MS's request to transmit; MS behaviour if it receives such a response in this context is outside the scope of the present document;
[code][/code]
• individually addressed D-TX GRANTED PDU, containing a layer 2 channel allocation, with "Transmission
grant" element having value "Transmission granted". The MS shall switch the U-plane on; the MS is
authorized to transmit. The SwMI shall not use this value of the "Transmission grant" element if the "Call is
queued" D-CALL RESTORE PDU rejected the MS's request to transmit; MS behaviour if it receives such a
response is described in clause 14.5.2.2.1 b) (refer to text describing handling of unsolicited transmission
grant).
[code][/code]
The call length timer T310 shall continue running during the call restoration and on expiry of T310, the procedure defined in clause 14.5.2.3.4 shall apply.
[code][/code]
If the call cannot be restored the CC shall receive a REOPEN indication primitive indicating that the call is lost.
[code][/code]
Upon reception of REOPEN indication primitive or on expiry of timer T307, the CC shall then stop all T3xx timers, clear the call identifier and temporary group address if applicable, and return to state IDLE and it shall send a TNCC-RELEASE indication primitive to the user application with the cause for disconnection, see figure 14.20.
[code][/code]
If the SwMI provides a new call identifier with the D-CALL RESTORE PDU, CC shall use it in all subsequent signalling relating to that call. The MS shall not send any other call related signalling than U-CALL RESTORE PDU, after a cell change, before it has received a D-CALL RESTORE PDU (and possible new call identifier) from the SwMI.
[code][/code]
A MS which is queueing for a traffic channel during restoration and which has an outstanding transmission request, may cancel that transmission request by sending a U-TX CEASED PDU. A MS which is queueing for a traffic channel during restoration and which does not have an outstanding transmission request, may make a transmission request by sending a U-TX DEMAND PDU, providing the SwMI has not disallowed transmission requests (via the "transmission request permission" element).
[code][/code]
If there is more than one circuit mode call active at the time when the MLE-BREAK indication primitive was received, each call shall be restored separately and hence U-CALL RESTORE and D-CALL RESTORE PDUs shall be exchanged one by one for each call.
[code][/code]
14.5.2.2.5 DTMF procedures
When a user application requires to transfer DTMF digits to other user applications during a circuit mode call, it shall issue a TNCC-DTMF request primitive to the CC entity. The DTMF protocol to be used is specified is clause 14.5.1.2.5.
[code][/code]
NOTE 1: The DTMF signalling can be used only after either a D-CONNECT or D-SETUP PDU has been received and the TETRA call is established.
NOTE 2: DTMF signalling may not function correctly during a group call (group addressed basic link LLC acknowledged service is required). The support of DTMF signalling during group calls is outside the scope of the present document.
[code][/code]
14.5.2.2.6 Temporary address handling procedures
The SwMI may allocate a temporary group address for a group call in a D-CONNECT, D-SETUP, D-CALL RESTORE or D-INFO PDU. The temporary address shall be a valid layer 2 address in the MS for reception of group addressed messages for the duration of the call.
[code][/code]
In addition, if the MS calls a group that is not attached in the MS (i.e. the group address is not a valid layer 2 address) when it is registered in the home SwMI of that group, and if the D-CONNECT PDU does not contain the temporary address element, then the MS shall implicitly assume temporary membership of the called group address for the duration of the call. This temporary membership shall apply only after receipt of the D-CONNECT PDU. However, if the D-CONNECT PDU contains the basic service information element with the ommunication type sub-element indicating "point to point" then the MS shall not adopt the called address as a temporary address.
[code][/code]
If the call was set up using a SNA, the calling MS shall not implicitly assume temporary membership of the called group address to which
the SNA corresponds;
[code][/code]
this restriction is imposed because the MS may not know the called group address to which the SNA corresponds, in which case it cannot assume temporary membership of the group.
[code][/code]
NOTE 1: If the SwMI is unsure whether the group address for the call is a valid layer 2 address for the calling MS, the SwMI should allocate the group address as a temporary address to the calling MS; this recommendation is made because if the group address for the call is not a valid layer 2 address, and the SwMI doesn't allocate the group address for the call as a temporary address, the MS will articipate in the call but will ignore all group addressed call maintenance signalling.
[code][/code]
NOTE: 2 In this procedure, if the MS calls a group that it is not a member of (when it is registered in the home SwMI of that group) then it may assume temporary membership of the called group address without having received a temporary address element in the D-CONNECT PDU.
[code][/code]
If the calling user has made an erroneous selection of communication type then this could result in the calling MS adopting another MS's
individual address as a temporary group address. Therefore the SwMI should check that the called address in a requested group call is actually a group address;
[code][/code]
if it is not then the SwMI should either disconnect the call or correct the communication type to "point to point" when sending the D-CONNECT PDU (the SwMI may also choose to correct the communication type to "point to point" in a D-CALL PROCEEDING, D-INFO or D-ALERT PDU).
[code][/code]
The CC sub-entity shall send a CONFIGURE request primitive informing the lower layers of the new temporary address and if required the change of basic service from individual to group call.
[code][/code]
When the call is then released, the CC sub-entity shall send a CONFIGURE request primitive informing the lower layers that the temporary group address is not longer valid (see clause 14.5.2.3).
[code][/code]
14.5.2.2.7 Calls to and from external subscribers
An external subscriber can call TETRA group numbers. The signalling needed between an external subscriber and a gateway is outside the scope of the present document. The signalling between the SwMI and the called group is the same as that for a mobile originated group call.
[code][/code]
'Protocol > TETRA' 카테고리의 다른 글
| 14.5.2.4 U-Plane switching (0) | 2013.09.25 |
|---|---|
| 14.5.2.3 Call disconnection procedures (0) | 2013.09.25 |
| 14.5.1.3 Call disconnection procedures (0) | 2013.09.25 |
| Figure 14.14: Individual call - unsuccessful call restoration (0) | 2013.09.25 |
| Figure 14.13: Individual call - successful call restoration (0) | 2013.09.25 |
