hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.2.2 MSC for short message routing | When a short message has to be routed to a MS, the GMSC addresses the VMSC by an MSC identity received from the HLR which complies with E.164 rules. For MS originating short message, the IWMSC address is derived from the Service Centre address. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.2.3 MSC for location request routing | When a location request for a particular MS needs to be sent to the MS's VMSC, the GMLC addresses the VMSC using an E.164 address received from the MS's HLR. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.2.4 MSC for LMU Control | When a control message has to be routed to an LMU from an SMLC, the SMLC addresses the serving MSC for the LMU using an E.164 address. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3 The Home Location Register (HLR) | There are several cases where the HLR has to be addressed: |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.1 During call set-up | When a call is initiated the HLR of the called mobile subscriber will be interrogated to discover the whereabouts of the MS. The addressing required by the SCCP will be derived from the MSISDN dialled by the calling subscriber. The dialled number will be translated into either an SPC, in the case of communications with... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.2 Before location updating completion | When a MS registers for the first time in a VLR, the VLR has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for address... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.3 After location updating completion | In this case, the subscriber's basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.4 VLR restoration | If a roaming number is requested by the HLR for an IMSI that has no data record in the interrogated VLR, the VLR provides the roaming number in the dialogue terminating message. Subsequently the VLR must retrieve the authentication data from the MS's HLR, if required, and must then trigger the restore data procedure. F... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.5 During Network-Requested PDP Context Activation | When receiving a PDP PDU the GGSN may interrogate the HLR of the MS for information retrieval. When initiating such a dialogue, the only data for addressing the HLR that the GGSN has available is contained in the IMSI, and addressing information must be derived from it. The IMSI is obtained from the IP address or the X... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.6 Before GPRS location updating completion | When a MS registers for the first time in a SGSN, the SGSN has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addre... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.7 After GPRS location updating completion | In this case, the subscriber's Basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.3.8 Query for a Location Request | For a location request from an external client, the GMLC needs to address the home HLR of the target MS to obtain the address of the target MS's serving MSC. The GMLC uses either the international E.164 MSISDN, the international E.214 number (if CCITT or ITU-T SCCP is used) or the international E.212 number (if ANSI SC... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.4 The Visitor Location Register (VLR) | There are several cases when the VLR needs to be addressed: |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.4.1 Inter-VLR information retrieval | When an MS moves from one VLR service area to another, the new VLR may request the IMSI and authentication sets from the previous VLR. The new VLR derives the address of the previous VLR from the Location Area Identification provided by the MS in the location registration request. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.4.2 HLR request | The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR's service area. This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has indicated successful completion of the update location procedure to the VLR. When ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service | The IWMSC is the interface between the mobile network and the network to access to the Short Message Service Centre. This exchange has an E.164 address known in the SGSN or in the MSC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.6 The Equipment Identity Register (EIR) | The EIR address is either unique or could be derived from the IMEI. The type of address is not defined. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.7 The Shared Inter Working Function (SIWF) | When the Visited MSC detects a data or fax call and the IWF in the V-MSC can not handle the required service an SIWF can be invoked. The SIWF is addressed with an E.164 number. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.8 The Serving GPRS Support Node (SGSN) | The HLR will initiate dialogues towards the SGSN if it is aware that one of its subscribers is in the SGSN's serving area. This means that a GPRS location updating has been successfully completed, i.e, the HLR has indicated successful completion of the GPRS location update to the SGSN. The routeing information used by ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.9 The Gateway GPRS Support Node (GGSN) | The GGSN provides interworking with external packet-switched networks, network screens and routing of the Network- Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the HLR will alert the GGSN when the subscriber becomes reachable. The HLR will use the E.164 GGSN number received as ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service | The GMSC provides interworking with the network to access the Short Message Service Centre, the mobile network and routing of Send Routing Info For SM. The GMSC has on E.164 address known in the HLR, SGSN or MSC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.10A Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.10A.1 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.10A.2 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.10B The Gateway Mobile Location Center (GMLC) | The GMLC initiates location requests on behalf of external clients. The E.164 address of the GMLC is provided to an HLR when the GMLC requests a serving MSC address from the HLR for a target MS. The E.164 address of the GMLC is also provided to a serving MSC when the GMLC requests the location of a target MS served by ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.1.3.11 Summary table | The following tables summarize the SCCP address used for invoke operations. As a principle, within a PLMN either an SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 6.2 Use of TC | The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of signalling system No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be consulted for the full specification of TC. The MAP uses all the services provided by TC except the one... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7 General on MAP services | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.1 Terminology and definitions | The term service is used in clauses 7 to 12 as defined in CCITT Recommendation X.200. The service definition conventions of CCITT Recommendation X.210 are also used. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.2 Modelling principles | MAP provides its users with a specified set of services and can be viewed by its users as a "black box" or abstract machine representing the MAP service-provider. The service interface can then be depicted as shown in figure 7.2/1. MAP service-user Service Interface MAP Service-provider MAP service-user Figure 7.2/1: M... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3 Common MAP services | All MAP service-users require access to services for performing basic application layer functions: - for establishing and clearing MAP dialogues between peer MAP service-users; - for accessing functions supported by layers below the applications layer; - for reporting abnormal situations; - for handling of different MA... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3.1 MAP-OPEN service | This service is used for establishing a MAP dialogue between two MAP service-users. The service is a confirmed service with service primitives as shown in table 7.3/1. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 59 (GSM 09.02 version 7.3.0 Release 1998) Table 7.3/1: Service-primitives for the MAP-OPEN service Parameters Requ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3.2 MAP-CLOSE service | This service is used for releasing a previously established MAP dialogue. The service may be invoked by either MAP service-user depending on rules defined within the service-user. The service is an unconfirmed service with parameters as shown in table 7.3/4. Table 7.3/4: Service-primitives for the MAP-CLOSE service Par... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3.3 MAP-DELIMITER service | This service is used to explicitly request the transfer of the MAP protocol data units to the peer entities. See also subclause 7.4 and 7.5 for the detailed use of the MAP-DELIMITER service. The service is an unconfirmed service with service-primitives as shown in table 7.3/5. Table 7.3/5: Service-primitives for the MA... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3.4 MAP-U-ABORT service | This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service with service-primitives as shown in table 7.3/6. Table 7.3/6: Service-primitives for the MAP-U-ABORT service Parameters Request Indication User reason M M(=) Diagnostic information U C(=) Specific info... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3.5 MAP-P-ABORT service | This service enables the MAP service-provider to abort a MAP dialogue. The service is a provider-initiated service with service-primitive as shown in table 7.3/8. Table 7.3/8: Service-primitive for the MAP-P-ABORT service Parameters Indication Provider reason M Source M Provider reason: This parameter indicates the rea... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.3.6 MAP-NOTICE service | This service is used to notify the MAP service-user about protocol problems related to a MAP dialogue not affecting the state of the protocol machines. The service is a provider-initiated service with service-primitive as shown in table 7.3/10. Table 7.3/10: Service-primitive for the MAP-NOTICE service Parameters Indic... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.4 Sequencing of services | The sequencing of services is shown in figure 7.4/1 and is as follows: Opening: The MAP-OPEN service is invoked before any user specific service-primitive is accepted. The sequence may contain none, one or several user specific service-primitives. If no user specific service-primitive is contained between the MAP-OPEN ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.5 General rules for mapping of services onto TC | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.5.1 Mapping of common services | Table 7.5/1 gives an overview of the mapping rules for mapping of common services onto TC-services. Table 7.5/2 gives the mapping rules for mapping of TC-services onto common services. Protocol machine description is given in clauses 14 to 17. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 67 (GSM 09.02 version 7.3.0 Release 19... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.5.2 Mapping of user specific services | Table 7.5/3 gives the general mapping rules which apply to mapping of MAP user specific services onto TC services and table 7.5/4 gives the similar rules for mapping of TC services onto MAP user specific services. Detailed mapping is given in clauses 14 to 17. Table 7.5/3: Mapping of MAP user specific services onto TC ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6 Definition of parameters | Following is an alphabetic list of parameters used in the common MAP-services in subclause 7.3: Application context name 7.3.1 Refuse reason 7.3.1 Destination address 7.3.1 Release method 7.3.2 Destination reference 7.3.1 Responding address 7.3.1 Diagnostic information 7.3.4 Result 7.3.1 Originating address 7.3.1 Sourc... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.1 Common parameters | The following set of parameters are used in several MAP service-primitives: |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.1.1 Invoke Id | This parameter identifies corresponding service primitives. The parameter is supplied by the MAP service-user and must be unique over each service-user/service-provider interface. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.1.2 Linked Id | This parameter us used for linked services and it takes the value of the invoke Id of the service linked to. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.1.3 Provider error | This parameter is used to indicate a protocol related type of error: - duplicated invoke Id; - not supported service; - mistyped parameter; - resource limitation; - initiating release, i.e. the peer has already initiated release of the dialogue and the service has to be released; - unexpected response from the peer; - ... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.1.4 User error | This parameter can take values as follows: NOTE: The values are grouped in order to improve readability; the grouping has no other significance. a) Generic error: - system failure, i.e. a task cannot be performed because of a problem in another entity. The type of entity or network resource may be indicated by use of t... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2 Numbering and identification parameter | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.1 IMSI | This parameter is the International Mobile Subscriber Identity defined in GSM 03.03. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.2 TMSI | This parameter is the Temporary Mobile Subscriber Identity defined in GSM 03.03. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.3 IMEI | This parameter is the International Mobile Equipment Identity defined in GSM 03.03. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.4 Previous location area Id | This parameter refers to the identity of the location area from which the subscriber has roamed. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.5 Stored location area Id | This parameter refers to the location area where the subscriber is assumed to be located. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.6 Current location area Id | This parameter is used to indicate the location area in which the subscriber is currently located. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 75 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.7 Target location area Id | This parameter refers to the location area into which the subscriber intends to roam. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.8 Target cell Id | This parameter refers to the identity of the cell to which a call has to be handed over. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.9 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.10 Originating entity number | This parameter refers to an application layer identification of a system component in terms of its associated ISDN number. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.11 MSC number | This parameter refers to the ISDN number of an MSC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.12 Target MSC number | This parameter refers to the ISDN number of an MSC to which a call has to be handed over. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.13 HLR number | This parameter refers to the ISDN number of an HLR. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.14 VLR number | This parameter refers to the ISDN number of a VLR. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.15 HLR Id | This parameter refers to the identity of an HLR derived from the IMSI defined in CCITT Recommendation E.212. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.16 LMSI | This parameter refers to a local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. LMSI shall not be sent to the SGSN. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.17 MS ISDN | This parameter refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with CCITT Recommendation E.213. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.18 OMC Id | This parameter refers to the identity of an operation and maintenance centre. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.19 Roaming number | This parameter refers to the roaming number as defined in CCITT Recommendation E.213. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 76 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.20 Void | |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.21 Handover number | This parameter refers to the number used for routing a call between MSCs during handover. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.22 Forwarded-to number | This parameter refers to the address to which a call is to be forwarded. This may include a subaddress. For subscribers having an originating CAMEL Phase 2 subscription this address need not be in non-E.164 international format. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.23 Forwarded-to subaddress | This parameter refers to the sub-address attached to the address to which a call is to be forwarded. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.24 Called number | This parameter refers to a called party number as defined in CCITT Recommendation Q.767. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.25 Calling number | This parameter refers to a calling party number as defined in CCITT Recommendation Q.767. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.26 Originally dialled number | This parameter refers to the number dialled by the calling party in order to reach a mobile subscriber. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.27 Service centre address | This parameter represents the address of a Short Message Service Centre. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.28 Zone Code | This parameter is used to define location areas into which the subscriber is allowed or not allowed to roam (regional subscription). With a complete list of Zone Codes the VLR or the SGSN is able to determine for all its location areas whether roaming is allowed or not. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.29 MSIsdn-Alert | This parameter refers to the MSISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service Centre when the MS is again attainable. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.30 Location Information | This parameter indicates the location of the served subscriber as defined in GSM 03.18. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.31 GMSC Address | This parameter refers to the E.164 address of a GMSC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.32 VMSC Address | This parameter refers to the E.164 address of a VMSC. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 77 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.33 Group Id | This parameter is used to describe groups a subscriber can be member of. A subscriber can partake in all group calls (VBS/VGCS) where he subscribed to the respective groups. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.34 North American Equal Access preferred Carrier Id | This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an interexchange carrier. This identity is used at: - outgoing calls: when the subscriber does not specify at call setup a carrier identity; - forwarded calls: when a call is forwarded by the subscriber; - incoming... |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.35 SIWFS Number | This parameter refers to the number used for routing a call between the MSC and the SIWFS (used by ISUP). |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.36 B-subscriber address | This parameter refers to the address used by the SIWFS to route the outgoing call from the SIWFS to either the B- subscriber in case the non-loop method or back to the VMSC in case of the loop method. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.37 Serving cell Id | This parameter indicates the cell currently being used by the served subscriber. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.38 SGSN number | This parameter refers to the ISDN number of a SGSN. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.39 SGSN address | This parameter refers to the IP-address of a SGSN. This parameter is defined in GSM 03.03. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.40 GGSN address | This parameter refers to the IP-address of a GGSN. This parameter is defined in GSM 03.03. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.41 GGSN number | This parameter refers to the ISDN number of a GGSN or the ISDN number of the protocol-converter if a protocol- converting GSN is used between the GGSN and the HLR.. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.42 APN | This parameter refers to the DNS name of a GGSN. This parameter is defined in GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.43 Network Node number | This parameter refers either to the ISDN number of SGSN or to the ISDN number of MSC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.44 PDP-Type | This parameter indicates which type of protocol is used by the MS as defined in GSM 03.60. ETSI ETSI TS 100 974 V7.3.0 (2000-02) 78 (GSM 09.02 version 7.3.0 Release 1998) |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.45 PDP-Address | This parameter indicates the address of the data protocol as defined in GSM 03.60. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.46 Additional number | This parameter can refer either to the SGSN number or to the MSC number. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.47 P-TMSI | This parameter is the Packet Temporary Mobile Subscriber Identity defined in GSM 03.03. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.48 B-subscriber number | This parameter refers to the number of the destination B dialled by the A user. This may include a subaddress. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.49 B-subscriber subaddress | This parameter refers to the sub-address attached to the destination B dialled by the A user. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.50 LMU Number | This parameter refers to a local number assigned to an LMU by an SMLC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.2.51 MLC Number | This parameter refers to the ISDN (E.164) number of an MLC. |
17250281ac36b9d402e66d0077cd67fd | 100 974 | 7.6.3 Subscriber management parameters |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.