Project

General

Profile

Actions

Feature #5504

open

GSM/GPRS coordination (RR/GRR)

Added by laforge almost 2 years ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
OsmocomBB Layer 3 (RR/MM/CC)
Target version:
Start date:
03/29/2022
Due date:
% Done:

0%

Resolution:
Spec Reference:
Tags:

Description

If we go from a pure circuit-switched GSM to a combined GSM + GPRS MS, we need various coordination tasks between the CS and PS plane - mostly on the RR/GRR layer, but possibly also ranging into MM/GMM.

For example, while the MS has active TBFs, it cannot scan for CS neighbor cells, and it might receive CS paging via the PACCH.


Related issues

Related to OsmocomBB - Feature #5501: MS-side GPRS Mobility Management (GMM) + Session Management (SM)Stalledpespin07/01/2022

Actions
Actions #1

Updated by laforge over 1 year ago

  • Tags set to ARDC
Actions #2

Updated by pespin 9 months ago

  • Related to Feature #5501: MS-side GPRS Mobility Management (GMM) + Session Management (SM) added
Actions #3

Updated by pespin 9 months ago

Figure 5.3/3GPP TS 24.007 depicts a "GMM/MM Coord" SAP (though doesn't formally specify it afaict). We probably want to implement that SAP with our own messages as we see need them.

Also TS 24.008 6.6 "Registration Services for GPRS-Services" states:

It shall be noted, that the registration services for mobiles of class A or B may depend on the service states for GPRS
and non-GPRS services. Therefore the internal access points MMCOORD and the GMMCOORD (see figure 5.3) are
used by GMM and MM to inform each other about the relevant conditions. No service primitives between the entities
within the same sublayer, i.e. the MM sublayer, are defined in the present document. The Mobility Management for
class A and B mobiles is further specified in 3GPP TS 24.008 [6].

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)