WO2020229496A1 - Active test system for the mobile iot network and test method using such a test system - Google Patents

Active test system for the mobile iot network and test method using such a test system Download PDF

Info

Publication number
WO2020229496A1
WO2020229496A1 PCT/EP2020/063233 EP2020063233W WO2020229496A1 WO 2020229496 A1 WO2020229496 A1 WO 2020229496A1 EP 2020063233 W EP2020063233 W EP 2020063233W WO 2020229496 A1 WO2020229496 A1 WO 2020229496A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
iot
network
miot
probe
Prior art date
Application number
PCT/EP2020/063233
Other languages
French (fr)
Inventor
Shicheng Hu
Goce Talaganov
Vlad Bratu
Original Assignee
SIGOS GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US16/412,459 external-priority patent/US10848562B1/en
Priority claimed from DE102019207051.5A external-priority patent/DE102019207051A1/en
Application filed by SIGOS GmbH filed Critical SIGOS GmbH
Priority to CN202080036248.7A priority Critical patent/CN114208260B/en
Priority to JP2021568671A priority patent/JP2022533377A/en
Priority to EP20726055.5A priority patent/EP3970405A1/en
Priority to KR1020217038035A priority patent/KR20220008834A/en
Priority to AU2020274610A priority patent/AU2020274610A1/en
Publication of WO2020229496A1 publication Critical patent/WO2020229496A1/en
Priority to IL288084A priority patent/IL288084A/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/06—Testing, supervising or monitoring using simulated traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the invention relates to an active test system for a mobile IoT network. Further, the invention relates to a test method using such a test system.
  • Test systems for mobile networks are known e.g. from US 10,097,981 Bl, from US 7,831,249 B2 and from WO 2004/049746 Al.
  • US 9,768,893 Bl discloses a method and a device for isolating an over-the- air segment within a mobile communications network.
  • DE 10 2005 027 027 B4 discloses a method and a test system to authentify a mobile test device in a mobile communications network.
  • the test system is capable of performing test of a mobile IoT (Internet of Things) network providing connectivity and ren dering services to mobile IoT (MIoT) devices.
  • Such test is an active test i.e. requires at least one component to actively initiate a respective test method.
  • the central test unit or a part of it may be such component for actively initiating the test method.
  • the mobile IoT network to be tested is considered as a subtype of the in stalled 4G networks enhanced with LPWA (Low Power Wide Area) tech nologies for device power saving, enhanced coverage and transmitting a small amount of data, tolerant latency.
  • LPWA Low Power Wide Area
  • the LPWA technology installed can be LTE-M and/or NB-IoT.
  • the LPWA mobile device connected to the MIoT networks can be a smart me ter, a home automation device, a building automation device, part of a smart grid, a part of industrial production line or a pipeline management, a part of automotive, a part of a transportation device or logistics, a drone, a part of a home security device, part of a patient monitoring device, part of an agriculture device serving e.g. irrigation or shadowing, part of a street lighting device, part of a tracking device, part of an industrial asset man- agement device, part of a retail/point of sale device or part of a wearable device, e.g. part of a wristwatch or part of a smartphone.
  • voice ser vice via LTE-M can be tested.
  • the mobile IoT network may be connected via an Application Server to an MIoT application platform and/or an IoT application platform.
  • the test system can be adapted and install one or more test probes according to the IoT network architecture and the scalability.
  • the test probes can be placed at different locations (test fields) within a single IoT network or across multiple inter connected networks.
  • data communication embodied by a SIM of the mobile IoT device can be simulated and/or emulated either over the LTE-Uu radio interface or the S I core network interface.
  • the SIM multiplexer may transfer the SIM data virtually and/or securely to the at least one test probe.
  • the SIM multiplexer can be embodied as a support to carry multiple SIMs, e.g. up to 3 SIMs or more.
  • the test system can be configured to run a mobile IoT test procedure de ploying end-to-end active test methodology between the at least one test probe and the MIoT network under test.
  • the test system can be configured to control the test probe(s) via a specific active test platform including a central test unit. Furthermore, via the central test unit, the test system can automatically run IoT test procedures, can collect test results and can pro prise test reports and dashboards.
  • End-to-end testing means that connectivity between an MIoT device and an MIoT application server and services provided by an MIoT application to an MIoT device are tested by using a data transfer to and from the MIoT device, in particular to and from the at least one test probe representing and simulating the MIoT device.
  • the data transfer tests can be performed with different sizes of
  • test system can be designed for testing a capability of MIoT networks in deployment of power saving mode (PSM) and/or extended dis continuous reception (eDRX) for MIoT applications.
  • test sys tem can be designed for testing IoT application servers in an IoT applica tion platform.
  • the test system can be designed to configure and initiate at least one test probe to trigger and initiate at least one of the groups of a power saving mode (PSM) or extended discontinuous reception (eDRX) mode in the serving MIoT network under test.
  • PSM power saving mode
  • eDRX extended discontinuous reception
  • the test system may be designed for ne gotiation of the power saving mode and eDRX mode, in particular in com bination with the configuration and initiation of the test probe to evolved packet system (EPS) attach in the serving MIoT network under test.
  • EPS evolved packet system
  • the test system can be designed to configure and initiate at least one test probe to access and enquire an IoT application server by using a variety of protocols including but not limited to oneM2M, Hypercat, constrained ap plication protocol (CoAP), message queuing telemetry transport
  • protocols including but not limited to oneM2M, Hypercat, constrained ap plication protocol (CoAP), message queuing telemetry transport
  • MQTT/MQTT-SN real time streaming protocol
  • RTSP real time streaming protocol
  • JSON JavaScript object notation
  • XML exten sible mark-up language
  • references with respect to the oneM2M protocol can be accessed via www.onem2m.org.
  • Information regarding the protocol Hypercat can be found in John Davies, Hypercat: resource discovery on the internet of things (January 12, 2016): IEEE Internet of Things, March 2, 2017. availa ble via http://iot.ieee.org ⁇
  • Information regarding the protocol CoAP can be found via the standard RFC7252 which is available via
  • JSON can be found via the standards RFC8259 and ECMA-404.
  • Information about RTSP can be found via the standard RFC2326.
  • a signal and data exchange according to claim 2 enables a test of the most common signal message and data types with the test system.
  • a message structure according to claim 5 is suitable for IoT application platform testing.
  • protocols and/or interfaces which are applicble to communicate with such a test system are oneM2M, Hypercat, CoAP, RTSP, JSON, XML.
  • test method has the advantages described above with respect to the test system according to the invention.
  • the test method in particular is an end-to-end test method.
  • the test method in particular includes testing an IoT application platform, in particular servers of such platform.
  • the IoT ser vice availability of the network can be tested.
  • the test steps may be period ically repeated during the test method.
  • the test results recorded may be aggregated and may further be statistically evaluated.
  • a mobile IoT connectivity can be per formed.
  • the repeating step may be periodically repeated and the test results may be aggregated for further statistical evaluation.
  • an IoT network accessibility for the pinging test probe and/or a round-trip time of the ping/echo can be evaluated.
  • a power saving function of the respective mobile IoT device can be tested.
  • the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
  • mobile-terminated data transfer in combination with a power saving function to be managed by the IoT serving network under test may be tested by sending downlink data to wards the test probe during T3324 active timer running, verifying that the test probe receives the complete downlink data packets, monitoring and recording all test events and repeating the above-mentioned test according to a given schedule.
  • the repeating step may be periodically re- peated, and the test results may be aggregated for further statistical evalua tion.
  • mobile-terminated SMS in combination with power saving function to be managed by the IoT serving network un der test can be tested by sending an SMS to the test probe during T3324 active timer running, verifying that the test probe receives the SMS, moni toring and recording all test events and repeating the above-mentioned test according to a given test schedule.
  • the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
  • eDRX functionality can be tested and, in the consequence, the capability of further power saving functions can be evaluated.
  • the repeating step may be periodically re peated, and the test results may be aggregated for further statistical evalua tion.
  • mobile-terminated data transfer in combination with eDRx function to be managed by the IoT serving network under test can be tested by sending downlink data towards the test probe within the paging time window (PTW), verifying that the test probe receives the com plete downlink data packets, monitoring and recording all test events and repeating the above-mentioned test according to a given test schedule.
  • PGW paging time window
  • the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
  • mobile-terminated SMS in combina tion with eDRX function to be managed by the IoT serving network under test may be tested by sending an SMS to the test probe within the paging time window (PTW), verifying that the test probe receives the SMS, moni toring and recording all test events and repeating the above-mentioned test according to a given test schedule.
  • PGW paging time window
  • the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
  • a connect retainability and unso licited network-initiated detach request may be tested.
  • Data and SMS data delivery can be tested after and during power saving mode.
  • Figure 1 main components of an active test system for a mobile
  • IoT Internet of Things
  • radio in terface IoT (Internet of Things) network including at least one test probe connected to the IoT network via a radio in terface
  • Figure 2 in a depiction similar to figure 1, a further embodiment of a test system for a mobile IoT network including a test probe connected to the IoT network via an S 1 in terface;
  • Figure 3 in a depiction similar to figure 1, an embodiment of the test system configured to test an IoT serving network on test connection paths across roaming interfaces;
  • Figure 4 main components of an embodiment of the test system including two test probes configured to communicate with an IoT application platform of an IoT service via MQTT/MQTT-SN messages.
  • Figure 1 shows main components of an active test system 1 for a mobile IoT (Internet of Things) network 2 which is represented by a variety of communication lines shown in figure 1.
  • a communication line can be ei ther a pure signaling path, a signaling path embedding IoT data, or an IoT data transport path.
  • the mobile IoT (MIoT) network 2 provides connectivi- ty and services to mobile IoT devices of low power wide area (LPWA) technologies.
  • LPWA low power wide area
  • a used LPWA frequency bandwidth regularly is on a li censed spectrum.
  • the LPWA technology installed may be LTE-M, and/or NB-IoT.
  • Mobile IoT networks to be tested via the test system 1 may also install EC- GSM-IoT (Extended Coverage GSM IoT).
  • the other communication tech nologies may also be used for additional network access for machine-to- machine communications, such as Bluetooth Mesh Networking, Light- Fidelity (Li-Fi), Near-Field Communication (NFC), Wi-Fi, ZigBee or Z- Wave as examples for a wireless communication with short-range, LTE- Advanced or LTE-Standard as examples for medium-range wireless, Lo- RaWan, Sigfox, or Weightless, or Very Small Aperture Terminal (VSAT) as examples for long-range wireless communication and Ethernet or Pow er-Line Communication as examples for a wired communication.
  • Li-Fi Light- Fidelity
  • NFC Near-Field Communication
  • Wi-Fi Wireless Fidelity
  • ZigBee or Z- Wave as examples for a wireless communication with short-range
  • LTE- Advanced or LTE-Standard as examples
  • the test system 1 of figure 1 includes one or multiple test probes 3 which are components of a local unit 4 of the test system 1.
  • Figure 1 shows sever al examples of such local units 4.
  • the local unit 4 may include 1 to 4 or even more, e.g. up to 15 or more test probes 3.
  • the test probes 3 are con nected to the IoT network 2 via a radio interface 5.
  • Respective interfaces 5 together with LTE RAN (Radio Access Network) are schematically shown in figure 1 and may be embodied by a plurality of antenna sites.
  • a central test unit 5a is connected to the test probes 3 via an internet net work 7, 8.
  • Such connection may be a permanent secure IP connection, e.g. via a VPN server and an LTE/GPRS/EDGE/HSPA modem or may be a quasi-permanent IP connection which is established via a VPN server when required during testing.
  • the network 7 which may be a wireless backhaul network or a fixed IP network, includes the internet 8 and further includes components of an Evolved Packet Core (EPC) of a 3 GPP LTE communication standard.
  • EPC Evolved Packet Core
  • the components of the network 7 are also components of the IoT network 2, but this is not mandatory, some of the components of the network 7 may be independent from the IoT net work 2.
  • test clients 5b which also are connected to the network 7, 8 of the test system 1.
  • FIG. 1 Shown in figure 1 are two main test communication paths between the test probes 3 and an Application Server (AS) 6 acting as IoT platform.
  • a first, NB-IoT test communication path 9 runs from the attributed local radio in terface 5 via a Mobile Management Entity (MME), further there are two split alternatives, either via a Serving Gateway (S-GW) and a Packet Data Network Gateway (P-GW) and the network 7 to the AS / IoT platform 6 (so-called direct mode), or via the test path 11, and SCEF (service Capabil ity Exposure Function), Services Capability Server (SCS) and the network 7 to the AS / IoT platform 6 (so-called indirect mode).
  • MME Mobile Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • SCEF service Capabil ity Exposure Function
  • SCS Services Capability Server
  • a further LTE-M test communication path 10 runs directly from a local radio interface 5 to the S-GW, i.e. does not run via the MME, further via a Serving Gateway (S-GW) and a Packet Data Network Gateway (P-GW) and the network 7 to the AS / IoT platform 6.
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • SIM multiplexer 12 dispatches virtually the SIM data to the individual test probes in a fully secure and trusted way.
  • the SIM multiplexer which is part of the test system 1 is known from DE 10 2005 027 027 B4.
  • the local unit 4 and the local unit 16 are equipped with a SIM multiplexer support.
  • the local unit 4 may include a support to carry multiple SIMs, e.g. up to 3 SIMs or more.
  • the local unit 4 is placed in a designated test field and connected to the test system.
  • a plurality of test probes 3 is arranged at different and in particular widespread locations covering a large national or international area.
  • the at least one test probe 3 is configured to be placed either in a home IoT network under test for national IoT services test, or in a visiting IoT network under test for international IoT roaming services test.
  • the test system 1 is configured to run mobile IoT test procedures deploy ing end-to-end active test methodology between the at least one test probe 3 and the IoT network 2 under test.
  • test system 1 is configured to control the at least one test probe 3, is configured to automatically run the IoT test procedures, is configured to collect the test results and further is configured to produce test reports and/or dashboards.
  • the test system 1 is configured to exchange signaling messages, is config ured to transport IP data and/or non-IP data and/or SMS to and from the IoT network 2 under test.
  • the test communication paths via the internet network 8 between the test probes 3 and the IoT platform 6 include a MQTT/MQTT-SN client/server structure where the test probes 3 are the MQTT clients and the IoT plat form 6 is the server/MQTT broker.
  • the IoT application data stored in the IoT platform can be retrieved, evaluated and verified via the messaging protocol MQTT (Message Queuing Telemetry Transport).
  • SCS Services Capability Server
  • AS Application Server
  • the availability and quality of the serving IoT network 2 under test can be test ed.
  • the timing of the re spective test events can be monitored and recorded in the test central unit 5a.
  • the test methods explained are controlled by the test central unit 5a unless otherwise indicated.
  • test method includes the following steps:
  • the respective test probe 3 is configured via the test client 5b and initiated to an evolved packet system (EPS) attach in the serving IoT network 2 un der test. After the initiation of the EPS attach, the completion of the attach procedure, the received messages from the IoT network under test by the test probe 3 are verified by the test central unit 5a.
  • EPS evolved packet system
  • test events during the configuration, initiating and verifying steps are monitored and recorded. These test steps are repeated according to a given test schedule. In particular, such repeating may be a periodically repeating of test steps. Further, such multiple test results are aggregated and are for warded to a statistical evaluation and the test result is presented via the test client 5b to a human tester.
  • the test probe is initiated to ping a server in stalled in the serving IoT network 2 under test or an IoT network compo nent, e.g. P-GW.
  • The“ping” is done by using the respective IP software utility.
  • a power saving function to be managed by the IoT serving network 2 under test can be tested.
  • Such power saving function test includes the enabling of a power saving mode (PSM) at the respective test probe 3, hereby setting values of the T3324 active timer and the T3412 timer extended at the test probe 3 of the local unit 4.
  • PSM power saving mode
  • an EPS attach of the test probe 3 in the serving IoT network 2 is initiated and the comple tion of the attach procedure is verified.
  • TAU Tracking Area Update
  • the respective test probe 3 can wake up from a power saving status to a communication status.
  • wake up for instance may occur every week once for 2 minutes.
  • the EPS at tach procedure, such wake up duty cycle is negotiated.
  • the wake up function and in particular the status changes between the power saving status and the communication status are tested. Again, all test events during this test method are monitored and recorded and the above-mentioned test is repeated according to a given test sched ule.
  • an SMS is sent to the test probe 3 during T3324 active timer running.
  • an eDRX (Extended Discontinuous Reception) function to be managed by the IoT serving network 2 under test is tested.
  • eDRX is enabled, hereby setting values of the eDRX cycle length and of the paging time window (PTW) at the respective test probe 3 of the local unit 4.
  • PTW paging time window
  • an EPS attach of the test probe 3 in the serv ing IoT network 2 under test is initiated. A completion of such attach pro cedure is verified. Further, it is verified whether the eDRX cycle length and the PTW value are accepted by the service IoT network 2, comparing these values with the ones requested by the respective test probe 3. All test events of this method are monitored and recorded, and the above- mentioned test method is repeated according to a given test schedule.
  • test method mobile-terminated data transfer in combination with eDRX function to be managed by the IoT serving network 2 under test is tested.
  • downlink data are sent towards the respective test probe 3 within PTW (Paging Time Window). It is verified whether the test probe 3 receives the complete downlink data packets. All test events of this test method are monitored and recorded, and the above-mentioned test method is repeated according to a given test schedule.
  • PTW Paging Time Window
  • mobile-terminated SMS in combination with eDRX function to be managed by the IoT serving network 2 under test is tested.
  • an SMS is sent to the respective test probe 3 within PTW. It is verified whether the SMS is correctly delivered to the test probe. All test events during this test method are monitored and recorded. The above- mentioned test method is repeated according to a given test schedule.
  • the connection retainability of the IoT network 2 is tested. Here, it is verified whether the respective test probe 3 is requested by the service IoT network 2 for detach after an EPS attach or after mobile origination (MO) or mobile termination (MT) data transfer. This Performance tion step is repeated multiple times. The multiple test results of this test method are aggregated. From this aggregation, a default EPS bearer con text cut-off ratio is calculated.
  • IoT MO data transfer provided by the serving IoT network 2 under test is tested.
  • a TCP (Transmission Control Proto col) transport protocol is deployed.
  • a mobile originated IoT data transfer from the respective test probe 3 is initiated to an application server 6 located in a home network (HPMN). It is verified whether the IoT data is correctly received by the application server 6. This verification step is re peated multiple times and the multiple test results are aggregated, indicat ing the default EPS bearer context cut-off ratio.
  • an UDP User Datagram Protocol
  • NAS Non-Access Stratum
  • an IoT MT (Mobile Termination) data transfer provided by the serving IoT network 2 under test is tested.
  • an application server i.e. the server of the IoT platform 6 located in the home network is initiated to transmit IoT data to the respective test probe 3. It is verified whether the IoT data is completely received by the respective test probe 3. Further steps of this test method including deployment of the UDP transport protocol and deploy ment of the non-IP data delivery mechanism over NAS signaling, corre spond to those explained above with respect to the MO data transfer test method.
  • an MO SMS transmission via the serving IoT net work 2 under test is tested.
  • the respective test probe 3 is initiated to send an SMS to a partner test probe 3 of local unit 4 in the home network (HPMN). It than is verified whether the SMS is correctly received by the partner test probe 3.
  • HPMN home network
  • an MT SMS delivery via the serving IoT network 2 under test is tested.
  • a partner test probe 3 in a home network (HPMN) is initiated to send a SMS to the test probe 3 in the serving IoT network 2. It is verified whether the SMS submitted by the partner test probe 3’ is correctly delivered to the respective test probe 3 in the serving IoT network 2. Again, this test is repeated multiple times and the multiple test results are aggregated.
  • HPMN home network
  • FIG 2 a further embodiment of a test system 15 for a mobile IoT network is described. Components and functions which corre spond to those explained above with respect to figure 1 show the same ref erence numerals and are not discussed in detail again.
  • a central test unit, test clients and SIM multiplexer which also may be present in the test sys tem 15 in addition to a local unit are not shown in figure 2.
  • a local unit 16 including the test probes 3 is embod ied as S 1 core unit which is connected to the IoT network 2 via an S 1 inter face 17.
  • a communication line 18 via this S I interface 17 is realized as emulated eNodeB (Evolved NodeB). Details with respect to an embodi ment of an S 1 interface and the protocol can be found in 3GPP TS 36.413 V.15.5.0, Release 15, March 2019: "Evolved Universal Terrestrial Access Network (E-UTRAN); S I Application Protocol (S 1AP)".
  • Figure 3 shows another embodiment of a test system 20.
  • Components and functions which correspond to those already explained with respect to fig ures 1 and 2 have the same reference numerals and are not discussed in detail again.
  • the test system 20 provides test for connectivity and services to mobile IoT devices in roaming conditions.
  • communication via lines 9, 10 and 11 is done between a home public mobile network (HPMN) and a vis iting public mobile network (VPMN) across a border 21.
  • HPMN home public mobile network
  • VPMN vis iting public mobile network
  • IWK-SCEF interworking SCEF
  • Figure 4 shows components of a further embodiment of a test system for a mobile IoT network including details with respect to testing data transfer between different test probes 3, 3’ wherein such different test probes 3, 3’ may be attributed to different, e.g. home/visiting, public mobile networks.
  • Components and functions which correspond to those explained above with respect to figures 1 to 3 have the same reference numerals and are not dis cussed in detail again.
  • test probe 3 is connected to the IoT platform 6 via a test communication path 22 which can include a radio interface 5 or a S I interface 17.
  • the test probe 3 includes an MQTT/MQTT-SN client 23 which communicates via the communication line 22 with an
  • test probe 3 communicates in figure 4 with the IoT platform 6 under test via another test communication path 25 which also may include a radio interface 5 or an S I interface 17.
  • test communication path 25 which also may include a radio interface 5 or an S I interface 17.
  • the fur ther test probe 3’ also includes an MQTT/MQTT-SN client 23’.
  • At least one of the fol lowing further protocols and/or one of the following device specific inter faces may be used: oneM2M, Hypercat, CoAP, RTSP, JSON, XML.
  • Use of a specific protocol/interface depends on the respective IoT device and/or the respective application.
  • CoAP is suitable for con strained networks having low bandwidth and low power.
  • the test probe 3, 3’ may be part of a moving device, i.e. may be part of a vehicle, e.g. a bike or a car.
  • the test device may initiate a track ing area update each time the respective test probe 3 enters a new tracking area within the MIoT network 2. After such tracking area update, data as signed to the PSM and/or assigned to the eDRX function may be renegoti- ated and/or overridden by initiation of the test system.
  • the relevant IoT data sent by test probe 3 and stored in the platform under test 6 can be retrieved by the test probes 3’.
  • the retrieved data is compared with the original data sent.
  • the corresponding test verdict can be assigned.
  • test probes 3, 3’ may be placed in the same home network. Alterna tively and as indicated in figure 4, the test probes 3 and 3’ may be located within separated networks. For example, and as shown in figure 4, the test probe 3 may be placed in a visiting public network VPMN and the further test probe 3’ may be located in a home public mobile network HPMN.
  • IoT application platform tests under IoT device roaming as explained above can be globally carried out.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

An active test system (1) for a mobile IoT network (2) providing connectivity and services to mobile IoT (MIoT) devices of low power wide area (LPWA) technologies is presented. The test system has at least one test probe (3) connected to the MIoT network (2) via an LTE-Uu interface (5) and/or at least one test probe connected to the MIoT network via an S1 interface. A central test unit (5a) is connected (8) to the at least one test probe (3) via a wireless backhaul network or a fixed IP network (7). A SIM multiplexer (12) is provided to transfer SIM data to the at least one test probe (3) in test fields. A test system with enhanced capabilities assure mobile IoT experience.

Description

Active test system for the mobile IoT network and test method using such a test system
The present application claims priority of German patent application DE 10 2019 207 051.5 and US patent application US 16/412 459 the content of which is incorporated herein by reference.
The invention relates to an active test system for a mobile IoT network. Further, the invention relates to a test method using such a test system.
Test systems for mobile networks are known e.g. from US 10,097,981 Bl, from US 7,831,249 B2 and from WO 2004/049746 Al.
US 9,768,893 Bl discloses a method and a device for isolating an over-the- air segment within a mobile communications network. DE 10 2005 027 027 B4 discloses a method and a test system to authentify a mobile test device in a mobile communications network.
It is an object of the invention to enhance the capabilities of such a test sys tem for testing mobile networks.
The object is met by an active test system including the features of claim 1.
The test system according to the invention is capable of performing test of a mobile IoT (Internet of Things) network providing connectivity and ren dering services to mobile IoT (MIoT) devices. Such test is an active test i.e. requires at least one component to actively initiate a respective test method. For example, the central test unit or a part of it may be such component for actively initiating the test method. The mobile IoT network to be tested is considered as a subtype of the in stalled 4G networks enhanced with LPWA (Low Power Wide Area) tech nologies for device power saving, enhanced coverage and transmitting a small amount of data, tolerant latency.
The LPWA technology installed can be LTE-M and/or NB-IoT. The LPWA mobile device connected to the MIoT networks can be a smart me ter, a home automation device, a building automation device, part of a smart grid, a part of industrial production line or a pipeline management, a part of automotive, a part of a transportation device or logistics, a drone, a part of a home security device, part of a patient monitoring device, part of an agriculture device serving e.g. irrigation or shadowing, part of a street lighting device, part of a tracking device, part of an industrial asset man- agement device, part of a retail/point of sale device or part of a wearable device, e.g. part of a wristwatch or part of a smartphone. Also, voice ser vice via LTE-M can be tested.
The mobile IoT network may be connected via an Application Server to an MIoT application platform and/or an IoT application platform.
With such test systems, an MIoT network connectivity test, and/or an MI oT application platform test can be performed. The test system can be adapted and install one or more test probes according to the IoT network architecture and the scalability. The test probes can be placed at different locations (test fields) within a single IoT network or across multiple inter connected networks. In particular, data communication embodied by a SIM of the mobile IoT device can be simulated and/or emulated either over the LTE-Uu radio interface or the S I core network interface. The SIM multiplexer may transfer the SIM data virtually and/or securely to the at least one test probe. The SIM multiplexer can be embodied as a support to carry multiple SIMs, e.g. up to 3 SIMs or more.
The test system can be configured to run a mobile IoT test procedure de ploying end-to-end active test methodology between the at least one test probe and the MIoT network under test. The test system can be configured to control the test probe(s) via a specific active test platform including a central test unit. Furthermore, via the central test unit, the test system can automatically run IoT test procedures, can collect test results and can pro duce test reports and dashboards.
Within the test system, the test methods and test sequences are deployed to test MIoT applications and/or services running beyond the IoT connectivity provided by the MIoT network under test. “End-to-end” testing means that connectivity between an MIoT device and an MIoT application server and services provided by an MIoT application to an MIoT device are tested by using a data transfer to and from the MIoT device, in particular to and from the at least one test probe representing and simulating the MIoT device.
In particular, it is tested whether the service data flow of an application is behaving as expected from start to completion. In particular, all steps of an application and/or of a service are tested. Download and upload data speeds and/or download/upload bandwidths can be tested.
The data transfer tests can be performed with different sizes of
sent/received data, in particular with different number of data packets and/or different data volumes.
Data transfer quality and also data transfer integrity can be tested.
Further, the test system can be designed for testing a capability of MIoT networks in deployment of power saving mode (PSM) and/or extended dis continuous reception (eDRX) for MIoT applications. Further, the test sys tem can be designed for testing IoT application servers in an IoT applica tion platform.
The test system can be designed to configure and initiate at least one test probe to trigger and initiate at least one of the groups of a power saving mode (PSM) or extended discontinuous reception (eDRX) mode in the serving MIoT network under test. The test system may be designed for ne gotiation of the power saving mode and eDRX mode, in particular in com bination with the configuration and initiation of the test probe to evolved packet system (EPS) attach in the serving MIoT network under test.
The test system can be designed to configure and initiate at least one test probe to access and enquire an IoT application server by using a variety of protocols including but not limited to oneM2M, Hypercat, constrained ap plication protocol (CoAP), message queuing telemetry transport
(MQTT/MQTT-SN), real time streaming protocol (RTSP) or via device specific interfaces such as JavaScript object notation (JSON) and/or exten sible mark-up language (XML) over HTTP.
References with respect to the oneM2M protocol can be accessed via www.onem2m.org. Information regarding the protocol Hypercat can be found in John Davies, Hypercat: resource discovery on the internet of things (January 12, 2016): IEEE Internet of Things, March 2, 2017. availa ble via http://iot.ieee.org· Information regarding the protocol CoAP can be found via the standard RFC7252 which is available via
https://tools.ietf. org/html/rfc 7252. Information about JSON can be found via the standards RFC8259 and ECMA-404. Information about RTSP can be found via the standard RFC2326.
A signal and data exchange according to claim 2 enables a test of the most common signal message and data types with the test system.
Configurations according to claim 3 have been proven to be essential for the most common testing requirements.
This in particular holds true for the test system according to claim 4.
A message structure according to claim 5 is suitable for IoT application platform testing. Alternatively or in addition, protocols and/or interfaces which are applicble to communicate with such a test system are oneM2M, Hypercat, CoAP, RTSP, JSON, XML.
A test method according to claim 6 has the advantages described above with respect to the test system according to the invention. The test method in particular is an end-to-end test method. The test method in particular includes testing an IoT application platform, in particular servers of such platform.
With the method according to claim 7, by simulating /emulating respective mobile IoT devices with the test probe within the IoT network, the IoT ser vice availability of the network can be tested. The test steps may be period ically repeated during the test method. The test results recorded may be aggregated and may further be statistically evaluated.
With the test method of claim 8, a mobile IoT connectivity can be per formed. Here again, the repeating step may be periodically repeated and the test results may be aggregated for further statistical evaluation.
Via such ping test, an IoT network accessibility for the pinging test probe and/or a round-trip time of the ping/echo can be evaluated.
With the test method according to claim 9, a power saving function of the respective mobile IoT device can be tested. Here again, the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
As part of such power saving test method, mobile-terminated data transfer in combination with a power saving function to be managed by the IoT serving network under test may be tested by sending downlink data to wards the test probe during T3324 active timer running, verifying that the test probe receives the complete downlink data packets, monitoring and recording all test events and repeating the above-mentioned test according to a given schedule. Here again, the repeating step may be periodically re- peated, and the test results may be aggregated for further statistical evalua tion.
Further, in such power saving test, mobile-terminated SMS in combination with power saving function to be managed by the IoT serving network un der test can be tested by sending an SMS to the test probe during T3324 active timer running, verifying that the test probe receives the SMS, moni toring and recording all test events and repeating the above-mentioned test according to a given test schedule. Here again, the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
In a test method according to claim 10, eDRX functionality can be tested and, in the consequence, the capability of further power saving functions can be evaluated. Here again, the repeating step may be periodically re peated, and the test results may be aggregated for further statistical evalua tion.
In such eDRX test method, mobile-terminated data transfer in combination with eDRx function to be managed by the IoT serving network under test can be tested by sending downlink data towards the test probe within the paging time window (PTW), verifying that the test probe receives the com plete downlink data packets, monitoring and recording all test events and repeating the above-mentioned test according to a given test schedule. Here again, the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
Further, in such eDRX test method, mobile-terminated SMS in combina tion with eDRX function to be managed by the IoT serving network under test may be tested by sending an SMS to the test probe within the paging time window (PTW), verifying that the test probe receives the SMS, moni toring and recording all test events and repeating the above-mentioned test according to a given test schedule. Here again, the repeating step may be periodically repeated, and the test results may be aggregated for further statistical evaluation.
With a test method according to claim 11, a connect retainability and unso licited network-initiated detach request may be tested.
With a test method of claim 12, mobile origination (MO) data transfer can be tested.
With the test method of claim 13, mobile termination (MT) data transfer can be tested.
With the test method according to claim 14, mobile originated SMS trans mission can be tested.
With the test method according to claim 15, mobile terminated SMS deliv ery can be tested.
Data and SMS data delivery can be tested after and during power saving mode.
Exemplary embodiments of the invention are further described with refer ence to the accompanying drawings. It is shown in: Figure 1 main components of an active test system for a mobile
IoT (Internet of Things) network including at least one test probe connected to the IoT network via a radio in terface;
Figure 2 in a depiction similar to figure 1, a further embodiment of a test system for a mobile IoT network including a test probe connected to the IoT network via an S 1 in terface;
Figure 3 in a depiction similar to figure 1, an embodiment of the test system configured to test an IoT serving network on test connection paths across roaming interfaces; and
Figure 4 main components of an embodiment of the test system including two test probes configured to communicate with an IoT application platform of an IoT service via MQTT/MQTT-SN messages. Figure 1 shows main components of an active test system 1 for a mobile IoT (Internet of Things) network 2 which is represented by a variety of communication lines shown in figure 1. A communication line can be ei ther a pure signaling path, a signaling path embedding IoT data, or an IoT data transport path. The mobile IoT (MIoT) network 2 provides connectivi- ty and services to mobile IoT devices of low power wide area (LPWA) technologies. A used LPWA frequency bandwidth regularly is on a li censed spectrum. The LPWA technology installed may be LTE-M, and/or NB-IoT. Throughout this application, in particular with respect to the standardized specifications of IoT networks, it is referred to the following references:
GSM Association; official document CLP.28-NB-IoT Deployment Guide to Basic Feature set Requirements, version 1.0, August 2, 2017 (White Paper of the GSMA);
Technical specification 3GPP TS 23.682, V.15.8.0, Release 15, March 2019.
Mobile IoT networks to be tested via the test system 1 may also install EC- GSM-IoT (Extended Coverage GSM IoT). The other communication tech nologies may also be used for additional network access for machine-to- machine communications, such as Bluetooth Mesh Networking, Light- Fidelity (Li-Fi), Near-Field Communication (NFC), Wi-Fi, ZigBee or Z- Wave as examples for a wireless communication with short-range, LTE- Advanced or LTE-Standard as examples for medium-range wireless, Lo- RaWan, Sigfox, or Weightless, or Very Small Aperture Terminal (VSAT) as examples for long-range wireless communication and Ethernet or Pow er-Line Communication as examples for a wired communication.
The test system 1 of figure 1 includes one or multiple test probes 3 which are components of a local unit 4 of the test system 1. Figure 1 shows sever al examples of such local units 4. The local unit 4 may include 1 to 4 or even more, e.g. up to 15 or more test probes 3. The test probes 3 are con nected to the IoT network 2 via a radio interface 5. Respective interfaces 5 together with LTE RAN (Radio Access Network) are schematically shown in figure 1 and may be embodied by a plurality of antenna sites. A central test unit 5a is connected to the test probes 3 via an internet net work 7, 8. Such connection may be a permanent secure IP connection, e.g. via a VPN server and an LTE/GPRS/EDGE/HSPA modem or may be a quasi-permanent IP connection which is established via a VPN server when required during testing.
In the embodiment of figure 1, the network 7, which may be a wireless backhaul network or a fixed IP network, includes the internet 8 and further includes components of an Evolved Packet Core (EPC) of a 3 GPP LTE communication standard. In general, the components of the network 7 are also components of the IoT network 2, but this is not mandatory, some of the components of the network 7 may be independent from the IoT net work 2.
Further parts of the test system 1 shown on the left side of figure 1 are test clients 5b which also are connected to the network 7, 8 of the test system 1.
Shown in figure 1 are two main test communication paths between the test probes 3 and an Application Server (AS) 6 acting as IoT platform. A first, NB-IoT test communication path 9 runs from the attributed local radio in terface 5 via a Mobile Management Entity (MME), further there are two split alternatives, either via a Serving Gateway (S-GW) and a Packet Data Network Gateway (P-GW) and the network 7 to the AS / IoT platform 6 (so-called direct mode), or via the test path 11, and SCEF (service Capabil ity Exposure Function), Services Capability Server (SCS) and the network 7 to the AS / IoT platform 6 (so-called indirect mode).
A further LTE-M test communication path 10 runs directly from a local radio interface 5 to the S-GW, i.e. does not run via the MME, further via a Serving Gateway (S-GW) and a Packet Data Network Gateway (P-GW) and the network 7 to the AS / IoT platform 6.
All test probes are equipped with SIM. Connected to the internet 8, a SIM multiplexer 12 dispatches virtually the SIM data to the individual test probes in a fully secure and trusted way. The SIM multiplexer which is part of the test system 1 is known from DE 10 2005 027 027 B4.
The local unit 4 and the local unit 16 are equipped with a SIM multiplexer support.
Alternatively, to a SIM multiplexer support, the local unit 4 may include a support to carry multiple SIMs, e.g. up to 3 SIMs or more.
The local unit 4 is placed in a designated test field and connected to the test system. In praxis, a plurality of test probes 3 is arranged at different and in particular widespread locations covering a large national or international area. As a consequence, the at least one test probe 3 is configured to be placed either in a home IoT network under test for national IoT services test, or in a visiting IoT network under test for international IoT roaming services test.
The test system 1 is configured to run mobile IoT test procedures deploy ing end-to-end active test methodology between the at least one test probe 3 and the IoT network 2 under test.
Further, the test system 1 is configured to control the at least one test probe 3, is configured to automatically run the IoT test procedures, is configured to collect the test results and further is configured to produce test reports and/or dashboards.
The test system 1 is configured to exchange signaling messages, is config ured to transport IP data and/or non-IP data and/or SMS to and from the IoT network 2 under test.
The test communication paths via the internet network 8 between the test probes 3 and the IoT platform 6 include a MQTT/MQTT-SN client/server structure where the test probes 3 are the MQTT clients and the IoT plat form 6 is the server/MQTT broker. The IoT application data stored in the IoT platform can be retrieved, evaluated and verified via the messaging protocol MQTT (Message Queuing Telemetry Transport).
As further components within the networks and/or communication paths may serve a Services Capability Server (SCS) and/or an Application Server (AS). With respect to the arrangement of such SCS/AS it is referred to the technical specification 3GPP TS 23.682, in particular to figure 4.2- la.
Further possible interfaces may work according to the standardized S6a,
S8, SGd or T7 roaming interfaces.
Via the test methods or test procedures carried out by the test system 1, the availability and quality of the serving IoT network 2 under test can be test ed. During the service availability test, in particular the timing of the re spective test events can be monitored and recorded in the test central unit 5a. The test methods explained are controlled by the test central unit 5a unless otherwise indicated.
An example of such a test method includes the following steps:
The respective test probe 3 is configured via the test client 5b and initiated to an evolved packet system (EPS) attach in the serving IoT network 2 un der test. After the initiation of the EPS attach, the completion of the attach procedure, the received messages from the IoT network under test by the test probe 3 are verified by the test central unit 5a.
All test events during the configuration, initiating and verifying steps are monitored and recorded. These test steps are repeated according to a given test schedule. In particular, such repeating may be a periodically repeating of test steps. Further, such multiple test results are aggregated and are for warded to a statistical evaluation and the test result is presented via the test client 5b to a human tester.
In a particular test method, the test probe is initiated to ping a server in stalled in the serving IoT network 2 under test or an IoT network compo nent, e.g. P-GW.
The“ping” is done by using the respective IP software utility.
After such ping procedure, its completion is verified and again all test events are monitored and recorded, and the test steps are repeated accord ing to the given test schedule. In a further test method, a power saving function to be managed by the IoT serving network 2 under test can be tested. Such power saving function test includes the enabling of a power saving mode (PSM) at the respective test probe 3, hereby setting values of the T3324 active timer and the T3412 timer extended at the test probe 3 of the local unit 4. Then, an EPS attach of the test probe 3 in the serving IoT network 2 is initiated and the comple tion of the attach procedure is verified. In addition, it is verified whether the timer values are accepted by the service IoT network 2. This is done by comparing these values with the ones requested by the respective test probe 3. In addition, it is verified whether the extended periodic Tracking Area Update (TAU) procedure is completed. Again, all test events during this test method are monitored and recorded and the above-mentioned test is repeated according to the given schedule.
In a further test method, mobile-terminated data transfer in combination with the power saving function (PSM) to be managed by the IoT serving network 2 under test is tested. To this end, downlink data towards the re spective test probe 3 are sent during a time span the T3324 active timer is running. It is verified that the respective test probe 3 receives the complete downlink data packets.
With help of the PSM, it is verified whether the respective test probe 3 can wake up from a power saving status to a communication status. Such wake up for instance may occur every week once for 2 minutes. In the EPS at tach procedure, such wake up duty cycle is negotiated. During the test method, the wake up function and in particular the status changes between the power saving status and the communication status are tested. Again, all test events during this test method are monitored and recorded and the above-mentioned test is repeated according to a given test sched ule.
In a further test method, testing mobile-terminated SMS in combination with power saving function to be managed by the IoT serving network 2 under test, an SMS is sent to the test probe 3 during T3324 active timer running.
It than is verified whether the SMS is correctly delivered to the test probe. All test events during this test methods again are monitored and recorded, and the above-mentioned test method is repeated according to a given test schedule.
In a further test method, an eDRX (Extended Discontinuous Reception) function to be managed by the IoT serving network 2 under test is tested. In this method eDRX is enabled, hereby setting values of the eDRX cycle length and of the paging time window (PTW) at the respective test probe 3 of the local unit 4. In addition, an EPS attach of the test probe 3 in the serv ing IoT network 2 under test is initiated. A completion of such attach pro cedure is verified. Further, it is verified whether the eDRX cycle length and the PTW value are accepted by the service IoT network 2, comparing these values with the ones requested by the respective test probe 3. All test events of this method are monitored and recorded, and the above- mentioned test method is repeated according to a given test schedule.
In a further test method, mobile-terminated data transfer in combination with eDRX function to be managed by the IoT serving network 2 under test is tested. Here, downlink data are sent towards the respective test probe 3 within PTW (Paging Time Window). It is verified whether the test probe 3 receives the complete downlink data packets. All test events of this test method are monitored and recorded, and the above-mentioned test method is repeated according to a given test schedule.
In a further test method, mobile-terminated SMS in combination with eDRX function to be managed by the IoT serving network 2 under test is tested. Here, an SMS is sent to the respective test probe 3 within PTW. It is verified whether the SMS is correctly delivered to the test probe. All test events during this test method are monitored and recorded. The above- mentioned test method is repeated according to a given test schedule. In a further test method, the connection retainability of the IoT network 2 is tested. Here, it is verified whether the respective test probe 3 is requested by the service IoT network 2 for detach after an EPS attach or after mobile origination (MO) or mobile termination (MT) data transfer. This verifica tion step is repeated multiple times. The multiple test results of this test method are aggregated. From this aggregation, a default EPS bearer con text cut-off ratio is calculated.
In a further method, IoT MO data transfer provided by the serving IoT network 2 under test is tested. Here, a TCP (Transmission Control Proto col) transport protocol is deployed. Further, a mobile originated IoT data transfer from the respective test probe 3 is initiated to an application server 6 located in a home network (HPMN). It is verified whether the IoT data is correctly received by the application server 6. This verification step is re peated multiple times and the multiple test results are aggregated, indicat ing the default EPS bearer context cut-off ratio. In addition, an UDP (User Datagram Protocol) is deployed and the above-mentioned IoT MO data transfer test is repeated. In addition, a non-IP data delivery mechanism over NAS (Non-Access Stratum) signaling is deployed. Again, the IoT MO data transfer test is repeated.
In a further test method, an IoT MT (Mobile Termination) data transfer provided by the serving IoT network 2 under test is tested. Here, after de ploying of a TCP transport protocol, an application server, i.e. the server of the IoT platform 6 located in the home network is initiated to transmit IoT data to the respective test probe 3. It is verified whether the IoT data is completely received by the respective test probe 3. Further steps of this test method including deployment of the UDP transport protocol and deploy ment of the non-IP data delivery mechanism over NAS signaling, corre spond to those explained above with respect to the MO data transfer test method.
In a further test method, an MO SMS transmission via the serving IoT net work 2 under test is tested. Here, the respective test probe 3 is initiated to send an SMS to a partner test probe 3 of local unit 4 in the home network (HPMN). It than is verified whether the SMS is correctly received by the partner test probe 3. This test is repeated multiple times and the multiple test results are aggregated for further statistical evaluation.
In a further test method, an MT SMS delivery via the serving IoT network 2 under test is tested. Here, a partner test probe 3 in a home network (HPMN) is initiated to send a SMS to the test probe 3 in the serving IoT network 2. It is verified whether the SMS submitted by the partner test probe 3’ is correctly delivered to the respective test probe 3 in the serving IoT network 2. Again, this test is repeated multiple times and the multiple test results are aggregated. With respect to figure 2, a further embodiment of a test system 15 for a mobile IoT network is described. Components and functions which corre spond to those explained above with respect to figure 1 show the same ref erence numerals and are not discussed in detail again. A central test unit, test clients and SIM multiplexer which also may be present in the test sys tem 15 in addition to a local unit are not shown in figure 2.
In the test system 15, a local unit 16 including the test probes 3 is embod ied as S 1 core unit which is connected to the IoT network 2 via an S 1 inter face 17. A communication line 18 via this S I interface 17 is realized as emulated eNodeB (Evolved NodeB). Details with respect to an embodi ment of an S 1 interface and the protocol can be found in 3GPP TS 36.413 V.15.5.0, Release 15, March 2019: "Evolved Universal Terrestrial Access Network (E-UTRAN); S I Application Protocol (S 1AP)".
Figure 3 shows another embodiment of a test system 20. Components and functions which correspond to those already explained with respect to fig ures 1 and 2 have the same reference numerals and are not discussed in detail again.
The test system 20 provides test for connectivity and services to mobile IoT devices in roaming conditions. Here, communication via lines 9, 10 and 11 is done between a home public mobile network (HPMN) and a vis iting public mobile network (VPMN) across a border 21. To this end, in the communication line 11, in addition to the SCEF module in the HPMN a further interworking SCEF (IWK-SCEF) module is arranged in the VPMN. This roaming scheme is possible with the radio interfaces 5 shown again in figure 3 as well as with the S I interface 17 according to figure 2 (not shown in fig. 3).
Figure 4 shows components of a further embodiment of a test system for a mobile IoT network including details with respect to testing data transfer between different test probes 3, 3’ wherein such different test probes 3, 3’ may be attributed to different, e.g. home/visiting, public mobile networks. Components and functions which correspond to those explained above with respect to figures 1 to 3 have the same reference numerals and are not dis cussed in detail again.
A first one of the test probes, test probe 3, is connected to the IoT platform 6 via a test communication path 22 which can include a radio interface 5 or a S I interface 17. The test probe 3 includes an MQTT/MQTT-SN client 23 which communicates via the communication line 22 with an
MQTT/MQTT-SN server/broker 24 of the IoT platform 6 under test.
Another test probe, test probe 3’, communicates in figure 4 with the IoT platform 6 under test via another test communication path 25 which also may include a radio interface 5 or an S I interface 17. To this end, the fur ther test probe 3’ also includes an MQTT/MQTT-SN client 23’.
Alternatively or in addition to MQTT/MQTT-SN, at least one of the fol lowing further protocols and/or one of the following device specific inter faces may be used: oneM2M, Hypercat, CoAP, RTSP, JSON, XML. Use of a specific protocol/interface depends on the respective IoT device and/or the respective application. As an example, CoAP is suitable for con strained networks having low bandwidth and low power. The test probe 3, 3’ may be part of a moving device, i.e. may be part of a vehicle, e.g. a bike or a car. In this case, the test device may initiate a track ing area update each time the respective test probe 3 enters a new tracking area within the MIoT network 2. After such tracking area update, data as signed to the PSM and/or assigned to the eDRX function may be renegoti- ated and/or overridden by initiation of the test system.
By using in particular one of the test methods explained above, the relevant IoT data sent by test probe 3 and stored in the platform under test 6 can be retrieved by the test probes 3’. The retrieved data is compared with the original data sent. The corresponding test verdict can be assigned.
The test probes 3, 3’ may be placed in the same home network. Alterna tively and as indicated in figure 4, the test probes 3 and 3’ may be located within separated networks. For example, and as shown in figure 4, the test probe 3 may be placed in a visiting public network VPMN and the further test probe 3’ may be located in a home public mobile network HPMN.
With such a configuration, IoT application platform tests under IoT device roaming as explained above can be globally carried out.

Claims

Patent claims
1. Active test system (1; 15; 20) for a mobile IoT network (2) providing connectivity and services to mobile IoT (MIoT) devices of low power wide area (LPWA) technologies,
wherein the test system is designed for testing MIoT services quality of the serving MIoT network under test and for testing MIoT service availability,
with
— at least one test probe (3; 3, 3’) connected to the MIoT network (2) via an LTE-Uu interface (5) and/or
— at least one test probe (3; 3, 3’) connected to the MIoT network (2) via a S I interface (17),
with a central test unit (5a), connected (8) to the at least one test probe (3; 3, 3’) via a wireless backhaul network or a fixed IP net work (7),
with a SIM multiplexer (12) to transfer SIM data to the at least one test probe (3; 3, 3’) in test fields,
wherein the test system is designed to configure and initiate a test probe to EPS attach in the serving MIoT network under test to ver ify the completion of the test procedure, to monitor and record all test events and to repeat the above mentioned test steps according to a test schedule.
2. Test system according to claim 1, configured to exchange signaling messages and to transport either IP data, non-IP data, or SMS to and from the MIoT network (2) under test.
3. Test system according to claim 1 or 2, wherein the at least one test probe (3; 3, 3’) is configured to be placed in a serving network, i.e. ei ther in a home IoT network (2, HPMN) under test for national MIoT services test, or in a visiting MIoT network (2, VPMN) under test for international MIoT roaming services test.
4. Test system according to claim 3, configured to test MIoT serving net work under test on different test connect and communication paths across different MIoT network (2) components via MME, S-GW, P- GW, SCEF, IWK-SCEF, SCS, AS, as well as across roaming interfac es S6a, S8, SGd, T7.
5. Test system according to one of claims 1 to 4, configured to communi cate with a MIoT platform (6) under test via MQTT / MQTT-SN mes sages and to verify an availability and connectivity of the MIoT plat form (6) via the underlying MIoT network, and an end-to-end data transfer and a data integrity between the MIoT platform (6) and the mobile IoT devices.
6. Test method using a test system according to one of claims 1 to 5 for testing MIoT services quality of the serving MIoT network under test.
7. Test method according to claim 6, testing MIoT service availability and including the following steps:
configuring and initiating test probe to EPS attach in the serving MIoT network under test,
verifying the completion of the attach procedure,
monitoring and recording all test events, repeating the above-mentioned test steps according to test sched ule.
8. Test method according to claim 6 to 7, testing IoT network connectivi ty and including the following steps:
initiating the test probe to ping a server in the serving MIoT net work under test,
verifying the completion of the ping procedure,
monitoring and recording all test events,
repeating the above-mentioned test steps according to test sched ule.
9. Test method according to one of claims 6 to 8, testing power saving function to be managed by the MIoT serving network under test and including the following steps:
enabling PSM (Power Saving Mode), hereby setting values of the T3324 Active Timer and the T3412 Timer extended at the test probe,
initiating an EPS attach of the test probe in the serving MIoT net work,
verifying the completion of the attach procedure,
verifying whether the timer values are accepted by the service MI oT network, comparing these values with the ones requested by the test probe,
verifying whether the extended periodic TAU (Tracking Area Up date) procedure is accepted,
monitoring and recording all test events,
repeating the above-mentioned test steps according to test sched ule.
10. Test method according to one of claims 6 to 9, testing eDRX function to be managed by the IoT serving network under test and including the following steps:
- enabling eDRX (Extended Discontinuous Reception), hereby set ting values of the eDRX cycle length and the paging time window (PTW) at the test probe,
initiating an EPS attach of the test probe in the serving IoT net work under test,
- verifying the completion of the attach procedure,
verifying whether the eDRX cycle length and the PTW value ac cepted by the service IoT network, comparing these values with the ones requested by the test probe,
monitoring and recording all test events,
- repeating the above-mentioned test steps according to test sched ule.
11. Test method according to one of claims 6 to 10, testing the connect retainability of IoT network and including the following steps:
- verifying whether the test probe is requested by the serving IoT network for detach after an EPS attach or after mobile origination (MO) or mobile termination (MT) data transfer,
repeating this verification step multiple times,
aggregating the multiple test results, indicating a default EPS bear- er context cut-off ratio.
12. Test method according to one of claims 6 to 11, testing an IoT mobile origination (MO) data transfer provided by the serving IoT network under test, including the following steps: deploying a TCP transport protocol,
initiating a mobile originated IoT data transfer from the test probe to an application server located in the home network (HPMN), verifying whether the IoT data is correctly received by the applica tion server,
repeating this verification step multiple times,
aggregating the multiple test results, indicating the default EPS bearer context cut-off ratio,
deploying a UDP transport protocol,
repeating IoT MO data transfer test,
deploying a non-IP data delivery mechanism over NAS signaling, repeating IoT MO data transfer test.
13. Test method according to one of claims 6 to 12, testing an IoT mobile termination (MT) data transfer provided by the serving IoT network under test and including the following steps:
deploying TCP transport protocol,
initiating an application server located in the home network (HPMN) to transmit IoT data to the test probe,
verifying whether the IoT data is completely received by the test probe,
repeating this verification step multiple times,
aggregating the multiple test results, indicating the default EPS bearer context cut-off ratio,
deploying a UDP transport protocol,
repeating IoT MT data transfer test,
deploying a non-IP data delivery mechanism over NAS signaling, Repeating IoT MT data transfer test.
14. Test method according to one of claims 6 to 13, testing an MO SMS transmission via the serving IoT network under test and including the following steps:
initiating the test probe to send an SMS to a partner test probe in the home network (HPMN),
verifying whether the SMS is correctly delivered to the partner test probe,
repeating the test multiple times,
aggregating the multiple test results.
15. Test method according to claims 6 to 14, testing an MT SMS delivery via the serving IoT network under test and including the following steps:
initiating a partner test probe in a home network to send an SMS to the test probe in the serving IoT network,
verifying whether the SMS submitted by the partner test probe is correctly delivered to the test probe in the serving IoT network, repeating the test multiple times,
aggregating the multiple test results.
PCT/EP2020/063233 2019-05-15 2020-05-12 Active test system for the mobile iot network and test method using such a test system WO2020229496A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN202080036248.7A CN114208260B (en) 2019-05-15 2020-05-12 Active test system for mobile IoT networks and test method using the same
JP2021568671A JP2022533377A (en) 2019-05-15 2020-05-12 Mobile IoT network active test system and test method using the test system
EP20726055.5A EP3970405A1 (en) 2019-05-15 2020-05-12 Active test system for the mobile iot network and test method using such a test system
KR1020217038035A KR20220008834A (en) 2019-05-15 2020-05-12 Active test systems for mobile IOT networks and test methods using such test systems
AU2020274610A AU2020274610A1 (en) 2019-05-15 2020-05-12 Active test system for the mobile IoT network and test method using such a test system
IL288084A IL288084A (en) 2019-05-15 2021-11-14 Active test system for the mobile iot network and test method using such a test system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
DE102019207051.5 2019-05-15
US16/412,459 US10848562B1 (en) 2019-05-15 2019-05-15 Test system for the mobile IoT network and test method using such a test system
DE102019207051.5A DE102019207051A1 (en) 2019-05-15 2019-05-15 Active test system for the mobile IoT network and test procedures using such a test system
US16/412,459 2019-05-15

Publications (1)

Publication Number Publication Date
WO2020229496A1 true WO2020229496A1 (en) 2020-11-19

Family

ID=70738527

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/063233 WO2020229496A1 (en) 2019-05-15 2020-05-12 Active test system for the mobile iot network and test method using such a test system

Country Status (7)

Country Link
EP (1) EP3970405A1 (en)
JP (1) JP2022533377A (en)
KR (1) KR20220008834A (en)
CN (1) CN114208260B (en)
AU (1) AU2020274610A1 (en)
IL (1) IL288084A (en)
WO (1) WO2020229496A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117176628B (en) * 2023-11-03 2024-01-16 中国电子科技集团公司第十研究所 Radio equipment interface conformance testing method and system based on embedded probe

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004049746A1 (en) 2002-11-28 2004-06-10 Sigos Systemintegration Gmbh Test system for checking transmission processes in a mobile radio network, and method for authenticating a mobile telephone using one such test system
US7831249B2 (en) 2004-12-28 2010-11-09 Keynote Sigos Gmbh Test device for use in a test system for checking transmission procedures in a mobile telephony network
EP2365662A2 (en) * 2010-03-12 2011-09-14 Telefonaktiebolaget L M Ericsson (publ) Method and apparatus for active probing of tunneled internet protocol (IP) transmission paths
DE102005027027B4 (en) 2005-06-11 2014-07-31 Keynote Systems, Inc. Method for authenticating a mobile test device in a mobile radio network and test system for checking transmission processes within a mobile radio network and for carrying out such an authentication method
EP3075180A1 (en) * 2013-11-29 2016-10-05 Telefonaktiebolaget LM Ericsson (publ) Method and corresponding apparatus, computer program product to validate an euicc subscription change
US9768893B1 (en) 2016-11-16 2017-09-19 Spirent Communications, Inc. Over-the-air isolation testing
US20180049050A1 (en) * 2016-08-12 2018-02-15 W2Bi, Inc. Automated validation and calibration portable test systems and methods
EP3355491A1 (en) * 2017-01-27 2018-08-01 Rohde & Schwarz GmbH & Co. KG Test device and test method
US10097981B1 (en) 2017-05-26 2018-10-09 Sigos Llc Test procedure for a mobile network of an emergency call network

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104009890B (en) * 2014-06-10 2017-08-15 江苏省邮电规划设计院有限责任公司 Network quality test system and method in a kind of internet
US10091785B2 (en) * 2014-06-11 2018-10-02 The Board Of Trustees Of The University Of Alabama System and method for managing wireless frequency usage
US10237284B2 (en) * 2016-03-31 2019-03-19 International Business Machines Corporation Internet of things security appliance
CN107819645B (en) * 2017-10-16 2021-02-09 南京网元通信技术有限公司 Internet of things testing method based on software simulation

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004049746A1 (en) 2002-11-28 2004-06-10 Sigos Systemintegration Gmbh Test system for checking transmission processes in a mobile radio network, and method for authenticating a mobile telephone using one such test system
US7831249B2 (en) 2004-12-28 2010-11-09 Keynote Sigos Gmbh Test device for use in a test system for checking transmission procedures in a mobile telephony network
DE102005027027B4 (en) 2005-06-11 2014-07-31 Keynote Systems, Inc. Method for authenticating a mobile test device in a mobile radio network and test system for checking transmission processes within a mobile radio network and for carrying out such an authentication method
EP2365662A2 (en) * 2010-03-12 2011-09-14 Telefonaktiebolaget L M Ericsson (publ) Method and apparatus for active probing of tunneled internet protocol (IP) transmission paths
EP3075180A1 (en) * 2013-11-29 2016-10-05 Telefonaktiebolaget LM Ericsson (publ) Method and corresponding apparatus, computer program product to validate an euicc subscription change
US20180049050A1 (en) * 2016-08-12 2018-02-15 W2Bi, Inc. Automated validation and calibration portable test systems and methods
US9768893B1 (en) 2016-11-16 2017-09-19 Spirent Communications, Inc. Over-the-air isolation testing
EP3355491A1 (en) * 2017-01-27 2018-08-01 Rohde & Schwarz GmbH & Co. KG Test device and test method
US10097981B1 (en) 2017-05-26 2018-10-09 Sigos Llc Test procedure for a mobile network of an emergency call network

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Evolved Universal Terrestrial Access Network (E-UTRAN); Sl Application Protocol (S1AP", 3GPP TS 36.413 V. 15.5.0, RELEASE 15, March 2019 (2019-03-01)
GSM ASSOCIATION; OFFICIAL DOCUMENT CLP.28-NB-IOT DEPLOYMENT GUIDE TO BASIC FEATURE SET REQUIREMENTS, VERSION 1.0, 2 August 2017 (2017-08-02)
JOHN DAVIES: "Hypercat: resource discovery on the internet of things (January 12, 2016", IEEE INTERNET OF THINGS, 2 March 2017 (2017-03-02), Retrieved from the Internet <URL:http://iot.ieee.org.>
TECHNICAL SPECIFICATION 3GPP TS 23.682, V. 15.8.0, RELEASE 15, March 2019 (2019-03-01)

Also Published As

Publication number Publication date
CN114208260A (en) 2022-03-18
KR20220008834A (en) 2022-01-21
AU2020274610A1 (en) 2021-11-25
IL288084A (en) 2022-01-01
CN114208260B (en) 2024-01-26
EP3970405A1 (en) 2022-03-23
JP2022533377A (en) 2022-07-22

Similar Documents

Publication Publication Date Title
US11134543B2 (en) Interworking LPWAN end nodes in mobile operator network
US10848562B1 (en) Test system for the mobile IoT network and test method using such a test system
US9407522B2 (en) Initiating data collection based on WiFi network connectivity metrics
KR101746912B1 (en) Testing of location information signaling related to minimization of drive tests and conformance tests
US20170339589A1 (en) Network-Controlled Terminal Data Call Performance Testing
US11539454B2 (en) Service validation using emulated virtual clients
KR20240039085A (en) Enhanced multilayer uplink transmission
EP3970405A1 (en) Active test system for the mobile iot network and test method using such a test system
CN107919936A (en) A kind of method and device of business data transmission
WO2023069653A1 (en) User equipment (ue) switching between networks using measurement gaps
Yang et al. Design of communication interface for M2M-based positioning and monitoring system
KR20240004257A (en) Configuring spatial relationships and power control for uplink transmission
CN116783882A (en) Performance measurement for edge computing applications
RU2802845C2 (en) Active testing system for mobile internet of things network and testing method using such testing system
US20230422038A1 (en) Cyber attack detection function
JP2024050470A (en) Low power wake-up signal having two parts in the time domain
WO2023150605A1 (en) Service mesh enabled sixth generation (6g) architecture
WO2023129362A1 (en) System and information for charging for edge application server (eas) deployment
WO2023287808A1 (en) Beamforming for multiple-input multiple-output (mimo) modes in open radio access network (o-ran) systems
WO2024015894A1 (en) Transmission triggering using a separate low-power wake-up receiver
WO2022094039A1 (en) Computing offloading for next generation cellular networks
WO2024036268A1 (en) Support of data transmission measurement action guarantee for data delivery service
CN117121394A (en) System and method for beamforming indication
WO2024015893A1 (en) Resource determination for low power wake-up signal
WO2024110081A1 (en) Data collection and reporting in a wireless communication system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20726055

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021568671

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217038035

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020274610

Country of ref document: AU

Date of ref document: 20200512

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020726055

Country of ref document: EP

Effective date: 20211215

WWE Wipo information: entry into national phase

Ref document number: 521430834

Country of ref document: SA