EP2954640A1 - Protocole de maintenance pour un système de réseau - Google Patents

Protocole de maintenance pour un système de réseau

Info

Publication number
EP2954640A1
EP2954640A1 EP13704576.1A EP13704576A EP2954640A1 EP 2954640 A1 EP2954640 A1 EP 2954640A1 EP 13704576 A EP13704576 A EP 13704576A EP 2954640 A1 EP2954640 A1 EP 2954640A1
Authority
EP
European Patent Office
Prior art keywords
data
local area
area network
protocol
maintenance
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP13704576.1A
Other languages
German (de)
English (en)
Inventor
Heikki Jarmo Tapani LAAKSONEN
Florent DEBAZAC
Eino Aku Tapio OINONEN
Jarmo Tolonen
Janne Juhani KOVANEN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
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
Application filed by Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Publication of EP2954640A1 publication Critical patent/EP2954640A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/26—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using dedicated tools for LAN [Local Area Network] management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/022—Multivendor or multi-standard integration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • Embodiments of the invention relate to a communication protocol that can carry information used to maintain a system.
  • the information can be communicated in accordance with the protocol to a user via a single interface.
  • the communication protocol carries configuration data and monitoring information that is typically transferred through an operatbn and maintenance (O&M) local-area network (LAN) as well as information that is typically transferred through LANs that are separate from the O&M LAN.
  • O&M operatbn and maintenance
  • LAN local-area network
  • a method may comprise receiving first data that is transmitted within a first local area network.
  • the first local area network is an operation-and- maintenance local area network.
  • the method may also comprise receiving second data that is transmitted within a second local area network, wherein the second local area network is different from and inaccessible by the first local area network.
  • the method may also comprise transmitting both the first data and the second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • transmitting both the first data and the second data in accordance with the protocol may comprise transmitting data relating to the maintenance of a mobile management entity.
  • transmitting both the first data and the second data in accordance with the protocol may comprise transmitting data to a single interface.
  • the protocol may comprise a maintenance protocol, a control protocol, and a transmission control protocol/transport layer security protocol.
  • an apparatus can comprise at least one processor.
  • the apparatus can also comprise at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured, with the at least one processor, to cause the apparatus at least to receive first data that is transmitted within a first local area network, wherein the first local area network is an operation-and-maintenance local area network.
  • the apparatus can also receive second data that is transmitted within a second local area network.
  • the second local area network is different from and inaccessible by the first local area network.
  • the apparatus can also transmit both the first data and the second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • transmitting both the first data and the second data in accordance with the protocol can comprise transmitting data relating to the maintenance of a mobile management entity.
  • transmitting both the first data and the second data in accordance with the protocol can comprise transmitting data to a single interface.
  • the protocol can comprise a maintenance protocol, a control protocol, and a transmissbn control protocol/transport layer security protocol.
  • a computer program product can be embodied on a computer readable medium .
  • the computer program product can be configured to control a processor to perform a process.
  • the process can comprise receiving first data that is transmitted within a first local area network, wherein the first local area network is an operation-and-maintenance local area network.
  • the process can also comprise receiving second data that is transmitted within a second local area network, wherein the second local area network is different from and inaccessible by the first local area network.
  • the process can also comprise transmitting both the first data and the second data in accordance with a protocol, wherein the first data and the second data relate to the maintenance of a network element.
  • a method can comprise receiving both first data and second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • the first data is data that is transmitted within a first local area network.
  • the first local area network is an operation-and-maintenance local area network.
  • the second data is data that is transmitted within a second local area network.
  • the second local area network is different from and inaccessible by the first local area network.
  • receiving both the first data and the second data in accordance with the protocol can comprise receiving data relating to the maintenance of a mobile management entity.
  • receiving both the first data and the second data in accordance with the protocol can comprise receiving data through a single interface.
  • the protocol can comprise a maintenance protocol, a control protocol, and a transmissbn control protocol transport layer security protocol.
  • an apparatus can comprise at least one processor.
  • the apparatus can also comprise at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured, with the at least one processor, to cause the apparatus at least to receive both first data and second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • the first data is data that is transmitted within a first local area network.
  • the first local area network is an operatbn-and-maintenance local area network.
  • the second data is data that is transmitted within a second local area network.
  • the second local area network is different from and inaccessible by the first local area network.
  • receiving both the first data and the second data in accordance with the protocol can comprise receiving data relating to the maintenance of a mobile management entity.
  • receiving both the first data and the second data in accordance with the protocol can comprise receiving data through a single interface.
  • the protocol can comprise a maintenance protocol, a control protocol, and a transmission control protocol/transport layer security protocol.
  • a computer program product can be embodied on a computer readable medium.
  • the computer program can be configured to control a processor to perform a process.
  • the process can comprise receiving both first data and second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • the first data is data that is transmitted within a first local area network.
  • the first local area network is an operation-and-maintenance local area network.
  • the second data is data that is transmitted within a second local area network.
  • the second local area network is different from and inaccessible by the first local area network.
  • a system can comprise a first apparatus.
  • the first apparatus can comprise at least one first processor.
  • the first apparatus can also comprise at least one first memory including first computer program code.
  • the at least one first memory and the first computer program code can be configured, with the at least one first processor, to cause the first apparatus at least to receive first data that is transmitted within a first local area network.
  • the first local area network is an operation-and-maintenance local area network.
  • the first apparatus can also receive second data that is transmitted within a second local area network.
  • the second local area network is different from and inaccessible by the first local area network.
  • the first apparatus can also transmit both the first data and the second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • the system can also comprise a second apparatus.
  • the second apparatus can comprise at least one second processor.
  • the second apparatus can also comprise at least one second memory including second computer program code.
  • the second apparatus can also comprise at least one second memory and the second computer program code configured, with the at least one second processor, to cause the second apparatus at least to receive both the first data and the second data in accordance with the protocol.
  • FIG. 1 illustrates connecting to a network element via an O&M LAN.
  • Fig. 2 illustrates functbnal units of a network element.
  • Fig. 3 illustrates a protocol stack used to carry data from a network element to a maintenance application.
  • Fig. 4 illustrates, according to one embodiment, a protocol stack of a communication protocol.
  • Fig. 5 illustrates, according to one embodiment, the configuration between a maintenance application and a network element.
  • FIG. 6 illustrates a flow diagram of a method according to an embodiment:
  • FIG. 7 illustrates an apparatus according to another embodiment:
  • FIG. 8 illustrates an apparatus according to another embodiment:
  • FIG. 9 illustrates an apparatus according to another embodiment:
  • the different functions discussed below can be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions can be optional or can be combined. As such, the folbwing descriptbn should be considered as merely illustrative of the principles, teachings, and embodiments of this invention, and not in limitation thereof.
  • the previous approaches would generally manually connect to each CPU blade to receive the necessary information from each CPU blade.
  • the previous approaches were generally directed to establishing connections with each CPU blade using a Telnet protocol to get information relating to CPU loads.
  • Fig. 1 illustrates connecting to a network element 103 via an O&M LAN 102.
  • Fig. 1 shows two different separated LANs.
  • O&M LAN 102 can be separated from a signaling/data LAN 104.
  • signaling/data LAN 104 can contain information that is needed to be received by user 101. As shown in Fig.
  • O&M LAN 102 and signaling/data LAN 104 can separate the two LANs using a firewall 1 10.
  • O&M LAN 102 and signaling/data LAN 104 can also each be implemented within separately operating blades, for example.
  • operators of different LANs can wish to separate the operability of each of the LANs in order to more securely manage the data that is transferred within each LAN.
  • separating LANs can better secure the data transferred within each LAN. the user, upon connecting to O&M LAN 102, generally cannot readily receive the data communicated via signaling/data LAN 104.
  • the network element of Fig. 2 can correspond to network element 103 of Fig. 1 , for example.
  • the functional units of a network element can include an operation and maintenance unit (OMU) 201 , a mobility management and database unit (MMDU) 203, a control plane processing unit (CPPU) 204, and an internet protocol director unit (IPDU) 205, for example.
  • the functbnal units of the network element can be connected to each other via switching unit (SWU) 202.
  • the OMU 201 may be in communication with marker and charging unit (MCHU) 220, which can offer statistics functions, and which can be equipped with its own rear transition module (RTM) having its own hard disk drive (HDD).
  • MCHU 220 can be provided with both a base interface (Bl) and a fabric interface (Fl) that connect the MCHU 220 to other units via SWU 202.
  • the other devices of the network system may be connected using an EL0 interface, or generally any Ethernet or other network interface.
  • the OMU 201 can be in communication with IPDU 205, which can provide load balancing and connectivity, and which can be equipped with its own RTM having its own HDD.
  • IPDU 205 can provide 3rd Generation Partnership Project (3GPP) interfaces like S1- MME, S1 1 , S3/Gn and S10.
  • 3GPP 3rd Generation Partnership Project
  • the OMU 201 may be in communication with MMDU 203, which can store visiting subscriber information into a visiting subscriber database.
  • the MMDU 203 may also be able to control an evolved packet system (EPS) mobility management and EPS system management level functions for LTE subscribers.
  • EPS evolved packet system
  • the OMU 201 can further be in communication with CPPU 204.
  • the CPPU 204 may provide transaction-based mobility management.
  • the OMU 201 can be configured to communicate using a maintenance protocol and a control protocol, and may serve as a maintenance proxy for O&M LAN 102.
  • the units MMDU 203, CPPU 204, and IPDU 205, or any other unit hosted in a network element, can each be configured as a remote maintenance server and may be configured to use simple object access protocol (SOAP).
  • SOAP simple object access protocol
  • Signaling/data LAN 104 that connects the various remote servers may be maintained in isolatbn from O&M LAN 102.
  • a maintenance application When a maintenance application registers from an interface of the user 101 to an OMU of network element 103, it can use a control protocol. Any desired login credentials can be used, but in certain embodiments, only a single set of login credentials are needed. 100461 MME configuration information can be exchanged via a maintenance protocol. Troubleshooting information can be delivered, with the help of a maintenance proxy in the OMU of network element 103, from the maintenance units (for example, MMDU 203, CPPU 204, and IPDU 205), which may, for example, be Linux units.
  • the maintenance units for example, MMDU 203, CPPU 204, and IPDU 205
  • Fig. 3 illustrates a protocol stack used to carry data from a network element (303, 305) to a maintenance application 301.
  • INT 304 corresponds to an interface for internal communication within the network element (303, 305).
  • INT 304 can be a signaling/data LAN within the network element (303, 305) that is separate from O&M LAN 302.
  • INT 304 can be used to carry data between different CPU blades, as discussed in more detail below.
  • a user 301 can access OMU 303 via O&M LAN 302.
  • O&M LAN 302 is separate from INT 304, the user 301 can have difficulty accessing INT 304 and LinDX 305. Therefore, as previously described, the user cannot readily receive data that is communicated via INT 304.
  • one embodiment of the present invention relates to a single communication protocol/interface that can be used to access all the necessary maintenance and troubleshooting informatbn. Specifically, one embodiment provides a way for a single communication interface to access data from an O&M LAN as well as data from LANs different and separate from the O&M LAN.
  • Fig. 4 illustrates, according to one embodiment, a protocol stack of a communication protocol.
  • the protocol stack of Fig. 4 can access data from an O&M LAN as well as from other LANs.
  • the protocol stack can be a Flexi Network Server (NS) Maintenance InterfaceTM protocol stack.
  • the communication protocol stack can be extend ed/config u red to carry all of the information necessary for maintaining a network element.
  • the information can be advanced telecommunications computing architecture (ATCA) configuration information.
  • the protocol stack can also carry signaling data that is communicated within different CPU blades.
  • ATCA advanced telecommunications computing architecture
  • a maintenance application agent 417 can be implemented within an O&M unit 407 of a network element 406 that enables connectivity to external applications, such as a web server 401.
  • maintenance application agent 417 can be a Flexi Maintenance ApplicationTM (FMA) agent that is implemented within an O&M unit 407 of a network element 406 that enables connectivity to an FMA Web Server, for example.
  • FMA Flexi Maintenance ApplicationTM
  • Maintenance application agent 417 can communicate different kinds of troubleshooting data. Maintenance personnel can use web server 401 to access the O&M Unit 407.
  • the network element can also include a processing unit 408 that processes signaling/data information.
  • processing unit 408 can be a Linux unit.
  • signaling/data information from processing unit 408 is routed to O&M Unit 407.
  • Maintenance application agent 417 of O&M Unit 407 can then transmit the signaling/data information to web server 401 , as described in more detail below.
  • Web server 401 can run on top of an application server 410, such as a TomcatTM server provided by Apache Software Foundation, for example.
  • Application server 410 can provide a graphical user interface (GUI) 412 for the user.
  • GUI graphical user interface
  • Application server 410 can also include application logic 41 1 to be used in conjunctbn with network elements.
  • Web server 401 can communicate with network element 406 in accordance with a communication protocol 402-405.
  • the communication protocol includes a maintenance protocol 402, a control protocol 403, a transmission control protocol / transport layer security (TCP TLS) protocol 404, and/or an internal channel 405.
  • maintenance protocol 402 can be Flexi Maintenance ProtocolTM (FMP), for example.
  • control protocol 403 can be Flexi Network Server Control ProtocolTM (FnsCP), for example.
  • internal channel 405 can be FlexiNS Internal ChannelTM (FnsIC), for example.
  • the communication protocol can use user datagram protocol (UDP) or shell (SSH) protocol.
  • UDP user datagram protocol
  • SSH shell
  • Web server 401 can be used by any device that allows the use of web browsers.
  • Web server 401 can be a maintenance and troubleshooting application for a mobility management entity, for a serving gateway (SGW), and for packet data network gateway (PDN GW) products in a packet core.
  • the mobility management entity can be a Nokia Siemens NetworksTM (NSN) 3GPP MME.
  • webserver 401 can be a maintenance and troubleshooting application for an NSN 3GPP Serving Gateway.
  • Fig. 4 illustrates communication between a network element 406 and a web server 401
  • network element 406 can be in communication with devices different than web servers.
  • Network element 406 can be in communication with devices that run applications unrelated to web browsers.
  • maintenance protocol 402 can be used to communicate information relating to logs.
  • Logs can refer to information written by application processes.
  • logs can contain information written by application processes of a mobility management entity. Such information can be stored within log files.
  • signaling information sent within LANs different and separate from an O&M LAN are typically not available to the O&M LAN.
  • One example of such signaling information is "adapt" signals.
  • "Adapt" signals can generally be considered to be signals that allow network elements to adapt to a network.
  • a protocol can be used to communicate information from the O&M LAN as well as "adapt” signals that are communicated within LANs different from the O&M LAN.
  • a user can utilize connectivity provided by O&M unit 407 to periodically trigger requests directed to the system so that the system provides data relating to CPU loads or subscriber counts. This data can be used to draw real-time graphs and visualizatbns to illustrate the information.
  • Fig. 5 illustrates, according to one embodiment, the configuration between a maintenance application 501 and a network element.
  • the network element of Fig. 5 can correspond to a mobile management entity (MME) 503, for example.
  • Maintenance application 501 can correspond to web server 401 of Fig. 4.
  • Mobile management entity 503 can correspond to network element 406 of Fig. 4.
  • Interface 502 can correspond to an interface between maintenance application 501 and mobile management entity 503.
  • maintenance application 501 is connected to MME 503, in other embodiments, maintenance application 501 can be connected to other network elements such as SGW 504, packet data network gateway (PGW) 505, policy and charging rules function (PCRF) element 506, authentication/authorization/accounting (AAA) element 507, and home subscriber server (HSS) 508, for example.
  • PGW packet data network gateway
  • PCRF policy and charging rules function
  • AAA authentication/authorization/accounting
  • HSS home subscriber server
  • One embodiment is directed to the maintenance and troubleshooting of network elements.
  • one embodiment is directed to the maintenance and troubleshooting of network elements that are found in Global System for Mobile Communications/3GPP (GSMTM/3GPP) networks.
  • GSMTM/3GPP Global System for Mobile Communications/3GPP
  • the above-described connectivity protocols can help to collect maintenance and troubleshooting information to speed up problem solving in product configurations.
  • One embodiment is directed to an external application that connects to a network element and uses a single interface to collect information about the network to allow a user to perform troubleshooting.
  • the external application connects to a 3GPP MME network element of an O&M network.
  • Fig. 6 illustrates a flow diagram of a method according to an embodiment.
  • the method illustrated in Fig. 6 includes, at 610, receiving first data that is transmitted within a first local area network, wherein the first local area network is an operation-and-maintenance local area network.
  • At 620 one embodiment receives second data that is transmitted within a second local area network.
  • the second local area network is different from, and can be inaccessible and/or separated from, the first local area network.
  • one embodiment transmits both the first data and the second data in accordance with a protocol.
  • the first data and the second data relate to the maintenance of a network element.
  • apparatus 10 can be a transmitting system, such as a network element, for example.
  • apparatus 10 can be a receiving device, such as a web server, for example.
  • Apparatus 10 can include a processor 22 for processing information and executing instructions or operations.
  • Processor 22 can be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 7, multiple processors can be utilized according to other embodiments.
  • Processor 22 can also include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.
  • Apparatus 10 can further include a memory 14, coupled to processor 22, for storing information and instructions that can be executed by processor 22.
  • Memory 14 can be one or more memories and of any type suitable to the local application environment, and can be implemented using any suitable volatile or nonvolatile data storage technology such as a sem icond uctor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory.
  • memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media.
  • the instructions stored in memory 14 can include program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.
  • Apparatus 10 can also include one or more antennas (not shown) for transmitting and receiving signals and/or data to and from apparatus 10.
  • Apparatus 10 can further include a transceiver 28 that modulates information on to a carrier waveform for transmissbn by the antenna(s) and demodulates informatbn received via the antenna(s) for further processing by other elements of apparatus 10.
  • transceiver 28 can be capable of transmitting and receiving signals or data directly.
  • Processor 22 can perform functbns associated with the operation of apparatus 10 including, without limitatbn, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communicatbn message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.
  • memory 14 stores software modules that provide functionality when executed by processor 22.
  • the modules can include an operating system 15 that provides operating system functionality for apparatus 10.
  • the memory can also store one or more functional modules 18, such as an application or program, to provide additional functionality for apparatus 10.
  • the components of apparatus 10 can be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 800 can be a transmitting system.
  • Apparatus 800 can include first receiving unit 81 1 configured to receive first data that is transmitted within a first local area network.
  • the first local area network can be an operation-and-maintenance local area network.
  • Apparatus 800 can also include second receiving unit 812 configured to receive second data that is transmitted within a second local area network.
  • the second local area network is different from, and can be inaccessible to and/or separated from , the first local area network.
  • Apparatus 800 can also include a transmitting unit 813 configured to transmit both the first data and the second data in accordance with a protocol, wherein the first data and the second data relate to the maintenance of a network element.
  • apparatus 920 can be a receiving system.
  • Apparatus 920 can include a receiving unit 921 configured to receive both first data and second data in accordance with a protocol, wherein the first data and the second data relate to the maintenance of a network element, the first data is data that is transmitted within a first local area network, the first local area network is an operation-and-maintenance local area network, the second data is data that is transmitted within a second local area network, and the second local area network is different from and inaccessible by the first local area network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente invention concerne un procédé et un appareil pouvant être configurés pour réaliser les étapes consistant à recevoir des premières données transmises au sein d'un premier réseau local. Le premier réseau local est un réseau local d'exploitation et de maintenance. Le procédé comprend en outre la réception de secondes données transmises au sein d'un second réseau local. Le second réseau local est différent du premier réseau local et est inaccessible par ce dernier. Le procédé comprend par ailleurs la transmission des premières données et des secondes données conformément à un protocole. Les premières données et les secondes données se rapportent à la maintenance d'un élément de réseau.
EP13704576.1A 2013-02-07 2013-02-07 Protocole de maintenance pour un système de réseau Withdrawn EP2954640A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/052377 WO2014121834A1 (fr) 2013-02-07 2013-02-07 Protocole de maintenance pour un système de réseau

Publications (1)

Publication Number Publication Date
EP2954640A1 true EP2954640A1 (fr) 2015-12-16

Family

ID=47720489

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13704576.1A Withdrawn EP2954640A1 (fr) 2013-02-07 2013-02-07 Protocole de maintenance pour un système de réseau

Country Status (2)

Country Link
EP (1) EP2954640A1 (fr)
WO (1) WO2014121834A1 (fr)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7228345B2 (en) * 2002-10-15 2007-06-05 Hewlett-Packard Development Company, L.P. Server with LAN switch that connects ports based on boot progress information
US7852873B2 (en) * 2006-03-01 2010-12-14 Lantronix, Inc. Universal computer management interface

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO2014121834A1 *

Also Published As

Publication number Publication date
WO2014121834A1 (fr) 2014-08-14

Similar Documents

Publication Publication Date Title
US11425564B2 (en) Wireless services gateway
US11019077B2 (en) Multi-access distributed edge security in mobile networks
US11051192B2 (en) Network data analytics in a communications network
US20210144183A1 (en) Network slice-based security in mobile networks
EP3085148B1 (fr) Procédé et appareil pour réaliser un chaînage de service flexible
TWI608717B (zh) 資料管理行動性政策
EP3735770B1 (fr) Sécurité de bord distribué à accès multiple dans des réseaux mobiles
US9392025B2 (en) Subscriber dependent redirection between a mobile packet core proxy and a cell site proxy in a network environment
US9113400B2 (en) Method and apparatus for offloading packet traffic from LTE network to WLAN using DPI
EP3837867B1 (fr) Sécurité basée sur une tranche de réseau dans des réseaux mobiles
US10547647B2 (en) Intra-carrier and inter-carrier network security system
US20180183717A1 (en) System and method for low-overhead interoperability between 4g and 5g networks
US20160353353A1 (en) Methods and systems for communications through a slave gateway
US10979349B2 (en) Methods and apparatuses for flexible mobile steering in cellular networks
EP4114061A1 (fr) Système de gestion de réseau pour embarquer des dispositifs clients hétérogènes dans des réseaux sans fil
WO2014121834A1 (fr) Protocole de maintenance pour un système de réseau
WO2014121835A1 (fr) Connectivité de maintenance dans un système avancé d'architecture informatique de télécommunications
WO2023150605A1 (fr) Architecture de sixième génération (6g) activée par maillage de service

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150907

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20170925

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20180206