71 test cases lte enb hot v1.1
DESCRIPTION
Test Cases Lte Enb HotTRANSCRIPT
-
Presentation / Author / Date1 Nokia Siemens Networks
LTE eNB Hands-on TrainingTest Cases
-
Presentation / Author / Date2 Nokia Siemens Networks
Nokia Siemens Networks Academy
Legal notice
Intellectual Property RightsAll copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.
-
Presentation / Author / Date3 Nokia Siemens Networks
Test Environment
MME
Flexi NS
HSS
Emulator PC
eNB
Flexi LBTS
Flexi NG
SGW PGW
SAE GW
Application Server
PC running Filezilla FTP
Server
UE
S1-MME
S1-U
S6a
SGi
LTE-UuTelecom
IP Network
PDN
Network Analyser
PC running Wireshark
LMTPC running BTS Local Maintenance Application (e.g. Site Manager or BTS log)
Logical interfacePhysical connection
Client PC
PC with UE manager, FTP Client, FTP Server and NetPerSec applications
The picture shows the basic network configuration to run all the test cases on this document. Detail network account (e.g. IP address, username and password) needs to be acquired from local lab support.
-
Presentation / Author / Date4 Nokia Siemens Networks
Test Cases
Case 1: Automatic Cell Setup Case 2: S6a Establishment Case 3: Inital Attach Case 4: Connection Management Case 5: Detach Case 6: FTP download Case 7: FTP upload
-
Presentation / Author / Date5 Nokia Siemens Networks
Case 1: Automatic Cell Setup
-
Presentation / Author / Date6 Nokia Siemens Networks
BTS Startup Overview
BTS Initialising
BTS Uncommissioned
BTS Commissioned
BTS Configured
BTS Integrated to RAN
BTS Test Dedicated State
BTS On Air
Power ON / reset
CDM (SCF file does not exist/ SCF file invalid/ BTS re-hosted)
SCF and RNW configuration file download
and reset
STUP (SCF exists in BTS, SCF parsed)
STUP (Ready check done, FD enabled)
STUP (S1 link connected)
STUP (at least one cell has operational state Enabled)
STUP (none of the cells is enabled)
STUP (TD state requested)
BTS can return to normal operation only after reset
-
Presentation / Author / Date7 Nokia Siemens Networks
Precondition eNB is installed and powered up. Physical interface between eNB and MME is connected. Configuration on
switch/router is needed if eNB and MME are not directly connected. MME is running with configured transport IP address on S1 interface. MME S11 interface is configured and available; routing to SAE GW needs
to be valid or MME will NOT respond to S1Setup Request from eNB. Necessary network configuration (e.g. MCC, MNC, MME code etc.) has
been done in MME. In MME SW load N1_1_18_0, this configuration is done as follow
Connect to OMUSet MCCZWVS:MCC=310;
Set MNCZWVS:MNC=089 ;
Set MME Code:ZWVF:MMEC=1;
Set MME Group ID:ZMVF:MMEGI:=10;
Note: N1_1_18 (Core 6) requires 3 digit MNC. Must be set to 3 digit on eNB as well as MME.
The example configuration as followPLMN: 262F01MME Group Id: 10MME Code: 1
ZDDS:MCHU,0;ZOS:*,*,9E1,,,,,6034,,,5,2,62,F2,10,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,10,00,FF,FF,FF,FF,FF,FF,FF,FF,01,FF,FF,FF,FF,00ZOS:*,*,9E1,,,,,6034,,,5,4,80ZE;
-
Presentation / Author / Date8 Nokia Siemens Networks
Test Execution
The eNB shows correct indication for every sequence.eNB operational state OnAir
Observe the automatic cell setup procedure
3
The eNB is restarting.Reboot the eNB to activate the new configurationOpen telnet session to FCMDGive reboot command
2
The file is succesfully copied.Copy the SCF_1.xml to eNB.Open ftp session to FCMDCopy the file to /rom/config directory
1
Expected resultProcedureStep
-
Presentation / Author / Date9 Nokia Siemens Networks
BTS log Printout During The eNodeB Start-up
DBG/LGC/CFM, SCF_1.xml found and parsed...INF/LGC/STUP, BTS Status is now Commissioned...INF/LGC/STUP, FD enabled...INF/LGC/STUP, Master started up (BTSState=Configured)...DBG/LTE TUP, SCTP_COMM_UP for address 10.31.171.9:49152 receivedDBG/LTE TUP 10.31.171.9:49152 found in dbDBG/LTE TUP Moving link=1 to state LinkStateOperational...INF/LGC/STUP, CStartManager: S1 link connected...INF/LGC/STUP, BTS Status is now IntegratedToRAN...INF/CELLC/CConfigCellcInstManagImpl.cpp#11 EutraCelId: 513INF/CELLC/CConfigCellcInstManagImpl.cpp#12 ENABLED...INF/LGC/STUP, BTS status is now OnAir
-
Presentation / Author / Date10 Nokia Siemens Networks
SCTP Association Establishment
eNB MMESCTP: INIT
SCTP: INIT_ACK
SCTP: COOKIE_ECHO
SCTP: COOKIE_ACK
SCTP: HEARTBEAT
SCTP: HEARTBEAT_ACK
SCTP: HEARTBEAT
SCTP: HEARTBEAT_ACK
...
SCTP establishment
SCTP link supervision
The initialization of an association is completed on both sides after the exchange of four messages. The passive side (called server, MME in S1 case) does not allocate resources until the third of these messages has arrived and been validated.
1. MME receives an association setup request (an INIT chunk).2. From the request, MME generates all the values needed at its side to enter an
established association and put into the so-called COOKIE. This COOKIE is returned to the sender of the INIT chunk in an INIT-ACK chunk.
3. Upon reception of a COOKIE-ECHO chunk, MME unpacks the data contained in this COOKIE to verify whether it was the originator of this COOKIE.
4. If it is a valid COOKIE, the MME will send a COOKIE-ACK to the eNBAfter all four messages have been exchanged, the SCTP association between MME and
eNB is established and both are ready to exchange SCTP data (S1AP messages).eNB sends a HEARTBEAT messages to monitor the tranmission path. This message has to
be acknowledged with HEARTBEAT_ACK.
-
Presentation / Author / Date11 Nokia Siemens Networks
S1 Setup Procedure
eNB MME
S1AP: S1 SETUP REQUEST
SCTP: SACK
S1AP: S1 SETUP RESPONSE
SCTP: SACK
eNB global ID, eNB name, supported TAs and Paging DRX configuration
ServedGUMMEI, Relative MME capacity
GUMMEI: Globally Unique MME IdentityTA: Tracking AreaDRX: Discontinue Reception
The S1 setup procedure shall be the first S1AP procedure triggered after the TNL association has become operational (after SCTP association establishment).The eNB initiates the procedure by sending a S1 SETUP REQUEST message including the appropriate data to the MME. The MME responds with S1 SETUP RESPONSE including the appropriate data.All S1 messages are treated as SCTP data, thus everytime either eNB or MME receives S1 message, it shall sends back selective acknowledge (SACK) chunk to its peer.
-
Presentation / Author / Date12 Nokia Siemens Networks
Handling Unexpected Situation
eNB stays in commissioned statePossible cause: eNB fails in performing internal configuration according to SCF.Workaround: Check the SCF_1.xml file, ensure all required parameters are set correctly and managed
object exist. (please refer to Commissioning and Integrating eNB chapter) S1 setup fails. eNB returns Error Indication after receiving S1 Setup Response
messagePossible cause: PLMN Id (MCC, MNC, MME code, MME group Id etc.) have not been set correctly in
MME.Workaround: Re-do the network configuration in MME.
S1Setup Request is ignored by MME (but SCTP connection is established) S11 Interface configuration needs to be valid on MME, ensure correct IP addresses are
used in mmeTRH.ini file and IP routing to SAE GW from S11 interface on MME is valid. Three digit MNC is required on MME and eNB when using Core 6 release on EPC.
-
Presentation / Author / Date13 Nokia Siemens Networks
S1 Setup Fails
eNB MME
S1AP: S1 SETUP REQUEST
S1AP: S1 SETUP RESPONSE
eNB global ID, eNB name, supported TAs and Paging DRX configuration
ServedGUMMEI, Relative MME capacity
S1AP: Error Indication
-
Presentation / Author / Date14 Nokia Siemens Networks
Case 2: S6a Establishment
-
Presentation / Author / Date15 Nokia Siemens Networks
S6a Establishment Overview The S6a Application is DIAMETER based application protocol*. It is carried over SCTP/IP S6a establishment follows the following step
SCTP association establishment MME HSS capability exchange
MME HSSDIAMETER: Capabilities-exchange Request
SCTP: SACK
DIAMETER: Capabilities-exchange Response
SCTP: SACK
* Diameter base protocol is specified RFC 3588** The Diameter application identifier assigned to the S6a interface application is 16777251 (allocated by IANA).
Supported-Vendor-Id:10415, Auth-Application-Id:16777251
Supported-Vendor-Id:10415, Auth-Application-Id:16777251
When two Diameter peers establish a transport connection, they MUST exchange the Capabilities Exchange messages. This message allows the discovery of a peer's identity and its capabilities.When establishing s6a connection, the following identifier must be included in Capabilities-exchange Request and Capabilties-exchange ResponseThe vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP fieldThe application identifier value of 3GPP S6a (16777251) shall be included in Auth-Application-Id AVP fieldAVP = Attribute Value Pairs.IANA = Internet Assigned Numbers Authority
-
Presentation / Author / Date16 Nokia Siemens Networks
Precondition HSS is up and running Necessary S6a configuration has been done in MME.
In MME SW load N1_1_18_0 this configuration is done as followConnect to SMMU ST:ZDDS:SMMU,0;
Enable T6ATESNX extension:ZLE:1,T6ATESNX;
Enable SCTP protocol:Z1P:S;
Set OriginHost and OrignRealm: mme2.syve.cic.nsn-rdnet.net, syve.cic.nsn-rdnet.netZ1O:"mme2.syve.cic.nsn-rdnet.net","syve.cic.nsn-rdnet.net";
Set DestinationHost and DestinationRealm: hip.hssdd-imscore.ims4.com, ims4.comZ1D:"hip.hssdd-imscore.ims4.com","ims4.com";
Set DestIP & port: 10.102.243.229:3868 (This is HSS S6a IP address)Z1I:"10.102.243.229",3868,0;
Set baseline version: 0=v8.1.0, 1=8.4.0Z1B:0;
Activate Connection (this will trigger S6a Diameter establishment with HSS)Z1C;
The example configuration as followOrigin host: mme1.code.muc.nsn-rdnet.net6d,6d,65,31,2e,63,6f,64,65,2e,6D,75,63,2e,6e, 73,6e,2d,72,64,6e,65,74,2e,6e,65,74,00,00,00,00,00,00,00,00Origin realm: code.muc.nsn-rdnet.net63,6F,64,65,2E,6D,75,63,2E,6E,73,6E,2D,72,64,6E,65,74,2E,6E,65,74,00,00,00,00,00,00,00,00,00,00,00,00,00Destination host: hssemu.muc.ims.net68,73,73,65,6D,75,2E,6D,75,63,2E,69,6D,73,2E,6E,65,74,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00Destination realm: muc.ims.net6D,75,63,2E,69,6D,73,2E,6E,65,74,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00Destination IP address and port number: 10.31.171.66:3868A,1F,AB,42,F,1C
-
Presentation / Author / Date17 Nokia Siemens Networks
HSS Parameter for S6a
[DIAMETER_1]entity_name=1ownhostdiaID= hssemu.muc.ims.netownrealm= muc.ims.netownhostip=10.31.171.66 (HSS S6a interface)ownport=3868productname=diameterPeerCount=1peerip_0=10.31.171.65 (MME S6a interface)peerport_0=3868peers6arole_0=1
-
Presentation / Author / Date18 Nokia Siemens Networks
Test Execution
The network analyser shows the following steps:
- SCTP association establishment between MME and HSS
- Capability exchange between MME and HSS
Activate S6a by using service terminal command on SMMUZOS:*,*,9C9,,,,,6034,,,9,0
3
The DIAMETER configuration is displayed correctly
Complete DIAMETER information on HSS (e.g. own host id, peer IP address etc.)
2
The MME configuration is displayed correctly
Complete MME information on HSS (e.g. PLMN Id, MME Id, IP address etc.)
1
Expected resultProcedureStep
-
Presentation / Author / Date19 Nokia Siemens Networks
Handling Unexpected Situation
S6a setup fails. HSS returns ABORT message during SCTP association establishment.Possible cause: HSS is down or not running properly.Workaround: Restart HSS and reinitialise S6a activation from MME Reactivate S6a interface on MME
ZDDS:SMMU; Z1C; If MME SMMU has restarted, you must enter all SMMU service terminal
commands under preconditions settings are lost on SMMU restart.
-
Presentation / Author / Date20 Nokia Siemens Networks
Case 3: Initial Attach
-
Presentation / Author / Date21 Nokia Siemens Networks
Initial Attach Overview The UE registers to network through initial attach procedure in order to get
services. The always-on IP connectivity for UE/users of the EPS is enabled by
establishing a default EPS bearer during Network Attachment . The initial attach procedure in LTE/SAE as follow.
StartStart
Authentication procedureAuthentication procedure
Security procedureSecurity procedure
Location Update procedureLocation Update procedure
Default bearer setupDefault bearer setup
FinishFinish
UE MMENAS: ATTACH REQUEST
NAS: ATTACH ACCEPT
NAS: ATTACH COMPLETE
eNB
Initial attach procedure is completed in 3 messages between UE and MME1. The UE initiates the Attach procedure by the transmission, to the eNodeB, of an Attach
Request.2. The MME sends an Attach Accept.3. The UE replies back with Attach Complete.In LTE/SAE, the attach procedure involves authentication procedure, security procedure,
location update procedure and default bearer. The default EPS bearer always be assigned to the UE during attach procedure. This requires a default PDN gateway information for the subscriber.
-
Presentation / Author / Date22 Nokia Siemens Networks
Precondition
eNB is up and working HSS is up and working MME is up and working, all interfaces are configured and
integrated (S1-MME, S6a and S11) SAE GW is configured and integrated at all interfaces (S1-U,
S11 and SGi). The physical connection between eNB and SAE GW is established successfully.
With N1_1_18_0 MME software release 3-digit MNC is required.
-
Presentation / Author / Date23 Nokia Siemens Networks
Test Execution
LLDM is started up.Start UE manager (LLDM) and prepare the automatic procedure .ini file
1
UE is powered on, find and select cell from the eNB.UE automatically performs attach to the network.We can observe the initial attach sequence on the network analyser.
Power on the UE (by connecting UE to the client PC) within the eNB coverage
2
Expected resultProcedureStep
-
Presentation / Author / Date24 Nokia Siemens Networks
Authentication Procedure
Authentication Vectors: RAND(i), KASME(i), XRES(i)
Authentication Data Response
NAS: attach Request
User Id, UE Capabilities, etc. Authentication Data Request
NAS: USER Authentication Request
KASME(i), RAND(i)
NAS: USER Authentication Response
RES(i) If RES(i)=XRES(i) Authentication successful
UE uses KASME to verify
the Network
UE eNB MME HSS
RAND is a random value KASME is an authentication parameter used, among other tasks, for
network authentication XRES is the UE expected result of the authentication computation
-
Presentation / Author / Date25 Nokia Siemens Networks
Security Procedure
The MME uses the NAS Security Mode Command (SMC) procedure to establish a NAS security association between the UE and MME, in order to protect the further NAS signalling messages.
NAS: Security Mode Command
NAS: Security Mode Complete
UE eNB MME
-
Presentation / Author / Date26 Nokia Siemens Networks
Location Update Procedure
MME HSS
DIAMETER: Update Location Request
SCTP: SACK
DIAMETER: Update Location Answer
SCTP: SACK
(MME Identity, IMSI, ME Identity, MME Capabilities, Update Type)
(IMSI, Subscription data)
Location update procedure initiated by the MME to update the UE presence in the HSS the MME sends an Update Location Request (MME Identity, IMSI, ME Identity, MME
Capabilities, Update Type) message to the HSS. The HSS acknowledges the Update Location message by sending an Update Location
Ack (IMSI, Subscription data) message to the new MME. The Subscription Data contain one or more PDN subscription contexts. Each PDN subscription context contains an 'EPS subscribed QoS profile' and the subscribed APN-AMBR.
-
Presentation / Author / Date27 Nokia Siemens Networks
Default Bearer Setup
GTP: Create Session Response
GTP: Create Session Request
NAS: Attach Accept
NAS: Attach Complete
UE eNB MME SAE GW
GTP: Modify Bearer Response
GTP: Modify Bearer Request
GTP: Echo Request
GTP: Echo Response
First uplink data
First downlink data
Default berer is setup in the following way1. MME sends Create session request to the SAE gateway.2. After the gateway creates new entry in EPS bearer context table, it will returns Create
session response to the MME.3. MME sends Attach accept including information of the default EPS bearer.4. The UE replies back to the MME with Attach complete. After this step, the UE can send
the uplink packets.5. MME sends Modify bearer request to the gateway including (EPS Bearer Identity,
eNodeB address, eNodeB TEID, Handover Indication).6. The gateway acknowledges by sending Modify Bearer Response then send its buffered
downlink packets.There is also a common mechanism for verifying connectivity from one endpoint to another
endpoint by sending Echo request and Echo response. If the other end does not respond the it can be treated as down and active connections will be deleted.
-
Presentation / Author / Date28 Nokia Siemens Networks
Handling Unexpected Situation
Default bearer setup fails.Possible cause Network configuration (e.g. IP address) are not set properlyWorkaround Verify network configuration in eNB (please refer to Commissioning and
Integrating eNB chapter) In addition, check whether the IP pool for UE and APN are configured in
SAE-GW
-
Presentation / Author / Date29 Nokia Siemens Networks
Case 4: Connection Management
-
Presentation / Author / Date30 Nokia Siemens Networks
Mobility Management Overview
EMM_Deregistered
ECM_Idle
Power On
Registration (Attach)
EMM_Registered
ECM_Connected
Allocate C-RNTI, S_TMSI Allocate IP addresses Authentication Establish security context
Release RRC connection Release C-RNTI Configure DRX for paging
EMM_Registered
ECM_Idle
Release due to Inactivity
Establish RRC ConnectionAllocate C-RNTI
New TrafficDeregistration (Detach)Change PLMN
Release C-RNTI, S-TMSI Release IP addresses
Timeout of Periodic TAUpdate
Release S-TMSI Release IP addresses
-
Presentation / Author / Date31 Nokia Siemens Networks
Precondition
eNB is up and working HSS is up and working MME is up and working, all interfaces are configured and
integrated (S1-MME, S6a and S11) SAE GW is configured and integrated at all interfaces (S1-U,
S11 and SGi). The physical connection between eNB and SAE GW is established successfully.
UE is on EMM_REGISTERED and ECM_Idle after previous test case (Initial Attach)
Periodic TA Update can be triggered by setting Periodic TA Update Timer in MME using ZEJ command group.
-
Presentation / Author / Date32 Nokia Siemens Networks
Test Execution
Ping is succcesfull, and state transition can be observed from network monitoring tool and UE managerUE move to ECM_CONNECTED
When UE on ECM_IDLE, trigger network test (ping) from Application Server to the UE
1
UE move back to ECM_IDLEStop the network testing2
Expected resultProcedureStep
-
Presentation / Author / Date33 Nokia Siemens Networks
Service Request (1/2)
From time to time a UE must switch from ECM_Idle to ECM_connected The reasons for this might be UL data is available, UL signaling is pending (e.g.
tracking area update, detach) or a paging from the network was received.
MMEServingGateway(SGW)
PDNGateway
Paging
S-TMSI, TAI/TAI-list
Service Request
DL Packet DataDL Packet NotificationPaging
S-TMSI
S-TMSI, TAI, service type
Authentication Requestauthentication challenge
Authentication ResponseAuthentication response
ECM_IDLE
ECM_CONNECTED
RRC_CONNECTED
May not exist if UE has been authenticated before
1. The UE sends the NAS message SERVICE REQUEST uplink via eNB to the MME. If there are multiple MME connected to the eNB it is the task of the eNB to select the right MME (the one the UE is registered with) from S-TMSI and TAI. The service type parameter indicates the above mentioned reason for the service request.
2. The MME can now start authentication if required.
-
Presentation / Author / Date34 Nokia Siemens Networks
Service Request (2/2)
MME
Initial Context Setup Req.
Update Bearer Request
eNB-S1 IP/TEIDUpdate Bearer Response
ServingGateway(SGW)
PDNGateway
SGW-S1 IP/TEID, QoSRB Establishment Req.
RB Establishment Rsp.Initial Context Setup Rsp.
eNB-S1 IP/TEID, ..
Ping request and reply
3. If the authentication is successfully completed the MME can start to re-establish the radio bearer and S1 tunnels for the active SAE bearers of the UE. Therefore it sends the S1-AP message INITIAL CONTEXT SETUP REQUEST to the eNB. This message contains the still active tunnel endpoint identifiers from SAE GW and request the eNB to create new radio bearers. If the eNB is done with it, it returns INITIAL CONTEXT SETUP RESPONSE in which it indicates its own tunnel endpoint identifiers for S1 interface.
4. These TEIDs of the eNB are now forwarded to the SAE GW with GTP-C UPDATE BEARER REQUEST. This completes the transition of the UE to LTE_ACTIVE.
-
Presentation / Author / Date35 Nokia Siemens Networks
S1 Release Procedure
MME
UE Context Release Request
Release Access Bearers Request
ServingGateway(SGW)
PDNGateway
UE Context Release Command
Release Access Bearers Response
RRC_IDLE
RRC Connection Release
UE Context Release Command
ECM_IDLE
-
Presentation / Author / Date36 Nokia Siemens Networks
Case 5: Detach
-
Presentation / Author / Date37 Nokia Siemens Networks
Detach Overview
Both UE and MME may trigger detach procedure. It will leads the UE to move from EMM_REGISTERED to EMM_DEREGISTERED state.
UE initiate detach procedure when requested by user via UE manager or it is powered off.
MME initiate detach procedure e.g. if the UE does not respond to periodic TA update.
The network may detach the UE implicitly (without notifying the UE). This is typically the case when the network presumes that it is not able to communicate with the UE, e.g. due to radio conditions.
-
Presentation / Author / Date38 Nokia Siemens Networks
Precondition
eNB is up and working. HSS is up and working. MME is up and working. SAE GW is up and working. UE has active network connection (attached to MME and has
at least a default bearer)
-
Presentation / Author / Date39 Nokia Siemens Networks
Test Execution
UE initiate detach procedure and the procedure can be completed, indicates by messages flow.
When UE has network connection, trigger detach from UE manager (LLDM application)
1
Expected resultProcedureStep
-
Presentation / Author / Date40 Nokia Siemens Networks
UE Initiated Detach
GTP: Delete Session Response
GTP: Delete Session RequestNAS: detach Request
NAS: detach Accept
UE eNB MME SAE GW
S1AP: UE Context Release Command
S1AP: UE Context Release Complete
-
Presentation / Author / Date41 Nokia Siemens Networks
MME Initiated Detach
GTP: Delete Session Response
GTP: Delete Session RequestNAS: detach Request
NAS: detach Accept
UE eNB MME SAE GW
S1AP: UE Context Release Command
S1AP: UE Context Release Complete
-
Presentation / Author / Date42 Nokia Siemens Networks
Case 6: FTP Download
-
Presentation / Author / Date43 Nokia Siemens Networks
Precondition
A network connectivity using UE as modem has been configured in Client PC.
Data generator or large size of data (>100 MB) is available in FTP server.
-
Presentation / Author / Date44 Nokia Siemens Networks
Test Execution
Data transfer is started and the speed speed can be observed on NetPerSec.
Start copying prepared file from ftp server to the client PC
4
The application displays the current data transfer speed
Run NetPerSec application3
The FTP connection is openedStart the FTP client application and open an FTP session to FTP server
2
The Client PC displays the network connectivity notification
Start the network connection on client PC using UE as modem
1
Expected resultProcedureStep
-
Presentation / Author / Date45 Nokia Siemens Networks
Case 7: FTP Upload
-
Presentation / Author / Date46 Nokia Siemens Networks
Precondition
A network connectivity using UE as modem has been configured in Client PC.
Data generator or large size of data (>100 MB) is available in Client PC.
-
Presentation / Author / Date47 Nokia Siemens Networks
Test Execution
Data transfer is started and the speed speed can be observed on NetPerSec.
Start copying prepared file from client PC to FTP server.
4
The application displays the current data transfer speed
Run NetPerSec application3
The FTP connection is openedStart the FTP client application and open an FTP session to FTP server
2
The Client PC displays the network connectivity notification
Start the network connection on client PC using UE as modem
1
Expected resultProcedureStep