Project

General

Profile

Feature #3069

investigate multiple CM Service Request on the same conn

Added by neels about 1 month ago. Updated 15 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/16/2018
Due date:
% Done:

0%

Resolution:

Description

TS 24.008 Section 4.5.2:

According to the protocol architecture described in 3GPP TS 24.007
[20], each CM entity will have its own MM connection. These different
MM connections are identified by the protocol discriminator PD and,
additionally, by the transaction identifier TI.

So for example, one could have multiple calls (same pdisc, but different TI),
or one could have SMS ongoing while a call (different pdisc+TI).

Testing an SMS sent during an ongoing call indeed shows a secondary CM Service Request.

In attached pcap it seems that we are already handling the situation rather well.
Nevertheless, take a close look:
  • are we handling the TI properly?
  • make sure that the tear down of one service handling doesn't cut short any other pending CM Service Requests,
    especially if one CM Service Request concludes while the another has just sent the CM Service Request and we are still waiting for the actual CC/RR/... service request following.

(I also notice in attached PCAP that DTMF requests are rejected, and that a call Hold command is rejected; that may have to become separate issues.)

multiple_cm_service_requests.pcapng (1.09 MB) neels, 03/16/2018 12:26 PM


Related issues

Duplicated by OsmoMSC - Feature #3156: make sure we handle N overlapping CM Service Requests properly New 04/11/2018

History

#1 Updated by laforge about 1 month ago

neels wrote:

(I also notice in attached PCAP that DTMF requests are rejected, and that a call Hold command is rejected; that may have to become separate issues.)

both are expected with the internal MNCC handler.

#2 Updated by laforge about 1 month ago

  • Assignee set to sysmocom

#3 Updated by laforge 15 days ago

  • Assignee changed from sysmocom to neels

#4 Updated by neels 8 days ago

  • Duplicated by Feature #3156: make sure we handle N overlapping CM Service Requests properly added

Also available in: Atom PDF