WO2013010443A1 - 一种组播业务的实现方法及装置 - Google Patents

一种组播业务的实现方法及装置 Download PDF

Info

Publication number
WO2013010443A1
WO2013010443A1 PCT/CN2012/078399 CN2012078399W WO2013010443A1 WO 2013010443 A1 WO2013010443 A1 WO 2013010443A1 CN 2012078399 W CN2012078399 W CN 2012078399W WO 2013010443 A1 WO2013010443 A1 WO 2013010443A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
service
information
queue
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.)
Ceased
Application number
PCT/CN2012/078399
Other languages
English (en)
French (fr)
Inventor
曹登元
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to BR112014001250A priority Critical patent/BR112014001250A2/pt
Priority to RU2014105673/08A priority patent/RU2571398C2/ru
Priority to EP12814733.7A priority patent/EP2736196B1/en
Publication of WO2013010443A1 publication Critical patent/WO2013010443A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing a multicast service.
  • a multicast service is a forwarding service that is sent by a single data source and received by multiple receiving sources. Since the multicast service is a single-point to multi-point service, its data transmission efficiency is relatively high, thereby achieving the purpose of saving network bandwidth and reducing network load. Multicast services can implement live video, Internet telephony, video conferencing, and more.
  • different multicast services have different requirements for transmission conditions such as bandwidth, delay, jitter, and real-time.
  • the IPTV service has higher requirements for jitter, and the video conference multicast service requires higher real-time performance.
  • different user levels have different bandwidth resource requirements.
  • different multicast services and user levels are not distinguished, that is, different multicast services use the same transmission conditions, and different user levels use the same bandwidth resources, thereby failing to satisfy different multicasts. Business and user level requirements.
  • the embodiments of the present invention provide a method and a device for implementing a multicast service, which are used to solve the problem that the existing multicast services are not differentiated from the multicast service and cannot meet the requirements of different multicast services.
  • An embodiment of the present invention provides a method for implementing a multicast service, including:
  • the service queue corresponding to the successfully matched multicast service identification information is allocated to the multicast service, and the service queue is used to implement the multicast. business;
  • the matching of the multicast service identification information is unsuccessful, the default service queue is allocated to the multicast service, and the multicast service is implemented by using the default queue.
  • the method further includes:
  • the user queue is allocated for the multicast service according to the configuration parameter information corresponding to the successfully matched user level identifier information, and when the user level identifier information is unsuccessful, The multicast service allocates a default user queue.
  • the method further includes:
  • the configuration parameter update information is received, and the correspondence between the user level identification information and the updated configuration parameter information is established according to the user level identification information and the updated configuration parameter information carried in the configuration parameter update information.
  • the method further includes:
  • the method further includes:
  • Receiving service queue update information establishing correspondence between the multicast service identification information and the updated service queue information according to the multicast service identification information and the updated service queue information carried in the service queue update information relationship.
  • An embodiment of the present invention provides a device for implementing a multicast service, including: a matching module, a first allocation implementation module, and a second distribution implementation module, where
  • the matching module is configured to: receive a multicast service join request, and match the multicast service identifier information carried in the request by the multicast service with the multicast service identifier information that is saved by the service to be guaranteed;
  • the first allocation implementation module is configured to: when the multicast service identification information is successfully matched, Allocating the saved service queue corresponding to the successfully matched multicast service identification information to the multicast service, and using the service queue to implement the multicast service;
  • the second allocation implementation module is configured to: when the multicast service identification information is unsuccessful, allocate a default service queue for the multicast service, and use the default queue to implement the multicast service.
  • the matching module is further configured to: match the user level identifier information carried in the multicast service request with the user level identifier information saved by the multicast service;
  • the first allocation implementation module is further configured to: when the user level identifier information is successfully matched, assign a user queue to the multicast service according to the configuration parameter information corresponding to the successfully matched user level identifier information, When the user level identifier information is unsuccessful, the default user queue is allocated for the multicast service.
  • the device further includes: an update module, wherein
  • the update module is configured to: receive the configuration parameter update information, and establish the user level identifier information and the updated one according to the user level identifier information and the updated configuration parameter information carried in the configuration parameter update information. Correspondence between configuration parameter information.
  • the matching module is further configured to: receive a multicast service release request, and perform the multicast service identifier information carried in the multicast service release request and the multicast service identifier information that is saved by the user to be guaranteed by the service Match
  • the device further includes: a release module, where the release module is configured to: when the multicast service identification information is successfully matched, release the service queue corresponding to the successfully matched multicast service identification information.
  • the update module is further configured to: receive service queue update information, and establish the multicast service identification information and the updated information according to the multicast service identification information and the updated service queue information carried in the service queue update information. Correspondence between service queues.
  • An embodiment of the present invention provides a method and an apparatus for implementing a multicast service.
  • the multicast service is added to the multicast service identifier information carried in the request and the required service guarantee is saved.
  • the multicast service identification information is matched, and when the multicast service identification information is successfully matched, the service queue corresponding to the successfully matched multicast service identification information is allocated to the multicast service and the multicast service is implemented.
  • the multicast service identification information is unsuccessful, the default service queue is used to implement the multicast service. Due to different multicasts in the embodiments of the present invention
  • the service is configured to meet the service queue of the multicast service.
  • the multicast service identifier information carried in the multicast service join request is allocated for the multicast service.
  • the service queue implements the multicast service, which satisfies the requirements of different multicast services, and is beneficial to the improvement of the service quality of the multicast service.
  • FIG. 1 is a schematic diagram of an implementation process of a multicast service according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a detailed implementation process of a multicast service according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of an apparatus for implementing a multicast service according to an embodiment of the present invention.
  • the embodiment of the present invention provides a multicast service implementation method and device.
  • FIG. 1 is a schematic diagram of an implementation process of a multicast service according to an embodiment of the present invention, where the process includes the following steps:
  • the multicast service join request carries the multicast service identifier information, where the multicast service identifier information may be an IDentity (ID) of the multicast service, or may be a name information of the multicast service. As long as the information that can uniquely identify the multicast service can be used as the identification information of the multicast service.
  • ID IDentity
  • step S102 Matching the multicast service identification information carried in the request of the multicast service to the multicast service identification information that is saved by the service, and the multicast service identification information is successfully matched.
  • the process proceeds to step S104.
  • S103 Allocate the saved service queue corresponding to the successfully matched multicast service identifier information to the multicast service, and use the service queue to implement the multicast service.
  • the service quality of the multicast service is ensured, and the identification information of each multicast service that needs to be guaranteed by the service is saved, and according to the requirements of different multicast services,
  • Each multicast service sets a corresponding service queue, each service queue meets the corresponding requirements of different multicast services, and uses different quality parameters for each service queue, and saves the identification information of each multicast service and the The corresponding relationship of the corresponding service queues is allocated, so that when the service queue is allocated, the service queue can be allocated for the multicast service according to the correspondence.
  • a service queue with a small jitter can be allocated to the multicast service, that is, a correspondence between the identification information of the VoIP service and the service queue with less jitter can be saved.
  • S104 Allocate a default service queue for the multicast service, and implement the multicast service by using the default queue.
  • the multicast service that is not required for the transmission condition may be allocated a default service queue for the multicast service, that is, the existing multicast service implementation manner is used to implement the multicast service.
  • a service queue that satisfies the multicast service is set for different multicast services.
  • the user level may be considered to correspond to the default parameter information, and the user queue may be allocated for the multicast service according to the default parameter information.
  • the user queue is allocated for the multicast service according to the configuration parameter information corresponding to the successfully matched user level identifier information, and when the user level identifier information is unsuccessful, the The multicast service allocates a default user queue.
  • the bandwidth requirements of different levels of users may also be constantly changing.
  • the configuration parameter information of the users of the level needs to be updated, and the method further includes And receiving the configuration parameter update information, and establishing a correspondence between the user level identifier information and the updated configuration parameter information according to the user level identifier information and the updated configuration parameter information carried in the configuration parameter update information.
  • the demand for the transmission condition of the multicast service may be changed.
  • the multicast service needs to be implemented by using other service queues.
  • the method further includes: receiving the service queue update information, and updating the multicast service identification information and the updated service carried in the service queue update information according to the service queue update information Queue information, establishing a correspondence between the multicast service identification information and the updated service queue information.
  • a certain multicast service is completed, a multicast service release request is sent, and the corresponding resource needs to be released.
  • the multicast service identification information carried in the multicast service release request is matched with the multicast service identification information that is saved by the service.
  • the service queue corresponding to the successfully matched multicast service identification information is released.
  • FIG. 2 is a schematic diagram of a detailed implementation process of a multicast service according to an embodiment of the present invention, where the process includes the following steps:
  • the related table entry is copied according to the forwarding requirement of the multicast service, and the multicast data packet is copied.
  • step S202 Matching the multicast service identification information carried in the request of the multicast service to the multicast service identification information that is saved by the service, and the multicast service identification information is successfully matched.
  • step S203 when the matching of the multicast service identification information is unsuccessful, step S204 is performed.
  • step S203 Allocate the saved service queue corresponding to the successfully matched multicast service identifier information to the multicast service, and use the service queue to implement the multicast service. Thereafter, step S205 is performed.
  • mapping relationship between the service quality parameter information and the service quality parameter information may be saved, and the mapping relationship between the service quality parameter information and the service queue is saved, and the configuration of the corresponding service quality parameter is determined according to the multicast service identification information, and A mapping of the internal index to the service queue is generated according to the mapping relationship between the quality of service parameter and the service queue.
  • S204 Allocate a default service queue for the multicast service, and implement the multicast service by using the default service queue.
  • the identifier information of the multicast service is the normal multicast service identifier information, that is, when the multicast service has a low transmission condition, the default quality parameter is assigned to the multicast service.
  • the multicast service allocates a default service queue, which generates a mapping of the default internal index to the default service queue.
  • step S206 Match the multicast service identifier information carried in the multicast service release request with the multicast service identifier information that is saved by the service. If the multicast service identifier information is successfully matched, go to step S207.
  • the service queue needs to be released, and the mapping to the service queue is released, and the internal index is released to be used by the multicast service at other points in time.
  • the multicast service that does not need to perform service guarantee is allocated a default service queue, that is, the method of the related technology is used to allocate a service queue for the multicast service. Since the same default service queue may be assigned to different multicast services, when the release request of the multicast service is received, if the default service queue is only used by the multicast service, the default may be released at this time. Service queue. If the default service queue is also used by other multicast services at this time, the default service queue cannot be released at this time.
  • Each corresponding default service queue is allocated, that is, each default service queue is used by only one multicast service.
  • the release request of the multicast service is received, the default service queue is released.
  • the multicast service identification information included in the multicast service join request is a normal multicast service, that is, if the matching of the multicast service identification information that is required to be guaranteed by the service is unsuccessful, the default index is obtained, and the default service queue is allocated. (Assigned based on physical or logical ports), and increments the reference count by 1, after which the mapping of the default index to the default service queue is set.
  • the multicast service identification information included in the multicast service join request is a special multicast service, that is, when the multicast service identification information of the saved service-guaranteed service is successfully matched, the multicast service identification information and the service quality are obtained.
  • Corresponding relationship between the user level identifier information and the updated configuration parameter information is established according to the user level identifier information and the updated configuration parameter information carried in the received configuration parameter update information. And establishing, according to the multicast service identifier information carried in the service queue update information and the updated service queue information, a correspondence between the multicast service identifier information and the updated service queue.
  • the multicast service release request When the multicast service release request is received, and the multicast service is a special multicast service, that is, the multicast service identification information carried in the multicast service release request matches the saved multicast service identification information of the required service guarantee.
  • the replication-related entries are deleted, the internal index is released, and the service queue corresponding to the successfully matched multicast service identification information is released, and the mapping of the internal index to the service queue is deleted, and the default service queue mapping relationship is restored.
  • FIG. 3 is a schematic structural diagram of an apparatus for implementing a multicast service according to an embodiment of the present disclosure, where the apparatus includes: a matching module 31, a first allocation implementation module 32, and a second allocation implementation module 33, where
  • the matching module 31 is configured to: receive a multicast service join request, and match the multicast service identifier information carried in the multicast service request with the multicast service identifier information that is saved by the service that is required by the service;
  • the first allocation implementation module 32 is configured to: when the multicast service identification information is successfully matched, allocate the saved service queue corresponding to the successfully matched multicast service identification information to the multicast service, and use the The service queue implements the multicast service;
  • the second allocation implementation module 33 is configured to: when the multicast service identification information is unsuccessful, allocate a default service queue for the multicast service, and use the default service queue to implement the multicast service.
  • the matching module 31 is further configured to: match the user level identification information carried in the multicast service request with the user level identifier information saved by the user;
  • the first allocation implementation module 32 is further configured to: when the user level identification information is successfully matched, assign a user queue to the multicast service according to the configuration parameter information corresponding to the successfully matched user level identification information, when the user level When the identification information is unsuccessful, a default user queue is allocated for the multicast service.
  • the apparatus also includes: an update module 34.
  • the update module 34 is configured to: receive the configuration parameter update information, and establish the user level identifier information and the updated information according to the user level identifier information and the updated configuration parameter information carried in the configuration parameter update information. Correspondence of configuration parameter information.
  • the matching module 31 is further configured to: receive a multicast service release request, and match the multicast service identification information carried in the multicast service release request with each multicast service identification information that is saved by the service to be guaranteed;
  • the device also includes: a release module 35.
  • the release module 35 is configured to: when the multicast service identification information is successfully matched, release the service queue corresponding to the successfully matched multicast service identification information.
  • the update module 34 is further configured to: receive the service queue update information, and establish the multicast service identifier information and the update according to the multicast service identifier information carried in the service queue update information and the updated service queue information. Correspondence between post-service queues.
  • An embodiment of the present invention provides a method and an apparatus for implementing a multicast service.
  • the multicast service is added to the multicast service identifier information carried in the request and the required service guarantee is saved.
  • the multicast service identification information is matched, and if the multicast service identification information is successfully matched, the service queue corresponding to the successfully matched multicast service identification information is allocated to the multicast service and the multicast service is implemented. If the multicast service identification information is unsuccessful, the default service queue is used to implement the multicast service.
  • a service queue that satisfies the multicast service is set for different multicast services.
  • the multicast carried in the multicast service join request is received.
  • the service identification information is used to allocate the corresponding service queue for the multicast service to implement the multicast service, thereby satisfying the requirements of different multicast services, and is beneficial to improving the service quality of the multicast service.
  • a service queue that satisfies the multicast service is set for different multicast services. Therefore, when the multicast service join request is received, the multicast service identifier carried in the multicast service join request is received. The information is allocated to the multicast service to implement the multicast service, so that the requirements of different multicast services are met, which is beneficial to the improvement of the service quality of the multicast service.

Landscapes

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

Abstract

一种组播业务实现方法及装置，该方法包括：当接收到组播业务加入请求时，将该组播业务加入请求中携带的组播业务标识信息与自身保存的各组播业务标识信息进行匹配，当组播业务标识信息匹配成功时，将保存的该匹配成功的组播业务标识信息对应的服务队列，分配给所述组播业务并实现该组播业务，当组播业务标识信息匹配不成功时，采用默认服务队列实现该组播业务。本发明实施例中针对不同的组播业务设置了相应的满足该组播业务的服务队列，因此当接收到该组播业务加入请求时，根据该组播业务加入请求中携带的组播业务标识信息，为该组播业务分配相应的服务队列实现该组播业务，从而满足了不同组播业务的需求，有利于组播业务服务质量的提高。

Description

一种组播业务的实现方法及装置
技术领域
本发明涉及通信技术领域， 尤其涉及一种组播（Multicast ) 业务的实现 方法及装置。
背景技术
组播业务是一种单个数据源发送， 多个接收源接收的转发业务。 组播业 务由于是单点到多点业务， 因此其数据传输效率比较高， 从而达到节约网络 带宽、 降低网络负荷的目的。 组播业务可以实现视频直播、 网络电话、 视频 会议等。
但是， 不同的组播业务对带宽、 延时、 抖动、 实时性等传输条件有不同 的要求， 例如， 网络电视组播业务对抖动要求比较高， 视频会议组播业务对 实时性要求比较高。 同时， 不同的用户等级有不同的带宽资源要求。 但是相 关技术中， 并没有针对不同的组播业务及用户等级进行区分， 即不同的组播 业务釆用相同的传输条件， 并且不同的用户等级釆用相同的带宽资源， 从而 无法满足不同组播业务及用户等级的需求。
发明内容
本发明实施例提供了一种组播业务实现方法及装置， 用以解决现有组播 业务实现过程中， 对组播业务不进行区分， 无法满足不同组播业务需求的问 题。
本发明实施例提供一种组播业务的实现方法， 包括：
接收组播业务加入请求， 将所述组播业务加入请求中携带的组播业务标 识信息与自身保存的需业务保证的各组播业务标识信息进行匹配；
当所述组播业务标识信息匹配成功时， 将保存的所述匹配成功的组播业 务标识信息对应的服务队列， 分配给所述组播业务， 并釆用所述服务队列实 现所述组播业务； 当所述组播业务标识信息匹配不成功时 , 为所述组播业务分配默认服务 队列， 釆用所述默认队列实现所述组播业务。
所述方法还包括：
将所述组播业务加入请求中携带的用户等级标识信息， 与自身保存的用 户等级标识信息进行匹配；
当所述用户等级标识信息匹配成功时， 根据所述匹配成功的用户等级标 识信息对应的配置参数信息， 为所述组播业务分配用户队列， 当所述用户等 级标识信息匹配不成功时， 为所述组播业务分配默认用户队列。
所述方法还包括：
接收配置参数更新信息， 根据所述配置参数更新信息中携带的用户等级 标识信息及更新后的配置参数信息， 建立所述用户等级标识信息与所述更新 后的配置参数信息的对应关系。
所述方法还包括：
接收组播业务释放请求 , 将所述组播业务释放请求中携带的所述组播业 务标识信息与自身保存的需业务保证的所述各组播业务标识信息进行匹配； 当所述组播业务标识信息匹配成功时， 释放匹配成功的组播业务标识信 息对应的所述 Λ良务队列。
所述方法还包括：
接收服务队列更新信息， 根据所述服务队列更新信息中携带的组播业务 标识信息及更新后的服务队列信息， 建立所述组播业务标识信息与所述更新 后的服务队列信息之间的对应关系。
本发明实施例提供一种组播业务的实现装置， 包括： 匹配模块， 第一分 配实现模块和第二分配实现模块， 其中，
所述匹配模块设置成： 接收组播业务加入请求， 将所述组播业务加入请 求中携带的组播业务标识信息与自身保存的需业务保证的各组播业务标识信 息进行匹配；
所述第一分配实现模块设置成： 当所述组播业务标识信息匹配成功时， 将保存的所述匹配成功的组播业务标识信息对应的服务队列， 分配给所述组 播业务， 并釆用所述服务队列实现所述组播业务； 以及
所述第二分配实现模块设置成： 当所述组播业务标识信息匹配不成功时， 为所述组播业务分配默认服务队列， 釆用所述默认队列实现所述组播业务。
所述匹配模块还设置成： 将所述组播业务加入请求中携带的用户等级标 识信息， 与自身保存的用户等级标识信息进行匹配；
所述第一分配实现模块还设置成： 当所述用户等级标识信息匹配成功时， 根据所述匹配成功的用户等级标识信息对应的配置参数信息， 为所述组播业 务分配用户队列， 当所述用户等级标识信息匹配不成功时， 为所述组播业务 分配默认用户队列。
所述装置还包括： 更新模块， 其中，
所述更新模块设置成： 接收所述配置参数更新信息， 根据所述配置参数 更新信息中携带的用户等级标识信息及更新后的配置参数信息， 建立所述用 户等级标识信息与所述更新后的配置参数信息的对应关系。
所述匹配模块还设置成： 接收组播业务释放请求， 将所述组播业务释放 请求中携带的所述组播业务标识信息与自身保存的需业务保证的所述各组播 业务标识信息进行匹配；
所述装置还包括： 释放模块， 所述释放模块设置成： 当所述组播业务标 识信息匹配成功时 ,释放匹配成功的组播业务标识信息对应的所述服务队列。
所述更新模块还设置成： 接收服务队列更新信息， 根据所述服务队列更 新信息中携带的组播业务标识信息及更新后的服务队列信息， 建立所述组播 业务标识信息与所述更新后的服务队列之间的对应关系。
本发明实施例提供一种组播业务实现方法及装置， 该方法中当接收到组 播业务加入请求时， 将该组播业务加入请求中携带的组播业务标识信息与自 身保存的需业务保证的各组播业务标识信息进行匹配， 当组播业务标识信息 匹配成功时， 将保存的该匹配成功的组播业务标识信息对应的服务队列， 分 配给所述组播业务并实现该组播业务， 当组播业务标识信息匹配不成功时， 釆用默认服务队列实现该组播业务。 由于在本发明实施例中针对不同的组播 业务设置了相应的满足该组播业务的服务队列， 因此当接收到该组播业务加 入请求时， 根据该组播业务加入请求中携带的组播业务标识信息， 为该组播 业务分配相应的服务队列实现该组播业务，从而满足了不同组播业务的需求， 有利于组播业务服务质量的提高。 附图概述
此处所说明的附图用作对本发明的进一步理解， 构成本发明的一部分， 本发明的示意性实施例及其说明用于解释本发明技术方案， 并不构成对本发 明技术方案的不当限定。 在附图中：
图 1为本发明实施例中组播业务的实现过程示意图；
图 2为本发明实施例提供的组播业务的详细实现过程示意图；
图 3为本发明实施例提供的一种组播业务的实现装置的结构示意图。
本发明的较佳实施方式
以下结合附图和实施例， 对本发明技术方案进行进一步详细说明。 应当 理解， 此处所描述的具体实施例仅仅用以解释本发明技术方案， 并不用于限 定本发明保护范围。
本发明实施例为了满足不同组播业务的需求，提高组播业务的服务质量， 提供了一种组播业务实现方法及装置。
图 1为本发明实施例中组播业务的实现过程示意图， 该过程包括以下步 骤：
S 101： 接收组播业务加入请求。
其中， 该组播业务加入请求中携带有组播业务标识信息， 该组播业务标 识信息可以为组播业务的身份标识号码（IDentity, ID ) , 也可以为该组播业 务的名称信息等， 只要可以唯一标识该组播业务的信息都可以作为该组播业 务的标识信息。
S102: 将该组播业务加入请求中携带的组播业务标识信息与自身保存的 需业务保证的各组播业务标识信息进行匹配， 当组播业务标识信息匹配成功 时， 进行步骤 S103 , 当组播业务标识信息匹配不成功时， 进行步骤 S104。
S103 : 将保存的该匹配成功的组播业务标识信息对应的服务队列， 分配 给所述组播业务， 并釆用所述服务队列实现所述组播业务。
具体的在本发明实施例中为了满足不同组播业务的需求， 保证组播业务 的服务质量， 保存了需要进行业务保证的各组播业务的标识信息， 并且根据 不同组播业务的需求， 为每个组播业务设置相应的服务队列， 每种服务队列 满足不同组播业务的相应需求， 并且为每个服务队列釆用不同的质量参数， 并保存每个组播业务的标识信息与该被分配的相应的服务队列的对应关系， 以便在进行服务队列分配时，可以根据该对应关系为组播业务分配服务队列。
例如， 对于网络电话组播业务， 可以将抖动较小的服务队列分配给该组 播业务， 即可以保存网络电话组播业务的标识信息， 与该抖动较小的服务队 列的对应关系。
S104: 为所述组播业务分配默认服务队列， 釆用所述默认队列实现所述 组播业务。
在本发明实施例中对传输条件没有要求的组播业务， 可以为该组播业务 分配默认服务队列， 即釆用现有的组播业务实现方式实现该组播业务。 由于在本发明实施例中针对不同的组播业务设置了相应的满足该组播业 务的服务队列， 因此当接收到该组播业务加入请求时， 根据该组播业务加入 请求中携带的组播业务标识信息， 为该组播业务分配相应的服务队列实现该 组播业务， 从而满足了不同组播业务的需求， 有利于组播业务服务质量的提 高。
另外， 由于不同的用户等级对带宽有不同的需求， 为了满足不同用户等 级的带宽需求， 为不同用户等级配置相应的参数， 并保存每个用户等级标识 信息与被配置的参数信息的对应关系。当某一用户等级未被配置参数信息时， 则可以认为该用户等级与默认参数信息相对应， 可以根据默认参数信息， 为 组播业务分配用户队列。
本发明实施例的方法还可以包括：
将该组播业务加入请求中携带的用户等级标识信息， 与自身保存的用户 等级标识信息进行匹配；
当所述用户等级标识信息匹配成功时， 根据匹配成功的用户等级标识信 息对应的配置参数信息， 为所述组播业务分配用户队列， 当所述用户等级标 识信息匹配不成功时， 为所述组播业务分配默认用户队列。
而不同等级的用户其所需的带宽条件也可能在不断的变化， 为了满足不 同等级用户的需求， 当该等级用户的需求发生变化时， 需要更新该等级用户 的配置参数信息， 该方法还包括： 接收配置参数更新信息， 根据所述配置参 数更新信息中携带的用户等级标识信息及更新后的配置参数信息， 建立所述 用户等级标识信息与更新后的所述配置参数信息的对应关系。
另外，在本发明实施例中组播业务其对传输条件的需求可能是在变化的， 此时需要釆用其他的服务队列实现该组播业务， 在本发明实施例中为了及时 准确的满足各种组播业务的需求， 当某一组播业务的传输条件发生变化时， 该方法还包括： 接收服务队列更新信息， 根据该服务队列更新信息中携带的 组播业务标识信息及更新后的服务队列信息， 建立所述组播业务标识信息与 该更新后的服务队列信息之间的对应关系。 在本发明实施例中当某一组播业务完成后， 会发送组播业务释放请求， 此时需要释放相应的资源， 具体的在本发明实施例中当接收到组播业务释放 请求时， 将该组播业务释放请求中携带的组播业务标识信息与自身保存的需 业务保证的各组播业务标识信息进行匹配；
当组播业务标识信息匹配成功时， 释放匹配成功的组播业务标识信息对 应的服务队列。
图 2为本发明实施例提供的组播业务的详细实现过程示意图， 该过程包 括以下步骤：
S201： 接收组播业务加入请求。
当接收到组播业务加入请求时， 根据该组播业务的转发需求复制相关表 项设置， 并完成组播数据包的复制。
S202: 将该组播业务加入请求中携带的组播业务标识信息与自身保存的 需业务保证的各组播业务标识信息进行匹配， 当组播业务标识信息匹配成功 时， 进行步骤 S203 , 当组播业务标识信息匹配不成功时， 进行步骤 S204。
S203 : 将保存的该匹配成功的组播业务标识信息对应的服务队列， 分配 给所述组播业务， 并釆用所述服务队列实现所述组播业务。 之后， 进行步骤 S205。
具体的也可以保存每个组播业务标识信息与服务质量参数信息的对应关 系， 并保存服务质量参数信息与服务队列的映射关系， 根据组播业务标识信 息确定相应的服务质量参数的配置， 并根据服务质量参数与服务队列之间的 映射关系， 生成内部索引到该服务队列的映射。
S204: 为所述组播业务分配默认服务队列， 釆用所述默认服务队列实现 所述组播业务。
当该组播业务加入请求中该组播业务的标识信息为普通的组播业务标识 信息时， 即该组播业务对传输条件不高时， 即为该组播业务分配默认质量参 数， 为该组播业务分配默认服务队列， 生成默认内部索引到该默认服务队列 的映射。
S205: 接收组播业务释放请求。
S206: 将该组播业务释放请求中携带的组播业务标识信息与自身保存的 需业务保证的各组播业务标识信息进行匹配， 当组播业务标识信息匹配成功 时， 进行步骤 S207。
S207: 释放该匹配成功的组播业务标识信息对应的服务队列。
此时需要释放该服务队列， 并解除到该服务队列的映射， 释放内部索引， 以便被其他时间点的组播业务使用。
具体的在本发明实施例中， 不需要进行业务保证的组播业务被分配了默 认服务队列， 即釆用相关技术的方法为该组播业务分配服务队列。 由于相同 的默认服务队列可能会被分配给不同的组播业务， 因此当接收到该组播业务 的释放请求时， 如果该默认服务队列只被该组播业务使用， 则此时可以释放 该默认服务队列， 如果该默认服务队列此时还被其他组播业务使用， 则此时 不能释放该默认服务队列。
或者，在本发明实施例中可以针对每个不需要进行业务保证的组播业务， 分配每个对应的默认服务队列， 也就是说每个默认服务队列只被一个组播业 务使用， 当接收到该组播业务的释放请求时， 则释放该默认服务队列。
下面以一个具体的实施例进行说明。
接收组播业务加入请求， 进行组播相关表项和组播数据包的复制。 当该 组播业务加入请求中包含的组播业务标识信息， 为普通组播业务时， 即与保 存的需业务保证的各组播业务标识信息匹配不成功时， 获取默认索引， 分配 默认服务队列 （基于物理或者逻辑端口来分配） ， 并将引用计数加 1 , 之后， 设置默认索引到默认服务队列的映射。
当该组播业务加入请求中包含的组播业务标识信息，为特殊组播业务时， 即与保存的需业务保证的各组播业务标识信息匹配成功时， 根据组播业务标 识信息与服务质量参数信息的对应关系， 及服务质量参数信息与服务队列的 映射关系， 申请内部索引及确定相应的服务队列， 设置该内部索引到该服务 队列的映射。
根据接收到的配置参数更新信息中携带的用户等级标识信息及更新后的 配置参数信息， 建立所述用户等级标识信息与更新后的所述配置参数信息的 对应关系。 并根据服务队列更新信息中携带的组播业务标识信息及更新后的 服务队列信息， 建立所述组播业务标识信息与该更新后的服务队列之间的对 应关系。
当接收到组播业务释放请求时， 且当该组播业务为特殊组播业务， 即组 播业务释放请求中携带的组播业务标识信息与保存的需业务保证的各组播业 务标识信息匹配成功时， 删除复制相关表项， 释放内部索引， 并释放该匹配 成功的组播业务标识信息对应的服务队列， 并删除内部索引到该服务队列的 映射， 还原默认服务队列映射关系。
当该组播业务为普通组播业务， 即组播业务释放请求中携带的组播业务 标识信息与保存的需业务保证的各组播业务标识信息匹配不成功时， 删除复 制相关表项， 引用计数减 1 , 如果引用计数为非 0, 则操作结束， 即此时还有 其他组播业务使用该默认服务队列， 否则， 释放默认服务队列， 删除内部索 引到该服务队列的映射。 图 3为本发明实施例提供的一种组播业务的实现装置的结构示意图， 所 述装置包括： 匹配模块 31 , 第一分配实现模块 32和第二分配实现模块 33 , 其中，
所述匹配模块 31设置成： 接收组播业务加入请求， 将所述组播业务加入 请求中携带的组播业务标识信息与自身保存的需业务保证的各组播业务标识 信息进行匹配；
所述第一分配实现模块 32设置成： 当组播业务标识信息匹配成功时， 将 保存的匹配成功的组播业务标识信息对应的服务队列，分配给所述组播业务， 并釆用所述服务队列实现所述组播业务；
所述第二分配实现模块 33设置成： 当组播业务标识信息匹配不成功时， 为所述组播业务分配默认服务队列， 釆用所述默认服务队列实现所述组播业 务。
所述匹配模块 31还设置成：将所述组播业务加入请求中携带的用户等级 标识信息， 与自身保存的用户等级标识信息进行匹配；
第一分配实现模块 32还设置成： 当用户等级标识信息匹配成功时， 根据 所述匹配成功的用户等级标识信息对应的配置参数信息， 为所述组播业务分 配用户队列， 当所述用户等级标识信息匹配不成功时， 为所述组播业务分配 默认用户队列。
所述装置还包括： 更新模块 34。
所述更新模块 34设置成： 接收所述配置参数更新信息， 根据所述配置参 数更新信息中携带的用户等级标识信息及更新后的配置参数信息， 建立所述 用户等级标识信息与所述更新后的配置参数信息的对应关系。
所述匹配模块 31还设置成： 接收组播业务释放请求， 将所述组播业务释 放请求中携带的组播业务标识信息与自身保存的需业务保证的各组播业务标 识信息进行匹配；
所述装置还包括： 释放模块 35。
所述释放模块 35设置成： 当组播业务标识信息匹配成功时， 释放匹配成 功的组播业务标识信息对应的服务队列。 所述更新模块 34还设置成： 接收服务队列更新信息， 根据所述服务队列 更新信息中携带的组播业务标识信息及更新后的服务队列信息， 建立所述组 播业务标识信息与所述更新后的服务队列之间的对应关系。
本发明实施例提供一种组播业务实现方法及装置， 该方法中当接收到组 播业务加入请求时， 将该组播业务加入请求中携带的组播业务标识信息与自 身保存的需业务保证的各组播业务标识信息进行匹配， 如果组播业务标识信 息匹配成功， 将保存的该匹配成功的组播业务标识信息对应的服务队列， 分 配给所述组播业务并实现该组播业务， 如果组播业务标识信息匹配不成功， 釆用默认服务队列实现该组播业务。 由于在本发明实施例中针对不同的组播 业务设置了相应的满足该组播业务的服务队列， 因此当接收到该组播业务加 入请求时， 根据该组播业务加入请求中携带的组播业务标识信息， 为该组播 业务分配相应的服务队列实现该组播业务，从而满足了不同组播业务的需求， 有利于组播业务服务质量的提高。
上述说明示出并描述了本发明的一个优选实施例， 但如前所述， 应当理 解本发明保护范围并非局限于本文所披露的形式， 不应看作是对其他实施例 的排除， 而可用于各种其他组合、 修改和环境， 并能够在本文所述发明构想 范围内， 通过上述教导或相关领域的技术或知识进行改动。 而本领域人员所 进行的改动和变化不脱离本发明的精神和范围， 则都应在本发明所附权利要 求的保护范围内。
工业实用性
本发明实施例中针对不同的组播业务设置了相应的满足该组播业务的服 务队列， 因此当接收到该组播业务加入请求时， 根据该组播业务加入请求中 携带的组播业务标识信息， 为该组播业务分配相应的服务队列实现该组播业 务， 从而满足了不同组播业务的需求， 有利于组播业务服务质量的提高。

Claims

权 利 要 求 书
1、 一种组播业务的实现方法， 包括：
接收组播业务加入请求， 将所述组播业务加入请求中携带的组播业务标 识信息与自身保存的需业务保证的各组播业务标识信息进行匹配；
当所述组播业务标识信息匹配成功时， 将保存的匹配成功的组播业务标 识信息对应的服务队列， 分配给所述组播业务， 并釆用所述服务队列实现所 述组播业务；
当所述组播业务标识信息匹配不成功时， 为所述组播业务分配默认服务 队列， 釆用所述默认队列实现所述组播业务。
2、 如权利要求 1所述的方法， 所述方法还包括：
将所述组播业务加入请求中携带的用户等级标识信息， 与自身保存的用 户等级标识信息进行匹配；
当所述用户等级标识信息匹配成功时， 根据匹配成功的用户等级标识信 息对应的配置参数信息， 为所述组播业务分配用户队列， 当所述用户等级标 识信息匹配不成功时， 为所述组播业务分配默认用户队列。
3、 如权利要求 2所述的方法， 还包括：
接收配置参数更新信息， 根据所述配置参数更新信息中携带的用户等级 标识信息及更新后的配置参数信息， 建立所述用户等级标识信息与所述更新 后的配置参数信息的对应关系。
4、 如权利要求 1所述的方法， 还包括：
接收组播业务释放请求 , 将所述组播业务释放请求中携带的所述组播业 务标识信息与自身保存的需业务保证的所述各组播业务标识信息进行匹配； 当所述组播业务标识信息匹配成功时， 释放匹配成功的组播业务标识信 息对应的所述 Λ良务队列。
5、 如权利要求 1所述的方法， 还包括： 接收服务队列更新信息， 根据所述服务队列更新信息中携带的组播业务 标识信息及更新后的服务队列信息， 建立所述组播业务标识信息与所述更新 后的服务队列信息之间的对应关系。
6、 一种组播业务的实现装置， 包括： 匹配模块， 第一分配实现模块和第 二分配实现模块， 其中，
所述匹配模块设置成： 接收组播业务加入请求， 将所述组播业务加入请 求中携带的组播业务标识信息与自身保存的需业务保证的各组播业务标识信 息进行匹配；
所述第一分配实现模块设置成： 当所述组播业务标识信息匹配成功时， 将保存的匹配成功的组播业务标识信息对应的服务队列， 分配给所述组播业 务， 并釆用所述服务队列实现所述组播业务； 以及
所述第二分配实现模块设置成：当所述组播业务标识信息匹配不成功时， 为所述组播业务分配默认服务队列， 釆用所述默认队列实现所述组播业务。
7、 如权利要求 6所述的装置， 其中，
所述匹配模块还设置成： 将所述组播业务加入请求中携带的用户等级标 识信息， 与自身保存的用户等级标识信息进行匹配；
所述第一分配实现模块还设置成：当所述用户等级标识信息匹配成功时， 根据所述匹配成功的用户等级标识信息对应的配置参数信息， 为所述组播业 务分配用户队列， 当所述用户等级标识信息匹配不成功时， 为所述组播业务 分配默认用户队列。
8、 如权利要求 7所述的装置， 还包括： 更新模块， 其中，
所述更新模块设置成： 接收配置参数更新信息， 根据所述配置参数更新 信息中携带的用户等级标识信息及更新后的配置参数信息， 建立所述用户等 级标识信息与所述更新后的配置参数信息的对应关系。
9、 如权利要求 6所述的装置， 其中， 所述匹配模块还设置成： 接收组播业务释放请求， 将所述组播业务释放 请求中携带的所述组播业务标识信息与自身保存的需业务保证的所述各组播 业务标识信息进行匹配；
所述装置还包括： 释放模块， 所述释放模块设置成： 当所述组播业务标 识信息匹配成功时，释放匹配成功的组播业务标识信息对应的所述服务队列。
10、 如权利要求 8所述的装置， 其中，
所述更新模块还设置成： 接收服务队列更新信息， 根据所述服务队列更 新信息中携带的组播业务标识信息及更新后的服务队列信息， 建立所述组播 业务标识信息与所述更新后的服务队列之间的对应关系。
PCT/CN2012/078399 2011-07-19 2012-07-10 一种组播业务的实现方法及装置 Ceased WO2013010443A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BR112014001250A BR112014001250A2 (pt) 2011-07-19 2012-07-10 método e dispositivo para realização de serviço de multidifusão
RU2014105673/08A RU2571398C2 (ru) 2011-07-19 2012-07-10 Способ и устройство для осуществления службы групповой передачи
EP12814733.7A EP2736196B1 (en) 2011-07-19 2012-07-10 Method and device for realizing multicast service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110202423.8 2011-07-19
CN201110202423.8A CN102325035B (zh) 2011-07-19 2011-07-19 一种组播业务的实现方法及装置

Publications (1)

Publication Number Publication Date
WO2013010443A1 true WO2013010443A1 (zh) 2013-01-24

Family

ID=45452709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/078399 Ceased WO2013010443A1 (zh) 2011-07-19 2012-07-10 一种组播业务的实现方法及装置

Country Status (5)

Country Link
EP (1) EP2736196B1 (zh)
CN (1) CN102325035B (zh)
BR (1) BR112014001250A2 (zh)
RU (1) RU2571398C2 (zh)
WO (1) WO2013010443A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102325035B (zh) * 2011-07-19 2017-11-03 中兴通讯股份有限公司 一种组播业务的实现方法及装置
CN107678856B (zh) * 2017-09-20 2022-04-05 苏宁易购集团股份有限公司 一种处理业务实体中增量信息的方法及装置
CN110620829B (zh) * 2018-06-19 2022-08-19 中兴通讯股份有限公司 组播业务标识号的分配方法、装置及设备、存储介质
CN113709676A (zh) * 2020-05-21 2021-11-26 维沃移动通信有限公司 一种多播业务的处理方法、装置及电子设备
CN114143126A (zh) * 2021-11-26 2022-03-04 广州芯德通信科技股份有限公司 一种利用默认vlan的组播数据处理方法、系统及平台
CN114518935B (zh) * 2021-12-31 2025-09-09 国电南瑞科技股份有限公司 一种容器无感知启动方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1756216A (zh) * 2004-09-30 2006-04-05 华为技术有限公司 多媒体广播组播业务系统中业务识别和路由方法
WO2006075277A1 (en) * 2005-01-12 2006-07-20 Koninklijke Philips Electronics N.V. Method and apparatus for multicast communication in wireless communication networks
CN101304548A (zh) * 2007-05-08 2008-11-12 中国移动通信集团公司 多媒体广播/组播业务数据传输系统、方法及终端
CN102056082A (zh) * 2009-11-05 2011-05-11 中兴通讯股份有限公司 多播广播业务配置信息发送方法及装置
CN102325035A (zh) * 2011-07-19 2012-01-18 中兴通讯股份有限公司 一种组播业务的实现方法及装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8429296B2 (en) * 2001-03-06 2013-04-23 Pluris, Inc. Method and apparatus for distributing routing instructions over multiple interfaces of a data router
KR100936586B1 (ko) * 2002-09-19 2010-01-13 엘지전자 주식회사 멀티미디어 방송 및 멀티캐스트 서비스에서의 데이터 전송 방법 및 시스템
CN101146271B (zh) * 2006-09-11 2010-05-19 中兴通讯股份有限公司 cdma2000集群通信系统的群组高速数据传送方法
CN101335907B (zh) * 2007-06-29 2011-04-06 上海贝尔阿尔卡特股份有限公司 基站中用于控制组播业务发送的方法及装置
CN101374066B (zh) * 2007-08-24 2012-04-04 华为技术有限公司 一种组播/单播业务接纳控制的方法、装置及系统
US8427943B2 (en) * 2008-01-28 2013-04-23 Cisco Technology, Inc. Bandwidth-aware multicast load balancing on a multi-interface host
US8312084B2 (en) * 2008-02-28 2012-11-13 Red Hat, Inc. Combined join and state transfer
US7921223B2 (en) * 2008-12-08 2011-04-05 Lemi Technology, Llc Protected distribution and location based aggregation service
CN101547100B (zh) * 2009-05-07 2011-01-19 杭州华三通信技术有限公司 组播接收控制方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1756216A (zh) * 2004-09-30 2006-04-05 华为技术有限公司 多媒体广播组播业务系统中业务识别和路由方法
WO2006075277A1 (en) * 2005-01-12 2006-07-20 Koninklijke Philips Electronics N.V. Method and apparatus for multicast communication in wireless communication networks
CN101304548A (zh) * 2007-05-08 2008-11-12 中国移动通信集团公司 多媒体广播/组播业务数据传输系统、方法及终端
CN102056082A (zh) * 2009-11-05 2011-05-11 中兴通讯股份有限公司 多播广播业务配置信息发送方法及装置
CN102325035A (zh) * 2011-07-19 2012-01-18 中兴通讯股份有限公司 一种组播业务的实现方法及装置

Also Published As

Publication number Publication date
EP2736196A1 (en) 2014-05-28
CN102325035B (zh) 2017-11-03
CN102325035A (zh) 2012-01-18
RU2014105673A (ru) 2015-09-10
EP2736196B1 (en) 2015-09-09
RU2571398C2 (ru) 2015-12-20
BR112014001250A2 (pt) 2017-02-21
EP2736196A4 (en) 2014-07-02

Similar Documents

Publication Publication Date Title
WO2013010443A1 (zh) 一种组播业务的实现方法及装置
KR20140133854A (ko) 무선 네트워크 상에서의 멀티 모달 통신 우선순위
WO2013076638A1 (en) Improved replication management for remote multicast replication network
CN102447746B (zh) 信息提供方法及家庭网关、家庭网络系统
WO2012159538A1 (zh) 一种信息共享的即时通讯系统及方法
CN102711260B (zh) GBR承载业务的QoS处理方法和系统以及设备
WO2013076637A1 (en) Managing multicast streams at a router in a remote multicast replication network (rmr)
CN108023832A (zh) 信息发送方法、装置及系统
WO2011131084A1 (zh) 数据通信系统及方法
CN104579722A (zh) 流统计能力的协商方法及装置
CN103716169B (zh) 点到多点的组播实现方法、网络节点和系统
WO2018010519A1 (zh) 一种建立组播隧道的方法和装置
CN102907044B (zh) 多宽带网络网关下业务调度方法及装置
WO2012041142A1 (zh) 一种建立和拆除双向点到多点标签转发路径的方法及系统
WO2007054006A1 (en) A base station of wideband wireless access system and a method for realizing group-broadcast service
CN103702001B (zh) 电话会议平台和电话会议处理方法
WO2011127824A1 (zh) 服务质量配置的方法、装置和系统
CN103428028B (zh) 异构网络的服务质量维护方法及系统
CN101789897A (zh) 一种协议无关组播中资源预留的方法和路由器
WO2014101733A1 (zh) 报文处理方法和装置
CN103414653B (zh) 一种流量控制方法及系统
CN103414647B (zh) 一种通信处理方法及系统
WO2012174928A1 (zh) 多点控制单元级联会议的注册方法及系统
CN1859278A (zh) 一种多方通信业务的媒体数据包发送方法
JP4974929B2 (ja) 通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12814733

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012814733

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2014105673

Country of ref document: RU

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112014001250

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112014001250

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20140117