Function Description of Softswitch
Function Description of Softswitch
Softswitch
Issue Date
1.00 2007-02-06
CONFIDENTIAL
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Page 2 of 146
CONFIDENTIAL
Summary
This document provides the function description of Softswitch.
Page 3 of 146
CONFIDENTIAL
History
Issue 1.00 Details Creation Date 2007-02-06 Author Liao zhi jun Approved by Yang Jun
Page 4 of 146
CONFIDENTIAL
Contents
1 Function Description of MSOFTX3000.....................................................................................6
1.1 Teleservices ...................................................................................................................................................... 6 1.2 Supplementary services.................................................................................................................................. 11 1.3 Operator Determined Barring (ODB) services............................................................................................... 21 1.4 Value-Added services..................................................................................................................................... 22 1.5 Mobility management .................................................................................................................................... 33 1.6 Security management ..................................................................................................................................... 36 1.7 Subscriber data management.......................................................................................................................... 39 1.8 Handover functions ........................................................................................................................................ 40 1.9 Tone and announcement functions ................................................................................................................. 46 1.10 The MGW completes the load of an announcement file. Charging functions.............................................. 51 1.11 Protocol interface functions.......................................................................................................................... 63 1.12 Operation and maintenance functions .......................................................................................................... 74 1.13 Routing functions ......................................................................................................................................... 83 1.14 Interconnection functions ............................................................................................................................. 93 1.15 SSP functions ............................................................................................................................................. 105 1.16 Enhanced system functions ........................................................................................................................ 112 1.17 Lawful interception functions .................................................................................................................... 139 1.18 Bill gateway (iGWB) functions.................................................................................................................. 140 1.19 System reliability functions........................................................................................................................ 145
Page 5 of 146
CONFIDENTIAL
1
1.1 Teleservices
This document aims to help readers better understand Softswitch functions and features. The document will provide a general overview of major functions and features of softswitch system.
WMFD-010000 Function name: Teleservices Description: The teleservices include basic teleservices and supplementary services. And the basic teleservices include speech service, bearer service and short message service. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-010100 Function name: Speech service Description: The speech service is the basic function of telecom network, including telephony (TS 11), emergency call (TS 12) and emergency call for special service (such as 119 and 110). Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
Page 6 of 146
CONFIDENTIAL
The operators provide the telephony service for the subscribers among PSTN, ISDN, and PLMN through the function. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-010102 Function name: Emergency call (TS12) Description: When the mobile subscribers press an emergency key or dial 112, the call is connected to the answer phone notice equipment which will tell the subscribers how to call the emergency center. The subscribers can make the emergency calls even without SIM or USIM. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-010103 Function name: Emergency call for special service Description: When dialing 119 (fire alarm center), 110 (mobster alarm center), 120 (first-aid center) and 122 (traffic accident center), the mobile subscribers access the nearest special service centers based on the BTS where the subscribers are located. The above calls can generate the alarms, and whether to charge for subscribers can be set as required. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-010200 Function name: Short Message Service (SMS) Description: The SMS includes Point-to-point (PTP) SMS, and point-to-multipoint SMS. Wherein, the latter refers to SM cell broadcast service, and the former includes the following: WMFD-010201 WMFD-010202 Short message MO/PP (SMS-MO) Short message MT/PP (SMS-MT)
SM: The length of cell content transferred each time is rather short in the SMS. According to the definition of relevant technical specifications (ETSI GSM 03.40 and ETSI GSM 03.41) in current ETSI GSM, each PTP SM includes a maximum of 140 bytes. That is, 160 ASCII characters or 70 Chinese words. But each broadcast SM includes a maximum of 82 bytes/page, that is, 92 ASCII characters or 41 words, and a maximum of 15 pages macro broadcast messages can be sent continuously. The point-to-multipoint SMS allows the subscribers to send/receive the SM at any time. But the broadcast SMS allows the subscribers to receive the public messages regularly and selectively.
Page 7 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Increase the traffic and enhance ARPU value. For subscribers Receive/send the SM. Requirements for peripheral network entities The network should provide SMC equipment.
WMFD-010201 Function name: Short message MO/PP(TS22) Description: This service provides the transmission of a short message from a user equipment to a message handling system (service center). After reception an acknowledgement message can be sent back. There is an interworking between the PLMN and SMS Service Center (SMS-SC). Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Increase the traffic and enhance ARPU value. For subscribers Send the SM. Requirements for peripheral network entities The network should have SMC-SC.
WMFD-010202 Function name: Short message MT/PP(TS21) Description: This service provides the transmission of a short message from a message handling system (service center) to a user equipment. After reception an acknowledgement message is sent back. There is an interworking between the PLMN and SMS Service Center (SMS-SC). Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit:
Page 8 of 146
CONFIDENTIAL
For operators Increase the traffic and enhance ARPU value. For subscribers Receive the SM. Requirements for peripheral network entities The network should have SMC-SC.
WMFD-010300 Function name: GSM facsimile services Description: Refer to defined facsimile services that MSOFTX3000 supports GSM protocol specifications, including automatic facsimile services and alternate speech and facsimile service.
WMFD-010301 Function name: Alternate speech and facsimile group 3 (TS61) Description: Huawei MSOFTX3000 supports the alternate of G3 transparent digital facsimile and speech. The rate can be 2.4kbps, 4.8kbps or 9.6kbps during the facsimile service. Implemented node: VMSC/VLR Serve Network: GSM Service benefit: For operators Provide GSM TS61 service. For subscribers Enjoy GSM TS61 service. Requirements for peripheral network entities Configure IWF equipment.
WMFD-010302 Function name: Automatic facsimile group 3 (TS62) Description: Most facsimiles adopt this mode. For GSM, currently Huawei MSOFTX3000 only supports G3 transparent digital facsimile. The automatic facsimile group 3 can be compatible with several analog facsimile service (currently, the GSM analog facsimile is unavailable, and current G3 facsimile is digital one).In addition, it only supports picture facsimile instead of text facsimile, and does not support ECM correction mode.
Page 9 of 146
CONFIDENTIAL
The rate can be 2.4kbps, 4.8kbps or 9.6kbps. Implemented node: VMSC/VLR Serve Network: GSM Service benefit: For operators Provide GSM TS62 service. For subscribers Enjoy GSM TS62 service. Requirements for peripheral network entities Configure IWF equipment.
WMFD-010500 Function name: GSM bearer services Description: Huawei MSOFTX3000 supports the following BS20 bearer services: WMFD-010501 Transparent asynchronous bearer services-3.1kHz audio, Fixed Network User Rate can be 2.4/4.8/9.6kbps under the GSM. WMFD-010502 Transparent asynchronous bearer services-UDI, and under the GSM, Fixed Network User Rate is 2.4/4.8/9.6kbps, and the rate adaptation is V.110. WMFD-010503 Non-transparent asynchronous bearer services-3.1kHz audio, and under the GSM, Fixed Network User Rate is 2.4/4.8/9.6kbps. WMFD-010504 Non-transparent asynchronous bearer services-UDI, and under the GSM, Fixed Network User Rate is 2.4/4.8/9.6kbps, and the rate adaptation is V.110. Implemented node: VMSC/VLR Serve Network: GSM Service benefit: For operators Provide GSM CS data service. For subscribers Enjoy GSM CS data service. Requirements for peripheral network entities Need IWF equipment.
Page 10 of 146
CONFIDENTIAL
Huawei MSOFTX3000 supports the following BS20 and BS30 bearer services: WMFD-010602 Non-transparent asynchronous bearer services-3.1kHz audio, and under the UMTS, Fixed Network User Rate is 9.6/14.4/19.2/28.8kbps. WMFD-010603 Non-transparent asynchronous bearer services-UDI, and under the UMTS, the rate is 9.6/14.4/19.2/28.8kbps, and the rate adaptation is V.110/V.120. WMFD-010605 Rate is 64kbps. Transparent synchronous bearer services-UDI, Fixed Network User
WMFD-010606 Transparent synchronous bearer services-multimedia, Fixed Network User Rate is 64kbps, the rate adaptation is H223 and H245. Implemented node: VMSC/VLR Serve Network: UMTS Service benefit: For operators Provide UMTS CS data service and video phone. For subscribers Enjoy GSM CS data service and video phone. Requirements for peripheral network entities Asynchronous bearer service needs IWF equipment.
Page 11 of 146
CONFIDENTIAL
The system forwards the calls to the Third Party based on the requirements of operator and subscriber. The CF SS include Call Forwarding Unconditional (CFU), Call Forwarding on Mobile Subscriber Busy (CFB), Call Forwarding on No Reply (CFNRy) and Call Forwarding on Mobile Subscriber Not Reachable (CFNRc). Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020101 Function name: Call Forwarding Unconditional (CFU) Description: When the mobile subscriber is a called party, all the calls are forwarded to the Third Party. The Third Party here either can be any subscriber in the PLMN, PSTN and ISDN or the service console (such as Voice Mailbox). Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020102 Function name: Call Forwarding on Mobile Subscriber Busy (CFB) Description: When the called mobile subscriber is busy, the call is forwarded to the Third Party. In addition, the CFB can be classified into Network Determined User Busy (NDUB) and User Determined User Busy (UDUB) based on the forwarding cause. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-020103 Function name: Call Forwarding on No Reply (CFNRy) Description: The mobile subscribers do not connect the call after receiving network ALERTING message for a long time, and the No reply duration timer expires, so the calls are forwarded to the Third Party. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-020104 Function name: Call Forwarding on Mobile Subscriber Not Reachable (CFNRc) Description:
Page 12 of 146
CONFIDENTIAL
If the network is disconnected with radio channel of mobile subscriber, and the mobile subscriber is the called party, all the calls are forwarded to the Third Party. The Not Reachable conditions include paging no reply, radio channel allocation failure, and subscriber power-off. The CFNRc is classified into the home CF and destination CF based on the forwarding places. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020200 Function name: Call Restriction SS Description: The Call Restriction SS include Barring of All Incoming Calls (BAIC), Barring of Incoming Calls when Roaming Outside the Home PLMN Country (BIC-Roam), Barring of All Outgoing Calls (BAOC), Barring of Outgoing International Calls (BOIC), and Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC). The Call Restriction SS defined standardized include barring of incoming calls and barring of outgoing calls. Wherein, the former includes BAIC and BIC-Roam, and the latter includes BAOC, BOIC, and BOIC-exHC. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020201 Function name: Barring of All Outgoing Calls (BAOC) Description: When the service is activated, the subscribers are unable to originate the calls except the emergency calls. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020202 Function name: Barring of Outgoing International Calls (BOIC) Description: When the service is activated, If the mobile subscribers are roamed in the home PLMN, they are not allowed to originate a call to the overseas subscriber. If the mobile subscribers are roamed outside the home PLMN, they can originate a call to local subscribers only.
Page 13 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020203 Function name: Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC) Description: When the service is activated, the subscribers are unable to originate the international toll calls except a call in home country. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020204 Function name: Barring of All Incoming Calls (BAIC) Description: When the service is activated, the subscribers are unable to connect all the incoming calls. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020205 Function name: Barring of Incoming Calls when Roaming Outside the Home PLMN Country (BIC-Roam) Description: When the service is activated and the mobile subscribers are roaming outside the home PLMN country, they are unable to receive the incoming calls from other subscribers. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020300 Function name: Number Identification SS Description: The system provides calling number for called identification presentation or restriction, and connected number for calling identification presentation or restriction. Number identification SS include Calling Line Identification Presentation (CLIP), Calling Line Identification Restriction (CLIR), Connected Line Identification Presentation (COLP) and Connected Line Identification Restriction (COLR). Implemented node: VMSC/VLR and GMSC
Page 14 of 146
CONFIDENTIAL
Serve Network: GSM and UMTS WMFD-020301 Function name: Calling Line Identification Presentation (CLIP) Description: CLIP is a supplementary service provided for called mobile subscriber. When the mobile subscriber connects a call, the system provides calling number for the subscriber, and the subscriber can know the calling party before connecting the call, and determine whether to connect, reject or forward the call. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020302 Function name: Calling Line Identification Restriction (CLIR) Description: CLIR is a supplementary service provided for calling mobile subscriber. When the mobile subscriber is a calling party, the system is not allowed to provide calling number for the called subscriber. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020303 Function name: Connected Line Identification Presentation (COLP) Description: When the mobile subscriber is a calling party, the system provides called number for the calling subscriber. When the called subscriber activates CF SS, and the subscriber communicating with mobile calling subscriber is the forwarded subscriber instead of the subscriber that the calling party calls, the system provides the forwarded number for the mobile calling subscriber. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-020304 Function name: Connected Line Identification Restriction (COLR) Description: When the mobile subscriber is a called party, the system is not allowed to provide called mobile number for the calling party. When this mobile subscriber is the forwarded one, the system is not allowed to provide forwarded number for the calling party. Implemented node: VMSC/VLR and GMSC
Page 15 of 146
CONFIDENTIAL
WMFD-020400 Function name: Call Completion SS (CW/HOLD) Description: Call Waiting (CW): When the mobile subscribers are in the conversation, they are allowed to connect another call. At that time, the system prompts that another call is waiting, and the called subscriber can determine whether to connect this call. Call Hold (HOLD): The subscriber terminates current call temporarily and connects a new incoming call. After the new call is connected, the subscriber can shift the conversation between the old and new one, and another call is in HOLD state. Generally, the CW and HOLD are effective when they are used together. If the subscriber wants to connect a new all, Call HOLD function is required, and the subscriber cannot connect the new call before current call is in HOLD state. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Enhance the service function and attract more subscribers. Increase successful connection ratio and traffic. For subscribers Connect a call when the subscribe is busy Enhance the subscriber satisfaction, especially for high-priority and commercial subscribers. Requirements for peripheral network entities None
WMFD-020500 Function name: Multiparty SS (MPTY) Description: The mobile subscriber registering the supplementary service can organize multiparty telephone conference, providing the conversation among multiparty (this mobile subscriber included). With a maximum of 6 subscribers have a conversation at the same time through the MPTY. During the MPTY, the main control subscriber can add/disconnect/isolate remote subscriber (note: here isolate means the chairman of the MPTY will hold one subscriber to isolate him from the meeting temporally). Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit:
Page 16 of 146
CONFIDENTIAL
For operators Enhance the service function and attract more subscribers. Provide a simple telephone conference solution for the commercial subscriber. For subscribers Provide multiparty chat service. Under some conditions, provide a simple telephone conference function for commercial subscribers. Requirements for peripheral network entities None
WMFD-020600 Function name: Unstructured Supplementary Service Data (USSD) Description: USSD: The subscriber enters operation command of the un-standardized supplementary service consistent with USSD format and originates a special service request to the network, or the network side sends a USSD command to the network to implement a special service. Compared with SMS, USSD service can exchange messages in real time for the convenience of stock query. MSOFTX3000 support USSD of protocol version 1 and version 2. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Provide special value-added service (VAS), such as stock/lottery/weather forecast/scheduled flight information. Enhance service function. Attract more subscribers. For subscribers Satisfy the requirements for information query, such as lottery and stock information. Requirements for peripheral network entities The network should provide USSD centre equipment.
Page 17 of 146
CONFIDENTIAL
One or several users with the same attributes form into a group, so the members have the same call attribute. CUG service is applicable for a small group with several members or a large enterprise with thousands of subscribers. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Enhance service capability. Attract more group subscribers. For subscribers The group members enjoy flexible charging preferential. Requirements for peripheral network entities None
WMFD-020800 Function name: Explicit Call Transfer (ECT) Description: ECT is a supplementary service and the description is available in the 3GPP TS 23.091. With the ECT function, subscriber A can respectively call subscribers B and C and both calls are in answer status. Or, when a call is in answer status and another is in ringing status, subscriber A (the calling party) can first connect subscriber B with subscriber C to allow them to talk with each other and then exit the call. Note, IN subscribers is not support ECT. Implemented node: MSC/VLR Served network: GSM or UMTS Service benefit: For operators Realize the diversification of services. For subscribers Enjoy the ECT service. Requirements for peripheral network entities: None.
WMFD-021100 Function name: Supplementary service restriction Specification: None Implemented node: VMSC/VLR
Page 18 of 146
CONFIDENTIAL
Served network: GSM and UMTS Brief introduction: The function is used to restrict a special number being HOLD, passively being added to the multiparty service (MPTY), or passively serving as an ECT diverting party. Description: The function is used to restrict a special number being HOLD, passively being added to the MPTY, or passively serving as an ECT diverting party. It aims to prevent illegal subscribers from deceiving by using the network supplementary service function. For example, cheater A dials the number of cheatee B who has a rechargeable card, holds B, and dials 0850. After dialing 0850, A enters his own MSISDN according to the voice prompt first, and then sets up the MPTY. B listens to the alert tone, requiring him to enter the information of the rechargeable card. Thus when B completes the operation, the money in the card is put on the account of A. This function can restrict this deceiving method, greatly reducing the probability of subscribers being deceived. It only supports the restriction function of supplementary services HOLD, MPTY and ECT. In the service, you can set self-defined properties 36, 37 and 38 for special numbers by setting the subscriber service property data to restrict HOLD, MPTY, and ECT respectively. When a calling subscriber calls a special number, since the subscriber service property data is matched, and restricting HOLD, MPTY, and ECT is set, the calling subscriber cannot perform the operation of HOLD, MPTY, and ECT. Typical application scenario: The function supports subscribers to directly dial some specific numbers which restrict the three supplementary services such as HOLD, MPTY, and ECT. 1: A calls B, or B calls A, and A originates call hold after call completion. If B is a restricted subscriber, the HOLD operation of A to B fails. 2: A calls B, and A originates call hold after call completion. A calls C, and A originates the MPTY or ECT service after call completion. If B is not a restricted subscriber, while C is a restricted subscriber, the MPTY or ECT service originated by A fails after C is put through. 3: B calls A, and A originates the call hold after call completion. A calls C, and A originates the MPTY or ECT service after call completion. If C is a restricted subscriber, the multi-connection request of A fails. 4: A calls B, and A originates call hold after call completion. C calls A, and A originates the MPTY or ECT service after call completion. If C is a restricted subscriber, the multi-connection request of A fails. The MPTY also contains adding new subscribers to the existing meeting. Through the forwarding mode, the function supports transferring subscribers to some specific numbers which restrict the three supplementary services such as HOLD, MPTY, and ECT.
Page 19 of 146
CONFIDENTIAL
When subscribers are transferred to some specific numbers such as 0850 through the forwarding mode, the three supplementary services such as HOLD, MPTY, and ECT can be transplanted. That is, restrict the function of HOLD, MPTY or ECT according to the latest put-through numbers, but not the intermediate numbers of subscribers. In which, the forwarding contains intra-office forwarding and other office forwarding. In addition, the function of whether to restrict these supplementary services is related to calls formed by subscriber dialing some specific numbers. When these calls are released, it is not required to restrict the function. For example, subscriber A dials and holds B who is not a restricted subscriber, and then dials C who is a restricted subscriber. At this time, it is not allowable for A to originate HOLD, MPTY or ECT. When A releases the call between A and C, and then dials D who is not a restricted subscriber, A can originate HOLD, MPTY or ECT after call completion. Service benefit: For operators The supplementary service restriction function makes operators restrict malicious subscribers to deceive through supplementary services provided by the network, thus improving subscriber satisfaction. For subscribers It greatly reduces the probability of subscribers being deceived. Requirements for peripheral network entities: The supplementary service restriction function only involves the requirements of the MSC. For the service, the originating office (V)MSC mainly completes different signaling processing and data analysis of relevant calls.
Page 20 of 146
CONFIDENTIAL
Page 21 of 146
CONFIDENTIAL
WMFD-040100 Function name: Multimedia Telephony service (H.324M) Description: With the support of UDI bearer service, implement the Visual Communication of circuit-switched domain (CS), including the multimedia services, such as video conference, Video on Demand and mobile TV and so on. Implemented node: VMSC/VLR, GMSC and TMSC Serve network: UMTS Service benefit: For operators Provide visual communication service of CS. Strengthen service competition Attract the fad or commercial subscribers that are interest in visual communication service. For subscribers Satisfy the desire for visual communication. Requirements for peripheral network entities Need the support from VIG for video conference, Video on Demand and mobile TV services.
WMFD-040200 Function name: Ring Back Tone service for speech Description: Ring Back Tone service for speech is also called Ring Back Tone (RBT) service. It replaces the tedious ring back tone with fair-sounding music and other special sounds and voices. When other subscribers call one customized with RBT service, they hear customized RBT instead of conventional RBT. Huawei MSOFTX3000 supports multiple implementation modes (such as, calling party devious, non-devious of calling party and non-devious of called party). Huawei MSOFTX3000 support these triggering mode: SS-CODE, IN, NPI. Implemented node: VMSC/VLR, GMSC, and TMSC
Page 22 of 146
CONFIDENTIAL
Serve network: GSM and UMTS Service benefit: For operators Provide rich services. Strengthen operator competition. Increase the revenue. For subscribers Enjoy fair-sounding music. Requirements for peripheral network entities Obtain the support from SCP and IP equipment.
WMFD-040400 Function name: Operator determinate call purge (ODR) Description: The operators can forcedly disconnect a call being in conversation at any time. Implemented node: VMSC/VLR, GMSC and TMSC Serve network: GSM and UMTS Service benefit: For operators Forcedly disconnect the malicious long-time conversation of fraud subscribers to reduce charging loss. Forcedly disconnect the long-time conversation because of network abnormity to reduce charging variance as possible and charging loss of end subscriber arising thereof. For subscribers Avoid the calls from being embezzled maliciously to reduce charging loss. Requirements for peripheral network entities None
WMFD-040500 Function name: Optimal Routing (OR) Description: Optimal Routing (OR) is a network optimization strategy of operators. Its description is available in 3GPP TS 23.079. Supporting OR can reduce alternate speech path routing of some calls to save the network resource and reduce the operation cost. Through negotiation and cooperation between operators, three types of OR call procedures can be supported:
Page 23 of 146
CONFIDENTIAL
Basic OR call: The GMSCA belonging to operator A can directly obtain the roaming number from the HLRB belonging to operator B and directly route the call to the VMSCB of the roaming subscriber, instead of routing the subscriber number to GMSCB for processing. Early forwarding OR call: If early forwarding occurs to the call upon the query of basic optimal route, early forwarding can be processing on the GMSCA so far the corresponding early forwarding charging principles are met. Late forwarding OR call: If late forwarding occurs to the call on the VMSCB, and the corresponding early forwarding charging principles are met, late forwarding procedure can be carried out on the GMSCA that obtains the roaming number to reduce alternate speech path routing when the call is transited through the VMSCB. Implemented node: VMSC/GMSC Served network: GSM or UMTS Service benefit: For operators OR can help save the operation cost. As the operation strategy, OR also help to win more subscribers by reducing the call costs of subscribers using the OR. For subscribers Subscribers can save call costs if operators reduce the call costs of subscribers using the OR. Requirements for peripheral network entities: Negotiation and cooperation between operators and support of the network entity HLR are required.
WMFD-040600 Function name: Black or white list for calls Description: Black or white list provides a means to bar calls according to the source of calling number and/or calling number, and called number. This function is primarily used by gateway offices to control the authority of inter-network calls. At present, black or white list is a powerful call restriction control function. The calling or called parties can be set through data configuration to a group such as black list group, white list group, or common group. Calls between the white list group and other groups are allowed. Calls between black list group and non-white list group are prohibited. Calls between common groups are restricted depending on the relationship between groups. Black or white list function is divided into two parts: Calling number discrimination and black and white lists. For an incoming trunk group call, the discrimination group number and call barring group number can be set in the trunk group. If the discrimination group number is valid, calling number discrimination is carried out and the discrimination result is direct call barring, or call barring according to the minimum or maximum number length, or modification of attributes (primarily the call barring group number). After the calling number discrimination is completed, if call barring is not carried out, the final mobile originated (MO) call barring group is obtained. Then the mobile-terminated (MT) call barring group is obtained through data configuration. If the relationship between calling and called parties
Page 24 of 146
CONFIDENTIAL
cannot be determined, the relationship between groups will be configured to decide whether to disconnect the call. Through the above procedures, calling and called parties of an incoming trunk call can be listed to the black or white list. Implemented node: GMSC Served network: GSM or UMTS Service benefit: For operators Allow or prohibit the transiting of toll calls to other operators. Intercept calls with wrong calling numbers to avoid wrong billing. For subscribers Requirements for peripheral network entities: None
WMFD-040900 Function name: Notification of Failure to Multimedia Calls (NFMC) Description: If the calling party originates an unsuccessful VP call, a USSD format notice will be returned immediately to the calling party. Because the call originated by calling party is video one, it is impossible to play announcement directly. The service will provide a USSD to perfect subscriber interface dramatically once the call is not connected. If multimedia fallback or video gateway function is selected, the subscriber also achieves the same result through playing failure announcement or video prompt. Implemented node: VMSC/VLR Serve network: Service benefit: For operators Enhance QoS. For subscribers Experience more friendly subscriber and optimized service. Requirements for peripheral network entities None UMTS
WMFD-041100 Function name: Speech telephony for international prepaid roaming subscribers (UCB) Description:
Page 25 of 146
CONFIDENTIAL
When an international roaming subscriber wants to originate a speech call, send a USSD request to home SCP and the USSD request includes subscriber USSD service code, and called number. According to subscriber USSD request, SCP authenticates the subscribers first, and then sends an ICA command to SSP. Upon receiving the command from SCP, SSP originates a call to calling and called party respectively. After the calling and called party connect the call, connect the two calls from SSP to calling and called party to implement the conversation between calling and called party. In addition, the subscriber can set a call from SCP to calling party first or a call from SCP to called party through this function. Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Service benefit: For operators Provide speech UCB call. For subscribers International roaming subscriber can originate a speech call through UCB service. Requirements for peripheral network entities Cooperate with SCP.
WMFD-041400 Function name: Caller or callee pay Description: Caller/callee pay is a new service over ETSI GSM CAMEL PHASE2 standard. Mobile subscriber enjoys caller pay service through adding service access code (such as 12597) to original MS number, and the caller pays partial or all the conversation fees for the callee. Mobile subscriber enjoys callee pay service through adding service access code (such as 12598) to original MS number, and the callee pays partial or all the conversation fees for the caller. For the caller pay service, the caller pays the conversation fees for the callee. For the callee pay service, the callee pays the conversation fees for the caller. Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS
Page 26 of 146
CONFIDENTIAL
Description: VPN service: Establish a private network of logic voice channel on the PLMN and PSTN, and enable the convenient communication among enterprise and group subscribers through private numbering plan and Abbreviated Dialing. If VPMN service is activated in the PLMN, we provide a private network service similar to PSTN Private Branch Exchange (PBX) for the mobile subscriber of the group registering this service. The system triggers the IN based on CSI. VPN service provides the following functions for VPMN subscriber: Intra-network call. External network call. Private label. Abbreviated label. Group access number. Override. The service provides a preferential strategy of conversation fee for the group and enterprise, which facilitates remaining the important customers for the mobile operators. According to the specifications, VPMN service requires that all the MSC/GMSC/HLR should support MAP2+, all the MSC/GMSC provides SSP function, and triggers the IN service through O-CSI/T-CSI. So VPMN service must be implemented in the target network. Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Service benefit: For operators Provide VPMN service. For subscribers Enjoy VPMN service. Requirements for peripheral network entities Cooperate with SCP.
WMFD-041700 Function name: Prepaid IP calls at fixed terminal (PPIP) Description: PPIP service is an intelligent network service over ETSI GSM CAMEL PHASE2 standard. The PSTN subscriber can establish a prepaid account in the system to originate an IP call through this account. Currently, set PSTN number directly to an account, that is, bind PSTN number with this account. The subscriber can originate an IP call directly through this PSTN telephone. The system determines whether to connect or disconnect the call based on the account balance in case of call setup. Once the call is connected, the system performs real-time charge and reduces the PP money on the subscriber account. If the account balance is used up, the call will be disconnected forcedly.
Page 27 of 146
CONFIDENTIAL
WMFD-041800 Function name: IP calls at fixed terminal for postpaid subscribers Description: Postpaid IP service: The mobile subscriber applies for the service and pays this service fees. The service account of service applicant is paid one, recording the service fees. The PSTN subscriber enjoys the service, and originates an IP call directly through this service. The service account of subscriber enjoying the service is used one, recording the setting of this service and conversations. The system determines whether to connect or disconnect the call based on the account balance in case of call setup. Once the call is connected, the system controls the charging. The marketing dept. charges IP conversation fees for the subscriber based on postpaid bill. You can bind multiple PSTN telephone accounts (with the maximum of 50 and default value 10) into a MS to pay conversation fees of all the IP calls. But the PSTN telephone should be located in the same service area with the bound MS. Implemented node: GMSC/SSP Serve network: GSM and UMTS
WMFD-042000 Function name: IP calls for mobile called party Description: The PSTN or mobile subscriber can originate an IP call through dialing IP access code+ called mobile number. Implemented node: GMSC
WMFD-042100 Function name: North American Equal Access (NAEA) Description: Equal access service: The mobile subscriber can select freely the network of each toll operator to implement the equal competition of toll operator. To implement the equal access, each toll operator is allocated for a CIC. After signing an agreement with relevant toll operator, the mobile subscriber can select freely the toll network of this toll operator to originate a call through adding CIC of this toll operator. Two modes to use the service are: Preset CIC and Dial up freely CIC. Mobile subscriber can add the function of network selection through preset. The mobile subscriber can select freely toll operator through the preset function. After the preset, mobile
Page 28 of 146
CONFIDENTIAL
subscriber can select a preset toll network channel of one operator to originate a toll call without dialing the CIC. The mobile subscriber with the preset function still can select non-preset toll operator through adding CIC. The subscriber neither dialing CIC nor performing preset for the operator adopts the default toll network set by the operator for the call proceeding. According to the technical specifications stipulated by Information Industry Ministry, the function of network selection through preset is implemented by enabling a subscriber parameter North American Equal Access Preferred Carrier ID (NAEA) defined in the ETSI 09.02 (MAP2+) specifications. This parameter is stored in HLR, identifying the toll operator selected by the mobile subscriber. This parameter can be located in the "Insert subscriber data" in case of location update and the "Send routing information ack in case of call connection. HLR sends the parameter to MSC/VLR. According to the received NAEA parameter, MSC/VLR maps the Carrier ID value of the parameter to toll service network code (CIC) of each toll operator. If the service requirements are satisfied, add the code to called number and send them to GMSC. In addition, GMSC completes the subsequent call proceeding. Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Service benefit: For operators Satisfy the requirements for equal competition. For subscribers Select the toll call service of each toll operators freely. Requirements for peripheral network entities HLR should be able to support the subscription of this service data.
WMFD-042200 Function name: Cell and Time Dependent Discount Description: Cell and Time Discount: According to the agreement with the operator in advance, the system can determine discount rate of current call based on the cell position where the subscriber is located when originating or connecting a call and time. The discount area of cell discount can be divided with unit of GSM cellular. Because the population and activity places are different, the cellular cell managed by one mobile network may be very busy, but other cellular cells are relatively idle. Cell discount facilitates operator adjusting the geographical distribution of traffic through the rate, and decreases the discount rate of the area with less traffic to increase the traffic in this area. The discount time segment of time discount can be divided with the unit of hour and minute. Different areas are located in different time segments. Because the centralized personnel and company institutes are different, the peak segments of traffic are different. For example, the traffic of the area with centralized offices, and enterprise/institutes at daylight can be the peak, but that with centralized supermarkets and amusement centres at night do.
Page 29 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR Serve network: GSM and UMTS Service benefit: For operators Time discount service enables the operators to provide preferential for the subscribers during the common time segment. Determine the specific preferential time segment and discount in the cell based on specific traffic model in the cell. Help the operator equalize traffic and enhance the economic efficiency. For subscribers More charging selection. Requirements for peripheral network entities None
WMFD-042300 Function name: Enhanced roaming restriction Description: It is not allow the subscriber to perform location update at local MSC based on the Zone Code, location area, roaming type and IMSI of current roaming subscriber to implement flexible roaming restriction function. It enables the operator to implement flexible roaming restriction function based on the Zone Code, location area, roaming type and IMSI of current roaming subscriber. Implemented node: VMSC/VLR Serve network: GSM and UMTS Service benefit:s For operators Provide flexible and controllable roaming restriction mechanism. Provide localization service similar to Wireless Local Loop (WLL) service. Attract more low-priority subscriber. Increase customer group. Increase the traffic. For subscribers Enjoy rich localization service to avoid the charging increment because of the roaming in another place. Requirements for peripheral network entities None
Page 30 of 146
CONFIDENTIAL
WMFD-042400 Function name: Enhanced MSRN allocation Description: Support the function of allocating roaming number based on location area cell. MSOFTX3000 also supports the function of allocating roaming number based on the MSC-ID in case of virtual multi-MSC solution. Implemented node: VMSC/VLR Serve network: GSM and UMTS Service benefit: For operators Determine the cell through roaming number to adopt different customer strategy, such as charging strategy. For subscribers None Requirements for peripheral network entities None
WMFD-042500 Function name: Mobile Number Portability (MNP) Description: Huawei MSOFTX3000 supports MNP service of intelligent network mode. When originating a call, MSC triggers CAMEL procedure to SCP, SCP queries the NP database. If the subscriber is a NP one, insert the route information to called number, and then set up a call normally. Huawei MSOFTX3000 also support MNP SRF mode, which need MSOFTX3000 cooperate with the STP to provide MNP service. The relevant NPDB function is embedded the STP.. Implemented node: VMSC/VLR Serve network: GSM and UMTS Service benefit: For operators Provide MNP service. For subscribers Subscribe different operators without modifying telephone number. Requirements for peripheral network entities Cooperate SCP or STP.
Page 31 of 146
CONFIDENTIAL
WMFD-042700 Function name: Alternate Line Selection (ALS) Description: Support the functions of line1 and line 2 through the terminal and subscribe a number for each line. For two numbers of ALS, the subscriber can set different CF SS and Call barring SS. When the subscriber adopts line 2 number: Perform only speech service and its supplementary service. Adopt ODB for service restriction. Only receive SM instead of sending SM. Can not perform USSD operation. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS Service benefit: For operators Provide two independent numbers for the subscriber to enhance the competition. For subscribers Apply for dual-line for office and private numbers. Requirements for peripheral network entities None
WMFD-042800 Function name: Dual-MSISDN for multimedia and speech telephony Description: Subscribe two services of independent numbers respectively based on video and speech service. This function is different from that with multiple MSISDN. After the subscriber subscribes the service, calling/called video and speech calls adopt different numbers, and dual-MSISDN function is effective only when the subscriber is a called party. If the subscriber registers this function and ALS, the subscriber has 3 telephone numbers. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS Service benefit: For operators Provide two independent speech and video call completely for the subscriber to enhance the competition. For subscribers Apply for two numbers for speech and video call respectively.
Page 32 of 146
CONFIDENTIAL
WMFD-050500 Function name: GERAN/UTRAN Access Restriction (ARD) Description: This function allows operators to control the access of subscriber to the GERAN or UTRAN. Provision of this function requires the collaboration of MSOFTX3000 and HLR and the HLR must support the ARD subscription function. The MSOFTX3000 provides the function to judge whether the subscriber has subscribed to the ARD service. For example, if GREANAllowed/UTRANNOTAllowed is configured upon the subscription of ARD on the HLR, if the local MSFTX3000 supports the ARD 3G function, location update will fail due to the access restriction when the subscriber tries to access the network of local office from the 3G UTRAN. In this way, the subscriber is restricted from accessing the 3G network. Implemented node: VMSC/VLR Served network: GSM or UMTS Service benefit: For operators Flexibly control the subscribers access to GERAN or UTRAN. For subscribers -
Page 33 of 146
CONFIDENTIAL
Requirements for peripheral network entities: The network must be equipped with HLR and the HLR must support the ARD subscription function.
WMFD-050600 Function name: Shared Network Area in Connected Mode (SNA) Description: At present, roaming restriction of mobile network is implemented in idle mode. There are ZC roaming restriction and enhanced roaming restriction and these types of restrictions are all controlled by the CN. If relocation occurs when a subscriber is engaged in the conversion, the CN cannot restrict the roaming area of the subscriber. In this case, the area that cannot be accessed in idle can be accessed in connected mode. The Shared Network Area in Connected Mode (SNA) function is used to solve this problem. For example, if two 2G network operators shares one 3G network, operators can use this function to ensure that subscribers use their own 2G network only. The SNA function is implemented by CN and UTRAN together. The MSC provides the configuration of roaming restriction information in connected mode and the shared network information and transfers the roaming restriction information to the RNC. The RNC completes the roaming restriction in connected mode based on the roaming restriction information received. The configuration of shared network information contains the configuration of shared network area, which helps realize the area-based roaming restriction. Configuration of subscriber roaming restriction information is completed through the IMSI number segment. The roaming restriction in connected mode is implemented by configuring the allowed shared network area group. Implemented node: VMSC/VLR Served network: UMTS Service benefit: For operator Realize consistent mobile access restriction in idle mode and in connected mode and enhance the network restriction function. For subscribers None Requirements for peripheral network entities: RNC must support the SNA function. WMFD-050700 Function name: Local-based service restriction Description: When a subscriber who subscribes to a ZoneCode updates a location or performs services, the MSC judges whether the subscriber belongs to a ZoneCode, and performs logic judgment according to the area service. For local smart services, this function allows or refuses subscribers
Page 34 of 146
CONFIDENTIAL
to update location, complete calls (calling or called), or to use the SMS, supplementary service and LCS service. Implemented node: VMSC/VLR Served network: GSM and UMTS Service benefit: For operators It is convenient for operators to develop the area service of local smart services. For subscribers Requirements for peripheral network entities: The HLR is required to support subscribing the ZoneCode.
WMFD-050900 Function name: Roaming restriction for CAMEL Description: When a subscriber subscribes the O-CSI, the MSC can consider whether the CAMEL subscriber is allowed or restricted to roam according to the subscribed CAMEL version. Implemented node: VMSC/VLR Served network: GSM and UMTS Service benefit: For operators It is convenient for operators to control whether to allow the roaming of intelligent subscribers. For subscribers Requirements for peripheral network entities: The HLR is required to support subscribing the O-CSI.
WMFD-051000 Function name: Priority selection of subscribers when VDB capacity being restricted Description: When the VDB capacity nears the upper limit, it is required to restrict online of subscribers with lower priority according to the roaming type, or subscribed EMLPP and CARP. Implemented node: VMSC/VLR Served network: GSM and UMTS
Page 35 of 146
CONFIDENTIAL
Service benefit: For operators In case that the capacity is restricted, it is required to ensure the normal online of subscribers with higher priority so as to reduce the loss of operation. For subscribers Requirements for peripheral network entities: When adopting subscribed EMLPP and CARP to control priorities, the HLR needs to support subscription.
WMFD-060100 Function name: TMSI re-allocation Description: Temporary Mobile Subscriber Identity (TMSI) is managed by MSC/VLR. TMSI re-allocation aims to ensure IMSI security through using TMSI in the air radio interface to prevent the Third Party from tracing the subscriber activities through IMSI. When the subscriber enjoys the services in the area controlled by a MSC/VLR, MSC/VLR allocates a TMSI identifying the subscriber uniquely at this MSC/VLR based on the special principle of TMSI allocation for the subscriber. So the network identifies the subscriber through the TMSI, all the exchange of signaling and data does not use IMSI again for the purpose of security. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-060200 Function name: Mobile subscriber identifier Description: Mobile subscriber identifier refers to IMSI.
Page 36 of 146
CONFIDENTIAL
When the network cannot identify TMSI used by mobile subscriber in case of the access, originate the IMSI identify process. After receiving the identifier response of mobile subscriber, the network allocates new TMSI. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-060300 Function name: Authentication and Encryption Description: Support authentication and encryption process defined by GSM and UMTS. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-060301 Function name: GSM Authentication and Encryption Description: Support authentication encryption algorithm and process defined by GSM. Support common authentication. Support 1/N authentication mode. Perform only once authentication during N times of location update and service access through data configuration. Support the multiplexing of authentication parameter. One authentication procedure requires a group of authentication parameters. Different authentication parameters for different authentications will result in high signaling load from MSC to HLR, and the decrease of HLR processing capability. The subscriber can use the authentication parameter multiplexing function and multiplexing times at MSC through the data configuration. In this way, multiple authentications use the same authentication parameters to reduce network load and enhance HLR processing capability. Support the encryption defined by GSM. Implemented node: VMSC/VLR Serve Network: GSM
WMFD-060302 Function name: UMTS Authentication and Encryption Description: Support authentication encryption algorithm and process defined for the UMTS. Compared with GSM network, the UMTS authentication parameters are extended from triplets and quintets. In addition, several new encryption algorithms are defined.
Page 37 of 146
CONFIDENTIAL
Support 1/N authentication mode and authentication parameter multiplexing. Implemented node: VMSC/VLR Serve Network: UMTS
WMFD-060400 Function name: Authentication one more time Description: In authentication procedure, if authentication is failure (SRES return from MS is not correct), then MSC will use another new parameter RAND to authenticate the MS in the current connection. If the second authentication is failure, then MSC will reject this service request according to GSM specification. Implemented node: VMSC/VLR Serve Network: UMTS
WMFD-060500 Function name: Conversion functions of authentication triplets and quintets Description: Support the inter-conversion between GSM Triplet and UMTS quintuple authentication sets to facilitate the free roaming or handover between GSM and UMTS for the subscribers. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Provide seamless roaming function in the system. For subscribers Enjoy the service provided by GSM network where the UMTS network is not covered. Requirements for peripheral network entities None
WMFD-060600 Function name: Built-in EIR Description: Built-in Equipment Identification Register (EIR) refers to the virtual EIR set on the MSC. Information about some illegal International Mobile Station Equipment Identities (IMEIs) can be configured on the built-in EIR to allow the local operator to realize the CHECKIMEI function.
Page 38 of 146
CONFIDENTIAL
With the CHECKIMEI function, IMEI can be obtained from the mobile equipment and sent to the EIR to further check the equipment status. In the function configuration table, there is an item indicating whether the built-in EIR function is supported. If built-in EIR is supported, grey list subscribers and black list subscribers can be configured. Those subscribers not configured are treated as white list subscribers by default. If a subscriber is a black list subscriber, the CHECKIMEI fails, and as a result, location update of the subscriber and service processing are rejected. If a subscriber is a grey list subscriber, location update of the subscriber is allowed. During the service processing, if the grey list subscriber is a calling party and the tone play is configured in the MAP function configuration table, the tone is played. After the tone is played, whether the call is connected is determined by the MAP function configuration table. If tone play is not configured in the MAP function configuration table, the tone is not played and the call is directly connected. If the grey list subscriber is a called party, no special processing is used. The maximum volume of build-in EIR is 20,000. Implemented node: VMSC/VLR (You can add GMSC or TMSC here.) Served network: GSM or UMTS Service benefit: For operators Use the built-in EIR to realize part of the EIR functions on the MSC. For subscribers None Requirements for peripheral network entities: None
Page 39 of 146
CONFIDENTIAL
VLR restoration WMFD-071300 Implemented node: VMSC/VLR Serve Network: GSM and UMTS
Page 40 of 146
CONFIDENTIAL
WMFD-080100 Function name: Intra-GSM handover Description: MSOFTX3000 supports intra-GSM-MSC handover, inter-GSM-MSC handover, and inter-GSM-MSC subsequent handover.
WMFD-080101 Function name: Intra-GSM_MSC handover Description: The handover between two BSS of the same MSC According to whether MSC is the Anchor MSC or not, divide the handover into intra- MSCa handover and intra-MSCb handover. The MSC of call established early is called Anchor MSC. The handover in the Anchor MSC is called intra-MSCa handover, and that in non-anchor MSC is called intra-MSCb handover.
WMFD-080102 Function name: Inter-GSM_MSC handover Description: The handover from BSS of Anchor MSC to BSS of non-anchor MSC During the inter-GSM-MSC handover, Anchor MSC (MSCa) controls all the handover process, including the following: Select target MSC from target cell and BSC. Originate a resource handover request to non-Anchor MSC (MSCb) through MAP signaling, bearer setup between MSCs and call control after the handover. MSCb is responsible for establishing the radio side resource required by this handover, and completes the call control after the handover, cooperating with MSCa.
WMFD-080103 Function name: Intra-GSM subsequent handover Description: Refer to the inter-GSM-MSC handover originated by non-anchor MSC (MSCb) after the inter-GSM-MSC handover According to whether target MSC is Anchor MSC, divide the handover into subsequent handover to MSCa and subsequent handover to the Third Party. The procedures for subsequent handover to MSCa: After receiving BSS handover request, MSCb originates a handover to MSCa through MAP signaling.
Page 41 of 146
CONFIDENTIAL
After controlling the resource allocation of local BSS, MSCa notifies MSCb to deliver a handover command. When the subsequent handover is over, release the bearer between MSCa and MSCb. The procedures for subsequent handover to the Third Party MSCb: After receiving BSS handover request, MSCb originates a handover to MSCa through MAP signaling. MSCa originates a handover to MSCb. When the subsequent handover is over, release the bearer between MSCa and MSCb.
WMFD-080200 Function name: Intra-UMTS handover Description: Intra UMTS 3G handover refers to the handover within the UMTS system. MSOFTX3000 supports intra-UMTS-MSC handover, inter-UMTS-MSC handover, and inter-UMTS-MSC subsequent handover.
WMFD-080201 Function name: Intra-UMTS_MSC handover Description: The handover between two RNS of the same MSC According to whether MSC is the Anchor MSC or not, divide the handover into intra- MSCa handover and intra-MSCb handover. The MSC of call established early is called Anchor MSC. The handover in the Anchor MSC is called intra-MSCa handover, and that in non-anchor MSC is called intra-MSCb handover.
WMFD-080202 Function name: Inter-UMTS_MSC handover Description: The handover from RNS of Anchor MSC to RNS of non-anchor MSC During the inter-UMTS-MSC handover, Anchor MSC (MSCa) controls all the handover process, including the following: Select target MSC from target cell and RNS. Originate a resource handover request to non-Anchor MSC (MSCb) through MAP signaling, bearer setup between MSCs and call control after the handover. MSCb is responsible for establishing radio side resource required by the handover, and completes the call control after the handover, cooperating with MSCa.
Page 42 of 146
CONFIDENTIAL
WMFD-080203 Function name: Intra-UMTS_MSC subsequent handover Description: Refer to the inter-UMTS-MSC handover originated by non-Anchor MSC (MSCb) after inter-UMTS-MSC handover According to whether target MSC is Anchor MSC, divide the handover into subsequent handover to MSCa and subsequent handover to the Third Party. The procedures for subsequent handover to MSCa: After receiving RNS handover request, MSCb originates a handover to MSCa through MAP signaling. After controlling the resource allocation of local RNS, MSCa notifies MSCb to deliver a handover command. When the subsequent handover is over, release the bearer between MSCa and MSCb. The procedures for subsequent handover to the Third Party: After receiving RNS handover request, MSCb originates a handover to MSCa through MAP signaling. MSCa originates a handover to MSCb. When the subsequent handover is over, release the bearer between MSCa and MSCb.
WMFD-080300 Function name: Inter-system handover Description: Include the handovers from GSM network to UMTS network or from UMTS network to GSM network.
WMFD-080301 Function name: Handover from GSM to UMTS Description: Support the function: GSM and UMTS dual-mode MS can be switched from GSM network to local office (3G MSC) during the conversation, and the system completes automatically differential processing of MS access mode. For example, encryption mode changes of UMTS and GSM. Service benefit: For operators If the operator has constructed a GSM network, the construction of 3G network can ensure the seamless roaming and handover of subscriber. The area that is not covered by a network can be switched to another network smoothly to ensure that the conversation is not affected by network coverage. Especially for the earlier stage of network construction, there may be many cross-system handovers.
Page 43 of 146
CONFIDENTIAL
For subscribers Ensure the conversation quality. Avoid call drop of cross-system handover. Requirements for peripheral network entities Upgrade GSM network.
WMFD-080302 Function name: Handover from UMTS to GSM Description: Support the function: GSM and UMTS dual-mode MS can be switched from UMTS network to GSM network during the conversation, and the system completes automatically differential processing of MS access mode. For example, encryption mode changes of UMTS and GSM. For Huawei MSOFTX3000, the subscriber can be switched from UMTS network to GSM network successfully when current GSM network is not upgraded. Service benefit: For operators If the operator has constructed a GSM network, the construction of 3G network can ensure the seamless roaming and handover of subscriber. The area that is not covered by a network can be switched to another network smoothly to ensure that the conversation is not affected by network coverage. Especially for the earlier stage of network construction, there may be many cross-system handovers. For subscribers Ensure the conversation quality. Avoid the call drop during the cross-system handover. Requirements for peripheral network entities None
WMFD-080600 Function name: Directed retry handover Description: When MSC assigns a traffic channel to a MS, the BSC/RNC initiates the handover to another BSC/RNC because of lack of resource or weakness of radio signal. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Facilitate enhancing successful handover ratio.
Page 44 of 146
CONFIDENTIAL
For subscribers Reduce the call drop. Requirements for peripheral network entities None
WMFD-080700 Function name: Signaling handover Description: It means the handover when a MS only has signaling connection with network (i.e. traffic channel not assigned). Service benefit: For operators Facilitate enhancing successful handover ratio. For subscribers The call loss is decreased. Requirements for peripheral network entities None
WMFD-080900
Function name: Load based handover Description: In the case of handover between the 2G system and the 3G system, the cell load information is carried to other systems to balance the traffic and load of the UMTS network and the GSM network of operators. Intra-office handover from 3G to 2G If the HANDOVER REQUEST ACKNOWLEDGE message returned to the MSC by the BSC contains the cell load information, and the MSC configures the RNC to support the function of cell load-based handover, the MSC transparently transmits the cell load information in the Iu interface message RELOCATION COMMAND. Inter-office handover from 3G to 2G During an inter-office handover, if the HANDOVER REQUEST ACKNOWLEDGE message returned to the MSC-B by the BSC contains the cell load information, the MSC-B transparently transmits the information to the MSC-A in the E interface message MAP-Prep-Handover resp. If the MSC-A configures the RNC to support the function of cell load-based handover, and the MAP-Prep-Handover resp message returned to the MSC-A by the MSC-B contains the cell load information of the destination side, the MSC-A transparently transmits it to the RNC in the RELOCATION COMMAND message. Intra-office handover from 2G to 3G
Page 45 of 146
CONFIDENTIAL
If the RELOCATION REQUEST ACKNOWLEDGE message returned to the MSC by the RNC contains the cell load information, and the MSC configures the BSC to support the function of cell load-based handover, the MSC transparently transmits the cell load information in the A-interface message HANDOVER COMMAND. Inter-office handover from 2G to 3G During an inter-office handover, if the RELOCATION REQUEST ACKNOWLEDGE message returned to the MSC-B by the RNC contains the cell load information, the MSC-B transparently transmits the information to the MSC-A in the E interface message MAP-Prep-Handover resp. During an inter-office handover, if the MSC-A configures the BSC to support the function of cell load-based handover, and the MAP-Prep-Handover resp message returned to the MSC-A by the MSC-B contains the cell load information of the destination side, the MSC-A transparently transmits it to the BSC in the HANDOVER COMMAND message of A-interface. Implemented node: VMSC/VLR Served network: GSM and UMTS Service benefit: For operators The function is used to balance the traffic and load of the UMTS network and the GSM network of operators. For subscribers Requirements for peripheral network entities: The MSC, BSC and RNC need to contain and process the cell load information.
Page 46 of 146
CONFIDENTIAL
WMFD-090100 Function name: Dual Tone Multiple Frequency (DTMF) Description: Number allocation function: After the system receives DTMF signal from mobile terminal side during the conversation, transfer the signals to former office after the conversion through inband number allocation of TUP/ISUP (or outside band number allocation of BICC signaling). Number collection function: After the system receives inband DTMF signal (or outside band DTMF signal of BICC signaling) of TUP/ISUP signaling, convert the signal into relevant signaling for the processing of system service software or the report mechanism.
WMFD-090200 Function name: Playing of general signal tone Description: Support the playing of general signal tone, such as busy tone, and ring back tone. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-090300 Function name: Playing of English tone Description: Support the playing of English tone. Support the local tone playing by adapting the local language grammar. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-090400 Function name: Dynamic adaptation of failure value and tone id Description: According to different failure value, play special tone through data configuration. Implemented node: VMSC/VLR, GMSC and TMSC Serve Network: GSM and UMTS Service benefit: For operators Provide the playing of tone for different failures. For subscribers -
Page 47 of 146
CONFIDENTIAL
Experience more friendly subscribers. Requirements for peripheral network entities Cooperate with media gateway.
WMFD-090600 Function name: Playing of tone for supplementary services (CW/HOLD/CF) Description: The relevant subscribers hear the prompt tone for supplementary services when performing supplementary services, such as CW, CH and CFW. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS Service benefit: For operators Provide playing of tone for supplementary services. For subscribers Experience more friendly subscribers. Requirements for peripheral network entities Cooperate with media gateway.
WMFD-090700 Function name: Playing of tone for dropped call Description: One party of a call is disconnected because of network signal quality, so the network automatically plays special announcement for another party of the call. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Provide the playing of tone for dropped call and network disconnection. For subscribers Better user friendly interface Requirements for peripheral network entities Cooperate with media gateway.
Page 48 of 146
CONFIDENTIAL
WMFD-090800 Function name: Playing of tone for MPTY Description: Add comfortable background tone through MSC to enable the telephone conference participants to know they are still enjoying the telephone conference. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Provide background tone prompt of telephone conference environment. Enhance the customer satisfaction. For subscribers Experience more friendly subscribers. Requirements for peripheral network entities Cooperate with media gateway.
WMFD-091000 Function name: Adaptation for local language Description: Play local language tone loaded by medial gateway through uniform data configuration. Implemented node: VMSC/VLR, GMSC and TMSC Serve Network: GSM and UMTS Service benefit: For operators Provide local speech prompt. Enhance customer satisfaction. For subscribers Experience more friendly subscribers. Requirements for peripheral network entities Cooperate with media gateway.
Page 49 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR and GMSC Served network: GSM and UMTS Target market/customer: China Mobile Brief introduction: If the HLR does not subscribe the intelligence, for example, the O/T-CSI subscription information is deleted wrongly, but the subscriber is an intelligent subscriber in the SCP. When the subscriber calls, the system gives the announcement alert and restricts the call. Description: The announcement protection requirements of intelligent subscribers are from a feature provided by the Ericsson equipment in the existing 2G network found during the test of Huizhou office of China Mobile. If the HLR does not subscribe the intelligence, but the subscriber is an intelligent subscriber in the SCP. When the subscriber calls, the system gives the announcement alert and restricts the call. This requires the MSOFTX3000 to solve such a problem actually. The HLR maintenance personnel modifies an intelligent subscriber as a postpaid subscriber wrongly, thus to cause the call of the subscriber to be free from the control of the SCP. Therefore, operators cannot charge such subscribers. The detailed specifications of the requirements are as follows. 1) It is only applied in the destination network, but not applied in the OVERLAY scenario of the cascade network. 2) It is applied in the originating office and the gateway office, and can only provide announcement protection to such situation that the HLR wrongly deletes the O/TCSI subscription information. 3) It can support and distinguish subscribers in the IMSI/MSISDN O-CSI number segment, and provide announcement protection to subscribers in the IMSI/MSISDN T-CSI number segment and the IMSI/MSISDN O&T-CSI number segment. 4) It cannot restrict calls to free numbers, including free recharge and fee query numbers used in the existing network, such as 1860, 1861 and 13800138000, and calling free numbers, such as 800. 5) It cannot restrict emergency calls, such as 110, 119, 112, and 120. 6) The existing network does not support forwarding intelligent subscribers and that the intelligent subscriber is free when serving as a callee, so it regards an intelligent subscriber whose O-CSI subscription information is wrongly deleted as a postpaid subscriber, and allows normal call transfer. But a call to such intelligent subscribers whose T-CSI subscription information is wrongly deleted is restricted unconditionally when they are a callee. 7) During early forwarding, it checks announcement protection to the T-CSI subscription information of the forwarding party. 8) During a call, it cannot cause the forced release when the O/T-CSI intelligent subscription information is deleted. 9) When the announcement protection causes call release, the announcement EID is configurable. The announcement content is The service is restricted temporarily, please contact 1860 uniformly in the existing network. 10) The call of the callee is restricted due to the loss of the T-CSI subscription information, and there is no way to notify the subscriber, so the alarm information is outputted for the maintenance personnel to conveniently process it.
Page 50 of 146
CONFIDENTIAL
Service benefit: For operators It provides the method of announcement alert and outputting alarms to avoid the problem that the HLR maintenance personnel modifies an intelligent subscriber as a postpaid subscriber wrongly, thus to cause the call of the subscriber to be free from the control of the SCP, therefore operators cannot charge such subscribers. 1. When an affected subscriber originates a call or is called, the system plays the alert tone to the caller. After the caller complains, the operator maintenance personnel solves this problem by querying the intelligent subscription information of the caller and the callee in the HLR 2. When an affected subscriber is called, the system plays the alert tone to the caller. The caller may not complain, and the operator maintenance personnel solves this problem through the output alarm. For subscribers None Requirements for peripheral network entities: The intelligent subscriber announcement protection involves two NE entities, MSC and MGW. For the service, the originating office (V)MSC or the gateway office (G)MSC mainly completes different signaling processing, data analysis, and announcement of calls.
1.10 The MGW completes the load of an announcement file. Charging functions
WMFD-100000 Function name: Charging functions Description: Provide charging basis (that is a CDR) for the operators.
WMFD-100100 Function name: Generation of Call Detail Record (CDR) Description: CDR contents The CDR information includes the following: Resource occupation (such as MSC ID and incoming/outgoing trunk group number). Basic service usage (based on originating place, destination, conversation date, time, duration, and bearer service). Supplementary services usage(such as CF)
Page 51 of 146
CONFIDENTIAL
Subscriber related numbers (such as MSISDN, IMSI and MSRN). Compared with the PSTN, the conversation of mobile network adopts two-way charge. The system generates a CDR for mobile calling and called party respectively when a call is finished. In addition, many intermediate CDRs may be generated during the long-time conversation. CDR generation process CDR generation process includes: Collection of call data. Generation of CDR. CDR transfer. Collection of call data When a mobile subscriber originates or receives a call, MSOFTX3000 records all the data related to the call. When the mobile subscriber is a calling party, and the call request is sent to MSOFTX3000, MSOFTX3000 records the information related to the calling party, including calling number, calling IMSI number, calling position (MSC, BSC and cell where the calling party is located). After the called party analysis, the information related to called party will be obtained and recorded. If the call is outgoing one, the data related to trunk should also be recorded, so do the start time and date of conversation. When the mobile subscriber is a called party, VMSC where the called party is located records the call information for the called party. If mobile called and calling parties are located in the same VMSC, VMSC records the information related to calling and called party for the generation of Mobile Originated Call (MOC) and Mobile Terminated Call (MTC). If the call request comes from other switches through the trunk, the VMSC where the called party is located records the information related to this call for the generation of MTC. Under other conditions, if MSOFTX3000 is GMSC or TMSC, the collection of call data should also perform the above processing. Generation of CDR MSOFTX3000 should generate a CDR when the call is completed, call time is up to the duration of CDR generation or the service used by this conversation is changed. MSOFTX3000 records the start and end date of call, conversation duration, CDR type (such as MOC and MTC), and the cause of call completion (for example, the call is released normally, the time for CDR generation is up, used service is changed, and charging turning point is met.) MSOFTX3000 also records the data related to the CDR, such as CDR SN, the first CDR SN, and record type (independent, the first, the last and intermediate). The above data is irrelevant with this call, and the purpose of this record is to provide a convenience for CDR management. When all the data related to the CDR is recorded, MSOFTX3000 generates a CDR based on the data, and stores the CDR into CDR pool. CDR Transfer WCCU or WCSU module of MSOFTX3000 provides specially a memory size for the CDR transfer to be the CDR pool to store the CDR through cycle queue FIFO. MSOFTX3000
Page 52 of 146
CONFIDENTIAL
stores the generated CDR to the CDR pool based on the conversation. But the CDR pool continuously sends the CDR to billing gateway for storage. The memory size occupied by the CDRs sent to billing gateway will be released for new CDR, and the memory size occupied by the CDRs not be sent to billing gateway will not be used again before they are sent. To enhance the reliability that CDR pool sends the CDRs to billing gateway, MSOFTX3000 adopts transport protocol of sliding window. The two parties determine the CDRs SN to be sent before the sending, and the billing gateway returns a response to CDR pool after receiving the SN, indicating that billing gateway has received the negotiated CDRs correctly. The CDR pool will send the same CDRs repeatedly instead of other CDRS before receiving a correct response. If CDR pool receives a correct response, send next group of CDR based on the protocol. The CDR pool of MSOFTX3000 is a memory size with fixed capacity. If MSOFTX3000 generates new CDRs continuously, and the CDRs cannot be sent to billing gateway in time because of various reasons, the remaining memory of CDR pool will be decreased dramatically until the CDR pool cannot store new CDRs. that is, the CDR cannot be recorded after the conversation. To avoid the case, when the memory size occupied by CDRs not be sent to billing gateway is up to 80% of memory size of CDR pool, send an alarm to the alarm box. If more and more CDRs are not sent to billing gateway, the system will reject some calls. Once the memory size of CDR pool is up to 99%, all the calls will be rejected. CDR Type MSOFTX3000 generates various CDRs to satisfy the subscriber requirements. According to charge purpose, CDR includes: Subscriber charging CDR (MOC, MTC, supplementary services CDR, location service CDR, MO_SMS, and MT_SMS). Inter-office settlement CDR (incoming gateway CDR, outgoing gateway CDR, roaming CDR, tandem CDR, and call attempt CDR) The following details the CDRs. Implemented node: VMSC/VLR, GMSC and TMSC Serve Network: GSM and UMTS
WMFD-100101 Function name: Mobile originated/terminated call attempt (MOC/MTC) Description: Provide the conversation bill of mobile calling/called subscriber If a mobile subscriber originates a call, and the called party connects the call, a MOC CDR is generated for the mobile originating subscriber when intermediate bill timer expires or the conversation is completed. When the intermediate bill timer expires or the conversation is completed, a MTC CDR is generated for mobile called subscriber. The bill includes conversation date, time, duration, communication service type (Teleservices or bearer service), call originated address or destination, and supplementary service code. MOC and MTC CDRs for mobile subscriber includes that of IN subscriber, and SSP generates IN MOC bill for the subscriber triggering calling IN in local office, and IN MTC bill for the subscriber triggering called IN. The CDRs are labeled as CAMEL USER.
Page 53 of 146
CONFIDENTIAL
WMFD-100102 Function name: Incoming/outgoing call attempt in a gateway MSC (GWO/GWI) Description: The CDR for inter-network call is generated through gateway, and this function is used for inter-network settlement. If a call is routed to other mobile network or PSTN through GMSC, GMSC SERVER generates a GATEWAY_OUTGOING bill. This bill can be a reference for the charge settlement of outgoing route occupation between mobile network and foreign mobile network and PSTN. This CDR includes incoming route, outgoing route, outgoing circuit and calling/called number, instead of charged mobile subscriber, the Third Party, called location area, and cell information. If a call is originated from PSTN or foreign mobile network through GMSC, a GATEWAY_INCOMNG bill will be generated in GMSC. Incoming gateway bill not only can be a reference for the charge when PSTN or foreign mobile network subscriber is the calling party, but also a reference for the charge settlement of incoming route occupation between mobile network and PSTN and foreign mobile network. The CDR includes incoming route, outgoing route, and incoming circuit, instead of calling location area, cell, and charged mobile subscriber. Implemented node: GMSC Serve Network: GSM and UMTS
WMFD-100103 Function name: Roaming call attempt (ROAM) Description: Provide roaming information bill of the subscriber roaming to other networks. For a call, if the mobile called subscriber is roamed out of home network, the home GMSC of this mobile subscriber should generate relevant roaming bill for the mobile subscriber. The CDR includes incoming route, outgoing route, calling/called number, and mobile roaming number charged, and there is no the Third Party number. Implemented node: GMSC Serve Network: GSM and UMTS
WMFD-100104 Function name: Call forwarding (CF) Description: Provide the call CDRs from A to B and from B to C respectively for the CF, and label the call as a CF in the CDR.
Page 54 of 146
CONFIDENTIAL
CF SS allows called mobile subscriber to forward the incoming calls to designated number. CF bill will be generated after the CF. CF bill is generated for the mobile subscriber originating the CF. CFW bill generated for mobile subscriber includes CFW bill of mobile subscriber. SSP generates CFW bill for the IN subscriber triggering IN forwarding process in local office. The subscriber type in this bill is labeled as CAMEL USER, and the billing centre can sort out the bill based on FCI and subscriber type information provided by Huawei CFW bill. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-100105 Function name: Transit call attempt (Transit) Description: When a call is routed to MSC, and this call is neither originated at local MSC, nor terminated at local MSC, a tandem CDR is generated. The tandem CDR is generated in the TMSC, and it is generated for the fee settlement of inter-office trunk occupation. This tandem CDR includes incoming route, outgoing route, calling/called number, instead of charged mobile subscriber and the Third Party number. Implemented node: TMSC Serve Network: GSM and UMTS WMFD-100106 Function name: Short message service (SMS-MO/SMS-MT) Description: Include MO_SMS and MT_SMS. SM communication is a communication mode to transfer the characters through signaling channel. The SMS-MO/SMS-MT is different from common CDR, including the following: Calling number Called number Operation result Bytes SMC address SM content
WMFD-100107 Function name: Mobile originated information (MOI) CDR Description: When the system handles the IN call of incoming OVERLAY, the originating VMSC does not the specific position of called party to disable the accurate charging for the calling party. At that time, a complete call record is generated for the calling party, which is called MOI CDR. And the MOI CDR is sent to billing center for the accurate charging of calling party.
Page 55 of 146
CONFIDENTIAL
Generally, when the called party is IN subscriber, calling party is non-IN subscriber of local network and the call is not forwarded before the incoming, MOI CDR is generated. To satisfy the requirements for some subscribers in a country, MOI CDR is controllable, and MOI CDR can be generated for calling subscriber in other networks. MOI CDR is generated after incoming OVERLAY triggers called IN, and MOI CDR will not be generated again in the target network, Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-100108 Function name: IMEI observation ticket (CHECK IMEI) Description: If Check IMEI is originated for the mobile subscriber during the call, corresponding MSC generates Check IMEI observation ticket in this process, recording the result of Check IMEI. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-100109 Function name: HLR interrogation Description: When GMSC interrogates the information about the mobile subscriber from HLR, the corresponding HLR query bill will be generated in the GMSC. If the mobile subscriber is IN one, interrogate HLR twice, and then generate two HLR interrogation bills. (When the route information for the first time is unavailable, configure whether to generate HLR interrogation bill.) Implemented node: GMSC Serve Network: GSM and UMTS WMFD-100110 Function name: Supplementary service actions (SS_ACT) Description: The SS_ACT (such as the registration, cancellation, activation and deactivation of SS) irrelevant with the call generates corresponding CDRs irrelevant with SS, recording the operation result and start date. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
Page 56 of 146
CONFIDENTIAL
In a successful call, if called mobile subscriber subscribes to CAMEL (containing T-CSI), called GMSC must generate bills for called party about IN calls. The bills contain the time to query HLR. If GMSC and TMSC are integrated, called bills are also generated. Implemented node: GMSC Serve Network: GSM and UMTS
WMFD-100112 Function name: IN subscriber Free Call Description: Premises: IN subscribers trigger IN procedure at SSP and SSP reports IDP to SCP. Operators can decide whether to allow and connect Free Call through based on exceptions if exceptions occur in the following cases: SSP or SCP is establishing conversation. Or SSP/SCP has established conversation. And Free Call bills of IN subscribers must be generated. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-100113 Function name: Mobile location request (MT/MO/NI-LR) Description: For location request terminated at MS or originated by MS, MSC serving MS generates location bills (bill of called or calling location). For location request originated by mobile network (such as location requests of emergency calls), corresponding MSC generates charging location bills (originated by network). Location bills record location information, such as approaches, time, and results. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-100114 Function name: Common equipment usage record Description: MSC embedded with common equipment (such as conference call equipment) or connected with common equipment must generate corresponding charging bills for common equipment usage. Charging bills contain the following information: Common equipment type. MSC number.
Page 57 of 146
CONFIDENTIAL
IMSI. MSISDN. Time to use equipment and total duration for usage. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-100115 Function name: Multi-PLMN handover record Description: When calls originated by mobile subscribers are handed over between two PLMNs, 2PLMN handover bills can be generated according to data configuration to record handover time and location information before and after handover. During frequent handover, you can control impact of frequent bills on MSC Server through data configuration. That is, when interval between two handovers is less than configured interval, 2PLMN handover bills are not generated and alarm information is sent. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-100116 Function name: Unsuccessful call attempt record Description: Bills are provided for some unsuccessful call attempts occupying partial network resources. In the following cases, a call attempt bill is generated: If calls are incoming route calls, outgoing route calls or tandem calls and these calls are not connected through. Incoming or outgoing routes occupied by calls are set to generate call attempt bills. Type of call attempt bills are still incoming GMSC bills, outgoing GMSC bills or tandem bills. However, release cause is unsuccessfulCallAttempt, which indicates unsuccessful call attempts. Call attempt bills indicate resources occupied by an unsuccessful call attempt. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-100200 Function name: Setting of chargeable event (time of call set-up) Description:
Page 58 of 146
CONFIDENTIAL
Set beginning time of charging: from ringing; and from answer. The default beginning time is from answer. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-100300 Function name: Setting of chargeable event (duration of the long call) Description: To avoid losses of operators due to long-time CDRs, an intermediate bill is generated for calls that exceed certain duration after certain duration. Duration for generating intermediate bills can be set according to subscriber requirements to 5, 10, 20, 30, 40, 60, and 120 minutes. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-100400 Function name: Charging of supplementary services Description: With this function, CDR related to supplementary services indicates information and flags of supplementary services, including usage information of supplementary or value-added services, such as CH, CW, MPTY, AOC, eMLPP, and CUG to facilitate operators implementing flexible charging strategies. Different from supplementary service bills, this charging bill is not only a bill. All information is recorded in related and aforesaid bills and an event bill can be generated specially. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-100500 Function name: Call restriction due to full bill pool Description: When bill poor of device are full, you can configure this function to restrict connection of new calls. Full bill poor are resulted by faulty communication of devices. In this case, if calls are connected continuously, CDRs are lost. Calls can be unrestricted through data configuration. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-100600 Function name: Call restriction duo to duration of the long call
Page 59 of 146
CONFIDENTIAL
Description: Restrict maximum conversation duration through data configuration to avoid address anti-spoofing and unconscious long-time conversation due to certain subscriber causes. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-100700 Function name: Hot Billing Description: After the original bill is generated and sent to the iGWB, the iGWB will allocate one single channel to store the final bill and send them to the billing center at real time to realize the billing for the subscriber. Implemented node: VMSC/VLR, GMSC, TMSC Serve Network: GSM, UMTS For operators Can implement some real time billing service based on the hotbilling service,e.g., telephone renting service. For subscribers can receive generally real time billing sheet, and enjoy some real time billing service. Requirements for peripheral network entities Require billing centers support.
WMFD-100800 Function name: Advice of Charge Charging/Information (AOCI/AOCC) Description: AOCI: This service provides real-time display of charge. After subscribers register AOCI services, network side delivers rate information and MS calculates charge automatically. Subscribers can display charge through menu and accumulate charge. Bill charges of AOCI services are settled at network side. Mobile subscribers only obtain charging information of this call. AOCC: Bill charges of AOCC services are settled at terminal MS. MSC is responsible for delivering rate information. Coordination of terminal MS supporting Phase2 standard and a special SIM card is required. AOCC is a simple mode to realize prepaid services. Implemented node: VMSC/VLR Serve Network: GSM, and UMTS Service benefit: For operators -
Page 60 of 146
CONFIDENTIAL
Enhance service function and implement advice of charging information and simple pre-paid charging, namely real-time charging in MS. For subscribers After adopting AOCI and leasing their own MSs to others, subscribers can charge the other party based on displayed charges. With AOCC, subscribers can buy local temporary card in the case of roaming to avoid premium roaming rate. The local temporary card features the following: One-off usage. No network access fees. No number fees. Un-rechargeable. Charged at MS side. No balance information of UE at network side. Requirements for peripheral network entities Require terminal support.
WMFD-101000 Function name: Charging of tone resources Description: When a tone is played and the number is collected in the IN service, the charging principles at the end office can be determined according to: Tone-play equipment: End office or independent IP These kinds of tone-play process can be realized: Play tone only, play tone after collecting number, collect number after playing tone, connect after playing tone, and connect after collecting number and playing tone. After specifying the IN resource charging principles, operators can provide paid IN resource service for subscribers. Because the independent IP supports the end office to charge the IN resource according to the tone ID, free tone play and number collection services can also be provided for some cases such as when a special service number is dialed. In a word, operators can determine whether to charge a certain type of resource service in a flexible manner. Implemented node: VMSC/VLR Served network: GSM or UMTS Service benefit: For operators Determine whether to charge a certain type of resource service in a flexible manner. For subscribers Requirements for peripheral network entities: None
Page 61 of 146
CONFIDENTIAL
WMFD-101100 Function name: ISDN CDR Description: PRA subscribers can be accessed to the MSC through the PRA trunk group, serving as ISDN subscribers to originate services. At the end of the call service of ISDN subscribers, it is required to provide the ISDN subscriber CDR instead of the gateway CDR. The generation of the ISDN CDR depends on the type of the outgoing and incoming trunk groups. If the type of the incoming trunk group is PRA, a software parameter is adopted to control whether to generate CDRs for the calling ISDN subscribers. If the type of the outgoing trunk group is PRA, a software parameter is adopted to control whether to generate CDRs for the called ISDN subscribers. Implemented node: VMSC Served network: GSM and UMTS Service benefit: For operators The services are enriched by implementing ISDN CDR. For subscribers Requirements for peripheral network entities
WMFD-101200 Function name: Cell-based charging Description: ZC is subscripted in HLR, and in MSC SERVER ZC list is configured. In the ZC list, Region service typeCell number, rate level and TC rate code are contained. As MS start
up the service, MSC SERVER will check if the area of the MS is configured with the ZC, and record the TC code in the BILL according to the rate information corresponding the ZC. At the same time, an USSD is sent to the MS to inform that it is in the favorable CELL. Implemented node: VMSC Served network: GSM and UMTS Service benefit: For operators The Service provider can deploy service more flexibility. For subscribers
Page 62 of 146
CONFIDENTIAL
The users can select different services. Requirements for peripheral network entities HLR needs support the service.
WMFD-110100 Function name: MAP protocol(C, D, E, G interface) Description: System can provide MAP protocol of C/D/E/G interface and its functions. MAP protocol supports the following four bearer modes to satisfy different networking requirements. Generally, the first mode is applied as basic bearer mode. Four bearer modes are as follows: WMFD-110101 WMFD-110102 WMFD-110103 WMFD-110104 MTP2/MTP3/SCCP/TCAP/MAP ATM/SAAL/MTP3B/SCCP/TCAP/MAP IP/SCTP/M3UA/SCCP/TCAP/MAP IP/SCTP/M2UA/MTP3/SCCP/TCAP/MAP
Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS
WMFD-110200 Function name: CAP protocol (L interface) Description: System can provide CAP protocol and functions of L interface. Similar CAP protocol supports the following four bearer modes to satisfy different networking requirements. Generally, the first mode is applied as basic bearer mode. Four bearer modes are as follows: WMFD-110201 WMFD-110203 WMFD-110204 MTP2/MTP3/SCCP/TCAP/CAP IP/SCTP/M3UA/SCCP/TCAP/CAP IP/SCTP/M2UA/MTP3/SCCP/TCAP/CAP
Page 63 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-110300 Function name: ISUP protocol Description: System can provide ISUP interface protocol and its functions. The following four bearer modes are supported to satisfy different networking requirements. Generally, the first mode is used as basic bearer mode. Four bearer modes are as follows: WMFD-110301 WMFD-110303 WMFD-110304 MTP2/MTP3/ISUP IP/SCTP/M3UA/ISUP IP/SCTP/M2UA/MTP3/ISUP
Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-110400 Function name: TUP protocol Description: Support interworking with other devices through TUP protocol. TUP protocol conforms to the following: TUP signaling regulations (Q.721-Q.725) of ITU-T 89, ITU-T 93, and ITU-T 97. Thailand requirements. TeleBras 210.110.724 (Brazil Telecommunication) ETR 256 (suggestions of TUP brought forth by Europe Telecommunication Organization are called TUP+). The following four bearer modes are supported to satisfy different networking requirements. Generally, the first mode is applied as basic bearer mode. Four bearer modes are as follows: WMFD-110401 WMFD-110403 WMFD-110404 MTP2/MTP3/TUP IP/SCTP/M3UA/TUP IP/SCTP/M2UA/MTP3/TUP
Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Improve networking flexibility. For subscribers -
Page 64 of 146
CONFIDENTIAL
None Requirements for peripheral network entities Devices of the other party must support TUP signaling.
WMFD-110500 Function name: R2 signaling Description: MSOFTX3000 supports R2 signaling. As a feature of the separated structure of R4 system, MGW processes channel associated signaling, transforms R2 signaling messages, and transmits them to MSC Server for processing. For example: In GMSC of mobile core network, R2 signaling can be used to connect enterprise PBX. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Network flexibly. For subscribers None Requirements for peripheral network entities Devices of the other party must support R2 signaling.
Specification:
It complies with ITU-T 1902 series specifications and 3GPP 23.205.Description: Bearer Independent Call Control Protocol (BICC) is the signaling protocol based on ISUP. System can provide BICC interface protocol and its functions. The BICC refers to call control independent of the bearer. In 3GPP, the BICC indicates the protocol defined on the Nc interface between the MSC Servers. It controls calls between the MSC Servers. The call setup process of the BICC varies according to the specific bearer type (IP or ATM) on the Nb interface. The BICC call setup process of the current MSOFTX3000 only supports the case that the Nb interface adopts the IP bearer type, including forward delay setup mode, forward quick setup mode , and backward delay setup mode. In addition, the MSOFTX3000 also supports the functions negotiated by encoding and decoding during call setup. For lower-layer signaling bearer of the BICC, the following three bearer modes are supported to meet different networking requirements.
Page 65 of 146
CONFIDENTIAL
Support ISN, GSN, TSN and CMN. Support the TrFO function. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Improve networking flexibility. For subscribers None Requirements for peripheral network entities Devices of the other party must support BICC protocol.
WMFD-110800 Function name: PRA interface Description: MSOFTX3000 supports PRA interface. For the R4 separated architecture, MGW transforms signaling messages of PRA interface and transmits them to MSC Server for processing through standard IUA protocol. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Improve networking flexibility. For subscribers None Requirements for peripheral network entities Devices of the other party must support PRA interface.
Page 66 of 146
CONFIDENTIAL
As a media gateway control protocol between soft switching device and MG, H.248 protocol is also called Megaco protocol. System can provide H.248 protocol and its functions. H.248 message is over SCTP/IP. WMFD-110901 H.248 extended by 3GPP Support extended H.248 protocol defined by UMTS WMFD-110902 IP/SCTP/H.248 Basic bearer mode and others are optional. WMFD-110906 H.248 protocol Binary code transmission of messages. An encoding mode conforming to UMTS standard. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-111000 Function name: BSSAP protocol (A interface) Description: System supports BSSAP signaling (ETSI 08.08) used in GSM and system functions related to A interface. The following three bearer modes are supported to satisfy different networking requirements. Generally, the first mode is the basic bearer mode. WMFD-111001 WMFD-111003 MTP2/MTP3/SCCP/BSSAP IP/SCTP/M2UA/MTP3/SCCP/BSSAP
WMFD-111100 Function name: RANAP protocol (Iu interface) Description: System supports RANAP signaling (3GPP 25.41X ) used by UMTS as well as system functions related to lu interface. The following three bearer modes are supported to satisfy different networking requirements. Generally, the first mode is the basic bearer mode. WMFD-111101 WMFD-111102 ATM/SAAL/MTP3B/SCCP/RANAP IP/SCTP/M3UA/SCCP/RANAP
Page 67 of 146
CONFIDENTIAL
Description: SGSN association management If Gs interface is configured between MSC and SGSN, association management can be implemented between local MSC and related SGSN. For example, record SGSN and Gs connection status of subscribers. Gs interface paging Premises: GPRS attaches GPRS and/or MSC in CS in A or B modes. If local MSC finds that subscriber Gs connection exists, SGSN is required to page subscribers through Gs interface and existing lu-PS wireless connection when CS pages subscribers. Correspondingly, subscriber paging establishes connection from lu-CS and feeds back to MSC. With this mechanism, new paging connection at wireless interface is saved. Associated location update of Gs interface GPRS subscribers can originate location update of routing area (RA) in PS and location area (LA) in CS. After location of RA in PS is updated, SGSN notifies VLRF or subscribers to update location through Gs interface. Alert of Gs interface MSC can require SGSN to report activities of subscribers through Gs interface, such as subscriber routing area update. The following three bearer modes are supported to satisfy different networking requirements. Generally, the first mode is the basic bearer mode. WMFD-111201 MTP2/MTP3/SCCP/BSSAP+ WMFD-111203 IP/SCTP/M2UA/MTP3/SCCP/BSSAP+ Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators With association location update of Gs interface, RA of subscribers in PS is guaranteed. Location update of SGSN and VLR depends on changes in location area of CS. Therefore, called subscribers can be paged correctly to avoid disconnection with subscribers in the case of in-service GPRS service. Appeals of GPRS services are enhanced. For subscribers Ensure subscribers to enjoy GPRS services and speech call services and important speech incoming calls are not lost. Requirements for peripheral network entities Cooperate with SGSN.
Page 68 of 146
CONFIDENTIAL
Connect with GMLC device through Lg interface and provide diversified location services. For example, Mobile terminated call location services: External devices can locate a mobile terminal. Mobile originated call location services: Mobile terminal originates location requirements voluntarily. Emergency call location services: In the case of emergency call, network side can locate subscribers. Subscriber privacy protection: In response to subscriber privacy, restrict requestor of location. Deferred location request with UE available event. Implemented node: VMSC/VLR Serve Network: UMTS Service benefit: For operators On the basis of location function provided by MSC, rich and colorful services related to locations are delivered in combination with network elements (NE) (such as SCP) that provides services. For subscribers Gain the profits from all location services. For example, Query location of subscriber itself. Query location of the other party. Locate emergency calls. Extend welcome and service introductions based on location. Requirements for peripheral network entities Cooperate with GMLC devices.
WMFD-111400 Function name: Check IMEI (MAP-F interface) Description: Support standard procedure of normative Check IMEI. Implement the following: Multiplex IMEI used by CHECK IMEI, namely originating OBTAIN IMEI periodically. You can set OBTAIN IMEI once to implement multiple CHECK IMEI operations. The usage times can be set from 0 through 255. Originate CHECK IMEI based on subscribers. If the result of CHECK IMEI shows that this subscriber is unknown, you can control whether to allow subscriber access based on subscriber IMSI. Therefore, MSC does not originate CHECK IMEI REQ to EIR is implemented. CHECK IMEI also implements the following enhanced functions:
Page 69 of 146
CONFIDENTIAL
Whether to allow subscriber access when EIR is not reachable. Whether to play announcement to subscribers in grey list. Whether to continue calls after announcement. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Prohibit invalid terminal accessing network. For subscribers You can select this service to prevent embezzlement of lost MS. Requirements for peripheral network entities None WMFD-111400 Function name: CHECK IMEI and F interface Specification: It complies with the 3GPP TS29.002 protocol. Implemented NE: VMSC/VLR Served network: GSM and UMTS Brief introduction: Support standard procedure of normative Check IMEI. Enhanced functions: IMEI multiplexing: According to the set multiplexing times, it is required to perform multiple CHECK IMEI operations on the obtained subscriber IMEI without getting the IMEI from the subscriber each time. CHECK IMEI based on the IMSI number segment: You can adopt the IMSI number segment to classify user groups on which CHECK IMEI needs to be performed. Controlling access of unknown subscribers based on the IMSI number segment: When the result of CHECK IMEI shows that a subscriber is unknown, you can adopt the IMSI number segment to classify the user groups to which the subscriber can be accessed and cannot be accessed. Accessing subscribers when the EIR is unreachable: You can control whether to access the subscriber when the EIR is unreachable. Announcement and connection of subscribers in the grey list: You can configure whether to play announcements to subscribers in the grey list and whether to access them after announcement according to the result of CHECK IMEI. Containing subscriber IMSI and MSISDN during the CHECK IMEI operation: When the CHECK IMEI message is needed to transfer subscriber parameters, the relevant message during the CHECK IMEI operation can contain subscriber IMSI and MISIDN. Description:
Page 70 of 146
CONFIDENTIAL
Support standard procedure of normative Check IMEI. Implement the following: Multiplex IMEI used by CHECK IMEI, namely originating OBTAIN IMEI periodically. You can set OBTAIN IMEI once to implement multiple CHECK IMEI operations. The usage times can be set from 0 through 255. Send the CHECK IMEI message based on subscriber IMSI. If the result of CHECK IMEI shows that this subscriber is unknown, you can control whether to allow subscriber to access based on subscriber IMSI. Therefore, The MSC does not send the CHECK IMEI REQ message to the EIR is implemented. CHECK IMEI also implements the following enhanced functions: Whether to allow subscriber to access when the EIR is unreachable. Whether to play announcement to subscribers in the grey list and whether to continue calls after announcement. During CHECK IMEI, the MAP_OPEN_REQ and MAP_CHECK_IMEI_REQ messages can contain the IMSI and MSISDN of the subscriber. Since the function focuses on parameter transfer instead of CHECK IMEI, you can set the time of waiting for the EIR to respond to 1s and connect the service after the time. Service benefit: For operators Prevent invalid terminal from accessing the network. For subscribers You can select this service to prevent embezzlement of lost MS. Requirements for peripheral network entities: When the enhanced function of carrying subscriber parameters is enabled, the receiving entity of the CHECK IMEI message must be able to correctly obtain parameters from the message.
WMFD-111500 Function name: MAP Policing Description: MAP Policing is defined as follows: After a designated network entity (or a group of designated network entities) originates a MAP dialogue request, the MAP carries out operation screening function according to the operation request class information upon the receipt of the first MAP service request. The designated network entity uses the address group for identification purpose. The format of the address could be GT or OPC. The operation request class information consists of the MAP operation code, indicated MAP version upon the setup of MAP dialogue, and the SSN in the local end address. You can use commands to configure the designated network entity and the MAP operation class to be screened.
Page 71 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR or GMSC Served network: GSM or UMTS Service benefit: For operators Screen the incoming messages that are not expected by the local office to realize the self-protection and avoid the full consumption of resource. For subscribers None Requirements for peripheral network entities: None
WMFD-111600 Function name: SCCP Policing Description: The function is controlled by LICENSE. When different networks or operators are interconnected, to avoid spreading authority override messages on the signaling network and ensure the security of the signaling network, SCCP policing function is required. The following combinations are available to implement the SCCP policing: Calling address DPCSSN screening Calling address GTSSN screening Calling address GTT screening Called address DPCSSN screening Called address GTT screening Called address GTSSN screening Calling address DPCSSN + Called address DPCSSN screening Calling address DPCSSN + Called address GTSSN screening Calling address DPCSSN + Called address GTSSN screening + Called address GTT screening Calling address DPCSSN + Called address GTT screening Calling address GTSSN + Called address DPCSSN screening Calling address GTSSN + Called address GTSSN screening Calling address GTSSN + Calling address GTT screening Calling address GTSSN + Called address GTSSN + Called address GTT screening Calling address GTSSN + Calling address GTT + Called address GTT screening Calling address GTSSN + Calling address GTT + Called address DPCSSN screening Calling address GTSSN + Calling address GTT + Called address GTSSN screening Calling address GTSSN + Calling address GTT + Called address GTSSN screening + Called address GTT screening
Page 72 of 146
CONFIDENTIAL
Calling address GTSSN + Called address GTT screening Calling address GTT + Called address DPCSSN screening Calling address GTT + Called address GTSSN screening Calling address GTT + Called address GTSSN screening + Called address GTT screening Calling address GTT + Called address GTT screening Called address GTSSN + Called address GTT screening Implemented node: VMSC or GMSC Served network: GSM or UMTS Service benefit: For operators Enhance the security of signaling network. For subscribers Requirements for peripheral network entities: None
WMFD-111700 Function name: MAP phase2+ Description: MAP 2+ is also called as MAP phase 3. It is the extension and enhancement to MAP protocol in order to fulfill the requirement of more supplementary service and teleservice. MAP phase2+ fully support CAMEL service, including CAMEL phase1, CAMEL phase2 and CAMEL phase3, no matter speech call and data call. MAP phase2+ also support LCS (Location Service). Implemented node: VMSC/VLR Served network: GSM or UMTS Service benefit: For operator Provide more value added service. For subscribers None Requirements for peripheral network entities: None
Page 73 of 146
CONFIDENTIAL
Description: AC version flexible control refers to the control over the dialogue originated by the local office to the designated network entity. It is one of the functions of AC version and a method of manual control of AC function. Through manual configuration, AC version is originated for the dialogue of the designated network entity. In this way, the message generated due to the version negotiation can be reduced. Before the local office originates a dialogue request, if this function is enabled, the destination address and AC name are used to search the table to obtain the configured MAP version. If the searching is successful, the searched MAP version is used to originate the dialogue. Otherwise, the latest version supported by the local office is used instead. Implemented node: VMSC/VLR Served network: GSM or UMTS Service benefit: For operator Control the AC version when the local office originates a dialogue to the designated network entity. For subscribers None Requirements for peripheral network entities: None
Page 74 of 146
CONFIDENTIAL
This function refers to traffic measurement, including measurement by links, office direction, type, and success/failure. Traffic measurement facilitates monitoring system running and optimizing network. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-120300 Function name: Alarm management Description: System provides alarm output signal and reports exceptional information during system running. Alarm can be outputted to alarm maintenance terminal and alarm box. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-120400 Function name: Configuration management Description: This function provides one operation, that is, configure office data through executing MML command, including number analysis, route, signaling, service function, and roaming restrictions. All configuration commands can be saved in host and BAM. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-120500 Function name: Device management Description: Include system hardware and software management and management related to devices. For example, Provide operation and maintenance function of board reset, switchover and loading. Enable software patch loading, activation, and deactivation. Provide running logs to record exception during daily running to facilitate obtaining more detailed information in the case of failure occurrence. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
Page 75 of 146
CONFIDENTIAL
Description: Include subscriber state tracing, interface signaling tracing, and interface message tracing for designated subscribers. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-120602 Function name: Interface or signaling tracing Description: Trace signaling of ISUP/TUP/BICC, SCCP, MTP, A, lu, MAP, and CAP interfaces and save tracing results in text files. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Trace all information transmitted from a certain interface to facilitate locating information protocol conformity in the case of equipment interconnection or faulty interface. For subscribers None Requirements for peripheral network entities None
WMFD-120603 Function name: Interface message tracing for designated subscriber Description: Trace signaling of one or some interfaces of designated subscriber. Provide in-service explanation of traced signaling information and save them in file form. The traced subscriber can be identified by IMSI, IMEI,MSISDN or PSTN number. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Facilitate locating causes when services of certain subscribers and network are exceptional. For subscribers None
Page 76 of 146
CONFIDENTIAL
WMFD-121000 Function name: Remote dialing maintenance Description: Support remote dialing maintenance. Control and manage remote access subscribers through remote maintenance. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Authorized maintenance personnel can perform dial access and remote maintenance for device to facilitate device maintenance. For subscribers None Requirements for peripheral network entities None
WMFD-121100 Function name: Testing of a designated circuit Description: In the MSOFTX3000, this function is primarily used for the availability test of the intermediate MGW and physical paths such as A-interface circuit and trunk circuit without blocking the paths or circuits. The test aims to find out problems such as monologue and loopback. This function is especially useful in testing the in-service equipment and in troubleshooting. The result of the trunk dialing test is printed in the trunk tracing window and can be saved as a file. The result of the trunk dialing test includes: test time, tested resource type, resource of the current test (such as the circuit No.), and test result. The test result covers: Success and Failure. In the case of test failure, output the specific reasons, including: Circuit invalid: The circuit is unavailable, including the following cases that the circuit is uninstalled, faulty or blocked. Circuit busy: The circuit under dialing test is found busy during routing. Circuit cycle: The circuit under dialing test is looped back by MGW. Circuit communication exceptional: Communication exception occurs to the tested trunk due to problems of the cross-connected lines or transmission. The cause value is invalid during manual test. During manual test, the testing personnel judges whether communication exception occurs to the tested circuit. Interwork Failure: The tested call fails due to call release by the opposite office.
Page 77 of 146
CONFIDENTIAL
Internal Failure: The tested call fails due to internal processing error of the local MSC. The trunk dialing test is classified into: Designated dialing test: The subscriber dials the same called number each time in a test task. The MSC Server selects the corresponding circuit to test according to the data configured in the Trunk Test Task table. Automatic dialing test: The subscriber triggers the corresponding automatic dialing test task by opening the trunk tracing window. After an automatic dialing test task is triggered, the MSC Server constructs a calling subscriber and a called subscriber to complete call connection according to the data configured in the Trunk Test Task Table. The corresponding circuit is selected each time. After a circuit is tested, the MSC Server automatically tests the next circuit according to the data configuration until the entire test task is complete. The designated dialing test includes: Testing of designated called A-interface circuit Testing of designated calling A-interface circuit Testing of designated trunk circuit. This function is applicable to the case of trunk outgoing, but not to the case of trunk incoming or local office calls. Testing of designated intermediate MGW. This function can designate a timeslot for an E1 between MGWs. The automatic dialing test includes: Testing of automatic trunk circuit. Only the trunk outgoing case is supported. Implemented node: VMSC Served network: GSM or UMTS Service benefit: For operators Detect problems such as monologue and loopback, master circuit status to ensure smoothness of the circuit, and reduce the maintenance cost. For subscribers Requirements for peripheral network entities: None.
WMFD-121200 Function name: Server security customized function Description: The customized tool is used to block the unused service/ports in the servers such as BAM server, emergency server and iGWB. This is useful to protect the system from attacks and virus spreading by means of operating system weak points. Implemented node: VMSC,GMSC,TMSC Served network: GSM or UMTS
Page 78 of 146
CONFIDENTIAL
Service benefit: For operators Improve the system robustness and keep the system away from virus attack. For subscribers Not visible. Requirements for peripheral network entities: None.
WMFD-121300 Function name: Server System Patron Description: The system patron is a tool to check the validity of application and service. Only the checked application and Dynamic Link Library file can be executed to ensure the system safety. The service should be registered in the system patron tool before running. Implemented node: VMSC,GMSC,TMSC Served network: GSM or UMTS Service benefit: For operators Only the carefully tested program can work on the server, which protect the system safety. For subscribers Not visible. Requirements for peripheral network entities: None.
WMFD-121400 Function name: Work station virus protection Description: To ensure the work station avoid of virus attack by centralize deploying the virus protection tools. Note: The server has the System Patron tools to ensure the safety, which has no need for virus protection tools. Implemented node: VMSC,GMSC,TMSC Served network: GSM or UMTS Service benefit: For operators -
Page 79 of 146
CONFIDENTIAL
Protect the maintenance terminals from virus attack. For subscribers Not visible. Requirements for peripheral network entities: None.
WMFD-121600 Function name: Malicious SMS warning Description: The charging mode of the SM origination service for Prepaid Service (PPS) subscribers of China Mobile fails to satisfy the requirement for some subscribers to send abundant SM advertisements within a short time using the dedicated equipment. The sending mode of SM advertisements originated from the dedicated equipment causes great interference on network running. Therefore, it is required to discriminate these malicious SMs through warning so that the operator can take corresponding measures. The function generates warning for all malicious SM subscribers, without distinguishing prepaid service subscribers and postpaid service subscribers. Within the statistical time period, the system only sends the warning to each malicious MS subscriber once to avoid frequent warning. In the MSOFTX3000, the subscriber can discriminate possible malicious SM subscribers by configuring the threshold of SMs originated by a subscriber within a time period. That is, within the statistical time period, if the number of SMs sent by a subscriber exceeds the threshold, the MSOFTX3000 reports warning. Implemented node: VMSC or VLR Served network: GSM and UMTS Service benefit: For operators Get the list of malicious SM subscribers and avoid further losses by taking corresponding measures. For subscribers Requirements for peripheral network entities: None
WMFD-121700 Function name: Union trace Description: The function supports mobile NEs to trace local HLR-based subscribers. That is, the subscriber tracing task can be created and deleted in the HLR. The HLR notifies the current MSC or VLR where the current subscriber is located to trace. The MSC generates changes each time (including location update, power-on or power-off, call origination and termination, and SM origination and termination) of the traced subscriber as a tracing file
Page 80 of 146
CONFIDENTIAL
and saves it in the background host. If required in the future, the maintenance personnel can use the file to locate problems. Implemented node: VMSC/VLR Served network: GSM Service benefit: For operators Joint subscriber tracing is effective to remove designated faults, especially in handing subscriber complaints. For subscribers None Requirements for peripheral network entities: HLR needs to support joint subscriber tracing.
WMFD-121800 Function name: Unicom CORBA Specification: None Implemented node: VMSC/VLR, GMSC and TMSC Served network: GSM and UMTS Target market/customer: China Unicom Brief introduction: The feature configuration parameters developed primarily aim to meet the requirements in Technical Specifications on GSM Network Management System constituted by China Unicom, as well as the requirements for the protocol, interface and interactive content between the MSC Server and gateway center. Description: The function improves configuration data exchange with the M2000 network management center from the following aspects: MSC configuration data: includes the MSC type, maximum subscriber numbers, BHCA value configured by the switch actually running in the existing network, and the voice BHCA value Circuit configuration data: includes the circuit numbers configured by the switch, maximum circuit numbers currently configured in the trunk group, trunk group type, and opposite office type End point of the signaling link set: direction of the link set End point of the signaling link: link type, signaling link status, and signaling link rate Service benefit: For operators
Page 81 of 146
CONFIDENTIAL
Better meet operators requirement for NMS maintenance, learn parameter configuration and capability capacity of the MSC in details, and facilitate the NMS to perform centralized maintenance by adding these configuration parameters. For subscribers End subscribers are unrelated. Requirements for peripheral network entities: The M2000 needs to support new configuration parameter interfaces.
WMFD-122000 Function name: Patch auto check and load Description: Periodically detect whether patch status of boards of the same type changes in the Patch Status table. If the patch status and the patch numbers are inconsistent due to subscribers operation on the patches, it is required to report the alarm information to notify the subscriber to solve it in time. According to the requirements of the operator, the system can automatically detect the patch situation of boards of the same type when new modules and boards are added. In the running state, if the number of patches for the boards of the same type is the same, the system automatically loads patches within the expanded module to ensure that the patches can be installed in time. Implemented node: MSC Served network: GSM and UMTS Service Benefit: For operators Ensure that all patches are installed during expansion. In addition, notify the subscriber in time to solve patch inconsistency if any. For subscribers None Requirements for peripheral network entities: None
WMFD-122300 Function name: Centralized right management Description: A centralized management information database is necessary to avoid replication of subscriber information and to synchronize the information through database replication. To realize this objective, the M2000 manages the information of the user account in a unified manner. After the M2000 creates a user account and allocates the rights to it, the subscriber can log in to the management NE through the M2000 Client or directly through the LMT to perform relevant operations.
Page 82 of 146
CONFIDENTIAL
Implemented node: VMSC/VLR, GMSC and TMSC Served network: GSM and UMTS Service benefit: For operators Realize centralized management of the password and policy through centralized subscriber management by the NMS. Realize centralized status authentication and authorization through centralized subscriber management by the NMS. Realize centralized log auditing and analysis through centralized subscriber management and dynamic NE subscriber monitoring by the NMS. For subscribers None Requirements for peripheral network entities: Centralization in this feature indicates management within the M2000 subnet and no application products of other manufacturers are involved. In addition, the feature focuses on account information management, centralized authentication, and centralized authorization.
WMFD-130100 Function name: Percentage and random based routing Description: Define different percentages for different sub-routes and perform load sharing based on different percentages. You can configure random trunk circuits in the same trunk group. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Set load proportion between different sub-routes flexibly. For subscribers End subscribers are unrelated.
Page 83 of 146
CONFIDENTIAL
WMFD-130200 Function name: Caller and callee MSISDN based routing Description: Implement routing based on caller and callee MSISDN number segment. Process is as follows: Configure to-be-processed MSISDN to a special one. Implement routing instead of entering procedure of obtaining roaming number. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators It can be used to trigger services related to MSISDN number segment, such as IN service outgoing in OVERLAY mode. For subscribers End subscribers are unrelated. Requirements for peripheral network entities None
WMFD-130300 Function name: Caller IMSI based routing Description: Implement routing according to calling IMSI. IMSI number segment is added to judge routing. Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS Service benefit: For operators It can be used to trigger services related to IMSI. For example, in the case of dialing international toll, subscribers of local network and other networks are distinguished based on calling IMSI to select different GMSC for outgoing calls. For subscribers Subscribers of different types can enjoy different services. Requirements for peripheral network entities -
Page 84 of 146
CONFIDENTIAL
None
WMFD-130400 Function name: Location area and cell based routing Description: Implement routing according to cell where calling party is located. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
Service benefit: For operators Enable subscribers to access proximate special service center (such as 110) and provide other services related to location. For subscribers Enjoy service proximately and fast. Requirements for peripheral network entities None
WMFD-130500 Function name: Services type (toll/local) based routing Description: Implement routing based on service types (international toll, national toll, and local calls). Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Provide different services for different subscriber types to improve toll call completion rate For subscribers Subscribers are unrelated. Requirements for peripheral network entities None
Page 85 of 146
CONFIDENTIAL
Description: Implement routing based on subscriber types (common subscriber, preferential subscriber, operator, data, and test) in MISUP/TUP signaling. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Provide different services for different subscriber types to improve call completion rate of subscribers with high priority. For subscribers Subscribers are unrelated. Requirements for peripheral network entities None
WMFD-130700 Function name: Time based routing Description: Implement routing based on time (week, and time period). Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Set different route strategies at different time periods. For subscribers Subscribers are unrelated. Requirements for peripheral network entities None
WMFD-130800 Function name: Transmission capability based routing Description: Implement routing based on bearer capability (speech, video, and data). Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
Page 86 of 146
CONFIDENTIAL
Service benefit: For operators Provide different routing strategies for different bearer capabilities. For subscribers Subscribers are unrelated. Requirements for peripheral network entities None
WMFD-130900 Function name: Call type (CFB/CFU/CFNRY/CFNRC/Normal) based routing Description: Implement routing based on call types (CFB/CFU/CFNRY/CFNRC/Normal). Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS Service benefit: For operators Provide various routing strategies for call forwarding and common calls. For subscribers Subscribers are unrelated. Requirements for peripheral network entities None
WMFD-131000 Function name: Length of MSISDN based routing Description: Select different routes for numbers with same prefixes and different lengths. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Facilitate increasing digit of number and processing special short number. For subscribers Subscribers are unrelated.
Page 87 of 146
CONFIDENTIAL
WMFD-131100 Function name: Automatic routing of incomplete call Description: According to failure causes, route un-completed call to a preset number, such as voice mailbox. Implemented node: VMSC/VLR, and GMSC Serve Network: GSM and UMTS Service benefit: For operators With this function, operators can give friendly prompt to end subscriber. Therefore, call completion rate and subscriber satisfaction are improved. For subscribers Friendly prompt instead of direct rejection is generated in the case of call failure. Requirements for peripheral network entities None
WMFD-131400 Function name: Analyze of 32 digit length MSISDN Description: Analysis and storage length of number can reach 32 digits. Meet requirements of card services required to enter long number. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Meet requirements of card services required to enter long number. Also, requirements of complicated number transform are satisfied or numbers conform to regulation requirements of customers. For subscribers Called number with 32 digits can be called. Requirements for peripheral network entities None
Page 88 of 146
CONFIDENTIAL
WMFD-131500 Function name: Multi-NDC function Description: MSISDN refers to to-be-dialed number when calling party calls a customer of PLMN. The structure of MSISDN is CC-NDC-SN. Generally, NDC contains 1 3 digits. MSOFTX3000 supports multi-NDCs to be configured in the same network. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Enable different services to use various NDCs. When number quantity is insufficient, subscriber number can be expanded through multi-NDCs. For subscribers None Requirements for peripheral network entities None WMFD-131600 Function name: Special Number Matching Specification: None Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Brief introduction: The function determines whether to trigger IN services when an IN subscriber dials the number of special services or an IN call is forwarded to the number. Description: The function is used to configure the number of special services. It also determines whether to trigger IN services when an IN subscriber dials the number or an IN call is forwarded to the number. The original number configuration adopts exact matching mode. Once there are many such numbers, you need to configure plenty of data. To reduce the volume of data to be configured, reset the number matching mode to Prefix (maximal matching) + Minimal length of number + Maximal length of number. Service benefit: For operators Reduce the volume of data to be configured and, therefore, cut down the maintenance cost. For subscribers None
Page 89 of 146
CONFIDENTIAL
Requirements for peripheral network entities The function is involved in the requirement for the MSC only. The VMSC or GMSC performs call-related signaling processing and data analysis.
WMFD-131700 Function name: Routing Based on Time Section Specification: None Implemented Node: VMSC/VLR, GMSC and TMSC Serve Network: GSM and UMTS Brief introduction: The function is used to change routing analysis number based on time section information, that is, the routing number is changed with variation of time sections. Compared with the original number change function, time section distribution processing is added. With the function, a number can be changed into different numbers at different time sections. Description: Compared with the original number change table, a number change table of time section distribution is added. To implement the function, the time section information is associated with the number change mode defined in the number change table. The time section information is expressed in a time section (unit: hour) of a day of a week (Monday, Tuesday). Service benefit: For operators The function offers more choices for number change. It can help operators provide new services related to the function. For subscribers None Requirement on auxiliary entity: None
WMFD-131800 Function name: CUG Direct Call Restriction Specification: None Implemented Node: VMSC/VLR Serve Network:
Page 90 of 146
CONFIDENTIAL
GSM and UMTS Brief introduction: The function is used to prohibit CUG subscribers without the outgoing call authority from calling PSTN subscribers in the originating office. Description: The function controls the call restriction of CUG subscribers without the outgoing call authority in the originating office. The call restriction is related to the type of numbers dialed by CUG subscribers. If the number is a CUG special service number, the system continues call proceeding and clears the CUG information. The system then considers the subscriber as the one who does not subscribe the CUG service. If the number is not a CUG special number, the system releases the call. If there is no indication for the number, the system continues call proceeding and remains the CUG information. The backward office then determines whether to restrict the call. Service benefit: For operators Based on the protocol, it is the terminating office that performs call restriction on the CUG subscriber without outgoing call authority. If the terminating office, such as the PSTN office, cannot process CUG information or perform call restriction, the originating office can perform call restriction function. For subscribers None Requirement on auxiliary entity: None WMFD-131900 Function name: Call Loop Control Description: The function covers two parts: peer-office routing restriction and call loop control. Peer-office routing restriction:
Page 91 of 146
CONFIDENTIAL
Local office
Incoming
Outgoing
If A and B are peer offices, B cannot select circuits to office direction C if C and B are judged as the peer offices during routing. If there is only the straight subroute from B to C and no other subroutes are available, however, B can also select circuits to office direction C during routing even if B and C are peer offices. Note: The straight subroute indicates the first subroute configured in [Routing Data Table]. The level relation is determined in Level of Opposite Office in [Office Direction Table]. Call loop control: Incoming calls at the trunk side are out from the trunk side after being connected. If the incoming trunk has the same office direction No. as the outgoing trunk, call barring is enabled. Call loop control aims to avoid unreasonable data configurations of the local and peer offices, and thus avoid trunk resource waste due to call loop and oscillation. Therefore, this type of looped calls is restricted. No call loop control is performed in the following cases because they are call loop caused by normal calls: call loop after the GMSC getting the roaming number, call loop after call forwarding occurs to the local office, and call loop due to re-attempt after contention occurs to the outgoing trunk. Implemented node: GMSC/TMSC Served network: GSM and UMTS Service benefit: For operators Reduce meaningless trunk resource occupation and improve equipment resource utilization. For subscribers
Page 92 of 146
CONFIDENTIAL
WMFD-140200 Function name: TDM 2M signaling link Description: Use bandwidth of one 2M E1 cable as one 2M bits/s signaling link connecting with other signaling points. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators When 2M links are applied between signaling points with large signaling flows, costs can be lowered and networking can be simplified. Additionally, if MSOFTX3000 does not support multiple signaling points, one signaling point can support up to 16 links. When sixteen 64K links cannot satisfy traffic requirement, application of 2M links can better satisfy flow requirements. For subscribers -
Page 93 of 146
CONFIDENTIAL
End subscribers are unrelated. Requirements for peripheral network entities None
WMFD-140300 Function name: Embedded STP function Description: When MSOFTX3000 works as VMSC/GMSC device and STP device, SCCP and MTP can be transferred between other signaling points. Transferred signaling can be transferred directly at MTP layer or signaling at SCCP layer translated by SCCP GT. MSOFTX3000 can also work as STP equipment medium/small-sized STP device. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators In the case of low signaling transfer flow, STP mode is also adopted so that network establishment costs are saved. For subscribers End subscribers are unrelated. Requirements for peripheral network entities None
WMFD-140500 Function name: IP bearer capability of multi-MGW Description: Core network of GSM/UMTS adopts an architecture that bearer is separated from control. MSC Server is responsible for signaling processing and call control and MGW implements connection and conversion of media stream. One MSC Server controls multiple MGWs to form a large MSC. Speech path connection between MGWs supports IP bearer. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators IP bearer improves bandwidth utilization, provides flexible networking between MGWs, and lower investment in network establishment.
Page 94 of 146
CONFIDENTIAL
For subscribers None Requirements for peripheral network entities MGW also supports IP bearer.
WMFD-140700 Function name: TDM bearer capability of multi-MGW Description: Core network of GSM/UMTS adopts an architecture that bearer is separated from control. MSC Server is responsible for signaling processing and call control and MGW implements connection and conversion of media stream. One MSC Server controls multiple MGWs to form a large MSC. Speech path connection between MGWs supports TDM bearer. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators Provide flexible networking between MGWs and protect existing investment in TDM transmission. For subscribers None Requirements for peripheral network entities MGW also supports TDM bearer.
WMFD-140800 Function name: A interface Satellite Transmission Mode Description: Support signaling at A interface to be transmitted through satellite. Therefore, networking flexibility is enhanced to satisfy requirements of remote areas or countries with many islands. Implemented node: VMSC/VLR Serve Network: GSM Service benefit: For operators Satisfy requirements of remote areas or countries with many islands. For subscribers -
Page 95 of 146
CONFIDENTIAL
WMFD-141000 Function name: Mc interface Satellite Transmission Mode Description: MSOFTX3000 can support signaling at Mc interface to be transmitted through satellite. With this feature, networking flexibility and geography adaptation of MSOFTX3000 are enhanced. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS Service benefit: For operators When MSC SERVER and MGW are far from each other, this function enables signaling at Mc interface to be transmitted through satellite. For subscribers None Requirements for peripheral network entities None
WMFD-141100 Function name: Inverse Multiplexing ATM(IMA,ATM2M) Description: MSOFTX3000 supports ATM data over E1 transmission, called Inverse Multiplexing ATM(IMA,ATM2M). Protocol stack is MTP3B/SAAL/ATM/E1, upper protocol can be MAP. Implemented node: VMSC/VLR, GMSC, TMSC Serve Network: GSM, UMTS Service benefit: For operators Reuse TDM transmission resource. For subscribers None Requirements for peripheral network entities None
Page 96 of 146
CONFIDENTIAL
WMFD-141200 Function name: T1 Digital Trunk (ISUP/PRA) Description: T1 cable is a type of cable used for the voice or data transmission and is widely used in areas such as North America. T1 cable is different from E1 cable used in other areas. The following table lists the major physical and standard difference between the T1 cable and E1 cable. Type T1 E1 Resistance 100 ohm 75 ohm or 120 ohm Available timeslots 24 32 (Timeslot 0 is unavailable) Bandwidth 1.5M 2.0M
ISUP supports the circuit management of T1 cables on the MGW. PRA supports the circuit management of T1 cables on the MGW. Implemented node: VMSC, GMSC, or TMSC Served network: GSM or UMTS Service benefit: For operator Improve the interconnection and interworking abilities of the network. For subscribers None Requirements for peripheral network entities: Equipment of the peer office supports the T1 cable transmission.
WMFD-141300 Function name: Signaling SSP (LOOPBACK) Description: In the network using ISUP for networking, if only signaling transmission but not voice transmission is needed (especially when the toll call transmission resource is not required), the signaling SSP (Loopback) function can be used to reduce the unnecessary voice transmission trunk between network entities and save the cost of network construction. For example, MSCs need to trigger the IN service through the overlaid SSP. Some MSCs are far away from the SSP. Thus, using the signaling SSP function can save the toll call transmission resource between the end office and SSP. Implemented node: SSP Served network: GSM or UMTS Service benefit: For operators -
Page 97 of 146
CONFIDENTIAL
Save the toll call transmission resource and the network construction cost. For subscribers None Requirements for peripheral network entities: Corresponding data configuration is needed on the peer MSC. Two trunk groups and the transmit/receive loopback of speech path must be configured. The CIC configuration varies with the requirement of local MSC.
WMFD-141400 Function name: Route between MGWs in one MSC Description: MGW path refers to the route between the MGW of the calling party and the MGW of the called party. The source MGW and destination MGW is managed by the same MSC Server. When there are multiple MGW paths between the source MGW and destination MGW, the route with the shortest span is generally selected. The function of selecting the route randomly, by percentage, or by turns is also supported. Implemented node: VMSC, GMSC, or TMSC Served network: GSM or UMTS Service benefit: For operators Allow more flexible networking. For subscribers Requirements for peripheral network entities: None
WMFD-141500 Function name: Connecting MGWs in one MSC by transit switch Description: In the 3GPP R4 layered architecture, an MSC Server can manage several MGWs. In the common networking mode, these MGWs are interconnected. MSOFTX3000 supports the networking mode that multiple MGWs in the same MSC are interconnected through transit switch instead of directly connected. Implemented node: VMSC/VLR, or GMSC Served network: GSM or UMTS Service benefit: For operators Allow more flexible networking.
Page 98 of 146
CONFIDENTIAL
WMFD-141600 Function name: MSC POOL Description: In the previous network structure, GSM or UMTS, an RAN node can be connected with only one CN node (a MSC or a SGSN). 3GPP introduces a new networking mode called IU-FLEX (also called MSC pool in the CS domain) in the R5 (TS 23.236). This networking mode allows on RAN node to connect with multiple CN nodes. The following figure shows the network structure of IU-FLEX:
MSC 3 MSC 2 MSC 1 MSC 6 MSC 5 MSC 4 MSC 7
CS poolarea 2
PS pool-area 1
PS pool-area 2
SGSN 1 SGSN 2
SGSN 6
In the above figure, MSC1, MSC2, and MSC3 form a pool and MSC4, MSC5, and MSC6 form another pool. Any of the RAN nodes in the pool can be connected with all MSCs in the pool and the load is shared among these MSCs. This networking mode brings the following advantages: Multiple CN nodes can share the load of an RAN to improve the utilization rate of CN nodes and meanwhile reduce the loss resulted from the error of a certain CN node.
Page 99 of 146
CONFIDENTIAL
The service area of a single CN node is expanded. The number of cross-CN node handover and the number of CN node update during roaming are reduced, which subsequently cuts down the signaling flow of the CN. Multiple operators can share their RANs. Implemented node: MSC/VLR Served network: GSM or UMTS Service benefit: For operators Realize load sharing among MSCs in a pool to enhance the security of the whole network. Expand the coverage area of a single MSC. Reduce the inter-CN signaling. Reach load balance in the CN area and make the CN expansion easier. For subscribers Enjoy services of higher quality. Requirements for peripheral network entities: Require the support of RAN node (RNC/BSC).
WMFD-141700 Function name: MGCF function Description: The MGCF is a controller that implements the interworking between the IP multimedia subsystem (IMS) and the circuit switched (CS) domain. Huawei MGCF is an entity developed based on the host software part of the MSOFTX3000 with the added function to interwork with the IMS. The hardware (rack, subrack, and boards) and software (BAM and O&M system) of the MGCF are the same as those of the MSOFTX3000. The 3GPP core network comprises two parts: CS domain and packet switched (PS) domain. The IMS is the IP multimedia subsystem put forward by the 3GPP in R5 based on the PS domain. In the trend of mobile network evolving to an all-IP network, the IMS technology develops rapidly and has been commercialized. The MGCF meets the requirement of the network evolution and realizes the interworking between the IMS and the CS. The MGCF communicates with the call session control function (CSCF) in the IMS domain and controls the connection of the media channels in the IMS-MGW. The MGCF also realizes the interworking between the SIP signaling in the IMS domain and the BICC/ISUP signaling in the CS domain. The typical networking of the MGCF is as shown in the following .Figure 1-1.
CONFIDENTIAL
CSCF Mg
MGCF
SGW
CS network
The MGCF also supports the fixed mobile combination (FMC) and provides solutions for the interworking between the mobile network and fixed network. As an independent device in networking, the MGCF provides the following three kinds of functions: Service functions: providing teleservices and supplementary services Network functions: including call control functions Operation and maintenance (O&M) functions: providing configuration management, fault management, alarm management, performance management, and security management Huawei MSC Server can be act as MGCF through software upgrade.
Huawei will provide MGCF function in CS6.0, and it can be used for test now.
Implemented node: MGCF Served network: IMS Service benefit: For operators MSC Server can be act as MGCF through software upgrade. For subscribers Requirements for peripheral network entities: None WMFD-141800 Function name: IP over E1 Specification: None Implemented node: VMSC/VLR, GMSC and TMSC
CONFIDENTIAL
Served network: GSM and UMTS Brief Introduction: During deployment of the mobile SoftSwitch market, some small operators are incapable of constructing and maintaining a large IP bearer network. Instead, they want to still use existing TDM networks after adopting the SoftSwitch technology. In this case, the IP over E1 technology is needed to meet the requirement of these operators. IP over E1 is a technology to provide transmission channels for IP packets by binding multiple timeslots/E1s. In addition, using the cRTP compression technology can further improve utilization of voice bandwidth. MSOFTX3000 supports IP over E1 bearer between gateways but does not provide interfaces for IP over E1. Instead, MSOFTX3000 still adopts the FE interface to connect the near-end switch or router. To adopt IP over E1 for the Mc/SIGTRAN interface, add the corresponding equipment that supports conversion between E1 and FE. When IP over E1 is adopted between offices, the signaling plane only supports the BICC protocol. Description: 1. MSOFTX3000 supports the Nb interface to adopt IP over E1 but does not provide the interface for IP over E1 itself. Instead, MSOFTX3000 still adopts the FE interface to connect the near-end switch or router. To adopt IP over E1 for the Mc/SIGTRAN interface, add the corresponding equipment that supports conversion between E1 and FE. Considering operation & maintenance cost, there is a competitive edge to select the transmission MSTIP equipment Metro1000 as the interface conversion equipment. The corresponding networking diagram is shown in the following figure.
LSW Metro
E1
FE Metro UMG Metro UMG Metro LAN Switch UMG Metro 1000
Same IP1
Same IP2
Same IP3
Metro1000 connects the FE interface at one end and the E1 interface at the other end. Ethernet packets are carried over E1. In terms of MSS and UMG, it is the same as FE direct connection. As the important signaling interface, Mc/SIGTRAN needs to adopt the active/standby link mode to support link switchover in such exceptions as E1 transmission
CONFIDENTIAL
interruption, near-end Metro1000 failure, LAN Switch failure, and far-end Metro1000 failure. 2. MSOFTX3000 only supports the BICC protocol on the Nc interface. It supports three bearer setup modes of the BICC, including forward quick setup, forward delay setup, and backward delay setup. BICC signaling is transited through the gateway. The private Codec is needed for the IAM message interface to transfer resources (IP address and port No.) on the bearer plane of the forward office. According to the transferred resources, the backward office allocates the corresponding resources on the bearer plane. 3. The QoS of voices carried on IP over E1 can be assured through the following methods: For inter-office calls, adopt the BICC CIC planned between offices and the IP QoS bearer quality detection function to implement flow control over inter-gateway bearer between offices. For inter-gateway calls (including intra-office and inter-office calls), adopt the VTID configured between intra-office gateways and the IP QoS bearer quality detection function to implement flow control over inter-gateway bearer within an office. Similar to TID of TDM bearer, VTID features the same maintenance mode as TID except that VTID is not delivered to the gateway or used to audit intermediate circuits with the gateway. Note: The number of BICC CICs and VTIDs depends on the bandwidth of common voice encoding and decoding (such as AMR) and total bandwidth carried between gateways. Service benefit: For operators 1. Make the best of existing TDM networks to provide the bearer network for mobile SoftSwitch, and thus protect the original investment. 2. IP over E1 can further improve utilization of voice bandwidth by adopting the cRTP compression technology. The following figure shows the procedure of cRTP compression.
IP Header Encapsulation Voice Data IP Compression Header Voice Data
PPP 8 bytes
IP
UDP
RTP
NbUP
Voice
PPP
NbUP
Voice
CRTP Compression
20 bytes 8 bytes 12 bytes 4 bytes X bytes
X bytes
With the cRTP compression technology, the original 40-byte header (including 20-byte IP header, 8-byte UDP header and 12-byte RTP header) can be compressed to a two-byte header. Take AMR 12.2k (including UP) encoding and decoding as an example, one timeslot of the original E1 can only carry one-channel conversation. After cRTP compression, one timeslot can carry four-channel conversations (VAD is disabled) or six-channel conversation (VAD is enabled). On the Nb interface, only adopting encoding and decoding compression can save transmission. G.711 encoding/decoding is not recommended. Considering voice quality, the control plane needs to support TrFO. In a 3G-to-3G scenario, the AMR encoding/decoding is required. In a 2G-to 2G scenario, you can only insert TC on the gateway since neither the Ater interface nor IP transformation of A-interface is supported. In a 3G-to-2G scenario, insert TC on the gateway of A-interface and adopt AMR coding/decoding for the Nb interface.
CONFIDENTIAL
3. The gateway supports the Nb interface directly connecting the IP over E1 port. No additional router is needed on the bearer plane. 4. The QoS of voices through IP over E1 can be assured by configuring BICC CIC between offices and VTID within an office, and by enabling the IP QoS bearer quality detection function. For subscribers None Requirements for peripheral network entities: The gateway needs to provide the interface board IOE for IP over E1.
CONFIDENTIAL
WMFD-150400 Function name: OVERLAY SSP Description: When other offices do not support CAMEL SSP function, calls can be routed to local office and IN services are triggered in local office. MSOFTX3000 features enhanced SSP functions and can be upgraded to target network fast. Meantime, MSOFTX3000 supports CSI and Overlay trigger modes. Service benefit: For operators When other MSCs even GMSCs of local network cannot upgrade to SSP, IN services can be provided fast in the case that MOSFTX3000 overlays to trigger IN services. For subscribers Enjoy IN services. Requirements for peripheral network entities None
CONFIDENTIAL
WMFD-150500 Function name: Trigger CAMEL 2 times Description: After an IN subscriber or non-IN subscriber dials the service number (for example, 800) and triggers the IN service in the O-CSI/N-CSI DP2 mode, this subscriber can also triggers the IN service in the N-CSI DP3 or DCSI mode according to the dialed special number. When this function is used, O-CSI/N-CSI DP2 connection is a steady process and is kept all the time to monitor the call and complete the service function. However, the DCSI/N-CSI DP3 connection that is set up later ends after the SCP sends the Continue/Connect message. Implemented node: VMSC/VLR Served network: GSM or UMTS Service benefit: For operator Support the PPS subscribers to trigger OCSI DP2/NCSI DP2 and access number type IN services (for example, 800 service) at the same time to fully satisfy the needs of subscribers. For subscribers PPS subscribers can also use the access number type IN services such as the 800 service. Requirements for peripheral network entities: None
WMFD-150600 Function name: Built-in CallGap Description: When the network resource is limited, especially during the peak hours such as holidays and weekends, the built-in CallGap can provide differential network service for intelligent service subscribers. The specific functions include: Provide better network service for high-end IN subscribers when the network resource is limited. The built-in CallGap can reduce the transmission rate of call requests sent to the SCF according to some service keys to realize the IN flow control function. Support the control of dial-barring number of different service keys. Restrict the calls to specified called parties according to service keys. Service benefit: For operators Set the built-in CallGap data flexibly when the traffic is in the peak to perform flow control over the IN subscribers, reduce impact of the peak traffic on the network, and meanwhile increase the satisfaction of high-end IN subscribers and non-IN subscribers. For subscribers High-end IN subscribers and common subscribers (non-IN subscribers) enjoy the access priority.
CONFIDENTIAL
Requirements for peripheral network entities: None WMFD-150700 Function name: DCH Specification: None Implemented node: VMSC/VLR and GMSC Served network: GSM and UMTS Brief introduction: Default Call Handling (DCH) refers to the mode of handling IN calls (including SMs) in the case of conversation interruption between the SCP and the SSP: releasing the call or (as the ordinary call) continuing the call. For IN calls, the SSP determines the specific call handling mode in the case of interaction exception between the SCP and SSP, according to the SCP address, service key, call type (international call, international roaming call, and so on), and acknowledgement situation. The call handling modes include: directly release the call, directly continue the call, and release or continue the call according to the DCH mode in subscriber data (OCSI/TCSI/NCSI). For IN SMs, the SSP determines the specific SM handling mode in the case of interaction exception between the SCP and the SSP, according to the SCP address and service key. The SM handling mode includes: directly terminate SM handling, directly continue SM handling, and terminate or continue SM handling according to the DCH mode in subscriber data (MO-SMS CSI/MT-SMS CSI). Description: 1. For IN calls, the SSP determines the specific call handling mode in the case of interaction exception between the SCP and the SSP, according to the SCP address, service key, call type (international call, international roaming call, and so on), and acknowledgement situation. The call handling modes include: directly release the call, directly continue the call, and release or continue the call according to the DCH mode in subscriber data (OCSI/TCSI/NCSI). 1.1. Before a call is answered, the SSP performs DCH in the following cases: After reporting IDP, the SSP receives such error messages from the SCP as MissingCustomerRecord, MissingParameter, SystemFailure, TaskRefused, UnexpectedComponentSequence, UnexpectedDataValue and UnexpectedParameter. Applying system resources failed when the SSP reports IDP. After reporting IDP, the SSP receives such messages delivered by TACP as TC_notice, TC_p_abort, TC_l_cancel, TC_continue (the application context is unmatched) and TC end (the application context is unmatched). The Tssf timer times out when the SSP is in the following three states: WaitingForInstructions, WaitingForEndOfTemporaryConnection and WaitingForEndOfUserInteraction. When the DCH occurs before an IN call is answered, continue the call. When DCH occurs after an IN call is answered, provide an ordinary CDR for the IN subscriber, containing the DCH flag (ContinueCall).
CONFIDENTIAL
1.2. After a call is answered, the SSP performs DCH in the following cases: The call is not released when the maximum call duration timer of the SSP times out. After reporting ACR, the SSP receives TC_notice, TC_p_abort and error messages (such as MissingParameter, SystemFailure, TaskRefused, UnexpectedComponentSequence, UnexpectedDataValue, UnexpectedParameter and ParameterOutOfRange) contained in the TC_continue or TC_end message from TCAP. Such messages as TC_notice, TC_p_abort and TC_u_abort are received from TCAP. When the DCH occurs after an IN call is answered, provide an IN CDR (the first CDR or intermediate CDR) for the IN subscriber if the call is continued. The start charging time refers to the time of answering the call (for the first CDR) or the end time of the previous intermediate CDR (for intermediate CDRs). The end charging time refers to the time when the DCH occurs. Fill the DCH flag (ContinueCall) in the CDR. Then provide an ordinary CDR and start to count from the time when DCH occurs. Fill the DCH flag (ContinueCall ) in the CDR. The generated IN and ordinary CDRs are for the same call. When DCH occurs after an IN call is answered, provide an IN CDR for the IN subscriber if the call is released. Fill the DCH flag (ReleaseCall) in the CDR. 1.3. When the IN subscriber is the calling party, the DCH supports separate handling for the following three types of call: call to international subscriber, call to international roaming subscribers, and call to subscribers of other types. When the IN subscriber is the called party, the DCH supports separate handling for the following three types of call: call from the attendant, call from international roaming subscribers, and call from subscribers of other types. 2. For IN SMs, the SSP determines the specific SM handling mode in the case of interaction exception between the SCP and the SSP according to the SCP address and service key. The SM handling mode includes: directly terminate SM handling, directly continue SM handling, and terminate or continue SM handling according to the DCH mode in subscriber data (MO-SMS CSI/MT-SMS CSI). The SSP performs DCH in the following cases: After reporting IDPSMS, the SSP receives such error messages from the SCP as MissingCustomerRecord, MissingParameter, SystemFailure, TaskRefused, UnexpectedComponentSequence, UnexpectedDataValue, UnexpectedParameter and ParameterOutOfRange. Applying system resources failed when the SSP reports the IDPSMS message. After reporting the IDPSMS message, the SSP receives such messages delivered by TCAP as TC_notice, TC_p_abort, TC_l_cancel, TC_continue (the application context is unmatched), and TC_end (the application context is unmatched). The Tssf timer times out when the SSP is in the WaitingForInstructionsSMS state. When the DCH occurs to IN SMs, provide the IN CDR for IN subscribers if the SM is continually handled. Fill the DCH flag (ContinueCall) in the CDR. Service benefit: For operators Provide flexible means to control whether to continue the call in the case of interaction exception between the SSP and the SCP. The generated ordinary CDR after the call is
CONFIDENTIAL
continued is indicated but is still used to charge IN subscribers, without causing fees loss for operators. For subscribers None Requirements for peripheral network entities: None
WMFD-151000 Function name: Configurable CalledPartyBCDNumber in IDP message for MO IN trigger Specification: None Implemented node: VMSC/VLR and GMSC Served network: GSM and UMTS Brief introduction: The called numbers reported by the IDP in the process of MO are configurable. Description: The called numbers reported by the IDP in the process of MO (DP2 or DP3) are configured to the numbers dialed by subscribers or the numbers through conversion processing. Note: When the SCP delivers the CONNECT message, it is required to compare the number reported by the IDP actually with the DRA number in the message to judge whether the SCP changes the number. Service benefit: For operators Flexibly configuring the called numbers reported by the IDP in the process of MO can meet the service processing requirements of the SCP. For subscribers None Requirements for peripheral network entities: None
WMFD-151100 Function name: Optional MSCaddress and SMS index in IDP-SMS message Specification: 3GPP TS29.078 Implemented node: VMSC/VLR Served network: UMTS
CONFIDENTIAL
Brief introduction: The SMS index and the MSC address in the InitialDPSMS reported in the process of SMMO or SMMT are optional. Description: It is required to control whether to contain the SMS index and the MSC address in the InitialDPSMS reported in the process of SMMO or SMMT according to the data configuration. Service benefit: For operators Flexibly configuring whether to contain the SMS index and the MSC address in the InitialDPSMS reported in the process of SMMO or SMMT can meet the service processing requirements of the SCP. For subscribers None Requirements for peripheral network entities: None
WMFD-151200 Function name: CAMEL phase4 Brief introduction: The phase 4 of the 3GPP CAMEL protocol mainly enhances the calling party control capability (CPH), so it can individually control a subscriber in a call, and convene multiple subscribers to call at the same time. Description: It supports the following 19 new capability sets of the CAMEL4 concretely. Initiate Call Attempt: It is initiated in the network, and creates a number portability (NP) of the caller or a call (NC). Split Leg: It makes a caller independent, or moves a caller to the CS1 when the CS1 does not exist. Move Leg: This CAP operation is used to move subscribers from the current CS to the main calling conference hall CS1. Disconnect Leg: This CAP operation is used to disconnect a specified leg of a subscriber from the current call without affecting other legs. Entity Released: The CSA uses this CAP operation to notify the SCF that the logic entity (CS or BCSM) is released due to an abnormal call. But other logic entities are not released, so the CSA cannot finish the session. DFC With Argument: This CAP operation is used for the SRF connection established through the CTR or ETC operation before the SCP split.
CONFIDENTIAL
Play Tone: This function of playing basic tone language of the MSC is used to play the tone language of a party in a call or select a more flexible bursts format. DTMF Mid Call: In the called DTMF MidCall process of the MO and the VT, the keys of the MO and the VT subscribers can be reported to the SCP in a call. Charging Indicator: In the O-Answer or T-Answer DP event, a charging indicator parameter can be reported to indicate the charging, and the parameter is the same as that in the ITU-T Q.763. Alerting DP: By extending the BCSM call model, it supports reporting the O_Term_Seized/T_Call_Accepted DP event in the O-BCSM or T-BCSM when the called number rings. Location At Alerting: The O_Term_Seized and T_Call_Accepted events contain the location information of subscribers. Change Of Position DP: The MO call supports the DP O_Change_Of_Position, the VT call supports the DP T_Change_Of_Position, and the position information during a call is reported. Criteria for Change Of Position DP: It indicates that the SSP supports the delivering of parameters of criteria for Change Of Position DP. BOR Interactions: It allows the SCP to control whether the SSP allows the BOR being used by the call. Warning Tone Enhancements: It indicates the SCP whether to contain the warning tone with the Burstlist format in the ApplyCharging. CF Enhancements: This function is used for the SSP to tell the SCP that the forwarded-to number (FTN) can be contained when the ERB reports the T_Busy or the T_No_Answer DP message. subscribedEnhancedDialedServices: The SSP supports the subscribed EDS function of subscribers. Serving Network Enhanced Dialed Services: The SSP supports the function of serving network EDS. Service Change DP: The SSP supports the configuration of the following EDP events, O_Service_Change and T_Service_Change DPs Specification: 3GPP TS 23.078 V6.3.0 (2004-09)
CONFIDENTIAL
multiparty conference call, intelligent ring back tone (RBT) service, simultaneous ringing service, and intelligent callback service. More flexible voice playing capabilities can construct more plentiful service flows, thus obtaining more profits for operators. For subscribers The mobile subscribers can obtain more plentiful service flows, and use diversified service flows at different time, so as to enjoy more personalized services. Requirements for peripheral network entities: MGW: It is cooperated with the MSC Server to complete the function of enhanced announcement, and supports playing the BurstList voice. HLR/VLR: The VLR is cooperated with the HLR to complete the flows of the location update and obtaining roaming numbers of CAMEL4 subscription subscribers. SCP: It can develop the service logic based on the CAMEL4.
WMFD-160300 Function name: Intra-MSC A-Flex Description: Intra-MSC A-Flex is also called Mini-A-FLEX. Normally, the MSOFTX3000 is only connected with GSM BSCs that belong to the same MGW. If the MGW that the BSCs belong
CONFIDENTIAL
to is faulty, the services handling by these BSC will be completely interrupted. To avoid the service failure caused by the MGW upgrade or MGW failure, Mini-A-FLEX is introduced to allow one BSC to connect with multiple MGWs. These MGWs adopt the load sharing mode for service management. When one MGW is faulty, other MGWs can take up the load. Meanwhile, to save the trunk transmission resource to the maximum extent, the circuit connections between MGWs under the same MSC system are reduced. When the calling and called BSCs are connected with the same MGW, the system selects the shared MGW first. The following figure shows the Mini-A-FLEX networking:
MSoftx3000
MGW1
MGW2
MGW3
BSC1
BSC2
BSC3
Mini-A-FLEX networking needs to implement the following system functions: A BSC can be connected with multiple MGWs. The MSOFTX3000 can select the circuit resource of the corresponding MGW based on the requirements. When the calling and called BSCs are connected with the same MGW, the system selects the circuit on the same MGW first to avoid wasting the circuit resource between MGWs. Implemented node: VMSC/VLR Served network: GSM Service benefit: For operators Enhance the network security. Prevent overall service failure when one MGW is faulty. Save the transmission resource. For subscribers None Requirements for peripheral network entities: None
WMFD-160400 Function name: Intra-MSC Iu-Flex Description: Intra-MSC Iu-Flex is also called Mini-Iu-FLEX. Normally, the MSOFTX3000 is only connected with RNCs that belong to the same MGW. If the MGW that the RNCs belong to is faulty, the services handling by these RNC will be completely interrupted. To avoid the
CONFIDENTIAL
service failure caused by the MGW upgrade or MGW failure, Mini-Iu-FLEX is introduced to allow one RNC to connect with multiple MGWs. These MGWs adopt the load sharing mode for service management. When one MGW is faulty, other MGWs can take up the load. Meanwhile, to save the terminal resource to the maximum extent, the connections between MGWs under the same MSC system are reduced. When the calling and called RNCs are connected with the same MGW, the system selects the shared MGW first. The following figure shows the Mini-Iu-FLEX networking:
MSoftx3000
MGW1
MGW2
MGW3
RNC1
RNC2
RNC3
Mini-Iu-FLEX networking needs to implement the following system functions: A RNC can be connected with multiple MGWs. The MSOFTX3000 can select the terminal resource of the corresponding MGW based on the requirements. When the calling and called RNCs are connected with the same MGW, the system selects the terminal on the same MGW first to avoid wasting the circuit resource between MGWs. When the bearer from the MGW to the RNC is faulty, the MGW reports the fault to the MSC Server through the Mc interface. When the RNC needs to set up a call, the MSC Server does not select the MGW for bearer establishment. Implemented node: VMSC/VLR Served network: UMTS Service benefit: For operators Enhance the network security. Prevent overall service failure when one MGW is faulty. Save the transmission resource. For subscribers None Requirements for peripheral network entities: None
CONFIDENTIAL
Network Time Protocol (NTP) was proposed by professor D.L. Mills of Delaware State University, U.S.A. in 1985. It is used to measure the round-trip delay of the data packet on the network and estimate the time deviation of the computer clock to reach the purpose of high-accuracy timing. At present, the protocol RFC1305 is in force. By connecting with the external NTP time server, the system can use the time of the NTP timer server to adjust the system time and ensure that the deviation of absolute time in the LAN is less than 10 ms. Implemented node: GMSC or TMSC Served network: GSM or UMTS Service benefit: For operators Ensure the accuracy of system absolute time. For subscribers Requirements for peripheral network entities: The NTP server must be available.
WMFD-161100 Function name: Early and late assignment of mobile subscriber Description: The difference between early and late assignments lies in assignment occasion of TCH. Called party: Early assignment: Begin to assign before hooking off. Late assignment: Begin to assign after hooking off. Calling party: Early assignment: Begin to assign before ALERTING. Late assignment: Begin to assign after ALERTING. Early assignment shortens call proceeding delay and improves call completion rate. Late assignment avoids idle occupation of TCH resources during ringing to increase TCH resource utilization. Implemented node: VMSC/VLR Serve Network: GSM and UMTS
WMFD-161200 Function name: Multiple national area code Description: MSOFTX3000 device can control MGW devices at physical location of different area codes. This function only supports multiple area codes simply and calls between area codes are still intra-office calls. Implemented node: VMSC/VLR, GMSC
CONFIDENTIAL
WMFD-161300 Function name: Multimedia fallback function Description: During call proceeding, calling party originates multimedia call. When network finds the following cases, multimedia call is fell back to common calls. Called terminal does not support VP call. Called party is unwilling to receive call in VP mode. Called party does not subscribe to VP service. Called party roams to GSM network. Called party is switched over to GSM network during VP call. This function can be applied in R99 and R4 networking. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: UMTS Service benefit: For operators Call completion rate between 3G subscribers and subscriber satisfaction can be improved obviously. For subscribers Simplify multimedia service operations. Requirements for peripheral network entities None
WMFD-161400 Function name: TFO function Description: It is a codec type negotiated and unified between codecs on call channel through bearer control protocol. On call channel, multiple encoding prior to decoding (or decoding prior to encoding) is avoided. During conversation, speech packet must pass codec. If speech packet does not pass codec, encoding and decoding are unnecessary. However, negotiation and control information of codec is monitored to determine whether TFO is sustained or encoding/decoding is necessary. TFO mechanism can be applied in R99 and R4 networking. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: UMTS Service benefit:
CONFIDENTIAL
For operators Speech quality of conversation between 3G MS subscribers can be improved obviously. For subscribers Enjoy high-quality conversation speech. Requirements for peripheral network entities None
WMFD-161500 Function name: TrFO function Description: In a R4 networking mode, if bearer type in internal core network is IP/ATM, MGW passing call channel adopts AMR codec which is applied in lu interface of calling subscriber after MSC Servers negotiating speech codec type. Therefore, bearer connection without TC in the whole call channel can be established to transmit speech packet uploaded from previous office (or MGW) transparently need not data coding and decoding. During a call, if a certain process cannot be implemented without TC due to handover or supplementary service usage, proper TC can be inserted into MGW under the control of MSC Server. After handover or using supplementary services, connection without TC is restored. Then, TrFO function restores. If conversation is not proceeded between 3G terminals or non-IP bearer type exists in call bearer connection channel (for example, in the case of interworking with other networks, bearer type changes into TDM bearer after GMSC is passed), TrFo mechanism can be applied in IP bearer section within mobile network. Additionally, Huawei MSOFTX3000 can also support TrFO function of intra-office calls. That is, perform AAL2 switching to intra-office mobile-to-mobile calls without applying TC resources. Therefore, speech quality is improved. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: UMTS Service benefit: For operators With TrFO function, speech quality between 3G MS subscribers is improved obviously. With TrFO bypass codec mechanism, a large amount of TC resources and network establishment investment are saved. For subscribers Enjoy high-quality conversation speech. Requirements for peripheral network entities None
WMFD-161700
CONFIDENTIAL
Function name: Echo cancellation (EC) control Description: When calls are from mobile network to PSTN, 4-wire transmission is applied in digital trunk network transmission system and a pair of lines among subscriber lines are performed full duplex transmission, namely 2-wire transmission. Switch in local PSTN adopts 2/4 converter to implement transformation and echo occurs during transformation. You can adopt EC device to cancel echo. Here, it specially refers to control EC parameter of MSC Server and process EC related signaling procedure. Coordinating with Huawei MGW, this function can provide suppression of acoustics and electricity echo. Implemented node: VMSC/VLR, and GMSC Serve Network: UMTS Service benefit: For operators With EC function, speech quality of conversation between 3G MS subscribers and fixed subscriber is improved obviously. For subscribers Enjoy high-quality conversation speech. Requirements for peripheral network entities None
WMFD-161800 Function name: Dialing without NDC Description: Allow end subscribers to dial MSISDN without NDC, namely connecting call through. Implemented node: VMSC/VLR, and GMSC Serve Network: GSM and UMTS Service benefit: For operators Allow subscribers to dial MSISDN that does not contain NDC to improve subscriber satisfaction. For subscribers Shorten length of dialed number. Requirements for peripheral network entities None
CONFIDENTIAL
Description: When call is dropped due to poor signal at air interface, MS originates procedure of CM service re-establishment within seven seconds. Network side re-establishes connection to ensure service continuity. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Decrease call dropped rate and improve service quality. For subscribers There is seldom call disconnection. Requirements for peripheral network entities None
WMFD-162000 Function name: Pre-paging Description: When HLR requires local MSC to allocate roaming numbers for mobile called subscribers roaming to local MSC, local MSC pre-pages mobile called subscriber. On the premises of successful pre-paging, roaming numbers are returned to HLR. Implemented node: VMSC/VLR Serve Network: GSM and UMTS Service benefit: For operators Clear known and disconnected calls at the earlier stage of call proceeding to: Decrease invalid network resource utilization. For example, circuit resources are allocated during inter-office ISUP signaling proceeding. Decrease invalid call attempts. Improve connection rate. Speed up call establishment. For subscribers End subscribers are unrelated. Requirements for peripheral network entities None
WMFD-162100
CONFIDENTIAL
Function name: Enhanced DCH Description: When an IN call is set up and sustained, if errors occur to the interaction between the MSC and the SCP because the link message to the SCP is unreachable, SSP internal timer expires, or the SSP internal resource is unavailable, the IN call is no longer controlled by the SCP. The Default Call Handle (DCH) function can flexibly control the call handling methods in the above case. The handling method include: Release the call by force. Continue the call by force. Use the default call handling method subscribed by the IN subscriber. In the above case, operators can set the data so as to continue the call by force for high-end IN subscribers or to release the call by force for low-end IN subscribers. When the traffic is in the peak and the SCP response speed is reduced, such setting can realize differential service, increase the call completion rate of high-end subscribers, and improve the service quality. Implemented node: VMSC/VLR, or GMSC Served network: GSM or UMTS Service benefit: For operators When errors occur to the interaction between the MSC and the SCP, the DCH function can flexibly control the subsequent call handling method according to the operators requirements. For subscribers Requirements for peripheral network entities: Billing center can process Free Call bills subsequently.
WMFD-162200 Function name: ISUP/TUP Continuity Check Description: Continuity Check is a function of SS7 circuit management. By using the SS7 continuity check signaling, the continuity of trunk circuit is effectively checked based on voice level. Without the continuity check, the problems resulted from the trunk interconnection errors between offices (such as cross-talking, monologue, and no audio caused by the error that A-Wire contacts earth and B-Wire contacts the battery), can only be detected by using inconvenient methods such as loopback, removal of trunk cables, or dialing test of specified circuit. The Continuity Check function helps locate the trunk errors in a fast and convenient manner. On the originating end of the continuity check, the transmitter and receiver that are used to check the tone must be connected with the transmitting path and receiving path of the circuit. On the receiving end of the continuity check, the check-loop must be connected with the transmitting path and receiving path of the circuit. If the originating end sends a tone on the transmitting path, the receiving end receives this tone, and the tone transmission quality and
CONFIDENTIAL
time limit are within the acceptable range specified in Q.724, the continuity check is regarded as successful. MSOFTX3000 support continuity check in maintenance but not in call flow. Implemented node: VMSC, GMSC, or TMSC Served network: GSM or UMTS Service benefit: For operator Improve the interconnection and interworking abilities, network quality, and call completion rate. For subscribers None Requirements for peripheral network entities: The peer office supports the Continuity Check function.
WMFD-162300 Function name: Assign half rate channel by user priority Description: With this function, the MSC can set the Channel Rate and Type (channel type assigned) in messages such as 2G Assignment Request and Handover Request based on the subscriber category and terminal capability reported by the MS. That is, assign subscribers with different priorities according to the subscriber category. If the terminal capability reported by the MS shows that terminal supports both full rate and half rate channels, the MSC will set the Channel Rate and Type to full rate channel (8) for subscribers with high priority. For subscribers with high priority, the BSC will always assign the full rate channel. For subscribers with low priority, the BSC will set the channel type to support both full rate and half rate channels and the full rate channel takes the precedence (10). When the load of BSC radio resource is light, assign the full rate channel. When the load of BSC radio resource is heavy, assign the half rate channel. Implemented node: MSC/VLR Served network: GSM Service benefit: For operator Ensure the Quality of Service for subscribers with high priority when the traffic is heavy. For subscribers None Requirements for peripheral network entities: None
CONFIDENTIAL
WMFD-162400 Function name: Enhanced subscriber category Description: On the existing networks, there are many applications using Calling Partys Category, E_CATEGORY, NAEA_CODE, or SS_CODE for special routing. Calling Partys Category, E_CATEGORY, NAEA_CODE, or SS_CODE is treated as a subscriber category. Calling Partys Category refers to the one defined in the Q.763 protocol. E_CATEGORY is a special indicator bit of a byte carried by the extension container and is used to identify the special category of a subscriber. SS_CODE refers to the customized supplementary service code defined in the protocol. When a subscriber subscribes to different Calling Partys Category, E_CATEGORY, NAEA_CODE, or SS_CODE, different processing, such as selection of different route and suppression of mobile originated IN service, will be carried out. In the MSOFTX3000, all of Partys Category, E_CATEGORY, NAEA_CODE, and SS_CODE are termed as enhanced subscriber category and a subscriber comprehensive service processing table is added. This table is used to complete the following processing based on Calling Partys Category, E_CATEGORY, NAEA_CODE, or SS_CODE: Conversion of calling and called numbers Determining whether to suppress the OCSI or DCSI intelligent service Determining whether to overwrite the DialNumber In addition, the enhanced subscriber category together with the service check type can provide different handling methods, such as failure handling. The announcement played during the failure handling can be specified by setting the failure source code. The following lists the specific applications: Before a prepaid service number is used, the E_CATEGORY is set to 10 upon subscription. No matter what number that the subscriber dials for the first time, the call is forwarded to a service center for registration. After the successful registration, the service center automatically modifies the value of E_CATEGORY. The above function can be realized by carrying out special number change processing on the E_CATEGORY10 through the comprehensive service processing table. The service center sets the E_CATEGORY of a defaulting post payment subscriber to 34. No matter what number that the subscriber dials, the call is forwarded to a service center and the service center informs the subscriber of the arrearage. The above function can be realized by carrying out special number change processing on the E_CATEGORY34 through the comprehensive service processing table. If the SS_CODE is set to F5 upon subscription, when the subscriber dials a toll call, operator 1 (access code: 800) will be selected. If the SS_CODE is set to F6 upon subscription, when the subscriber dials a toll call, operator 2 (access code: 801) will be selected. The above function can be realized by carrying out special number change processing on the SS_CODE5 and SS_CODE6 through the comprehensive service processing table, respectively adding prefix 800 and 801 to the called number, and then configuring different number analysis schemes and route selection codes. The combination of E_CATEGORY and ODB is used for playing announcement. Different E_CATEGORY can match the ODB sent from the HLR to provide announcement playing. Assume that when E_CATEGORY is set to 0, it indicates the
CONFIDENTIAL
ordinary subscriber and when E_CATEGORY is set to 12, it indicates the pre-paid subscriber. When an ordinary subscriber is delinquent, the HLR sends the ODB_BOIC&ODB_BAOC to identify that the subscriber is delinquent. When the subscriber originates a call, the MSC restricts the call and plays the announcement "Your mobile phone is out of service due to owning fee." When a pre-paid subscriber is delinquent, the HLR sends the ODB_BOIC&ODB_BAOC to identify that the subscriber is delinquent. When the subscriber originates a call, the MSC restricts the call and plays the announcement "Sorry, your balance has little money. Please charge." The MSC can restrict calls through the combination of the E_CATEGORY and the ODB BAOC or ODB BOIC by setting the subscriber's integrated service processing data. The MSC also can specify the cause value of disconnection and the failure code. Different announcements can be played for the same failure cause. Implemented node: VMSC/GMSC Served network: GSM or UMTS Service benefit: For operators Customize special services using Calling Partys Category, E_CATEGORY, NAEA_CODE, or SS_CODE. For subscribers Requirements for peripheral network entities: The HLR must support the Calling Partys Category, E_CATEGORY, NAEA_CODE, and SS_CODE.
WMFD-162500 Function name: Daylight saving time Description: Some countries require the system to support the auto adjustment of daylight saving time. That is, users can specify the start time and end time of daylight saving time, as well as the adjustment cycle (the adjustment amplitude when the daylight saving time comes, for example, one hour). When the system time reaches the start time of daylight saving time, the system automatically sets the time an adjustment cycle backward. For example, if the adjustment cycle is one hour and the current time is 09:00, the time will be set one hour backward and become 08:00. When the system time reaches the end time of daylight saving time, the system automatically sets the time an adjustment cycle forward. For example, if the adjustment cycle is one hour and the current time is 09:00, the time will be set one hour forward and become 10:00. Implemented node: GMSC or TMSC Served network: GSM or UMTS Service benefit: For operators -
CONFIDENTIAL
Ensure the accuracy of local time. For subscribers None Requirements for peripheral network entities: None
WMFD-162600 Function name: Mobile Virtual Network Operator (MVNO) Description: MVNO is an operating mode that multiple operators share the core network (CN) and access network. Currently, the MSOFTX3000 supports the five scenarios defined by the TR22.951 (V6.1.0) specifications. This function is available based on the availability of these techniques: Iu-Flex, network sharing in connected mode, NITZ, MVNO-based user number control, and charging for different operators. Implemented node: VMSC/VLR, GMSC Served network: GSM and UMTS Service benefits For operators Operator can share networks. Operators without network infrastructure can operate virtually through leasing networks of other operators. For subscribers Requirements for peripheral network entities: None
WMFD-162700 Function name: Multiple time zones Description: One MSC Server can cover an area having multiple time zones or an area having different daylight saving time. The MSC Server can automatically adjust the time stamp on the CDR according to the time zone and daylight saving time setting. This function ensures that the recorded time is the same as the local time where the subscriber locates, guarantees the accuracy of time reporting, and updates the time on the UE to the time of the area where the subscriber locates. Implemented node: VMSC/VLR Served network: GSM and UMTS Service benefits For operators
CONFIDENTIAL
One MSC Server can cover an area having multiple time zones or an area having different daylight saving time, so operators can reduce the costs. For subscribers Requirements for peripheral network entities: None
WMFD-162900 Function name: Camel trigger based on INClassMark Description: This function indicates whether a user is an IN subscriber by using the SS-CODE information element (IE) in the call forwarding subscription data. If the SS-CODE IE is set to plmn-specificSS-4 (0xF4), this is an IN subscriber; if not, this is a common subscriber. This data is inserted into the VLR during location updating procedure. If the user subscription data includes the previously mentioned extended supplementary service code in a call, the MSOFTX3000 adds a service attribute code SERVICE 13 for the subscriber. Then, you must configure the Caller Attribute Processing table and the Caller Feature Analysis table: 1. In the Caller Attribute Processing table, map the service attribute SERVICE 13 to a caller feature. 2. In the Caller Feature Analysis table, set the Processing type to Trigger NCSI_DP2. When the configuration is completed, IN services can be successfully triggered for the subscriber. Example: During location update, the user subscription data is inserted into the VLR. The MSOFTX3000 judges whether the user is an IN subscriber according to the SS-CODE IE in the call forwarding subscription. If so, the MSOFTX3000 automatically adds the service attribute SERVICE 13 for the user. When the user originates a call, the MSOFTX3000 triggers NCSI DP2 IN service according to the settings in the Caller Attribute Processing table and Caller Feature Analysis table. If a user subscribes to trigger IN services through INClassMark, and the call forwarding (CF) service: When the MSOFTX3000 acquires the called MSRN from the HLR in an early forwarding, the subscription data is returned to the MSOFTX3000 through an SRI message. After the call is forwarded, the MSOFTX3000 judges whether to trigger IN services for the subscriber according to the extended supplementary service code. If so, it triggers the MF IN flow according to settings in the Caller Attribute Processing table and Caller Feature Analysis table. If not, it forwards the call in the common flow. In a late forwarding, the user data is inserted into the VLR during location updating procedure. After the call is forwarded, the MSOFTX3000 judges whether to trigger IN services for the subscriber according to the extended supplementary service code in the VLR. If so, it triggers the MF IN flow according to settings in the Caller Attribute Processing table and Caller Feature Analysis table. If not, it forwards the call in the common flow.
CONFIDENTIAL
Implemented node: VMSC/VLR, GMSC Served network: GSM and UMTS Service benefits For operators The operator can provide caller subscription IN services by using extended supplementary services and configuring data. For subscribers Subscribers can subscribe to caller IN services as needed. Requirements for peripheral network entities: The HLR must support the subscription of extended supplementary services.
WMFD-163000 Function name: SMS notification if call incomplete Description: SMS notification if call incomplete is a service that informs the called party of missed calls. When a call fails, the network sends a short message to the called party to inform the subscriber of the date, time and caller number of the missed call. The content format of the SMS is: date of a failed call + time of a failed call + content defined by the configuration + callers MSISDN. The content can be defined as required by the operator by using the ADD SMCONT command. SMS notification if call incomplete is a network-level service. It does not need service subscription data in the HLR. In one of the following cases, the network side triggers this service: The called party power off; The called party is unreachable (for example, the subscriber is out of the service area); The called party is network-decided busy; The called party does not reply. Example: A calls B when B switches off. The network side sends an SMS to B to inform B of the date and time of the call and As number. A calls B when B is out of the service area (no signal). The network side sends an SMS to B to inform B of the date and time of the call and As number. A calls B when B is in a call. The network side sends an SMS to B to inform B of the date and time of the call and As number. A calls B, but B does not answer the call after the MS rings. The network side sends an SMS to B to inform B of the date and time of the call and As number. Implemented node: VMSC/VLR, GMSC Served network: GSM and UMTS Service benefits
CONFIDENTIAL
For operators SMS notification if call incomplete allows the operator to provide another compensation service in call failure, which is one more measure for subscribers to make compensation on missed calls. The operator can edit specific SMSs for different call failure types so that the subscriber can learn the specific reason of each missed call. For subscribers The function provides another compensation service to reduce the loss from a missed call when the subscriber cannot answer the call. The subscriber can learn the specific reason, callers number, and date and time of each missed call. Requirements for peripheral network entities: This service involves three NE entities: MSC, HLR and Short Message Service Center (SMSC). For this service, the GMSC or VMSC completes various signaling processing, data analysis, and construction and transmission of SMSs of call failures. If the called party is absent in the call (switching off, roaming not allowed, deleted from the VMSC or unreachable), the HLR sends the information of the called party in the SRI message to the GMSC to prepare the condition for triggering the SMS notification if call incomplete service. The SMSC receives and sends the SMS of call failure.
WMFD-163100 Function name: User differentiated service Description: User differentiated service can decide service priority level according to the subscription information (Category, eMLPP, CARP), service type (emergency call, voice service, transparent data service, non-transparent data service, facsimile), access network type (BSC, RNC) and the called number of the subscriber. For IN subscribers, the MSC can define service brands by using different combinations of the four key fields: service key, caller number, called number, and SCFID. In addition, it can define the processing type, call restriction or flow control, of this brand when the SSP is overloaded. A specific priority level can be set to each service brand. The function allows the operator to define strategies for different subscribers and scenarios. The function can assign a priority level and pre-empt resources in radio channels. The function can assign a specific priority level to a mobile subscriber and the subscriber can select a priority level for each specific call within the authority. Calls of different priority levels are set up in different modes. Calls of high priority level are set up faster than those of low priority level, or even allowed to pre-empt resources. When the network resources (including processing ability, signaling channels and service channels) are highly occupied, the calls of high priority level can pre-empt the resources occupied by calls of low priority. Preemption can disconnect ongoing calls of low priority level by force to connect the calls of high priority level.
CONFIDENTIAL
select the corresponding radio channel type (full rate channel or half rate channel) according to the service priority. grand the access of high priority service when the MSOTX3000 lacks resources. The function ensures more support to high priority services. improve the pre-emption capability of high priority services in pre-empting trunk resources from low priority services when the narrowband circuits are insufficient. The function ensures that high priority services can gain resource support efficiently. Huawei MSOFTX3000 supports subscription information: CATEGORY, eMLPP, CARP (in 3G networks), service key, and SCFID. Implemented node: VMSC/VLR, GMSC Served network: GSM and UMTS Service benefits For operators This function allows the operator to adopt user strategies flexibly. When the network is congested, high-end users can enjoy better QoS, such as short connection time, good voice quality and high connection rate. For low-end users, resources may be pre-empted and the voice codec rate may be decreased. For subscribers Requirements for peripheral network entities: The HLR must support the subscription of caller category (all HLRs support this function), eMLPP, CARP, and IN subscription information related to differentiated service (service key/SCP ID). The BSC/RNC must support the function of providing differentiated service according to the priority level, Pre-emption Capability Indicator (PCI), Pre-emption Vulnerability Indicator (PVI) and Queue Allowed (QA) indicator in the Assignment Request message.
WMFD-163200 Function name: Service based handover Description: Service based handover decides whether to allow inter-system handover and the preferred network type (GSM/WCDMA) according to the IMSI number segment, category and service type of the subscriber. If the current network is not the preferred network (for example, the subscriber currently registers on a GSM network, but the preferred network in data configuration is WCDMA network), the MSC Server notifies the BSC/RNC to activate handover in the Assignment Request message. Thus, the call is handed over to the target network. Handover can optimize resources. Currently, the service types supporting the service-based handover function include voice service, transparent data service and non-transparent data service. The supported handover strategies include: For 2G services: Handover to 3G should be performed
CONFIDENTIAL
For the Non-Access Stratum (NAS), calls should be handed over to the UMTS or cdma2000 network as soon as possible, but the BSS has the final decision on handover. Handover to 3G should not be performed For the NAS, the user should stay on the GSM network as long as possible, but the BSS has the final decision. Handover to 3G shall not be performed Handover to UMTS or cdma2000 network is absolutely prohibited. Handover to 3G not contained The Handover Request and Assignment Request messages do not bring the ServiceHandover IE. Handover to 3G reject by card Handover from a 2G network to a 3G network is rejected according to card type (SIM or USIM). Handover to 3G not reject by card Handover from a 2G network to a 3G network is rejected not according to card type. For 3G services: Handover to 2G should be performed For the NAS, this RAB should be handed over to a GSM network as soon as possible, but the UTRAN has the final decision. Handover to 2G should not be performed For the NAS, this RAB should stay in the UMTS network as long as possible, but the UTRAN has the final decision. Handover to 2G shall not be performed Handover to the GSM network is absolutely prohibited (unless under normal condition when the RAB will be released). Handover to 2G not contained The Handover Request and Assignment Request messages do not bring the ServiceHandover IE. Handover to 2G reject by card Handover from a 3G network to a 2G network is rejected according to card type. Handover to 2G not reject by card Handover from a 3G network to a 2G network is rejected not according to card type.
Implemented node: VMSC/VLR Served network: GSM and UMTS Service benefits For operators
CONFIDENTIAL
Operators who have both GSM and WCDMA networks can use the function to activate the service on the corresponding network and save radio resources. For subscribers Requirements for peripheral network entities: The BSC/RNC must support activating the required handover request according to handover parameters in the Assignment Request message.
WMFD-163400 Function name: Update Network Indicator and Time Zone (NITZ) Description: The NITZ function complies with 3GPP 22042 specifications. According to the location and IMSI of the subscriber, the network sends the carrier name, local time, time zone and daylight saving time (DST) of the area where the user locates in the MM INFORMATION message to the MS of the subscriber. After the MM INFORMATION message is sent to the MS, the carrier name (including full name and short name) displayed in the MS can be updated immediately. The supported coding schemes include UCS2 and 7Bit. After the MM INFORMATION message is sent to the MS, the time information (including time zone and DST) in the MS can also be updated immediately. Huawei MSOFTX3000 can control to send the time of the area where the switch locates or where the mobile subscriber locates. When in the DST time, the system automatically adjusts the time. The time sent in the MM INFORMATION message is the adjusted time. Implemented node: VMSC/VLR Served network: GSM and UMTS Service benefits For operators The operator can provide more user experience and increase users satisfaction. For subscribers Requirements for peripheral network entities: The MS must support the MM INFORMATION message.
WMFD-163400 Function name: Paging based on service type Description: In 3GPP 48.008 specifications, the optional IE Channel Needed is defined in the Paging message. This IE indicates the radio channel type that may be used in the subsequent service flows. The BSC can use this IE to decide the subsequent channel type, distinguish service type and carry out flow control. Example:
CONFIDENTIAL
In an MT call, the MSC can indicate the subsequent services to use full rate channel or dual rate channel in the Channel Needed cell in the Paging message. For the SMS reception service/USSD service/LCS, the MSC can indicate the subsequent services to use SDCCH channel in the Channel Needed cell in the Paging message. If the BSC does not support the Channel Needed IE, the Paging message does not necessarily bring the IE. Implemented node: VMSC/VLR Served network: GSM Service benefits For operators If the BSC supports the Channel Needed IE in the Paging message, it can effectively distinguish various service flows, carry out flow control on services (SMS for example) of low priority level in the case of large traffic, reduce the load of the BSC and 2G access networks, and ensure normal provision of services of high priority level. The BSC can also reduce the unnecessary occupation of TCH bearer channels according to the Channel Needed IE. For subscribers Requirements for peripheral network entities: The BSC must support the Channel Needed IE in the Paging message and carry out service-based flow control or channel distribution optimization accordingly.
WMFD-163600 Function name: Equipment archive management Description: The operator can use the NMS to obtain detailed information of the switch, including basic information, connection, modules, configuration, peer equipment, host version, cabinet, shelves, boards and electronic stamp of on the board Flash memory of the equipment. The BAM generates an equipment archive XML file after receiving the command of equipment archive generation sent by the NMS. The NMS can also send a command to require the BAM to upload the equipment archive file to directory designated by the NMS. Implemented node: VMSC/VLR, GMSC, TMSC Served network: GSM and UMTS Service benefits For operators Convenient for operator to query, manage and maintain the equipment information. For subscribers Requirements for peripheral network entities: All NEs must be provided by Huawei, so that this function can be enabled at the NMS.
CONFIDENTIAL
WMFD-163700 Function name: Dual Transfer Mode (DTM) Description: DTM means that one Mobile Equipment is running CS service and PS service simultaneously, according to 3GPP TS 0355. This function is only for GSM network. Implemented node: VMSC/VLR Served network: GSM Service benefits For operators The operator can provide better QoS to the subscribers and improve the user satisfaction. For subscribers Requirements for peripheral network entities: The MS must be a Class A MS (there are class A, B and C MSs that support PS domain) and support the DTM feature. The BSC must support the DTM feature.
WMFD-163800 Function name: TFO/TrFO Interworking Description: For a R4 network used to GSM/UMTS, TFO can be used on A interface to negotiate as a common codec such as EFR, and TrFO can be used Nb interface to negotiate common codec between MGWs, the proper codec can be selected for end to end. Please refer to the following figure:
Option 1: FR/EFR is highly recommended, BSC need to support TFO and softswitch need to support TFO/TrFO interworking with FR/EFR codec Option 2: AMR is adopted on Nb interface, G.711 is on A interface, TC is deployed in BSC;
CONFIDENTIAL
Implemented node: VMSC/VLR Served network: GSM/UMTS Service benefits For operators The operator can provide better QoS to the subscribers and reduce Coding and Decoding. For subscribers Requirements for peripheral network entities: The BSC must support the TFO feature.
WMFD-163900 Function name: IP CAC (Call admission control) Description: CAC mechanisms: IP QoS function: By using H248 message, MSC Server can monitor the status of IP bearer between MGWs. If MGW detects the value IP QoS is lower than the threshold, a Notify message with the IP QoS level will be reported to MSC Server. Then MSC Server can initiate the call flow control between these 2 MGWs. And the call with lower priority will be abandoned first. The priority can be configured according to the subscriber priority or service priority. Support H.248 flow control function: For each call, when create a new context by using ADD command, the priority will be send to MGW too. And this priority can be configured according to different service. For example, for emergency call, it can be assigned a high priority. When the Mc link or MGW overloads, the higher priority context will be reserved and lower priority ones will be released first.
CONFIDENTIAL
Served network: GSM and UMTS Service benefits For operators The operator can provide better QoS to the subscribers and improve the user satisfaction. For subscribers Requirements for peripheral network entities: No WMFD-164100 Function name: REL reroute Specifications: None Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Target market/customer: Hong Kong, the UAE Brief introduction: During an ISUP/BICC-based outgoing call, after receiving the REL message containing the redirection number parameter from the peer office, the MSOFTX3000 starts call redirection based on the redirection number. Description: The call from A to B is rerouted to C before being answered (UAE requirement): When A calls B, after the MSOFTX3000 detects that B has subscribed to the REL reroute service and obtains the international roaming number, the MSOFTX3000 directs the call to a
CONFIDENTIAL
server. The server decides whether to redirect the call to B's international roaming number, that is, the MSRN or to the voice mail by using the access number of the voice mail. The call from A to B is rerouted to C after being answered (Hong Kong SUNDAY requirement): A calls a service center (number B). After the call is connected, number C is dialed. Then, the service center originates the redirection of the REL number change. The REL message contains the redirection number. This function cannot be realized when number B is an IN subscriber number. Service benefit: For operators Carriers can provide the number redirection service and the service for shielding international roaming subscribers. For subscribers None
WMFD-164200 Function name: BICC bearer redirection Specifications: ITU-T Q.1902.5 Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Target market/customer: None Brief introduction: The BICC bearer redirection can optimize the inter-office bearer by reducing the number of offices by which the bearer path passes. Description: During a call, assume that the MSC Server requires to connect the call to another destination instead of the original callee (for example, in the case of call forwarding on mobile subscriber not reply). When the BICC bearer redirection function is enabled, the bearer connection that has been set up can be disconnected, and a direct bearer from the caller to the new destination is set up. In this case, the office where the original callee is located becomes the CMN node and does not control the bearer resources. The BICC bearer redirection can used for forwarding only. Service benefit: For operators Carriers can optimize the bearer path. For subscribers None Requirements for peripheral network entities -
CONFIDENTIAL
WMFD-164300
Function name: Anti-Cheat (to restrict forwarding and the number of ECTs) Implemented node: VMSC/VLR Serve network: GSM and UMTS Description: An example is used for describing the Anti-Cheat function. When A calls B, if B has subscribed to the service that the call is forwarded to C, connection between A and C is set up, but it is not required to set up the connection between A and B, or B and C. In this case, if B has activated the forwarding service, B can unrestrictedly set up several connections between An and Cn. Therefore, a large amount of fee is generated in a short time. If the fee cannot be paid, carriers consider it as a cheat. The case also occurs in the explicit call transfer (ECT) service. To avoid the cheat, the number of times a call is forwarded by a subscriber in the local office and the number of ECTs are restricted. Carriers can enable the Anti-Cheat function and control the number. Service benefit: For operators The security of the network can be improved. For subscribers The function can prevent malice subscribers from using the network illegally. Requirements for peripheral network entities None
WMFD-164400
Function name: VDB backup Implemented node: VMSC/VLR Serve network: GSM and UMTS Description: The VDB dynamic backup means that in the dual-homing networking, the VLR of the active MSC Server backs up the subscriber data from the VDB of the active MSC Server to the VDB of the standby MSC Server through the M3UA link. When the active MSC Server is faulty, the standby MSC Server takes over the services of the active MSC Server and directly use the backup subscriber data. This avoids the impact on the A/IU/C/D interface when the subscriber data restores automatically. The VDB dynamic data backup must be used together with the dual-homing function in the dual-homing networking. The VDB dynamic data backup supports 1+1 mutual assistant networking, 1+1 backup networking, n+1 backup networking and n+1 mutual assistant networking.
CONFIDENTIAL
The VDB backup supports that the active MSC Server can obtain the backup subscriber data from the standby MSC Server during the dual-homing rollback. To obtain the backup subscriber data from the VDB of the standby MSC Server, the dual-homing rollback must be performed manually. For n+1 backup networking or n+1 mutual assistant networking, the standby MSC Server can back up the subscriber data from all active MSC Servers. When the dual-homing switchover occurs, the subscriber data of only one active MSC Server can be retained, and the subscriber data of other active MSC Servers is deleted. That is, the standby MSC Server can take over the subscriber data of only one active MSC Server. Service benefit: For operators The function can avoid the impact caused by the dual-homing switchover on the A/IU/C/D interfaces. Therefore, the dual-homing switchover is more reliable and effective, and the disaster tolerance is ensured. For subscribers None Requirements for peripheral network entities The VDB dual-homing backup function is based on the dual-homing feature, so the MGW is required to realize the function.
WMFD-164500
Function name: China Unicom IVPN service Specifications: None Implemented node: VMSC/VLR and GMSC Serve network: GSM and UMTS Target market/customer: China Unicom Brief introduction: This function makes the IVPN service more accordant with specifications, so that China Unicom's requirement on the IVPN service can be met. Description: This function meets the following requirements: The IVPN bill sorting function is available for China Unicom of Guiyang, China, so the bills of roaming VPN subscribers can be sorted. Requirements on the IVPN bill generation for China Unicom in Guangdong, China: The ordinary MOC bill can be generated during the OVERLAY outgoing call. The generation of bills can be restricted when the IN service is triggered in the local office. Requirements on the caller number attribute of the IVPN for China Unicom in Guangdong, China: Subscribers can dial back the caller even if there is "0" wrongly displayed before the caller number.
CONFIDENTIAL
Requirements of the China Unicom IVPN signaling process guide V1.0: In the IVPN service triggered by the access code, the following functions are available:
The redirecting party ID can be used for triggering the MT intelligent service. The IDP message contains the ForwardingPending parameter during the Call Forwarding Unconditional service. Two methods are available for filling the MTC with the original callee number during non-forwarding cases.
Service benefit: For operators The function meets carriers' requirements on the IVPN service and ensures the good provision of the IVPN service. For subscribers Subscribers can be provided with more IVPN service processes. Requirements for peripheral network entities Only the MSC Server is required to realize the function.
WMFD-164600
Function name: H248.11 Function Specifications: H248.11 Implemented node: VMSC/VLR and GMSC and TMSC Serve network: GSM and UMTS Brief introduction: This function conforms to H248.11 specification, as MGW overload, MSC SERVER can limit the traffic allocated to the MGW. Description: If the MGW overload, it will send the Notify message to MSC Serverand MSC Sever can reduce the traffic of the MGW according to the Notify messages it received. By using this mechanism, MSC Server can keep the MGW in the safe output mode, avoiding collapse of the MGW. Service benefit: For operators By using the function, as MGW in high traffic, the MSC Sever can keep it in safe mode, avoid the collapse caused by overload traffic. Requirements for peripheral network entities It needs MGW to support H248.11 too.
CONFIDENTIAL
Russian lawful interception specification for GSM network(SOSM) WMFD-170103 Huawei lawful interception specification for GSM network WMFD-170104 Implemented node: VMSC/VLR and GMSC Serve Network: GSM and UMTS Service benefit: For operators Provide lawful interception service. For subscribers None Requirements for peripheral network entities Cooperate with XPTU device and interception center.
WMFD-170300
Function name: Multi-number interception Description:
CONFIDENTIAL
When performing the multi-CP and multi-number interception, one CP setting or deleting a number of a subscriber does not affect other CPs to set or delete the same number or different number of the subscriber, and has no influence on the interception event report of other interception numbers of the subscriber and the output of interception circuits. For example, the subscriber A is intercepted by CP1 and CP2 simultaneously, the CP1 intercepts the IMSI, and the CP2 intercepts the IMEI. If the subscriber A dials a phone number, the call voice is intercepted and outputted to the CP1 and CP2. At this time, the CP2 sets the IMSI interception of the subscriber A without affecting the existing interception circuits, and the IMSI interception of the CP2 to the subscriber A is of no effect on the call, namely the MSC does not output the IMSI interception circuit to the CP2. The multi-number only allows setting IMSI, MSISDN and IMEI simultaneously. Setting multi-number formats simultaneously is not allowed, for example, if 89020020 is set, and it is not allowed to set 79020020, and 9020020. Implemented node: VMSC Served network: GSM and UMTS Service benefit: For operators The multi-number interception service is used to realize the diversity of interception set by the security department. For subscribers Requirements for peripheral network entities:
WMFD-180100 Function name: Billing system interface Description: It refers to interface protocol and bill transmission mode between iGWB and billing center.
CONFIDENTIAL
WMFD-180101 Function name: FTP pull method to the billing system Description: With this collection mode, billing center obtains bill files from iGWB voluntarily. iGWB is FTP server and billing center is FTP client. Billing center logs in to iGWB automatically through running FTP and transmits bill files to local storage devices.
WMFD-180102 Function name: FTP push method to the billing system Description: With this collection mode, iGWB transmits bill files to billing center voluntarily. iGWB is FTP client and billing center is FTP server. iGWB logs in to billing center automatically by running FTP and transmits bill files to storage devices of billing center.
WMFD-180103 Function name: FTAM pull method to the billing system Description: With this collection mode, billing center obtains bills from iGWB. iGWB is FTAM responder and billing center is FTAM initiator. Billing center logs in to iGWB automatically through FTAM and transmits bill files to local storage devices. When this protocol is adopted, the following two modes are possible: FTAM over TCP/IP or FTAM over OSI-LAN.
WMFD-180200 Function name: CDR collecting Description: With sliding window protocol, bills are collected from MSC to iGWB. Sliding window protocol is a private message protocol over TCP/IP between Huawei MSC and iGWB with high reliability. With this protocol, bills can be transmitted to iGWB without repetition and loss, and MSC transmits generated bills to iGWB voluntarily and real time to realize high real-time charging. iGWB supports the following three bill formats: text, binary, and ASN.1 coding formats.
WMFD-180300 Function name: CDR storage Description: CDR storage includes original and final bill storage.
CONFIDENTIAL
Original bills refer to those that iGWB collect from MSC without preprocessing. iGWB supports original bill storage. Original bills are saved in physical medium for a certain period (you can configure storage days). When storage days exceed configured days, bill files are deleted automatically. After preprocessing such as consolidation, bills collected by iGWB from MSC become final bills whose formats meet billing center requirements. Then final bills are transmitted to charging center. iGWB can support final bill storage. Final bills are saved in physical medium for a certain period (you can configured storage days). When storage days exceed configured days, bill files are deleted automatically. WMFD-180400 Function name: CDR operation Description: CDR operation includes the following: Browse original or final bills. Query original or final bills. Measure original or final bills. Print original or final bills. LMT provides shortcut menu to support subscribers to perform the following operations: Browse bill details. Browse the next page of bills. Browse the last page of bills. Save bill information. Subscribers can query bills based on bill types. LMT provides subscriber interface for subscribers to select type of to-be-queried bills and enter query condition. When iGWB queries required bills, query results are displayed in a window. Logical expression of bill measurement is based on bill contents and can be configured flexibly. LMT provides expression modes, such as pie charts and histograms. LMT provides subscriber interface for subscribers to save bill browse contents in a text file so that subscribers can print bills.
WMFD-180500 Function name: CDR auto-deletion Description: iGWB support auto-deletion of original or final bills. Bills are saved in file form. When storage days of bill files pass, bill files are deleted automatically. Subscribers can set storage days of original bill files.
WMFD-180600
CONFIDENTIAL
Function name: CDR preprocessing Description: CDR preprocessing refers to sort bills and convert bill formats. Bill sort: iGWB sorts collected bills to corresponding paths based on sort conditions. With the definition of path brought forth by iGWB, iGWB stores collected bills based on sort conditions in different paths. You can configure bill sort conditions. Currently, the following two modes are supported: by bill types; by charging features. Bill format conversion: iGWB supports converting bills to those in text, binary or ASN.1 format based on operators requirements. Equipment vendor must coordinates with operators for specific fields contained in bills.
WMFD-180700 Function name: CDR auto-backup Description: iGWB can support automatic backup of original and final bills. After appropriate configuration, bills can be performed local backup or remote backup through network. Local backup: Back up files to local hard disks or other storage devices. Remote backup: Back up files to hard disks of remote devices.
WMFD-180800 Function name: System auto-switchover Description: System auto-switchover includes automatic synchronization, automatic switchover, and manual switchover supported by iGWB. iGWB can support automatic synchronization between dual-systems. If shared disk array is not installed in dual-system, activation node of dual-system can send status information of local end to peer end. iGWB can support automatic dual-system switchover. When current activation nodes are faulty, peer nodes can be switched over automatically. iGWB can support manual switchover of dual-system. Subscribers can implement manual switchover by operation at maintenance terminal.
WMFD-180900 Function name: User management Description: User management include: add a user; delete a user; modify user information; and authenticate a user.
CONFIDENTIAL
Add a user: Add a new user at iGWB maintenance terminal. To add a new user, administrator must enter username, user description, user authentication, and user passwords. Only administrator has rights to add new users. Delete a user: Delete an existing user through iGWB maintenance terminal. Only administrator has rights to delete a user. Modify user information: Modify existing user information through iGWB maintenance terminal. Administrator can modify information and passwords of all users. Common users can only modify their own information and passwords. Authenticate a user: Only valid users after authentication can log in to iGWB. iGWB can authenticate a user to judge whether users have rights to log in to operation and maintenance terminal or to execute a certain operation.
WMFD-181000 Function name: Log management Description: Users can perform the following operation through iGWB maintenance terminal: browse logs; view log details; save logs; and query logs. iGWB logs are classified into system logs and operation logs. Users can save log browse information to a text file and print log contents.
WMFD-181100 Function name: Alarm management Description: iGWB mainly supports the following alarms: Writing files failure Insufficient disk space Heartbeat link interruption Hard disk failure Charging interface failure If writing files failure occurs in the case of saving original and final bills or backing up bills, writing files failure alarm is generated. When the size of disk where original and final bills or backup bills are saved is smaller than a set value (can be configured), insufficient disk space alarm is generated. When all heartbeat links between iGWB dual-systems are interrupted, heartbeat link interruption alarm is generated. When iGWB detects that hard disk is faulty during periodical detection, hard disk failure alarm is generated. When final bills generated by iGWB are not transmitted to billing center within specified time (can be configured), charging interface failure alarm is generated.
CONFIDENTIAL
WMFD-181200 Function name: Performance management Description: iGWB can support performance management. The utilizations of CPU, memory and disk can be monitored in realtime and also displayed on the O&M client of iGWB.
WMFD-181300 Function name: Slide-window interface to MSC Description: iGWB supports self-defined slide-window protocol to MSC. This protocol can guarantee no duplication and no missing CDR happens between MSC and iGWB.
WMFD-190100 Function name: Automatic or manual switchover when main processing board faults Description: Switch over to standby boards automatically when main processing board is faulty, such as breakdown. Switch over active board to standby board manually in the case of special situations, such as network upgrade. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-190200 Function name: Load management when processor overloads Description: Activate flow control program when system processor overloads, so that mass congestion or breakdown of system is avoided.
CONFIDENTIAL
Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS
WMFD-190300 Function name: Fast system upgrade/restoration function Description: By using this function, upgrade of MSC Sever can be faster : If signaling links to another MSC/MGW are configured in BSG board with odd module number and BSG board with even module, the interrupt duration of upgrade can be less than 3 minutes, and duration of restoration can be limited to 5 minutes. The procedure of the upgrade/restoration is designed as following: First upgrade the backup boards of the system, and after finished all backup boards upgrade, revert all Main and Backup boards, then system is running with new version software, services are interrupt within the very limited duration. At last the upgrade the other half boards, then whole system upgrade is finished. Implemented node: VMSC/VLR, GMSC, and TMSC Serve Network: GSM and UMTS