ETSI ETS 300 757 ed.1 (1997-04)

Digital Enhanced Cordless Telecommunications (DECT); Data Services Profile (DSP); Low rate messaging service (service type E, class 2)

DE/DECT-020078

Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Profil podatkovnih storitev (DSP) – Nizkohitrostna storitev sporočanja (storitev tipa E, razred 2)

General Information

• Status: Published
• Publication Date: 07-Apr-1997
• Technical Committee: DECT 2 - Data applications
• Current Stage: 12 - Completion
• Due Date: 14-Mar-1997
• Completion Date: 08-Apr-1997
• Ref Project: SIST ETS 300 757 E1:2003 - Digital Enhanced Cordless Telecommunications (DECT); Data Services Profile (DSP); Low rate messaging service (service type E, class 2)

Standards Content (Sample)

SLOVENSKI STANDARD
01-december-2003
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH'(&7±3URILOSRGDWNRYQLK
VWRULWHY'63±1L]NRKLWURVWQDVWRULWHYVSRURþDQMDVWRULWHYWLSD(UD]UHG
Digital Enhanced Cordless Telecommunications (DECT); Data Services Profile (DSP);
Low rate messaging service (service type E, class 2)
Ta slovenski standard je istoveten z: ETS 300 757 Edition 1
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 757
TELECOMMUNICATION April 1997
STANDARD
Source: ETSI TC-RES Reference: DE/DECT-020078
ICS: 33.020
Key words: DECT, profile, data, messaging
Digital Enhanced Cordless Telecommunications (DECT);
Data Services Profile (DSP);
Low rate messaging service;
(Service type E, class 2)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1997. All rights reserved.

Page 2
ETS 300 757: April 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 757: April 1997
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .11
4 Description of services .12
4.1 General .12
4.2 Low Rate Messaging Service Point-To-Point (LRMS PTP).12
4.3 Low Rate Messaging Service Point-To-Multipoint (LRMS PTM) .13
4.4 Service objectives.14
5 Point-to-point service, LRMS PTP.15
5.1 Reference configuration.15
5.2 Functional description.15
5.3 Physical layer requirements.15
5.4 MAC layer requirements .15
5.5 DLC layer requirements.16
5.5.1 C-plane requirements.16
5.5.2 U-plane requirements.16
5.6 Network layer requirements.16
5.7 Management entity requirements .16
5.8 Generic interworking conventions.16
5.8.1 MMSP procedures.16
5.8.2 Multimedia Messaging Service - Service Access Point (MMS-SAP) .17
5.8.3 MMSP primitives .17
5.8.3.1 C-MMS primitives .17
5.8.3.2 M-MMS primitives.18
5.8.3.3 Parameters .18
6 Point-to-multipoint service, LRMS PTM .18
6.1 Reference configuration.18
6.2 Functional description.19
6.2.1 General.19
6.2.2 MMS relations to outside networks (horizontal model).19
6.2.3 Architecture .19
6.2.4 MMS relations to the upper/lower layers (vertical model) .19
6.2.5 Phases of the horizontal interactions .19
6.3 Physical layer requirements.20
6.4 MAC layer requirements. .20
6.5 DLC layer requirements.20
6.5.1 C-plane requirements.20
6.5.2 U-plane requirements.20
6.6 Network layer requirements.20
6.7 Management entity requirements .21
6.8 Generic interworking conventions.21
6.8.1 MMSP procedures.21
6.8.2 MMS-SAP.21
6.8.3 MMSP primitives .21
6.8.3.1 M-MMS primitives.21
6.8.3.2 Parameters .21
Annex A (normative): Support of MMSP by the DECT lower layers.22

Page 4
ETS 300 757: April 1997
A.1 Profile-specific information elements. 22
A.2 MMSP message implementation. 22
A.2.1 General. 22
A.2.2 C-MMS primitives mapping rules . 22
A.2.2.1 LRMS PTP C-MMS primitives . 22
A.2.2.2 LRMS PTM C-MMS primitives. 22
A.2.3 M-MMS message mapping rules . 22
A.2.3.1 General rules for LRMS PTP. 22
A.2.3.2 General rules for LRMS PTM . 22
A.2.3.3 Information element mapping rules . 23
A.3 Network layer segmentation rules for LRMS PTP . 23
A.3.1 Procedure at the sending side. 23
A.3.2 Procedure at the receiving side. 24
Annex B (informative): Interworking conventions to specific networks. 25
B.1 GSM short message services, SMS Mobile Terminated (SMS-MT), SMS Mobile Originated
(SMS-MO) and GSM SMS Cell Broadcast (SMS-CB). 25
Annex C (normative): Service E2: fixed termination MAC Protocol Implementation Conformance
Statement (PICS) proforma . 26
C.1 Standardized symbols for the status column. 26
C.2 Capabilities . 27
C.2.1 Services. 27
C.2.2 Protocol parameters. 27
C.2.3 Messages. 28
C.2.4 Message parameters . 30
C.2.5 Functions implemented. 31
C.2.6 Timer support. 32
C.2.7 Procedure support. 32
Annex D (normative): Service E2: Portable termination MAC PICS proforma . 34
D.1 Standardized symbols for the status column. 34
D.2 Capabilities . 35
D.2.1 Services. 35
D.2.2 Protocol parameters. 35
D.2.3 Messages. 36
D.2.4 Message parameters . 38
D.2.5 Functions implemented. 40
D.2.6 Timer support. 41
D.2.7 Procedure support. 41
Annex E (normative): Service E2: Fixed termination DLC PICS proforma. 43
E.1 Standardized symbols for the status column. 43
E.2 Capabilities . 44
E.2.1 Major capabilities. 44
E.2.1.1 C-plane capabilities . 44
E.2.1.1.1 C-plane services . 44
E.2.1.1.2 C-plane procedures . 44
E.2.1.1.2.1 Point to point acknowledged operation 44
E.2.1.1.2.2 Unacknowledged operation. 46
E.2.1.1.2.3 Broadcast operation . 46
E.2.1.2 Management procedures. 46
E.2.2 Protocol Data Units (PDUs) . 47
E.2.2.1 C-plane PDUs. 47

Page 5
ETS 300 757: April 1997
E.2.2.1.1 C-plane frame structure.47
E.2.2.1.2 C-plane messages.48
E.2.3 Timers.58
E.2.3.1 C-plane timers.58
E.2.4 Protocol error handling.58
E.2.4.1 C-plane protocol error handling.58
Annex F (normative): Service E2: Portable termination DLC PICS proforma.59
F.1 Standardized symbols for the status column .59
F.2 Capabilities.59
F.2.1 Major capabilities .59
F.2.1.1 C-plane capabilities .59
F.2.1.1.1 C-plane services.59
F.2.1.1.2 C-plane procedures .60
F.2.1.1.2.1 Point to point acknowledged operation.60
F.2.1.1.2.2 Unacknowledged operation .61
F.2.1.1.2.3 Broadcast operation.61
F.2.1.2 Management procedures .62
F.2.2 PDUs.63
F.2.2.1 C-plane PDUs .63
F.2.2.1.1 C-plane frame structure.63
F.2.2.1.2 C-plane messages.64
F.2.3 Timers.74
F.2.3.1 C-plane timers.74
F.2.4 Protocol error handling.74
F.2.4.1 C-plane protocol error handling.74
Annex G (informative): Profile selection coding.75
G.1 <> coding.75
G.2 <> coding .75
G.3 <> coding.75
Annex H (informative): Applicability of ETS 300 755 interworking annexes.76
Annex J (informative): Interworking to other message-based teleservices and application-level
services .77
J.1 General.77
J.2 WWW/HTTP .77
History.78

Page 6
ETS 300 757: April 1997
Blank page
Page 7
ETS 300 757: April 1997
Foreword
This European Telecommunication Standard (ETS) has been produced by the Digital Enhanced Cordless
Telecommunications (DECT) Project of the European Telecommunications Standards Institute (ETSI).
Transposition dates
Date of adoption: 21 February 1997
Date of latest announcement of this ETS (doa): 30 June 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 December 1997
Date of withdrawal of any conflicting National Standard (dow): 31 December 1997

Page 8
ETS 300 757: April 1997
Blank page
Page 9
ETS 300 757: April 1997
1 Scope
This European Telecommunication Standard (ETS) defines a profile for Digital Enhanced Cordless
Telecommunications (DECT) systems conforming to ETS 300 175, parts 1 to 8 [1] - [8]. It is part of a
family of profiles aimed at the general connection of terminals supporting non-voice services to a fixed
infra-structure, private and public.
The Low Rate Messaging Service (LRMS), specified in this ETS, provides a means for the slow,
acknowledged or unacknowledged, transfer of multimedia message objects, including alphanumeric
paging messages. It provides both point-to-point and point-to-multipoint messaging and exploits the
Multimedia Messaging Service (MMS) specified ETS 300 755 [13]. This service may be used for private
and public roaming applications.
This ETS specifies the type E service, mobility class 2, as described in ETR 185 [11]. The service
employs solely C-plane functionality and has been designed to coexist with other profiles such as the
Generic Access Profile (GAP), ETS 300 444 [9] or the Global System for Mobile communication (GSM)
Interworking Profile, ETS 300 370 [10]. No User plane (U-plane) functionality is required for the service.
Interworking with the GSM Short Message Service (SMS) is specifically provided for in an annex of this
ETS which cross-references to GSM interworking profile standards (see ETS 300 764 [14]).
This ETS defines the requirements on the Physical (PHL), Medium Access Control (MAC), Data Link
Control (DLC) and Network (NWK) layers of DECT. The standard also specifies management entity
requirements and generic interworking conventions which ensure the efficient use of the DECT spectrum.
2 Normative references
This ETS incorporates, by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to, or revisions of, any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 175-1: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 1:
Overview".
[2] ETS 300 175-2: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 2: Physical
Layer".
[3] ETS 300 175-3: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 3: Medium
Access Control (MAC) layer".
[4] ETS 300 175-4: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data
Link Control (DLC) layer".
[5] ETS 300 175-5: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network
(NWK) layer".
[6] ETS 300 175-6: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 6:
Identities and addressing".
[7] ETS 300 175-7: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 7: Security
features".
Page 10
ETS 300 757: April 1997
[8] ETS 300 175-8: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common Interface (CI); Part 8: Speech
coding and transmission".
[9] ETS 300 444: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Generic Access Profile (GAP)".
[10] ETS 300 370: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications / Global System for Mobile communications
(DECT/GSM) inter-working profile; Access and mapping (Protocol/procedure
description for 3,1 kHz speech service)".
[11] ETR 185: "Radio Equipment and Systems (RES); Digital European Cordless
Telecommunications (DECT); Data Services Profile (DSP); Profile overview".
[12] ETS 300 651: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Data Services Profile (DSP); Generic
data link service; Service type C, class 2".
[13] ETS 300 755: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Data services profile; Multimedia
Messaging Service (MMS) with specific provision for facsimile services; (Service
type F, class 2)".
[14] ETS 300 764: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications / Global System for Mobile communications
(DECT/GSM) Interworking Profile (IWP); Implementation of short message
service, point-to-point and cell broadcast".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
mobility class 1: Local area applications, for which terminals are pre-registered off-air with one or more
specific fixed parts, and establishment of service and user parameters is therefore implicit, according to a
profile-defined list.
mobility class 2: Private and public roaming applications for which terminals may move between fixed
parts within a given domain and for which association of service parameters is explicit at the time of
service request.
multiframe: A repeating sequence of 16 successive Time Division Multiple Access (TDMA) frames, that
allows low rate or sporadic information to be multiplexed (e.g. basic system information or paging).
service type A: Low speed frame relay, with a net sustainable throughput of up to 24 kbits/s, optimized
for bursty data, low power consumption and low complexity applications such as hand-portable
equipment.
service type B: High performance frame relay, with a net sustainable throughput of up to 552 kbits/s,
optimized for high speed and low latency with bursty data. Equipment implementing the type B profile shall
inter-operate with type A equipment.
service type C: Non-transparent connection of data streams requiring Link Access Protocol (LAP)
services, optimized for high reliability and low additional complexity. This builds upon the services offered
by the type A or B profiles.
service type E: A short message transfer or paging service which may be unacknowledged or
acknowledged, optimized for small Service Data Units (SDUs), low Portable Part (PP) complexity and
ultra-low power consumption.
Page 11
ETS 300 757: April 1997
service type F: An application profile specifically supporting teleservices such as fax, building upon the
services offered by the type A/B and C profiles, optimized for terminal simplicity, spectrum efficiency and
network flexibility.
TDMA frame: A time-division multiplex of 10 ms duration, containing 24 successive full slots. A TDMA
frame starts with the first bit period of full slot 0 and ends with the last bit period of full slot 23.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ACK Acknowledgement
CB Cell Broadcast
CC Call Control
C higher layer signalling Channel (Fast)
F
CLMS Connectionless Message Service
C-plane Control Plane
C higher layer signalling Channel (Slow)
S
DECT Digital Enhanced Cordless Telecommunications
DLC Data Link Control
FP Fixed Part
FT Fixed radio Termination
FTAM File Transfer Access & Management
FTP File Transfer Protocol
GAP Generic Access Profile
GSM Global System for Mobile communication
HTTP Hyper Text Transfer Protocol
I higher layer Information channel (Protected)
P
ISDN Integrated Services Digital Network
IWF Interworking Functions
IWU Interworking Unit
LAP Link Access Procedure
LAP-B Link Access Procedure (Balanced)
LAP-C Link Access Procedure (Control)
LCE Link Control Entity
LLN Logical Link Number (DLC layer)
LRMS PTM Low Rate Messaging Service Point-To-Multipoint
LRMS PTP Low Rate Messaging Service Point-To-Point
LRMS Low Rate Messaging Service
M MAC control channel
MAC Medium Access Control
MCE Message Control Entity
MCI MAC Connection Identification
MMSP Multimedia Messaging Service Protocol
MNCC Mobile Network Call Control
MO Mobile Originated
MT Mobile Terminated
NLF New Link Flag
NWK Network
P Paging channel
PDU Protocol Data Unit
PHL Physical
PICS Protocol Implementation Conformance Statement
PP Portable Part
PT Portable radio Termination
PTM Point-To-Multipoint
Q system information channel
RFP Radio Fixed Part
RFPI Radio Fixed Part Identifier
SAP Service Access Point
SAPI Service Access Point Identifier
SDU Service Data Unit
SMS Short Message Service
Page 12
ETS 300 757: April 1997
TDMA Time Division Multiple Access
UI Unnumbered Information (Frame)
U-plane User plane
WWW World Wide Web
4 Description of services
4.1 General
The DECT data profile defined in this ETS has been intended for message transfer or paging and is
optimized for small SDUs, low PP complexity and ultra-low power consumption. Two service types are
defined: Low Rate Messaging Service Point-To-Point (LRMS PTP) which may be unacknowledged or
acknowledged used for point-to-point messaging and Low Rate Messaging Service Point-To-Multipoint
(LRMS PTM) used for point-to-multipoint messaging. The LRMS PTM is an optional feature while LRMS
PTP support is mandatory if this profile is supported.
The LRMS PTP and PTM may co-exist with other profiles and their existence should not have any effect
on the functionality of the other existing profiles. That is, the LRMS functionality should have a secondary
priority in respect to the profile relations.
4.2 Low Rate Messaging Service Point-To-Point (LRMS PTP)
The objectives of the data profile service type E, class 2 LRMS PTP are as follows:
The LRMS PTP is a generic set of commands, information elements and functionality for file/messaging
service. In most of the cases LRMS can be regarded as a DECT internal teleservice that can be
interworked to the similar services in external networks. In addition LRMS PTP provides means to convey
transparently application specific upper layer protocol frames thus facilitating the usage of this profile as a
bearer service. It provides a generic file handling/messaging services over the DECT air interface by
utilizing the transportation mechanism of the DECT C-plane in the best way possible while offering a
general set of functions to the applications using its services. The LRMS procedures can be accessed in a
standardized way through a set of primitives. The LRMS point-to-point service may be acknowledge or
unacknowledged.
LRMS provides a compact subset of functions to messaging servers with the advantage that a single
terminal with LRMS support can use a wide variety of messaging services with minimum amount of
application layer complexity. If a complete set of services is needed an escape sequence has to be used
or some other means such as transparent protocol transportation mechanism should be used.
These objectives are fulfilled by Multimedia Messaging Service Protocol (MMSP).
MMSP that is used for the provision of LRMS services and functionality is a stateless protocol which
defines a set of messages, framing rules and information elements each containing optional and
mandatory information fields.
MMSP utilities the services of the DECT Call Control (CC)entity. It could be regarded as a supplementary
service type of service that provides signalling/control and application specific information related to the
teleservices provided by the DECT data profiles.
The MMSP layer functionality is provided by a set of specific DECT network layer CC information
elements. Therefore the MMSP is not from DECT layer viewpoint a separate real protocol layer but a
service provided to the application. However, from the application perspective the MMSP can be seen as
a protocol layer. Therefore, the MMSP can be regarded as a virtual protocol layer.
The support of MMSP protocol in LRMS PTP is mandatory.

Page 13
ETS 300 757: April 1997
The LRMS PTP is closely aligned with the ETS 300 755 [13] Multimedia Messaging Service (MMS) in the
following way:
- the MMSP protocol used by LRMS PTP is the MMSP protocol used by MMS;
- LRMS PTP utilized only the C-plane services; no U-plane is required;
- the LRMS PTP and MMS may co-exist in a same terminal. It is the matter of the implementation if
the services of LRMS and MMS are joined or separated i.e. if the messaging is done through the
same link or a separate link is instantiated;
- a specific procedure can be used to change the type E profile (this ETS) connection into type F
profile (ETS 300 755 [13]) connection. However, this requires the support of the both profiles as
well as additional DECT network layer functionality.
In general the LRMS PTP may receive or send messages during a on-going other profile based call but
this requires a separate CC instance.
4.3 Low Rate Messaging Service Point-To-Multipoint (LRMS PTM)
The objectives of data profile service type E, class 2 LRMS PTM are as follows:
The purpose of this service is to provide a point-to-multipoint broadcast service of alphanumeric
messages from Fixed Part (FP) to PPs. The messages are not acknowledged. With the addressing
provided a subset of the receiving PP can be preselected or the messages can be aimed at all PPs in the
range of a specific Radio Fixed Part (RFP). Thus the receiving terminals and area can be selected by the
DECT FP service provider.
NOTE: For the addressing of the PPs the connectionless TPUI is used.
The LRMS PTM service provides means for sending a subset of MMSP messages over a point-to-
multipoint link. This facilitates the usage of standard format messages in both point-to-point and point-to-
multipoint cases. With this functionality a network server can control a subgroup of MMSP terminals with
single multicast messages without a need of full bi-directional link instantiation. In this way the LRMS PTM
facilitates a simple and cost effective means of messaging and remote group control of terminal
equipment saving at the same time the air interface resources.
The LRMS PTM may co-exist with other profiles in the PPs and FPs. The co-existence of the LRMS PTM
should not have any affect on the functionality of the co-existing profiles.
The support of LRMS PTM is optional and if supported the MMSP support is mandatory.
In general the LRMS PTM may function during a on-going other profile based call.

Page 14
ETS 300 757: April 1997
4.4 Service objectives
The profile has the service objectives given in table 1 and table 2:
Table 1
Offered services LRMS PTP LRMS PTM
point-to-point SDU transfer PP-FP Yes Not supported
point-to-point SDU transfer FP-PP
point-to-multipoint SDU transfer FP-PP Not Supported Yes
Encryption Optional Not supported
MMSP support Mandatory Mandatory
Profile up/downgrading Optional Not Supported
Support in this ETS Mandatory Optional
Table 2
Performance LRMS PTP LRMS PTM
Maximum throughput for unsegmented 1,38 kbit/s C channel 1,23 kbit/s CL channel
S
s
messages with minimum header (note 1) 17,6 kbit/s C channel, 15,6 kbit/s CL channel
F
f
full slot full slot
-9 -9
Error rate < 10 per bit < 10 per bit
Minimum SDU size (note 2) 48 octets 43 octets
SDU size if segmentation used (note 3)
≤ 5 632 octets ≤ 4 992 octets
NOTE 1: The throughput depends strongly on the used control channel and on the other
services that are in use simultaneously and these figures are the maximum
reachable rates for the user data if no other profiles are in use.
NOTE 2: This length is the maximum length of the application layer SDU (user information)
if only mandatory elements are used at their minimum length and no network layer
segmentation is used.
NOTE 3: The maximum supported size is defined in the interworking annexes on a per
service basis.
Page 15
ETS 300 757: April 1997
5 Point-to-point service, LRMS PTP
5.1 Reference configuration
The reference configuration for this profile shall be as shown in figure 1.
Service interworking
management
Network specific
MMS
m essaging
application
services
IW F
MMSP
MMSP
NW K NW K
Network
Mobility
Network
control/
class 2
DLC DLC
control/
LAP-C LAP-C
transport
transport
protocol
protocol
MAC MAC
PHY PHY
Network
PP FP
IW F:   Interworking Functions.
Figure 1: Profile reference configuration of LRMS PTP showing signalling and message
interworking to connectionless networks via the C-plane
5.2 Functional description
The functional description as outlined in clause 5 of ETS 300 755 [13] shall apply.
5.3 Physical layer requirements
The physical layer requirements of ETS 300 444 [9] shall apply.
5.4 MAC layer requirements
The minimum instance shall only require the capability to establish and maintain single-bearer
connections. The provisions of ETS 300 175-3 [3] shall be implemented with respect to the services,
procedures, messages and information elements coding listed in annexes C to D with the condition of
LRMS PTP. The provisions of ETS 300 175-6 [6] shall be implemented with respect to the structure and
use of identities.
The C may be used if the co-existing profile provides the channel and the LRMS PTP usage does not
F
noticeably disturb the main profile transmissions. If no other profiles exist then the C channel shall be
s
used.
The MAC extended fixed part information message shall be used and, therefore, bit a12 of the fixed part
information field shall be set to 1. In addition, the extended higher layer capabilities bit a43 for the support
of the type E profile shall be set to 1.

Page 16
ETS 300 757: April 1997
5.5 DLC layer requirements
5.5.1 C-plane requirements
All internal DECT protocol control, all external user data and control shall be handled by the C-plane. The
provisions of ETS 300 175-4 [4] shall be implemented with respect to the services, procedures, messages
and information elements coding listed in annexes E and F. The minimum supported DLC layer frame
length shall be 63 octets.
NOTE: The requirement of the DLC layer C plane is as far as possible compatible with GAP
(ETS 300 444 [9]).
5.5.2 U-plane requirements
The U-plane shall not be used by this ETS. However the presence of LRMS PTP service should not
noticeably limit the functionality of the possible other coexisting profiles using the U-plane.
5.6 Network layer requirements
The provision of ETS 300 175-5 [5] shall be implemented with respect to the services, procedures,
messages and information elements listed in annexes F to G of ETS 300 755 [13], with the condition of
LRMS PTP.
NOTE: These network layer requirements are closely related with ETS 300 755 [13] network
layer requirements.
The CC entity in FP and PP shall support either packet mode procedures as specified in subclause 9.7 of
ETS 300 175-5 [5] and indicated by condition C7 in annexes F and G of ETS 300 651 [12] or circuit mode
procedures as specified in ETS 300 444 [9] and indicated by condition C1 in annexes F and G of
ETS 300 651 [12]. The used CC procedure is dependent of the interworking profile and therefore defined
in appropriate interworking annexes.
The <> information element in the {IWU-INFO} message shall be used to carry the
application information in the active state of CC. The messages shall be segmented by using the
<> element in the {IWU-INFO} message if the original {IWU-INFO} message length
exceeds 58 octets. The rules for segmentation are specified in clause A.3.
If LRMS PTP is used during ongoing call a separate CC instance shall be required for LRMS.
Type E/F profile upgrading procedure may optionally be supported. In this case the procedures for the up
and downgrading as specified in clause 9 of ETS 300 755 [13] shall apply.
5.7 Management entity requirements
The management entity requirements of ETS 300 444 [9] shall apply.
5.8 Generic interworking conventions
5.8.1 MMSP procedures
The MMSP elements of procedures and message definitions are defined in clause A.1 of
ETS 300 755 [13].
The MMSP information elements are defined in clause A.2 of ETS 300 755 [13].
The MMSP implementation on lower layers has been defined in annex A of this ETS.

Page 17
ETS 300 757: April 1997
5.8.2 Multimedia Messaging Service - Service Access Point (MMS-SAP)
The MMS-SAP is the service access point on the top of MMSP that shall be accessed by the interworking
unit (IWU) or the application. The M-MMS-SAP primitives are used for LRMS CC and for requesting
LRMS message transportation or reception directly by the upper layer application. The main CC
functionality for different services is done as defined in an appropriate service interworking definition. The
MMS-SAP primitives have been defined in subclause 5.8.3 of this ETS.
Interworking Unit (IWU) or Application
MMS-SAP
MMSP Messaging Part
MMSP Call Control
(M-MMS)
Part (C-MMS)
MNCC-SAP
MMSP Messaging Part Call Control (CC)
DECT NWK C-plane
IWU: Interworking Unit.
Figure 2: The LRMS PTP protocol model
5.8.3 MMSP primitives
5.8.3.1 C-MMS primitives
The following primitives are provided by MMS-SAP for the control of C-MMS part of the MMSP.
Table 3
Primitive Req Cfm Ind Res
C-MMS-SETUP- x x
C-MMS-CONNECT- x x x
C-MMS-RELEASE- x x x x
C-MMS-MODIFY- x x x
NOTE: C-MMS-MODIFY- primitive is used for type F and E profile changes. It can be used
only if the functionality is supported.

Page 18
ETS 300 757: April 1997
5.8.3.2 M-MMS primitives
The following primitives are provided by MMS-SAP for the control of M-MMS part of the MMSP.
Table 4
Primitive Req Cfm Ind Res
M-MMS-SEND- x x
M-MMS-SEND-REQ x x
M-MMS-SEND-RPY x x
M-MMS-RETRIEVE- x x
M-MMS-RETRIEVE-HDR x x
M-MMS-RETRIEVE-RPY x x
M-MMS-STATUS- x x
M-MMS-STATUS-RPY x x
M-MMS-EXT-CMD- x x
M-MMS-EXT-CMD-RPY x x
M-MMS-ESC-CMD- x x
M-MMS-ESC-CMD-RPY x x
5.8.3.3 Parameters
The parameters for each primitive are described in clause A.3 of the of ETS 300 755 [13].
6 Point-to-multipoint service, LRMS PTM
6.1 Reference configuration
The reference configuration for this profile shall be as shown in figure 3.
Service interworking
managem ent
Network specific
MMS
messaging
application
services
IW F
MMSP
MMSP
NW K NW K
Mobility Network
Network
control/
class 2
DLC DLC
control/
LAP-C LAP-C
transport
transport
protocol
protocol
MAC MAC
PHY PHY
Network
PP FP
Figure 3: Profile reference configuration of LRMS PTM showing signalling and message
interworking to connectionless networks via the C-plane

Page 19
ETS 300 757: April 1997
6.2 Functional description
6.2.1 General
The functional description as outlined in clause 5 of ETS 300 755 [13] shall apply with the exceptions
outlined in this subclause.
6.2.2 MMS relations to outside networks (horizontal model)
The model defined in the subclause 5.2 of ETS 300 755 [13] shall apply with the following rules:
- the messaging direction is always from MCE to portable MMS entity. Due to this no IWU conversion
can be requested in FP IWU or MCE IWU with MMSP messages;
- the MCE as well as the fixed MMS entity may do implicit IWU conversions but this conversion
cannot be controlled with MMSP;
- only such MMS procedures are available that are allowed in the direction of fixed MMS entity to
portable MMS entity. The portable MMS entity cannot control the MCE messaging;
- the end entity may send message only to the MMS entities;
- the addressing of a group of portable entities shall be done in the fixed entity by mapping the
incoming address to the Point-To-Multipoint (PTM) as specified in each interworking descriptions.
The PTM MMS messaging horizontal functional model has been illustrated in figure 4.
MMS
point-to-
multipoint
EE
procedures
Portable Fixed I Message
network End
MMS MMS W Control
interface Entity (EE)
entity entity F Entity (MCE)
Message
(IW U)
Message Message
transfer
transfer transfer
DECT Outside network
Figure 4: The MMS horizontal functional model for point-to-multipoint service
6.2.3 Architecture
The internal architecture of the MMSP layer as defined in ETS 300 755 [13], subclause 5.3 shall apply with
the exception that the C-MMS part is not required in the LRMS PTM service. That is, the M-MMS part
interacts directly with the DECT upper layer as illustrated in figure 5. No connection establishment phase
is required on MMSP layer.
6.2.4 MMS relations to the upper/lower layers (vertical model)
The model defined in the subclause 5.4 of ETS 300 755 [13] shall apply.
6.2.5 Phases of the horizontal interactions
Only the phase 3 b) of the horizontal interaction of PP terminated incoming MMS call as defined i
...