hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.3 Clear Mobile Originated SS Transaction | Clear Mobile Originated SS Transaction
These messages are used to clear a Mobile originated SS transaction.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
258
Facility Confirmation Parameter:
Facility selector
word
256: GSM Support
Function
word
258 |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.4 Receive SS Message | Receive SS Message
These messages are used to handle:
1) The spontaneous reception of an incoming SS transaction (Forward check indication).
2) The message transfer for unstructured SS data.
Facility Indication Parameter:
Facility selector
word
256: GSM Support
Function
word
259
ss_operation
word
ss_code
struct
Byte 0 ... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.5 Call Hold | Call Hold
These messages are used to handle the call related part of the Call Hold Supplementary service. The PLCI of the FACILITY messages describes the identifier of the call, which will be put on "Hold".
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
260
Facility Confirmation Param... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.6 Call Retrieve | Call Retrieve
These messages are used to handle the call related part of the Call Retrieve Supplementary service. The PLCI of the FACILITY messages describes the identifier of the call, which will be retrieved.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
261
Facility Confirmation P... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.7 Call Related Ussd | Call Related Ussd
These messages are used to handle the Call Related Ussd Supplementary service. The PLCI of the FACILITY_REQ/CONF/IND/RESP messages describes the identifier of the call.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
262
ss_ussd_string
struct
Facility Confirmation Par... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.7.4.8 Receive Call Related Facility | Receive Call Related Facility
These messages are used to receive the information of a call related facility. The related call is identified by the PLCI of the FACILITY_IND and FACILITY_RESP message.
Facility Indication Parameter:
Facility selector
word
256: GSM support
Function
word
263
ss_operation
word
ss_code
struct... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8 Extended GSM functionality | This subclause defines additional functions for GSM‑API (Facility selector 256): |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1 Facility Message parameter | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1.1 Get Service State | Get Service State
These messages are used, to get information of the current Service State. An application may use the request of this function to ask for the information.
If the application asked for the GSM service "enable Service State indication", the indication of this function will be sent whenever the Service St... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1.2 RX Level and RX Quality | RX Level and RX Quality
These messages are used, to get information of the current receiving field strength and receiving quality.
An application can only request for this information. An automatic indication is not defined.
Facility Request Parameter:
Facility selector
word
256: GSM Support
Function
word
513
Facility ... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7.8.1.3 Get SIM Present Info | Get SIM Presence Info
These messages are used, to get information if the SIM card is physically present and ready for access. An application may use the request of this function to ask for the information.
If the application asked for the GSM service "enable SIM presence indication", the indication of this function wil... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 UDI mode with ISO3309 HDLC framing. This is the default B1 protocol; | 1 analogue mode; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 2 UDI mode without any additional framing; | 3 reserved, shall be rejected;
4 fax G3 mode; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5 UDI mode with ISO3309 HDLC framing (for compatibility to existing applications); | 6 analogue mode (for compatibility to existing applications).
protocol 0 and 5 shall establish an UDI connection where layer two frames additionally are encapsulated by an HDLC framing structure with byte stuffing according to ISO 3309.
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Transparent; | 2 SDLC [18];
3 LAPD according Q.921 [19] for D channel X.25;
4 T.30 [20] for fax group 3;
5 Point to Point Protocol (PPP [21] [22]);
6 Transparent (ignoring framing errors of B1 protocol).
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Transparent. This is the default B3 protocol; | 1 T.90NL with compatibility to T.70NL according to T.90 Appendix II [23];
2 ISO 8208 [24] (X.25 DTE‑DTE); |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3 X.25 DCE; | 4 T.30 [20] for fax group 3.
This sub parameter appears in parameter:
B protocol |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 4 For calls from the analogue network. (not necessary in GSM‑API) | 17 For calls within ISDN.
Non standard 64 kBit/s data applications
2 No checking of High Layer Compatibility information is provided. The application should verify that no High Layer Compatibility information is received.
Non standard 56 kBit/s data applications
8 No checking of High Layer Compatibility information is ... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 DTMF (Dual Tone Multi Frequency); | 256 GSM specific functions.
GSM specific functions identified by this facility selector are described in clause 7.
This information element appears in:
FACILITY_REQ
FACILITY_CONF
FACILITY_IND
FACILITY_RESP |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Parameter does not apply (coded as empty structure); | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 DTMF (Dual Tone Multi Frequency): | DTMF digits
byte array
Received characters, coded as IA5‑char. "0" to "9", "*", "#", "A", "B", "C" or "D"
This information element appears in:
FACILITY_IND |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Parameter does not apply (coded as structure with a length of 0); | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Parameter does not apply (coded as structure with a length of 0) | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Parameter does not apply (coded as structure with a length of 0) | This information element appears in:
FACILITY_RESP |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 Accept the call; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Ignore the call; | 2 reject call, normal call clearing;
3 reject call, user busy;
4 reject call, requested circuit/channel not available;
5 reject call, facility rejected;
6 reject call, channel unacceptable;
7 reject call, incompatible destination;
8 reject call, destination out of order;
0x8xxx GSM‑API specific reason. Used only, if GS... |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Register GSM support | The facility message parameter for this function are described below. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 Register GSM Support (as described above); | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 2 Send Short Message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 3 Receive Short Message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 4 Receive Cell Broadcast Message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 5 In Call Modification; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 6 Read SIM Data; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 7 Update SIM Data; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 8 Invalidate SIM File; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 9 Rehabilitate SIM File; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 10 Get SIM File Status; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 11 Handle PIN code; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 12 Get available PLMNs; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 13 Set PLMN mode; | 14 ‑ 255 reserved for basic GSM functions.
The facility message parameter for these basic functions are described in the following subclauses. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 256 Restrict SS information; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 257 Mobile originated SS transaction; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 258 Clear Mobile originated SS transaction; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 259 Receive SS message; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 260 Call Hold; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 261 Call Retrieve; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 262 Call Ussd; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 263 Receive Call related Facility; | 264 ‑ 511 reserved for GSM Supplementary Services functions; |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 512 Get Service State; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 513 Get RX Level and RX Quality; | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 514 Get SIM Presence Info; | 515 ‑ ... reserved. |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 0 SIM is not present | |
62d647ebf6fb27c62e31dabd4f0b53c9 | 07.08 | 1 SIM is present and accessible | Facility Response Parameter:
Facility selector
word
256: GSM Support
Function
word
54
Annex A (informative): GSM Supplementary Services Message flow
A.1 Restrict SS information
This Message Flow chart describes the flow for restriction of SS information.
Application MS Network
| facility_req(funct = 256) | ... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 1 Scope | The present document specifies the third version of the Integrated Services Digital Network (ISDN) - Global System for Mobile communications (GSM) Public Land Mobile Network (PLMN) signalling interface. The present document is applicable to the interconnection of PLMN and ISDN.
The ISUP interface defined is the trunk s... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• Fo... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
3PTY Three-Party
ACM Address Complete Message
AoC Advice of Charge
CB Call Barring
CCBS Completion of Calls to Busy Subscriber
CCNR Completion of Calls on No Reply
CD Call Deflection
CFB Call Forwarding Busy
CFNR Call Forwarding No Reply
CFNRc... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 4 General principles | The gateway exchanges in both networks behave like international incoming or outgoing gateways in the relevant cases as described in EN 300 356-1 [1] to EN 300 356-20 [19], with the exceptions indicated within the present document. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5 Exceptions and clarifications for basic call | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.1 Formats and codes | The formats and codes specified in EN 300 356‑1 [1] with the exceptions and clarifications described in the table in annex D shall be applicable. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2 Basic call signalling procedures | The basic call procedures of EN 300 356-1 [1] apply with the following exceptions and clarifications. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.1 Signalling procedures for connection type allowing fallback | The gateway in the preceding network (PLMN or ISDN) shall perform fallback according to the procedures defined in EN 300 356-1 [1] when the succeeding network does not support fallback. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.2 Echo control procedure | The enhanced echo control procedure according to EN 300 356-1 [1] is not supported. Instead the simple echo control procedure described in EN 300 356-1 [1] is applicable.
According to GSM 03.50 [21], for speech and 3,1 kHz audio connection types an acoustic echo control shall be provided in the MS. The PLMN may provide... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3 Calls from the PLMN to the fixed network | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3.1 Gateway in the PLMN | The Initial Address Message (IAM) sent by the gateway in the PLMN shall be coded taking into account the following exceptions and clarifications. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.3.1.1 Initial address message | Called party number
The called party number parameter may contain a Mobile Station Roaming Number (MSRN).
- Internal network number indicator:
0 if the MSRN is included;
1 otherwise.
The use of the internal network number indicator is an option.
User service information
The IAM shall always include a user service infor... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4 Calls from the fixed network to the PLMN | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.1 Gateway in the fixed network | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.1.1 Initial address message | Called party number
The called party number parameter contains the MSISDN or MSRN:
- Internal network number indicator:
0 if MSRN is included;
1 if MSISDN is included.
NOTE: The value of the internal network number indicator is set in the exchange having the relevant knowledge, and is passed transparently through the f... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.2 Gateway in the PLMN | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 5.2.4.2.1 Address complete message | Significant delays may be incurred while interrogating location registers and while paging the terminating MS.
Due to the possible delays involved in setting up mobile calls, the PLMN needs to take special action to ensure that timer T7 (awaiting address complete timer) does not expire.
For this reason, whenever a call... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6 Exceptions and clarifications for supplementary services | Supplementary services are used according to EN 300 356‑1 [1] to EN 300 356‑20 [19]. When considering supplementary services, there exists a symmetry about this interface although the ISDN services may not be the same as the PLMN services. For each service supported by EN 300 356‑2 [2] to EN 300 356‑20 [19] or GSM 03.8... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1 Considerations on ISDN supplementary services | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1 Handling of number parameters related to supplementary services | The following text applies when referenced for the appropriate parameters.
Number parameters related to supplementary services sent across the ISDN-PLMN interface shall have the following coding of the nature of address indicator.
National significant number (000 0011) shall be used in the following cases:
- for a numb... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.1 Calling Line Identification Presentation/Restriction (CLIP/CLIR) supplementary services | EN 300 356‑3 [3] and EN 300 356‑4 [4] apply with the exceptions below:
Calling party number and generic number
Handling of calling party number and the appropriate generic number shall be made according to subclause 6.1.1.
For mobile originated calls the calling line identity is mapped into the calling party number par... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.2 Connected Line Identification Presentation/Restriction (COLP/COLR) supplementary services | EN 300 356‑5 [5] and EN 300 356‑6 [6] apply with the exceptions below:
Connected number and generic number
Handling of connected number and the appropriate generic number shall be made according to subclause 6.1.1. For mobile terminated calls the connected line identity is to be mapped into the connected number paramet... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.3 Terminal Portability (TP) supplementary service | EN 300 356‑7 [7] applies.
NOTE: Terminal Portability is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.4 User-to-User Signalling (UUS) supplementary service | EN 300 356‑8 [8] applies.
NOTE: The maximum length of the user-user parameter of the setup message at the GSM access is restricted to 35 octets. When a GSM PLMN receives a longer user-to-user information element in the IAM message the User-to-user information element will be discarded without indication. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.5 Closed User Group (CUG) supplementary service | EN 300 356‑9 [9] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.6 Subaddressing (SUB) supplementary service | EN 300 356‑10 [10] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.7 Malicious Call Identification (MCID) supplementary service | EN 300 356‑11 [11] applies with the exceptions below:
Calling party number and generic number
Handling of calling party number and the appropriate generic number shall be made according to subclause 6.1.1.
NOTE: Malicious Call Identification is supported by the protocol, however the service is not provided for the GSM ... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.8 Conference call, add-on (CONF) supplementary service | EN 300 356‑12 [12] applies with the exception below:
Notification messages may be sent from the ISDN to the PLMN according to GSM 03.84 [23].
NOTE: Conference call is supported by the protocol, however the service is not provided for the GSM access. The corresponding service in GSM is the multiparty service defined by ... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.9 Explicit Call Transfer (ECT) supplementary service | EN 300 356‑14 [13] applies with the exceptions below:
Call Transfer Number
Handling of call transfer number shall be made according to subclause 6.1.1. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.10 Diversion supplementary services (Call Forwarding Unconditional (CFU)/Call Forwarding on Busy (CFB)/Call Forwarding on No Reply (CFNR)/Call Deflection (CD)) | EN 300 356‑15 [14] applies with the exceptions below:
Original called number, redirecting number and redirection number
Handling of original called number, redirecting number and redirection number shall be made according to subclause 6.1.1. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.11 Call Hold (HOLD) supplementary service | EN 300 356‑16 [15] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.12 Call Waiting (CW) supplementary service | EN 300 356‑17 [16] applies. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.13 Completion of Calls to Busy Subscriber (CCBS) supplementary service | EN 300 356‑18 [17] applies with the exception below:
If the GMSC has the knowledge that the CCBS service is not supported the diagnostics in the Release message will be set to indicate "CCBS not possible" (for cause values 17 or 34). |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.14 Completion of Calls on No Reply (CCNR) supplementary service | EN 300 356‑20 [19] applies with the exception below:
NOTE: Completion of Calls on No Reply is supported by the protocol, however the service is not provided for the GSM access. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.1.1.15 Three party (3PTY) supplementary service | EN 300 356‑19 [18] applies with the exceptions below:
Notification messages may be sent from the ISDN to the PLMN according to GSM 03.84 [23].
NOTE: Three party is supported by the protocol, however the service is not provided for the GSM access. The 3PTY service can be a part of the multiparty service as defined by th... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2 Considerations on GSM unique supplementary services | |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.1 Call Forwarding on Mobile Subscriber Not Reachable (CFNRc) supplementary service | EN 300 356‑15 [14] applies with the exceptions below:
Original Called Number, Redirecting Number and Redirection Number
Handling of original called number, redirecting number and redirection number shall be made according to subclause 6.1.1. For calls that have been redirected (because of mobile subscriber not reachabl... |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.2 Advice of Charge (AoC) supplementary service | No impact on the ISDN-PLMN- interface. The service is described in GSM 03.86 [24]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.3 Call Barring (CB) supplementary service | No impact on the ISDN-PLMN interface. The service is described in GSM 03.88 [25]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.4 Unstructured Supplementary Service Data (USSD) | No impact on the ISDN-PLMN interface. The service is described in GSM 03.90 [26]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.5 Calling Name Presentation supplementary service (CNAP) | No impact on the ISDN-PLMN interface. The service is described in GSM 03.96 [33]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.6 Multiple Subscriber Profile (MSP) supplementary service | No impact on the ISDN-PLMN interface. The service is described in GSM 02.97 [34]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 6.2.7 Multi Party (MPTY) supplementary service | The service is described in ETS 300 545 [26].
Notification messages of the MPTY supplementary service may be mapped on the ISDN-PLMN interface into notification messages of the ISDN Conference call (CONF) supplementary service defined in EN 300 356-12 [12]. |
050dd1f8ccaa6938e4dea97b2c4f9a36 | 09.14 | 7 Message Transfer Part (MTP) protocol requirements | The Message Transfer Part (MTP) protocol shall conform to the requirements in ETS 300 008 [31] with the appropriate value for the Network Indicator (NI).
It is preferred that NI value 10 (national network) is used within GSM networks as in the fixed national network. Based on national agreement, any NI value may be app... |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1 Scope | The purpose of this document is to describe the project plan for the Mobile Station Execution Environment (MEXE) work item standardisation.
This document is a ‘living document’ and permanently updated by PT SMG. Proposals for change shall be forwarded to PT SMG, where the latest version can be obtained any time. The ME... |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1.1 References | |
fa1f7147965681eaaaf31c7cb7fe148b | 10.57 | 1.2 Abbreviations | MNCRS WG4 Mobile Network Computer Reference Standard Working Group 4 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.