[go: up one dir, main page]

EP3050328A1 - Gestion de transmissions multidiffusion - Google Patents

Gestion de transmissions multidiffusion

Info

Publication number
EP3050328A1
EP3050328A1 EP13894933.4A EP13894933A EP3050328A1 EP 3050328 A1 EP3050328 A1 EP 3050328A1 EP 13894933 A EP13894933 A EP 13894933A EP 3050328 A1 EP3050328 A1 EP 3050328A1
Authority
EP
European Patent Office
Prior art keywords
service
client device
network
announcement
multicast
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
EP13894933.4A
Other languages
German (de)
English (en)
Inventor
Jorge Arturo SAUMA
John W FLICK
Ashwin Bhalchandra Hegde
James P HICKEY
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.)
Hewlett Packard Enterprise Development LP
Original Assignee
Hewlett Packard Enterprise Development LP
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 Hewlett Packard Enterprise Development LP filed Critical Hewlett Packard Enterprise Development LP
Publication of EP3050328A1 publication Critical patent/EP3050328A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • Zero-configuration (zeroconf) networking protocols such as the multicast domain name system (mDNS) protocol allow network devices to advertise and discover services offered by the network devices, without using a centralized DNS server. Each network device may send a multicast packet announcing the services, thus allowing client devices to discover the services offered by the network devices,
  • mDNS multicast domain name system
  • FIG. 1 is a block diagram of a network access point for managing multicast transmissions, according to one example
  • FIG, 2 is a block diagram of a network access point for managing multicast transmissions over a network, according to one example
  • FIG. 3 is a flowchart of a method for managing multicast transmissions, according to one example
  • FIG, 4 is a flowchart of a method for managing multicast transmissions, according to another example.
  • FIG. 5 is a block diagram of a multicast transmission manager including a computer- readable medium having instructions for managing multicast transmissions, according to one example,
  • Zeroconf is a set of network technologies used together to allow for automated network configuration of devices and services, without the use of central services such as DNS and dynamic host configuration protocol (DHCP). Thus, zeroconf does not require manual operator intervention (e.g., network administrator) or special configuration servers. Zeroconf covers addressing (i.e., IP address configuration), name resolution (e.g., translation between host name and IP address), and service discovery (e.g., printing).
  • addressing i.e., IP address configuration
  • name resolution e.g., translation between host name and IP address
  • service discovery e.g., printing
  • multicast requests i.e., multicast query
  • Devices which can fulfill such requests then send a multicast reply (e.g., service announcement).
  • This method of multicast transmission may cause network congestion and increased traffic, especially in special environment like wireless networks. For example, since the multicast traffic must reach all devices connected to the wireless network, the wireless rate of transmission may need to be adjusted to the devices with the slowest data rate, thereby slowing down the whole network.
  • Examples disclosed herein provide a solution for managing such multicast transmissions (e.g., queries or services requests). For example, when a network manager (e.g., a network access point) receives a service announcement, the network manager keeps records of the services. Then, when a multicast query is received and based on the records, the query is forwarded to the right client devices via unicast transmission.
  • a network manager e.g., a network access point
  • the network manager keeps records of the services.
  • the query is forwarded to the right client devices via unicast transmission.
  • a wireless tablet computing device wants to print a document
  • the tablet device sends a query for printers to an access point to which the tablet is associated/connected.
  • the access point may create a query table that includes a record associating the tablet device with a type of service (e.g., print service).
  • a layer-2 multicast wireless packet can be converted to a layer-2 unicast wireless traffic, making the transmission more efficient. Because the response is not multicast to other devices that may not need the print service, the efficiency of the network is improved and the network traffic is significantly reduced.
  • a method for managing multicast transmissions includes receiving, at a network access point, a multicast query from a client device, where the multicast query includes a service request.
  • the method includes creating and storing a record associating the service with the client device.
  • the method also includes receiving a service announcement from a network device hosting the service requested by the client device, and forwarding the service announcement to the client device via unicast transmission.
  • a network access point for managing multicast transmission includes a processor to receive a multicast transmission from a client device, where the multicast transmission includes a service request.
  • the processor is to determine a type of service requested by the client device, create and store a record associating the type of service to the client, and forward the service request to a network device via unicast transmission.
  • the processor is further to receive a service announcement from the network device, where the service announcement includes the type of service requested by the client device, and forward the service announcement to the client device via unicast transmission.
  • a non-transitory computer-readable medium includes instructions that, when executed by a processor of a multicast transmission manager, cause the processor to receive a multicast transmission from a client device, where the multicast transmission includes a service request.
  • the instructions are executable by the processor to analyze the service request to determine a type of service requested by the client device, create and store a record that associates the type of service to the client device, and forward the service request via unicast transmission to a network device known to host the type of service.
  • the instructions are further executable by the processor to receive a response to the service request from tire network device, and to forward the response to the client device via unicast transmission.
  • FIG. 1 is a block diagram of a network access point for managing multicast transmissions, according to one example.
  • Access point 102 is any network device or computing device that serves and/or provides a plurality of client devices such as client device 104 with access to a network (e.g., wireless local area network
  • access point 102 may be a WLA access point, a router, an ad-hoc device, a station, a router, a network controller, or any other network node.
  • client device 104 may connect to the network by associating with the access point 102, to transmit and receive data and/or network services.
  • Client device 104 may be, for example, a cellular device, a notebook computing device, a tablet computing device, a personal digital assistance (PDA), a desktop PC, a smartphone, or any other computing device that may rely on the access point 102 for network access.
  • Client device 104 may request services from network devices such as network device 106.
  • network device 106 For example in a zeroconf protocol such as a multicast DNS (mDNS) protocol, client device 104 may request one or more services by sending out a multicast request (or multicast query).
  • Network device 106 may be, for example, a printing device, a scanning device, facsimile device, or any other network device to provide network services to client devices and/or to respond to network requests received from client devices.
  • network device 106 may be a printer, scanner, a multifunction printer (MFP), an all-in-one (AiO) de vice, a ser v er, or any other device capable of processing requests from client devices.
  • MFP multifunction printer
  • Access point 102 may include a processor 1 12. and storage 122.
  • Processor 112. can be one or more central processing units (CPUs), microprocessors, and/or other hardware devices suitable for managing multicast transmissions.
  • Storage 122 represents generally any device or combination of devices configured to store data for use by access point 102. Such data may include a list of client devices such as client device 104, and services requested by the client devices.
  • Client device 104 may send a multicast query that includes a service request (e.g., printing service).
  • a service request e.g., printing service
  • processor 1 12 can analyze the query to determine the type of service requested by the client device 104.
  • Processor 1 12 creates a record that associates the client device 1 4 with the type of service. The record is stored in the storage device 122.
  • Processor 1 12 forwards the service request to the network device 106 via unicast transmission,
  • the multicast query including the service request is a layer-2 multicast packet.
  • multicast transmission data packets are delivered to a group of devices in a network simultaneously in a single transmission from a source.
  • unicast transmission data packets are delivered to a single network destination. Accordingly, in the described examples, the layer-2 packet query packet received from the client device 104 is converted to a layer-2 unicast packet.
  • the network device 106 is known by the access point 102 to offer the service requested by the client device 104.
  • the service request may be directed to an appropriate and targeted network device 106 instead of sending the service request to all network devices 106.
  • the processor 1 12 may set a threshold time for receiving a response from the network device 106.
  • the response to the service may be in the form of a service announcement including the service requested by the client device 104. If the service announcement is received within the threshold time, the access point 102. forwards the service announcement to the client device 104 via unicast transmission. However, if the service announcement is not received within the threshold time, the service announcement is discarded. Because the service announcement is sent via unicast transmission to the client device 104 requesting the service, traffic is reduced in the network.
  • FIG. 2 is a block diagram of a network access point for managing multicast transmissions over a network, according to one example.
  • access point 202 may communicate with a plurality of client devices 204a-204n over a network 220. Moreover, access point 202 may provide client devices 204a-204n with access to the network. Further, access point 202 may forward service requests received from client devices 204a-204n to one or more of network devices 206a-206n.
  • access point 202 may include a number of modules 221-227.
  • Each of the modules 221-227 may include a series of instructions encoded on a machine- readable storage medium and executable by a processor of the access point 202.
  • each module may include one or more hardware devices including electronic circuitry for implementing the functionality described below.
  • access point 202 may be any network node or device for providing network access to the plurality of client devices 204a-204n and/or for forwarding a multicast query/service request from the client devices 204a-204n to the network devices 206a-206n capable of fulfilling the service request.
  • access point 202 may include a series of modules 221-227 for receiving a multicast transmission from one or more client devices 204a-204n, forwarding the service request included in the multicast transmission to one or more network devices 206a-206n via unicast transmission, receiving a service announcement from the one or more network devices 206a-2.06n, and forwarding the one or more service announcements to the one or more client devices 204a-204n that request the service via unicast transmission.
  • Multicast query receiving module 221 may receive a multicast transmission from a client device such as client device 204a, where the multicast transmission includes a service request.
  • the service request can be a printing service.
  • Service type determining module 222 may determine a type of service requested by the client device 204a. For example, the multicast transmission may be analyzed to determine the type of service requested by the client device 204a (e.g., a printing service).
  • Service record creating module 223 may create and store a record associating the type of service to the client device. For example, a query table or record may be created to keep track of which clien t devices 204a-204n request what services.
  • Service request forwarding module 224 may forward the service request to one or more network devices 206a-206n via unicast transmission.
  • the service request may be forwarded to network devices 206a and 206n which may be identified or known to host tire type of service requested by tire client device 206a.
  • the service request is may not be forwarded via multicast transmission, thereby reducing the network traffic.
  • Timing module 2.25 may set a threshold time for receiving a response (e.g., a service announcement) from the network devices 206a and 206b. For example, a predetermined time in the order of a few seconds (e.g., 7 seconds) may be set for receiving a service
  • the service announcement may indicate that the network devices 206a, 206n are able to fulfill the service requested by the client device 204a.
  • the service announcement may also include information usable by the client device 204a for connecting to and accessing the service at the network device (e.g., network address, location of service, etc.).
  • Service announcement receiving module 22.6 may receive a service announcement from the network device 206a and/or 206n. As noted above, the service announcement may- enable the client device to discover the network device.
  • Service announcement forwarding module 227 may forward the service
  • the service announcement to the client device via unicast transmission. For example, if the service announcement is received within the threshold time, the service announcement is forwarded to the client device 204a via unicast transmission. If the service announcement is received after the threshold time has elapsed, the service announcement may be discarded. Further, the service announcement may also be sent via unicast transmission to another client device, for example client device 204b, that may have previously requested the same service requested by the client device 204a. Accordingly, the service announcement for a particular service may be sent to client devices 204a and 2.04b that have requested the particular service, but not to client devices 204c-204n that have not requested the particular service, based on the record (e.g., a query table) that associates client devices with types of service requested.
  • the record e.g., a query table
  • FIG. 3 is a flowchart of a method for managing multicast transmissions, according to one example.
  • Method 300 may be implemented, for example, in the form of executable instructions stored on a non-transitory computer-readable storage medium and/or in the form of electronic circuitry.
  • Method 300 includes receiving, at a network access point, a multicast query from a client device, where the multicast query includes a service request, at 310.
  • a printing service request may be sent from a client device to an access point via multicast transmission,
  • Method 300 includes creating and storing a record that associates the service with the client device, at 320.
  • the access point may create a record that contains information regarding the identity of a client device and the type of service requested by the client device.
  • Method 300 includes receiving a service announcement from a network device that hosts the service requested by the client device, at 330.
  • a network device may send a service announcement that indicates the availability of the service at the network device.
  • an available network printer may respond to the printing service request.
  • Method 300 includes forwarding the service announcement to the client via unicast transmission, at 340.
  • the access point may forward the service announcement to the client device that requested the service via unicast transmission.
  • the service request is forwarded via unicast transmission to other client devices that have also requested the same service.
  • FIG. 4 is a flowchart of a method for managing multicast transmissions, according to another example.
  • Method 400 may be implemented, for example, in the form of executable instructions stored on a non -transitory computer-readable storage medium and/or in the form of electronic circuitry.
  • Method 400 includes receiving, at a network access point, a multicast query from a client device, where the multicast query includes a service request, at 410.
  • a multicast service request may be sent from a client device requesting a service such as a printing sendee.
  • Method 400 includes creating and storing a record that associates the service with the client device, at 420.
  • the access point may analyze the query to determine the type of service requested by the client device, information relating to the client device and the type of service requested is stored as a record (e.g., in a table).
  • Method 400 includes forwarding the query to a network device hosting the requested service via unicast transmission, at 430.
  • the access point may forward a unicast service request to a network device such as a printing device that may service the request.
  • Method 400 includes setting a threshold time for receiving a service announcement from the network device, at 440.
  • the access point may set a timer (e.g., a few second) to receive a service announcement from the network device.
  • Method 400 includes receiving the service announcement from the network device, where the service announcement includes a type of service requested by the client device, at 450.
  • the access point may receive a service announcement from the network device.
  • Method 400 includes determining whether the service announcement is received wi hin the threshold time, at 460. if the service announcement is received within the threshold time, the service announcement is forwarded to the client device via unicast transmission, at 470. If however, it is determined at 460 that the service announcement is received after the threshold time has elapsed, the service announcement is discarded, at 480,
  • FIG. 5 is a block diagram of a multicast transmission manager including a computer- readable medium having instructions for managing multicast transmissions, according to one example.
  • Multicast transmission manager can be a wireless network access point, a base station, ad-hoc device, a controller, or any other network manager.
  • Manager 502 can include non-transitory computer-readable medium 520.
  • Medium 520 can include instructions 521- 526 that, if executed by a processor 12, can cause the processor to perform the functionality of the manager 501.
  • multicast service request receiving instructions 521 are executable to receive a multicast transmission from a client device, where the multicast transmission includes a service request.
  • Service request analyzing instructions 522 are executable to analyze the service request to determine a type of service requested by the client device.
  • Record creating and storing instructions 523 are executable to create and store a record that associates the type of service to the client device.
  • Service request forwarding instructions 524 are executable to forward the service request via unicast transmission to a network device known to host the type of service.
  • Service response receiving instructions 525 are executable to receive a response to the service request from the network device.
  • Service response forwarding instructions 526 are executable to forward the response to the client device via unicast transmission.
  • the examples described above may be embodied in a computer-readable medium for configuring a computing system to execute the method.
  • the computer-readable media may include, for example and without limitation, any number of the following non-transitive mediums: magnetic storage media including disk and tape storage media; optical storage media such as compact disk media (e.g., CD-ROM, CD-R, etc.) and digital video disk storage media; holographic memory; nonvolatile memory storage media including semiconductor- based memory units such as FLASH memory, EEPROM, EPROM, ROM; ferromagnetic digital memories; volatile storage media including registers, buffers or caches, main memory, RAM, etc.; and the internet, just to name a few.
  • Other new and obvious types of computer- readable media may be used to store the software modules discussed herein.
  • Computing systems may be found in many forms including but not limited to mainframes,

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon l'invention, une demande de service multidiffusion est reçue au niveau d'un point d'accès au réseau. Le point d'accès crée et stocke un enregistrement qui associe le service au dispositif client. Le point d'accès reçoit une annonce de service d'un dispositif de réseau hébergeant le service demandé par le dispositif client, et transmet l'annonce de service au dispositif client par le biais d'une transmission monodiffusion.
EP13894933.4A 2013-09-27 2013-09-27 Gestion de transmissions multidiffusion Withdrawn EP3050328A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/062416 WO2015047335A1 (fr) 2013-09-27 2013-09-27 Gestion de transmissions multidiffusion

Publications (1)

Publication Number Publication Date
EP3050328A1 true EP3050328A1 (fr) 2016-08-03

Family

ID=52744232

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13894933.4A Withdrawn EP3050328A1 (fr) 2013-09-27 2013-09-27 Gestion de transmissions multidiffusion

Country Status (3)

Country Link
EP (1) EP3050328A1 (fr)
CN (1) CN105745950A (fr)
WO (1) WO2015047335A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108834081B (zh) * 2018-05-25 2021-05-18 北京星网锐捷网络技术有限公司 一种组播业务处理方法及ap
US11824640B2 (en) * 2020-06-17 2023-11-21 Hewlett Packard Enterprise Development Lp System and method for reconfiguring a network using network traffic comparisions

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU7170301A (en) * 2000-06-29 2002-01-14 Cachestream Corp Virtual multicasting
KR100449018B1 (ko) * 2002-05-28 2004-09-18 삼성전자주식회사 멀티캐스트 서비스 제공방법과 그 방법을 적용한 서버
JP4898667B2 (ja) * 2004-06-16 2012-03-21 エルジー エレクトロニクス インコーポレイティド ユーザ位置情報に基づくブロードキャスト／マルチキャストサービス方法
US8626925B2 (en) * 2005-12-16 2014-01-07 Panasonic Corporation Systems and methods for providing a selective multicast proxy on a computer network
WO2011094939A1 (fr) * 2010-02-04 2011-08-11 上海贝尔股份有限公司 Procédé et dispositif d'accès pour un service basé sur des informations de position géographique
CN102300168B (zh) * 2010-06-22 2015-08-12 中兴通讯股份有限公司 一种实现集群通信的方法及系统
KR20130032173A (ko) * 2011-09-22 2013-04-01 한국전자통신연구원 멀티캐스트 방송 서비스를 위한 전송 모드 스위칭 방법 및 그 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2015047335A1 *

Also Published As

Publication number Publication date
WO2015047335A1 (fr) 2015-04-02
CN105745950A (zh) 2016-07-06

Similar Documents

Publication Publication Date Title
CN104283979B (zh) 组播域名系统中报文传输的方法、装置及系统
US20150326524A1 (en) Address resolution in software-defined networks
US20150222446A1 (en) Discovering IP Multicast Group Memberships in Software Defined Networks
JP2016510460A5 (fr)
CN107800625B (zh) 一种报文转发方法及装置
US11070424B2 (en) System and method for dynamic name configuration in content-centric networks
US20160036770A1 (en) Method to control dynamic host configuration protocol pool exhaustion in dynamic network environments
US20150281376A1 (en) System and method for device registration and discovery in content-centric networks
US10498836B2 (en) Network based service discovery via unicast messages
EP2218214B1 (fr) Service de localisation de réseau
WO2009024076A1 (fr) Procédé pour configurer un service et entité pour stocker une configuration de service
CN106027354B (zh) Vpn客户端的回流方法及装置
US9277014B2 (en) Handling of auxiliary NAS
CN105979405A (zh) 访问视频设备的方法及装置
CN105897542B (zh) 一种隧道建立方法及视频监控系统
EP3050328A1 (fr) Gestion de transmissions multidiffusion
WO2017219777A1 (fr) Procédé et dispositif de traitement de paquets
CN102710810A (zh) 一种自动分配ip地址的方法及一种中继设备
US11102167B2 (en) Systems and methods for multicast domain name system redundant query suppression
TW202333534A (zh) 運用於邊緣計算之資料傳送系統、方法及其電腦可讀媒介
JP2017152991A (ja) 情報配信装置、情報配信プログラム、通信端末、通信処理プログラム及び情報配信システム
JP6690291B2 (ja) 情報配信システム、情報配信装置、情報配信プログラム、及び情報配信方法
US20250310276A1 (en) Flood Suppression of Link-Local Multicast and Broadcast Traffic
US20200021450A1 (en) Managing multicast scaling
US12284056B2 (en) Service discovery across tunnel endpoints in overlays

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: 20160329

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

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: 20160817