Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.172  Word version:  18.0.0

Top   Top   Up   Prev   None
1…   4…   4.2.2…   4.2.3   4.2.4   4.2.5…   4.2.5.2   4.3…   4.3.2…   4.3.3…   4.3.3.1.3   4.3.3.1.4   4.3.3.1a…   4.3.4   4.3.5…   4.3.5.2   4.3.6… 
4.3.6 Interaction with supplementary services  4.3.6.1 Call forwarding and Call deflection  4.3.6.2 Closed User Group (CUG)  4.3.6.3 Call barring  4.3.7 Interactions with CAMEL  4.3.7.1 Interaction at call setup  4.3.7.2 Interaction at call answer  4.3.7.3 Interaction with Call Party Handling  4.3.7.4 Interaction with CAMEL in-band information and user interaction  4.3.7.5 Interaction during service change  4.3.8 Interworking with external networks  4.3.9 User interaction and in-band information  5 Lawful Interception  $ Change history 

 

4.3.6  Interaction with supplementary services  p. 55

4.3.6.1  Call forwarding and Call deflection  p. 55

If CFB(UDUB), CFNRy, or Call Deflection is invoked in a SCUDIF call, and both basic services are provisioned, the HLR (for early call forwarding) or VLR (for late call forwarding) shall check the handling of the call should continue with the active service negotiated between the called UE and the network.
If call forwarding except CFB(UDUB) and CFNRy is invoked in a SCUDIF call, and both basic services are provisioned, the HLR (for early call forwarding) or VLR (for late call forwarding) shall check the service for both the preferred service and the less preferred service.
Then, the SCUDIF call interacting with call forwarding shall be handled according to the following rules:
  • If the call forwarding is active only for the less preferred service, the preferred service shall be selected and the call setup shall continue with a single service without invoking call forwarding.
  • If the call forwarding is active only for the preferred service, the preferred service shall be selected and call forwarding shall continue with a single service to the destination indicated by the forwarded to number.
  • If the call forwarding is active for both services and the forwarded to number for the preferred service is same as for the less preferred service, the call shall continue as a SCUDIF call to the destination indicated by the forwarded to number.
  • If the call forwarding is active for both services and the forwarded to number for the preferred service is different from that for the less preferred service, the preferred service shall be selected and call forwarding shall continue with a single service to the destination indicated by the forwarded to number for the preferred service.
  • If the call forwarding is active for both services and CF type for the preferred service is different from that of less preferred service, the call shall continue as a SCUDIF call to the destination indicated by the forwarded to number, and the forwarding reason for the preferred service shall be indicated.
Up

4.3.6.2  Closed User Group (CUG)  p. 56

If a SCUDIF call interacts with CUG and both basic services are provisioned, the service state shall be checked for both the preferred service and the less preferred service. If one service is not allowed, then the call shall fall back to the allowed service.

4.3.6.3  Call barring  p. 56

If a SCUDIF call interacts with call barring and both basic services are provisioned, the service state shall be checked for both the preferred service and the less preferred service. If one service is barred, then the call shall fall back to the allowed service.

4.3.7  Interactions with CAMEL  p. 56

4.3.7.1  Interaction at call setup  p. 56

When a SCUDIF call activates a CAMEL dialogue for the originating or the terminating subscriber, both basic services shall be indicated to the gsmSCF in the InitialDP message (see TS 23.078):
  • the bearer capability IE and the ext-basic service code IE shall indicate the preferred service (i.e. 3G-324.M if the 3G-324.M codec is the first codec in the list of supported codecs ; speech otherwise),
  • the bearer capability 2 IE and the ext-basic service code 2 IE shall indicate the other, less preferred service (i.e. resp. speech or 3G-324.M).
Up

4.3.7.2  Interaction at call answer  p. 56

When the Answer DP is triggered according to the BCSM (see TS 23.078), the event report sent to the gsmSCF shall indicate the result from the OoBTC codec negotiation procedure according to the following:
  • the ext-basic service code IE is included, and represents the selected service (indicated by the selected codec);
  • the ext-basic service code 2 IE is included if the list of available codecs contains codecs both for speech and 3G-324.M, and represents the other service (i.e. speech if the selected service is 3G-324.M, and vice-versa).
Up

4.3.7.3  Interaction with Call Party Handling  p. 56

Interaction with Call Party Handling is allowed, when the call is a speech call and it cannot become a multimedia call.
See clause 21 of TS 22.078.

4.3.7.4  Interaction with CAMEL in-band information and user interaction  p. 57

Interaction with Camel in-band information and user interaction is allowed, when the call is a speech call and it cannot become a multimedia call.
See clause 21 of TS 22.078.

4.3.7.5  Interaction during service change |R6|  p. 57

When a service change is successfully completed (i.e. the codec modification or mid-call codec negotiation reply message indicates a successful codec modification), and the O_Service_Change DP or the T_Service_Change DP is armed, then the relevant detection point is triggered (see TS 23.078).
When a service change is rejected (i.e. the codec modification or mid-call codec negotiation reply message indicates a failure), then the previously selected service is kept, and no event report shall be sent to the gsmSCF for the O_Service_Change DP and the T_Service_Change DP.
Up

4.3.8  Interworking with external networks  p. 57

If the 3G-324.M codec is included in the list of supported codec types received by a Gateway MSC, and the external network does not support BICC or does not support Codec Negotiation, the Gateway MSC shall terminate the codec negotiation and fallback to a single service.
In the case where the 3G-324.M codec is the first in the list, the network decides by configuration to fallback either to a UDI multimedia-only call or to speech. In the case where the 3G-324.M codec is not the first on the list, the call shall fallback to speech only.
If fallback to multimedia occurs, the call control parameters sent towards the external network shall be set according to the setting for multimedia calls, and TMR is set to "64 kbit/s unrestricted". The 3G-324.M codec shall be returned to the originating MSC server as the selected codec and be the only member of the available codec list.
If fallback to speech occurs, the call control parameters shall be set according to the setting for speech calls, and TMR is set to "speech". The 3G-324.M codec shall be removed from the available codec list. Speech codec selection shall be made according to normal OoBTC procedures for interworking to external networks, and the selected codec and available codec list returned to the originating MSC server.
Up

4.3.9  User interaction and in-band information  p. 57

The MSC provided announcements and tones do not work, if the negotiated BC is a multimedia BC. Most often the in-band information is connected to the originating UE but the same rules apply for the terminating UE. The following rules apply:
  1. Before sending the CONNECT message the originating MSC may insert in-band information if CALL PROCEEDING message indicates speech as the selected or preferred service. When fallback to multimedia occurs after CALL PROCEEDING but before CONNECT, the MSC may insert in-band information.
  2. Before sending the CONNECT message the originating MSC shall not insert in-band information, if CALL PROCEEDING message indicates multimedia as the selected or preferred service. When fallback to speech occurs after CALL PROCEEDING but before CONNECT, the MSC shall not insert in-band information.
  3. After the CONNECT message to/from the UE the originating/terminating MSC may insert in-band information, if the selected service is speech. Otherwise, the MSC shall not insert any in-band information. As an option, if the call is to be cleared, the MSC may perform an in-call modification to speech prior to the insertion of the in-band information.
  4. During the call setup phase the terminating MSC, transit MSC and GMSC may insert in-band information, if the selected/preferred service received from the originating switch is speech. Otherwise the terminating MSC, transit MSC and GMSC shall not insert any in-band information during the call setup phase.
  5. In the active phase of the call the terminating MSC, transit MSC and GMSC may insert in-band information, if the selected service is speech. Otherwise the terminating MSC, transit MSC and GMSC shall not insert any in-band information. As an option, if the call is to be cleared, the terminating MSC, transit MSC or GMSC may perform an in-call modification to speech prior to insertion of the in-band information.
Up

5  Lawful Interception  p. 58

SCUDIF calls shall be monitored as for normal Circuit Switched data calls, for detailed requirements see TS 33.106.

$  Change history  p. 59

Up   Top