1

INTRODUCTION

This document is a document to define a new GSM Traffic Model BAS4. BAS3 is a development of BAS1/BAS2. First, it contains changes of some old parameters, like increased SMS usage. Second, it introduces usage of new traffic services (like positioning and DTM). Third, some values are rounded and/or aligned with findings from the Common Ericsson Traffic Model project. BAS4 is the latest traffic model with addition of the new stuff. The data traffic has increased. BAS4 is a traffic model where CS and PS busy hour coincide and it is aligned with findings from the Common Ericsson Traffic Model. The focus is an average user behaviour model. Network data model is not included. 2 TRAFFIC MODELS, NUMBERS

See table on following pages and explanations to follow. BAS4 is a traffic model for the China (or Asia) market in an urban area, e.g. Shanghai, year 2014.
Part 1: CIRCUIT SWITCHED TRAFFIC MODEL Busy Hour Call Attempts (BHCA) Milli Erlang per CS subscriber Mobile originated call attempts (%) ... with B answer (%) ... duration when B answer (s) ... duration when no B answer (s) Mobile terminated call attempts (%) leading to Page (%) with B answer (%) ... duration when B answer (s) ... duration when no B answer (s) ... duration when no Page (s) Immediate Assignment on TCH (%) Share HR calls (%) whereof share Vamos Share EFR calls (%) whereof share Vamos Share AMRHR calls (%) whereof share Vamos Share AMRFR calls (%) whereof share Vamos Share AMRWB calls (%) whereof share Vamos Share MS-MS calls (%) (intra operator) Abis Local Switching MS-MS Selective authentication (1 out of.) Extra DTAPs SMS point-to-point BAS3 1.2 20 60 80 75 20 40 70 85 75 20 25 0 20 0 0 0 5 4 1.0 BAS4 1.7 30 60 70 85 20 40 80 70 85 30 30 5 0 0 5 0 50 40 35 0 10 20 35 0 5 8 4

... mobile originated SMS/ptp (%) ... characters per SMS/ptp Handovers per call share GSM handovers (%) whereof intra-BSC handovers whereof share intra-cell handovers (%) DTM per call Voice Activity Factor (VAF) Location Update Normal Location Update Periodic t P i di Location Update Attach / Detach Positionings, per subscriber and BH ... for already active MS (%) ... that need a page (%) ... assistance data size (octets) HSCSD data

40 160 1.00 85 0.02 0.50 0.20 0.50 0.2 64 16 200 0

25 160 1.5 95 80 35 0.1 60 0.5 0.5 0.5 0.2 64 16 200 0

Part 3: PACKET SWITCHED SUMMARY

BAS3 70 0.50 0.3

BAS4 80 0.5 3 500 7 3 40 8 25

GPRS devices being attached in BH (%) Sessions (flows) per subscriber and BH (DL+UL) Pagings per session (flow) Pagings per TBF (activity) BSC internal i DL Kbytes per session (flow) TBFs (activity) TBFs via CCCH (%) UL Kbytes per session (flow) TBFs (activity) TBFs via CCCH (%)

50 10 5 12 40 20

Management procedures: Attach + Detach /subscr. & BH PDP Context Activation /subscr. & BH RA Periodic Reg. /subscr. & BH RA Updates /subscr. & BH Cell Updates /subscriber & BH Average estimate from application input: Share EGPDCHs (%) Share EGPRS Data volume (%) 0.20 0.20 0.25 0.40 0.50 0.2 0.2 0.25 0.4 0.5

30

60 90

Share GPRS Data Volume (%) Appl. rate per EPDCH DL (Kbps) 3

10 16

TRAFFIC MODELS, EXPLANATIONS

Circuit Switched Traffic
Busy Hour Call Attempts (BHCA) per subscriber = This refers to all call attempts, mobile originated and terminated, successful and unsuccessful. This includes speech calls as well as (single slot) data calls (basically no difference to the BSC). Milli Erlang per subscriber = The traffic strength per subscriber on PLMN level. This also includes traffic to not active subscribers, i.e. diverted to announcing machines or similar. This part of the traffic does not reach BSS. Mobile originated (MO) call attempts (%) = The percentage of all call attempts that are mobile originated. ... (MO) with B answer (%) = The percentage of the mobile originated call attempts (see above) that are answered by the called party. ... (MO) duration when B answer (s) = The duration in case of mobile originated call with B answer (see above) expressed in seconds. Could include ring tone as well (preferably). ... (MO) duration when no B answer (s) = The duration in case of mobile originated call with no B answer, expressed in seconds. Typically ring tone. Mobile terminated (MT) call attempts (%) The fraction of call attempts that are not mobile originated, i.e. 100% minus mobile originated call fraction specified above.

... (MT) leading to page (%) = The fraction of all MS terminated call attempts that leads to page attempt. This basically depends on the fraction active (switchedon) mobiles, plus how well the activity supervision in the network works. Suppose you have 40% 'real' active subscribers (i.e. the fraction that is switched-on and within radio coverage). As 'registered' activity in VLR typically shows a higher figure (due to imperfections in supervision), maybe 50% of the MT call attempts leads to page. (In addition, some knowledge from calling party whether the mobile is attached or not can be assumed). Consequently, only 4 out of 5 page attempts will succeed (i.e. paging success rate equals 80%). Note: If active subscribers only are considered, this figure shall be close to 100%. See discussion for "BHCA per subscriber" above. ... (MT) with B answer (%) = The percentage of the page attempts (see above) that leads to B answer. ... (MT) duration when page and B answer (s) = The duration in case of mobile terminated call with B answer, expressed in seconds. Could include ring tone as well (preferably). The probably less frequent case 'page success but no B answer' is neglected (to simplify). ... (MT) duration when no B answer (s) = The duration in case of page attempt but no page answer, expressed in seconds. Typically the call is diverted to (e.g.) announcing machine. I.e. no Erlang in BSS, as only signalling is needed for paging. ... (MT) duration when no page attempt (s) = The duration in case of no page (due to e.g. MS registered as not active in VLR), expressed in seconds. Typically call is diverted to announcing machine or C number. Immediate Assign on TCH (%) = The percentage of all Immediate Assignment that skips the intermediate SDCCH channel and goes directly to TCH for call setup signalling (authentication, ciphering etc). Some operators activates this upon SDCCH congestion only. Share HR calls (%) = The percentage of all speech calls that use basic (non-AMR) halfrate coding.

Share VAMOS calls (%) = Share of Voice services over Adaptive Multi-user channels on One Slot which will give up to two full rate or four half rate connections on the same air timeslot. Share EFR calls (%) = The percentage of all speech calls that use enhanced full-rate coding. Share AMRHR calls (%) = The percentage of all speech calls that use AMR-based half-rate coding. Share AMRFR calls (%) = The percentage of all speech calls that use AMR-based full-rate coding. Note: The rest not specified by the 4 categories above are assumed to use standard FR (full-rate) coding. Share AMRWB calls (%) = The percentage of all speech calls that use AMR-WB coding. Note: The rest not specified by the 5 categories above are assumed to use standard FR (full-rate) coding. Share MS-MS calls (%) = The percentage of all speech calls that is intra operator MS to MS. Selective authentication on one out of n connections n = If selective authentication is used, the value here shall tell the number of successive accesses that can be performed without authentication. If authentication is made for all accesses (selective authentication is not used) the value should be set to 1. If authentication is not used at all, the figure shall be set to "something big", e.g. 10000. Extra DTAP messages per connection =

At set-up of call, registration etc, DTAP messages for CIPHERING and AUTHENTICATION (selective) are included. This relates to default value '0'. Depending on for example MSC settings, more DTAPs can be transferred (giving more load in BSC). The unit for this parameter is one DTAP message in one direction. The parameter is also considered to affect all three traffic cases (call set-up, registration and SMS). This means that if extra DTAPs are sent for only one traffic case (e.g. TMSI at location update) ExDtap should be increased by a factor less than 1. Also, DTMFlike services (such as number sending when checking bank account, or handling of Subscriber Services) may create extra DTAPs (in fact 4 for each figure sent /received). SMS) point-to-point, per subscriber and BH = This figure should give the total amount of Short Message Service (including Delivery Receipts) / point-to-point messages transferred to/from mobiles per subscriber and busy hour. are included in these figures. (Note that SMS cell broadcast is something completely different.)

... mobile originated SMS/ptp (%) = The percentage of SMS/ptp messages that are mobile originated. ... characters per SMS/ptp = The number of characters in the average SMS/ptp. Classic ptp messages are limited to 160. With concatenated ptp (supported by modern mobile phones), up to 39,000 characters can be transferred by one connection (/SMS). Handovers per call = Total number of (successful) handovers per call attempt. ... share intra-BSC handovers (%) = The fraction of handovers that are made between cells belonging to the same BSC. The remaining part is inter-BSC or intra-cell. (Whether they are intra- or inter MSC does not matter for BSC load.) As Ericsson BSCs are quite big, intra-BSC handovers typically dominate. Handovers to/from UMTS shall be counted as inter-BSC handovers. ... share intra-cell handovers (%) = The fraction of handovers that are made within a cell. DTM per call =

The number of DTM set-ups for the average (BHCA) call. The mobile initially has a CS call, then adds a PS connection. For example, 2% means each 50th call makes one DTM set-up. Location Updating, type Normal, per subscr. and BH = Amount of Location Updating type normal, both intra MSC (new LAI) and inter MSC (new registration). Alternatively, all types of registrations can be inserted here and the two types below set to zero. The load per registration in BSC is anyway assumed to be the same. Location Updating, type Periodic, per subscr. and BH = Amount of Location Updating type periodic. Location Updating, type IMSI Attach/Detach, per subscr. and BH = Amount of Location Updating type attach (/sub. registered before), type attach (/new registration) and type detach. Positionings per subscriber and BH = Number of positionings made by/for the average subscriber during busy hour. Excluded are simple SMS-based positionings (which actually shall be counted as SMSs, see above). Included is (the sum of) CGI+TA, A-GPS and U-TDOA positionings. (A requirement on R9 was that a BSC with 100,000 subscribers should handle 8 positionings/s. This corresponds to almost 0.3 positionings per average subscriber and busy hour.) ... positionings, for already active MS (%) = Share (%) of all positioning made for an MS already connected. ... positionings, that need a page (%) = Share (%) of positionings that need an initial page to find the mobile. ... positionings, assistance data size (octets) = In the positioning procedure, the "MS Positioning Command" message (see specification 09.31) is sent from SMLC to MS (embedding the "Measure Positioning Request" message, see specification 04.31). Included is assistance data to facilitate the positioning. The amount of data can be quite large. This is the case for an A-GPS positioning for a mobile not having done this for a long time (as the MS then is updated about satellite orbits etc). If such positionings are frequent, load impacts in CP as well as TRH, LAPD link and SDCCH channels may be noticed. For CGI+TA positioning, this message does not exist at all.

Packet Switched

GPRS devices being attached in BH (%) = The percentage of GPRS capable devices being GPRS attached during busy hour. Sessions per subscriber & Busy Hour = Number of GPRS sessions for the average subscriber with GPRS capability during busy hour. A session can be e.g. downloading a file, checking mail, sending MMS or visiting a WAP/web site. There is a 2 seconds timer for a session before it expires at inactivity. Pagings per activity (TBF) = Number of pagings needed for the average session. In some live networks, roughly one out of three sessions need page. One reason is that most sessions are mobile originated. Another that one page can be enough for more than one session (but less likely is that more than one paging is needed for one session). Down-link Kbytes per activity (TBF) = Total number of Kbytes (user data) sent from network to mobile per average session. Down-link TBFs per activity = Total number of down-link TBFs on average per session. Down-link TBFs via CCCH (%) = Percentage of TBFs that are sent via CCCH (the others are sent via PACCH). Up-link Kbytes per session = Total number of Kbytes (user data) sent from mobile to network per average session. Up-link TBFs per session = Total number of up-link TBFs per average session. Up-link TBFs via CCCH (%) = Percentage of TBFs that are received via CCCH (the others are received via PACCH). GPRS Attach/detach per subscriber and BH = Number of Attach/Detach procedures for the average GPRS subscriber during busy hour. PDP Context Activations per subscriber and BH =

Number of PDP Context Activation procedures for the average GPRS subscriber during busy hour. RA Periodic Registrations per subscriber and BH = Number of Periodic Routing Area Registration procedures for the average GPRS subscriber during busy hour. RA Updates per subscriber and BH = Number of Routing Area Update procedures for the average GPRS subscriber during busy hour (in addition to periodic ones above). Cell Updates per subscriber and BH = Number of Cell Update procedures for the average GPRS subscriber during Busy Hour. These are the correspondence to handovers in circuit switched traffic. Share EGPDCHs (%) = Percentage of all PDCHs that are EDGE (EPDCH) or CS3/CS4 (GPDCH) channels, i.e. the ones needing Abis connections of 64 Kbps. (The remaining ones, connected by 16 Kbps, are called BPDCHs.) Note that also non-EDGE capable mobiles might use EGPDCH channels, as these are allocated in the first place (when available in cell). Note also that the parameter "BPCs of 64 Kbps" above must be high enough for this one. Application rate per EPDCH DL (Kbps) = Average application data rate per EPDCH DL on Abis interface. In an early stage of GPRS, many GPRS mobiles may be around sending occasional updates but not doing much more. This means, average PDCH load was quite low (e.g. some bps in average). In a more mature network, peak hours on an EPDCH DL may see a rate close to maximum utilization (e.g. 10 Kbps or up to 16 Kbps).