EP3282718A1 - Accorder des senseurs avec des applications sur un serveur à la limite du réseau - Google Patents

Accorder des senseurs avec des applications sur un serveur à la limite du réseau Download PDF

Info

Publication number
EP3282718A1
EP3282718A1 EP16196272.5A EP16196272A EP3282718A1 EP 3282718 A1 EP3282718 A1 EP 3282718A1 EP 16196272 A EP16196272 A EP 16196272A EP 3282718 A1 EP3282718 A1 EP 3282718A1
Authority
EP
European Patent Office
Prior art keywords
mec
edge
sensor nodes
operating modes
devices
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
EP16196272.5A
Other languages
German (de)
English (en)
Inventor
Vikas Shah
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.)
Wipro Ltd
Original Assignee
Wipro Ltd
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 Wipro Ltd filed Critical Wipro Ltd
Publication of EP3282718A1 publication Critical patent/EP3282718A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • 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
    • Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
    • Y04S40/18—Network protocols supporting networked applications, e.g. including control of end-device applications over a network

Definitions

  • the present subject matter is related, in general to communication systems, and more particularly, but not exclusively to a method and a system for identifying operating modes of communications in a mobile-edge computing environment.
  • MEC Mobile edge computing
  • IT Information Technology
  • RAN radio access network
  • MEC separates functionality from the underlying hardware infrastructure to increase mobile network flexibility, economy and scale.
  • MEC empowers computational power into the mobile RAN, and it promotes virtualized software based ecosystems at the radio edge.
  • the MEC platforms enable virtualized applications to run much closer to mobile users to boost the user experience.
  • IoT Internet of things
  • a method for communication between one or more sensor nodes associated with one or more sensor devices, and one or more mobile edge computing devices associated with one or more edge users comprising: defining, by a mobile edge computing server, one or more applications for which a sensor node and sensor device may be used, and one or more dimensions associated with each of the one or more applications; identifying, by the mobile edge computing server, one or more operating modes associated with the one or more sensor nodes based on the one or more dimensions, wherein each of the one or more operating modes are associated with one or more communication channels; and receiving, by the mobile edge computing server, information captured by the one or more sensor nodes associated with the one or more sensor devices based on the identified one or more operating modes, via the associated one or more communication channels.
  • a method for communication between one or more IoT sensor nodes associated with one or more IoT sensor devices, and one or more mobile edge computing (MEC) devices associated with one or more edge users comprises defining, by a mobile edge computing (MEC) server, one or more business verticals and one or more dimensions associated with each of the one or more business verticals.
  • the method further comprises identifying, by the MEC server, one or more operating modes associated with the one or more IoT sensor nodes based on the one or more dimensions, wherein each of the one or more operating modes are associated with one or more communication channels.
  • the method further comprises receiving, by the MEC server, information captured by the one or more IoT sensor nodes associated with the one or more IoT sensor devices based on the identified one or more operating modes, via the associated one or more communication channels.
  • the term business vertical may be used to describe an application for which an IoT sensor node and an IoT sensor device may be used.
  • the method may further comprise creating one or more edge services associated with the one or more communication channels for the one or more MEC devices based on the received information, wherein the one or more edge services comprise metadata of the one or more operating modes and the associated one or more communication channels, wherein the metadata comprises service identification number, a message sequence number, number of IoT sensor nodes, a channel number associated with each of the one or more communication channels, a serial number of the one or more IoT sensor nodes, and a timestamp.
  • the method may further comprise extending the metadata to include one or more updates necessary to identify the one or more edge services and the one or more operating modes. Alternatively or in addition, the method may further comprise updating the metadata based on an association between each of the one or more operating modes and the one or more communication channels.
  • the association between the one or more operating modes and the one or more edge services associated with the one or more communication channels is determined based on the metadata.
  • the method may further comprise receiving a subscription request for one or more edge services associated with the one or more communication channels from the one or more MEC devices associated with the one or more edge users.
  • the method may further comprise transmitting the information captured by the one or more IoT sensor nodes to the one or more MEC devices associated with the one or more edge users via the one or more communication channels based on the subscription request and the metadata in the one or more edge services, wherein the information associated with the subscription request for the one or more edge services associated with the one or more communication channels is transmitted via the one or more communication channels associated with the one or more edge services.
  • the method may further comprise monitoring a change in the one or more business verticals and one or more dimensions; and updating the one or more operating modes associated with the one or more IoT sensor nodes based on the monitoring.
  • the method may further comprise communicating the identified one or more operating modes to the one or more IoT sensor nodes.
  • the one or more dimensions may correspond to a set of values obtained from the one or more IoT sensor nodes, wherein the one or more dimensions may be specific to each of the one or more business verticals, and wherein the one or more business verticals may comprise at least one of smart grid, smart healthcare, smart cars, and smart homes.
  • the one or more operating modes may specify the information that is to be transmitted across the one or more communication channels.
  • the information may comprises a type of each of the one or more IoT sensor nodes, device specification of each of the one or more MEC devices, data captured by each of the one or more IoT sensor nodes, and type of data captured by each of the one or more IoT sensor nodes.
  • the one or more IoT sensor nodes may transmit the information captured by the one or more IoT sensor nodes based on the one or more operating modes.
  • the method may further comprise updating the one or more business verticals and one or more dimensions associated with each of the one or more business verticals based on user inputs.
  • a MEC server for communication between one or more IoT sensor nodes associated with one or more IoT sensor devices, and one or more mobile edge computing (MEC) devices associated with one or more edge users.
  • the MEC server comprises a processor and a memory communicatively coupled to the processor.
  • the memory stores processor instructions, which, on execution, causes the processor to define one or more business verticals and one or more dimensions associated with each of the one or more business verticals.
  • the processor may be further configured to identify one or more operating modes associated with the one or more IoT sensor nodes based on the one or more dimensions, wherein each of the one or more operating modes are associated with one or more communication channels.
  • the processor may be further configured to receive information captured by the one or more IoT sensor nodes associated with the one or more IoT sensor devices based on the identified one or more operating modes, via the associated one or more communication channels.
  • the processor may be further configured to create one or more edge services associated with the one or more communication channels for the one or more MEC devices based on the received information, wherein the one or more edge services comprise metadata of the one or more operating modes and the associated one or more communication channels, wherein the metadata comprises service identification number, a message sequence number, number of IoT sensor nodes, a channel number associated with each of the one or more communication channels, a serial number of the one or more IoT sensor nodes, and a timestamp.
  • the processor may be further configured to extend the metadata to include one or more updates necessary to identify the one or more edge services and the one or more operating modes.
  • the processor may be further configured to update the metadata based on an association between each of the one or more operating modes and the one or more communication channels.
  • the association between the one or more operating modes and the one or more edge services associated with the one or more communication channels may be determined based on the metadata.
  • the processor may be further configured to receive a subscription request for one or more edge services associated with the one or more communication channels from the one or more MEC devices associated with the one or more edge users.
  • the processor may be further configured to transmit the information captured by the one or more IoT sensor nodes to the one or more MEC devices associated with the one or more edge users via the one or more communication channels based on the subscription request and the metadata in the one or more edge services, wherein the information associated with the subscription request for the one or more edge services associated with the one or more communication channels is transmitted via the one or more communication channels associated with the one or more edge services.
  • a non-transitory computer-readable storage medium having stored thereon, a set of computer-executable instructions for causing a computer comprising one or more processors to perform steps of defining one or more business verticals and one or more dimensions associated with each of the one or more business verticals.
  • the one or more processors may be configured to identify one or more operating modes associated with one or more IoT sensor nodes based on the one or more dimensions, wherein each of the one or more operating modes are associated with one or more communication channels.
  • the one or more processors may be configured to receive information captured by the one or more IoT sensor nodes associated with one or more IoT sensor devices based on the identified one or more operating modes, via the associated one or more communication channels.
  • references to "one embodiment,” “at least one embodiment,” “an embodiment,” “one example,” “an example,” “for example,” and so on indicate that the embodiment(s) or example(s) may include a particular feature, structure, characteristic, property, element, or limitation but that not every embodiment or example necessarily includes that particular feature, structure, characteristic, property, element, or limitation. Further, repeated use of the phrase “in an embodiment” does not necessarily refer to the same embodiment.
  • Mobile Edge Computing (MEC) server may refer to a computing device that has the ability to run Information Technology (IT) services at the edge of mobile Radio Access Network (RAN) based on the concepts of cloud computing.
  • edge in this context means the radio base station itself (eNodeB, RNC, etc.), and servers within the RAN (e.g. at "aggregation points”).
  • eNodeB radio base station
  • RNC Radio Access Network
  • the presence of MEC server at the edge of the RAN allows exposure to real-time radio and network information (such as subscriber location, cell load, etc.) that can be leveraged by applications and services to offer context-related services to one or more edge users.
  • IoT sensor nodes may refer to devices that detects/measures events or changes in quantities and provides a corresponding output, generally as an electrical or optical signal.
  • the terms "IoT sensor node” and “sensor node” are used interchangeably herein.
  • one or more IoT sensor nodes may be connected to one or more IoT sensor devices via a communication media such as, the mobile RAN, a WiFi network, a wired network, and WiMAX.
  • the sensor may be operable to detect biological, physical, and/or chemical signals associated with first patient and may measure and record those signals.
  • pressure sensors, temperature sensors, and humidity sensors are used to monitor and regulate gas flow and gas conditions in Anesthesia Machines, Respirators and Ventilators.
  • IoT sensor devices refers to a computer, a device including a processor/microcontroller and/or any other electronic component, device or system that performs one or more operations according to one or more programming instructions.
  • the terms "IoT sensor device” and “sensor device” are used interchangeably herein.
  • the one or more IoT sensor nodes may be communicatively coupled with the one or more IoT sensor devices via the mobile RAN. Examples of the IoT sensor devices include, but are not limited to, a desktop computer, a laptop, a personal digital assistant (PDA), a Smartphone, or the like.
  • PDA personal digital assistant
  • the computing device is capable of accessing (or being accessed over) a network (e.g., using wired or wireless communication capabilities)
  • Edge users refers to users associated with the MEC devices.
  • the edge users may utilize the MEC devices to subscribe to one or more edge services offered by the MEC server.
  • MEC devices refers to a computer, a device including a processor/microcontroller and/or any other electronic component, device or system that performs one or more operations according to one or more programming instructions. Examples of the MEC device include, but are not limited to, a desktop computer, a laptop, a personal digital assistant (PDA), a Smartphone, or the like.
  • PDA personal digital assistant
  • the MEC device is capable of accessing (or being accessed over) a network (e.g., using wired or wireless communication capabilities).
  • Mobile edge application refers to applications that can be instantiated on a MEC server within a mobile edge system and can potentially provide or consume mobile edge services.
  • one or more rules may be associated with the mobile edge application.
  • the one or more rules may comprise at least required resources, maximum latency, traffic rules, Domain Name Server (DNS) rules, and mobility support.
  • DNS Domain Name Server
  • MEC server level management refers to components that handle the management of the functionalities of the MEC devices of a particular mobile edge platform, MEC server and the mobile edge applications running on the MEC server.
  • Mobile edge platform refers to a collection of functionality that is required to run mobile edge applications on a virtualization infrastructure in a MEC server and to enable the MEC server to provide and consume mobile edge services.
  • Mobile edge service refers to service provided via the mobile edge platform either by the mobile edge platform itself or by a mobile edge application.
  • Mobile edge system refers to a collection of MEC servers to run mobile edge applications within a mobile RAN or a subset of the mobile RAN.
  • FIG. 1 is a diagram that illustrates a Mobile Edge Computing (MEC) environment 100 in which various embodiments of the method and the system may be implemented.
  • MEC Mobile Edge Computing
  • FIG. 1 offers application developers and content providers cloud-computing capabilities and an Information Technology (IT) service environment at the edge of mobile Radio Access Network (RAN) 110.
  • IT Information Technology
  • RAN Mobile Radio Access Network
  • the MEC environment 100 may include one or more IoT sensor nodes 102, one or more IoT sensor devices 104 associated with the one or more IoT sensor nodes 102, a MEC server 106, an edge cloud 108, a mobile Radio Access Network (RAN) 110, an Application Programming Interface (API) 112 associated with the mobile RAN 110, developer and customer community 114, a demilitarized zone (DMZ) 116, one or more enterprise devices 118, a private cloud 120, one or more Mobile edge computing (MEC) devices 122, and a communication network 124.
  • the MEC server 106 may reside within the edge cloud 108 as represented in FIG. 1 .
  • the developer and customer community 114 may utilize the API 112 associated with the mobile RAN 110 to access information associated with the mobile RAN 110.
  • Each of the one or more IoT sensor devices 104 may communicatively coupled to the one or more IoT sensor nodes 102, the MEC server 106 and the mobile RAN 110.
  • the one or more IoT sensor devices 104 may communicatively coupled to the one or more IoT sensor nodes 102 via the communication network 124.
  • the one or more MEC devices 122 may be associated with one or more edge users.
  • one or more enterprise devices 118 in an enterprise may be communicatively coupled to the mobile RAN 110 via the DMZ 116.
  • the one or more enterprise devices 118 may be communicatively coupled to the private cloud 120 associated with the enterprise.
  • the one or more IoT sensor nodes 102 may refer to a device that detects/measures events or changes in quantities and provides a corresponding output, generally as an electrical or optical signal.
  • one or more IoT sensor nodes 102 may be connected to one or more IoT sensor devices 104 via the mobile RAN 110.
  • the sensor may be operable to detect biological, physical, and/or chemical signals associated with first patient and may measure and record those signals.
  • pressure sensors, temperature sensors, and humidity sensors are used to monitor and regulate gas flow and gas conditions in Anesthesia Machines, Respirators and Ventilators.
  • the one or more IoT sensor devices 104 refers to a computer, a device including a processor/microcontroller and/or any other electronic component, device or system that performs one or more operations according to one or more programming instructions.
  • the one or more IoT sensor nodes 102 may be communicatively coupled with the one or more IoT sensor devices 104 via the mobile RAN 110.
  • Examples of the IoT sensor devices 104 include, but are not limited to, a desktop computer, a laptop, a personal digital assistant (PDA), a Smartphone, or the like.
  • the computing device is capable of accessing (or being accessed over) a network (e.g., using wired or wireless communication capabilities).
  • the MEC server 106 may refer to a computing device that has the ability to run Information Technology (IT) services at the edge of mobile Radio Access Network (RAN) 110 based on the concepts of cloud computing.
  • edge in this context means the radio base station itself (eNodeB, Radio Network Controller (RNC), etc.), and servers within the mobile RAN 110 (e.g. at "aggregation points").
  • the MEC server 106 may be implemented at cellular base stations to provide flexible and rapid deployment of new applications and services for customers.
  • the MEC server 106 may be considered as a cloud server running at the edge of the mobile RAN 110.
  • the MEC server 106 may be configured to perform one or more specific tasks that cannot be achieved with the traditional network infrastructure.
  • the MEC server 106 may be configured to enable applications and services to be hosted on top of the mobile network elements, i.e. above the network layer.
  • the presence of MEC server 106 at the edge of the mobile RAN 110 allows exposure to real-time radio and network information (such as subscriber location, cell load, etc.) that can be leveraged by applications and edge services to offer context-related services to one or more edge users.
  • the edge cloud 108 refers to a cloud computing environment in which the MEC server 106 may be implemented. As the applications and services are implemented on the MEC server 106 that is at the edge of the mobile RAN 110, thus the applications and services are in close proximity to the customer. Hence, by running applications and performing related processing tasks closer to a cellular customer, network congestion is reduced and applications perform better.
  • the one or more MEC devices 122 may be associated with one or more edge users.
  • the one or more edge users may utilize the one or more MEC devices 122 to communicate with the MEC server 106 and subscribe to one or more services via the mobile RAN 110.
  • the one or more MEC devices 122 refers to a computer, a device including a processor/microcontroller and/or any other electronic component, device or system that performs one or more operations according to one or more programming instructions. Examples of the MEC device include, but are not limited to, a desktop computer, a laptop, a personal digital assistant (PDA), a Smartphone, or the like.
  • PDA personal digital assistant
  • the MEC device is capable of accessing (or being accessed over) a network (e.g., using wired or wireless communication capabilities).
  • the communication network 124 may be utilized to communicate the information captured by the one or more IoT sensor nodes 102 to the one or more IoT sensor devices 104.
  • one or more IoT sensor nodes 102 may communicate the information captured by the one or more IoT sensor nodes 102 to the one or more IoT sensor devices 104 via the communication network 124, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN).
  • the communication network 124 such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN).
  • LAN wireless local area network
  • MAN metropolitan area network
  • the wireless communication may use any of a plurality of communication standards, protocols and technologies, such as: Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS).
  • GSM Global System for Mobile Communications
  • EDGE Enhanced Data GSM Environment
  • W-CDMA wideband code division multiple access
  • CDMA code division multiple access
  • TDMA time division multiple access
  • Wi-Fi e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n
  • VoIP voice over Internet Protocol
  • Wi-MAX a protocol for email, instant messaging
  • the mobile RAN 110 may correspond to a communication medium through which the one or more IoT sensor nodes 102, the one or more IoT sensor devices 104, the MEC server 106, and the one or more MEC devices 122 may communicate with each other.
  • a communication may be performed, in accordance with various wired and wireless communication protocols.
  • wired and wireless communication protocols include, but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), ZigBee, EDGE, infrared (IR), IEEE 802.11, 802.16, 2G, 3G, 4G, 5G cellular communication protocols, and/or Bluetooth (BT) communication protocols.
  • the API 112 may be accessible to the developer and customer community 114 to develop one or more edge services that may be run on the MEC server 106.
  • the one or more enterprise devices 118 in the enterprise may be communicatively coupled to the mobile RAN 110 via the DMZ 116.
  • the DMZ 116 or demilitarized zone (sometimes referred to as a perimeter network) is a physical or logical subnetwork that contains and exposes an organization's external-facing services to an untrusted network, such as the Internet or the mobile RAN 110.
  • the purpose of the DMZ 116 is to add an additional layer of security to an organization's local area network (LAN).
  • the one or more enterprise devices 118 may be communicatively coupled to the private cloud 120 associated with the enterprise.
  • the users of the one or more enterprise devices 118 may be enabled to subscribe to one or more edge services hosted by the MEC server 106.
  • the communication between the one or more IoT sensor nodes 102 associated with the one or more IoT sensor devices 104, the one or more MEC devices 122 and the MEC server 106 has been discussed later in conjunction with FIG. 3 .
  • the MEC environment 100 is characterized by ultra-low latency and high bandwidth as well as real-time access to mobile RAN information that can be leveraged by mobile edge applications.
  • the MEC environment 100 may enable new services for consumers and enterprise customers. Use cases of such services may comprise video analytics, location services, Internet-of-Things (IoT), augmented reality, optimized local content distribution, data caching.
  • IoT Internet-of-Things
  • MEC environment 100 enhances the mobile RAN 110 with MEC server 106 that enable applications to run in the mobile edge. Due to the proximity of the MEC server 106 into the mobile RAN 110, there is a latency reduction of delivering such applications or services. Such applications can expose information that can be used to optimize the network and services, reduce latency, and support creating personalized and contextualized services.
  • Internet of Things (IOT) applications or enterprise communications can benefit greatly from environment 100, as it allows service delivery in close proximity to the actual mobile edge devices such as, the one or more IoT sensor devices 104.
  • IOT Internet of Things
  • FIG. 2 is a block diagram that illustrates a Mobile Edge Computing (MEC) framework 200 that is configured to enable communication within the MEC environment 100, in accordance with some embodiments of the present disclosure.
  • MEC environment 100 enables the implementation of mobile edge applications as software-only entities that run on top of a virtualization infrastructure, which is located in or close to the network edge based on the MEC framework 200.
  • the MEC framework 200 is broadly divided into three levels viz. communication network level 202, a MEC server level 204, and a mobile edge system level 206.
  • the communication network level 202 comprises different types of networks such as, the mobile RAN 110, local networks 208, and an external networks 210.
  • the MEC server level 204 comprises a virtualization infrastructure (e.g.
  • the Network Functions Virtualization Infrastructure 212, a mobile edge platform 214, one or more mobile edge applications 216, and MEC server level management 218.
  • the virtualization infrastructure 212, the mobile edge platform 214, and the one or more mobile edge applications 216 may be implemented in the MEC server 106.
  • the one or more mobile edge applications 216 may be implemented in the MEC server 106 may be implemented through virtual machines managed by the virtualization infrastructure 212.
  • the mobile edge system level 206 comprises mobile edge system level management 220, one or more IoT sensor nodes 102, IoT sensor devices 104, and one or more MEC devices 122.
  • the MEC server 106 is an entity that contains the mobile edge platform 214 and the virtualization infrastructure 212 which provides compute, storage, and network resources for the one or more mobile edge applications 216.
  • the virtualization infrastructure 212 includes a data plane that executes the traffic rules received by the mobile edge platform 214, and routes the traffic among applications, services, DNS server/proxy, mobile RAN 110, local networks 208 and external networks 210. Further, a virtualization infrastructure manager 212a may be configured to implement all the functions of the virtualization infrastructure 212.
  • the virtualization infrastructure manager 212a may be configured for allocating, managing and releasing virtualized (compute, storage and networking) resources of the virtualization infrastructure 212.
  • the virtualization infrastructure manager 212a may prepare the virtualization infrastructure 212 to run a software image. The preparation includes configuring the virtualization infrastructure212, and can include receiving and storing the software image.
  • virtualization infrastructure manager 212a may perform rapid provisioning of applications.
  • the virtualization infrastructure manager 212a may be configured for collecting and reporting performance and fault information about the virtualized resources.
  • virtualization infrastructure manager 212a may performing application relocation. For application relocation from/to external cloud environments, the virtualization infrastructure manager 212a interacts with the external cloud manager to perform the application relocation.
  • the mobile edge platform 214 may be configured to provide an environment where the mobile edge applications may discover, advertise, consume and offer mobile edge services.
  • the mobile edge platform 214 may be further configured to receive traffic rules from the mobile edge platform manager 218a, applications, or services, and instructing the data plane accordingly.
  • mobile edge platform 214 may be configured for translation of tokens representing the one or more MEC devices 122 associated with the one or more edge users in the traffic rules into specific IP addresses.
  • the mobile edge platform 214 may receive DNS records from the mobile edge platform manager 218a and may configure a DNS proxy/server based on the received DNS records. Further, the mobile edge platform 214 may be configured to host one or more mobile edge services.
  • the one or more mobile edge applications 216 may be running as virtual machines (VM) on top of the virtualization infrastructure 212 provided by the MEC server 106, and can interact with the mobile edge platform 214 to consume and provide one or more mobile edge services.
  • mobile edge applications can also interact with the mobile edge platform 214 to perform support procedures related to the lifecycle of the application, such as indicating availability, preparing relocation of user state, and the like.
  • the one or more mobile edge applications 216 may have a certain number of rules and requirements associated to them, such as required resources, maximum latency, required or useful services, and the like. Such requirements may be validated by the mobile edge system level management 220, and can be assigned to default values if missing.
  • the MEC server level management 218 comprises the mobile edge platform manager 218a.
  • the mobile edge platform manager 218a may be configured to manage the life cycle of applications including informing the mobile edge orchestrator of relevant application related events.
  • the mobile edge platform manager 218a may be configured to provide element management functions to the mobile edge platform 214. Further, the application rules and requirements including service authorizations, traffic rules, DNS configuration and resolving conflicts may be configured by the mobile edge platform manager 218a.
  • the mobile edge platform manager 218a also receives virtualized resources fault reports and performance measurements from the virtualization infrastructure manager for further processing.
  • the mobile edge system level management 220 comprises the mobile edge orchestrator 220a, Operations Support System (OSS) 220b and application lifecycle management proxy 220c.
  • the mobile edge orchestrator 220a is the core functionality in mobile edge system level management 220.
  • the mobile edge orchestrator 220a may be configured for maintaining an overall view of the mobile edge system based on deployed MEC servers 106, available resources, available mobile edge services, and topology.
  • the mobile edge orchestrator 220a may be configured for validating application rules and requirements and if necessary adjusting them to comply with operator policies, keeping a record of on-boarded packages, and preparing the virtualization infrastructure manager 212a to handle the applications.
  • the mobile edge orchestrator 220a may be configured for selecting appropriate MEC servers for application instantiation based on constraints, such as latency, available resources, and available services.
  • the mobile edge orchestrator 220a may be configured for triggering mobile edge application instantiation and termination.
  • the Operations Support System (OSS) 212b may receive requests from the MEC devices 122 for instantiation or termination of mobile edge applications. Operations Support System (OSS) 212b may decide on the granting of these requests. Granted requests are forwarded to the mobile edge orchestrator 220a for further processing. When supported, the OSS also receives requests from MEC devices 122 for relocating mobile edge applications between external clouds and the MEC server 106.
  • OSS Operations Support System
  • the mobile user application is a mobile edge application that is instantiated in the mobile edge system in response to a request of an edge user via an application running in the MEC device 122.
  • the application lifecycle management proxy 220c allows MEC device 122 to request on-boarding, instantiation, termination of applications and when supported, relocation of applications in and out of the mobile edge system.
  • the application lifecycle management proxy 220c authorizes requests from MEC device 122 and interacts with the OSS 212b and the mobile edge orchestrator 220a for further processing of these requests.
  • the application lifecycle management proxy 220c is only accessible from within the mobile RAN 110.
  • FIG. 3 is a block diagram of the Mobile Edge Computing (MEC) server 106 that contains the mobile edge platform 214 and the virtualization infrastructure 212 which provides compute, storage, and network resources for one or more mobile edge applications 216, in accordance with some embodiments of the present disclosure.
  • the one or more mobile edge applications 216 may be associated with one or more one or more edge services.
  • the MEC server 106 further comprises a processor 302, a memory 304, an analysis unit 306, an operating mode identification unit 308, an edge service creation unit 310, a transceiver 312, an input/output unit 314, the channel association engine 316, and the monitoring unit 318.
  • MEC Mobile Edge Computing
  • the processor 302 may be communicatively connected to the memory 304, the analysis unit 306, the operating mode identification unit 308, the edge service creation unit 310, the transceiver 312, the input/output unit 314, the channel association engine 316, and the monitoring unit 318.
  • the processor 302 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to execute a set of instructions stored in the memory 304.
  • the processor 302 may be implemented based on a number of processor technologies known in the art. Examples of the processor 302 include, but not limited to, an X86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processor.
  • RISC Reduced Instruction Set Computing
  • ASIC Application-Specific Integrated Circuit
  • CISC Complex Instruction Set Computing
  • the memory 304 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to store the set of instructions, which are executed by the processor 302.
  • the memory 304 may be configured to store one or more programs, routines, or scripts that may be executed in coordination with the processor 302.
  • the memory 304 may retain one or more predefined decision rules whether to accept or reject subscribe or unsubscribe request sent by one or more MEC devices 122.
  • the memory 304 may be configured to store the monitoring information for the edge services and corresponding metadata associated with edge services.
  • the memory 304 may be implemented based on a Random Access Memory (RAM), a Read-Only Memory (ROM), a Hard Disk Drive (HDD), a storage server, and/or a Secure Digital (SD) card.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • HDD Hard Disk Drive
  • SD Secure Digital
  • the analysis unit 306 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to define one or more applications for which an IoT sensor node and IoT sensor device may be used, and one or more dimensions associated with each of the one or more applications.
  • the analysis unit 306 may be configured to extend the metadata to include one or more updates necessary to identify the one or more edge services and the one or more operating modes.
  • the analysis unit 306 may be further configured to update the metadata based on an association between each of the one or more operating modes and the one or more communication channels.
  • the analysis unit 306 may be further configured to monitor a change in the one or more applications and one or more dimensions.
  • the analysis unit 306 may be further configured to update the one or more operating modes associated with the one or more IoT sensor nodes based on the monitoring.
  • the operating mode identification unit 308 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to identify one or more operating modes associated with the one or more IoT sensor nodes based on the one or more dimensions. In an embodiment, each of the one or more operating modes are associated with one or more communication channels.
  • the edge service creation unit 310 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to create one or more edge services associated with the one or more communication channels for the one or more MEC devices based on the received information
  • the transceiver 312 comprises of suitable logic, circuitry, interfaces, and/or code that may be configured to receive information captured by the one or more IoT sensor nodes associated with the one or more IoT sensor devices based on the identified one or more operating modes.
  • the transceiver 312 may be further configured to receive a subscription request for one or more edge services associated with the one or more communication channels from the one or more MEC devices associated with the one or more edge users.
  • the transceiver 312 may be further configured to transmit the information captured by the one or more IoT sensor nodes to the one or more MEC devices associated with the one or more edge users via the one or more communication channels based on the subscription request and the metadata in the one or more edge services.
  • the transceiver 312 may communicate information between the one or more IoT sensor nodes and the one or more MEC devices associated with one or more edge users, via the mobile RAN 110.
  • the transceiver 312 may implement one or more known technologies to support wired or wireless communication with the mobile RAN 110.
  • the transceiver 312 may include, but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a Universal Serial Bus (USB) device, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and/or a local buffer.
  • RF radio frequency
  • the transceiver 312 may communicate via wireless communication with networks, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN).
  • the wireless communication may use any of a plurality of communication standards, protocols and technologies, such as: Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS).
  • GSM Global System for Mobile Communications
  • EDGE Enhanced Data GSM Environment
  • W-CDMA wideband code division multiple access
  • CDMA code division multiple access
  • the Input/ Output (I/O) unit 314 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to receive an input corresponding to the one or more applications and one or more dimensions associated with each of the one or more applications.
  • the input/output unit 314 comprises of various input and output devices that are configured to communicate with the processor 302. Examples of the input devices include, but are not limited to, a keyboard, a mouse, a joystick, a touch screen, a microphone, and/or a docking station. Examples of the output devices include, but are not limited to, a display screen and/or a speaker.
  • the channel association engine 316 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to associate and dissociate the one or more communication channels to the identified one or more operating modes.
  • the monitoring unit 318 comprises suitable logic, circuitry, interfaces, and/or code that may be configured to monitor the created one or more edge services and the associated one or more communication channels.
  • the analysis unit 306 may be configured to define the one or more applications and the one or more dimensions associated with each of the one or more applications.
  • Examples of the one or more applications may comprise at least one of smart grid, smart cars, smart healthcare and smart homes.
  • the one or more dimensions correspond to a set of values associated with the application. Every application may have its own dimensions to utilize information generated by the one or more IoT sensor nodes 102.
  • the analysis unit 306 may be configured to discover and place the one or more dimensions associated with the smart grid (application).
  • the one or more dimensions correspond to the set of values obtained from the one or more IoT sensor nodes 102.
  • one or more dependencies associated with the one or more dimensions may be identified with respective application (e.g. smart grid) and the other dimensions pertaining to the other applications. Further, evolving and interdependent dimensions are required to be managed and maintained in their correctness to effectively identify and utilize the one or more operating modes, as the one or more operating modes are highly dependent on the one or more dimensions.
  • application e.g. smart grid
  • evolving and interdependent dimensions are required to be managed and maintained in their correctness to effectively identify and utilize the one or more operating modes, as the one or more operating modes are highly dependent on the one or more dimensions.
  • dimensions for smart grid application are illustrated below:
  • the operating mode identification unit 308 may be configured to identify the one or more operating modes associated with the one or more IoT sensor nodes 102 based on the defined one or more dimensions.
  • the identified operating modes for the smart grid comprise Utilization, Status, Validation, Transaction, and Remote.
  • each of the one or more operating modes are associated with one or more communication channels.
  • the one or more operating modes specify the information that may be to be transmitted across the one or more communication channels.
  • the one or more operating modes decide what information needs to be sent across to the one or more communication channels.
  • the identified operating modes for the smart healthcare comprise condition, and quality.
  • the condition operating mode provides the gas condition for the specific product whereas, quality operating mode provides present qualitative parameters of the product.
  • the one or more operating modes are either a data entity or a set of data entities that represent factors impacting to rationalize the information communicated within the MEC environment 100.
  • the one or more operating modes may vary across multiple dimensions. Further, the one or more operating modes may be associated to that one or more dimensions that are identified and placed. For example, utilization is associated with the ERT metering and monitoring in the example of smart grid. Diversified applications can have similar or similar set of operating modes. In an embodiment, the one or more operating modes represent the dependencies among the one or more dimensions. In an embodiment, the correlations between the one or more operating modes and the one or more dimensions may be stored in the memory 304. The operating mode identification unit 308 may be configured to manage the operating mode configuration to correlate the one or more communication channels, IoT sensor nodes, and cross reference data to generate operating mode correspondence for channeling. In an embodiment, the change in the one or more dimensions may be based on the operating mode configuration and the correlation between one or more communication channels and the one or more operating modes.
  • the channel association engine 316 may be configured to associate and dissociate the one or more communication channels to the identified one or more operating modes.
  • a set of predefined channels may be utilized for specific operating modes.
  • at least one communication channel may be associated with each of the one or more operating modes for transmitting the information to the MEC devices 122.
  • the change in the operating modes configuration may be performed based on IoT sensor nodes 102, correlation between one or more communication channels and the one or more operating modes, and cross reference data from various other participants of the MEC environment 100 including external resources such as environmental conditions impacting quality of transmission, vicinity information retrieved for the county, and the like.
  • the transceiver 312 may be configured to communicate the identified one or more operating modes to the one or more IoT sensor nodes 102. Based on the communicated one or more operating modes associated with each of the one or more IoT sensor nodes 102, each of the one or more IoT sensor nodes 102 may transmit the information captured by the one or more IoT sensor nodes in accordance with the communicated one or more operating modes. Thus, the one or more IoT sensor nodes 102 transmit the information captured by the one or more IoT sensor nodes 102 based on the one or more operating modes.
  • the transceiver 312 may be configured to receive the information captured by the one or more IoT sensor nodes 102 associated with the one or more IoT sensor devices 104 based on the identified one or more operating modes, via the associated one or more communication channels.
  • the information comprises type of each of the one or more IoT sensor nodes, device specification of each of the one or more MEC devices, data captured by each of the one or more IoT sensor nodes, and type of data captured by each of the one or more IoT sensor nodes.
  • the edge service creation unit 310 may be configured to create one or more edge services associated with the one or more communication channels for the one or more MEC devices based on the received information.
  • one or more retention policies may be defined and configured by the edge service creating unit 310 for each of the edge service during creation.
  • the one or more edge services may comprise metadata of the one or more operating modes and the associated one or more communication channels.
  • the metadata may comprise service identification number, a message sequence number, number of IoT sensor nodes, a channel number associated with each of the one or more communication channels, a serial number of the one or more IoT sensor nodes, and a timestamp.
  • one or more edge services may be created and formulated for the mobile edge applications 216.
  • Such one or more edge services may be utilized by the one or more edge users of the specific application.
  • the developers of the mobile edge applications 216 may utilize edge service creation unit 310 to develop and deploy services for the one or more communication channels.
  • the one or more edge services may be a logical composition for sending and receiving the information via the communication channels.
  • Each edge service name assigned to the edge service is unique and the edge service name may be associated with plurality of communication channels with the condition that same or subset of one or more operating modes are also associated with the one or more communication channels.
  • the edge service creation unit 310 may be further configured to manage the configuration of the MEC devices 122 associated with the edge users at the edge of mobile RAN 110. Further, the correlation between the edge users and their associated one or more edge services may be maintained by the edge service creation unit 310. Further, the edge service creation unit 310 may maintain the metadata associated with the communication channels in adherence to information captured by the IoT sensors nodes 102. In an embodiment, the memory 304 may be utilized to manage the correlation between MEC devices 122, edge services, the one or more communication channels, and the one or more operating modes.
  • the transceiver 312 may be configured to receive a subscription request for one or more edge services associated with the one or more communication channels from the one or more MEC devices 122 associated with the one or more edge users. In an embodiment, the transceiver 312 may be configured to receive an unsubscribe request for the one or more edge services to which the edge user may have already subscribed. In response to the received subscription/unsubscribe request, the processor 302 may validate subscription or unsubscribe request and sends acknowledgement in correspondence to the request by one or more MEC devices 122 indicating whether the subscription/unsubscribe request is accepted or rejected. The validation of the subscription or unsubscribe request may be performed based on the one or more predefined decision rules stored in the memory 304.
  • the transceiver 312 may be configured to transmit the information captured by the one or more IoT sensor nodes 102 to the one or more MEC devices 122 associated with the one or more edge users via the one or more communication channels based on the subscription request and the metadata in the one or more edge services. For example, for "Status" operating mode, transceiver 312 only sends status of the IoT sensor nodes 102.
  • the information associated with the subscription request for the one or more edge services associated with the one or more communication channels is transmitted via the one or more communication channels associated with the one or more edge services.
  • Another critical action during transmission of the information may be to acquire qualitative measures including, however, not limited to security, connectivity, and signal-to-noise ratio.
  • the one or more MEC devices may be configured to detect faults, and security issues associated with the received information.
  • the edge users may receive the desired information captured by the IoT sensors nodes 102 based on the identified operating modes.
  • the edge users receive the IoT information.
  • the transceiver 312 may be configured to transmit information to the MEC devices 122 based on the one or more operating modes associated with the one or more communication channel via the edge services. For example, for the smart healthcare application, the transceiver 312 transmits the gas condition to specific communication channel associated with condition operating mode.
  • the one or more MEC devices 122 may receive the information via the edge services and associated communication channel.
  • the mapping can be updated or changed based on the type and requirements of the edge users.
  • the one or more edge services may retain the metadata binding based on the one or more operating modes and the communication channel associated with that operating mode. Services can be created as more operating modes and associated communication channels are identified, however, the metadata remains consistent across services.
  • Example of the metadata is the timestamp, sequence number, number of participant IoT sensor nodes, and IoT sensor device serial number.
  • Such metadata that may remain consistent throughout one or more edge services may be utilized to transmit the relevant information to the edge users based on the identified operating mode.
  • a mobile edge application 216 may identify and associate the metadata to the services.
  • the metadata may comprise IoT sensor node operating mode, mapping of IoT sensor node operating mode, source, communication channel, notification (from IoT), timestamp.
  • the analysis unit 306 may be configured to extend the metadata to include one or more updates necessary to identify the one or more edge services and the one or more operating modes.
  • the metadata may be updated based on an association between each of the one or more operating modes and the one or more communication channels.
  • the association between the one or more operating modes and the one or more edge services associated with the one or more communication channels is determined based on the metadata.
  • the analysis unit 306 may be configured to continuously monitor a change in the one or more applications and the one or more dimensions.
  • the one or more operating modes associated with the one or more IoT sensor nodes may be updated based on the monitoring.
  • the analysis engine 306 may be configured to recognize additional applications or additional dimensions to existing applications has been introduced to the MEC environment 100. The additional applications may be introduced using the APIs 112 and the additional dimensions may be introduced with the facilitation of functionalities or services associated with the APIs 112.
  • the smart healthcare application may have one or more API's configured to regulate gas flow and manage gas condition with specifically controlling pressure sensors, temperature sensors, and humidity sensors in anesthesia machines, respirators and ventilators.
  • the dimensions and their values may be analyzed such as product (anesthesia machines, respirators, and ventilators), process (gas flow), patient information (name, address, age, and, condition) and control (monitor, higher, and lower).
  • different applications may utilize the same dimensions, however, different values may be associated with the dimensions.
  • the one or more applications and one or more dimensions associated with each of the one or more applications may be updated based on user inputs.
  • the updated applications and the dimensions may be communicated to the MEC devices 122 via the mobile RAN 110.
  • the transceiver 312 may be configured to broadcast a change/update or new association between the edge services, one or more communication channels, and one or more operating modes, to the MEC devices 122 based on the configuration of the MEC environment 100 and MEC devices 122 for receiving the broadcast messages.
  • the monitoring unit 318 may be configured to monitor the created one or more edge services and the associated one or more communication channels.
  • the monitoring unit 318 may be configured to store runtime utilization of the one or more edge services and associated metadata in the memory 304.
  • the monitoring unit 318 may be enabled or disabled for a specific edge service.
  • the processor 302 may be configured to generate one or more graphical visualizations that may depict the runtime utilization information of the one or more edge services.
  • FIG. 4 is a flowchart illustrating a method for communication between one or more IoT sensor nodes 102 associated with one or more IoT sensor devices 104, the MEC server 106, and one or more Mobile Edge Computing (MEC) devices 122, in accordance with some embodiments of the present disclosure.
  • MEC Mobile Edge Computing
  • the MEC server 106 may define one or more applications and one or more dimensions associated with each of the one or more applications.
  • the MEC server 106 may identify one or more operating modes associated with the one or more IoT sensor nodes 102 based on the one or more dimensions. In an embodiment, each of the one or more operating modes may be associated with one or more communication channels.
  • the MEC server 106 may receive information captured by the one or more IoT sensor nodes associated with the one or more IoT sensor devices based on the identified one or more operating modes, via the associated one or more communication channels.
  • the MEC server 106 may create one or more edge services associated with the one or more communication channels for the one or more MEC devices 122 based on the received information.
  • the one or more edge services may comprise metadata of the one or more operating modes and the associated one or more communication channels.
  • the MEC server 106 may receive a subscription request for one or more edge services associated with the one or more communication channels from the one or more MEC devices 122 associated with the one or more edge users.
  • the MEC server 106 may transmit the information captured by the one or more IoT sensor nodes 102 to the one or more MEC devices 122 associated with the one or more edge users via the one or more communication channels based on the subscription request and the metadata in the one or more edge services. Control passes to end step 416.
  • FIG. 5 illustrates a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.
  • Variations of computer system 501 may be used for communication between one or more IoT sensor nodes 102 associated with one or more IoT sensor devices 104, the MEC server 106, and one or more Mobile Edge Computing (MEC) devices 122.
  • the computer system 501 may correspond to MEC server 106.
  • the computer system 501 may comprise a central processing unit (“CPU” or "processor") 502.
  • Processor 502 may comprise at least one data processor for executing program components for executing user- or system-generated requests.
  • a user may include a person, a person using a device such as such as those included in this disclosure, or such a device itself.
  • the processor 502 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.
  • the processor 502 may include a microprocessor, such as AMD Athlon, Duron or Opteron, ARM's application, embedded or secure processors, IBM PowerPC, Intel's Core, Itanium, Xeon, Celeron or other line of processors, etc.
  • the processor 502 may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), Field Programmable Gate Arrays (FPGAs), etc.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • FPGAs Field Programmable Gate Arrays
  • I/O Processor 502 may be disposed in communication with one or more input/output (I/O) devices via I/O interface 503.
  • the I/O interface 503 may employ communication protocols/methods such as, without limitation, audio, analog, digital, monaural, RCA, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc.
  • CDMA code-division multiple access
  • HSPA+ high-speed packet access
  • GSM global system for mobile communications
  • LTE long-term evolution
  • WiMax wireless wide area network
  • the computer system 501 may communicate with one or more I/O devices.
  • the input device 504 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope, proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, visors, etc.
  • Output device 505 may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, or the like), audio speaker, etc.
  • video display e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, or the like
  • audio speaker etc.
  • a transceiver 506 may be disposed in connection with the processor 502. The transceiver 506 may facilitate various types of wireless transmission or reception.
  • the transceiver 506 may include an antenna operatively connected to a transceiver chip (e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like), providing IEEE 802.11a/b/g/n, Bluetooth, FM, global positioning system (GPS), 2G/3G HSDPA/HSUPA communications, etc.
  • a transceiver chip e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like
  • IEEE 802.11a/b/g/n e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like
  • IEEE 802.11a/b/g/n e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB
  • the processor 502 may be disposed in communication with a communication network 508 via a network interface 507.
  • the network interface 507 may communicate with the communication network 508.
  • the network interface 507 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc.
  • the communication network 508 may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc.
  • the computer system 501 may communicate with devices 510, 511, and 512.
  • These devices may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Blackberry, Android-based phones, etc.), tablet computers, eBook readers (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gaming consoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or the like.
  • the computer system 501 may itself embody one or more of these devices.
  • the processor 502 may be disposed in communication with one or more memory devices (e.g., RAM 513, ROM 514, etc.) via a storage interface 512.
  • the storage interface may connect to memory devices including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-1394, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc.
  • the memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, solid-state drives, etc.
  • the memory devices may store a collection of program or database components, including, without limitation, an operating system 516, user interface application 517, web browser 518, mail server 519, mail client 520, user/application data 521 (e.g., any data variables or data records discussed in this disclosure), etc.
  • the operating system 516 may facilitate resource management and operation of the computer system 501.
  • Operating systems include, without limitation, Apple Macintosh OS X, Unix, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linux distributions (e.g., Red Hat, Ubuntu, Kubuntu, etc.), IBM OS/2, Microsoft Windows (XP, Vista/7/8, etc.), Apple iOS, Google Android, Blackberry OS, or the like.
  • User interface 517 may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities.
  • user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 501, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc.
  • GUIs Graphical user interfaces
  • GUIs may be employed, including, without limitation, Apple Macintosh operating systems' Aqua, IBM OS/2, Microsoft Windows (e.g., Aero, Metro, etc.), Unix X-Windows, web interface libraries (e.g., ActiveX, Java, Javascript, AJAX, HTML, Adobe Flash, etc.), or the like.
  • the computer system 501 may implement a web browser 518 stored program component.
  • the web browser may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, etc. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), etc. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, application programming interfaces (APIs), etc.
  • the computer system 501 may implement a mail server 519 stored program component.
  • the mail server 519 may be an Internet mail server such as Microsoft Exchange, or the like.
  • the mail server 519 may utilize facilities such as ASP, ActiveX, ANSI C++/C#, Microsoft .NET, CGI scripts, Java, JavaScript, PERL, PHP, Python, WebObjects, etc.
  • the mail server 519 may utilize communication protocols such as internet message access protocol (IMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), or the like.
  • IMAP internet message access protocol
  • MAPI messaging application programming interface
  • PMP post office protocol
  • SMTP simple mail transfer protocol
  • the computer system 501 may implement a mail client 520 stored program component.
  • the mail client may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Mozilla Thunderbird, etc.
  • computer system 501 may store user/application data 521, such as the data, variables, records, etc. as described in this disclosure.
  • databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase.
  • databases may be implemented using standardized data structures, such as an array, hash, linked list, struct, structured text file (e.g., XML), table, or as object-oriented databases (e.g., using ObjectStore, Poet, Zope, etc.).
  • object-oriented databases e.g., using ObjectStore, Poet, Zope, etc.
  • Such databases may be consolidated or distributed, sometimes among the various computer systems discussed above in this disclosure. It is to be understood that the structure and operation of the any computer or database component may be combined, consolidated, or distributed in any working combination.
  • FIG. 6 illustrates an interaction diagram 600 between the various entities involved in the communication in the MEC environment 100, in accordance with some embodiments of the present disclosure.
  • the various entities involved in the communication in the MEC environment 100 are an MEC developer 602, MEC devices 122, MEC server 106, IoT sensor nodes 102, and IoT sensor devices 104.
  • Step 604 illustrates that the MEC developer may have access to the MEC devices one or more edge applications 216.
  • Step 606 illustrates that the MEC devices 122 may send a request to the MEC server 106 to publish one or more edge applications 216.
  • Step 608 illustrates that the MEC server 106 may define one or more applications and one or more dimensions associated with each of the one or more applications.
  • Step 610 illustrates that the MEC server 106 may identify one or more operating modes associated with the one or more IoT sensor nodes 102 based on the one or more dimensions.
  • Step 612 illustrates that the MEC server 106 may communicate the identified operating mode to the one or more IoT sensor nodes 102.
  • Step 614 illustrates that the MEC server 106 may associate one or more communication channels to each of the one or more operating modes.
  • Step 616 illustrates that the MEC developer 602 may deploy one or more edge services at the MEC server 106.
  • Step 618 illustrates that the MEC server 106 may associate one or more communication channels to each of the one or more edge services.
  • Step 620 illustrates that the IoT sensor nodes 102 may transmit the captured sensor information to the IoT devices 104.
  • Step 622 illustrates that IoT devices 104 may be configured to manage sensor information based on the one or more operating modes.
  • Step 624 illustrates that one or more MEC devices 122 may send a request to the MEC server 106 for subscribing to an edge service.
  • Step 626 illustrates that in response to the received subscription request, the MEC server may validate the subscription request based on the one or more predefined decision rules stored in the memory 304.
  • Step 628 illustrates that based on the validation performed by the MEC server 106, the MEC server may either accept or deny the subscription request and communicate the same accordingly to the MEC devices 122.
  • Step 630 illustrates that the MEC server may receive the sensor information captured by the IoT sensor nodes 102 from the IoT sensor devices 104 in accordance with the identified one or more operating modes.
  • Step 632 illustrates that the MEC server 106 may transmit the sensor information to the MEC devices 122 in accordance with the identified one or more operating modes.
  • one or more communication channels 634 may be associated with the MEC devices 122, the MEC server 106, IoT sensor devices 104, and IoT sensor nodes 102. Each of the one or more communication channels 634 may be associated with one or more operating modes.
  • Step 636 illustrates that the updates/changes in the edge services may be broadcasted by the MEC server 106.
  • Step 638 illustrates that the MEC server 106 may be configured to monitor each of the one or more edge services to determine the utilization of each edge service.
  • Step 640 illustrates that one or more MEC devices 122 may send a request to the MEC server 106 for unsubscribing to an edge service.
  • Step 642 illustrates that in response to the unsubscribe request, the MEC server 106 may be configured to update the correlation between the edge service and the MEC devices 122.
  • Step 644 illustrates that after updating the correlation, the MEC server 106 may transmit an unsubscribe confirmation to the MEC devices 122.
  • a computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored.
  • a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein.
  • the term "computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, nonvolatile memory, hard drives, Compact Disc (CD) ROMs, Digital Video Disc (DVDs), flash drives, disks, and any other known physical storage media.
  • the disclosed method described herein streamlines the communication between one or more IoT sensor nodes 102 associated with one or more IoT sensor devices 104, and one or more mobile edge computing (MEC) devices 122 associated with one or more edge users.
  • MEC mobile edge computing
  • an embodiment means “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the invention(s)” unless expressly specified otherwise.
  • the terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.
  • the terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.
  • the present disclosure may be realized in hardware, or a combination of hardware and software.
  • the present disclosure may be realized in a centralized fashion, in at least one computer system, or in a distributed fashion, where different elements may be spread across several interconnected computer systems.
  • a computer system or other apparatus adapted for carrying out the methods described herein may be suited.
  • a combination of hardware and software may be a general-purpose computer system with a computer program that, when loaded and executed, may control the computer system such that it carries out the methods described herein.
  • the present disclosure may be realized in hardware that comprises a portion of an integrated circuit that also performs other functions.
  • any of the aforementioned steps and/or system modules may be suitably replaced, reordered, or removed, and additional steps and/or system modules may be inserted, depending on the needs of a particular application.
  • the systems of the aforementioned embodiments may be implemented using a wide variety of suitable processes and system modules, and are not limited to any particular computer hardware, software, middleware, firmware, microcode, and the like.
  • the claims can encompass embodiments for hardware and software, or a combination thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
EP16196272.5A 2016-08-09 2016-10-28 Accorder des senseurs avec des applications sur un serveur à la limite du réseau Withdrawn EP3282718A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/232,578 US10104672B2 (en) 2016-08-09 2016-08-09 Method and a system for identifying operating modes of communications in mobile edge computing environment

Publications (1)

Publication Number Publication Date
EP3282718A1 true EP3282718A1 (fr) 2018-02-14

Family

ID=57389183

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16196272.5A Withdrawn EP3282718A1 (fr) 2016-08-09 2016-10-28 Accorder des senseurs avec des applications sur un serveur à la limite du réseau

Country Status (2)

Country Link
US (1) US10104672B2 (fr)
EP (1) EP3282718A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408234A (zh) * 2018-10-19 2019-03-01 国云科技股份有限公司 一种基于边缘计算的增强现实技术数据优化系统及方法
WO2020180072A1 (fr) * 2019-03-04 2020-09-10 삼성전자 주식회사 Appareil et procédé de commande de relocalisation d'application dans un environnement informatique périphérique
WO2021018529A1 (fr) * 2019-07-31 2021-02-04 Renault S.A.S Procédé de souscription à un géo-service dans une architecture mec
CN112835708A (zh) * 2020-12-14 2021-05-25 浙大城市学院 一种面向边缘计算环境中移动群体感知系统的高质量任务分配与服务部署方法
US12034812B2 (en) * 2020-10-01 2024-07-09 Ray Quinney & Nebeker Global internet of things (IoT) connectivity fabric

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017169061A1 (fr) * 2016-03-31 2017-10-05 日本電気株式会社 Nœud de réseau d'accès sans fil, nœud externe et procédé associe
US10470192B2 (en) * 2017-03-08 2019-11-05 Zte Corporation Traffic path change detection mechanism for mobile edge computing
US11204816B2 (en) 2017-05-09 2021-12-21 Microsoft Technology Licensing, Llc Deployment of modular applications from the cloud to local devices
US20180352038A1 (en) * 2017-05-30 2018-12-06 Intel Corporation Enhanced nfv switching
CN109818868B (zh) * 2017-11-20 2021-06-22 中兴通讯股份有限公司 一种实现边缘网络能力开放的方法、装置、设备及存储介质
US20210211914A1 (en) * 2018-01-12 2021-07-08 Idac Holdings, Inc. Methods and procedures for providing an ieee 802.11 based radio network information service for etsi mec
CN112236989A (zh) * 2018-06-07 2021-01-15 诺基亚技术有限公司 用于无线网络的移动边缘计算应用管理
CN116232667A (zh) * 2018-07-13 2023-06-06 三星电子株式会社 用于边缘计算服务的方法及其电子装置
US10666557B2 (en) * 2018-08-03 2020-05-26 Hitachi, Ltd. Method to manage data flow for edge-core distributed analytics systems
TWI674780B (zh) * 2018-11-23 2019-10-11 財團法人工業技術研究院 網路服務系統及網路服務方法
US10764072B2 (en) * 2019-01-23 2020-09-01 Verizon Patent And Licensing Inc. Systems and methods for configuring a private multi-access edge computing environment
US11172366B2 (en) 2019-06-20 2021-11-09 Bank Of America Corporation Edge-node authentication-data exchange system
CN110290140B (zh) * 2019-06-28 2021-09-24 腾讯科技（深圳）有限公司 多媒体数据处理方法及装置、存储介质、电子设备
CN110300024A (zh) * 2019-06-28 2019-10-01 中天宽带技术有限公司 一种服务器任务处理方法、装置及其相关设备
US11151575B2 (en) 2019-07-09 2021-10-19 Bank Of America Corporation Trusted pair authentication with edge-computing devices
CN110324433A (zh) * 2019-08-07 2019-10-11 南京理工大学 基于移动边缘计算的用户与基站的匹配博弈方法
TWI734249B (zh) * 2019-11-07 2021-07-21 財團法人資訊工業策進會 網路系統以及決策方法
US11770734B2 (en) * 2020-01-28 2023-09-26 Verizon Patent And Licensing Inc. Method and system for edge network exposure function with MEC network
CN113381871B (zh) * 2020-03-10 2023-04-07 中国电信股份有限公司 移动边缘业务编排方法、编排器和移动边缘计算系统
CN111654833B (zh) * 2020-06-02 2023-09-19 Tcl通讯（宁波）有限公司 传感器数据的处理方法和装置
CN111757547A (zh) * 2020-07-02 2020-10-09 赛特斯信息科技股份有限公司 一种多边缘云平台监控管理系统
US11700309B2 (en) 2020-08-13 2023-07-11 Alibaba Group Holding Limited Network parameter provisioning for instantiation of a network entity
CN114080058A (zh) * 2020-08-17 2022-02-22 华为技术有限公司 一种计算任务的处理方法、通信装置及无线网络架构
CN112492543B (zh) * 2020-10-30 2023-08-18 南京邮电大学 基于车联网mec和d2d链路的车辆安全传输系统及方法
US12095823B2 (en) 2021-12-10 2024-09-17 Bank Of America Corporation System and method for self-clustering edge computing protection

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150026044A1 (en) * 2013-07-07 2015-01-22 Gaonic Ltd. Method, protocol and system for universal sensor communication
US20160072892A1 (en) * 2013-12-10 2016-03-10 Shenyang Institute Of Automation Of The Chinese Academy Of Sciences A semantics-based architectural model of the internet of things

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10122547B2 (en) * 2015-08-14 2018-11-06 Nec Corporation Enabling high-bandwidth, responsive mobile applications in LTE networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150026044A1 (en) * 2013-07-07 2015-01-22 Gaonic Ltd. Method, protocol and system for universal sensor communication
US20160072892A1 (en) * 2013-12-10 2016-03-10 Shenyang Institute Of Automation Of The Chinese Academy Of Sciences A semantics-based architectural model of the internet of things

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHENG BIN ET AL: "Geelytics: Enabling On-Demand Edge Analytics over Scoped Data Sources", 2016 IEEE INTERNATIONAL CONGRESS ON BIG DATA (BIGDATA CONGRESS), IEEE, 27 June 2016 (2016-06-27), pages 101 - 108, XP032975957, DOI: 10.1109/BIGDATACONGRESS.2016.21 *
HUAWEI : MILAN ET AL: "Mobile-Edge Computing - Introductory Technical White Paper Issue 1 Mobile-Edge Computing Contributing Organizations and Authors Table of Contents", 1 September 2014 (2014-09-01), XP055303917, Retrieved from the Internet <URL:https://portal.etsi.org/Portals/0/TBpages/MEC/Docs/Mobile-edge_Computing_-_Introductory_Technical_White_Paper_V1 18-09-14.pdf> [retrieved on 20160920] *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408234A (zh) * 2018-10-19 2019-03-01 国云科技股份有限公司 一种基于边缘计算的增强现实技术数据优化系统及方法
WO2020180072A1 (fr) * 2019-03-04 2020-09-10 삼성전자 주식회사 Appareil et procédé de commande de relocalisation d'application dans un environnement informatique périphérique
KR20200106317A (ko) * 2019-03-04 2020-09-14 삼성전자주식회사 엣지 컴퓨팅 환경에서 어플리케이션 재배치를 제어하기 위한 장치 및 방법
US11729277B2 (en) 2019-03-04 2023-08-15 Samsung Electronics Co., Ltd. Apparatus and method for controlling application relocation in edge computing environment
KR102704802B1 (ko) 2019-03-04 2024-09-09 삼성전자주식회사 엣지 컴퓨팅 환경에서 어플리케이션 재배치를 제어하기 위한 장치 및 방법
WO2021018529A1 (fr) * 2019-07-31 2021-02-04 Renault S.A.S Procédé de souscription à un géo-service dans une architecture mec
FR3099680A1 (fr) * 2019-07-31 2021-02-05 Renault Sas Procédé de souscription à un géo-service dans une architecture MEC
CN114175688A (zh) * 2019-07-31 2022-03-11 日产自动车株式会社 用于在mec架构中订阅地理服务的方法
CN114175688B (zh) * 2019-07-31 2023-09-29 日产自动车株式会社 用于在mec架构中订阅地理服务的方法
US12034812B2 (en) * 2020-10-01 2024-07-09 Ray Quinney & Nebeker Global internet of things (IoT) connectivity fabric
CN112835708A (zh) * 2020-12-14 2021-05-25 浙大城市学院 一种面向边缘计算环境中移动群体感知系统的高质量任务分配与服务部署方法
CN112835708B (zh) * 2020-12-14 2023-11-10 浙大城市学院 一种面向边缘计算环境中移动群体感知系统的高质量任务分配与服务部署方法

Also Published As

Publication number Publication date
US10104672B2 (en) 2018-10-16
US20180049179A1 (en) 2018-02-15

Similar Documents

Publication Publication Date Title
US10104672B2 (en) Method and a system for identifying operating modes of communications in mobile edge computing environment
CN107872823B (zh) 识别移动边缘计算环境中通信操作模式的方法和系统
US11444835B2 (en) System and method of maintenance of network slice templates for slice orchestration
US20160239770A1 (en) Method and system for dynamically changing process flow of a business process
US10701593B2 (en) Method and systems for performing orchestration of services in a next generation mobile core network
US20200026787A1 (en) METHOD, SYSTEM, AND FRAMEWORK FOR IMPLEMENTING INTERNET OF THINGS (IoT) APPLICATIONS
US10057915B2 (en) Methods and systems for adaptive scheduling of packets in a wireless broadband network
US10140444B2 (en) Methods and systems for dynamically managing access to devices for resolution of an incident ticket
US20150186133A1 (en) Systems and methods for enterprise application portfolio management
EP3343863A1 (fr) Établir une connexion d&#39;accès sécurisé avec des dispositifs électroniques
US10152317B2 (en) Method and system for updating software packages in a storage system
US10514999B2 (en) Method and a system to determine an effectiveness index of a software test environment
US11616860B2 (en) Information display method, terminal, and server
CN105610538A (zh) 物理小区标识有效再利用的系统和方法
US10445205B2 (en) Method and device for performing testing across a plurality of smart devices
US11463525B1 (en) Method and system for managing internet of things (IoT) devices in heterogeneous communication networks
US10721289B2 (en) Apparatus and method for improving loading time in electronic device
US10417582B2 (en) Method and device for automating operational tasks in an enterprise network
US12032986B2 (en) Automated training environment selection
KR102653516B1 (ko) 데이터를 제공하는 방법 및 장치
US9215630B2 (en) Method and system for creating a global neighbor list
US9747595B1 (en) Readying customer data based on geo-location
CN118796258A (zh) 灰度发布方法、装置

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

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

17P Request for examination filed

Effective date: 20180814

RBV Designated contracting states (corrected)

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

17Q First examination report despatched

Effective date: 20181002

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

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20200619