We Know Where You Are!
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
SGSN in a 2.5G GPRS Network
SGSN in a 2.5G GPRS Network • SGSN in a 2.5G GPRS Network, on page 1 • 2.5G SGSN Configuration Components, on page 2 • How the 2.5G SGSN Works , on page 4 • Information Required for the 2.5G SGSN, on page 6 SGSN in a 2.5G GPRS Network This chapter outlines the basic configuration and operation of the Serving GPRS Support Node (SGSN) in 2.5G GPRS wireless data networks. The simplest configuration that can be implemented on the system to support SGSN functionality in a 2.5G network requires one context but we recommend a minimum of two: one for the SGSN service (required) and another for the charging context. The service context organizes the following: • GPRS service configuration • MAP (Mobile Application Part) configuration • DNS (Domain Naming System) configuration for resolution of APN (Access Point Name) domain names • SGTP (SGSN GPRS Tunneling Protocol) configuration The charging context facilitates the following: • Configuration of connectivity to the CGF (Charging Gateway Function) The following functionality is configured at the global or system level in the local management context: • NSEI (Network Service Entity Identity) configuration • SCCP (Signalling Connection Control Part) network configuration • SS7 (Signaling System 7) connectivity configuration • GTT (Global Title Translation) configuration To simplify configuration management, more contexts can be created to categorize the service configuration. Each context can be named as needed. The contexts listed above can be configured as illustrated in the figure on the next page. SGSN in a 2.5G GPRS Network 1 SGSN in a 2.5G GPRS Network 2.5G SGSN Configuration Components 2.5G SGSN Configuration Components In order to support 2.5G SGSN functionality, the system must be configured with at least one context for the GPRS service (2.5G SGSN service). -
N-Squared Software N2SRP INAP Protocol Conformance Statement
N-Squared Software N2SRP INAP Protocol Conformance Statement Version 2020-02 N2SRP INAP Protocol Conformance Statement Version 2020-02 1 Document Information 1.1 Scope and Purpose This document describes the implementation of the INAP (including CAMEL variants) protocols for real-time SRP flows for voice interaction control using the N-Squared (N2) SIP Specialized Resource Platform (SRP) when used in conjunction with an INAP Service Control Platform (SCP). It should be read in conjunction with the N2SRP Technical Guide [R-1]. This document assumes a working knowledge of the relevant INAP and other telephony concepts, including the standard INAP interactions between an SCP, an SSP, and an SRP (or Intelligent Peripheral). 1.2 Definitions, Acronyms, and Abbreviations Term Meaning AC Application Context (in TCAP) ARI Assist Request Instructions AS Application Server ASP Application Server Process ASPAC ASP Active ASPTM ASP Traffic Maintenance ASN.1 Abstract Syntax Notation One CAMEL Customized Applications for Mobile Network Enhanced Logic CAP CAMEL Application Part DTMF Dual Tone Multi-Frequency ETSI European Telecommunications Standards Institute GT Global Title GTI Global Title Indicator IETF Internet Engineering Task Force INAP Intelligent Networking Application Part IP Internet Protocol ITU-T International Telecommunication Union Telecommunication Standardization Sector M3UA MTP3 User Adaption Layer MTP3 Message Transfer Part Level 3 N2 N-Squared OCNCC Oracle Communications Network Charging & Control PA Play Announcement PACUI Prompt -
Get SATA Cell D
US 20100189035A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2010/0189035 A1 Pehrsson et al. (43) Pub. Date: Jul. 29, 2010 (54) SERVICE AREAS IN CS DOMAIN SERVICES (86). PCT No.: PCT/EP2007/056278 (75) Inventors: Arne Pehrsson, Huddinge (SE); S371 (c)(1), Magnus Hallenstal, Taby (SE); (2), (4) Date: Feb. 22, 2010 Göran Rune, Linkoping (SE); Jari Publication Classification Vikberg, Jarna (SE); Andreas (51) Int. Cl. Witzel, Herzogenrath (DE) H0474/00 (2009.01) (52) U.S. Cl. ......................................... 370/328; 370/352 Correspondence Address: (57) ABSTRACT ERCSSON INC. 6300 LEGACY DRIVE, M/S EVR1-C-11 The invention provides a method of enabling the service level networks (e.g. CSoLTE or IMS CN) to provide location PLANO, TX 75024 (US) dependent services based on a circuit Switched domain from a service level network to a mobile station communicating (73) Assignee: TELEFONAKTIEBOLAGET with a cell in a radio access network that utilises a packet LM ERICSSON (PUBL), Switched domain. The method includes providing cell loca Stockholm (SE) tion information relating to the location of the cell; determin ing a Service Area Identifier based on the cell location infor mation; and providing the Service Area Identifier to the (21) Appl. No.: 12/666,036 service level network. The Service Area Identifier is then used for different location based services and applications in the (22) PCT Filed: Jun. 22, 2007 service level network nodes. Get SATA cell D Send SASA Patent Application Publication Jul. 29, 2010 Sheet 1 of 5 US 2010/O189035 A1 Contro interface Internet, " see Data litterface Operator Services, etc. -
LTE-M Deployment Guide to Basic Feature Set Requirements
LTE-M DEPLOYMENT GUIDE TO BASIC FEATURE SET REQUIREMENTS JUNE 2019 LTE-M DEPLOYMENT GUIDE TO BASIC FEATURE SET REQUIREMENTS Table of Contents 1 EXECUTIVE SUMMARY 4 2 INTRODUCTION 5 2.1 Overview 5 2.2 Scope 5 2.3 Definitions 6 2.4 Abbreviations 6 2.5 References 9 3 GSMA MINIMUM BAseLINE FOR LTE-M INTEROPERABILITY - PROBLEM STATEMENT 10 3.1 Problem Statement 10 3.2 Minimum Baseline for LTE-M Interoperability: Risks and Benefits 10 4 LTE-M DATA ARCHITECTURE 11 5 LTE-M DePLOYMENT BANDS 13 6 LTE-M FeATURE DePLOYMENT GUIDE 14 7 LTE-M ReLEAse 13 FeATURes 15 7.1 PSM Standalone Timers 15 7.2 eDRX Standalone 18 7.3 PSM and eDRX Combined Implementation 19 7.4 High Latency Communication 19 7.5 GTP-IDLE Timer on IPX Firewall 20 7.6 Long Periodic TAU 20 7.7 Support of category M1 20 7.7.1 Support of Half Duplex Mode in LTE-M 21 7.7.2 Extension of coverage features (CE Mode A / B) 21 7.8 SCEF 22 7.9 VoLTE 22 7.10 Connected Mode Mobility 23 7.11 SMS Support 23 7.12 Non-IP Data Delivery (NIDD) 24 7.13 Connected-Mode (Extended) DRX Support 24 7.14 Control Plane CIoT Optimisations 25 7.15 User Plane CIoT Optimisations 25 7.16 UICC Deactivation During eDRX 25 7.17 Power Class 26 LTE-M DEPLOYMENT GUIDE TO BASIC FEATURE SET REQUIREMENTS 8 LTE-M ReLEAse 14 FeATURes 27 8.1 Positioning: E-CID and OTDOA 27 8.2 Higher data rate support 28 8.3 Improvements of VoLTE and other real-time services 29 8.4 Mobility enhancement in Connected Mode 29 8.5 Multicast transmission/Group messaging 29 8.6 Relaxed monitoring for cell reselection 30 8.7 Release Assistance Indication -
A-Port User's Guide, Release 46.2 Copyright © 1993, 2015, Oracle And/Or Its Affiliates
Oracle® Communications EAGLE A-Port User©s Guide Release 46.2 E63583 Revision 1 July 2015 Oracle® Communications EAGLE A-Port User's Guide, Release 46.2 Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. -
Technical Architecture Alternatives for Open Connectivity Roaming Hubbing Model
GSM Association Non-confidential Official Document IR.80 - Technical Architecture Alternatives for Open Connectivity Roaming Hubbing Model Technical Architecture Alternatives for Open Connectivity Roaming Hubbing Model Version 2.0 26 February 2015 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © 2015 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V2.0 Page 1 of 95 GSM Association Non-confidential Official Document IR.80 - Technical Architecture Alternatives for -
Location Update Procedure
Location Update Procedure In order to make a mobile terminated call, The GSM network should know the location of the MS (Mobile Station), despite of its movement. For this purpose the MS periodically reports its location to the network using the Location Update procedure. Location Area (LA) A GSM network is divided into cells. A group of cells is considered a location area. A mobile phone in motion keeps the network informed about changes in the location area. If the mobile moves from a cell in one location area to a cell in another location area, the mobile phone should perform a location area update to inform the network about the exact location of the mobile phone. The Location Update procedure is performed: When the MS has been switched off and wants to become active, or When it is active but not involved in a call, and it moves from one location area to another, or After a regular time interval. Location registration takes place when a mobile station is turned on. This is also known as IMSI Attach because as soon as the mobile station is switched on it informs the Visitor Location Register (VLR) that it is now back in service and is able to receive calls. As a result of a successful registration, the network sends the mobile station two numbers that are stored in the SIM (Subscriber Identity Module) card of the mobile station. These two numbers are:- 1. Location Area Identity (LAI) 2. Temporary Mobile Subscriber Identity (TMSI). The network, via the control channels of the air interface, sends the LAI. -
ETSI TS 125 412 V9.0.0 (2010-01) Technical Specification
ETSI TS 125 412 V9.0.0 (2010-01) Technical Specification Universal Mobile Telecommunications System (UMTS); UTRAN Iu interface signalling transport (3GPP TS 25.412 version 9.0.0 Release 9) 3GPP TS 25.412 version 9.0.0 Release 9 1 ETSI TS 125 412 V9.0.0 (2010-01) Reference RTS/TSGR-0325412v900 Keywords UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. -
Cell Oscillation Resolution in Mobility Profile Building Cell Oscillation
Cell oscillation resolution in mobility profile building Shafqat Ali Shad 1, Enhong Chen 2 1 Department of Computer Science and Technology University of Science and Technology of China Huangshan Road, Hefei, 230027 Anhui, China [email protected] 2 Department of Computer Science and Technology University of Science and Technology of China Huangshan Road, Hefei, 230027 Anhui, China [email protected] Abstract depending on its configuration and methods used. As for Mobility profile building became extensively examined mobile users GPS is discouraging in term of high power area in Location based services (LBS) through extraction consumption and extra equipment installation in network. of significant locations. Mobility traces are recorded under This makes its use limited for positioning or location three reference positioning systems that are Satellite based extraction. While in case of Local positioning systems i.e. i.e. GPS, Network based i.e. GSM and Local positioning Bluetooth, RFID, Infrared, Wifi, IrDA they operate in i.e. WLAN, RFID, IrDA. Satellite based and local limited space area due to of its short range signal positioning due to of high power consumption, additional capabilities. So only viable solution for position extraction resource installation, low accuracy and space limitation are widely spread and examined is Network position system less encouraging. So network based positioning i.e. GSM i.e. GSM. While in case of GSM, location exaction can be is only viable solution for mobility tracing through Cell done through Assisted-GPS (A-GPS), Time difference of global identity (CGI). CGI presents the Cell-ids to extract arrival (TDOA) and Enhanced observed time difference the significant locations from mobility history. -
Miot Location in Roaming Version 1.0 20 May 2020
GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members Official Document NG.120 - MIoT Location in Roaming MIoT Location in Roaming Version 1.0 20 May 2020 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Confidential - Full, Rapporteur, Associate and Affiliate Members Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice Copyright © 2020 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V1.0 Page 1 of 37 GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members Official Document NG.120 - MIoT Location -
Physical Cell ID Allocation in Cellular Networks
Linköping University | Department of Computer Science Master thesis, 30 ECTS | Informationsteknologi 2016 | LIU-IDA/LITH-EX-A--16/039--SE Physical Cell ID Allocation in Cellular Networks Sofia Nyberg Supervisor : Kaj Holmberg Examiner : Niklas Carlsson Linköpings universitet SE–581 83 Linköping +46 13 28 10 00 , www.liu.se Upphovsrätt Detta dokument hålls tillgängligt på Internet – eller dess framtida ersättare – under 25 år från publiceringsdatum under förutsättning att inga extraordinära omständigheter uppstår. Tillgång till dokumentet innebär tillstånd för var och en att läsa, ladda ner, skriva ut enstaka kopior för enskilt bruk och att använda det oförändrat för ickekommersiell forskning och för undervisning. Överföring av upphovsrätten vid en senare tidpunkt kan inte upphäva detta tillstånd. All annan användning av dokumentet kräver upphovsmannens medgivande. För att garantera äktheten, säkerheten och tillgängligheten finns lösningar av teknisk och admin- istrativ art. Upphovsmannens ideella rätt innefattar rätt att bli nämnd som upphovsman i den omfattning som god sed kräver vid användning av dokumentet på ovan beskrivna sätt samt skydd mot att dokumentet ändras eller presenteras i sådan form eller i sådant sam- manhang som är kränkande för upphovsmannenslitterära eller konstnärliga anseende eller egenart. För ytterligare information om Linköping University Electronic Press se förlagets hemsida http://www.ep.liu.se/. Copyright The publishers will keep this document online on the Internet – or its possible replacement – for a period of 25 years starting from the date of publication barring exceptional circum- stances. The online availability of the document implies permanent permission for anyone to read, to download, or to print out single copies for his/hers own use and to use it unchanged for non-commercial research and educational purpose. -
USSD Gateway Technical Guide
Oracle® Communications Network Charging and Control USSD Gateway Technical Guide Release 12.0.0 December 2017 Copyright Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.