hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.10.2 ptime and mptime SDP Interworking | IPCablecom 1.5 MTAs and Media Gateways are mandated to send an a=mptime line in all LCD. However, this attribute line is not defined in ITU or IETF and is specific to IPCablecom 1.0 and 1.5. Therefore, IPCablecom 2.0 [i.9] devices and non-IPCablecom devices will not recognize this line. Further, IPCablecom 1.5 MTAs and... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.11 MGC Caller ID Procedures | |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.11.1 MGC Processing - Egress | The following closely follows [i.10]. When an MGC receives a SIP request destined for the PSTN, it translates the call signalling from SIP to SS7. The SS7 interface is defined in [i.11]. The ISUP call setup messages for circuit switch calls indicate presentation statuses of calling identity items in data fields known a... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.11.2 MGC Processing - Ingress | When a MGC receives an incoming ISUP IAM, it translates the call from Common Channel Signaling SS7 ISUP to SIP [i.11]. The ISUP call setup messages for circuit switch calls indicate presentation statuses of calling identity items in data fields known as presentation sub fields. A presentation subfield exists for each c... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12 Procedures for Request History Information | RFC 4244 [41] defines a standard mechanism for capturing the history information associated with a Session Initiation Protocol (SIP) request. This capability enables many enhanced services by providing the information as to how and why a call arrives at a specific application or user. RFC 4244 [41] also defines a new S... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12.2 Setting of the Call Forwarding parameters | After checking the number of forwards, a number of fields of the INVITE request are set by the CMSS compliant implementation as defined in the following subclauses. |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12.2.1 First Forwarded INVITE | The absence of a History-Info header in the INVITE or the presence of a History-Info with no entries containing a nested Reason header with a protocol-cause parameter means that this is the first instance of a forwarding action. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 126 When this is the first forward the INVITE has ... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12.2.2 Second or Subsequent Forwarded INVITE | When this is the second or subsequent forwarding of the INVITE, the CMSS compliant implementation shall add a new entry to the History-Info header according to the rules defined in [41]. If the history entry representing the forwarding party already contains the correct privacy value for the forwarding party (in an esc... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12.3 MGC Inter-working | To prevent forwarding loops occurring between the IPCablecom network and the PSTN, forwarding information needs to be maintained by the MGC when mapping from SIP to ISUP and vice versa. Given that all of the applicable ISUP parameters required are optional rather than mandatory in an ISUP IAM or ACM message, the proced... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12.3.1 MGC Processing - Egress | When a MGC receives a SIP request destined for the PSTN, it translates the call from SIP to Common Channel Signaling SS7 ISUP, as specified in [i.11]. The ISUP IAM that is mapped from a received SIP INVITE can optionally carry call redirection information. If the received SIP INVITE contains a History-Info header indic... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.12.3.2 MGC Processing - Ingress | When a MGC receives an ISUP IAM, it translates the call from Common Channel Signaling SS7 ISUP to SIP, as specified in [i.11]. The IAM can optionally carry call redirection information. If the received ISUP IAM contains the Original Called Number, Redirection Information and Redirecting Number parameters then the MGC s... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.13 Operator Services | Operator Services (Busy Line verification and Emergency Interrupt) are initiated from the MGC on behalf of a PSTN gateway connecting to special MF trunks groups from the OSPS system. The SIP messages SUBSCRIBE(Dialog Event) and INVITE(BLV) are initiated by the MGC after performing a basic call to the line being verifie... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 8.4.14 Signaling Dialled Non-Geographic Numbers | This clause describes the procedures for conveying a non-geographic dialled number (e.g. a dialled 800 number) to the terminating IPCablecom network for calls originating in the PSTN. ETSI ETSI TS 103 161-16 V1.1.1 (2011-04) 132 When the MGC receives an incoming call from the PSTN on an SS7 trunk, it performs the mappi... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 9 Application Layer Anonymizer | In this clause, additional detail about an application-level anonymizer that is used to support Privacy is provided. As described earlier, a user may request three different forms of Privacy: user, name and IP-address Privacy. In order to provide these three different types of Privacy, an application-layer anonymizer i... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 9.1 Signaling Content Privacy | The Signaling Content Privacy function serves the role of modifying the SIP signalling messages to handle calling name and calling number Privacy as specified in clause 8.4. More specifically, the Signaling Content Privacy function shall ensure that the Privacy requirements pertaining to the headers below are met: Head... |
64029922d6f9738ac70ee1d11cbc5838 | 103 161-16 | 9.2 IP Address Privacy | The IP address Privacy function serves the role of modifying the SIP signalling messages to honour IP-address Privacy requests in CMSS as specified in clause 8.4. The IP address Privacy function considers IP address Privacy for both media and signalling. This allows the IP address Privacy function to be used in a varie... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 1 Scope | |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 1.1 Introduction and Purpose | The present document defines extensions to the IPCablecom Network-based Call Signalling (NCS) [2] protocol to support the following analogue trunking for PBX interfaces on an embedded Voice-Over-IP client device in a IPCablecom environment: • Ground-start lines. • PBX one-way and two-way DTMF (dual-tone multi frequency... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ANSI T1.401: "Network to Customer Installations - Analog Voicegrade Switched Access Lines Using Loop-Start and Ground-Start Signaling". [2] ETSI TS 103 161-4: "Access, Terminals, Transmission and Multiplexing (ATTM); Integ... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Telcordia GR-31-CORE LSSGR, Issue 4: "CLASS Feature: Calling Number Delivery", June 2006. [i.2] Telcordia GR-1188: "LSSGR CLASS Feature: Calling Name ... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 3 Definitions and abbreviations | |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 3.1 Definitions | For the purposes of the present document, the terms and definitions following apply: endpoint: terminal, gateway or Multipoint Conference Unit (MCU) gateway: devices bridging between the IPCablecom IP Voice Communication world and the PSTN NOTE: Examples are the Media Gateway, which provides the bearer circuit interfac... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CAS Channel Associated Signalling CMS Call Management Server DID Direct Inward Dialling DOD Direct Outward Dialling DTMF Dual-tone Multi Frequency (tones) E&M E and M Signalling GS Ground-start LS Loop-start MTA Multimedia Terminal Adapter NCS... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 4 Void | |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5 Overview | The present document describes the functional requirements for an embedded client to support one-way incoming, one- way outgoing, and two-way PBX trunks. The physical interfaces used to support these trunk types are also defined. |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.1 Functional Responsibility | To maintain compliance with the IPCablecom NCS specification [2], the Call Agent will remain responsible for all higher order functionality whenever possible. Only when timing is critical will the endpoint be responsible for the required functionality. For example, the endpoint is expected to out-pulse a string of succ... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2 Physical Endpoint Interface | Various physical interfaces provided by an endpoint of an MTA are used to support the following PBX trunks: • One-way incoming trunk - supports calls originating from the network towards the PBX via the MTA. A specific example of a one-way incoming trunk is a DID PBX (direct inward dialling private branch exchange) tru... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2.1 Loop-Start Line Interface | The NCS Line package defined in the IPCablecom NCS specification [2] is used to support loop-start lines. Loop-start lines are typically used for residential voice services, but may be used to support analogue trunking for PBX. |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2.2 Ground-Start Line Interface | Ground-start signalling interfaces are used to provide two-way service to customer-installation switching systems, e.g. legacy PBX systems. According to [1] ground-start signalling for two-way dial facilities was introduced to reduce the likelihood of seizure of the line at both ends during the silent interval of the a... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2.3 DID PBX Trunk Interface | A one-way Direct Inward Dialling (DID) trunk interface as described in [3] is required to support a DID interface of a PBX. DID trunks can only make calls in the direction from the network towards the PBX. Electrically, a DID trunk looks similar to the reverse of a 2-wire loop-start interface. The PBX provides loop cur... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2.4 E&M | E&M is described in annex F of [3] and is typically used as a PBX tie trunk. E&M trunks may be configured to be 2- way or 1-way. Signalling may be either dial pulse or DTMF. The interface is extremely simple and only off-hook and on-hook are signalled in each direction. The PBX signals off-hook and on-hook on the M-lea... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2.4.1 Two-wire E&M | Two-wire E&M (or Type I E&M) has two conductors on the interface called the E-lead (or Ear) and the M-lead (or Mouth). The PBX provides -48 volt battery on both leads. The MTA signals off-hook by shorting the PBX E-lead to ground. The PBX signals off-hook by closing a contact to provide battery to the M-lead. |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.2.4.2 Four-wire E&M | Four-wire E&M (Type II E&M) has four conductors called the E-Lead, the M-Lead, Sleeve Battery, and Sleeve Ground. The PBX applies -48 volt battery to the E-Lead and grounds the Sleeve Ground. The MTA provides -48 volt battery on the Sleeve Battery and grounds the M-Lead with a current detector. The MTA signals off-hook... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 5.3 NCS Package Support | In order to avoid the unnecessary complexity of supporting redundant signals and events, an additional package above and beyond the NCS Line package is defined here to include only those events and signals that are needed to support analogue trunking for PBX, but do not already exist in the NCS Line package. Due to thi... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1 Endpoint Configuration | To support the trunk types defined in clause 5.2, the endpoint must be configured with the following: • Physical interface type • PBX Trunk type • Start of dialling method • Out-pulse dialling method • Maximum length of out-pulsed dial string • Re-seizure delay |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1.1 Physical Interface Type Configuration | At any given point in time, an endpoint supports one and only one type of interface: • Loop-start line interface • Ground-start line interface • E&M 2-wire line interface • E&M 4-wire line interface • DID PBX trunk interface • T1 ETSI ETSI TS 103 161-15 V1.1.1 (2011-10) 13 The question of how a particular endpoint is c... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1.2 PBX Trunk Type Configuration | As stated in clause 5.2, the following PBX trunk types are supported: • One-way incoming trunk • One-way outgoing trunk • Two-way trunk The endpoint must be configured as such when used to interface to a PBX to provide one of the above trunk types. When this configuration information is missing, the default behaviour i... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1.3 Start of Dialling Method Configuration | In order for the MTA to provide an interface to a PBX using either a PBX DID or E&M physical interface, the start of dialling method must be configured to something other than the default "dial tone" method. The configured start of dialling method for two-way E&M PBX trunks is used in both directions - PBX to endpoint ... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1.4 Out-pulse Dialling Method | When an endpoint is configured to support incoming PBX calls, the endpoint will be expected to out-pulse a dial string towards the PBX. In this case, the endpoint must be configured to out-pulse one of the following digit types: • DTMF • Dial Pulse |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1.5 Maximum Out-pulsed Dial String Length | The Call Agent may provide the entire external phone number of the extension being dialled in the PBX. Typically, however, only the last few digits are needed. As such, the endpoint must be configured with the maximum dial string length when configured to support incoming PBX calls. When the Call Agent provides a dial ... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.1.6 Re-seizure Delay | Due to PBX requirements once a trunk is released it cannot be seized again for a short period of time. The MTA must be configured with the amount of time required to wait (in ms). The default is zero, i.e. no delay. The MTA must not re- seize a trunk during this period of time. If a new Call Setup request is received d... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2 Signalling Support | In order to help quickly detect configuration issues (e.g. endpoint is configured for residential voice while the Call Agent is configured for PBX service), commands issued to the endpoint that are specific to a particular service must be rejected when the endpoint is configured to support any other service. The revers... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.1 Digit and Digit Related Events | When the endpoint is expected to receive digits from the PBX and the Call Agent is to be notified of these events, the Call Agent must use the NCS Line package digit (0-9,*,#,A,B,C,D,X) and digit related events (L, t) to request them. The Call Agent may request the processing of digit events in any manor allowed by NCS... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.2 Digit Events over E&M | When an E&M PBX trunk is setup to use a start of dialling method of "immediate start" the Call Agent should take special precautions to insure that digits are not missed from the PBX. The PBX will start dialling after a short delay after going off-hook. This may occur before the Call Agent requests digits from the endp... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.3 Local Tones | Though only a few local tones (MTA ≥ PBX) are required for analogue trunking for PBX as indicated in table 2, each physical interface should be capable of applying all requested NCS Line package tones towards the PBX. To maintain as much flexibility as possible and to support potential future PBX-like features, the end... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.3.1 Local Tones over E&M | Dial tone is not applied over an E&M physical interface. When either dial-tone (L/dl), stutter dial tone (L/sl) or message waiting indicator tone (L/mwi) is requested by the Call Agent to be applied over an E&M interface, the MTA must not apply the tone itself. Instead, the MTA must use the signal request to aid in det... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.4 Caller ID and VMWI | The Caller ID and VMWI NCS Line package signals apply only to LS/GS (loop-start/ground-start) PBX trunk interfaces. The call setup (PAT/sup) signal defined in the PAT package is used to deliver caller ID information; however, the Call Agent may alternatively use the Line package Caller ID signal to provide caller ID in... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.5 Hook Events | For all physical interface types, the NCS Line package hook events (L/hd, L/hf, L/hu) are used to indicate hook state at the PBX. For LS/GS, hook events are detected and generated as defined in NCS. Similarly, for E&M, on-hook and off-hook events are generated when the corresponding signal is detected from the PBX. Bas... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.6 Open Signal Interval | For loop-start lines the L/osi NCS Line package signal is used as a trigger for the endpoint to perform a "timed disconnect release". For ground-start lines, the signal is used as a trigger for the endpoint to provide a "guard release" which has similar characteristics to the loop-start "timed disconnect release". This... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.7 Ring Requests | The ring NCS Line package signal requests only apply to LS/GS trunks. The call setup (PAT/sup) signal defined in the PAT package is used as a trigger to seize the trunk by applying standard ringing; however, the Call Agent may alternatively use the Line package RG signal to provide ringing. Though the PBX typically onl... |
31ebfbca95ba5153cb05caf4fbcb6211 | 103 161-15 | 6.2.8 T1 Trunk Signalling Requirements | T1 is a digital trunk interface. As such, the signalling between the MTA and PBX required to support one-way incoming, one-way outgoing and two-way PBX trunks is emulated using Channel Associated Signalling (CAS). The signalling between the MTA and Call Agent, however, remains unchanged. In other words, the fact that t... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 1 Scope | The present document contains the Profile Test Specification (PTS) and the Test Case Library (TCL) for "New Generation DECT; Part 4"Digital Enhanced Cordless Telecommunications (DECT); New Generation DECT; Part 4: Light Data Services; Software Update Over The Air (SUOTA), content downloading and HTTP based applications... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non- specific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 175-5: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network (NWK) layer". [2] ETSI EN 300 444: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profil... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] World Wide Web Consortium Recommendation XHTML™ 1.1: "Module-based XHTML - Second Edition" - 23 November 2010. NOTE: http://www.w3.org/TR/2010/REC-xht... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 3 Definitions, symbols and abbreviations | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 102 527-5 [6], ETSI TS 102 527-3 [4], ETSI TS 102 527-1 [3], ETSI EN 300 444 [2] and the following apply: GAP (PP, FP, device or equipment): PP, FP or any of them compliant with ETSI EN 300 444 [2]. golden device: ideal example of a de... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: C conditional to support (process mandatory) E Test Parameter used in parameterized tests for an HTTP Error I out-of-scope (provision optional, process optional) not subject for testing M mandatory to support (provision mandatory, process mandatory)... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BCD Binary Content Download CC Call Control CI Common Interface DECT Digital Enhanced Cordless Telecommunications DLC Data Link Control DS Download Server FP Fixed Part FT Fixed radio Termination GAP Generic Access Profile HTTP HyperText Trans... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4 Test method | This clause describes the test method used to test the NG DECT Part 4 devices. DECT DLC DECT MAC DECT PHL Tester Test System Device Under Test DECT DLC DECT MAC DECT PHL DECT NWK IUT Application NWK PDUs Figure 1: New Generation DECT remote test method A tester (see figure 1) is located in a remote DECT test system. It... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1 Test platform | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1 PP test platform | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.1 PP test platform main requirements | The PP test platform is outlined in figure 2. Test System T S 1 P P DUT Figure 2: PP Test Platform The first RF front-end of Test system "TS_1" plays the role of a LDS FP to which the PP under test is registered. The DUT supplier shall also supply new software revision file/files for installation on the Test System. |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.2 Test content for HTTP-based applications, Simple profile | NOTE : This test content was designed for TC_PT_NGLDS.A3_BV_109 and is reused for test TC_FT_NGLDS.A.2_BV_105 on FT side. |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.2.1 Test url and index page: index.html | Test url1 = http:// ${SERVER_HOSTNAME}/http-based-application-1/ The SERVER_HOSTNAME variable value shall be provided by the 3rd party providing the server. Home_page=Test url1 + 'index.html' shall target the following resource. <html> <head><title>My service</title></head> <body> <p style="text-align:left;"><a href="p... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.2.2 Left page: pages/left.html | <html> <head><title>Left page</title></head> <body><p>Link for this page was on the left</p></body> </html> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.2.3 Center page: pages/center.html | <html> <head><title>Center page</title></head> <body><p>Link for this page was centered</p></body> </html> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.2.4 Right page: pages/right.html | <html> <head><title>Right page</title></head> <body><p>Link for this page was on the right</p></body> </html> ETSI ETSI TS 103 158 V1.1.1 (2014-11) 10 |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.3 Test content for HTTP-based applications, Baseline profile | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.3.1 Test url and index page: index.html | Test url2 = http:// ${SERVER_HOSTNAME}/http-based-application-2/ The SERVER_HOSTNAME variable value shall be provided by the 3rd party providing the server. Home_page=Test url2 + 'index.html' shall target the following resource. <html> <head><title>My service</title></head> <body> <ul> <li style="text-align:left;"> <a ... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.3.2 Left page: pages/left.html | <html> <head><title>Left page</title></head> <body><p>Link for this page was on the left</p></body> </html> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.3.3 Center page: pages/center.html | <html> <head><title>Center page</title></head> <body><p>Link for this page was centered</p></body> </html> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.1.3.4 Right page: pages/right.html | <html> <head><title>Right page</title></head> <body><p>Link for this page was on the right</p></body> </html> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.2 FP test platform | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.2.1 FP test platform main requirements | The fixed part under test shall be connected to a network when running the tests suite. It shall be ready to support the SUOTA feature. An example of FP test platform is depicted in figure 3. ETSI ETSI TS 103 158 V1.1.1 (2014-11) 11 Test System T S 1 F P DUT T S 2 NET Download Server (DS) Management Server (MS) Figure ... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.1.2.2 Test content for software upgrade (TS_1 + MS) | Table 1 describes the data to be used for populating TS_1 (PT), the Management Server (MS) or both when testing the FT (multiple file upgrade with two files is used). The values listed below for populating the MS (or for populating both the MS and TS_1) shall apply whether the MS used for a given test is provided by a ... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.2 Hypothesis | Protocol layers tested Network and application features are only tested. DLC, MAC and PHY procedures used by new DECT generation standard are supposed to be tested when testing network features. Speech services tested The device under test is required to support only mandatory speech services. Optional codecs are out o... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.3 Test groups | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.3.1 Network features | Network features are described in clauses 5.2, 6.4 and 6.10 of ETSI TS 102 527-5 [6]. |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 4.3.2 Application features | Application features are described in clauses 5.7, 6.9 and 6.13 of ETSI TS 102 527-5 [6]. |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5 Test Cases (TCs) | Each test case is allocated directly under a defined TC. ETSI ETSI TS 103 158 V1.1.1 (2014-11) 13 |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1 TC definition conventions | The TCs are defined following particular rules as shown in table 2. Table 2: TC definition rules TC Id according to the TC naming conventions Test case objective Main test purpose: Optional detailed description of test case objective for complex test cases Reference: The reference should contain the references of the s... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.1 Test equipment implementation requirements | This clause specifies the general requirements to be implemented by the test equipment. The requirements listed below can be valid either for several features on one side, or for one feature on both sides, PP and FP side. Specific requirements for a single feature are given in the related clause describing the sub test... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2 Definitions of used MACROs (PT and FT sides) | The following Macros are used for the test body definition, for frequently re-used test chunks. |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.1 Basic service MACROs (request from PP to FP) | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.1.1 Suota C-plane | None. |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.1.2 Binary content download | The following values are defined binary content download in ETSI TS 102 527-4 [5], clause 7.6.1.4. <<BASIC-SERVICE BCD >> = << Basic-Service <Call class = 'Normal call setup' = 8H>, <Basic service = 'LDS: SUOTA, Class 4 DPRS management, default setup attributes' = 9H> ETSI ETSI TS 103 158 V1.1.1 (2014-11) 15 |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.1 Handset version indication MACRO (request from PP to FP) | The 'Handset version indication' command is defined in ETSI TS 102 527-4 [5], clause 7.5.5.2.1. hsv_ind(emc=EMC, url1=URL1, fileNumber=FN, flags=F, reason=R, swv=SWV1, hwv=HWV1)= local variables: n, N1(N1: fix integer value chosen by sender) {FACILITY} message with IE <<IWU-to-IWU>> with: - Handset version indication (... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.2 Handset version available MACRO (from FP to PP) | The 'Handset version available' command is defined in ETSI TS 102 527-4 [5 ], clause 7.5.5.2.2. This is the answer to command 'Handset version indication'. hsv_avail(dm=DM, url2=URL2, u_inter=UI, swv=SWV)= local variables: n, N2(N2: fix integer value chosen by sender) {FACILITY} message with IE <<IWU-to-IWU>> with: - H... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.3 HTTP related MACROS | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.3.1 Submacros | filesize(url): size of the targeted resource (as a string) request_uri(url): resource identifying part of the url (identification within the server) EXAMPLE 1: request_uri("http://suota.example.com/Suota/suota1?test=2") = "/Suota/suota1?test=2" hostname(url): server identifying part of the url EXAMPLE 2: hostname("http... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.3.2 range request MACRO (from PP to FP) | range request MACRO (from PP to FP) range_http_req(target=URL2, r_low=RL, r_high=RH)= GET request_uri(URL2) + " " + "HTTP1.1"\r\n Host: hostname(URL2)\r\n Accept: application/octet-stream\r\n Range: bytes=RL-RH\r\n \r\n EXAMPLE: range_http_request("http://suota.example.com/Suota/suota1?test=2", 1000, 1999) = GET /Suota... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.3.3 HTTP range response MACRO (from FP to PP) | range_http_resp(target=URL2, r_low=RL, r_high= RH)= HTTP/1.1 206 Partial Content Content-Range: bytes=RL-RH/filesize(URL2) \r\n Content-Length: value_of(RL-RH+1)\r\n Content-Type: application/octet-stream\r\n \r\n <partial octet stream itself> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.1.2.3.4 HTTP error MACRO (from FP to PP) | http_error(e=HTTP_ERROR, text=TEXT)= "HTTP/1.1" + " " + HTTP_ERROR + \r\n \r\n <html><head><title>TEXT </title></head> |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.2 TC naming conventions | Each feature to be tested corresponds to a group of test cases identified by its standard feature number. The identifier of the TC is built according to table 3. Table 3: TC naming convention TC_<rt>_<fn>_<tt>_<ppnn> <rt> = type of radio termination FT Fixed radio Termination PT Portable radio Termination <fn> = featur... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.3 Portable Part TC purposes | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.3.1 List of New Generation DECT Part 4 PT tests cases | Table 4 gives the list of NG-DECT Part 4 PT test cases related to the DECT "Light Data Services; Software Update Over The Air (SUOTA), content downloading and HTTP based applications" features (ETSI TS 102 527-4 [5]). Table 4: NG-DECT Part 4 [5] PT Test Case Index NG-DECT Part 4 [5] PT test case index Test Group Refere... |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.4 Fixed Part TC purposes | |
f0c592daf024022db4705a3d366b0a5f | 103 158 | 5.4.1 List of New Generation DECT Part 4 FT tests cases | Table 5 gives the list of NG-DECT Part 4 FT test cases related to the DECT "Light Data Services; Software Update Over The Air (SUOTA), content downloading and HTTP based applications" features (ETSI TS 102 527-4 [5]). Table 5: NG-DECT Part 4 FT Test Case Index NG-DECT Part 4 FT test case index Test Group Reference Test... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.